From owner-freebsd-current Sun Jan 28 13:38:21 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id NAA02830 for current-outgoing; Sun, 28 Jan 1996 13:38:21 -0800 (PST) Received: from ibp.ibp.fr (ibp.ibp.fr [132.227.60.30]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id NAA02805 for ; Sun, 28 Jan 1996 13:38:13 -0800 (PST) Received: from blaise.ibp.fr (blaise.ibp.fr [132.227.60.1]) by ibp.ibp.fr (8.6.12/jtpda-5.0) with ESMTP id WAA29953 for ; Sun, 28 Jan 1996 22:38:05 +0100 Received: from (uucp@localhost) by blaise.ibp.fr (8.6.12/jtpda-5.0) with UUCP id WAA11987 for freebsd-current@FreeBSD.ORG; Sun, 28 Jan 1996 22:38:04 +0100 Received: (from roberto@localhost) by keltia.freenix.fr (8.7.3/keltia-uucp-2.7) id WAA23462 for freebsd-current@FreeBSD.ORG; Sun, 28 Jan 1996 22:28:23 +0100 (MET) From: Ollivier Robert Message-Id: <199601282128.WAA23462@keltia.freenix.fr> Subject: lpt0 incorrect interrupt count / systat To: freebsd-current@FreeBSD.ORG (FreeBSD Current Users' list) Date: Sun, 28 Jan 1996 22:28:21 +0100 (MET) X-Operating-System: FreeBSD 2.2-CURRENT ctm#1586 X-Mailer: ELM [version 2.4ME+ PL3 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.ORG Precedence: bulk Hi, Two (well three) things: - I'm seeing a weird interrupt count (much too high) for lpt0 since a few days... interrupt total rate clk0 irq0 334008 114 rtc0 irq8 374530 128 fdc0 irq6 1 0 sc0 irq1 6724 2 sio0 irq4 5880 2 sio1 irq3 8193 2 lpt0 irq7 665828 227 ep0 irq10 22 0 Total 1395186 476 The printer is of course inactive and even turned off. Where do these interrupts come from ? I recently changed my NE2000 for a 3C509B; can this be the cause of the problem ? eisa0: Probing for devices on the EISA bus eisa0:1 unknown device [...] 1 3C5x9 board(s) on EISA found at 0x1000 1 3C5x9 board(s) on ISA found at 0x300 ep0 at 0x300-0x30f irq 10 on isa ep0: aui/utp[*AUI*] address 00:20:af:5a:51:9d irq 10 - the 3C509B is unusable when configured as an EISA device Jan 28 20:21:16 keltia /kernel.3com: 1 3C5x9 board(s) on EISA found at 0x1000 Jan 28 20:21:16 keltia /kernel.3com: ep0: 3c5x9 at 0x1000 in test mode. Erase pencil mark! Jan 28 20:21:16 keltia /kernel.3com: ep0: eeprom failed to come ready. Jan 28 20:21:16 keltia /kernel.3com: epprobe: ignoring model ffff Jan 28 20:21:16 keltia /kernel.3com: ep0 not found at 0x1000 I have modified if_ep.c with the latest Serge's patches after merging -CURRENT's differences and it changes nothing. I can use the card only in pure ISA mode. PnP doesn't make any difference. - I have wired down my SCSI devices on my two SCSI controllers and I've used the sd11 notation for the second disk on the second controller and "systat -vmstat" shows the devices like the following, masking the full sdNN name. I guess systat should be modified but is there someone with the same setup who has already done that ? Discs sd0 sd3 sd1 sd1 cd1 fd1 intrn controller eisa0 controller bt0 controller ahb0 controller scbus0 at bt0 controller scbus1 at ahb0 # BT: conner + quantum + tandberg + hp disk sd0 at scbus0 target 0 unit 0 disk sd1 at scbus0 target 1 disk sd2 at scbus0 target 2 disk sd3 at scbus0 target 3 tape st1 at scbus0 target 4 tape st0 at scbus0 target 5 device cd0 at scbus0 target 6 # 1742: seagate + micropolis + CD disk sd10 at scbus1 target 0 disk sd11 at scbus1 target 1 disk sd12 at scbus1 target 2 disk sd13 at scbus1 target 3 -- Ollivier ROBERT -=- The daemon is FREE! -=- roberto@keltia.frmug.fr.net FreeBSD keltia.freenix.fr 2.2-CURRENT #1: Sun Jan 14 20:23:45 MET 1996 From owner-freebsd-current Sun Jan 28 14:10:20 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id OAA04494 for current-outgoing; Sun, 28 Jan 1996 14:10:20 -0800 (PST) Received: from ref.tfs.com (ref.tfs.com [140.145.254.251]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id OAA04489 for ; Sun, 28 Jan 1996 14:10:18 -0800 (PST) Received: (from julian@localhost) by ref.tfs.com (8.6.12/8.6.9) id OAA02244; Sun, 28 Jan 1996 14:09:28 -0800 From: Julian Elischer Message-Id: <199601282209.OAA02244@ref.tfs.com> Subject: Re: lpt0 incorrect interrupt count / systat To: roberto@keltia.freenix.fr (Ollivier Robert) Date: Sun, 28 Jan 1996 14:09:28 -0800 (PST) Cc: freebsd-current@FreeBSD.ORG In-Reply-To: <199601282128.WAA23462@keltia.freenix.fr> from "Ollivier Robert" at Jan 28, 96 10:28:21 pm X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-current@FreeBSD.ORG Precedence: bulk untraceable interrupts get assigned to irq7 My guess is that your new ethernet card is generating interrrupts sometimes that are too short (or you clear the interrupt before it is serviced soemtimes (a lot actually) and they become "untraceable" and are caught by the lpt driver... it's a hardware "feature" in the PC. > - I'm seeing a weird interrupt count (much too high) for lpt0 since a few > days... > > interrupt total rate > lpt0 irq7 665828 227 > > The printer is of course inactive and even turned off. Where do these > interrupts come from ? I recently changed my NE2000 for a 3C509B; can this > be the cause of the problem ? From owner-freebsd-current Sun Jan 28 15:07:05 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id PAA09313 for current-outgoing; Sun, 28 Jan 1996 15:07:05 -0800 (PST) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id PAA09308 for ; Sun, 28 Jan 1996 15:07:03 -0800 (PST) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id QAA01815; Sun, 28 Jan 1996 16:04:07 -0700 From: Terry Lambert Message-Id: <199601282304.QAA01815@phaeton.artisoft.com> Subject: Re: writes still slower than before recent vm changes To: bde@zeta.org.au (Bruce Evans) Date: Sun, 28 Jan 1996 16:04:06 -0700 (MST) Cc: current@FreeBSD.org In-Reply-To: <199601280713.SAA31441@godzilla.zeta.org.au> from "Bruce Evans" at Jan 28, 96 06:13:13 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.org Precedence: bulk > Bonnie reports that writes are 30%-50% slower than 2 weeks ago. However, > iozone reports that writes are slightly faster than 2 weeks ago. The > only significant difference between iozone writes and bonnie writes is > that iozone writes are page-aligned while bonnie writes aren't. Not > page aligning the buffers is stupid but shouldn't have such a large > penalty. Do either of them pre-create the file? If the file is precreated, a read must occur before a write can take place. The only "real" fix I can see for this would be to modify the cache to allow I/O in smaller than page-sized chunks, perhaps using a bitmap to indicate valid 512b chunks of a 4k page. This would at least reduce the amount of read required for a write. I don't know exactly what can be done about non-aligned boundries, though for a non alinged read of 512b or less, we are guaranteed 1/4 of the amount needed to read. This is still an improvement. I don't know how this would be impacted by a non-512b dev_bsize, nor how it should be altered to deal with the issue of frags. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-current Sun Jan 28 17:15:02 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id RAA16409 for current-outgoing; Sun, 28 Jan 1996 17:15:02 -0800 (PST) Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id RAA16379 for ; Sun, 28 Jan 1996 17:14:52 -0800 (PST) Received: from sax.sax.de by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id CAA28315 for ; Mon, 29 Jan 1996 02:14:47 +0100 Received: by sax.sax.de (8.6.11/8.6.12-s1) with UUCP id CAA13924 for freebsd-current@FreeBSD.org; Mon, 29 Jan 1996 02:14:47 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.7.3/8.6.9) id BAA05488 for freebsd-current@FreeBSD.org; Mon, 29 Jan 1996 01:56:08 +0100 (MET) From: J Wunsch Message-Id: <199601290056.BAA05488@uriah.heep.sax.de> Subject: Re: cvs commit: src/sys/scsi worm.c To: freebsd-current@FreeBSD.org (FreeBSD-current users) Date: Mon, 29 Jan 1996 01:56:08 +0100 (MET) Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199601290009.BAA04550@uriah.heep.sax.de> from "J Wunsch" at Jan 29, 96 01:09:07 am X-Phone: +49-351-2012 669 X-Mailer: ELM [version 2.4 PL23] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-current@FreeBSD.org Precedence: bulk As J Wunsch wrote: > > Since the NAME##init()'s are external, i assume they are used > elsewhere, not inside /sys/scsi. I've botched my yesterday fix by > declaring worminit() static. Corrected this half an hour ago. Well, config(8) seems to be supposed to create the prototypes in ioconf.h (and presumable use them in ioconf.c), but i have yet to figure out how to arrange this... Even rebuilding config and re-configing the test kernel didn't help. sdinit() and all the other things were there, worminit() not. What am i doing wrong? -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-current Sun Jan 28 17:48:07 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id RAA17739 for current-outgoing; Sun, 28 Jan 1996 17:48:07 -0800 (PST) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id RAA17637 Sun, 28 Jan 1996 17:47:55 -0800 (PST) Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.9/8.6.9) id MAA02742; Mon, 29 Jan 1996 12:46:57 +1100 Date: Mon, 29 Jan 1996 12:46:57 +1100 From: Bruce Evans Message-Id: <199601290146.MAA02742@godzilla.zeta.org.au> To: dyson@freebsd.org Subject: i/o speed is OK now Cc: current@freebsd.org Sender: owner-current@freebsd.org Precedence: bulk Bonnie now reports an improvement since Jan 14 for all cases. Bruce -------Sequential Output-------- ---Sequential Input-- --Random-- -Per Char- --Block--- -Rewrite-- -Per Char- --Block--- --Seeks--- Machine MB K/sec %CPU K/sec %CPU K/sec %CPU K/sec %CPU K/sec %CPU /sec %CPU before 128 1334 97.8 3095 42.8 1238 26.8 1507 97.8 3357 46.0 52.7 7.2 after(1) 128 1407 98.2 3104 37.7 1094 19.4 960 56.2 1664 22.4 55.0 6.9 after(2) 128 1399 97.7 3314 41.1 1444 27.9 1558 97.5 2379 30.0 59.3 7.5 after(3) 128 1398 97.2 3351 45.8 1400 29.4 1565 98.1 3639 48.6 59.1 7.5 before: kernel-Jan14 after(1): kernel-Jan20 after(2): kernel-Jan28 after(3): kernel-Jan29 (current) System: CPU: i486DX (486-class CPU) real memory = 16777216 (16384K bytes) ... bt0: Bt44xC/ 0-(32bit) bus (bt0:3:0): "QUANTUM XP34301 102C" type 0 fixed SCSI 2 sd1(bt0:3:0): Direct-Access 4106MB (8410200 512 byte sectors) From owner-freebsd-current Sun Jan 28 17:58:16 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id RAA18180 for current-outgoing; Sun, 28 Jan 1996 17:58:16 -0800 (PST) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id RAA18166 Sun, 28 Jan 1996 17:57:42 -0800 (PST) Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.9/8.6.9) id MAA03073; Mon, 29 Jan 1996 12:54:31 +1100 Date: Mon, 29 Jan 1996 12:54:31 +1100 From: Bruce Evans Message-Id: <199601290154.MAA03073@godzilla.zeta.org.au> To: dyson@freebsd.org Subject: too many cached pages for profiled kernel Cc: current@freebsd.org Sender: owner-current@freebsd.org Precedence: bulk I booted a profiling kernel by mistake and was surprised when it was extremely slow because of heavy swapping. The profile buffers take 1.7MB and `Cache' takes 2.5MB so an 8MB system was reduced to < 4MB. I've never seen so much memory allocated for `Cache' before, and the same profiling kernel runs normally (without anything in `Cache') on a 16MB system. `68Kout' in the top output should be formatted better. Bruce load averages: 0.14, 0.14, 0.09 09:57:13 19 processes: 1 running, 18 sleeping Cpu states: 1.4% user, 0.0% nice, 18.8% system, 4.8% interrupt, 74.9% idle Mem: 272K Active, 12K Inact, 3360K Wired, 2488K Cache, 509K Buf, 60K Free Swap: 33M Total, 6736K Used, 27M Free, 20% Inuse 68Kout PID USERNAME PRI NICE SIZE RES STATE TIME WCPU CPU COMMAND 217 bde 30 0 292K 264K RUN 0:01 5.33% 3.05% top 215 root 10 0 844K 28K wait 0:00 5.47% 0.76% 164 bde 10 0 844K 28K wait 0:01 0.77% 0.57% 218 root 18 0 136K 20K pause 0:00 0.00% 0.00% 119 root 18 0 236K 12K pause 0:00 0.00% 0.00% 26 root 18 0 140K 12K pause 0:00 0.00% 0.00% 163 bde 10 0 844K 28K wait 0:03 0.00% 0.00% 1 root 10 0 180K 12K wait 0:00 0.00% 0.00% 108 root 10 0 144K 12K nfsidl 0:00 0.00% 0.00% 109 root 10 0 144K 12K nfsidl 0:00 0.00% 0.00% 107 root 10 0 144K 12K nfsidl 0:00 0.00% 0.00% 106 root 10 0 144K 12K nfsidl 0:00 0.00% 0.00% 165 root 3 0 156K 20K ttyin 0:00 0.00% 0.00% 166 root 3 0 156K 20K ttyin 0:00 0.00% 0.00% 97 daemon 2 0 176K 16K select 0:00 0.00% 0.00% 124 root 2 0 480K 12K accept 0:00 0.00% 0.00% 121 root 2 0 192K 12K select 0:00 0.00% 0.00% 112 root 2 0 192K 12K select 0:01 0.00% 0.00% --- 2 users Load 0.21 0.17 0.10 Mon Jan 29 09:58 Mem:KB REAL VIRTUAL VN PAGER SWAP PAGER Interrupts Tot Share Tot Share Free in out in out 240 total Act 2068 1020 432 56 2484 count 3 99 clk0 irq0 All 6136 4016 1484 308 pages 3 127 rtc0 irq8 cow fdc0 irq6 Proc:r p d s w Csw Trp Sys Int Sof Flt zfod 14 wdc0 irq14 2 4 21 13 7 244 10 11 3384 wire sc0 irq1 248 act sio1 irq3 3.3%Sys 0.7%Intr 0.3%User 0.0%Nice 95.7%Idl 72 inact ed0 irq15 | | | | | | | | | | 2428 cache == 60 free daefr Namei Name-cache Proc-cache prcfr Calls hits % hits % 11 react 10 pdwake 2408 pdpgs Discs fd1 wd0 intrn seeks 3 528 buf xfers 3 blks 7 msps 7.3 From owner-freebsd-current Sun Jan 28 21:57:54 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id VAA05845 for current-outgoing; Sun, 28 Jan 1996 21:57:54 -0800 (PST) Received: from time.cdrom.com (time.cdrom.com [192.216.222.226]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id VAA05836 for ; Sun, 28 Jan 1996 21:57:51 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by time.cdrom.com (8.6.12/8.6.9) with SMTP id VAA17707 for ; Sun, 28 Jan 1996 21:57:46 -0800 To: current@freebsd.org Subject: Please test this on your system (and see if you crash) Date: Sun, 28 Jan 1996 21:57:46 -0800 Message-ID: <17705.822895066@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-current@freebsd.org Precedence: bulk Yes, this program may hose you. It hoses me, so be careful trying it out. Its function is to allow anyone in group wheel to execute commands as arbitrary users and it should be run setuid to root. In 2.1 it works fine, in 2.2 I get a very strange lock-up which may just be me, thus this email for confirmation. Thanks! Jordan ---- #include #include #include #include #define WHEEL_GID 0 extern int errno; main (argc, argv, envp) int argc; char *argv[]; char *envp[]; { char *shell, *name; struct passwd *ent; char **av = argv; char ps1[128]; gid_t gids[NGROUPS]; int i, ng, ac = argc; if ((ng = getgroups(NGROUPS, gids)) < 0) { perror("getgroups"); return 1; } for (i = 0; i < ng; i++) if (gids[i] == WHEEL_GID) break; if (i == ng) { fprintf(stderr, "Sorry, you are simply not studly enough to run this program!\n"); return 1; } if ((argc > 1) && (argv[1][0] == '-')) { name = av[1] + 1; sprintf(ps1, "PS1=(%s) ", name); av++; ac--; } else { name = "root"; strcpy(ps1, "PS1=(#) "); } if ((ent = getpwnam(name)) == NULL) { fprintf(stderr, "Can't find password entry for \"%s\"\n", name); return 1; } if (!(setgid(ent->pw_gid) || setuid(ent->pw_uid))) { putenv(ps1); if (ac == 1) if (shell = getenv("SHELL")) execl(shell, shell, (char *)0L); else execl("/bin/sh", "sh", (char *)(0L)); else execvp(av[1], av + 1); fprintf(stderr, "Error in %s: ", argv[0]); perror(""); } else { fprintf(stderr, "%s setuid failed - ", argv[0]); perror(""); } return 0; } From owner-freebsd-current Sun Jan 28 23:42:34 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id XAA11389 for current-outgoing; Sun, 28 Jan 1996 23:42:34 -0800 (PST) Received: from ref.tfs.com (ref.tfs.com [140.145.254.251]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id XAA11384 for ; Sun, 28 Jan 1996 23:42:31 -0800 (PST) Received: (from julian@localhost) by ref.tfs.com (8.6.12/8.6.9) id XAA05419 for current@freebsd.org; Sun, 28 Jan 1996 23:41:51 -0800 From: Julian Elischer Message-Id: <199601290741.XAA05419@ref.tfs.com> Subject: any ideas about this crash? To: current@freebsd.org Date: Sun, 28 Jan 1996 23:41:51 -0800 (PST) X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-current@freebsd.org Precedence: bulk julian@freefall.freebsd.org:/a/julian/src/sys/compile/ERF4 CPU: Pentium (66.66-MHz 586-class CPU) ----------- note: It's a 60Mhz, not 66, nor is it a 50 as seen below.... ----------- Origin = "GenuineIntel" Id = 0x515 Stepping=5 Features=0x1bf real memory = 33554432 (32768K bytes) avail memory = 31043584 (30316K bytes) eisa0: Probing for devices on the EISA bus bt0: at 0x330-0x333, 0x2c00-0x2cff irq 11 bt0: on eisa0 slot 2 bt0: Bt742A/H0-(32bit) bus bt0: reading board settings, busmastering, int=11 bt0: version 3.37, fast sync, parity, 32 mbxs, 32 ccbs bt0: targ 0 sync rate= 4.54MB/s(220ns), offset=15 bt0: Using Strict Round robin scheme (bt0:0:0): "IMPRIMIS 94601-15 4614" type 0 fixed SCSI 1 sd0(bt0:0:0): Direct-Access 992MB (2031705 512 byte sectors) Probing for devices on PCI bus 0: chip0 rev 3\M^?\^A:0 chip1 rev 4 on pci0:2 vga0 rev 0 on pci0:7 Probing for devices on the ISA bus: sc0 at 0x60-0x6f irq 1 on motherboard sc0: VGA color <16 virtual consoles, flags=0x0> ed0 at 0x300-0x31f irq 10 maddr 0xcc000 msize 16384 on isa ed0: address 00:00:c0:f8:c0:70, type WD8013EPC (16 bit) lpt0 at 0x378-0x37f irq 7 on isa lpt0: Interrupt-driven port lp0: TCP/IP capable interface sio0 at 0x3f8-0x3ff irq 4 on isa sio0: type 16450 pca0 on motherboard pca0: PC speaker audio driver bt: unit number (1) too high bt0 not found at 0x330 wdc0 not found at 0x1f0 fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa fdc0: NEC 765 fd0: 1.44MB 3.5in fd1: 1.2MB 5.25in npx0 on motherboard npx0: INT 16 interface sctarg0(noadapter::): Processor Target changing root device to sd0a new masks: bio c0000840, tty c0030492, net c0030492 Fatal trap 12: page fault while in kernel mode fault virtual address = 0x6 fault code = supervisor write, page not present instruction pointer = 0x8:0xf01ea038 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = 29 (mount_kernfs) ---------------- hmmmm. bet I need a new mount_kernfs... I'll go try that.... still it SHOULDN'T crash the system.. I get the same if I compile here or on Freefall. ------------ interrupt mask = panic: (fmt null) syncing disks... 4 4 2 done dumping to dev 1, offset 0 dump device bad ------------------ hmm pitty about that :( ------------------ Automatic reboot in 15 seconds - press a key on the console to abort Rebooting... FreeBSD 2.2-CURRENT #1: Sun Nov 26 13:20:14 PST 1995 julian@erf.tfs.com:/usr/src/sys/compile/ERF4 CPU: 55-MHz Pentium 510\\60 or 567\\66 (Pentium-class CPU) ------------------- Not 55MHz.. either ------------------- Origin = "GenuineIntel" Id = 0x515 Stepping=5 Features=0x1bf real memory = 33554432 (32768K bytes) avail memory = 31019008 (30292K bytes) Probing for devices on the ISA bus: sc0 at 0x60-0x6f irq 1 on motherboard .... From owner-freebsd-current Mon Jan 29 00:01:35 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id AAA12058 for current-outgoing; Mon, 29 Jan 1996 00:01:35 -0800 (PST) Received: from gilberto.physik.rwth-aachen.de (gilberto.physik.rwth-aachen.de [137.226.31.2]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id AAA12049 for ; Mon, 29 Jan 1996 00:01:32 -0800 (PST) Received: (from kuku@localhost) by gilberto.physik.rwth-aachen.de (8.6.11/8.6.9) id JAA16621; Mon, 29 Jan 1996 09:04:09 +0100 Message-Id: <199601290804.JAA16621@gilberto.physik.rwth-aachen.de> Subject: Re: lpt0 incorrect interrupt count / systat To: roberto@keltia.freenix.fr (Ollivier Robert) Date: Mon, 29 Jan 1996 09:04:09 +0100 (MET) Cc: freebsd-current@FreeBSD.ORG In-Reply-To: <199601282128.WAA23462@keltia.freenix.fr> from "Ollivier Robert" at Jan 28, 96 10:28:21 pm From: Christoph Kukulies Reply-To: Christoph Kukulies X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-current@FreeBSD.ORG Precedence: bulk > > Hi, > > Two (well three) things: > > - I'm seeing a weird interrupt count (much too high) for lpt0 since a few > days... > > interrupt total rate > clk0 irq0 334008 114 > rtc0 irq8 374530 128 > fdc0 irq6 1 0 > sc0 irq1 6724 2 > sio0 irq4 5880 2 > sio1 irq3 8193 2 > lpt0 irq7 665828 227 > ep0 irq10 22 0 > Total 1395186 476 > > The printer is of course inactive and even turned off. Where do these > interrupts come from ? I recently changed my NE2000 for a 3C509B; can this > be the cause of the problem ? It may be hardware. Do you remember the stray interrupt 7 from earlier releases? Have you tried to used lpt in polled mode (lptcontrol)? [config and dmesg excerpt deleted] > -- > Ollivier ROBERT -=- The daemon is FREE! -=- roberto@keltia.frmug.fr.net > FreeBSD keltia.freenix.fr 2.2-CURRENT #1: Sun Jan 14 20:23:45 MET 1996 > --Chris Christoph P. U. Kukulies kuku@gil.physik.rwth-aachen.de From owner-freebsd-current Mon Jan 29 01:52:56 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id BAA17905 for current-outgoing; Mon, 29 Jan 1996 01:52:56 -0800 (PST) Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id BAA17886 for ; Mon, 29 Jan 1996 01:52:41 -0800 (PST) Received: from sax.sax.de by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id KAA22789; Mon, 29 Jan 1996 10:52:05 +0100 Received: by sax.sax.de (8.6.11/8.6.12-s1) with UUCP id KAA17394; Mon, 29 Jan 1996 10:52:03 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.7.3/8.6.9) id KAA07727; Mon, 29 Jan 1996 10:41:40 +0100 (MET) From: J Wunsch Message-Id: <199601290941.KAA07727@uriah.heep.sax.de> Subject: Re: Please test this on your system (and see if you crash) To: jkh@time.cdrom.com (Jordan K. Hubbard) Date: Mon, 29 Jan 1996 10:41:39 +0100 (MET) Cc: current@freebsd.org Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <17705.822895066@time.cdrom.com> from "Jordan K. Hubbard" at Jan 28, 96 09:57:46 pm X-Phone: +49-351-2012 669 X-Mailer: ELM [version 2.4 PL23] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-current@freebsd.org Precedence: bulk As Jordan K. Hubbard wrote: > > Yes, this program may hose you. It hoses me, so be careful trying it > out. It works for me. System built around end of December. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-current Mon Jan 29 02:14:13 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id CAA18925 for current-outgoing; Mon, 29 Jan 1996 02:14:13 -0800 (PST) Received: from asstdc.scgt.oz.au (asstdc.scgt.oz.au [202.14.234.65]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id CAA18917 for ; Mon, 29 Jan 1996 02:14:02 -0800 (PST) Received: (from imb@localhost) by asstdc.scgt.oz.au (8.6.12/BSD4.4) id VAA18928; Mon, 29 Jan 1996 21:09:35 +1100 From: michael butler Message-Id: <199601291009.VAA18928@asstdc.scgt.oz.au> Subject: Re: lpt0 incorrect interrupt count / systat To: kuku@gilberto.physik.rwth-aachen.de Date: Mon, 29 Jan 1996 21:09:32 +1100 (EST) Cc: roberto@keltia.freenix.fr, freebsd-current@freebsd.org In-Reply-To: <199601290804.JAA16621@gilberto.physik.rwth-aachen.de> from "Christoph Kukulies" at Jan 29, 96 09:04:09 am X-Mailer: ELM [version 2.4 PL24beta] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org Precedence: bulk Christoph Kukulies writes: > > interrupts come from ? I recently changed my NE2000 for a 3C509B; can > > this be the cause of the problem ? Yup. I have identical symptoms. > It may be hardware. Do you remember the stray interrupt 7 from > earlier releases? Have you tried to used lpt in polled mode (lptcontrol)? I have no printer port in the machine. It's associated with the 3C509. If I replace it with any other card (WD8003 or WD8013), the problem goes away, michael From owner-freebsd-current Mon Jan 29 03:07:53 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id DAA21828 for current-outgoing; Mon, 29 Jan 1996 03:07:53 -0800 (PST) Received: from iworks.InterWorks.org (iworks.interworks.org [128.255.18.10]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id DAA21822 for ; Mon, 29 Jan 1996 03:07:51 -0800 (PST) Received: by iworks.InterWorks.org (1.37.109.8/16.2) id AA00681; Mon, 29 Jan 1996 05:05:45 -0600 Message-Id: <9601291105.AA00681@iworks.InterWorks.org> Date: Mon, 29 Jan 1996 05:05:45 -0600 From: "Daniel M. Eischen" To: current@FreeBSD.org Subject: Re: any ideas about this crash? Sender: owner-current@FreeBSD.org Precedence: bulk > julian@freefall.freebsd.org:/a/julian/src/sys/compile/ERF4 >CPU: Pentium (66.66-MHz 586-class CPU) >----------- >note: It's a 60Mhz, not 66, nor is it a 50 as seen below.... >----------- I don't crash, but I do get odd MHz ratings. FreeBSD 2.2-CURRENT #0: Sun Jan 28 10:17:25 EST 1996 deischen@rigel:/usr/src/sys/compile/rigel CPU: Pentium (76.42-MHz 586-class CPU) ^^^^^^^^^ Mine is 90MHz. Dan Eischen deischen@iworks.InterWorks.org From owner-freebsd-current Mon Jan 29 06:52:50 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id GAA06454 for current-outgoing; Mon, 29 Jan 1996 06:52:50 -0800 (PST) Received: from time.cdrom.com (time.cdrom.com [192.216.222.226]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id GAA06449 for ; Mon, 29 Jan 1996 06:52:43 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by time.cdrom.com (8.6.12/8.6.9) with SMTP id GAA09716; Mon, 29 Jan 1996 06:49:35 -0800 To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) cc: current@freebsd.org Subject: Re: Please test this on your system (and see if you crash) In-reply-to: Your message of "Mon, 29 Jan 1996 10:41:39 +0100." <199601290941.KAA07727@uriah.heep.sax.de> Date: Mon, 29 Jan 1996 06:49:35 -0800 Message-ID: <9714.822926975@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-current@freebsd.org Precedence: bulk Anybody more recent? :-) Jordan > As Jordan K. Hubbard wrote: > > > > Yes, this program may hose you. It hoses me, so be careful trying it > > out. > > It works for me. System built around end of December. > > -- > cheers, J"org > > joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE > Never trust an operating system you don't have sources for. ;-) From owner-freebsd-current Mon Jan 29 07:03:16 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id HAA06976 for current-outgoing; Mon, 29 Jan 1996 07:03:16 -0800 (PST) Received: from time.cdrom.com (time.cdrom.com [192.216.222.226]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id HAA06968 for ; Mon, 29 Jan 1996 07:03:04 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by time.cdrom.com (8.6.12/8.6.9) with SMTP id HAA09835 for ; Mon, 29 Jan 1996 07:02:44 -0800 To: current@freebsd.org Subject: I'm rather annoyed with -current. Date: Mon, 29 Jan 1996 07:02:44 -0800 Message-ID: <9833.822927764@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-current@freebsd.org Precedence: bulk Not only has the thread_init race problem still NOT been fixed (try a make world in -current using a 2.1-RELEASE system as the base - it will fall over!) but today we have this new problem: ===> lib/librpcsvc cc -O -pipe -I/usr/include/rpcsvc -c klm_prot_xdr.c -o klm_prot_xdr.o In file included from klm_prot_xdr.c:6: /usr/include/rpcsvc/klm_prot.h:10: parse error before `xdr_klm_stats' /usr/include/rpcsvc/klm_prot.h:10: warning: data definition has no type or storage class /usr/include/rpcsvc/klm_prot.h:15: parse error before `netobj' /usr/include/rpcsvc/klm_prot.h:15: warning: no semicolon at end of struct or union I'm not even particularly sure how to fix this one, either. The header file that's generated here certainly doesn't include the required header files itself, and blowing away /usr/include/rpcsvc and trying to repopulate it from scratch didn't help. I haven't been able to build -stable for several weeks now - is it just me, managing to try it on every single day that the tree is broken? I'm about to give up on the whole idea of a 2.2-SNAP, to be honest! :-( We really need to be more careful with the -current tree. This is not good. Jordan From owner-freebsd-current Mon Jan 29 07:23:32 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id HAA08031 for current-outgoing; Mon, 29 Jan 1996 07:23:32 -0800 (PST) Received: from Adonis.Dorm10.NCTU.edu.tw (Adonis.Dorm10.NCTU.edu.tw [140.113.122.84]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id HAA08022 for ; Mon, 29 Jan 1996 07:23:17 -0800 (PST) Received: (from jdli@localhost) by Adonis.Dorm10.NCTU.edu.tw (8.7.3/8.6.12) id XAA16030 for freebsd-current@FreeBSD.ORG; Mon, 29 Jan 1996 23:24:21 +0800 (CST) Date: Mon, 29 Jan 1996 23:24:21 +0800 (CST) From: Chien-Ta Lee Message-Id: <199601291524.XAA16030@Adonis.Dorm10.NCTU.edu.tw> To: freebsd-current@FreeBSD.ORG Subject: lsdev broken Sender: owner-current@FreeBSD.ORG Precedence: bulk cc -O2 -m486 -pipe -I/usr/src/usr.sbin/lsdev/../../sys -c /home/current/src/usr.sbin/lsdev/i386.c /home/current/src/usr.sbin/lsdev/i386.c: In function `print_eisa': /home/current/src/usr.sbin/lsdev/i386.c:168: structure has no member named `iobase' /home/current/src/usr.sbin/lsdev/i386.c:169: structure has no member named `iobase' /home/current/src/usr.sbin/lsdev/i386.c:169: structure has no member named `iosize' *** Error code 1 Stop. From owner-freebsd-current Mon Jan 29 07:54:26 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id HAA09654 for current-outgoing; Mon, 29 Jan 1996 07:54:26 -0800 (PST) Received: from rocky.sri.MT.net (rocky.sri.MT.net [204.182.243.10]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id HAA09642 for ; Mon, 29 Jan 1996 07:54:17 -0800 (PST) Received: (from nate@localhost) by rocky.sri.MT.net (8.6.12/8.6.12) id IAA08024; Mon, 29 Jan 1996 08:56:51 -0700 Date: Mon, 29 Jan 1996 08:56:51 -0700 From: Nate Williams Message-Id: <199601291556.IAA08024@rocky.sri.MT.net> To: "Jordan K. Hubbard" Cc: current@FreeBSD.org Subject: Re: I'm rather annoyed with -current. In-Reply-To: <9833.822927764@time.cdrom.com> References: <9833.822927764@time.cdrom.com> Sender: owner-current@FreeBSD.org Precedence: bulk > Not only has the thread_init race problem still NOT been fixed (try a > make world in -current using a 2.1-RELEASE system as the base - it > will fall over!) but today we have this new problem: > > ===> lib/librpcsvc > cc -O -pipe -I/usr/include/rpcsvc -c klm_prot_xdr.c -o klm_prot_xdr.o > In file included from klm_prot_xdr.c:6: > /usr/include/rpcsvc/klm_prot.h:10: parse error before `xdr_klm_stats' > /usr/include/rpcsvc/klm_prot.h:10: warning: data definition has no type or storage class > /usr/include/rpcsvc/klm_prot.h:15: parse error before `netobj' > /usr/include/rpcsvc/klm_prot.h:15: warning: no semicolon at end of struct or union > > I'm not even particularly sure how to fix this one, either. The > header file that's generated here certainly doesn't include the > required header files itself, and blowing away /usr/include/rpcsvc > and trying to repopulate it from scratch didn't help. Both of these problems are due to ordering problems in the Makefile, which can be fixed in the 'world' target, but don't really fit into the current model used. You need to build and install rpcgen *before* the include files are built. There is also a dependency problem with either the libraries or the crt0.o file (I don't remember which one is first.) It basically boils down to the fact that we *should* be building the sources out of the src tree and not out of the stuff in /usr/{lib|include} etc... (Which I've argued against in the past as un-necessary and complex, but I think we've now reached critical mass and require it.) > I haven't been able to build -stable for several weeks now - is it > just me, managing to try it on every single day that the tree is > broken? I'm about to give up on the whole idea of a 2.2-SNAP, to be > honest! :-( I haven't tried -stable yet, but I may get time today. :) Nate From owner-freebsd-current Mon Jan 29 08:39:20 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id IAA12342 for current-outgoing; Mon, 29 Jan 1996 08:39:20 -0800 (PST) Received: from scrooge.ee.swin.oz.au (scrooge.ee.swin.oz.au [136.186.4.20]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id IAA12333 for ; Mon, 29 Jan 1996 08:39:10 -0800 (PST) Received: (from dtc@localhost) by scrooge.ee.swin.oz.au (8.6.9/8.6.9) id DAA28428; Tue, 30 Jan 1996 03:39:57 +1100 From: Douglas Thomas Crosher Message-Id: <199601291639.DAA28428@scrooge.ee.swin.oz.au> Subject: Re: lpt0 incorrect interrupt count / systat To: roberto@keltia.freenix.fr (Ollivier Robert) Date: Tue, 30 Jan 1996 03:39:57 +1100 (EST) In-Reply-To: <199601282128.WAA23462@keltia.freenix.fr> from "Ollivier Robert" at Jan 28, 96 10:28:21 pm X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-current@FreeBSD.ORG Precedence: bulk > The printer is of course inactive and even turned off. Where do these > interrupts come from ? I recently changed my NE2000 for a 3C509B; can this > be the cause of the problem ? > > eisa0: > Probing for devices on the EISA bus > eisa0:1 unknown device > [...] > 1 3C5x9 board(s) on EISA found at 0x1000 > 1 3C5x9 board(s) on ISA found at 0x300 > ep0 at 0x300-0x30f irq 10 on isa > ep0: aui/utp[*AUI*] address 00:20:af:5a:51:9d irq 10 > > - the 3C509B is unusable when configured as an EISA device > > Jan 28 20:21:16 keltia /kernel.3com: 1 3C5x9 board(s) on EISA found at 0x1000 > Jan 28 20:21:16 keltia /kernel.3com: ep0: 3c5x9 at 0x1000 in test mode. Erase pencil mark! > Jan 28 20:21:16 keltia /kernel.3com: ep0: eeprom failed to come ready. > Jan 28 20:21:16 keltia /kernel.3com: epprobe: ignoring model ffff > Jan 28 20:21:16 keltia /kernel.3com: ep0 not found at 0x1000 > > I have modified if_ep.c with the latest Serge's patches after merging > -CURRENT's differences and it changes nothing. I can use the card only in > pure ISA mode. PnP doesn't make any difference. I recently tried current and found that my 3c509 card would lockup within a few seconds of heavy transmittions. I noticed that there is no timeout code in the current if_ep.c driver and had to put back the kludge from the 2.1 version, patch below. I'd be interested to know if you have the card working reliably under current without such a kludge. Regards Douglas Crosher -=-=-=-=- *** if_ep.c.orig Fri Jan 26 20:48:38 1996 --- if_ep.c Tue Jan 30 03:14:07 1996 *************** *** 436,441 **** --- 436,442 ---- ifp->if_start = epstart; ifp->if_ioctl = epioctl; ifp->if_watchdog = epwatchdog; + ifp->if_timer=1; /* Get the timeouts started! */ if_attach(ifp); kdc_ep[is->id_unit].kdc_state = DC_BUSY; *************** *** 1252,1258 **** epwatchdog(ifp) struct ifnet *ifp; { ! /* printf("ep: watchdog\n"); log(LOG_ERR, "ep%d: watchdog\n", ifp->if_unit); --- 1253,1260 ---- epwatchdog(ifp) struct ifnet *ifp; { ! ! /* Don't want to log a message every second! printf("ep: watchdog\n"); log(LOG_ERR, "ep%d: watchdog\n", ifp->if_unit); *************** *** 1262,1267 **** --- 1264,1273 ---- ifp->if_flags &= ~IFF_OACTIVE; epstart(ifp); epintr(ifp->if_unit); + + /* What a kludge; just keeps timing out every second! */ + ifp->if_timer=1; + } static void From owner-freebsd-current Mon Jan 29 08:45:51 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id IAA12741 for current-outgoing; Mon, 29 Jan 1996 08:45:51 -0800 (PST) Received: from biblioteca.campus.unal.edu.co ([200.21.26.198]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id IAA12716 Mon, 29 Jan 1996 08:45:26 -0800 (PST) Received: by biblioteca.campus.unal.edu.co (AIX 3.2/UCB 5.64/4.03) id AA22755; Mon, 29 Jan 1996 11:41:02 -0500 Date: Mon, 29 Jan 1996 11:41:02 -0500 (EST) From: Pedro Giffuni To: freebsd-stable@FreeBSD.org Cc: freebsd-current@FreeBSD.org Subject: Please include Mail Handler Message-Id: Mime-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="-938140986-2078917053-822933662=:11404" Sender: owner-current@FreeBSD.org Precedence: bulk This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. Send mail to mime@docserver.cac.washington.edu for more info. ---938140986-2078917053-822933662=:11404 Content-Type: TEXT/PLAIN; charset=US-ASCII Hi, I want to propose the inclusion of the MH pacakage with the main FreeBSD distribution. MH is a public domain package developed by the RAND corporation that permits mail management with a shell. I knew of it because it is necesary for using XMH, and several operating systems like AIX include it. The latest version I know, mh-6.8.tar.gz, also includes support for POP2-POP3 and IMAPD (if NNTP is present it can also be handled). The original distribution is kept by UCLA, but I found it ported for BSD-4.4 lite. I am sending an attached file I archied. regards, Pedro Universidad Nacional de Colombia ---938140986-2078917053-822933662=:11404 Content-Type: TEXT/PLAIN; charset=US-ASCII; name=where Content-Transfer-Encoding: BASE64 Content-ID: Content-Description: DQpIb3N0IG1pbm5pZS5jcy5hZGZhLm96LmF1DQoNCiAgICBMb2NhdGlvbjog L0JTRC80LjRCU0QtTGl0ZS80LjRCU0QtTGl0ZS91c3IvY29udHJpYg0KICAg ICAgRElSRUNUT1JZIGRyd3hyLXhyLXggICAgICAgIDUxMiAgTWF5IDMwIDE5 OTQgIG1oLTYuOA0KDQpIb3N0IGZ0cC5tcy5tZmYuY3VuaS5jeg0KDQogICAg TG9jYXRpb246IC9NSVJST1JTL2Z0cC5jZHJvbS5jb20vcHViL2JzZC1zb3Vy Y2VzLzQuNEJTRC1MaXRlL3Vzci9jb250cmliDQogICAgICBESVJFQ1RPUlkg ZHJ3eHJ3eHJ3eCAgICAgICAyMDQ4ICBNYXIgMjEgMTk5NCAgbWgtNi44DQog ICAgTG9jYXRpb246IC9PUy80LjRCU0QtTGl0ZS80LjRCU0QtTGl0ZS91c3Iv Y29udHJpYg0KICAgICAgRElSRUNUT1JZIGRyd3hyd3hyd3ggICAgICAgMjA0 OCAgTWFyIDIxIDE5OTQgIG1oLTYuOA0KDQpIb3N0IGZ0cC51bmktdHJpZXIu ZGUNCg0KICAgIExvY2F0aW9uOiAvcHViL3VuaXgvc3lzdGVtcy9CU0QtNC40 bGl0ZS80LjRCU0QtTGl0ZS91c3IvY29udHJpYg0KICAgICAgRElSRUNUT1JZ IGRyd3hyLXhyLXggICAgICAgIDUxMiAgTWF5IDE2IDE5OTUgIG1oLTYuOA0K DQpIb3N0IGZ0cC5pc2kuZWR1DQoNCiAgICBMb2NhdGlvbjogL3B1Yi92bWgN CiAgICAgIERJUkVDVE9SWSBkcnd4ci14ci14ICAgICAgICA1MTIgIEp1biAg MiAxOTkzICBtaC02LjgNCg0KSG9zdCBmdHAuY3Mub3JzdC5lZHUNCg0KICAg IExvY2F0aW9uOiAvc29mdHdhcmUvb3Bfc3lzLzQuNC1MaXRlLzQuNEJTRC1M aXRlL3Vzci9jb250cmliDQogICAgICBESVJFQ1RPUlkgZHJ3eHJ3eHIteCAg ICAgICAgNTEyICBBdWcgIDggMTk5NCAgbWgtNi44DQoNCkhvc3QgZnRwLm1h dGgub3JzdC5lZHUNCg0KICAgIExvY2F0aW9uOiAvMzg2QlNELzAuMS1wb3J0 cw0KICAgICAgRElSRUNUT1JZIGRyd3hyLXhyLXggICAgICAgIDUxMiAgRmVi IDE0IDE5OTMgIG1oLTYuOA0KDQpIb3N0IGZ0cC5tZWlqaS5hYy5qcA0KDQog ICAgTG9jYXRpb246IC9taXJyb3IvLjQvTmV0QlNEL05ldEJTRC1jdXJyZW50 L290aGVyc3JjDQogICAgICBESVJFQ1RPUlkgZHJ3eHIteHIteCAgICAgICAg NTEyICBEZWMgMjEgMTk5MyAgbWgtNi44DQoNCkhvc3QgbmFkaWEuaWNzLmVz Lm9zYWthLXUuYWMuanANCg0KICAgIExvY2F0aW9uOiAvZDAvMzg2QlNELzAu MS1wb3J0cw0KICAgICAgRElSRUNUT1JZIGRyd3hyd3hyLXggICAgICAgIDUx MiAgTm92IDI4IDE5OTMgIG1oLTYuOA0KDQpIb3N0IGZ0cC5paWouYWQuanAN Cg0KICAgIExvY2F0aW9uOiAvcHViLzM4NmJzZC8wLjEtcG9ydHMNCiAgICAg IERJUkVDVE9SWSBkcnd4ci14ci14ICAgICAgICA1MTIgIE5vdiAyNiAxOTkz ICBtaC02LjgNCg0KSG9zdCBmdHAuYXN0ZWMuY28uanANCg0KICAgIExvY2F0 aW9uOiAvcHViL21haWwNCiAgICAgIERJUkVDVE9SWSBkcnd4cnd4ci14ICAg ICAgICA1MTIgIE1hciAyNCAxOTk0ICBtaC02LjgNCg0KSG9zdCBmdHAuc3Jh LmNvLmpwDQoNCiAgICBMb2NhdGlvbjogL3B1Yi9vcy80LjRCU0QtTGl0ZS9l eHRyYWN0ZWQvNC40QlNELUxpdGUvdXNyL2NvbnRyaWINCiAgICAgIERJUkVD VE9SWSBkcnd4ci14ci14ICAgICAgICA1MTIgIE1hciAyMiAxOTk0ICBtaC02 LjgNCg0KSG9zdCBmdHAubmN1LmVkdS50dw0KDQogICAgTG9jYXRpb246IC9P Uy9CU0QtU291cmNlcy80LjRCU0QtTGl0ZS91c3IvY29udHJpYg0KICAgICAg RElSRUNUT1JZIGRyd3hyLXhyLXggICAgICAgIDUxMiAgTWFyIDIyIDE5OTQg IG1oLTYuOA0KDQpIb3N0IHNvZnR1MS5uY3UuZWR1LnR3DQoNCiAgICBMb2Nh dGlvbjogL3B1Yi8zODZCU0QvMC4xLXBvcnRzDQogICAgICBESVJFQ1RPUlkg ZHJ3eHIteHIteCAgICAgICAgNTEyICBNYXkgMTEgMTk5MyAgbWgtNi44DQog ICAgTG9jYXRpb246IC9wdWIvMzg2QlNELzM4NmJzZC0wLjEvdW5vZmZpY2lh bC9wb3J0cw0KICAgICAgRElSRUNUT1JZIGRyd3hyLXhyLXggICAgICAgIDUx MiAgTWF5ICA1IDE5OTMgIG1oLTYuOA0KDQpIb3N0IHNjaXRzYy53bHYuYWMu dWsNCg0KICAgIExvY2F0aW9uOiAvcHViL2luZm9tYWdpYzIvc291cmNlLmNv ZGUuY2Ryb20uT2N0OTQvNC40QlNELUxpdGUvdXNyL2NvbnRyaWINCiAgICAg IERJUkVDVE9SWSBkcnd4ci14ci14ICAgICAgICA1MTIgIE9jdCAzMSAwODoy OSAgbWgtNi44DQo= ---938140986-2078917053-822933662=:11404-- From owner-freebsd-current Mon Jan 29 09:01:06 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id JAA13625 for current-outgoing; Mon, 29 Jan 1996 09:01:06 -0800 (PST) Received: from miller.cs.uwm.edu (miller.cs.uwm.edu [129.89.9.13]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id JAA13613 for ; Mon, 29 Jan 1996 09:00:58 -0800 (PST) Received: (from james@localhost) by miller.cs.uwm.edu (8.7.3/8.7.3) id LAA21244 for current@freebsd.org; Mon, 29 Jan 1996 11:00:53 -0600 Date: Mon, 29 Jan 1996 11:00:53 -0600 From: Jim Lowe Message-Id: <199601291700.LAA21244@miller.cs.uwm.edu> To: current@freebsd.org Subject: Recent sound changes Sender: owner-current@freebsd.org Precedence: bulk I did a sup this morning to pick up the new malloc/vm changes and something is amuck in the sound driver. I keep getting: isa_dmastart: channel 3 busy Any idea why? -Jim From owner-freebsd-current Mon Jan 29 09:14:50 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id JAA14645 for current-outgoing; Mon, 29 Jan 1996 09:14:50 -0800 (PST) Received: from localhost.cdrom.com (localhost.cdrom.com [127.0.0.1]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id JAA14635 Mon, 29 Jan 1996 09:14:43 -0800 (PST) Message-Id: <199601291714.JAA14635@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: Host localhost.cdrom.com [127.0.0.1] didn't use HELO protocol To: Chien-Ta Lee cc: freebsd-current@FreeBSD.ORG Subject: Re: lsdev broken In-reply-to: Your message of "Mon, 29 Jan 1996 23:24:21 +0800." <199601291524.XAA16030@Adonis.Dorm10.NCTU.edu.tw> Date: Mon, 29 Jan 1996 09:14:40 -0800 From: "Justin T. Gibbs" Sender: owner-current@FreeBSD.ORG Precedence: bulk I'm away from my FreeBSD box until Tuesday night. If someone wants to fix the code (eisaconf.c has to externalize the linked lists and lsdev must learn about them) before then or #if 0 the old code, feel free. -- Justin T. Gibbs =========================================== FreeBSD: Turning PCs into workstations =========================================== From owner-freebsd-current Mon Jan 29 09:16:35 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id JAA14853 for current-outgoing; Mon, 29 Jan 1996 09:16:35 -0800 (PST) Received: from omega.physik.fu-berlin.de (omega.physik.fu-berlin.de [130.133.3.51]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id JAA14544 for ; Mon, 29 Jan 1996 09:12:35 -0800 (PST) Received: from prospero.physik.fu-berlin.de (lislip.physik.fu-berlin.de [130.133.3.126]) by omega.physik.fu-berlin.de (8.7.1/8.7.1) with ESMTP id SAA04611 for ; Mon, 29 Jan 1996 18:12:13 +0100 (MET) Received: (from graichen@localhost) by prospero (8.6.12/8.6.12) id MAA02467 for current@freebsd.org; Mon, 29 Jan 1996 12:13:12 +0100 Date: Mon, 29 Jan 1996 12:13:12 +0100 From: Thomas Graichen Message-Id: <199601291113.MAA02467@prospero> To: current@freebsd.org Subject: (fwd) too many cached pages for profiled kernel Newsgroups: local.freebsd-current Organization: home :-) Sender: owner-current@freebsd.org Precedence: bulk ... `68Kout' in the top output should be formatted better. ... Swap: 33M Total, 6736K Used, 27M Free, 20% Inuse 68Kout ... how about "K Out" and "K In" - that's what i use t _______________________________________________________||___________________ __|| Perfection is reached, not when there is no __|| thomas graichen longer anything to add, but when there __|| freie universitaet berlin is no longer anything to take away __|| fachbereich physik __|| - Antoine de Saint-Exupery - __|| graichen@mail.physik.fu-berlin.de ___________________________||__________________graichen@FreeBSD.org_________ From owner-freebsd-current Mon Jan 29 09:31:13 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id JAA15876 for current-outgoing; Mon, 29 Jan 1996 09:31:13 -0800 (PST) Received: from halloran-eldar.lcs.mit.edu (halloran-eldar.lcs.mit.edu [18.26.0.159]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id JAA15866 for ; Mon, 29 Jan 1996 09:31:05 -0800 (PST) Received: by halloran-eldar.lcs.mit.edu; (5.65/1.1.8.2/19Aug95-0530PM) id AA05796; Mon, 29 Jan 1996 12:30:57 -0500 Date: Mon, 29 Jan 1996 12:30:57 -0500 From: "Garrett A. Wollman" Message-Id: <9601291730.AA05796@halloran-eldar.lcs.mit.edu> To: "Daniel M. Eischen" Cc: current@FreeBSD.org Subject: Re: any ideas about this crash? In-Reply-To: <9601291105.AA00681@iworks.InterWorks.org> References: <9601291105.AA00681@iworks.InterWorks.org> Sender: owner-current@FreeBSD.org Precedence: bulk < said: > FreeBSD 2.2-CURRENT #0: Sun Jan 28 10:17:25 EST 1996 > deischen@rigel:/usr/src/sys/compile/rigel > CPU: Pentium (76.42-MHz 586-class CPU) > ^^^^^^^^^ > Mine is 90MHz. Your timer/counter is bogus. Complain to the vendor. -GAWollman -- Garrett A. Wollman | Shashish is simple, it's discreet, it's brief. ... wollman@lcs.mit.edu | Shashish is the bonding of hearts in spite of distance. Opinions not those of| It is a bond more powerful than absence. We like people MIT, LCS, ANA, or NSA| who like Shashish. - Claude McKenzie + Florent Vollant From owner-freebsd-current Mon Jan 29 10:12:51 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id KAA18821 for current-outgoing; Mon, 29 Jan 1996 10:12:51 -0800 (PST) Received: from cabri.obs-besancon.fr (cabri.obs-besancon.fr [193.52.184.3]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id KAA18803 for ; Mon, 29 Jan 1996 10:12:41 -0800 (PST) Received: by cabri.obs-besancon.fr (5.57/Ultrix3.0-C) id AA01323; Mon, 29 Jan 96 19:12:18 +0100 Date: Mon, 29 Jan 96 19:12:18 +0100 Message-Id: <9601291812.AA01323@cabri.obs-besancon.fr> From: Jean-Marc Zucconi To: jkh@time.cdrom.com Cc: current@freebsd.org In-Reply-To: <17705.822895066@time.cdrom.com> (jkh@time.cdrom.com) Subject: Re: Please test this on your system (and see if you crash) X-Mailer: Emacs Sender: owner-current@freebsd.org Precedence: bulk >>>>> "Jordan K Hubbard" writes: > Yes, this program may hose you. It hoses me, so be careful trying it > out. No problem at home (kernel from yesterday - make world from Jan 22) Jean-Marc _____________________________________________________________________________ Jean-Marc Zucconi Observatoire de Besancon F 25010 Besancon cedex PGP Key: finger jmz@cabri.obs-besancon.fr ============================================================================= From owner-freebsd-current Mon Jan 29 10:21:02 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id KAA19423 for current-outgoing; Mon, 29 Jan 1996 10:21:02 -0800 (PST) Received: from skynet.ctr.columbia.edu (skynet.ctr.columbia.edu [128.59.64.70]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id KAA19410 for ; Mon, 29 Jan 1996 10:20:52 -0800 (PST) Received: (from wpaul@localhost) by skynet.ctr.columbia.edu (8.6.12/8.6.9) id NAA26785; Mon, 29 Jan 1996 13:20:34 -0500 From: the revolution will not be televised Message-Id: <199601291820.NAA26785@skynet.ctr.columbia.edu> Subject: Re: I'm rather annoyed with -current. To: jkh@time.cdrom.com (Jordan K. Hubbard) Date: Mon, 29 Jan 1996 13:20:33 -0500 (EST) Cc: current@freebsd.org In-Reply-To: <9833.822927764@time.cdrom.com> from "Jordan K. Hubbard" at Jan 29, 96 07:02:44 am X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-current@freebsd.org Precedence: bulk Of all the gin joints in all the world, Jordan K. Hubbard had to walk into mine and say: > Not only has the thread_init race problem still NOT been fixed (try a > make world in -current using a 2.1-RELEASE system as the base - it > will fall over!) but today we have this new problem: > > ===> lib/librpcsvc > cc -O -pipe -I/usr/include/rpcsvc -c klm_prot_xdr.c -o klm_prot_xdr.o > In file included from klm_prot_xdr.c:6: > /usr/include/rpcsvc/klm_prot.h:10: parse error before `xdr_klm_stats' > /usr/include/rpcsvc/klm_prot.h:10: warning: data definition has no type or storage class > /usr/include/rpcsvc/klm_prot.h:15: parse error before `netobj' > /usr/include/rpcsvc/klm_prot.h:15: warning: no semicolon at end of struct or union > > I'm not even particularly sure how to fix this one, either. The > header file that's generated here certainly doesn't include the > required header files itself, and blowing away /usr/include/rpcsvc > and trying to repopulate it from scratch didn't help. Uhm... not to sound patronizing, but this has been discussed already. You have to do the following things: 1) build and install the new rpcgen (make sure that it'll get used for 'make world'). 2) blow away and rebuild the /usr/include/rpcsvc directory using the new rpcgen. 3) blow away and rebuild /usr/src/lib/rpcsvc, also with the new rpcgen (if you have any stale .c files left from a previous build, clobber them). The important thing to remember is that you must use the new rpcgen for both halves. I thought that adding rpcgen to the tools target in /usr/src/Makefile was supposed to fix this. -Bill -- ============================================================================= -Bill Paul (212) 854-6020 | System Manager Work: wpaul@ctr.columbia.edu | Center for Telecommunications Research Home: wpaul@skynet.ctr.columbia.edu | Columbia University, New York City ============================================================================= License error: The license for this .sig file has expired. You must obtain a new license key before any more witty phrases will appear in this space. ============================================================================= From owner-freebsd-current Mon Jan 29 10:24:23 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id KAA19772 for current-outgoing; Mon, 29 Jan 1996 10:24:23 -0800 (PST) Received: from rocky.sri.MT.net (rocky.sri.MT.net [204.182.243.10]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id KAA19737 Mon, 29 Jan 1996 10:24:10 -0800 (PST) Received: (from nate@localhost) by rocky.sri.MT.net (8.6.12/8.6.12) id LAA08463; Mon, 29 Jan 1996 11:26:17 -0700 Date: Mon, 29 Jan 1996 11:26:17 -0700 From: Nate Williams Message-Id: <199601291826.LAA08463@rocky.sri.MT.net> To: Pedro Giffuni Cc: freebsd-stable@FreeBSD.ORG, freebsd-current@FreeBSD.ORG Subject: Re: Please include Mail Handler In-Reply-To: References: Sender: owner-current@FreeBSD.ORG Precedence: bulk > I want to propose the inclusion of the MH pacakage with the main > FreeBSD distribution. Noooooo........ :) > MH is a public domain package developed by the RAND corporation that > permits mail management with a shell. I knew of it because it is > necesary for using XMH, and several operating systems like AIX include it. This particular topic has been discussed to death in the past, and the conclusion was that everyone has a pet mail program they prefer, so by only distributing the most basic mail program (mail), we allow folks to read/write email on the base system. However, we also supply ports to most of the more popular mailers like elm, mh, and pine. They are easily installed, and don't have to be part of the base system. It's as simply as grab the mh package and running pkg_install on it to have it part of your system. Nate From owner-freebsd-current Mon Jan 29 10:24:45 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id KAA19833 for current-outgoing; Mon, 29 Jan 1996 10:24:45 -0800 (PST) Received: from insecurity.shockwave.com (insecurity.shockwave.com [171.69.60.233]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id KAA19806 Mon, 29 Jan 1996 10:24:34 -0800 (PST) Received: (from pst@localhost) by insecurity.shockwave.com (8.6.12/8.6.12) id KAA10791; Mon, 29 Jan 1996 10:25:22 -0800 Date: Mon, 29 Jan 1996 10:25:22 -0800 From: Paul Traina Message-Id: <199601291825.KAA10791@insecurity.shockwave.com> To: freebsd-stable@FreeBSD.ORG, pgiffuni@biblioteca.campus.unal.edu.co Subject: Re: Please include Mail Handler Cc: freebsd-current@FreeBSD.ORG Sender: owner-current@FreeBSD.ORG Precedence: bulk MH is already available as a port to FreeBSD, just go to /usr/ports/mail/mh and type make install. From owner-freebsd-current Mon Jan 29 11:04:40 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id LAA22151 for current-outgoing; Mon, 29 Jan 1996 11:04:40 -0800 (PST) Received: from alpha.xerox.com (alpha.Xerox.COM [13.1.64.93]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id LAA22128 Mon, 29 Jan 1996 11:04:27 -0800 (PST) Received: from crevenia.parc.xerox.com ([13.2.116.11]) by alpha.xerox.com with SMTP id <15155(14)>; Mon, 29 Jan 1996 11:03:24 PST Received: from localhost ([127.0.0.1]) by crevenia.parc.xerox.com with SMTP id <177478>; Mon, 29 Jan 1996 11:03:15 -0800 X-Mailer: exmh version 1.6.4 10/10/95 To: Pedro Giffuni cc: freebsd-stable@freebsd.org, freebsd-current@freebsd.org Subject: Re: Please include Mail Handler In-reply-to: Your message of "Mon, 29 Jan 1996 08:41:02 PST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 29 Jan 1996 11:03:12 PST From: Bill Fenner Message-Id: <96Jan29.110315pst.177478@crevenia.parc.xerox.com> Sender: owner-current@freebsd.org Precedence: bulk In message you write: >I want to propose the inclusion of the MH pacakage with the main >FreeBSD distribution. MH-6.8.3 is included with FreeBSD, in the ports/packages collection. Bill From owner-freebsd-current Mon Jan 29 11:09:39 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id LAA22546 for current-outgoing; Mon, 29 Jan 1996 11:09:39 -0800 (PST) Received: from grumble.grondar.za (root@grumble.grondar.za [196.7.18.130]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id LAA22523 Mon, 29 Jan 1996 11:09:25 -0800 (PST) Received: from localhost (mark@localhost [127.0.0.1]) by grumble.grondar.za (8.7.3/8.7.3) with SMTP id VAA03407; Mon, 29 Jan 1996 21:08:21 +0200 (SAT) Message-Id: <199601291908.VAA03407@grumble.grondar.za> X-Authentication-Warning: grumble.grondar.za: Host mark@localhost [127.0.0.1] didn't use HELO protocol To: Pedro Giffuni cc: freebsd-stable@FreeBSD.ORG, freebsd-current@FreeBSD.ORG Subject: Re: Please include Mail Handler Date: Mon, 29 Jan 1996 21:08:20 +0200 From: Mark Murray Sender: owner-current@FreeBSD.ORG Precedence: bulk Pedro Giffuni wrote: > I want to propose the inclusion of the MH pacakage with the main > FreeBSD distribution. Hmm.. while the idea has merits, you will have some problems convincing folks that this should be _mainstream_ code. MH is, however, a port. Look at /usr/ports/mail/mh (if you have the ports directory), or look at the ports collection. We include mh-6.8.3 as a standard port for FreeBSD (I know, because I am the maintainer). M -- Mark Murray 46 Harvey Rd, Claremont, Cape Town 7700, South Africa +27 21 61-3768 GMT+0200 Finger mark@grondar.za for PGP key From owner-freebsd-current Mon Jan 29 11:10:18 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id LAA22645 for current-outgoing; Mon, 29 Jan 1996 11:10:18 -0800 (PST) Received: from news1.gtn.com (news1.gtn.com [192.109.159.3]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id LAA22639 for ; Mon, 29 Jan 1996 11:10:14 -0800 (PST) Received: (from uucp@localhost) by news1.gtn.com (8.7.2/8.7.2) id UAA11519; Mon, 29 Jan 1996 20:00:22 +0100 (MET) Received: from knobel.gun.de (localhost [127.0.0.1]) by knobel.gun.de (8.7.3/8.7.3) with SMTP id SAA06815; Mon, 29 Jan 1996 18:34:08 +0100 (MET) Date: Mon, 29 Jan 1996 18:34:08 +0100 (MET) From: Andreas Klemm To: "Daniel M. Eischen" cc: current@freebsd.org Subject: Re: any ideas about this crash? In-Reply-To: <9601291105.AA00681@iworks.InterWorks.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org Precedence: bulk On Mon, 29 Jan 1996, Daniel M. Eischen wrote: > > > julian@freefall.freebsd.org:/a/julian/src/sys/compile/ERF4 > >CPU: Pentium (66.66-MHz 586-class CPU) > >----------- > >note: It's a 60Mhz, not 66, nor is it a 50 as seen below.... > >----------- > > I don't crash, but I do get odd MHz ratings. > > FreeBSD 2.2-CURRENT #0: Sun Jan 28 10:17:25 EST 1996 > deischen@rigel:/usr/src/sys/compile/rigel > CPU: Pentium (76.42-MHz 586-class CPU) > ^^^^^^^^^ > > Mine is 90MHz. FreeBSD 2.2-CURRENT #0: Sun Jan 28 16:07:44 MET 1996 root@:/local/FreeBSD/current/src/sys/compile/KNOBEL CPU: Pentium (99.46-MHz 586-class CPU) Hmm, mine is a 90MHz CPU driven at 100MHz. 99.46 is nearly 100 ;-) ASUS P55 board. -- andreas@knobel.gun.de /\/\___ Wiechers & Partner Datentechnik GmbH Andreas Klemm ___/\/\/ - Support Unix - aklemm@wup.de - \/ ftp://sunsite.unc.edu/pub/Linux/system/Printing/aps-491.tgz apsfilter - magic print filter 4lpd >>> knobel is powered by FreeBSD <<< From owner-freebsd-current Mon Jan 29 11:10:24 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id LAA22664 for current-outgoing; Mon, 29 Jan 1996 11:10:24 -0800 (PST) Received: from news1.gtn.com (news1.gtn.com [192.109.159.3]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id LAA22652 for ; Mon, 29 Jan 1996 11:10:21 -0800 (PST) Received: (from uucp@localhost) by news1.gtn.com (8.7.2/8.7.2) id UAA11527; Mon, 29 Jan 1996 20:00:29 +0100 (MET) Received: from knobel.gun.de (localhost [127.0.0.1]) by knobel.gun.de (8.7.3/8.7.3) with SMTP id SAA06944; Mon, 29 Jan 1996 18:43:11 +0100 (MET) Date: Mon, 29 Jan 1996 18:43:11 +0100 (MET) From: Andreas Klemm To: "Jordan K. Hubbard" cc: current@freebsd.org Subject: Re: Please test this on your system (and see if you crash) In-Reply-To: <17705.822895066@time.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org Precedence: bulk On Sun, 28 Jan 1996, Jordan K. Hubbard wrote: > Yes, this program may hose you. It hoses me, so be careful trying it > out. Not hosed ;-) > Its function is to allow anyone in group wheel to execute commands as > arbitrary users and it should be run setuid to root. In 2.1 it works > fine, in 2.2 I get a very strange lock-up which may just be me, thus > this email for confirmation. Jordan, I'm running -current of 28. Jan. I compiled this program, named it xxx, did a chmod 4755. I created a shellscript /tmp/yyy, chmod 700 owner: root. yyy does a '/bin/ls /' User andreas (me): uid=1000(andreas) gid=1000(andreas) groups=1000(andreas), 0(wheel), 5(operator) /tmp/xxx /tmp/yyy worked perfectly without hosing anything. Andreas /// -- andreas@knobel.gun.de /\/\___ Wiechers & Partner Datentechnik GmbH Andreas Klemm ___/\/\/ - Support Unix - aklemm@wup.de - \/ ftp://sunsite.unc.edu/pub/Linux/system/Printing/aps-491.tgz apsfilter - magic print filter 4lpd >>> knobel is powered by FreeBSD <<< From owner-freebsd-current Mon Jan 29 11:11:28 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id LAA22737 for current-outgoing; Mon, 29 Jan 1996 11:11:28 -0800 (PST) Received: from news1.gtn.com (news1.gtn.com [192.109.159.3]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id LAA22729 for ; Mon, 29 Jan 1996 11:11:18 -0800 (PST) Received: (from uucp@localhost) by news1.gtn.com (8.7.2/8.7.2) id UAA11524; Mon, 29 Jan 1996 20:00:25 +0100 (MET) Received: from knobel.gun.de (localhost [127.0.0.1]) by knobel.gun.de (8.7.3/8.7.3) with SMTP id SAA06847; Mon, 29 Jan 1996 18:36:05 +0100 (MET) Date: Mon, 29 Jan 1996 18:36:05 +0100 (MET) From: Andreas Klemm To: Chien-Ta Lee cc: freebsd-current@freebsd.org Subject: Re: lsdev broken In-Reply-To: <199601291524.XAA16030@Adonis.Dorm10.NCTU.edu.tw> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org Precedence: bulk On Mon, 29 Jan 1996, Chien-Ta Lee wrote: > cc -O2 -m486 -pipe -I/usr/src/usr.sbin/lsdev/../../sys -c /home/current/src/usr.sbin/lsdev/i386.c > /home/current/src/usr.sbin/lsdev/i386.c: In function `print_eisa': > /home/current/src/usr.sbin/lsdev/i386.c:168: structure has no member named `iobase' > /home/current/src/usr.sbin/lsdev/i386.c:169: structure has no member named `iobase' > /home/current/src/usr.sbin/lsdev/i386.c:169: structure has no member named `iosize' > *** Error code 1 > > Stop. Hi Chien-Ta, for your information: knobel# make cc -m486 -pipe -O2 -I/usr/src/usr.sbin/lsdev/../../sys -c /local/FreeBSD/current/src/usr.sbin/lsdev/lsdev.c cc -m486 -pipe -O2 -I/usr/src/usr.sbin/lsdev/../../sys -c /local/FreeBSD/current/src/usr.sbin/lsdev/i386.c cc -m486 -pipe -O2 -I/usr/src/usr.sbin/lsdev/../../sys -o lsdev lsdev.o i386.o gzip -c /usr/src/usr.sbin/lsdev/lsdev.8 > lsdev.8.gz -current from 28. Januar. Andreas /// -- andreas@knobel.gun.de /\/\___ Wiechers & Partner Datentechnik GmbH Andreas Klemm ___/\/\/ - Support Unix - aklemm@wup.de - \/ ftp://sunsite.unc.edu/pub/Linux/system/Printing/aps-491.tgz apsfilter - magic print filter 4lpd >>> knobel is powered by FreeBSD <<< From owner-freebsd-current Mon Jan 29 11:24:42 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id LAA23914 for current-outgoing; Mon, 29 Jan 1996 11:24:42 -0800 (PST) Received: from news1.gtn.com (news1.gtn.com [192.109.159.3]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id LAA23909 Mon, 29 Jan 1996 11:24:37 -0800 (PST) Received: (from uucp@localhost) by news1.gtn.com (8.7.2/8.7.2) id UAA14384; Mon, 29 Jan 1996 20:15:15 +0100 (MET) Received: from knobel.gun.de (localhost [127.0.0.1]) by knobel.gun.de (8.7.3/8.7.3) with SMTP id UAA08099; Mon, 29 Jan 1996 20:05:49 +0100 (MET) Message-ID: <310D1A85.41C67EA6@knobel.gun.de> Date: Mon, 29 Jan 1996 20:05:41 +0100 From: Andreas Klemm Organization: home sweet home X-Mailer: Mozilla 2.0b6a (X11; I; FreeBSD 2.2-CURRENT i386) MIME-Version: 1.0 To: pascal@ramoth.xs4all.nl CC: ports@freebsd.org, phk@critter.tfs.com, current@freebsd.org Subject: problems running X11R6 after compiling X with pgcc (gcc-2.7.2p-p6) on FreeBSD-current X-URL: http://www-iss.mach.uni-karlsruhe.de/pcg/pgcc-faq.html Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org Precedence: bulk Hi ! I compiled X11R6 on FreeBSD-current with the gcc 2.7.2p-p6 using the Compiler switches: -mpentium -pipe -O2. When trying to run X11 via xinit, the Xserver hung during startup. So I think, that the patched gcc somehow produced strange code... Any thoughts ? For other programs the new gcc seems to work ok. Andreas /// -- andreas@knobel.gun.de /\/\___ Wiechers & Partner Datentechnik GmbH Andreas Klemm ___/\/\/ - Support Unix - aklemm@wup.de - \/ ftp://sunsite.unc.edu/pub/Linux/system/Printing/aps-491.tgz apsfilter - magic print filter 4lpd >>> knobel is powered by FreeBSD <<< From owner-freebsd-current Mon Jan 29 11:25:01 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id LAA23970 for current-outgoing; Mon, 29 Jan 1996 11:25:01 -0800 (PST) Received: from smart.ruhr.de (smart.ruhr.de [193.100.176.36]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id LAA23953 for ; Mon, 29 Jan 1996 11:24:55 -0800 (PST) Received: (qmail-queue invoked by uid 1000); 29 Jan 1996 19:24:43 GMT To: Chien-Ta Lee CC: freebsd-current@freebsd.org Subject: Re: lsdev broken References: <199601291524.XAA16030@Adonis.Dorm10.NCTU.edu.tw> From: tom@smart.ruhr.de (Thomas Neumann) Date: 29 Jan 1996 20:24:42 +0100 In-Reply-To: Chien-Ta Lee's message of Mon, 29 Jan 1996 23:24:21 +0800 (CST) Message-ID: <8720oikdmt.fsf@smart.ruhr.de> Organization: Ruhr.DE Lines: 54 Sender: owner-current@freebsd.org Precedence: bulk Yep, that one stopped my "make world" a few minutes ago, too. I was so anoyed that I just *had* to fix it :-) See the patch below, which modifies lsdev to print a comma separated list of I/O ranges (if there's more than one entry. With a single I/O range the output should be compatible with prevoius versions of lsdev). Someone with an EISA system should try this, as I don't have an EISA machine and thus the code is untested by me. -t *** usr.sbin/lsdev/i386.c.old Wed Dec 13 17:07:19 1995 --- usr.sbin/lsdev/i386.c Mon Jan 29 20:15:21 1996 *************** *** 159,171 **** static void print_eisa(struct devconf *dc) { struct eisa_device *e_dev = (struct eisa_device *)dc->dc_data; ! printf("%s%d\tat eisa0 slot %d # %#lx-%#lx", dc->dc_name, dc->dc_unit, ! e_dev->ioconf.slot, ! e_dev->ioconf.iobase, ! e_dev->ioconf.iobase + e_dev->ioconf.iosize - 1); if(e_dev->ioconf.irq) printf(" irq %d", ffs(e_dev->ioconf.irq) - 1); --- 159,182 ---- static void + print_eisa_ioaddrs(struct resvlist *list) + { + resvaddr_t *rp; + + for (rp = list->lh_first; rp; rp = rp->links.le_next) + printf("%#lx-%#lx%s", rp->addr, rp->addr + rp->size - 1, + rp->links.le_next ? ", " : ""); + } + + static void print_eisa(struct devconf *dc) { struct eisa_device *e_dev = (struct eisa_device *)dc->dc_data; ! ! printf("%s%d\tat eisa0 slot %d # ", dc->dc_name, dc->dc_unit, ! e_dev->ioconf.slot); ! print_eisa_ioaddrs(&e_dev->ioconf.ioaddrs); ! if(e_dev->ioconf.irq) printf(" irq %d", ffs(e_dev->ioconf.irq) - 1); From owner-freebsd-current Mon Jan 29 12:59:50 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id MAA02611 for current-outgoing; Mon, 29 Jan 1996 12:59:50 -0800 (PST) Received: from eel.dataplex.net (EEL.DATAPLEX.NET [199.183.109.245]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id MAA02600 for ; Mon, 29 Jan 1996 12:59:40 -0800 (PST) Received: from [199.183.109.242] (cod [199.183.109.242]) by eel.dataplex.net (8.6.11/8.6.9) with SMTP id OAA03172; Mon, 29 Jan 1996 14:58:37 -0600 X-Sender: rkw@shark.dataplex.net Message-Id: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Mon, 29 Jan 1996 14:58:50 -0600 To: Nate Williams From: Richard Wackerbarth Subject: Re: I'm rather annoyed with -current. Cc: current@freebsd.org Sender: owner-current@freebsd.org Precedence: bulk Nate Williams writes: >You need to build and install rpcgen *before* the include files are >built. There is also a dependency problem with either the libraries or >the crt0.o file (I don't remember which one is first.) > >It basically boils down to the fact that we *should* be building the >sources out of the src tree and not out of the stuff in >/usr/{lib|include} etc... (Which I've argued against in the past as >un-necessary and complex, but I think we've now reached critical mass >and require it.) Now, while we are at it, will you also agree that we should not be using the tools in /usr/bin either? In particular, there are three (logical) systems to consider. A. The host B. The cross-compiler C. The target "make world" runs through everything twice in order to produce both "B" and "C". In the process, it trashes "A". If we recognize that each pass of "world" is really just like a compilation of one tree, we can do everything with a straight forward "make". First we make the tools into the object tree and then we turn around and make the target binaries using those tools. Since we want to fold the sources, we need to have "make" look into the tree for the current definition of the tools like rpcgen. ---- Richard Wackerbarth rkw@dataplex.net From owner-freebsd-current Mon Jan 29 13:09:54 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id NAA03470 for current-outgoing; Mon, 29 Jan 1996 13:09:54 -0800 (PST) Received: from rocky.sri.MT.net (rocky.sri.MT.net [204.182.243.10]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id NAA03461 for ; Mon, 29 Jan 1996 13:09:44 -0800 (PST) Received: (from nate@localhost) by rocky.sri.MT.net (8.6.12/8.6.12) id OAA09260; Mon, 29 Jan 1996 14:11:39 -0700 Date: Mon, 29 Jan 1996 14:11:39 -0700 From: Nate Williams Message-Id: <199601292111.OAA09260@rocky.sri.MT.net> To: Richard Wackerbarth Cc: Nate Williams , current@freebsd.org Subject: Re: I'm rather annoyed with -current. In-Reply-To: References: Sender: owner-current@freebsd.org Precedence: bulk > Nate Williams writes: > > >You need to build and install rpcgen *before* the include files are > >built. There is also a dependency problem with either the libraries or > >the crt0.o file (I don't remember which one is first.) > > > >It basically boils down to the fact that we *should* be building the > >sources out of the src tree and not out of the stuff in > >/usr/{lib|include} etc... (Which I've argued against in the past as > >un-necessary and complex, but I think we've now reached critical mass > >and require it.) > > Now, while we are at it, will you also agree that we should not be using > the tools in /usr/bin either? Unfortunately, we *have* to use them. You can't build a c-compiler w/out a C-compiler. Obviously, all of the support tools that go along with are also important. > In particular, there are three (logical) systems to consider. > > A. The host > B. The cross-compiler > C. The target > > "make world" runs through everything twice in order to produce both "B" and "C". > In the process, it trashes "A". If we recognize that each pass of "world" > is really just like a compilation of one tree, we can do everything with a > straight forward "make". While I agree in theory, I don't think we can make it all work in one simple 'make'. You *must* assume certain programs exist, and they must exist prior to a system build. This in itself isn't a problem, but it is not only possible but highly probably that remaining parts of the system (including the tools themselves) should be built using themselves. > First we make the tools into the object tree and then we turn around and > make the target binaries using those tools. True, but we still have the same problems as before. We update our C-compiler to avoid the -O2 strength reduce bug. For this arguement, let's assume we can't avoid the bug with compiler flags. In order to fully guarantee that the bug is irradicated from the system, we must first build gcc using the buggy compiler. Then, we should rebuild gcc again using the newly built gcc (which won't work in the current model since you can't over-write running binaries). Then, the final gcc built should be used to build the rest of the tools. We still have the same dependency problems that the current system has, except that in the solution that doesn't yet exist, we don't clobber the hosts system. > Since we want to fold the sources, we need to have "make" look into the > tree for the current definition of the tools like rpcgen. Again, the dependencies are still there. We still have to build rpcgen before we can build the include files. I guess I may be thinking that changing the tools to build in-place is a good thing on paper, but I don't see it solving any of the existing problems we have. Nate From owner-freebsd-current Mon Jan 29 14:01:07 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id OAA08163 for current-outgoing; Mon, 29 Jan 1996 14:01:07 -0800 (PST) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id OAA08158 Mon, 29 Jan 1996 14:01:01 -0800 (PST) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id OAA04701; Mon, 29 Jan 1996 14:58:37 -0700 From: Terry Lambert Message-Id: <199601292158.OAA04701@phaeton.artisoft.com> Subject: Optimization topics To: bde@zeta.org.au (Bruce Evans) Date: Mon, 29 Jan 1996 14:58:36 -0700 (MST) Cc: dyson@freefall.freebsd.org, terry@lambert.org, current@freefall.freebsd.org In-Reply-To: <199601262317.KAA27798@godzilla.zeta.org.au> from "Bruce Evans" at Jan 27, 96 10:17:54 am X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.ORG Precedence: bulk With all the pipe optimization stuff and all the work I've been doing in the Windows95 kernel recently. it occurs to me that there might be room for some optimizations in FreeBSD that Microsoft totally buggered up in Windows95. Specifically, it should be possible to run FreeBSD with the unaligned access bit set to disallow unaligned access of word/dword/qword objects. At the very least, the kernel code should be clean of this cruft. In Windows95, some programmers apparently believe that adding 3 bytes to the end of a packed structure containing a byte followed by 20 longs means "align to a longword boundry" -- at least that's what the comments in the DDK header files say. Clearly, these people never ran their own code in a kernel debugger, or they simply failed to see the significance of unaligned access. Many of the problems derive from unaligned stacks being passed down to otherwise "correct" code. Fie. Maybe this is a direction that can be explored? Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-current Mon Jan 29 14:19:28 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id OAA09389 for current-outgoing; Mon, 29 Jan 1996 14:19:28 -0800 (PST) Received: from localhost.cdrom.com (localhost.cdrom.com [127.0.0.1]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id OAA09378 Mon, 29 Jan 1996 14:19:19 -0800 (PST) Message-Id: <199601292219.OAA09378@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: Host localhost.cdrom.com [127.0.0.1] didn't use HELO protocol To: tom@smart.ruhr.de (Thomas Neumann) cc: Chien-Ta Lee , freebsd-current@FreeBSD.ORG Subject: Re: lsdev broken In-reply-to: Your message of "29 Jan 1996 20:24:42 +0100." <8720oikdmt.fsf@smart.ruhr.de> Date: Mon, 29 Jan 1996 14:19:18 -0800 From: "Justin T. Gibbs" Sender: owner-current@FreeBSD.ORG Precedence: bulk > >Yep, that one stopped my "make world" a few minutes ago, too. >I was so anoyed that I just *had* to fix it :-) See the patch >below, which modifies lsdev to print a comma separated list >of I/O ranges (if there's more than one entry. With a single >I/O range the output should be compatible with prevoius versions >of lsdev). Someone with an EISA system should try this, as >I don't have an EISA machine and thus the code is untested by me. > >-t The patch looks good except that it should also print out the maddrs. To stop it from core dumping, you will also need to externalize the two lists in eisaconf.c otherwise they won't be copied out and the pointers will be garbage. I won't be able to do the work until Tuesday night, so if you don't mind finishing this up, be my guest. -- Justin T. Gibbs =========================================== FreeBSD: Turning PCs into workstations =========================================== From owner-freebsd-current Mon Jan 29 14:36:44 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id OAA16261 for current-outgoing; Mon, 29 Jan 1996 14:36:44 -0800 (PST) Received: from news1.gtn.com (news1.gtn.com [192.109.159.3]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id OAA16216 Mon, 29 Jan 1996 14:36:30 -0800 (PST) Received: (from uucp@localhost) by news1.gtn.com (8.7.2/8.7.2) id XAA12111; Mon, 29 Jan 1996 23:15:15 +0100 (MET) Received: from knobel.gun.de (localhost [127.0.0.1]) by knobel.gun.de (8.7.3/8.7.3) with SMTP id XAA01190; Mon, 29 Jan 1996 23:05:33 +0100 (MET) Date: Mon, 29 Jan 1996 23:05:31 +0100 (MET) From: Andreas Klemm To: Pedro Giffuni cc: freebsd-stable@FreeBSD.ORG, freebsd-current@FreeBSD.ORG Subject: Re: Please include Mail Handler In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@FreeBSD.ORG Precedence: bulk Hi Pedro ! On Mon, 29 Jan 1996, Pedro Giffuni wrote: > Hi, > I want to propose the inclusion of the MH pacakage with the main > FreeBSD distribution. > [...] It's already in the ports collection... See the fine FreeBSD manual for more informations (-> http://www.freebsd.org/). You might also find it in /usr/share/doc/handbook on your local disk. BTW: noone would like to increase the main FreeBSD source tree for such a mail program. It already lasts long enough to do a make world. And ... everybody has his 'pet toy'. Who should deceide, what to include and what not ? Where should this end ? In a 600MB source tree and nobody has time or room enough to run a make world ?! ;-) Andreas /// -- andreas@knobel.gun.de /\/\___ Wiechers & Partner Datentechnik GmbH Andreas Klemm ___/\/\/ - Support Unix - aklemm@wup.de - \/ ftp://sunsite.unc.edu/pub/Linux/system/Printing/aps-491.tgz apsfilter - magic print filter 4lpd >>> knobel is powered by FreeBSD <<< From owner-freebsd-current Mon Jan 29 14:41:44 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id OAA16731 for current-outgoing; Mon, 29 Jan 1996 14:41:44 -0800 (PST) Received: from ibp.ibp.fr (ibp.ibp.fr [132.227.60.30]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id OAA16719 for ; Mon, 29 Jan 1996 14:41:33 -0800 (PST) Received: from blaise.ibp.fr (blaise.ibp.fr [132.227.60.1]) by ibp.ibp.fr (8.6.12/jtpda-5.0) with ESMTP id XAA23460 ; Mon, 29 Jan 1996 23:41:22 +0100 Received: from (uucp@localhost) by blaise.ibp.fr (8.6.12/jtpda-5.0) with UUCP id XAA18383 ; Mon, 29 Jan 1996 23:41:21 +0100 Received: (from roberto@localhost) by keltia.freenix.fr (8.7.3/keltia-uucp-2.7) id VAA03554; Mon, 29 Jan 1996 21:00:47 +0100 (MET) From: Ollivier Robert Message-Id: <199601292000.VAA03554@keltia.freenix.fr> Subject: Re: Please test this on your system (and see if you crash) To: jkh@time.cdrom.com (Jordan K. Hubbard) Date: Mon, 29 Jan 1996 21:00:47 +0100 (MET) Cc: current@freebsd.org In-Reply-To: <17705.822895066@time.cdrom.com> from "Jordan K. Hubbard" at "Jan 28, 96 09:57:46 pm" X-Operating-System: FreeBSD 2.2-CURRENT ctm#1586 X-Mailer: ELM [version 2.4ME+ PL3 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org Precedence: bulk It seems that Jordan K. Hubbard said: > Yes, this program may hose you. It hoses me, so be careful trying it > out. Seems to work here. Last "make world" yesterday: -rw-r--r-- 1 root bin 888750 Jan 29 00:17 /usr/src/make.world -rwsr-xr-x 1 root wheel 8822 Jan 29 20:56 foo* -rw------- 1 roberto staff 1667 Jan 29 20:56 foo.c 205 [20:56] roberto@keltia:/tmp> ./foo roberto has logged on ttyp4 from :0.0. roberto has logged on ttyp5 from :0.0. roberto has logged on ttyp6 from :0.0. roberto has logged on ttyp7 from :0.0. roberto has logged on ttyv0 from local. 201 [20:56] root@keltia:/tmp# id uid=0(root) gid=10(staff) groups=10(staff), 0(wheel), 2(kmem), 5(operator), 6(man), 8(news), 15(cvs), 20(majordom), 21(list), 100(copains), 117(dialer), 2000(dos), 2001(tex) 211 [20:58] roberto@keltia:/tmp> ./foo id uid=0(root) gid=10(staff) groups=10(staff), 0(wheel), 2(kmem), 5(operator), 6(man), 8(news), 15(cvs), 20(majordom), 21(list), 100(copains), 117(dialer), 2000(dos), 2001(tex) It a dangerous program though... No password asked, nothing except "wheel"... My own program ("calife") ask for it (unless compiled with --relaxed). 212 [20:58] roberto@keltia:/tmp> ... Password: roberto has logged on ttyp4 from :0.0. roberto has logged on ttyp5 from :0.0. roberto has logged on ttyp6 from :0.0. roberto has logged on ttyp7 from :0.0. roberto has logged on ttyv0 from local. 201 [DING!] root@keltia:/tmp# What does a "ktrace foo" give you ? -- Ollivier ROBERT -=- The daemon is FREE! -=- roberto@keltia.frmug.fr.net FreeBSD keltia.freenix.fr 2.2-CURRENT #1: Sun Jan 14 20:23:45 MET 1996 From owner-freebsd-current Mon Jan 29 14:46:09 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id OAA17206 for current-outgoing; Mon, 29 Jan 1996 14:46:09 -0800 (PST) Received: from time.cdrom.com (time.cdrom.com [192.216.222.226]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id OAA17195 for ; Mon, 29 Jan 1996 14:46:02 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by time.cdrom.com (8.6.12/8.6.9) with SMTP id OAA12032; Mon, 29 Jan 1996 14:45:44 -0800 To: Nate Williams cc: current@FreeBSD.org Subject: Re: I'm rather annoyed with -current. In-reply-to: Your message of "Mon, 29 Jan 1996 08:56:51 MST." <199601291556.IAA08024@rocky.sri.MT.net> Date: Mon, 29 Jan 1996 14:45:43 -0800 Message-ID: <12030.822955543@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-current@FreeBSD.org Precedence: bulk > Both of these problems are due to ordering problems in the Makefile, > which can be fixed in the 'world' target, but don't really fit into the > current model used. Ah. Feh, this REALLY needs to be fixed. -current is broken right now, plain and simple, and if the people who implemented the features which have added all this dependency brokenness don't stand up and finish the job soon, I think it might be reasonable to start calling for the backing-out of certain changes, the thread stuff coming especially to mind. Leaving -current broken for this long is truly not acceptable and it's persisted for long enough. > It basically boils down to the fact that we *should* be building the > sources out of the src tree and not out of the stuff in > /usr/{lib|include} etc... (Which I've argued against in the past as > un-necessary and complex, but I think we've now reached critical mass > and require it.) I agree. Do I hear a volunteer? :-) > > I haven't been able to build -stable for several weeks now - is it Ack, typo, I meant -current. Jordan From owner-freebsd-current Mon Jan 29 14:56:47 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id OAA18271 for current-outgoing; Mon, 29 Jan 1996 14:56:47 -0800 (PST) Received: from ref.tfs.com (ref.tfs.com [140.145.254.251]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id OAA18263 for ; Mon, 29 Jan 1996 14:56:41 -0800 (PST) Received: (from julian@localhost) by ref.tfs.com (8.6.12/8.6.9) id OAA06769; Mon, 29 Jan 1996 14:55:51 -0800 From: Julian Elischer Message-Id: <199601292255.OAA06769@ref.tfs.com> Subject: Re: I'm rather annoyed with -current. To: nate@sri.MT.net (Nate Williams) Date: Mon, 29 Jan 1996 14:55:51 -0800 (PST) Cc: rkw@dataplex.net, nate@sri.MT.net, current@FreeBSD.org In-Reply-To: <199601292111.OAA09260@rocky.sri.MT.net> from "Nate Williams" at Jan 29, 96 02:11:39 pm X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-current@FreeBSD.org Precedence: bulk > > Unfortunately, we *have* to use them. You can't build a c-compiler > w/out a C-compiler. Obviously, all of the support tools that go along > with are also important. > > > > First we make the tools into the object tree and then we turn around and > > make the target binaries using those tools. When I make OSF1 it starts off with some stashed away binaries of cc then remakes them using the sources.. then it remakes the libs with the new compilers then it remakes the compilers with the new libs and then old new compilers then compiles the rest of the tree using the new libs and new new compilers It doesn't touch what's on the host system for anything.. it even looks in the source tree for the /usr/share/mk stuff which BTW is based on the BSD stuff. From owner-freebsd-current Mon Jan 29 14:59:40 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id OAA18444 for current-outgoing; Mon, 29 Jan 1996 14:59:40 -0800 (PST) Received: from werple.net.au (werple.mira.net.au [203.9.190.18]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id OAA18426 for ; Mon, 29 Jan 1996 14:59:32 -0800 (PST) Received: from cimaxp1.UUCP (Ucimlogi@localhost) by werple.net.au (8.7/8.7.1) with UUCP id JAA06436 for mira!FreeBSD.ORG!current; Tue, 30 Jan 1996 09:52:40 +1100 (EST) Message-Id: <199601292252.JAA06436@werple.net.au> X-Authentication-Warning: werple.net.au: Ucimlogi set sender to cimaxp1!jb using -f Received: by cimaxp1.cimlogic.com.au; (5.65/1.1.8.2/10Sep95-0953AM) id AA14234; Tue, 30 Jan 1996 09:51:37 +1100 From: John Birrell Subject: Re: I'm rather annoyed with -current. To: sri.MT.net!nate@werple.net.au (Nate Williams) Date: Tue, 30 Jan 1996 09:51:31 +1100 (EST) Cc: time.cdrom.com!jkh@werple.net.au, FreeBSD.ORG!current@werple.net.au In-Reply-To: <199601291556.IAA08024@rocky.sri.MT.net> from "Nate Williams" at Jan 29, 96 08:56:51 am X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-current@FreeBSD.ORG Precedence: bulk > Both of these problems are due to ordering problems in the Makefile, > which can be fixed in the 'world' target, but don't really fit into the > current model used. I agree with this. The changes are not bugs in the -current code committed. Instead they show up a bogus build process. > > You need to build and install rpcgen *before* the include files are > built. There is also a dependency problem with either the libraries or > the crt0.o file (I don't remember which one is first.) crt0 and libc will build OK with installed tools, but they *must* be installed _together_. If you check the logic in /usr/src/Makefile you will see that, on the surface, they *should* be built and installed together because they are not part of separate targets. The fact that they are not must be the result of 'make depend'. Sigh. > > It basically boils down to the fact that we *should* be building the > sources out of the src tree and not out of the stuff in > /usr/{lib|include} etc... (Which I've argued against in the past as > un-necessary and complex, but I think we've now reached critical mass > and require it.) It is not simply a matter of using -nostdinc, -nostdlib and -nostartfiles although these are still needed. There are too many race conditions in the software design. Look at the build process and you will see that it only works at all because it tries to install *all* header files up front regardless of what their dependencies are. Normally this is OK, but in the rpcgen case it is not (though no fault of the rpcgen code). [Stands up on soap box to begin preaching... I've been flamed by NetBSD folk for saying what I'm about to, but I'll say it anyway. 8-)] In the *BSD software design there is no concept of header files that are private to the kernel/driver build and header files that are purely for user-land code. There is also no modularity within the design - everything depends on everything. As a result of this design, the build process has to take all the sys header files and install them for the user-land code to compile against. And because they are all available, people expect to write code that *requires* their use. Including the build tools... so the dependencies become horribly complex. And race conditions arise. At any time, the installed /usr/include /usr/bin /usr/lib etc *should* be capable of starting a 'make universe' (since the world is imperfect) and there should be a concept of 'release' to update /usr/include /usr/bin /usr/lib _only_ when the 'make universe' has been successful in creating a complete set of compatible files to install in the traditional places. If I had my way [And of course I think the world is imperfect because I haven't had my way yet 8-).] the basic set of header files that user-land programs compile against would not contain any implementation specific stuff and in particular no device driver or kernel specific stuff. If you want a list of these header files, take a look at POSIX 1003.1b-1993 Annex C. That's a start. These don't include any networking stuff - the basic build tools should not require it. Note that these header files do not contain enough definitions for things like executable file format etc. Programs like ld need extra header files, but there additional header files should not be visible to the build process until the point where they are required. These header files should *only* be installed _with_ the program (or library) that they are compatible with. And the rest of the build process should work the same way. By _preventing_ the build process from being able to access a file (include, library, program) until all its dependencies have been processed, race conditions are avoided - you just can't build the software without getting the design right. The build order of libraries and programs should NOT be allowed to change depending on the poor software design and coding in C source. [This is what is happening at the moment - make depend can't handle race conditions so it gets the build order wrong - someone forgot to teach it that there *is* no correct order]. The order that directories are processed should be *designed* into the makefiles. This is the way that it looks when you read the current makefiles. But when you see the way it works... If you're not ready to flame me yet, take this: FreeBSD should STOP USING MAKE DEPEND. You need to ensure that at *least* the order that directories are built does not change because of something like make depend. The build process should not have a separate command to work out dependencies. These should be determined on-the-run by make so that you can't build the system without the dependencies from being checked. Two years ago we bit the bullet and stopped using make for these reasons (and many more like version control, traceablility, automated software testing before release). So I know that what I am saying can be done! Regards, -- John Birrell CIMlogic Pty Ltd jb@cimlogic.com.au 119 Cecil Street Ph +61 3 9690 6900 South Melbourne Vic 3205 Fax +61 3 9690 6650 Australia Mob +61 18 353 137 From owner-freebsd-current Mon Jan 29 15:19:04 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id PAA20217 for current-outgoing; Mon, 29 Jan 1996 15:19:04 -0800 (PST) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id PAA20201 for ; Mon, 29 Jan 1996 15:18:57 -0800 (PST) Received: from msmith@localhost by genesis.atrad.adelaide.edu.au (8.6.12/8.6.9) id KAA11874; Tue, 30 Jan 1996 10:01:09 +1030 From: Michael Smith Message-Id: <199601292331.KAA11874@genesis.atrad.adelaide.edu.au> Subject: Re: I'm rather annoyed with -current. To: jkh@time.cdrom.com (Jordan K. Hubbard) Date: Tue, 30 Jan 1996 10:01:09 +1030 (CST) Cc: current@freebsd.org In-Reply-To: <9833.822927764@time.cdrom.com> from "Jordan K. Hubbard" at Jan 29, 96 07:02:44 am MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org Precedence: bulk Jordan K. Hubbard stands accused of saying: > > Not only has the thread_init race problem still NOT been fixed (try a > make world in -current using a 2.1-RELEASE system as the base - it > will fall over!) but today we have this new problem: Until my "new" hack machine pulled over to the side of the desk billowing smoke, I'd establiched that the following were necessary prior to building -current under 2.1R : - build and install 'install' (required in the tools step) - build and install 'rpcgen' (required before building includes) - build and install libc (required by crt0) > ===> lib/librpcsvc This looks like the rpcgen one. > I haven't been able to build -stable for several weeks now - is it > just me, managing to try it on every single day that the tree is > broken? I'm about to give up on the whole idea of a 2.2-SNAP, to be > honest! :-( Hmm, did you mean -stable or -current there? I'm about to rebuild -stable on several of our systems, but if it's broken I won't 8) > Jordan -- ]] Mike Smith, Software Engineer msmith@atrad.adelaide.edu.au [[ ]] Genesis Software genesis@atrad.adelaide.edu.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control (ph/fax) +61-8-267-3039 [[ ]] "wherever you go, there you are" - Buckaroo Banzai [[ From owner-freebsd-current Mon Jan 29 15:21:44 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id PAA20646 for current-outgoing; Mon, 29 Jan 1996 15:21:44 -0800 (PST) Received: from eel.dataplex.net (EEL.DATAPLEX.NET [199.183.109.245]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id PAA20603 for ; Mon, 29 Jan 1996 15:21:18 -0800 (PST) Received: from [199.183.109.242] (cod [199.183.109.242]) by eel.dataplex.net (8.6.11/8.6.9) with SMTP id RAA03696; Mon, 29 Jan 1996 17:20:46 -0600 X-Sender: rkw@shark.dataplex.net Message-Id: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Mon, 29 Jan 1996 17:20:50 -0600 To: Julian Elischer From: Richard Wackerbarth Subject: Re: I'm rather annoyed with -current. Cc: nate@sri.MT.net, current@FreeBSD.org Sender: owner-current@FreeBSD.org Precedence: bulk >> >> Unfortunately, we *have* to use them. You can't build a c-compiler >> w/out a C-compiler. Obviously, all of the support tools that go along >> with are also important. >> >> >> > First we make the tools into the object tree and then we turn around and >> > make the target binaries using those tools. > >When I make OSF1 >it starts off with some stashed away binaries of cc >then remakes them using the sources.. >then it remakes the libs with the new compilers >then it remakes the compilers with the new libs and then old new compilers >then compiles the rest of the tree using the new libs and new new compilers > >It doesn't touch what's on the host system for anything.. >it even looks in the source tree for the /usr/share/mk stuff >which BTW is based on the BSD stuff. And that is just the idea that I am proposing. OSF1 isn't the only system to do this. And we should do so also. ---- Richard Wackerbarth rkw@dataplex.net From owner-freebsd-current Mon Jan 29 15:25:01 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id PAA21102 for current-outgoing; Mon, 29 Jan 1996 15:25:01 -0800 (PST) Received: from jhome.DIALix.COM (root@jhome.DIALix.COM [192.203.228.69]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id PAA21083 for ; Mon, 29 Jan 1996 15:24:52 -0800 (PST) Received: from localhost.DIALix.oz.au (peter@localhost.DIALix.oz.au [127.0.0.1]) by jhome.DIALix.COM (8.7.3/8.7.3) with SMTP id HAA01647 for ; Tue, 30 Jan 1996 07:24:17 +0800 (WST) Message-Id: <199601292324.HAA01647@jhome.DIALix.COM> X-Authentication-Warning: jhome.DIALix.COM: Host peter@localhost.DIALix.oz.au [127.0.0.1] didn't use HELO protocol To: current@freebsd.org Subject: Linux Netscape 2.0b6a? Date: Tue, 30 Jan 1996 07:24:16 +0800 From: Peter Wemm Sender: owner-current@freebsd.org Precedence: bulk I guess this is an odd question, but I've been trying to figure out what's wrong with the Linux native netscape when running under our emulator. Specifically, check http://proto.netscape.com/ and see if it correctly gives you scroll bars, or whether you have to press arrow keys first. The scroll bars do not seem to be being resized properly on initial open of a non-paneled screen either. It happens to me whether I run it under 2.1R through to the current version that I've been beating up in my kernel in order to fix problems with it and fill in missing stuff. At this stage, it'd be really useful for me to know: 1: Does 2.0b6a actually work on linux properly? If so, what libc, libm and ld.so is in use? (the rest of the X11/Motif stuff is statically linked) 2: Does the Linux 2.0b6a version run on the NetBSD linux emulator ok? 3: Does it work for anybody else on FreeBSD? I know the BSDI version of 2.0b6a works fine for me, but it doesn't have Java support in it. I've just about run out of ideas of what to look for.. I've tried a fair few things already, including imitating the linux signal stack frames with a specific trampoline and sigreturn for those. I've found some non-trivial bugs in the emulator itself that I'm really suprised have not turned up by now (including kernel VM leaks, mismapped pages, not freeing resources when doing error recovery, etc). Any suggestions would be appreciated! -Peter From owner-freebsd-current Mon Jan 29 15:25:44 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id PAA21184 for current-outgoing; Mon, 29 Jan 1996 15:25:44 -0800 (PST) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id PAA21162 Mon, 29 Jan 1996 15:25:33 -0800 (PST) Received: from msmith@localhost by genesis.atrad.adelaide.edu.au (8.6.12/8.6.9) id KAA11949; Tue, 30 Jan 1996 10:07:09 +1030 From: Michael Smith Message-Id: <199601292337.KAA11949@genesis.atrad.adelaide.edu.au> Subject: Re: Please include Mail Handler To: pgiffuni@biblioteca.campus.unal.edu.co (Pedro Giffuni) Date: Tue, 30 Jan 1996 10:07:08 +1030 (CST) Cc: freebsd-stable@FreeBSD.ORG, freebsd-current@FreeBSD.ORG In-Reply-To: from "Pedro Giffuni" at Jan 29, 96 11:41:02 am MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.ORG Precedence: bulk Pedro Giffuni stands accused of saying: > Hi, > I want to propose the inclusion of the MH pacakage with the main > FreeBSD distribution. It already is : /usr/ports/mail/mh. -- ]] Mike Smith, Software Engineer msmith@atrad.adelaide.edu.au [[ ]] Genesis Software genesis@atrad.adelaide.edu.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control (ph/fax) +61-8-267-3039 [[ ]] "wherever you go, there you are" - Buckaroo Banzai [[ From owner-freebsd-current Mon Jan 29 15:39:39 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id PAA22618 for current-outgoing; Mon, 29 Jan 1996 15:39:39 -0800 (PST) Received: from time.cdrom.com (time.cdrom.com [192.216.222.226]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id PAA22607 for ; Mon, 29 Jan 1996 15:39:27 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by time.cdrom.com (8.6.12/8.6.9) with SMTP id PAA12598; Mon, 29 Jan 1996 15:38:54 -0800 To: the revolution will not be televised cc: current@freebsd.org Subject: Re: I'm rather annoyed with -current. In-reply-to: Your message of "Mon, 29 Jan 1996 13:20:33 EST." <199601291820.NAA26785@skynet.ctr.columbia.edu> Date: Mon, 29 Jan 1996 15:38:53 -0800 Message-ID: <12594.822958733@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-current@freebsd.org Precedence: bulk > Uhm... not to sound patronizing, but this has been discussed already. > You have to do the following things: Yes, I know it's been discussed already (though I somehow didn't flash on the rpcgen stuff until later - it's been a pretty busy week, OK? My cache was flushed several times :-) but it's still largely irrelevant. The tree is broken. It should be fixed. It should require NO, NADA, NONE, ZIP, ZERO special actions to allow a `make world' to work and if we've screwed up the toolchain dependencies then we need to fix those or we need to eliminate the dependencies altogether. I don't think that this is too much to ask, and the tree has successfully bootstrapped itself at many times in its history (often from considerably "far back") and think that, at the very MINIMUM, -current should always be capable of bootstrapping itself from the last major release. This is not the case now, the tree is broken. QED. Jordan From owner-freebsd-current Mon Jan 29 15:39:49 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id PAA22651 for current-outgoing; Mon, 29 Jan 1996 15:39:49 -0800 (PST) Received: from ibp.ibp.fr (ibp.ibp.fr [132.227.60.30]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id PAA22603 Mon, 29 Jan 1996 15:39:22 -0800 (PST) Received: from blaise.ibp.fr (blaise.ibp.fr [132.227.60.1]) by ibp.ibp.fr (8.6.12/jtpda-5.0) with ESMTP id AAA23921 ; Tue, 30 Jan 1996 00:38:52 +0100 Received: from (uucp@localhost) by blaise.ibp.fr (8.6.12/jtpda-5.0) with UUCP id AAA18549 ; Tue, 30 Jan 1996 00:38:44 +0100 Received: (from roberto@localhost) by keltia.freenix.fr (8.7.3/keltia-uucp-2.7) id AAA10167; Tue, 30 Jan 1996 00:30:46 +0100 (MET) From: Ollivier Robert Message-Id: <199601292330.AAA10167@keltia.freenix.fr> Subject: Re: Please include Mail Handler To: pgiffuni@biblioteca.campus.unal.edu.co (Pedro Giffuni) Date: Tue, 30 Jan 1996 00:30:46 +0100 (MET) Cc: freebsd-stable@FreeBSD.ORG, freebsd-current@FreeBSD.ORG In-Reply-To: from "Pedro Giffuni" at "Jan 29, 96 11:41:02 am" X-Operating-System: FreeBSD 2.2-CURRENT ctm#1586 X-Mailer: ELM [version 2.4ME+ PL3 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.ORG Precedence: bulk It seems that Pedro Giffuni said: > MH is a public domain package developed by the RAND corporation that > permits mail management with a shell. I knew of it because it is > necesary for using XMH, and several operating systems like AIX include it. I object strongly against this. I can't stand MH (and I'm sure others can't stand Elm or PINE) so it is really a matter of personal preference. Including it in the main base means more code to maintain and force people to have it. The argument can be used for any package other than Mail so its why we don't have one of them in the base code. > The latest version I know, mh-6.8.tar.gz, also includes support for > POP2-POP3 and IMAPD (if NNTP is present it can also be handled). The latest is 6.8.3 and have been in ports for a long time. -- Ollivier ROBERT -=- The daemon is FREE! -=- roberto@keltia.frmug.fr.net FreeBSD keltia.freenix.fr 2.2-CURRENT #1: Sun Jan 14 20:23:45 MET 1996 From owner-freebsd-current Mon Jan 29 17:04:10 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id RAA00166 for current-outgoing; Mon, 29 Jan 1996 17:04:10 -0800 (PST) Received: from time.cdrom.com (time.cdrom.com [192.216.222.226]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id RAA00127 Mon, 29 Jan 1996 17:04:01 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by time.cdrom.com (8.6.12/8.6.9) with SMTP id RAA10450; Mon, 29 Jan 1996 17:01:42 -0800 To: Pedro Giffuni cc: freebsd-stable@FreeBSD.ORG, freebsd-current@FreeBSD.ORG Subject: Re: Please include Mail Handler In-reply-to: Your message of "Mon, 29 Jan 1996 11:41:02 EST." Date: Mon, 29 Jan 1996 17:01:42 -0800 Message-ID: <10445.822963702@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-current@FreeBSD.ORG Precedence: bulk > I want to propose the inclusion of the MH pacakage with the main > FreeBSD distribution. The MH program is scheduled for incorporation into the mainline just 3 days after the release of FreeBSD version 301.10.1, scheduled for August 3rd, 2065. :-) In other words, I doubt that we'll see this happen in our lifetimes. I think it does just fine as a port, yes? Why change it? Jordan From owner-freebsd-current Mon Jan 29 17:34:25 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id RAA04108 for current-outgoing; Mon, 29 Jan 1996 17:34:25 -0800 (PST) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id RAA04057 for ; Mon, 29 Jan 1996 17:34:16 -0800 (PST) Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.9/8.6.9) id MAA11362; Tue, 30 Jan 1996 12:30:01 +1100 Date: Tue, 30 Jan 1996 12:30:01 +1100 From: Bruce Evans Message-Id: <199601300130.MAA11362@godzilla.zeta.org.au> To: jkh@time.cdrom.com, joerg_wunsch@uriah.heep.sax.de Subject: Re: Please test this on your system (and see if you crash) Cc: current@FreeBSD.ORG Sender: owner-current@FreeBSD.ORG Precedence: bulk >Anybody more recent? :-) >> It works for me. System built around end of December. Works for me. System built yesterday :-). This doesn't prove much since the bug might depend on the number of groups... Bruce From owner-freebsd-current Mon Jan 29 17:53:32 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id RAA06049 for current-outgoing; Mon, 29 Jan 1996 17:53:32 -0800 (PST) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id RAA06027 for ; Mon, 29 Jan 1996 17:53:23 -0800 (PST) Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.9/8.6.9) id MAA12255; Tue, 30 Jan 1996 12:49:20 +1100 Date: Tue, 30 Jan 1996 12:49:20 +1100 From: Bruce Evans Message-Id: <199601300149.MAA12255@godzilla.zeta.org.au> To: current@FreeBSD.ORG, jkh@time.cdrom.com Subject: Re: I'm rather annoyed with -current. Sender: owner-current@FreeBSD.ORG Precedence: bulk >Not only has the thread_init race problem still NOT been fixed (try a >make world in -current using a 2.1-RELEASE system as the base - it >will fall over!) but today we have this new problem: >===> lib/librpcsvc >cc -O -pipe -I/usr/include/rpcsvc -c klm_prot_xdr.c -o klm_prot_xdr.o >In file included from klm_prot_xdr.c:6: >/usr/include/rpcsvc/klm_prot.h:10: parse error before `xdr_klm_stats' >/usr/include/rpcsvc/klm_prot.h:10: warning: data definition has no type or storage class >/usr/include/rpcsvc/klm_prot.h:15: parse error before `netobj' >/usr/include/rpcsvc/klm_prot.h:15: warning: no semicolon at end of struct or union >I'm not even particularly sure how to fix this one, either. The I think it's just the old Makefile ordering problem. Your line numbers don't match the ones in a working klm_prot.h. >header file that's generated here certainly doesn't include the >required header files itself, and blowing away /usr/include/rpcsvc >and trying to repopulate it from scratch didn't help. Build and install the new rpcgen first. >I haven't been able to build -stable for several weeks now - is it >just me, managing to try it on every single day that the tree is >broken? I'm about to give up on the whole idea of a 2.2-SNAP, to be >honest! :-( -current rebuilds itself OK on most days. Only bootstrapping is broken. Bruce From owner-freebsd-current Mon Jan 29 18:18:29 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id SAA07903 for current-outgoing; Mon, 29 Jan 1996 18:18:29 -0800 (PST) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id SAA07888 for ; Mon, 29 Jan 1996 18:18:17 -0800 (PST) Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.9/8.6.9) id NAA13193; Tue, 30 Jan 1996 13:12:56 +1100 Date: Tue, 30 Jan 1996 13:12:56 +1100 From: Bruce Evans Message-Id: <199601300212.NAA13193@godzilla.zeta.org.au> To: current@FreeBSD.ORG, graichen@omega.physik.fu-berlin.de Subject: Re: (fwd) too many cached pages for profiled kernel Sender: owner-current@FreeBSD.ORG Precedence: bulk >... >`68Kout' in the top output should be formatted better. >... >Swap: 33M Total, 6736K Used, 27M Free, 20% Inuse 68Kout >... >how about "K Out" and "K In" - that's what i use You have commit privileges :-). I'd also prefer the numbers to be in consistent units (K). Bruce From owner-freebsd-current Mon Jan 29 19:18:59 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id TAA14182 for current-outgoing; Mon, 29 Jan 1996 19:18:59 -0800 (PST) Received: from werple.net.au (werple.mira.net.au [203.9.190.18]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id TAA14172 for ; Mon, 29 Jan 1996 19:18:47 -0800 (PST) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by werple.net.au (8.7/8.7.1) with SMTP id OAA21069; Tue, 30 Jan 1996 14:18:02 +1100 (EST) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id UAA05479; Mon, 29 Jan 1996 20:15:47 -0700 From: Terry Lambert Message-Id: <199601300315.UAA05479@phaeton.artisoft.com> Subject: Re: I'm rather annoyed with -current. To: cimaxp1!jb@werple.net.au (John Birrell) Date: Mon, 29 Jan 1996 20:15:47 -0700 (MST) Cc: sri.MT.net!nate@werple.net.au, time.cdrom.com!jkh@werple.net.au, FreeBSD.ORG!current@werple.net.au In-Reply-To: <199601292252.JAA06436@werple.net.au> from "John Birrell" at Jan 30, 96 09:51:31 am X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.ORG Precedence: bulk > I agree with this. The changes are not bugs in the -current code committed. > Instead they show up a bogus build process. [ ... ] > It is not simply a matter of using -nostdinc, -nostdlib and -nostartfiles > although these are still needed. There are too many race conditions > in the software design. Look at the build process and you will see that > it only works at all because it tries to install *all* header files up > front regardless of what their dependencies are. Normally this is OK, > but in the rpcgen case it is not (though no fault of the rpcgen code). The header files should be used from the uninstalled locations in the source tree instead of the installed locations. The use of the RPC headers needs to depend on the generated header files in an "obj" directory that is also not installed. The problem here is defining global rules causing the creation of missing files (ie: .h targets as opposed to sources). I think there is a need for an incremental build. For instance, I want to rebuild and install the world from sources on a read-only/remote/CDROM volume, but I don't have enough space for a full obj tree. These are competing goals, but it doesn't mean that compromise isn't possible. Specifically, the build environment needs to be seperated from the target environment, and thee needs to be at least two target environments (1 == kernel, 2 == ...). I would be happy to be able to delete one .obj file and have only the necessary things rebuilt (lib if it's used in a library, everything that uses the lib if it's static, etc., etc.). > [Stands up on soap box to begin preaching... I've been flamed by NetBSD > folk for saying what I'm about to, but I'll say it anyway. 8-)] You're elected. }B-). Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-current Mon Jan 29 19:58:54 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id TAA17365 for current-outgoing; Mon, 29 Jan 1996 19:58:54 -0800 (PST) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id TAA17333 for ; Mon, 29 Jan 1996 19:58:39 -0800 (PST) Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.9/8.6.9) id OAA17636; Tue, 30 Jan 1996 14:44:50 +1100 Date: Tue, 30 Jan 1996 14:44:50 +1100 From: Bruce Evans Message-Id: <199601300344.OAA17636@godzilla.zeta.org.au> To: current@FreeBSD.ORG, james@miller.cs.uwm.edu Subject: Re: Recent sound changes Sender: owner-current@FreeBSD.ORG Precedence: bulk >I did a sup this morning to pick up the new malloc/vm changes and >something is amuck in the sound driver. I keep getting: > isa_dmastart: channel 3 busy >Any idea why? The ISA DMA code now keeps track of busy channels and my attempt to register the completion of sound DMAs didn't work. isa_dmadone() or isa_dmadone_nobounce() must be called when DMA is complete. Bruce From owner-freebsd-current Mon Jan 29 20:13:33 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id UAA18971 for current-outgoing; Mon, 29 Jan 1996 20:13:33 -0800 (PST) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id UAA18948 Mon, 29 Jan 1996 20:13:14 -0800 (PST) Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.9/8.6.9) id PAA18640; Tue, 30 Jan 1996 15:08:25 +1100 Date: Tue, 30 Jan 1996 15:08:25 +1100 From: Bruce Evans Message-Id: <199601300408.PAA18640@godzilla.zeta.org.au> To: bde@zeta.org.au, terry@lambert.org Subject: Re: Optimization topics Cc: current@freefall.freebsd.org, dyson@freefall.freebsd.org Sender: owner-current@FreeBSD.ORG Precedence: bulk >Specifically, it should be possible to run FreeBSD with the unaligned >access bit set to disallow unaligned access of word/dword/qword objects. I implemented this in Minix about 5 years ago. My compiler generates many misaligned access (it forgets to align switch tables) and gcc generates a few (e.g., it generates pessimized inline code for assigning poorly (but correctly!) aligned structs: --- struct foo { char x[4096]; }; struct bar { char pad; struct foo slow; }; void misaligned_copy(struct bar *p, struct bar *q) { p->slow = q->slow; } --- so my alignment trap handler silently clears the alignment check in the flags and returns (printing a warning was too annoying and not printing a warning wasn't annoying enough for me to fix the compilers :-). >At the very least, the kernel code should be clean of this cruft. It isn't easy to check for alignment in the kernel because the alignment trap doesn't apply in ring 0. >In Windows95, some programmers apparently believe that adding 3 bytes >to the end of a packed structure containing a byte followed by 20 >longs means "align to a longword boundry" -- at least that's what >the comments in the DDK header files say. >Clearly, these people never ran their own code in a kernel debugger, >or they simply failed to see the significance of unaligned access. Well, alignment to 32-bit boundaries is standard for the i386 (Unix) version of gcc. The longs would be automatically aligned and the 3 bytes at the end would waste 4 bytes of space. There is a problem for alignment of doubles. They should be aligned on 64 boundaries but ABIs specify only 32-bit boundaries >Many of the problems derive from unaligned stacks being passed down >to otherwise "correct" code. Fie. This isn't a problem for FreeBSD (except when the temporary kernel stack was misaligned in an old version :-). Bruce From owner-freebsd-current Mon Jan 29 21:42:01 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id VAA27324 for current-outgoing; Mon, 29 Jan 1996 21:42:01 -0800 (PST) Received: from zibbi.mikom.csir.co.za (zibbi.mikom.csir.co.za [146.64.24.58]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id VAA27305 for ; Mon, 29 Jan 1996 21:41:45 -0800 (PST) Received: (from jhay@localhost) by zibbi.mikom.csir.co.za (8.6.12/8.6.9) id HAA12613; Tue, 30 Jan 1996 07:41:25 +0200 From: John Hay Message-Id: <199601300541.HAA12613@zibbi.mikom.csir.co.za> Subject: Re: cvs commit: src Makefile To: nate@freefall.freebsd.org (Nate Williams) Date: Tue, 30 Jan 1996 07:41:25 +0200 (SAT) Cc: freebsd-current@FreeBSD.ORG (FreeBSD-current) In-Reply-To: <199601300522.VAA25369@freefall.freebsd.org> from "Nate Williams" at Jan 29, 96 09:22:15 pm X-Mailer: ELM [version 2.4 PL24 ME8b] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.ORG Precedence: bulk > > > nate 96/01/29 21:22:12 > > Modified: . Makefile > Log: > Kludge alert! > > Add new 'include-tools' target, which the 'includes' target depends on. > Currently, it consists of rpcgen. > > Revision Changes Path > 1.73 +10 -4 src/Makefile > I think install should also be there. It has a new option "-C" which is used when installing the include files. John -- John Hay -- John.Hay@csir.co.za From owner-freebsd-current Mon Jan 29 21:50:13 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id VAA28272 for current-outgoing; Mon, 29 Jan 1996 21:50:13 -0800 (PST) Received: from rocky.sri.MT.net (rocky.sri.MT.net [204.182.243.10]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id VAA28207 for ; Mon, 29 Jan 1996 21:49:55 -0800 (PST) Received: (from nate@localhost) by rocky.sri.MT.net (8.6.12/8.6.12) id WAA11011; Mon, 29 Jan 1996 22:51:37 -0700 Date: Mon, 29 Jan 1996 22:51:37 -0700 From: Nate Williams Message-Id: <199601300551.WAA11011@rocky.sri.MT.net> To: John Hay Cc: nate@freefall.freebsd.org (Nate Williams), freebsd-current@FreeBSD.ORG (FreeBSD-current) Subject: Re: cvs commit: src Makefile In-Reply-To: <199601300541.HAA12613@zibbi.mikom.csir.co.za> References: <199601300522.VAA25369@freefall.freebsd.org> <199601300541.HAA12613@zibbi.mikom.csir.co.za> Sender: owner-current@FreeBSD.ORG Precedence: bulk > > Modified: . Makefile > > Log: > > Kludge alert! > > I think install should also be there. It has a new option "-C" which is used > when installing the include files. Thanks, I've added install to my kludge. :) Nate From owner-freebsd-current Mon Jan 29 23:13:51 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id XAA08147 for current-outgoing; Mon, 29 Jan 1996 23:13:51 -0800 (PST) Received: from werple.net.au (werple.mira.net.au [203.9.190.18]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id XAA08125 for ; Mon, 29 Jan 1996 23:13:39 -0800 (PST) Received: from cimaxp1.UUCP (Ucimlogi@localhost) by werple.net.au (8.7/8.7.1) with UUCP id RAA01049 for mira!FreeBSD.ORG!current; Tue, 30 Jan 1996 17:36:52 +1100 (EST) Message-Id: <199601300636.RAA01049@werple.net.au> X-Authentication-Warning: werple.net.au: Ucimlogi set sender to cimaxp1!jb using -f Received: by cimaxp1.cimlogic.com.au; (5.65/1.1.8.2/10Sep95-0953AM) id AA16054; Tue, 30 Jan 1996 17:34:16 +1100 From: John Birrell Subject: Re: I'm rather annoyed with -current. To: lambert.org!terry@werple.net.au (Terry Lambert) Date: Tue, 30 Jan 1996 17:34:15 +1100 (EST) Cc: lambert.org!cimaxp1!jb@werple.net.au, sri.MT.net!nate@werple.net.au, time.cdrom.com!jkh@werple.net.au, FreeBSD.ORG!current@werple.net.au In-Reply-To: <199601300315.UAA05479@phaeton.artisoft.com> from "Terry Lambert" at Jan 29, 96 08:15:47 pm X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-current@FreeBSD.ORG Precedence: bulk > > [Stands up on soap box to begin preaching... I've been flamed by NetBSD > > folk for saying what I'm about to, but I'll say it anyway. 8-)] > > You're elected. }B-). Gad. For what? > > > Terry Lambert > terry@lambert.org > --- > Any opinions in this posting are my own and not those of my present > or previous employers. > -- John Birrell CIMlogic Pty Ltd jb@cimlogic.com.au 119 Cecil Street Ph +61 3 9690 6900 South Melbourne Vic 3205 Fax +61 3 9690 6650 Australia Mob +61 18 353 137 From owner-freebsd-current Mon Jan 29 23:28:38 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id XAA09792 for current-outgoing; Mon, 29 Jan 1996 23:28:38 -0800 (PST) Received: from ref.tfs.com (ref.tfs.com [140.145.254.251]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id XAA09784 for ; Mon, 29 Jan 1996 23:28:32 -0800 (PST) Received: (from julian@localhost) by ref.tfs.com (8.6.12/8.6.9) id XAA07720 for current@freebsd.org; Mon, 29 Jan 1996 23:27:50 -0800 From: Julian Elischer Message-Id: <199601300727.XAA07720@ref.tfs.com> Subject: Announcing fer.tfs.com To: current@freebsd.org Date: Mon, 29 Jan 1996 23:27:49 -0800 (PST) X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-current@freebsd.org Precedence: bulk Fer.tfs.com is an almost exact copy of ref.tfs.com. differences.. 1/ as soon as I've finished, it will run 2.2-current and not 2.1 2/ it will contain a separate 2.2-based chroot partition, in which there will be a cvs and source tree for experimentation. 3/It will hopefully act as a sup server for a fully built 2.2-current tree.. i.e. sup it to upgrade to 2.2 :) accounts will be available on fer for people who need to test 2.2 based tools etc. such 'guest' accounts will automatically chroot to the 2.2 sandbox fer will come on-line in the next day or two.. it is there but is still 2.1 based. From owner-freebsd-current Tue Jan 30 00:10:00 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id AAA14229 for current-outgoing; Tue, 30 Jan 1996 00:10:00 -0800 (PST) Received: from grumble.grondar.za (root@grumble.grondar.za [196.7.18.130]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id AAA14218 for ; Tue, 30 Jan 1996 00:09:51 -0800 (PST) Received: from localhost (mark@localhost [127.0.0.1]) by grumble.grondar.za (8.7.3/8.7.3) with SMTP id KAA23819; Tue, 30 Jan 1996 10:09:18 +0200 (SAT) Message-Id: <199601300809.KAA23819@grumble.grondar.za> X-Authentication-Warning: grumble.grondar.za: Host mark@localhost [127.0.0.1] didn't use HELO protocol To: Nate Williams cc: freebsd-current@FreeBSD.org (FreeBSD-current) Subject: Re: cvs commit: src Makefile Date: Tue, 30 Jan 1996 10:09:18 +0200 From: Mark Murray Sender: owner-current@FreeBSD.org Precedence: bulk Nate Williams wrote: > > > Modified: . Makefile > > > Log: > > > Kludge alert! > > > > I think install should also be there. It has a new option "-C" which is use d > > when installing the include files. > > Thanks, I've added install to my kludge. :) Shouldn't rpcgen also be there? It does quite a bit in include/rpc and/or include/rpcsvc. M -- Mark Murray 46 Harvey Rd, Claremont, Cape Town 7700, South Africa +27 21 61-3768 GMT+0200 Finger mark@grondar.za for PGP key From owner-freebsd-current Tue Jan 30 00:43:35 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id AAA17015 for current-outgoing; Tue, 30 Jan 1996 00:43:35 -0800 (PST) Received: from omega.physik.fu-berlin.de (omega.physik.fu-berlin.de [130.133.3.51]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id AAA16790 for ; Tue, 30 Jan 1996 00:40:19 -0800 (PST) Received: from julia.physik.fu-berlin.de (julia.physik.fu-berlin.de [130.133.3.235]) by omega.physik.fu-berlin.de (8.7.1/8.7.1) with ESMTP id JAA14962; Tue, 30 Jan 1996 09:38:49 +0100 (MET) Received: (from graichen@localhost) by julia.physik.fu-berlin.de (8.6.12/8.6.12) id JAA16517; Tue, 30 Jan 1996 09:38:49 +0100 From: Thomas Graichen Message-Id: <199601300838.JAA16517@julia.physik.fu-berlin.de> Subject: Re: (fwd) too many cached pages for profiled kernel To: bde@zeta.org.au (Bruce Evans) Date: Tue, 30 Jan 1996 09:38:47 +0100 (MET) Cc: current@FreeBSD.ORG, graichen@omega.physik.fu-berlin.de In-Reply-To: <199601300212.NAA13193@godzilla.zeta.org.au> from "Bruce Evans" at Jan 30, 96 01:12:56 pm X-Mailer: ELM [version 2.4 PL23] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.ORG Precedence: bulk hasn't Bruce Evans said ? ... > > >... > >`68Kout' in the top output should be formatted better. > >... > >Swap: 33M Total, 6736K Used, 27M Free, 20% Inuse 68Kout > >... > > >how about "K Out" and "K In" - that's what i use > > You have commit privileges :-). > ok - i may change it within the next days if nobody disagrees > I'd also prefer the numbers to be in consistent units (K). > i think they are - but they swich to M if the amount is >= 10M to get only a limited number of digits i think t _______________________________________________________||___________________ __|| Perfection is reached, not when there is no __|| thomas graichen longer anything to add, but when there __|| freie universitaet berlin is no longer anything to take away __|| fachbereich physik __|| - Antoine de Saint-Exupery - __|| graichen@mail.physik.fu-berlin.de ___________________________||__________________graichen@FreeBSD.org_________ From owner-freebsd-current Tue Jan 30 01:34:45 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id BAA22946 for current-outgoing; Tue, 30 Jan 1996 01:34:45 -0800 (PST) Received: from sequent.kiae.su (sequent.kiae.su [144.206.136.6]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id BAA22830 for ; Tue, 30 Jan 1996 01:34:00 -0800 (PST) Received: by sequent.kiae.su id AA24167 (5.65.kiae-2 ); Tue, 30 Jan 1996 12:26:03 +0300 Received: by sequent.KIAE.su (UUMAIL/2.0); Tue, 30 Jan 96 12:26:03 +0300 Received: (from ache@localhost) by ache.dialup.ru (8.7.3/8.7.3) id MAA25217; Tue, 30 Jan 1996 12:21:06 +0300 (MSK) To: Bruce Evans , current@FreeBSD.org, james@miller.cs.uwm.edu References: <199601300344.OAA17636@godzilla.zeta.org.au> In-Reply-To: <199601300344.OAA17636@godzilla.zeta.org.au>; from Bruce Evans at Tue, 30 Jan 1996 14:44:50 +1100 Message-Id: Organization: Olahm Ha-Yetzirah Date: Tue, 30 Jan 1996 12:21:05 +0300 (MSK) X-Mailer: Mail/@ [v2.42 FreeBSD] From: =?KOI8-R?Q?=E1=CE=C4=D2=C5=CA_=FE=C5=D2=CE=CF=D7?= (aka Andrey A. Chernov, Black Mage) X-Class: Fast Subject: Re: Recent sound changes Lines: 23 Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.org Precedence: bulk In message <199601300344.OAA17636@godzilla.zeta.org.au> Bruce Evans writes: >>I did a sup this morning to pick up the new malloc/vm changes and >>something is amuck in the sound driver. I keep getting: >> isa_dmastart: channel 3 busy >>Any idea why? >The ISA DMA code now keeps track of busy channels and my attempt to >register the completion of sound DMAs didn't work. isa_dmadone() or >isa_dmadone_nobounce() must be called when DMA is complete. I don't shure, but probably isa_dmadone() must be called on each soundcard interrupt. -- Andrey A. Chernov : And I rest so composedly, /Now, in my bed, ache@astral.msk.su : That any beholder /Might fancy me dead - http://dt.demos.su/~ache : Might start at beholding me, /Thinking me dead. RELCOM Team,FreeBSD Team : E.A.Poe From "For Annie" 1849 From owner-freebsd-current Tue Jan 30 02:04:07 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id CAA26445 for current-outgoing; Tue, 30 Jan 1996 02:04:07 -0800 (PST) Received: from who.cdrom.com (who.cdrom.com [192.216.222.3]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id CAA26423 for ; Tue, 30 Jan 1996 02:03:58 -0800 (PST) Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by who.cdrom.com (8.6.12/8.6.11) with ESMTP id CAA22370 for ; Tue, 30 Jan 1996 02:02:46 -0800 Received: from sax.sax.de by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id KAA13986 for ; Tue, 30 Jan 1996 10:21:56 +0100 Received: by sax.sax.de (8.6.11/8.6.12-s1) with UUCP id KAA00930 for freebsd-current@FreeBSD.org; Tue, 30 Jan 1996 10:21:56 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.7.3/8.6.9) id BAA10336 for freebsd-current@FreeBSD.org; Tue, 30 Jan 1996 01:58:32 +0100 (MET) From: J Wunsch Message-Id: <199601300058.BAA10336@uriah.heep.sax.de> Subject: Re: any ideas about this crash? To: freebsd-current@FreeBSD.org (FreeBSD-current users) Date: Tue, 30 Jan 1996 01:58:32 +0100 (MET) Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <9601291730.AA05796@halloran-eldar.lcs.mit.edu> from "Garrett A. Wollman" at Jan 29, 96 12:30:57 pm X-Phone: +49-351-2012 669 X-Mailer: ELM [version 2.4 PL23] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-current@FreeBSD.org Precedence: bulk As Garrett A. Wollman wrote: > > > CPU: Pentium (76.42-MHz 586-class CPU) > > ^^^^^^^^^ > > > Mine is 90MHz. > > Your timer/counter is bogus. Complain to the vendor. My machine at work claims 99.95 MHz since i've upgraded it to -current today. It displayed 100 MHz with 2.0.5. I still believe abusing this timer to generate the system clock is not the way to go. You cannot sue anybody for the CPU-internal timer not being accurate within 1E-5 or so (and that's what is needed for a freestanding clock). -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-current Tue Jan 30 03:33:44 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id DAA08027 for current-outgoing; Tue, 30 Jan 1996 03:33:44 -0800 (PST) Received: from iworks.InterWorks.org (iworks.interworks.org [128.255.18.10]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id DAA08008 for ; Tue, 30 Jan 1996 03:33:37 -0800 (PST) Received: by iworks.InterWorks.org (1.37.109.8/16.2) id AA11076; Tue, 30 Jan 1996 05:31:33 -0600 Message-Id: <9601301131.AA11076@iworks.InterWorks.org> Date: Tue, 30 Jan 1996 05:31:33 -0600 From: "Daniel M. Eischen" To: current@freebsd.org, joerg_wunsch@uriah.heep.sax.de Subject: Re: any ideas about this crash? Sender: owner-current@freebsd.org Precedence: bulk >As Garrett A. Wollman wrote: >> >> > CPU: Pentium (76.42-MHz 586-class CPU) >> > ^^^^^^^^^ >> >> > Mine is 90MHz. >> >> Your timer/counter is bogus. Complain to the vendor. > >My machine at work claims 99.95 MHz since i've upgraded it to -current >today. It displayed 100 MHz with 2.0.5. > >I still believe abusing this timer to generate the system clock is not >the way to go. You cannot sue anybody for the CPU-internal timer not >being accurate within 1E-5 or so (and that's what is needed for a >freestanding clock). It seems that this is true with my timer. Other than the time I reported above, during the month of January I've seen times usually around 90MHz reported, but also other times: 58-MHz 78-MHz 85-MHz 84-MHz 87-MHz 86-MHz 89-MHz and 90.19-MHz [I should have said rates] The last boot was 90.19 MHz. Dan Eischen deischen@iworks.InterWorks.org From owner-freebsd-current Tue Jan 30 03:41:14 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id DAA08892 for current-outgoing; Tue, 30 Jan 1996 03:41:14 -0800 (PST) Received: from Root.COM (implode.Root.COM [198.145.90.17]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id DAA08874 for ; Tue, 30 Jan 1996 03:41:07 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by Root.COM (8.6.12/8.6.5) with SMTP id DAA00416; Tue, 30 Jan 1996 03:37:57 -0800 Message-Id: <199601301137.DAA00416@Root.COM> X-Authentication-Warning: implode.Root.COM: Host localhost didn't use HELO protocol To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) cc: freebsd-current@FreeBSD.org (FreeBSD-current users) Subject: Re: any ideas about this crash? In-reply-to: Your message of "Tue, 30 Jan 1996 01:58:32 +0100." <199601300058.BAA10336@uriah.heep.sax.de> From: David Greenman Reply-To: davidg@Root.COM Date: Tue, 30 Jan 1996 03:37:57 -0800 Sender: owner-current@FreeBSD.org Precedence: bulk >As Garrett A. Wollman wrote: >> >> > CPU: Pentium (76.42-MHz 586-class CPU) >> > ^^^^^^^^^ >> >> > Mine is 90MHz. >> >> Your timer/counter is bogus. Complain to the vendor. > >My machine at work claims 99.95 MHz since i've upgraded it to -current >today. It displayed 100 MHz with 2.0.5. > >I still believe abusing this timer to generate the system clock is not >the way to go. You cannot sue anybody for the CPU-internal timer not >being accurate within 1E-5 or so (and that's what is needed for a >freestanding clock). Worse than that, it is fundamentally broken on machines that have variable clocks (read: laptops and "green" PCs). The folks in Intel's P6 architecture group were shocked when they heard about what we were doing with the internal cycle counter..."It was never intended to be used that way!". At the very least, we should make it a compile-time option (defaulting to off!). -DG David Greenman Core Team/Principal Architect, The FreeBSD Project From owner-freebsd-current Tue Jan 30 04:12:20 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id EAA12773 for current-outgoing; Tue, 30 Jan 1996 04:12:20 -0800 (PST) Received: from tfs.com (tfs.com [140.145.250.1]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id EAA12719 for ; Tue, 30 Jan 1996 04:12:13 -0800 (PST) Received: from critter.tfs.com by tfs.com (smail3.1.28.1) with SMTP id m0thEuu-0003xTC; Tue, 30 Jan 96 04:12 PST Received: from localhost.tfs.com (localhost.tfs.com [127.0.0.1]) by critter.tfs.com (8.6.12/8.6.12) with SMTP id NAA02642; Tue, 30 Jan 1996 13:12:02 +0100 X-Authentication-Warning: critter.tfs.com: Host localhost.tfs.com didn't use HELO protocol To: "Daniel M. Eischen" cc: current@freebsd.org, joerg_wunsch@uriah.heep.sax.de Subject: Re: any ideas about this crash? In-reply-to: Your message of "Tue, 30 Jan 1996 05:31:33 CST." <9601301131.AA11076@iworks.InterWorks.org> Date: Tue, 30 Jan 1996 13:12:00 +0100 Message-ID: <2640.823003920@critter.tfs.com> From: Poul-Henning Kamp Sender: owner-current@freebsd.org Precedence: bulk > It seems that this is true with my timer. Other than the time I reported > above, during the month of January I've seen times usually around 90MHz > reported, but also other times: > > 58-MHz 78-MHz 85-MHz 84-MHz 87-MHz 86-MHz 89-MHz and 90.19-MHz > > [I should have said rates] Is any kind of Power Management/Power Save features enabled in your bios ? -- Poul-Henning Kamp | phk@FreeBSD.ORG FreeBSD Core-team. http://www.freebsd.org/~phk | phk@login.dknet.dk Private mailbox. whois: [PHK] | phk@ref.tfs.com TRW Financial Systems, Inc. Future will arrive by its own means, progress not so. From owner-freebsd-current Tue Jan 30 05:29:08 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id FAA19184 for current-outgoing; Tue, 30 Jan 1996 05:29:08 -0800 (PST) Received: from sequent.kiae.su (sequent.kiae.su [144.206.136.6]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id FAA19169 for ; Tue, 30 Jan 1996 05:28:39 -0800 (PST) Received: by sequent.kiae.su id AA08320 (5.65.kiae-2 for current@freebsd.org); Tue, 30 Jan 1996 16:26:48 +0300 Received: by sequent.KIAE.su (UUMAIL/2.0); Tue, 30 Jan 96 16:26:45 +0300 Received: (from ache@localhost) by ache.dialup.ru (8.7.3/8.7.3) id QAA26163 for current@freebsd.org; Tue, 30 Jan 1996 16:26:21 +0300 (MSK) To: current@freebsd.org Message-Id: Organization: Olahm Ha-Yetzirah Date: Tue, 30 Jan 1996 16:26:20 +0300 (MSK) X-Mailer: Mail/@ [v2.42 FreeBSD] From: =?KOI8-R?Q?=E1=CE=C4=D2=C5=CA_=FE=C5=D2=CE=CF=D7?= (aka Andrey A. Chernov, Black Mage) X-Class: Fast Subject: ATTENTION to CD driver authors (matcd, scd) Lines: 10 Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org Precedence: bulk I found that READTOCENTRYS ioctl completely broken in matcd/scd. I don't have enough time to fix them and not have those cards to test the fix. So, please fix them. As template you can look at mcd,wcd,cd drivers, here is correct implementation after my latest commit sequence. -- Andrey A. Chernov : And I rest so composedly, /Now, in my bed, ache@astral.msk.su : That any beholder /Might fancy me dead - http://dt.demos.su/~ache : Might start at beholding me, /Thinking me dead. RELCOM Team,FreeBSD Team : E.A.Poe From "For Annie" 1849 From owner-freebsd-current Tue Jan 30 05:47:40 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id FAA21196 for current-outgoing; Tue, 30 Jan 1996 05:47:40 -0800 (PST) Received: from eel.dataplex.net (EEL.DATAPLEX.NET [199.183.109.245]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id FAA21189 for ; Tue, 30 Jan 1996 05:47:27 -0800 (PST) Received: from [199.183.109.242] (cod [199.183.109.242]) by eel.dataplex.net (8.6.11/8.6.9) with SMTP id HAA06033; Tue, 30 Jan 1996 07:47:17 -0600 X-Sender: rkw@shark.dataplex.net Message-Id: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Tue, 30 Jan 1996 07:47:20 -0600 To: Terry Lambert From: Richard Wackerbarth Subject: Building a better world Cc: current@freebsd.org Sender: owner-current@freebsd.org Precedence: bulk >The header files should be used from the uninstalled locations in the >source tree instead of the installed locations. > >The use of the RPC headers needs to depend on the generated header files >in an "obj" directory that is also not installed. The problem here is >defining global rules causing the creation of missing files (ie: .h >targets as opposed to sources). Cannot we treat ALL the source files as coming from the obj tree? The rule to create a normal header or source is to generate a symbolic link from the reference source tree (IOW "install" the source file in the active (not the system's) tree). The rule to generate rpc headers uses rpcgen to create them, etc. >I think there is a need for an incremental build. For instance, I want >to rebuild and install the world from sources on a read-only/remote/CDROM >volume, but I don't have enough space for a full obj tree. I see no problem splitting the "world" into "continents".(kernel, libraries, core, compilers, games, etc.) Could we not "prebuild" the objects as links to the CDROM? ---- Richard Wackerbarth rkw@dataplex.net From owner-freebsd-current Tue Jan 30 06:38:35 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id GAA25859 for current-outgoing; Tue, 30 Jan 1996 06:38:35 -0800 (PST) Received: from iworks.InterWorks.org (iworks.interworks.org [128.255.18.10]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id GAA25854 for ; Tue, 30 Jan 1996 06:38:29 -0800 (PST) Received: by iworks.InterWorks.org (1.37.109.8/16.2) id AA11539; Tue, 30 Jan 1996 08:36:24 -0600 Message-Id: <9601301436.AA11539@iworks.InterWorks.org> Date: Tue, 30 Jan 1996 08:36:24 -0600 From: "Daniel M. Eischen" To: phk@critter.tfs.com Subject: Re: any ideas about this crash? Cc: current@freebsd.org, joerg_wunsch@uriah.heep.sax.de Sender: owner-current@freebsd.org Precedence: bulk > > It seems that this is true with my timer. Other than the time I reported > > above, during the month of January I've seen times usually around 90MHz > > reported, but also other times: > > > > 58-MHz 78-MHz 85-MHz 84-MHz 87-MHz 86-MHz 89-MHz and 90.19-MHz > > > > [I should have said rates] > > Is any kind of Power Management/Power Save features enabled in your bios ? No. FYI, it's an Intel Premier II with AMI BIOS 1.00.08. After the reboot to check the BIOS, I observed a rate of 55 MHz. I then rebooted again and got 76 MHz. My third reboot got it back to 90 MHz. Dan Eischen deischen@iworks.InterWorks.org From owner-freebsd-current Tue Jan 30 08:42:05 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id IAA05253 for current-outgoing; Tue, 30 Jan 1996 08:42:05 -0800 (PST) Received: from fw.ast.com (fw.ast.com [165.164.6.25]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id IAA05237 for ; Tue, 30 Jan 1996 08:41:57 -0800 (PST) Received: from nemesis by fw.ast.com with uucp (Smail3.1.29.1 #2) id m0thIqD-00085AC; Tue, 30 Jan 96 10:23 CST Received: by nemesis.lonestar.org (Smail3.1.27.1 #20) id m0thIlW-000CvTC; Tue, 30 Jan 96 10:18 WET Message-Id: Date: Tue, 30 Jan 96 10:18 WET To: freebsd-current@freebsd.org From: uhclem@nemesis.lonestar.org (Frank Durda IV) Sent: Tue Jan 30 1996, 10:18:41 CST Subject: Re: any ideas about this crash? Sender: owner-current@freebsd.org Precedence: bulk [5] Worse than that, it is fundamentally broken on machines that have [5]variable clocks (read: laptops and "green" PCs). The folks in Intel's [5]P6 architecture group were shocked when they heard about what we were [5]doing with the internal cycle counter..."It was never intended to be used [5]that way!". [5] At the very least, we should make it a compile-time option (defaulting [5]to off!). [5] -DG THANK YOU for saying that! I have been saying this for three months now and was ignored even though I was probably arguing the same points and looking at the same material out of Intels Oregon shop and from the chipset vendors that you were. This Pentium internal timer is USELESS as a TOD timepiece! Stop using it this way! It is only good for relative measurements within the processors realm. Why give the Linux guys something else to razz us about? Frank Durda IV |"The Knights who say "LETNi" or uhclem%nemesis@rwsystr.nkn.net | demand... A SEGMENT REGISTER!!!" ^------(this is the fastest route)|"A what?" or ...letni!rwsys!nemesis!uhclem |"LETNi! LETNi! LETNi!" - 1983 From owner-freebsd-current Tue Jan 30 08:52:15 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id IAA06382 for current-outgoing; Tue, 30 Jan 1996 08:52:15 -0800 (PST) Received: from halloran-eldar.lcs.mit.edu (halloran-eldar.lcs.mit.edu [18.26.0.159]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id IAA06322 for ; Tue, 30 Jan 1996 08:52:04 -0800 (PST) Received: by halloran-eldar.lcs.mit.edu; (5.65/1.1.8.2/19Aug95-0530PM) id AA15588; Tue, 30 Jan 1996 11:38:27 -0500 Date: Tue, 30 Jan 1996 11:38:27 -0500 From: "Garrett A. Wollman" Message-Id: <9601301638.AA15588@halloran-eldar.lcs.mit.edu> To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) Cc: freebsd-current@FreeBSD.org (FreeBSD-current users) Subject: Re: any ideas about this crash? In-Reply-To: <199601300058.BAA10336@uriah.heep.sax.de> References: <9601291730.AA05796@halloran-eldar.lcs.mit.edu> <199601300058.BAA10336@uriah.heep.sax.de> Sender: owner-current@FreeBSD.org Precedence: bulk < said: > My machine at work claims 99.95 MHz since i've upgraded it to -current > today. It displayed 100 MHz with 2.0.5. 2.0.5 automatically (:-() added a very large rounding factor to make sure that my 60-MHz machine would actually be diagnosed as 60 MHz. 2.2 does not. All the evidence I've seen points to problems with the ISA timer/counter chip (well, cell in the bridge chip) and the DELAY() function. If you have a 90-MHz CPU and the system diagnoses it at 100 MHz, then your timer/counter is running 11% too slow, or your CPU clock is running 11% too fast. -GAWollman -- Garrett A. Wollman | Shashish is simple, it's discreet, it's brief. ... wollman@lcs.mit.edu | Shashish is the bonding of hearts in spite of distance. Opinions not those of| It is a bond more powerful than absence. We like people MIT, LCS, ANA, or NSA| who like Shashish. - Claude McKenzie + Florent Vollant From owner-freebsd-current Tue Jan 30 09:07:13 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id JAA07746 for current-outgoing; Tue, 30 Jan 1996 09:07:13 -0800 (PST) Received: from news1.gtn.com (news1.gtn.com [192.109.159.3]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id JAA07726 for ; Tue, 30 Jan 1996 09:07:04 -0800 (PST) Received: (from uucp@localhost) by news1.gtn.com (8.7.2/8.7.2) id SAA09372; Tue, 30 Jan 1996 18:00:29 +0100 (MET) Received: from knobel.gun.de (localhost [127.0.0.1]) by knobel.gun.de (8.7.3/8.7.3) with SMTP id RAA00345; Tue, 30 Jan 1996 17:48:59 +0100 (MET) Date: Tue, 30 Jan 1996 17:48:59 +0100 (MET) From: Andreas Klemm To: Peter Wemm cc: current@freebsd.org Subject: Re: Linux Netscape 2.0b6a? In-Reply-To: <199601292324.HAA01647@jhome.DIALix.COM> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org Precedence: bulk On Tue, 30 Jan 1996, Peter Wemm wrote: > I know the BSDI version of 2.0b6a works fine for me, but it doesn't have > Java support in it. Does somebody know, why those people at mcom deceided not to include Java support into the BSDI binary ? Could it be the case that they have compilation trouble or such ? Perhaps they should go and get a FreeBSD system ;-) Andreas /// -- andreas@knobel.gun.de /\/\___ Wiechers & Partner Datentechnik GmbH Andreas Klemm ___/\/\/ - Support Unix - aklemm@wup.de - \/ ftp://sunsite.unc.edu/pub/Linux/system/Printing/aps-491.tgz apsfilter - magic print filter 4lpd >>> knobel is powered by FreeBSD <<< From owner-freebsd-current Tue Jan 30 09:27:49 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id JAA09197 for current-outgoing; Tue, 30 Jan 1996 09:27:49 -0800 (PST) Received: from jhome.DIALix.COM (root@jhome.DIALix.COM [192.203.228.69]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id JAA09192 for ; Tue, 30 Jan 1996 09:27:41 -0800 (PST) Received: from localhost.DIALix.oz.au (peter@localhost.DIALix.oz.au [127.0.0.1]) by jhome.DIALix.COM (8.7.3/8.7.3) with SMTP id BAA05108; Wed, 31 Jan 1996 01:27:23 +0800 (WST) Message-Id: <199601301727.BAA05108@jhome.DIALix.COM> X-Authentication-Warning: jhome.DIALix.COM: Host peter@localhost.DIALix.oz.au [127.0.0.1] didn't use HELO protocol To: Andreas Klemm cc: current@freebsd.org Subject: Re: Linux Netscape 2.0b6a? In-reply-to: Your message of "Tue, 30 Jan 1996 17:48:59 +0100." Date: Wed, 31 Jan 1996 01:27:23 +0800 From: Peter Wemm Sender: owner-current@freebsd.org Precedence: bulk >On Tue, 30 Jan 1996, Peter Wemm wrote: > >> I know the BSDI version of 2.0b6a works fine for me, but it doesn't have >> Java support in it. > >Does somebody know, why those people at mcom deceided not to include >Java support into the BSDI binary ? Beats me.. :-( They apparently said it was because we dont have a thread-safe libc, but that argument doesn't exactly hold water because the vintage of the Linux libc/libm that they are linking with does not appear to be thread-safe or reentrant either. As near as I can guess, either the re-entrant libc requirement is a smoke screen, or they are using wrappers around the linux libc stuff that they need. >Could it be the case that they have compilation trouble or such ? >Perhaps they should go and get a FreeBSD system ;-) > > Andreas /// If it were that simple.. :-) If they have a Linux fanatic in-house then he's probably brainwashed them into believing that we dont exist. The other thing I wonder about sometimes is the time that a Netscape employee slipped and said with a loose group like FreeBSD it was difficult to deal with. Reading in between the lines of that (and I've lost the posting), I wonder if people like BSDI have made a "strategic arrangement" to get a native version? Unfortunately, I dont think we're in a position to make Netscape an offer they can't refuse. :-( Cheers, -Peter From owner-freebsd-current Tue Jan 30 10:30:08 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id KAA14585 for current-outgoing; Tue, 30 Jan 1996 10:30:08 -0800 (PST) Received: from skiddaw.elsevier.co.uk (skiddaw.elsevier.co.uk [193.131.222.60]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id KAA14515 for ; Tue, 30 Jan 1996 10:29:24 -0800 (PST) Received: from snowdon.elsevier.co.uk (snowdon.elsevier.co.uk [193.131.197.164]) by skiddaw.elsevier.co.uk (8.6.12/8.6.12) with ESMTP id SAA19178 for ; Tue, 30 Jan 1996 18:27:10 GMT Received: from cadair.elsevier.co.uk (actually host cadair) by snowdon with SMTP (PP); Tue, 30 Jan 1996 18:27:14 +0000 Received: (from dpr@localhost) by cadair.elsevier.co.uk (8.6.12/8.6.12) id SAA19450; Tue, 30 Jan 1996 18:27:17 GMT From: Paul Richards Message-Id: <199601301827.SAA19450@cadair.elsevier.co.uk> Subject: Re: Linux Netscape 2.0b6a? To: andreas@knobel.gun.de (Andreas Klemm) Date: Tue, 30 Jan 1996 18:27:16 +0000 (GMT) Cc: peter@jhome.DIALix.COM, current@FreeBSD.org In-Reply-To: from "Andreas Klemm" at Jan 30, 96 05:48:59 pm X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-current@FreeBSD.org Precedence: bulk In reply to Andreas Klemm who said > > On Tue, 30 Jan 1996, Peter Wemm wrote: > > > I know the BSDI version of 2.0b6a works fine for me, but it doesn't have > > Java support in it. > > Does somebody know, why those people at mcom deceided not to include > Java support into the BSDI binary ? Most likely because no-one's ported Java to BSDI and that's probably for the same reason as FreeBSD, no multi-threading support. Looks like that may be changing though :-) -- Paul Richards. Originative Solutions Ltd. Internet: paul@netcraft.co.uk, http://www.netcraft.co.uk Phone: 0370 462071 (Mobile), +44 1225 447500 (work) From owner-freebsd-current Tue Jan 30 10:40:56 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id KAA15715 for current-outgoing; Tue, 30 Jan 1996 10:40:56 -0800 (PST) Received: from ormail.intel.com ([134.134.192.3]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id KAA15642 Tue, 30 Jan 1996 10:40:28 -0800 (PST) Received: from ichips.intel.com (ichips.intel.com [134.134.50.200]) by ormail.intel.com (8.6.12/8.6.12) with ESMTP id KAA18905; Tue, 30 Jan 1996 10:37:56 -0800 Received: from pdxlx008.intel.com.intel.com by ichips.intel.com (8.7.1/jIII); Tue, 30 Jan 1996 10:37:54 -0800 (PST) Received: from loopback.jf.intel.com by pdxlx008.intel.com.intel.com (8.6.12/10.0i); Tue, 30 Jan 1996 10:37:55 -0800 Message-Id: <199601301837.KAA07469@pdxlx008.intel.com.intel.com> To: Bruce Evans cc: terry@lambert.org, current@freefall.freebsd.org, dyson@freefall.freebsd.org Subject: Re: Optimization topics In-reply-to: Your message of "Tue, 30 Jan 1996 15:08:25 +1100." <199601300408.PAA18640@godzilla.zeta.org.au> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Date: Tue, 30 Jan 1996 10:37:55 -0800 From: Wayne Scott Sender: owner-current@FreeBSD.ORG Precedence: bulk > >Specifically, it should be possible to run FreeBSD with the unaligned > >access bit set to disallow unaligned access of word/dword/qword objects. > > I implemented this in Minix about 5 years ago. My compiler generates > many misaligned access (it forgets to align switch tables) and gcc > generates a few (e.g., it generates pessimized inline code for assigning > poorly (but correctly!) aligned structs: I might have an easier solution for you. The Pentium Pro has a misaligned access performance counter that has the ability to generate interrupts. You can tell the processor to count misaligns and generate an interrupt every 1000 times it sees one. Put this into you existing profiling code and you will get a profile of where the system is doing misaligned references. Now you only need to fix the very common cases in the critical paths. The same thing can be done which all the counters. Which branches are not predicted well, where am I missing the cache, etc... The information is in the P6 PRM that should be available next month... -Wayne Wayne Scott P6 Architecture wscott@ichips.intel.com Work #: (503) 264-4165 Disclaimer: All views expressed are my own opinions, and not necessarily those of Intel Corporation. From owner-freebsd-current Tue Jan 30 10:48:22 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id KAA16399 for current-outgoing; Tue, 30 Jan 1996 10:48:22 -0800 (PST) Received: from Root.COM (implode.Root.COM [198.145.90.17]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id KAA16392 for ; Tue, 30 Jan 1996 10:48:14 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by Root.COM (8.6.12/8.6.5) with SMTP id KAA01434; Tue, 30 Jan 1996 10:44:24 -0800 Message-Id: <199601301844.KAA01434@Root.COM> X-Authentication-Warning: implode.Root.COM: Host localhost didn't use HELO protocol To: uhclem@nemesis.lonestar.org (Frank Durda IV) cc: freebsd-current@freebsd.org Subject: Re: any ideas about this crash? In-reply-to: Your message of "Tue, 30 Jan 1996 10:18:00 +0700." From: David Greenman Reply-To: davidg@Root.COM Date: Tue, 30 Jan 1996 10:44:24 -0800 Sender: owner-current@freebsd.org Precedence: bulk >[5] Worse than that, it is fundamentally broken on machines that have >[5]variable clocks (read: laptops and "green" PCs). The folks in Intel's >[5]P6 architecture group were shocked when they heard about what we were >[5]doing with the internal cycle counter..."It was never intended to be used >[5]that way!". >[5] At the very least, we should make it a compile-time option (defaulting >[5]to off!). >[5] -DG > >THANK YOU for saying that! I have been saying this for three months now >and was ignored even though I was probably arguing the same points and >looking at the same material out of Intels Oregon shop and from the chipset >vendors that you were. It makes a big difference when the P6 architects tell you this personally. > This Pentium internal timer is USELESS as a >TOD timepiece! Stop using it this way! It is only good for relative >measurements within the processors realm. > >Why give the Linux guys something else to razz us about? "USELESS" might be a little strong - it does have the merit of being a very fast, "accurate", and easy way to do time measurements. Unfortunately, it also has apparantly shown us that DELAY() has a bug of some kind as *all* of the machines I've tested come up with an incorrect calibration about 10% of the time I boot. The result it comes up with is actually wrong, too, as the statistics that the system generates later are clearly wrong (off by the same amount as the mis-calibration). It acts like some sort of rounding or arithmetic error that occurs during the calibration. -DG David Greenman Core Team/Principal Architect, The FreeBSD Project From owner-freebsd-current Tue Jan 30 11:05:18 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id LAA18172 for current-outgoing; Tue, 30 Jan 1996 11:05:18 -0800 (PST) Received: from news1.gtn.com (news1.gtn.com [192.109.159.3]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id LAA18153 for ; Tue, 30 Jan 1996 11:05:06 -0800 (PST) Received: (from uucp@localhost) by news1.gtn.com (8.7.2/8.7.2) id TAA09470; Tue, 30 Jan 1996 19:45:16 +0100 (MET) Received: (from andreas@localhost) by knobel.gun.de (8.7.3/8.7.3) id TAA06418; Tue, 30 Jan 1996 19:39:58 +0100 (MET) From: Andreas Klemm Message-Id: <199601301839.TAA06418@knobel.gun.de> Subject: Re: Linux Netscape 2.0b6a? To: peter@jhome.DIALix.COM (Peter Wemm) Date: Tue, 30 Jan 1996 19:39:58 +0100 (MET) Cc: current@freebsd.org In-Reply-To: <199601301727.BAA05108@jhome.DIALix.COM> from "Peter Wemm" at Jan 31, 96 01:27:23 am X-Mailer: ELM [version 2.4 PL24 ME8b] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org Precedence: bulk > The other thing I wonder about sometimes is the time that a Netscape > employee slipped and said with a loose group like FreeBSD it was difficult > to deal with. *sigh* > Reading in between the lines of that (and I've lost the > posting), I wonder if people like BSDI have made a "strategic arrangement" > to get a native version? Unfortunately, I dont think we're in a position > to make Netscape an offer they can't refuse. :-( shit. and offering them a fast developement machine running -stable ? -- andreas@knobel.gun.de /\/\___ Wiechers & Partner Datentechnik GmbH Andreas Klemm ___/\/\/ - Support Unix - aklemm@wup.de - \/ ftp://sunsite.unc.edu/pub/Linux/system/Printing/aps-491.tgz apsfilter - magic print filter 4lpd >>> knobel is powered by FreeBSD <<< From owner-freebsd-current Tue Jan 30 11:12:30 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id LAA18846 for current-outgoing; Tue, 30 Jan 1996 11:12:30 -0800 (PST) Received: from time.cdrom.com (time.cdrom.com [192.216.222.226]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id LAA18826 for ; Tue, 30 Jan 1996 11:12:25 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by time.cdrom.com (8.7.3/8.6.9) with SMTP id LAA01920; Tue, 30 Jan 1996 11:10:11 -0800 (PST) To: davidg@Root.COM cc: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch), freebsd-current@freebsd.org (FreeBSD-current users) Subject: Re: any ideas about this crash? In-reply-to: Your message of "Tue, 30 Jan 1996 03:37:57 PST." <199601301137.DAA00416@Root.COM> Date: Tue, 30 Jan 1996 11:10:10 -0800 Message-ID: <1918.823029010@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-current@freebsd.org Precedence: bulk > clocks (read: laptops and "green" PCs). The folks in Intel's P6 architecture > group were shocked when they heard about what we were doing with the internal > cycle counter..."It was never intended to be used that way!". So where to from here, a BOGOMIPS rating at startup? :-) Jordan From owner-freebsd-current Tue Jan 30 11:13:27 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id LAA18913 for current-outgoing; Tue, 30 Jan 1996 11:13:27 -0800 (PST) Received: from time.cdrom.com (time.cdrom.com [192.216.222.226]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id LAA18901 for ; Tue, 30 Jan 1996 11:13:16 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by time.cdrom.com (8.7.3/8.6.9) with SMTP id LAA01931; Tue, 30 Jan 1996 11:12:06 -0800 (PST) To: uhclem@nemesis.lonestar.org (Frank Durda IV) cc: freebsd-current@freebsd.org Subject: Re: any ideas about this crash? In-reply-to: Your message of "Tue, 30 Jan 1996 10:18:00 +0700." Date: Tue, 30 Jan 1996 11:12:05 -0800 Message-ID: <1929.823029125@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-current@freebsd.org Precedence: bulk > vendors that you were. This Pentium internal timer is USELESS as a > TOD timepiece! Stop using it this way! It is only good for relative Whoops, ignore my previous comment. I sort of came in at the middle of this and thought you guys were talking about measuring processor speed (something else we get wrong, I guess) not the TOD. Jordan From owner-freebsd-current Tue Jan 30 11:14:51 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id LAA19002 for current-outgoing; Tue, 30 Jan 1996 11:14:51 -0800 (PST) Received: from time.cdrom.com (time.cdrom.com [192.216.222.226]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id LAA18995 for ; Tue, 30 Jan 1996 11:14:45 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by time.cdrom.com (8.7.3/8.6.9) with SMTP id LAA01942; Tue, 30 Jan 1996 11:13:48 -0800 (PST) To: Andreas Klemm cc: Peter Wemm , current@freebsd.org Subject: Re: Linux Netscape 2.0b6a? In-reply-to: Your message of "Tue, 30 Jan 1996 17:48:59 +0100." Date: Tue, 30 Jan 1996 11:13:47 -0800 Message-ID: <1940.823029227@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-current@freebsd.org Precedence: bulk > Does somebody know, why those people at mcom deceided not to include > Java support into the BSDI binary ? I was told that it's because BSD/OS doesn't support the runtime loading of shared libraries (no dlopen(), dlsym(), etc). Yes, I already suggested that they do a FreeBSD native support then. I don't think they were too enthusiastic.. :-) Jordan From owner-freebsd-current Tue Jan 30 11:23:14 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id LAA19789 for current-outgoing; Tue, 30 Jan 1996 11:23:14 -0800 (PST) Received: from news1.gtn.com (news1.gtn.com [192.109.159.3]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id LAA19780 for ; Tue, 30 Jan 1996 11:23:02 -0800 (PST) Received: (from uucp@localhost) by news1.gtn.com (8.7.2/8.7.2) id UAA13994 for current@freebsd.org; Tue, 30 Jan 1996 20:00:30 +0100 (MET) Received: (from andreas@localhost) by knobel.gun.de (8.7.3/8.7.3) id TAA06496 for current@freebsd.org; Tue, 30 Jan 1996 19:52:19 +0100 (MET) From: Andreas Klemm Message-Id: <199601301852.TAA06496@knobel.gun.de> Subject: -current a bit unstable for me, why ... ??? To: current@freebsd.org Date: Tue, 30 Jan 1996 19:52:19 +0100 (MET) X-Mailer: ELM [version 2.4 PL24 ME8b] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org Precedence: bulk Hi ! For weeks I had no problems with -current. Yesterday 2 system lockups with no error message. And now during runtime the system can't execute pstat -s. 15 minutes ago pstat -s worked very well. But now, pstat -s: pstat: cannot read swaplist: kvm_read: Bad address pstat: cannot read swaplist: kvm_read: Bad address pstat: cannot read swaplist: kvm_read: Bad address pstat: cannot read swaplist: kvm_read: Bad address .... The only thing I changed yesterday was a) supped new -current and rebuild kernel b) upgraded AWARD bios of my Asus board from rel. 0109 to 0114. The default value for the PCI latency timer changed from 80 to 32. Dunno if this change might cause trouble ... ?! Here a boot -v ... Jan 29 21:39:03 knobel /kernel: FreeBSD 2.2-CURRENT #0: Sun Jan 28 16:07:44 MET 1996 Jan 29 21:39:03 knobel /kernel: root@:/local/FreeBSD/current/src/sys/compile/KNOBEL Jan 29 21:39:03 knobel /kernel: CPU: Pentium (99.46-MHz 586-class CPU) Jan 29 21:39:03 knobel /kernel: Origin = "GenuineIntel" Id = 0x525 Stepping=5 Jan 29 21:39:03 knobel /kernel: Features=0x1bf Jan 29 21:39:03 knobel /kernel: real memory = 33554432 (32768K bytes) Jan 29 21:39:03 knobel /kernel: avail memory = 31477760 (30740K bytes) Jan 29 21:39:03 knobel /kernel: BIOS Geometries: Jan 29 21:39:03 knobel /kernel: 0:020afe3f 0..522=523 cylinders, 0..254=255 heads, 1..63=63 sectors Jan 29 21:39:03 knobel /kernel: 0 accounted for Jan 29 21:39:03 knobel /kernel: DEVFS: ready for devices Jan 29 21:39:03 knobel /kernel: pcibus_setup(1): mode 1 addr port (0x0cf8) is 0x8000005c Jan 29 21:39:03 knobel /kernel: pcibus_setup(1a): mode1res=0x80000000 (0x80000000) Jan 29 21:39:03 knobel /kernel: pcibus_check: device 0 is there (id=122d8086) Jan 29 21:39:03 knobel /kernel: Probing for devices on PCI bus 0: Jan 29 21:39:03 knobel /kernel: configuration mode 1 allows 32 devices. Jan 29 21:39:03 knobel /kernel: chip0 rev 2 on pci0:0 Jan 29 21:39:04 knobel /kernel: CPU Inactivity timer: clocks Jan 29 21:39:04 knobel /kernel: Peer Concurrency: enabled Jan 29 21:39:04 knobel /kernel: CPU-to-PCI Write Bursting: enabled Jan 29 21:39:04 knobel /kernel: PCI Streaming: enabled Jan 29 21:39:04 knobel /kernel: Bus Concurrency: enabled Jan 29 21:39:04 knobel /kernel: Cache: 256K pipelined-burst secondary; L1 enabled Jan 29 21:39:04 knobel /kernel: DRAM: no memory hole, 66 MHz refresh Jan 29 21:39:04 knobel /kernel: Read burst timing: x-2-2-2/x-3-3-3 Jan 29 21:39:04 knobel /kernel: Write burst timing: x-2-2-2 Jan 29 21:39:04 knobel /kernel: RAS-CAS delay: 2 clocks Jan 29 21:39:04 knobel /kernel: chip1 rev 2 on pci0:7 Jan 29 21:39:04 knobel /kernel: I/O Recovery Timing: 8-bit 1 clocks, 16-bit 1 clocks Jan 29 21:39:04 knobel /kernel: Extended BIOS: disabled Jan 29 21:39:04 knobel /kernel: Lower BIOS: enabled Jan 29 21:39:04 knobel /kernel: Coprocessor IRQ13: enabled Jan 29 21:39:05 knobel /kernel: Mouse IRQ12: disabled Jan 29 21:39:05 knobel /kernel: Interrupt Routing: A: IRQ11, B: disabled, C: IRQ12, D: disabled Jan 29 21:39:05 knobel /kernel: MB0: disabled, MB1: disabled Jan 29 21:39:05 knobel /kernel: chip2 rev 2 on pci0:7 Jan 29 21:39:05 knobel /kernel: mapreg[20] type=1 addr=0000e800 size=ffff0010. Jan 29 21:39:05 knobel /kernel: I/O Base Address: 0xe800 Jan 29 21:39:05 knobel /kernel: Primary IDE: disabled Jan 29 21:39:05 knobel /kernel: Secondary IDE: disabled Jan 29 21:39:05 knobel /kernel: vga0 rev 0 int a irq 12 on pci0:10 Jan 29 21:39:05 knobel /kernel: mapreg[10] type=0 addr=f8000000 size=2000000. Jan 29 21:39:05 knobel /kernel: ahc0 rev 3 int a irq 11 on pci0:12 Jan 29 21:39:05 knobel /kernel: mapreg[10] type=1 addr=0000e400 size=0100. Jan 29 21:39:05 knobel /kernel: mapreg[14] type=0 addr=f7ff0000 size=1000. Jan 29 21:39:05 knobel /kernel: ahc0: BurstLen = 8DWDs, Latency Timer = 32PCLKS Jan 29 21:39:05 knobel /kernel: ahc0: Reading SEEPROM...done. Jan 29 21:39:05 knobel /kernel: ahc0: aic7870 Single Channel, SCSI Id=7, 16 SCBs Jan 29 21:39:06 knobel /kernel: ahc0: Downloading Sequencer Program...Done Jan 29 21:39:06 knobel /kernel: ahc0: Probing channel A Jan 29 21:39:06 knobel /kernel: ahc0 waiting for scsi devices to settle Jan 29 21:39:06 knobel /kernel: ahc0: target 0 synchronous at 10.0MHz, offset = 0xf Jan 29 21:39:06 knobel /kernel: ahc0: target 0 Tagged Queuing Device Jan 29 21:39:06 knobel /kernel: (ahc0:0:0): "QUANTUM XP34301 1051" type 0 fixed SCSI 2 Jan 29 21:39:06 knobel /kernel: sd0(ahc0:0:0): Direct-Access 4106MB (8410200 512 byte sectors) Jan 29 21:39:06 knobel /kernel: sd0(ahc0:0:0): with 4076 cyls, 20 heads, and an average 103 sectors/track Jan 29 21:39:06 knobel /kernel: ahc0: target 6 synchronous at 4.0MHz, offset = 0xf Jan 29 21:39:06 knobel /kernel: (ahc0:6:0): "TOSHIBA CD-ROM XM-3601TA 0725" type 5 removable SCSI 2 Jan 29 21:39:06 knobel /kernel: cd0(ahc0:6:0): CD-ROM cd present [325252 x 2048 byte records] Jan 29 21:39:06 knobel /kernel: pci0: uses 33558528 bytes of memory from f7ff0000 upto f9ffffff. Jan 29 21:39:06 knobel /kernel: pci0: uses 272 bytes of I/O space from e400 upto e80f. Jan 29 21:39:06 knobel /kernel: Probing for devices on the ISA bus: Jan 29 21:39:07 knobel /kernel: sc0 at 0x60-0x6f irq 1 on motherboard Jan 29 21:39:07 knobel /kernel: sc0: VGA color <4 virtual consoles, flags=0x0> Jan 29 21:39:07 knobel /kernel: ed0 at 0x300-0x31f irq 10 maddr 0xcc000 msize 16384 on isa Jan 29 21:39:07 knobel /kernel: ed0: address 00:00:c0:25:fd:2d, type WD8013EPC (16 bit) Jan 29 21:39:07 knobel /kernel: bpf: ed0 attached Jan 29 21:39:07 knobel /kernel: sio0 at 0x3f8-0x3ff irq 4 on isa Jan 29 21:39:07 knobel /kernel: sio0: type 16550A Jan 29 21:39:07 knobel /kernel: sio1 at 0x2f8-0x2ff irq 3 on isa Jan 29 21:39:08 knobel /kernel: sio1: type 16550A Jan 29 21:39:08 knobel /kernel: lpt0 at 0x378-0x37f irq 7 on isa Jan 29 21:39:08 knobel /kernel: lpt0: Interrupt-driven port Jan 29 21:39:08 knobel /kernel: lp0: TCP/IP capable interface Jan 29 21:39:08 knobel /kernel: bpf: lp0 attached Jan 29 21:39:08 knobel /kernel: fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa Jan 29 21:39:08 knobel /kernel: fdc0: NEC 72065B Jan 29 21:39:08 knobel /kernel: fd0: 1.44MB 3.5in Jan 29 21:39:08 knobel /kernel: npx0 on motherboard Jan 29 21:39:08 knobel /kernel: npx0: INT 16 interface Jan 29 21:39:08 knobel /kernel: joy0 at 0x201 on isa Jan 29 21:39:08 knobel /kernel: joy0: joystick Jan 29 21:39:08 knobel /kernel: sb0 at 0x220 irq 5 drq 1 on isa Jan 29 21:39:08 knobel /kernel: sb0: Jan 29 21:39:08 knobel /kernel: sbxvi0 at 0x0 drq 5 on isa Jan 29 21:39:08 knobel /kernel: sbxvo0: Jan 29 21:39:08 knobel /kernel: sbmidi0 at 0x330 on isa Jan 29 21:39:08 knobel /kernel: Jan 29 21:39:08 knobel /kernel: opl0 at 0x388 on isa Jan 29 21:39:08 knobel /kernel: opl0: Jan 29 21:39:09 knobel /kernel: imasks: bio c0000840, tty c003009a, net c0020400 Jan 29 21:39:09 knobel /kernel: devfs ready to run Jan 29 21:39:09 knobel /kernel: bpf: tun0 attached Jan 29 21:39:09 knobel /kernel: bpf: lo0 attached Jan 29 21:39:09 knobel /kernel: sd0s1: type 0x6, start 63, end = 514079, size 514017 : OK Jan 29 21:39:09 knobel /kernel: sd0s2: type 0x5, start 514080, end = 2056319, size 1542240 : OK Jan 29 21:39:09 knobel /kernel: sd0s3: type 0xa5, start 2056320, end = 8401994, size 6345675 : OK Jan 29 21:39:09 knobel /kernel: sd0s5: type 0x6, start 514143, end = 1028159, size 514017 : OK Jan 29 21:39:09 knobel /kernel: sd0: type 0x5, start 1028160, end = 2056319, size 1028160 : OK Jan 29 21:39:09 knobel /kernel: sd0s6: type 0x7, start 1028223, end = 2056319, size 1028097 : OK My kernel config file: machine "i386" cpu "I586_CPU" ident KNOBEL maxusers 64 options INET #InterNETworking options FFS #Berkeley Fast Filesystem options PROCFS #Process filesystem options "COMPAT_43" #Compatible with BSD 4.3 options "SCSI_DELAY=3" #Be pessimistic about Joe SCSI device options UCONSOLE #Allow users to grab the console options FDESC #File descriptor filesystem options DEVFS #devices filesystem options SYSVSHM options SYSVSEM options SYSVMSG options AHC_TAGENABLE options QUEUE_FULL_SUPPORTED options SCSI_REPORT_GEOMETRY options MFS #Memory File System config kernel root on sd0 controller isa0 controller pci0 controller fdc0 at isa? port "IO_FD1" bio irq 6 drq 2 vector fdintr disk fd0 at fdc0 drive 0 controller ahc0 controller scbus0 device sd0 device st0 device cd0 #Only need one of these, the code dynamically grows # syscons is the default console driver, resembling an SCO console options "MAXCONS=4" device sc0 at isa? port "IO_KBD" tty irq 1 vector scintr device npx0 at isa? port "IO_NPX" irq 13 vector npxintr device sio0 at isa? port "IO_COM1" tty irq 4 vector siointr device sio1 at isa? port "IO_COM2" tty irq 3 vector siointr device lpt0 at isa? port? tty irq 7 vector lptintr device ed0 at isa? port 0x300 net irq 10 iomem 0xcc000 vector edintr # Joystick device joy0 at isa? port "IO_GAME" pseudo-device loop pseudo-device ether pseudo-device log pseudo-device tun 1 pseudo-device pty 16 pseudo-device bpfilter 2 #Berkeley packet filter pseudo-device snp 3 #Snoop device - to look at pty/vty/etc.. pseudo-device vn #Vnode driver (turns a file into a device) pseudo-device speaker # SB = SoundBlaster; PAS = ProAudioSpectrum; GUS = Gravis UltraSound # Controls all sound devices controller snd0 # SoundBlaster DSP driver - for SB, SB Pro, SB16, PAS(emulating SB) device sb0 at isa? port 0x220 irq 5 drq 1 vector sbintr # SoundBlaster 16 DSP driver - for SB16 - requires sb0 device device sbxvi0 at isa? drq 5 # SoundBlaster 16 MIDI - for SB16 - requires sb0 device device sbmidi0 at isa? port 0x330 # Yamaha OPL-2/OPL-3 FM - for SB, SB Pro, SB16, PAS device opl0 at isa? port 0x388 -- andreas@knobel.gun.de /\/\___ Wiechers & Partner Datentechnik GmbH Andreas Klemm ___/\/\/ - Support Unix - aklemm@wup.de - \/ ftp://sunsite.unc.edu/pub/Linux/system/Printing/aps-491.tgz apsfilter - magic print filter 4lpd >>> knobel is powered by FreeBSD <<< From owner-freebsd-current Tue Jan 30 12:00:48 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id MAA23851 for current-outgoing; Tue, 30 Jan 1996 12:00:48 -0800 (PST) Received: from jhome.DIALix.COM (root@jhome.DIALix.COM [192.203.228.69]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id MAA23841 for ; Tue, 30 Jan 1996 12:00:37 -0800 (PST) Received: from localhost.DIALix.oz.au (peter@localhost.DIALix.oz.au [127.0.0.1]) by jhome.DIALix.COM (8.7.3/8.7.3) with SMTP id EAA06557; Wed, 31 Jan 1996 04:00:08 +0800 (WST) Message-Id: <199601302000.EAA06557@jhome.DIALix.COM> X-Authentication-Warning: jhome.DIALix.COM: Host peter@localhost.DIALix.oz.au [127.0.0.1] didn't use HELO protocol To: "Jordan K. Hubbard" cc: Andreas Klemm , current@freebsd.org Subject: Re: Linux Netscape 2.0b6a? In-reply-to: Your message of "Tue, 30 Jan 1996 11:13:47 PST." <1940.823029227@time.cdrom.com> Date: Wed, 31 Jan 1996 04:00:07 +0800 From: Peter Wemm Sender: owner-current@freebsd.org Precedence: bulk >> Does somebody know, why those people at mcom deceided not to include >> Java support into the BSDI binary ? > >I was told that it's because BSD/OS doesn't support the runtime loading >of shared libraries (no dlopen(), dlsym(), etc). Sigh.. That's disappointing. The Linux version doesn't have or use it (runtime loading) either. The newer Linux ELF shared libraries have dlopen etc, but the a.out system that the Linux version is compiled under does not. For what it's worth, the Linux version is mostly statically linked and only uses the libc. It doesn't even use any X11 shared libs and doesn't come with any of it's own libraries to do a dlopen() on.. >Yes, I already suggested that they do a FreeBSD native support then. >I don't think they were too enthusiastic.. :-) > > Jordan I wonder if it's time to resort to terrorising their web server by posting a program to do a steady stream of fake http lookups and specify a "X-UserAgent: X11 (I; FreeBSD-2.x; i386)" string in the lookup to try and cause a "blip" on their usage stats. (yes, Netscape does count and record a profile of their users) A few hundred sites with spare bandwidth doing one reqest for "/" every 15 seconds might do it. Naturally, I'm joking, but it is tempting.. :-) Cheers, -Peter From owner-freebsd-current Tue Jan 30 12:16:27 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id MAA25414 for current-outgoing; Tue, 30 Jan 1996 12:16:27 -0800 (PST) Received: from ki.net (root@ki.net [142.77.249.8]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id MAA25405 for ; Tue, 30 Jan 1996 12:16:14 -0800 (PST) Received: (from scrappy@localhost) by ki.net (8.7.3/8.7.3) id PAA18847; Tue, 30 Jan 1996 15:15:34 -0500 (EST) Date: Tue, 30 Jan 1996 15:15:31 -0500 (EST) From: "Marc G. Fournier" To: Peter Wemm cc: "Jordan K. Hubbard" , Andreas Klemm , current@FreeBSD.org Subject: Re: Linux Netscape 2.0b6a? In-Reply-To: <199601302000.EAA06557@jhome.DIALix.COM> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@FreeBSD.org Precedence: bulk On Wed, 31 Jan 1996, Peter Wemm wrote: > I wonder if it's time to resort to terrorising their web server by posting a > program to do a steady stream of fake http lookups and specify a > "X-UserAgent: X11 (I; FreeBSD-2.x; i386)" string in the lookup to try and > cause a "blip" on their usage stats. (yes, Netscape does count and record > a profile of their users) A few hundred sites with spare bandwidth doing > one reqest for "/" every 15 seconds might do it. > > Naturally, I'm joking, but it is tempting.. :-) > Everyone doing this once a day though...? How many of us are there? Marc G. Fournier | POP Mail Telnet Acct DNS Hosting System | WWW Services Database Services | Knowledge, Administrator | | Information and scrappy@ki.net | WWW: http://www.ki.net | Communications, Inc From owner-freebsd-current Tue Jan 30 12:38:20 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id MAA27200 for current-outgoing; Tue, 30 Jan 1996 12:38:20 -0800 (PST) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id MAA27193 Tue, 30 Jan 1996 12:38:12 -0800 (PST) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id NAA07203; Tue, 30 Jan 1996 13:34:00 -0700 From: Terry Lambert Message-Id: <199601302034.NAA07203@phaeton.artisoft.com> Subject: Re: Optimization topics To: wscott@pdxlx008.intel.com (Wayne Scott) Date: Tue, 30 Jan 1996 13:34:00 -0700 (MST) Cc: bde@zeta.org.au, terry@lambert.org, current@freefall.freebsd.org, dyson@freefall.freebsd.org In-Reply-To: <199601301837.KAA07469@pdxlx008.intel.com.intel.com> from "Wayne Scott" at Jan 30, 96 10:37:55 am X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.ORG Precedence: bulk > I might have an easier solution for you. > > The Pentium Pro has a misaligned access performance counter that has > the ability to generate interrupts. You can tell the processor to > count misaligns and generate an interrupt every 1000 times it sees > one. > > Put this into you existing profiling code and you will get a profile > of where the system is doing misaligned references. Now you only need > to fix the very common cases in the critical paths. > > The same thing can be done which all the counters. Which branches are > not predicted well, where am I missing the cache, etc... > > The information is in the P6 PRM that should be available next month... I want a MIPS port. All unaligned access is to be forbidden, not just where it may impact performance. Unaligned access is one of the things tying Win95 to Intel. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-current Tue Jan 30 12:52:21 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id MAA28408 for current-outgoing; Tue, 30 Jan 1996 12:52:21 -0800 (PST) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id MAA28317 Tue, 30 Jan 1996 12:52:11 -0800 (PST) Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.9/8.6.9) id HAA25491; Wed, 31 Jan 1996 07:51:31 +1100 Date: Wed, 31 Jan 1996 07:51:31 +1100 From: Bruce Evans Message-Id: <199601302051.HAA25491@godzilla.zeta.org.au> To: current@freebsd.org, dyson@freebsd.org Subject: new pipes fail several tests #1 Sender: owner-current@freebsd.org Precedence: bulk The Minix test programs found several bugs in the new pipe code. #1: read() doesn't return -1/EAGAIN for EOF in non-blocking mode. See POSIX.1-1990 6.4.1.2(2). Bruce #include #include #include #include #include #include #define check(what, expected) assert((what, expected)) int main(void) { char buf[1]; int fd[2]; int r; r = pipe(fd); check("pipe", r == 0); r = fcntl(fd[0], F_SETFL, O_NONBLOCK); check("fcntl", r == 0); r = read(fd[0], buf, 1); printf("read %d bytes, errno = %d\n", r, errno); check("read", r == -1); check("read", errno == EAGAIN); return 0; } From owner-freebsd-current Tue Jan 30 12:53:56 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id MAA28517 for current-outgoing; Tue, 30 Jan 1996 12:53:56 -0800 (PST) Received: (from dyson@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id MAA28505 Tue, 30 Jan 1996 12:53:52 -0800 (PST) Date: Tue, 30 Jan 1996 12:53:52 -0800 (PST) From: John Dyson Message-Id: <199601302053.MAA28505@freefall.freebsd.org> To: bde@zeta.org.au, current@freebsd.org, dyson@freebsd.org Subject: Re: new pipes fail several tests #1 Sender: owner-current@freebsd.org Precedence: bulk Will fix it tonite!!!, also it'll be another 50% faster :-). John From owner-freebsd-current Tue Jan 30 13:17:45 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id NAA00402 for current-outgoing; Tue, 30 Jan 1996 13:17:45 -0800 (PST) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id NAA00376 Tue, 30 Jan 1996 13:17:25 -0800 (PST) Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.9/8.6.9) id IAA26417; Wed, 31 Jan 1996 08:15:16 +1100 Date: Wed, 31 Jan 1996 08:15:16 +1100 From: Bruce Evans Message-Id: <199601302115.IAA26417@godzilla.zeta.org.au> To: current@freebsd.org, dyson@freebsd.org Subject: new pipes fail several tests #2 Sender: owner-current@freebsd.org Precedence: bulk Writes to a pipe with no reader don't return -1/EPIPE. Bruce #include #include #include #include #include #include #define check(what, expected) assert((what, expected)) sig_atomic_t caught; static void catch(int s) { caught = 1; } int main(void) { char buf[1]; int fd[2]; int r; r = pipe(fd); check("pipe", r == 0); check("signal", signal(SIGPIPE, catch) != SIG_ERR); r = close(fd[0]); check("close", r == 0); r = write(fd[1], buf, 1); printf("wrote %d bytes, errno = %d, caught = %d\n", r, errno, caught); check("write", r == -1); check("write", errno == EPIPE); check("write", caught == 1); return 0; } From owner-freebsd-current Tue Jan 30 13:38:04 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id NAA01695 for current-outgoing; Tue, 30 Jan 1996 13:38:04 -0800 (PST) Received: from mail.cs.tu-berlin.de (root@mail.cs.tu-berlin.de [130.149.17.13]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id NAA01677 for ; Tue, 30 Jan 1996 13:37:51 -0800 (PST) Received: from caramba.cs.tu-berlin.de (wosch@caramba.cs.tu-berlin.de [130.149.17.12]) by mail.cs.tu-berlin.de (8.6.12/8.6.12) with ESMTP id WAA27701 for ; Tue, 30 Jan 1996 22:36:45 +0100 Received: (from wosch@localhost) by localhost (8.6.9/8.6.9) id WAA01347; Tue, 30 Jan 1996 22:24:21 +0100 Date: Tue, 30 Jan 1996 22:24:21 +0100 From: Wolfram Schneider Message-Id: <199601302124.WAA01347@localhost> To: current@freebsd.org Subject: chown in bsd.doc.mk and bsd.info.mk Reply-to: Wolfram Schneider MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-current@freebsd.org Precedence: bulk chown root.wheel ${DESTDIR}${BINDIR}/${VOLUME} should be: chown ${BINOWN}:${BINGRP} ${DESTDIR}${BINDIR}/${VOLUME} ^^^^^^^^^^^^^^^^^^^ Wolfram From owner-freebsd-current Tue Jan 30 13:57:59 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id NAA03651 for current-outgoing; Tue, 30 Jan 1996 13:57:59 -0800 (PST) Received: from mail.cs.tu-berlin.de (root@mail.cs.tu-berlin.de [130.149.17.13]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id NAA03617 for ; Tue, 30 Jan 1996 13:57:42 -0800 (PST) Received: from caramba.cs.tu-berlin.de (wosch@caramba.cs.tu-berlin.de [130.149.17.12]) by mail.cs.tu-berlin.de (8.6.12/8.6.12) with ESMTP id WAA27707; Tue, 30 Jan 1996 22:36:50 +0100 Received: (from wosch@localhost) by localhost (8.6.9/8.6.9) id WAA01244; Tue, 30 Jan 1996 22:01:24 +0100 Date: Tue, 30 Jan 1996 22:01:24 +0100 From: Wolfram Schneider Message-Id: <199601302101.WAA01244@localhost> To: Thomas Graichen Cc: current@freebsd.org Subject: Re: (fwd) too many cached pages for profiled kernel In-Reply-To: <199601300838.JAA16517@julia.physik.fu-berlin.de> References: <199601300212.NAA13193@godzilla.zeta.org.au> <199601300838.JAA16517@julia.physik.fu-berlin.de> Reply-to: Wolfram Schneider MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-current@freebsd.org Precedence: bulk Thomas Graichen writes: >ok - i may change it within the next days if nobody disagrees I suggest a new module `machine/m_freebsd21.c' ^ Wolfram From owner-freebsd-current Tue Jan 30 13:58:06 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id NAA03671 for current-outgoing; Tue, 30 Jan 1996 13:58:06 -0800 (PST) Received: from ki.net (root@ki.net [142.77.249.8]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id NAA03557 Tue, 30 Jan 1996 13:57:02 -0800 (PST) Received: (from scrappy@localhost) by ki.net (8.7.3/8.7.3) id QAA21071; Tue, 30 Jan 1996 16:55:16 -0500 (EST) Date: Tue, 30 Jan 1996 16:55:12 -0500 (EST) From: "Marc G. Fournier" To: current@freebsd.org cc: questions@freebsd.org Subject: sup server/system builds Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org Precedence: bulk Hi... I couldn't think of a better (or worse) subject, and the one that is there isn't very informative, so apologies for that... now, I've setup one of my machines as a supfile server, right now with current/ports being kept up to date on a daily basis. (the link is sllloooowwww, but its there if anyone really needs it...'sup.ki.net' will work) What I want to know is how do ppl maintain both a sup server on a machine, as well as maintain their -current implementation without messing up the sup server side of things. I tried to sup to the same machine,but a different directory, but that doesn't work. If I build in the same directories, then if someone sup's in from my machine, they'll get a mess of files that they don't need. I figure I'm probably missing something (find . -print | cpio... could be one solution, altho messy, I would think), so hopefully someone can give me a guiding hand on this? Thanks... Marc G. Fournier | POP Mail Telnet Acct DNS Hosting System | WWW Services Database Services | Knowledge, Administrator | | Information and scrappy@ki.net | WWW: http://www.ki.net | Communications, Inc From owner-freebsd-current Tue Jan 30 14:00:27 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id OAA03964 for current-outgoing; Tue, 30 Jan 1996 14:00:27 -0800 (PST) Received: from ref.tfs.com (ref.tfs.com [140.145.254.251]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id OAA03893 for ; Tue, 30 Jan 1996 14:00:06 -0800 (PST) Received: (from julian@localhost) by ref.tfs.com (8.6.12/8.6.9) id NAA09092 for current@freebsd.org; Tue, 30 Jan 1996 13:59:21 -0800 Date: Tue, 30 Jan 1996 13:59:21 -0800 From: Julian Elischer Message-Id: <199601302159.NAA09092@ref.tfs.com> To: current@freebsd.org Subject: upgrade 2.1->2.2 failure Sender: owner-current@freebsd.org Precedence: bulk sed from 2.1 coredumped cd /usr/src/usr.bin/sed make all install fixed the problem (BTW sed was being called when doing 'make libraries' I believe.. as part of make world) julian From owner-freebsd-current Tue Jan 30 14:07:03 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id OAA04561 for current-outgoing; Tue, 30 Jan 1996 14:07:03 -0800 (PST) Received: from Sysiphos (Sysiphos.MI.Uni-Koeln.DE [134.95.212.10]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id OAA04528 for ; Tue, 30 Jan 1996 14:06:50 -0800 (PST) Received: by Sysiphos id AA04937 (5.67b/IDA-1.5 for freebsd-current@freebsd.org); Tue, 30 Jan 1996 23:05:57 +0100 Message-Id: <199601302205.AA04937@Sysiphos> From: se@zpr.uni-koeln.de (Stefan Esser) Date: Tue, 30 Jan 1996 23:05:57 +0100 In-Reply-To: "Jordan K. Hubbard" "Re: any ideas about this crash?" (Jan 30, 11:10) X-Mailer: Mail User's Shell (7.2.6 alpha(2) 7/9/95) To: "Jordan K. Hubbard" Subject: Re: any ideas about this crash? Cc: freebsd-current@freebsd.org Sender: owner-current@freebsd.org Precedence: bulk On Jan 30, 11:10, "Jordan K. Hubbard" wrote: } Subject: Re: any ideas about this crash? } > clocks (read: laptops and "green" PCs). The folks in Intel's P6 architecture } > group were shocked when they heard about what we were doing with the internal } > cycle counter..."It was never intended to be used that way!". } } So where to from here, a BOGOMIPS rating at startup? :-) YES! I'm all for it! But we always display TWICE the value Linux would return X-) :-) This gives us quite a competetive advantage ! Regards, STefan -- Stefan Esser, Zentrum fuer Paralleles Rechnen Tel: +49 221 4706021 Universitaet zu Koeln, Weyertal 80, 50931 Koeln FAX: +49 221 4705160 ============================================================================== http://www.zpr.uni-koeln.de/~se From owner-freebsd-current Tue Jan 30 14:35:57 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id OAA11892 for current-outgoing; Tue, 30 Jan 1996 14:35:57 -0800 (PST) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id OAA11874 Tue, 30 Jan 1996 14:35:44 -0800 (PST) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id PAA07678; Tue, 30 Jan 1996 15:29:54 -0700 From: Terry Lambert Message-Id: <199601302229.PAA07678@phaeton.artisoft.com> Subject: Re: Optimization topics To: terry@safetynet.net (Terry Lambert) Date: Tue, 30 Jan 1996 15:29:54 -0700 (MST) Cc: wscott@pdxlx008.intel.com, bde@zeta.org.au, terry@lambert.org, current@freefall.freebsd.org, dyson@freefall.freebsd.org In-Reply-To: <199601302034.NAA07203@phaeton.artisoft.com> from "Terry Lambert" at Jan 30, 96 01:34:00 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.ORG Precedence: bulk > I want a MIPS port. All unaligned access is to be forbidden, not just > where it may impact performance. > > Unaligned access is one of the things tying Win95 to Intel. Note: that may have seemed harsh. I am a portability bigot, not an anti-Intel bigot. ...Though if you could get rid of segements in the P7 design, I'd be grateful. 8-). Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-current Tue Jan 30 14:42:34 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id OAA12391 for current-outgoing; Tue, 30 Jan 1996 14:42:34 -0800 (PST) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id OAA12378 Tue, 30 Jan 1996 14:42:18 -0800 (PST) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id PAA07715; Tue, 30 Jan 1996 15:39:46 -0700 From: Terry Lambert Message-Id: <199601302239.PAA07715@phaeton.artisoft.com> Subject: Re: new pipes fail several tests #1 To: dyson@freefall.freebsd.org (John Dyson) Date: Tue, 30 Jan 1996 15:39:46 -0700 (MST) Cc: bde@zeta.org.au, current@FreeBSD.org, dyson@FreeBSD.org In-Reply-To: <199601302053.MAA28505@freefall.freebsd.org> from "John Dyson" at Jan 30, 96 12:53:52 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.org Precedence: bulk > Will fix it tonite!!!, also it'll be another 50% faster :-). When I ioctl my birthday down as a command with a buffer, it doesn't put "Happy Birthday, Terry!" in the buffer. This isn't a bug, but if evey time you touch the code it gets faster, I figured I'd give you an excuse to touch it again. 8-) 8-). Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-current Tue Jan 30 15:11:54 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id PAA15798 for current-outgoing; Tue, 30 Jan 1996 15:11:54 -0800 (PST) Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id PAA15730 for ; Tue, 30 Jan 1996 15:11:27 -0800 (PST) Received: from sax.sax.de by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id AAA22453 for ; Wed, 31 Jan 1996 00:09:43 +0100 Received: by sax.sax.de (8.6.11/8.6.12-s1) with UUCP id AAA05074 for freebsd-current@FreeBSD.org; Wed, 31 Jan 1996 00:09:42 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.7.3/8.6.9) id XAA16189 for freebsd-current@FreeBSD.org; Tue, 30 Jan 1996 23:59:36 +0100 (MET) From: J Wunsch Message-Id: <199601302259.XAA16189@uriah.heep.sax.de> Subject: invalid primary partition table: no magic To: freebsd-current@FreeBSD.org (FreeBSD-current users) Date: Tue, 30 Jan 1996 23:59:36 +0100 (MET) Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) X-Phone: +49-351-2012 669 X-Mailer: ELM [version 2.4 PL23] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-current@FreeBSD.org Precedence: bulk Couldn't we find a way to stop this? uriah # vnconfig -c /dev/rvn0 fooimage uriah # Jan 30 23:51:48 uriah /kernel: vn0: invalid primary partition table: no magic It's starting to get annoying. Not only that any /dev/zero-created empty file that we are about to disklabel during the release process causes this bogus warning (until it's disklabeled -B), but fooimage above was an cd9660 image, so the warning is not of much use. Since the warning is not of interest for ``ordinary people'' anyway, i'd vote for hiding it behind some debugging option (perhaps enabled via sysconfig). -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-current Tue Jan 30 15:47:29 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id PAA19980 for current-outgoing; Tue, 30 Jan 1996 15:47:29 -0800 (PST) Received: from mshslc.k12.mi.us (pm039-03.dialip.mich.net [198.110.208.14]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id PAA19966 for ; Tue, 30 Jan 1996 15:47:18 -0800 (PST) Received: (from root@localhost) by mshslc.k12.mi.us (8.7.3/8.7.3) id SAA01637 for freebsd-current@freebsd.org; Tue, 30 Jan 1996 18:45:23 GMT Date: Tue, 30 Jan 1996 18:45:23 GMT From: Rut0fAll3v1l Message-Id: <199601301845.SAA01637@mshslc.k12.mi.us> To: freebsd-current@freebsd.org Subject: ps, w Sender: owner-current@freebsd.org Precedence: bulk I got the 960116 snapshot from freedffall  bah freefall...Anyways I needed some kernel sources to kmake a new kernel so i got current as of jan 23. ps an d w broke after that so i got current ps/w and they are still broken. I now have a jan 30 kernel source tree which i haven't yet booted under cuz i'm gettin irq/drq values for my soundblaster equipment which i will put in the config file later.. but tha's not relavent.. ps and w complain about the chunk size and so forth.. From owner-freebsd-current Tue Jan 30 16:43:58 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id QAA24879 for current-outgoing; Tue, 30 Jan 1996 16:43:58 -0800 (PST) Received: from prod1.satelnet.org (prod1.satelnet.org [204.157.227.1]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id QAA24846 for ; Tue, 30 Jan 1996 16:43:46 -0800 (PST) Received: from sefl by prod1.satelnet.org; (5.65/1.1.8.2/04Mar95-0901AM) id AA05117; Tue, 30 Jan 1996 19:43:44 -0500 Received: (from ccappuc@localhost) by sefl.satelnet.org (8.6.8.1/8.6.6) id TAA17384 for current@freebsd.org; Tue, 30 Jan 1996 19:42:17 -0500 Date: Tue, 30 Jan 1996 19:42:17 -0500 From: Chris Cappuccio Message-Id: <199601310042.TAA17384@sefl.satelnet.org> To: current@freebsd.org Sender: owner-current@freebsd.org Precedence: bulk I have the 960116 snapshot installed just a few days after it appeared on freefall (I could not get the 2.1 boot flp to install over ppp with ftp at all!)... I decided that I might as well use the -current kernel sources becasue there's something appealing about bleeding edge ;) Anyways, between 1/16 and 1/23-current ps and w became incompatible with the kernel (proc size mismatch err something...) and recompiling them does nothing to help... any fix? From owner-freebsd-current Tue Jan 30 16:50:00 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id QAA25491 for current-outgoing; Tue, 30 Jan 1996 16:50:00 -0800 (PST) Received: from apollo.COSC.GOV (root@apollo.COSC.GOV [198.94.103.34]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id QAA25476 for ; Tue, 30 Jan 1996 16:49:44 -0800 (PST) Received: (from vince@localhost) by apollo.COSC.GOV (8.7.3/8.6.9) id QAA12830; Tue, 30 Jan 1996 16:49:35 -0800 (PST) Date: Tue, 30 Jan 1996 16:49:34 -0800 (PST) From: -Vince- To: current@FreeBSD.ORG Subject: make world failed Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@FreeBSD.ORG Precedence: bulk cc -O -I/usr/src/usr.sbin/lsdev/../../sys -c /usr/src/usr.sbin/lsdev/i386.c /usr/src/usr.sbin/lsdev/i386.c: In function `print_eisa': /usr/src/usr.sbin/lsdev/i386.c:168: structure has no member named `iobase' /usr/src/usr.sbin/lsdev/i386.c:169: structure has no member named `iobase' /usr/src/usr.sbin/lsdev/i386.c:169: structure has no member named `iosize' *** Error code 1 Stop. Cheers, -Vince- vince@COSC.GOV - GUS Mailing Lists Admin - http://www.COSC.GOV/~vince UC Berkeley AstroPhysics - Electrical Engineering (Honorary B.S.) Chabot Observatory & Science Center - Board of Advisors Running FreeBSD - Real UN*X for Free! Linda Wong/Vivian Chow/Hacken Lee/Danny Chan/Priscilla Chan Fan Club Mailing Lists Admin From owner-freebsd-current Tue Jan 30 17:14:37 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id RAA27728 for current-outgoing; Tue, 30 Jan 1996 17:14:37 -0800 (PST) Received: from fw.ast.com (fw.ast.com [165.164.6.25]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id RAA27719 for ; Tue, 30 Jan 1996 17:14:27 -0800 (PST) Received: from nemesis by fw.ast.com with uucp (Smail3.1.29.1 #2) id m0thR2v-000858C; Tue, 30 Jan 96 19:09 CST Received: by nemesis.lonestar.org (Smail3.1.27.1 #20) id m0thQws-000C6IC; Tue, 30 Jan 96 19:02 WET Message-Id: Date: Tue, 30 Jan 96 19:02 WET To: davidg@Root.COM, freebsd-current@freebsd.org From: uhclem@nemesis.lonestar.org (Frank Durda IV) Sent: Tue Jan 30 1996, 19:02:57 CST Subject: Re: any ideas about this crash? Sender: owner-current@freebsd.org Precedence: bulk [6]This Pentium internal timer is USELESS as a [6]TOD timepiece! Stop using it this way! It is only good for relative [6]measurements within the processors realm. [7]"USELESS" might be a little strong - it does have the merit of being a [7]very fast, "accurate", and easy way to do time measurements. That's why I said what I said above. For measurements of relative times within the processor, its ok. The moment you leave that context and try to use it to compare between different brands of machines or hold it against an external clock standard, it is useless. Frank Durda IV |"Your choice: FreeBSD or or uhclem%nemesis@rwsystr.nkn.net | Bob-Pro. See, that wasn't so ^------(this is the fastest route)| tough." (C) July 1995, FDIV or ...letni!rwsys!nemesis!uhclem | From owner-freebsd-current Tue Jan 30 17:26:57 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id RAA28712 for current-outgoing; Tue, 30 Jan 1996 17:26:57 -0800 (PST) Received: from fw.ast.com (fw.ast.com [165.164.6.25]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id RAA28696 for ; Tue, 30 Jan 1996 17:26:48 -0800 (PST) Received: from nemesis by fw.ast.com with uucp (Smail3.1.29.1 #2) id m0thRHb-000859C; Tue, 30 Jan 96 19:24 CST Received: by nemesis.lonestar.org (Smail3.1.27.1 #20) id m0thRDH-000CAPC; Tue, 30 Jan 96 19:19 WET Message-Id: Date: Tue, 30 Jan 96 19:19 WET To: ache@astral.msk.su From: uhclem@nemesis.lonestar.org (Frank Durda IV) Sent: Tue Jan 30 1996, 19:19:54 CST Subject: re: ATTENTION to CD driver authors (matcd, scd) Cc: current@freebsd.org Sender: owner-current@freebsd.org Precedence: bulk [0]I found that READTOCENTRYS ioctl completely broken in matcd/scd. [0]I don't have enough time to fix them and not have those cards to test [0]the fix. [0]So, please fix them. [0]As template you can look at mcd,wcd,cd drivers, here is correct [0]implementation after my latest commit sequence. Uh, would you mind saying what you think is wrong? I spent a lot of time on those ioctls in the matcd driver for 2.1.0, and made them: (A) EXACTLY match the output that the other drivers were generating (I checked several out since there were some disagreements between mcd, wcd, scd, and cd). And, (B) EXACTLY match the output that xcdplayer was expecting. And, (C) EXACTLY match the output that cdplayer was expecting. Now in the past few days I have noticed changes going through for cdplayer and other drivers. Are we redefining what is "correct"? Is there any particular reason, since these ioctls and the apps that used them *were* working? Frank Durda IV |"The Knights who say "LETNi" or uhclem%nemesis@rwsystr.nkn.net | demand... A SEGMENT REGISTER!!!" ^------(this is the fastest route)|"A what?" or ...letni!rwsys!nemesis!uhclem |"LETNi! LETNi! LETNi!" - 1983 From owner-freebsd-current Tue Jan 30 17:44:54 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id RAA00249 for current-outgoing; Tue, 30 Jan 1996 17:44:54 -0800 (PST) Received: from who.cdrom.com (who.cdrom.com [192.216.222.3]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id RAA00243 for ; Tue, 30 Jan 1996 17:44:45 -0800 (PST) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by who.cdrom.com (8.6.12/8.6.11) with ESMTP id RAA02267 for ; Tue, 30 Jan 1996 17:44:21 -0800 Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.9/8.6.9) id MAA05401; Wed, 31 Jan 1996 12:32:12 +1100 Date: Wed, 31 Jan 1996 12:32:12 +1100 From: Bruce Evans Message-Id: <199601310132.MAA05401@godzilla.zeta.org.au> To: davidg@Root.COM, uhclem@nemesis.lonestar.org Subject: Re: any ideas about this crash? Cc: freebsd-current@freebsd.org Sender: owner-current@freebsd.org Precedence: bulk >> This Pentium internal timer is USELESS as a >>TOD timepiece! Stop using it this way! It is only good for relative >>measurements within the processors realm. >> >>Why give the Linux guys something else to razz us about? > "USELESS" might be a little strong - it does have the merit of being a very >fast, "accurate", and easy way to do time measurements. Unfortunately, it also It needs to be accurate to about 1% or better for the time measurements to be useful. >has apparantly shown us that DELAY() has a bug of some kind as *all* of the >machines I've tested come up with an incorrect calibration about 10% of the >time I boot. The result it comes up with is actually wrong, too, as the >statistics that the system generates later are clearly wrong (off by the same >amount as the mis-calibration). It acts like some sort of rounding or >arithmetic error that occurs during the calibration. Which statistics? The statistics clock uses the real time clock so it isn't affected by misc-calibration. The statistics counts are only used as weights inside the kernel so only their relative values matter. Everything depends on the accuracy of microtime(), which depended on the accuracy of the calibration of the Pentium clock until Garrett changed things a few hours ago. I'm surprised that people don't notice the time being wrong more than the boot message or statistics. A 10% error is 2.4 hours/day. Try profiling a kernel configured for high resolution profiling (config -pp). Then times are accumulated using cputime(), which uses essentially the same method as DELAY() for reading the 8254 clock. Consistent biases and invalid clock values should show up in the statistics. Bruce From owner-freebsd-current Tue Jan 30 18:05:07 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id SAA01465 for current-outgoing; Tue, 30 Jan 1996 18:05:07 -0800 (PST) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id SAA01382 for ; Tue, 30 Jan 1996 18:03:31 -0800 (PST) Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.9/8.6.9) id NAA06888; Wed, 31 Jan 1996 13:01:03 +1100 Date: Wed, 31 Jan 1996 13:01:03 +1100 From: Bruce Evans Message-Id: <199601310201.NAA06888@godzilla.zeta.org.au> To: current@freebsd.org, wosch@cs.tu-berlin.de Subject: Re: chown in bsd.doc.mk and bsd.info.mk Sender: owner-current@freebsd.org Precedence: bulk >chown root.wheel ${DESTDIR}${BINDIR}/${VOLUME} >should be: >chown ${BINOWN}:${BINGRP} ${DESTDIR}${BINDIR}/${VOLUME} > ^^^^^^^^^^^^^^^^^^^ Actually, the chown shouldn't be there at all. The directory should be created by mtree, not by `mkdir -p' in the Makefile. bsd.prog.mk has a silly `chown games.bin' of a symlink. chown(8) is now a no-op. Bruce From owner-freebsd-current Tue Jan 30 18:37:26 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id SAA03539 for current-outgoing; Tue, 30 Jan 1996 18:37:26 -0800 (PST) Received: (from dima@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id SAA03523 Tue, 30 Jan 1996 18:37:09 -0800 (PST) Message-Id: <199601310237.SAA03523@freefall.freebsd.org> Subject: Re: Good news -- pipe stuffdd To: nate@sri.MT.net (Nate Williams) Date: Tue, 30 Jan 1996 18:37:07 -0800 (PST) Cc: dyson@freefall.freebsd.org, current@freefall.freebsd.org In-Reply-To: <199601261658.JAA02871@rocky.sri.MT.net> from "Nate Williams" at Jan 26, 96 09:58:36 am From: dima@FreeBSD.ORG (Dima Ruban) X-Class: Fast Organization: HackerDome X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-current@FreeBSD.ORG Precedence: bulk Nate Williams writes: > > > Pipe latency is about 2x the speed, pipe bandwidth is about 50% faster, > > and I am still evaluating the context switch -- but it is faster. > > Go Johnny go, go, Johnny be *good*. :-) > > [ For those international folks who didn't understand that, it's the > words to be an old Chuck Barry song. ] Yeah, right! From my expirience, at least half of the Americans didn't even heard about Chuck Berry :-) Maybe more :-) > > > Nate > -- dima From owner-freebsd-current Tue Jan 30 19:43:29 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id TAA07818 for current-outgoing; Tue, 30 Jan 1996 19:43:29 -0800 (PST) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id TAA07806 for ; Tue, 30 Jan 1996 19:43:13 -0800 (PST) Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.9/8.6.9) id OAA11342; Wed, 31 Jan 1996 14:38:58 +1100 Date: Wed, 31 Jan 1996 14:38:58 +1100 From: Bruce Evans Message-Id: <199601310338.OAA11342@godzilla.zeta.org.au> To: freebsd-current@FreeBSD.org, j@uriah.heep.sax.de Subject: Re: invalid primary partition table: no magic Sender: owner-current@FreeBSD.org Precedence: bulk >Couldn't we find a way to stop this? >uriah # vnconfig -c /dev/rvn0 fooimage >uriah # Jan 30 23:51:48 uriah /kernel: vn0: invalid primary partition table: no magic >It's starting to get annoying. Not only that any /dev/zero-created >empty file that we are about to disklabel during the release process >causes this bogus warning (until it's disklabeled -B), but fooimage >above was an cd9660 image, so the warning is not of much use. >Since the warning is not of interest for ``ordinary people'' anyway, >i'd vote for hiding it behind some debugging option (perhaps enabled >via sysconfig). It is an error for disks that should have a partition table, but since there is no way of telling which disks those are, it is hard to tell when to suppress the warning. For emulating physical disks that don't have partition tables or labels, don't use the `-s labels' option to vnconfig. Bruce From owner-freebsd-current Tue Jan 30 20:34:56 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id UAA12065 for current-outgoing; Tue, 30 Jan 1996 20:34:56 -0800 (PST) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id UAA12023 Tue, 30 Jan 1996 20:34:36 -0800 (PST) Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.9/8.6.9) id PAA13400; Wed, 31 Jan 1996 15:29:45 +1100 Date: Wed, 31 Jan 1996 15:29:45 +1100 From: Bruce Evans Message-Id: <199601310429.PAA13400@godzilla.zeta.org.au> To: current@freebsd.org, dyson@freebsd.org Subject: new pipes fail several tests #3 Sender: owner-current@freebsd.org Precedence: bulk The fixes for #1 and #2 seem to work. Thanks. New pipes are uninterruptible, unlike old pipes and named pipes. The SA_RESTART bit in sa.sa_flags is cleared so no syscalls should be restarted when the signal occurs. This is probably because sys_pipe.c converts all or almost all of the nonzero returned by tsleep() to ERESTART. The signal catcher wasn't called. I think it should be called even for syscalls that are restarted. Bruce #include #include #include #include #include #include #include #include #define check(what, expected) assert((what, expected)) sig_atomic_t caught; void catch(int s) { caught = 1; } int main(void) { char buf[1]; int fd[2]; struct sigaction osa, sa; pid_t pid, rpid; int r; int status; r = pipe(fd); check("pipe", r == 0); pid = fork(); check("fork", pid != -1); switch(pid) { case 0: alarm(5); sa.sa_handler = catch; sigemptyset(&sa.sa_mask); sa.sa_flags = 0; r = sigaction(SIGUSR1, &sa, &osa); check("sigaction", r == 0); #ifdef OK sleep(3); check("sleep", caught == 1); #else r = read(fd[0], buf, sizeof buf); printf("read %d bytes, errno = %d, caught = %d\n", r, errno, caught); check("read", r == -1); check("read", errno == EINTR); check("read", caught == 1); #endif r = sigaction(SIGUSR1, &osa, NULL); check("sigaction2", r == 0); r = close(fd[0]); check("close", r == 0); r = close(fd[1]); check("close2", r == 0); break; default: sleep(1); r = close(fd[0]); check("close3", r == 0); r = kill(pid, SIGUSR1); check("kill", r == 0); rpid = wait(&status); printf("wait returned %ld, status = %d, errno = %d\n", rpid, status, errno); check("wait", rpid == pid); check("wait", status == 0); break; } return 0; } From owner-freebsd-current Tue Jan 30 21:20:36 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id VAA16639 for current-outgoing; Tue, 30 Jan 1996 21:20:36 -0800 (PST) Received: from localhost.cdrom.com (localhost.cdrom.com [127.0.0.1]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id VAA16561 Tue, 30 Jan 1996 21:20:18 -0800 (PST) Message-Id: <199601310520.VAA16561@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: Host localhost.cdrom.com [127.0.0.1] didn't use HELO protocol To: -Vince- cc: current@FreeBSD.ORG Subject: Re: make world failed In-reply-to: Your message of "Tue, 30 Jan 1996 16:49:34 PST." Date: Tue, 30 Jan 1996 21:20:15 -0800 From: "Justin T. Gibbs" Sender: owner-current@FreeBSD.ORG Precedence: bulk Old news Vince. This was discussed in depth yesturday. Read the archives for details. >cc -O -I/usr/src/usr.sbin/lsdev/../../sys -c /usr/src/usr.sbin/lsdev/i386.c >/usr/src/usr.sbin/lsdev/i386.c: In function `print_eisa': >/usr/src/usr.sbin/lsdev/i386.c:168: structure has no member named `iobase' >/usr/src/usr.sbin/lsdev/i386.c:169: structure has no member named `iobase' >/usr/src/usr.sbin/lsdev/i386.c:169: structure has no member named `iosize' >*** Error code 1 > >Stop. > >Cheers, >-Vince- vince@COSC.GOV - GUS Mailing Lists Admin - http://www.COSC.GOV/~vince >UC Berkeley AstroPhysics - Electrical Engineering (Honorary B.S.) >Chabot Observatory & Science Center - Board of Advisors >Running FreeBSD - Real UN*X for Free! >Linda Wong/Vivian Chow/Hacken Lee/Danny Chan/Priscilla Chan Fan Club >Mailing Lists Admin -- Justin T. Gibbs =========================================== FreeBSD: Turning PCs into workstations =========================================== From owner-freebsd-current Tue Jan 30 22:09:01 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id WAA20602 for current-outgoing; Tue, 30 Jan 1996 22:09:01 -0800 (PST) Received: from dyson.iquest.net (dyson.iquest.net [198.70.144.127]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id WAA20583 Tue, 30 Jan 1996 22:08:52 -0800 (PST) Received: (from root@localhost) by dyson.iquest.net (8.6.11/8.6.9) id AAA00200; Wed, 31 Jan 1996 00:59:05 GMT From: "John S. Dyson" Message-Id: <199601310059.AAA00200@dyson.iquest.net> Subject: Re: new pipes fail several tests #3 To: bde@zeta.org.au (Bruce Evans) Date: Wed, 31 Jan 1996 00:59:05 +0000 () Cc: current@freebsd.org, dyson@freebsd.org In-Reply-To: <199601310429.PAA13400@godzilla.zeta.org.au> from "Bruce Evans" at Jan 31, 96 03:29:45 pm X-Mailer: ELM [version 2.4 PL24 ME8] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org Precedence: bulk > > The fixes for #1 and #2 seem to work. Thanks. > > New pipes are uninterruptible, unlike old pipes and named pipes. > The SA_RESTART bit in sa.sa_flags is cleared so no syscalls should > be restarted when the signal occurs. > > This is probably because sys_pipe.c converts all or almost all of > the nonzero returned by tsleep() to ERESTART. > > The signal catcher wasn't called. I think it should be called > even for syscalls that are restarted. > > Bruce > Just committed the fix!!! THANKS again Bruce!!! John dyson@freebsd.org From owner-freebsd-current Tue Jan 30 23:47:55 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id XAA27310 for current-outgoing; Tue, 30 Jan 1996 23:47:55 -0800 (PST) Received: from omega.physik.fu-berlin.de (omega.physik.fu-berlin.de [130.133.3.51]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id XAA27300 for ; Tue, 30 Jan 1996 23:47:41 -0800 (PST) Received: from prospero.physik.fu-berlin.de (lislip.physik.fu-berlin.de [130.133.3.126]) by omega.physik.fu-berlin.de (8.7.1/8.7.1) with ESMTP id IAA07121; Wed, 31 Jan 1996 08:37:55 +0100 (MET) Received: (from graichen@localhost) by prospero.physik.fu-berlin.de (8.6.12/8.6.12) id IAA00472; Wed, 31 Jan 1996 08:32:17 +0100 From: Thomas Graichen Message-Id: <199601310732.IAA00472@prospero.physik.fu-berlin.de> Subject: Re: (fwd) too many cached pages for profiled kernel To: wosch@cs.tu-berlin.de Date: Wed, 31 Jan 1996 08:31:23 +0100 (MET) Cc: graichen@omega.physik.fu-berlin.de, current@freebsd.org In-Reply-To: <199601302101.WAA01244@localhost> from "Wolfram Schneider" at Jan 30, 96 10:01:24 pm X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-current@freebsd.org Precedence: bulk hasn't Wolfram Schneider said ? ... > > Thomas Graichen writes: > >ok - i may change it within the next days if nobody disagrees > > I suggest a new module `machine/m_freebsd21.c' > ^ i may also make a new module - but it will take some time - because i'm currently very short on time - maybe someone else wil do it before me ? t _______________________________________________________||___________________ __|| Perfection is reached, not when there is no __|| thomas graichen longer anything to add, but when there __|| freie universitaet berlin is no longer anything to take away __|| fachbereich physik __|| - Antoine de Saint-Exupery - __|| graichen@mail.physik.fu-berlin.de ___________________________||__________________graichen@FreeBSD.org_________ From owner-freebsd-current Wed Jan 31 00:03:59 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id AAA28628 for current-outgoing; Wed, 31 Jan 1996 00:03:59 -0800 (PST) Received: from jhome.DIALix.COM (root@jhome.DIALix.COM [192.203.228.69]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id AAA28559 for ; Wed, 31 Jan 1996 00:03:08 -0800 (PST) Received: (from peter@localhost) by jhome.DIALix.COM (8.7.3/8.7.3) id QAA07718; Wed, 31 Jan 1996 16:02:09 +0800 (WST) Date: Wed, 31 Jan 1996 16:02:09 +0800 (WST) From: Peter Wemm Message-Id: <199601310802.QAA07718@jhome.DIALix.COM> To: jkh@time.cdrom.com (Jordan K. Hubbard) cc: current@freebsd.org Subject: Re: any ideas about this crash? Newsgroups: freebsd.current References: <199601301137.DAA00416@Root.COM> <1918.823029010@time.cdrom.com> X-Newsreader: NN version 6.5.0 #1 (NOV) Sender: owner-current@freebsd.org Precedence: bulk In freebsd.current Jordan K. Hubbard writes: >> clocks (read: laptops and "green" PCs). The folks in Intel's P6 architecture >> group were shocked when they heard about what we were doing with the internal >> cycle counter..."It was never intended to be used that way!". >So where to from here, a BOGOMIPS rating at startup? :-) I'd agree to a BOGOMIPS rating at bootup, but only if we multiplied the result by 1.5 in order to make a machine's bogomips rating under FreeBSD significantly higher than the same machine under Linux, thus "prove" that FreeBSD is heaps faster... :-) Seriously, bogomips would likely be a pain in the backside if we attempted to make it comparable to Linux, because if Joe User got 81.23 bogomips under Linux and "only" 81.22 under FreeBSD, they'd just _have_ to write in to complain to us how much slower it is. (This is just like the users over here in *.au that phone you to complain that a modem answered the modem call but didn't give them a login: prompt because the machine was down and "wasted" their $0.25 flag-fall local call fee. (Just like they've just blown an extra $0.25 to tell you this)) > Jordan Cheers, -Peter From owner-freebsd-current Wed Jan 31 01:21:54 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id BAA03672 for current-outgoing; Wed, 31 Jan 1996 01:21:54 -0800 (PST) Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id BAA03664 for ; Wed, 31 Jan 1996 01:21:45 -0800 (PST) Received: from sax.sax.de by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id KAA10466; Wed, 31 Jan 1996 10:21:32 +0100 Received: by sax.sax.de (8.6.11/8.6.12-s1) with UUCP id KAA10006; Wed, 31 Jan 1996 10:21:31 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.7.3/8.6.9) id JAA19853; Wed, 31 Jan 1996 09:54:36 +0100 (MET) From: J Wunsch Message-Id: <199601310854.JAA19853@uriah.heep.sax.de> Subject: Re: (fwd) too many cached pages for profiled kernel To: wosch@cs.tu-berlin.de Date: Wed, 31 Jan 1996 09:54:35 +0100 (MET) Cc: graichen@omega.physik.fu-berlin.de, current@FreeBSD.ORG Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199601302101.WAA01244@localhost> from "Wolfram Schneider" at Jan 30, 96 10:01:24 pm X-Phone: +49-351-2012 669 X-Mailer: ELM [version 2.4 PL23] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-current@FreeBSD.ORG Precedence: bulk As Wolfram Schneider wrote: > > Thomas Graichen writes: > >ok - i may change it within the next days if nobody disagrees > > I suggest a new module `machine/m_freebsd21.c' > ^ m_freebsd22.c -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-current Wed Jan 31 01:22:23 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id BAA03712 for current-outgoing; Wed, 31 Jan 1996 01:22:23 -0800 (PST) Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id BAA03679 for ; Wed, 31 Jan 1996 01:21:55 -0800 (PST) Received: from sax.sax.de by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id KAA10488 for ; Wed, 31 Jan 1996 10:21:47 +0100 Received: by sax.sax.de (8.6.11/8.6.12-s1) with UUCP id KAA10010 for freebsd-current@FreeBSD.org; Wed, 31 Jan 1996 10:21:47 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.7.3/8.6.9) id KAA19954 for freebsd-current@FreeBSD.org; Wed, 31 Jan 1996 10:13:42 +0100 (MET) From: J Wunsch Message-Id: <199601310913.KAA19954@uriah.heep.sax.de> Subject: Re: any ideas about this crash? To: freebsd-current@FreeBSD.org (FreeBSD-current users) Date: Wed, 31 Jan 1996 10:13:42 +0100 (MET) Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199601302205.AA04937@Sysiphos> from "Stefan Esser" at Jan 30, 96 11:05:57 pm X-Phone: +49-351-2012 669 X-Mailer: ELM [version 2.4 PL23] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-current@FreeBSD.org Precedence: bulk As Stefan Esser wrote: > > } So where to from here, a BOGOMIPS rating at startup? :-) > > YES! I'm all for it! > > But we always display > TWICE the value Linux > would return X-) :-) But we should give it another name, Bohoomips? :) -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-current Wed Jan 31 01:23:52 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id BAA03931 for current-outgoing; Wed, 31 Jan 1996 01:23:52 -0800 (PST) Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id BAA03728 for ; Wed, 31 Jan 1996 01:22:25 -0800 (PST) Received: from sax.sax.de by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id KAA10458; Wed, 31 Jan 1996 10:21:26 +0100 Received: by sax.sax.de (8.6.11/8.6.12-s1) with UUCP id KAA10002; Wed, 31 Jan 1996 10:21:26 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.7.3/8.6.9) id JAA19837; Wed, 31 Jan 1996 09:53:53 +0100 (MET) From: J Wunsch Message-Id: <199601310853.JAA19837@uriah.heep.sax.de> Subject: Re: proc size mismatch To: ccappuc@satelnet.org (Chris Cappuccio) Date: Wed, 31 Jan 1996 09:53:53 +0100 (MET) Cc: current@freebsd.org Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199601310042.TAA17384@sefl.satelnet.org> from "Chris Cappuccio" at Jan 30, 96 07:42:17 pm X-Phone: +49-351-2012 669 X-Mailer: ELM [version 2.4 PL23] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-current@freebsd.org Precedence: bulk As Chris Cappuccio wrote: > > Anyways, > between 1/16 and 1/23-current ps and w became incompatible with the kernel > (proc size mismatch err something...) and recompiling them does nothing > to help... any fix? if(error == "proc size mismatch") then begin recompile(libkvm); reinstall(libkvm); if((item = find(everywhere)) && linked_static(item, libkvm)) then recompile(item); reinstall(item); end; end. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-current Wed Jan 31 01:24:44 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id BAA04047 for current-outgoing; Wed, 31 Jan 1996 01:24:44 -0800 (PST) Received: from grumble.grondar.za (root@grumble.grondar.za [196.7.18.130]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id BAA04039 for ; Wed, 31 Jan 1996 01:24:25 -0800 (PST) Received: from localhost (mark@localhost [127.0.0.1]) by grumble.grondar.za (8.7.3/8.7.3) with SMTP id LAA04043 for ; Wed, 31 Jan 1996 11:24:00 +0200 (SAT) Message-Id: <199601310924.LAA04043@grumble.grondar.za> X-Authentication-Warning: grumble.grondar.za: Host mark@localhost [127.0.0.1] didn't use HELO protocol To: current@freebsd.org Subject: lsdev woes. Date: Wed, 31 Jan 1996 11:23:59 +0200 From: Mark Murray Sender: owner-current@freebsd.org Precedence: bulk Hi Either I am being inordinately stupid, or there really is a problem. I read the discussions about this a day or two ago, including one that claimed that this was OK "after the 28th". I have a full CVS repository here, and I cannot get lsdev to compile. I have looked at the definition of eisa_device in sys/i386/eisa/eisaconf.h and I must agree that the errors below apply. I have rechecked-out src/sys and src/usr.sbin/lsdev - with no change whatsoever. I get CTM updates continually - and my CVS tree is up-to date minus maybe 6 hours. What gives? bash# make cc -O -I/a/src/usr.sbin/lsdev/../../sys -c /a/src/usr.sbin/lsdev/i386.c /a/src/usr.sbin/lsdev/i386.c: In function `print_eisa': /a/src/usr.sbin/lsdev/i386.c:168: structure has no member named `iobase' /a/src/usr.sbin/lsdev/i386.c:169: structure has no member named `iobase' /a/src/usr.sbin/lsdev/i386.c:169: structure has no member named `iosize' *** Error code 1 Stop. M -- Mark Murray 46 Harvey Rd, Claremont, Cape Town 7700, South Africa +27 21 61-3768 GMT+0200 Finger mark@grondar.za for PGP key From owner-freebsd-current Wed Jan 31 01:54:07 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id BAA06310 for current-outgoing; Wed, 31 Jan 1996 01:54:07 -0800 (PST) Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id BAA06161 for ; Wed, 31 Jan 1996 01:52:30 -0800 (PST) Received: from sax.sax.de by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id KAA11608 for ; Wed, 31 Jan 1996 10:51:24 +0100 Received: by sax.sax.de (8.6.11/8.6.12-s1) with UUCP id KAA10111 for freebsd-current@FreeBSD.org; Wed, 31 Jan 1996 10:51:23 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.7.3/8.6.9) id KAA20195 for freebsd-current@FreeBSD.org; Wed, 31 Jan 1996 10:26:23 +0100 (MET) From: J Wunsch Message-Id: <199601310926.KAA20195@uriah.heep.sax.de> Subject: Re: invalid primary partition table: no magic To: freebsd-current@FreeBSD.org (FreeBSD-current users) Date: Wed, 31 Jan 1996 10:26:22 +0100 (MET) Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199601310338.OAA11342@godzilla.zeta.org.au> from "Bruce Evans" at Jan 31, 96 02:38:58 pm X-Phone: +49-351-2012 669 X-Mailer: ELM [version 2.4 PL23] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-current@FreeBSD.org Precedence: bulk As Bruce Evans wrote: > > >uriah # vnconfig -c /dev/rvn0 fooimage > >uriah # Jan 30 23:51:48 uriah /kernel: vn0: invalid primary partition table: no magic > For emulating physical disks that don't have partition tables or labels, > don't use the `-s labels' option to vnconfig. Well, what about those that are about to get a label the next second? New vn devices are often created by dd'ing the appropriate amount of data out of /dev/zero. And why is it printed in the cited case, with an cd9660 image? I haven't used -s labels. I think it should at least go away for vn devices. Anybody playing with vn is expected to know what (s)he's doing. It's annoying enough with non-bootable physical disks that are dangerously dedicated, but i could perhaps live with that. People in Usenet are often more confused by this message. That's why i would like to have it an option. Any disk without the magic should simply (and silently, unless told otherwise) be considered an unsliced disk. To refine my proposal: use a sysctl-changeable variable, defaulting to "off" unless bootverbose is in effect. This way, we could ask the < 5 % people that experience problems in this area to turn on bootverbose. (All Usenet questions i've seen about this weren't errors, but referred to the bogus message.) -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-current Wed Jan 31 02:22:16 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id CAA08758 for current-outgoing; Wed, 31 Jan 1996 02:22:16 -0800 (PST) Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id CAA08743 for ; Wed, 31 Jan 1996 02:21:55 -0800 (PST) Received: from sax.sax.de by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id LAA12998 for ; Wed, 31 Jan 1996 11:21:26 +0100 Received: by sax.sax.de (8.6.11/8.6.12-s1) with UUCP id LAA10260 for freebsd-current@FreeBSD.org; Wed, 31 Jan 1996 11:21:26 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.7.3/8.6.9) id KAA20566 for freebsd-current@FreeBSD.org; Wed, 31 Jan 1996 10:56:13 +0100 (MET) From: J Wunsch Message-Id: <199601310956.KAA20566@uriah.heep.sax.de> Subject: Re: Optimization topics To: freebsd-current@FreeBSD.org (FreeBSD-current users) Date: Wed, 31 Jan 1996 10:56:13 +0100 (MET) Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199601302034.NAA07203@phaeton.artisoft.com> from "Terry Lambert" at Jan 30, 96 01:34:00 pm X-Phone: +49-351-2012 669 X-Mailer: ELM [version 2.4 PL23] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-current@FreeBSD.org Precedence: bulk As Terry Lambert wrote: > > I want a MIPS port. All unaligned access is to be forbidden, not just > where it may impact performance. Also Motorola 88000. Alas, they ceased to develop this line further. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-current Wed Jan 31 02:37:01 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id CAA09734 for current-outgoing; Wed, 31 Jan 1996 02:37:01 -0800 (PST) Received: from sovcom.kiae.su (sovcom.kiae.su [144.206.136.1]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id CAA09722 for ; Wed, 31 Jan 1996 02:36:37 -0800 (PST) Received: by sovcom.kiae.su id AA03777 (5.65.kiae-1 ); Wed, 31 Jan 1996 13:27:47 +0300 Received: by sovcom.KIAE.su (UUMAIL/2.0); Wed, 31 Jan 96 13:27:47 +0300 Received: (from ache@localhost) by ache.dialup.ru (8.7.3/8.7.3) id NAA00680; Wed, 31 Jan 1996 13:25:53 +0300 (MSK) To: Frank Durda IV Cc: current@freebsd.org References: In-Reply-To: ; from Frank Durda IV at Tue, 30 Jan 96 19:19 WET Message-Id: Organization: Olahm Ha-Yetzirah Date: Wed, 31 Jan 1996 13:25:53 +0300 (MSK) X-Mailer: Mail/@ [v2.42 FreeBSD] From: =?KOI8-R?Q?=E1=CE=C4=D2=C5=CA_=FE=C5=D2=CE=CF=D7?= (aka Andrey A. Chernov, Black Mage) X-Class: Fast Subject: re: ATTENTION to CD driver authors (matcd, scd) Lines: 50 Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org Precedence: bulk In message Frank Durda IV writes: >[0]I found that READTOCENTRYS ioctl completely broken in matcd/scd. >[0]I don't have enough time to fix them and not have those cards to test >[0]the fix. >[0]So, please fix them. >[0]As template you can look at mcd,wcd,cd drivers, here is correct >[0]implementation after my latest commit sequence. >Uh, would you mind saying what you think is wrong? I spent a lot of >time on those ioctls in the matcd driver for 2.1.0, and made them: >(A) EXACTLY match the output that the other drivers were > generating (I checked several out since there were some > disagreements between mcd, wcd, scd, and cd). And, Mcd was broken initially when taken from Linux. Most correct driver was cd, but it can't handle leadout and zero track requests. scd was written from mcd and broken too. wcd was written looking to mcd and cd so was broken too. NetBSD mcd driver is real fresh blood in this stream of brokennes. >(B) EXACTLY match the output that xcdplayer was expecting. And, >(C) EXACTLY match the output that cdplayer was expecting. cdplayer and cdplay was changed to deal with broken ioctl. The history is: cdplay was initially correct, then it was changed to handle our broken driver (by me). cdplayer was written looking into cdplay and was broken too. >Now in the past few days I have noticed changes going through for cdplayer >and other drivers. Are we redefining what is "correct"? Is there >any particular reason, since these ioctls and the apps that used them >*were* working? Existing few apps uses only small subset of what ioctls does, they use this subset because more wide subset is broken differently in different systems. F.e. apps not use LBA mode for this reason. Moreover, even this small subset not works for us, f.e. xcdplayer uses leadout track request which not handled properly with our driver. Now we are at least NetBSD compatible in this ioctl. -- Andrey A. Chernov : And I rest so composedly, /Now, in my bed, ache@astral.msk.su : That any beholder /Might fancy me dead - http://dt.demos.su/~ache : Might start at beholding me, /Thinking me dead. RELCOM Team,FreeBSD Team : E.A.Poe From "For Annie" 1849 From owner-freebsd-current Wed Jan 31 05:03:16 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id FAA26214 for current-outgoing; Wed, 31 Jan 1996 05:03:16 -0800 (PST) Received: from asstdc.scgt.oz.au (root@asstdc.scgt.oz.au [202.14.234.65]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id FAA26208 for ; Wed, 31 Jan 1996 05:03:10 -0800 (PST) Received: (from imb@localhost) by asstdc.scgt.oz.au (8.6.12/BSD4.4) id AAA06084; Thu, 1 Feb 1996 00:02:37 +1100 From: michael butler Message-Id: <199601311302.AAA06084@asstdc.scgt.oz.au> Subject: Re: any ideas about this crash? To: peter@jhome.DIALix.COM (Peter Wemm) Date: Thu, 1 Feb 1996 00:02:36 -73300 (EST) Cc: jkh@time.cdrom.com, current@FreeBSD.org In-Reply-To: <199601310802.QAA07718@jhome.DIALix.COM> from "Peter Wemm" at Jan 31, 96 04:02:09 pm X-Mailer: ELM [version 2.4 PL24beta] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.org Precedence: bulk Peter Wemm writes: > >So where to from here, a BOGOMIPS rating at startup? :-) > I'd agree to a BOGOMIPS rating at bootup, .. > Seriously, bogomips would likely be a pain in the backside if we attempted > to make it comparable to Linux, .. This is precisely why they would have to be "FreeStones" (if that name isn't already "tainted") or some totally and obviously incomparable figure. > (This is just like the users over here in *.au that phone you to complain > that a modem answered the modem call but didn't give them a login: > prompt because the machine was down and "wasted" their $0.25 flag-fall > local call fee. (Just like they've just blown an extra $0.25 to tell you > this)) .. and yet they won't leave a message on an answering machine or with my message service to tell me who it is that I'm supposed to call back .. it's a wierd country this :-) michael From owner-freebsd-current Wed Jan 31 05:43:16 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id FAA28958 for current-outgoing; Wed, 31 Jan 1996 05:43:16 -0800 (PST) Received: from cocoa.ops.neosoft.com (root@cocoa.ops.neosoft.com [206.109.5.227]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id FAA28953 for ; Wed, 31 Jan 1996 05:43:13 -0800 (PST) Received: (from dbaker@localhost) by cocoa.ops.neosoft.com (8.6.12/8.6.12) id HAA05295; Wed, 31 Jan 1996 07:42:31 -0600 Date: Wed, 31 Jan 1996 07:42:30 -0600 (CST) From: Daniel Baker X-Sender: dbaker@cocoa.ops.neosoft.com To: Mark Murray cc: current@freebsd.org Subject: Re: lsdev woes. In-Reply-To: <199601310924.LAA04043@grumble.grondar.za> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org Precedence: bulk I've gotten the same problem here. On Wed, 31 Jan 1996, Mark Murray wrote: > Hi > > Either I am being inordinately stupid, or there really is a problem. > > I read the discussions about this a day or two ago, including one > that claimed that this was OK "after the 28th". I have a full > CVS repository here, and I cannot get lsdev to compile. I have > looked at the definition of eisa_device in sys/i386/eisa/eisaconf.h > and I must agree that the errors below apply. > > I have rechecked-out src/sys and src/usr.sbin/lsdev - with no > change whatsoever. I get CTM updates continually - and my CVS > tree is up-to date minus maybe 6 hours. > > What gives? > > bash# make > cc -O -I/a/src/usr.sbin/lsdev/../../sys -c /a/src/usr.sbin/lsdev/i386.c > /a/src/usr.sbin/lsdev/i386.c: In function `print_eisa': > /a/src/usr.sbin/lsdev/i386.c:168: structure has no member named `iobase' > /a/src/usr.sbin/lsdev/i386.c:169: structure has no member named `iobase' > /a/src/usr.sbin/lsdev/i386.c:169: structure has no member named `iosize' > *** Error code 1 > > Stop. > > M > > -- > Mark Murray > 46 Harvey Rd, Claremont, Cape Town 7700, South Africa > +27 21 61-3768 GMT+0200 > Finger mark@grondar.za for PGP key > -- Daniel Baker - Daniel@Cuckoo.COM "Huhuhu, thank you, drive through please" From owner-freebsd-current Wed Jan 31 06:33:12 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id GAA03836 for current-outgoing; Wed, 31 Jan 1996 06:33:12 -0800 (PST) Received: from jhome.DIALix.COM (root@jhome.DIALix.COM [192.203.228.69]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id GAA03828 for ; Wed, 31 Jan 1996 06:33:07 -0800 (PST) Received: from localhost.DIALix.oz.au (peter@localhost.DIALix.oz.au [127.0.0.1]) by jhome.DIALix.COM (8.7.3/8.7.3) with SMTP id WAA09368; Wed, 31 Jan 1996 22:32:42 +0800 (WST) Message-Id: <199601311432.WAA09368@jhome.DIALix.COM> X-Authentication-Warning: jhome.DIALix.COM: Host peter@localhost.DIALix.oz.au [127.0.0.1] didn't use HELO protocol To: michael butler cc: jkh@time.cdrom.com, current@FreeBSD.org Subject: Re: any ideas about this crash? In-reply-to: Your message of "Thu, 01 Feb 1996 00:02:36." <199601311302.AAA06084@asstdc.scgt.oz.au> Date: Wed, 31 Jan 1996 22:32:42 +0800 From: Peter Wemm Sender: owner-current@FreeBSD.org Precedence: bulk >Peter Wemm writes: >> (This is just like the users over here in *.au that phone you to complain >> that a modem answered the modem call but didn't give them a login: >> prompt because the machine was down and "wasted" their $0.25 flag-fall >> local call fee. (Just like they've just blown an extra $0.25 to tell you >> this)) > > .. and yet they won't leave a message on an answering machine or with my >message service to tell me who it is that I'm supposed to call back .. it's >a wierd country this :-) And then those people will complain "I left three messages on your answering machine/answering service but you didn't call me back!".... .. but this is getting a little off charter for -current.. :-) > michael Cheers, -Peter From owner-freebsd-current Wed Jan 31 08:10:41 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id IAA12362 for current-outgoing; Wed, 31 Jan 1996 08:10:41 -0800 (PST) Received: from localhost.cdrom.com (localhost.cdrom.com [127.0.0.1]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id IAA12352 Wed, 31 Jan 1996 08:10:38 -0800 (PST) Message-Id: <199601311610.IAA12352@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: Host localhost.cdrom.com [127.0.0.1] didn't use HELO protocol To: Mark Murray cc: current@freebsd.org Subject: Re: lsdev woes. In-reply-to: Your message of "Wed, 31 Jan 1996 11:23:59 +0200." <199601310924.LAA04043@grumble.grondar.za> Date: Wed, 31 Jan 1996 08:10:38 -0800 From: "Justin T. Gibbs" Sender: owner-current@freebsd.org Precedence: bulk >Hi > >Either I am being inordinately stupid, or there really is a problem. There really is a problem, I said there was a problem on the lists, and I'm testing the patch right now. >M > >-- >Mark Murray >46 Harvey Rd, Claremont, Cape Town 7700, South Africa >+27 21 61-3768 GMT+0200 >Finger mark@grondar.za for PGP key -- Justin T. Gibbs =========================================== FreeBSD: Turning PCs into workstations =========================================== From owner-freebsd-current Wed Jan 31 08:16:06 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id IAA12762 for current-outgoing; Wed, 31 Jan 1996 08:16:06 -0800 (PST) Received: from grumble.grondar.za (root@grumble.grondar.za [196.7.18.130]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id IAA12688 for ; Wed, 31 Jan 1996 08:16:00 -0800 (PST) Received: from localhost (mark@localhost [127.0.0.1]) by grumble.grondar.za (8.7.3/8.7.3) with SMTP id SAA12074; Wed, 31 Jan 1996 18:15:46 +0200 (SAT) Message-Id: <199601311615.SAA12074@grumble.grondar.za> X-Authentication-Warning: grumble.grondar.za: Host mark@localhost [127.0.0.1] didn't use HELO protocol To: "Justin T. Gibbs" cc: current@freebsd.org Subject: Re: lsdev woes. Date: Wed, 31 Jan 1996 18:15:45 +0200 From: Mark Murray Sender: owner-current@freebsd.org Precedence: bulk "Justin T. Gibbs" wrote: > There really is a problem, I said there was a problem on the lists, and > I'm testing the patch right now. Ooops! Missed that one. I spent this morning grepping the archives... -- Mark Murray 46 Harvey Rd, Claremont, Cape Town 7700, South Africa +27 21 61-3768 GMT+0200 Finger mark@grondar.za for PGP key From owner-freebsd-current Wed Jan 31 10:17:59 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id KAA24004 for current-outgoing; Wed, 31 Jan 1996 10:17:59 -0800 (PST) Received: (from jmb@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id KAA23984 Wed, 31 Jan 1996 10:17:55 -0800 (PST) From: "Jonathan M. Bresler" Message-Id: <199601311817.KAA23984@freefall.freebsd.org> Subject: Re: any ideas about this crash? To: joerg_wunsch@uriah.heep.sax.de Date: Wed, 31 Jan 1996 10:17:54 -0800 (PST) Cc: freebsd-current@FreeBSD.org In-Reply-To: <199601310913.KAA19954@uriah.heep.sax.de> from "J Wunsch" at Jan 31, 96 10:13:42 am X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-current@FreeBSD.org Precedence: bulk > > } So where to from here, a BOGOMIPS rating at startup? :-) > > > > YES! I'm all for it! > > > > But we always display > > TWICE the value Linux > > would return X-) :-) > > But we should give it another name, Bohoomips? > :) > beaucoupMips, :^) From owner-freebsd-current Wed Jan 31 12:27:11 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id MAA07045 for current-outgoing; Wed, 31 Jan 1996 12:27:11 -0800 (PST) Received: from time.cdrom.com (time.cdrom.com [192.216.222.226]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id MAA07034 for ; Wed, 31 Jan 1996 12:27:07 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by time.cdrom.com (8.7.3/8.6.9) with SMTP id MAA29350; Wed, 31 Jan 1996 12:26:39 -0800 (PST) To: Daniel Baker cc: Mark Murray , current@freebsd.org Subject: Re: lsdev woes. In-reply-to: Your message of "Wed, 31 Jan 1996 07:42:30 CST." Date: Wed, 31 Jan 1996 12:26:39 -0800 Message-ID: <29348.823119999@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-current@freebsd.org Precedence: bulk > I've gotten the same problem here. #ifdef it out - it's just a bogus printf that Justin mentioned a few days ago as causing problems. Jordan From owner-freebsd-current Wed Jan 31 13:17:10 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id NAA11586 for current-outgoing; Wed, 31 Jan 1996 13:17:10 -0800 (PST) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id NAA11581 for ; Wed, 31 Jan 1996 13:17:04 -0800 (PST) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id OAA10622; Wed, 31 Jan 1996 14:14:43 -0700 From: Terry Lambert Message-Id: <199601312114.OAA10622@phaeton.artisoft.com> Subject: Re: ps, w To: root@mshslc.k12.mi.us (Rut0fAll3v1l) Date: Wed, 31 Jan 1996 14:14:42 -0700 (MST) Cc: freebsd-current@FreeBSD.org In-Reply-To: <199601301845.SAA01637@mshslc.k12.mi.us> from "Rut0fAll3v1l" at Jan 30, 96 06:45:23 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.org Precedence: bulk RutOfAll3vll writes: > I got the 960116 snapshot from freedffall  > bah freefall...Anyways I needed some kernel sources to kmake > a new kernel so i got current as of jan 23. ps an d w broke > after that so i got current ps/w and they are still broken. I now > have a jan 30 kernel source tree which i haven't yet booted under > cuz i'm gettin irq/drq values for my soundblaster equipment which > i will put in the config file later.. but tha's not relavent.. > ps and w complain about the chunk size and so forth.. Dear Rut: 1) This is the wrong list for this. 2) When the proc structure changes, things which rely on the proc structure must be rebuilt (like devfs). 3) When things that rely on the proc structure are changed (like devfs), things that rely on them (like ps and w) must be rebuilt. 4) Same goes for routing code or any other kernel/user interface not mandated by POSIX and generally hidden in ioctl()'s (like routing) or under library interfaces (in which case the libraries need to be rebuilt, and the application using them statically need to be rebuilt). Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-current Wed Jan 31 13:55:58 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id NAA15226 for current-outgoing; Wed, 31 Jan 1996 13:55:58 -0800 (PST) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id NAA15217 for ; Wed, 31 Jan 1996 13:55:55 -0800 (PST) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id OAA10765; Wed, 31 Jan 1996 14:52:43 -0700 From: Terry Lambert Message-Id: <199601312152.OAA10765@phaeton.artisoft.com> Subject: Re: invalid primary partition table: no magic To: bde@zeta.org.au (Bruce Evans) Date: Wed, 31 Jan 1996 14:52:43 -0700 (MST) Cc: freebsd-current@FreeBSD.org, j@uriah.heep.sax.de In-Reply-To: <199601310338.OAA11342@godzilla.zeta.org.au> from "Bruce Evans" at Jan 31, 96 02:38:58 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.org Precedence: bulk > >uriah # vnconfig -c /dev/rvn0 fooimage > >uriah # Jan 30 23:51:48 uriah /kernel: vn0: invalid primary partition table: no magic > > >It's starting to get annoying. Not only that any /dev/zero-created > >empty file that we are about to disklabel during the release process > >causes this bogus warning (until it's disklabeled -B), but fooimage > >above was an cd9660 image, so the warning is not of much use. > > >Since the warning is not of interest for ``ordinary people'' anyway, > >i'd vote for hiding it behind some debugging option (perhaps enabled > >via sysconfig). > > It is an error for disks that should have a partition table, but > since there is no way of telling which disks those are, it is hard > to tell when to suppress the warning. > > For emulating physical disks that don't have partition tables or labels, > don't use the `-s labels' option to vnconfig. I think this falls into the category of the "how do I attach a label" problems, which in turn fall into the "why is a label expected" problems. I think the magic here is to allow devfs ioctl()'s to specify logical device manager controls to instantiate management in the first place. This provides a general soloution for integrating an existing OS's arbitrary logical partitioning, media perfection, and volume spanning with only minor changes to the BSD code. This sounds kind of weird unless you've seen some of the discussions of devfs based logical device management that I've had with Julian (and a couple of other people who've asked about fixing DOSFS device tromping, adding VFAT long name support, or supporting NTFS). Here is one excerpt of a system configuration followed by a devfs based logical device registration process. The idea of "how to handle a new disk" follows the excerpted material: ============================================================================= Consider the following: There exists two SCSI and one IDE controllers such that: o SCSI controller 0 has a 1G disk such that: o DOS partition table o 500M VFAT partition o 500M BSD partition shuch that: o 100M / o 32M swap o 120M /var o 248M /usr o SCSI controller 0 has a CDROM o SCSI controller 1 has a 500M disk such that: o DOS partition table o 200M DOS partition o 300M Extended DOS partition such that: o 80M DOS Partition o 188M Linux EXT2FS Partition o 32M Linux Swap Partition o IDE controller 0 has a 500M disk such that: o DOS Partition table o 250M VFAT Partition o 250M Extended DOS partition such that: o 250M VFAT Partition Each one of these items needs to be accessable. SCO (SCSI controller 0) registers: creates /dev/dsk/sc0 SC0 probes a physical device 0: creates /dev/dsk/sc0/t0u0 SCO registers device. Logical driver "DOS partitioning" => claims device creates /dev/dsk/sc0/t0u0/p0 creates /dev/dsk/sc0/t0u0/p1 => registers /dev/dsk/sc0/t0u0/p0 (no claimant *) => registers /dev/dsk/sc0/t0u0/p1 Logical driver "BSD slices" => claims device creates /dev/dsk/sc0/t0u0/p1/s0 creates /dev/dsk/sc0/t0u0/p1/s1 creates /dev/dsk/sc0/t0u0/p1/s2 creates /dev/dsk/sc0/t0u0/p1/s3 => registers /dev/dsk/sc0/t0u0/p1/s0 (no claimant *) => registers /dev/dsk/sc0/t0u0/p1/s1 (no claimant *) => registers /dev/dsk/sc0/t0u0/p1/s2 (no claimant *) => registers /dev/dsk/sc0/t0u0/p1/s3 (no claimant *) SCO probes a physical device 3: creates /dev/dsk/sc0/t3u0 SCO registers device (no claimant *) SC1 (SCSI controller 1) registers: creates /dev/dsk/sc1 SC1 probes a physical device 1: creates /dev/dsk/sc1/t1u0 Logical driver "DOS partitioning" => claims device creates /dev/dsk/sc1/t1u0/p0 creates /dev/dsk/sc1/t1u0/p1 => registers /dev/dsk/sc1/t1u0/p0 (no claimant *) => registers /dev/dsk/sc1/t1u0/p1 Logical driver "DOS extended partitioning" => claims device creates /dev/dsk/sc1/t1u0/p1/e0 creates /dev/dsk/sc1/t1u0/p1/e1 creates /dev/dsk/sc1/t1u0/p1/e2 => registers /dev/dsk/sc1/t1u0/p1/e0 (no claimant *) => registers /dev/dsk/sc1/t1u0/p1/e1 (no claimant *) => registers /dev/dsk/sc1/t1u0/p1/e2 (no claimant *) WC0 (IDE controller 0) registers: creates /dev/dsk/wc0 WCO probes a physical device 0: creates /dev/dsk/wc0/t0 Logical driver "DOS partitioning" => claims device creates /dev/dsk/wc0/t0/p0 creates /dev/dsk/wc0/t0/p1 => registers /dev/dsk/wc0/t0/p0 (no claimant *) => registers /dev/dsk/wc0/t0/p1 Logical driver "DOS extended partitioning" => claims device creates /dev/dsk/wc0/t0/p1/e0 => registers /dev/dsk/wc0/t0/p1/e0 (no claimant *) Each logical device has a physical device a start sector, and a length, at a bare minimum. Some logical devices substitute a pseudo-device for the physical device, and the pseudo device performs operations on the real physical device on the requesters behalf. Like bad sector mapping, or 64 sector ofsetting for OnTrack DiskManager 6.x or 7.x (neither shown in the above example). As long as we realize that directories are accessed via getdents and files via read/write, we can still treat the devices as raw devices even though they show up as directory vnodes. That means we don't need /dev/dsk/wc0, /dev/dsk/wc0/t0, and /dev/wc0/t0/p0 to be seperate devices to let us access the controller, the first raw disk (including partition table), or the VFAT partition, erspectively. We can use the directories as devices. Because we get range restriction guarantees, FS events in the kernel on the /dev/wc0/t0/p0 devie can't screw up the contents of any other slice, period. No matter what bad calculations the MSDOSFS makes. So now we have the device/slice mess straightened out. (*) One thing we may want to consider is that the "no claimant" cases above are nearly the perfect mechanism to cause a callback to the VFS code to ask each VFS if it want to "claim" a device -- causing it to be mounted. On the VFATFS itself (I'd prefer long name semantics if allowable, so I'm calling it that instead of MSDOSFS), one of the first things to consider is that long name storage is in Unicode. The impact of either supporting Unicode at the user interface level, or of integrating a file systems that can support Unicode at a lower level is a big one. The largest impact is in path parsing. The first step to allowing Unicode and non-Unicode semantics to exist (for both VFATFS and NTFS uniformity) is to move the path parsing buffer manipulation code up above the VFS layer. In the current BSD, the path buffer is freed on a per FS basis, which is really quite broken if the buffer can be dimorphic for char and wchar_t values (which it must be for the 16 bit Unicode storage model used in VFAT, since short names are stored as DOS ASCII: code page 435). This implies that both Unicode and non-Unicode path components may be simultaneously required by an underlying FS. Because we must consider more than one Unicode FS to exist below the VFS layer, we must create the path dimorphism support above the VFS itself (in what is typically called the "vncalls" layer in an SVR4 system). [ ... ] ============================================================================= OK. Now we add a disk, ID 1, to SC0. This adds: SC0 probes a physical device 1: creates /dev/dsk/sc0/t1u0 SCO registers device (no claimant *) Note: This may be the result of a hot plug of a SCSI device followed by a callback to a configuration manager to trigger notification of "device arrival". The same thing applies to CDROM's, 3.5" floppies, ZIP drives, PCMCIA flash RAM, etc. -- anything that actually *has* a notification mechanism. A user program for "reprobe" or explicit notificaton of the configuration manager can be provided for pluggable devices without a notification mechanism. Finally, notification of a user space daemon can be used to trigger Windows96-like "autorun" behaviour on CROM and similar media for easy upgrade from standard distribution media. The user wants to partition the device, and starts a logical partitioning tool. This tool does the following: 1) IOCTL's the /dev/dsk/sc0/t1u0 device to get a list of applicable logical device drivers which may be applied to the device. 2) Presents a picklist to the caller. This might resemble: a) Add media perfection and rexeport same device b) Add DOS partitioning and export partition devices c) Add BSD partitioning and export partition devices d) Insert this device in a volume spanning set 3) Based on an identifier returned with the logical device and a device class descriptor, allow the users to perform operations applicable to that logical device. One of these operations is instantiating one of the drivers. This takes the place of raw disk I/O for partitioning, etc.. 4) Save and Exit. Device reregistration is triggered on close and export proceeds normally. Note that the tool in this instance is data-driven from the registered logical devices and the class designation that comes from the controller target identification on a per driver basis (ie: you aren't allowed to partition CDROM's, for instance). For a vnconfiged device, a device /dev/dsk/vn0 is exported in the DEVFS name space. It may be acted upon normally. Because the "hosted device" bit is set, DOS partitioning is not offered. If the hosted drive already has a media perfection layer present (ie: bad144), then media perfection is not offered. A newly exported /dev/dsk/vn0 will not have a claimant unless it is a reexport of an "existing" device (a vnconfig of a previously vnconfiged device). Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-current Wed Jan 31 15:32:55 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id PAA24170 for current-outgoing; Wed, 31 Jan 1996 15:32:55 -0800 (PST) Received: from cocoa.ops.neosoft.com (root@cocoa.ops.neosoft.com [206.109.5.227]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id PAA24148 Wed, 31 Jan 1996 15:32:46 -0800 (PST) Received: (from dbaker@localhost) by cocoa.ops.neosoft.com (8.6.12/8.6.12) id RAA09984; Wed, 31 Jan 1996 17:32:29 -0600 Date: Wed, 31 Jan 1996 17:32:28 -0600 (CST) From: Daniel Baker X-Sender: dbaker@cocoa.ops.neosoft.com To: freebsd-questions@freebsd.org, freebsd-current@freebsd.org Subject: compiling current kernel Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org Precedence: bulk I have finished makeworld and am trying to make a -current kernel, but I get this message: cocoa# config COCOA Removing old directory ../../compile/COCOA: Done. Unknown % construct in generic makefile: %SFILES Kernel build directory is ../../compile/COCOA cocoa# when I go to /sys/compile/COCOA almost all of the files are from 14 - 16 bytes any ideas? Daniel -- Daniel Baker - Daniel@Cuckoo.COM "Huhuhu, thank you, drive through please" From owner-freebsd-current Wed Jan 31 15:37:57 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id PAA24648 for current-outgoing; Wed, 31 Jan 1996 15:37:57 -0800 (PST) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id PAA24608 for ; Wed, 31 Jan 1996 15:37:36 -0800 (PST) Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.9/8.6.9) id KAA29774; Thu, 1 Feb 1996 10:35:55 +1100 Date: Thu, 1 Feb 1996 10:35:55 +1100 From: Bruce Evans Message-Id: <199601312335.KAA29774@godzilla.zeta.org.au> To: freebsd-current@FreeBSD.ORG, j@uriah.heep.sax.de Subject: Re: invalid primary partition table: no magic Sender: owner-current@FreeBSD.ORG Precedence: bulk >> >uriah # vnconfig -c /dev/rvn0 fooimage >> >uriah # Jan 30 23:51:48 uriah /kernel: vn0: invalid primary partition table: no magic >> For emulating physical disks that don't have partition tables or labels, >> don't use the `-s labels' option to vnconfig. >Well, what about those that are about to get a label the next second? >New vn devices are often created by dd'ing the appropriate amount of >data out of /dev/zero. You can ignore the problem or dd an MBR or dd just an 0xAA55 signature. >And why is it printed in the cited case, with an cd9660 image? I >haven't used -s labels. Because -s labels was set previously. I think all the options have to live across opens so that they don't go away after you have vnconfig'ed them, but perhaps they should go away when the device is unconfigured. >I think it should at least go away for vn devices. Anybody playing >with vn is expected to know what (s)he's doing. It's annoying enough That's right, they are expected to know enough to ignore the problem or to use a binary editor to avoid it :-). I get it all the time for floppies and have been ignoring it. Bruce From owner-freebsd-current Wed Jan 31 16:40:43 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id QAA29265 for current-outgoing; Wed, 31 Jan 1996 16:40:43 -0800 (PST) Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id QAA29225 for ; Wed, 31 Jan 1996 16:40:27 -0800 (PST) Received: from sax.sax.de by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id BAA12137 for ; Thu, 1 Feb 1996 01:39:48 +0100 Received: by sax.sax.de (8.6.11/8.6.12-s1) with UUCP id BAA24312 for freebsd-current@FreeBSD.org; Thu, 1 Feb 1996 01:39:47 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.7.3/8.6.9) id BAA23762 for freebsd-current@FreeBSD.org; Thu, 1 Feb 1996 01:35:25 +0100 (MET) From: J Wunsch Message-Id: <199602010035.BAA23762@uriah.heep.sax.de> Subject: Re: invalid primary partition table: no magic To: freebsd-current@FreeBSD.org (FreeBSD-current users) Date: Thu, 1 Feb 1996 01:35:24 +0100 (MET) Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199601312335.KAA29774@godzilla.zeta.org.au> from "Bruce Evans" at Feb 1, 96 10:35:55 am X-Phone: +49-351-2012 669 X-Mailer: ELM [version 2.4 PL23] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-current@FreeBSD.org Precedence: bulk As Bruce Evans wrote: > > >Well, what about those that are about to get a label the next second? > >New vn devices are often created by dd'ing the appropriate amount of > >data out of /dev/zero. > > You can ignore the problem or dd an MBR or dd just an 0xAA55 signature. Hmm, but the first access does always cause this message. > >And why is it printed in the cited case, with an cd9660 image? I > >haven't used -s labels. > > Because -s labels was set previously. I think all the options have to Possible, but i don't remember. Perhaps i did a `make release' once. > live across opens so that they don't go away after you have vnconfig'ed > them, but perhaps they should go away when the device is unconfigured. It should, yes. > >I think it should at least go away for vn devices. > That's right, they are expected to know enough to ignore the problem > or to use a binary editor to avoid it :-). I get it all the time > for floppies and have been ignoring it. :-) (Run a ``make release''. The doFS.sh tries to optimize the file system usage. Be as nitpicking as i am about kernel messages, so i'm getting all of them logged onto any xterms where i'm logged in. Now you know why i'm complaining... :) -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-current Wed Jan 31 18:50:40 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id SAA12117 for current-outgoing; Wed, 31 Jan 1996 18:50:40 -0800 (PST) Received: from marble.eps.nagoya-u.ac.jp (marble.eps.nagoya-u.ac.jp [133.6.57.68]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id SAA12110 for ; Wed, 31 Jan 1996 18:50:37 -0800 (PST) Received: from marble.eps.nagoya-u.ac.jp (localhost [127.0.0.1]) by marble.eps.nagoya-u.ac.jp (8.7.3+2.6Wbeta5/3.3W9) with ESMTP id LAA00929 for ; Mon, 1 Jan 1996 11:50:21 +0900 (JST) Message-Id: <199601010250.LAA00929@marble.eps.nagoya-u.ac.jp> To: current@freebsd.org Subject: TSS broken X-Mailer: Mew beta version 0.96 on Emacs 19.28.1, Mule 2.3 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Date: Mon, 01 Jan 1996 11:50:18 +0900 From: KATO Takenori Sender: owner-current@freebsd.org Precedence: bulk In recent change of sys/i386/i386/swtch.s, the code movl %esp,PCB_ESP(%ecx) is changed into leal 4(%esp),%eax movl %eax,PCB_ESP(%ecx) (in savectx). After this operation, the member tss_esp points not user stack pointer, but the address of TSS. This may causes panic when swapper is activated. ---- KATO Takenori Dept. Earth Planet. Sci., Nagoya Univ., Nagoya 464-01 Voice: +81-52-789-2529 Fax: +81-52-789-3033 From owner-freebsd-current Wed Jan 31 18:59:53 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id SAA13231 for current-outgoing; Wed, 31 Jan 1996 18:59:53 -0800 (PST) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id SAA12944 Wed, 31 Jan 1996 18:57:39 -0800 (PST) Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.9/8.6.9) id NAA06197; Thu, 1 Feb 1996 13:56:26 +1100 Date: Thu, 1 Feb 1996 13:56:26 +1100 From: Bruce Evans Message-Id: <199602010256.NAA06197@godzilla.zeta.org.au> To: current@freebsd.org, dyson@freebsd.org Subject: new pipes fail several tests #4 Sender: owner-current@freebsd.org Precedence: bulk The fix for #3 seems to work. Thanks. New pipes don't honor the O_NONBLOCK flag or _POSIX_PIPE_MAX or PIPE_MAX. sys_pipe.c doesn't even reference these values. This test demonstrates that non-blocking writes block and that atomic writes may be non-atomic. PIPESIZE can be determined in a machine-independent way by nonblock-writing a byte at a time until the pipe fills up, but this can't be used here because the writes would block. PIPE_MAX can be checked automatically iff nonblocking writes work. Old pipes have several bugs involving PIPE_MAX: 1. PIPE_MAX is defined in , so if you fix it or change it, all binaries that depend on it must be recompiled. 2. PIPE_MAX is identical with _POSIX_PIPE_MAX (512). It is actually kinda sorta identical with MCLBYTES (2048). 3. MCLBYTES > _POSIX_PIPE_MAX is not enforced. 3. The corresponding socket semantics are a little different. Nonblocking that don't fit work correctly when <= MCLBYTES is written (-1/EAGAIN is returned) buy sometimes fail when > MCLBYTES is written (-1/EAGAIN is sometimes returned instead of writing what fits). PIPE_MAX should be a significant fraction of PIPESIZE in the new implementation. I think Linux uses 4095 for PIPE_MAX and 4096 for PIPESIZE. The non-power of 2 is probably not so good - processes wanting to do atomic writes to pipes should write PIPE_MAX bytes at a time and this will cause extra blocking overhead. Bruce #include #include #include #include #include #include #include #include #include #define check(what, expected) assert((what, expected)) #define NONBLOCKING 0 /* option */ #define USE_NAMED_PIPE_P 0 /* option */ #if USE_NAMED_PIPE_P #define PIPESIZE 8192 #else #define PIPESIZE 16384 #endif sig_atomic_t caught; static void catch(int s) { caught = 1; } int main(void) { char buf[_POSIX_PIPE_BUF]; int fd[2]; size_t nw; int r; long tot; #if USE_NAMED_PIPE_P fd[0] = open("p", O_RDONLY | O_NONBLOCK); check("open", fd[0] != -1); r = fcntl(fd[0], F_SETFL, O_RDONLY); check("fcntl", r == 0); fd[1] = open("p", O_WRONLY | O_NONBLOCK); check("open", fd[1] != -1); r = fcntl(fd[1], F_SETFL, O_WRONLY); check("fcntl", r == 0); #else r = pipe(fd); check("pipe", r == 0); #endif #if NONBLOCKING r = fcntl(fd[1], F_SETFL, O_NONBLOCK); check("fcntl", r == 0); #endif /* * Fill up the pipe except for a little less than _POSIX_PIPE_BUF * bytes so that the next write of _POSIX_PIPE_BUF bytes (only) * partly fits. */ for (tot = 0; tot + sizeof buf <= PIPESIZE;) { nw = (tot + sizeof buf == PIPESIZE) ? 1 : sizeof buf; r = write(fd[1], buf, nw); if (r != -1) tot += r; fprintf(stderr, "write returned %d, tot = %ld\n", r, tot); check("write", r == nw); } check("almost filled", tot < PIPESIZE && tot + sizeof buf > PIPESIZE); /* Trap failures. */ check("siginterrupt", siginterrupt(SIGALRM, 1) == 0); check("signal", signal(SIGALRM, catch) != SIG_ERR); alarm(2); /* * Now we should be able to write at least _POSIX_PIPE_BUF bytes * atomically (or PIPE_BUF bytes, or fpathconf(fd[1], _PC_PIPE_BUF) * bytes, but those are bogusly the same as _POSIX_PIPE_BUF under * FreeBSD). */ r = write(fd[1], buf, sizeof buf); alarm(0); fprintf(stderr, "wrote %d bytes, errno = %d, caught = %d\n", r, errno , caught); #if NONBLOCKING /* Should have returned immediately without writing anything. */ check("write", r == -1); check("write", errno == EAGAIN); check("write", caught == 0); #else /* Should have returned after the alarm without writing anything. */ check("write", r == -1); check("write", errno == EINTR); check("write", caught == 1); #endif return 0; } From owner-freebsd-current Wed Jan 31 20:34:02 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id UAA20923 for current-outgoing; Wed, 31 Jan 1996 20:34:02 -0800 (PST) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id UAA20871 for ; Wed, 31 Jan 1996 20:32:51 -0800 (PST) Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.9/8.6.9) id PAA10717; Thu, 1 Feb 1996 15:28:51 +1100 Date: Thu, 1 Feb 1996 15:28:51 +1100 From: Bruce Evans Message-Id: <199602010428.PAA10717@godzilla.zeta.org.au> To: freebsd-current@freebsd.org, j@uriah.heep.sax.de Subject: Re: invalid primary partition table: no magic Sender: owner-current@freebsd.org Precedence: bulk >> >Well, what about those that are about to get a label the next second? >> >New vn devices are often created by dd'ing the appropriate amount of >> >data out of /dev/zero. >> >> You can ignore the problem or dd an MBR or dd just an 0xAA55 signature. >Hmm, but the first access does always cause this message. You can edit the file before vnconfig'ing it. You can also run fdisk -u on the file to partition it. This is a good way to learn how to use fdisk (start with an MBR with random garbage on it and fix it). >> That's right, they are expected to know enough to ignore the problem >> or to use a binary editor to avoid it :-). I get it all the time >> for floppies and have been ignoring it. >:-) >(Run a ``make release''. The doFS.sh tries to optimize the file >system usage. Be as nitpicking as i am about kernel messages, so i'm >getting all of them logged onto any xterms where i'm logged in. Now >you know why i'm complaining... :) Complain to the author of doFS.sh :-). Bruce From owner-freebsd-current Wed Jan 31 23:29:43 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id XAA01618 for current-outgoing; Wed, 31 Jan 1996 23:29:43 -0800 (PST) Received: from tanelorn.netural.com (root@tanelorn.NETural.com [206.54.248.5]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id XAA01613 for ; Wed, 31 Jan 1996 23:29:41 -0800 (PST) Received: (from thekind@localhost) by tanelorn.netural.com (8.6.12/8.6.12) id BAA00246; Thu, 1 Feb 1996 01:29:40 -0600 Date: Thu, 1 Feb 1996 01:29:40 -0600 (CST) From: "Adam W. Dace" To: freebsd-current@freebsd.org Subject: bind() Security Problems (fwd) Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org Precedence: bulk I don't know if any of you are on the linux-security mailing list, but you might wanna hop on if you aren't...some interesting, yet obscure exploits come from there...maybe a fix is in order? ---------- Forwarded message ---------- Date: Tue, 30 Jan 1996 15:18:21 -0800 (PST) From: Aleph's K-Rad GECOS Field To: linux-security@tarsier.cv.nrao.edu Cc: linux-alert@tarsier.cv.nrao.edu, bugtraq@crimelab.com, best-of-security@suburbia.net Subject: bind() Security Problems System Call: bind() Affected Operating System: Linux, SunOS, FreeBSD, BSDI, Ultrix Probably others. Requirement: account on system. Security Compromise: Stealing packets from nfsd, yppasswd, ircd, etc. Credits: *Hobbit* bitblt Aleph One Synopsis: bind() does not properly check to make sure there is not a socket already bound to INADDR_ANY on the same port when binding to a specific address. On most systems, a combination of setting the SO_REUSEADDR socket option, and a call to bind() allows any process to bind to a port to which a previous process has bound width INADDR_ANY. This allows a user to bind to the specific address of a server bound to INADDR_ANY on an unprivileged port, and steal its udp packets/tcp connection. Exploit: Download and compile netcat from ftp://ftp.avian.org/src/hacks/nc100.tgz Make sure an nfs server is running: w00p% netstat -a | grep 2049 udp 0 0 *.2049 *.* LISTEN Run netcat: w00p% nc -v -v -u -s 192.88.209.5 -p 2049 listening on [192.88.209.5] 2049 ... Wait for packets to arrive. Fix: Linux: A patch was been sent to Linus and Alan Cox. It should be included with 1.3.60. My original patch (included bellow) allows for binds from the same uid, as some virtual hosting software like modified httpds, and ftpds, may break otherwise. Alan didnt like this, so all bind to the same port will not be allowed in newer kernels. You should be able to easily adapt this patch or Alan's patch to 1.2.13 without much trouble. Others: Pray to your vendors. --- begin patch --- diff -u --recursive --new-file linux-1.3.57/net/ipv4/af_inet.c linux/net/ipv4/af_inet.c --- linux-1.3.57/net/ipv4/af_inet.c Mon Dec 25 20:03:01 1995 +++ linux/net/ipv4/af_inet.c Tue Jan 16 19:46:28 1996 @@ -46,6 +46,8 @@ * Germano Caronni : Assorted small races. * Alan Cox : sendmsg/recvmsg basic support. * Alan Cox : Only sendmsg/recvmsg now supported. + * Aleph One : Rogue processes could steal packets + * from processes bound to INADDR_ANY. * * This program is free software; you can redistribute it and/or * modify it under the terms of the GNU General Public License @@ -899,6 +901,12 @@ if (sk2->num != snum) continue; /* more than one */ + if ((sk2->rcv_saddr == 0 || sk->rcv_saddr == 0) && + current->euid != sk2->socket->inode->i_uid) + { + sti(); + return(-EADDRINUSE); + } if (sk2->rcv_saddr != sk->rcv_saddr) continue; /* socket per slot ! -FB */ if (!sk2->reuse || sk2->state==TCP_LISTEN) Aleph One / aleph1@underground.org http://underground.org/ KeyID 1024/948FD6B5 Fingerprint EE C9 E8 AA CB AF 09 61 8C 39 EA 47 A8 6A B8 01 From owner-freebsd-current Thu Feb 1 00:22:12 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id AAA05654 for current-outgoing; Thu, 1 Feb 1996 00:22:12 -0800 (PST) Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id AAA05614 Thu, 1 Feb 1996 00:21:54 -0800 (PST) Received: from sax.sax.de by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id JAA28203; Thu, 1 Feb 1996 09:21:39 +0100 Received: by sax.sax.de (8.6.11/8.6.12-s1) with UUCP id JAA27399; Thu, 1 Feb 1996 09:21:38 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.7.3/8.6.9) id JAA25852; Thu, 1 Feb 1996 09:06:42 +0100 (MET) From: J Wunsch Message-Id: <199602010806.JAA25852@uriah.heep.sax.de> Subject: Re: compiling current kernel To: dbaker@cocoa.ops.neosoft.com (Daniel Baker) Date: Thu, 1 Feb 1996 09:06:41 +0100 (MET) Cc: freebsd-questions@freebsd.org, freebsd-current@freebsd.org Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: from "Daniel Baker" at Jan 31, 96 05:32:28 pm X-Phone: +49-351-2012 669 X-Mailer: ELM [version 2.4 PL23] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-current@freebsd.org Precedence: bulk As Daniel Baker wrote: > > I have finished makeworld and am trying to make a -current kernel, but > I get this message: > > cocoa# config COCOA > Removing old directory ../../compile/COCOA: Done. > Unknown % construct in generic makefile: %SFILES When running -current, update your config(8) properly. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-current Thu Feb 1 00:32:57 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id AAA06443 for current-outgoing; Thu, 1 Feb 1996 00:32:57 -0800 (PST) Received: from ref.tfs.com (ref.tfs.com [140.145.254.251]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id AAA06434 for ; Thu, 1 Feb 1996 00:32:55 -0800 (PST) Received: (from julian@localhost) by ref.tfs.com (8.6.12/8.6.9) id RAA11946; Wed, 31 Jan 1996 17:02:56 -0800 From: Julian Elischer Message-Id: <199602010102.RAA11946@ref.tfs.com> Subject: Re: invalid primary partition table: no magic To: terry@lambert.org (Terry Lambert) Date: Wed, 31 Jan 1996 17:02:55 +73600 (PST) Cc: bde@zeta.org.au, freebsd-current@freebsd.org, j@uriah.heep.sax.de In-Reply-To: <199601312152.OAA10765@phaeton.artisoft.com> from "Terry Lambert" at Jan 31, 96 02:52:43 pm X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-current@freebsd.org Precedence: bulk Terry, will you stop stealing my ideas? :) I have code for some of this written Peter and I went over it in Perth a few weeks ago.. I think it basically impliments exactly what you are talking about here.. there are a few problems however.... consider a BSD partition put at the beginning of a disk.. at the beginning of the disk we therefore have a fdisk slice AND and disklabel slice... which gets to claim the disk? :) Possibly the fdisk-slice probe() method knows that if a BSD subslice starts at 0 then to NOT grab control :) > > Each logical device has a physical device a start sector, and a length, > at a bare minimum. Some logical devices substitute a pseudo-device for > the physical device, and the pseudo device performs operations on the > real physical device on the requesters behalf. Like bad sector mapping, > or 64 sector ofsetting for OnTrack DiskManager 6.x or 7.x (neither shown > in the above example). > > As long as we realize that directories are accessed via getdents and > files via read/write, we can still treat the devices as raw devices > even though they show up as directory vnodes. That means we don't > need /dev/dsk/wc0, /dev/dsk/wc0/t0, and /dev/wc0/t0/p0 to be seperate > devices to let us access the controller, the first raw disk (including > partition table), or the VFAT partition, erspectively. We can use > the directories as devices. > > Because we get range restriction guarantees, FS events in the kernel > on the /dev/wc0/t0/p0 devie can't screw up the contents of any other > slice, period. No matter what bad calculations the MSDOSFS makes. I THINK we might have that now anyhow.. My guess our problem isn't just disk overshoots. > > > So now we have the device/slice mess straightened out. > > (*) One thing we may want to consider is that the "no claimant" cases > above are nearly the perfect mechanism to cause a callback to the > VFS code to ask each VFS if it want to "claim" a device -- causing > it to be mounted. I don't know about that.. we don't know where to mount it.. such leaf nodes however would probably be given some sort of descriptive name however, describing what they are... The way I've been looking at it is that there are many stackable "disk-like object" drivers that have a bunch of methods. The default method is to simply supply an offset and the handle to the next layer down, however there are at LEAST the following methods available: probe attach doIO <------ These two are really mutually exlusive offset <------ This is a special case of doIO for common simple cases parent <------ not used for such things as CCD drivers so that if type.diIO is NULL then you simply add type.offset and switch to type.parent, which might in turn have a doIO or offset.. etc. eventually you hit the methods that were expoerted by the physical device driver. Devices always have a doIO method. basically 1) when you register a new 'disk-like' object, the 'disk-object' handler creates a DEVFS entry for it and calls the 'probe' method of all known types until one says "I can handle this". 2) the new method is 'stacked' and it's 'attach' method is called. 3) The attach method will 'register' any sub-partitions it finds, (goto 1 for ewach such sub partition) 4) Any sub partition that doesn't have a 'claiment' still has it's devfs entry which becomes the only source of actions. Notes: A 'type' might be a CCD driver, which recognises a label saying "part 4 of a 5 part volume" Every time you register a new 'disk-like' device, a 'structure is allocated, and the 'next' ID is incremented. an entry is put into a hash table so that that structure can be easily located, given that ID number. The ID number is the minor number.. This means that there is no encoding of bits in minor numbers. It also means that minors might be differnt each time you boot (that's why devfs).. The whole thind hangs off a NEW major number and might be done in parallel witht eh existing system for a while.. All disk-like parts form all devices would have the same major number but would have differnt names under devfs and would have different minors (allocated sequentially). There would be methods to allow a 'disk-like' part to subdivide itself assuming all existing parts were closed. I haven't done or worked out this bit yet, though it might be enough to allow each method to 'spy' on writes so that they can figure out when a new partition table (or whatever) is being written. Interestingly enough, when Peter and I did a white-board session over this we decided that there were really two classes of methods. Those called by a layer to act on it's own subdivisions and those which acted on the larger (parent?) "device". Because probing can be tricky I plan on passing 'context' hints at probe time so that various probe routines are not working totally in the dark as to what happenned before.. (e.g. finding a fdisk slice within an fdisk slice is legal but should be treated differently (I think block numbers are not absolute in extended partitions .. needs confirmation). Writing a new disk driver get's to be really simple.. write basic IO routines, register a disk-like device.. stand back and await work.. +----------------------------------+ ______ _ __ | __--_|\ Julian Elischer | \ U \/ / On assignment | / \ julian@ref.tfs.com +------>x USA \ in a very strange | ( OZ ) 300 lakeside Dr. oakland CA. \___ ___ | country ! +- X_.---._/ USA+(510) 645-3137(wk) \_/ \\ v From owner-freebsd-current Thu Feb 1 00:47:46 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id AAA07227 for current-outgoing; Thu, 1 Feb 1996 00:47:46 -0800 (PST) Received: from sequent.kiae.su (sequent.kiae.su [144.206.136.6]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id AAA07218 for ; Thu, 1 Feb 1996 00:47:29 -0800 (PST) Received: by sequent.kiae.su id AA12526 (5.65.kiae-2 ); Thu, 1 Feb 1996 11:46:20 +0300 Received: by sequent.KIAE.su (UUMAIL/2.0); Thu, 1 Feb 96 11:46:20 +0300 Received: (from ache@localhost) by ache.dialup.ru (8.7.3/8.7.3) id LAA01787; Thu, 1 Feb 1996 11:17:59 +0300 (MSK) To: Frank Durda IV Cc: current@freebsd.org References: In-Reply-To: ; from =?KOI8-R?Q?=E1=CE=C4=D2=C5=CA_=FE=C5=D2=CE=CF=D7?= at Wed, 31 Jan 1996 13:25:53 +0300 (MSK) Message-Id: Organization: Olahm Ha-Yetzirah Date: Thu, 1 Feb 1996 11:17:59 +0300 (MSK) X-Mailer: Mail/@ [v2.42 FreeBSD] From: =?KOI8-R?Q?=E1=CE=C4=D2=C5=CA_=FE=C5=D2=CE=CF=D7?= (aka Andrey A. Chernov, Black Mage) X-Class: Fast Subject: re: ATTENTION to CD driver authors (matcd, scd) Lines: 15 Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org Precedence: bulk In message =?KOI8-R?Q?=E1=CE=C4=D2=C5=CA_=FE=C5=D2=CE=CF=D7?= writes: >>(B) EXACTLY match the output that xcdplayer was expecting. And, >>(C) EXACTLY match the output that cdplayer was expecting. >cdplayer and cdplay was changed to deal with broken ioctl. ^^^^^^^^ Oops, I mean cdcontrol here. -- Andrey A. Chernov : And I rest so composedly, /Now, in my bed, ache@astral.msk.su : That any beholder /Might fancy me dead - http://dt.demos.su/~ache : Might start at beholding me, /Thinking me dead. RELCOM Team,FreeBSD Team : E.A.Poe From "For Annie" 1849 From owner-freebsd-current Thu Feb 1 02:07:33 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id CAA13654 for current-outgoing; Thu, 1 Feb 1996 02:07:33 -0800 (PST) Received: from Root.COM (implode.Root.COM [198.145.90.17]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id CAA13647 for ; Thu, 1 Feb 1996 02:07:27 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by Root.COM (8.6.12/8.6.5) with SMTP id CAA01314; Thu, 1 Feb 1996 02:07:28 -0800 Message-Id: <199602011007.CAA01314@Root.COM> X-Authentication-Warning: implode.Root.COM: Host localhost didn't use HELO protocol To: KATO Takenori cc: current@FreeBSD.org Subject: Re: TSS broken In-reply-to: Your message of "Mon, 01 Jan 1996 11:50:18 +0900." <199601010250.LAA00929@marble.eps.nagoya-u.ac.jp> From: David Greenman Reply-To: davidg@Root.COM Date: Thu, 01 Feb 1996 02:07:28 -0800 Sender: owner-current@FreeBSD.org Precedence: bulk >In recent change of sys/i386/i386/swtch.s, the code > movl %esp,PCB_ESP(%ecx) >is changed into > leal 4(%esp),%eax > movl %eax,PCB_ESP(%ecx) >(in savectx). > >After this operation, the member tss_esp points not user stack >pointer, but the address of TSS. > >This may causes panic when swapper is activated. I don't think so. At the time of entry to this function, the stack pointer points to the return address of the caller that was saved on the stack when the call was made. The stack layout looks like this: ... address of caller (?) auto variables used in mi_switch arguments to cpu_switch (proc) address of caller (mi_switch) auto variables used in cpu_switch arguments to savectx (pcb) address of caller (cpu_switch) The instruction pointer that is saved is the caller of savectx(), which is in cpu_switch. When the new process is scheduled to run, it will start at the return address. Previously, the stack was not fixed up to remove the return address and the result was that it was off-by-four. If cpu_switch referenced any of it's auto variables when the child started, bad things would have happened. The messed up stack pointer wasn't normally a problem because none of the auto variables were referenced after 'returning' to cpu_switch and the frame pointer fixes up the stack before the return to mi_switch. -DG David Greenman Core Team/Principal Architect, The FreeBSD Project From owner-freebsd-current Thu Feb 1 02:23:28 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id CAA14655 for current-outgoing; Thu, 1 Feb 1996 02:23:28 -0800 (PST) Received: from grumble.grondar.za (root@grumble.grondar.za [196.7.18.130]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id CAA14631 for ; Thu, 1 Feb 1996 02:23:08 -0800 (PST) Received: from localhost (mark@localhost [127.0.0.1]) by grumble.grondar.za (8.7.3/8.7.3) with SMTP id MAA14308 for ; Thu, 1 Feb 1996 12:22:53 +0200 (SAT) Message-Id: <199602011022.MAA14308@grumble.grondar.za> X-Authentication-Warning: grumble.grondar.za: Host mark@localhost [127.0.0.1] didn't use HELO protocol To: current@freebsd.org Subject: mount_devfs not in sbin/Makefile Date: Thu, 01 Feb 1996 12:22:53 +0200 From: Mark Murray Sender: owner-current@freebsd.org Precedence: bulk Hi Is there a good reason why mount_devfs is not in src/sbin/Makefile ? It builds and runs OK. M -- Mark Murray 46 Harvey Rd, Claremont, Cape Town 7700, South Africa +27 21 61-3768 GMT+0200 Finger mark@grondar.za for PGP key From owner-freebsd-current Thu Feb 1 02:31:20 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id CAA15233 for current-outgoing; Thu, 1 Feb 1996 02:31:20 -0800 (PST) Received: from Root.COM (implode.Root.COM [198.145.90.17]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id CAA15224 for ; Thu, 1 Feb 1996 02:31:16 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by Root.COM (8.6.12/8.6.5) with SMTP id CAA01387; Thu, 1 Feb 1996 02:30:47 -0800 Message-Id: <199602011030.CAA01387@Root.COM> X-Authentication-Warning: implode.Root.COM: Host localhost didn't use HELO protocol To: KATO Takenori cc: current@FreeBSD.org Subject: Re: TSS broken In-reply-to: Your message of "Mon, 01 Jan 1996 11:50:18 +0900." <199601010250.LAA00929@marble.eps.nagoya-u.ac.jp> From: David Greenman Reply-To: davidg@Root.COM Date: Thu, 01 Feb 1996 02:30:47 -0800 Sender: owner-current@FreeBSD.org Precedence: bulk >In recent change of sys/i386/i386/swtch.s, the code > movl %esp,PCB_ESP(%ecx) >is changed into > leal 4(%esp),%eax > movl %eax,PCB_ESP(%ecx) >(in savectx). > >After this operation, the member tss_esp points not user stack >pointer, but the address of TSS. > >This may causes panic when swapper is activated. I just read the above again a few times and I think I see now the misunderstanding. The "leal" instruction moves the _address_ of its argument. In this case, %esp+4. It is similar to: movl %esp,%eax addl $4,%eax movl %eax,PCB_ESP(%ecx) The only difference being that leal is faster and also doesn't affect the condition codes like the addl does (although in this case it doesn't matter since we're not using them). -DG David Greenman Core Team/Principal Architect, The FreeBSD Project From owner-freebsd-current Thu Feb 1 03:29:08 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id DAA19383 for current-outgoing; Thu, 1 Feb 1996 03:29:08 -0800 (PST) Received: from Root.COM (implode.Root.COM [198.145.90.17]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id DAA19371 for ; Thu, 1 Feb 1996 03:28:59 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by Root.COM (8.6.12/8.6.5) with SMTP id DAA01552; Thu, 1 Feb 1996 03:28:58 -0800 Message-Id: <199602011128.DAA01552@Root.COM> X-Authentication-Warning: implode.Root.COM: Host localhost didn't use HELO protocol To: KATO Takenori cc: current@FreeBSD.org Subject: Re: TSS broken In-reply-to: Your message of "Mon, 01 Jan 1996 11:50:18 +0900." <199601010250.LAA00929@marble.eps.nagoya-u.ac.jp> From: David Greenman Reply-To: davidg@Root.COM Date: Thu, 01 Feb 1996 03:28:58 -0800 Sender: owner-current@FreeBSD.org Precedence: bulk Gack, I said: >the call was made. The stack layout looks like this: > >... >address of caller (?) >auto variables used in mi_switch >arguments to cpu_switch (proc) >address of caller (mi_switch) >auto variables used in cpu_switch >arguments to savectx (pcb) >address of caller (cpu_switch) Actually, the stack layout is: ... address of caller (fork1) auto variables used in vm_fork arguments to cpu_fork (proc1, proc2) address of caller (vm_fork) auto variables used in cpu_fork arguments to savectx (pcb) address of caller (cpu_fork) The "switch" code I mentioned previously has nothing to do with this. :-) ...nonetheless, all of my comments still hold generally - I'm pretty sure that you've misunderstood the operation of the 'leal' instruction. The code as I've written it appears to be correct. -DG David Greenman Core Team/Principal Architect, The FreeBSD Project From owner-freebsd-current Thu Feb 1 04:33:29 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id EAA22865 for current-outgoing; Thu, 1 Feb 1996 04:33:29 -0800 (PST) Received: from tfs.com (tfs.com [140.145.250.1]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id EAA22850 for ; Thu, 1 Feb 1996 04:33:25 -0800 (PST) Received: from critter.tfs.com by tfs.com (smail3.1.28.1) with SMTP id m0thyCZ-0003wNC; Thu, 1 Feb 96 04:33 PST Received: from localhost.tfs.com (localhost.tfs.com [127.0.0.1]) by critter.tfs.com (8.6.12/8.6.12) with SMTP id NAA08373 for ; Thu, 1 Feb 1996 13:33:23 +0100 X-Authentication-Warning: critter.tfs.com: Host localhost.tfs.com didn't use HELO protocol To: current@freebsd.org Subject: ip_fw ordering of rules.. Date: Thu, 01 Feb 1996 13:33:22 +0100 Message-ID: <8371.823178002@critter.tfs.com> From: Poul-Henning Kamp Sender: owner-current@freebsd.org Precedence: bulk Does anybody but me find the ordering IP_FW does weird ? I'd like to kick it out entirely, but at least an option to disable it is in order... What do other users of it think ? Poul-Henning From owner-freebsd-current Thu Feb 1 05:34:23 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id FAA26396 for current-outgoing; Thu, 1 Feb 1996 05:34:23 -0800 (PST) Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id FAA26067 for ; Thu, 1 Feb 1996 05:29:54 -0800 (PST) Received: from sax.sax.de by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id OAA15276 for ; Thu, 1 Feb 1996 14:23:42 +0100 Received: by sax.sax.de (8.6.11/8.6.12-s1) with UUCP id OAA29539 for freebsd-current@FreeBSD.org; Thu, 1 Feb 1996 14:23:41 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.7.3/8.6.9) id NAA00654 for freebsd-current@FreeBSD.org; Thu, 1 Feb 1996 13:54:02 +0100 (MET) From: J Wunsch Message-Id: <199602011254.NAA00654@uriah.heep.sax.de> Subject: Re: ATTENTION to CD driver authors (matcd, scd) To: freebsd-current@FreeBSD.org (FreeBSD-current users) Date: Thu, 1 Feb 1996 13:54:02 +0100 (MET) In-Reply-To: from "=?KOI8-R?Q?=E1=CE=C4=D2=C5=CA_=FE=C5=D2=CE=CF=D7?=" at Feb 1, 96 11:17:59 am X-Phone: +49-351-2012 669 X-Mailer: ELM [version 2.4 PL23] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-current@FreeBSD.org Precedence: bulk As =?KOI8-R?Q?=E1=CE=C4=D2=C5=CA_=FE=C5=D2=CE=CF=D7?= wrote: > > >cdplayer and cdplay was changed to deal with broken ioctl. > ^^^^^^^^ > Oops, I mean cdcontrol here. Btw., do we really need both? -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-current Thu Feb 1 06:46:16 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id GAA00441 for current-outgoing; Thu, 1 Feb 1996 06:46:16 -0800 (PST) Received: from fw.ast.com (fw.ast.com [165.164.6.25]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id GAA00435 for ; Thu, 1 Feb 1996 06:46:11 -0800 (PST) Received: from nemesis by fw.ast.com with uucp (Smail3.1.29.1 #2) id m0ti0AH-000858C; Thu, 1 Feb 96 08:39 CST Received: by nemesis.lonestar.org (Smail3.1.27.1 #20) id m0ti07a-000CokC; Thu, 1 Feb 96 08:36 WET Message-Id: Date: Thu, 1 Feb 96 08:36 WET To: ache@astral.msk.su, current@freebsd.org From: uhclem@nemesis.lonestar.org (Frank Durda IV) Sent: Thu Feb 1 1996, 08:36:22 CST Subject: re: ATTENTION to CD driver authors (matcd, scd) Sender: owner-current@freebsd.org Precedence: bulk [0](B) EXACTLY match the output that xcdplayer was expecting. And, [0](C) EXACTLY match the output that cdplayer was expecting. [1]cdplayer and cdplay was changed to deal with broken ioctl. [1]^^^^^^^^ [2]Oops, I mean cdcontrol here. Ok, is someone going to "fix" xcdplayer? That is the application that I got the most complaints about (over two dozen different people complained) matcds beta version audio support until I got matcd to put out exactly what xcdplayer wanted. xcdplayer and cdplay request TOC data differently via the ioctls. cdplay asks about one track at a time, while xcdplayer asks for the entire thing in one lump and expects a "forged" leadout TOC entry that is different than the one cdplay expects/ed. Oh, and with regard to playing ranges of blocks, matcd has been able to do that all along. I had to write an app to test that since I wanted to make sure the "snarf straight redbook audio" worked. It does. I am in the middle of adding support for three more drive types to matcd and having the definition of what is "correct" change is a bit annoying and I want to make sure the extra work is really necessary before I start throwing away code that was working by the two measurements available. If we aren't having someone change xcdplayer, IMO we should delay all of these ioctl changes until both xcdplayer and the other audio apps are updated. There is nothing like a programmer who can't listen to his CDs anymore. :-( Frank Durda IV |"The Knights who say "LETNi" or uhclem%nemesis@rwsystr.nkn.net | demand... A SEGMENT REGISTER!!!" ^------(this is the fastest route)|"A what?" or ...letni!rwsys!nemesis!uhclem |"LETNi! LETNi! LETNi!" - 1983 From owner-freebsd-current Thu Feb 1 07:31:54 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id HAA03257 for current-outgoing; Thu, 1 Feb 1996 07:31:54 -0800 (PST) Received: from sequent.kiae.su (sequent.kiae.su [144.206.136.6]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id HAA03239 Thu, 1 Feb 1996 07:31:33 -0800 (PST) Received: by sequent.kiae.su id AA15328 (5.65.kiae-2 ); Thu, 1 Feb 1996 18:29:28 +0300 Received: by sequent.KIAE.su (UUMAIL/2.0); Thu, 1 Feb 96 18:29:26 +0300 Received: (from ache@localhost) by ache.dialup.ru (8.7.3/8.7.3) id SAA00589; Thu, 1 Feb 1996 18:28:36 +0300 (MSK) To: current@freebsd.org, S0ren Schmidt Message-Id: Organization: Olahm Ha-Yetzirah Date: Thu, 1 Feb 1996 18:28:36 +0300 (MSK) X-Mailer: Mail/@ [v2.42 FreeBSD] From: =?KOI8-R?Q?=E1=CE=C4=D2=C5=CA_=FE=C5=D2=CE=CF=D7?= (aka Andrey A. Chernov, Black Mage) X-Class: Fast Subject: Multiscreen, Bell & Talk Lines: 19 Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org Precedence: bulk Imagine you work at multiscreen console and someone tries to talk you. And talk requests comes to another (not current) screen, so you may even never notice them. Another variant: ncftp2 produce bell when (long) file transfer is done, since you never hear it from another screen, you forced to check it often. I have syscons patch wich delivers all bells to current screen independently of screen they originally comes. It really helps in situation like this. I saw several multiscreen implementations which do the same thing, f.e. 'screen' program notice you when bell comes to another screen. If no objection comes, I plan to commit the patch. -- Andrey A. Chernov : And I rest so composedly, /Now, in my bed, ache@astral.msk.su : That any beholder /Might fancy me dead - http://dt.demos.su/~ache : Might start at beholding me, /Thinking me dead. RELCOM Team,FreeBSD Team : E.A.Poe From "For Annie" 1849 From owner-freebsd-current Thu Feb 1 07:46:42 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id HAA04721 for current-outgoing; Thu, 1 Feb 1996 07:46:42 -0800 (PST) Received: from sequent.kiae.su (sequent.kiae.su [144.206.136.6]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id HAA04695 for ; Thu, 1 Feb 1996 07:46:25 -0800 (PST) Received: by sequent.kiae.su id AA17014 (5.65.kiae-2 ); Thu, 1 Feb 1996 18:34:54 +0300 Received: by sequent.KIAE.su (UUMAIL/2.0); Thu, 1 Feb 96 18:34:52 +0300 Received: (from ache@localhost) by ache.dialup.ru (8.7.3/8.7.3) id SAA00682; Thu, 1 Feb 1996 18:33:11 +0300 (MSK) To: current@freebsd.org, Frank Durda IV References: In-Reply-To: ; from Frank Durda IV at Thu, 1 Feb 96 08:36 WET Message-Id: Organization: Olahm Ha-Yetzirah Date: Thu, 1 Feb 1996 18:33:10 +0300 (MSK) X-Mailer: Mail/@ [v2.42 FreeBSD] From: =?KOI8-R?Q?=E1=CE=C4=D2=C5=CA_=FE=C5=D2=CE=CF=D7?= (aka Andrey A. Chernov, Black Mage) X-Class: Fast Subject: re: ATTENTION to CD driver authors (matcd, scd) Lines: 39 Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org Precedence: bulk In message Frank Durda IV writes: >[0](B) EXACTLY match the output that xcdplayer was expecting. And, >[0](C) EXACTLY match the output that cdplayer was expecting. >[1]cdplayer and cdplay was changed to deal with broken ioctl. >[1]^^^^^^^^ >[2]Oops, I mean cdcontrol here. >Ok, is someone going to "fix" xcdplayer? That is the application that I got >the most complaints about (over two dozen different people complained) >matcds beta version audio support until I got matcd to put out exactly what >xcdplayer wanted. xcdplayer does right thing and not needed to be fixed. >xcdplayer and cdplay request TOC data differently via the ioctls. >cdplay asks about one track at a time, while xcdplayer asks for the No, cdplay ask all TOC an once. >entire thing in one lump and expects a "forged" leadout TOC entry that >is different than the one cdplay expects/ed. No, it is the same. >If we aren't having someone change xcdplayer, IMO we should delay all of >these ioctl changes until both xcdplayer and the other audio apps are updated. >There is nothing like a programmer who can't listen to his CDs anymore. :-( They not needed to be updated, they do right thing. -- Andrey A. Chernov : And I rest so composedly, /Now, in my bed, ache@astral.msk.su : That any beholder /Might fancy me dead - http://dt.demos.su/~ache : Might start at beholding me, /Thinking me dead. RELCOM Team,FreeBSD Team : E.A.Poe From "For Annie" 1849 From owner-freebsd-current Thu Feb 1 08:28:29 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id IAA07851 for current-outgoing; Thu, 1 Feb 1996 08:28:29 -0800 (PST) Received: from asstdc.scgt.oz.au (root@asstdc.scgt.oz.au [202.14.234.65]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id IAA07840 for ; Thu, 1 Feb 1996 08:28:18 -0800 (PST) Received: (from imb@localhost) by asstdc.scgt.oz.au (8.6.12/BSD4.4) id DAA14231; Fri, 2 Feb 1996 03:28:02 +1100 From: michael butler Message-Id: <199602011628.DAA14231@asstdc.scgt.oz.au> Subject: Re: ip_fw ordering of rules.. To: phk@critter.tfs.com (Poul-Henning Kamp) Date: Fri, 2 Feb 1996 03:28:01 +1100 (EST) Cc: current@FreeBSD.ORG In-Reply-To: <8371.823178002@critter.tfs.com> from "Poul-Henning Kamp" at Feb 1, 96 01:33:22 pm X-Mailer: ELM [version 2.4 PL24beta] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.ORG Precedence: bulk Poul-Henning Kamp writes: > Does anybody but me find the ordering IP_FW does weird ? Yes ! > I'd like to kick it out entirely, but at least an option to > disable it is in order... > What do other users of it think ? I couldn't use FreeBSD without it .. no .. maybe that's a bit strong .. I'd just have to learn a bit more about Cisco's access-lists :-) However, the order rearrangement forces a particular strategy when building ipfw scripts that requires considerable patience by virtue of not always producing the expected (and desired) results. On the other side, I understand that searching a rule tree similar to that found in the routing tables is of considerable performance advantage as compared to the traversal a (possibly lengthy) singly linked list .. It's swings and roundabouts, michael From owner-freebsd-current Thu Feb 1 08:36:14 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id IAA08662 for current-outgoing; Thu, 1 Feb 1996 08:36:14 -0800 (PST) Received: from tfs.com (tfs.com [140.145.250.1]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id IAA08579 for ; Thu, 1 Feb 1996 08:36:05 -0800 (PST) Received: from critter.tfs.com by tfs.com (smail3.1.28.1) with SMTP id m0ti1zK-0003x9C; Thu, 1 Feb 96 08:35 PST Received: from localhost.tfs.com (localhost.tfs.com [127.0.0.1]) by critter.tfs.com (8.6.12/8.6.12) with SMTP id RAA08727; Thu, 1 Feb 1996 17:35:58 +0100 X-Authentication-Warning: critter.tfs.com: Host localhost.tfs.com didn't use HELO protocol To: michael butler cc: current@freebsd.org Subject: Re: ip_fw ordering of rules.. In-reply-to: Your message of "Fri, 02 Feb 1996 03:28:01 +1100." <199602011628.DAA14231@asstdc.scgt.oz.au> Date: Thu, 01 Feb 1996 17:35:57 +0100 Message-ID: <8725.823192557@critter.tfs.com> From: Poul-Henning Kamp Sender: owner-current@freebsd.org Precedence: bulk > Poul-Henning Kamp writes: > > > Does anybody but me find the ordering IP_FW does weird ? > > Yes ! > > On the other side, I understand that searching a rule tree similar to that > found in the routing tables is of considerable performance advantage as > compared to the traversal a (possibly lengthy) singly linked list .. It is always a singled linked list anyway... At least as far as I can tell... -- Poul-Henning Kamp | phk@FreeBSD.ORG FreeBSD Core-team. http://www.freebsd.org/~phk | phk@login.dknet.dk Private mailbox. whois: [PHK] | phk@ref.tfs.com TRW Financial Systems, Inc. Future will arrive by its own means, progress not so. From owner-freebsd-current Thu Feb 1 08:41:07 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id IAA08981 for current-outgoing; Thu, 1 Feb 1996 08:41:07 -0800 (PST) Received: from asstdc.scgt.oz.au (root@asstdc.scgt.oz.au [202.14.234.65]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id IAA08970 for ; Thu, 1 Feb 1996 08:40:59 -0800 (PST) Received: (from imb@localhost) by asstdc.scgt.oz.au (8.6.12/BSD4.4) id DAA14729; Fri, 2 Feb 1996 03:40:52 +1100 From: michael butler Message-Id: <199602011640.DAA14729@asstdc.scgt.oz.au> Subject: Re: ip_fw ordering of rules.. To: phk@critter.tfs.com (Poul-Henning Kamp) Date: Fri, 2 Feb 1996 03:40:48 +1100 (EST) Cc: current@freebsd.org In-Reply-To: <8725.823192557@critter.tfs.com> from "Poul-Henning Kamp" at Feb 1, 96 05:35:57 pm X-Mailer: ELM [version 2.4 PL24beta] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org Precedence: bulk > > On the other side, I understand that searching a rule tree similar to > > that found in the routing tables is of considerable performance > > advantage as compared to the traversal a (possibly lengthy) singly > > linked list .. > It is always a singled linked list anyway... Ugh ! Then there'll be no disadvantage in removing the "sort" :-) michael From owner-freebsd-current Thu Feb 1 09:11:59 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id JAA10719 for current-outgoing; Thu, 1 Feb 1996 09:11:59 -0800 (PST) Received: from tfs.com (tfs.com [140.145.250.1]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id JAA10714 for ; Thu, 1 Feb 1996 09:11:57 -0800 (PST) Received: from critter.tfs.com by tfs.com (smail3.1.28.1) with SMTP id m0ti2Y2-0003wCC; Thu, 1 Feb 96 09:11 PST Received: from localhost.tfs.com (localhost.tfs.com [127.0.0.1]) by critter.tfs.com (8.6.12/8.6.12) with SMTP id SAA09459; Thu, 1 Feb 1996 18:11:50 +0100 X-Authentication-Warning: critter.tfs.com: Host localhost.tfs.com didn't use HELO protocol To: michael butler cc: current@freebsd.org Subject: Re: ip_fw ordering of rules.. In-reply-to: Your message of "Fri, 02 Feb 1996 03:40:48 +1100." <199602011640.DAA14729@asstdc.scgt.oz.au> Date: Thu, 01 Feb 1996 18:11:46 +0100 Message-ID: <9454.823194706@critter.tfs.com> From: Poul-Henning Kamp Sender: owner-current@freebsd.org Precedence: bulk > > > On the other side, I understand that searching a rule tree similar to > > > that found in the routing tables is of considerable performance > > > advantage as compared to the traversal a (possibly lengthy) singly > > > linked list .. > > > It is always a singled linked list anyway... > > Ugh ! Then there'll be no disadvantage in removing the "sort" :-) Well, all the people who have managed to make it "DTRT" will disagree with you there I presume... -- Poul-Henning Kamp | phk@FreeBSD.ORG FreeBSD Core-team. http://www.freebsd.org/~phk | phk@login.dknet.dk Private mailbox. whois: [PHK] | phk@ref.tfs.com TRW Financial Systems, Inc. Future will arrive by its own means, progress not so. From owner-freebsd-current Thu Feb 1 09:58:31 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id JAA13911 for current-outgoing; Thu, 1 Feb 1996 09:58:31 -0800 (PST) Received: from rocky.sri.MT.net (rocky.sri.MT.net [204.182.243.10]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id JAA13901 for ; Thu, 1 Feb 1996 09:58:27 -0800 (PST) Received: (from nate@localhost) by rocky.sri.MT.net (8.6.12/8.6.12) id LAA20341; Thu, 1 Feb 1996 11:01:04 -0700 Date: Thu, 1 Feb 1996 11:01:04 -0700 From: Nate Williams Message-Id: <199602011801.LAA20341@rocky.sri.MT.net> To: Poul-Henning Kamp Cc: current@freebsd.org Subject: Re: ip_fw ordering of rules.. In-Reply-To: <8371.823178002@critter.tfs.com> References: <8371.823178002@critter.tfs.com> Sender: owner-current@freebsd.org Precedence: bulk > Does anybody but me find the ordering IP_FW does weird ? Yep. > I'd like to kick it out entirely, but at least an option to > disable it is in order... > > What do other users of it think ? I'm with you. Ugen was supposed to be adding code to allow folks to explicitly set some sort of priority (my wording, not his) so that folks who understand the code could set up the ordering, but I think anyone capable of seting up a firewall should understand that the order of rules is important. I've got a patch someone posted if you want it. It's two lines of code. :) Nate From owner-freebsd-current Thu Feb 1 10:04:39 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id KAA14453 for current-outgoing; Thu, 1 Feb 1996 10:04:39 -0800 (PST) Received: from who.cdrom.com (who.cdrom.com [192.216.222.3]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id KAA14435 for ; Thu, 1 Feb 1996 10:04:36 -0800 (PST) Received: from sequent.kiae.su (sequent.kiae.su [144.206.136.6]) by who.cdrom.com (8.6.12/8.6.11) with SMTP id KAA23533 for ; Thu, 1 Feb 1996 10:03:48 -0800 Received: by sequent.kiae.su id AA26772 (5.65.kiae-2 for current@freebsd.org); Thu, 1 Feb 1996 20:59:14 +0300 Received: by sequent.KIAE.su (UUMAIL/2.0); Thu, 1 Feb 96 20:59:14 +0300 Received: (from ache@localhost) by ache.dialup.ru (8.7.3/8.7.3) id UAA00489 for current@freebsd.org; Thu, 1 Feb 1996 20:54:49 +0300 (MSK) To: current@freebsd.org Message-Id: Organization: Olahm Ha-Yetzirah Date: Thu, 1 Feb 1996 20:54:48 +0300 (MSK) X-Mailer: Mail/@ [v2.42 FreeBSD] From: =?KOI8-R?Q?=E1=CE=C4=D2=C5=CA_=FE=C5=D2=CE=CF=D7?= (aka Andrey A. Chernov, Black Mage) X-Class: Fast Subject: Need at least one tester (cdcontrol with SCSI cd). Lines: 11 Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org Precedence: bulk Can anybody with -current cdcontrol.c and current scsi/cd.c run cdcontrol, enter "info" with audio disk and with data disk, and tell me, does info output determine audio/data correctly, please? Half of our CD drivers assume one order of control/addr_type field and another half assume another order, I want to be shure. -- Andrey A. Chernov : And I rest so composedly, /Now, in my bed, ache@astral.msk.su : That any beholder /Might fancy me dead - http://dt.demos.su/~ache : Might start at beholding me, /Thinking me dead. RELCOM Team,FreeBSD Team : E.A.Poe From "For Annie" 1849 From owner-freebsd-current Thu Feb 1 10:28:21 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id KAA16501 for current-outgoing; Thu, 1 Feb 1996 10:28:21 -0800 (PST) Received: from rocky.sri.MT.net (rocky.sri.MT.net [204.182.243.10]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id KAA16492 for ; Thu, 1 Feb 1996 10:28:14 -0800 (PST) Received: (from nate@localhost) by rocky.sri.MT.net (8.6.12/8.6.12) id LAA20539; Thu, 1 Feb 1996 11:30:40 -0700 Date: Thu, 1 Feb 1996 11:30:40 -0700 From: Nate Williams Message-Id: <199602011830.LAA20539@rocky.sri.MT.net> To: michael butler Cc: phk@critter.tfs.com (Poul-Henning Kamp), current@freebsd.org Subject: Re: ip_fw ordering of rules.. In-Reply-To: <199602011640.DAA14729@asstdc.scgt.oz.au> References: <8725.823192557@critter.tfs.com> <199602011640.DAA14729@asstdc.scgt.oz.au> Sender: owner-current@freebsd.org Precedence: bulk > > > On the other side, I understand that searching a rule tree similar to > > > that found in the routing tables is of considerable performance > > > advantage as compared to the traversal a (possibly lengthy) singly > > > linked list .. > > > It is always a singled linked list anyway... > > Ugh ! Then there'll be no disadvantage in removing the "sort" :-) Except that supposedly it 'orders' things so that the most common rules (or what it thinks should be most common) will be found at the top, thus making it faster since you don't have to walk the entire tree. Nate From owner-freebsd-current Thu Feb 1 11:33:48 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id LAA21926 for current-outgoing; Thu, 1 Feb 1996 11:33:48 -0800 (PST) Received: from sequent.kiae.su (sequent.kiae.su [144.206.136.6]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id LAA21920 for ; Thu, 1 Feb 1996 11:33:33 -0800 (PST) Received: by sequent.kiae.su id AA17944 (5.65.kiae-2 ); Thu, 1 Feb 1996 22:30:48 +0300 Received: by sequent.KIAE.su (UUMAIL/2.0); Thu, 1 Feb 96 22:30:48 +0300 Received: (from ache@localhost) by ache.dialup.ru (8.7.3/8.7.3) id WAA00445; Thu, 1 Feb 1996 22:30:19 +0300 (MSK) To: FreeBSD-current users , J Wunsch References: <199602011254.NAA00654@uriah.heep.sax.de> In-Reply-To: <199602011254.NAA00654@uriah.heep.sax.de>; from J Wunsch at Thu, 1 Feb 1996 13:54:02 +0100 (MET) Message-Id: Organization: Olahm Ha-Yetzirah Date: Thu, 1 Feb 1996 22:30:19 +0300 (MSK) X-Mailer: Mail/@ [v2.42 FreeBSD] From: =?KOI8-R?Q?=E1=CE=C4=D2=C5=CA_=FE=C5=D2=CE=CF=D7?= (aka Andrey A. Chernov, Black Mage) X-Class: Fast Subject: Re: ATTENTION to CD driver authors (matcd, scd) Lines: 18 Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org Precedence: bulk In message <199602011254.NAA00654@uriah.heep.sax.de> J Wunsch writes: >As =?KOI8-R?Q?=E1=CE=C4=D2=C5=CA_=FE=C5=D2=CE=CF=D7?= wrote: >> >> >cdplayer and cdplay was changed to deal with broken ioctl. >> ^^^^^^^^ >> Oops, I mean cdcontrol here. >Btw., do we really need both? Cdcontrol is beter. We can nuke cdplay if someone add command-line input to cdcontrol (it is recent addition to cdplay). -- Andrey A. Chernov : And I rest so composedly, /Now, in my bed, ache@astral.msk.su : That any beholder /Might fancy me dead - http://dt.demos.su/~ache : Might start at beholding me, /Thinking me dead. RELCOM Team,FreeBSD Team : E.A.Poe From "For Annie" 1849 From owner-freebsd-current Thu Feb 1 12:28:42 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id MAA26655 for current-outgoing; Thu, 1 Feb 1996 12:28:42 -0800 (PST) Received: from mpp.minn.net (root@mpp.Minn.Net [204.157.201.242]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id MAA26647 Thu, 1 Feb 1996 12:28:36 -0800 (PST) Received: (from mpp@localhost) by mpp.minn.net (8.7.3/8.6.9) id OAA27026; Thu, 1 Feb 1996 14:27:43 -0600 (CST) Message-Id: <199602012027.OAA27026@mpp.minn.net> Subject: Re: Multiscreen, Bell & Talk To: ache@astral.msk.su (=?KOI8-R?Q?=E1=CE=C4=D2=C5=CA_=FE=C5=D2=CE=CF=D7?=) Date: Thu, 1 Feb 1996 14:27:43 -0600 (CST) From: "Mike Pritchard" Cc: current@freebsd.org, sos@freebsd.org In-Reply-To: from "=?KOI8-R?Q?=E1=CE=C4=D2=C5=CA_=FE=C5=D2=CE=CF=D7?=" at Feb 1, 96 06:28:36 pm X-Mailer: ELM [version 2.4 PL25 ME8b] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org Precedence: bulk > Imagine you work at multiscreen console and someone tries to talk you. > And talk requests comes to another (not current) screen, so you may > even never notice them. Another variant: ncftp2 produce bell > when (long) file transfer is done, since you never hear it from > another screen, you forced to check it often. > > I have syscons patch wich delivers all bells to current screen > independently of screen they originally comes. It really helps > in situation like this. I saw several multiscreen > implementations which do the same thing, f.e. 'screen' program > notice you when bell comes to another screen. > > If no objection comes, I plan to commit the patch. I've thought about doing the same thing myself. However, can you make the bell a different pitch/duration or something so that you have an idea that the bell is ringing in a another screen, and not in the current one? -- Mike Pritchard mpp@minn.net "Go that way. Really fast. If something gets in your way, turn" From owner-freebsd-current Thu Feb 1 12:33:47 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id MAA27132 for current-outgoing; Thu, 1 Feb 1996 12:33:47 -0800 (PST) Received: from grumble.grondar.za (root@grumble.grondar.za [196.7.18.130]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id MAA27126 Thu, 1 Feb 1996 12:33:41 -0800 (PST) Received: from localhost (mark@localhost [127.0.0.1]) by grumble.grondar.za (8.7.3/8.7.3) with SMTP id WAA02690; Thu, 1 Feb 1996 22:32:35 +0200 (SAT) Message-Id: <199602012032.WAA02690@grumble.grondar.za> X-Authentication-Warning: grumble.grondar.za: Host mark@localhost [127.0.0.1] didn't use HELO protocol To: =?KOI8-R?Q?=E1=CE=C4=D2=C5=CA_=FE=C5=D2=CE=CF=D7?= (aka Andrey A. Chernov, Black Mage) cc: current@freebsd.org, S0ren Schmidt Subject: Re: Multiscreen, Bell & Talk Date: Thu, 01 Feb 1996 22:32:33 +0200 From: Mark Murray Sender: owner-current@freebsd.org Precedence: bulk =?KOI8-R?Q?=E1=CE=C4=D2=C5=CA_=FE=C5=D2=CE=CF=D7?= wrote: > Imagine you work at multiscreen console and someone tries to talk you. > And talk requests comes to another (not current) screen, so you may > even never notice them. Another variant: ncftp2 produce bell > when (long) file transfer is done, since you never hear it from > another screen, you forced to check it often. This irritates me too. > I have syscons patch wich delivers all bells to current screen > independently of screen they originally comes. It really helps > in situation like this. I saw several multiscreen > implementations which do the same thing, f.e. 'screen' program > notice you when bell comes to another screen. Is there some kind of "code" that could be used? The tone changes if it comes froma different console. I often have biff set on my master console, and it would be nice to know that something else has happened, apart from incoming mail... > If no objection comes, I plan to commit the patch. Yes, please! M -- Mark Murray 46 Harvey Rd, Claremont, Cape Town 7700, South Africa +27 21 61-3768 GMT+0200 Finger mark@grondar.za for PGP key From owner-freebsd-current Thu Feb 1 12:41:41 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id MAA27714 for current-outgoing; Thu, 1 Feb 1996 12:41:41 -0800 (PST) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id MAA27708 for ; Thu, 1 Feb 1996 12:41:36 -0800 (PST) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id NAA13606; Thu, 1 Feb 1996 13:37:05 -0700 From: Terry Lambert Message-Id: <199602012037.NAA13606@phaeton.artisoft.com> Subject: Re: invalid primary partition table: no magic To: julian@ref.tfs.com (Julian Elischer) Date: Thu, 1 Feb 1996 13:37:04 -0700 (MST) Cc: terry@lambert.org, bde@zeta.org.au, freebsd-current@freebsd.org, j@uriah.heep.sax.de In-Reply-To: <199602010102.RAA11946@ref.tfs.com> from "Julian Elischer" at Jan 31, 96 05:02:55 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org Precedence: bulk > consider a BSD partition put at the beginning of a disk.. > > at the beginning of the disk we therefore have a fdisk slice AND and disklabel > slice... which gets to claim the disk? :) > Possibly the fdisk-slice probe() method knows that if a BSD subslice > starts at 0 then to NOT grab control :) Well, the fdisk table has to start at 0, so only one can occupy the space at a time. My first reaction would be to disallow that arrangement at all, or, less optimally, have the BSD subslice code force an *unclaim* by the FDISK code. I wasn't really thinking in terms of allowing the claim process to continue indefinitely, I was thinking of some method of prioritization. For instance, the difference between a FAT and a VFAT volume is allowing VFAT to claim the volume first if there is any VFAT data on it already. > > Because we get range restriction guarantees, FS events in the kernel > > on the /dev/wc0/t0/p0 devie can't screw up the contents of any other > > slice, period. No matter what bad calculations the MSDOSFS makes. > > I THINK we might have that now anyhow.. My guess our problem isn't just > disk overshoots. No. But for developement, protection against overshoots is an issue. Personally, I think overshoots are the current *worst* problem of the DOSFS code -- there should be no way for it to corrupt an area not designated as under its control, which is basically what's happening in the FIPS case. It's irrelevant that a robust DOSFS would not make the cluster count cache write mistake that causes that particular problem: you can't trust the FS's to be robust -- and you *should* not. > > So now we have the device/slice mess straightened out. > > > > (*) One thing we may want to consider is that the "no claimant" cases > > above are nearly the perfect mechanism to cause a callback to the > > VFS code to ask each VFS if it want to "claim" a device -- causing > > it to be mounted. > > I don't know about that.. we don't know where to mount it.. > such leaf nodes however would probably be given some sort of descriptive name > however, describing what they are... There are two or three nice approaches to this. The first would be to cause the fstab to be accessed and the device mounted based on that information. This requires a premount of root. This is somewhat unsatisfactory, in that devices may probe out of mount dependency order; it would require establishing a shadow frame under which translucent mounts could take place. On the other hand, such a frame is useful for establishing a /dev mapping prior to a root mapping, or allowing a root remapping. It is also a useful mechanism for a nomadic computing environment, where mirrored resources exist at multiple access locations. Functionally, this would cause mounts to default to being "union". The second would use a "drive" paradigm -- similar to DOS. Each mount as a result of a callback establishes a "drive mapping". If you wanted to, you could set up such a mapping to use "//drivename/..." to access the per-drive "root". This has the advantage of not needing a mapping to a fixed location in the FS hierarchy (impling a mount oder that may be different from the device discovery order). This would be extremely useful for a nomadic computing system, since an installed software package could be in "//package-name/" on a remote resource. If I took my laptop from a company location in AZ to one in MA, as long as I could get authenticated to the local net, I would have access to the package without having it installed locally. The problem that this has is still there, though: you would have to have an fstab that mapped by resource name rather than by device and/or FS type. The implication of this is clear: the fsck file system recovery would need to run as part of the kernel for an automount situation. On the other hand, there has been little work (other than mine) on an fstyp type of FS auto-recognition. An fsck utility could simply be run on all resources, and call the per-fs-type checker based on the results of a type identification. This is moderately SVR4'ish, but is very modular, allowing for drop in addition of supported file system types. One missing key piece in a user space implementation is forced cleaning after a boot count has been exceeded. To accomplish that requires some of the recent work that has been done for our commercial product: First, the sync'er process needs to restore the file system to a "clean" state after a period of inactivity. This lets an fssync type operation set the FS clean, and if the device is locaked against user access during the period, the cleaner can be run against a mounted FS. Second, root mounts on unclean FS's are R/O if the clean bit is not set. The mount becomes a two-stage "mount, then remount". If the remount fails, you leave the FS mounted but read-only. The consistency check can force a remount on the FS being marked clean. At this point the fstab is just a mechanism for specifying resource to hierarchy mapping and options. To allow the widest range of possibility, the remount as read/write should take place when the resource is mapped to a hierarchy locationfrom the identified resource list -- in the /etc/rc file's mount of fstab partitions. A third approach (these three are not the only possible ones!) would be to use the "last mounted on location" and a bit to tag whether that has been changed -- requiring an API in the modification of the fstab to "notify" the underlying FS of changes. There are additional "enhancements" that can be forseen -- for instance, it would be relatively trivial to identify all resources before mount and sort the mount order based on the implied graph dependency of the previous mount locations. This may fail when there is a very complex mapping -- like a mount of one or more FS's on a vnconfig'ed file on an existing FS that is not yet mounted -- etc.. > The way I've been looking at it > is that there are many stackable "disk-like object" drivers that have a bunch > of methods. The default method is to simply supply an offset and the handle > to the next layer down, however there are at LEAST the following methods > available: > > probe > attach > doIO <------ These two are really mutually exlusive > offset <------ This is a special case of doIO for common simple cases > parent <------ not used for such things as CCD drivers > > so that if type.diIO is NULL then you simply add type.offset and switch to > type.parent, which might in turn have a doIO or offset.. etc. > eventually you hit the methods that were expoerted by the physical > device driver. Devices always have a doIO method. The "non-doIO" case is what I have internally called a logical partition driver. This is a simple sector remapping. The "doIO" case can be broken into at least three type of drivers: I/O by intent, I/O by side effect, and I/O by proxy. The "intent" describes physical device drivers. The "side effect" describes multiplex drivers, like a CDROM or tape changer. The "proxy" describes volume concatenation, block level compression, and media perfection drivers. I think "proxy" drivers need to be given first shot at an "arriving" physical device. > basically > 1) when you register a new 'disk-like' object, the > 'disk-object' handler creates a DEVFS entry for it and > calls the 'probe' method of all known > types until one says "I can handle this". This defeats your "two types would claim it if they were allowed to" scenario -- but I agree with it. I would fix your scenario by fiat (making it illegal) or by specifying priority, and mandating that the author establish an order (and leave a large space between for binary insertion, like I did with kerninit). This doesn't necessarily allow support for "host drive + drivespace drive" both being visible -- something that might be desirable. The final fix on that is handled by the "drivespace driver" having a higher priority and reexporting the host drive as a pseduo-drive (if it's still allowable) with a tag saying "don't claim" to himself. > 2) the new method is 'stacked' and it's 'attach' method is called. > 3) The attach method will 'register' any sub-partitions it finds, > (goto 1 for ewach such sub partition) > 4) Any sub partition that doesn't have a 'claiment' > still has it's devfs entry which becomes the only source of > actions. I'd add that you could "collapse" a logical device stack to avoid unnecessary cruft. Specifically, you'd have to have a "collapsed" logical device record with a pointer to the original. Consider: 1) disk has DOS partition table, claimed by DOS partition driver, partition 2 is exported as a offset/length/ptr-to-phys. 2) partition 2 has BSD slice code, claimed by BSD slice driver, slice 'a' is is exported as offset/length/ptr-to-P2-part 3) Reference is "collapsed" to "offset/length/ptr-to-phys, with a pointer to the proginal slice 'a' export. 4) I/O skips logical placement calculations inhernet in stack traversal of an "uncollapsed" stack. 5) Geometry modifications must operate on the uncollapsed stack and recalculate the collapsed as necessary. 6) "proxy" layers limit collapsability. 7) Stack existance limits the ability to damage structures necessary for maintaining currently mounted FS's. > Notes: > A 'type' might be a CCD driver, which recognises a label saying > "part 4 of a 5 part volume" Definite agreement here. There must be a recognition mechanism unique across all type instances... for historal screwups, like FAT vs. VFAT, you have to punt to ordering and more in-depth analysis than a simple magic number.. > Every time you register a new 'disk-like' device, a 'structure is allocated, > and the 'next' ID is incremented. an entry is put into a hash table so > that that structure can be easily located, given that ID number. > The ID number is the minor number.. I think the use of major/minor is not really necessary, except as a method of exporting devices into the name space at a particular layer -- that is, it can be maintained by an integer parameter initialized to zero, the address of which is passed in on each registration by a layer: it is associated with the export interface structure that causes the device name to show up. > This means that there is no encoding of bits in minor numbers. This is a good idea -- this information should be encoded in the hierarchy in the devfs anyway, IMO. One example of this is pty designation, which I'd like to see set up as a directory of cloning devices aquired by ioctl() on the controlling device (the directory their name space export occurs in). > It also means that minors might be differnt each time you boot > (that's why devfs).. Programs should nominally ignore minor numbers in any case. > The whole thind hangs off a NEW major number and might be done in > parallel witht eh existing system for a while.. Time to murder mknod, MAKEDEV, etc., IMO. To hell with them. 8-). Really, we should consider throwing them out entirely; we've been in a migration state for some time. The missing piece is the devfs /dev and / mount-interaction... and we're discussing that here. > Because probing can be tricky I plan on passing 'context' hints > at probe time so that various probe routines are not working totally in > the dark as to what happenned before.. > (e.g. finding a fdisk slice within an fdisk slice is legal but > should be treated differently (I think block numbers are not absolute in > extended partitions .. needs confirmation). I think this is exposed by the hiearchy in the example I posted; the real issue is applicability of interfaces at the higher layers. This can be handled by physical and logical attribution -- both of which "bleed up". The physical attribute bits are determined (and assigned) by the device driver (removable media, read-only media, arrival notification, etc.). The logical attribute bits are set by each layer (has media perfection, don't allow more, has compression, don't allow more, etc.). Finally, there is attribution by identifier, where, for instance, DOS partitioning can disallow itself by virtue of a predecessor device having DOS compression already. This would have to be carefully handled, since this would disallow vnconfig'ed devices as disks unless attribution could be changed at vnconfig level (creation of ISOFS images, etc. would need this). > Writing a new disk driver get's to be really simple.. > write basic IO routines, > register a disk-like device.. stand back and await work.. Yes, exactly. It also provides for the ability to do "media arrival" for removable devices that do notification, and FS callback for "media validation" for already mounted FS's on removable media without notification (I have shot myself in the foot swapping floppies on a mounted drive on more than one occasion). Regards, Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-current Thu Feb 1 12:45:54 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id MAA28040 for current-outgoing; Thu, 1 Feb 1996 12:45:54 -0800 (PST) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id MAA28031 Thu, 1 Feb 1996 12:45:48 -0800 (PST) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id NAA13624; Thu, 1 Feb 1996 13:42:32 -0700 From: Terry Lambert Message-Id: <199602012042.NAA13624@phaeton.artisoft.com> Subject: Re: Multiscreen, Bell & Talk To: ache@astral.msk.su (=?KOI8-R?Q?=E1=CE=C4=D2=C5=CA_=FE=C5=D2=CE=CF=D7?=) Date: Thu, 1 Feb 1996 13:42:32 -0700 (MST) Cc: current@FreeBSD.ORG, sos@FreeBSD.ORG In-Reply-To: from "=?KOI8-R?Q?=E1=CE=C4=D2=C5=CA_=FE=C5=D2=CE=CF=D7?=" at Feb 1, 96 06:28:36 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.ORG Precedence: bulk > I have syscons patch wich delivers all bells to current screen > independently of screen they originally comes. It really helps > in situation like this. I saw several multiscreen > implementations which do the same thing, f.e. 'screen' program > notice you when bell comes to another screen. > > If no objection comes, I plan to commit the patch. Does it deliver the bells in the pitch, frequency, and duration of the originating console, or does it always use the current console settings? I could see it being marginally useful to use the local console (that's what SCO does), on the other hand, being able to identify console beep origination by pitch would keep people from confusing a local event (like a vi error bell) with an event that requires their attention. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-current Thu Feb 1 12:47:08 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id MAA28116 for current-outgoing; Thu, 1 Feb 1996 12:47:08 -0800 (PST) Received: from deadline.snafu.de (deadline.snafu.de [194.64.158.28]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id MAA28105 for ; Thu, 1 Feb 1996 12:46:56 -0800 (PST) Received: by deadline.snafu.de id m0ti5uX-0009i7C; Thu, 1 Feb 96 21:47 MET (/\oo/\ Smail3.1.29.1 #29.1) Message-Id: From: root@deadline.snafu.de (Andreas S. Wetzel) Subject: -current: isa_dmadone_nobounce: channel 6 not busy To: current@freebsd.org Date: Thu, 1 Feb 1996 21:47:16 +0100 (MET) Organization: A world stranger than you have ever imagined. X-Mailer: ELM [version 2.4 PL25 ME8b] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org Precedence: bulk Hi! --- With a freshly installed -current as of Feb 01 1996 I get the following message on the system console, when playing sounds via rplay. isa_dmadone_nobounce: channel 6 not busy Any ideas? Regards, mickey -- (__) (@@) Andreas S. Wetzel E-mail: mickey@deadline.snafu.de /-------\/ Utrechter Strasse 41 Web: http://deadline.snafu.de/ / | || 13347 Berlin Voice: <+4930> 456 81 68 * ||----|| Germany Fax/Data: <+4930> 455 19 57 ~~ ~~ From owner-freebsd-current Thu Feb 1 13:30:19 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id NAA01537 for current-outgoing; Thu, 1 Feb 1996 13:30:19 -0800 (PST) Received: from ra.dkuug.dk (ra.dkuug.dk [193.88.44.193]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id NAA01529 for ; Thu, 1 Feb 1996 13:30:13 -0800 (PST) Received: from critter.tfs.com ([193.88.44.194]) by ra.dkuug.dk (8.6.12/8.6.12) with ESMTP id WAA10155; Thu, 1 Feb 1996 22:17:45 +0100 Received: from localhost.tfs.com (localhost.tfs.com [127.0.0.1]) by critter.tfs.com (8.6.12/8.6.12) with SMTP id WAA00995; Thu, 1 Feb 1996 22:07:58 +0100 X-Authentication-Warning: critter.tfs.com: Host localhost.tfs.com didn't use HELO protocol To: Nate Williams cc: michael butler , current@freebsd.org Subject: Re: ip_fw ordering of rules.. In-reply-to: Your message of "Thu, 01 Feb 1996 11:30:40 MST." <199602011830.LAA20539@rocky.sri.MT.net> Date: Thu, 01 Feb 1996 22:07:57 +0100 Message-ID: <993.823208877@critter.tfs.com> From: Poul-Henning Kamp Sender: owner-current@freebsd.org Precedence: bulk > > > It is always a singled linked list anyway... > > > > Ugh ! Then there'll be no disadvantage in removing the "sort" :-) > > Except that supposedly it 'orders' things so that the most common rules > (or what it thinks should be most common) will be found at the top, thus > making it faster since you don't have to walk the entire tree. Well, I suggest you look at the ordering then, that is most certainly >NOT< what the code does. I will make it an option. -- Poul-Henning Kamp | phk@FreeBSD.ORG FreeBSD Core-team. http://www.freebsd.org/~phk | phk@login.dknet.dk Private mailbox. whois: [PHK] | phk@ref.tfs.com TRW Financial Systems, Inc. Future will arrive by its own means, progress not so. From owner-freebsd-current Thu Feb 1 13:54:56 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id NAA03581 for current-outgoing; Thu, 1 Feb 1996 13:54:56 -0800 (PST) Received: from rocky.sri.MT.net (rocky.sri.MT.net [204.182.243.10]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id NAA03565 for ; Thu, 1 Feb 1996 13:54:49 -0800 (PST) Received: (from nate@localhost) by rocky.sri.MT.net (8.6.12/8.6.12) id OAA21193; Thu, 1 Feb 1996 14:57:18 -0700 Date: Thu, 1 Feb 1996 14:57:18 -0700 From: Nate Williams Message-Id: <199602012157.OAA21193@rocky.sri.MT.net> To: Poul-Henning Kamp Cc: Nate Williams , michael butler , current@freebsd.org Subject: Re: ip_fw ordering of rules.. In-Reply-To: <993.823208877@critter.tfs.com> References: <199602011830.LAA20539@rocky.sri.MT.net> <993.823208877@critter.tfs.com> Sender: owner-current@freebsd.org Precedence: bulk > > > > It is always a singled linked list anyway... > > > > > > Ugh ! Then there'll be no disadvantage in removing the "sort" :-) > > > > Except that supposedly it 'orders' things so that the most common rules > > (or what it thinks should be most common) will be found at the top, thus > > making it faster since you don't have to walk the entire tree. > > Well, I suggest you look at the ordering then, that is most > certainly >NOT< what the code does. That's what it's supposed to do. I guess it depends on what you think should be the most 'common' rules. :) > I will make it an option. Thanks! Nate From owner-freebsd-current Thu Feb 1 14:53:19 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id OAA08041 for current-outgoing; Thu, 1 Feb 1996 14:53:19 -0800 (PST) Received: from ra.dkuug.dk (ra.dkuug.dk [193.88.44.193]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id OAA08024 for ; Thu, 1 Feb 1996 14:52:56 -0800 (PST) Received: from critter.tfs.com ([193.88.44.194]) by ra.dkuug.dk (8.6.12/8.6.12) with ESMTP id XAA10534; Thu, 1 Feb 1996 23:41:43 +0100 Received: from localhost.tfs.com (localhost.tfs.com [127.0.0.1]) by critter.tfs.com (8.6.12/8.6.12) with SMTP id XAA01198; Thu, 1 Feb 1996 23:52:40 +0100 X-Authentication-Warning: critter.tfs.com: Host localhost.tfs.com didn't use HELO protocol To: Nate Williams cc: michael butler , current@freebsd.org Subject: Re: ip_fw ordering of rules.. In-reply-to: Your message of "Thu, 01 Feb 1996 14:57:18 MST." <199602012157.OAA21193@rocky.sri.MT.net> Date: Thu, 01 Feb 1996 23:52:39 +0100 Message-ID: <1196.823215159@critter.tfs.com> From: Poul-Henning Kamp Sender: owner-current@freebsd.org Precedence: bulk > > > > > It is always a singled linked list anyway... > > > > > > > > Ugh ! Then there'll be no disadvantage in removing the "sort" :-) > > > > > > Except that supposedly it 'orders' things so that the most common rules > > > (or what it thinks should be most common) will be found at the top, thus > > > making it faster since you don't have to walk the entire tree. > > > > Well, I suggest you look at the ordering then, that is most > > certainly >NOT< what the code does. > > That's what it's supposed to do. I guess it depends on what you think > should be the most 'common' rules. :) It basically sorts so that the rule covering most addresses come first. It doesn't look at deny/pass in that context, so if you say: deny some specific port allow the rest It will come out as: allow everything a deny rule never used. -- Poul-Henning Kamp | phk@FreeBSD.ORG FreeBSD Core-team. http://www.freebsd.org/~phk | phk@login.dknet.dk Private mailbox. whois: [PHK] | phk@ref.tfs.com TRW Financial Systems, Inc. Future will arrive by its own means, progress not so. From owner-freebsd-current Thu Feb 1 15:45:56 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id PAA11517 for current-outgoing; Thu, 1 Feb 1996 15:45:56 -0800 (PST) Received: from sequent.kiae.su (sequent.kiae.su [144.206.136.6]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id PAA11512 Thu, 1 Feb 1996 15:45:49 -0800 (PST) Received: by sequent.kiae.su id AA21114 (5.65.kiae-2 ); Fri, 2 Feb 1996 02:38:24 +0300 Received: by sequent.KIAE.su (UUMAIL/2.0); Fri, 2 Feb 96 02:38:23 +0300 Received: (from ache@localhost) by ache.dialup.ru (8.7.3/8.7.3) id CAA00695; Fri, 2 Feb 1996 02:36:01 +0300 (MSK) To: Terry Lambert Cc: current@freebsd.org, sos@freebsd.org References: <199602012042.NAA13624@phaeton.artisoft.com> In-Reply-To: <199602012042.NAA13624@phaeton.artisoft.com>; from Terry Lambert at Thu, 1 Feb 1996 13:42:32 -0700 (MST) Message-Id: Organization: Olahm Ha-Yetzirah Date: Fri, 2 Feb 1996 02:36:01 +0300 (MSK) X-Mailer: Mail/@ [v2.42 FreeBSD] From: =?KOI8-R?Q?=E1=CE=C4=D2=C5=CA_=FE=C5=D2=CE=CF=D7?= (aka Andrey A. Chernov, Black Mage) X-Class: Fast Subject: Re: Multiscreen, Bell & Talk Lines: 23 Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org Precedence: bulk In message <199602012042.NAA13624@phaeton.artisoft.com> Terry Lambert writes: >Does it deliver the bells in the pitch, frequency, and duration of >the originating console, or does it always use the current console >settings? >I could see it being marginally useful to use the local console >(that's what SCO does), on the other hand, being able to identify >console beep origination by pitch would keep people from confusing >a local event (like a vi error bell) with an event that requires >their attention. I can use originating console pitch value, but usualy it is the same as current console have. So, I can up or down originating console pitch with some const instead. -- Andrey A. Chernov : And I rest so composedly, /Now, in my bed, ache@astral.msk.su : That any beholder /Might fancy me dead - http://dt.demos.su/~ache : Might start at beholding me, /Thinking me dead. RELCOM Team,FreeBSD Team : E.A.Poe From "For Annie" 1849 From owner-freebsd-current Thu Feb 1 17:01:30 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id RAA17284 for current-outgoing; Thu, 1 Feb 1996 17:01:30 -0800 (PST) Received: from iceland.it.earthlink.net (iceland-f.it.earthlink.net [206.85.92.28]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id RAA17279 Thu, 1 Feb 1996 17:01:28 -0800 (PST) Received: from STEPHENT (stevt.earthlink.net [206.85.81.224]) by iceland.it.earthlink.net (8.6.12/8.6.12) with SMTP id RAA06440; Thu, 1 Feb 1996 17:01:25 -0800 Date: Thu, 1 Feb 1996 17:01:25 -0800 Message-Id: <199602020101.RAA06440@iceland.it.earthlink.net> X-Sender: stevt@earthlink.net (Unverified) X-Mailer: Windows Eudora Light Version 1.5.2 Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" To: questions@freebsd.org From: Steve Tan Subject: newbie : How write to DOS Floppy ? Cc: current@freebsd.org Sender: owner-current@freebsd.org Precedence: bulk Hi, I'm not sure if this is the right place to ask, but I'm trying to figure out how to write files to a DOS disk, my floppy drive. I didn't see any info in the FAQ's or installation guides. I believe I need to mount /dev/fd0 or /dev/rmt0 , but I can't find the specific command to use. I'm using BSD to develop CGI perl scripts and need to transfer them to a PC running Win95. Any help would be greatly appreciated. Steve From owner-freebsd-current Thu Feb 1 17:50:47 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id RAA21661 for current-outgoing; Thu, 1 Feb 1996 17:50:47 -0800 (PST) Received: from deadline.snafu.de (deadline.snafu.de [194.64.158.28]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id RAA21656 for ; Thu, 1 Feb 1996 17:50:37 -0800 (PST) Received: by deadline.snafu.de id m0tiAeS-0009ikC; Fri, 2 Feb 96 02:51 MET (/\oo/\ Smail3.1.29.1 #29.1) Message-Id: Date: Fri, 2 Feb 96 02:51 MET X-Newsreader: knews 0.9.3 References: From: root@deadline.snafu.de (Andreas S. Wetzel) Subject: Re: Linux Netscape 2.0b6a? X-Original-Newsgroups: deadline.lists.freebsd-current In-Reply-To: To: Peter Wemm Cc: current@freebsd.org Sender: owner-current@freebsd.org Precedence: bulk Hi! --- In article , Peter Wemm writes: >3: Does it work for anybody else on FreeBSD? I was also trying to get the linux version of netscape 2.0b6a to work on -current. What I get is lots of: "Linux-emul(430): syslog() not supported (BSD sigreturn)" messages on the sysconsole and the message: resolv+: "bind" is an invalid keyword resolv+: "hosts" is an invalid keyword on the shell window where I started netscape. The last message does not seem quite new to me since I remember to have seen it anywhere before. I guess it was when trying to play linuxxdoom over IP network. The main problem on this is, that netscape is not able to resolve *ANY* hostnames, since it seems to have trouble with the resolver. Regards, Mickey -- (__) (@@) Andreas S. Wetzel E-mail: mickey@deadline.snafu.de /-------\/ Utrechter Strasse 41 Web: http://deadline.snafu.de/ / | || 13347 Berlin Voice: <+4930> 456 81 68 * ||----|| Germany Fax/Data: <+4930> 455 19 57 ~~ ~~ From owner-freebsd-current Thu Feb 1 18:04:20 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id SAA22218 for current-outgoing; Thu, 1 Feb 1996 18:04:20 -0800 (PST) Received: from deadline.snafu.de (deadline.snafu.de [194.64.158.28]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id SAA22212 for ; Thu, 1 Feb 1996 18:04:15 -0800 (PST) Received: by deadline.snafu.de id m0tiArK-0009ikC; Fri, 2 Feb 96 03:04 MET (/\oo/\ Smail3.1.29.1 #29.1) Message-Id: Date: Fri, 2 Feb 96 03:04 MET X-Newsreader: knews 0.9.3 References: From: root@deadline.snafu.de (Andreas S. Wetzel) Subject: Re: Need at least one tester (cdcontrol with SCSI cd). X-Original-Newsgroups: deadline.lists.freebsd-current In-Reply-To: To: =?KOI8-R?Q?=E1=CE=C4=D2=C5=CA_=FE=C5=D2=CE=CF=D7?= (aka Andrey A. Chernov, Black Mage) Cc: current@freebsd.org Sender: owner-current@freebsd.org Precedence: bulk Hi! --- In article , =?KOI8-R?Q?=E1=CE=C4=D2=C5=CA_=FE=C5=D2=CE=CF=D7?= (aka Andrey A. Chernov, Black Mage) writes: >Can anybody with -current cdcontrol.c and current scsi/cd.c >run cdcontrol, enter "info" with audio disk and with data >disk, and tell me, does info output determine audio/data correctly, >please? Half of our CD drivers assume one order of >control/addr_type field and another half assume another order, Here's what I get using -current as of Feb 01 96 on an i486 box with Buslogic BT747S SCSI Host adapter and a sanyo CRD-254S CD-Rom drive: Audio CD, 4 tracks audio: Audio status = 0, current track = 1, current position = 0:00.02 Left volume = 255, right volume = 255 Starting track = 1, ending track = 4, TOC size = 42 bytes track start duration block length type ------------------------------------------------- 1 16:01.00 0:03.00 71925 75 audio 2 16:02.00 0:03.00 72000 75 audio 7 16:03.00 0:03.00 72075 75 data 58 16:04.00 128:16.58 72150 -72108 data end 0:02.42 - 42 - - Data CD: Audio status = 0, current track = 1, current position = 0:01.02 Left volume = 255, right volume = 255 Starting track = 1, ending track = 1, TOC size = 18 bytes track start duration block length type ------------------------------------------------- 1 20:01.00 124:19.34 89925 -89907 audio end 0:02.18 - 18 - - Does not look correct to me... maybe that helps you. Regards, Mickey -- (__) (@@) Andreas S. Wetzel E-mail: mickey@deadline.snafu.de /-------\/ Utrechter Strasse 41 Web: http://deadline.snafu.de/ / | || 13347 Berlin Voice: <+4930> 456 81 68 * ||----|| Germany Fax/Data: <+4930> 455 19 57 ~~ ~~ From owner-freebsd-current Thu Feb 1 18:22:33 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id SAA22973 for current-outgoing; Thu, 1 Feb 1996 18:22:33 -0800 (PST) Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id SAA22967 for ; Thu, 1 Feb 1996 18:22:28 -0800 (PST) Received: from sax.sax.de by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id DAA09078 for ; Fri, 2 Feb 1996 03:22:26 +0100 Received: by sax.sax.de (8.6.11/8.6.12-s1) with UUCP id DAA09037 for freebsd-current@FreeBSD.org; Fri, 2 Feb 1996 03:22:25 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.7.3/8.6.9) id CAA02536 for freebsd-current@FreeBSD.org; Fri, 2 Feb 1996 02:52:42 +0100 (MET) From: J Wunsch Message-Id: <199602020152.CAA02536@uriah.heep.sax.de> Subject: Re: Multiscreen, Bell & Talk To: freebsd-current@FreeBSD.org (FreeBSD-current users) Date: Fri, 2 Feb 1996 02:52:42 +0100 (MET) Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: from "=?KOI8-R?Q?=E1=CE=C4=D2=C5=CA_=FE=C5=D2=CE=CF=D7?=" at Feb 1, 96 06:28:36 pm X-Phone: +49-351-2012 669 X-Mailer: ELM [version 2.4 PL23] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-current@FreeBSD.org Precedence: bulk As =?KOI8-R?Q?=E1=CE=C4=D2=C5=CA_=FE=C5=D2=CE=CF=D7?= wrote: > > Imagine you work at multiscreen console and someone tries to talk you. > And talk requests comes to another (not current) screen, so you may > even never notice them. pcvt ever did ring the bell regardless of the vty currently active. I think SCO does not, and so syscons does not (?). -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-current Thu Feb 1 21:05:55 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id VAA11401 for current-outgoing; Thu, 1 Feb 1996 21:05:55 -0800 (PST) Received: from ki.net (root@ki.net [142.77.249.8]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id VAA11348 Thu, 1 Feb 1996 21:05:26 -0800 (PST) Received: (from scrappy@localhost) by ki.net (8.7.3/8.7.3) id AAA00389; Fri, 2 Feb 1996 00:05:20 -0500 (EST) Date: Fri, 2 Feb 1996 00:05:19 -0500 (EST) From: "Marc G. Fournier" To: stable@freebsd.org, current@freebsd.org Subject: PCI-SC200 SCSI Controller on ACER AP43 486 Motherboard Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org Precedence: bulk Hi... I asked earlier about this, but figured out a little bit more detail that might help. First, I'm trying to get a PCI-SC200 controller running on a 486DX4-100 ACER PCI motherboard (the motherboard has BIOS support for the 53c810). When I boot up, just before F1-FreeBSD comes up, the SCSI controller comes up, and probes the SCSI devices, and finds all three of my drives, therefore I'm assuming that the controller works. After hitting F1, and hitting return at 'Boot:', the operating system also find the ncr0 device, with a message of (not 100% exact): ncr0: <53c810> rev 2 int a irq 12 on pci0:11 After which, it panics and reboots. So, I'm assuming that FreeBSD is properly finding the controller. Now, one thing I hadn't thought about in the last, which is prompting me to write a new "query". I have an ATI Mach64 PCI 4M video card in this machine, that on a normal boot (without the PCI-SC200 installed) as: FreeBSD 2.1-STABLE #5: Thu Feb 1 23:29:03 EST 1996 scrappy@ki.net:/home/stable/sys/compile/kinet CPU: i486 DX4 (486-class CPU) Origin = "GenuineIntel" Id = 0x480 Stepping=0 Features=0x3 real memory = 16777216 (16384K bytes) avail memory = 14807040 (14460K bytes) Probing for devices on PCI bus 0: chip0 rev 49 on pci0:5 vga0 rev 0 on pci0:15 Probing for devices on the ISA bus: It didn't click in the first time that the failure was occuring between findign the ncr0 and not finding the vga0, but I'm not sure if that is relevant. Where does the OS "look for" the sdx devices? ie. should it be probing for the SCSI devices before finding the vga0 device? Or sometime after that? My first assumption is that it should be before, right after finding the controller itself. Hopefully this is better detail then my last one. I'm sending this to the -current list as well, as this may be something that *was* a known problem and has been since fixed in -current. I had thought about just grabbing ncr.c and ncrreg.h from -current and plugging it in, but didn't figure that was a wise thing to do (a diff between -stable/-current shows alot of changes, to the extent of defines totally being renamed) I have no problems with having to reboot and test out things on this machine to get it working, so suggestions/recommendations are most welcome. Thanks... Marc G. Fournier | POP Mail Telnet Acct DNS Hosting System | WWW Services Database Services | Knowledge, Administrator | | Information and scrappy@ki.net | WWW: http://www.ki.net | Communications, Inc From owner-freebsd-current Thu Feb 1 21:23:21 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id VAA14436 for current-outgoing; Thu, 1 Feb 1996 21:23:21 -0800 (PST) Received: from time.cdrom.com (time.cdrom.com [192.216.222.226]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id VAA14425 for ; Thu, 1 Feb 1996 21:23:15 -0800 (PST) Received: (from jkh@localhost) by time.cdrom.com (8.7.3/8.6.9) id VAA00808 for current@freebsd.org; Thu, 1 Feb 1996 21:23:12 -0800 (PST) Date: Thu, 1 Feb 1996 21:23:12 -0800 (PST) From: "Jordan K. Hubbard" Message-Id: <199602020523.VAA00808@time.cdrom.com> To: current@freebsd.org Subject: cdcontrol appears to be broken Sender: owner-current@freebsd.org Precedence: bulk jkh@time-> cdcontrol -f cd0 Compact Disc Control Utility, Version 1.0 Type `?' for command list cd> play 1 99 Ambiguous command cd> Try any form of "play" you like and you'll only get the same response - Ambiguous command. Jordan From owner-freebsd-current Fri Feb 2 09:05:11 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id JAA00986 for current-outgoing; Fri, 2 Feb 1996 09:05:11 -0800 (PST) Received: from who.cdrom.com (who.cdrom.com [192.216.222.3]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id JAA00973 Fri, 2 Feb 1996 09:05:09 -0800 (PST) Received: from ki.net (root@ki.net [142.77.249.8]) by who.cdrom.com (8.6.12/8.6.11) with ESMTP id IAA00358 ; Fri, 2 Feb 1996 08:53:26 -0800 Received: (from scrappy@localhost) by ki.net (8.7.3/8.7.3) id LAA06010; Fri, 2 Feb 1996 11:35:53 -0500 (EST) Date: Fri, 2 Feb 1996 11:35:52 -0500 (EST) From: "Marc G. Fournier" To: current@freebsd.org cc: stable@freebsd.org, hackers@freebsd.org Subject: Re: ASUS PCI SC-200 under -stable? In-Reply-To: <199602021215.AA17042@Sysiphos> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org Precedence: bulk On Fri, 2 Feb 1996, Stefan Esser wrote: > On Feb 1, 22:19, "Marc G. Fournier" wrote: > } Subject: ASUS PCI SC-200 under -stable? > } > } Hi... > } > } I just picked up an ASUS PCI SC-200 SCSI controller and tried > } to install it on a -stable kernel, and it failed to boot. > } > } The "BIOS" finds it, and the drives, and FreeBSD seems to find > } it, or at least, it prints up what I expect it to in the boot phase. > } It finds it at the right INT/IRQ, and puts it on 'pci0:11', all as I > } expect. > > Which IRQ does it find ? > Are you sure that IRQ has not been assigned to some > ISA device ? > I've tried both 9 and 12, with the same results. Looking through dmesg on a "good boot" (using an Adaptec 1542CF controller instead), there is nothing listed as being at either of those IRQs: sio @ 4 and 3 lp @ 7 ether @ 10 vt0 @ 1 fd @ 6 And that's it, at least according to dmesg > Could you please try booting the kernel up to the panic, > and then boot some other kernel that is known to work. That kernel is actually known to work, but I don't have any kernel that works with the PCI SCSI controller. I'm running the exact same kernel with the aha driver and ncr driver enabled. > Check, whether the second kernel can get at the first > one's message buffer (i.e. whether 'dmesg' still gets > at the messages from the failed boot attempt ...) > Assuming I understand what you mean here, I have tried this, and it doesn't work. dmesg only gets the "current bootup" > Guess there is some hardware configuration proble, > e.g. the card might be jumpered to use some PCI > interrupt line other than IntA. > Checked that too, even tried a different slot. I did a follow-up posting to current@/stable@ with a few more details, like the fact that on a clean boot, my "PCI" devices come up as: Probing for devices on PCI bus 0: chip0 rev 49 on pci0:5 vga0 rev 0 on pci0:15 Probing for devices on the ISA bus: If I install the NCR, I get chip0, then ncr0 on pci0:11, and at that point, it panics. So, it is finding the ncr0 device, and even at the IRQ/INT that I'm expecting it at, but its either failing at the SCSI probe part (where it looks for the drives) or, if the probe for vga0 is before that (not sure of ordering here), its failing to find the vga0 device. The vga0 device is an ATI Mach64 PCI w/ 4M VRAM...in case that clicks something somewhere? > Seems fine except for the fact, that there are quite > a number of devices, that surely don't all fit into > your system :) > Was worried I might have missed something... > And I now think, that one of them conflicts with the > IRQ assigned to the NCR ... > Any idea of which? Again, it is finding my SCSI card, as is the BIOS on bootup, it just seems to either be failing at the drive probe, or at the vga0 probe...depending on which ordering is correct. Marc G. Fournier | POP Mail Telnet Acct DNS Hosting System | WWW Services Database Services | Knowledge, Administrator | | Information and scrappy@ki.net | WWW: http://www.ki.net | Communications, Inc From owner-freebsd-current Fri Feb 2 09:05:18 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id JAA01028 for current-outgoing; Fri, 2 Feb 1996 09:05:18 -0800 (PST) Received: from who.cdrom.com (who.cdrom.com [192.216.222.3]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id JAA00989 for ; Fri, 2 Feb 1996 09:05:11 -0800 (PST) Received: from sequent.kiae.su (sequent.kiae.su [144.206.136.6]) by who.cdrom.com (8.6.12/8.6.11) with SMTP id DAA06285 for ; Fri, 2 Feb 1996 03:47:35 -0800 Received: by sequent.kiae.su id AA27919 (5.65.kiae-2 ); Fri, 2 Feb 1996 14:41:10 +0300 Received: by sequent.KIAE.su (UUMAIL/2.0); Fri, 2 Feb 96 14:41:08 +0300 Received: (from ache@localhost) by ache.dialup.ru (8.7.3/8.7.3) id OAA00563; Fri, 2 Feb 1996 14:29:18 +0300 (MSK) To: current@freebsd.org, "Jordan K. Hubbard" References: <199602020523.VAA00808@time.cdrom.com> In-Reply-To: <199602020523.VAA00808@time.cdrom.com>; from "Jordan K. Hubbard" at Thu, 1 Feb 1996 21:23:12 -0800 (PST) Message-Id: Organization: Olahm Ha-Yetzirah Date: Fri, 2 Feb 1996 14:29:18 +0300 (MSK) X-Mailer: Mail/@ [v2.42 FreeBSD] From: =?KOI8-R?Q?=E1=CE=C4=D2=C5=CA_=FE=C5=D2=CE=CF=D7?= (aka Andrey A. Chernov, Black Mage) X-Class: Fast Subject: Re: cdcontrol appears to be broken Lines: 17 Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org Precedence: bulk In message <199602020523.VAA00808@time.cdrom.com> Jordan K. Hubbard writes: >cd> play 1 99 >Ambiguous command >cd> >Try any form of "play" you like and you'll only get the same response - >Ambiguous command. It was logstanding bug, I already fix it in -current. -- Andrey A. Chernov : And I rest so composedly, /Now, in my bed, ache@astral.msk.su : That any beholder /Might fancy me dead - http://dt.demos.su/~ache : Might start at beholding me, /Thinking me dead. RELCOM Team,FreeBSD Team : E.A.Poe From "For Annie" 1849 From owner-freebsd-current Fri Feb 2 09:07:42 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id JAA01597 for current-outgoing; Fri, 2 Feb 1996 09:07:42 -0800 (PST) Received: from cocoa.ops.neosoft.com (root@cocoa.ops.neosoft.com [206.109.5.227]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id JAA01493 Fri, 2 Feb 1996 09:07:20 -0800 (PST) Received: (from dbaker@localhost) by cocoa.ops.neosoft.com (8.6.12/8.6.12) id JAA06138; Fri, 2 Feb 1996 09:07:34 -0600 Date: Fri, 2 Feb 1996 09:07:32 -0600 (CST) From: Daniel Baker X-Sender: dbaker@cocoa.ops.neosoft.com To: Joerg Wunsch cc: freebsd-questions@freebsd.org, freebsd-current@freebsd.org Subject: Re: compiling current kernel In-Reply-To: <199602010806.JAA25852@uriah.heep.sax.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org Precedence: bulk Uggg, I forgot to do a make install, as the make world didn't work the first time, and it finished just with a 'make'. Little stupid mistake... On Thu, 1 Feb 1996, J Wunsch wrote: > As Daniel Baker wrote: > > > > I have finished makeworld and am trying to make a -current kernel, but > > I get this message: > > > > cocoa# config COCOA > > Removing old directory ../../compile/COCOA: Done. > > Unknown % construct in generic makefile: %SFILES > > When running -current, update your config(8) properly. > > -- > cheers, J"org > > joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE > Never trust an operating system you don't have sources for. ;-) > Daniel -- Daniel Baker - Daniel@Cuckoo.COM "Huhuhu, thank you, drive through please" From owner-freebsd-current Fri Feb 2 09:16:33 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id JAA03229 for current-outgoing; Fri, 2 Feb 1996 09:16:33 -0800 (PST) Received: from marble.eps.nagoya-u.ac.jp (marble.eps.nagoya-u.ac.jp [133.6.57.68]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id JAA03200 for ; Fri, 2 Feb 1996 09:16:18 -0800 (PST) Received: from marble.eps.nagoya-u.ac.jp (localhost [127.0.0.1]) by marble.eps.nagoya-u.ac.jp (8.7.3+2.6Wbeta5/3.3W9) with ESMTP id CAA00247; Sat, 3 Feb 1996 02:15:52 +0900 (JST) Message-Id: <199602021715.CAA00247@marble.eps.nagoya-u.ac.jp> To: davidg@Root.COM Cc: current@FreeBSD.org Subject: Re: TSS broken In-Reply-To: Your message of "Thu, 01 Feb 1996 03:28:58 -0800" References: <199602011128.DAA01552@Root.COM> X-Mailer: Mew beta version 0.96 on Emacs 19.28.1, Mule 2.3 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Date: Sat, 03 Feb 1996 02:15:50 +0900 From: KATO Takenori Sender: owner-current@FreeBSD.org Precedence: bulk > you've misunderstood the operation of the 'leal' instruction. The > code as I've written it appears to be correct. Your code depends on compiler options. I know the kernel should be compiled only with '-O', but I usually do with -fomit-frame-pointer option. After I applied the change of swtch, the kernel compiled with -fomit-frame-pointer causes panic. When cpu_switch restores context, saved eip is restored as movl PCB_EIP(%edx),%eax movl %eax,(%esp) After this operation caller address of savectx overwrites argument to savectx. So esp of child process just after 'call _savectx' points the argument to bcopy. If vm_machdep.c is compiled without -fomit-frame-pointer, esp is restored by: leal -16(%ebp),%esp and the popl and ret operations works correctly. On the other hand, if vm_machdep.c is compiled with -fomit-frame-pointer, esp is restored by: addl $24,%esp Because this code assumes esp points argument to savectx, popl operations restore the registers from wrong addresses, and also ret operation clobbers eip. The conclusion is simple. I should compile without -fomit-frame-pointer. ---- KATO Takenori Dept. Earth Planet. Sci., Nagoya Univ., Nagoya 464-01 Voice: +81-52-789-2529 Fax: +81-52-789-3033 From owner-freebsd-current Fri Feb 2 10:02:26 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id KAA08344 for current-outgoing; Fri, 2 Feb 1996 10:02:26 -0800 (PST) Received: from cocoa.ops.neosoft.com (root@cocoa.ops.neosoft.com [206.109.5.227]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id KAA08315 Fri, 2 Feb 1996 10:02:08 -0800 (PST) Received: (from dbaker@localhost) by cocoa.ops.neosoft.com (8.7.3/8.6.12) id MAA01042; Fri, 2 Feb 1996 12:00:53 -0600 (CST) Date: Fri, 2 Feb 1996 12:00:50 -0600 (CST) From: Daniel Baker X-Sender: dbaker@cocoa.ops.neosoft.com To: freebsd-questions@freebsd.org, freebsd-current@freebsd.org Subject: SB16 & Current Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org Precedence: bulk I had my SB16 basically working on the 21-Release, but now that I'm running current, not everything work.. XCD works fine, but when I try to cat to /dev/dsp0 for a test, I get: Sound: DMA timed out - IRQ/DRQ config error? on my console Then, when I try and use sox, I get: isa_dmadone_nobounce: channel 1 not busy I don't think this is a conflict, as at one time, all of this worked... Any ideas? -- Daniel Baker - Daniel@Cuckoo.COM "Huhuhu, thank you, drive through please" From owner-freebsd-current Fri Feb 2 10:28:24 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id KAA10193 for current-outgoing; Fri, 2 Feb 1996 10:28:24 -0800 (PST) Received: from Root.COM (implode.Root.COM [198.145.90.17]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id KAA10024 for ; Fri, 2 Feb 1996 10:25:18 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by Root.COM (8.6.12/8.6.5) with SMTP id KAA07931; Fri, 2 Feb 1996 10:25:17 -0800 Message-Id: <199602021825.KAA07931@Root.COM> X-Authentication-Warning: implode.Root.COM: Host localhost didn't use HELO protocol To: KATO Takenori cc: current@FreeBSD.org Subject: Re: TSS broken In-reply-to: Your message of "Sat, 03 Feb 1996 02:15:50 +0900." <199602021715.CAA00247@marble.eps.nagoya-u.ac.jp> From: David Greenman Reply-To: davidg@Root.COM Date: Fri, 02 Feb 1996 10:25:17 -0800 Sender: owner-current@FreeBSD.org Precedence: bulk >> you've misunderstood the operation of the 'leal' instruction. The >> code as I've written it appears to be correct. > >Your code depends on compiler options. > >I know the kernel should be compiled only with '-O', but I usually do >with -fomit-frame-pointer option. After I applied the change of >swtch, the kernel compiled with -fomit-frame-pointer causes panic. > >When cpu_switch restores context, saved eip is restored as > movl PCB_EIP(%edx),%eax > movl %eax,(%esp) >After this operation caller address of savectx overwrites argument to >savectx. So esp of child process just after 'call _savectx' points >the argument to bcopy. You are right. I didn't realize that cpu_switch() clobbers the top of stack with the EIP and then does a return, making the assumption that the return address wasn't previously popped off. The change I made is wrong - I didn't realize the interaction between cpu_fork and cpu_switch. I'll back out that change. -DG David Greenman Core Team/Principal Architect, The FreeBSD Project From owner-freebsd-current Fri Feb 2 11:09:37 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id JAA01641 for current-outgoing; Fri, 2 Feb 1996 09:07:52 -0800 (PST) Received: from who.cdrom.com (who.cdrom.com [192.216.222.3]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id JAA01528 for ; Fri, 2 Feb 1996 09:07:34 -0800 (PST) Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by who.cdrom.com (8.6.12/8.6.11) with ESMTP id CAA05835 for ; Fri, 2 Feb 1996 02:24:02 -0800 Received: from sax.sax.de by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id LAA23545 for ; Fri, 2 Feb 1996 11:21:24 +0100 Received: by sax.sax.de (8.6.11/8.6.12-s1) with UUCP id LAA11943 for freebsd-current@FreeBSD.org; Fri, 2 Feb 1996 11:21:23 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.7.3/8.6.9) id LAA04712 for freebsd-current@FreeBSD.org; Fri, 2 Feb 1996 11:05:31 +0100 (MET) From: J Wunsch Message-Id: <199602021005.LAA04712@uriah.heep.sax.de> Subject: Re: list of major device numbers? To: freebsd-current@freebsd.org (FreeBSD-current users) Date: Fri, 2 Feb 1996 11:05:30 +0100 (MET) Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199602020602.WAA14635@ref.tfs.com> from "Julian Elischer" at Feb 1, 96 10:02:29 pm X-Phone: +49-351-2012 669 X-Mailer: ELM [version 2.4 PL23] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-current@freebsd.org Precedence: bulk As Julian Elischer wrote: > > > > > > > Here's the list I have so far: > > Ok, we should check this in asap, and it should probably be in 2.1 > too or SOMEthing.. > (so that we can keep them in sync) What are the plans to dynamicalize the assignment of major numbers? I think, except for a few ``well-known'' devices that might be important for the bootstrap, everything else could be handled in a dynamic scenario. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-current Fri Feb 2 11:09:42 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id JAA02144 for current-outgoing; Fri, 2 Feb 1996 09:09:28 -0800 (PST) Received: from who.cdrom.com (who.cdrom.com [192.216.222.3]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id JAA02007 for ; Fri, 2 Feb 1996 09:09:04 -0800 (PST) Received: from grumble.grondar.za (root@grumble.grondar.za [196.7.18.130]) by who.cdrom.com (8.6.12/8.6.11) with ESMTP id AAA04884 for ; Fri, 2 Feb 1996 00:41:39 -0800 Received: from localhost (mark@localhost [127.0.0.1]) by grumble.grondar.za (8.7.3/8.7.3) with SMTP id KAA13323 for ; Fri, 2 Feb 1996 10:39:58 +0200 (SAT) Message-Id: <199602020839.KAA13323@grumble.grondar.za> X-Authentication-Warning: grumble.grondar.za: Host mark@localhost [127.0.0.1] didn't use HELO protocol To: current@freebsd.org Subject: New DES library is close! Date: Fri, 02 Feb 1996 10:39:49 +0200 From: Mark Murray Sender: owner-current@freebsd.org Precedence: bulk Hi folks The new DES library is close to commit! It has taken long because the Aussie author has been developing it as part of a larger library (SSL/Crypto), and this project was delayed for many reasons. Anyway - before I start the work, I will do some reminding: It has already been agreed that: 1) The new library is so far in advance of the old one that it will simply be imported and the old pushed into the Attic. 2) The new library will be imported into secure/lib/libdes. The current one is in eBones/des. 3) The header file will be installed into /usr/include/des.h (the current one is in /usr/include/kerberosIV/des.h). In checking out the code, a small problem has (again) reared up its ugly head; there is a name conflict between two functions in separate libraries. There is a documented function called des_set_key in libdes, which in the current library is not used (internally or externally). This function also exists in libkrb (a Kerberos/eBones lib) and is used only by rlogin{d} and rsh{d}. As this second use of this function (name) is undocumented, I propose to change it. The new code has a des_set_key which is referred to in a few places throughout the library, and as it is a bsd4.4 function (documented in the 4.4 PRM) I think we should keep it. Also this library is now maintained code, and I believe we should keep changes to a minimum. Comments? Flames? Praise? Ca$h? M -- Mark Murray 46 Harvey Rd, Claremont, Cape Town 7700, South Africa +27 21 61-3768 GMT+0200 Finger mark@grondar.za for PGP key From owner-freebsd-current Fri Feb 2 12:10:05 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id MAA19681 for current-outgoing; Fri, 2 Feb 1996 12:10:05 -0800 (PST) Received: from news1.gtn.com (news1.gtn.com [192.109.159.3]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id MAA19644 Fri, 2 Feb 1996 12:10:01 -0800 (PST) Received: (from uucp@localhost) by news1.gtn.com (8.7.2/8.7.2) id VAA26017; Fri, 2 Feb 1996 21:00:23 +0100 (MET) Received: from knobel.gun.de (localhost [127.0.0.1]) by knobel.gun.de (8.7.3/8.7.3) with SMTP id TAA00679; Fri, 2 Feb 1996 19:45:42 +0100 (MET) Date: Fri, 2 Feb 1996 19:45:42 +0100 (MET) From: Andreas Klemm To: Steve Tan cc: questions@FreeBSD.org, current@FreeBSD.org Subject: Re: newbie : How write to DOS Floppy ? In-Reply-To: <199602020101.RAA06440@iceland.it.earthlink.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@FreeBSD.org Precedence: bulk On Thu, 1 Feb 1996, Steve Tan wrote: > I'm not sure if this is the right place to ask, but I'm > trying to figure out how to write files to a DOS disk, my > floppy drive. I didn't see any info in the FAQ's or > installation guides. Best is to install mtools. With mdir, mcopy and such you are able to write directly to the disk. > I believe I need to mount /dev/fd0 or /dev/rmt0 , but I can't > find the specific command to use. mount -t msdos /dev/fd0 /mnt > I'm using BSD to develop CGI perl scripts and need to transfer > them to a PC running Win95. If I were you, I'd buy 2 ethernet cards, a RG58 cable, two 50 ohm terminators and build up a network. Install samba (-> ports section) on your FreeBSD box. Then you can directly mount a via samba exported filesystem to your Windows 95 box. Better, faster, trickier, easier, than to use a floppy to transfer files... Andreas /// -- andreas@knobel.gun.de /\/\___ Wiechers & Partner Datentechnik GmbH Andreas Klemm ___/\/\/ - Support Unix - aklemm@wup.de - \/ ftp://sunsite.unc.edu/pub/Linux/system/Printing/aps-491.tgz apsfilter - magic print filter 4lpd >>> knobel is powered by FreeBSD <<< From owner-freebsd-current Fri Feb 2 12:49:25 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id MAA23250 for current-outgoing; Fri, 2 Feb 1996 12:49:25 -0800 (PST) Received: from ki.net (root@ki.net [142.77.249.8]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id MAA23226 Fri, 2 Feb 1996 12:49:01 -0800 (PST) Received: (from scrappy@localhost) by ki.net (8.7.3/8.7.3) id PAA00913; Fri, 2 Feb 1996 15:48:42 -0500 (EST) Date: Fri, 2 Feb 1996 15:48:40 -0500 (EST) From: "Marc G. Fournier" To: stable@freebsd.org, current@freebsd.org Subject: PR: ASUS PC-SC200 panicks at _scsi_attachdevs+0x20 Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org Precedence: bulk Hi... I just submitted a problem report for the problem I'm having with the PCI-SC200 card, mainly because I've now got what I think is sufficient data. Today, I realized that I didn't have DDB enabled on my kernel, which is why I could never get a trace on the panic, so, here is what I think is the pertinent data, in its entirety, including teh config file for the kernel I'm using to debug this with. I'm sending this to current, as this might be a problem that was known to be in stable, has been fixed in current, but hasn't been brought back to stable yet...well, I'm hoping it was a known problem at least :( Thanks... ----[ outcome of booting with ASUS PC-SC200 controller ]---- FreeBSD 2.1-STABLE #6: Fri Feb 2 14:09:42 EST 1996 scrappy@ki.net:/home/stable/sys/compile/kinet CPU: i486 DX4 (486-class CPU) Origin = "GenuineIntel" Id = 0x480 Stepping=0 Features=0x3 real memory = 16777216 (16384K bytes) avail memory = 14716928 (14372K bytes) Probing for devices on PCI bus 0: chip0 rev 49 on pci0:5 ncr0 rev 2 int a irq 12 on pci0:11 Fatal Trap 12: page fault while in kernel mode fault virtual address = 0x7 fault code = supervisor read, page not present instruction pointer = 0x8:0xf0173724 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = 0 () interrupt mask = net tty bio kernel: type 12, code = 0 Stopped at _scsi_attachdevs+0x20: cmpb $0,0x7(%ebx) db> tra _scsi_attachdevs() at _scsi_attachdevs+0x20 _ncr_attach() at _ncr_attach+0x192 _pci_bus_config() at _pci_bus_config+0x4b8 _pci_configure() at _pci_configure+0x51 _configure() at _configure+0x2a _cpu_startup() at _cpu_startup+4b6 _main() at _main+0x36 begin() at begin+0x6b db> -----[ config file for kernel being used for testing ]----- machine "i386" cpu "I486_CPU" ident kinet maxusers 32 options "CHILD_MAX=128" options "OPEN_MAX=128" options USER_LDT #allow user-level control of i386 ldt options QUOTA #enable disk quotas options DDB options DODUMP options INET #InterNETworking options FFS #Berkeley Fast Filesystem options NFS #Network Filesystem options MSDOSFS #MSDOS Filesystem options "CD9660" #ISO 9660 Filesystem options PROCFS #Process filesystem options "COMPAT_43" #Compatible with BSD 4.3 options "SCSI_DELAY=15" #Be pessimistic about Joe SCSI device options BOUNCE_BUFFERS #include support for DMA bounce buffers options UCONSOLE #Allow users to grab the console options SYSVSHM options SYSVSEM options SYSVMSG config kernel root on sd0 controller isa0 controller pci0 controller fdc0 at isa? port "IO_FD1" bio irq 6 drq 2 vector fdintr disk fd0 at fdc0 drive 0 controller ncr0 controller aha0 at isa? port "IO_AHA0" bio irq ? drq 5 vector ahaintr controller scbus0 device sd0 device st0 device vt0 at isa? port "IO_KBD" tty irq 1 vector pcrint options "PCVT_FREEBSD=210" # pcvt running on FreeBSD 2.1 options XSERVER # include code for XFree86 device npx0 at isa? port "IO_NPX" irq 13 vector npxintr device sio0 at isa? port "IO_COM1" tty irq 4 vector siointr device sio1 at isa? port "IO_COM2" tty irq 3 vector siointr device lpt0 at isa? port? tty irq 7 vector lptintr device ep0 at isa? port 0x300 net irq 10 vector epintr pseudo-device loop pseudo-device speaker #Play IBM BASIC-style noises out your speaker pseudo-device ether pseudo-device log pseudo-device tun 1 pseudo-device pty 64 pseudo-device bpfilter 4 ----[ dmesg output for same system without the ncr controller ]---- FreeBSD 2.1-STABLE #6: Fri Feb 2 14:09:42 EST 1996 scrappy@ki.net:/home/stable/sys/compile/kinet CPU: i486 DX4 (486-class CPU) Origin = "GenuineIntel" Id = 0x480 Stepping=0 Features=0x3 real memory = 16777216 (16384K bytes) avail memory = 14716928 (14372K bytes) Probing for devices on PCI bus 0: chip0 rev 49 on pci0:5 vga0 rev 0 on pci0:15 Probing for devices on the ISA bus: vt0 at 0x60-0x6f irq 1 on motherboard vt0: generic, 80 col, color, 8 scr, mf2-kbd, [R3.20-b24] sio0 at 0x3f8-0x3ff irq 4 on isa sio0: type 16550A sio1 at 0x2f8-0x2ff irq 3 on isa sio1: type 16550A lpt0 at 0x378-0x37f irq 7 on isa lpt0: Interrupt-driven port lp0: TCP/IP capable interface fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa fdc0: NEC 72065B fd0: 1.44MB 3.5in aha0 at 0x330-0x333 irq 11 drq 5 on isa aha0 waiting for scsi devices to settle (aha0:0:0): "CONNER CFA540S 13B0" type 0 fixed SCSI 2 sd0(aha0:0:0): Direct-Access 515MB (1056708 512 byte sectors) (aha0:1:0): "QUANTUM LPS340S 020B" type 0 fixed SCSI 2 sd1(aha0:1:0): Direct-Access 327MB (670506 512 byte sectors) (aha0:2:0): "QUANTUM LP240S GM240S01X 4.6" type 0 fixed SCSI 2 sd2(aha0:2:0): Direct-Access 234MB (479350 512 byte sectors) 1 3C5x9 board(s) on ISA found at 0x300 ep0 at 0x300-0x30f irq 10 on isa ep0: aui/bnc[*BNC*] address 00:a0:24:0a:6d:ce irq 10 npx0 on motherboard npx0: INT 16 interface Marc G. Fournier | POP Mail Telnet Acct DNS Hosting System | WWW Services Database Services | Knowledge, Administrator | | Information and scrappy@ki.net | WWW: http://www.ki.net | Communications, Inc From owner-freebsd-current Fri Feb 2 13:45:38 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id NAA28519 for current-outgoing; Fri, 2 Feb 1996 13:45:38 -0800 (PST) Received: from ibp.ibp.fr (ibp.ibp.fr [132.227.60.30]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id NAA28500 for ; Fri, 2 Feb 1996 13:45:29 -0800 (PST) Received: from blaise.ibp.fr (blaise.ibp.fr [132.227.60.1]) by ibp.ibp.fr (8.6.12/jtpda-5.0) with ESMTP id WAA27222 ; Fri, 2 Feb 1996 22:45:17 +0100 Received: from (uucp@localhost) by blaise.ibp.fr (8.6.12/jtpda-5.0) with UUCP id WAA06098 ; Fri, 2 Feb 1996 22:44:53 +0100 Received: (from roberto@localhost) by keltia.freenix.fr (8.7.3/keltia-uucp-2.7) id WAA23947; Fri, 2 Feb 1996 22:19:54 +0100 (MET) From: Ollivier Robert Message-Id: <199602022119.WAA23947@keltia.freenix.fr> Subject: Re: ip_fw ordering of rules.. To: phk@critter.tfs.com (Poul-Henning Kamp) Date: Fri, 2 Feb 1996 22:19:53 +0100 (MET) Cc: nate@sri.MT.net, imb@scgt.oz.au, current@FreeBSD.org In-Reply-To: <1196.823215159@critter.tfs.com> from "Poul-Henning Kamp" at "Feb 1, 96 11:52:39 pm" X-Operating-System: FreeBSD 2.2-CURRENT ctm#1586 X-Mailer: ELM [version 2.4ME+ PL3 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.org Precedence: bulk It seems that Poul-Henning Kamp said: > It basically sorts so that the rule covering most addresses come first. > > It doesn't look at deny/pass in that context, so if you say: I'm coming a little bit late on the subject, but I think that we should remove the sorting altogether. Sorting make the software do things you don't expect (as in Poul-Henning's example). In that respect, anyone using ipfw can't afford the potential risk. > deny some specific port > allow the rest > > It will come out as: > allow everything > a deny rule never used. Sorting access lists is *evil*. -- Ollivier ROBERT -=- The daemon is FREE! -=- roberto@keltia.frmug.fr.net FreeBSD keltia.freenix.fr 2.2-CURRENT #1: Sun Jan 14 20:23:45 MET 1996 From owner-freebsd-current Fri Feb 2 14:31:43 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id OAA05432 for current-outgoing; Fri, 2 Feb 1996 14:31:43 -0800 (PST) Received: from sequent.kiae.su (sequent.kiae.su [144.206.136.6]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id OAA05377 for ; Fri, 2 Feb 1996 14:31:06 -0800 (PST) Received: by sequent.kiae.su id AA20142 (5.65.kiae-2 for current@freebsd.org); Sat, 3 Feb 1996 01:27:03 +0300 Received: by sequent.KIAE.su (UUMAIL/2.0); Sat, 3 Feb 96 01:27:02 +0300 Received: (from ache@localhost) by ache.dialup.ru (8.7.3/8.7.3) id BAA00265 for current@freebsd.org; Sat, 3 Feb 1996 01:09:59 +0300 (MSK) To: current@freebsd.org Message-Id: Organization: Olahm Ha-Yetzirah Date: Sat, 3 Feb 1996 01:09:59 +0300 (MSK) X-Mailer: Mail/@ [v2.42 FreeBSD] From: =?KOI8-R?Q?=E1=CE=C4=D2=C5=CA_=FE=C5=D2=CE=CF=D7?= (aka Andrey A. Chernov, Black Mage) X-Class: Fast Subject: I am about nuking cdplay Lines: 7 Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org Precedence: bulk Because cdcontrol is superset. Anybody disagree? -- Andrey A. Chernov : And I rest so composedly, /Now, in my bed, ache@astral.msk.su : That any beholder /Might fancy me dead - http://dt.demos.su/~ache : Might start at beholding me, /Thinking me dead. RELCOM Team,FreeBSD Team : E.A.Poe From "For Annie" 1849 From owner-freebsd-current Fri Feb 2 14:32:30 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id OAA05628 for current-outgoing; Fri, 2 Feb 1996 14:32:30 -0800 (PST) Received: from precipice.shockwave.com (precipice.shockwave.com [171.69.108.33]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id OAA05611 for ; Fri, 2 Feb 1996 14:32:26 -0800 (PST) Received: (from pst@localhost) by precipice.shockwave.com (8.7.3/8.7.3) id OAA01708 for current@freebsd.org; Fri, 2 Feb 1996 14:31:53 -0800 (PST) Date: Fri, 2 Feb 1996 14:31:53 -0800 (PST) From: Paul Traina Message-Id: <199602022231.OAA01708@precipice.shockwave.com> To: current@freebsd.org Subject: compiling the kernel with -O2 Sender: owner-current@freebsd.org Precedence: bulk has anyone determined if this is safe? From owner-freebsd-current Fri Feb 2 14:40:16 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id OAA06465 for current-outgoing; Fri, 2 Feb 1996 14:40:16 -0800 (PST) Received: from ref.tfs.com (ref.tfs.com [140.145.254.251]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id OAA06458 for ; Fri, 2 Feb 1996 14:40:14 -0800 (PST) Received: (from julian@localhost) by ref.tfs.com (8.6.12/8.6.9) id OAA16197; Fri, 2 Feb 1996 14:39:04 -0800 From: Julian Elischer Message-Id: <199602022239.OAA16197@ref.tfs.com> Subject: Re: list of major device numbers? To: joerg_wunsch@uriah.heep.sax.de Date: Fri, 2 Feb 1996 14:39:03 -0800 (PST) Cc: freebsd-current@freebsd.org In-Reply-To: <199602021005.LAA04712@uriah.heep.sax.de> from "J Wunsch" at Feb 2, 96 11:05:30 am X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-current@freebsd.org Precedence: bulk > > As Julian Elischer wrote: > > > > > > > > > > > Here's the list I have so far: > > > > Ok, we should check this in asap, and it should probably be in 2.1 > > too or SOMEthing.. > > (so that we can keep them in sync) > > What are the plans to dynamicalize the assignment of major numbers? I > think, except for a few ``well-known'' devices that might be important > for the bootstrap, everything else could be handled in a dynamic > scenario. if you specify (-1?) it will dynamically assign you one, but I need to change this so that it statrs at a higher number so as to not collide with devices that already statically have a spot.. of course you MUST have a devfs to make this work, (or have the modload program return the new major number) > > -- > cheers, J"org > > joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE > Never trust an operating system you don't have sources for. ;-) > From owner-freebsd-current Fri Feb 2 14:52:47 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id OAA08119 for current-outgoing; Fri, 2 Feb 1996 14:52:47 -0800 (PST) Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id OAA08094 for ; Fri, 2 Feb 1996 14:52:31 -0800 (PST) Received: from sax.sax.de by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id XAA15396; Fri, 2 Feb 1996 23:52:09 +0100 Received: by sax.sax.de (8.6.11/8.6.12-s1) with UUCP id XAA19099; Fri, 2 Feb 1996 23:52:07 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.7.3/8.6.9) id XAA06141; Fri, 2 Feb 1996 23:29:31 +0100 (MET) From: J Wunsch Message-Id: <199602022229.XAA06141@uriah.heep.sax.de> Subject: Re: cdcontrol appears to be broken To: jkh@time.cdrom.com (Jordan K. Hubbard) Date: Fri, 2 Feb 1996 23:29:31 +0100 (MET) Cc: current@FreeBSD.ORG Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199602020523.VAA00808@time.cdrom.com> from "Jordan K. Hubbard" at Feb 1, 96 09:23:12 pm X-Phone: +49-351-2012 669 X-Mailer: ELM [version 2.4 PL23] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-current@FreeBSD.ORG Precedence: bulk As Jordan K. Hubbard wrote: > > jkh@time-> cdcontrol -f cd0 > Compact Disc Control Utility, Version 1.0 > Type `?' for command list > > cd> play 1 99 > Ambiguous command > cd> > > Try any form of "play" you like and you'll only get the same response - > Ambiguous command. Well, it's not broken, it's only slightly weird. :-> Watch out for the capitalization in the usage summary... simply use `p', not `play'. :) -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-current Fri Feb 2 14:54:21 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id OAA08313 for current-outgoing; Fri, 2 Feb 1996 14:54:21 -0800 (PST) Received: from osti.rmt.utk.edu (OSTI.RMT.UTK.EDU [128.169.24.17]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id OAA08300 for ; Fri, 2 Feb 1996 14:54:15 -0800 (PST) Received: (from wolpert@localhost) by osti.rmt.utk.edu (8.6.12/8.6.12) id SAA25581; Fri, 2 Feb 1996 18:01:36 -0500 Date: Fri, 2 Feb 1996 18:01:36 -0500 From: Edward Wolpert Message-Id: <199602022301.SAA25581@osti.rmt.utk.edu> To: current@freebsd.org Subject: Problem compiling current (Feb 1) Sender: owner-current@freebsd.org Precedence: bulk Folks- I'm trying to compile current, as of Feb 1, after 8pm USA east standard time. I updated my includes and libs, and now I went after rebuilding the kernel. When I do, the i386/i386/genassym.c file complains about opt_sysvipc.h not being found. I haven't found the file in my area, nor in current elsewhere... When I do a make depend after doing a config on the build file, in the compile directory, the make depend gives the following output: wolpert osti [159] make depend cc -c -O -W -Wreturn-type -Wcomment -Wredundant-decls -Wimplicit -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Winline -nostdinc -I. -I../.. -I../../sys -I../../../include -DGENERIC -DI586_CPU -DI486_CPU -DI386_CPU -DSYSVMSG -DSYSVSEM -DSYSVSHM -DCOMPAT_LINUX -DUSER_LDT -DUCONSOLE -DBOUNCE_BUFFERS -DSCSI_DELAY=15 -DCOMPAT_43 -DPROCFS -DCD9660 -DMSDOSFS -DNFS -DFFS -DINET -DKERNEL -DTIMEZONE=0 -DDST=0 -DMAXUSERS=10 -UKERNEL ../../i386/i386/genassym.c ../../i386/i386/genassym.c:40: opt_sysvipc.h: No such file or directory *** Error code 1 Stop. Ideas? I sup everything but gnu and games. Do I need gnu? -- Virtually, Edward Wolpert ------------------------------ "Nothingness is the worm at the |wolpert@utk.edu | center of being." -Sartre |wolpert@osti.rmt.utk.edu | ------------------------------ Fnord! [DC 92 17 C1 7A 42 06 73 66 9D A9 00 52 07 6B 3B] From owner-freebsd-current Fri Feb 2 15:42:01 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id PAA17095 for current-outgoing; Fri, 2 Feb 1996 15:42:01 -0800 (PST) Received: from Sysiphos (Sysiphos.MI.Uni-Koeln.DE [134.95.212.10]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id PAA16991 Fri, 2 Feb 1996 15:41:14 -0800 (PST) Received: by Sysiphos id AA01725 (5.67b/IDA-1.5); Sat, 3 Feb 1996 00:40:49 +0100 Message-Id: <199602022340.AA01725@Sysiphos> From: se@zpr.uni-koeln.de (Stefan Esser) Date: Sat, 3 Feb 1996 00:40:48 +0100 In-Reply-To: "Marc G. Fournier" "PR: ASUS PC-SC200 panicks at _scsi_attachdevs+0x20" (Feb 2, 15:48) X-Mailer: Mail User's Shell (7.2.6 alpha(2) 7/9/95) To: "Marc G. Fournier" Subject: Re: PR: ASUS PC-SC200 panicks at _scsi_attachdevs+0x20 Cc: stable@freebsd.org, current@freebsd.org Sender: owner-current@freebsd.org Precedence: bulk On Feb 2, 15:48, "Marc G. Fournier" wrote: } Subject: PR: ASUS PC-SC200 panicks at _scsi_attachdevs+0x20 } } Hi... } } I just submitted a problem report for the problem I'm having } with the PCI-SC200 card, mainly because I've now got what I think is } sufficient data. Well, yes, having looked at it, I'd tend to agree :) } I'm sending this to current, as this might be a problem that } was known to be in stable, has been fixed in current, but hasn't been } brought back to stable yet...well, I'm hoping it was a known problem } at least :( Haven't checked for differences between -stable and -current in this area, but I have identified the failing instruction. See below ... } ncr0 rev 2 int a irq 12 on pci0:11 } } Fatal Trap 12: page fault while in kernel mode } fault virtual address = 0x7 } fault code = supervisor read, page not present } instruction pointer = 0x8:0xf0173724 } code segment = base 0x0, limit 0xfffff, type 0x1b } = DPL 0, pres 1, def32 1, gran 1 } processor eflags = interrupt enabled, resume, IOPL = 0 } current process = 0 () } interrupt mask = net tty bio } kernel: type 12, code = 0 } Stopped at _scsi_attachdevs+0x20: cmpb $0,0x7(%ebx) } db> tra } _scsi_attachdevs() at _scsi_attachdevs+0x20 } _ncr_attach() at _ncr_attach+0x192 } _pci_bus_config() at _pci_bus_config+0x4b8 } _pci_configure() at _pci_configure+0x51 } _configure() at _configure+0x2a } _cpu_startup() at _cpu_startup+4b6 } _main() at _main+0x36 } begin() at begin+0x6b } db> void scsi_attachdevs(scbus) struct scsibus_data *scbus; { int scsibus; struct scsi_link *sc_link_proto = scbus->adapter_link; if ( (scsibus = scsi_bus_conf(sc_link_proto)) == -1) { return; } /* * if the adapter didn't give us this, set a default * (compatibility with old adapter drivers) */ if(!(sc_link_proto->opennings)) { <=== openings is at offset 7 sc_link_proto->opennings = 1; } } Stopped at _scsi_attachdevs+0x20: cmpb $0,0x7(%ebx) <=== Looks as if scbus->adapter_link had not been correctly initialized ... But I checked the code in the NCR driver leading to scsi_attachdevs(), and it seems that np->sc_link is correctly allocated, and that it is dereferenced successfully just before the call np->sc_link.adapter = &ncr_switch; np->sc_link.device = &ncr_dev; np->sc_link.flags = 0; if(!scbus) return; scbus->adapter_link = &np->sc_link; { some unrelated code removed ... } scsi_attachdevs (scbus); And the access to scbus->opennings fails, but the flags component has been accessed just a few instructions before ... struct scsi_link { u_int8 target; /* targ of this dev */ u_int8 lun; /* lun of this dev */ u_int8 adapter_targ; /* what are we on the scsi bus */ u_int8 adapter_unit; /* e.g. the 0 in aha0 */ u_int8 adapter_bus; /* e.g. the 0 in bus0 */ u_int8 scsibus; /* the Nth scsibus */ u_int8 dev_unit; /* e.g. the 0 in sd0 */ u_int8 opennings; /* available operations */ u_int8 active; /* operations in progress */ u_int16 flags; /* flags that all devices have */ u_int16 quirks; /* device specific quirks */ ... } Don't currently understand, what's going on here ... Could you please print the value of scbus and scbus->adapter_link before the call to scsi_attachdevs() and the corresponding values within that function ? I don't see what's going on here, but I don't have a 2.1R tree checked out and can't easily build and boot a 2.1R kernel currently ... Regards, STefan -- Stefan Esser, Zentrum fuer Paralleles Rechnen Tel: +49 221 4706021 Universitaet zu Koeln, Weyertal 80, 50931 Koeln FAX: +49 221 4705160 ============================================================================== http://www.zpr.uni-koeln.de/~se From owner-freebsd-current Fri Feb 2 15:44:49 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id PAA17620 for current-outgoing; Fri, 2 Feb 1996 15:44:49 -0800 (PST) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id PAA17602 for ; Fri, 2 Feb 1996 15:44:44 -0800 (PST) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id QAA00880; Fri, 2 Feb 1996 16:43:35 -0700 From: Terry Lambert Message-Id: <199602022343.QAA00880@phaeton.artisoft.com> Subject: Re: list of major device numbers? To: joerg_wunsch@uriah.heep.sax.de Date: Fri, 2 Feb 1996 16:43:35 -0700 (MST) Cc: freebsd-current@freebsd.org In-Reply-To: <199602021005.LAA04712@uriah.heep.sax.de> from "J Wunsch" at Feb 2, 96 11:05:30 am X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org Precedence: bulk > > Ok, we should check this in asap, and it should probably be in 2.1 > > too or SOMEthing.. > > (so that we can keep them in sync) > > What are the plans to dynamicalize the assignment of major numbers? I > think, except for a few ``well-known'' devices that might be important > for the bootstrap, everything else could be handled in a dynamic > scenario. The plans are to replace major numbers with vnode instances generated from device registration information and specific to the reference instance for a given boot sequence, AFAIK. In other words, major and minor number are to be made meaningless. At the same time specfs will either go away entirely or be subsumed by devfs, assuming everything works out correctly. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-current Fri Feb 2 16:21:15 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id QAA22279 for current-outgoing; Fri, 2 Feb 1996 16:21:15 -0800 (PST) Received: from sequent.kiae.su (sequent.kiae.su [144.206.136.6]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id QAA22262 for ; Fri, 2 Feb 1996 16:20:36 -0800 (PST) Received: by sequent.kiae.su id AA04473 (5.65.kiae-2 ); Sat, 3 Feb 1996 03:18:57 +0300 Received: by sequent.KIAE.su (UUMAIL/2.0); Sat, 3 Feb 96 03:18:56 +0300 Received: (from ache@localhost) by ache.dialup.ru (8.7.3/8.7.3) id DAA00385; Sat, 3 Feb 1996 03:13:19 +0300 (MSK) To: current@FreeBSD.org, Paul Traina References: <199602022231.OAA01708@precipice.shockwave.com> In-Reply-To: <199602022231.OAA01708@precipice.shockwave.com>; from Paul Traina at Fri, 2 Feb 1996 14:31:53 -0800 (PST) Message-Id: Organization: Olahm Ha-Yetzirah Date: Sat, 3 Feb 1996 03:13:19 +0300 (MSK) X-Mailer: Mail/@ [v2.42 FreeBSD] From: =?KOI8-R?Q?=E1=CE=C4=D2=C5=CA_=FE=C5=D2=CE=CF=D7?= (aka Andrey A. Chernov, Black Mage) X-Class: Fast Subject: Re: compiling the kernel with -O2 Lines: 12 Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.org Precedence: bulk In message <199602022231.OAA01708@precipice.shockwave.com> Paul Traina writes: >has anyone determined if this is safe? I always run kernel with -O2. -- Andrey A. Chernov : And I rest so composedly, /Now, in my bed, ache@astral.msk.su : That any beholder /Might fancy me dead - http://dt.demos.su/~ache : Might start at beholding me, /Thinking me dead. RELCOM Team,FreeBSD Team : E.A.Poe From "For Annie" 1849 From owner-freebsd-current Fri Feb 2 16:37:20 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id QAA23384 for current-outgoing; Fri, 2 Feb 1996 16:37:20 -0800 (PST) Received: from rocky.sri.MT.net (rocky.sri.MT.net [204.182.243.10]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id QAA23370 for ; Fri, 2 Feb 1996 16:36:59 -0800 (PST) Received: (from nate@localhost) by rocky.sri.MT.net (8.6.12/8.6.12) id RAA25641; Fri, 2 Feb 1996 17:39:01 -0700 Date: Fri, 2 Feb 1996 17:39:01 -0700 From: Nate Williams Message-Id: <199602030039.RAA25641@rocky.sri.MT.net> To: Paul Traina Cc: current@FreeBSD.org Subject: Re: compiling the kernel with -O2 In-Reply-To: <199602022231.OAA01708@precipice.shockwave.com> References: <199602022231.OAA01708@precipice.shockwave.com> Sender: owner-current@FreeBSD.org Precedence: bulk > has anyone determined if this is safe? It *should* be, but I haven't checked it myself. Andrey removed the -fno-strength-reduce bug after the fix for it was checked in, so you should be okay. Nate From owner-freebsd-current Fri Feb 2 16:43:32 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id QAA23651 for current-outgoing; Fri, 2 Feb 1996 16:43:32 -0800 (PST) Received: from precipice.shockwave.com (precipice.shockwave.com [171.69.108.33]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id QAA23646 for ; Fri, 2 Feb 1996 16:43:30 -0800 (PST) Received: from localhost.shockwave.com (localhost.shockwave.com [127.0.0.1]) by precipice.shockwave.com (8.7.3/8.7.3) with SMTP id QAA17309; Fri, 2 Feb 1996 16:42:25 -0800 (PST) Message-Id: <199602030042.QAA17309@precipice.shockwave.com> To: Edward Wolpert cc: current@FreeBSD.org Subject: Re: Problem compiling current (Feb 1) In-reply-to: Your message of "Fri, 02 Feb 1996 18:01:36 EST." <199602022301.SAA25581@osti.rmt.utk.edu> Date: Fri, 02 Feb 1996 16:42:24 -0800 From: Paul Traina Sender: owner-current@FreeBSD.org Precedence: bulk It sounds like you didn't recompile and install the new config(1). Paul From: Edward Wolpert Subject: Problem compiling current (Feb 1) Folks- I'm trying to compile current, as of Feb 1, after 8pm USA east standard time. I updated my includes and libs, and now I went after rebuilding the kernel. When I do, the i386/i386/genassym.c file complains about opt_sysvipc.h not being found. I haven't found the file in my area, nor in current elsewhere... When I do a make depend after doing a config on the build file, in the compile directory, the make depend gives the following output: wolpert osti [159] make depend cc -c -O -W -Wreturn-type -Wcomment -Wredundant-decls -Wimplicit -Wnested-ex >>terns -Wstrict-prototypes -Wmissing-prototypes -Winline -nostdinc -I. -I../ >>.. -I../../sys -I../../../include -DGENERIC -DI586_CPU -DI486_CPU -DI386_CPU >>-DSYSVMSG -DSYSVSEM -DSYSVSHM -DCOMPAT_LINUX -DUSER_LDT -DUCONSOLE -DBOUNCE_B >>UFFERS -DSCSI_DELAY=15 -DCOMPAT_43 -DPROCFS -DCD9660 -DMSDOSFS -DNFS -DFFS -D >>INET -DKERNEL -DTIMEZONE=0 -DDST=0 -DMAXUSERS=10 -UKERNEL ../../i386/i386/gen >>assym.c ../../i386/i386/genassym.c:40: opt_sysvipc.h: No such file or directory *** Error code 1 Stop. Ideas? I sup everything but gnu and games. Do I need gnu? -- Virtually, Edward Wolpert ------------------------------ "Nothingness is the worm at the |wolpert@utk.edu | center of being." -Sartre |wolpert@osti.rmt.utk.edu | ------------------------------ Fnord! [DC 92 17 C1 7A 42 06 73 66 9D A9 00 52 07 6B 3B] From owner-freebsd-current Fri Feb 2 16:51:34 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id QAA24071 for current-outgoing; Fri, 2 Feb 1996 16:51:34 -0800 (PST) Received: from GndRsh.aac.dev.com (GndRsh.aac.dev.com [198.145.92.241]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id QAA24062 for ; Fri, 2 Feb 1996 16:51:19 -0800 (PST) Received: (from rgrimes@localhost) by GndRsh.aac.dev.com (8.6.12/8.6.12) id QAA22113; Fri, 2 Feb 1996 16:49:09 -0800 From: "Rodney W. Grimes" Message-Id: <199602030049.QAA22113@GndRsh.aac.dev.com> Subject: Re: ip_fw ordering of rules.. To: roberto@keltia.freenix.fr (Ollivier Robert) Date: Fri, 2 Feb 1996 16:49:09 -0800 (PST) Cc: phk@critter.tfs.com, nate@sri.MT.net, imb@scgt.oz.au, current@FreeBSD.org In-Reply-To: <199602022119.WAA23947@keltia.freenix.fr> from "Ollivier Robert" at Feb 2, 96 10:19:53 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.org Precedence: bulk > > It seems that Poul-Henning Kamp said: > > It basically sorts so that the rule covering most addresses come first. > > > > It doesn't look at deny/pass in that context, so if you say: > > I'm coming a little bit late on the subject, but I think that we should > remove the sorting altogether. Sorting make the software do things you > don't expect (as in Poul-Henning's example). > > In that respect, anyone using ipfw can't afford the potential risk. > > > deny some specific port > > allow the rest > > > > It will come out as: > > allow everything > > a deny rule never used. > > Sorting access lists is *evil*. "Building Internet FIREWALLS", D. Brent Chapman and Elizabeth D. Zwicky, O'Reilly & Associates, Inc., pp173: "It Should Apply Rules in the Order Specified" You want your packet fileter to apply, in a predicatable order, the rules you specify for it. By far the simplest order is the order is which you, the person configuring the router, specify the rules. Unfortunately, some products, instead of applying rules in the order you specify, try to reorder and merge rules to achieve greater efficiency in applying the rules. This causes several problems: o Reordering rules makes it difficult for you to figure out what's going on, and what the router is going to do with a particular set of filtering instructions. Configuring a packet filtering system is already complicated enough, without having a vendor add additonal complications by merging and reordering rule sets. o If there are any quirks or bugs in the merging or reordering of rule sets (and there often are, because it's something that's very difficult for the vendors to test), it becomes impossible to figure out what the system is going to do with a given set of filters. o Most importantly, reordering rules can break a rule set that would work just fine if it had not been reordered. 3 more pages of samples showing why it is bad and evil to do this... then pp 176: You should make sure the packet filtering router you select doesn't reorder rule sets. Enough said??? Can we remove the sorting PLEASE?? -- Rod Grimes rgrimes@gndrsh.aac.dev.com Accurate Automation Company Reliable computers for FreeBSD From owner-freebsd-current Fri Feb 2 17:15:57 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id RAA26095 for current-outgoing; Fri, 2 Feb 1996 17:15:57 -0800 (PST) Received: from ki.net (root@ki.net [142.77.249.8]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id RAA26072 Fri, 2 Feb 1996 17:15:50 -0800 (PST) Received: (from scrappy@localhost) by ki.net (8.7.3/8.7.3) id UAA03516; Fri, 2 Feb 1996 20:15:47 -0500 (EST) Date: Fri, 2 Feb 1996 20:15:46 -0500 (EST) From: "Marc G. Fournier" To: Stefan Esser cc: stable@freebsd.org, current@freebsd.org Subject: Re: PR: ASUS PC-SC200 panicks at _scsi_attachdevs+0x20 In-Reply-To: <199602022340.AA01725@Sysiphos> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org Precedence: bulk On Sat, 3 Feb 1996, Stefan Esser wrote: > Well, yes, having looked at it, I'd tend to agree :) > Apologizes for previous ones...figured it might be one of those "known" bugs that someone would pop up with "just change this" *sigh* > void > scsi_attachdevs(scbus) > struct scsibus_data *scbus; > { > int scsibus; > struct scsi_link *sc_link_proto = scbus->adapter_link; > > if ( (scsibus = scsi_bus_conf(sc_link_proto)) == -1) { > return; > } > /* > * if the adapter didn't give us this, set a default > * (compatibility with old adapter drivers) > */ > if(!(sc_link_proto->opennings)) { <=== openings is at offset 7 > sc_link_proto->opennings = 1; > } > > } Stopped at _scsi_attachdevs+0x20: cmpb $0,0x7(%ebx) <=== > Stupid question, but how do I read this? I'd like to at least be able to present the code along with my debug reports, so that everyone else doesn't have to go searching :) > Could you please print the value of scbus > and scbus->adapter_link before the call to > scsi_attachdevs() and the corresponding > values within that function ? > Okay, but you'll need to tell me how. All I have to work with is DDB, since I'm not getting a physical dump, and all I know how to use so far in DDB (all I've ever needed to use) is trace :( I'm going to read through the man page on DDB right now, and see if I can figure it out, but it may be faster if someone just tells me what I should be doing, at least for the first time? :( > I don't see what's going on here, but I > don't have a 2.1R tree checked out and > can't easily build and boot a 2.1R kernel > currently ... > No probs, I don't mind being a guinea pig :) Once I get this machine upgraded properly, -current is going onto it, but I can't get -current onto it until I get this controller working (chicken before egg dilemna :( ) Marc G. Fournier | POP Mail Telnet Acct DNS Hosting System | WWW Services Database Services | Knowledge, Administrator | | Information and scrappy@ki.net | WWW: http://www.ki.net | Communications, Inc From owner-freebsd-current Fri Feb 2 17:23:02 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id RAA26840 for current-outgoing; Fri, 2 Feb 1996 17:23:02 -0800 (PST) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id RAA26835 for ; Fri, 2 Feb 1996 17:22:59 -0800 (PST) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id SAA01056; Fri, 2 Feb 1996 18:21:17 -0700 From: Terry Lambert Message-Id: <199602030121.SAA01056@phaeton.artisoft.com> Subject: Re: Problem compiling current (Feb 1) To: wolpert@osti.rmt.utk.edu (Edward Wolpert) Date: Fri, 2 Feb 1996 18:21:17 -0700 (MST) Cc: current@FreeBSD.org In-Reply-To: <199602022301.SAA25581@osti.rmt.utk.edu> from "Edward Wolpert" at Feb 2, 96 06:01:36 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.org Precedence: bulk > I'm trying to compile current, as of Feb 1, after 8pm USA > east standard time. I updated my includes and libs, and now I went > after rebuilding the kernel. When I do, the i386/i386/genassym.c > file complains about opt_sysvipc.h not being found. I haven't > found the file in my area, nor in current elsewhere... > > When I do a make depend after doing a config on the build file, > in the compile directory, the make depend gives the following > output: Rebuild the new config and use it instead of the installed one to config the kernel. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-current Fri Feb 2 19:09:50 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id TAA07536 for current-outgoing; Fri, 2 Feb 1996 19:09:50 -0800 (PST) Received: from gdi.uoregon.edu (riley-net170-164.uoregon.edu [128.223.170.164]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id TAA07511 Fri, 2 Feb 1996 19:09:41 -0800 (PST) Received: (from dwhite@localhost) by gdi.uoregon.edu (8.6.12/8.6.12) id TAA03170; Fri, 2 Feb 1996 19:07:08 -0800 Date: Fri, 2 Feb 1996 19:07:07 -0800 (PST) From: Doug White Reply-To: dwhite@resnet.uoregon.edu To: Steve Tan cc: questions@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: newbie : How write to DOS Floppy ? In-Reply-To: <199602020101.RAA06440@iceland.it.earthlink.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@FreeBSD.ORG Precedence: bulk On Thu, 1 Feb 1996, Steve Tan wrote: > I'm not sure if this is the right place to ask, but I'm > trying to figure out how to write files to a DOS disk, my > floppy drive. I didn't see any info in the FAQ's or > installation guides. > I believe I need to mount /dev/fd0 or /dev/rmt0 , but I can't > find the specific command to use. mount_msdos /dev/fd0 /mnt will mount DOS's drive A: to /mnt. > I'm using BSD to develop CGI perl scripts and need to transfer > them to a PC running Win95. Ugly. Why not run a FreeBSD web server and get the better performance? :) Doug White | University of Oregon Internet: dwhite@gladstone.uoregon.edu | Residence Networking Assistant http://gladstone.uoregon.edu/~dwhite | Computer Science Major From owner-freebsd-current Fri Feb 2 19:10:07 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id TAA07627 for current-outgoing; Fri, 2 Feb 1996 19:10:07 -0800 (PST) Received: from precipice.shockwave.com (precipice.shockwave.com [171.69.108.33]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id TAA07578 for ; Fri, 2 Feb 1996 19:10:02 -0800 (PST) Received: from localhost.shockwave.com (localhost.shockwave.com [127.0.0.1]) by precipice.shockwave.com (8.7.3/8.7.3) with SMTP id TAA28595; Fri, 2 Feb 1996 19:08:52 -0800 (PST) Message-Id: <199602030308.TAA28595@precipice.shockwave.com> To: Mark Murray cc: current@freebsd.org Subject: Re: New DES library is close! In-reply-to: Your message of "Fri, 02 Feb 1996 10:39:49 +0200." <199602020839.KAA13323@grumble.grondar.za> Date: Fri, 02 Feb 1996 19:08:44 -0800 From: Paul Traina Sender: owner-current@freebsd.org Precedence: bulk win, win, win, and win. go for it, no objections from the crypto weenie here. From owner-freebsd-current Fri Feb 2 19:34:22 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id TAA10893 for current-outgoing; Fri, 2 Feb 1996 19:34:22 -0800 (PST) Received: from linux.csie.nctu.edu.tw (linux.csie.nctu.edu.tw [140.113.235.252]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id TAA10456 for ; Fri, 2 Feb 1996 19:31:42 -0800 (PST) Received: (from jdli@localhost) by linux.csie.nctu.edu.tw (8.6.9/8.6.9) id LAA23878 for freebsd-current@FreeBSD.ORG; Sat, 3 Feb 1996 11:26:36 +0800 From: Chien-Ta Lee Message-Id: <199602030326.LAA23878@linux.csie.nctu.edu.tw> Subject: make world with -fomit-frame-pointer To: freebsd-current@FreeBSD.ORG Date: Sat, 3 Feb 1996 11:26:34 +0800 (CST) X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-current@FreeBSD.ORG Precedence: bulk Hi : I noticed an gcc option from recently pentium-gcc discussions, that's "-fomit-frame-pointer". (I remembered linux often use it) I man gcc and it said that the option will make debug impossible. I always making my world with "-O2 -m486", is it ok to use this option to make world ? How about make kernel ?! About make kernel, will "-O2" or "-O2 -m486" make kernel run faster ? Thanks. -- 李 建 達 (Adonis) 交大資工 Mail: jdli@csie.nctu.edu.tw From owner-freebsd-current Fri Feb 2 22:07:18 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id WAA00969 for current-outgoing; Fri, 2 Feb 1996 22:07:18 -0800 (PST) Received: (from pst@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id WAA00963 Fri, 2 Feb 1996 22:07:16 -0800 (PST) Date: Fri, 2 Feb 1996 22:07:16 -0800 (PST) From: Paul Traina Message-Id: <199602030607.WAA00963@freefall.freebsd.org> To: wosch Subject: make world broken: calendar does not compile Cc: current Sender: owner-current@FreeBSD.ORG Precedence: bulk Please check your commits. You appear to be missing calendar.h. From owner-freebsd-current Fri Feb 2 23:47:06 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id XAA05550 for current-outgoing; Fri, 2 Feb 1996 23:47:06 -0800 (PST) Received: from zibbi.mikom.csir.co.za (zibbi.mikom.csir.co.za [146.64.24.58]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id XAA05543 Fri, 2 Feb 1996 23:46:39 -0800 (PST) Received: (from jhay@localhost) by zibbi.mikom.csir.co.za (8.6.12/8.6.9) id JAA21882; Sat, 3 Feb 1996 09:46:30 +0200 From: John Hay Message-Id: <199602030746.JAA21882@zibbi.mikom.csir.co.za> Subject: Is ctm running? To: freebsd-current@FreeBSD.ORG (FreeBSD-current), phk@FreeBSD.ORG Date: Sat, 3 Feb 1996 09:46:30 +0200 (SAT) X-Mailer: ELM [version 2.4 PL24 ME8b] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.ORG Precedence: bulk Hi, I haven't received any ctm-cvs updates for more than 24 hours. Is there something wrong somewhere? John -- John Hay -- John.Hay@csir.co.za From owner-freebsd-current Sat Feb 3 00:08:33 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id AAA06819 for current-outgoing; Sat, 3 Feb 1996 00:08:33 -0800 (PST) Received: from oznet02.ozemail.com.au (oznet02.ozemail.com.au [203.2.192.124]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id AAA06811 Sat, 3 Feb 1996 00:08:24 -0800 (PST) Received: from rlyon.mynet.au (slmel1p27.ozemail.com.au [203.2.195.43]) by oznet02.ozemail.com.au (8.7.1/8.6.12) with SMTP id TAA10528; Sat, 3 Feb 1996 19:07:52 +1100 (EST) Date: Sat, 3 Feb 1996 19:02:37 +1100 (EST) From: Richard Lyon To: Steve Tan cc: questions@freebsd.org, current@freebsd.org Subject: Re: newbie : How write to DOS Floppy ? In-Reply-To: <199602020101.RAA06440@iceland.it.earthlink.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org Precedence: bulk On Thu, 1 Feb 1996, Steve Tan wrote: > I'm not sure if this is the right place to ask, but I'm > trying to figure out how to write files to a DOS disk, my > floppy drive. I didn't see any info in the FAQ's or > installation guides. > Look at mtools available in the ports collection. This bypasses the need to mount and umount the floppy manually. It also can take care of end-of-line text translation. ie. mdir A: mcopy "A:\*.*" . mcopy unixfile "A:\dosfile" etc etc. Regards ... From owner-freebsd-current Sat Feb 3 00:21:40 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id AAA08290 for current-outgoing; Sat, 3 Feb 1996 00:21:40 -0800 (PST) Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id AAA08279 for ; Sat, 3 Feb 1996 00:21:35 -0800 (PST) Received: from sax.sax.de by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id JAA25421 for ; Sat, 3 Feb 1996 09:21:34 +0100 Received: by sax.sax.de (8.6.11/8.6.12-s1) with UUCP id JAA23498 for freebsd-current@FreeBSD.org; Sat, 3 Feb 1996 09:21:33 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.7.3/8.6.9) id JAA08609 for freebsd-current@FreeBSD.org; Sat, 3 Feb 1996 09:16:40 +0100 (MET) From: J Wunsch Message-Id: <199602030816.JAA08609@uriah.heep.sax.de> Subject: Re: list of major device numbers? To: freebsd-current@FreeBSD.org (FreeBSD-current users) Date: Sat, 3 Feb 1996 09:16:40 +0100 (MET) Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199602022239.OAA16197@ref.tfs.com> from "Julian Elischer" at Feb 2, 96 02:39:03 pm X-Phone: +49-351-2012 669 X-Mailer: ELM [version 2.4 PL23] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-current@FreeBSD.org Precedence: bulk As Julian Elischer wrote: > > > What are the plans to dynamicalize the assignment of major numbers? I > if you specify (-1?) it will dynamically assign you one, > but I need to change this so that it statrs at a higher number > so as to not collide with devices that already statically > have a spot.. So we should reserve the first 20 numbers for fixed ones, and convert all but the critical drivers to no longer using a fixed one. Should we? -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-current Sat Feb 3 00:33:02 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id AAA09199 for current-outgoing; Sat, 3 Feb 1996 00:33:02 -0800 (PST) Received: from grumble.grondar.za (root@grumble.grondar.za [196.7.18.130]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id AAA09192 for ; Sat, 3 Feb 1996 00:32:57 -0800 (PST) Received: from localhost (mark@localhost [127.0.0.1]) by grumble.grondar.za (8.7.3/8.7.3) with SMTP id KAA11618; Sat, 3 Feb 1996 10:32:38 +0200 (SAT) Message-Id: <199602030832.KAA11618@grumble.grondar.za> X-Authentication-Warning: grumble.grondar.za: Host mark@localhost [127.0.0.1] didn't use HELO protocol To: John Hay cc: freebsd-current@FreeBSD.org (FreeBSD-current) Subject: Re: Is ctm running? Date: Sat, 03 Feb 1996 10:32:38 +0200 From: Mark Murray Sender: owner-current@FreeBSD.org Precedence: bulk John Hay wrote: > I haven't received any ctm-cvs updates for more than 24 hours. Is there > something wrong somewhere? Yehbo. Freefall was down for an upgrade/repair. M -- Mark Murray 46 Harvey Rd, Claremont, Cape Town 7700, South Africa +27 21 61-3768 GMT+0200 Finger mark@grondar.za for PGP key From owner-freebsd-current Sat Feb 3 00:51:41 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id AAA10539 for current-outgoing; Sat, 3 Feb 1996 00:51:41 -0800 (PST) Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id AAA10530 for ; Sat, 3 Feb 1996 00:51:37 -0800 (PST) Received: from sax.sax.de by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id JAA25749 for ; Sat, 3 Feb 1996 09:51:35 +0100 Received: by sax.sax.de (8.6.11/8.6.12-s1) with UUCP id JAA23692 for freebsd-current@FreeBSD.org; Sat, 3 Feb 1996 09:51:35 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.7.3/8.6.9) id JAA08893 for freebsd-current@FreeBSD.org; Sat, 3 Feb 1996 09:34:08 +0100 (MET) From: J Wunsch Message-Id: <199602030834.JAA08893@uriah.heep.sax.de> Subject: Re: newbie : How write to DOS Floppy ? To: freebsd-current@FreeBSD.org (FreeBSD-current users) Date: Sat, 3 Feb 1996 09:34:08 +0100 (MET) Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: from "Doug White" at Feb 2, 96 07:07:07 pm X-Phone: +49-351-2012 669 X-Mailer: ELM [version 2.4 PL23] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-current@FreeBSD.org Precedence: bulk As Doug White wrote: > > > I'm using BSD to develop CGI perl scripts and need to transfer > > them to a PC running Win95. > > Ugly. Why not run a FreeBSD web server and get the better performance? :) Because Win95 is now true multitasking: it can boot and crash simultaneously. :-] -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-current Sat Feb 3 04:54:42 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id EAA27329 for current-outgoing; Sat, 3 Feb 1996 04:54:42 -0800 (PST) Received: from osti.rmt.utk.edu (OSTI.RMT.UTK.EDU [128.169.24.17]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id EAA27324 for ; Sat, 3 Feb 1996 04:54:38 -0800 (PST) Received: (from wolpert@localhost) by osti.rmt.utk.edu (8.6.12/8.6.12) id IAA07812; Sat, 3 Feb 1996 08:01:02 -0500 Date: Sat, 3 Feb 1996 08:01:02 -0500 From: Edward Wolpert Message-Id: <199602031301.IAA07812@osti.rmt.utk.edu> To: current@freebsd.org Subject: Re: Problems with compiling current (Feb 1) Sender: owner-current@freebsd.org Precedence: bulk Thanks, the new config was the problem. My 'make world' failed at making /bin/sh, (and tn3270, but that's a different story) The /bin/sh problem was after the make depend went, the make started, and I got the following: --Cut here--> cc -O -DSHELL -I. -I/usr/src/bin/sh -static /usr/src/bin/sh/mkinit.c -o mkinit cc -O -DSHELL -I. -I/usr/src/bin/sh -static /usr/src/bin/sh/builtins.c -o /usr/src/bin/sh/builtins /usr/lib/crt0.o: Undefined symbol `_main' referenced from text segment /var/tmp/cc0076051.o: Undefined symbol `_bltincmd' referenced from text segment /var/tmp/cc0076051.o: Undefined symbol `_bgcmd' referenced from text segment /var/tmp/cc0076051.o: Undefined symbol `_breakcmd' referenced from text segment /var/tmp/cc0076051.o: Undefined symbol `_cdcmd' referenced from text segment /var/tmp/cc0076051.o: Undefined symbol `_dotcmd' referenced from text segment /var/tmp/cc0076051.o: Undefined symbol `_echocmd' referenced from text segment /var/tmp/cc0076051.o: Undefined symbol `_evalcmd' referenced from text segment /var/tmp/cc0076051.o: Undefined symbol `_execcmd' referenced from text segment /var/tmp/cc0076051.o: Undefined symbol `_exitcmd' referenced from text segment /var/tmp/cc0076051.o: Undefined symbol `_expcmd' referenced from text segment /var/tmp/cc0076051.o: Undefined symbol `_exportcmd' referenced from text segment /var/tmp/cc0076051.o: Undefined symbol `_histcmd' referenced from text segment /var/tmp/cc0076051.o: Undefined symbol `_fgcmd' referenced from text segment /var/tmp/cc0076051.o: Undefined symbol `_getoptscmd' referenced from text segment /var/tmp/cc0076051.o: Undefined symbol `_hashcmd' referenced from text segment /var/tmp/cc0076051.o: Undefined symbol `_jobidcmd' referenced from text segment [...deleted...] *** Error code 1 Stop. --Cut here--> If I do a make clean manually, and then make, it works fine. If I type make again, it dies. Perhaps I don't understand this as well as I should... If I'm in the /usr/src, and type 'make depend all' so I don't install everything, should that work? I did this just to make sure I could compile all of current before installing it. It died in usr.bin/sh, as shown. What did I do wrong here? -- Virtually, Edward Wolpert ------------------------------ "Nothingness is the worm at the |wolpert@utk.edu | center of being." -Sartre |wolpert@osti.rmt.utk.edu | ------------------------------ Fnord! [DC 92 17 C1 7A 42 06 73 66 9D A9 00 52 07 6B 3B] From owner-freebsd-current Sat Feb 3 07:34:34 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id HAA05490 for current-outgoing; Sat, 3 Feb 1996 07:34:34 -0800 (PST) Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id HAA05437 for ; Sat, 3 Feb 1996 07:34:23 -0800 (PST) Received: from sax.sax.de by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id QAA03155; Sat, 3 Feb 1996 16:34:15 +0100 Received: by sax.sax.de (8.6.11/8.6.12-s1) with UUCP id QAA26611; Sat, 3 Feb 1996 16:34:14 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.7.3/8.6.9) id QAA11512; Sat, 3 Feb 1996 16:23:00 +0100 (MET) From: J Wunsch Message-Id: <199602031523.QAA11512@uriah.heep.sax.de> Subject: Re: Problems with compiling current (Feb 1) To: wolpert@osti.rmt.utk.edu (Edward Wolpert) Date: Sat, 3 Feb 1996 16:23:00 +0100 (MET) Cc: current@freebsd.org Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199602031301.IAA07812@osti.rmt.utk.edu> from "Edward Wolpert" at Feb 3, 96 08:01:02 am X-Phone: +49-351-2012 669 X-Mailer: ELM [version 2.4 PL23] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-current@freebsd.org Precedence: bulk As Edward Wolpert wrote: > > Thanks, the new config was the problem. My 'make world' failed at making > /bin/sh, (and tn3270, but that's a different story) The /bin/sh problem > was after the make depend went, the make started, and I got the following: > > --Cut here--> > cc -O -DSHELL -I. -I/usr/src/bin/sh -static /usr/src/bin/sh/mkinit.c -o mkinit > cc -O -DSHELL -I. -I/usr/src/bin/sh -static /usr/src/bin/sh/builtins.c -o /usr/src/bin/sh/builtins > /usr/lib/crt0.o: Undefined symbol `_main' referenced from text segment > /var/tmp/cc0076051.o: Undefined symbol `_bltincmd' referenced from text segment > /var/tmp/cc0076051.o: Undefined symbol `_bgcmd' referenced from text segment This was a problem with the Makefile. As a side-effect of some other work, i've committed a fix for this problem an hour ago. For the curious: our /usr/share/mk files now define a default rule for compiling `foo.c' into `foo'. This used to be broken for a long time, but it's fixed now. In the above case, the shell script `builtins' is used to create the source file `builtins.c'. Once this file is there after the first run, make attempts to rebuild the (outdated :) script `builtins' from the C ``source''. The fix was to add a null rule for `builtins'. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-current Sat Feb 3 09:36:54 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id JAA14698 for current-outgoing; Sat, 3 Feb 1996 09:36:54 -0800 (PST) Received: from news1.gtn.com (news1.gtn.com [192.109.159.3]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id JAA14692 Sat, 3 Feb 1996 09:36:52 -0800 (PST) Received: (from uucp@localhost) by news1.gtn.com (8.7.2/8.7.2) id SAA29892; Sat, 3 Feb 1996 18:15:17 +0100 (MET) Received: from knobel.gun.de (localhost [127.0.0.1]) by knobel.gun.de (8.7.3/8.7.3) with SMTP id QAA01871; Sat, 3 Feb 1996 16:47:31 +0100 (MET) Date: Sat, 3 Feb 1996 16:47:31 +0100 (MET) From: Andreas Klemm To: Daniel Baker cc: freebsd-questions@FreeBSD.org, freebsd-current@FreeBSD.org Subject: Re: SB16 & Current In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@FreeBSD.org Precedence: bulk On Fri, 2 Feb 1996, Daniel Baker wrote: > I had my SB16 basically working on the 21-Release, but now that I'm > running current, not everything work.. XCD works fine, but when I try to > cat to /dev/dsp0 for a test, I get: No problems here. Here my kernel config file: # Controls all sound devices controller snd0 # SoundBlaster DSP driver - for SB, SB Pro, SB16, PAS(emulating SB) device sb0 at isa? port 0x220 irq 5 drq 1 vector sbintr # SoundBlaster 16 DSP driver - for SB16 - requires sb0 device device sbxvi0 at isa? drq 5 # SoundBlaster 16 MIDI - for SB16 - requires sb0 device device sbmidi0 at isa? port 0x330 # Yamaha OPL-2/OPL-3 FM - for SB, SB Pro, SB16, PAS device opl0 at isa? port 0x388 # Joystick device joy0 at isa? port "IO_GAME" -- andreas@knobel.gun.de /\/\___ Wiechers & Partner Datentechnik GmbH Andreas Klemm ___/\/\/ - Support Unix - aklemm@wup.de - \/ ftp://sunsite.unc.edu/pub/Linux/system/Printing/aps-491.tgz apsfilter - magic print filter 4lpd >>> knobel is powered by FreeBSD <<< From owner-freebsd-current Sat Feb 3 09:47:27 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id JAA15464 for current-outgoing; Sat, 3 Feb 1996 09:47:27 -0800 (PST) Received: from cocoa.ops.neosoft.com (root@cocoa.ops.neosoft.com [206.109.5.227]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id JAA15437 Sat, 3 Feb 1996 09:47:20 -0800 (PST) Received: (from dbaker@localhost) by cocoa.ops.neosoft.com (8.7.3/8.6.12) id LAA04294; Sat, 3 Feb 1996 11:47:01 -0600 (CST) Date: Sat, 3 Feb 1996 11:47:00 -0600 (CST) From: Daniel Baker X-Sender: dbaker@cocoa.ops.neosoft.com To: Andreas Klemm cc: freebsd-questions@FreeBSD.org, freebsd-current@FreeBSD.org Subject: Re: SB16 & Current In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@FreeBSD.org Precedence: bulk On Sat, 3 Feb 1996, Andreas Klemm wrote: > On Fri, 2 Feb 1996, Daniel Baker wrote: > > > I had my SB16 basically working on the 21-Release, but now that I'm > > running current, not everything work.. XCD works fine, but when I try to > > cat to /dev/dsp0 for a test, I get: > Are you running 2.2-CURRENT from after Feb 1? > No problems here. Here my kernel config file: > > # Controls all sound devices > controller snd0 > # SoundBlaster DSP driver - for SB, SB Pro, SB16, PAS(emulating SB) > device sb0 at isa? port 0x220 irq 5 drq 1 vector sbintr > # SoundBlaster 16 DSP driver - for SB16 - requires sb0 device > device sbxvi0 at isa? drq 5 > # SoundBlaster 16 MIDI - for SB16 - requires sb0 device > device sbmidi0 at isa? port 0x330 > # Yamaha OPL-2/OPL-3 FM - for SB, SB Pro, SB16, PAS > device opl0 at isa? port 0x388 > # Joystick > device joy0 at isa? port "IO_GAME" > > -- > andreas@knobel.gun.de /\/\___ Wiechers & Partner Datentechnik GmbH > Andreas Klemm ___/\/\/ - Support Unix - aklemm@wup.de - > \/ > ftp://sunsite.unc.edu/pub/Linux/system/Printing/aps-491.tgz > apsfilter - magic print filter 4lpd >>> knobel is powered by FreeBSD <<< > -- Daniel Baker - Daniel@Cuckoo.COM "Huhuhu, thank you, drive through please" From owner-freebsd-current Sat Feb 3 12:49:40 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id MAA28511 for current-outgoing; Sat, 3 Feb 1996 12:49:40 -0800 (PST) Received: from rover.village.org (rover.village.org [204.144.255.49]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id MAA28503 for ; Sat, 3 Feb 1996 12:49:35 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by rover.village.org (8.6.11/8.6.6) with SMTP id NAA13034; Sat, 3 Feb 1996 13:49:25 -0700 Message-Id: <199602032049.NAA13034@rover.village.org> To: "Rodney W. Grimes" Subject: Re: ip_fw ordering of rules.. Cc: current@freebsd.org In-reply-to: Your message of Fri, 02 Feb 1996 16:49:09 PST Date: Sat, 03 Feb 1996 13:49:25 -0700 From: Warner Losh Sender: owner-current@freebsd.org Precedence: bulk : Enough said??? Can we remove the sorting PLEASE?? We aren't using IPFW right now because it reorders rules. This is completely *EVIL*, as Rod said, and our firewall marshall punted when he saw this feature of IPFW and went to IPFILT, which seems to have tied us to 1.1.5.1R, which isn't necessarily bad, but isn't necessarily good either... Our rules right now look like: allow port 21 to ir allow port 25 to ir ... disallow all which most sane people would consider means "Allow FTP and TELNET to ir, but nothing else is allowed at all." As far as we've been able to determine, IPFW doens't allow this to work properly, and is therefore nearly useless as a firewall. I agree with Rod. Let's take the sorting out! Warner From owner-freebsd-current Sat Feb 3 13:14:02 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id NAA00581 for current-outgoing; Sat, 3 Feb 1996 13:14:02 -0800 (PST) Received: from ra.dkuug.dk (ra.dkuug.dk [193.88.44.193]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id NAA00570 for ; Sat, 3 Feb 1996 13:13:55 -0800 (PST) Received: from critter.tfs.com ([140.145.230.144]) by ra.dkuug.dk (8.6.12/8.6.12) with ESMTP id WAA27277; Sat, 3 Feb 1996 22:01:53 +0100 Received: from localhost.tfs.com (localhost.tfs.com [127.0.0.1]) by critter.tfs.com (8.6.12/8.6.12) with SMTP id WAA06827; Sat, 3 Feb 1996 22:13:09 +0100 X-Authentication-Warning: critter.tfs.com: Host localhost.tfs.com didn't use HELO protocol To: Warner Losh cc: "Rodney W. Grimes" , current@freebsd.org Subject: Re: ip_fw ordering of rules.. In-reply-to: Your message of "Sat, 03 Feb 1996 13:49:25 MST." <199602032049.NAA13034@rover.village.org> Date: Sat, 03 Feb 1996 22:13:08 +0100 Message-ID: <6825.823381988@critter.tfs.com> From: Poul-Henning Kamp Sender: owner-current@freebsd.org Precedence: bulk > : Enough said??? Can we remove the sorting PLEASE?? > > I agree with Rod. Let's take the sorting out! I just did :-) (In -current that is.) -- Poul-Henning Kamp | phk@FreeBSD.ORG FreeBSD Core-team. http://www.freebsd.org/~phk | phk@login.dknet.dk Private mailbox. whois: [PHK] | phk@ref.tfs.com TRW Financial Systems, Inc. Future will arrive by its own means, progress not so. From owner-freebsd-current Sat Feb 3 13:52:18 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id NAA04533 for current-outgoing; Sat, 3 Feb 1996 13:52:18 -0800 (PST) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id NAA04523 for ; Sat, 3 Feb 1996 13:52:16 -0800 (PST) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id OAA04419; Sat, 3 Feb 1996 14:50:46 -0700 From: Terry Lambert Message-Id: <199602032150.OAA04419@phaeton.artisoft.com> Subject: Re: list of major device numbers? To: joerg_wunsch@uriah.heep.sax.de Date: Sat, 3 Feb 1996 14:50:46 -0700 (MST) Cc: freebsd-current@FreeBSD.ORG In-Reply-To: <199602030816.JAA08609@uriah.heep.sax.de> from "J Wunsch" at Feb 3, 96 09:16:40 am X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.ORG Precedence: bulk > > > What are the plans to dynamicalize the assignment of major numbers? I > > > if you specify (-1?) it will dynamically assign you one, > > but I need to change this so that it statrs at a higher number > > so as to not collide with devices that already statically > > have a spot.. > > So we should reserve the first 20 numbers for fixed ones, and convert > all but the critical drivers to no longer using a fixed one. Should > we? We should be using vnode struct addresses instead of major/minor numbers internally to the kernel. For boot-critical drivers, the correct method is not to assign a particular lexical offset to the critical drivers (since this implies a lexically based lookup, and we want to kill that). Major and minor numbers need to die. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-current Sat Feb 3 16:27:27 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id QAA13416 for current-outgoing; Sat, 3 Feb 1996 16:27:27 -0800 (PST) Received: from deadline.snafu.de (deadline.snafu.de [194.64.158.28]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id QAA13411 for ; Sat, 3 Feb 1996 16:27:24 -0800 (PST) Received: by deadline.snafu.de id m0tisJ3-0009uSC; Sun, 4 Feb 96 01:27 MET (/\oo/\ Smail3.1.29.1 #29.1) Message-Id: From: root@deadline.snafu.de (Andreas S. Wetzel) Subject: SUP busy? To: current@freebsd.org Date: Sun, 4 Feb 1996 01:27:48 +0100 (MET) Organization: A world stranger than you have ever imagined. X-Mailer: ELM [version 2.4 PL25 ME8b] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org Precedence: bulk Hi! --- In the last few days I noticed that the SUP server at freefall.freebsd.org is busy almost everytime I try to update my -current and -ports collection. Are there any problems with this server (i.e. overload, burnout, etc...) ?? Regards, mickey -- (__) (@@) Andreas S. Wetzel E-mail: mickey@deadline.snafu.de /-------\/ Utrechter Strasse 41 Web: http://deadline.snafu.de/ / | || 13347 Berlin Voice: <+4930> 456 81 68 * ||----|| Germany Fax/Data: <+4930> 455 19 57 ~~ ~~ From owner-freebsd-current Sat Feb 3 16:57:27 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id QAA14872 for current-outgoing; Sat, 3 Feb 1996 16:57:27 -0800 (PST) Received: from time.cdrom.com (time.cdrom.com [192.216.222.226]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id QAA14867 for ; Sat, 3 Feb 1996 16:57:24 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by time.cdrom.com (8.6.12/8.6.9) with SMTP id QAA27549; Sat, 3 Feb 1996 16:57:14 -0800 To: root@deadline.snafu.de (Andreas S. Wetzel) cc: current@freebsd.org Subject: Re: SUP busy? In-reply-to: Your message of "Sun, 04 Feb 1996 01:27:48 +0100." Date: Sat, 03 Feb 1996 16:57:14 -0800 Message-ID: <27547.823395434@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-current@freebsd.org Precedence: bulk EVERYONE: Please, STOP using sup.freebsd.org! You should try to use sup2.freebsd.org, sup3.freebsd.org or sup4.freebsd.org, as I've talked about a great deal in -hackers and -announce over the last month or so. We've not actually put a ban on sup connections to sup.freebsd.org, but that's probably going to come pretty soon. The network situation to freefall has reached crisis proportions! If you're in europe, try nic.funet.fi. Not sure why the name server at nl.freebsd.org hasn't pointed sup.fi.freebsd.org at it yet, though that should happen soon. Jordan > Hi! > --- > > In the last few days I noticed that the SUP server at freefall.freebsd.org > is busy almost everytime I try to update my -current and -ports collection. > > Are there any problems with this server (i.e. overload, burnout, etc...) ?? > > Regards, mickey > > -- > (__) > (@@) Andreas S. Wetzel E-mail: mickey@deadline.snafu.de > /-------\/ Utrechter Strasse 41 Web: http://deadline.snafu.de / > / | || 13347 Berlin Voice: <+4930> 456 81 68 > * ||----|| Germany Fax/Data: <+4930> 455 19 57 > ~~ ~~ From owner-freebsd-current Sat Feb 3 17:30:59 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id RAA16540 for current-outgoing; Sat, 3 Feb 1996 17:30:59 -0800 (PST) Received: from time.cdrom.com (time.cdrom.com [192.216.222.226]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id RAA16532 for ; Sat, 3 Feb 1996 17:30:52 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by time.cdrom.com (8.6.12/8.6.9) with SMTP id RAA28259; Sat, 3 Feb 1996 17:30:41 -0800 cc: root@deadline.snafu.de (Andreas S. Wetzel), current@freebsd.org Subject: Re: SUP busy? In-reply-to: Your message of "Sat, 03 Feb 1996 16:57:14 PST." <27547.823395434@time.cdrom.com> Date: Sat, 03 Feb 1996 17:30:41 -0800 Message-ID: <28257.823397441@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-current@freebsd.org Precedence: bulk > If you're in europe, try nic.funet.fi. Not sure why the name server > at nl.freebsd.org hasn't pointed sup.fi.freebsd.org at it yet, though > that should happen soon. P.S. I forgot to mention that there's also a sup.de.freebsd.org which you should almost certainly be using! :-) Jordan From owner-freebsd-current Sat Feb 3 18:21:41 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id SAA18527 for current-outgoing; Sat, 3 Feb 1996 18:21:41 -0800 (PST) Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id SAA18517 for ; Sat, 3 Feb 1996 18:21:38 -0800 (PST) Received: from sax.sax.de by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id DAA15933; Sun, 4 Feb 1996 03:21:28 +0100 Received: by sax.sax.de (8.6.11/8.6.12-s1) with UUCP id DAA04651; Sun, 4 Feb 1996 03:21:28 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.7.3/8.6.9) id DAA15448; Sun, 4 Feb 1996 03:11:23 +0100 (MET) From: J Wunsch Message-Id: <199602040211.DAA15448@uriah.heep.sax.de> Subject: Re: SUP busy? To: freebsd-current@FreeBSD.org (FreeBSD-current users) Date: Sun, 4 Feb 1996 03:11:23 +0100 (MET) Cc: root@deadline.snafu.de In-Reply-To: <27547.823395434@time.cdrom.com> from "Jordan K. Hubbard" at Feb 3, 96 04:57:14 pm X-Phone: +49-351-2012 669 X-Mailer: ELM [version 2.4 PL23] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-current@FreeBSD.org Precedence: bulk As Jordan K. Hubbard wrote: > > If you're in europe, try nic.funet.fi. If you're in germany, try sup.de.freebsd.org. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-current Sat Feb 3 18:49:45 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id SAA19820 for current-outgoing; Sat, 3 Feb 1996 18:49:45 -0800 (PST) Received: from ki.net (root@ki.net [142.77.249.8]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id SAA19814 Sat, 3 Feb 1996 18:49:40 -0800 (PST) Received: (from scrappy@localhost) by ki.net (8.7.3/8.7.3) id VAA00463; Sat, 3 Feb 1996 21:49:37 -0500 (EST) Date: Sat, 3 Feb 1996 21:49:36 -0500 (EST) From: "Marc G. Fournier" To: current@freebsd.org, stable@freebsd.org Subject: FIXED: NCR problem until -stable Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org Precedence: bulk Hi... After figuring out that scbus wasn't a known symbol, and looking through the ncr.c code, I recompiled the kernel using gcc 2.6.3 instead of 2.7.2, and the system is operational again. That's for the lesson in DDB, since without that, I would never have figured this out on my own. One stupid question though...in ncr.c, the "offending" code was where statements like: #if (__FreeBSD__ >= 2) struct scsibus_data *scbus; #endif happened. Where its checking to see if __FreeBSD__ >= 2...now, I realize that if my 2.7.2 was proper, this wouldn't happen, but since this is 2.1-STABLE, is there a reason why those statements aren't just changed to #if (__FreeBSD__) struct scsibus_data *scbus; #endif ? Even looking through /usr/src/current/sys sources, there are alot of similar #if structs...if there is no reason for it anymore, and I generate patches to get rid of all that, is there someone I can submit the patches to in order to get it rolled into -current? Thanks... Marc G. Fournier | POP Mail Telnet Acct DNS Hosting System | WWW Services Database Services | Knowledge, Administrator | | Information and scrappy@ki.net | WWW: http://www.ki.net | Communications, Inc From owner-freebsd-current Sat Feb 3 20:02:15 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id UAA23403 for current-outgoing; Sat, 3 Feb 1996 20:02:15 -0800 (PST) Received: from asstdc.scgt.oz.au (root@asstdc.scgt.oz.au [202.14.234.65]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id UAA23384 Sat, 3 Feb 1996 20:02:08 -0800 (PST) Received: (from imb@localhost) by asstdc.scgt.oz.au (8.6.12/BSD4.4) id PAA20522; Sun, 4 Feb 1996 15:02:02 +1100 From: michael butler Message-Id: <199602040402.PAA20522@asstdc.scgt.oz.au> Subject: Re: SUP busy? To: freebsd-current@freebsd.org Date: Sun, 4 Feb 1996 15:01:58 +1100 (EST) Cc: freebsd-stable@freebsd.org In-Reply-To: <199602040211.DAA15448@uriah.heep.sax.de> from "J Wunsch" at Feb 4, 96 03:11:23 am X-Mailer: ELM [version 2.4 PL24beta] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org Precedence: bulk J Wunsch writes: > As Jordan K. Hubbard wrote: > > If you're in europe, try nic.funet.fi. > If you're in germany, try sup.de.freebsd.org. Whilst not appropriate to European sites .. for Australia and New Zealand, we have sup.au.freebsd.org and sup2.au.freebsd.org, michael From owner-freebsd-current Sat Feb 3 20:20:08 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id UAA24274 for current-outgoing; Sat, 3 Feb 1996 20:20:08 -0800 (PST) Received: from deadline.snafu.de (deadline.snafu.de [194.64.158.28]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id UAA24240 for ; Sat, 3 Feb 1996 20:20:01 -0800 (PST) Received: by deadline.snafu.de id m0tivjt-0009QgC; Sun, 4 Feb 96 05:07 MET (/\oo/\ Smail3.1.29.1 #29.1) Message-Id: From: root@deadline.snafu.de (Andreas S. Wetzel) Subject: Strange kernel messages on -current? To: current@freebsd.org Date: Sun, 4 Feb 1996 05:07:44 +0100 (MET) Organization: A world stranger than you have ever imagined. X-Mailer: ELM [version 2.4 PL25 ME8b] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org Precedence: bulk Hi! --- Using -current as of Feb 04 I get strange syslog messages everytime when sounds are being played. The message is alwas the same and it says: isa_dmadone_nobounce: channel 6 not busy Does anybody know what this message is about to tell me? Regards, mickey -- (__) (@@) Andreas S. Wetzel E-mail: mickey@deadline.snafu.de /-------\/ Utrechter Strasse 41 Web: http://deadline.snafu.de/ / | || 13347 Berlin Voice: <+4930> 456 81 68 * ||----|| Germany Fax/Data: <+4930> 455 19 57 ~~ ~~ From owner-freebsd-current Sat Feb 3 22:41:44 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id WAA02762 for current-outgoing; Sat, 3 Feb 1996 22:41:44 -0800 (PST) Received: from grumble.grondar.za (root@grumble.grondar.za [196.7.18.130]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id WAA02739 Sat, 3 Feb 1996 22:41:37 -0800 (PST) Received: from localhost (mark@localhost [127.0.0.1]) by grumble.grondar.za (8.7.3/8.7.3) with SMTP id IAA01786; Sun, 4 Feb 1996 08:40:39 +0200 (SAT) Message-Id: <199602040640.IAA01786@grumble.grondar.za> X-Authentication-Warning: grumble.grondar.za: Host mark@localhost [127.0.0.1] didn't use HELO protocol To: michael butler cc: freebsd-current@freebsd.org, freebsd-stable@freebsd.org Subject: Re: SUP busy? Date: Sun, 04 Feb 1996 08:40:39 +0200 From: Mark Murray Sender: owner-current@freebsd.org Precedence: bulk michael butler wrote: > J Wunsch writes: > > > As Jordan K. Hubbard wrote: > > > > If you're in europe, try nic.funet.fi. > > > If you're in germany, try sup.de.freebsd.org. > > Whilst not appropriate to European sites .. for Australia and New Zealand, > we have sup.au.freebsd.org and sup2.au.freebsd.org, ... and in South Africa there is sup.za.freebsd.org, ftp.za.freebsd.org and ftp2.frebsd.org. There are also CTMs of the international crypto code if for FTP and for email for thos who ask me. M -- Mark Murray 46 Harvey Rd, Claremont, Cape Town 7700, South Africa +27 21 61-3768 GMT+0200 Finger mark@grondar.za for PGP key