Jeremy Chadwick wrote:
> Oliver Fromme wrote:
> > If it's really only a web server, then you probably don't
> > need the USB ports. In that case you should remove ohci
> > and ehci from your kernel. The USB interrupt handler is
> > quite heavy-weight, so it can have a noticeable impact if
>
On Mon, Nov 13, 2006 at 08:22:39PM +0100, Greg Byshenk wrote:
> Don't you really need to have a monitor, as well? I _have_ worked
> "blind" before, but I didn't enjoy it. I can imagine having a
> keyboard with me when wandering around, but wouldn't normally have
> a monitor. I had always though
o sort something out.
It's cheaper and faster. And besides that I have console access to the
servers wherever I happen to be that and an internet connection.
- Original Message -
From: "Greg Byshenk" <[EMAIL PROTECTED]>
To:
Sent: Monday, November 13, 2006 9:22 P
On Mon, Nov 13, 2006 at 09:19:45AM -0800, Jeremy Chadwick wrote:
> I'll agree with this (re: webservers not needing USB), except in
> regards to one item: keyboards.
>
> More and more x86 PCs these days are expecting keyboards to be
> USB-based. Yes, PS/2 ports are still present on most (but no
Jeremy Chadwick wrote:
> On Mon, Nov 13, 2006 at 05:33:24PM +0100, Oliver Fromme wrote:
>> If it's really only a web server, then you probably don't
>> need the USB ports. In that case you should remove ohci
>> and ehci from your kernel. The USB interrupt handler is
>> quite heavy-weight, so it c
On Mon, Nov 13, 2006 at 05:33:24PM +0100, Oliver Fromme wrote:
> If it's really only a web server, then you probably don't
> need the USB ports. In that case you should remove ohci
> and ehci from your kernel. The USB interrupt handler is
> quite heavy-weight, so it can have a noticeable impact i
Ivan Voras wrote:
> - The less serious problem: It looks like a whole bunch of built-in
> devices is routed to irq 29: bce, ciss, ohci and ehci. I notice last
> three are giant locked, which doesn't look good, especially since this
> should be a loaded web server.
If it's really only a web ser
On Mon, 13 Nov 2006, Pete French wrote:
There's something unusual going on and I don't know what else to try.
Finally, after fiddling with various options, I've sort-of got it to
work by creating two slices (s1, s2), setting root partition on s1a and
the rest (/usr, /var, etc.) on s2. Now, the "
> There's something unusual going on and I don't know what else to try.
> Finally, after fiddling with various options, I've sort-of got it to
> work by creating two slices (s1, s2), setting root partition on s1a and
> the rest (/usr, /var, etc.) on s2. Now, the "F1 prompt" boot stage
> behaves
Ivan Voras wrote:
- The showstopper: Sysinstall completes (though slowly), but on reboot
the loader doesn't go further than the "F1 prompt" :( This is very
curious, since when booting from install CD the loader shows it
recognizes the CD drive and drives A: and C:, so BIOS seems to be ok. If
I u
The machine in question has a 2-core Xeon, 2GB RAM and a new
ciss-compatible controller, for which I appologise for not remembering
the exact model but it's "200-something" with three attached 7.2k RPM
SATA drives (so it's probably SAS-compatible) in RAID5, and 128 MB cache
with BBU. I'm trying to
11 matches
Mail list logo
