> I want to tighten up my spaces for diskless machines and I came across
> this puzzle with pxeboot:
>
> I can share /usr and most other filesystems, but my individual roots
> for the machine each have to have the full kernel. But /boot/kernel
> is rather large these days and totally identical, s
On Sun, Jul 01, 2007 at 05:35:40PM -0400, Martin Cracauer wrote:
> Bernd Walter wrote on Sun, Jul 01, 2007 at 09:36:41PM +0200:
> > On Sun, Jul 01, 2007 at 02:13:34PM -0400, Martin Cracauer wrote:
> > 4) Use different / on the same server filesystem with hardlinked /boot.
>
> Hmm, directory hardl
Bernd Walter wrote on Sun, Jul 01, 2007 at 09:36:41PM +0200:
> On Sun, Jul 01, 2007 at 02:13:34PM -0400, Martin Cracauer wrote:
> > I want to tighten up my spaces for diskless machines and I came across
> > this puzzle with pxeboot:
> >
> > I can share /usr and most other filesystems, but my indi
On Sun, Jul 01, 2007 at 02:13:34PM -0400, Martin Cracauer wrote:
> I want to tighten up my spaces for diskless machines and I came across
> this puzzle with pxeboot:
>
> I can share /usr and most other filesystems, but my individual roots
> for the machine each have to have the full kernel. But /
On Mon, Jun 11, 2007 at 05:31:54PM -0400, Mark Saad wrote:
Hello Hackers@
I have been searching around and I can not find an answer to a
problem of mine . Does anyone know if its possible
to make camcontrol show the drive health for drives in a HP SMART Array
. Currently it will show the A
>NetBSD:
> dev/pci/satalink.c
>
>/*
> * Rev. <= 0x01 of the 3112 have a bug that can cause data
> * corruption if DMA transfers cross an 8K boundary. This is
> * apparently hard to tickle, but we'll go ahead and play it
> * safe.
> */
>
I want to tighten up my spaces for diskless machines and I came across
this puzzle with pxeboot:
I can share /usr and most other filesystems, but my individual roots
for the machine each have to have the full kernel. But /boot/kernel
is rather large these days and totally identical, so I'd rather
> >> Any input on the reliability of SII3512 is also welcomed.
> >
> >dmesg | grep 3512
> >satalink0: Silicon Image SATALink 3512 (rev. 0x01)
> >
> >No reliability problems from the 3512. (up 74 days)
> >
> >This is on an Alpha box running NetBSD. I haven't tried the 3512
> >with FreeBSD.
I took
On Sun, 1 Jul 2007 11:58:27 +0200
Erik Trulsson <[EMAIL PROTECTED]> wrote:
> The msk(4) driver should support that chip. This driver is also
> available in both -CURRENT and 6-STABLE and thus will appear in both
> FreeBSD 6.3 and 7.0.
great! is it as good as Marvell's one?
[SorAlx] ridin' VN150
On Sun, Jul 01, 2007 at 02:30:00AM -0700, [EMAIL PROTECTED] wrote:
> On Sun, 1 Jul 2007 01:26:09 -0700
> Josef Grosch <[EMAIL PROTECTED]> wrote:
>
> > There are 3 drivers that I have been using with FreeBSD 6.2-RELEASE
> > and 6.2-RELEASE-p5. They are
> >
> > 1) Intel's new driver for em
> >
>
On Sun, Jul 01, 2007 at 02:30:00AM -0700, [EMAIL PROTECTED] wrote:
> On Sun, 1 Jul 2007 01:26:09 -0700
> Josef Grosch <[EMAIL PROTECTED]> wrote:
>
> > There are 3 drivers that I have been using with FreeBSD 6.2-RELEASE
> > and 6.2-RELEASE-p5. They are
> >
> > 1) Intel's new driver for em
The em
On Sun, 1 Jul 2007 01:26:09 -0700
Josef Grosch <[EMAIL PROTECTED]> wrote:
> There are 3 drivers that I have been using with FreeBSD 6.2-RELEASE
> and 6.2-RELEASE-p5. They are
>
> 1) Intel's new driver for em
>
> 2) Adaptec's new driver for the 3805
>
> 3) 3ware's new SATA RAID controller (9500
There are 3 drivers that I have been using with FreeBSD 6.2-RELEASE and
6.2-RELEASE-p5. They are
1) Intel's new driver for em
2) Adaptec's new driver for the 3805
3) 3ware's new SATA RAID controller (9500)
The drivers can be found :
Intel:
http://downloadcenter.intel.com/T8Clearance.aspx
13 matches
Mail list logo
