Hi,
I think we should move portmap(8) to /sbin for the following reason:
portmap(8) and therefore mountd(8) should be started before
the nfs filesystems get mounted. But because portmap(8) is in
/usr/sbin , users with a nfs mounted /usr filesystem or with
diskless filesystems will
portmap(8) and therefore mountd(8) should be started before
the nfs filesystems get mounted. But because portmap(8) is in
/usr/sbin , users with a nfs mounted /usr filesystem or with
diskless filesystems will have big problems.
I mean, that if I do the change of startup-order, diskless
: portmap(8) and therefore mountd(8) should be started before
: the nfs filesystems get mounted. But because portmap(8) is in
: /usr/sbin , users with a nfs mounted /usr filesystem or with
: diskless filesystems will have big problems.
:
:I mean, that if I do the change of startup-order,
Hi,
should not have to run either, *even* for diskless boot.
What's all this about loopback mounts in fstab about? What does
that have to do with diskless startup?
Ok. I just rethought everything. It seems that a move is
unnecessary because:
- Sharity light and cfs are
Hi,
should not have to run either, *even* for diskless boot.
What's all this about loopback mounts in fstab about? What does
that have to do with diskless startup?
Ok. I just rethought everything. It seems that a move is
unnecessary because:
- Sharity light and
At 7:57 PM -0500 2000/1/11, Mike Fisher wrote:
Why not use Knuth's (good) suggestion for differentiating these prefixes?
http://www-cs-faculty.stanford.edu/~knuth/news99.html
Blech. The prefixes should be aware of the nature of the term to
which they are being applied. For
(kgdb) bt
#8 0xc025c1a1 in Debugger (msg=0xc028fc72 "panic") at machine/cpufunc.h:64
#9 0xc015ac04 in panic (fmt=0xc02a0ee0 "flush_pagedep_deps: flush 3 failed")
at ../../kern/kern_shutdown.c:552
#10 0xc020441a in flush_pagedep_deps (pvp=0xd8f15da0, mp=0xc1e4c400,
diraddhdp=0xc204d5e4)
hi,
On Tue, Jan 11, 2000 at 05:41:59PM -0800, Matthew Dillon wrote:
:I just discovered some strange points about using vn devices (files) as
:swap devices.
:
:I have placed below some output gathered with script(1) and now
:some comments.
:
:1) I can easy unconfigure vn device which
I'm running -current from July 1999. Now I getting
a core dump of the swapper daemon (sic!!!) after booting.
This is really strange ... a dying swapper and 100MB free memory.
I guess it is a interupt conflict with the 3com ethernet
card.
$ ls -l /swapper.core
-rw--- 1 root wheel 8192
hi,
Sorry, but after my last make world (Tue Jan 11 15:07:18 CET 2000) I
didn't have to reboot (ok, once, after the install ;). I'm using
softupdates, vinum, smp and scsi, but the instability seems gone.
I've caused heavy load on the machine for reasonable long periods, but
nothing crashed.
--
On Wed, 12 Jan 2000, Christian Carstensen wrote:
Sorry, but after my last make world (Tue Jan 11 15:07:18 CET 2000) I
didn't have to reboot (ok, once, after the install ;). I'm using
softupdates, vinum, smp and scsi, but the instability seems gone.
I've caused heavy load on the machine for
On Wed, 12 Jan 2000, Donn Miller wrote:
My guess is that once -current gets closer to the release date, it becomes
more and more stable. I guess the period of greatest instability occurs
somewhere about 1/4 to 1/2 through the -current life cycle. We could do a
chart plotting stability vs.
On Wed, Jan 12, 2000 at 01:23:14AM -0800, Rodney W. Grimes wrote:
Also moving them to pass1 would bring up nfs exports before we
brought up nfs mounts. syslogd would not be running to catch
Shouldn't nfs exports happen before nfs mounts, so that machines
which have nfs interdependencies
Folks,
I've run into the following problem since about 1/6 or so:
Have I missed something obvious, do I need the conical hat here?
If so I've got a stool in the corner to sit on.
The wired scsi devices no longer configure as such...
I'm sure it must be me, since I've seen no messages in
"Rodney W. Grimes" wrote:
[..]
So no disk, so just what is it that you are exporting???
Just a comment:
I've seen scenarios where a local disk is attached holding a kernel,
bootblocks loader etc, but otherwise booting from a server over NFS. And
it exported the rest of it's disk for general
kB and kiB are the proper abreviations, not KB and KiB. I don't know
if miB or MiB is correct, likely MiB.
I always thought it was "k/m/b = 1,000/1,000,000/1,000,000,000"
and "K/M/G = 2^10/2^20/2^30". Or was this just some convention I
learned somewhere that I mistakenly thought
With my CURRENT-tre updated within an hour ago ... Buildworld is broken.
cc -O -pipe -DFREEBSD_NATIVE -DIN_GCC -DHAVE_CONFIG_H
-DDEFAULT_TARGET_VERSION=\ "2.95.2\"
-DDEFAULT_TARGET_MACHINE=\"i386-unknown-freebsd\"
-DPREFIX=\"/usr/obj/usr/src/i386/usr\"
I've just turned on IPSec between two machines, an i386 and Alpha,
both running very recent currents, each has the IPSEC and IPSEC_ESP
config options set, but does not have IP6 support enabled. I used
setkey and could establish what appear to be encrypted connections using
vanilla telnet
Hi folks,
Those of you who whined about the absence of manual pages in the NTP4
package recently imported into the base system, please check your commit
mail. Selected pages have been transcribed from the HTML documentation
and committed to the base system.
Ciao,
Sheldon.
To Unsubscribe:
On Tue, 11 Jan 2000 15:49:54 EST, Kelly Yancey wrote:
David, I just noticed that this note in 4.0's RELNOTES about the
relocation doesn't appear applicable anymore:
You're right. I've removed the comment from the RELNOTES.TXT for the
i386 and alpha. Thanks!
Ciao,
Sheldon.
To
Got this error, just now after a CVSUP:
/usr/obj/usr/src/i386/usr/src/gnu/usr.bin/cc/cpp/../cc_drv/libcc_drv.a(choos
e-temp.o)
: In function `choose_temp_base':
choose-temp.o(.text+0x13e): warning: mktemp() possibly used unsafely;
consider using
mkstemp()
I've got a loopback mount in /var/db/mounttab that looks like this:
946789037 localhost /null
which is there because I run cfs (a crypto file system; see
/usr/ports/security/cfs). Part of the cfs startup script does
this:
/usr/local/sbin/cfsd mount -o port=3049,intr
Matt,
Like I said, I disabled softupdates on all my filesystems (and added DDB
to the kernel). The system has been running 7 hours smoothly now, that's
the longest uptime I've had so far with version 1.47 of ffs_softdep.c.
I even recreated the directory that I couldn't delete previously and
I got more panic with DEBUG=-g and INVARIANTS. I saved core dump at
this time.
This panic is caused when I tested heavy traffic via aue0 (USB
ethernet adaptor) with "while looped" large file scp. I think that is
only active process.
My ipfw is set as default like as "65535 allow ip from any
Of all the gin joints in all the towns in all the world, Jun Kuriyama
had to walk into mine and say:
I got more panic with DEBUG=-g and INVARIANTS. I saved core dump at
this time.
We need version information! How recent is your version of -current!
What's the rcsid from if_aue.c! Details
For about the last 24 hours, there was a botch in the scsi device wiring
support in config(8).
Please make sure you are running config from -current with version 1.59 or
later of mkioconf.c, or your device wiring will be most definately broken.
What happened is that 'da0 at scbus0 target 3'
On Wed, Jan 12, 2000 at 10:01:42AM +0200, Maxim Sobolev wrote:
Is there are any compiler guys to address my question or not?
There is, I'm the one. But there are a few things ahead in the queue.
Of course a patch would make things go much faster.
--
-- David([EMAIL PROTECTED])
To
David O'Brien wrote:
On Wed, Jan 12, 2000 at 10:01:42AM +0200, Maxim Sobolev wrote:
Is there are any compiler guys to address my question or not?
There is, I'm the one. But there are a few things ahead in the queue.
Please excuse me if I've offended you, but I just doubted that no one has
Hello!
I have a recent current:
FreeBSD cichlids.cichlids.com 4.0-CURRENT FreeBSD 4.0-CURRENT #0: Tue Jan 11 13:18:21
CET 2000 [EMAIL PROTECTED]:/usr/src/sys/compile/cichlids i386
I cannot build the CVS version of GNATS with this.
This is kinda strange, because with a kernel from Dec
On Wed, Jan 12, 2000 at 01:23:14AM -0800, Rodney W. Grimes wrote:
Also moving them to pass1 would bring up nfs exports before we
brought up nfs mounts. syslogd would not be running to catch
Shouldn't nfs exports happen before nfs mounts, so that machines
which have nfs
"Rodney W. Grimes" wrote:
[..]
So no disk, so just what is it that you are exporting???
Just a comment:
I've seen scenarios where a local disk is attached holding a kernel,
bootblocks loader etc, but otherwise booting from a server over NFS. And
it exported the rest of it's disk for
In message v04220801b4a20f42cd3a@[195.238.1.121] Brad Knowles writes:
: I always thought it was "k/m/b = 1,000/1,000,000/1,000,000,000"
: and "K/M/G = 2^10/2^20/2^30". Or was this just some convention I
: learned somewhere that I mistakenly thought of as an actual accepted
: rule?
This
The following backtrace comes from a panic I just had on my laptop
that appears to be softupdates-related. Sources are from yesterday,
re-cvsup'ing shows no new fs-related sources updated. At the time I was
in the middle of compiling the Window Maker port (actually compiling the
jpeglib
If your talking about dead lock caused by mutual cross mounting
between 2 systems via NFS the NFS rule book says ``don't do that,
it hurts''.
Independent of order of export/mounting the dead lock occurs. Cross
mounting via NFS is a verbotten thing in the sysadmin world of production
Folks, this is getting a little silly. Can't we cut all the esoteric
mumbo-jumbo and agree to do it the same way that gnuls and our own
existing df do it?
Ciao,
Sheldon.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
On Wed, Jan 12, 2000 at 02:57:41PM +0100, Pascal Hofstee wrote:
With my CURRENT-tre updated within an hour ago ... Buildworld is broken.
cc -O -pipe -DFREEBSD_NATIVE -DIN_GCC -DHAVE_CONFIG_H
-DDEFAULT_TARGET_VERSION=\ "2.95.2\"
-DDEFAULT_TARGET_MACHINE=\"i386-unknown-freebsd\"
On Wed, Jan 12, 2000 at 11:16:38AM -0800, Jason Evans wrote:
On Wed, Jan 12, 2000 at 02:57:41PM +0100, Pascal Hofstee wrote:
With my CURRENT-tre updated within an hour ago ... Buildworld is broken.
cc -O -pipe -DFREEBSD_NATIVE -DIN_GCC -DHAVE_CONFIG_H
-DDEFAULT_TARGET_VERSION=\
Hi
Anyone else seeing this?
cc -O -pipe -DFREEBSD_NATIVE -DIN_GCC -DHAVE_CONFIG_H
-DDEFAULT_TARGET_VERSION=\"2.95.2\" -DDEFAULT_TARGET_MACHINE=\"i386-unknown-freebsd\"
-DPREFIX=\"/usr/obj/usr/src/i386/usr\"
-I/usr/obj/usr/src/i386/usr/src/gnu/usr.bin/cc/cpp/../cc_tools
Hmm. I was under the impression that this problem was fixed, but I am
getting it again. When I have a crash and reboot fsck runs through
all the filesystems but then mount refuses to mount / thinking that it's
dirty when it isn't.
On Wed, Jan 12, 2000 at 09:56:22PM +0200, Mark Murray wrote:
Hi
Anyone else seeing this?
cc -O -pipe -DFREEBSD_NATIVE -DIN_GCC -DHAVE_CONFIG_H
-DDEFAULT_TARGET_VERSION=\"2.95.2\" -DDEFAULT_TARGET_MACHINE=\"i386-unknown-freebsd\"
-DPREFIX=\"/usr/obj/usr/src/i386/usr\"
-current supped 10 minutes ago gives during make depend:
c ../../isa/vga_isa.c ../../kern/subr_diskmbr.c ../../libkern/bcmp.c
../../libkern/ffs.c ioconf.c param.c vnode_if.c config.c
../../alpha/alpha/genassym.c
../../isa/sio.c:2926: macro `CONS_DRIVER' used with only 7 args
mkdep: compile
Personally, I'd much prefer to simply use separator characters
like this:
-rw--- 1 olli olli 211,602,776 Nov 28 23:09 S1E1.mpg
This makes it very easy to recognize the size, and you still
have the exact number of bytes, not rounded. It's even
possible to to respect the locale setting
"Rodney W. Grimes" wrote:
"Rodney W. Grimes" wrote:
[..]
So no disk, so just what is it that you are exporting???
Just a comment:
I've seen scenarios where a local disk is attached holding a kernel,
bootblocks loader etc, but otherwise booting from a server over NFS. And
it
Hi,
Could somebody help me setting up my ntp server with a DCF
receiver.
Since I updated to ntp4, ntpd does not like my old ntp.conf
any more.
Here is my old ntp.conf. my ntpd daemon was doing just fine
and now :^(
# --
# XNTP configuration
On Wed, Jan 12, 2000 at 11:16:38AM -0800, Jason Evans wrote:
On Wed, Jan 12, 2000 at 02:57:41PM +0100, Pascal Hofstee wrote:
With my CURRENT-tre updated within an hour ago ... Buildworld is broken.
cc -O -pipe -DFREEBSD_NATIVE -DIN_GCC -DHAVE_CONFIG_H
-DDEFAULT_TARGET_VERSION=\
At 6:01 PM -0800 1/11/00, Rodney W. Grimes wrote:
Garance wrote:
personally, I'd just as soon use K, M, and G and have it mean
the base-10 values. If I'm looking at a decimal number for one
file (because it's small enough), I don't want a base-2 version
of the similar number for some
On Wed, Jan 12, 2000 at 10:07:25PM +0100, Wilko Bulte wrote:
On Wed, Jan 12, 2000 at 09:56:22PM +0200, Mark Murray wrote:
Hi
Anyone else seeing this?
cc -O -pipe -DFREEBSD_NATIVE -DIN_GCC -DHAVE_CONFIG_H
-DDEFAULT_TARGET_VERSION=\"2.95.2\"
On Wed, 12 Jan 2000, Wilko Bulte wrote:
-current supped 10 minutes ago gives during make depend:
c ../../isa/vga_isa.c ../../kern/subr_diskmbr.c ../../libkern/bcmp.c
../../libkern/ffs.c ioconf.c param.c vnode_if.c config.c
../../alpha/alpha/genassym.c
../../isa/sio.c:2926: macro
"Rodney W. Grimes" wrote:
...
Independent of order of export/mounting the dead lock occurs. Cross
mounting via NFS is a verbotten thing in the sysadmin world of production
systems. :-) I have had to fix it at several sites admin'd by newbies...
I'm not sure you are really understanding
On Wed, 12 Jan 2000 16:21:05 -0500, Garance A Drosihn [EMAIL PROTECTED] said:
In 'ls' we are not talking about a block count, we are talking about
a byte-count.
ls -s
-GAWollman
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
At 4:51 PM -0500 1/12/00, Garrett Wollman wrote:
On Wed, 12 Jan 2000, Garance A Drosihn [EMAIL PROTECTED] said:
In 'ls' we are not talking about a block count, we are talking about
a byte-count.
ls -s
Hmm, valid point. 'ls -l' is not using a block count though, and so
all of my previous
Back on December 27, 1999, Garance A Drosihn wrote:
At 8:55 AM -0500 12/24/99, Robert Watson wrote:
For example, imagine that the user has a
number of hard links to the file in question.
Okay, here's my newer version of the code, which takes
into account multiple hard links, and also makes it
On Wed, Jan 12, 2000 at 04:21:05PM -0500, Garance A Drosihn wrote:
The first one changes because it's over 1 megabyte, but the second
one does not change. So you get:
-rw-r--r-- 1 gad staff 1951k Dec 11 03:39 asciiedit.c
-rw-r--r-- 1 gad staff999123 Dec 11 03:39 asciisrch.c
I haven't seen any reports of this yet. After a make world yesterday, I hear
stuttered sound from RealPlayer G2 and xmms won't play anything at all. I
tried to figure out when it was broken but didn't have any luck. It worked
fine after my last make world on December 27th.
--
Jeremy L. Stock
On Wed, Jan 12, 2000 at 01:22:25PM -0800, Jason Evans wrote:
On Wed, Jan 12, 2000 at 10:07:25PM +0100, Wilko Bulte wrote:
On Wed, Jan 12, 2000 at 09:56:22PM +0200, Mark Murray wrote:
Hi
Anyone else seeing this?
...
"Jeremy L. Stock" wrote:
I haven't seen any reports of this yet. After a make world yesterday, I hear
stuttered sound from RealPlayer G2 and xmms won't play anything at all. I
tried to figure out when it was broken but didn't have any luck. It worked
fine after my last make world on
On 2000-Jan-13 09:54:17 +1100, Joerg Micheel [EMAIL PROTECTED] wrote:
-rw-r--r-- 1 gad staff 1951k Dec 11 03:39 asciiedit.c
-rw-r--r-- 1 gad staff999123 Dec 11 03:39 asciisrch.c
You still need to mentally re-align the numbers before you can compare
the sizes.
-rw-r--r-- 1 gad
On Thu, Jan 13, 2000 at 12:16:31AM +0100, Wilko Bulte wrote:
On Wed, Jan 12, 2000 at 01:22:25PM -0800, Jason Evans wrote:
On Wed, Jan 12, 2000 at 10:07:25PM +0100, Wilko Bulte wrote:
On Wed, Jan 12, 2000 at 09:56:22PM +0200, Mark Murray wrote:
Hi
Anyone else seeing this?
...
On Wed, Jan 12, 2000 at 08:29:44AM -0500, Tom Embt wrote:
This would be great, but I wonder from what source we could take reliable
data about -current's stability.
How 'bout some sort of client program that is run via the rc.d and
rc.shutdown scripts?
One of the more annoying
obrien A while back I moved the install location for chown and chgrp
obrien from /usr/sbin and /usr/bin to /sbin and /bin. This was
obrien because of MAKEDEV(8)'s dependence on them, and thus forced
obrien /usr to be mounted for correct operation of MAKEDEV(8).
But MAKEDEV(8) still depends on
obrien A while back I moved the install location for chown and chgrp
obrien from /usr/sbin and /usr/bin to /sbin and /bin. This was
obrien because of MAKEDEV(8)'s dependence on them, and thus forced
obrien /usr to be mounted for correct operation of MAKEDEV(8).
But MAKEDEV(8) still
msmith A release build requires a complete "make buildworld" of the
msmith relevant world to have been completed before starting.
Not "make buildworld" but "make installworld" ? In anyway, "make
distrib-dirs distribution" depends on some tools (not only mknod), and
it's no way to install these
On Wed, Jan 12, 2000 at 10:08:17AM -0800, Glendon Gross wrote:
Are there any tricks to enabling Awe64 support? I initially removed my
Awe64 card from my first FreeBSD machine to avoid interrupt conflicts, and
now I would like to try to integrate it back again. Would you mind
sending me
msmith A release build requires a complete "make buildworld" of the
msmith relevant world to have been completed before starting.
Not "make buildworld" but "make installworld" ?
No. I said "make buildworld".
In anyway, "make
distrib-dirs distribution" depends on some tools (not only
msmith No. I said "make buildworld".
Ah, sorry, I must say "make installworld in the process of make release".
msmith The chroot area is populated via "make installworld" from the
msmith abovementioned buildworld. The mknod that is then used to
msmith build device nodes is the one inside the
On Wed, Jan 12, 2000 at 11:58:34AM -0800, Matthew Dillon wrote:
Hmm. I was under the impression that this problem was fixed, but I am
getting it again. When I have a crash and reboot fsck runs through
all the filesystems but then mount refuses to mount / thinking that it's
I guess I forgot MKNOD from my list. I must have copied it to /bin
so I have
/usr/bin/chgrp
/usr/lib/libc.so.3
/usr/libexec/ld-elf.so.1
/usr/sbin/chown
/usr/sbin/chroot
as being needed to run MAKEDEV in 3.4-RELEASE
MAKDEV will complain while its running that it needs libgnuerex (can't
On Thu, Jan 13, 2000 at 12:16:31AM +0100, Wilko Bulte wrote:
On Wed, Jan 12, 2000 at 01:22:25PM -0800, Jason Evans wrote:
On Wed, Jan 12, 2000 at 10:07:25PM +0100, Wilko Bulte wrote:
On Wed, Jan 12, 2000 at 09:56:22PM +0200, Mark Murray wrote:
Hi
Anyone else seeing this?
...
The buildworld problem that I introduced is due to cc_fbsd directly
compiling and linking in src/lib/libc/stdio/mktemp.c. This is in my
opinion a questionable practice, since it adds dependencies to the
internals of the libc code, which has just been proven to bite. =)
Aesthetics aside, I'm not
On Thu, Jan 13, 2000 at 12:16:31AM +0100, Wilko Bulte wrote:
I copied libc.so.4 manually to /usr/lib but that is not sufficient.
It looks like ld-elf sticks to libc.so.4 even if I move the symlink
libc.so back from libc.so.4 to libc.so.3
Yes. Each shared library knows it's name when it was
In article [EMAIL PROTECTED],
Jason Evans [EMAIL PROTECTED] wrote:
The buildworld problem that I introduced is due to cc_fbsd directly
compiling and linking in src/lib/libc/stdio/mktemp.c. This is in my
opinion a questionable practice, since it adds dependencies to the
internals of the libc
On Wed, 12 Jan 2000 17:45:51 -0500, Garance A Drosihn [EMAIL PROTECTED] said:
Yes, it may be "more pure" to use 1024 when comparing 'ls' listings
to block counts, but it is less confusing WITHIN a single 'ls -l'
listing if all the numbers are decimal, and not some combination of
base-10 and
On Wed, Jan 12, 2000 at 07:00:01PM -0800, John Polstra wrote:
The buildworld problem that I introduced is due to cc_fbsd directly
compiling and linking in src/lib/libc/stdio/mktemp.c. This is in my
opinion a questionable practice, since it adds dependencies to the
internals of the libc
I have a similar problem, in kernels build Monday and yesterday. I get
a kernel panic when while booting, I don't know how to capture the boot
messages to a file (do you) so I can not post them but this is the line
that it dies on:
panic: ahc0: brkadrint, scratch or SCB Memory Parity Error
[Charset iso-8859-1 unsupported, filtering to ASCII...]
I'm sorry but I would find it non-obvious and more confusing. When ls or a
similar disk/memory utility tells me xxxK or xxxM, I would expect it to be
in 2^10 or 2^20 units. To appear otherwise would surprise me.
I guess you get
Sick, poor in performance and the wrong tool for the job.
See mount_null(8) for more details on how to do it right.
Yes its perfect for the job apart from:
man mount_null
THIS FILESYSTEM TYPE IS NOT YET FULLY SUPPORTED (READ: IT DOESN'T WORK)
AND USING IT MAY, IN FACT, DESTROY DATA ON
On Wed, 12 Jan 2000 22:10:07 +0100, Jean Louis Ntakpe wrote:
# Server is a Boeder DCF77 receiver
server 127.127.8.41
Does your server look like any of those listed in reflock.htm? Most of
the documentation for your application has not been transcribed into
manual page format.
Ciao,
On Wed, Jan 12, 2000 at 05:25:22PM -0800, David O'Brien wrote:
On Thu, Jan 13, 2000 at 12:16:31AM +0100, Wilko Bulte wrote:
I copied libc.so.4 manually to /usr/lib but that is not sufficient.
It looks like ld-elf sticks to libc.so.4 even if I move the symlink
libc.so back from libc.so.4
78 matches
Mail list logo
