Re: mount_nfs/df bug?

[David Malone]

On Wed, Jun 21, 2000 at 09:50:57PM +0200, Cyrille Lefevre wrote:

> well, what about exporting a directory w/o exporting a filesystem ?
> which is usefull somethimes. possible too ?

Add the directory to exports and HUP mountd. (I think that in the
kernel the exports are at a filesystem level, so while you can
export any directory a naughty client can do "cd ../../../.." and
find their way back up to the top of the exported filesystem. Most
people's NFS clients won't allow you to do this, but you could
write your own client to do it).

David.


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: Now softupdates are BSD licenced can they go in smoothly?

[Brandon D. Valentine]

On Thu, 22 Jun 2000, George Michaelson wrote:

>So does this mean the whole shebang of find/read/link/recompile can finally
>end? NetBSD got rid of this ages ago.

Well Kirk McKusick has already committed the license change, a la:
http://docs.freebsd.org/cgi/getmsg.cgi?fetch=524952+0+current/cvs-all

If you follow that thread you will find discussion on cvs-committers
about including it in GENERIC, etc.  With the license issue resolved I
don't see any reason it couldn't be permanently symlinked.  I'm sure
this will happen over the next few days.  Watch cvs-all for related
commits.

Brandon D. Valentine
-- 
bandix at looksharp.net  |  bandix at structbio.vanderbilt.edu
"Truth suffers from too much analysis." -- Ancient Fremen Saying



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: make.conf fix

[Will Andrews]

On Wed, Jun 21, 2000 at 12:09:02AM -0700, Satoshi - Ports Wraith - Asami wrote:
> Waitaminit.  These are correct, please look at bsd.sites.mk.  What
> makes you think they are not working?

Hmm... weird.  I tried using the overrides in make.conf some time ago
and they didn't work and I had to use ${MASTER_SITE_SUBDIR} instead of
%SUBDIR%.  Anyway, I withdraw this patch.

-- 
Will Andrews <[EMAIL PROTECTED]> <[EMAIL PROTECTED]>
GCS/E/S @d- s+:+>+:- a--->+++ C++ UB P+ L- E--- W+++ !N !o ?K w---
?O M+ V-- PS+ PE++ Y+ PGP+>+++ t++ 5 X++ R+ tv+ b++> DI+++ D+ 
G++>+++ e-> h! r-->+++ y?


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Now softupdates are BSD licenced can they go in smoothly?

[George Michaelson]

>From Daemon news:

 Kirk McKusick announced this morning at the USENIX keynote that the
 softupdates code will now be available under a BSD license. Details
 to follow.

So does this mean the whole shebang of find/read/link/recompile can finally
end? NetBSD got rid of this ages ago.

-George


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: vnode_if.h: how should it be done ?

[Assar Westerlund]

Garrett Wollman <[EMAIL PROTECTED]> writes:

> < said:
> 
> > So I propose the patch below, to create vnode_if.h and then add it to CVS.
> 
> There are too many generated files in CVS as it is.
> 
> If there is a problem here, the correct fix is to supply the source
> files, not the generated output.

The problem is that the source files are hidden in the kernel source
directory and not installed.  Where should vnode_if.{src,pl} get
installed?  It seems much simpler just to install vnode_if.h in
/usr/include/sys.  Patch appended.

/assar

Index: Makefile
===
RCS file: /home/ncvs/src/include/Makefile,v
retrieving revision 1.113
diff -u -w -r1.113 Makefile
--- Makefile2000/05/19 22:08:18 1.113
+++ Makefile2000/06/22 03:55:52
@@ -6,7 +6,7 @@
 # The ``rm -rf''s used below are safe because rm doesn't follow symbolic
 # links.
 
-CLEANFILES= osreldate.h version vers.c
+CLEANFILES= osreldate.h version vers.c vnode_if.h
 SUBDIR= rpcsvc
 FILES= a.out.h ar.h assert.h bitstring.h ctype.h db.h dirent.h disktab.h \
dlfcn.h elf.h err.h fnmatch.h fstab.h \
@@ -57,7 +57,7 @@
 #SHARED=   symlinks
 SHARED?=   copies
 
-all:   osreldate.h
+all:   osreldate.h vnode_if.h
 
 osreldate.h:   ${.CURDIR}/../sys/conf/newvers.sh \
${.CURDIR}/../sys/sys/param.h
@@ -68,6 +68,11 @@
echo \#'undef __FreeBSD_version' >> osreldate.h;\
echo \#'define __FreeBSD_version' $$RELDATE >> osreldate.h
 
+vnode_if.h:${.CURDIR}/../sys/kern/vnode_if.pl \
+   ${.CURDIR}/../sys/kern/vnode_if.src
+   @${ECHO} creating vnode_if.h
+   perl ${.CURDIR}/../sys/kern/vnode_if.pl -h ${.CURDIR}/../sys/kern/vnode_if.src
+
 beforeinstall: ${SHARED}
@rm -f ${DESTDIR}/usr/include/timepps.h
cd ${.CURDIR}; \
@@ -85,6 +90,9 @@
${INSTALL} -C -o ${BINOWN} -g ${BINGRP} -m 444 \
${.OBJDIR}/osreldate.h \
${DESTDIR}/usr/include
+   ${INSTALL} -C -o ${BINOWN} -g ${BINGRP} -m 444 \
+   ${.OBJDIR}/vnode_if.h \
+   ${DESTDIR}/usr/include/sys
 .for i in ${LFILES}
ln -sf sys/$i ${DESTDIR}/usr/include/$i
 .endfor


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

vnode_if.h: how should it be done ?

[Garrett Wollman]

< said:

> So I propose the patch below, to create vnode_if.h and then add it to CVS.

> Any objectsions/comments/whatever?

Yes.

There are too many generated files in CVS as it is.

If there is a problem here, the correct fix is to supply the source
files, not the generated output.

-GAWollman



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Missing openssl/idea.h?

[Jun Kuriyama]

Building world failed on my machine... (with USA_RESIDENT=NO)

