Dann, Do you have any plans to update to debian packages to 3.7.4? If not can you possibly offer some pointers as to the steps to create a new package?
Thanks Alan > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On > Behalf Of Andrea Righi > Sent: Friday, October 06, 2006 2:40 AM > To: [email protected] > Cc: Dann Frazier > Subject: Re: [Sisuite-users] debian, systemimager > versions,and x86_64 support > > Not yet... the official maintainer of systemimager is Dann > Frazier (I've added his email in CC), maybe you can ask > directly to him if he has more recent packages available for > Debian... or maybe he can give to you useful hints to build it... > > Cheers, > -Andrea > > Alan Holmes wrote: > > Andrea, > > > > Are there debian 3.7.4 packages available anywhere? The > only version I > > can find on the debian mirrors or download.systemimager.org > in stable, > > testing and unstable is 3.6.3-2 > > > > Alan > > > >> -----Original Message----- > >> From: [EMAIL PROTECTED] > >> [mailto:[EMAIL PROTECTED] On Behalf Of > >> Andrea Righi > >> Sent: Thursday, October 05, 2006 4:55 PM > >> To: [email protected] > >> Subject: Re: [Sisuite-users] debian, systemimager > versions,and x86_64 > >> support > >> > >> Justin, > >> > >> it would be better to start from 3.7.4... a lot of > problems you found > >> should be fixed in that release. Even if it's tagget as "unstable" > >> 3.7.4 is surely more stable than 3.6.3, since it includes > *a lot* of > >> bugfixes... unfortunately at the moment I've not a testing machine > >> with Debian, so it's quite difficult for me to check the > particular > >> problems for Debian, but if you want to start a bugfix > activity with > >> the last release I'll be happy to help you. > >> > >> Cheers, > >> -Andrea > >> > >> Justin Thiessen wrote: > >>> 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 ------------------------------------------------------------------------- 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
