RE: new rc.network6 and rc.firewall6

[Andrea Campi]

Maybe we could have a script to do the dependency check and "compile"
everything in a single big file? This script could run at boot and also
after mergemaster, whatever: it just check the modification time against a
cache file, where it also stores dependencies.

Just my Euro 0.02 ;-)

Bye,
Andrea

 -Original Message-
 From: David O'Brien [mailto:[EMAIL PROTECTED]]
 Sent: Tuesday, October 24, 2000 10:27 PM
 To: Warner Losh
 Cc: [EMAIL PROTECTED]
 Subject: Re: new rc.network6 and rc.firewall6
 
 
 On Tue, Oct 24, 2000 at 12:31:57PM -0600, Warner Losh wrote:
  The scripts themselves have the ordering dependencies.  The startup
  system runs them in the proper order.  I don't know if this is
  pre-computed or redone each boot.
 
 Redone on each boot up (and shutdown).

--
You can have it soon, cheap and working. Choose *two*, not three!

Andrea Campi
Network Administrator
World Online S.rl.
V. Montecuccoli, 20 - 20132 Milano, Italy

Tel. +39 02 483293.1
Fax. +39 02 483293.601
--


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

Re: strange problem of PPPoE + NAT

[Idea Receiver]

thx. that fix my problem ;)

the other problem i had after switch that system to -current
is that after a random time, the connection will frzzed.
the routing table still exist, connection is still up.
just cant connect to anywhere outside the network. no error
or anything been loged in ppp.log. the connection just simply
freezed. the only way to bring the connection back is to reboot
the system. (i try to just bring down the interface and bring
back up. but it seems doesnt help), otherwise it will give
an error of unable to connect to device..

at the moment, everytime i run ppp, follow error will appear

 module_register: module netgraph already exists!
 linker_file_sysinit "netgraph.ko" failed to register! 17

but i believe this has nothing to do with the problem connection
freezed.

plz help!


On Sat, 21 Oct 2000, Josh Tiefenbach wrote:

 On Sat, Oct 21, 2000 at 11:08:28PM +1000, Idea Receiver wrote:
  
  I just upgrade one of my server to -current. that server connect to ADSL
  and act as a gateway.
  
  however, after I upgrade that server to -current, all other clients
  (all windows 98) start acting really strange. clients was unable to 
  connect to more then 60% of web sites. for example, clients can not 
 
 Sounds like a PMTU-D problem. Either change the MTU of the machines behind the
 gateway to something like 1440, or try /usr/ports/net/tcpmssd.
 
 josh
 
 -- 
 "Watching those 2 guys [Bush and Gore] debate is like watching Ben Stein read
 'The Story of O'" -- Dennis Miller
 
 
 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: make release breakage - dokern.sh patch 2

[Andrzej Bialecki]

On Tue, 24 Oct 2000, Jordan Hubbard wrote:

 Believe me, if we were to put out a serious call to kill NFS from the
 installation boot images, you'd very quickly hear from all of those
 people and they would be screaming.  We need to exhaust all other
 possibilities before we even contemplate that option.

IMHO the battle to keep the floppies from overflowing is already lost.
Each time it's like cutting out your limbs to fit into tight clothes. What
I think we need is to find new clothes, so to speak, i.e. some other way
of organizing the content on the floppies. If we don't do it, we will keep
loosing.

E.g. we could move some of the drivers to the mfsroot.flp as KLDs, and
either autoload them later (i.e. not from the bootloader, but using
kldload), or have some options in the menu for loading. This way at least
we will avoid overflowing kern.flp.

Andrzej Bialecki

//  [EMAIL PROTECTED] WebGiro AB, Sweden (http://www.webgiro.com)
// ---
// -- FreeBSD: The Power to Serve. http://www.freebsd.org 
// --- Small  Embedded FreeBSD: http://www.freebsd.org/~picobsd/ 




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

Re: current hangs when boot

[Johan Kruger]

In message [EMAIL PROTECTED] Bigbear writes:
: i update my system from 4.1 to current, when system boot, it hangs when:
: start elf ldconfig: /usr/lib /usr/lib/compat /usr/X11R6/lib
: why?


This is not a hang, otherwise you would not have been able to boot by
pressing ^C or ^T
The files , especially rc files in /etc are not the newest ones. The
script rc is suppose to use ldconfig to update the library database,
but when it starts it waits. If you bypass this by pressing keys, the
it might happen that you get errors with certain libraries, seeing that
they are not loaded.

So, all you need to do is to take /usr/src/etc and copy rc* /etc
This solved the problem for me. I did a make buildworld and installworld
yesterday and i got the problem on a second reboot.
I had a look in the /etc directory and saw that the files did not install ...
which makes sense since the spec of buildworld/installworld is that the etc dir
is not updated.

I started a make release 25 minutes ago, will see if the end result of a
snapshot will give the same problem.

P.S. After updating your files in /etc, do a shutdown -r now , the shutdown rc
script will take care of the entropy factor next time around.


 : ^C also works.
 : 
 : ^T is generally useful if you suspect something is hanging on bootup but
 : don't know what it is.
 
 We also found at bsdcon that lots of keystrokes would also make the
 system boot.
 
 Which reminds me of the Sun software problem report that had as the
 engineering reply: "Don't hit on the keyboard like a wild monkey" .. :-)
 
--
Unix Software Developer/Engineer
E-Mail: Johan Kruger [EMAIL PROTECTED]
Date: 25-Oct-00
Time: 11:02:51
OS: FreeBSD 5.0-2724-SNAP
All good things come to those who ... run FreeBSD
--


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

Re: entropy reseeding is totally broken

[Terry Lambert]

 I see the opposite.  I see that without writing to the /dev/random
 device I get a cons is an object that cares fortune 99+% of the time
 on my first login.  With it, I see more decently random fortunes (but
 I haven't done a statistical analysis of them to see how random things 
 are).

Is it just me, or have there been more problems achieving
real statistical randomness since /dev/random went in, than
at any other time in BSD history?

I booted a 1.5 system a couple of times for grins.

It gives you a different fortune each time.

Note that 1.5 "lacked" /dev/random.

Perhaps it's time to rename it as /dev/deliberate?


Terry Lambert
[EMAIL PROTECTED]
---
Any opinions in this posting are my own and not those of my present
or previous employers.


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

Re: make release breakage - dokern.sh patch 2

[Tatsumi Hosokawa]

At Wed, 25 Oct 2000 04:48:14 +0900,
Motomichi Matsuzaki [EMAIL PROTECTED] wrote:
 
 I vote for 'remove NFS away'.

How about mergeing ifconfig kldload function into sysinstall, and move
/boot/kernel/if_xxx.ko into mfsroot.gz mfs image.

hosokawa

--
Tatsumi Hosokawa
[EMAIL PROTECTED]
http://www.sm.rim.or.jp/~hosokawa/


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

Re: make release breakage - dokern.sh patch 2

[Tatsumi Hosokawa]

At Wed, 25 Oct 2000 19:37:42 +0900,
Tatsumi Hosokawa [EMAIL PROTECTED] wrote:
 
 How about mergeing ifconfig kldload function into sysinstall, and move
 /boot/kernel/if_xxx.ko into mfsroot.gz mfs image.

or simply add,

