From: Ralf Baechle <ralf@linux-mips.org>
To: Andrew Sharp <andy.sharp@onstor.com>
Cc: Laurent GUERBY <laurent@guerby.net>,
Jon Fraser <jfraser@broadcom.com>,
Andrew Wiley <debio264@gmail.com>,
"linux-mips@linux-mips.org" <linux-mips@linux-mips.org>,
"Maciej W. Rozycki" <macro@linux-mips.org>
Subject: Re: Bigsur?
Date: Wed, 20 May 2009 20:16:18 +0100 [thread overview]
Message-ID: <20090520191618.GA32295@linux-mips.org> (raw)
In-Reply-To: <20090520110105.6fb81573@ripper.onstor.net>
On Wed, May 20, 2009 at 11:01:05AM -0700, Andrew Sharp wrote:
> Question: are machines that must be NFS-root and tftp booted acceptable
> or not acceptable for such work? The machines in question would 750MHz
> Sibyte 1250s, so 3 Gigabit ports natively, and 2 serial consoles.
For many uses that will be decent but there are still a few things out
there that don't quite work the same way on NFS that they do on other
filesystems and that tends to break some software and autoconf-like
things. I'd probably give such a config a 90% score - good for most stuff.
Ralf
next prev parent reply other threads:[~2009-05-20 19:16 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-16 3:14 Bigsur? Andrew Wiley
2009-05-18 14:13 ` Bigsur? Ralf Baechle
2009-05-18 16:13 ` Bigsur? Jon Fraser
2009-05-18 16:31 ` Bigsur? David Daney
2009-05-18 17:23 ` Bigsur? Maciej W. Rozycki
2009-05-18 17:28 ` Bigsur? Markus Gothe
2009-05-18 19:02 ` Bigsur? Imre Kaloz
2009-05-18 19:37 ` Bigsur? Jon Fraser
2009-05-18 22:23 ` Bigsur? Ralf Baechle
2009-05-18 22:47 ` Bigsur? Maciej W. Rozycki
2009-05-19 12:17 ` Bigsur? Laurent GUERBY
2009-05-19 12:53 ` Bigsur? Ralf Baechle
2009-05-20 18:01 ` Bigsur? Andrew Sharp
2009-05-20 19:16 ` Ralf Baechle [this message]
2009-05-20 19:22 ` Bigsur? Manuel Lauss
2009-05-20 20:21 ` Bigsur? Laurent GUERBY
2009-05-20 23:17 ` Bigsur? Ralf Baechle
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=20090520191618.GA32295@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=andy.sharp@onstor.com \
--cc=debio264@gmail.com \
--cc=jfraser@broadcom.com \
--cc=laurent@guerby.net \
--cc=linux-mips@linux-mips.org \
--cc=macro@linux-mips.org \
/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.