Running FreeBSD 5.0 installer, I see a few messages along the lines of
configured IRQ 3 is not in bitmap of irqs and then the following pair
of lines:
ad0: READ command timeout tag=0 serv=0 - resetting
ata0: resetting devices ..
And then the system seems to jam, the drive light still on, and no
[EMAIL PROTECTED] wrote:
Running FreeBSD 5.0 installer, I see a few messages along the lines of
configured IRQ 3 is not in bitmap of irqs and then the following pair
of lines:
ad0: READ command timeout tag=0 serv=0 - resetting
ata0: resetting devices ..
And then the system seems to jam, the
During buildworld, I wandered off. When I returned, my machine was,
alarmingly, in single user mode, demanding that I run fsck manually.
I'm running fsck right now, and it's finding all sorts of block size
errors, to which I'm simply hitting 'y' and agreeing that things should
be salvaged and
I have no CD drive on my EPIA machine, so I plugged the 2.5 Toshiba
drive into another machine to install FreeBSD 5.2.1 from a minimal
install CD I burned myself.
Installation ran fine on the big machine (a Pentium 4) and FreeBSD was
able to boot on that machine without problem.
I plugged the
Newbie Fodder (skip down the page if old and wise):
The FreeBSD Handbook describes running BIND (named) in a sandbox, i.e.
using chroot to force the named to think that its place in the
filesystem is actually the filesystem root when it's not, so it sees
/somewhere/deep/inthe/file/jungle as /.
There seems to be confusion as soon as IPFW is used for NAT and for
stateful dynamic rules.
My ruleset so far contains the below rules, and I wonder if someone can
tell me if there's anything incorrect about them (with regard to
correctly using NAT and dynamic rulesets):
bash-2.05b# ipfw -a
I'm obviously missing something...
I've read as much about IPFW and firewall packet filtering as I can, and
Im still happy with these very simple rules:
su-2.05b# ipfw -a list
00100 16 1144 divert 8668 ip from any to any in via rl0
00200 17 964 divert 8668 ip from any to any out via rl0
JJB wrote:
First indication is the hit count on the check-state rule. It's zero
which means there is never an match in the keep-state table. For all
practical purposes your firewall keep-state rules are useless.
I was suspicious of that too, but if I remove the keep-state option from
the allow
JJB wrote:
Fundamentally his keep-state rules work and yours don't.
I have used his script exactly, modifying only for the differences in my
ISP's addresses. Everything works as before, and still the check-state
rule is showing zero packets and zero bytes, even though keep-state
rules have been
[EMAIL PROTECTED] wrote:
Hi,
I've tried to install the last freebds4.10 on an ASUS PUNDIT, from the
iso images downloaded from the freeBSD website.
But it can't install. It stops on a :
ata0 : resetting devices
I had that problem. I disabled UDMA (Ultra DMA) in the BIOS, and the
problem was
Bernard Dugas wrote:
Thanks very much, Robert, it was the udma option : but this is quite
inefficient if I can't use UDMA with FreeBSD ?
FreeBSD will drop down to PIO mode, probably mode 4.
According to Scott Mueller's book, PIO mode 4 offers up to 16.67 MB/sec,
whereas UDMA can offer up to 100
I gave up on IRC when it became clear that anyone claiming to be female
was actually male (and slightly twisted - I am a girl! I've got tits
and everything!!!)
Stick to official forums and this usenet group and you should be safe.
(And even then you'll get sexnet ads being posted every now and
Bernardo Marcelo Brummer wrote:
I'm trying to upgrade from 4.7 to 4.9
I made cvsup (src-all), with no problems, then: cd /usr/src and:
make buildworld
It runs for a while (about 10 -15 minutes) and stops (see message bellow)
I already tried cvsup three more times but always with the same result.
My make.conf file contains the line:
MASTER_SITE_OVERRIDE=ftp://ftp.uk.freebsd.org/pub/FreeBSD/ports/distfiles
Someone gave me this line months ago when I asked how to instruct make
to request files from local FTP servers (rather than dumping all
requests on the master server).
However, I
Kris Kennaway wrote:
On Sun, Apr 04, 2004 at 08:33:33AM +0100, Robert Downes wrote:
My make.conf file contains the line:
MASTER_SITE_OVERRIDE=ftp://ftp.uk.freebsd.org/pub/FreeBSD/ports/distfiles
It's documented in /usr/ports/Mk/bsd.port.mk, together with most of
the other port-related
Barry Skidmore wrote:
Are there any users of apcupsd on the list? If so, please respond to me
privately. I have a question about recommended UPS's that work well
with FreeBSD.
I have used apcupsd before. I have an ancient old APC Back-UPS Pro 420
with serial cable, and everything was
I use the US Dvorak keyboard layout, and I find it very difficult to
type in single user mode (when installing world, for example), because
single user mode uses the QWERTY keyboard layout, and does not seem to
pay any attention to kbdmap (I think that's the command name - the one
with the
Robert Downes wrote:
I use the US Dvorak keyboard layout, and I find it very difficult to
type in single user mode (when installing world, for example), because
single user mode uses the QWERTY keyboard layout, and does not seem to
pay any attention to kbdmap (I think that's the command name
Reply to myself again, just to make sure this thread can be of use to
anyone searching archives at any point in the future.
Stéphane Witzmann suggested that the kernel configuration be altered to
specify a default keyboard.
So, after checking NOTES and the name of the keyboard map I want
Kris Kennaway wrote:
Notice the difference between these two approaches? It means there's
basically no chance that what happened with RedHat will ever happen to
FreeBSD.
No, but it surely is possible that the people that devote time to
FreeBSD will be taken for granted, and will drift away
The quick start instructions for the FreeBSD documentation project say
2. Get a local copy of the FreeBSD doc tree. Either use CVSup in
checkout mode to do this, or get a full copy of the CVS repository locally.
I have, so far, used CVSup to reconcile sources and ports and docs, but
I'm
21 matches
Mail list logo
