|
Hi guys. Well, after locking
myself in my office for a day, I figured it out. (amd x86_64, even with
sata drives. Happy happy happy!) The si_mkbootserver stuff threw
me off, when all I really needed was to run si_mkclientnetboot.
(si_mkbootserver still seems to insist on a pxe daemon, which really isn’t
around anymore, especially for redhat!). Anyway, I have a simple question-- a
minor annoyance, but requires manual intervention upon booting a cloned client. When the client comes up after being
imaged, kudzu insists that the two network Ethernet devices were “removed”,
and prompts the user to remove or keep them. (then, kudzu “finds”
the two network devices right away as well….). the result is
that if you accidently “remove device” as prompted, you wipe out
the client’s Ethernet config and have to do it all
over. Choosing to “keep configuration”
seems to work ok, but as I said- requires manual intervention when booting the
first time. Any idea why this is so? Anyone
know how I can prevent the system from being configured so it’s thinking
the Ethernet devices are “new”? As I said- minor annoyance. I’m
pretty sure it’s a systemconfigurator thing, but the modprobe.conf
entries that are commented out (and subsequently added!) are the SAME.
(alias eth0 tg3)……. PS: I tried to build 3.7.x, but had issues
on the client with the RPM failing the MD5 checksum. I’m more
comfortable using the (distributed, stable) rpms…….. |
------------------------------------------------------------------------- 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
