Sean Eric Fagan wrote about the security implications of making the bpf device
the default in GENERIC etc.
> I'm sorry, but that's a complete non-issue:
>
> 1. /dev/bpf0 is mode 400, root.wheel -- to read it, you need to break root.
> 2. If you can break root, you can rebuild a kernel with BP
Is it about FreeBSD (http://www.roms.cx)??
"TANTOWEL? THE SELF-TANNING TOWELETTE
LOOK GOOD? FEEL GOOD?
STAY HEALTHY !!! "
m...@ratatosk.assetfactory.com wrote:
> http://www.roms.cx - new freebsd news website, updated daily.
>
> To Unsubscribe:
Sean Eric Fagan writes :
>
> 1. /dev/bpf0 is mode 400, root.wheel -- to read it, you need to break root.
> 2. If you can break root, you can rebuild a kernel with BPF *anyway*.
Not quite - bpf is potentially dangerous where a sysadmin is inexperienced.
On a system with a generic kernel and no s
I also have this problem
Randy Bush wrote:
> 4.0 -current
>
> touch?? opt_spx_hack.h
> cc -O -pipe -DCOMPAT_IBCS2? -DKERNEL -Wall -Wredundant-decls -Wnested-externs
> -Wstrict-prototypes? -Wmissing-prototypes -Wpointer-arith -Winline
> -Wcast-qual? -fformat-extensions -ansi -DKLD_MODULE -nostdi
According to Steve Kargl:
> So, we'll import a pop server, apache, g77, ad nauseam
> to increase the credibility of FreeBSD as a workstation OS.
No but if you want to install from a cable modem (they're becoming quite
common these days, even in France), you _need_ it. Period.
I'm as much anti-blo
In article <19990209091330.18608.qmail.kithrup.freebsd.curr...@rucus.ru.ac.za>
you write:
>I would still
>be very reticent to see BPF in a generic kernel because of the security
>implications.
I'm sorry, but that's a complete non-issue:
1. /dev/bpf0 is mode 400, root.wheel -- to read it, you
> Daniel O'Connor wrote:
> >
> > On 09-Feb-99 Steve Kargl wrote:
> > > > And just WHERE is the package?? Often on an NFS or FTP server, no??
> > > > And just HOW am I to communicate with that NFS or FTP server??
> > > Drop FreeBSD cd-rom into tray (or caddy).
> > > mount_cd9660 /dev/cd0a /mnt
>
> - DHCP-WIDE requires you to have bpf configured into your kernel
> for a GENERIC kernel, this is VERY BAD - is there a more elegant
> way to handle this? I certainly would not like to see the
> generic kernel in the distribution going out into the world with
> bpf enabled.
That's not "
>
> On 09-Feb-99 Charlie ROOT wrote:
> > Further, the assertion that it is easier to configure the WIDE client is
> > WRONG. The ISC CLIENT requires NO configuration. I don't see how anything
> > can be simpler. :-)
> Hmmm.. This annoyed me actually..
> There is NO config file which means it
Sean Eric Fagan writes :
> There's really no other way to do it: you need the ability to grab packets
> that come from an unidentified machine, which doesn't have an IP address. You
> could write some other method of doing this -- and then put it into every
> single ethernet (et al) device driver
On Tue, 9 Feb 1999, Daniel O'Connor wrote:
>
> On 09-Feb-99 Charlie ROOT wrote:
> > Further, the assertion that it is easier to configure the WIDE client is
> > WRONG. The ISC CLIENT requires NO configuration. I don't see how anything
> > can be simpler. :-)
> Hmmm.. This annoyed me actual
> > That argument won't work with Media-One, Roadrunner, RCN, etc who
> > just simply *DO* *NOT* *SUPPORT* *STATIC* *IP* *ASSIGNMENTS*. How
> > can we make this any clearer to you? Its fine to say `I don't want
> > to see DHCP in the base system' when you have the choice of getting
> > a static IP.
Steve Kargl wrote in message ID
<199902090634.waa65...@troutmask.apl.washington.edu>:
> Then, *BUY* the cd-rom and support the FreeBSD project.
All that would happen would be that ppl will see `oh, no DHCP support on
install. Better go with that linux dist which supports it' and we lose
support.
On 09-Feb-99 Sean Eric Fagan wrote:
> >There is NO config file which means its damn annoying for you to tweak how
> >it works..
> Would you please settle on a set of misinformation and stick with it?
Argh!
Damn I got WIDE and ISC confused.. AGAIN..
My aplogies..
OK, lets do ISC instead of WIDE
In article <19990209082922.17759.qmail.kithrup.freebsd.curr...@rucus.ru.ac.za>
you write:
>- DHCP-WIDE requires you to have bpf configured into your kernel
> for a GENERIC kernel, this is VERY BAD - is there a more elegant
> way to handle this? I certainly would not like to see the
> generic
On 09-Feb-99 Steve Kargl wrote:
> > Or I'd like to play with FreeBSD, but I'd rather not fork out US$30 for
> > something I
> > haven't tested.
> Cheapbytes.
Argument still holds..
---
Daniel O'Connor software and network engineer
for Genesis Software - http://www.gsoft.com.au
"The nice thing
In article
you write:
>Hmmm.. This annoyed me actually..
>There is NO config file which means its damn annoying for you to tweak how it
>works..
Would you please settle on a set of misinformation and stick with it?
isc-dhcp's client *does* have a very extensive configuration file. Same
parse
Daniel O'Connor wrote:
>
> On 09-Feb-99 Steve Kargl wrote:
> > > And just WHERE is the package?? Often on an NFS or FTP server, no??
> > > And just HOW am I to communicate with that NFS or FTP server??
> > Drop FreeBSD cd-rom into tray (or caddy).
> > mount_cd9660 /dev/cd0a /mnt
> > pkg_add dh
Steve Kargl wrote:
> David's original email said he was going to commit without giving
> a justification. I call it bloat, then the justifications pour in.
> I'm now convinced it may be a good thing with a security audit.
>
> However, if every committer starting to push his (pet) software
> as c
Gary Palmer wrote:
> Steve Kargl wrote in message ID
> <199902090603.waa65...@troutmask.apl.washington.edu>:
> > I do live in a dhcp world, but our net admins appreciate
> > the fact my machines are up 7/24 and serve my research group,
> > so they have given me a fixed ip.
>
> That argument won't
John Birrell wrote:
> Steve Kargl wrote:
> > David O'Brien wrote:
> > > > These should be left has ports.
> > >
> > > Explain how I am to install FreeBSD at my campus when DHCP has been
> > > mandated. Many univ. are moving in this direction.
> > >
> >
> > Maybe, support WC by purchasing the c
Sean Eric Fagan writes :
> In article
> <19990209074440.15845.qmail.kithrup.freebsd.curr...@rucus.ru.ac.za> you write:
> >Is DHCP core functionality?
>
> As much as an editor and PPP are, yes -- without it, some people simply
> *cannot* get on the net.
Your point is valid.
Before it goes in, the
Gary Palmer wrote:
> Steve Kargl wrote in message ID
> <199902090600.waa65...@troutmask.apl.washington.edu>:
> > Drop FreeBSD cd-rom into tray (or caddy).
> > mount_cd9660 /dev/cd0a /mnt
> > pkg_add dhcp
> > umount /mnt
>
[watch the long lines]
> So you are suggesting we no longer supporting FTP
On 09-Feb-99 Charlie ROOT wrote:
> Further, the assertion that it is easier to configure the WIDE client is
> WRONG. The ISC CLIENT requires NO configuration. I don't see how anything
> can be simpler. :-)
Hmmm.. This annoyed me actually..
There is NO config file which means its damn annoyin
I am glad to see some SOME version of the dhcp client included in base
floppies.
However, I must take exception to David's choice for any purpose other
than single floppy situations.
Although it is somewhat larger, the ISC dhcp2 client has significantly
more flexability WRT options beyond the bar
Remember that the client, relay, and server are all independent items.
Each MUST meet the same RFC specification.
On Tue, 9 Feb 1999, Andreas Braukmann wrote:
> On Mon, Feb 08, 1999 at 02:28:20PM -0800, David O'Brien wrote:
> > I am planning on adding the Wide-DHCP client to src/contrib/ and
> I
Wrong! The dhcp client is ESSENTIAL to boot floppies for modern use.
As for "bloat", one man's bloat is another's essential material :-(
On Mon, 8 Feb 1999, Steve Kargl wrote:
> Joe Abley wrote:
> > On Mon, Feb 08, 1999 at 02:28:20PM -0800, David O'Brien wrote:
> > > I am planning on adding the W
Steve Kargl wrote:
> David O'Brien wrote:
> > > These should be left has ports.
> >
> > Explain how I am to install FreeBSD at my campus when DHCP has been
> > mandated. Many univ. are moving in this direction.
> >
>
> Maybe, support WC by purchasing the cd-rom?
>
> Convince your University t
Steve Kargl wrote in message ID
<199902090603.waa65...@troutmask.apl.washington.edu>:
> I do live in a dhcp world, but our net admins appreciate
> the fact my machines are up 7/24 and serve my research group,
> so they have given me a fixed ip.
That argument won't work with Media-One, Roadrunner,
> David O'Brien wrote:
> > > These should be left has ports.
> >
> > Explain how I am to install FreeBSD at my campus when DHCP has been
> > mandated. Many univ. are moving in this direction.
> >
>
> Maybe, support WC by purchasing the cd-rom?
>
> Convince your University to get a large quant
Steve Kargl wrote in message ID
<199902090600.waa65...@troutmask.apl.washington.edu>:
> Drop FreeBSD cd-rom into tray (or caddy).
> mount_cd9660 /dev/cd0a /mnt
> pkg_add dhcp
> umount /mnt
So you are suggesting we no longer supporting FTP installs? Do you realise
what impact that would have? I gu
David O'Brien wrote:
> > These should be left has ports.
>
> Explain how I am to install FreeBSD at my campus when DHCP has been
> mandated. Many univ. are moving in this direction.
>
Maybe, support WC by purchasing the cd-rom?
Convince your University to get a large quantity of cd-roms
from
On 09-Feb-99 Steve Kargl wrote:
> > And just WHERE is the package?? Often on an NFS or FTP server, no??
> > And just HOW am I to communicate with that NFS or FTP server??
> Drop FreeBSD cd-rom into tray (or caddy).
> mount_cd9660 /dev/cd0a /mnt
> pkg_add dhcp
> umount /mnt
Excuse me sir.. I a
David O'Brien wrote:
> > So, we'll import a pop server, apache, g77, ad nauseam
> > to increase the credibility of FreeBSD as a workstation OS.
>
> NO. Again, the problem is boot strapping. If you lived in a DHCP world
> (and not in control of it) you would understand.
>
I do live in a dhcp w
David O'Brien wrote:
> > Make sysinstall be able to pkg_add? We do something similar to that
>
> And just WHERE is the package?? Often on an NFS or FTP server, no??
> And just HOW am I to communicate with that NFS or FTP server??
>
Drop FreeBSD cd-rom into tray (or caddy).
mount_cd9660 /dev/cd
In article <19990209074440.15845.qmail.kithrup.freebsd.curr...@rucus.ru.ac.za>
you write:
>Is DHCP core functionality?
As much as an editor and PPP are, yes -- without it, some people simply
*cannot* get on the net.
>Anyone putting any DHCP functionality in should look
>very seriously at any pos
Steve Kargl writes :
>
> Content-Type: text/BLOAT
>
> These should be left has ports.
>
I can understand the people who need DHCP to get their systems
up. OTOH, where does one draw the line. Is DHCP core functionality?
Another issue to be taken into account: there is already a bootp daemon
in
> Make sysinstall be able to pkg_add? We do something similar to
It can already pkg_add. However, I need dhcp in the crunched image
since I can't very well GET a package if I don't have any bloody IP
addresses to configure the network interface with and the user doesn't
know what they are either
> These should be left has ports.
Can't really get away with that anymore - too many people require
DHCP for very basic bootstrapping.
- Jordan
To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-current" in the body of the message
From: "David O'Brien"
> > Make sysinstall be able to pkg_add? We do something similar to that
>
> And just WHERE is the package?? Often on an NFS or FTP server, no??
> And just HOW am I to communicate with that NFS or FTP server??
Sorry. It's got to go somewhere offline. If not in the crunch
At 6:02 PM -0800 2/8/99, Steve Kargl wrote:
>Mike Holling wrote:
>> ... What's the problem? It's not like putting emacs in the base
>> install or anything. I still run FreeBSD on a 386/40 with a 40M MFM
>> main drive, and even so I'm not worried about the "bloat" of adding
>> DHCP.
>
> Bloat by
This does not make any operational change except to get rid
of the $conf_dir junk from rc.conf, which I originally put
in to try to bootstrap rc.diskless.
A much better way to do rc.diskless was suggested to me,
which I'm going to implement. It involves retargeting
the /c
> Make sysinstall be able to pkg_add? We do something similar to that
And just WHERE is the package?? Often on an NFS or FTP server, no??
And just HOW am I to communicate with that NFS or FTP server??
--
-- David(obr...@nuxi.com -or- obr...@freebsd.org)
To Unsubscribe: send mail to majo
From: "David O'Brien"
Subject: Re: adding DHCP client to src/contrib/
Date: Mon, 8 Feb 1999 18:27:57 -0800
> > These should be left has ports.
>
> Explain how I am to install FreeBSD at my campus when DHCP has been
> mandated. Many univ. are moving in this direction.
Make sysinstall be able to
> :Actually RedHat's boot floopy has a BOOTP client and thus the Linux
> :weenies on campus don't have the bootstrapping problem the FreeBSD users
> :do.
>
> I'm not sure I follow this. FreeBSD's kernel can be compiled up as
> a BOOTP client too.
Sorry, add to that, and their "sysinsta
:
:> Or would you rather have FreeBSD be like RedHat, where you have to
:> install an RPM for just about everything?
:
:Actually RedHat's boot floopy has a BOOTP client and thus the Linux
:weenies on campus don't have the bootstrapping problem the FreeBSD users
:do.
:
:--
:-- David(obr...@nux
> Or would you rather have FreeBSD be like RedHat, where you have to
> install an RPM for just about everything?
Actually RedHat's boot floopy has a BOOTP client and thus the Linux
weenies on campus don't have the bootstrapping problem the FreeBSD users
do.
--
-- David(obr...@nuxi.com -or-
> So, we'll import a pop server, apache, g77, ad nauseam
> to increase the credibility of FreeBSD as a workstation OS.
NO. Again, the problem is boot strapping. If you lived in a DHCP world
(and not in control of it) you would understand.
--
-- David(obr...@nuxi.com -or- obr...@freebsd.
> These should be left has ports.
Explain how I am to install FreeBSD at my campus when DHCP has been
mandated. Many univ. are moving in this direction.
--
-- David(obr...@nuxi.com -or- obr...@freebsd.org)
To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-curr
> I'm mostly interested in choosing the server part.
I am NOT importing the server. Only the client and that is because it is
required to get booted enought to install FreeBSD and to install
packages.
--
-- David(obr...@nuxi.com -or- obr...@freebsd.org)
To Unsubscribe: send mail to majo
On Mon, 8 Feb 1999, Satoshi Asami wrote:
> * Just curious as to why share/emacs and share/emacs/site-lisp are created by
> * BSD.local.dist instead of by the emacs ports which might want to use them?
> * It's not a big deal, but it seems to me that these aren't useful for the
> * general case
this causes the generation of opt_isp.h, and so you'll need to
reconfig
To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-current" in the body of the message
< said:
> So, we'll import a pop server, apache, g77, ad nauseam
> to increase the credibility of FreeBSD as a workstation OS.
None of those things are required to get a machine onto the network.
DHCP is, in a large and growing number of places.
-GAWollman
--
Garrett A. Wollman | O Siem / We
http://www.roms.cx - new freebsd news website, updated daily.
To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-current" in the body of the message
:Mike Holling wrote:
:
:It will probably go into /sbin, /bin, or /stand. These are statically
:linked exacutables.
:
:> I built a static version of the WIDE client and server, both were only
:> around 140K. What's the problem? It's not like putting emacs in the base
:> install or anything. I s
* Just curious as to why share/emacs and share/emacs/site-lisp are created by
* BSD.local.dist instead of by the emacs ports which might want to use them?
* It's not a big deal, but it seems to me that these aren't useful for the
* general case of someone not wanting to install an emacs port (s
Mike Holling wrote:
> > > If we want FreeBSD to have any credibility as a workstation OS, we
> > > need DHCP. It should be possible for a user or admin to smack in the
> > > boot floppy, have it autoconfigure the selected network interface, and
> > > perform an FTP installation.
> >
> > So, we'll
Mike Holling wrote:
} > > If we want FreeBSD to have any credibility as a workstation OS, we
} > > need DHCP. It should be possible for a user or admin to smack in the
} > > boot floppy, have it autoconfigure the selected network interface, and
} > > perform an FTP installation.
This would be re
Hi,
I beleive version 1.14 of ibcs2_ipc.c is bad. I've been receiving
the following error(s) when trying to comile it:
Thanks!
John
cc -nostdinc -O -pipe -DCOMPAT_IBCS2 -DKERNEL -Wall -Wredundant-decls
-Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith
-Winline -Wca
Hi,
...sorry, I just didn't get it ...
On Mon, Feb 08, 1999 at 04:32:39PM -0800, Steve Kargl wrote:
> > > > > I am planning on adding the Wide-DHCP client to src/contrib/ and
^^
^^^
I agree.
having a DHCP client can make the difference between being able to
get ont he net at all and not being able to get on the net.
On 9 Feb 1999, Dag-Erling Smorgrav wrote:
> Steve Kargl writes:
> > Dag-Erling Smorgrav wrote:
> > > If we want FreeBSD to have any credibility as a workstati
On 09-Feb-99 Steve Kargl wrote:
> So, we'll import a pop server, apache, g77, ad nauseam
> to increase the credibility of FreeBSD as a workstation OS.
Yes, of course, I need a pop server to install freesbsd.. NOT.
Lots of places use DHCP and in some cases you can't actually use the network
wit
> > If we want FreeBSD to have any credibility as a workstation OS, we
> > need DHCP. It should be possible for a user or admin to smack in the
> > boot floppy, have it autoconfigure the selected network interface, and
> > perform an FTP installation.
>
> So, we'll import a pop server, apache, g77
>Date: Sun, 07 Feb 1999 12:48:13 -0800
>From: Mike Smith
>> What do you think ? Or what are your experiences ?
>I hate it unreservedly. If we need a source of seeded default values,
>we should have rc.conf.default, uncommented, read-only. rc.conf is
>where people expect to make their changes
Steve Kargl writes:
> Dag-Erling Smorgrav wrote:
> > If we want FreeBSD to have any credibility as a workstation OS, we
> > need DHCP. It should be possible for a user or admin to smack in the
> > boot floppy, have it autoconfigure the selected network interface, and
> > perform an FTP installatio
So a double-fault is always a kernel stack problem?
I find it suspicious that this same machine
also had trouble with the 3c905B flaking out --
dropping packets during an ifconfig alias, and
sometimes never reactivating the interface
according to what tcpdump shows.
The 3c905B problem repeates it
On Mon, 8 Feb 1999, Mike Smith wrote:
> > The machine is running a custom kernel, but nothing
> > very unusual. My instinct is that it may be related to
> > something with the 3c905B 3COM cards that I reported
> > earlier, I'm trying with Intel EtherExpresses right now
> > and getting no fault p
Dag-Erling Smorgrav writes:
> Steve Kargl writes:
> > Dag-Erling Smorgrav wrote:
> > > I stumbled upon the (undocumented) gpib driver today [...]
> > Actually, John Galbraith has written
> > a better driver for the National Instrument GPIB cards. Search
> > the hardware mailing list for a
Dag-Erling Smorgrav wrote:
> Steve Kargl writes:
> > Dag-Erling Smorgrav wrote:
> > > I stumbled upon the (undocumented) gpib driver today [...]
> > Actually, John Galbraith has written
> > a better driver for the National Instrument GPIB cards. Search
> > the hardware mailing list for a URL to
4.0 -current
touch opt_spx_hack.h
cc -O -pipe -DCOMPAT_IBCS2 -DKERNEL -Wall -Wredundant-decls -Wnested-externs
-Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual
-fformat-extensions -ansi -DKLD_MODULE -nostdinc -I-
-I/usr/obj/usr/src/sys/modules/ibcs2 -I/usr/obj
Judging by the traffic on it over the last year it's in use widely.
On Mon, 8 Feb 1999, Brian Handy wrote:
> >I stumbled upon the (undocumented) gpib driver today - apparently for
> >the "National Instruments AT-GPIB and AT-GPIB/TNT board", according to
> >LINT. Apart from staticization sweeps,
Dag-Erling Smorgrav wrote:
> Steve Kargl writes:
> > > On Mon, Feb 08, 1999 at 02:28:20PM -0800, David O'Brien wrote:
> > > > I am planning on adding the Wide-DHCP client to src/contrib/ and
> > > > src/sbin/ in a few days.
> > [...]
> > These should be left has ports.
>
> If we want FreeBSD to h
Steve Kargl writes:
> Dag-Erling Smorgrav wrote:
> > I stumbled upon the (undocumented) gpib driver today [...]
> Actually, John Galbraith has written
> a better driver for the National Instrument GPIB cards. Search
> the hardware mailing list for a URL to his latest driver. It
> is reported to
Dag-Erling Smorgrav wrote:
> I stumbled upon the (undocumented) gpib driver today - apparently for
> the "National Instruments AT-GPIB and AT-GPIB/TNT board", according to
> LINT. Apart from staticization sweeps, -Wall fixes and the like,
> nobody's touched it since 1995. Does anybody have an AT-GP
> The machine is running a custom kernel, but nothing
> very unusual. My instinct is that it may be related to
> something with the 3c905B 3COM cards that I reported
> earlier, I'm trying with Intel EtherExpresses right now
> and getting no fault problems.
>
> The double-fault does not occur con
Steve Kargl writes:
> > On Mon, Feb 08, 1999 at 02:28:20PM -0800, David O'Brien wrote:
> > > I am planning on adding the Wide-DHCP client to src/contrib/ and
> > > src/sbin/ in a few days.
> [...]
> These should be left has ports.
If we want FreeBSD to have any credibility as a workstation OS, we
>I stumbled upon the (undocumented) gpib driver today - apparently for
>the "National Instruments AT-GPIB and AT-GPIB/TNT board", according to
>LINT. Apart from staticization sweeps, -Wall fixes and the like,
>nobody's touched it since 1995. Does anybody have an AT-GPIB board, or
>even know what it
> I stumbled upon the (undocumented) gpib driver today - apparently for
> the "National Instruments AT-GPIB and AT-GPIB/TNT board", according to
> LINT. Apart from staticization sweeps, -Wall fixes and the like,
> nobody's touched it since 1995. Does anybody have an AT-GPIB board, or
> even know wh
The machine is running a custom kernel, but nothing
very unusual. My instinct is that it may be related to
something with the 3c905B 3COM cards that I reported
earlier, I'm trying with Intel EtherExpresses right now
and getting no fault problems.
The double-fault does not occur consistently, unf
I stumbled upon the (undocumented) gpib driver today - apparently for
the "National Instruments AT-GPIB and AT-GPIB/TNT board", according to
LINT. Apart from staticization sweeps, -Wall fixes and the like,
nobody's touched it since 1995. Does anybody have an AT-GPIB board, or
even know what it is?
> Can someone please give me a short guide
> on how to track down a fatal double fault?
> System is 3.0-19990205-STABLE, and I've written
> down the fault info.
Ack. It's actually pretty difficult. You can start by trying to
locate the PC for the fault in the kernel image, but the typical cause
> I am planning on adding the Wide-DHCP client to src/contrib/ and
> src/sbin/ in a few days.
>
> I have it bmaked and ready go to. I have choosen the WIDE client because
> it is much smaller space-wise than the ISC client and its configuration
> is simplier.
I tried both, and I must say that I
> speaking about DHCP-things (clients and servers) I would like to
> hear from some 'export' on choosing a the 'right' dhcp-software
> for FreeBSD.
> I'm mostly interested in choosing the server part. In the past I
> deployed only the wide-dhcp server from the ports collection; but
> only because
Joe Abley wrote:
> On Mon, Feb 08, 1999 at 02:28:20PM -0800, David O'Brien wrote:
> > I am planning on adding the Wide-DHCP client to src/contrib/ and
> > src/sbin/ in a few days.
> >
> > I have it bmaked and ready go to. I have choosen the WIDE client because
> > it is much smaller space-wise th
Hi,
On Mon, Feb 08, 1999 at 02:28:20PM -0800, David O'Brien wrote:
> I am planning on adding the Wide-DHCP client to src/contrib/ and
> src/sbin/ in a few days.
speaking about DHCP-things (clients and servers) I would like to
hear from some 'export' on choosing a the 'right' dhcp-software
for Fre
On Mon, Feb 08, 1999 at 02:28:20PM -0800, David O'Brien wrote:
> I am planning on adding the Wide-DHCP client to src/contrib/ and
> src/sbin/ in a few days.
>
> I have it bmaked and ready go to. I have choosen the WIDE client because
> it is much smaller space-wise than the ISC client and its con
I am planning on adding the Wide-DHCP client to src/contrib/ and
src/sbin/ in a few days.
I have it bmaked and ready go to. I have choosen the WIDE client because
it is much smaller space-wise than the ISC client and its configuration
is simplier.
The plan is to make a boot floppy / boot CDROM w
Can someone please give me a short guide
on how to track down a fatal double fault?
System is 3.0-19990205-STABLE, and I've written
down the fault info.
Thanks,
-Troy Cobb
Circle Net, Inc.
http://www.circle.net
To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-curren
Mike Tancsa writes:
> OK, looking back at some of the threads, it seems I am hosed since the ELF
> cannot load klds ? Is that correct ?
>
> Are there any other options for VPN on the 3.0 branch ? SKIP wasnt/isnt
> the greatest, but I had decent luck with it on the 2.2 branch of things...
I hope
Replies to curr...@freebsd.org only, please.
I am doing some final beta testing before releasing a new version of
CVSup. When you run your next CVSup update from a FreeBSD mirror
site, you may find that it spews out a whole bunch of "SetAttrs"
messages. Or, maybe not. :-) It depends on a lot of
> Hopefully that is now fixed.
It is.
- Jordan
To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-current" in the body of the message
Tony Kimball writes:
> : Imagine this:
> :
> : $ file /tmp/test.sh
> : /tmp/test.sh: a /tmp/test.sh script text
> : $ /tmp/test.sh
>
> Won't this just fail when the recursion level is such that
> the command length exceeds stringspace?
>
> Ah, I see the difference:
> /*
>
On Sun, Feb 07, 1999 at 04:33:00PM -0800, Parag Patel wrote:
> > Because rc.conf contains configuration variables, whereas rc contains
> > commands to execute at boot time.
>
> Then I would suggest renaming rc.conf to be rc.vars or rc.config-vars
> or something more appropriate than rc.conf, whi
> Nate Williams wrote:
> > The patch implementing these changes are adequate in the kernel, but are
> > incomplete.
>
> Yes, I should have attached patch for usr.sbin/pccard/* too.
The changes to pccardd to support the new 'inactive' flag are still
missing. We can power the slot on/off, but pcca
'lo all -
On Friday, I did a make world from that day's sources. The previous build
had been in early December I think.
Anyway, once I got the new sources down and compiled I started seeing funny
problems with identd (2.8.2) - telnetting to the identd port would work
fine, but IRC servers wouldn'
Thank you for your comment.
Nate Williams wrote:
> The patch implementing these changes are adequate in the kernel, but are
> incomplete.
Yes, I should have attached patch for usr.sbin/pccard/* too.
> What about the changes to usr.sbin/pccard/*? With regard
> to the power-on modifications, it i
Thank you for your comment.
Mike Smith wrote:
> But this diagram worries me. Does this explicitly disallow physical
> removal without a preceeding virtual removal?
No. This is for card such as:
o Some cards go unstable when it is removed from slot with power on.
But turning off the power
On Sun, 7 Feb 1999, Mike Smith wrote:
> I hate it unreservedly. If we need a source of seeded default values,
> we should have rc.conf.default, uncommented, read-only. rc.conf is
Absolutely...agreed!
_
Lauri Laupmaa
...speaking for myself only...
To Unsubscribe: send mail to maj
> -Original Message-
> From: Christopher Masto [mailto:ch...@netmonger.net]
> Sent: 07 February 1999 20:14
> To: curr...@freebsd.org
> Subject: Re: was: some woes about rc.conf.site
>
>
> I haven't used it yet, but I definately think the idea is an
> improvement. I hate trying to update
hello!
I have some critical problems with fbsd. When I try to boot with fbsd
install disk (boot.flp), my system is halt.
I tried different versions of fbsd from 2.2.8R and 3.0-STABLE till
4.0-CURRENT.
I have IBM server, model 8640ES0, with PPro 200, 128 MB RAM,
SCSII-adapter AIC-7880 (it was "modi
1 - 100 of 103 matches
Mail list logo
