On Thu, Feb 11, 1999 at 09:46:06AM -0800, Steve Kargl wrote:
> (2) never question the intentions of a committer particularly
> on a mailing list.
Do NOT follow this rule. We should all be questioned.
Eivind.
To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-current" i
On Thu, 11 Feb 1999 09:46:06 PST, Steve Kargl wrote:
> (2) never question the intentions of a committer particularly
> on a mailing list.
Hi Steve,
I think it's healthy to question the intentions of commiters. However, I
think it's important to clearly state your concerns. If you object, list
Bruce Evans wrote:
> >> > Where did the "-C" option for install(1) come from? bde pick up on
> >> > somethings I did a long time ago.
> >>
> >> Uh, no, wrong. (Speaking as the creator of `install -C'.)
> >
> >In defense of Steven, he was the 'original' author of -C, whether or not
> >you used
>> > Where did the "-C" option for install(1) come from? bde pick up on
>> > somethings I did a long time ago.
>>
>> Uh, no, wrong. (Speaking as the creator of `install -C'.)
>
>In defense of Steven, he was the 'original' author of -C, whether or not
>you used his code or not. He pushed for t
Mike Smith writes:
> > You will get "no route to host" type messages.
>
> Yup. That's just the way it is - I can't imagine what alternative the
> original poster thought they could have, steal an address? Ignore your
> least? Get real.
Nope, just curious as to what would would happen. I kind
> > Where did the "-C" option for install(1) come from? bde pick up on
> > somethings I did a long time ago.
>
> Uh, no, wrong. (Speaking as the creator of `install -C'.)
In defense of Steven, he was the 'original' author of -C, whether or not
you used his code or not. He pushed for this lon
< said:
> Where did the "-C" option for install(1) come from? bde pick up on
> somethings I did a long time ago.
Uh, no, wrong. (Speaking as the creator of `install -C'.)
-GAWollman
--
Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same
woll...@lcs.mit.edu | O S
Steve Kargl wrote:
>Drop FreeBSD cd-rom into tray (or caddy).
>mount_cd9660 /dev/cd0a /mnt
>pkg_add dhcp
>umount /mnt
Hmmm... Lets see:
1) Drop FreeBSD CD-ROM into tray on server
2) mount_cd9660 /dev/cd0a /cdrom
3) [NFS export /cdrom]
4) Boot client from floppy.
so far so good.
5) Configure c
Steve Kargl writes:
> Dag-Erling Smorgrav wrote:
> > Steve isn't even a committer. He's one of those oh-so-many people who
> > love to whine about practically anything we do, on the assumption that
> > they know better, even though they never do any work of their own.
> [...]
> Finally, when do I
Dag-Erling Smorgrav wrote:
> Sheldon Hearn writes:
> > Anyway, 30 minutes later, I've figured it out. You're endorsing FreeBSD
> > crippleware. I sincerely hope that your attitude is _not_ endorsed by
> > the core team.
>
> Steve isn't even a committer. He's one of those oh-so-many people who
>
Sheldon Hearn writes:
> Anyway, 30 minutes later, I've figured it out. You're endorsing FreeBSD
> crippleware. I sincerely hope that your attitude is _not_ endorsed by
> the core team.
Steve isn't even a committer. He's one of those oh-so-many people who
love to whine about practically anything
>From: "Daniel C. Sobral"
>
>>Steve Kargl wrote:
>>
>> > > The plan is to make a boot floppy / boot CDROM with a DHCP client on it.
>>
>> Content-Type: text/BLOAT
>>
>> These should be left has ports.
>
>I disagree. It is very common nowadays to need to extract your IP
>address through DHCP. N
2:41 PM
To: obr...@freebsd.org
Cc: curr...@freebsd.org
Subject: Re: adding DHCP client to src/contrib/
On Tue, 9 Feb 1999, David O'Brien wrote:
> On Tue, Feb 09, 1999 at 09:27:44AM -0700, Lyndon Nerenberg wrote:
> >
> > PlatformHas DHCP
> > -
On Mon, 08 Feb 1999 22:34:52 PST, Steve Kargl wrote:
> > 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. A lot of the emerging high-speed access
> > providers aren't giving you that op
> Mike Smith wrote:
> >In a situation like that, you would just tune the dhcp client not to
> >ask for a lease on that interface. You know you've done something
> >silly; there's a mechanism to stop it breaking things. What more could
> >you ask for?
>
> POLA. Currently, an interface that is
Mike Smith wrote:
>
>> I've got a machine on the DHCP required network with two NICs. Currently
>> I'm only using one of them and thus don't have it listed in
>> ``network_interfaces''. So it just happily sits there. IMHO we
>> shouldn't try to dhcp configure it. It will just fill up logs as i
> > > Most basic, you would have ``network_interfaces="lo0 fxp0"'' as usual,
> > > but no "ifconfig_fxp0="inet " line.
> >
> > then specify a 'DHCP' token to have all non-listed interfaces do the
> > DHCP thing, eg:
> >
> > network_interfaces="lo0 dhcp"
>
> Hum... can you give a little more
> > Most basic, you would have ``network_interfaces="lo0 fxp0"'' as usual,
> > but no "ifconfig_fxp0="inet " line.
>
> then specify a 'DHCP' token to have all non-listed interfaces do the
> DHCP thing, eg:
>
> network_interfaces="lo0 dhcp"
Hum... can you give a little more of the approach?
> Ok! So I'll stop passing on this information, I'll try it again. Last
> time I used ISC-dhclient, it did infact REQUIRE a configuration file.
> Now a zero length file might of done the trick.. but it bitched about a
> non-existent file. and would not fetch an IP address for me when I ran
> it.
Just wanted to mention something that I haven't seen mentioned here in
all the flaming and whatnot.
OpenBSD ships out-of-the-box with dhcp client support available as an
install option. This turned out to be very nice when I was installing
it on one of my friend's Sparcs. His network is on a
on Feb 9, David O'Brien wrote:
> > What impact will this have on the rc files? How will it affect
> > rc.conf, seeing as it overrides several values therein?
>
> Most basic, you would have ``network_interfaces="lo0 fxp0"'' as usual,
> but no "ifconfig_fxp0="inet " line.
>
> Rather you wo
> > What impact will this have on the rc files? How will it affect
> > rc.conf, seeing as it overrides several values therein?
>
> Most basic, you would have ``network_interfaces="lo0 fxp0"'' as usual,
> but no "ifconfig_fxp0="inet " line.
Actually, I'm not sure I'd want to be that locked
In article <19990209003618.b19...@relay.nuxi.com>, David O'Brien
wrote:
> Maybe Gary isn't yelling loud enought, so let me try.
>
> I AM part of the FreeBSD Project. I'm contributing about as much as
> I possibly can.
David, please Just Do It. As is often the case, the loudest of the
obstructi
On Tue, 9 Feb 1999, David O'Brien wrote:
> On Tue, Feb 09, 1999 at 09:27:44AM -0700, Lyndon Nerenberg wrote:
> >
> > PlatformHas DHCP
> >
> > Irix 6.5Yes
> > Solaris 2.5.1 No
> Solaris 2.6 Yes
>
> You should have used a mor
On Tue, Feb 09, 1999 at 09:27:44AM -0700, Lyndon Nerenberg wrote:
>
> Platform Has DHCP
>
> Irix 6.5 Yes
> Solaris 2.5.1 No
Solaris 2.6 Yes
You should have used a more modern Solaris. It helps your argment. :-)
On Mon, 8 Feb 1999, Steve Kargl wrote:
> 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 cadd
> To insert some reality into this discussion, a quick survey at the
> office shows:
>
> Platform Has DHCP
>
> Irix 6.5 Yes
> Solaris 2.5.1 No
... and Solaris 2.6 has DHCP.
> HP/UX 10.20 Yes
> Linux (RH 5.x)
From: Charlie ROOT
> Although it is somewhat larger, the ISC dhcp2 client has significantly
> more flexability WRT options beyond the bare basics.
>
> I would recommend that the default client on HD based systems be the
> ISC client because of that flexability.
I have to agree here.
The problem
"David O'Brien" wrote:
> I was taking the "contribute code, not ideas with no one to act on them"
> route.
Hear, Hear! Please import this, it will certainly make may (and many of
those I work with) lives a $#!tload easier.
M
--
Mark Murray
Join the anti-SPAM movement: http://www.cauce.org
To Uns
On 8 Feb, Jordan K. Hubbard wrote:
>> These should be left has ports.
>
> Can't really get away with that anymore - too many people require
> DHCP for very basic bootstrapping.
To insert some reality into this discussion, a quick survey at the
office shows:
PlatformHas DHCP
Sean Eric Fagan writes:
> >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
> parser as the server.
>
>
<
said:
> The issue, as I understand it, is to get a reply from an unknown server
> (who has an IP address), while you have no IP address.
You also have to send a packet *from* 0.0.0.0 (since you have no IP
address). I'm almost irritated enough to consider fixing this this
week.
-GAWollman
From: John Birrell
> Or convince FreeBSD developers to simply add a DHCP client to the base
> sources and build a boot/install floppy with that functionality.
> No user cost. No user hassle. Why not?! Sigh.
Agree that this should be done for now. Absolutely.
In the long run, an extensible sysin
Steve Kargl wrote:
>
> > > The plan is to make a boot floppy / boot CDROM with a DHCP client on it.
>
> Content-Type: text/BLOAT
>
> These should be left has ports.
I disagree. It is very common nowadays to need to extract your IP
address through DHCP. Not having a DHCP boot floppy/cd is a seri
Karl Pielorz wrote:
>
> Whilst the argument about removing the source tree / kernel source etc. has
> always been pretty mute (what hackers not worth their salt don't come
> prepared? :) - I don't like the idea of every root exploiter just being able
> to 'instantly' sit there and run BPF! (Withou
Steve Kargl wrote:
>
> Drop FreeBSD cd-rom into tray (or caddy).
> mount_cd9660 /dev/cd0a /mnt
> pkg_add dhcp
> umount /mnt
What about us without FreeBSD cd-roms?
--
Daniel C. Sobral(8-DCS)
d...@newsguy.com
d...@freebsd.org
Well, as a computer geek, I have to be
From: "Jordan K. Hubbard"
Subject: Re: adding DHCP client to src/contrib/
Date: Mon, 08 Feb 1999 21:05:59 -0800
> > 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
> -Original Message-
> From: David O'Brien [mailto:obr...@nuxi.com]
> Sent: 09 February 1999 10:54
> To: Geoff Rehmet
> Cc: curr...@freebsd.org
> Subject: Re: adding DHCP client to src/contrib/
>
>
> > It may even be necessary to use bpf ini
In article
you write:
>What impact will this have on the rc files? How will it affect
>rc.conf, seeing as it overrides several values therein?
PAO already has some support for this; it works, and is what I've been using.
>What happens
>if your lease expires and doesn't get renewed, or gets ren
Can we go onto a more interesting discussion? I'm a bit tired of
debating the merits of DHCP or rc.conf.site.foo.bar and this
discussion thread (and that one) have now moved to the "delete at
first sight" stage.
- Jordan
> David O'Brien wrote:
> > > These should be left has ports.
> >
> > Expla
On Mon, Feb 08, 1999 at 04:32:39PM -0800, Steve Kargl
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 F
> 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
> parser as the server.
Ok! So I'll stop passing on this information, I'll try it again. Last
time I used ISC-dhclient, it did infact REQUIRE a co
> What impact will this have on the rc files? How will it affect
> rc.conf, seeing as it overrides several values therein?
Most basic, you would have ``network_interfaces="lo0 fxp0"'' as usual,
but no "ifconfig_fxp0="inet " line.
Rather you would have a ``/etc/start_if.fxp0'' file with:
> > *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'
> Then, *BUY* the cd-rom and support the FreeBSD project.
Maybe Gary isn't yelling loud enought, so let me try.
I AM part of the
On Mon, Feb 08, 1999 at 11:10:53PM -0800, Mike Smith wrote:
>
> There are any number of reasons for going with the ISC client,
> including an involved ISC developer that's keen to help it happen.
The WIDE project has been very responsive in the past in supporting their
products on FreeBSD. Unle
> David's original email said he was going to commit without giving
> a justification. I call it bloat, then the justifications pour in.
I may have been too close to the situation. JKH asked for a DHCP client
on -STABLE a few days ago to add to the boot floppy. He now has one.
I was taking th
> It may even be necessary to use bpf initially, but there must be a more
> elegant way - having a quick look around - it would be a good idea to
> look at the code which already exists in libstand
> (/usr/src/lib/libstand/bootp.c).
There is.
Date: Wed, 16 Sep 1998 15:20:45 -0400 (EDT)
I'm not convinced that DHCP CLIENT needs to have everything wide open.
It sends a broadcast, but the response is directed.
On Mon, 8 Feb 1999, Sean Eric Fagan wrote:
> In article
> <19990209082922.17759.qmail.kithrup.freebsd.curr...@rucus.ru.ac.za> you write:
> >- DHCP-WIDE requires you to have
"David O'Brien" writes:
> 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 pla
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
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
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
> 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 direc
> :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
< 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
: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
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
1 - 100 of 113 matches
Mail list logo
