Re: Problem pulling particular directory from CVS
On Wednesday, November 27, 2002, at 11:34 pm, Paul A. Scott wrote: Oh, #$%@. I'm so embarrassed. My terminal session was logged into Mac OSX not FreeBSD, and I had mirrored the same directory structure, so I faked myself out. Bottom line is, cvs on Freebsd works like a champ. The cvs on MacOSX does not. My mistake. And I humbly appolgize for the stupid user error. CVS works just fine - it's just that the filesystem is case insensitive [1], so when you check out src/contrib, the distinction between src/contrib/CVS [2] src/contrib/cvs is lost, and Bad Shit happens. Try using Disk Copy to setup and mount a blank (UFS) image, or having a separate UFS partition. [1] Unless your filesystem is UFS, rather than HFS+, in which case you'll have lots of interesting other problmes. [2] CVS keeps a shedload of metadata here -- Am I getting older, or are these shows getting more entertaining? -- Flash, on Children in Need. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: cvs commit: src/lib/libstand ext2fs
On Mon, May 01, 2000 at 09:08:02PM -0700, Mike Smith wrote: What sort of fallback behaviour would you want in case of error here? Just let chroot() either succeed or fail. It's own "fallback behavior" in such a case should prove adequate. :) Hmm. Failure to chroot == failure to start init? If Linux emulation is non modular, what happens if /sbin/init is a linux binary? I admit to being tempted to find out exactly how good Linux emulation is... -- Mike Bristow, seebitwopie To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ports /work/ directory.
On Fri, Jun 16, 2000 at 11:59:18AM -0400, Will Mitayai Keeso Rowe wrote: Is there any plans to move the ports' working directory out of the /usr/ports/ tree? Look at /usr/ports/Mk/bsd.port.mk; in particular WRKDIRPREFIX. Setting it in /etc/make.conf seems sensible, perhaps WRKDIRPREFIX=/usr/ports/`hostname` or WRKDIRPREFIX=/disks/big-fast-disk/ports-build as approprate -- Mike Bristow, seebitwopie To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: SB Live (or RAM parity?) crash on today's -CURRENT
On Thu, Jul 06, 2000 at 06:32:49PM -0700, Doug Barton wrote: On Thu, 6 Jul 2000, Thomas Stromberg wrote: 'panic: RAM parity error, likely hardware failure.' This one had me confused at first, because it blamed a RAM parity error. As this is a brand new machine (Gateway GP-800), so I first thought I got a bad batch. Then I realized this only happens with apps that try to do sound stuff. This is a known problem with all PCI sound cards. It happens most often with ECC ram, but it also happens without. What kind of NIC do you have, and specifically, is it a PCI card or ISA? We're trying to track that bit down too. I see it with: mike@gurgle:~$ dmesg | grep vr0 vr0: VIA VT3043 Rhine I 10/100BaseTX port 0xb000-0xb07f mem 0xdf80-0xdf80007f irq 10 at device 10.0 on pci0 The machine does have ECC ram. If you need more, let me know and I'll give you what you need... -- Mike Bristow, seebitwopie To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: help! 5.1 doesn't do the rc thing?
On Thu, Aug 07, 2003 at 11:49:00AM -0700, Charlie Schluting wrote: Yes, of course :) That's why I'm perplexed. I let it install the files it wanted to, except for obvious things I didn't want overwritten: passwd file, sendmail config, etc. Just to verify: my old rc.conf should be read (and honored) right? Yes. But it may contain bogosity; what does . /etc/rc.conf do? What's in /etc/rc.conf? ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: uucp user shell and home directory
On Wed, Oct 03, 2001 at 01:36:26PM -0600, Lyndon Nerenberg wrote: All these solutions assume that everyone is wired up with IP connectivity. The original questions was who uses UUCP? Me. UUCP has many valid uses. Even today. If you don't understand the software, that's fine with me. Just don't use your ignorance as an excuse to dike the software out. Or more precisely, admit you want to rip the code out because you don't understand what it is, rather than making up specious excuses for it's removal. I support it's removal, because I think that software that is used by a tiny fraction of the userbase (and I suspect that uucp fits into that catagory) should be removed from the core distribution, and made into a seperate package; provided that obtaining the package and integrating it into FreeBSD is not too onerous. -- Mike Bristow, seebitwopie To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: ** HEADS UP **
On Thu, Mar 15, 2001 at 11:13:09AM -0600, Peter Schultz wrote:
On Mon, Mar 12, 2001 at 05:52:00PM -0600, Jonathan Lemon wrote:
I committed a miibus'ified fxp driver to the tree today, and made
it the default. If you compile fxp into your kernel statically,
you will also need "device miibus" as well, if it isn't there already.
If you notice any problems with the driver (things that were working
and are not working now), please let me know. If you happend to have
a chip that did _NOT_ work but now DOES work, please boot the machine
with -v, and send me the line that says "PCI IDs:".
If you have a fxp device that still doesn't work, then please get
in touch with me (and send the output of the line above).
--
Jonathan
Hi Jonathan,
I've got a slight problem in that it is not correctly auto detecting
the media type. It should be setting itself to 10baseT/UTP. I'm
running DHCP on my -current machine and I'm not sure how to set it
so that it configures the interface correctly. It previously "just
worked" without any special media settings. Is there something I
can provide to help correct this?
something like:
interface "fxp0" {
media "media 100baseTX mediaopt full-duplex";
}
in /etc/dhclient.conf will make dhclient DTRT when ifconfig ing the
interface. Of course, that means that you're forcing the
interface to be 100meg (which won't work when you plug your
laptop in $CLIENT's 10 meg hub)
--
Mike Bristow, seebitwopie
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: Make world problems
On Tue, Feb 01, 2000 at 03:34:51AM +0100, Marc Schneiders wrote: As far as this is possible for me in rather heterogenous threads, I've tried to follow the messages about recent make world problems. I've done exactly what is in src/UPDATING (and like another poster here I did *not* get the 24/01/2000 message until today...): build and install (x)install, make buildworld, installworld, distrib dirs, kernel. Some problems have disappeared, some remain, to wit: /kernel: cmd ntpd pid 86 tried to use non-present sched_get_priority_max /kernel: cmd ntpd pid 86 tried to use non-present sched_setscheduler ntpd [86]: sched_setscheduler(): Function not implemented This shouldn't (IIR comments to this list C) affect ntp, but if you want the nasty messages to go away, include: options P1003_1B options _KPOSIX_PRIORITY_SCHEDULING options _KPOSIX_VERSION=199309L in your kernel config. -- Mike Bristow, Geek At Large ``Beware of Invisible Cows'' To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: [HEADSUP] making /bin/sh the default shell for root
On Wed, Sep 22, 2021 at 10:00:49AM -0300, Renato Botelho wrote: > +1 for keeping this behavior on default config -1 for this. Things should be as default-as-possible, so that the behaviour of /bin/sh as root on FreeBSD is unsuprising to someone used to /bin/sh on other systems or users, because they won't be used to the magic config. I have no problem with a section of root's .profile having the approprate magic commented out so that folk who want this can easily have it, of course. Cheers, Mike -- Mike Bristow m...@urgle.com
