20031021 snapshot install has glitches
You cannot set the root password as passwd dumps core on a signal 12. I cannot mount any live filesystem CDROM since neither acd0 as acd1 seem to satisfy the installer, they both fail with a file not found error, most likely a device node. -- Jeroen Ruigrok van der Werven asmodai(at)wxs.nl / asmodai / kita no mono PGP fingerprint: 2D92 980E 45FE 2C28 9DB7 9D88 97E6 839B 2EAC 625B http://www.tendra.org/ | http://www.in-nomine.org/~asmodai/diary/ Hope and fear cannot alter the seasons... ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 20031021 snapshot install has glitches
-On [20031021 20:52], Kris Kennaway ([EMAIL PROTECTED]) wrote: On Tue, Oct 21, 2003 at 07:10:30PM +0200, Jeroen Ruigrok/asmodai wrote: You cannot set the root password as passwd dumps core on a signal 12. This indicates you're not running the right kernel. It's the kernel on the floppy images provided by the snapshot server, so if it is not the right kernel then that might be a problem on the snapshot server then. Or were you hinting at something else? -- Jeroen Ruigrok van der Werven asmodai(at)wxs.nl / asmodai / kita no mono PGP fingerprint: 2D92 980E 45FE 2C28 9DB7 9D88 97E6 839B 2EAC 625B http://www.tendra.org/ | http://www.in-nomine.org/~asmodai/diary/ How are the mighty fallen... ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Breaking old compilation paths
-On [20020504 20:15], Jeroen Ruigrok/asmodai ([EMAIL PROTECTED]) wrote: It is only here that warnings are treated as errors. I am thinking something in the upgrade path is not 100% thought out, trying to see what exactly, but my focus has been way more on STABLE than CURRENT, so some more exposed experience gladly received. Of course, the entire build complains due to WARNS being raised above 0 and NO_WERROR has not been defined. The only reference I can find in UPDATING is: 20020225: Warnings are now errors in the kernel. Unless you are a developer, you should add -DNO_WERROR to your make line. I definately do not call libiberty kernel related. Nor do we, by default, advocate NO_WERROR. So in effect, we broke moving from older versions to newer versions of CURRENT. -- Jeroen Ruigrok van der Werven / asmodai / Kita no Mono [EMAIL PROTECTED], finger [EMAIL PROTECTED] http://www.softweyr.com/asmodai/ | http://www.tendra.org/ I am, I was, and I will be... To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Breaking old compilation paths
-On [20020506 00:30], Kris Kennaway ([EMAIL PROTECTED]) wrote: On Sun, May 05, 2002 at 02:42:22PM +0200, Jeroen Ruigrok/asmodai wrote: I definately do not call libiberty kernel related. Nor do we, by default, advocate NO_WERROR. So in effect, we broke moving from older versions to newer versions of CURRENT. Can you track down what the actual cause of the breakage is? I can't immediately see why compiling on an older version should cause extra warnings, because the build should be using the up-to-date system headers and code. The libiberty Makefile sets WARNS higher than 0, which effectively [through share/mk] also sets -Werror since NO_WERROR is not defined. I would need to see if it is something libc related or something which causes the function failure. -- Jeroen Ruigrok van der Werven / asmodai / Kita no Mono [EMAIL PROTECTED], finger [EMAIL PROTECTED] http://www.softweyr.com/asmodai/ | http://www.tendra.org/ Where does the world end if the enternal optimist loses faith..? To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Odd problem with MTRR and ACPI
-On [20020504 11:45], David Malone ([EMAIL PROTECTED]) wrote: I did find some AMD errata docs which hinted at a problem involving 4MB pages, MTRR and SMM. (Search for MTRR SMM athlon ASEG on google and you should get the PDF - there are two pages describing errata involving ASEG and TSEG. Does anyone know what ASEG and TSEG are?) I tried using a kernel with DISABLE_PSE but the problem seemed to persist. However, the docs do hint at there being a link between SMM and MTRRs for the Athlon. TSEG - Time Segment ASEG - Absolute Segment Those are the ones I know are part of CPUs commonly. -- Jeroen Ruigrok van der Werven / asmodai / Kita no Mono [EMAIL PROTECTED], finger [EMAIL PROTECTED] http://www.softweyr.com/asmodai/ | http://www.tendra.org/ Once upon a midnight dreary, while I pondered, weak and weary... To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Breaking old compilation paths
So I decided it might be nice to upgrade my Nov 21 CURRENT to today's and started a make buildworld on a clean /usr/src and a /usr/obj with nothing it. After a while I get: === gnu/usr.bin/binutils === gnu/usr.bin/binutils/libiberty cc -O -g -pipe -march=pentium -Wall -D_GNU_SOURCE -I. -I/storage/src/gnu/usr.bi n/binutils/libiberty -I/storage/src/gnu/usr.bin/binutils/libiberty/../libbfd/i38 6 -I/storage/src/gnu/usr.bin/binutils/libiberty/../../../../contrib/binutils/inc lude -DHAVE_CONFIG_H -Werror -c /storage/src/gnu/usr.bin/binutils/libiberty/../ ../../../contrib/binutils/libiberty/argv.c -o argv.o cc -O -g -pipe -march=pentium -Wall -D_GNU_SOURCE -I. -I/storage/src/gnu/usr.bi n/binutils/libiberty -I/storage/src/gnu/usr.bin/binutils/libiberty/../libbfd/i38 6 -I/storage/src/gnu/usr.bin/binutils/libiberty/../../../../contrib/binutils/inc lude -DHAVE_CONFIG_H -Werror -c /storage/src/gnu/usr.bin/binutils/libiberty/../ ../../../contrib/binutils/libiberty/choose-temp.c -o choose-temp.o cc1: warnings being treated as errors /storage/src/gnu/usr.bin/binutils/libiberty/../../../../contrib/binutils/libiber ty/choose-temp.c: In function `choose_temp_base': /storage/src/gnu/usr.bin/binutils/libiberty/../../../../contrib/binutils/libiber ty/choose-temp.c:68: warning: implicit declaration of function `mktemp' *** Error code 1 Stop in /storage/src/gnu/usr.bin/binutils/libiberty. *** Error code 1 [more Error code 1's] It is only here that warnings are treated as errors. I am thinking something in the upgrade path is not 100% thought out, trying to see what exactly, but my focus has been way more on STABLE than CURRENT, so some more exposed experience gladly received. -- Jeroen Ruigrok van der Werven / asmodai / Kita no Mono [EMAIL PROTECTED], finger [EMAIL PROTECTED] http://www.softweyr.com/asmodai/ | http://www.tendra.org/ Keep your face to the sun and you will never see the shadows... To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: FreeBSD 4.5-STABLE not easily scalable to large servers ... ?
Marc, -On [20020421 00:30], Marc G. Fournier ([EMAIL PROTECTED]) wrote: Over the past week, I've been trying to get information on how to fix a server that panics with: | panic: vm_map_entry_create: kernel resources exhausted | mp_lock = 0101; cpuid = 1; lapic.id = 0100 | boot() called on cpu#1 Take a look at this: http://www.freebsd.org/cgi/getmsg.cgi?fetch=245329+248644+/usr/local/www/db/text/2001/freebsd-hackers/20010624.freebsd-hackers Hope this helps, -- Jeroen Ruigrok van der Werven / asmodai / Kita no Mono asmodai@[wxs.nl|xmach.org], finger [EMAIL PROTECTED] http://www.softweyr.com/asmodai/ | http://www.[tendra|xmach].org/ How many cares one loses when one decides not to be something but to be someone. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: make world stops...
-On [20020414 19:14], Matthias Schuendehuette ([EMAIL PROTECTED]) wrote: make: don't know how to make neqn. Stop *** Error code 2 I think David O`Brien fixed this by backing out a commit to make. In general, wait a couple of hours or a day before reporting a failure, since chances are good it has already been fixed. -- Jeroen Ruigrok van der Werven / asmodai / Kita no Mono asmodai@[wxs.nl|xmach.org], finger [EMAIL PROTECTED] http://www.softweyr.com/asmodai/ | http://www.[tendra|xmach].org/ Like cures like... To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: ATA errors on recent -current
-On [20020414 17:00], Michael Class ([EMAIL PROTECTED]) wrote: Quoting the real panic message would have been nice. ad_service (e5217c00,1,12788100,0,0) +0x36 ad_transfer (e51fcdc0) ata_start adstrategy ar_rw ar_promise_read_conf ata_raiddisk_attach ad_attach This looks a lot like the panic on boot problems fixed earlier this week. If you panic was biodone: bp 0xnumber not busy 0, update your sourcetree and try again. -- Jeroen Ruigrok van der Werven / asmodai / Kita no Mono asmodai@[wxs.nl|xmach.org], finger [EMAIL PROTECTED] http://www.softweyr.com/asmodai/ | http://www.[tendra|xmach].org/ Every revolution was first a thought in one man's mind... To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: NetBSD sort l10n: I give up!
-On [20020407 07:00], Andrey A. Chernov ([EMAIL PROTECTED]) wrote: So, I plan to remove all vestiges of NetBSD sort and ask to restore GNU sort from the Attic. Reasons are: Better option: 1) leave NetBSD sort 2) unhook from build 3) add GNU sort back for now 4) fix up NetBSD sort That you are unable doesn't mean others are unable as well. :) -- Jeroen Ruigrok van der Werven / asmodai / Kita no Mono asmodai@[wxs.nl|xmach.org], finger [EMAIL PROTECTED] http://www.softweyr.com/asmodai/ | http://www.[tendra|xmach].org/ Resolve to find thyself; and to know that he who finds himself, loses his misery... To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: NetBSD sort l10n: I give up!
-On [20020407 12:00], Andrey A. Chernov ([EMAIL PROTECTED]) wrote: On Sun, Apr 07, 2002 at 11:48:15 +0200, Jeroen Ruigrok/asmodai wrote: -On [20020407 07:00], Andrey A. Chernov ([EMAIL PROTECTED]) wrote: So, I plan to remove all vestiges of NetBSD sort and ask to restore GNU sort from the Attic. Reasons are: Better option: 1) leave NetBSD sort 2) unhook from build 3) add GNU sort back for now It is not better but the same as mine. I don't plan to remove inactive contrib stuff. That was not what you said in your initial suggestion: ``I plan to remove all vestiges of NetBSD sort'', that really sounds, to me, as if you were going to cvs rm it. So, to get it clear, it will remain in contrib? -- Jeroen Ruigrok van der Werven / asmodai / Kita no Mono asmodai@[wxs.nl|xmach.org], finger [EMAIL PROTECTED] http://www.softweyr.com/asmodai/ | http://www.[tendra|xmach].org/ And I'm learning the highs and lows of the fake promises... To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: NetBSD sort l10n: I give up!
-On [20020407 12:30], Andrey A. Chernov ([EMAIL PROTECTED]) wrote: Sorry if I was unclear, I mean functionality. Yes, it will remains in the contrib, if somebody needs it, I am not picky about inactive stuff. If you notice my second (after give up) message, I even suggest to install it under different name, if someone wants it. Tim J Robbins whipped up some code which seems to take us to the same level as GNU sort, as far as we could see. As present the GNU sort we have doesn't seem to be able to handle multibyte and/or shift states, does it? As far as he and I could see it was only 8-bit limited. And his work gives that to the NetBSD sort as well. -- Jeroen Ruigrok van der Werven / asmodai / Kita no Mono asmodai@[wxs.nl|xmach.org], finger [EMAIL PROTECTED] http://www.softweyr.com/asmodai/ | http://www.[tendra|xmach].org/ Life can only be understood backwards, but it must be lived forwards... To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: named -u bind
-On [20010804 04:30], Jun Kuriyama ([EMAIL PROTECTED]) wrote: Are there any reasons not to use -u bind flag for named by default? Last time I discussed this with some people it was said that named will have a fit if you change the interface's IP address. It apparantly cannot accomodate for this change in rebinding. Going to a chrooted and non-root-running process is where I am going to, but I will test this first before I will commit this. And people, please remember that for now I am maintaining BIND, I will never see your emails if I am not reading these lists [the signal to noise ratio is so bad I hardly get around to weed through the STABLE and CURRENT lists. Thank god I do a fast subject check with `bind' to find things like this.] -- Jeroen Ruigrok van der Werven/Asmodai asmodai@[wxs.nl|freebsd.org|xmach.org] Documentation nutter/C-rated Coder, finger [EMAIL PROTECTED] http://www.freebsd.org/doc/en_US.ISO8859-1/books/developers-handbook/ A thousand times these mysteries unfold themselves like galaxies in my head... To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: proctitle progress reporting for dump(8)
-On [20010901 23:24], Arne Dag Fidjestøl ([EMAIL PROTECTED]) wrote: You'd still need somewhere to put the status message; the dump process above has no controlling terminal. Putting it into syslog might be a bit too verbose for this? -- Jeroen Ruigrok van der Werven/Asmodai asmodai@[wxs.nl|freebsd.org|xmach.org] Documentation nutter/C-rated Coder, finger [EMAIL PROTECTED] http://www.freebsd.org/doc/en_US.ISO8859-1/books/developers-handbook/ Give me the rest to accept what I cannot change, give me the strength to change when I can, and give me the wisdom to see the difference... To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: proctitle progress reporting for dump(8)
-On [20010901 19:00], Mikhail Teterin ([EMAIL PROTECTED]) wrote: 79240 ?? S 0:06,85 dump: /dev/da0h(0): 92.44% done, finished in 0:43 (dump) Does anyone think, it is a bad idea? If no, I'll send-pr the patch... For me, dump is driven by a remote amanda and its nice to know, when it is going to be over (I have a fairly slow link to the backup server). Looks nice. Would definately be an improvement. I would like it. How often does it update the proctitle? -- Jeroen Ruigrok van der Werven/Asmodai asmodai@[wxs.nl|freebsd.org|xmach.org] Documentation nutter/C-rated Coder, finger [EMAIL PROTECTED] http://www.freebsd.org/doc/en_US.ISO8859-1/books/developers-handbook/ I dream of gardens in the desert sand... To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: proctitle progress reporting for dump(8)
-On [20010901 21:48], Garrett Wollman ([EMAIL PROTECTED]) wrote: On Sat, 1 Sep 2001 19:47:06 +0200, Jeroen Ruigrok/Asmodai [EMAIL PROTECTED] said: 79240 ?? S 0:06,85 dump: /dev/da0h(0): 92.44% done, finished in 0:43 (dump) SIGINFO! SIGINFO! SIGINFO! Heh. :) Let me elaborate your, erm, somewhat terse reply so that I understand you. You mean dump should get a signal handler for SIGINFO to print/display the current status of the application? -- Jeroen Ruigrok van der Werven/Asmodai asmodai@[wxs.nl|freebsd.org|xmach.org] Documentation nutter/C-rated Coder, finger [EMAIL PROTECTED] http://www.freebsd.org/doc/en_US.ISO8859-1/books/developers-handbook/ Someone help me, I think I've lost control... To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: HEADS UP: doc/ tree frozen (was Re: HEADS UP for /usr/src/release/doc /usr/doc)
[Crawling out of hiding again] -On [20010611 19:30], Andrey A. Chernov ([EMAIL PROTECTED]) wrote: I agree, but just imagine that I have assumption that Peter already resolve this issue with Nick (since he do repo copy) and you'll find a reason to not be extra-cautious. First lesson I learned when playing in the real world is to never assume anything get verification from anyone in writing. Besides, with source repositories one always needs to be cautious, at least in my humble opinion. No critique, just, hopefully, helpful comments. -- Jeroen Ruigrok van der Werven/Asmodai asmodai@[wxs.nl|freebsd.org|xmach.org] Documentation nutter/C-rated Coder, finger [EMAIL PROTECTED] http://www.freebsd.org/doc/en_US.ISO_8859-1/books/developers-handbook/ Conscience is God's presence in man... To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: cp -u patch
-On [20010426 23:27], Matt Dillon ([EMAIL PROTECTED]) wrote: There is a whole lot more to doing an efficient copy then simply checking the mtime. It's silly to try to integrate it into 'cp'. Use cpdup instead. plug plug plug. That's missing the point. This is for script compatibility where people idiotically depend on cp -u to be standard. But basically I don't give a flying h00t or two whether or not it enters the source tree. -- Jeroen Ruigrok van der Werven/Asmodai --=-- asmodai@[wxs.nl|freebsd.org] Documentation nutter/C-rated Coder BSD: Technical excellence at its best http://www.freebsd.org/doc/en_US.ISO_8859-1/books/developers-handbook/ Geef me die lach waarvoor je mij gewaarschuwd hebt... To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
cp -u patch
Please test this further.
This adds -u to our cp, which is a reimplemented GNU feature after Jim
Mock asked me if we supported -u in our cp.
Basically cp -u compares src and dest and only overwrites if dest's
mtime src's mtime.
Only caveat which I haven't yet solved is that it still shows dirs on
cp -Ruv copy actions, whilst it doesn't copy the directory. Solutions
welcome.
Question is, do we want to add this to our cp?
I found it handy for stuff like:
cp -Ruv mozilla mozilla-test
so that my mozilla CVS tree [not touched] only overwrites the
mozilla-test files which are older.
--
Jeroen Ruigrok van der Werven/Asmodai --=-- asmodai@[wxs.nl|freebsd.org]
Documentation nutter/C-rated Coder BSD: Technical excellence at its best
http://www.freebsd.org/doc/en_US.ISO_8859-1/books/developers-handbook/
Only in sleep can one find salvation that resembles Death...
Index: src/bin/cp/cp.1
===
RCS file: /home/ncvs/FreeBSD/src/bin/cp/cp.1,v
retrieving revision 1.16.2.2
diff -u -r1.16.2.2 cp.1
--- src/bin/cp/cp.1 2001/03/05 04:32:59 1.16.2.2
+++ src/bin/cp/cp.1 2001/04/14 11:54:01
@@ -48,7 +48,10 @@
.Op Fl H | Fl L | Fl P
.Oc
.Op Fl f | i
-.Op Fl pv
+.Oo
+.Fl v
+.Op Fl p | u
+.Oc
.Ar source_file target_file
.Nm
.Oo
@@ -56,7 +59,10 @@
.Op Fl H | Fl L | Fl P
.Oc
.Op Fl f | i
-.Op Fl pv
+.Oo
+.Fl v
+.Op Fl p | u
+.Oc
.Ar source_file ... target_directory
.Sh DESCRIPTION
In the first synopsis form, the
@@ -155,6 +161,13 @@
and either the user ID or group ID cannot be preserved, neither
the set user ID nor set group ID bits are preserved in the copy's
permissions.
+.It Fl u
+Cause
+.Nm
+to not copy the source file
+if the modification time is less than
+or equal to the modification time of the destination file,
+if it exists.
.It Fl v
Cause
.Nm
Index: src/bin/cp/cp.c
===
RCS file: /home/ncvs/FreeBSD/src/bin/cp/cp.c,v
retrieving revision 1.24
diff -u -r1.24 cp.c
--- src/bin/cp/cp.c 1999/11/28 09:34:21 1.24
+++ src/bin/cp/cp.c 2001/04/12 16:16:37
@@ -83,7 +83,7 @@
PATH_T to = { to.p_path, , };
uid_t myuid;
-int Rflag, iflag, pflag, rflag, fflag, vflag;
+int Rflag, iflag, pflag, rflag, fflag, uflag, vflag;
int myumask;
enum op { FILE_TO_FILE, FILE_TO_DIR, DIR_TO_DNE };
@@ -102,7 +102,7 @@
char *target;
Hflag = Lflag = Pflag = 0;
- while ((ch = getopt(argc, argv, HLPRfiprv)) != -1)
+ while ((ch = getopt(argc, argv, HLPRfipruv)) != -1)
switch (ch) {
case 'H':
Hflag = 1;
@@ -132,6 +132,11 @@
break;
case 'r':
rflag = 1;
+ break;
+ case 'u':
+ uflag = 1;
+ fflag = 0;
+ pflag = 0;
break;
case 'v':
vflag = 1;
Index: src/bin/cp/extern.h
===
RCS file: /home/ncvs/FreeBSD/src/bin/cp/extern.h,v
retrieving revision 1.9
diff -u -r1.9 extern.h
--- src/bin/cp/extern.h 1999/08/27 23:13:39 1.9
+++ src/bin/cp/extern.h 2001/04/12 16:07:56
@@ -42,7 +42,7 @@
extern PATH_T to;
extern uid_t myuid;
-extern int iflag, pflag, fflag, vflag, myumask;
+extern int iflag, pflag, fflag, uflag, vflag, myumask;
#include sys/cdefs.h
Index: src/bin/cp/utils.c
===
RCS file: /home/ncvs/FreeBSD/src/bin/cp/utils.c,v
retrieving revision 1.27.2.1
diff -u -r1.27.2.1 utils.c
--- src/bin/cp/utils.c 2000/10/27 16:24:22 1.27.2.1
+++ src/bin/cp/utils.c 2001/04/15 19:21:27
@@ -62,7 +62,7 @@
int dne;
{
static char buf[MAXBSIZE];
- struct stat to_stat, *fs;
+ struct stat from_stat, to_stat, *fs;
int ch, checkch, from_fd, rcount, rval, to_fd, wcount, wresid;
char *bufp;
#ifdef VM_AND_BUFFER_CACHE_SYNCHRONIZED
@@ -105,9 +105,27 @@
(void)unlink(to.p_path);
to_fd = open(to.p_path, O_WRONLY | O_TRUNC | O_CREAT,
fs-st_mode ~(S_ISUID | S_ISGID));
- } else
- /* overwrite existing destination file name */
- to_fd = open(to.p_path, O_WRONLY | O_TRUNC, 0);
+ } else {
+ if (uflag) {
+ if (fstat(from_fd, from_stat) == -1) {
+ warn(%s, entp-fts_path);
+ (void)close(from_fd);
+ return (1);
+ } else if (stat(to.p_path, to_stat) == -1) {
+ warn(%s, to.p_path);
+ (void)close(from_fd);
+
Re: FW: Filesystem gets a huge performance boost
-On [20010417 20:47], Matt Dillon ([EMAIL PROTECTED]) wrote: Testing it 'on' in stable on production systems and observing the relative change in performance is a worthy experiment. Testing it 'on' in current is just an experiment. I have been running vfs.vmiodirenable=1 on two STABLE boxes for the last week or so. Still no problems. Been doing massive cvsups and all that. This is not in combination with softupdates. That's next on the agenda. I think Dan Langille enabled it on a cvsupd server he has set up after I mentioned this sysctl to him. Dan? -- Jeroen Ruigrok van der Werven/Asmodai .oUo. asmodai@[wxs.nl|freebsd.org] Documentation nutter/C-rated Coder BSD: Technical excellence at its best D78D D0AD 244D 1D12 C9CA 7152 035C 1138 546A B867 We decide who's crazy or not... To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: FW: Filesystem gets a huge performance boost
-On [20010418 01:00], Alfred Perlstein ([EMAIL PROTECTED]) wrote: (although afaik we're basing it on both Solaris and BSD/os's implementation so... well I'm not going to bother defending it.) You just scared the shit out of me by mentioning Solaris. I've found Solaris to be a PITA with all new subsequent releases. Surely we're not aiming towards their goals where we can only run on state of the art hardware? -- Jeroen Ruigrok van der Werven/Asmodai .oUo. asmodai@[wxs.nl|freebsd.org] Documentation nutter/C-rated Coder BSD: Technical excellence at its best D78D D0AD 244D 1D12 C9CA 7152 035C 1138 546A B867 Expansion of happiness is the purpose of life... To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: FW: Filesystem gets a huge performance boost
-On [20010418 14:38], Bruce Evans ([EMAIL PROTECTED]) wrote: [vfs.vmiodirenable] So, how much slower was it? ;-) Not noticeable for me at least. -- Jeroen Ruigrok van der Werven/Asmodai --=-- asmodai@[wxs.nl|freebsd.org] Documentation nutter/C-rated Coder BSD: Technical excellence at its best http://www.freebsd.org/doc/en_US.ISO_8859-1/books/developers-handbook/ Cogito, ergo sum... To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: i586 FP optimizations hosed.
-On [20010331 05:30], John Baldwin ([EMAIL PROTECTED]) wrote: It looks like it is just broken in the SMP case. Note: I got a i586_bzero_oops on an UP box. It was invoked through the random_process and the random_kthread. -- Jeroen Ruigrok van der Werven/Asmodai .oUo. asmodai@[wxs.nl|freebsd.org] Documentation nutter/C-rated Coder BSD: Technical excellence at its best D78D D0AD 244D 1D12 C9CA 7152 035C 1138 546A B867 How the gods kill... To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: /etc/exports: 192.168.5 = 192.168.0.5
-On [20010325 09:45], Leif Neland ([EMAIL PROTECTED]) wrote: /var -alldirs -maproot=root: -network 192.168.5 -mask 255.255.255.0 But after the portmapper change, I couldn't mount, was getting permission denied. showmount -e showed 192.168.5 was being interpreted as 192.168.0.5 Changing -network to 192.168.5.0 fixed it, naturally, but the 192.168.5 used to work. You can only `compress' leading zeroes IIRC. So it should have had interpreted the .5 as 000.005, not 005.000. -- Jeroen Ruigrok van der Werven/Asmodai .oUo. asmodai@[wxs.nl|freebsd.org] Documentation nutter/C-rated Coder BSD: Technical excellence at its best D78D D0AD 244D 1D12 C9CA 7152 035C 1138 546A B867 Time will tell everything - given time... To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
vm page panic
Hi guys, ok, sources cvsupped yesterday afternoon, just before my ffs_alloc.c commit [which I did, obviously, add myself locally]. Box had been running for a while when all of a sudden it got into a panic: vm_page_alloc: free/cache page 0xc0776fa4 was dirty a trace in ddb shows: allocbuf() getblk() ffs_balloc() ffs_write() vn_rdwr() elf_coredump() coredump() Unfortunately my ata controller didn't get reprobed [just was hanging there] so I couldn't get a crashdump. =( [HPT366] So consider this a heads-up, since you might encounter this. Extra info: devfs running, / is normal FFS /tmp, /var, /usr, /storage all soft-updated. -- Jeroen Ruigrok van der Werven/Asmodai .oUo. asmodai@[wxs.nl|freebsd.org] Documentation nutter/C-rated Coder BSD: Technical excellence at its best D78D D0AD 244D 1D12 C9CA 7152 035C 1138 546A B867 Pleasure's a sin, and sometimes sin's a pleasure... To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Request for review [Re: /bin/ls patch round #2]
-On [20010320 09:09], MINOURA Makoto ([EMAIL PROTECTED]) wrote: Use standard types and functions such as wchar_t and mb*, wc* family. Which is still something which needs to be done yes. -- Jeroen Ruigrok van der Werven/Asmodai .oUo. asmodai@[wxs.nl|freebsd.org] Documentation nutter/C-rated Coder BSD: Technical excellence at its best D78D D0AD 244D 1D12 C9CA 7152 035C 1138 546A B867 The Prince of Darkness is a gentleman... To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: nos-tun multihomed machines
-On [20010316 10:43], Eugene Polovnikov ([EMAIL PROTECTED]) wrote: Please, review the following PR: http://www.freebsd.org/cgi/query-pr.cgi?pr=25847 Same patch is in the attach. Just a question, the gif interface now part of the system does tunneling as well in as much the same way as nos-tun does. Does gif work for the multihomed case? [I'll otherwise when not getting any responses dig up the answer myself.] I ask this because it serves no purpose having an IPv4-only [as far as my knowledge goes] tunnel application, whilst we have a more flexible new solution present. Translated, does gif do what nos-tun can do and more? Yes? Let's rip out nos-tun and support the other well maintained solution. -- Jeroen Ruigrok van der Werven/Asmodai .oUo. asmodai@[wxs.nl|freebsd.org] Documentation nutter/C-rated Coder BSD: Technical excellence at its best D78D D0AD 244D 1D12 C9CA 7152 035C 1138 546A B867 Don't try to find the Answer where there ain't no Question here... To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: nos-tun multihomed machines
-On [20010316 12:45], Ruslan Ermilov ([EMAIL PROTECTED]) wrote: On Fri, Mar 16, 2001 at 10:50:26AM +0100, Jeroen Ruigrok/Asmodai wrote: -On [20010316 10:43], Eugene Polovnikov ([EMAIL PROTECTED]) wrote: [gif versus nos-tun] Yes, gif(4) works the same way, and multihomed enabled (see gifconfig(8)), with the exception that it always uses the IPPROTO_IPV4 (protocol 4) for encapsulating of IPv4 payload. [gif preferred over nos-tun] I fully agree. Noted. Translated, does gif do what nos-tun can do and more? Yes? Let's rip out nos-tun and support the other well maintained solution. Except that it does not allow to use proto 94 (the default for nos-tun). I'm sure we can work something out with the KAME guys over this, if it is necessary to keep this in. *chalks up another task* -- Jeroen Ruigrok van der Werven/Asmodai .oUo. asmodai@[wxs.nl|freebsd.org] Documentation nutter/C-rated Coder BSD: Technical excellence at its best D78D D0AD 244D 1D12 C9CA 7152 035C 1138 546A B867 In the dark backward and abysm of time... To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Current SMP Kernel panics
-On [20010210 06:26], Manfred Antar ([EMAIL PROTECTED]) wrote:
APIC_IO: routing 8254 via 8259 and IOAPIC #0 intpin 0
IPsec: Initialized Security Association Processing.
panic: mutex sched lock not owned at ../../kern/kern_synch.c:175
AOL
Me too.
/AOL
166 static void
167 roundrobin(arg)
168 void *arg;
169 {
170 #ifndef SMP
171 struct proc *p = curproc; /* XXX */
172 #endif
173
174 #ifdef SMP
175 need_resched();
176 forward_roundrobin();
177 #else
178 if (p == PCPU_GET(idleproc) || RTP_PRIO_NEED_RR(p-p_rtprio.type)
)
179 need_resched();
180 #endif
181
182 callout_reset(roundrobin_callout, sched_quantum, roundrobin, NUL
L);
183 }
Should it become:
#ifdef SMP
mtx_lock_spin(sched_lock);
need_resched();
forward_roundrobin();
mtx_unlock_spin(sched_lock);
#else
?
I cannot test it yet, need to reanimate my testbox first.
--
Jeroen Ruigrok vd Werven/Asmodaiasmodai@[wxs.nl|bart.nl|freebsd.org]
Documentation nutter/C-rated Coder BSD: Technical excellence at its best
D78D D0AD 244D 1D12 C9CA 7152 035C 1138 546A B867
I'm a child of the air, I'm a witch of the wind...
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: Current SMP Kernel panics
-On [20010210 16:27], Jeroen Ruigrok/Asmodai ([EMAIL PROTECTED]) wrote: #ifdef SMP mtx_lock_spin(sched_lock); need_resched(); forward_roundrobin(); mtx_unlock_spin(sched_lock); #else This does not quite work. I don't get the panic() anymore, but now I have solve the hanging. :) Perhaps only need_resched() needs to be spinlocked. I am not sure, I am not a SMP guru. -- Jeroen Ruigrok vd Werven/Asmodaiasmodai@[wxs.nl|bart.nl|freebsd.org] Documentation nutter/C-rated Coder BSD: Technical excellence at its best D78D D0AD 244D 1D12 C9CA 7152 035C 1138 546A B867 I'm a child of the air, I'm a witch of the wind... To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Current SMP Kernel panics
-On [20010210 18:08], Alfred Perlstein ([EMAIL PROTECTED]) wrote: * Jeroen Ruigrok/Asmodai [EMAIL PROTECTED] [010210 08:24] wrote: Perhaps only need_resched() needs to be spinlocked. I am not sure, I am not a SMP guru. That looks correct, need_resched() needs sched_lock. Problem is that when I sched_lock need_resched() it just hangs and doesn't boot further. -- Jeroen Ruigrok vd Werven/Asmodaiasmodai@[wxs.nl|bart.nl|freebsd.org] Documentation nutter/C-rated Coder BSD: Technical excellence at its best D78D D0AD 244D 1D12 C9CA 7152 035C 1138 546A B867 I'm a child of the air, I'm a witch of the wind... To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Current SMP Kernel panics
-On [20010210 17:30], Jeroen Ruigrok/Asmodai ([EMAIL PROTECTED]) wrote: Perhaps only need_resched() needs to be spinlocked. I am not sure, I am not a SMP guru. To add: It needed to be spinlocked as you saw jake's commit affirmed and fixed. However I am currently hanging just after lauching the second CPU: art_init: trying /sched!st in/init SMP: CPU1 apic_initialize(): lint0: 0x00010700 lint1: 0x00010400 TPR: 0x0010 SVR: 0x01ff After that the only things I get are: Generator gate Generator gate finish after each couple of seconds. Going in ddb yields [abbreviated, no serial console]: ddb show mutex Giant @ ../../kern_intr:427 ddb show witness spinlocks: sio @ isa/sio.c:2549 sched_lock @ kern/kern_sync.c:809 clk @ i386/isa/clock.c:406 callout @ kern/kern_timeout.c:283 ithread table @ i386/isa/intr_machdep.c:587 ithread list@ kern/kern_intr.237 ap boot @ i386/i386/mp_machdep.c:2270 imen@ i386/i386/mpapic.c:261 Going out of ddb by panicing resulted in either a direct kernel trap 12 with interrupts disabled or a kernel trap 0 with interrupts disabled after which another panic led to a kernel trap 12 with interrupts disabled. The kernel trap 12 was an infinite loop. -- Jeroen Ruigrok vd Werven/Asmodaiasmodai@[wxs.nl|bart.nl|freebsd.org] Documentation nutter/C-rated Coder BSD: Technical excellence at its best D78D D0AD 244D 1D12 C9CA 7152 035C 1138 546A B867 I'm a child of the air, I'm a witch of the wind... To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: phkmalloc pam_ssh xdm
-On [2731 15:24], Alexander Leidinger ([EMAIL PROTECTED]) wrote: I rebuilded libssh.a and pam_ssh.so with this patch and I didn't get the error anymore. I haven't rebuilded the world or anything openssh related, but I think this should work (and because of the readability of pam_ssh.c and authfd.c it was easy to trace only by looking at the source... it seems using FreeBSD is the "Right Thing[TM]" :) ). It survived at least a make world here. Committed. Thanks. -- Jeroen Ruigrok vd Werven/Asmodaiasmodai@[wxs.nl|bart.nl|freebsd.org] Documentation nutter/C-rated Coder BSD: Technical excellence at its best The BSD Programmer's Documentation Project http://home.wxs.nl/~asmodai Abandon hope, all ye who enter here... To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
snes9x
I am really uncertain where to set the reply-to to. I don't read ports though. Anyways. I have been using snes9x 1.26 some time ago on my CURRENT box and everything worked ok. Today, after I updated my CURRENT this weeks from a month old to something more recent, I figured I should install snes9x again. So I installed 1.29. 'lo and behold, the colours are all crazy, lots of green. I cannot remember exactly when I last used snes9x, but my .snes96_snapshots/ directory shows february as the last savedates. I just asked some guys who are using 4-STABLE to test a ROM and with 4-STABLE, snes9x 1.29 and that same rom they see the colours as they should be. So I cannot say anything else but that CURRENT has a weird bug somewhere. So therefor I am looking for people with CURRENTs which are between january and now to install snes9x 1.29 and try the rom at http://lucifer.in-nomine.org/~asmodai/Ff5.zip And see what colours the opening screen have [that's the final fantasy logo]. I get all kinds of greens, but it should be blue IIRC. Some info about my setup: Xfree 3.3.6 on CURRENT. /usr/X11R6/bin/snes9x: libXext.so.6 = /usr/X11R6/lib/libXext.so.6 (0x280e7000) libX11.so.6 = /usr/X11R6/lib/libX11.so.6 (0x280f2000) libz.so.2 = /usr/lib/libz.so.2 (0x28192000) libstdc++.so.3 = /usr/lib/libstdc++.so.3 (0x2819f000) libm.so.2 = /usr/lib/libm.so.2 (0x281de000) libc_r.so.4 = /usr/lib/libc_r.so.4 (0x281fa000) libXThrStub.so.6 = /usr/X11R6/lib/libXThrStub.so.6 (0x282aa000) 4-STABLE: /usr/X11R6/bin/snes9x: libXext.so.6 = /usr/X11R6/lib/libXext.so.6 (0x280e7000) libX11.so.6 = /usr/X11R6/lib/libX11.so.6 (0x280f6000) libz.so.2 = /usr/lib/libz.so.2 (0x281e9000) libstdc++.so.3 = /usr/lib/libstdc++.so.3 (0x281f6000) libm.so.2 = /usr/lib/libm.so.2 (0x28234000) libc_r.so.4 = /usr/lib/libc_r.so.4 (0x2824f000) The only difference is the XThrStub, but that's the X Threaded Stub library if I can judge by its name. Ideas are welcome, I mean, could syscons influence this? -- Jeroen Ruigrok vd Werven/Asmodaiasmodai@[wxs.nl|bart.nl|freebsd.org] Documentation nutter/C-rated Coder BSD: Technical excellence at its best The BSD Programmer's Documentation Project http://home.wxs.nl/~asmodai Abandon hope, all ye who enter here... To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: snes9x
-On [2730 19:47], Brian Fundakowski Feldman ([EMAIL PROTECTED]) wrote: On Sun, 30 Jul 2000, Jeroen Ruigrok/Asmodai wrote: I cannot remember exactly when I last used snes9x, but my .snes96_snapshots/ directory shows february as the last savedates. Definitely too long ;) Yeah I know. =P Indeed it's blue on my current as of last week. Hmmm. Ideas are welcome, I mean, could syscons influence this? What color depth are you running at? I wouldn't expect that anything 16-bit or higher wouldn't work well, at least. -CURRENT usually works great for gaming for me; I'm going through, e.g., Chrono Trigger my second time now :) 16-bit, 1024x768 as I have done in the past as well. Window Maker set to its default colour allocating scheme. I'd guess something may be taking up a HUGE amount of the palette, unless you are running in 24-bit mode. If it's not that, perhaps it's the video card itself. This is a rather strange problem to have. Well, that's the whole confusing thing in this situation. Nothing changed in my configuration aside from reinstalling X and Window Maker and any supporting library. But all the configurations are still the same. And those worked before. I wish I knew where to start looking. -- Jeroen Ruigrok vd Werven/Asmodaiasmodai@[wxs.nl|bart.nl|freebsd.org] Documentation nutter/C-rated Coder BSD: Technical excellence at its best The BSD Programmer's Documentation Project http://home.wxs.nl/~asmodai Abandon hope, all ye who enter here... To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: snes9x
-On [2730 19:47], Brian Fundakowski Feldman ([EMAIL PROTECTED]) wrote: What color depth are you running at? I wouldn't expect that anything 16-bit or higher wouldn't work well, at least. -CURRENT usually works great for gaming for me; I'm going through, e.g., Chrono Trigger my second time now :) I'd guess something may be taking up a HUGE amount of the palette, unless you are running in 24-bit mode. If it's not that, perhaps it's the video card itself. This is a rather strange problem to have. I just tried twm, if something ain't a palette eater it's twm, and I get the exact same problems. A bit flickery display, with too much greens. Odd. -- Jeroen Ruigrok vd Werven/Asmodaiasmodai@[wxs.nl|bart.nl|freebsd.org] Documentation nutter/C-rated Coder BSD: Technical excellence at its best The BSD Programmer's Documentation Project http://home.wxs.nl/~asmodai Abandon hope, all ye who enter here... To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: cvs commit: src/contrib/isc-dhcp - Imported sources
-On [2629 20:03], Garrett Wollman ([EMAIL PROTECTED]) wrote: On Thu, 29 Jun 2000 10:01:25 -0700, "David O'Brien" [EMAIL PROTECTED] said: 1. Everyone uses /bin/csh (show me a box that has never had root login at least once. I can show you several boxes where first thing root did after logging in was to configure itself for a Real Shell(tm). I personally would be much happier if root's default shell were /bin/sh (as it is on all of the new non-FreeBSD boxes we have around here). Although I agree 200% with your /bin/sh statement, heck I was one of the people advocating it on -arch, I think it is time we bury this dead horse once and for all. We have had this endless discussion on -arch, -committers got rigged with it and now we're infecting -current. Please put this noise to rest. Please. -- Jeroen Ruigrok vd Werven/Asmodaiasmodai@[wxs.nl|bart.nl|freebsd.org] Documentation nutter/C-rated Coder BSD: Technical excellence at its best The BSD Programmer's Documentation Project http://home.wxs.nl/~asmodai No man is good enough to govern another man without the other's consent... To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: 'miibus_if.h' file missing for 'dc' ethernet driver
-On [2420 08:49], attila! ([EMAIL PROTECTED]) wrote: ../../pci/if_dc.c:151: miibus_if.h: No such file or directory mkdep: compile failed 'find' on entire sys subsystem fails to show it, and I pulled cvsups on 19th and 20th to see if it was in the stream --nope. pulled a 'glimpse' of 'current' list but found no reference. You _did_ add device miibus to the kernel config file did you? -- Jeroen Ruigrok vd Werven/Asmodaiasmodai@[wxs.nl|bart.nl|freebsd.org] Documentation nutter/C-rated Coder BSD: Technical excellence at its best The BSD Programmer's Documentation Project http://home.wxs.nl/~asmodai Answering the questions that no one asks... To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Summer/winter time problems with daily/460
Just went through a few logfiles: Checking for rejected mail hosts: -1d: Cannot apply date adjustment usage: date [-nu] [-d dst] [-r seconds] [-t west] [-v[+|-]val[ymwdHMS]] ... [-f fmt date | [cc]yy]mm]dd]HH]MM[.ss]] [+format] Someone more acquainted with the daily scripts may want to investigate/fix that. -- Jeroen Ruigrok vd Werven/Asmodaiasmodai@[wxs.nl|bart.nl|freebsd.org] Documentation nutter/C-rated Coder BSD: Technical excellence at its best The BSD Programmer's Documentation Project http://home.wxs.nl/~asmodai Veni, Vidi, Vici... To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: fsck_msdos
-On [2326 12:10], Kris Kennaway ([EMAIL PROTECTED]) wrote: Does anyone object to adding NetBSD's fsck_msdos to /sbin? ISTR this has come up several times in the past with positive feelings, but no-one actually did the work (it compiles trivially). I could just as easily make it a port, depending on the consensus opinion. I am not sure. I mean, I agree it is useful, however I never had the need to use something like fsck_msdos in my past 1.5-2 years, so IMHO it would be best as port. -- Jeroen Ruigrok vd Werven/Asmodaiasmodai@[wxs.nl|bart.nl|freebsd.org] Documentation nutter/C-rated Coder BSD: Technical excellence at its best The BSD Programmer's Documentation Project http://home.wxs.nl/~asmodai The descent to hell is easy... To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
DDB and dumping disk
Ok, so thanks to Brian I can at least get a good value for my swap slice by using show disk/ad0s1b. It returns that the dev_t is 0xc0b65800 Ok, so I then proceed to look at dumpdev A p dumpdev shows me that it is set to a weird value not matching my dev_t above. A p *dumpdev returns When I want to set dumpdev to the dev_t by using w dumpdev=c0b65800 or w dumpdev=c0b65800 or whatever combination will either result in `nothing written' or `symbol not found'. I am obviously doing something wrong. Help appreciated. -- Jeroen Ruigrok vd Werven/Asmodaiasmodai@[wxs.nl|bart.nl|freebsd.org] Documentation nutter/C-rated Coder BSD: Technical excellence at its best The BSD Programmer's Documentation Project http://home.wxs.nl/~asmodai The descent to hell is easy... To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: DDB and dumping disk
-On [2327 00:00], Brian Fundakowski Feldman ([EMAIL PROTECTED]) wrote: On Sun, 26 Mar 2000, Jeroen Ruigrok/Asmodai wrote: dumpdev=c0b65800 or w dumpdev=c0b65800 or whatever combination will either result in `nothing written' or `symbol not found'. Just do a "w dumpdev 0xc0b65800". You do need the 0x prefix, something I tried to hint at with the printout of show disk ;) Yeah, but I went wrong into using dumpdev= instead of just using dumpdev. Thanks, it works now. ;) -- Jeroen Ruigrok vd Werven/Asmodaiasmodai@[wxs.nl|bart.nl|freebsd.org] Documentation nutter/C-rated Coder BSD: Technical excellence at its best The BSD Programmer's Documentation Project http://home.wxs.nl/~asmodai Veni, Vidi, Vici... To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: -current, ep and fragment problems.
-On [2325 08:00], Andrew Sherrod ([EMAIL PROTECTED]) wrote: My 3.4 machine at work has periodic problems with the fxp. No performance issues (perhaps a little slow, but the network is congested enough that this is hard to measure). However it does periodically display an error message about "PHYS" and "unsupported". I am home right now, so I can't reproduce the exact message. That is unrelated to what Dan was asking. Wrt your fxp, we're working on that. -- Jeroen Ruigrok vd Werven/Asmodaiasmodai@[wxs.nl|bart.nl|freebsd.org] Documentation nutter/C-rated Coder BSD: Technical excellence at its best The BSD Programmer's Documentation Project http://home.wxs.nl/~asmodai Any fool can make a rule. And every fool will mind it... To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: -current, ep and fragment problems.
[cc:'d shin] -On [2324 00:04], Dan Moschuk ([EMAIL PROTECTED]) wrote: Is anyone else seeing odd behaviour with a fairly recent -current, an ep driver nic card and fragmented packets? Yes. And add to that a fxp card as well next to the ep card. For some weird reason (almost) every packet or datagram which gets fragmented because it is larger than the MTU will have problems. This causes tcp stalls. 80% packetloss when pinging a 3.4-S host across a WAN with a packetsize of 1600 bytes. I am using natd. Mayhaps unrelated but my firewall rules give me: 0 divert 8668 ip from any to any via fxp0 ip_fw_ctl: invalid command ipfw: setsockopt(IP_FW_ADD): Invalid argument 00100 allow ip from any to any via lo0 nowadays with my March 19th kernel/userland. A few weeks before this upgrade, when I was still 4.0-CURRENT, this whole set-up worked fine. The ep0 card which is also in this machine serves my LAN. If I try to use the cvs pserver on this box from another box (ep0 - fxp0 / 5.0 - 4.0) It will work up until a moment where nothing less of a ifconfig down/up of the ep0 driver will help. But that's different from the fxp0 case with the natd. Just to be sure: WAN---ISDN router---(natd)fxp0(daemon)ep0---3Com hub---fxp0(celestial) -- Jeroen Ruigrok vd Werven/Asmodaiasmodai@[wxs.nl|bart.nl|freebsd.org] Documentation nutter/C-rated Coder BSD: Technical excellence at its best The BSD Programmer's Documentation Project http://home.wxs.nl/~asmodai Any fool can make a rule. And every fool will mind it... To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ATA timeout errors
-On [2315 00:00], Will Saxon ([EMAIL PROTECTED]) wrote: I will continue to use ata because my drives work (albeit in PIO mode apparently) and I don't play audio off the cdrom. Some people will probably hold off on upgrading to 4.0 because of this, and I don't know if anyone important cares about that but imho it kind of looks bad. The 4.x tree will keep wd around until we either fix all the problems or until 5.x becomes mainstream. 5.x has wd removed and people following the bleeding edge are required to send in feedback and not expect it to be easy to use as it was the past year. =) -- Jeroen Ruigrok vd Werven/Asmodaiasmodai@[wxs.nl|bart.nl|freebsd.org] Documentation nutter/C-rated Coder BSD: Technical excellence at its best The BSD Programmer's Documentation Project http://home.wxs.nl/~asmodai Any fool can make a rule. And every fool will mind it... To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Panic (TCP)
-On [2221 12:01], Luigi Rizzo ([EMAIL PROTECTED]) wrote: this is fun... Just caught panic #3 on my Diablo newstransit box running 4.0 from the 7th of February. This box pushes around 360-380 GB in a weekend on network IO. this is the right kind of app for -current isn't it :) Hey you guys claim everything was limited and fixed and more stable and errr... Wait a sec, I'm part of this development. Mmm. =) Well, it's definately a good torture box for CURRENT. I was already able to get the amr driver to wedge once after which I changed something in the driver after speaking with Mike. Now to get the last few panics looked at. OBTW, is it possible to gdb -k kernel.0 vmcore.0 the files on another box, or not? -- Jeroen Ruigrok vd Werven/Asmodaiasmodai@[wxs.nl|bart.nl|freebsd.org] Documentation nutter/B-rated Coder BSD: Technical excellence at its best The BSD Programmer's Documentation Project http://home.wxs.nl/~asmodai Religion... Is the opium of the people... To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: 4.0 will ship with NODOC=YES
-On [2211 20:00], Jordan K. Hubbard ([EMAIL PROTECTED]) wrote: Unless the docs people can actually make the doc tools build again and successfully format the docs under -current. :) Sorry for what sounds like a threat of sorts, but I've been building the -current snapshots with NODOC=YES for months now because that aspect of release building just hasn't worked for ages, and if it's not fixed then I'll have little choice but to continue doing so. This will mean that no handbook/FAQ/etc get distributed as part of the doc distribution and I certainly don't see that as a good thing. JFYI! Tail end of last failure (as of this morning): === Generating temporary packing list strip /usr/local/bin/jade strip /usr/local/bin/nsgmls /usr/libexec/elf/strip: /usr/local/bin/nsgmls: No such file or directory *** Error code 1 Stop in /usr/ports/textproc/jade. *** Error code 1 Weird, since I made sure our sp port got upgraded to the last version so that it works with CURRENT. I am still not happy with some of the sp patches, but what Chuck Robey committed did what my patches also did (albeit mine were a bit cleaner ;) ). And anyways Jordan, I cannot remember you having notified -doc of your problems. So you get to get a piece of the blame yourself as well. =) -- Jeroen Ruigrok vd Werven/Asmodaiasmodai@[wxs.nl|bart.nl|freebsd.org] Documentation nutter/B-rated Coder BSD: Technical excellence at its best The BSD Programmer's Documentation Project http://home.wxs.nl/~asmodai Slow down, god can't hear you... To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Review wanted: [peter.jeremy@alcatel.com.au: docs/14530: Printed manual pages have extraneous blank first page]
-On [2205 00:01], Nik Clayton ([EMAIL PROTECTED]) wrote: -current, Peter Jeremy forwarded this to me. I'm happy to commit it, because it solves the problem. However, I don't understand the cause of the problem, so I don't know whether or not the fix is an appropriate one or not. And what is wrong with rev 1.20 of doc-common? === RCS file: /home/CVSROOT/src/contrib/groff/tmac/doc-common,v retrieving revision 1.19 Old version. With 1.20 in effect I don't have probles with the spurious pages anymore. I think the PR can just be closed with a fixed in rev 1.20 in CURRENT. According to Joerg, STABLE doesn't seem to have this problem. -- Jeroen Ruigrok vd Werven/Asmodaiasmodai@[wxs.nl|bart.nl|freebsd.org] Documentation nutter/B-rated Coder BSD: Technical excellence at its best The BSD Programmer's Documentation Project http://home.wxs.nl/~asmodai Together we stand, steel in our hands... To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: de0 driver
-On [2203 08:00], Kenneth Wayne Culver ([EMAIL PROTECTED]) wrote: It appears that the de0 driver needs to be slightly updated... just letting someone know in case nobody had noticed.. pci_compat.c and isa_compat.c contains lists of the drivers which need to be updated. We're quite aware. ;) -- Jeroen Ruigrok vd W/Asmodai asmodai@[wxs.nl|bart.nl|freebsd.org] Documentation nutter/B-rated Coder BSD: Technical excellence at its best The BSD Programmer's Documentation Project http://home.wxs.nl/~asmodai How the gods kill... To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Makefile.inc1 change
-On [2128 20:00], Warner Losh ([EMAIL PROTECTED]) wrote: In message [EMAIL PROTECTED] "David O'Brien" writes: : I like it. If it passes a clean and -DNOCLEAN buildworld, commit that : baby! OK. It passes a clean buildworld + installworld. I'll crank up the -DNOCLEAN right now. Looks like the savings aren't huge. Like 3 minutes out of 140 on my fast machine. More on my slow machine. Still 2% increase in buildworld times for a 5 line hack isn't that bad, no? All the bits help. =) And anyways, as you said, compiling it twice seems a bit unnecessary. Feel free to commit when you're sure. -- Jeroen Ruigrok vd W/Asmodai asmodai@[wxs.nl|bart.nl|freebsd.org] Documentation nutter/B-rated Coder BSD: Technical excellence at its best The BSD Programmer's Documentation Project http://home.wxs.nl/~asmodai How the gods kill... To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: cvsup current - problems with -release kernel
-On [2122 17:17], Matt M. ([EMAIL PROTECTED]) wrote: I cvsupd current, and did a make buildworld last night - i didn't do make installworld - now when i boot my system (when it is initializing the network) I get a message that is similar to "cannot allocate llinfo for /kernel" - i tried an older kernel and i got the same message. I am using DHCP, so I thought maybe there was a problem with that, and I ran /stand/sysinstall to setup my system to NOT use DHCP and rebooted. Same message. What could be the problem? make buildworld doesn't actually change any installed files or settings does it? CURRENT introduced syscall changes, signal changes and god knows what else. Apparantly you didn't see /usr/src/UPDATING. -- Jeroen Ruigrok vd W/Asmodai asmodai@[wxs.nl|bart.nl|freebsd.org] Documentation nutter/B-rated Coder BSD: Technical excellence at its best The BSD Programmer's Documentation Project http://home.wxs.nl/~asmodai Ain't gonna spend the rest of my Life, quietly fading away... To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: With feature freeze being in place
-On [2122 15:22], Nick Hibma ([EMAIL PROTECTED]) wrote: - writing manpages (or send a skeleton of to someone who will finish it) Damn right! =) - update HARDWARE.TXT - check UPDATING - replace controller with device in all manpages I think I solved most, if not all, manpages by now, also changed most disk statements to device. What needs to be done is making sure our userland tools stop depending on /dev/r* device nodes, since they aren't needed anymore. - improving manpages in general Always a good option. - FIXING PRs Always a good option. Its saddening to see it alwyas being the same people taking care of this. Even if you don't have freebsd.org access you can easily check what the originator tried on your own system and submit a follow-up saying your system (uname -a) has the same problem or not. I am busy pulling newbus manpages out of my, erhm, head. =) But I also note a lack of ata/ad manpages. I offered sos that I'd be doing them or mdoc if someone wrote the bare text. But if someone takes this task from my shoulders, I'd be happy. Also, are GENERIC and LINT in sync? Are LINT and GENERIC in sync with the manpages and vice versa? Are there tools/manpages which need to be removed but were forgotten? Check the ports tree, there's tidy, libtool, leafnode+, diablo and more ports which need updating. Some ARE NOT even the Y2k ready ports yet!!! Compile world with a memleak package and check for memleaks. Help the audit project. Make sure cross compilation works. Verify the sysinstall. Alpha support for it greatly improved. We even have booting from CD if dfr's and o`brien's stuff works! wchar support, something we NEED if we want to use OpenJade someday. Heck, it's part of the SUSv2 and C specs. Test IPv6 support! You've all been asking for it, test it. Given stream.c recent affairs, check boundschecking in code. See how we can maintain our stack and other relevant subsystems as part of the best in the world. I am also working on an up-to-date tasklist which will allow everyone to look for tasks which measure up to his or her ability and be more active on the FreeBSD project. I can't believe that Linux with its ``rabid'' users and less stable source manages to have more enthusiatic supporters in terms of fixes, additions, documentation and all that. -- Jeroen Ruigrok vd W/Asmodai asmodai@[wxs.nl|bart.nl|freebsd.org] Documentation nutter/B-rated Coder BSD: Technical excellence at its best The BSD Programmer's Documentation Project http://home.wxs.nl/~asmodai Ain't gonna spend the rest of my Life, quietly fading away... To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: This mornings make world stops at alpm.4
-On [2123 00:00], Oliver Fromme ([EMAIL PROTECTED]) wrote: Edwin Culp [EMAIL PROTECTED] wrote in list.freebsd-current: === share/man/man4 gzip -cn /usr/src/share/man/man4/ahc.4 ahc.4.gz make: don't know how to make alpm.4. Stop *** Error code 2 [...] Delete src/share/man/man4/alpm.4 The committer who deleted (moved) alpm.4 forgot to update the Makefile. This fixes it: [snip] This has been fixed. Sorry for inconvenience caused. -- Jeroen Ruigrok vd W/Asmodai asmodai@[wxs.nl|bart.nl|freebsd.org] Documentation nutter/B-rated Coder BSD: Technical excellence at its best The BSD Programmer's Documentation Project http://home.wxs.nl/~asmodai Ain't gonna spend the rest of my Life, quietly fading away... To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: error in share/man/man4
-On [2122 20:00], joanra ([EMAIL PROTECTED]) wrote: == share/man/man4 gzip -cn /usr/src/share/man/man4/ahc-4 ahc.4.gz make: don't know how to make alpm.4. Stop stop in /usr/src/share/man *** Error code 1 I fixed this a few hours after Nicholas committed. Sorry for any inconvenience. -- Jeroen Ruigrok vd W/Asmodai asmodai@[wxs.nl|bart.nl|freebsd.org] Documentation nutter/B-rated Coder BSD: Technical excellence at its best The BSD Programmer's Documentation Project http://home.wxs.nl/~asmodai Ain't gonna spend the rest of my Life, quietly fading away... To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: bzip2 in src tree (Was Re: ports/16252: bsd.port.mk: Add bzip2 support for distribution patches)
-On [2123 00:01], Akinori MUSHA aka knu ([EMAIL PROTECTED]) wrote: Yes, they are pretty big enough to see the difference between two... .tar.bz2.tar.gz lynx2.8.2rel1 1.4MB 1.8MB WindowMaeker 0.61.1 1.6MB 1.9MB gimp-1.1.13 6.2MB 8.0MB kdebase-1.1.2 7.0MB 8.9MB linux-2.2.14 12.3MB 15.2MB It's crystal clear bzip2 wins in these cases. and far enough. Then look at the memory overhead caused by bzipping versus gzipping and you'll loose. Anyways, we have had this discussion a few times in the past. Lets consult the archives and see what the reason was why we didn't do it back then. I am in favor with Chuck here. Its fine as it is, as a port. -- Jeroen Ruigrok vd W/Asmodai asmodai@[wxs.nl|bart.nl|freebsd.org] Documentation nutter/B-rated Coder BSD: Technical excellence at its best The BSD Programmer's Documentation Project http://home.wxs.nl/~asmodai Ain't gonna spend the rest of my Life, quietly fading away... To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: boot messages for pci devices...
-On [2119 08:00], Warner Losh ([EMAIL PROTECTED]) wrote: In message [EMAIL PROTECTED] Chris Piazza writes: : I *thought* I noticed it was different. I actually find this pretty : annoying because it wraps almost all of the lines and makes it difficult : to read dmesg. I don't mind them, but wouldn't object to a generic wrapping mechanism. Ditto, I like the current verbosity, and the really bootverbose stuff is WAY much more verbose than this. For me, at least, this allows easy debugging without going full verbose. That wrapping issue seems very useful indeed. At least it would structure the information a bit more orderly. -- Jeroen Ruigrok vd W/Asmodai asmodai@[wxs.nl|bart.nl|freebsd.org] Documentation nutter/B-rated Coder BSD: Technical excellence at its best The BSD Programmer's Documentation Project http://home.wxs.nl/~asmodai Peace with honour... To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Integrated Vibra16 in -current
-On [2118 04:02], Andy Sparrow ([EMAIL PROTECTED]) wrote: Given the Plug'n'Pray changes in -current, I pretty much expected to lose AWE32 support (as I can no longer use the 'pnp' commands in 'userconfig' to probe the "magic" ports for the AWE32). AWE32 here, PnPBIOS to off, and added device pcm0 and device sbc0 to my kernel config file. Works perfectly for me. Thanks Cameron! -- Jeroen Ruigrok vd W/Asmodai asmodai@[wxs.nl|bart.nl|freebsd.org] Documentation nutter/B-rated Coder BSD: Technical excellence at its best The BSD Programmer's Documentation Project http://home.wxs.nl/~asmodai I was searching through the Heavens and somehow I slipped... To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: newbye question
-On [2117 08:00], Andrey ([EMAIL PROTECTED]) wrote: Is it safe to 'make world' on a recently cvsup-ed current version while the system installed (i.e. being upgraded) is 3.4? I heard from some people, Will Andrews and George Cox, that it isn't easy. Would there be any changes in /dev entries, network configuration (i.e. drivers changed) kernel configuration, etc, that need to be made? Read /usr/src/UPDATING My question does not concern stability and possibility of crashes, but rather overall system configuration and possible conflicts with -stable... Your probably better off installing/upgrading by means of a snap. -- Jeroen Ruigrok van der Werven/Asmodai asmodai@[wxs.nl|bart.nl] Documentation nutter. *BSD: Technical excellence at its best... The BSD Programmer's Documentation Project http://home.wxs.nl/~asmodai We must all hang together, else we shall all hang separately... To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: 4.0 code freeze scheduled for Jan 15th
-On [2107 00:01], Poul-Henning Kamp ([EMAIL PROTECTED]) wrote: In message [EMAIL PROTECTED], Steve Ames writes: On the other hand, there are *plenty* of things already in 4.0 that really need to get out there and get a workout by a larger audience. Delaying *them* is a big mistake. *shudder* I really, really dislike the idea of -RELEASE actually being a wide beta so that some code can get a workout. Who said anything about -RELEASE being a beta ? Some parts of a release will always be new, but the majority of it is the same code we released as 3.X, 2.X and even 1.X. We need for people to stop thinking of FreeBSD as commercial software which comes in "natural number" style enumerable packets. While I agree with the sentiment Poul-Henning, the fact that Walnut Creek actually packages a given CVS tag as being the 4.0-RELEASE or whatever as a CD-ROM product gives it a commercial taste, no denying that. FreeBSD style is "real number", it is a continuously evolving quantity which every now and then passes a natural number on the way to infinity. We can now spot a milestone called 4.0 and that's very nice, but we are not going to stop, because the road goes on past 4.0. I think everyone knows that and acknowledges that, but the only thing I tasted from the multitude of mails I just read and evaluated was that people are satisfied with 4.0, but just want IPv6 support to be there, in it's most finished state as possible, and not some half-rushed thinghy which is there, but which is unusable. I think that that is only fair. BUT! Given Shin's RFC on his KAME patches and the answers he got, it almost looks like I was one of the very, very few to actually review his patches (until I got sick and all that). From those demanding IPv6 support in FreeBSD I have yet to see active testing and feedback to Shin. It seems people think the developers are here to do everything. Well, this is your wake-up call guys, it doesn't work that way. We only have the ability to use CVS on the sourcetree directly and we will do a lot of stuff out of ourselves, but we need the community to test, tinker and blow-up stuff and then report this back to the community with general ideas of how and what if you are not that much of a coder, or with patches if you can whoop them up. FreeBSD's Quality Assurance is something in which we all take place. Not just Walnut Creek or any of the committers. -- Jeroen Ruigrok van der Werven/Asmodai asmodai@[wxs.nl|bart.nl] Documentation nutter. *BSD: Technical excellence at its best... The BSD Programmer's Documentation Project http://home.wxs.nl/~asmodai ...fools rush in where Daemons fear to tread. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: HEADSUP: wd driver will be retired!
-On [19991209 06:59], Warner Losh ([EMAIL PROTECTED]) wrote: : P.S. I'm not trying to cut down Warner, but I do think we really need to : focus on regaining support for things we've lost in the past 6 months. I agree with this completely. The newbus excursion of the old code likely was a big mistake. We have a basically working system now, but I've not had time to focus on the new system because of the amount of time I've spent on legacy issues. Part of this is too blame on the sparse documentation available about newbus. The relevant people clued about newbus know I am working on manpages/documents to get into the basesystem. It's coming (and hopefully with less typo's as in elf.5 ;) ) -- Jeroen Ruigrok van der Werven/Asmodai asmodai@[wxs.nl|bart.nl] Documentation nutter. *BSD: Technical excellence at its best... The BSD Programmer's Documentation Project http://home.wxs.nl/~asmodai Atone me to my throes curtail... To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: HEADSUP: wd driver will be retired!
-On [19991209 12:00], Wilko Bulte ([EMAIL PROTECTED]) wrote: As Mike Smith wrote ... On Wed, Dec 08, 1999 at 10:56:24AM -0800, Mike Smith wrote: [there] were the SCSI drivers lost to CAM Actually, most of this is histrionics. CAM didn't lose us SCSI drivers; Not quite true: the esp driver for the alphas got lost. No attack on anyone, just stating a fact. Another state of fact, until no-one finds it annoying enough to fix it it will be Atticised for quite some time longer. Apparantly the people whom caused a ruckus about losing some functionality when moving to better designed new driver framework weren't quite that bothered at all. Else we would've seen submissions for those drivers to be upgraded to the new framework. Luoqi is a prime example for aic. (If my memory serves me right.) -- Jeroen Ruigrok van der Werven/Asmodai asmodai@[wxs.nl|bart.nl] Documentation nutter. *BSD: Technical excellence at its best... The BSD Programmer's Documentation Project http://home.wxs.nl/~asmodai Atone me to my throes curtail... To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: HEADSUP: wd driver will be retired!
-On [19991209 16:03], Greg Lehey ([EMAIL PROTECTED]) wrote: On Wednesday, 8 December 1999 at 20:23:24 +0100, Brad Knowles wrote: This is -CURRENT. It pains me to say it, but anyone trying to run anything "useful" on -CURRENT gets what they deserve. This is the only place where we can make clean breaks with the past, and as painful as that can be, we simply have to do that occasionally. Next month it'll be -RELEASE. This isn't the time to remove such significant functionality. If it weren't for that, I'd agree with you. Think about that some more. After that it will be 4.1. Nice to give people a driver and then rip it out when 4.1 comes when Soren fixes the last of the things people needed to have into the ata driver. I was already testing the ata driver and even procured some more info for Soren than he already had. Same goes for a bunch of other people. But the opposite goes for a lot of people. People running CURRENT to be cutting edge as in being elite with the latest FreeBSD thus get bitten. I'd say, cut loose the wd driver. (VoxWare removed would be cool too.) -- Jeroen Ruigrok van der Werven/Asmodai asmodai@[wxs.nl|bart.nl] Documentation nutter. *BSD: Technical excellence at its best... The BSD Programmer's Documentation Project http://home.wxs.nl/~asmodai Atone me to my throes curtail... To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Flash (was: Re: Sound card support)
[again subject changes] -On [19991209 16:00], Donn Miller ([EMAIL PROTECTED]) wrote: On Thu, 9 Dec 1999, Motoyuki Konno wrote: Please see Netscape plugin port (ports/www/flashplugin) to find out why we still have to need a.out support. Wow -- there's a flash plugin for Netscape? That's what I needed for a couple of web sites. Good luck using it under current. First site you hit quits netscape without reasons... ...until you drop out of X and see a __sh_getcontext IIRC warning on your console. I already mailed maintainer about this. -- Jeroen Ruigrok van der Werven/Asmodai asmodai@[wxs.nl|bart.nl] Documentation nutter. *BSD: Technical excellence at its best... The BSD Programmer's Documentation Project http://home.wxs.nl/~asmodai Atone me to my throes curtail... To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Is there any way to use ATAPI CD-R?
-On [19991209 06:58], Andrey A. Chernov ([EMAIL PROTECTED]) wrote: Do you have a plan to merge ATAPI as part of SCSI (CAM) interface as NetBSD already does? It will solve problems with all SCSI-only CD* soft automatically. I thought this was the original idea back then when work started on the new drivers. -- Jeroen Ruigrok van der Werven/Asmodai asmodai@[wxs.nl|bart.nl] Documentation nutter. *BSD: Technical excellence at its best... The BSD Programmer's Documentation Project http://home.wxs.nl/~asmodai Atone me to my throes curtail... To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: HEADSUP: wd driver will be retired!
-On [19991209 00:03], Bill Fumerola ([EMAIL PROTECTED]) wrote: On Wed, 8 Dec 1999, Soren Schmidt wrote: The same thing is about to apply to the woxware sound code, we have a new shiny system that works and is much better designed... For some definitions of "works". Low shot. If not for Cameron and Sanimura-san we would still be left dangling with the hopeless kludge of pcm vs VoxWare. They finally put their effort into something which all questions plus remarks on the topic would already have released a long time ago. -- Jeroen Ruigrok van der Werven/Asmodai asmodai@[wxs.nl|bart.nl] Documentation nutter. *BSD: Technical excellence at its best... The BSD Programmer's Documentation Project http://home.wxs.nl/~asmodai Atone me to my throes curtail... To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: mount(2) broken?
-On [19991206 00:00], Khetan Gajjar ([EMAIL PROTECTED]) wrote: On Sun, 5 Dec 1999, Garrett Wollman wrote: * Why isn't MAKEDEV installed by `make install' in a kernel compilation directory? Afaik, anyone tracking -current either knows to do this or uses a tool (like mergemaster) that does it for you (I know I do ;-) Not exactly a relevant answer to the question. There is no reason that after a new kernel or make world MAKEDEV shouldn't be upgraded/replaced by the new one. Installing MAKEDEV also won't solve these problems from what I understand unless the disk devices are re-made. Is it acceptable for MAKEDEV to be installed into /dev (at some stage of the make world, rebuild kernel and install process) and have it re-make at least the disk devices contained in /etc/fstab and /etc/amd.conf ? I don't think you want to force mknod's automatically for the same reason you don't want /etc to be overwritten by new files. Effectively: you want to have the framwork ready yet let the administrator decide when to remake the devices. Just my 0.02 Euro. -- Jeroen Ruigrok van der Werven/Asmodai asmodai@[wxs.nl|bart.nl] Documentation nutter. *BSD: Technical excellence at its best... The BSD Programmer's Documentation Project http://home.wxs.nl/~asmodai Atone me to my throes curtail... To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Compiler looping
-On [19991206 21:57], Forrest Aldrich ([EMAIL PROTECTED]) wrote: Someone recently posted a note about a compiler error (loop?) when compiling mysql. I just did buildworld/installworld from today's cvsup and still get the same problem when it goes to: c++ -DMYSQL_SERVER -DDEFAULT_MYSQL_HOME="\"/usr/local\"" -DDATADIR="\"/var/db/mysql\"" -DSHAREDIR="\"/usr/local/share/mysql\""-DHAVE_CONFIG_H -I./../include -I./../regex-I. -I../include -I.. -I. -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64 -DDBUG_OFF -O -pipe -fno-implicit-templates -c sql_yacc.cc As what said in the other mail. This is not a `loop'. The C++ compilation takes ages before it is done compiling. Just let it finish, if you are worried about resources, you can limit those per instructions in the other mail. -- Jeroen Ruigrok van der Werven/Asmodai asmodai@[wxs.nl|bart.nl] Documentation nutter. *BSD: Technical excellence at its best... The BSD Programmer's Documentation Project http://home.wxs.nl/~asmodai Atone me to my throes curtail... To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: question regarding info
-On [19991205 16:00], Jeroen Ruigrok/Asmodai ([EMAIL PROTECTED]) wrote: The problem comes when I install ports, they place info documents into /usr/local/info. And when I try to info for example libtool which is present in there it doesn't `know' about the .info file. Now. I know info can accept a longoption to specify the directories to look for, but given that the average user nowadays doesn't seem to bother to man info before looking further and that I am fairly positive that this used to work before and I wonder if something is b0rked. OK, nothing seems to be borked except that: if you decide to cleanse /usr/local and accidently rm all in info you should be well after your next make world, since the makefile targets in src/share/info/Makefile will make sure that if the file doesn't exist it will get copied (dir-tmpl to dir that is) so that it is ready to register info files. naturally if dir exists and we make world we don't want to overwrite our present dir with a copied over dir-tmpl. The `problem' (as found in mailinglist archives under install targets fail to register info files) is that if the file in question (dir) is zero-length or otherwise does not contain dir-tmpl stuff, the info files cannot register. Mayhaps this info/dir `problem' might be suitable for a FAQ entry? It will surely answer the archived questions about info files failing to install. with thanks to Peter Wemm for pointing some things out. -- Jeroen Ruigrok van der Werven/Asmodai asmodai@[wxs.nl|bart.nl] Documentation nutter. *BSD: Technical excellence at its best... The BSD Programmer's Documentation Project http://home.wxs.nl/~asmodai A pilgrim must follow in search of a shrine, as he enters inside a cathedral... To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Problem with syscons in VESA mode
-On [19991202 19:24], Maxim Sobolev ([EMAIL PROTECTED]) wrote: Tony Finch wrote: Maxim Sobolev [EMAIL PROTECTED] wrote: but sometimes when I'm building world or some other app text suddenly shifts from the edge of the screen by several spaces and all text passed to the console after that also being printed with that offset. I've seen this on -stable with standard large modes set by vidcontrol. It is interesting. Seems like it is not only VESA modes bug. Strange that nobody else observed this misbehaviour. I see exact the same behaviour. When I switch between vty's the cursor seems to move back to the position where it should've been and when I press enter the new lines start at the normal position again. This is in VESA_132x25 using: VESA: v2.0, 4096k memory, flags:0x0, mode table:0xc02cc1c8 (1a8) VESA: Tseng Labs ET6000 -- Jeroen Ruigrok van der Werven/Asmodai asmodai(at)wxs.nl The BSD Programmer's Documentation Project http://home.wxs.nl/~asmodai Network/Security SpecialistBSD: Technical excellence at its best Learn e-mail netiquette: http://www.lemis.com/email.html ...fools rush in where Daemons fear to tread. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Soundblaster 128 PCI
-On [19991201 20:01], Russell Cattelan ([EMAIL PROTECTED]) wrote: Dag-Erling Smorgrav wrote: I have a Soundblaster 128 PCI (labeled "MODEL:CT4810") which I can't get to work with newpcm. What mother board are you using? There have been some reports of the new 1371's not working with non intel chip sets. Asus boards are know to be a problem. Apparently it is a timing bug in the sound card. The timing bug, is that a PCI bus clock/signal bug which the card has, or an internal timing problem? -- Jeroen Ruigrok van der Werven/Asmodai asmodai(at)wxs.nl The BSD Programmer's Documentation Project http://home.wxs.nl/~asmodai Network/Security SpecialistBSD: Technical excellence at its best Learn e-mail netiquette: http://www.lemis.com/email.html We do not count a man's years, until he has nothing left to count... To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: More newpcm breakage
-On [19991129 19:49], Dag-Erling Smorgrav ([EMAIL PROTECTED]) wrote: My SB32 PnP, which had so far worked nicely with newpcm except for the "fast forward" bug, stopped working after the newmidi import. This means that none of my sound cards (except for the GUS PnP, which I haven't tested) work any more, and I am seriously losing faith in the authors' ability to maintain a device driver. This is CURRENT des, things are expected to not work or even break at times. And instead of just throwing out and voicing this `loss of faith' you could have taken a more active approach and try and help and see what was causing the actual problems with the not-detection of the cards. Cameron and Tanimura-san have done great work and we getting further and further where we want to go with the new sound support. The FreeBSD Project taught me that it is easy to just bitch and moan, but that the real work only comes when you help with it yourself. That's a lesson you must have learned way before I even joined helping on the project. -- Jeroen Ruigrok van der Werven/Asmodai asmodai(at)wxs.nl The BSD Programmer's Documentation Project http://home.wxs.nl/~asmodai Network/Security SpecialistBSD: Technical excellence at its best Learn e-mail netiquette: http://www.lemis.com/email.html Sometimes the Heart wanders in fantasies, keeping the mind in its power constantly... To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: cpu name
-On [19991120 04:01], Byung Yang ([EMAIL PROTECTED]) wrote: as I see the source code, it is not doing what it is supposed to do.. any suggestions? (it's not a big deal but still it's a bug) I did not modify any of the source codes. I think someone else suggested lowering the optimisation level. Have you tried that yet? -- Jeroen Ruigrok van der Werven/Asmodai asmodai(at)wxs.nl The BSD Programmer's Documentation Project http://home.wxs.nl/~asmodai Network/Security SpecialistBSD: Technical excellence at its best ...in this world nothing is certain but death and taxes. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: libvgl - status and perspectives
-On [19991106 04:01], Andrzej Bialecki ([EMAIL PROTECTED]) wrote: Today I noticed accidentally that either libvgl is broken, or the demo program does something wrong - the mouse cursor doesn't move. But this brings more general question regarding console graphics library. As it is today, libvgl is almost useless due to very limited set of functions. There were discussions whether to port SVGAlib or GGI. Do you know if someone is working/planning to work on it? libggi has more support for FreeBSD than svgalib has and it also seems to be preferred over svgalib due to security hassles and all that. So you might want to try that route. -- Jeroen Ruigrok van der Werven/Asmodai asmodai(at)wxs.nl The BSD Programmer's Documentation Project http://home.wxs.nl/~asmodai Network/Security SpecialistBSD: Technical excellence at its best In every stone sleeps a crystal... To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: QIC ft0 driver support in 4.0-CURRENT gone?
On [19991016 04:00], jack ([EMAIL PROTECTED]) wrote: Today Julian Elischer wrote: hey If someone did adopt it then it wouldn't be a problem.. if no-on edoes then it can remain 'unsupported' unsupported != tucked away in the attic, out of reach of many/most users. Current != platform for users. Anyone tracking CURRENT should know how to use Attic. -- Jeroen Ruigrok van der Werven/Asmodai asmodai(at)wxs.nl The BSD Programmer's Documentation Project http://home.wxs.nl/~asmodai Network/Security SpecialistBSD: Technical excellence at its best Millions for defence but not one cent for tribute. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Call for projects
Since no-one except Poul-Henning gave a start with this I thought I might try my hand at this. Given FreeBSD's rapid development over the last year a lot of things around the releases have changed. Nik Clayton and his team are doing a terrific job to keep up with the documentation. However, what has been lacking, at least in my opinion, is the lack of alerting less advanced, more time-restrained, however you wish to call it, hackers of tasks which need to be fixed in FreeBSD. The PR system is nice and works pretty well [thanks to a lot of people] but it is not what I meant with my above words. What I did mean though, is that when someone messes with source code at large in FreeBSD to let the hacker/developer-community know of these changes plus point out some areas which need to be fixed/looked-out with these patches in place. Small-term projects. Also, put out more patches on either -hackers or -current [depending on what platform the patches aim at] and call for more test reviews to eliminate more and more initial bugs upon introducing. Plus, let the doc guys know what changes have been made and in which places the docs should be altered. Doesn't take much, but remember that not every docperson is a kernel hacker and vice versa, so UTSL, how well intended doesn't always help in these cases. All of this is merely a call for clearer communication between the diverse efforts within the project as a whole and external hackers with no access to the repository but who wish to send-pr diffs/patches to fix up forgotten/neglected/overseen areas in the code. Thanking you all in advance for helping on this. It's together we make this project work... -- Jeroen Ruigrok van der Werven/Asmodai asmodai(at)wxs.nl The BSD Programmer's Documentation Project http://home.wxs.nl/~asmodai Network/Security SpecialistBSD: Technical excellence at its best Any fool can make a rule And every fool will mind it. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
more
Just a question, who changed more's behaviour? On this CURRENT of 3-4 weeks old I can do /blah and then use / to find the next occurance of blah in the same file. With the `new' more this behaviour has been barfed. Wonder why and who... -- Jeroen Ruigrok van der Werven/Asmodai asmodai(at)wxs.nl The BSD Programmer's Documentation Project http://home.wxs.nl/~asmodai Network/Security SpecialistBSD: Technical excellence at its best There is no greater sorrow than to recall, in misery, the time when we were happy. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: more
* Tim Vanderhoek ([EMAIL PROTECTED]) [990912 17:50]: On Sun, Sep 12, 1999 at 03:20:02PM +0200, Jeroen Ruigrok/Asmodai wrote: On this CURRENT of 3-4 weeks old I can do /blah and then use / to find the next occurance of blah in the same file. With the `new' more this behaviour has been barfed. Accidentally. I didn't notice that particular (mis?)-feature when reading the older code. I'll re-add it. You can, of course, also use "n" in the meantime. *nod* That's ok. I was merely curious as to the why. I am used to using it, but I can easily adopt myself to using `n'. Just wonder who else wants this behaviour to stay away and come back. It's not like I am emotionally attached to it =) Of course, one really wonders why we need "/\n" to be a synonym for "n", but I hadn't meant to change this behaviour. That's ok =) Cheers, -- Jeroen Ruigrok van der Werven/Asmodai asmodai(at)wxs.nl The BSD Programmer's Documentation Project http://home.wxs.nl/~asmodai Network/Security SpecialistBSD: Technical excellence at its best Millions for defense but not one cent for tribute. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: make world failure (signal 11 in cpp)
* Greg Lehey ([EMAIL PROTECTED]) [990826 06:19]: On Wednesday, 25 August 1999 at 23:39:56 -0400, John W. DeBoskey wrote: === cpp cc -O -pipe -I/usr/src/gnu/usr.bin/cc/cpp/../../../../contrib/egcs/gcc -I/usr/src/gnu/usr.bin/cc/cpp/../../../../contrib/egcs/gcc/config -DFREEBSD_NATIVE -DHAVE_CONFIG_H -DDEFAULT_TARGET_VERSION=\"egcs-2.91.66\" -DDEFAULT_TARGET_MACHINE=\"i386-unknown-freebsd\" -I/usr/obj/usr/src/gnu/usr.bin/cc/cpp/../cc_tools -I/usr/src/gnu/usr.bin/cc/cpp/../cc_tools -DPREFIX=\"/usr\" -I/usr/obj/usr/src/tmp/usr/include -c /usr/src/gnu/usr.bin/cc/cpp/../../../../contrib/egcs/gcc/cccp.c yacc -o cexp.c /usr/src/gnu/usr.bin/cc/cpp/../../../../contrib/egcs/gcc/cexp.y *** Signal 11 The canonical explanation for this sort of thing is processor or memory problems. Would that fit? Could I think, but... Last time I had that when making a week/two week old CURRENT to the current CURRENT I got sig 11's on all my compiles. I had to install a snapshot cc in order to rebuilt libc and cc and then make world again. Everything compiled core dumped with the first compiler. After reinstalling cc, no more problems. So compliers and Sig 11's are harder to troubleshoot, at least IMHO. HTH, -- Jeroen Ruigrok van der Werven asmodai(at)wxs.nl The BSD Programmer's Documentation Project http://home.wxs.nl/~asmodai Network/Security SpecialistBSD: Technical excellence at its best Man shall not live by bread alone. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Q: Extending the sysctl MIB for Linuxulator variables
* Doug ([EMAIL PROTECTED]) [990817 03:40]: In case anyone cares I'd like to put in a vote for compat.linux. From the design standpoint this balances the needs of prominence and clean top level name space nicely. Count me as another in favor of Mike's explanation. Like Mike said, there were a few mistakes already at the top, and IMHO linux ABI stuff doesn't justify a top-level assignment since in fact it's a remapping of Linux calls to FreeBSD equivalent calls, not a true implementation of Linux. So compat.* sounds way more sensible to shim- like implementations. Just my 0.02 euro's. -- Jeroen Ruigrok van der Werven asmodai(at)wxs.nl The BSD Programmer's Documentation Project http://home.wxs.nl/~asmodai Network/Security SpecialistBSD: Technical excellence at its best Take thy beak from out my heart and take thy form from off my door! To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Audio notice
Hi, before the newbus changes I used to get a ton of: Sorry, read DMA channel unavailable. Now playing mp3's under CURRENT from yesterday I only get about three of those messages per 10 minutes. That's better ;) cheers! -- Jeroen Ruigrok van der Werven asmodai(at)wxs.nl The BSD Programmer's Documentation Project http://home.wxs.nl/~asmodai Network/Security SpecialistBSD: Technical excellence at its best Cum angelis et pueris, fideles inveniamur. Quis est iste Rex gloriae...? To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Library question/challenge
* John Polstra ([EMAIL PROTECTED]) [990731 09:28]: Jeroen Ruigrok/Asmodai wrote: * John Polstra ([EMAIL PROTECTED]) [990729 18:49]: Right. So the problem must be that you have LD_LIBRARY_PATH set. Yes I have, but this hasn't been a problem for the last 5-6 months. In what way could it interfere with my ldconfig then? (I read man 1aout ld) It won't intefere with ldconfig, but it will affect what the dynamic linker does. If you have "/usr/lib" in your LD_LIBRARY_PATH then the dynamic linker will find libc there, rather than in "/usr/lib/aout" as it should. Ah, ok, I was thinking in the wrong direction. The main reason I stuck LD_LIBRARY_PATH in there is because of Qt. If ldconfig paths are configured ok, will these replace LD_LIBRARY_PATH or would I have to adjust Makefiles/configures in order to point to the libraries present on this system? I don't know why it didn't cause problems for you earlier. Well, I am glad it broke... Because else I would still be using this. This was netscape, right? If so, there's an easy fix. The command that you execute for netscape is really a shell script which does some stuff and then executes a big binary somewhere else. You could add "unset LD_LIBRARY_PATH" to that shell script to work around the problem. Mayhaps, but I would rather tackle the whole of this challenge instead of just a subset. I mean if this LD_LIBRARY_PATH I set is a bad thing to do I want to learn the ways how to best do it instead. -- Jeroen Ruigrok van der Werven asmodai(at)wxs.nl The BSD Programmer's Documentation Project http://home.wxs.nl/~asmodai Network/Security SpecialistBSD: Technical excellence at its best Cum angelis et pueris, fideles inveniamur. Quis est iste Rex gloriae...? To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Panic plus advice needed
* Greg Lehey ([EMAIL PROTECTED]) [990731 03:50]: On Saturday, 31 July 1999 at 0:19:27 +0200, Jeroen Ruigrok/Asmodai wrote: * Greg Lehey ([EMAIL PROTECTED]) [990730 11:23]: On Friday, 30 July 1999 at 8:45:32 +0200, Jeroen Ruigrok/Asmodai wrote: The first thing you should do with any dump is a backtrace (bt). The appearance depends on how you got there. Since you appear to have gone via ddb, your dump should look something like this: (kgdb) bt #0 0xc0155f14 in boot () #1 0xc0156249 in panic () #2 0xc01e737b in ffs_mapsearch () #3 0xc01e5cea in ffs_alloccg () #4 0xc01e5756 in ffs_hashalloc () #5 0xc01e4adc in ffs_alloc () #6 0xc01e7af0 in ffs_balloc () #7 0xc01f0a5c in ffs_write () #8 0xc01827ce in vn_write () #9 0xc01623ac in dofilewrite () #10 0xc01622bb in write () #11 0xc0225066 in syscall () #12 0xc02192b6 in Xint0x80_syscall () #13 0x807d24a in ?? () #14 0x807666d in ?? () Hmm, that doesn't look like a dump from ddb. Did you have DDB_UNATTENDED set? No, just options DDB. This bt was obtained after doing gdb -k kernel.0 vmcore.0 I still have the DDB trace on paper which I can type in if needed/wanted. What you do with the results depends a lot on what you find. On the whole, I wouldn't think it worth the pain of debugging without symbols. No it isn't... I just made world and am building two kernels now (one with and one without debug info) so that the next time something happens like that I am prepared. Thanks anyways for the help Greg, this will surely help some parts of the PDP, hope I get some stuff in there about this sort of thing today. 'gards, -- Jeroen Ruigrok van der Werven asmodai(at)wxs.nl The BSD Programmer's Documentation Project http://home.wxs.nl/~asmodai Network/Security SpecialistBSD: Technical excellence at its best Cum angelis et pueris, fideles inveniamur. Quis est iste Rex gloriae...? To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
An oddity after a panic
Thanks to you all for the hints and tips... I finally solved it by wanting to run fsck again before messing around with fsdb and stat. I shutdown'd, went into single user mode, fsck'd my slice and the problem got fixed. H, gotta love FFS =) Thanks 'gain, -- Jeroen Ruigrok van der Werven asmodai(at)wxs.nl The BSD Programmer's Documentation Project http://home.wxs.nl/~asmodai Network/Security SpecialistBSD: Technical excellence at its best Cum angelis et pueris, fideles inveniamur. Quis est iste Rex gloriae...? To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Panic plus advice needed
* Greg Lehey ([EMAIL PROTECTED]) [990730 11:23]: On Friday, 30 July 1999 at 8:45:32 +0200, Jeroen Ruigrok/Asmodai wrote: I started a make world on my box last night and then proceeded to go to bed. When I looked at my console this morning it had sprung into DDB because of a panic: ffs_alloccg: map corrupted. The first question is: do you have a kernel with debug symbols? If not, gdb isn't going to help you much. bde can do it with ddb (though it's a bit late if you have the dump), but mere mortals are in trouble without symbols. I thought I had one, but alas I didn't. *sigh* One of those days when ye bump against stuff you should've done. Learned from that in a multiple ways, so next time I got everything I need... The first thing you should do with any dump is a backtrace (bt). The appearance depends on how you got there. Since you appear to have gone via ddb, your dump should look something like this: Here is at least some info: (kgdb) bt #0 0xc0155f14 in boot () #1 0xc0156249 in panic () #2 0xc01e737b in ffs_mapsearch () #3 0xc01e5cea in ffs_alloccg () #4 0xc01e5756 in ffs_hashalloc () #5 0xc01e4adc in ffs_alloc () #6 0xc01e7af0 in ffs_balloc () #7 0xc01f0a5c in ffs_write () #8 0xc01827ce in vn_write () #9 0xc01623ac in dofilewrite () #10 0xc01622bb in write () #11 0xc0225066 in syscall () #12 0xc02192b6 in Xint0x80_syscall () #13 0x807d24a in ?? () #14 0x807666d in ?? () Think I'll read up on GDB in my printed manual... Other hints/tips still welcome, I still have the dumps =) -- Jeroen Ruigrok van der Werven asmodai(at)wxs.nl The BSD Programmer's Documentation Project http://home.wxs.nl/~asmodai Network/Security SpecialistBSD: Technical excellence at its best Cum angelis et pueris, fideles inveniamur. Quis est iste Rex gloriae...? To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Panic plus advice needed
Hi, I started a make world on my box last night and then proceeded to go to bed. When I looked at my console this morning it had sprung into DDB because of a panic: ffs_alloccg: map corrupted. This panic occured on a box running pretty stable (at least panic less for the last past 4-8 weeks). I got show registers and trace information from DDB and also a crashdump. Now I am wanting to use GDB to get more relevant information from the crashdump. I have the GDB manual here, but could use some advice from people who've done this under FreeBSD before and could inform me of any things that are somewhat obligatory to look at under FreeBSD. If you want I can type in the DDB stuff later this day, but work awaits my presence first. Thanks for any advice. -- Jeroen Ruigrok van der Werven asmodai(at)wxs.nl The BSD Programmer's Documentation Project http://home.wxs.nl/~asmodai Network/Security SpecialistBSD: Technical excellence at its best Cum angelis et pueris, fideles inveniamur. Quis est iste Rex gloriae...? To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
An oddity after a panic
Hi, I was cleansing /usr/obj after a panic to see if I could reproduce it and I have this slight oddity: [root@daemon:/usr/obj] (32) # rm -rf work/ rm: work/FreeBSD/src/gnu/usr.bin/: Directory not empty rm: work/FreeBSD/src/gnu: Directory not empty rm: work/FreeBSD/src: Directory not empty rm: work/FreeBSD: Directory not empty rm: work/: Directory not empty [note I already did chflags] [root@daemon:/usr/obj] (33) # cd work/FreeBSD/src/gnu/usr.bin/ [root@daemon:/usr/obj/work/FreeBSD/src/gnu/usr.bin] (34) # ll total 2 1 drwxr-xr-x 3 root wheel - 512 Jul 30 08:31 ./ 1 drwxr-xr-x 3 root wheel - 512 Jul 30 08:31 ../ [root@daemon:/usr/obj/work/FreeBSD/src/gnu/usr.bin] (35) # cd .. [root@daemon:/usr/obj/work/FreeBSD/src/gnu] (36) # ll total 3 1 drwxr-xr-x 3 root wheel - 512 Jul 30 08:31 ./ 1 drwxr-xr-x 3 root wheel - 512 Jul 30 08:33 ../ 1 drwxr-xr-x 3 root wheel - 512 Jul 30 08:31 usr.bin/ I have no idea what's wrong here. After the panic however I did get some softupdates inconsistencies, such as: DUPs, Block counts, even an internal error: dups with -p. I'd love to hear some ideas about how to solve this. -- Jeroen Ruigrok van der Werven asmodai(at)wxs.nl The BSD Programmer's Documentation Project http://home.wxs.nl/~asmodai Network/Security SpecialistBSD: Technical excellence at its best Cum angelis et pueris, fideles inveniamur. Quis est iste Rex gloriae...? To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
make.conf on CURRENT question
Hi, just a couple of questions: compat22=yes in /etc/make.conf accomplishes a.out support which we need for netscape support. Correct? What does compat3x do however? Provide ELF compatibility libraries for programs written for 3.x? Also. Suppose I have an ELF CURRENT box that never ran a.out. If I want a.out support from a make world I would need to uncomment compat22=yes in /etc/make.conf, correct in assuming this? Thanks for the time taken to answer this, -- Jeroen Ruigrok van der Werven asmodai(at)wxs.nl The BSD Programmer's Documentation Project http://home.wxs.nl/~asmodai Network/Security SpecialistBSD: Technical excellence at its best Cum angelis et pueris, fideles inveniamur. Quis est iste Rex gloriae...? To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Library question/challenge
* Matthew Dillon ([EMAIL PROTECTED]) [990729 07:20]: lib/libc.so.3: minor version -1 older : than expected 0, using it anyway : ld.so failed: bad magic number in "/usr/lib/libc.so.3" : : This is netscape4.5 on CURRENT tracked since October 1998. : : /var/run/ld.so.hints: : search directories: /usr/lib/aout:/usr/lib/compat/aout: :/usr/X11R6/lib/aout:/usr/local/lib/aout : : [ it has about 66 libs in this hints file ] This happened to me. The problem is usually that the library it is looking for is simply missing from /usr/lib/aout or /usr/X11R6/lib/aout. Another possibility is that there may be old softlinks laying around /usr/lib or /usr/X11R6/lib for that library which are pointing to nowhere. I will have to see about the softlinks. Well, it seems to want libc.so.3.1 and that one is present in /usr/lib/aout and is grepable from ldconfig -aout -r: [asmodai@daemon:/usr/home/asmodai] (3) $ ldconfig -aout -r | grep libc.so 27:-lc.3.1 = /usr/lib/aout/libc.so.3.1 See if you can find where those aout/ compatibility libraries are. Either you have them properly installed and the ldconfig_paths in /etc/rc.conf (defaults in /etc/defaults/rc.conf) are wrong, or you do not have them installed. My aout ldconfig path is the /etc/defaults/rc.conf one, I always sync /etc after a make world using mergemaster most of the time. In /usr/lib/aout there's a libc.so.3.1 but it is dated March the 20th. But given the fact that it ran good until now it should still be good I guess. One person also pointed out in another later post of mine that I forgot -DWANT_AOUT during make world, this might have caused problems. So I am trying a make world with -DWANT_AOUT as well. I am also going to build XFree 3.3.4.x just to be sure it's not that as well. Thanks for the suggestions, -- Jeroen Ruigrok van der Werven asmodai(at)wxs.nl The BSD Programmer's Documentation Project http://home.wxs.nl/~asmodai Network/Security SpecialistBSD: Technical excellence at its best Cum angelis et pueris, fideles inveniamur. Quis est iste Rex gloriae...? To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Library question/challenge
* John Polstra ([EMAIL PROTECTED]) [990729 07:20]: Run ldd on the netscape binary and figure out why it's finding the wrong libc. Make sure you don't have LD_LIBRARY_PATH set to include "/usr/lib". Well, I needed to update netscape anyways, so I rm'd the old binaries and proceeded to install navigator46. I even got these errors I mentioned during install of navigator. I am going to try some of what Matthew wrote [see other follow-up]. thanks for the suggestion, -- Jeroen Ruigrok van der Werven asmodai(at)wxs.nl The BSD Programmer's Documentation Project http://home.wxs.nl/~asmodai Network/Security SpecialistBSD: Technical excellence at its best Cum angelis et pueris, fideles inveniamur. Quis est iste Rex gloriae...? To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Library question/challenge
[ in case this should've been -questions, please redirect this thread there ] Hi, after a make world on the 26th I tried to start netscape today and got a library error: /usr/libexec/ld.so: warning: /usr/lib/libc.so.3: minor version -1 older than expected 0, using it anyway ld.so failed: bad magic number in "/usr/lib/libc.so.3" This is netscape4.5 on CURRENT tracked since October 1998. One change since my previous builds is that I uncommented compat22 and compat3x prior to making world. I have the default aout ld path in /etc/defaults/rc.conf, none in /etc/rc.conf. A ldconfig -aout -r | head -2 yields: /var/run/ld.so.hints: search directories: /usr/lib/aout:/usr/lib/compat/aout: /usr/X11R6/lib/aout:/usr/local/lib/aout [ it has about 66 libs in this hints file ] I also get the above error when trying to install a newer netscape. Can it be I need to rebuild my XFree? I currently run 3.3.3.1 compiled under ELF and with a.out support AFAIK, else I couldn't have been running netscape before. Timestamp of /usr/X11r6/lib/aout is July 21st. /usr/lib/aout is dated March 20th /usr/lib/compat/aout is July 26th /usr/local/lib/aout is empty Anything you guys can think of, want to inspect, want me to test, because I cannot see where it goes wrong exactly. Thanks, -- Jeroen Ruigrok van der Werven asmodai(at)wxs.nl The BSD Programmer's Documentation Project http://home.wxs.nl/~asmodai Network/Security SpecialistBSD: Technical excellence at its best Cum angelis et pueris, fideles inveniamur. Quis est iste Rex gloriae...? To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: whereis broken?
* Sheldon Hearn ([EMAIL PROTECTED]) [990725 20:29]: On Sun, 25 Jul 1999 14:12:53 -0400, Dan Moschuk wrote: whereis anything yields.. Warning: couldn't stat file /usr/local/lib/perl5/5.00502/man! Staleness. Unfortunately, the whereis(1) manpage doesn't tell you to look at the manpath(1) manpage. Do so now and you'll see that you should check your /etc/manpath.config and your $MANPATH environment variable. Prolly didn't use mergemaster after making world eh Dan? ;) -- Jeroen Ruigrok van der Werven asmodai(at)wxs.nl The BSD Programmer's Documentation Project http://home.wxs.nl/~asmodai Network/Security SpecialistBSD: Technical excellence at its best Cum angelis et pueris, fideles inveniamur. Quis est iste Rex gloriae...? To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: loads of SetAttrs in cvsup of cvs repo
* Mark Huizer ([EMAIL PROTECTED]) [990705 02:47]: I did change the cvsup server some time ago, but I'm now back at cvsup.nl.FreeBSD.org hey! that's my queue! when did it start to happen? If it was last week, then there might have been some cause in the upgrading of the machine to 3.2, or it might involve softupdates. That was once last week, which made sense to me after you told me you upgraded cvsup.nl. I think Wilko must have suffered from the same `problem'. regards, -- Jeroen Ruigrok van der Werven asmodai(at)wxs.nl The BSD Programmer's Documentation Project http://home.wxs.nl/~asmodai Network/Security SpecialistBSD: Technical excellence at its best Cum angelis et pueris, fideles inveniamur. Quis est iste Rex gloriae...? To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: General feeling on merging APIs...
* Warner Losh ([EMAIL PROTECTED]) [990627 09:02]: In message [EMAIL PROTECTED] "Justin T. Gibbs" writes: : The hope is to provide a consistent interface across : all *BSDs which is why I've addressed this to all of the *BSD projects. More generally, I'd like to identify areas where the kernel APIs of the various projects have diverged and see what, if anything, can be done about them. I'd also like to get commitment from the various controlling bodies of the *BSD projects to a statement something along the lines of: Nice to see interest about this, it means a lot to me that the three BSD's, all with their own fun in use, etc, are willing to work together on this goal. Also, what I am doing with the PDP (here he goes again) is that I am trying to determine which BSD got which function where and in what version. Would make an excellent reference for people wanting to get something running on all three BSD's. (btw, ignore any FreeBSD words in the PDP, I am currently making it *BSD.) We support the identification of API differences between the various BSDs. We generally support the idea of merging the APIs, but reserve the right to veto anything too radical. Sounds like a nice stance, however (not saying you did Warner) it _is_ absolutely fundamental that we, as the three BSD's speaking, put back ego's where it's technical excellence that counts. Private agenda's never served someone. So I myself am counting on the maturity of the participants to discuss technical internals and not moving to ego-talk. Note, this isn't about merging all the three BSD's back together. It's merely about making the API not too diverse/different from each other. (together we stand, divided we fall - cliche, but true) To clue in the OpenBSD people who haven't been reading tech-kern of NetBSD, it started when I pointed out to Bill Sommerfeld that FreeBSD already had an asleep function, which he was about to implement. A good function, but substantially different from FreeBSD's asleep, that I didn't think it was a good idea to just let Bill continue without warning him at least, as well as Matthew Dillon (original writer of FreeBSD's asleep()). Can we say at least, that the core 4.4BSD functions have remained largely/ almost the same across the 3 BSD's? Can we point out at least a few areas in which we differ? Are there differences spotted at hand which can be resolved on short time? I've been trying to put together some compatibility shims for newconfig drivers in FreeBSD's new-bus world and have run accross a number of minor differences that would be trivial to fix. That sounds like a good thing Warner. Any more to tell about this wrt NetBSD and OpenBSD? Looking forward to hear from the lot of you, -- Jeroen Ruigrok van der Wervenasmodai(at)wxs.nl The *BSD Programmer's Documentation Project Network/Security Specialist http://home.wxs.nl/~asmodai *BSD: We are back and will not accept no... To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Suspend/resume hooks
* Warner Losh ([EMAIL PROTECTED]) [990627 09:02]: [Excuse my posting this to multiple lists, but I cannot let this go unnoticed] In message [EMAIL PROTECTED] Allen Briggs writes: : Ideally, there should be no more unnecessary divergence of the APIs--it : would also be nice to work toward removing any API differences that there : are now (no matter where they came from, what discussions have taken place, : or what body parts have been scorched in the past). I know that's a lot : easier said than done, but I'd be surprised if this isn't what most : people would like to see. Allen, you are correct. I think that there's a lot to benefit any three of the BSD's from the other. I know that I'm working on newconfig shims for FreeBSD's new-bus system and am running into many stupid, trivial errors in doing that... I'd like to see these areas minimized where it makes sense and it technical and politically possible to do so. I couldn't agree more on that Warner. If there is interest in cataloging these differences and trying to resolve them, I hereby volunteer to setup mailing lists to facilitate that process. Like I said, I was already busy doing that, albeit slowly, but getting there eventually... Also, a few BSD developers have already been dabbling in userland synchronisation and are still doing that, albeit, as I said before, slowly. It would be nice if NetBSD's core and FreeBSD's core would approve, in principle, a statement that says that they generally support reduction in the differences in API between the two systems, but resolution of said differences will be handled on a case by case basis. And OpenBSD's core. Basically, a "we like the idea in principle, but we'll reserve the right to veto anything that is too radical." True, that's the best approach, but like I pointed out in another mail, we need to be careful not to bring out old things. Let the past just be the past and concentrate on the future in which this, the API cleanup/ synchronisation, will play an important role. Since I'm not a member of either core group, I'm not sure what the best way to proceed here would be. The only comparable `projects' I can name in this aspect Warner, is the Linux Standard Base, POSIX, and the Single Un*x Specification. http://www.linuxbase.org http://www.opengroup.org/austin Comments? You got my support Warner, actually you took my ideas a little further, I was merely documenting the differences, and you want to get them straightened out as much as possible. I don't think any core-team can deny the importance of a somewhat consistent base API (on multiple areas) in order to keep porting from FreeBSD to NetBSD, or from OpenBSD to FreeBSD to a minimum fuzz. This could also allow us to try to create a driver system that would make exchanging device drivers a breeze. And that would benefit us all... -- Jeroen Ruigrok van der Wervenasmodai(at)wxs.nl The *BSD Programmer's Documentation Project Network/Security Specialist http://home.wxs.nl/~asmodai *BSD: We are back and will not accept no... To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
RE: Protocol analyzer
On 03-May-99 Chuck Robey wrote: If you've EVER used tcpdump, go take a look at this site, I guarantee it's worth your time: http://www.capmedia.fr/mgall/xip/ What a GREAT idea! A full graphical tcpdump! Damn, another project down the wastebasket =P --- Jeroen Ruigrok van der Wervenasmodai(at)wxs.nl The FreeBSD Programmer's Documentation Project Network/Security Specialist http://home.wxs.nl/~asmodai *BSD: Powered by Knowledge Know-how http://www.freebsd.org To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
RE: Protocol analyzer
On 03-May-99 Chuck Robey wrote: If you've EVER used tcpdump, go take a look at this site, I guarantee it's worth your time: http://www.capmedia.fr/mgall/xip/ What a GREAT idea! A full graphical tcpdump! Also has some probs compiling... Looking at it... Might be nice to have in the ports *chuckle* --- Jeroen Ruigrok van der Wervenasmodai(at)wxs.nl The FreeBSD Programmer's Documentation Project Network/Security Specialist http://home.wxs.nl/~asmodai *BSD: Powered by Knowledge Know-how http://www.freebsd.org To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: Our routed - Vern says it's old and buggy.
On 28-Apr-99 Kris Kennaway wrote: On Tue, 27 Apr 1999, Garrett Wollman wrote: Most importantly: - Recent values of GateD are distributed under a very unfriendly license. There's also zebra, in ports (as someone pointed out on -net the other day),which seems to be GPL'ed. I haven't tried either of the two except to poke around briefly in the code.. Well, I can tell you this: the source code last time I was able to check it (which was about a week, week and a half ago) compiles cleanly under 2.2.8-4.x (where else did ye think those mentions on the site came from? ;) and also works as far as I have been able to test it. (People with better test environments than mine are MORE THAN WELCOME to test the routing code!) Thankfully I got Andreas Klemm on the list as well to test the source and we have been very active in reporting back bugs and submitting patches and Kunihiro-san has been very flexible with releasing snapshots for the ports as well as maintaining a ports directory within the total package for ease of use within FreeBSD. So for a Linux dude he has a very strong sympathy for FreeBSD =) --- Jeroen Ruigrok van der Wervenasmodai(at)wxs.nl The FreeBSD Programmer's Documentation Project Network/Security Specialist http://home.wxs.nl/~asmodai *BSD: Powered by Knowledge Know-how http://www.freebsd.org To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Some questions about booting with newbus
Some questions I have pertaining the newbus stuff (and as a reminder to you Peter, thanks for looking into it): Am I the only one where booting with -v doesn't really do any verbose booting? Also, as talked about with Peter, -v should report unclaimed/unmatched devices, currently it doesn't... Also, I am trying to work up a driver here, but have only a list of vendor ID's for the PCI bus, anyone have a textfile with some more ID's such as the classes, etc..? Thanks, --- Jeroen Ruigrok van der Wervenasmodai(at)wxs.nl The FreeBSD Programmer's Documentation Project Network/Security Specialist http://home.wxs.nl/~asmodai *BSD: Powered by Knowledge Know-how http://www.freebsd.org To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
RE: WORLD fails at rpcsvc
On 11-Apr-99 S. Akmentins-Teilors wrote: I've repeatedly cleared obj, clobbered, and whatnot. This has been a problem here for the last two days. Last cvsup was midnight PST on 11 Apr. === rpcsvc rpcgen -C -h -DWANT_NFS3 /usr/src/include/rpcsvc/key_prot.x -o key_prot.h /usr/src/gnu/usr.bin/cc/cpp/../../../../contrib/egcs/gcc/cccp.c:1882: Internal compiler error in function main *** Error code 33 Please browse back on the list, since we've covered this twice or thrice already. short version: rebuild /usr/src/lib first, then /usr/src/gnu/usr.bin/cc, then make world again, and mayhaps again. Also read UPDATING in /usr/src --- Jeroen Ruigrok van der Werven http://www.freebsdzine.org asmodai(at)wxs.nlThe idea does not replace the work... Network/Security Specialist http://home.wxs.nl/~asmodai *BSD: Powered by Knowledge Know-how http://www.freebsd.org To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
RE: thread-safe libgcc
On 11-Apr-99 Luoqi Chen wrote: For threaded applications to work correctly, we need a thread-safe version of libgcc. It is straight forward to build: define _PTHREADS in CFLAGS. We can have both versions just like libc and libc_r, and use the thread-safe version when linking threaded applications. If no one objects, I will add it to our tree and make necessary changes to gcc to use it. By all means, please do. Since GTk+ or Gnome likes threads as well, and a lot more Linux apps do as well... --- Jeroen Ruigrok van der Werven http://www.freebsdzine.org asmodai(at)wxs.nlThe idea does not replace the work... Network/Security Specialist http://home.wxs.nl/~asmodai *BSD: Powered by Knowledge Know-how http://www.freebsd.org To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
