Re: How to configure FreeBSD for rebooting when kernel panic
On Fri, 10 Jun 2005, Andrey V. Elsukov wrote: Andrew McNaughton wrote: You can't unmount your root file system. Because of this it's possibly a good idea to have as minimal a root partition system as possible, off the raid system, and very rarely changed, so it's unlikely to get screwed up. Yes, i know. Root FS, and othser system FS's is on the other disk. RAID stripe have only public data. You want a system where if the mounts (other than the root fs) fail, the system will still be adminsterable. To maintain remote access, you'd need to make sure that all your basic login tools are on the root disk. eg sshd, root's default shell, etc. Should be doable, but would be nice if it didn't involve as much custom tinkering as I expect it would. Andrew -- Life is a process of becoming, a combination of states we have to go through. Where people fail is that they wish to elect a state and remain in it. This is a kind of death. -- Anais Nin --- Andrew McNaughton http://www.scoop.co.nz/ [EMAIL PROTECTED] Mobile: +61 422 753 792 -- pgp encrypted mail welcome keyid: 70F6C32D keyserver: pgp.mit.edu 5688 2396 AA81 036A EBAC 2DD4 1BEA 7975 A84F 6686 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: [HEADS UP] perl symlinks in /usr/bin will be gone
On Sun, 30 Jan 2005, Matthias Andree wrote: Oliver Lehmann [EMAIL PROTECTED] writes: Anton Berezin wrote: In practical terms this will mean a one-time sweep of your scripts in order to convert them, in a typical case, from #! /usr/bin/perl to #! /usr/local/bin/perl. Wouldn't that break most of the 3rd party scripts out in the world? Hardcoded paths in scripts are a mess. What if I installed Perl into /opt/mumble on some other machine? /usr/freeware? /what/ever? Changed $PREFIX and/or $LOCALBASE? I'd say let the ports patch the right location at install time and if they break after upgrading both perl and the port, they deserve no better. Ports covers only a *very* small proportion of the perl scripts in use out there. There are for instance no end of CGI scripts and system automation scripts out there that are produced for in house use. Imagine what will be a fairly typical case: Some website owner who hired a programmer in the past to set stuff up suddenly finds their site is broken. They'll probably call their hosting provider first. The hosting provider might require all their affected customers to find someone who understands enough to fix this - which would add up to millions of dollars of expenditure worldwide if everyone took that approach. More likely, most hosting providers would put back in the symlinks that it is proposed to remove. They'll then have a 'non-standard' modification to maintain on their own systems, and this will probably be standard practice, not modifying all the scripts people want to put in. Seems like a lot of people wasting effort to me. Andrew McNaughton -- The United States is committed to the worldwide elimination of torture and we are leading this fight by example. - George Bush, 26 June 2003 --- Andrew McNaughton http://www.scoop.co.nz/ [EMAIL PROTECTED] Mobile: +61 422 753 792 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: [HEADS UP] perl symlinks in /usr/bin will be gone
On Sat, 29 Jan 2005, Chuck Swiger wrote: Oliver Lehmann wrote: Anton Berezin wrote: In practical terms this will mean a one-time sweep of your scripts in order to convert them, in a typical case, from #! /usr/bin/perl to #! /usr/local/bin/perl. Wouldn't that break most of the 3rd party scripts out in the world? Well-behaved 3rd party scripts ought to start Perl via: #! /usr/bin/env perl ...so long as /usr/local/bin is in the $PATH, they should still work fine. I commonly use this approach, but I run into some problems with flags. Probably a simple gotcha someone can help with. Eg the following useful constructs don't work: #!/usr/bin/env perl -p #!/usr/bin/env perl -T #!/usr/bin/env perl -w Andrew McNaughton -- The United States is committed to the worldwide elimination of torture and we are leading this fight by example. - George Bush, 26 June 2003 --- Andrew McNaughton http://www.scoop.co.nz/ [EMAIL PROTECTED] Mobile: +61 422 753 792 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: failure to build gcc in make world
On Thu, 22 Aug 2002, Jens Rehsack wrote: Date: Thu, 22 Aug 2002 00:33:07 +0200 From: Jens Rehsack [EMAIL PROTECTED] To: Andrew McNaughton [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Subject: Re: failure to build gcc in make world Andrew McNaughton wrote: I've worked through this more thoroughly, but I still can't get a successful make buildworld. I've thoroughly checked my source tree. I've compared all files' checksums against a known good source tree on a different system which compiles correctly (it's a later freebsd running gcc 3). Something's wrong with my build environment. You use gcc v3 to compile 4.6-STABLE? gcc version 2.95.3 [FreeBSD] 20010315 (release) I'm upgrading from 4.3-STABLE. I could install a later gcc, but I'm a little wary of moving further from a standard setup unless there's an explanation of why it should matter. The bit that's failing checks to see if it's gcc compiling itself and does different things accordingly. I presume this is about avoiding linking the new gcc against the one that's about to get over-written. Somehow this check is going wrong. If I do `CC=gcc make buildworld` then it gets past this point, but it fails later on when building libg2c. Does anyone know what might be going wrong? On Fri, 21 Jun 2002, Jens Rehsack wrote: Andrew McNaughton wrote: I've just brought my source tree up to sync with RELENG_4_6, and tried to do a make world. It fails with the following output: - cc -c -O -pipe -march=pentium -I/mnt/imac/andrew/src/gnu/lib/libgcc/../../../contrib/gcc/config -I/mnt/imac/andrew/src/gnu/lib/libgcc/../../../contrib/gcc -I. -fexceptions -DIN_GCC -D_PTHREADS -fPIC -DGTHREAD_USE_WEAK -DL_mulsi3 -o _mulsi3.o /mnt/imac/andrew/src/gnu/lib/libgcc/../../../contrib/gcc/libgcc1.c /mnt/imac/andrew/src/gnu/lib/libgcc/../../../contrib/gcc/libgcc1.c:244: `a' was not declared in this scope /mnt/imac/andrew/src/gnu/lib/libgcc/../../../contrib/gcc/libgcc1.c:244: `b' was not declared in this scope /mnt/imac/andrew/src/gnu/lib/libgcc/../../../contrib/gcc/libgcc1.c:245: syntax error before `long' *** Error code 1 Stop in /mnt/imac/andrew/src/gnu/lib/libgcc. *** Error code 1 Stop in /mnt/imac/andrew/src. *** Error code 1 Stop in /mnt/imac/andrew/src. *** Error code 1 Stop in /mnt/imac/andrew/src. - Does anyone recognise this? Can anyone tell me what is going wrong? If sth. like that hitting me, I usually delete all files which have sth. to do with that and redo a cvsup. If it's important, my system is currently running 4.3-RELEASE. Andrew McNaughton To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message -- L i W W W i Jens Rehsack LW W W L i W W W W i nnnLiWing IT-Services L iW W W Wi n n g g i W W i n n g gFriesenstraße 2 06112 Halle g g g Tel.: +49 - 3 45 - 5 17 05 91ggg e-Mail: [EMAIL PROTECTED] Fax: +49 - 3 45 - 5 17 05 92http://www.liwing.de/ -- L i W W W i Jens Rehsack LW W W L i W W W W i nnnLiWing IT-Services L iW W W Wi n n g g i W W i n n g gFriesenstraße 2 06112 Halle g g g Tel.: +49 - 3 45 - 5 17 05 91ggg e-Mail: [EMAIL PROTECTED] Fax: +49 - 3 45 - 5 17 05 92http://www.liwing.de/ To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: Releases means?
On Sun, 14 Jul 2002, Tortise@Paradise wrote: Hi I've been trying to sort out which update to download. I seek a stable version of FreeBSD. Am I correct that of the Current and Stable paths there are releases for each? ie that there are Current Releases and Stable Releases? I have downloaded releng_4_6 in the expectation it is the Stable Release. Clarity would be appreciated. With thanks in advance. David Hingston There is a current branch, and a stable branch, but those are not 'releases'. They're both moving targets which vary rapidly. every so often the stable branch is used to construct a new release. releng_4_6 gives you the latest (at present) stable release plus the critical fixes only. Andrew McNaughton To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
failure to build gcc in make world
I've just brought my source tree up to sync with RELENG_4_6, and tried to do a make world. It fails with the following output: - cc -c -O -pipe -march=pentium -I/mnt/imac/andrew/src/gnu/lib/libgcc/../../../contrib/gcc/config -I/mnt/imac/andrew/src/gnu/lib/libgcc/../../../contrib/gcc -I. -fexceptions -DIN_GCC -D_PTHREADS -fPIC -DGTHREAD_USE_WEAK -DL_mulsi3 -o _mulsi3.o /mnt/imac/andrew/src/gnu/lib/libgcc/../../../contrib/gcc/libgcc1.c /mnt/imac/andrew/src/gnu/lib/libgcc/../../../contrib/gcc/libgcc1.c:244: `a' was not declared in this scope /mnt/imac/andrew/src/gnu/lib/libgcc/../../../contrib/gcc/libgcc1.c:244: `b' was not declared in this scope /mnt/imac/andrew/src/gnu/lib/libgcc/../../../contrib/gcc/libgcc1.c:245: syntax error before `long' *** Error code 1 Stop in /mnt/imac/andrew/src/gnu/lib/libgcc. *** Error code 1 Stop in /mnt/imac/andrew/src. *** Error code 1 Stop in /mnt/imac/andrew/src. *** Error code 1 Stop in /mnt/imac/andrew/src. - Does anyone recognise this? Can anyone tell me what is going wrong? If it's important, my system is currently running 4.3-RELEASE. Andrew McNaughton To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message