All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jacob Gorm Hansen <jacobg@diku.dk>
To: James Bulpin <james@xensource.com>
Cc: 'Kip Macy' <kip.macy@gmail.com>,
	'xen-devel' <xen-devel@lists.xensource.com>
Subject: Re: Diskless boot at cambridge
Date: Thu, 14 Apr 2005 10:49:01 -0700	[thread overview]
Message-ID: <425EAD0D.8030103@diku.dk> (raw)
In-Reply-To: <002701c54118$e4ef3670$b13a6a83@falcon>

James Bulpin wrote:
> Kip,
> 
> We use either grub with tftp (limited driver support here), or XenoBoot
> (now an optional function of the new Xen demo CD). We have a fairly
> elaborate system involving our lab-wide NFS tree and scripts and
> symlinks for getting the right images for each machine. Root filesystems
> for diskless systems are either iSCSI, as previously discussed or NFS.

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.

I would recommend NFS for debug-rootfs, as with iSCSI you still have a 
chance of corrupting the fs image.

Jacob

  reply	other threads:[~2005-04-14 17:49 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 [this message]
2005-04-14 18:03     ` Kip Macy
2005-04-14 18:14       ` Jacob Gorm Hansen
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=425EAD0D.8030103@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.