On 26-Jan-01 Steve O'Hara-Smith wrote:
> Hi,
>
> Following some recent comments on the evil ways of ports have of
> writing in /etc on install -
This assumes that everyone uses /usr/local for ${LOCALBASE}, which is
not a good assumption to make. If you want to do this right, then
> On Thu, Jan 25, 2001 at 02:18:01PM -0800, Matthew Jacob wrote:
> > An update on this
> >
> > If the server is Solaris, neither NetBSD nor FreeBSD (i386 or alpha) have a
> > problem (as clients).
> >
> > The problem is therefore in some interaction between this server (see
> > http://ww
On Thu, Jan 25, 2001 at 02:18:01PM -0800, Matthew Jacob wrote:
> An update on this
>
> If the server is Solaris, neither NetBSD nor FreeBSD (i386 or alpha) have a
> problem (as clients).
>
> The problem is therefore in some interaction between this server (see
> http://www.traakan.com- sort
Louis A. Mamakos <[EMAIL PROTECTED]> types:
> I think that /etc/X11 which came along with the XFree86 4 port is a
> step in the right direction, too. Frankly, I'd rather have an /etc/local
> than /usr/local/etc for that sort configuration data so that it's in
> one place, and backed up along with
> Perhaps /etc/shells is the least of all evils here.
I think there's way too much paranoia about software systems putting
stuff into /etc. It intended to contain host-specific configuration data
I think there's value in having this configuration data in one or very
few places so you're n
On Fri, 26 Jan 2001 16:21:01 -0500 (EST)
Garrett Wollman <[EMAIL PROTECTED]> wrote:
GW> <
said:
GW>
GW> > The patch below (against 4-stable but it will probably apply easily
GW> > to -current) moves /etc/shells to /usr/local/etc/shells.
GW>
GW> Bad idea. No base component (never mind libc!)
< said:
> The patch below (against 4-stable but it will probably apply easily
> to -current) moves /etc/shells to /usr/local/etc/shells.
Bad idea. No base component (never mind libc!) should hard-code a
pathname in /usr/local.
-GAWollman
To Unsubscribe: send mail to [EMAIL PROTECTED]
Hi,
Following some recent comments on the evil ways of ports have of
writing in /etc on install -
The patch below (against 4-stable but it will probably apply easily
to -current) moves /etc/shells to /usr/local/etc/shells. It should include
the removal of /usr/src/etc/she
Hi,
I plugged my HP Omnibook 4150 into my dock for the first time in a couple
months only to discover that I couldn't attach any of the PCI devices in
it. I'm running -current as of sometime in the last week or so. I traced
the problem to the new PCI code comitted six weeks ago. Specificaly:
John Hay wrote:
>
> If you have current source, just recompile rpcgen and try again. Something
> like:
>
> cd /usr/src/usr.bin/rpcgen
> make all install clean
>
> should do it. Then you can return to your regular make world.
>
> John
That did end up working. Thanks. I just wanted to mention
>
> } --
> } >>> stage 4: populating /usr/obj/usr/src/i386/usr/include
> } --
>
> [snip]
>
> } ===> rpcsvc
> } rpcgen -C -h -DWANT_NFS3 /usr/src/include/rpcsvc/key_prot.x -o k
This has been happening for sometime. It seems to happen when you upgrade a
recent 5.0-SNAPSHOT (not a 4-STABLE install).
I believe that David O'Brien is aware of this. He was working on it - I
wonder if it slipped away :)
Tom Veldhouse
[EMAIL PROTECTED]
- Original Message -
From: "Ni
Nick Sayer <[EMAIL PROTECTED]> wrote:
} --
} >>> stage 4: populating /usr/obj/usr/src/i386/usr/include
} --
[snip]
} ===> rpcsvc
} rpcgen -C -h -DWANT_NFS3 /usr/src/include/rp
--
>>> stage 4: populating /usr/obj/usr/src/i386/usr/include
--
cd /usr/src; MAKEOBJDIRPREFIX=/usr/obj
COMPILER_PATH=/usr/obj/usr/src/i386/usr/libexec:/usr/obj/usr/src/i386/usr
> I'd be happy to (I like a challenge) but I still require access to the
> standards for that. So my question still stands, does BSDi have IEEE
> subscriptions for FreeBSD developers to use, or are there any other ways
> for me to aquire (legally of course) the standards I need without having t
>
> > There's a Spanning Tree Protocol (STP) defined by IEEE 802.1D. I'd prefer
> > to have that, but I don't have the 1K US$ to shell out for that.
> > Does BSDi have IEEE subscriptions for FreeBSD developers to use?
>
>Please also consider implementing 802.1G, which is for bridging over PPP
>(B
subscrive [EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
On Thu, Jan 25, 2001 at 12:19:16PM +0100, Rogier R. Mulhuijzen wrote:
> At 09:37 25-1-01 -0800, Archie Cobbs wrote:
> >Rogier R. Mulhuijzen writes:
> > > But from my list of wishes I'd say the first 3 are gone. All that's
> > left is
> > > spanning tree. I'm probably going to need this pretty soo
suscribe
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
19 matches
Mail list logo
