Welcome
Welcome to refracta

You are currently viewing our boards as a guest, which gives you limited access to view most discussions and access our other features. By joining our free community, you will have access to post topics, communicate privately with other members (PM), respond to polls, upload content, and access many other special features. In addition, registered members also see less advertisements. Registration is fast, simple, and absolutely free, so please, join our community today!

Snapshot : Customising boot menu (isolinux/syslinux)

Tips and Instructional topics. Not for support questions.

Re: Snapshot : Customising boot menu (isolinux/syslinux)

Postby meandean » Sat Nov 12, 2011 6:49 pm

dzz wrote:Well, the point of this thread was originally an easy way for a user to create/modify and quickly test a custom menu, "custom" being the essence of Snapshot. That's why I wrote in the how-to section (we're really in "discuss" territory now)
And I just wanted to add another method for testing a custom menu to your howto and answer the questions you posed, ergo discussion.

I didn't mean to suggest changes in original snapshot (working great as-is) which might go against any standards.
Sheesh I am not sure what the original snapshot actually is anymore. Obviously fsmithred can decide what he wants to include in refracta snapshot.
I was just talking about changing stuff for my snapshot scripts. I rewrote mine last nite after reading this thread. It is now all self-contained in one script, no files laying around. I like it! So thanks again for indulging in some discussion.


what are the "standards" and why.
All kinds of iso-levels, eltorito, emulation and no-emulation, joliet, rockridge, and on and on and on.
Basically (and in very general terms) they try to be sure that different systems can understand the data on the disk.


So the boot catalog is indeed autogenerated... but *You must specify* where it will go.

Actually I think the point to all that is that with the -c option you get a hidden boot catalog which complies with some standard(s). Otherwise you get a non-hidden boot catalog wich may or may not be compliant.

I would say it probably has to do with ancient computers that didn't really boot from a cd but did boot from floppy. So you create a hidden 'floppy' image on the cd with the proper boot files to make the computer think it is booting a floppy. Once again that is in general terms rather than technical specifics. Which is probably nothing to be concerned about anymore unless someone is still pecking away on a 350mhz PII system from 1997.
User avatar
meandean
 
Posts: 392
Joined: Wed Mar 09, 2011 5:16 am

Previous

Return to How-to

Who is online

Users browsing this forum: No registered users and 0 guests

suspicion-preferred