From: Digital I. Inc. <ok...@di...> - 2004-05-18 21:09:46
|
Hello Chris. This is same issue as you discussed in the previous thread. and I am for your opinion - using "device alias" would be the right answer. I dont know which is better, device name approach( your opinion) or major/minor approach(Daniel Slater's opinion), anyway, aliasing by kernel layer would be better. It can be applied for all file systems without fsck problem. one proposal - there are many virtualizing technology. UML, coLinux, Xen, Plex86, LilyVM, ,,,. and they adopt almost same way for using a distribution. maybe the biggest difference is a device name. I ask you that it is impossible to unite all formats? in other words, I hope "Install Once, Runs Anywhere!." --- Okajima. > > >The downside to this method is that it can only be used for a formatted >image. (possibly only ext* so that may leave the reiser fans out) It would >also be nice to be able to have the cdrom, floppy or other removable media >have an entry in fstab that would work for both boot methods. So I think a >true aliasing method should be back on the table. However this may be an >interesting intrem solution. > >chris > > >> Dan Aloni wrote: >>> * cobd: >>> * Support device aliasing, e.g alias="hda2" >> >> I'm in the process of finding an acceptable method of dual booting (I've >> also started writing on the wiki, but what I've written so far are only >> some ramblings). >> >> I've tested on the my native linux and using the LABEL statement in >> fstab works great. Unfortunately, colinux 20040509 can't use it, >> probably due to using kernel 2.4.26, while my native is 2.5.6. >> >> So how should this work ? >> >> 1. label your partitions with e2label (works with ext2 and ext3) >> >> e2label /dev/hda2 ROOT >> e2label /dev/hda3 HOME >> >> 2. modify the fstab to something like >> >> LABEL=ROOT / .... >> LABEL=HOME /home ... >> >> 3. re-boot >> >> It should work with no problem from both native and colinux. >> >> The good news is that e2label finds the correct label under colinux: >> >> # e2label /dev/hda2 >> ROOT >> # e2label /dev/hda3 >> HOME >> # >> >> So probably the only thing is porting colinux to kernel 2.6 ? >> >> On the other hand, aliasing wouldn't harm, I guess. >> >> Ionutz >> >> >> ________ Information from NOD32 ________ >> This message was checked by NOD32 Antivirus System for Linux Mail Server. >> http://www.nod32.com >> >> >> ------------------------------------------------------- >> This SF.Net email is sponsored by: SourceForge.net Broadband >> Sign-up now for SourceForge Broadband and get the fastest >> 6.0/768 connection for only $19.95/mo for the first 3 months! >> http://ads.osdn.com/?ad_id=2562&alloc_id=6184&op=click >> _______________________________________________ >> coLinux-devel mailing list >> coL...@li... >> https://lists.sourceforge.net/lists/listinfo/colinux-devel >> > |