RE: [Sisuite-users] IA64 questions

[Bernard Li]

IA64 should still work, though I have not recently compiled it.   The latest stable is 3.6.2, though the code in branch/3.6.x has a bunch of bugfixes which you probably want, so just check out the code from SVN.   Once the code is checked out, run:   % make source_tarball % rpmbuild -ta /tmp/<systemimager-tarball>   It will then build the necessary RPMs for you to use.   Regarding using eth1 on your clients, it might just be a simple search and replace of eth0 with eth1 in your autoinstall script in /var/ilb/systemimager/scripts/.   Cheers,   Bernard From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Brodie, Kent Sent: Wednesday, January 11, 2006 13:59 To: sisuite-users@lists.sourceforge.net Subject: [Sisuite-users] IA64 questions Hi!   I’ve been using systemimager on my ia64 servers (RHEL3) for some time now.  Works well!!   Problems started when I changed my clients to use their gig port (eth1) instead of the 10/100 port (eth0).     Looks like the default is to ONLY use eth0 as clients, and the tg3 driver isn’t loaded.   /etc/modules.conf on the clients gets overwritten.    I can get the clients to run as they should, but only after they’re imaged and I tweak a few files- manually.   Ugh.   I have done list searching, and the questions I have seem to have inconclusive answers—a brief bit if help would be great, to avoid my wasting time!   Q1: I am currently at systemimager 3.2.3-1.    Latest systemimager appears to be 3.4.1-1.  Cool, but I cannot find any boot files for IA64 beyond Version 3.3.2-1….  Does this mean I’m stuck at trying to use 3.3.2-1…?    Is ia64 development dead?   Q2: Does anyone know what version, if any, the bcm5700/tg3 issues are fixed, so my gig ports actually work?      Q3: Do any of the newer versions support the ability to “only” use eth1 on the clients, and leave eth0 off???   Thanks in advance for any insight you can provide!     --Kent