> other than walking the sysctl tree regularly looking for changes
Use a similar hack: map the sysctl tree to the filesystem (ala kernfs) and
then stat the directory nodes.
John
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Garrett Wollman speaks the truth when he says:
> > I can't quite figure why they stuck the word "open" in there, because it
> > couldn't possibly be more open than RIP.
>
> Because a previous link-state (aka shortest-path-first) routing
> protocol had been deployed which was not.
I can't believe
> No I have to use two vi sessions (or one ,more' and one ,vi' session)
> in two different (!) windows (especially after a new installation,
Or type "vi /etc/rc.conf /etc/rc.conf.site" and then hit ":N" to split
the screen into two sessions, one in /etc/rc.conf and one in /etc/rc.conf.site.
Use ^W
> Well, I need to learn a little about programming first, so where do you
> reccomend I begin learning?
> E-Mail: William Woods
> FreeBSD 4.0 -Current
If you don't know about programming, then you just shouldn't be running
-current. Step back to 2.2.8R and enjoy the Floppy Tape support there.
J
Will you be keeping the last snapshot of 2.2.X around when it returns?
On another note, does curr...@freebsd.org now correspond to 4.X ("-current")
discussions, while sta...@freebsd.org now correspond to 3.X ("-stable")?
If so, is there / will there be a separate forum for 2.X ("-stable in a
past
