Quote Originally Posted by simone.montanari
Now remains the bigger problem of writing the label "Volume set id" in a very easy way on the ISO.
If I have time I will try something this evening.
Yup, that is the problem. If the label information can be written with a standard burning program like Nero while burning an ISO, then this would be a very clean way to let users to modify an ISO file for custom booting, if Klaus would include the code changes. However, if an ISO burn applied the labels that are imbedded in the image (as I suspect), then this gains nothing. While there may be some complex ways to edit the ISO file, that would be rather pointless, since a more direct approach would be to edit the isolinux boot parameters inside the file. That would completely bypass the need for any additional startup code that could read "labels". The only problem, as far as I know, that prevents this now is that there isn't space in the file for lots of added parameters. But it would be much easier to ask Klaus to just enlarge the isolinux boot line and pad it with spaces or something that would be easy to find but not affect booting than it would be to add hokey code to read burn parameter information and then juggle it around and try to affect booting. Such an approach would still require hex editing (or a simple tool that knew what bytes to find in the ISO and accepted input on what to replace it with), and this would be more complex than just setting a burning option, but it shouldn't be beyond the reach of most Linux users if cleanly and clearly documented.