On 02/05/2010 05:13 AM, Thomas Bächler wrote:
Am 05.02.2010 04:24, schrieb Gerardo Exequiel Pozzi:
I was thinking about dropping the special udev rule and using blkid to find the right device, it has an option for that. I also thought about a failsafe mechanism in case the label is incorrect.
This sound interesting. Are you talking about blkid -t LABEL="xyz" ?
Didn't look at the manpage, but yes, something like that.
Oops, I tried without this rule, works but only when booting the iso as disk (/dev/sd) if you boot the iso as cdrom blkid does not list any device. if you force blkid /dev/sr0 will work.
Ah, not good. Maybe we keep the rule then. So my ideas were (if you have time to do them, I don't right now):
- Remove the special vfat handling in favor of the cool blkid - Add an "archisodevice=" fallback option that will override archisolabel and simply mount the specified device.
Implemented http://github.com/djgera/archiso/commit/fbb210ed79faec77985975fa6434c6088079...
- If nothing can be found, use dialog to display a list of block devices archiso can try.
I guess that the option archisodevice= is suficient. If something fails user can load the "special" module, then exit from the shell and continue with the device specified in parameter.
And then something that needs changes in mkinitcpio: Instead of doing the mounting in a special hook (and not letting /init finish), register a "mount hook" that will be run right at the end of /init and let /init finish as usual. No idea if it's a good idea, I will have to look at the code again.
This sound interesting. But I have no idea about this, I leave it in your hands :) Thanks, -- Gerardo Exequiel Pozzi ( djgera ) http://www.djgera.com.ar KeyID: 0x1B8C330D Key fingerprint = 0CAA D5D4 CD85 4434 A219 76ED 39AB 221B 1B8C 330D