Recent changes to patches: Recent Episodes

None

Recent changes to patches

View Details

  • status: open --> closed-fixed
  • assigned_to: Steven Shiau

View Details

I saw the message. Looks good... very helpful and informative IMHO.

View Details

This issue was addressed in Clonezilla live >= 3.0.0-18 and 20220419-*:

https://clonezilla.org/downloads.php

Please give it a try and let us know the results.

Thanks.

Steven

View Details

Oh, please forgive me. I finally understood what you meant. So you boot Clonezilla live via netboot, and want to run ocs-iso to create a recovery iso file. Yes, in that case, that's true.

Will try to improve ocs-iso and ocs-live-dev based on your patch. Thanks.

Steven

View Details

Since I have ocs_daemonon="ssh" set, I was logged in via ssh... it makes testing easier. The strange colors are custom for my rxvt-unicode terminal via ~/.Xresources :-)

So the screenshot is of a clonezilla live environment (PXE booted from the network). Naturally, the same problem happens at a console... but, again, only if clonezilla is PXE booted from the network.

I think you should be able to reproduce the problem without much trouble.

View Details

So under which GNU/Linux did you run that?

It's recommended to run in Clonezilla live environment, as mentioned here:

https://clonezilla.org/show-live-doc-content.php?topic=clonezilla-live/doc/04_Create_Recovery_Clonezilla

Steven

View Details

You're saying I should be able to create an iso when clonezilla is PXE booted from the network, correct?

I wonder what's causing this error message then?

View Details

It's the same thing we use here. We have used the original one in Clonezilla lite server and it does work well. Therefore I do not think this patch is required.

Thanks anyway.

Steven

View Details

I think it's because the latter looks more like sed or perl to me.

Naturally, this clears things up a fair bit...

https://www.gnu.org/software/bash/manual/bash.html#Shell-Parameter-Expansion

View Details

Also, assuming the patch is useful, I copy/pasted the following bash string replacement to report the script name:

``` ${0##*/}

```

but in retrospect, I think this one is more readable:

``` ${0/#*\//}

```

and may amount to the same thing; I'm certainly not the final authority on bash scripting.

:-/