From: Jacob Gorm Hansen <jacobg@diku.dk>
To: Kip Macy <kip.macy@gmail.com>
Cc: James Bulpin <james@xensource.com>,
xen-devel <xen-devel@lists.xensource.com>
Subject: Re: Diskless boot at cambridge
Date: Thu, 14 Apr 2005 11:14:59 -0700 [thread overview]
Message-ID: <425EB323.6000705@diku.dk> (raw)
In-Reply-To: <b1fa2917050414110345119787@mail.gmail.com>
Kip Macy wrote:
>>I am using Grub 0.95 with an UNDI patch I found somewhere, that means I
>>can PXE-boot from some (at least e1000) network adapters not directly
>>supported by Grub.
>
>
> Thanks. Do you know offhand if that supports the tg3 chip?
No, sorry I don't. If you can't get the tg3 working another option is to
drop in an eepro100 or old 3com just for use with Grub.
>>I would recommend NFS for debug-rootfs, as with iSCSI you still have a
>>chance of corrupting the fs image.
>
> Do you export a separate mount point to each client, or do you have
> something like cluster NFS?
>
What I usually do for debugging is share the same mount point, and then
mount /tmp and other similar stuff from a ramdisk formatted at boot, or
from tmpfs.
Jacob
next prev parent reply other threads:[~2005-04-14 18:14 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-14 17:29 Diskless boot at cambridge Kip Macy
2005-04-14 17:39 ` James Bulpin
2005-04-14 17:49 ` Jacob Gorm Hansen
2005-04-14 18:03 ` Kip Macy
2005-04-14 18:14 ` Jacob Gorm Hansen [this message]
2005-04-14 18:46 ` Adam Heath
2005-04-15 2:26 ` Jacob Gorm Hansen
2005-04-14 17:51 ` Kip Macy
2005-04-14 18:28 ` James Bulpin
2005-04-14 18:42 ` Jacob Gorm Hansen
2005-04-15 10:43 ` Tim Deegan
-- strict thread matches above, loose matches on Subject: below --
2005-04-14 19:15 Ian Pratt
2005-04-15 0:45 James Harper
2005-04-15 16:21 ` Adam Heath
2005-04-15 5:20 William (Andy) Smith
2005-04-15 6:48 Ian Pratt
2005-04-16 5:20 James Harper
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=425EB323.6000705@diku.dk \
--to=jacobg@diku.dk \
--cc=james@xensource.com \
--cc=kip.macy@gmail.com \
--cc=xen-devel@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.