Hello, I have just started reading about SystemImager. In the manual, there are a lot of warnings that you can only use an image on identical hardware. However, I can't figure out why there would be such a restriction.
With hardware autodetection (thanks to udev) and comprehensive initrd systems in modern Linux distributions, I don't think it really matters all that much. I can take a single kernel (with its initrd and modules) and boot it up on all sorts of machines. They don't have to have the same type of network card, disk controller, etc. So why would SystemImager require the same type of network card? Surely the initrd would load the module for the network card before SystemImager ever gets to run? As long as it's still eth0, SystemImager should be happy, right? The only problem I can think of is differeng names for hard disk devices. /dev/hda on IDA systems vs. /dev/sda on SCSI or SATA ones, for instance. But even that can be worked around trivially. A udev rule could automatically assign symlinks to the primary disk in the system. Or, with LVM support in initrds, by the time SystemImager boots, /etc/fstab can be the same everywhere. (The only trick would be at install time to partition the correct disk) So it seems that most things would just work, and really the only diverging thing would be hard disks. And even that can be worked around pretty easily. So, what am I missing? Or is the documentation just very outdated there? Thanks, -- John ------------------------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ Sisuite-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/sisuite-users