Does IDEA stuff compiled by default?


===> libssh
rm -f .depend
mkdep -f .depend -a-DSKEY -I/usr/obj/usr/src/i386/usr/include  
/usr/src/secure/lib/libssh/../../../crypto/openssh/authfd.c 
/usr/src/secure/lib/libssh/../../../crypto/openssh/authfile.c 
/usr/src/secure/lib/libssh/../../../crypto/openssh/aux.c 
/usr/src/secure/lib/libssh/../../../crypto/openssh/bufaux.c 
/usr/src/secure/lib/libssh/../../../crypto/openssh/buffer.c 
/usr/src/secure/lib/libssh/../../../crypto/openssh/canohost.c 
/usr/src/secure/lib/libssh/../../../crypto/openssh/channels.c 
/usr/src/secure/lib/libssh/../../../crypto/openssh/cipher.c 
/usr/src/secure/lib/libssh/../../../crypto/openssh/compat.c 
/usr/src/secure/lib/libssh/../../../crypto/openssh/compress.c 
/usr/src/secure/lib/libssh/../../../crypto/openssh/crc32.c 
/usr/src/secure/lib/libssh/../../../crypto/openssh/deattack.c 
/usr/src/secure/lib/libssh/../../../crypto/openssh/fingerprint.c 
/usr/src/secure/lib/libssh/../../../crypto/openssh/hostfile.c 
/usr/src/secure/lib/libssh/../../../crypto/openssh/log.c /usr/src/sec!
 ure/lib/libssh/../../../crypto/openssh/match.c 
/usr/src/secure/lib/libssh/../../../crypto/openssh/mpaux.c 
/usr/src/secure/lib/libssh/../../../crypto/openssh/nchan.c 
/usr/src/secure/lib/libssh/../../../crypto/openssh/packet.c 
/usr/src/secure/lib/libssh/../../../crypto/openssh/readpass.c 
/usr/src/secure/lib/libssh/../../../crypto/openssh/rsa.c 
/usr/src/secure/lib/libssh/../../../crypto/openssh/tildexpand.c 
/usr/src/secure/lib/libssh/../../../crypto/openssh/ttymodes.c 
/usr/src/secure/lib/libssh/../../../crypto/openssh/uidswap.c 
/usr/src/secure/lib/libssh/../../../crypto/openssh/xmalloc.c 
/usr/src/secure/lib/libssh/../../../crypto/openssh/atomicio.c 
/usr/src/secure/lib/libssh/../../../crypto/openssh/key.c 
/usr/src/secure/lib/libssh/../../../crypto/openssh/dispatch.c 
/usr/src/secure/lib/libssh/../../../crypto/openssh/dsa.c 
/usr/src/secure/lib/libssh/../../../crypto/openssh/kex.c 
/usr/src/secure/lib/libssh/../../../crypto/openssh/hmac.c 
/usr/src/secure/lib/libssh/../../../crypto/!
 openssh/uuencode.c /usr/src/secure/lib/libssh/../../../crypto/openssh/
auth-skey.c
In file included from /usr/obj/usr/src/i386/usr/include/openssl/pem.h:66,
 from /usr/src/secure/lib/libssh/../../../crypto/openssh/authfile.c:24:
/usr/obj/usr/src/i386/usr/include/openssl/evp.h:99: openssl/idea.h: No such file or 
directory
In file included from /usr/obj/usr/src/i386/usr/include/openssl/hmac.h:69,
 from /usr/src/secure/lib/libssh/../../../crypto/openssh/packet.c:40:
/usr/obj/usr/src/i386/usr/include/openssl/evp.h:99: openssl/idea.h: No such file or 
directory
In file included from /usr/src/secure/lib/libssh/../../../crypto/openssh/key.c:40:
/usr/obj/usr/src/i386/usr/include/openssl/evp.h:99: openssl/idea.h: No such file or 
directory
In file included from /usr/src/secure/lib/libssh/../../../crypto/openssh/dsa.c:43:
/usr/obj/usr/src/i386/usr/include/openssl/evp.h:99: openssl/idea.h: No such file or 
directory
In file included from /usr/obj/usr/src/i386/usr/include/openssl/pem.h:66,
 from /usr/src/secure/lib/libssh/../../../crypto/openssh/kex.c:49:
/usr/obj/usr/src/i386/usr/include/openssl/evp.h:99: openssl/idea.h: No such file or 
directory
In file included from /usr/obj/usr/src/i386/usr/include/openssl/hmac.h:69,
 from /usr/src/secure/lib/libssh/../../../crypto/openssh/hmac.c:37:
/usr/obj/usr/src/i386/usr/include/openssl/evp.h:99: openssl/idea.h: No such file or 
directory
mkdep: compile failed
*** Error code 1

Stop in /usr/src/secure/lib/libssh.
*** Error code 1

Stop in /usr/src/secure/lib.
*** Error code 1

Stop in /usr/src.
*** Error code 1

Stop in /usr/src.
*** Error code 1

Stop in /usr/src.


-- 
Jun Kuriyama <[EMAIL PROTECTED]> // FreeBSD Project


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: HEADS UP: Destabilization due to SMP development

[Chuck Robey]

On Wed, 21 Jun 2000, Mark Murray wrote:

> > Has anyone given any thought to what it would take to create an 
> > open source version of something similar to perforce?  ;-)
> 
> Clearly you have. :-). We await your submissions with baited breath...

I have mixed feelings about that.  The Perforce people have been willing
for FreeBSD to use it free.  They're really nice about that, it seems more
than a bit discourteous to try to copy it.  If you'd asked to duplicate
MSWord, they're a unethical monopolist, I wouldn't have any scruples
attacking them, but I don't like attacking folks who've been displaying
towards free software such a friendly attitude.

Makes me (and I sure support free software!) feel like a predator when you
go after folks who've been doing good.

I think, if you want it fixed, you should go fix cvs.


Chuck Robey| Interests include C & Java programming, FreeBSD,
[EMAIL PROTECTED]  | electronics, communications, and signal processing.

