Dylan Griffiths wrote:
> Lance Levsen wrote:
> My Intel NICs all support PXE natively w/o the need for option ROMs.
Absolutely. On some of our NICs that do support PXE, I use dhcp/tftp
combo to serve up the etherboot .zpxe ROM first. It's also way easier to
test too and removes the floppy/CD hassle.
> Steven's comment about using initrd seems to be the way to go. Give the
> kernel + a minimum environment in an image to the PXE loader, something
> that's enough to initialize itself to be an NFS client.
Yes. Another argument for the rescue disk how-to's too. They detail all
that. I haven't booted from a custom initrd, just a zImage or bzImage,
so I can't say what will work.
> I think I'll have to experiment with using ndb and raw swap to see what
> works best. Linux used to be able to swap to a file, which would be
> the path I'd expect this kind of swap to take.
Yeah, it probably wouldn't be too big a deal to setup a perl FIFO or
netcat server to handle the mkswap side on your server. Then it's just a
matter of the init scripts using nbd to do swapon etc.
Oh, and you'll want to look into the fuse module so that your local
devices are available if you want them.
> Actually, it'd make the one share I have that's shared out via SMB (to
> VMware and Xbox Media Center, which speaks SMB to get movies/etc) happier.
I should note that ext3 also supports Posix ACL's so it's really a
toss-up on your end.
Football is starting. Go Riders!
Cheers,
lance
-- Lance Levsen, Catprint Computing Tel: (306) 493-2249 Cell: (306) 230-8783 Blog: http://www.catprint.ca/blog/ SaskBlogs: http://saskblogs.catprint.ca/
This archive was generated by hypermail 2.1.8 : Sun Nov 05 2006 - 12:02:23 CST