cvs annotate is your friend. The code was added in revision 1.95 of
src/sys/net/if.c by Jonathan Lemon. Please talk to him about what should
be done to fix the drivers.
Yes, and I shall... but this came up in a public forum. I'm making a point
here (that apparently you and others don't
On Thu, Jan 25, 2001 at 02:18:01PM -0800, Matthew Jacob wrote:
An update on this
If the server is Solaris, neither NetBSD nor FreeBSD (i386 or alpha) have a
problem (as clients).
The problem is therefore in some interaction between this server (see
http://www.traakan.com
I came across an embarrassing comparison last night-
FreeBSD NFS clients (well, i386) stop writing files at 4GB.
Solaris, with O_LARGEFILE options in the open arguments, does not.
Does anyone here know what FreeBSD ought to be doing about this?
Or have I missed something? There is no
On Thu, 25 Jan 2001, Dan Nelson wrote:
In the last episode (Jan 25), Matthew Jacob said:
I came across an embarrassing comparison last night-
FreeBSD NFS clients (well, i386) stop writing files at 4GB.
Solaris, with O_LARGEFILE options in the open arguments, does not.
Does
something that "just works"... .:-)
On Thu, 25 Jan 2001, Matthew Jacob wrote:
On Thu, 25 Jan 2001, Dan Nelson wrote:
In the last episode (Jan 25), Matthew Jacob said:
I came across an embarrassing comparison last night-
FreeBSD NFS clients (well, i386) stop writing fi
On Thu, 25 Jan 2001, Dan Nelson wrote:
In the last episode (Jan 25), Matthew Jacob said:
On Thu, 25 Jan 2001, Dan Nelson wrote:
Make sure you're using NFSv3 mounts (should be the default, but if not,
add "nfsv3" to the options column in fstab). I cross-mount FreeBSD
But I won't let it go! I was hoping to replace my Solaris box with either
FreeBSD or NetBSD as my main home directory server. FreeBSD 4.2 panics part
way through the first LADDIS runs I was using to test it with and I can't get
NetBSD to start as a LADDIS client (I hadn't got the auth
On Thu, 25 Jan 2001, Andrew Gallatin wrote:
Matthew Jacob writes:
I came across an embarrassing comparison last night-
FreeBSD NFS clients (well, i386) stop writing files at 4GB.
Solaris, with O_LARGEFILE options in the open arguments, does not.
Does anyone here
Matthew Jacob writes:
Same code compiled on Solaris is happy.
Perhaps there's some braindamage in it. I'm afraid of something like:
#ifdef Solaris
typedef filefoo u_int64_t;
#else
typedef filefoo u_int32_t;
#endif
I'll try with dd then,... let y'all know
knowing NFS in general far better than *BSD in specific, I would guess the best
thing to do (if you suspect server/client communication anomaly) is to grab a
snoop/tcpdump of the failure. I'm trying to think of a clever way to cause the
failure immediately, so you're not tracing 4GB of
Nope, been fixed. I fixed it quickly and was yelled at by DES who fixed it
better.
=== usr.bin/vmstat
cc -O -pipe -I/usr/src/usr.bin/vmstat/../../sys -I/usr/obj/usr/src/i386/usr/in
clude -c /usr/src/usr.bin/vmstat/vmstat.c
/usr/src/usr.bin/vmstat/vmstat.c:483: warning: `pgtok' redefined
Debugger("panic")
Stopped at Debugger+0x44: pushl %ebx
db t
Debugger(c02b8303) at Debugger+0x44
panic(c02c9040,bfc0,581000,c02ea620,c030ab0c) at panic+0x70
kmem_malloc(c0312d20,bfc0,8,bfbff810,c898) at kmem_malloc+0xd7
malloc(bfbff810,c02ea620,8,c0ff1e00,c898) at
* Matthew Jacob [EMAIL PROTECTED] [010122 15:32] wrote:
Debugger("panic")
Stopped at Debugger+0x44: pushl %ebx
db t
Debugger(c02b8303) at Debugger+0x44
panic(c02c9040,bfc0,581000,c02ea620,c030ab0c) at panic+0x70
kmem_malloc(c0312d20,bfc0,8,bfbff81
mountd exporting stuff causes a panic.
This is and isn't my fault, struct ucred needs a lock for refcounts.
Since mount uses ucreds in userspace and passes them to the kernel
we have a issue when struct mtx changes. I'm going to take a shot
at removing struct ucred from userland this
The loopback nfs hangs that have been with us for a month have now propagated
to -stable.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
I'll confirm a hang on both alpha i386 (both SCSI, qlogic ahc resp). The
i386 was SMP. The Qlogic wasn't. Both were hung with phk's make -j 256
foolery.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Well, details would be nice.
I checked in current with little luck. Does -current support VXA-1 tape
drives by Ecrix. The site claims that freebsd does, but the only response
by someone that has one says that it won't successfully backup.
To Unsubscribe: send mail to [EMAIL
On Mon, 15 Jan 2001, Matthew Jacob wrote:
FWIW, serial now is happy again. I guess the planets realigned.
Nope- it just happens more fitfully.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Cool!
On Sat, 13 Jan 2001, David O'Brien wrote:
Until Paul Richards fixes the bug, do NOT run `pkg_update' on a package
w/o a version number in the name. Ie, ``pkg_update gtk.tgz'' will delete
every package off your system.
--
-- David ([EMAIL PROTECTED])
GNU is Not Unix /
Interesting theory, but no- that wasn't it.
Matthew Jacob wrote:
Something wierd has been happening lately- the serial console on my i386
machine works fine up until init is forked.. THen the output is mangled, and
one gets replicated and/or mangled stuff. On a reboot I'm getthing
Matthew Jacob wrote:
Yeah, weird. I'm at 9600... What's wierd is that it's got to be some userland
induced thing because printouts from the kernel are fine until init is
invoked...
This is an ongoing "Hmm, that is strange!" type problem. There are several
symptoms
isp_pci.c just moved from sys/pci to sys/dev/isp (for maintenance ease).
You will need to reconfig kernels if you included this.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Good guess, I shouldn't wonder, but:
quarm.feral.com diff /etc/rc.serial /usr/src/etc/
quarm.feral.com
On Wed, 10 Jan 2001, Bruce Evans wrote:
On Mon, 8 Jan 2001, Matthew Jacob wrote:
Something wierd has been happening lately- the serial console on my i386
machine works fine up
Something wierd has been happening lately- the serial console on my i386
machine works fine up until init is forked.. THen the output is mangled, and
one gets replicated and/or mangled stuff. On a reboot I'm getthing things
like:
Waiting (max
Same with me.
All the machines that I have running Current dumped core at the same
place this morning.
=== share/termcap
ex - /usr/src/share/termcap/termcap.src /usr/src/share/termcap/reorder
/dev/null
Segmentation fault - core dumped
*** Error code 139
Stop in
Ta-da!
In message [EMAIL PROTECTED] Matthew Jacob
writes:
: Same with me.
This sounds like a job for Captain UPDATING:
20010101:
ex and vi were broken by some changes to sys/queue.h. If
you have a bad vi (and are getting core dumps when building
termcap), you can
Why in (insert favorite deity)'s name does ex and vi depend on
sys/queue.h ?
Oh, christ, who knows? I just saw the new David Mamet film "State
Main"... in one scene, Alec Baldwin has just crashed a stationwagon and
flipped it, wiping out the only stoplight in this town. he
I'm getting these on NFS for loopback.
On 29-Dec-00 Poul-Henning Kamp wrote:
I am totally unable to complete a
cd /usr/src
cvs -q update -P -d -A
on any of my two -current systems.
The systems stalls as described in my email yesterday.
CCD is now out of the
I'll try- lots on plate to do.
There's a lot of iffy stuff with ithreads on alpha. But this theory of yours
doesn't match the situation where I can then still log in and ping, but that
the NFS loopback mount is still hosed.
I went back to building across NFS and that worked mucho better.
:
:
:I'll try- lots on plate to do.
:
:There's a lot of iffy stuff with ithreads on alpha. But this theory of yours
:doesn't match the situation where I can then still log in and ping, but that
:the NFS loopback mount is still hosed.
:
:I went back to building across NFS and that
I had a panic just now:
db t
tprintf() at tprintf+0x7c
nfs_msg() at nfs_msg+0x28
nfs_timer() at nfs_timer+0x1fc
softclock() at softclock+0x4f4
sithd_loop() at sithd_loop+0x18c
exception_return() at exception_return
This is where it's saying the server isn't responding... and as best as I can
Hmm. The client wasn't following symlinks. The patch seems
simple enough, but it probably shouldn't just swallow the
error.
It looks like the last phk simplification lost some of the
functionality of the previous code- that I can fix.
On 23 Dec 2000, Assar Westerlund wrote:
Matthew Jacob
I'm pretty sure that the server had no symlinks in that filesystem.
On 23 Dec 2000, Assar Westerlund wrote:
Matthew Jacob [EMAIL PROTECTED] writes:
Hmm. The client wasn't following symlinks.
You sure? What happens is when you queue up an nfs operation provoked
by following a symlink
A month or so ago I queried/complained about src/sys/modules getting corrupted
with architecture specific derived files such that I could no longer share
between i386 alpha.
Part of this issue had to do with having some idiocy on my part, but part of
it *seems* to have to do with if you change
Should be fixed.
Savecore isn't working in -current, dying in my case with "read:
invalid argument". (This is on an Alpha -- I don't have an i386
-current machine to test it on at the moment.) I traced it down to
the fact that getbootfile() is returning "kernel" -- not the full
pathname
Though the alpha code (alpha/libalpha/bootinfo.c) also fill in a lot of
stuff in bi, it has no reference at all to "kernelname". Did it ever
work? :-)
Hmm. Maybe not. I'd convinced myself that the loader is currently just
passing "kernel" either as an environmental variable or in
Savecore isn't working in -current, dying in my case with "read:
invalid argument". (This is on an Alpha -- I don't have an i386
-current machine to test it on at the moment.) I traced it down to
the fact that getbootfile() is returning "kernel" -- not the full
pathname as the man page
kernel to have the actual path or not.
It is supposed to. Looks like a bug in the alpha startup code somewhere:
uname -a
FreeBSD laptop.baldwin.cx 5.0-CURRENT FreeBSD 5.0-CURRENT #40: Fri Nov 10
15:17:48 PST 2000 [EMAIL PROTECTED]:/usr/src/sys/compile/LAPTOP-card
i386
sysctl
kernel to have the actual path or not.
It is supposed to. Looks like a bug in the alpha startup code somewhere:
uname -a
FreeBSD laptop.baldwin.cx 5.0-CURRENT FreeBSD 5.0-CURRENT #40: Fri Nov 10
15:17:48 PST 2000 [EMAIL PROTECTED]:/usr/src/sys/compile/LAPTOP-card
i386
Well, things are more broken than I thought.
The -current loader for alpha is passing "kernel"
in the bootinfo structure- not the full pathname.
Loader bug.
What's amusing is that kenv does see a full pathname.
So, now why did the lines below fail to see the pathname?
Hmmm.. ponders
On Mon, 6 Nov 2000, John W. De Boskey wrote:
Hi,
Each night I run a 'make release' and then tar it off to
a public storage area...
For some time now, tar has been complaining...
tar: cdrom/disc2/dev/acd0t32: minor number too large; not dumped
tar: cdrom/disc2/dev/acd0t33: minor
Hmm. I've seen several panics over the last day or so with -current where /
got corrupted (ino 2).
On Thu, 2 Nov 2000, Justin T. Gibbs wrote:
I beleive that I've somehow corrupted my /dev on my laptop.
An ls -l in there causes an instant panic:
Copied by hand...
Hmm?... my forth is poor, but I don't believe that's the issue. If I
understand how the floppies currently work is that it's just like our normal
boot loader- we start coming up. If you want to load other drivers or modules
(like ispfw), you hit the 'other than Enter' to stop the loading
The problem with such an approach is that it's not very user-friendly
to first-time installers who have no idea how to drive the loader.
Most of the relevant modules can actually be tried by sysinstall. In the
CD case we can just put them on the CDROM. I'd be inclined to look for
I'm not aware of any 4MB limit on kernel size (and I ought to be if there
is one 8). Can you run the details past me? (I've regularly booted much
larger kernels in the past...)
Alpha?
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the
How did you manage to generate this list. You're smoking
crack on this one
dev/isp/isp_target.c
dev/isp/isp_freebsd.h
as the isp_OS_PLATFORM.h includes is the only include this file has.
-matt
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe
Oh- don't get me wrong. Valuable info. Thanks.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Yes, but no. Let the MAINTAINERS shoot their own lines. A script with nag mail
is good though.
On Wed, 20 Sep 2000, Brandon D. Valentine wrote:
On Tue, 19 Sep 2000, Matthew Jacob wrote:
Oh- don't get me wrong. Valuable info. Thanks.
What would be very cool is to feed
On Wed, 20 Sep 2000, Poul-Henning Kamp wrote:
In message [EMAIL PROTECTED], Matthew J
acob writes:
How did you manage to generate this list. You're smoking
crack on this one
dev/isp/isp_target.c
dev/isp/isp_freebsd.h
as the isp_OS_PLATFORM.h includes is the only
On Wed, 20 Sep 2000, Poul-Henning Kamp wrote:
In message [EMAIL PROTECTED], Matthew J
acob writes:
How did you manage to generate this list. You're smoking
crack on this one
dev/isp/isp_target.c
dev/isp/isp_freebsd.h
as the isp_OS_PLATFORM.h includes is the only
On Thu, 14 Sep 2000, Warner Losh wrote:
In message [EMAIL PROTECTED] Julian Elischer writes:
: Someone once mentionned an actual
: document but I've been unable to find it.
: Was it my imagination?
: (and if so, why isn't there one?)
What do you mean actual document? man pages are
In message [EMAIL PROTECTED] Matthew Jacob
writes:
: I would imagine an overall architecture doc. Sort of like what
: Jordan just did for sysinst (e.g.).
Then he should ask for an architecture doc rather than being so snippy
and snide about "actual documentation."
Proba
Are you sure you don't have a partial update?
On Wed, 6 Sep 2000, Jordan Hubbard wrote:
.. during the depend phase..
/usr/src/lib/libc/../libc/gen/getgrent.c:48: nsswitch.h: No such file or directo
ry
/usr/src/lib/libc/../libc/gen/getpwent.c:54: nsswitch.h: No such file or directo
-
Progress will be more rapid with things checked in than not, as long as
Jason's statement about "the (alpha) system will run" after the checkin.
Jason- I think we'd all appreciate a UTC timestamp suitable for -D that we can
all use to checkout stuff prior to the big change.
-matt
To
Oops- sorry- this is what I get for catching up email after a long
day. Thanks.
On 5 Sep 2000, Jason Evans wrote:
[-smp dropped from cc list.]
On Tue, Sep 05, 2000 at 09:57:05PM -0700, Matthew Jacob wrote:
Jason- I think we'd all appreciate a UTC timestamp suitable for -D that we
can
Anyone else seen this with SMP and latest as of maybe early yesterday morning?
done
panic: vinvalbuf: dirty bufs
mp_lock = 0001; cpuid = 0; lapic.id =
Debugger("panic")
Stopped at Debugger+0x34: movb$0,in_Debugger.591
db
db t
Debugger(c0267f32)
Maybe. It's also not clear to me whether my current breakage is PCI related
or device.hints related (it appears that the read of my /boot/devices.hints
file gets things garbled):
Hit [Enter] to boot immediately, or any other key for command prompt.
Booting [kernel]...
Entering
Maybe. It's also not clear to me whether my current breakage is PCI related
or device.hints related (it appears that the read of my /boot/devices.hints
file gets things garbled):
If you want a working vidconsole on the alpha, compile your hints statically
into the kernel. :)
Hey- I do
What names do you usually access your disks by ? Just da0a etc ?
da0{a,b,c,d} and so on..
You should be able to find those as well with the clone stuff...
Nope. Weren't there.
I booted up once. I had 3 disks- none with a FreeBSD label. The
contents of /dev for da disks was
I do read cvs-all, and I missed it. Not did I find device.hints in the
relevant Makefiles. Can you provide a pointer to details on how
/boot/device.hints is used in the build process, or how having an
empty one keeps you from shooting yourself in the foot?
cvs-all is not appropriate. I am
That's more than show up on i386's :-). After booting with -s, only
the whole disk devices and the root device show up. Devices for slices
and partitions slices only show up when they are opened or stat'ed.
This bug is normally mostly hidden by opening most partitions to mount
them.
Hmm.
In message [EMAIL PROTECTED] Matthew Jacob
writes:
: I do read cvs-all, and I missed it. Not did I find device.hints in the
: relevant Makefiles. Can you provide a pointer to details on how
: /boot/device.hints is used in the build process, or how having an
: empty one keeps you from
I compiled and booted on alpha. It sees my ad0 now. Plus it also sees the 3
'da' disks that were found.
The only real problem is that it won't see the partitions made for
'dangerously dedicated' 'da' disks. What's the plan for addressing this?
-matt
To Unsubscribe: send mail to [EMAIL
If the answer from the person who would have to approve the code had
come back "Ok, provide the code and we'll see how well it works in
practice", I'd do the code. But when it appears the code would never
make it into the tree to be used, why waste my time?
'coz we're taking a page from
Already told him. It is.
On Sun, 20 Aug 2000, Tony Fleisher wrote:
Not sure if this is related to the recent commit of DEVFS code, but a
build of both the GERNERIC kernel and a custom kernel from a very recent
(last few hours) cvsup of -current failed during the 'make depend' with
an
I'm sorry- I really haven't been paying much attention to this, but it seems
it's sort of on the wrong mailing list, isn't it?
Mike- can you take a deep breath and send a summary of what you see the
techical problems/requirements are to the freebsd-scsi alias? I'll admit that
I'm not up on a
What hardware?
On Sat, 29 Jul 2000, Alexander Leidinger wrote:
Hi,
while trying to read (dd if=/dev/cd0c) from a damaged cd (the surface is
a little bit damaged), I've got a panic:
---snip---
#0 boot (howto=260) at ../../kern/kern_shutdown.c:303
#1 0xc01a0f19 in panic (fmt=0xc029aa60
That's groovy, Sheldon.. could you maybe fix nullfs while you're at it, too?
:-)
On Fri, 28 Jul 2000, Sheldon Hearn wrote:
I've just renamed the nullfs kernel module from null to nullfs. The
only impact that this may have on some people is as follows:
If you have null_load="YES" in
Tsk. Coward. I ran for at least a week mounting /usr/src/sys/compile on top
an NFS mounted /usr/src/sys before I panic'd (and read the NOTES file)
Tsk. It's too bad. This works in NetBSD :-)
On Fri, 28 Jul 2000, Sheldon Hearn wrote:
On Fri, 28 Jul 2000 06:44:17 MST, Matthew Jacob
I'm running with softupdates on /, and it has happened to me several times.
On Fri, 28 Jul 2000, Brian Fundakowski Feldman wrote:
On Fri, 28 Jul 2000, Sheldon Hearn wrote:
Just a quick note to let you two gentlement know that the problem
persists with rev 1.107 of buf.h.
Brian,
FWIW, works for me
On Fri, 28 Jul 2000, Poul-Henning Kamp wrote:
I'm in my beach-house and pretty offline right now, but I reviewed the
change Kirk did to addaliasu() and found at least one scenario where
it wouldn't do what he expected:
If bdevvp() is called more than once with the
Thanks,
--
Jos Backus [EMAIL PROTECTED]
WebTV Networks, Inc., Mountain View, CA
I can confirm that on my system with world built from sources cvsuped on
Sunday and a kernel just built from sources cvsuped today, I see these
messages with an mfs mounted /tmp.
Hmm. They went away for me-
Somebody send it to Kirk
On Wed, 26 Jul 2000, George W. Dinolt wrote:
Mahtew Jacob wrote:
Hmm. They went away for me- I thought, but no, you're right. They're
still
there. This is what I actually use to get rid of them:
Index: mfs_vnops.c
I already mentioned it
On Thu, 27 Jul 2000, Andrey A. Chernov wrote:
This is at current -current, softupdates. Panic happens at reboot, from
sync() kernel function:
panic: lockmgr: pid 1, not exlusive lock holder 0 unlocking
--
Andrey A. Chernov
[EMAIL PROTECTED]
You'll have to raise issue on freebsd-scsi.
I sent the likely owner of the issue mail, but they don't monitor -current.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
any reason that we should be seeing these now:
mfs_badop[vop_getwritemount]
mfs_badop[vop_getwritemount] = 45
mfs_badop[vop_getwritemount]
mfs_badop[vop_getwritemount] = 45
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
That theory is not correct, I have seen multiple Alpha machines reporting
buffer underruns as well. No ATA disk in sight there..
This has been a reported feature of the tulip chip and alphas (de driver
usually) forever forever forever.
It's not a bug, per se, IMO.
To Unsubscribe: send
*I'll* check it too- I'd *love* to have if_de as a loadable since most of the
alphas I have use if_de (not dc)!
On Mon, 10 Jul 2000, Mark Murray wrote:
Hi Bill
If I apply the enclosed patch to sys/pci/if_de.c, and make a
copy of (say) sys/modules/dc to sys/modules/de (while changing
all
*I'll* check it too- I'd *love* to have if_de as a loadable since most of the
alphas I have use if_de (not dc)!
Umm- started okay:
de0: Digital 21140A Fast Ethernet port 0x10300-0x1037f mem
0x82083000-0x8208307f irq 3 at device 9.0 on pci0
de0: interrupting at CIA irq 3
de0: 21140A
-current, as of ~today:
FreeBSD/alpha (farrago.feral.com) (console)
login: panic: freeing free cluster
panic
Stopped at Debugger+0x2c: ldq ra,0(sp) 0xfe000a2019f0
ra=0xfc4dbd40,sp=0xfe000a2019f0
db t
Debugger() at Debugger+0x2c
panic() at panic+0x100
m_freem() at
Nope, not for me.
I probably have a core dump, but because gdb is busted for alpha in -current,
it won't say much.
On Mon, 10 Jul 2000, Pascal Hofstee wrote:
On Mon, Jul 10, 2000 at 01:15:20PM -0700, Matthew Jacob wrote:
-current, as of ~today:
FreeBSD/alpha (farrago.feral.com
This doesn't happen for me except in this (loadable de) case.
On Mon, 10 Jul 2000, Rodney W. Grimes wrote:
Umm- started okay:
:
and then died:
rplookup 192.67.166.155 failed: could not allocate llinfo
arpresolve: can't allocate llinfo for 192.67.166.155rt
arplookup
I did some thinking about this, but no real code inspection, on a walk today-
I think what is occurring is that the list of directory updates is getting
refreshed from another process while the first process' list is being written
out. A quick hack would be to make sure this doesn't happen (no
Huh. That's what it has. Sigh...Whine.
On Wed, 5 Jul 2000, John Polstra wrote:
In article [EMAIL PROTECTED],
Matthew Jacob [EMAIL PROTECTED] wrote:
And for -stable (instead of -current);
=== Creating README.html for jpeg-6b
=== graphics/juno-2
"Makefile"
This really bit me- it shouldn't have- but it did
I had a i386 system with a 4GB disk -- root partition ~1GB but the
motherboard was setting up BIOS as a CHS instead of an LBA arrangement.
The only time this showed up as problem was that when I reinstalled the
loader (and related
On Wed, 5 Jul 2000, Mike Smith wrote:
This really bit me- it shouldn't have- but it did
I had a i386 system with a 4GB disk -- root partition ~1GB but the
motherboard was setting up BIOS as a CHS instead of an LBA arrangement.
The only time this showed up as problem
Making docs...
=== Extracting for docproj-1.1
No MD5 checksum file.
=== Patching for docproj-1.1
=== Configuring for docproj-1.1
=== Installing for docproj-1.1
=== docproj-1.1 depends on executable: instant - not found
===Verifying install for instant in /usr/ports/textproc/sgmlformat
On Tue, 4 Jul 2000, Kris Kennaway wrote:
On Tue, 4 Jul 2000, Matthew Jacob wrote:
Making docs...
=== Extracting for docproj-1.1
No MD5 checksum file.
=== Patching for docproj-1.1
=== Configuring for docproj-1.1
=== Installing for docproj-1.1
=== docproj-1.1 depends
On Fri, 30 Jun 2000, Mark Murray wrote:
Interesting. I've also been seeing this on alphas.
Do you have sys/dev/randomdev/randomdev.c v1.5?
Now I do. Better.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
On Wed, 28 Jun 2000, Mark Murray wrote:
Adding something to bootstrap-tools implies that we can't use the
installed miniperl (backward compatibility problem) or the host doesn't
have miniperl. The bootstrap-tools built miniperl would then be used
throughout the build and install
Interesting. I've also been seeing this on alphas.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Can anyone shed light on why a CVSUP'd dirtree I have now always
falls down with the following error?... Because it's CVSUP'd, the
local repository is just /home/ncvs (NFS mounted). I cannot figure out why it
all of a sudden wants to run off the Freefall .
U usr.sbin/ypset/Makefile
U
On Sun, 25 Jun 2000, Matthew Jacob wrote:
Can anyone shed light on why a CVSUP'd dirtree I have now always
falls down with the following error?... Because it's CVSUP'd, the
local repository is just /home/ncvs (NFS mounted). I cannot figure out why it
all of a sudden wants to run
On Thu, 22 Jun 2000, Greg Lehey wrote:
On Thursday, 22 June 2000 at 10:07:38 -0700, Matthew Dillon wrote:
On Mon, Jun 19, 2000 at 05:34:47PM -0700, Matthew Dillon wrote:
Ok, I have put up a web page that will track my efforts.
http://apollo.backplane.com/FreeBSDSmp/
Your
[ if you don't use any of the Qlogic cards, ignore this message for now ]
By tonight a new version of this driver will be checked in that no longer
supports most of the config options previously used.
The most obvious effect of this change will be that firmware can no longer be
compiled into
Uh, 'help' doesn't give you a list of commands I believe.
On Thu, 15 Jun 2000, Mike Smith wrote:
On 15 Jun, Marc van Woerkom wrote:
3. in the boot loader I miss the list of commands,
? (i hope this was the command) just yields a number
I also see this.
The use of ? was
Uh, 'help' doesn't give you a list of commands I believe.
Damn, it doesn't either. 'help' is the same as 'help help'.
Suggestions for a better replacement for ? 'commands'?
Just change unadorned help to say 'help help' to get a list.
To Unsubscribe: send mail to [EMAIL PROTECTED]
# I cannot stress this enough: **SAVE A WORKING /kernel**
cp /kernel /kernel.works
Save a working /modules and /boot as well.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
On Mon, 8 May 2000, Warner Losh wrote:
In message [EMAIL PROTECTED] Matthew Jacob
writes:
: Oh, and in the updating of this, don't forget the FreeBSD usage of .ctl for
: tape devices- as far as I know this is the only *BSD that has this.
Which devices use .ctl? sa and ast don't seem
On Mon, 8 May 2000, Dan Nelson wrote:
In the last episode (May 08), Warner Losh said:
In message [EMAIL PROTECTED] Matthew
Jacob writes:
: Oh, and in the updating of this, don't forget the FreeBSD usage of
: .ctl for tape devices- as far as I know this is the only *BSD that
: has
301 - 400 of 557 matches
Mail list logo
