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
Re: how to track stable
FreeBSD Admin wrote: Can someone point me to a clear step-by-step explanation of how to do this? I have cvsup'd the stable sources and the ports, but now what? 1. Set KERNCONF=FOO in /etc/make.conf, where FOO is the name of your kernel. 2. cvsup, you say you've done that bit. 3. # cd /usr/src # make buildworld buildkernel # mergemaster (may as well do that while build is running) # shutdown now (go to single user mode) # make installworld installkernel # reboot That should be all you need to do, it normally just works though things can go wrong. Probably best to wait a bit to see if anyone points out something blatantly obvious that I've missed. Anything important you need to do when updating should be listed in /usr/src/UPDATING, so read that. As for ports, most of them should just keep working but you can recompile your installed ports if you want. Things like lsof, if you have it installed, *will* need recompiling because it deals with the kernel very closely (same reason ps, top, etc, need to be recompiled for a new kernel). Good luck! -- Ben Smithurst / [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: Further question Re: cvsupped to RELENG_4 but got 4.3-RC
Brian D. Woodruff wrote: At 10:35 PM 4/4/01 -0400, you wrote: On Wed, Apr 04, 2001 at 09:32:39PM -0500, Brian D. Woodruff wrote: Here are my questions: 1.) is there a way to specify 4.2-STABLE, which is what I have been using? excellent answer to part 2 can anyone tell me how to get the STABLE version I want? Did you read the first sentence of that FAQ entry? "Short answer: it's just a name." If you cvsup the RELENG_4 branch, you're getting FreeBSD-stable, whether it be called -STABLE, -RC, -BETA, -FISHCAKE, -UNSTABLE-AS-HELL, or even -CURRENT if someone felt like playing an April Fool's day joke in /sys/conf/newvers.sh. :-) I would rather be consistent across my servers than have some be one release past the others. Well if it said 4.2-STABLE and you builtworld on one and not the others you still wouldn't be consistent, they'd still be different codebases but with the same name. If it _really_ bothers you just change /sys/conf/newvers.sh appropriately so your kernel reports itself as 4.2-STABLE, if all you want is the same name but different codebases. -- Ben Smithurst / [EMAIL PROTECTED] / PGP: 0x99392F7D To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: Weird files in root
Erich Zigler wrote: For some resaon this keeps appearing in / 0 lrwxr-xr-x 1 root wheel 10 Jan 9 14:49 ttyv0 - /dev/ttyv0 Anyone know why? Probably /etc/rc.devfs combined with a /dev/vga symlink pointing at nothing. Not sure how that broken symlink got there, but it was there on three of my machines.. :-/ -- Ben Smithurst / [EMAIL PROTECTED] / PGP: 0x99392F7D To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: I'll be rolling a 4.1.1 release on September 25th
Peter Radcliffe wrote: However, I don't know who the committers are, Read the handbook if you really want to know... or where they hang out. [EMAIL PROTECTED] -- Ben Smithurst / [EMAIL PROTECTED] / PGP: 0x99392F7D To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: /kernel: negative proccnt for uid = 0
Jung-an Fan wrote: Since last noon , I make world.(4.1-stable) It occured at yesterday 16:30 and repeat until now. May I ask what error is it? I've not see this kind of message since I use FreeBSD 2.2.5. This has been fixed already, as far as I know, do keep up. :-) CVSup again and rebuild your kernel (and world too just to be sure). -- Ben Smithurst / [EMAIL PROTECTED] / PGP: 0x99392F7D To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: tail -f over NFS in -stable
Ben Smithurst wrote: Fred Gilham wrote: In 4.1-stable tail -f over NFS polls rather than blocking. Yes, this is acknowledged in the kqueue() manual page. Try this patch, it seems to work for me so I might commit it if no-one objects. Scratch that, the problem is fixed in -current (kevent returns 'Operation not supported' for an NFS), so you'll just have to wait until that bit of code is MFC'd. The patch will work as a temporary fix for you though. -- Ben Smithurst / [EMAIL PROTECTED] / PGP: 0x99392F7D To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: tail -f over NFS in -stable
Fred Gilham wrote:
In 4.1-stable tail -f over NFS polls rather than blocking.
Yes, this is acknowledged in the kqueue() manual page. Try this patch,
it seems to work for me so I might commit it if no-one objects.
Index: forward.c
===
RCS file: /usr/cvs/src/usr.bin/tail/forward.c,v
retrieving revision 1.15
diff -u -r1.15 forward.c
--- forward.c 2000/07/18 19:38:38 1.15
+++ forward.c 2000/09/02 16:16:40
@@ -40,7 +40,8 @@
static char sccsid[] = "@(#)forward.c 8.1 (Berkeley) 6/6/93";
#endif /* not lint */
-#include sys/types.h
+#include sys/param.h
+#include sys/mount.h
#include sys/stat.h
#include sys/time.h
#include sys/mman.h
@@ -96,6 +97,7 @@
int action = USE_SLEEP;
struct kevent ev[2];
struct stat sb2;
+ struct statfs statfsbuf;
switch(style) {
case FBYTES:
@@ -170,7 +172,10 @@
break;
}
- if (fflag) {
+ if (statfs(fname, statfsbuf) != 0)
+ err(1, "statfs %s", fname);
+
+ if (fflag strcmp(statfsbuf.f_fstypename, "ufs") == 0) {
kq = kqueue();
if (kq 0)
err(1, "kqueue");
--
Ben Smithurst / [EMAIL PROTECTED] / PGP: 0x99392F7D
FreeBSD Documentation Project /
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-stable" in the body of the message
Re: How can I obtain -stable for previous date ?
[EMAIL PROTECTED] wrote: I'm obtain -stable (RELENG_4) every 2 days via cvsup. And do make world every time... But after Aug 20, the system became unstable ;( It locks on hard loading (hard HDD usage), like a make release or even make buildworld ;( No panic, no crashdump, nothing, full lock... Just many HDD problems after hard reboot ;( Look at the date= option in CVSup. date=[cc]yy.mm.dd.hh.mm.ss This specifies a date that should be used to select the revi- sions that are checked out from the CVS repository. The client will receive the revisions that were in effect at the specified date and time. So perhaps you want src-all date=2000.08.20.00.00.00 tag=RELENG_4 or something to get the code from midnight on the 20th August. But ideally you should try to find what is causing the problem, of course. I assume that will work anyway, I've never actually used the date option in CVSup myself. -- Ben Smithurst / [EMAIL PROTECTED] / PGP: 0x99392F7D To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: burncd...
Michael Matsumura wrote: [root:~]# ls -l /usr/share/examples/atapi/ total 0 [root:~]# ls -l /usr/src/share/examples/atapi gnuls: /usr/src/share/examples/atapi: No such file or directory I guess it was removed for 4.x since burncd was added. The burndata script is basically just: device=/dev/r$1 wormcontrol -f$device prepdisk double wormcontrol -f$device track data dd if=$2 of=$device bs=20k wormcontrol -f$device fixate 1 onp I don't know if this will help though, or even if it will work at all. I guess you'll get the same problem as this probably does similar things to burncd. -- Ben Smithurst / [EMAIL PROTECTED] / PGP: 0x99392F7D FreeBSD Documentation Project / To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: README.TXT and RELNOTES.TXT not updated before release tag?
Bruce A. Mah wrote:
I just cvsup-ed my sources this morning, and it looks to me like the
versions of README.TXT and {i386,alpha}/RELNOTES.TXT that got tagged for
RELENG_4_1_0_RELEASE still say "4.0-STABLE" rather than "4.1-RELEASE"
(at the tops of the files). Is it just me, or does someone need to do an
edit-slidetags-reroll on these?
Hmm, I see what you mean. Jordan, do these need fixing? It would
look rather silly if the CDs went out with a readme saying "4.0-stable
snapshot" or something. :-(
--
Ben Smithurst / [EMAIL PROTECTED] / PGP: 0x99392F7D
FreeBSD Documentation Project /
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-stable" in the body of the message
Re: Color ls
Matthew Hunt wrote: Does anyone know why XFree86's xterm, as shipped, doesn't set TERM to xterm-color? Is it for fear of an xterm-color entry not existing (either on the local machine, or machines you telnet/ssh to from the xterm)? ok, next question. If that's the case, why don't we change our termcap so that "xterm" and "xterm-color" are the same thing, and "xterm-mono" is there for people who _reall_ don't want color, or have a monochrome display, or whatever. It seems really dumb not to have colour by default, but perhaps there's a good reason. /me runs away for fear of annoying people by even daring to suggest this. -- Ben Smithurst / [EMAIL PROTECTED] / PGP: 0x99392F7D FreeBSD Documentation Project / PGP signature
Re: HEADS UP! Always use the 'make buildkernel' target to make yerkernels
Shawn Barnhart wrote: I guess it's not a question of finding glaring errors that seemed worthy of send-pr, but things I found misleading, confusing or outdated by "newer and better" procedures like make buildkernel. I got my commit bit by sending PRs which were as simple as typos sometimes. Go figure. :-) If you find _any_ documentation problem, it needs fixing. The first PR I committed was just a typo, too. -- Ben Smithurst / [EMAIL PROTECTED] / PGP: 0x99392F7D FreeBSD Documentation Project / PGP signature
Re: Attachments request -OOOOOPS
David Nixon wrote: Now back to your first e-mail. I mentioned the setting for vi in response to Chad R. Larson's e-mail. He specifically mentioned that he used vi for e-mail in a previous e-mail. If you go back and reread his message then you might realize why I mentioned it. I honestly ask, does Chad Larson change that setting for e-mail then change it back for other vi uses? If not, then he and everyone else who does not format their text at less that 65 characters are guilty of violating RFC 1855 (as you have quoted this group). Most people use 80 characters, which is a hell of a lot closer to 65 than your unbroken lines (or broken, depending on which way you look at it). multiple columns just for fun? Anyway, read this extract from RFC 1855 and +1+2+3+4+5+6+7+8 *** Count the splats. This line appears in Ben Smithurst's message below. How many characters per line? Hypocritical. Welcome to the guilty. Shit, I'm about 10 characters over the limit. You're a few hundred over. Nevermind, you're getting boring now. You'll be glad to know you'll get no more responses from me. *plonk* -- Ben Smithurst / [EMAIL PROTECTED] / PGP: 0x99392F7D To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: 4.0 Kernel
Jeremiah Gowdy wrote: If you go to http:///www.de.freebsd.org/de/gif/bsd/ there should be a lot of artwork to look at. They even have the famous nomad daemon on a cliff pic. --cokane For some reason my name server cannot resolve that hostname. Can you give me the IP ? Name:baerenklau.de.freebsd.org Address: 195.185.195.14 Aliases: www.de.freebsd.org -- Ben Smithurst / [EMAIL PROTECTED] / PGP: 0x99392F7D To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: 4.0 STABLE CVSUP tags?
Stan Brown wrote: Building my first 4.0 machine. Could someone please give me the tags for 4.0 STABLE, and the ports tree for it. Probably need the 4.0 security set tag also. for cvsup, src-all tag=RELENG_4 cvs-crypto tag=RELENG_4 ports-all tag=. The ports tree *never* uses a tag other than ".", it's not branched in the way the source tree is. -- Ben Smithurst / [EMAIL PROTECTED] / PGP: 0x99392F7D To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: ps, w, top and netstat problem
Jerry Bell wrote: I just tried removing the 'options PROCFS' from the kernel config and recompiled. After a reboot, I get the same thing. I ran another make buildworld and make installworld, so the ps, w, top and netstat binaries are _definately_ in sync with the kernel. I removed all compiler options during this make world. ok, I hate to ask questions which imply you're stupid, but you *did* do 'make install' in the kernel compile directory, didn't you? It's just that you've never explicitly mentioned that, and I don't know what else would cause these problems. -- Ben Smithurst / [EMAIL PROTECTED] / PGP: 0x99392F7D To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: CD problems after upgrade to 4.0
Luc Morin wrote: I also have the following entries in /dev: bash-2.03# cd /dev/ bash-2.03# ls acd* acd0a acd0c acd1a acd1c bash-2.03# ls -l cdrom lrwxr-xr-x 1 root wheel 5 Mar 19 15:58 cdrom - acd0a And the following entry in /etc/fstab: /dev/acd0c /cdrom cd9660 ro,noauto 0 0 As I write this, I notice the different references to acd0a and acd0c... what should I be using ? I've always used the 'c' partition on CDs. I don't know whether that's your problem with audio CDs, but that shouldn't affect "mount /cdrom" operation. Have I overlooked anything else? I assume the CD is detected at boot time? 'dmesg | grep acd' -- Ben Smithurst / [EMAIL PROTECTED] / PGP: 0x99392F7D To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: tun0 lost in 4.0
Sergei Vyshenski wrote: Can not revive tun0 interface after moving to 4.0 from 3.4 in a way that src/UPDATING teaches. Kernel file has "pseudo-device tun 1", kernel builds ok; ./MAKEDEV tun0 in /dev does not complain; but ifconfig says: "interface tun0 does not exist" Actually, I need tun0 to accept incoming user-ppp, and would be happy to hear of workaround at least. I have a feeling there's something funny about tun devices now, IIRC hearing they're created on demand or something... What error is ppp(8) giving you? -- Ben Smithurst / [EMAIL PROTECTED] / PGP: 0x99392F7D To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: Huge differences in suid programs ?
Brad Knowles wrote: At 10:21 AM -0700 1999/12/28, Chad R. Larson wrote: The -C option to install causes install to make a temporary copy of the "new" file in the target directory, and then does a byte-by-byte compare with the "old" one. If they're different, it deletes the old and renames the new. Sigh. It can't do the comparison with the new file in it's current location, then do the copy if they're different? That would seem to be the intelligent thing to do. You mean compare /usr/obj/usr/src/bin/sh with /bin/sh (or whatever the path is)? I don't think that would work, since /usr/obj/... files aren't stripped, and the installed versions are. -- Ben Smithurst| PGP: 0x99392F7D [EMAIL PROTECTED] | key available from keyservers and | [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