New Year's Resolution:  I will not sphroxify gullible people into looking up
fictitious words in the dictionary.




To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

vnode_if.h: how should it be done ?

[Assar Westerlund]

I think it's wrong that vnode_if.h is not installed, this means that
you need to have kernel source to compile any third-party file system.

So I propose the patch below, to create vnode_if.h and then add it to CVS.

Any objectsions/comments/whatever?

/assar

Index: Makefile
===
RCS file: /home/ncvs/src/sys/kern/Makefile,v
retrieving revision 1.6
diff -u -w -r1.6 Makefile
--- Makefile1999/11/14 13:54:42 1.6
+++ Makefile2000/06/22 01:34:13
@@ -6,7 +6,7 @@
 ARCH=  i386 # luna68k news3400 pmax sparc tahoe vax
 
 all:
-   @echo "make tags, make links or init_sysent.c only"
+   @echo "make tags, make links, init_sysent.c, or ../sys/vnode_if.h only"
 
 init_sysent.c syscalls.c ../sys/syscall.h ../sys/syscall-hide.h \
 ../sys/syscall.mk ../sys/sysproto.h: makesyscalls.sh syscalls.master
@@ -17,6 +17,10 @@
-mv -f ../sys/syscall.mk ../sys/syscall.mk.bak
-mv -f ../sys/sysproto.h ../sys/sysproto.h.bak
sh makesyscalls.sh syscalls.master
+
+../sys/vnode_if.h: vnode_if.pl vnode_if.src
+   perl vnode_if.pl -h vnode_if.src
+   mv vnode_if.h ../sys
 
 # Kernel tags:
 # Tags files are built in the top-level directory for each architecture,


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

