On Sun, 17 Oct 1999, Garrett Wollman wrote:
;-On Sun, 17 Oct 1999 11:55:21 -0400, "Patrick Bihan-Faou" [EMAIL PROTECTED]
said:
;-
;- This is going in the right direction, but here is a question (and I don't
;- have the answer). Is it so much more easier to create new compile time
;- directive
Warner Losh writes:
In message [EMAIL PROTECTED] Jason Evans writes:
: Summary: -current will be destabilized for an extended period (on the order
: of months). A tag (not a branch) will be laid down before the initial
: checkin, and non-developers should either stick closely to that tag
Peter Jeremy writes:
On 2000-Jun-22 15:22:12 -0500, Chris Dillon [EMAIL PROTECTED] wrote:
I think it would be a very good idea to enable softupdates by default
when a new filesystem is created. Modify newfs to do this and use
tunefs only if you want to _disable_ softupdates on a filesystem.
Nick Hibma writes:
Yes, the driver is here and it seems to work according to Mike Meyer
(IIRC), he's fixed up a few other bits and pieces and I am ready to
commit it, but I haven't had time to test it yet.
I've still got the problems I reported to the bsd-usb list, but I
suspect those
Jonathan Smith writes:
I, for one, like the functionality, and thought it kinda already worked
that way (or maybe I _made_ it work that way on my machines, cn't
remember). I would like solid facts, rather than a religious/exagerated
discussion.
I agree. I first ran into this on solaris. I
By all means, use start/stop args, but hard link the .sh files into seperate
directories or something so that the order can be tweaked..
If all you want is to make sure that shutdown happens in the reverse
order of startup, that can be done by reversing the list in
rc.shutdown. But how about
Warner Losh writes:
In message l03130304b57ec3bf8693@[194.32.164.2] Bob Bishop writes:
: Can anyone give a quick synopsis of the current status of support for USB
: modems? TIA
They aren't supported yet. There's at least one group that might be
working on them. The value of supporting them
Daniel C. Sobral writes:
Mike Meyer wrote:
The multiple levels are there to deal with changes in state. In BSD, for
instance, we have single user/multi-user. A number of other variations
can exist, both in heavy duty servers where you might want to bring
certain services down for upgrade
The build broke this morning, and is still broken as of a few moments
ago. The problem is that systat tries to use the (apparently now
missing) m_mtypes element of the mbstat structure:
su-2.04# pwd
/usr/src/usr.bin/systat
su-2.04# make
cc -O -pipe -march=pentium
Nick Hibma writes:
Right, I finally committed the driver you sent me. let me know if I've
made a mistake and committed the wrong one.
Well, the one you committed doesn't have the notification support I
added, or the serial state bits that are in usbcdc.h. Do you need/want
copies of the one
[I asked this on -questions, and got no response, so...]
Is it just me, or has disklabel lost the ability to read/write from
extended slices in 5.0-RELEASE?
mike
--
Mike Meyer [EMAIL PROTECTED] http://www.mired.org/consulting.html
Independent WWW/Perforce/FreeBSD/Unix
. It would require
reworking the comments in the files in /etc/defaults, and a little
more discipline in editing them, but that's not necessarily a bad
thing.
mike
--
Mike Meyer [EMAIL PROTECTED] http://www.mired.org/home/mwm/
Independent WWW/Perforce/FreeBSD/Unix consultant
as well.
mike
--
Mike Meyer [EMAIL PROTECTED] http://www.mired.org/home/mwm/
Independent WWW/Perforce/FreeBSD/Unix consultant, email for more information.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
It seems that the last changes to the ahc drivers (committed on the
18th) are causing my system to lock up. I'd check the aic7890 specific
changes first, but that's just me.
The problem is that when I start doing I/O to two drives, the system
hangs. The SCSI controller and both drives(*) turn on
Ok, I give up. It seems that the world change from exit to sys_exit
broke the world build, but I can't figure out where. I've fixed every
occurence of SYS_exit in the source tree (this one seems to be
src/lib/csu/i386/crt0.c, but there were some in gdb as well), and
removed /usr/obj - and I still
Peter Wemm writes:
Argh! I knew today was going to stay a bad day.
I had similar thoughts about mine, both before I started the build,
and afterwards.
I am pretty sure I know how to fix this and will commit a fix shortly. If you
want to try now, edit sys/kern/syscalls.master:
1 STD
My last grip about this didn't draw any response except for "Yeah, I
have that problem to". Is there a better place to discuss problems
with the Perl integration with FreeBSD? send-pr doesn't have a "perl"
category, or I'd try that.
Basically, the problem is that ports that install Perl modules
Idea Receiver writes:
i have try to upgrade one of my 4.1 release to -current.
however, when i try to build the kernel, it failed as following
message.
The nasty downside of the the module system is that people who don't
adequately test module code before checking it in will screw up kernel
Warner Losh writes:
In message [EMAIL PROTECTED] Mike Meyer writes:
: The nasty downside of the the module system is that people who don't
: adequately test module code before checking it in will screw up kernel
: builds for kernels that don't need that code.
But I did test it. But I had
Warner Losh writes:
In message [EMAIL PROTECTED] Mike Meyer writes:
: Warner Losh writes:
: In message [EMAIL PROTECTED] Mike Meyer writes:
: : The nasty downside of the the module system is that people who don't
: : adequately test module code before checking it in will screw up kernel
Warner Losh writes:
So we're down to stale sources at one of the mirrors, I think. My
kernel tree here is completely clean and checked out from the my local
cvs tree. Where do you get your sources from? What revision of
src/sys/dev/pccard/card_if.m do you have? The following changed
I'm curious - is there some reason that the CDR ioctls (in
/usr/include/sys/cdrio.h) aren't supported for MMC cds? It looks like
doing them for MMC would be straightforward, it's the kind of thing
that an OS is supposed to do, and it would allow people with MMC
drives to cdrecord for the much
Kenneth D. Merry writes:
On Mon, Aug 21, 2000 at 10:54:49 -0500, Mike Meyer wrote:
I'm curious - is there some reason that the CDR ioctls (in
/usr/include/sys/cdrio.h) aren't supported for MMC cds? It looks like
doing them for MMC would be straightforward, it's the kind of thing
Kenneth D. Merry writes:
Which should actually be smaller than the flood of mail saying things
like "why doesn't burncd support my nice, standard-compliant CD-R?" In
fact, according to the documentation that comes with cdrecord, it
would be *much* smaller, because all the SCSI CD-Rs
Kenneth D. Merry writes:
On Mon, Aug 21, 2000 at 18:19:47 -0500, Mike Meyer wrote:
Kenneth D. Merry writes:
Which should actually be smaller than the flood of mail saying things
like "why doesn't burncd support my nice, standard-compliant CD-R?" In
fact,
Kenneth D. Merry writes:
Does this extend to the point of supporting things that happen to
share a physical connector with SCSI, but otherwise aren't SCSI?
Because that's what supporting non-MMC CD-R drives would amount to.
Not really. Non-MMC CD-Rs not only use the same connectors and
Christopher Masto writes:
I'd rather see cdrecord work on ATAPI CD-Rs. burncd gives me a lot of
trouble.
As cdrecord isn't part of FreeBSD, this is clearly the wrong place to
ask about that. Joe Schilling watches [EMAIL PROTECTED], and
that's the place to ask.
I've been told that ATAPI CD-Rs
Christopher Masto writes:
I'd rather see cdrecord work on ATAPI CD-Rs. burncd gives me a lot of
trouble.
Spoke to soon - according to the pkg/DESCR file, it should work on
them now.
mike
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body
I'm curious - are there any committers who regularly use a system with
LOCALBASE set to something other than /usr/local?
Thanx,
mike
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Warner Losh writes:
Having said this, if you can come up with a foolproof way to get the
ioctls right on all the drives that do support them, even the whacked
out ones that need all kinds of quirky entries, and do it in a way
that doesn't needlessly bloat the kernel for little gain (few
Matthew Jacob writes:
If the answer from the person who would have to approve the code had
come back "Ok, provide the code and we'll see how well it works in
practice", I'd do the code. But when it appears the code would never
make it into the tree to be used, why waste my time?
'coz
Mark Murray writes:
So, I think having the option to use encrypted swap on FreeBSD
would be nice. Is anybody already working on this? If not, how do
I get somebody to work on it? ;-)
Ever since the Phoenecians invented money, there has been at least
one guaranteed answer to that :-)
Brian Fundakowski Feldman writes:
One thing that's missing is the ioctl CDRIOCSETBLOCKSIZE. It would
be _really_ nice if cd(4) supported that ioctl so I could just seek
and read from a CD. I had knu trying out my read_cd program, and it
doesn't work for SCSI CD-ROMs, seemingly because of
Jacques A. Vidrine writes:
On Mon, Aug 21, 2000 at 11:59:26PM -0500, Mike Meyer wrote:
I'm curious - are there any committers who regularly use a system with
LOCALBASE set to something other than /usr/local?
I have LOCALBASE=/opt for a couple of years now.
OTOH, I also have a symlink
Mark Murray writes:
However, I was wondering if there was anyone who could fix things that
weren't PREFIX clean who would also find them on a regular
basis. That's not you.
There is a non-trivial Perl5 LOCALBASE problem that I'm trying to
get my head around.
If this is the problem with
Mark Murray writes:
However, I was wondering if there was anyone who could fix things that
weren't PREFIX clean who would also find them on a regular
basis. That's not you.
There is a non-trivial Perl5 LOCALBASE problem that I'm trying to
get my head around.
I'm actually discussing one
Konstantin Chuguev writes:
"Jacques A. Vidrine" wrote:
On Wed, Aug 23, 2000 at 01:01:59AM -0500, Mike Meyer wrote:
Um - why? If you removed the setting of LOCALBASE in that case, you
wouldn't change the disk layout at all.
I prefer installed executables, data files, and
Satoshi - Ports Wraith - Asami writes:
* From: Mike Meyer [EMAIL PROTECTED]
* However, I was wondering if there was anyone who could fix things that
* weren't PREFIX clean who would also find them on a regular
* basis. That's not you.
I can help you when the new package building cluster
Satoshi - Ports Wraith - Asami writes:
* From: Kris Kennaway [EMAIL PROTECTED]
* On Wed, 23 Aug 2000, Mike Meyer wrote:
* How does it decide whether or not a package conforms?
* Probably by looking for files which get installed in /usr/local or
* /usr/X11R6 instead of ${LOCALBASE
Brooks Davis writes:
On Sun, Aug 27, 2000 at 09:33:21PM +0900, Motomichi Matsuzaki wrote:
Doing 'make install' without /boot/device.hints is failed,
saying "You must set up a /boot/device.hints file first."
Is this right?
You should read cvs-all. There was a commit by Peter which forces
James Johnson writes:
The method of building and installing a kernel to me seems a bit off.. Both
the buildworld and installworld targets default to GENERIC, yet GENERIC is a
file checked into the -CURRENT CVS repository.. Any changes to this file
will get blown away if whenever you update
Donn Miller writes:
Mike Meyer wrote:
I do read cvs-all, and I missed it. Not did I find device.hints in the
relevant Makefiles. Can you provide a pointer to details on how
/boot/device.hints is used in the build process, or how having an
empty one keeps you from shooting yourself
Maxim Sobolev writes:
Mike Meyer wrote:
Donn Miller writes:
Mike Meyer wrote:
I do read cvs-all, and I missed it. Not did I find device.hints in the
relevant Makefiles. Can you provide a pointer to details on how
/boot/device.hints is used in the build process, or how having
Maxim Sobolev writes:
Mike Meyer wrote:
Will the system fail to boot if there isn't an empty device.hints
file?
No, it will boot, but some devices (like keyboard, console etc) would not work.
That's clearly not true - I just removed an empty /boot/device.hints
and rebooted
First, I want to thank everyone for taking the time to explain what
was going on. It's now clear that I was confused, and things aren't
as bad as I thought. I'd like to see the Makefile changes so that if
there wasn't an empty /boot/device.hints, one was created, but that's
relatively minor.
David O'Brien writes:
On Mon, Aug 28, 2000 at 06:29:21PM -0700, Brooks Davis wrote:
On Tue, Aug 29, 2000 at 10:25:26AM +0930, Greg Lehey wrote:
At the very least, there appears to be confusion about how to use the
2. You must have a /boot/device.hints file, and it must contain at
Looks like 3dfx linux emulation aren't mixing well. Since I don't
use 3dfx, I turn off that module.
What we really need is a system that lets me specify *which* modules
to build. Hmmm.
mike
=== 3dfx
make: don't know how to make @/i386/linux/linux_ioctl.h. Stop
*** Error code 2
Chris Hedley writes:
On Mon, 4 Sep 2000, Brandon Hume wrote:
Just after the "waiting for SCSI devices to settle" message, I'll get a
number of SCB errors (which I don't have written down, unfortunately), and
then eventually a panic. This is with ACPI enabled... if I don't enable
ACPI,
Mitsuru IWASAKI writes:
All I can say is that acpi is initilized after pcib and its children
are attached so I don't think ACPI code affects PCI stuff...
# Power management support (see LINT for more options)
#device apm
device acpi
Could you disable acpi and
Jason Evans writes:
jasone 2000/09/06 18:33:03 PDT
Modified files:
bin/ps print.c
[...]
Nice try, but you didn't fool me. That's the SMP patch, even if the
first change in the first modified file is a spelling fix in a comment
in userland code!
Nice to see it's
Ben Smithurst writes:
After poking around a bit with remote GDB, this seems to be caused by a
stray IRQ 7, since irq == 7, ir == ithds[irq] == NULL, ir-foo == BOOM.
The attached rather crude patch has "fixed" the problem for now, but
does anyone have any suggestions for a real fix?
Isn't a
Poul-Henning Kamp writes:
In message [EMAIL PROTECTED], Ben Smithurs
t writes:
Poul-Henning Kamp wrote:
I must admit that I think in general that /dev/std{in,out,err} and /dev/fd
is bogus. It looks like something which happened "because we can" more
than something which has a
I just realized this may be a difference due to a between -current and
-stable, so I've moved discussion to -current to check. Apologies if
this was the wrong thing to do.
On Wed, 13 Sep 2000, Mike Meyer wrote:
It then fails to install for me with the error messages:
/tmp/sv001.tmp/setup.bin
Brandon D. Valentine writes:
On Sat, 16 Sep 2000, John Baldwin wrote:
Err, AFAIK, the only instability atm is that under heavy load some ahc
controllers seem to hang (or possibly the ahc driver is getting out of
sorts and hanging.) However, the problem is not so bad that you can't
I've had
I cvsupped and rebuilt earlier to today, only to find that the kernel
was installed as /boot/kernel/kernel instead of
/boot/kernel/kernel.ko. While fixing this was trivial, it was a bit of
a surprise.
Is this a bug, or did I happen to catch the world in a state of change
described in a cvs-all
Ben Smithurst writes:
Mike Meyer wrote:
I cvsupped and rebuilt earlier to today, only to find that the kernel
was installed as /boot/kernel/kernel instead of
/boot/kernel/kernel.ko. While fixing this was trivial, it was a bit of
a surprise.
Is this a bug, or did I happen to catch
It seems that recent (the last two weeks?) changes to periodic have
changed things so that non-root users of it no longer get any output.
A simple fix would be to change the default output to $USER (not yet
tested). However, having a user-specific periodic.conf would be a lot
more useful. But I
Vallo Kallaste writes:
On Sat, Sep 16, 2000 at 03:01:28PM -0500, Mike Meyer [EMAIL PROTECTED] wrote:
I've had a ton of experience with ahc lately, as those of you who follow
-questions, -stable, or -scsi know. r1.48 of aic7xxx.c is horribly
broken. I can't get current snaps after
Alexander Langer writes:
Thus spake Donn Miller ([EMAIL PROTECTED]):
What is the suggested best way to set permissions on devices in DEVFS?
(I want to chmod 664 /dev/acd0c to let users in the group operator
burn CD-R's).
Do we already have a common way that I missed?
/etc/rc.devfs
Seigo Tanimura writes:
On Thu, 28 Sep 2000 11:55:55 -0500,
"Jacques A. Vidrine" [EMAIL PROTECTED] said:
It would also be helpful for us to (semi-)automatically update old
binaries installed by ports. (I have been trying this for a couple of
days)
Jacques Personally I don't want
Alexander Langer writes:
Thus spake Mike Meyer ([EMAIL PROTECTED]):
Does it possibly belong in /etc/defaults/rc.devfs, to slurp in
/etc/rc.devfs (if it exists) at the end?
No - instead we should add something like devfs_permission{0,1,2,etc}
(and maybe ownership) to rc.conf, which can
Seigo Tanimura writes:
On Sat, 30 Sep 2000 13:35:48 -0500 (CDT), Mike Meyer [EMAIL PROTECTED] said:
Mike Seigo Tanimura writes:
Completely automatic update of installed ports is acutally difficult
because we cannot get to know the language or required toolkit from
the name of a binary
Jordan Hubbard writes:
That's a nice idea and may work in my particular case, but this is
also the out-of-box configuration for Red Hat and most
Linux-to-FreeBSD users wouldn't know a tune2fs if it snuck up and bit
them on the ass in broad daylight. How hard would it be to support
sparse
I recently got my digital camera back out, and started pulling the old
pictures from it. I noticed something I hadn't ever seen before - silo
overflows from the sio port. At the moment, I'm wondering if this is a
known problem that is being investigated (SMPNG comes to mind), or
something new.
attila! writes:
on Sat, 7 Oct 2000 20:03:12 -0500 (CDT), Mike Meyer [EMAIL PROTECTED] said:
I recently got my digital camera back out, and started pulling the old
pictures from it. I noticed something I hadn't ever seen before - silo
overflows from the sio port. At the moment, I'm
It seems that something has broken plaympeg - at least for video. In
trying to play video back, I get a black window and no images. Audio
playback seems fine. This is something I don't do often, so I'm not
sure when it happened.
Anyone else seeing this? Anyone working on it?
Thanx,
Nickolay Dudorov writes:
In article [EMAIL PROTECTED] you wrote:
It seems that something has broken plaympeg - at least for video. In
trying to play video back, I get a black window and no images. Audio
playback seems fine. This is something I don't do often, so I'm not
sure when it
I've got a system with 4.1-STABLE installed. I mount -current sources
on it, do make buildworld/buildkernel/installkernel/installworld and
reboot. The boot loader runs, gives me the "booting default in..."
countdown, prints "|", and then stops. After thrashing the disks (with
*no* boot messages),
Just curious - now that the kernel has moved into /boot/kernel/kernel,
does anyone know how well would it work to put /boot in it's own
partition (possibly in it's own slice)?
Thanx,
mike
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the
Maxim Sobolev writes:
"Michael C . Wu" wrote:
On Fri, Oct 13, 2000 at 07:22:20AM -0500, Mike Meyer scribbled:
| Just curious - now that the kernel has moved into /boot/kernel/kernel,
| does anyone know how well would it work to put /boot in it's own
| partition (possibly i
I'm getting hard lockups booting a -current kernel supped about 6
hours ago. If I try to boot multiuser, I get a message about the
ethernet interface being configured, and then nothing. If I boot
single user, it comes up fine, and I can configure the NIC. The system
then locks up maybe 10 seconds
David O'Brien writes:
On Fri, Oct 13, 2000 at 07:18:05PM +0300, Maxim Sobolev wrote:
Nope, the loader can load stuff from other partitions, even from some strange
ones like msdos ;), so theoretically it should be possible to have /boot, or
even /boot/kernel, on another partition (it may
Garrett Rooney writes:
On Tue, Oct 24, 2000 at 04:49:40AM +0700, Alexey Dokuchaev wrote:
Well, would not be this stepping aside from BSD startup sequence, which we
all know and love? Having dozens of small files instead of pair of
big ones always frustrates me when I have to work with
Alexey Dokuchaev writes:
Well, we *already* have over a dozen /etc/rc.* files on -current. And
we *don't* have the advantage of a consistent interface to control all
the functions in /etc/rc. If you break things up, then if you need to
restart the mail server, just go "/etc/rc.d/sendmail
Jordan Hubbard writes:
[redirected to just -current; I'm not sure what this has to do with -net]
I agree. I've been using them for a while on my dog slow Windows CE
machine. There were some minor issues when they were first committed
to NetBSD on some platforms (due to a too early use of
Chuck Robey writes:
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
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,
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
Like everyone else, I've been bit by /dev/random blocking because it
didn't have enough entropy. I recently got bit after booting the
system single-user to do some work, meaning nothing in the discussion
about when/where/how to deal with the entropy information addressed
this one.
It seems like
Could I get some feedback on URL:
http://www.freebsd.org/cgi/query-pr.cgi?pr=22755 ? It's just a
one-line kernel patch with some attendant updates in the kernel and
libc, but it makes dealing with broken #! scripts *much* saner, and no
one has even seen fit to comment on it yet :-(.
Alfred Perlstein [EMAIL PROTECTED] types:
* Mike Meyer [EMAIL PROTECTED] [001122 22:41] wrote:
Could I get some feedback on URL:
http://www.freebsd.org/cgi/query-pr.cgi?pr=22755 ? It's just a
one-line kernel patch with some attendant updates in the kernel and
libc, but it makes dealing
the stupidity? I have a test machine running both
-current and -stable (and NetBSD-current, Solaris, Linux, and last and
least Win98), and haven't encountered any problems with it.
mike
--
Mike Meyer http://www.mired.org/home/mwm/
Independent WWW/Unix/FreeBSD
David O'Brien [EMAIL PROTECTED] types:
On Wed, Nov 29, 2000 at 07:41:14PM -0600, Mike Meyer wrote:
Hmm - what's the stupidity? I have a test machine running both
-current and -stable
Do you have the two FreeBSD installations on the same disk? If so, I'd
love to hear how you did it. I
, ...), and you use it just like a tty line tied to
an external modem.
mike
--
Mike Meyer http://www.mired.org/home/mwm/
Independent WWW/Unix/FreeBSD consultant,email for rates.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubs
Warner Losh [EMAIL PROTECTED] types:
In message [EMAIL PROTECTED] "David O'Brien" writes:
: Except for stupidity in libdisk(I believe) and thus sysinstall, there is
: no, none, zero reason why one cannot have two installations of FreeBSD in
: two different slices on the same disk.
I've done
involved.
mike
--
Mike Meyer [EMAIL PROTECTED] http://www.mired.org/home/mwm/
Independent WWW/Unix/FreeBSD consultant,email for more information.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Brandon D. Valentine [EMAIL PROTECTED] types:
There are other places where FreeBSD doesn't comply with the
appropriate standard - packages vs. FHS, for instance. I claim that
We don't seek to comply with the arbitrarily devised linux filesystem
standard. We comply with hier(5), a standard
fixed.
mike
--
Mike Meyer [EMAIL PROTECTED] http://www.mired.org/home/mwm/
Independent WWW/Unix/FreeBSD consultant,email for more information.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
David O'Brien [EMAIL PROTECTED] types:
On Sat, Dec 09, 2000 at 01:59:51PM -0600, Mike Meyer wrote:
I know. Unfortunately, support for PREFIX seems to draw more lip
service than actual service.
I disagree. If one of the ports I maintain isn't PREFIX-clean, let me
know and it _will_
Warner Losh [EMAIL PROTECTED] types:
In message [EMAIL PROTECTED] Mike Meyer writes:
: I know. Unfortunately, support for PREFIX seems to draw more lip
: service than actual service.
Actually, which ports, specically, doesn't this work with? I've
installed several ports with PREFIX defined
Daniel C. Sobral [EMAIL PROTECTED] types:
Mike Meyer wrote:
Rant second: FreeBSD *violates* years of traditions with it's
treatment of /usr/local. /usr/local is for *local* things, not add-on
software packages! Coopting /usr/local for non-local software creates
needless complexity
Garrett Wollman [EMAIL PROTECTED] types:
On Sun, 10 Dec 2000 09:37:53 -0600 (CST), Mike Meyer [EMAIL PROTECTED] said:
However, FreeBSD is still the only vendor distribution I know of that
installs software in /usr/local. That's the problem - software that
comes from the vendor doesn't
Joe Kelsey [EMAIL PROTECTED] types:
Mike Meyer writes:
If memory serves (and it may not at this remove), /usr/local/bin
wasn't on my path until I started using VAXen, meaning there were few
or no packages installing in /usr/local on v6 v7 on the 11s.
If you remember v6 and v7
Forrest Aldrich [EMAIL PROTECTED] types:
Haha... okay, then what's the argument about.
You're about six years late. The ports system has used $PREFIX for
precisely this purpose since October 1994.
As Jacques pointed out, you set LOCALBASE in /etc/make.conf.
The problem is that *it doesn't
Nat Lanza [EMAIL PROTECTED] types:
Mike Meyer [EMAIL PROTECTED] writes:
Whether or not it's part of FreeBSD is immaterial. It's part of the
distribution that comes from FreeBSD, and is treated differentlyh from
locally installed software (whether written locally or by a third
party
Brian Dean [EMAIL PROTECTED] types:
On Sun, Dec 10, 2000 at 01:02:09PM -0600, Mike Meyer wrote:
The problem is that *it doesn't work*. Well, not very well. Part of it
is that it's only given lip service: the porters handbook says "make
your ports PREFIX clean"; portlint does
Joe Kelsey [EMAIL PROTECTED] types:
Mike Meyer writes:
Sure, the software in ports/packages aren't part of FreeBSD. Using
that to claim they should have the same status or treatment as locally
written or maintained software is a rationalization.
You are simply wrong in your
David O'Brien [EMAIL PROTECTED] types:
This control is part of why it would be nice to have /usr/pkg separate
from /usr/local. I've given up on FreeBSD and had to create my own
/usr/treats to hold what should have been in /usr/local if the FreeBSD
Packages hadn't polluted it.
I went the
Joe Kelsey [EMAIL PROTECTED] types:
David O'Brien writes:
On Sun, Dec 10, 2000 at 11:22:17AM -0800, Joe Kelsey wrote:
Basically, /usr/local is for anything the local administration wants to
officially support. The ports use of this (and by extension,
pre-compiled ports
David O'Brien [EMAIL PROTECTED] types:
Wherease "PREFIX clean" means "all installed files are in the PREFIX
tree",
Correct.
I intend "LOCALBASE clean" to mean "all files installed by other ports
are looked for in the LOCALBASE tree".
If all ports are PREFIX clean, you will have
1 - 100 of 124 matches
Mail list logo
