Greetings, I'm working on updating our install of systemimager. We've been running debian versions 3.2.3-6 and 3.4.0-2 from debian stable.
I downloaded 3.6.3-2 from debian testing and experienced several issues: (i386-boot issues) modprobe is borked in th i386-boot deb. This may just be a problem in the debian build. It errors out during the install, complaining about glibc 2.0. Insmod works, so I hardcoded that plus the dependencies into /etc/init.d/* and the install scripts. This works but is not ideal. Building 3.6.3-2 from source on amd64 resulted in the following issues: (amd64-boot issues) /lib and /lib64 are unique directories. The install does not create a library cache file (ld.so.cache), so the linker in the install relies on all libraries being in the trusted directories. Unfortunately, since the only trusted directory is /lib, anything which needs a library in /lib64 fails. I simply collapsed the /lib64 directory into /lib, and symlinked /lib64 to /lib, which makes the filesystem look more like a typical debian install. This works, but is probably not ideal. (si_mkbootpackage issues) The biggest win for us would be gaining the ability to use si_mkbootpackage to create custom install kernels and initrds. Unfortunately, the script as present in 3.6.3-2 exhibits a number of problems. * depends on devfs, which disappears after linux 2.6.12. We need a newer kernel for hardware support. I did not try to switch to udev support, although it might have not been too tough. I just populated a /dev directory with the appropriate entries. * the regexp that is supposed to determine the kernel version (2.4 vs 2.6) fails, and no modules get copied into the initrd. I fixed this, but... * discover is old enough that it doesn't know much about our hardware. forcing modules to be probed (and having static /dev entries) gets items working, but is kludgy. Other issues: ---------------------- the install script edits /etc/fstab to match actual hard drives, but does not edit /etc/lilo.conf. I can fix this easily, but, again, should I just update to the latest source? Are these fixed in the latest source release? And would it be more practical to start from 3.7.3(4)? I'd be happy to contribute any fixes back to the project. Sincerely, Justin Thiessen -------------------------- [EMAIL PROTECTED] ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Sisuite-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/sisuite-users