sys/sys/signalvar.h: change cursig to `static inline'

[Assar Westerlund]

I would like to commit the patch below to -current and 4-stable in a
little while.  It allows KLDs to be compiled without optimization.

Any objections/comments/anything?

/assar

Index: signalvar.h
===
RCS file: /home/ncvs/src/sys/sys/signalvar.h,v
retrieving revision 1.36
diff -u -w -r1.36 signalvar.h
--- signalvar.h 2000/03/28 18:06:49 1.36
+++ signalvar.h 2000/06/22 01:18:38
@@ -210,7 +210,6 @@
 void   sigexit __P((struct proc *p, int signum));
 void   siginit __P((struct proc *p));
 void   trapsignal __P((struct proc *p, int sig, u_long code));
-int__cursig __P((struct proc *p));
 
 /*
  * Machine-dependent functions:
@@ -229,7 +228,7 @@
  *
  * MP SAFE
  */
-extern __inline int __cursig(struct proc *p)
+static __inline int __cursig(struct proc *p)
 {
sigset_t tmpset;
int r;


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: mount_nfs/df bug?

[Kevin Day]

> 
> Hello!
> 
> Today I wanted to add a new NFS to my /etc/fstab, but forgot to add it
> to /etc/exports on the server.
> However, I did mount -a several times and always got a "Permission
> denied" for the last one.
> 
> Now look what I have here:
> 
> Filesystem   1K-blocks UsedAvail Capacity  Mounted on
> /dev/ad2a   396895   2919047324080%/
> /dev/ad2e  5257421  4626154   21067496%/usr
> procfs   440   100%/proc
> /dev/ad0s1 4224828  3755464   46936489%/dos
> neutron:/usr/ports  496367   3634489321080%/usr/ports
> neutron:/usr/ports-distfiles   2482878  1191660  109258852%
>/usr/ports-distfiles
> neutron:/usr/home/ncvs  992439   9606843175597%/usr/home/ncvs
> neutron:/usr/src928695   482371   37202956%/usr/src
> neutron:/usr/home/mp3  9591515  9298876   29263997%/usr/home/mp3
> neutron:/usr/home/brenn 695311   5948384484993%/usr/home/brenn
> neutron:/www/docs   297423   168669   10496162%/www
> neutron:/usr/doc   2482878  1191660  109258852%/usr/doc
> neutron:/usr/home/ncvs  992439   9606843175597%/usr/home/ncvs
> neutron:/usr/home/mp3  9591515  9298876   29263997%/usr/home/mp3
> neutron:/usr/home/brenn 695311   5948384484993%/usr/home/brenn
> neutron:/usr/home/ncvs  992439   9606843175597%/usr/home/ncvs
> neutron:/usr/home/mp3  9591515  9298876   29263997%/usr/home/mp3
> neutron:/usr/home/brenn 695311   5948384484993%/usr/home/brenn
> neutron:/usr/home/ncvs  992439   9606843175597%/usr/home/ncvs
> neutron:/usr/home/mp3  9591515  9298876   29263997%/usr/home/mp3
> neutron:/usr/home/brenn 695311   5948384484993%/usr/home/brenn
> neutron:/usr/home/ncvs  992439   9606843175597%/usr/home/ncvs
> neutron:/usr/home/mp3  9591515  9298876   29263997%/usr/home/mp3
> neutron:/usr/home/brenn 695311   5948384484993%/usr/home/brenn
> 
> Cute, isn't it?
> 
> Not yet discovered why.
> 
> Alex
> -- 
> cat: /home/alex/.sig: No such file or directory
> 
> 
> To Unsubscribe: send mail to [EMAIL PROTECTED]
> with "unsubscribe freebsd-current" in the body of the message
> 

This is probably similar to this:

http://www.freebsd.org/cgi/query-pr.cgi?pr=6187


-- Kevin


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Subversion (CVS rewrite) [Was: HEADS UP SMP development]

[Yusuf Goolamabbas]

I am not sure if people here are aware of Subversion which is CVS
redesigned to rip out its bad features. It's not ready yet though :-(

http://subversion.tigris.org/

More info on the Tigris project can be found here

http://www.tigris.org/

Cheers, Yusuf 
-- 
Yusuf Goolamabbas
[EMAIL PROTECTED]


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: HEADS UP: Destabilization due to SMP development

[Brad Knowles]

At 5:00 PM -0400 2000/6/21, Dan Papasian wrote:

>  Eivind Elkund was talking about doing something like
>  this.  He had a pretty nice document about it,
>  too.  If I recall, the name was "OVCS: Open Version Control System"

Hmm.  So far, Google hasn't been particularly useful in trying to 
track this stuff down.  The first page that came up was 
, which is for the "Open Source 
Version Control Software" page (i.e., good ole' CVS itself), and the 
next search turned up , which is the page for 
"Otselic Valley Central School".

Doing a bit more digging, I did finally manage to find 
, and 
although it has his name and the magic "ocvs" characters, I don't 
think this is quite what I'm looking for, either.


So far, the most useful page I've found on this topic is 
, but all it does is mention:

Notes: I'm a FreeBSD developer, presently on sabbatical.
For my sabbatical, I'm working on a new version control
system, aimed at distributed development.


Does anyone have any real information or useful pointers on 
exactly what he's working on right now, and what the current state of 
that project is?  Thanks!

--
   These are my opinions -- not to be taken as official Skynet policy
==
Brad Knowles, <[EMAIL PROTECTED]>|| Belgacom Skynet SA/NV
Systems Architect, Mail/News/FTP/Proxy Admin || Rue Colonel Bourg, 124
Phone/Fax: +32-2-706.13.11/12.49 || B-1140 Brussels
http://www.skynet.be || Belgium


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: HEADS UP: Destabilization due to SMP development

[Brad Knowles]

At 11:09 PM +0200 2000/6/21, Mark Murray wrote:

>>  Has anyone given any thought to what it would take to create an
>>  open source version of something similar to perforce?  ;-)
>
>  Clearly you have. :-). We await your submissions with baited breath...

If you're waiting for me on this, you might want to buy your 
burial plot now and go ahead and make all your final arrangements -- 
you're going to be waiting for a while.  ;-)

--
   These are my opinions -- not to be taken as official Skynet policy
==
Brad Knowles, <[EMAIL PROTECTED]>|| Belgacom Skynet SA/NV
Systems Architect, Mail/News/FTP/Proxy Admin || Rue Colonel Bourg, 124
Phone/Fax: +32-2-706.13.11/12.49 || B-1140 Brussels
http://www.skynet.be || Belgium


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: kernel config format migration script

[Cyrille Lefevre]

Brian Fundakowski Feldman <[EMAIL PROTECTED]> writes:

> I made a sed script to ease migration of kernel configuration files from
> the few-weeks-ago-CURRENT to current-CURRENT, and thought I might as well
> share it since it makes things easy (autonomous :)
> 
> You can find it at
>   http://people.freebsd.org/~green/oldconfig2new
> It requires extended regular expression support (because old regexps
> are so cumbersome to actually _use_), so for example:
>   mv GREEN GREEN.old
>   perl gethints.pl GREEN
>   sed -Ef oldconfig2new GREEN.old > GREEN

this one seems to be working w/ a standard sed :

==--== CUT HERE ==--==
#!/usr/bin/sed -f

# since ata[0-9] requires ata alone, delete them.
/^#*[ \t]*device[ \t]\{1,\}ata[0-9]\{1,\}/d

# delete fd[0-9] and fd alone.
/^#*[ \t]*device[ \t]\{1,\}fd[0-9]\{1,\}/d
/^#*[ \t]*device[ \t]\{1,\}fd$/d

# get rid of terminal spaces
s/[ \t]\{1,\}$//

# hints stuffs
/^ident[ \t]\{1,\}/ {
h
s/^ident\([ \t]\{1,\}\)\([a-zA-Z0-9_]\{1,\}\)/hints\1"\2.hints"/
# ^^ I'm not sure about this
#   are underscore and digits valid characters here ?
H
x
}
s/^\(#*[ \t]*\)pseudo-device\([ \t]\{1,\}\)/\1device\2/
s/^\(#*[ \t]*\)device\([ \t]\{1,\}\)\([a-zA-Z_]\{1,\}\)\([0-9]\{1,\}\)\([ 
\t]*\)\([^#]*\)\(.*\)$/\1device\2\3\5\7/
#  ^^^ also, here ?

==--== CUT HERE ==--==

\t need to be replaced w/ real tabs (under vi, :%s/\\t//g)
just in case, I put them here to be reliable (and visible :) via email.

Cyrille.
-- 
home:mailto:[EMAIL PROTECTED] Supprimer "no-spam." pour me repondre.
work:mailto:[EMAIL PROTECTED] Remove "no-spam." to answer me back.


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: HEADS UP!: config changes...

[Daniel C. Sobral]

Andrzej Bialecki wrote:
> 
> That's fine. However, this practically makes using /boot/loader
> mandatory. I still wonder if having some in-kernel interpreter wouldn't
> give us more choice, with exactly the same functionality. Of course, it
> would have to be run before any probing starts...

If you do not want to use loader, then use the "hints" option in the
config file.

What is going to get deprecated, though, is being able to userconfig
without using /boot/loader.

-- 
Daniel C. Sobral(8-DCS)
[EMAIL PROTECTED]
[EMAIL PROTECTED]
[EMAIL PROTECTED]

Windows works, for sufficently small values of "works".


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: HEADS UP: Destabilization due to SMP development

[Mark Murray]

>   Has anyone given any thought to what it would take to create an 
> open source version of something similar to perforce?  ;-)

Clearly you have. :-). We await your submissions with baited breath...

M
--
Mark Murray
Join the anti-SPAM movement: http://www.cauce.org


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: HEADS UP: Destabilization due to SMP development

[Dan Papasian]

Eivind Elkund was talking about doing something like
this.  He had a pretty nice document about it,
too.  If I recall, the name was "OVCS: Open Version Control System"

Perhaps someone could fill in the blanks?  I couldn't
find the document at the address I thought it was kept,
http://yes.no/perhaps/

I don't believe he had any code the last time we talked about it.
I do recall reading that he's using his time off to work on 
OVCS.  While I still don't think he has anything usable, 
you'd want to get in touch with him to reduce duplicated
effort.


-Dan

On Wed, Jun 21, 2000 at 09:59:25PM +0200, Brad Knowles wrote:
> At 9:34 PM +0200 2000/6/21, Soren Schmidt wrote:
> 
> >  Using a non opensource commercial version control system is just
> >  to ask for bad carma, extended murphy fields and whatnot in an
> >  opensource volounteer project...
> 
>   Has anyone given any thought to what it would take to create an 
> open source version of something similar to perforce?  ;-)
> 
> --
>These are my opinions -- not to be taken as official Skynet policy
> ==
> Brad Knowles, <[EMAIL PROTECTED]>|| Belgacom Skynet SA/NV
> Systems Architect, Mail/News/FTP/Proxy Admin || Rue Colonel Bourg, 124
> Phone/Fax: +32-2-706.13.11/12.49 || B-1140 Brussels
> http://www.skynet.be || Belgium


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: kernel config format migration script

[Eric Jacoboni]

> "Cyrille" == Cyrille Lefevre <[EMAIL PROTECTED]> writes:

Cyrille> well, at 4.x, FreeBSD sed doesn't support -E, is that GNU sed
Cyrille> which support this option or 5.x FreeBSD sed ? for instance,
Cyrille> GNU sed port doesn't exists !

FreeBSD-Current sed supports -E option...

-- 
-
Éric Jacoboni   « No sport, cigars! »  (W. Churchill)
-


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: HEADS UP!: config changes...

[Warner Losh]

In message <[EMAIL PROTECTED]> Andrzej Bialecki 
writes:
: That's fine. However, this practically makes using /boot/loader
: mandatory. I still wonder if having some in-kernel interpreter wouldn't
: give us more choice, with exactly the same functionality. Of course, it
: would have to be run before any probing starts...

All you'd need to do, if you don't want to compile it statically into
the kernel, is arrange to read a file in from disk.  With minor mods,
you could read the entire environement which the hints mechanism now
uses.

Warner


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: kernel config format migration script

[Cyrille Lefevre]

Brian Fundakowski Feldman <[EMAIL PROTECTED]> writes:

> I made a sed script to ease migration of kernel configuration files from
> the few-weeks-ago-CURRENT to current-CURRENT, and thought I might as well
> share it since it makes things easy (autonomous :)
> 
> You can find it at
>   http://people.freebsd.org/~green/oldconfig2new
> It requires extended regular expression support (because old regexps
> are so cumbersome to actually _use_), so for example:
>   mv GREEN GREEN.old
>   perl gethints.pl GREEN
>   sed -Ef oldconfig2new GREEN.old > GREEN

well, at 4.x, FreeBSD sed doesn't support -E, is that GNU sed which support
this option or 5.x FreeBSD sed ? for instance, GNU sed port doesn't exists !

Cyrille.
-- 
home:mailto:[EMAIL PROTECTED] Supprimer "no-spam." pour me repondre.
work:mailto:[EMAIL PROTECTED] Remove "no-spam." to answer me back.


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: HEADS UP: Destabilization due to SMP development

[Brad Knowles]

At 9:34 PM +0200 2000/6/21, Soren Schmidt wrote:

>  Using a non opensource commercial version control system is just
>  to ask for bad carma, extended murphy fields and whatnot in an
>  opensource volounteer project...

Has anyone given any thought to what it would take to create an 
open source version of something similar to perforce?  ;-)

--
   These are my opinions -- not to be taken as official Skynet policy
==
Brad Knowles, <[EMAIL PROTECTED]>|| Belgacom Skynet SA/NV
Systems Architect, Mail/News/FTP/Proxy Admin || Rue Colonel Bourg, 124
Phone/Fax: +32-2-706.13.11/12.49 || B-1140 Brussels
http://www.skynet.be || Belgium


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: VMware detection code in boot loader

[Warner Losh]

In message <[EMAIL PROTECTED]> Mike Smith writes:
: > a larger issue. It is not the loader's job to detect the underlying
: > hardware configuration.
: 
: Actually, in a broad fashion, it _is_.  This is why the loader 
: understands PCI and PnP, for example.

How hard would it be to add usb and pccard support?

Warner


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: mount_nfs/df bug?

[Cyrille Lefevre]

David Malone <[EMAIL PROTECTED]> writes:

> On Wed, Jun 21, 2000 at 02:35:51AM +0200, Cyrille Lefevre wrote:
> 
> > why there isn't an exportfs command as most unices have ?
> 
> "killall -HUP mountd" or "mount -u /" both work. This is mentioned
> in the mountd man page, but should probably also be mentioned in
> the exports man page.

well, what about exporting a directory w/o exporting a filesystem ?
which is usefull somethimes. possible too ?

Cyrille.
-- 
home:mailto:[EMAIL PROTECTED] Supprimer "no-spam." pour me repondre.
work:mailto:[EMAIL PROTECTED] Remove "no-spam." to answer me back.


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: HEADS UP: Destabilization due to SMP development

[Soren Schmidt]

It seems Warner Losh wrote:
> In message <12213.961613148@localhost> "Jordan K. Hubbard" writes:
> : Everyone talks about using bitkeeper but none of the people who
> : recommend it have ever actually tried to use it for anything.
> : Before such recommendations will bear weight, this needs to
> : change. :)
> 
> In that case, I'd recommend perforce :-)  I used it extensively at
> Pluto while I was there.  I'd love to see FreeBSD use it.  The
> non-open source ness of it is a bummer, but how much pain are we
> willing to tolerate for our ideals? :-)

Alot. 

Using a non opensource commercial version control system is just
to ask for bad carma, extended murphy fields and whatnot in an
opensource volounteer project...

-Søren


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: Unknown Devices

[Warner Losh]

In message <[EMAIL PROTECTED]> Mike Smith writes:
: Watch out - some USB modems are also WinModems.

usb tty and modems aren't supported, as far as I know.  How can you
tell the usb modems that are win modems?  And can y ou get docs on
them?

Warner


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: Unknown Devices

[Warner Losh]

In message <[EMAIL PROTECTED]> Eaglez writes:
: Well, i'm not sure about 5.0's new funky support (i
: mean, if it supports the SB Live, who knows), but in
: the past, PCI modems have never been supported,
: because they all tend to be win modems (only MS
: windows drivers available). I'd advise possibly an
: external modem. (Hey, they're probably still cheaper
: than USB modems, although i'd go with that if it IS
: somehow cheaper.)

PCI modems have been supported since just after 4.0 was released.
They *MUST* be controller based.  There are only two or three of these 
in the marketplace.

> pci0:  (vendor=0x11c1, dev=0x0441) at

0x11c1 is actiontec.  0x0441 is not the one known good device.  0x0480 
is that one.  0x0441 is, I think, the winmodem version, which sadly we 
cannot support at this time.

Warner


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: HEADS UP: Destabilization due to SMP development

[Warner Losh]

In message <12213.961613148@localhost> "Jordan K. Hubbard" writes:
: Everyone talks about using bitkeeper but none of the people who
: recommend it have ever actually tried to use it for anything.
: Before such recommendations will bear weight, this needs to
: change. :)

In that case, I'd recommend perforce :-)  I used it extensively at
Pluto while I was there.  I'd love to see FreeBSD use it.  The
non-open source ness of it is a bummer, but how much pain are we
willing to tolerate for our ideals? :-)

Warner


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: HEADS UP: Destabilization due to SMP development

[Jordan K. Hubbard]

Everyone talks about using bitkeeper but none of the people who
recommend it have ever actually tried to use it for anything.
Before such recommendations will bear weight, this needs to
change. :)

- Jordan


> 
> [EMAIL PROTECTED] said:
> :- "CVS branches suck" is the reason I belive. 
> 
> Bitkeeper?
> 
> -- 
> Robert Withrow -- (+1 978 288 8256)
> [EMAIL PROTECTED]
> 
> 
> 
> To Unsubscribe: send mail to [EMAIL PROTECTED]
> with "unsubscribe freebsd-current" in the body of the message



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: smbfs second mount

[Jordan K. Hubbard]

I think it should *definitely* be in the base system. :)

> On Sun, 18 Jun 2000, Brandon D. Valentine wrote:
> 
> > Out of curiosity, are there any plans to commit the smbfs stuff?  It is
> > really useful and I'd love to see it in the base system.
> 
>   Yes, I'm get much more responses about smbfs compared to nwfs. So,
> probably it should be in the base system.
> 
> --
> Boris Popov
> http://www.butya.kz/~bp/
> 
> 
> 
> To Unsubscribe: send mail to [EMAIL PROTECTED]
> with "unsubscribe freebsd-current" in the body of the message



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: SMP locking primities (was Re: HEADS UP: Destabilization due to SMP development)

[Greg Lehey]

On Tuesday, 20 June 2000 at 11:16:24 +0200, Martin Cracauer wrote:
> In <[EMAIL PROTECTED]>, Poul-Henning Kamp wrote:
>>
>> Am I the only person who miss a brief document which tells what
>> the outcome of the meeting was ?
>
> Who was there, anyway?

>From my trip report.  This can hardly be confidential.

Participants were:

  Don BradyApple Computer   File systems
  Ramesh   Apple Computer
  Ted Walker   Apple Computer   network drivers
  Jeffrey Hsu  FreeBSD project
  Chuck Paterson   BSDi Chief developer
  Jonathan Lemon   Cisco, FreeBSD project
  Matt Dillon  FreeBSD project  VM, NFS
  Paul SaabYahoo!
  Kirk McKusick
  Peter Wemm   Yahoo!
  Jayanth  Yahoo!
  Doug Rabson  FreeBSD project  Alpha port
  Jason Evans  FreeBSD project  kernel threads
  David Greenman   FreeBSD project  chief architect
  Justin Gibbs Adaptec, FreeBSD project SCSI, 0 copy TCP
  Greg Lehey   Linuxcare, FreeBSD project   storage management
  Mike Smith   BSDi, FreeBSD projecthardware, iA64 port
  Alfred Perlstein Wintel, FreeBSD project
  David O'BrienBSDi, FreeBSD projectcompilers, binutils
  Ceren Ercen  LinuxcareDaemon babe

Look also at http://ziplok.dyndns.org/msmith/SMPng/.

Greg
--
Finger [EMAIL PROTECTED] for PGP public key
See complete headers for address and phone numbers


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: HEADS UP: Destabilization due to SMP development

[Greg Lehey]

On Tuesday, 20 June 2000 at 12:57:41 -0600, Warner Losh wrote:
> In message <[EMAIL PROTECTED]> Poul-Henning Kamp writes:
>>  I think core has approved in principle, and several core members
>>  were present at the meeting (at least peter, dg, gibbs, dfr), that
>>  being said, I think we need to see some more concrete info before
>>  we pull the lever, just so we know what to expect.
>
> I'd like to see an explicit vote saying that current can be broken for
> months for SP users so the MP work can go in.  It has often been said
> that individual core members do not speak for core.

I'm quite happy to accept a majority vote of -core.

>>> The instability ni -current for MONTHS is pain not acceptible.
>>
>>  Sorry, Warner, but progress has its price, and this may be it.
>
> I don't think so.  I've done all the NEWCARD work in the tree, and it
> hasn't broken anything else (at least not for more than a few hours
> when I screwed up).  It has been painful for me to do it that way, but
> I think that some consideration should be given for the transition
> period for SP users.
>
> A few days or weeks I don't have a prblem with, but a few months is
> flat not acceptible.  It is too long.  If the code is that green, then
> some other mechanism needs to be used to facilitate collaberative
> working.
>
> I'd rather see a firm deadline proposed (eg, we'll commit the core on
> June 26, and will be done by Aug 26) so that I know what to expect
> rather than having the nebulous a few months phrase kicked around.  I
> expected the newcard stuff to be working in a few months, and it has
> been about 8 so far.

This was one of the points we discussed.  I was very much in favour of
a longer period so that people like you could commit their changes.
On the other hand, I think that the breakage will be relative, and it
will be less for SP systems than for SMP systems.  Certainly I think
that Matt and I need to get our act together (i.e. a system which at
least limps) before we commit anything; possibly people were a little
too optimistic about how quickly we could do things when we broke up
on Friday.

> Also, what if the new MP core goes in and one or more of the key
> players all of a sudden have no time to finish this due to unforseen
> circumstances?  Will the tree remain broken while they sort this
> out?

Maybe.  It depends on the circumstances and the preparedness of others
to fix it.  But I do think that we're entering a new phase of software
development with this project: for the first time we have a project
manager (Jason Evans), and I'd expect him to drum up some support,
from BSDi if necessary.  Note that Chuck Patterson is slated to help
us with 50% of his working time until we get this rickety framework to
fly.

Greg
--
Finger [EMAIL PROTECTED] for PGP public key
See complete headers for address and phone numbers


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: SMP locking primities (was Re: HEADS UP: Destabilization due to SMP development)

[Greg Lehey]

On Tuesday, 20 June 2000 at  9:41:57 +0200, Poul-Henning Kamp wrote:
>
> Am I the only person who miss a brief document which tells what
> the outcome of the meeting was ?

I'm writing up a detailed trip report for my company.  I can't see why
I shouldn't forward it to the SMP list as well, but I suppose I should
check.

> Can we get to see the slides ?

Chuck Patterson has some.  I'm sure we could get him to send the
.pdf's.

> Audio ?

No.

> Video ?

Very patchy.  I started taping about 3 hours into the meeting, and
since I had better things to do than be cameraman, from time to time
we ran out of tape.  I'll make copies when I get back home.  On the
positive side, it's PAL.  But Apple has promised to make an NTSC
conversion.

Greg
--
Finger [EMAIL PROTECTED] for PGP public key
See complete headers for address and phone numbers


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

kernel config format migration script

[Brian Fundakowski Feldman]

I made a sed script to ease migration of kernel configuration files from
the few-weeks-ago-CURRENT to current-CURRENT, and thought I might as well
share it since it makes things easy (autonomous :)

You can find it at
http://people.freebsd.org/~green/oldconfig2new
It requires extended regular expression support (because old regexps
are so cumbersome to actually _use_), so for example:
mv GREEN GREEN.old
perl gethints.pl GREEN
sed -Ef oldconfig2new GREEN.old > GREEN

Hope it saves some people time! :)

-- 
 Brian Fundakowski Feldman   /  "Any sufficiently advanced bug is\
 [EMAIL PROTECTED]   |   indistinguishable from a feature."  |
 FreeBSD: The Power to Serve!\-- Rich Kulawiec   /



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: irunning, width in bits.

[Matthew Dillon]

(Moving this to freebsd-smp, Bcc'ing current)

:What about shared interrupts? How are they going to be treated? With the
:spl leaving the arena it somehow looks feasible to run one interrupt
:source on two different threads if there are two pieces of hardware
:attached to the same interrupt line.
:
:>From what I understood from dfr, when switching away from an interrupt
:handler it is converted into a full thread. When the second piece of
:hardware fires an interrupt it could then run at the same time.
:
:Nick
:--
:[EMAIL PROTECTED]

This came up at the meeting and the conclusion was that shared
interrupts would run serially.  That is, each 'bit' in the cpl
(spl*(), also represented by ipending, the vector table dispatch, and
so forth) would be treated as a single interrupt thread.  If there 
are N interrupts hanging off that IRQ, then each of the N would
be run serially from a single interrupt thread.

This also came up a few months ago, you can probably find the discussion
in the archives.

What it comes down to is complexity and convenience.  In almost all
systems it is possible to rearrange the PCI boards such that you do
not have two critical interrupts on the same IRQ.

We are not precluding being able to schedule shared interrupts separately,
but if we are going to do it it will probably be much later when things
are more stable and not now.  The KISS principle applies here.

-Matt
Matthew Dillon 
<[EMAIL PROTECTED]>


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: HEADS UP: Destabilization due to SMP development

[Robert Withrow]

[EMAIL PROTECTED] said:
:- "CVS branches suck" is the reason I belive. 

Bitkeeper?

-- 
Robert Withrow -- (+1 978 288 8256)
[EMAIL PROTECTED]



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: mount_nfs/df bug?

[Ben Smithurst]

Alexander Langer wrote:

>> You probably have a symlink in the client path somewhere.  Is /usr/home
>> a symlink to /home or something?
> 
> drwxr-xr-x  7 root  wheel  512  6 Mär 14:45 /usr/home/
> lrwxrwxrwx  1 root  wheel  9 27 Feb 20:33 /home@ -> /usr/home

ok, that's not it, the /home symlink shouldn't matter...  Or are any of
the affected directories (brenn, mp3, ncvs) symlinks?  Or maybe your
/etc/fstab lists /home/foo instead of /usr/home/foo?

> However, that is not the point.

Well, if symlinks are involved I think this is a known bug.  Would you
care to fix it? :-) Whether it's a bug in the mount(8) program, the
mount(2) syscall, or somewhere deeper, I don't know.

-- 
Ben Smithurst / [EMAIL PROTECTED] / PGP: 0x99392F7D

 PGP signature

Re: ACPI project progress report

[Narvi]

On Tue, 20 Jun 2000, Warner Losh wrote:

> In message <[EMAIL PROTECTED]> Narvi 
>writes:
> : You obviously haven't considered the ability to be able to near hot-swap
> : motherboard and cpu - or even RAM - in this way. 
> 
> The ACPI spec specifically states that one cannot disassemble a
> machine in S4 state and expect the state to be saved on reassembly.
> Maybe the same sort of mechanism could be used to do this, but then
> again, maybe night.
> 

At any rate, being able to save and then restore the state would be the
needed inital step in reassembly related state saves/recoveres.

> Warner
> 



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: HEADS UP: Destabilization due to SMP development

[Nick Hibma]

CAM is not a valid example. It only touched the disk subsystem.

Merging back changes in blocks might not be possible. As Matthew
mentioned, Chuck's experience should be taken for a fact.

And bounding the amount of breakage is almost impossible without
squeezing the people doing the SMP work really badly. I don't think that
that is reasonable.

Nick

> One could argue that you could merge the changes to FreeBSD 5.X on a
> daily or weekly basis to that branch so that the branch doesn't get
> too far out of what.  Perforce users do this all the time (cf the cam
> project).  The model that I see is that a branch is created for SMP
> work, and that you find a volunteer who has access to SMP machines who 
> will merge from current into the SMP branch once a week and boot the
> resulting kernel.  If it works, he commits it, otherwise he resovles
> the problems.  That way the main developers aren't significantly
> impacted by the merging.
> 
> I'd be a lot happier if there was an upper bound on the length of time 
> that -current would be unstable, if there was a plan in place on what
> to do if that timelimit was exceeded, if there was a roadmap I could
> look at, etc.  Right now the vagueness of it all pushes my panic
> button.  I'm trying to get more information so that I know if I should 
> just calm down and it won't be that bad, or if I should pitch a huge
> fit because it will be too painful to make progress on any other
> front.  Please help me with that.
> 
> I'd also be happy if I could create a newcard branch off the last
> stable version of freebsd 5.0-current.  That way I could continue my
> work with others and the instability wouldn't matter.  All merging, if 
> any, would be my responsibility.  I don't know what the level of pain 
> 
> Of course the same arugment about merging you make could be made for
> new kernel work.  They will either have to live with the pain (which
> is currently ill-defined at best, knowing what the pain would be would 
> help my confort level), or do their work and then redo it on the new
> and improved FreeBSD months later.  Why should SMP force others to do
> that?
> 
> Warner
> 
> 
> To Unsubscribe: send mail to [EMAIL PROTECTED]
> with "unsubscribe freebsd-current" in the body of the message
> 

--
[EMAIL PROTECTED]
[EMAIL PROTECTED]  USB project
http://www.etla.net/~n_hibma/



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: HEADS UP: Destabilization due to SMP development

[Nick Hibma]

More over, unlike other big project like CAM, this baby is going to
touch the gut of the OS.

It might be possible however for individual projects to move into a
separate branch.

Nick

> >What about doing the changes on a branch with the understanding that 
> >the branch will *replace* HEAD when it stabilises ?
> 
> "CVS branches suck" is the reason I belive.
> 
> --
> Poul-Henning Kamp   | UNIX since Zilog Zeus 3.20
> [EMAIL PROTECTED] | TCP/IP since RFC 956
> FreeBSD coreteam member | BSD since 4.3-tahoe
> Never attribute to malice what can adequately be explained by incompetence.
> 
> 
> To Unsubscribe: send mail to [EMAIL PROTECTED]
> with "unsubscribe freebsd-current" in the body of the message
> 
> 

--
[EMAIL PROTECTED]
[EMAIL PROTECTED]  USB project
http://www.etla.net/~n_hibma/




To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

irunning, width in bits.

[Nick Hibma]

What about shared interrupts? How are they going to be treated? With the
spl leaving the arena it somehow looks feasible to run one interrupt
source on two different threads if there are two pieces of hardware
attached to the same interrupt line.

>From what I understood from dfr, when switching away from an interrupt
handler it is converted into a full thread. When the second piece of
hardware fires an interrupt it could then run at the same time.

Nick
--
[EMAIL PROTECTED]
[EMAIL PROTECTED]  USB project
http://www.etla.net/~n_hibma/



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: ACPI project progress report

[Josef Karthauser]

On Tue, Jun 20, 2000 at 08:14:41PM +0200, Narvi wrote:
> 
> You obviously haven't considered the ability to be able to near hot-swap
> motherboard and cpu - or even RAM - in this way. 
> 

You're right!  I hadn't!  (Although I've dreamed about it a few times).

Joe


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: mount_nfs/df bug?

[David Malone]

On Wed, Jun 21, 2000 at 02:35:51AM +0200, Cyrille Lefevre wrote:

> why there isn't an exportfs command as most unices have ?

"killall -HUP mountd" or "mount -u /" both work. This is mentioned
in the mountd man page, but should probably also be mentioned in
the exports man page.

David. 


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: SMP locking primities (was Re: HEADS UP: Destabilization due to SMP development)

[Jason Evans]

On Tue, Jun 20, 2000 at 09:41:57AM +0200, Poul-Henning Kamp wrote:
> 
> Am I the only person who miss a brief document which tells what
> the outcome of the meeting was ?

I'm at USENIX right now, so I'm a bit strapped for time to work on this.
Still, I plan to email a brief summary of the meeting within the next
couple of days.  It won't include all of the gory details, simply because I
don't remember all of them(my notes were mainly for my own benefit, and are
of limited usefulness).

> Can we get to see the slides ?

I have the slides, but need to get them on a web page.  This will also
happen in the next couple of days.

> Audio ?
> 
> Video ?

Greg Lehey has a PAL recording of much of the meeting.  If you want to get
ahold of a copy, talk to him privately to see what arrangements you can
make.

Jason


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: make.conf fix

[Satoshi - Ports Wraith - Asami]

 * From: Will Andrews <[EMAIL PROTECTED]>

 * Hi -current and -ports,
 * 
 * I've noticed something that seems to have been broken for a long time.
 * In etc/defaults/make.conf we have several MASTER_SITE_* variables which
 * reference "%SUBDIR%".  However, these variables do not work as expected.
 * So we must fix this discrepancy with the following patch.

 * -#MASTER_SITE_XCONTRIB=  ftp://ftp.x.org/contrib/%SUBDIR%/
 * +#MASTER_SITE_XCONTRIB=  ftp://ftp.x.org/contrib/${MASTER_SITE_SUBDIR}/

Waitaminit.  These are correct, please look at bsd.sites.mk.  What
makes you think they are not working?

Satoshi


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message