Preferred way of going to XFree86 4.1.0
Currently running 4.3-stable with Xfree86 3x and am seriously thinking about upgrading Xfree86 4.1.0. IS there any thing I have to watch out for? A recommeneded step by step. TAI -- -- Ron Rosson... and a UNIX user said ... The InSaNe Onerm -rf * [EMAIL PROTECTED]and all was /dev/null and *void() -- Make something idiot proof, and someone will build a better idiot. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
pod2man problem persists
Hi! Though you would like to know that the make installworld problem with pod2man (part of gnu perl) posted 2 weeks ago still persists in the sources cvsupped this morning. make buildworld completes, although it coughs when going thru pod2man. A workaround is to do make install on pod2man alone in its source directory, then (re)do make installworld. Whom can I send a copy of this mail to in order to call attention of the directly responsible person to the problem? Cheers! Lucien To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: of shell, find, and (g)xargs (Re: mass uninstall all ports?)
i forgot to include this message in my last reply, so bear w/ me...
on Jul 16 11:29, i got this from Andreas...
On Thu, Jul 12, 2001 at 07:10:17PM -0400, parv wrote:
...in the end both will do the same thing: remove/delete all the
installed software as listed in /var/db/pkg. if you go the 'pkg_info'
route, you should add '-f' and or '-d' flag.
if pkg_delete/xargs/shell complain that 'pipe broken', 'too many
arguments', or some such, then you can try this...
# find /var/db/pkg -type d -execdir pkg_delete -fd {} \;
This forks a pkg_delete command for every port found, thats expensive.
Why not use find/xargs combination in this case as well ?
( cd /var/db/pkg; find . -type d | xargs pkg_delete )
Andreas ///
to give everybody else the right context, my last message was a reply
to abe, omitted from the above andreas' quoted message...
on Jul 12 18:48, i got this from abram...
I have updated the ports using cvsup. So, this:
cd /var/db/pkg pkg_delete -fd *
will remove all the packages and ports that are
installed?
I really want to understand what I'm doing here ;-)
Another person suggested I do:
pkg_info | cut -d\ -f1 | xargs pkg_delete
what is the difference between what these two commands
will do?
Abe
andreas, your 'find+xargs' script is basically same as
'pkg_info+cut+xargs', as quoted by abe above, as far as 'xargs'
is concerned. so the 'too many arguments' problem is still exists.
thus was the reason of using 'find ... -execdir ...'; i suppose i
should have noted the expense instead of intentionally omitting it.
--
so, do you like word games or scrabble?
- parv
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-stable in the body of the message
Re: bad cookie?
On Mon, 16 Jul 2001, Bill Moran wrote: Virtual Bob wrote: I got 4.3-S running on Xeon and was compiling a custom kernel. On another console, I was doing telnet and then this message suddenly popped up: Jul 16 12:43:07 kablooi /kernel: got bad cookie vp 0xc876c740 bp 0xc3394950 ... I'm suddenly getting several lines every few minutes. I searched Yahoo and FreeBSD mail list but couldn't get any results that has to do with it. What is it? It's an NFS error. What are you doing with NFS while this is going on? Wow, interesting. On my network, a 3.5-S is the NFS server exporting only /usr/src (updated every night). I looked at the dates of /bin/* etc., and see that 3.5-S's last made world was on May 6 this year. Anyway, I got this Xeon 4.3-S workstation that was compiling a custom kernel, which accesses NFS:/usr/src and it's the only time NFS would get accessed. No wonder I don't recall seeing that error before. This workstation just got brand spanking new make world this weekend. But since I just left it running on its own, I guess I never saw the error if it did appeared then. I just did a quick browse of the link provided by Mike. Looks like problems with theories vs. reality. Did NFS client code on RELENG_4 get a touch-up recently? Who's at fault here? 4.3-S NFS client or 3.5-S NFS server? - clip here with virtual scissors -- Keyboard stuck error. Press F1 to continue. Any unsolicited e-mails will be charged US$500 per e-mail, plus court cost. Your contribution to Bill Gates' personal wealth: US$359.17 To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Netscape 6 Segfaults on Startup
Hello, I'm trying to get Linux Netscape 6 to work on my 4.3-STABLE system and every time I try to run it, I get the following output: %./run-mozilla.sh ./mozilla-bin MOZILLA_FIVE_HOME=. LD_LIBRARY_PATH=./Cool:.:/usr/local/lib LIBPATH=.:./Cool SHLIB_PATH=.:./Cool XPCS_HOME=./Cool MOZ_PROGRAM=./mozilla-bin MOZ_TOOLKIT= moz_debug=0 moz_debugger= Segmentation fault This was installed from the ports collection...has anyone else had problems like this? Any help would be greatly appreciated! If you need more info, I'd be more than happy to oblige. Thanks! Scott P.S. I have tried searching the mailing list archives, but nothing like this seems to come up. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: Preferred way of going to XFree86 4.1.0
Ron 'The InSaNe One' Rosson schrieb: Currently running 4.3-stable with Xfree86 3x and am seriously thinking about upgrading Xfree86 4.1.0. IS there any thing I have to watch out for? A recommeneded step by step. # tar cf backup.tar /usr/X11R6 # rm -rf /usr/X11R6 # cd /usr/ports/x11/XFree86-4 # make install distclean Note there are additional ports, names starting with the same prefix. You probably want them, too. In addition, watch out: NVidia GeForce chipsets are currently not supported. Have fun -Christoph Sold To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: Problem with user-pppoe after upgrade, fixed
Hi, Let me make sure I've got things straight. You've upgraded to -stable and removed any ``set mtu'' or ``set mru'' lines that you've got in your ppp.conf. If this is the case, then I'm not sure what's happening. The only way I can reproduce what you're seeing in your log is if I add ``set mtu 1500'' to the configuration - which is incorrect (you can't force the link to have a 1500 byte mtu as it's physically invalid). Ok. I ran some tests on the server, from here, and I of course fried my connection. :) It's all back up now and I have the logs of the failure, so... http://anarcat.dyndns.org/ftp/pub/FreeBSD/local/info/ppp.log Also censored, properly, this time. Neal (the -questions guy :) sent me this privately: -- Looking at CVS for ppp, I noticed that the last change seemed to be MFC: Support stateful MPPE Insist on correct MRU negotiation during LCP I wonder if this would have anything to do with my problems? -- What do you think? a. -- Brian [EMAIL PROTECTED][EMAIL PROTECTED] http://www.freebsd-services.com/brian@[uk.]FreeBSD.org Don't _EVER_ lose your sense of humour ! brian@[uk.]OpenBSD.org To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: kill list signals - newsyslog (newbie question)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, Yes, you right. But I think it depends on what shell we are using. For example: su -l to root with csh shell: # kill -l HUP INT QUIT ILL TRAP ABRT EMT FPE KILL BUS SEGV SYS PIPE ALRM TERM URG STOP TSTP CONT CHLD TTIN TTOU IO XCPU XFSZ VTALRM PROF WINCH INFO USR1 USR2 and my normal login with a bash shell: [admin@ admin]$ kill -l 1) SIGHUP 2) SIGINT 3) SIGQUIT 4) SIGILL 5) SIGTRAP 6) SIGABRT 7) SIGEMT 8) SIGFPE 9) SIGKILL 10) SIGBUS 11) SIGSEGV 12) SIGSYS 13) SIGPIPE 14) SIGALRM 15) SIGTERM 16) SIGURG 17) SIGSTOP 18) SIGTSTP 19) SIGCONT 20) SIGCHLD 21) SIGTTIN 22) SIGTTOU 23) SIGIO 24) SIGXCPU 25) SIGXFSZ 26) SIGVTALRM 27) SIGPROF 28) SIGWINCH 29) SIGINFO 30) SIGUSR1 31) SIGUSR2 Why it works like that? Thanks, - -- Nuno Teixeira Dir. Técnico pt-quorum.com On Sun, 15 Jul 2001, Charles Clark wrote: I should make this question on freebsd-newbies! Probably :) look here for a list of all signals and their numbers: /usr/include/sys/signal.h On Sun, 15 Jul 2001, Tom wrote: kill -l lists all the signals and signal numbers. actually it doesn't, it just lists the signals. it does list them in order, so if you start counting at 1 you can figure it out. Also you can kill -l 30 and find that 30 is usr1, but there is no quick way to do the reverse, ie to map usr1 to 30, other than a grep USR1 from the above signal.h file. BTW, many of these numbers, especially the ones above 15, are different on other unices. For instance on Solaris, SIGUSR1 is 16. -- cmc -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.6 (FreeBSD) Comment: Made with pgp4pine 1.76 iD8DBQE7U04KjwdyCmOgT8cRAiQDAKDAJjybqY9Cuh+BAvVsXXO19RRVPQCfZpJw 7AeBvo0D1vt0n3GpQ10R7Q0= =5uSM -END PGP SIGNATURE- To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: kill list signals - newsyslog (newbie question)
your PGP signature failed to verify, btw. Nuno Teixeira wrote: su -l to root with csh shell: # kill -l HUP INT QUIT ILL TRAP ABRT EMT FPE KILL BUS SEGV SYS PIPE ALRM TERM URG STOP TSTP CONT CHLD TTIN TTOU IO XCPU XFSZ VTALRM PROF WINCH INFO USR1 USR2 and my normal login with a bash shell: [admin@ admin]$ kill -l 1) SIGHUP 2) SIGINT 3) SIGQUIT 4) SIGILL 5) SIGTRAP 6) SIGABRT 7) SIGEMT 8) SIGFPE 9) SIGKILL 10) SIGBUS 11) SIGSEGV 12) SIGSYS 13) SIGPIPE 14) SIGALRM 15) SIGTERM 16) SIGURG 17) SIGSTOP 18) SIGTSTP 19) SIGCONT 20) SIGCHLD 21) SIGTTIN 22) SIGTTOU 23) SIGIO 24) SIGXCPU 25) SIGXFSZ 26) SIGVTALRM 27) SIGPROF 28) SIGWINCH 29) SIGINFO 30) SIGUSR1 31) SIGUSR2 Why it works like that? Because the kill command is builtin to some shells (including bash and csh) and their versions of kill treat the -l flag differently. If you ran the external /bin/kill -l command the result would be the same regardless of the shell, but since these shells have their own kill function you're not running the /bin/kill program normally. -- Ben Smithurst / [EMAIL PROTECTED] PGP signature