main()
{
+   for ( i in /kernel/*.ko ) {
+   kdload(i);
+   }

How about it?  If it's acceptable, I'll try to write this patch this
weekend.


--
Tatsumi Hosokawa
[EMAIL PROTECTED]
http://www.sm.rim.or.jp/~hosokawa/


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

Re: make release breakage - dokern.sh patch 2

[Terry Lambert]

 Again. There is no public NFS servers for distributing FreeBSD as I know.
 You can't get any FreeBSD, even if you sends NFS packets to the Internet.
 Can I and anybody access your favorite NFS servers?

MIT, gatekeeper.dec.com, and Sunsite all run anonymous NFS
mountable archives.

Also, be aware, that webnfs is getting more support in some
browsers, recently, and it rides on top of NFS.


Terry Lambert
[EMAIL PROTECTED]
---
Any opinions in this posting are my own and not those of my present
or previous employers.


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

Re: new rc.network6 and rc.firewall6

[Terry Lambert]

 This was my thought also.  I put the TCP/IP scripts at 99 to make 
 sure that any slow network initialization is done.
 
 Since they all start with S - for example S99tcp - moving it
 to s99tcp will keep it from starting, and the Knnname in the same
 directory is used to stop things when moving from that run level.
 
 It's one of the things I like about the Sys V /etc/rcn.d
 directory structure, as you can easily fine tune it to fit your
 needs.  Just a look at the files and you know the order.

The primary reason I'm aware of is to support transitioning
between run levels, where some of the stuff in the previous
run level is left running.

For the increasingly anal security types, run levels would let
you support booting without a network, until after you had
battened down the hatches.  I'd never use it, in normal use,
but what the heck...


Terry Lambert
[EMAIL PROTECTED]
---
Any opinions in this posting are my own and not those of my present
or previous employers.


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

Re: entropy reseeding is totally broken

On Wed, Oct 25, 2000 at 10:35:55AM +, Terry Lambert wrote:
  I see the opposite.  I see that without writing to the /dev/random
  device I get a cons is an object that cares fortune 99+% of the time
  on my first login.  With it, I see more decently random fortunes (but
  I haven't done a statistical analysis of them to see how random things 
  are).
 
 Is it just me, or have there been more problems achieving
 real statistical randomness since /dev/random went in, than
 at any other time in BSD history?
 
 I booted a 1.5 system a couple of times for grins.
 
 It gives you a different fortune each time.
 
 Note that 1.5 "lacked" /dev/random.

It is because /dev/random totally ignore _time_ and not reseed from it,
but no other randomness source available at boot time. 

At the boot /dev/random tries to reseed from other sources (excepting
time), but:

1) Reseed code is broken, in come case (as I describe) all reseeding data
is ignored, only its size is counted until it was as big as 16384. Mark
not fix it yet at this moment nor confirm he is able to reproduce this
bug.

2) Reseeding state may not preserve across the boot due to various reasons
like panic, etc. Since _time_ is ignored, all other data /etc/rc tries to
collect now can be non-random _easily_!

Unless _time_ will be used, /dev/random is plain unusable for production
usage.

-- 
Andrey A. Chernov
http://ache.pp.ru/


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

Re: sysinstall's console keymap menu

[Jordan Hubbard]

 OK, if I understood correctly, is this patch reasonable at this time?

Yes, this looks much better!

- Jordan


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

Re: make release breakage on today's -current

[Makoto MATSUSHITA]

obrien I just diked out more bits.  Lets see if that will give us
obrien enough space on tonights snapshot build.

Whole release procedures are works fine. Thank you. Here's summary of
current size of floppies (i386 architecture):

* boot.flp (639k left)
Filesystem  1K-blocks UsedAvail Capacity iused   ifree  %iused  Mounted
/dev/vnn1c   2843 2204  41284%   6  5610%   /mnt

* kern.flp (19k left)
Filesystem  1K-blocks UsedAvail Capacity iused   ifree  %iused  Mounted
/dev/vnn1c   1407 1388  -93   107%   6  2420%   /mnt

* mfsroot (926k left)
Filesystem  1K-blocks UsedAvail Capacity iused   ifree  %iused  Mounted
/dev/vnn1c   2803 1877  70273%  67 31518%   /mnt

* mfsroot.flp (579k left)
Filesystem  1K-blocks UsedAvail Capacity iused   ifree  %iused  Mounted
/dev/vnn1c   1407  828  46664%   2  28 7%   /mnt

* fixit.flp (37k left)
Filesystem  1K-blocks UsedAvail Capacity iused   ifree  %iused  Mounted
/dev/vnn1c   1363 1326  -72   106% 263 11969%   /mnt



FYI for hosokawa-san: We have total 912kbytes of 'if_*' modules, and
it can be shrinked to 328kbytes if gzip -9.

-- -
Makoto `MAR' MATSUSHITA


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

Re: make release breakage - dokern.sh patch 2

[Tatsumi Hosokawa]

At Wed, 25 Oct 2000 21:23:01 +0900,
[EMAIL PROTECTED] wrote:
 
 From: "David O'Brien" [EMAIL PROTECTED]
 Date: Tue, 24 Oct 2000 13:15:26 -0700
 
  Before removing NFS, I'd remove the new `ncv', `nsp', and `stg' drivers.
 
 Please do not remove them. Many people are waiting for them to switch
 from 3.x with PAO3 or even with 2.x with PAO to more recent FreeBSD.

If sysinstall with kldload works, we don't have to remove no driver
and no protocols from boot.flp.  I'll work on it this weekend.


--
Tatsumi Hosokawa
[EMAIL PROTECTED]
http://www.sm.rim.or.jp/~hosokawa/


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

LINT broken...

[Poul-Henning Kamp]

Somebody killed "swihand_t" without cleaning up three drivers:

otte# ./gsys swihand_t
./i386/isa/cy.c:static  swihand_t siopoll;
./i386/isa/rc.c:static swihand_t rcpoll;
./pc98/pc98/sio.c:staticswihand_t siopoll;



otte# cd /sys/i386/conf
otte# make LINT
`LINT' is up to date.
otte# config LINT
WARNING: Old PCI driver compatability shims present.
WARNING: Old ISA driver compatability shims present.
Don't forget to do a ``make depend''
Kernel build directory is ../../compile/LINT
otte# cd ../../compile/LINT
otte# make cy.o
cc -c -O -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes  
-Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual  -fformat-extensions -ansi  
-nostdinc -I- -I. -I../.. -I../../../include -DGPROF -D_KERNEL -include opt_global.h 
-elf -malign-functions=4 -fno-builtin -mpreferred-stack-boundary=2 -pg 
../../i386/isa/cy.c
../../i386/isa/cy.c:338: syntax error before `cypoll'
../../i386/isa/cy.c:338: warning: type defaults to `int' in declaration of `cypoll'
../../i386/isa/cy.c:338: warning: data definition has no type or storage class
[...]

otte# make rc.o
cc -c -O -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes  
-Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual  -fformat-extensions -ansi  
-nostdinc -I- -I. -I../.. -I../../../include -DGPROF -D_KERNEL -include opt_global.h 
-elf -malign-functions=4 -fno-builtin -mpreferred-stack-boundary=2 -pg 
../../i386/isa/rc.c
../../i386/isa/rc.c:187: syntax error before `rcpoll'
../../i386/isa/rc.c:187: warning: type defaults to `int' in declaration of `rcpoll'
[...]

--
Poul-Henning Kamp   | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD committer   | 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

Re: smp instability

[Patrick Hartling]

John Baldwin [EMAIL PROTECTED] wrote:

} 
} On 25-Oct-00 Chuck Robey wrote:
}  I'm having rather extreme problems with stability on my dual PIII
}  setup.  I know this is to be expected, but it's gotten so extreme on my
}  system, I can't spend more than a few minutes before it locks up.
}  
}  Is there any chance that I could make things better by using a sysctl to
}  tell the box it's now a single-cpu system?  I can't read man pages at the
}  moment (I'm composing this on my Sparc Ultra-5) so if this might work, and
}  someone knows the exact command to use, I'd appreciate a bit of help.
} 
} You can use kernel.old to compile a UP kernel.  I always keep a UP kernel
} around just in case.  Also, when did your SMP box become unstable?  There
} was a known problem with SMP boxes when the vm page zero'ing during the idle
} loop was first turned on that has since been fixed with the latest commit to
} vm_machdep.c yesterday.  Symptoms were frequent kernel panic 12's with
} interrupts disabled .

I am having the same lockup problems as Chuck with SMP kernels built since
October 21.  The system completely locks up after a short period of time.
If I'm running X, it does it within 10-15 minutes, but if I don't run X
and just leave it at the console, it can go for a few hours.  It does
eventually lock up, though.  I haven't tried building a UP kernel, but I
will try the latest vm_machdep.c changes.  If that doesn't work, I'll go
the UP route since I'm tired of being unable to list my processes.  :\

My working world+kernel was built October 4.  Normally, I update my
-current system more frequently than that, but this has been an abnormally
busy month.  Because of that, I can't narrow down exactly when the
instability began.  Right now, I'm running with a world built October 23
and the October 4 kernel which is rather unpleasant.

 -Patrick


Patrick L. Hartling | Research Assistant, VRAC
[EMAIL PROTECTED] | 2624 Howe Hall -- (515)294-4916
http://www.137.org/patrick/ | http://www.vrac.iastate.edu/


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

$B#D%^%,9XFI$N$*4j$$!*(B

[DNT$B4IM}<T(B]

$B$I$&$+$46(NO$r4j$$$7$^$9!#(B
$BEvJ}$O@lLg#D%^%,%8%s$rH/9T$7$F$$$k$NL5$$J}$O:#8e0l@Z$NG[?.5Z$S%"%I%l%9$N1J5W:o(B
$B=|(B
$B:n6H$rI,$:CW$7$^$9!#$I$&$+$4N;>54j$$$^$9$3$H$r$*4j$$CW$7$^$9!#(B
$B@?$K>!?'!9!d(B
$B$H$J$j$^$9!#(B
$B$^$?!"7n$K0lEY$4EPO?$5$l$J$$J}$O0J8eG[?.$r$7$J$$$h$&1J5W:o=|$r$$$?$7$^$9$N$G!"$*(B
$BeBeM}E9$K$J$i$J$/$F$O$^$:!"<}F~$O(B
$B%7%e%_%l!<%7%g%sDL$j$K$O$J$j$^$;$s!#(B
$B;d$?$A$N%0%k!<%W$G$O!"$I$3$h$j$bAa$/BeM}E9$K$J$l$k%N%&%O%&$r(B
$B;}$C$F$$$^$9!#(B
$B%0%k!<%W$N%5%]!<%HBN@)$,<+K}$G$9!*(B
 http://www.jin.ne.jp/joyful21/bp/bp065.htm

$BC4Ev;3ED$7$E$+(B
$B%a!<%k!!([EMAIL PROTECTED]

=
===

$B%a!<%k$G9-9p$r

Re: divert as module?

[Bill Fumerola]

On Sun, Oct 22, 2000 at 09:52:03PM +0200, Leif Neland wrote:
 I want to install ipfw and natd to a machine working as isdn-router, which I
 lost the kernel config for
 I connect to the world via userland-ppp and isdnd.
 
 I don't have any ipfw or divert compiled in the kernel, but I can load
 ipfw.ko, so the firewall rules can work (I now see my isp sends IGMP's to
 me...)

Stop right here. If you didn't compile IPDIVERT in the kernel, the hooks aren't
in the tcp/ip stack and you're screwed.

Figuring out a way to fix this is on my TODO list, though I don't have any ideas that
don't cost a performance hit for non-DIVERT users.

-- 
Bill Fumerola - Network Architect, BOFH / Chimes, Inc.
[EMAIL PROTECTED] / [EMAIL PROTECTED]





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

Re: entropy reseeding is totally broken

[Mark Murray]

 1) Reseed code is broken, in come case (as I describe) all reseeding data
 is ignored, only its size is counted until it was as big as 16384. Mark
 not fix it yet at this moment nor confirm he is able to reproduce this
 bug.

I'm trying to reproduce this formally. I'm looking for reasons, not
any more hacks.

 2) Reseeding state may not preserve across the boot due to various reasons
 like panic, etc. Since _time_ is ignored, all other data /etc/rc tries to
 collect now can be non-random _easily_!
 
 Unless _time_ will be used, /dev/random is plain unusable for production
 usage.

Andrey, read the code; nanotime is all over the harvested entropy.

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: -current hangs during boot (UPDATING entry)

[Mark Hittinger]

It does look like an updating entry is needed for this badly.

I did the following things, some of which may not be needed, and now my 
-current boxes boot OK.

1.  update MAKEDEV from /usr/src/etc, run MAKEDEV all

2.  update /etc/rc /etc/rc.* /etc/defaults/rc.conf from /usr/src/etc

3.  add random_load="YES" to /boot/loader.conf

4.  update /etc/login.conf from /usr/src/etc

5.  do a "shutdown -r now" which creates the entropy file and reboots

Now the system boot does not hang at the ldconfig spots.  It does look like
there is a lot to do to get back on course, enough to justify adding to
UPDATING.

Later

Mark Hittinger
Earthlink
[EMAIL PROTECTED]


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

Re: entropy reseeding is totally broken

On Wed, Oct 25, 2000 at 10:37:31AM -0700, Mark Murray wrote:
  Unless _time_ will be used, /dev/random is plain unusable for production
  usage.
 
 Andrey, read the code; nanotime is all over the harvested entropy.

I saw it in the code, but it not means it working. If the time is really
taken, neither mine or Warner case is ever possible.

-- 
Andrey A. Chernov
http://ache.pp.ru/


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

USW2 Root: -current build report for Wed Oct 25 02:11:14 CDT 2000

[Jordan Hubbard]

Woohoo!  First one in awhile! :-)

Of course, given that freebsd-current has a routing loop right
now you'll all probably see this message at least 4 times over
the next week, but hey, not my fault. :)

- Jordan

--- Forwarded Message

Return-Path: [EMAIL PROTECTED]
Delivery-Date: Wed Oct 25 07:28:01 2000
Return-Path: [EMAIL PROTECTED]
Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125])
by winston.osd.bsdi.com (8.11.1/8.9.3) with ESMTP id e9PES0444547
for [EMAIL PROTECTED]; Wed, 25 Oct 2000 07:28:01 -0700 (PDT)
(envelope-from [EMAIL PROTECTED])
Received: from hub.freebsd.org (hub.FreeBSD.org [216.136.204.18])
by mx1.FreeBSD.org (Postfix) with ESMTP id D860B6E3213
for [EMAIL PROTECTED]; Wed, 25 Oct 2000 07:28:02 -0700 (PDT)
Received: by hub.freebsd.org (Postfix)
id BCC5D37B4C5; Wed, 25 Oct 2000 07:28:02 -0700 (PDT)
Delivered-To: [EMAIL PROTECTED]
Received: from usw2.freebsd.org (usw2.freebsd.org [209.180.6.226])
by hub.freebsd.org (Postfix) with ESMTP id 3C7EE37B479
for [EMAIL PROTECTED]; Wed, 25 Oct 2000 07:28:02 -0700 (PDT)
Received: (from root@localhost)
by usw2.freebsd.org (8.11.1/8.11.0) id e9PES1a37516
for [EMAIL PROTECTED]; Wed, 25 Oct 2000 09:28:01 -0500 (CDT)
(envelope-from root)
Date: Wed, 25 Oct 2000 09:28:01 -0500 (CDT)
From: USW2 Root [EMAIL PROTECTED]
Message-Id: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: -current build report for Wed Oct 25 02:11:14 CDT 2000

Doing nightly build attempt for 5.0-20001025-CURRENT at Wed Oct 25 02:11:14 CDT 2000
Updating source tree...
Making release...
Release build of 5.0-20001025-CURRENT was a success at Wed Oct 25 09:12:54 CDT 2000

--- End of Forwarded Message



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

Re: make release breakage - dokern.sh patch 2

[Terry Lambert]

   Other candidates I've been pointed to include the removal of
   /boot/boot[12] and NFS
  IMO NFS needs to stay.  It is *very* useful to many (including me).
 
 I vote for 'remove NFS away'.
 
 Yes, there are many people using NFS install, but it is site-specific.
 There are no services distributing FreeBSD via NFS in public.
 In such site-specific situation,
 you can make your *specific* floppies with NFS and without INET6 or some.

IPv6 is site specific, but it has been important since April
24th of this year to support IPv6, since that was the date
that Cisco released code to support it in all their supported
routers.  But right now, we all know that widescale acceptance
of IPv6 is going to have to come in at the client level, with
Microsoft driving the deployment process.

It wouldn't hurt if someone were to build a highly efficient
NAT box for IPv6-IPv4, so that once Microsoft CDROMs could be
pressed by ATT @HOME or some other severable network provider,
that IPv6 deployment could go forward a large chunk of the net
at a time, instead of being an all-or-nothing crash-fest.  Take
this as a hint to the IPv6 advocates in the audience that they
need to do something.

NFS is also important.  NFS is hard to load as a driver, and
keep the LEASE code working.  NFSv4 is looming on the horizon,
and it appears to finally fix locking, for once and for all,
for non-coelescing clients, as well as for stacking VFS layers
including an NFS VFS somewhere in the stack.  There is some
possibility that it will actually be useful to Windows systems.

I think it's time to look at supporting "drivers" floppies,
and the pain in having no floppies is certainly incentive for
someone to do the work, should that become stated policy of
the project to support most things through driver floppies
that are loaded post-boot.


Terry Lambert
[EMAIL PROTECTED]
---
Any opinions in this posting are my own and not those of my present
or previous employers.


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

Re: new rc.network6 and rc.firewall6

[Gerhard Sittig]

On Wed, Oct 25, 2000 at 06:04 +0700, Alexey Dokuchaev wrote:
 On Tue, 24 Oct 2000, David O'Brien wrote:
 
  On Tue, Oct 24, 2000 at 04:23:40PM +0700, Alexey Dokuchaev wrote:
   Why can't I simply write kill -1 `cat
   /var/run/sendmail.pid`?
  
  What about deamons that don't understand `kill -HUP'?
  Sendmail didn't until very reciently.
  ``/etc/rc.d/some-deamon restart'' does the right thing
  reguardless how involved that might be.
 
 Though I see your point, actually, many UNIX books, including
 some pretty old ones, refer to sending HUP signal as standard
 way of restarting/resetting daemons.

Please tell the software authors about it, too. :)  Although
there might be some form of convention, not everyone might follow
it (some might not be able even if they tried without breaking
established behaviour).  Wrapping those services will make
starting, stopping, reloading, querying status and whatever you
usually do to them easy and consistent for the user again.

BTW:  Do you know all the pidfile names and locations by heart?
Across every version and platform you are running / taking care
of?


virtually yours   82D1 9B9C 01DC 4FB4 D7B4  61BE 3F49 4F77 72DE DA76
Gerhard Sittig   true | mail -s "get gpg key" [EMAIL PROTECTED]
-- 
 If you don't understand or are scared by any of the above
 ask your parents or an adult to help you.


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

Re: new rc.network6 and rc.firewall6

[Gerhard Sittig]

On Tue, Oct 24, 2000 at 14:56 -0700, Jordan Hubbard wrote:
 
  [ ... NetBSD (or Linux?) like rc scripts ... ]
 
 So, who wants to do a proof-of-concept implementation for
 -current which integrates with our existing rc.conf mechanism?
 In order to obey POLA, we should at least have the separate
 scripts switch off the same knobs whenever possible.

I do.  As far as I understand the new scripts typically look
something like this:

- am I (the special service) enabled?
- is my executable present?
- is my config present?
- optional:  are my prerequisited (neighbour / underlying
  services) met?
- start me up, obeying flags if present

All of this is currently done in the monolithic block, too.  I
don't see the difference yet (except for splitting the logically
distinct functions apart into "natural" groups).

What's new is:

- include the general config at the start (and yes, in every
  single script -- but this should be neglectable in terms of
  speed penalty and makes them work separately, too -- which is a
  real big gain!)
- maybe include (source) some common code like
  - determining pids belonging to program names
  - starting processes in an supervised or backgrounded or any
other special way
  - have some printouts, error level summary, etc

but I don't see FreeBSD having this level of "rc lib" as NetBSD
has in rc.subr or even RedHat has in /etc/rc.d/functions(sp?).
So only the sourced rc.conf (default and customized) remains.

The real new part eating most of the time to implement is the
shutdown path (which I understand to be somewhat absent in
FreeBSD right now, "kill -TERM everything" seems to do the job
right now).

 It's something I'd be willing to do, I guess.  I have some
 history with the rc.foo files. :)

Tell me what I can do to help.  I'm willing to contribute, too.


virtually yours   82D1 9B9C 01DC 4FB4 D7B4  61BE 3F49 4F77 72DE DA76
Gerhard Sittig   true | mail -s "get gpg key" [EMAIL PROTECTED]
-- 
 If you don't understand or are scared by any of the above
 ask your parents or an adult to help you.


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

Re: new rc.network6 and rc.firewall6

[Mike Meyer]

Gerhard Sittig writes:
 On Wed, Oct 25, 2000 at 06:04 +0700, Alexey Dokuchaev wrote:
  Though I see your point, actually, many UNIX books, including
  some pretty old ones, refer to sending HUP signal as standard
  way of restarting/resetting daemons.
 Please tell the software authors about it, too. :)  Although
 there might be some form of convention, not everyone might follow
 it (some might not be able even if they tried without breaking
 established behaviour).  Wrapping those services will make
 starting, stopping, reloading, querying status and whatever you
 usually do to them easy and consistent for the user again.

Actually, the HUP convention has been around since at least v6. As
noted, it's still not universal. The pid file convention is more
recent, and less followed. Fixing that in a startup script is easy
(and what I recommend for string daemons that use the HUP convention,
so that it can be used for the script's stop command :-).

Now, which process do I need to create a pidfile for to get my ipfw
config reloaded?

mike



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

Re: new rc.network6 and rc.firewall6

[David O'Brien]

On Tue, Oct 24, 2000 at 02:56:07PM -0700, Jordan Hubbard wrote:
 So, who wants to do a proof-of-concept implementation for -current
 which integrates with our existing rc.conf mechanism?

I was going to if no one else did.

Who ever does it should coordinate with Luke M @ NetBSD.  He is willing
to make tweaks such that we could use as much of the NetBSD bits as
possible.  He really hopes we [BSD] can standardize on this interface.

-- 
-- David  ([EMAIL PROTECTED])
  GNU is Not Unix / Linux Is Not UniX


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

Re: new rc.network6 and rc.firewall6

[David O'Brien]

On Wed, Oct 25, 2000 at 08:14:01PM +0200, Gerhard Sittig wrote:
 but I don't see FreeBSD having this level of "rc lib" as NetBSD
 has in rc.subr

We would import the NetBSD rc.subr.

-- 
-- David  ([EMAIL PROTECTED])
  GNU is Not Unix / Linux Is Not UniX


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

Re: new rc.network6 and rc.firewall6

[David O'Brien]

On Tue, Oct 24, 2000 at 02:58:08PM -0700, Jordan Hubbard wrote:
 With the NetBSD stuff, this is not immediately obvious though I guess
 one could have a top level rc file with an explicit ordering similar to
 our various subdir Makefiles,

Nope.  All the /etc/rc.d/ files are scanned by `rcorder'.  `rcorder' then
creates a dependacy graph from information in each /etc/rc.d/ file.  A
walk of the graph is done to output the list of scripts in the order they
should run in.

To quote what you once wrote about `pib', the NetBSD implimentation is
"slicker than two eels screwing in a bucket of snot!" :-)

-- 
-- David  ([EMAIL PROTECTED])
  GNU is Not Unix / Linux Is Not UniX


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

Re: new rc.network6 and rc.firewall6

[Garrett Wollman]

Grrr !@#$^ Reply-To:...

On Wed, 25 Oct 2000 13:01:04 -0700, "David O'Brien" [EMAIL PROTECTED] said:

 Nope.  All the /etc/rc.d/ files are scanned by `rcorder'.  `rcorder' then
 creates a dependacy graph from information in each /etc/rc.d/ file.  A
 walk of the graph is done to output the list of scripts in the order they
 should run in.

Hmmm.  We already have a program (called `tsort') which does this
(i.e., a topological sort).  Does `rcorder' call `tsort' or does it
reinvent the wheel?

-GAWollman



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

Re: new rc.network6 and rc.firewall6

[David O'Brien]

On Wed, Oct 25, 2000 at 09:42:23AM +0200, Andrea Campi wrote:
 Maybe we could have a script to do the dependency check and "compile"
 everything in a single big file?

Luke already has this support in NetBSD 1.5 for those who demand it, but
its a secret. ;-)

-- 
-- David  ([EMAIL PROTECTED])
  GNU is Not Unix / Linux Is Not UniX


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

Re: new rc.network6 and rc.firewall6

[David O'Brien]

On Wed, Oct 25, 2000 at 04:04:13PM -0400, Garrett Wollman wrote:
 Hmmm.  We already have a program (called `tsort') which does this
 (i.e., a topological sort).  Does `rcorder' call `tsort' or does it
 reinvent the wheel?

UTSL

lynx ftp://ftp.netbsd.org/pub/NetBSD-current/src/sbin/rcorder/



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

Re: new rc.network6 and rc.firewall6

[Mike Meyer]

Gerhard Sittig writes:
 What's new is:
 - include the general config at the start (and yes, in every
   single script -- but this should be neglectable in terms of
   speed penalty and makes them work separately, too -- which is a
   real big gain!)

This isn't really new; it's been nagging me for a while. Also,
periodic.conf does this now.  I'm not convined it's negligible when
added up over dozens of scripts.  I'm planning on taking some
measurements to see how much this really costs. I believe I have a
solution if it turns out to be non-negligible.

 - maybe include (source) some common code like
   - determining pids belonging to program names
   - starting processes in an supervised or backgrounded or any
 other special way
   - have some printouts, error level summary, etc
 but I don't see FreeBSD having this level of "rc lib" as NetBSD
 has in rc.subr or even RedHat has in /etc/rc.d/functions(sp?).
 So only the sourced rc.conf (default and customized) remains.

Said solutions works shell functions as well.

 The real new part eating most of the time to implement is the
 shutdown path (which I understand to be somewhat absent in
 FreeBSD right now, "kill -TERM everything" seems to do the job
 right now).

Well, rc.shutdown has the appropriate loop processing in it for doing
this for the rc.d directories already. So the new part is the
per-system shutdown. That's where the shell subroutine library comes
in handy. Provide functions start/stop/reconfig that do the right
thing for the conventional single daemon subsystem like so (vertically
compressed to save space):

start() {
eval command="\$${name}_program \$${name}_flags"
command 
echo $!  /var/run/${name}.pid
echo -n " $name"
}

stop() {
kill -TERM /var/run/${name}.pid
echo -n " $name"
}

config() {
kill -HUP /var/run/${name}.pid
}

run()
eval check="\$${name}_enable"
case "${check}" in
[Yy][Ee][Ss]) run="yes" ;;
[Nn][Oo]) run="no" ;;
esac

case "$1" in
start) if [ "$run" = "yes" ]; then start(); fi ;;
stop) if [ "$run" = "yes" ]; then stop(); fi ;;
config) if [ "$run" = "yes" ]; then config(); fi ;;
*) echo "Usage: $0 [ start | stop | config ] $12 ;;
esac
}

Then simple daemons turn into:

#!/bin/sh
#
# PROVIDES: foobar
# REQUIRES: ...
# ...

name=foobar

. /etc/rc.setup

run

Breaking out the seperate functions allows you to change just part of
it easily. For example, if the daemon creates a pid, or the flags to
it, you'd do:

#!/bin/sh
# ...

name=smartbar

. /etc/rc.setup

start() {
$foobar_program $foobar_flags 
echo -n " foobar"
}

run

Some things are hairy enough to require doing everything over, and
there is probably a better way to organize the subroutines, but that's
the general idea.

The next step is to get ports authors to start using /etc/rc.setup or
whatever it gets called :-).

mike


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

Re: new rc.network6 and rc.firewall6

[Garrett Wollman]

Grrr !@#%$^ Reply-To: header

On Wed, 25 Oct 2000 13:13:53 -0700, "David O'Brien" [EMAIL PROTECTED] said:

 (i.e., a topological sort).  Does `rcorder' call `tsort' or does it
 reinvent the wheel?

 UTSL

You could have simply answered the question.  For the benefit of
everyone else: yes, it reinvents the wheel.

-GAWollman



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

Re: entropy reseeding is totally broken

[Wesley Morgan]

I'm not knocking anyone or any code, especially considering this IS
-current... BUT... I don't need to read the code to know that I am seeing
the same fortunes on first login after reboot more often than I can
attribute to random chance. Maybe nanotime is being harvested, but it
seems that there is a time lag between system startup and reaching a state
of "true pseudo-entropy". Also, every reboot has entropy caching failing
to work. I don't know if this is a product of the broken reseeding or
what, because the /etc/rc files seem to be fine.

On Wed, 25 Oct 2000, Mark Murray wrote:

  2) Reseeding state may not preserve across the boot due to various reasons
  like panic, etc. Since _time_ is ignored, all other data /etc/rc tries to
  collect now can be non-random _easily_!
  
  Unless _time_ will be used, /dev/random is plain unusable for production
  usage.
 
 Andrey, read the code; nanotime is all over the harvested entropy.
 
 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
 

-- 
   _ __ ___   ___ ___ ___
  Wesley N Morgan   _ __ ___ | _ ) __|   \
  [EMAIL PROTECTED]  _ __ | _ \._ \ |) |
  FreeBSD: The Power To Serve  _ |___/___/___/
  6bone: 3ffe:1ce3:7::b4ff:fe53:c297
Hi! I'm a .signature virus! Copy me into your ~/.signature to help me spread!



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

Re: new rc.network6 and rc.firewall6

[Jordan Hubbard]

 I was going to if no one else did.
 
 Who ever does it should coordinate with Luke M @ NetBSD.  He is willing
 to make tweaks such that we could use as much of the NetBSD bits as
 possible.  He really hopes we [BSD] can standardize on this interface.

Well, it sounds like David is already working with Luke on this
so why don't we just tag him as "it" and get past the deadlock
on this one. :)

- Jordan


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

Re: entropy reseeding is totally broken

[Mark Murray]

 I'm not knocking anyone or any code, especially considering this IS
 -current... BUT... I don't need to read the code to know that I am seeing
 the same fortunes on first login after reboot more often than I can
 attribute to random chance. Maybe nanotime is being harvested, but it
 seems that there is a time lag between system startup and reaching a state
 of "true pseudo-entropy". Also, every reboot has entropy caching failing
 to work. I don't know if this is a product of the broken reseeding or
 what, because the /etc/rc files seem to be fine.

I am not seeing this, and I am unable to reproduce it.

i terefore need better info than "it is so" to do anything about it.

Please get a complete log of the boot process (put a set -x in /etc/rc
while you are about it) and get that over to me.

M

 On Wed, 25 Oct 2000, Mark Murray wrote:
 
   2) Reseeding state may not preserve across the boot due to various reason
s
   like panic, etc. Since _time_ is ignored, all other data /etc/rc tries to
   collect now can be non-random _easily_!
   
   Unless _time_ will be used, /dev/random is plain unusable for production
   usage.
  
  Andrey, read the code; nanotime is all over the harvested entropy.
  
  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
  
 
 -- 
_ __ ___   ___ ___ ___
   Wesley N Morgan   _ __ ___ | _ ) __|   \
   [EMAIL PROTECTED]  _ __ | _ \._ \ |) |
   FreeBSD: The Power To Serve  _ |___/___/___/
   6bone: 3ffe:1ce3:7::b4ff:fe53:c297
 Hi! I'm a .signature virus! Copy me into your ~/.signature to help me spread!
 
 
--
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: divert as module?

[Terry Lambert]

 Stop right here. If you didn't compile IPDIVERT in the kernel,
 the hooks aren't in the tcp/ip stack and you're screwed.
 
 Figuring out a way to fix this is on my TODO list, though I don't
 have any ideas that don't cost a performance hit for non-DIVERT
 users.

The LEASE stuff has a similar problem, but it eats the overhead
anyway, but screws up a number of details in a couple of places,
making it pretty useless to load NFS as a module, at least for
serving.

There are really several ways to do this:

o   Jump table with fixup on first call

- This is the least overhead, since each caller is
  fixed up once; the bad news is: no unload.

o   Another way is to do what the NFS LEASE code does;
this adds a pointer dereference and compare to zero
with jump

- This is more overhead, as you say; the real pain
  here is the jump, which wouldn't be necessary, if
  it were possible to tell the compiler "I expect
  this compare to succeed most of the time" or "I
  expect this compare to fail most of the time"
  using a "#pragma"; if you could do that, the
  compiler could change branch order generation by
  tacking a hint onto the quad tree, and reordering
  (or not reordering) it.  You can get the same
  effect by placing the default path inside the
  if test, but then you get a branch instruction,
  which is not much better.

o   A sneaky way to do this is to put the diversion into
the failure path.  This makes divert very expensive,
comparatively (in terms of code path), and adds some
constraints to how it must be used, but makes it so
that you only ever divert packets you would otherwise
throw away

- That said, there are server things in the IPFW code
  that could be diked out as "more useless than divert",
  forceful rejection being one of them, since everyone
  who is a bad guy ignores it anyway, so the argument
  would be "what's important?", since everyone's choice
  for success and failure code path would be different.

- On the other hand, if it's considered so heavy that
  it already has #ifdef's for it, the divert code is
  a good candidate for failure code path.

My personal vote would be fore LEASE, if the reason is that the
code is large, not because it is slow, and failure path, if it's
because the code is slow, not because it is large.


Terry Lambert
[EMAIL PROTECTED]
---
Any opinions in this posting are my own and not those of my present
or previous employers.


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

Re: new rc.network6 and rc.firewall6

[Terry Lambert]

  (i.e., a topological sort).  Does `rcorder' call `tsort' or does it
  reinvent the wheel?
 
  UTSL
 
 You could have simply answered the question.  For the benefit of
 everyone else: yes, it reinvents the wheel.

I personally don't have a problem with this; tsort should be
a library routine referenced by both tsort(1) and rcorder(8),
of course, but the way tsort(1) works, there is really no
easy way to use it to do the job in any reasonable amount of
time.

As far as wheel reinvention goes, we should add gcc, ld, and
make to the list of programs reinventing the tsort wheel...
kinda calls out for a library routine; wait, I already said
that once... 8-).


Terry Lambert
[EMAIL PROTECTED]
---
Any opinions in this posting are my own and not those of my present
or previous employers.


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

Re: sysinstall's console keymap menu

[Jose M. Alcaide]

Jordan Hubbard wrote:
 
  OK, if I understood correctly, is this patch reasonable at this time?
 
 Yes, this looks much better!
 

Jordan, what do you think about making the keymap selection the first
step of the "Standard" installation?

Cheers,
-- JMA
** Jose M. Alcaide  //  [EMAIL PROTECTED]  //  [EMAIL PROTECTED] **
** "Beware of Programmers who carry screwdrivers" --  Leonard Brandwein **


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

Watching DVD on FreeBSD

[dmitry]

I am sorry this is a little off the topic:

1) Has anyone been able to get css-auth patch to work on current/stable? (And 
was able to watch DVD movies with sound and color at 720x480)

2) Can we use some of the LiViD tools? 

3) If someone got it to work before, could you give some points on how to get 
it to work?

4) On http://www.opendvd.org there is a link to FreeBSD DVD HowTO. The links 
that follow from that page are broken: ** What is Nist? **

Thank you,

-dmitry






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

Re: new rc.network6 and rc.firewall6

[Brian O'Shea]

On Wed, Oct 25, 2000 at 06:04:43AM +0700, Alexey Dokuchaev wrote:
 On Tue, 24 Oct 2000, David O'Brien wrote:
 
  On Tue, Oct 24, 2000 at 04:23:40PM +0700, Alexey Dokuchaev wrote:
   Why can't I simply write kill -1 `cat /var/run/sendmail.pid`?
  
  What about deamons that don't understand `kill -HUP'?  Sendmail didn't
  until very reciently.  ``/etc/rc.d/some-deamon restart'' does the right
  thing reguardless how involved that might be.
 
 Though I see your point, actually, many UNIX books, including some pretty
 old ones, refer to sending HUP signal as standard way of
 restarting/resetting daemons.

Using the `kill -HUP` method, how do you deal with the dependency
issues that people have been mentioning in this thread?

-brian

-- 
Brian O'Shea
[EMAIL PROTECTED]


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

Re: Watching DVD on FreeBSD

[Brian Reichert]

On Wed, Oct 25, 2000 at 10:51:33AM -0700, dmitry wrote:
 I am sorry this is a little off the topic:
 
 1) Has anyone been able to get css-auth patch to work on current/stable? (And 
 was able to watch DVD movies with sound and color at 720x480)

Yes, I have.  I can't get the audio to work, but have been able to
'play' vob files.

Audio is played with 'ac3dec', which built easily enough.  It
seemingly can find audio (doesn't complain, at least) but wedged
the hell out of my soundcard, I had to powercycle to get that
back...

 2) Can we use some of the LiViD tools? 
 
 3) If someone got it to work before, could you give some points on how to get 
 it to work?
 
 4) On http://www.opendvd.org there is a link to FreeBSD DVD HowTO. The links 
 that follow from that page are broken: ** What is Nist? **

Don't use nist.  Look for 'DecVOB'.

I have source/binaries that work under 4.1-R.

 Thank you,

Good luck.  Let me know if you need specifics...

 -dmitry

-- 
Brian 'you Bastard' Reichert[EMAIL PROTECTED]
37 Crystal Ave. #303Daytime number: (603) 434-6842
Derry NH 03038-1713 USA Intel architecture: the left-hand path


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

src/release/Makefile patch so cdrom will autoboot

[John W. De Boskey]

Don't want to step on toes.. Someone please commit. I believe
we need to 'load /kernel' no matter what... it's the
'read' that's in question. Allows a cdrom to autoboot.

patch also located at ~jwd/src/src/release/Makefile.patch so you
don't have to cut'n'paste.

-John

Index: Makefile
===
RCS file: /home/ncvs/src/release/Makefile,v
retrieving revision 1.576
diff -u -r1.576 Makefile
--- Makefile2000/10/24 19:05:39 1.576
+++ Makefile2000/10/25 23:01:44
@@ -827,8 +827,8 @@
${RD}/kernels/BOOTMFS.${FSIMAGE}.hints  \
${RD}/image.${FSIMAGE}/boot/device.hints  \
  echo "include /boot/device.hints"  ${RD}/image.${FSIMAGE}/boot/loader.rc
-.if !defined(FDSIZE) || ${FDSIZE} != "BIG"
@echo "load /kernel"  ${RD}/image.${FSIMAGE}/boot/loader.rc
+.if !defined(FDSIZE) || ${FDSIZE} != "BIG"
@echo "echo \\007\\007"  ${RD}/image.${FSIMAGE}/boot/loader.rc
@echo "echo Please insert MFS root floppy and press enter:"  
${RD}/image.${FSIMAGE}/boot/loader.rc
@echo "read"  ${RD}/image.${FSIMAGE}/boot/loader.rc


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

Re: entropy reseeding is totally broken

[John W. De Boskey]

Also, what rev of /etc/rc do you have installed?

-john

- Mark Murray's Original Message -
  I'm not knocking anyone or any code, especially considering this IS
  -current... BUT... I don't need to read the code to know that I am seeing
  the same fortunes on first login after reboot more often than I can
  attribute to random chance. Maybe nanotime is being harvested, but it
  seems that there is a time lag between system startup and reaching a state
  of "true pseudo-entropy". Also, every reboot has entropy caching failing
  to work. I don't know if this is a product of the broken reseeding or
  what, because the /etc/rc files seem to be fine.
 
 I am not seeing this, and I am unable to reproduce it.
 
 i terefore need better info than "it is so" to do anything about it.
 
 Please get a complete log of the boot process (put a set -x in /etc/rc
 while you are about it) and get that over to me.
 
 M
 


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

Re: -current hangs during boot (UPDATING entry)

[John W. De Boskey]

Thanks for the updates. A few questions below.

-John

- Mark Hittinger's Original Message -
 
 It does look like an updating entry is needed for this badly.
 
 I did the following things, some of which may not be needed, and now my 
 -current boxes boot OK.
 
 1.  update MAKEDEV from /usr/src/etc, run MAKEDEV all
 
 2.  update /etc/rc /etc/rc.* /etc/defaults/rc.conf from /usr/src/etc
 
 3.  add random_load="YES" to /boot/loader.conf

or add the random device to the kernel config file.

 4.  update /etc/login.conf from /usr/src/etc

I don't remember having to do this... was there a
specific reason?

 5.  do a "shutdown -r now" which creates the entropy file and reboots
 
 Now the system boot does not hang at the ldconfig spots.  It does look like
 there is a lot to do to get back on course, enough to justify adding to
 UPDATING.
 
 Later
 
 Mark Hittinger
 Earthlink
 [EMAIL PROTECTED]
 


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

Re: entropy reseeding is totally broken

[Wesley Morgan]

Ok, I rebooted once and the entropy caching did not work. Changed
entropy_file to point to /var/db/entropy, rebooted. Did not
work. Commented out the entropy_file setting and rebooted... And it
worked. Rebooted 5 times, worked every time. Laptop is working
now. cvsup'd my desktop, ran mergemaster and it worked for 3 reboots... 

Now, the problem I am seeing is that not only do I get the same fortunes
between reboots, but it is _always_ the same one:

"Be ALERT (the world needs more lerts"

has shown up first nearly every time for the past week. Waiting a few
minutes to log in has no effect... Still the same one. Now I'm no expert
on randomness and the like, but surely this can't be very random.

I'll be eating my words tonight, but I swear it wasn't working for me
:) (and yes i had the latest rc files).

On Wed, 25 Oct 2000, Mark Murray wrote:

 I am not seeing this, and I am unable to reproduce it.
 
 i terefore need better info than "it is so" to do anything about it.
 
 Please get a complete log of the boot process (put a set -x in /etc/rc
 while you are about it) and get that over to me.

-- 
   _ __ ___   ___ ___ ___
  Wesley N Morgan   _ __ ___ | _ ) __|   \
  [EMAIL PROTECTED]  _ __ | _ \._ \ |) |
  FreeBSD: The Power To Serve  _ |___/___/___/
  6bone: 3ffe:1ce3:7::b4ff:fe53:c297
Hi! I'm a .signature virus! Copy me into your ~/.signature to help me spread!



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

Re: strange problem of PPPoE + NAT

[Josh Tiefenbach]

 the other problem i had after switch that system to -current
 is that after a random time, the connection will frzzed.
 the routing table still exist, connection is still up.
 just cant connect to anywhere outside the network. no error
 or anything been loged in ppp.log.

Interestingly enough, I've been having the same problem with PPPoE ever since
it hit the tree 'bout a year ago. It happens infrequently enough that I tend
to blame my provider, rather than ppp.

When it happens, killing ppp and restarting it is usually enough. 

I have no idea what causes it.

  module_register: module netgraph already exists!
  linker_file_sysinit "netgraph.ko" failed to register! 17

Just a guess, but thats probably because you're trying to kldload netgraph.ko,
but have already compiled it into your kernel with options NETGRAPH

josh

-- 
"Watching those 2 guys [Bush and Gore] debate is like watching Ben Stein read
'The Story of O'" -- Dennis Miller


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

Re: entropy reseeding is totally broken

[Mark Murray]

 Ok, I rebooted once and the entropy caching did not work. Changed
 entropy_file to point to /var/db/entropy, rebooted. Did not
 work. Commented out the entropy_file setting and rebooted... And it
 worked. Rebooted 5 times, worked every time. Laptop is working
 now. cvsup'd my desktop, ran mergemaster and it worked for 3 reboots... 

I need logs.

What is "did not work"?

What is "it worked"?

What was the line you commented out?

What are the other things that your eye/brain are filtering out that I need to see in 
copious detail?

M

 Now, the problem I am seeing is that not only do I get the same fortunes
 between reboots, but it is _always_ the same one:
 
 "Be ALERT (the world needs more lerts"
 
 has shown up first nearly every time for the past week. Waiting a few
 minutes to log in has no effect... Still the same one. Now I'm no expert
 on randomness and the like, but surely this can't be very random.
 
 I'll be eating my words tonight, but I swear it wasn't working for me
 :) (and yes i had the latest rc files).
 
 On Wed, 25 Oct 2000, Mark Murray wrote:
 
  I am not seeing this, and I am unable to reproduce it.
  
  i terefore need better info than "it is so" to do anything about it.
  
  Please get a complete log of the boot process (put a set -x in /etc/rc
  while you are about it) and get that over to me.
 
 -- 
_ __ ___   ___ ___ ___
   Wesley N Morgan   _ __ ___ | _ ) __|   \
   [EMAIL PROTECTED]  _ __ | _ \._ \ |) |
   FreeBSD: The Power To Serve  _ |___/___/___/
   6bone: 3ffe:1ce3:7::b4ff:fe53:c297
 Hi! I'm a .signature virus! Copy me into your ~/.signature to help me spread!
 
 
--
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

ftp vs. nfs install times

[John W. De Boskey]

Hi,

   I've tested last nights make release built
install via both ftp and nfs and am seeing
some rather strange results timeing wise:

   A full install (ie: select ALL) w/ ports.

   NFS:  about 18 minutes. (ave. about 1000KB/sec)

   FTP:  about 70 minutes. (ave. about 45KB/sec)

   on the same box after the install, I can
ftp to the server and mget all the files in
just a few moments. ie: The snap server I'm
using isn't the problem.

   Any ideas of what the best way to debug this
from the holographic shell might be?  Some tools
are available, others are available but don't
work (like top). While this is happenning, the
idle process is accumulating time almost lockstep
with walltime.

   Ideas welcome.

John


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

Re: src/release/Makefile patch so cdrom will autoboot

[Mike Smith]

 Don't want to step on toes.. Someone please commit. I believe
 we need to 'load /kernel' no matter what... it's the
 'read' that's in question. Allows a cdrom to autoboot.

Actually, the kernel should be autoloaded anyway, but you appear to be 
right here.

 patch also located at ~jwd/src/src/release/Makefile.patch so you
 don't have to cut'n'paste.

Unless someone has a good reason not to, I think you should just commit 
it.

-- 
... every activity meets with opposition, everyone who acts has his
rivals and unfortunately opponents also.  But not because people want
to be opponents, rather because the tasks and relationships force
people to take different points of view.  [Dr. Fritz Todt]
   V I C T O R Y   N O T   V E N G E A N C E




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

Re: strange problem of PPPoE + NAT

[Idea Receiver]

On Wed, 25 Oct 2000, Josh Tiefenbach wrote:
 Interestingly enough, I've been having the same problem with PPPoE ever since
 it hit the tree 'bout a year ago. It happens infrequently enough that I tend
 to blame my provider, rather than ppp.
 
 When it happens, killing ppp and restarting it is usually enough. 
 
 I have no idea what causes it.
 

kill ppp and restart it doesnt help at all.
will it make any different if i change a network card?
it happen so frequently, it is impossible to run a stable
server with PPPoE!


   module_register: module netgraph already exists!
   linker_file_sysinit "netgraph.ko" failed to register! 17
 
 Just a guess, but thats probably because you're trying to kldload netgraph.ko,
 but have already compiled it into your kernel with options NETGRAPH

nope. i didnt kldload netgraph.ko at all.



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

Re: strange problem of PPPoE + NAT

[Josh Tiefenbach]

  When it happens, killing ppp and restarting it is usually enough. 
  
  I have no idea what causes it.
  
 
 kill ppp and restart it doesnt help at all.
 will it make any different if i change a network card?

I dont think so. There are times when I cant do a simple kill/restart, and I
have to physically shut off the modem, cycle power on my server, and bring it
up again.

While this *may* be a function of the PPPoE code, I'm inclined to blame my
provider, if only because they've had issues in the past. I presently lack the
resources to adequately debug the issue.

 it happen so frequently, it is impossible to run a stable
 server with PPPoE!

Might I suggest you drop a note over on freebsd-net? Perhaps you'll rustle up
some more support there.

josh

-- 
"Watching those 2 guys [Bush and Gore] debate is like watching Ben Stein read
'The Story of O'" -- Dennis Miller


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

Re: entropy reseeding is totally broken

[Doug Barton]

Wesley Morgan wrote:
 
 I'm not knocking anyone or any code, especially considering this IS
 -current... BUT... I don't need to read the code to know that I am seeing
 the same fortunes on first login after reboot more often than I can
 attribute to random chance. Maybe nanotime is being harvested, but it
 seems that there is a time lag between system startup and reaching a state
 of "true pseudo-entropy". Also, every reboot has entropy caching failing
 to work. I don't know if this is a product of the broken reseeding or
 what, because the /etc/rc files seem to be fine.

How exactly are you rebooting? If you're using the 'reboot' command,
that explains why entropy reseeding is not working. As has been
discussed several times on -current, you only run rc.shutdown if you use
another method, like 'shutdown -r now', 'init 6', or even the trust
three-finger salute. 

Good luck,

Doug
-- 
"The dead cannot be seduced."
- Kai, "Lexx"

Do YOU Yahoo!?


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

Re: Intel Etherexpress support?

[Matthew N. Dodd]

On Tue, 24 Oct 2000, Glendon Gross wrote:
 Is it possible to use the old Intel EtherExpress-16 cards with FreeBSD?

The driver was broken a while back and I'm right in the middle of trying
to fix it.  I've actually given up on the FreeBSD driver and ported the
NetBSD driver with mixed success.  I've got 3c503 boards working great but
the EE16s are really nasty and I'm still tracking down a few issues.

You might try the attached patch against sys/dev/ie/if_ie.c though as I'm
not quite ready to commit what I've got.

-- 
| Matthew N. Dodd  | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/NetBSD  |
| [EMAIL PROTECTED] |   2 x '84 Volvo 245DL| ix86,sparc,pmax |
| http://www.jurai.net/~winter | This Space For Rent  | ISO8802.5 4ever |


Index: if_ie.c
===
RCS file: /cvs/src/sys/dev/ie/if_ie.c,v
retrieving revision 1.77
diff -u -r1.77 if_ie.c
--- if_ie.c 2000/10/15 14:18:16 1.77
+++ if_ie.c 2000/10/18 17:40:54
@@ -216,8 +216,12 @@
  * This tells the autoconf code how to set us up.
  */
 struct isa_driver iedriver = {
-   ieprobe, ieattach, "ie",
+   INTR_TYPE_NET,
+   ieprobe,
+   ieattach,
+   "ie",
 };
+COMPAT_ISA_DRIVER(ie, iedriver);
 
 enum ie_hardware {
IE_STARLAN10,
@@ -2069,6 +2073,7 @@
}
ie-arpcom.ac_if.if_flags |= IFF_RUNNING;   /* tell higher levels
 * we're here */
+   ie-arpcom.ac_if.if_flags = ~IFF_OACTIVE;
start_receiver(unit);
 
return;
@@ -2089,6 +2094,7 @@
 
switch (command) {
 case SIOCSIFADDR:
+   ieinit(ifp-if_softc);
 case SIOCGIFADDR:
case SIOCSIFMTU:
error = ether_ioctl(ifp, command, data);

Re: ftp vs. nfs install times

[John Hay]

 Hi,
 
I've tested last nights make release built
 install via both ftp and nfs and am seeing
 some rather strange results timeing wise:
 
A full install (ie: select ALL) w/ ports.
 
NFS:  about 18 minutes. (ave. about 1000KB/sec)
 
FTP:  about 70 minutes. (ave. about 45KB/sec)
 
on the same box after the install, I can
 ftp to the server and mget all the files in
 just a few moments. ie: The snap server I'm
 using isn't the problem.
 

Maybe just as a datapoint. My -current snap building machine is running
a kernel of Oct 24 and I noticed this morning that it is taking a very
long time to scp the snap to internat. Normally it takes a few minutes
but it is now more than a hour and it isn't halfway yet. The machine
is almost totally idle. The machine is running an SMP kernel if it
matters.

John
-- 
John Hay -- [EMAIL PROTECTED]


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

call for testers: nsswitch + dynamic linking

[Jacques A. Vidrine]

[Please follow-up to only one list]

Hello,

I need more testers for the following!

nsswitch extends the C library so that arbitrary sources may be
consulted by database routines such as getpwent, gethostbyname, and so
on.  This implementation was based on NetBSD's implementation.  I have
enhanced it to make the interfaces thread safe, and to provide support
for dynamically loaded nsswitch modules.

Patches for 4-STABLE and 5-CURRENT are at:
  http://www.nectar.com/freebsd/nsswitch.  
Also available there are patches for PADL.COM's nss_ldap so that it may
be used with FreeBSD.

Incidentally this also adds reentrant versions of common routines such
as getpwnam_r.  Note that routines that eventually call the resolver are
only as thread safe as the resolver -- i.e. not really.

Please contact me with any comments/bugs/patches.

Cheers,
-- 
Jacques Vidrine / [EMAIL PROTECTED] / [EMAIL PROTECTED] / [EMAIL PROTECTED]


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