Soeren Schmidt <[EMAIL PROTECTED]> wrote:
It seems Aaron D. Gifford wrote:
Then on one of the messages, I noticed a link to Patrick Bihan-Faou's
problem report, read it, and tried out his patch under 5.0-CURRENT
(having completed my install of 5.0-RELEASE and updated to -CURRENT).
Hi,
When I attempted to install FreeBSD 5.0-RELEASE on a Shuttle SS51G box,
just like some other users, I encountered the "ata0: READ command
timeout" error during boot. I then tried 4.7-RELEASE and saw the same
problem.
A quick search of the FreeBSD mail archives turned up other users with
Is there any chance of getting the fix suggested in PR-47024 in 5.0
before release? Looks like a similar script bug with natd start-up was
fixed in 4.x-STABLE back in Feb. of 2002 -- See the CVS logs for
/etc/rc.network, in particular, cjc's log entries for revision 1.124
(MAIN) and revision 1
Hi,
There's trouble in the /etc/rc.d/ipfw script in how it changes things
versus the 4.7 /etc/rc.network script when it comes to NAT in certain
configurations.
For example, on my home gateway box, rc.conf contains:
# Network address translation:
natd_enable="YES"
natd_interface=""
natd
Craig Boston wrote:
On Wed, 2002-12-11 at 13:45, Aaron D. Gifford wrote:
Let me correct this to state that the full volume name was "raid5volume"
and I just shortened it to save typing. This turns out to be important.
Looking at newfs.c, it looks like the last letter of the speci
I wrote in my previous message:
>
># newfs -O 2 -U /dev/vinum/raid5vol
>newfs: /dev/vinum/raid5vol: 'e' partition is unavailable
>
...
>Here's my vinum setup:
...
> volume raid5vol
Let me correct this to state that the full volume name was "raid5volume"
and I just shortened it to save typing.
Okay,
I had a vinum RAID5 set working on 4.7. Since I didn't have any data on
it yet and saw today's announcement of 5.0-RC1, I thought I'd give
5.0-RC1 a try on the box in question. Vinum sees the RAID5 set I
created just fine, so I decided to use newfs to create a UFS2 filesystem
on the vo
Hello,
For fun, this last weekend I decided to update from 3.4-STABLE to
-CURRENT and try out some of the new features. I grabbed the
sources (cvsup) and following the directions in UPDATING managed
to build everything and install everything. Whew! I then compiled
a new GENERIC kernel and rebo
I'm still trying to upgrade from 3.0-RELEASE to 3.0-CURRENT
unsuccessfully. It used to die in perl, then that was fixed, but for
the past 2 days, it has been dying in /usr/src/sys/boot/i386/libi386.
Is this a known problem? Yes, I'm a CURRENT newbie, but hopefully only
until the split to 3.1 whe
