From owner-freebsd-hackers Sun Feb 23 00:00:39 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id AAA27397 for hackers-outgoing; Sun, 23 Feb 1997 00:00:39 -0800 (PST) Received: from profane.iq.org (profane.iq.org [203.4.184.217]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id AAA27377; Sun, 23 Feb 1997 00:00:06 -0800 (PST) Received: (from proff@localhost) by profane.iq.org (8.8.4/8.8.2) id SAA09960; Sun, 23 Feb 1997 18:54:23 +1100 (EST) From: Julian Assange Message-Id: <199702230754.SAA09960@profane.iq.org> Subject: Re: o [1997/02/01] bin/2634 rtld patches for easy creation of chroot enviroments In-Reply-To: <27770.856542186@critter.dk.tfs.com> from Poul-Henning Kamp at "Feb 21, 97 05:23:06 pm" To: phk@critter.dk.tfs.com (Poul-Henning Kamp) Date: Sun, 23 Feb 1997 18:54:22 +1100 (EST) Cc: security@freebsd.org, hackers@freebsd.org X-Mailer: ELM [version 2.4ME+ PL28 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > >: >I have read it twice now, to be quite honest, this sort of change scares > >: >the hell out of me. It seems like it'd be real easy to make a mondo > >: >security hole out of it due to the usual chroot() risks. No, it has the same protection that LD_PRELOAD does. > >I took a quick peek at it while looking for other security problems, > > Considering the way shared libs work, I would not trust a program in > a chroot sandbox to use the shlibs I use outside. This does >not< > in any way improve security. The only way to break out of the sandbox into the shlib image is if the vm system is broken and permits mprotect() transition to PROT_WRITE/MAP_SHARED of the shlib code area, which was opened as RDONLY and mapped PROT_READ/MAP_COPY. mmap.2 -> [EACCES] The flag PROT_READ was specified as part of the prot param- eter and fd was not open for reading. The flags PROT_WRITE, MAP_SHARED and MAP_WRITE were specified as part of the flags and prot parameters and fd was not open for writing. I haven't tested to see if the vm system is broken. If it is it must be fixed. Dyson? > Complication (and slowing down) the shlib startup is not warranted > by the gain in functionality. Did you actually look at the patch? It only requires an additional getenv (not a system call). There are several in ld.so. L("LD_LIBRARY_PATH=", 1, &ld_library_path) L("LD_PRELOAD=", 1, &ld_preload) L("LD_IGNORE_MISSING_OBJECTS=", 1, &ld_ignore_missing_objects) L("LD_TRACE_LOADED_OBJECTS=", 0, &ld_tracing) L("LD_BIND_NOW=", 0, &ld_bind_now) L("LD_SUPPRESS_WARNINGS=", 0, &ld_suppress_warnings) L("LD_WARN_NON_PURE_CODE=", 0, &ld_warn_non_pure_code) > You can obtain the same savings in disk by hardlinking the copies of > the shlibs together (since they're probably on the same filesystem anyway. Oh boy. > I vote >NO< to this change. Maybe you should read your signature first ;) > -- > Poul-Henning Kamp | phk@FreeBSD.ORG FreeBSD Core-team. > http://www.freebsd.org/~phk | phk@login.dknet.dk Private mailbox. > whois: [PHK] | phk@tfs.com TRW Financial Systems, Inc. > Power and ignorance is a disgusting cocktail. -- Prof. Julian Assange |If you want to build a ship, don't drum up people |together to collect wood and don't assign them tasks proff@iq.org |and work, but rather teach them to long for the endless proff@gnu.ai.mit.edu |immensity of the sea. -- Antoine de Saint Exupery From owner-freebsd-hackers Sun Feb 23 00:16:11 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id AAA27955 for hackers-outgoing; Sun, 23 Feb 1997 00:16:11 -0800 (PST) Received: from profane.iq.org (profane.iq.org [203.4.184.217]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id AAA27891; Sun, 23 Feb 1997 00:15:49 -0800 (PST) Received: (from proff@localhost) by profane.iq.org (8.8.4/8.8.2) id TAA10018; Sun, 23 Feb 1997 19:10:20 +1100 (EST) From: Julian Assange Message-Id: <199702230810.TAA10018@profane.iq.org> Subject: Re: o [1997/02/01] bin/2634 rtld patches for easy creation of chroot enviroments In-Reply-To: <199702210853.QAA15189@spinner.DIALix.COM> from Peter Wemm at "Feb 21, 97 04:53:33 pm" To: peter@spinner.DIALix.COM (Peter Wemm) Date: Sun, 23 Feb 1997 19:10:20 +1100 (EST) Cc: hackers@freebsd.org, security@freebsd.org X-Mailer: ELM [version 2.4ME+ PL28 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > What's to stop a user from setting LD_CHROOT to a "hostile" invironment, > running a setuid program (which ignores LD_CHROOT), which happens to set > it's uid's to the new id, and that process exec's some binary with uid == > euid now, so that new binary now takes note of LD_CHROOT and is now > vulnerable to the "hostile" chroot environment... Same argument applies to all the LD_* variables. This technique was used to undermine the sync:: account under sunos with login -p etc > Also, wouldn't this be better in crt0.c so it'd be usable for statically > linked binaries? crt0.c should be as minimal as possible (since it is linked with all code) , and the crt0.c solution requires relinking of all binaries (which may not be possible). Further, statics don't have as much need for this type of thing. > Hmm.. another thing.. Once the chroot has happened, nothing removes the > LD_CHROOT variable from the environment.. Any sub processes will also try > to chroot within the chroot space.. This chould be a bit noisy.. :-] You shouldn't be running sub-processes in the chroot space that are dynamically linked, because they won't be able to get at the shlibs or ld.so. None-the-less it is probably worthwhile zorching LD_CHROOT when chroot() is called. -- Prof. Julian Assange |If you want to build a ship, don't drum up people |together to collect wood and don't assign them tasks proff@iq.org |and work, but rather teach them to long for the endless proff@gnu.ai.mit.edu |immensity of the sea. -- Antoine de Saint Exupery From owner-freebsd-hackers Sun Feb 23 00:20:07 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id AAA28160 for hackers-outgoing; Sun, 23 Feb 1997 00:20:07 -0800 (PST) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id AAA28155 for ; Sun, 23 Feb 1997 00:20:04 -0800 (PST) Received: from time.cdrom.com (jkh@localhost [127.0.0.1]) by time.cdrom.com (8.8.5/8.6.9) with ESMTP id AAA22537 for ; Sun, 23 Feb 1997 00:19:58 -0800 (PST) To: hackers@freebsd.org Subject: Please welcome Mike Pritchard, GNATSmeister! Date: Sun, 23 Feb 1997 00:19:58 -0800 Message-ID: <22533.856685998@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Mike Pritchard has been kind enough to take over that most thankless role of GNATSmeister, just another one of those guys-behind-the-scenes who keep FreeBSD running. His job is to oversee the GNATS database and generally tries to keep our bug reporting mechanism both sane and reasonably up-to-date in the features it offers, so if you have any problems to report or suggestions to make concerning the bug reporting system, now you know who to ask! :-) Thanks, Mike. Jordan From owner-freebsd-hackers Sun Feb 23 01:36:11 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id BAA01822 for hackers-outgoing; Sun, 23 Feb 1997 01:36:11 -0800 (PST) Received: from rah.star-gate.com (rah.star-gate.com [204.188.121.18]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id BAA01816 for ; Sun, 23 Feb 1997 01:36:06 -0800 (PST) Received: from rah.star-gate.com (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.8.5/8.7.3) with ESMTP id BAA05670; Sun, 23 Feb 1997 01:35:59 -0800 (PST) Message-Id: <199702230935.BAA05670@rah.star-gate.com> X-Mailer: exmh version 1.6.9 8/22/96 To: Mark Mayo cc: hackers@FreeBSD.ORG Subject: Re: CTPPRO? In-reply-to: Your message of "Sun, 23 Feb 1997 00:02:37 EST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 23 Feb 1997 01:35:59 -0800 From: Amancio Hasty Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Hi, I found a device driver called perfmon in -current. It can read the model specific registers and write them (rdmsr and wrmsr). Additionally, if you search the web for Intel Secrets and look up Pentium Pro Family Developer's Manual in Appendix C it has a description for the Model specific registers. The filename is 242692_1.pdf . I think that these are all the bits that we need to implement fastvid 8) Enjoy, Amancio From owner-freebsd-hackers Sun Feb 23 02:36:53 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id CAA03191 for hackers-outgoing; Sun, 23 Feb 1997 02:36:53 -0800 (PST) Received: from paris.CS.Berkeley.EDU (paris.CS.Berkeley.EDU [128.32.34.47]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id CAA03186 for ; Sun, 23 Feb 1997 02:36:51 -0800 (PST) Received: from paris.CS.Berkeley.EDU (localhost.Berkeley.EDU [127.0.0.1]) by paris.CS.Berkeley.EDU (8.8.3/8.8.2) with ESMTP id CAA16290 for ; Sun, 23 Feb 1997 02:36:50 -0800 (PST) From: Josh MacDonald Message-Id: <199702231036.CAA16290@paris.CS.Berkeley.EDU> To: freebsd-hackers@freebsd.org Subject: killing traced processes MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <16283.856694207.1@paris.CS.Berkeley.EDU> Date: Sun, 23 Feb 1997 02:36:48 -0800 Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I sometimes run into the following: * Running process in gdb. * Interupt, process ends up stopped, I don't really know how tracing works, so I don't know exactly what happens. ps shows state="TX", meaning trace and stopped. * type "kill", and it doesn't die. At first I tried to blame gdb and checked the source, but all it does is call kill (pid, SIGKILL), so I tried it from the shell and sure enough, it won't die. Its a little annoying, I have to exit the gdb before the process will die. Can anyone else reproduce or explain this? -josh From owner-freebsd-hackers Sun Feb 23 03:15:21 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id DAA04889 for hackers-outgoing; Sun, 23 Feb 1997 03:15:21 -0800 (PST) Received: from paris.CS.Berkeley.EDU (paris.CS.Berkeley.EDU [128.32.34.47]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id DAA04884 for ; Sun, 23 Feb 1997 03:15:18 -0800 (PST) Received: from paris.CS.Berkeley.EDU (localhost.Berkeley.EDU [127.0.0.1]) by paris.CS.Berkeley.EDU (8.8.3/8.8.2) with ESMTP id DAA16417 for ; Sun, 23 Feb 1997 03:15:17 -0800 (PST) From: Josh MacDonald Message-Id: <199702231115.DAA16417@paris.CS.Berkeley.EDU> To: freebsd-hackers@freebsd.org Subject: more on killing traced processes MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <16410.856696513.1@paris.CS.Berkeley.EDU> Date: Sun, 23 Feb 1997 03:15:15 -0800 Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Sorry for giving so little info. Jordan replied off list with an example of how not to show this behaviour, so I'll provide an example. Run gdb on /bin/cat: Current directory is /bin/ GDB is free software and you are welcome to distribute copies of it under certain conditions; type "show copying" to see the conditions. There is absolutely no warranty for GDB; type "show warranty" for details. GDB 4.16 (i386-unknown-freebsd), Copyright 1996 Free Software Foundation, Inc... (no debugging symbols found)... (gdb) run Starting program: /bin/cat Program received signal SIGINT, Interrupt. 0xe7b5 in ?? () (gdb) kill Kill the program being debugged? (y or n) y (gdb) A second attempt to kill from gdb reports, "The program is not being run." Investigation from 'ps' output shows that the /bin/cat process is still running, in the TX state. Running "kill -9 PID" will not kill the process. Only when the parent exits can it die. -josh From owner-freebsd-hackers Sun Feb 23 04:38:56 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id EAA08109 for hackers-outgoing; Sun, 23 Feb 1997 04:38:56 -0800 (PST) Received: from awfulhak.demon.co.uk (awfulhak.demon.co.uk [158.152.17.1]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id EAA08090; Sun, 23 Feb 1997 04:38:48 -0800 (PST) Received: from awfulhak.demon.co.uk (localhost.coverform.lan [127.0.0.1]) by awfulhak.demon.co.uk (8.8.5/8.7.3) with ESMTP id MAA14310; Sun, 23 Feb 1997 12:04:52 GMT Message-Id: <199702231204.MAA14310@awfulhak.demon.co.uk> X-Mailer: exmh version 1.6.9 8/22/96 To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) cc: mark@quickweb.com (Mark Mayo), hackers@freebsd.org, questions@freebsd.org Subject: Re: Install to second hard-drive... In-reply-to: Your message of "Sat, 22 Feb 1997 12:43:50 +0100." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 23 Feb 1997 12:04:52 +0000 From: Brian Somers Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > As Joerg Wunsch wrote: > I don't know whether booteasy can handle more than one drive. I > remember somebody saying that os-bs is better in this respect. > osbs20b8 works with more than one drive, and is pretty (it gives you a nice menu), but not with some BIOSs - specifically any laptops I've tried (but then, you won't have two disks, so os-bs, the previous version, will suffice). The problem with osbs20b8 however may be a geometry thing. I found it impossible to convince DOS of the correct geometry - it insisted on 60 heads, and the BIOS only allows up to 15. As osbs20b8 installs through DOS, and writes to more than the first sector, this causes problems.... Does anyone know where DOS gets it's geometry from ? I've tried writing the correct values into that control block thingy, but it didn't help. I eventually stuck with the BIOS's idea - it means that suspend/resume work, and was the same as the recommended geometry in the drive spec. -- Brian , Don't _EVER_ lose your sense of humour.... From owner-freebsd-hackers Sun Feb 23 04:58:41 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id EAA08768 for hackers-outgoing; Sun, 23 Feb 1997 04:58:41 -0800 (PST) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id EAA08750; Sun, 23 Feb 1997 04:58:36 -0800 (PST) Received: from time.cdrom.com (jkh@localhost [127.0.0.1]) by time.cdrom.com (8.8.5/8.6.9) with ESMTP id EAA05774; Sun, 23 Feb 1997 04:58:15 -0800 (PST) To: Brian Somers cc: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch), mark@quickweb.com (Mark Mayo), hackers@freebsd.org, questions@freebsd.org Subject: Re: Install to second hard-drive... In-reply-to: Your message of "Sun, 23 Feb 1997 12:04:52 GMT." <199702231204.MAA14310@awfulhak.demon.co.uk> Date: Sun, 23 Feb 1997 04:58:15 -0800 Message-ID: <5770.856702695@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > As Joerg Wunsch wrote: > > > I don't know whether booteasy can handle more than one drive. I > > remember somebody saying that os-bs is better in this respect. > > > osbs20b8 works with more than one drive, and is pretty (it gives you > a nice menu), but not with some BIOSs - specifically any laptops I've > tried (but then, you won't have two disks, so os-bs, the previous version, > will suffice). Well, my own experience with 2.1.7 and the following configuration: Generic 486 blah blah 2 IDE HDs 1 AHA 1542 w/HD + CDROM DOS is on 1st HD, FreeBSD on 2nd and 3rd HDs (all 3 of which DOS can see when doing a "full" DOS install with its defaults). When the 2.1.7 system initially comes up off the HD (install goes great, without a hitch) you get BOOTEASY with the following prompt: F? DOS And that's it. No other choices! First time I tried selecting just the first drive for a boot manager. No joy. Then I reinstalled and said "boot manager" for every drive. No change. Then I tried installing BOOTEASY by hand by running bootinst.exe with boot.bin. No difference. Then I installed OSBS20BETA and lo-and-behold it saw the 2nd drive and its FreeBSD partition, allowing me to add it to the boot menu. I rebooted and now I could get to the FreeBSD boot blocks, typing in: 1:wd(1,a)/kernel for a successful boot into FreeBSD. So just one bit of first-hand testimony that booteasy may not quite be a 100% solution. :-( Jordan From owner-freebsd-hackers Sun Feb 23 05:55:11 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id FAA10637 for hackers-outgoing; Sun, 23 Feb 1997 05:55:11 -0800 (PST) Received: from nic.follonett.no (nic.follonett.no [194.198.43.10]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id FAA10619; Sun, 23 Feb 1997 05:55:05 -0800 (PST) Received: (from uucp@localhost) by nic.follonett.no (8.8.5/8.8.3) with UUCP id OAA02292; Sun, 23 Feb 1997 14:53:00 +0100 (MET) Received: from oo7 (oo7.dimaga.com [192.0.0.65]) by dimaga.com (8.8.5/8.7.2) with SMTP id OAA11550; Sun, 23 Feb 1997 14:49:02 +0100 (MET) Message-Id: <3.0.32.19970223144902.00c19100@dimaga.com> X-Sender: eivind@dimaga.com X-Mailer: Windows Eudora Pro Version 3.0 (32) Date: Sun, 23 Feb 1997 14:49:03 +0100 To: Julian Assange From: Eivind Eklund Subject: Re: o [1997/02/01] bin/2634 rtld patches for easy creation of chroot enviroments Cc: peter@spinner.DIALix.COM (Peter Wemm), hackers@freebsd.org, security@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk At 07:10 PM 2/23/97 +1100, Julian Assange wrote: >> What's to stop a user from setting LD_CHROOT to a "hostile" invironment, >> running a setuid program (which ignores LD_CHROOT), which happens to set >> it's uid's to the new id, and that process exec's some binary with uid == >> euid now, so that new binary now takes note of LD_CHROOT and is now >> vulnerable to the "hostile" chroot environment... > >Same argument applies to all the LD_* variables. This technique was used >to undermine the sync:: account under sunos with login -p etc Not quite. If we allow users to do this to setuid binaries, they can make setuid programs read dangerous config files, and exploit the new behaviour. A really simple example would be to create a fake /etc with a new master.passwd and run su. Sure, you have su only in the chroot()ed environment, but you could easily create a new suid binary... There is a reason chroot() is restricted to root, and I think we'd better keep that. If the patch was changed to restrict use to non-suid only (ie, root only), I'd be much more comfortable with it. Eivind Eklund perhaps@yes.no http://maybe.yes.no/perhaps/ eivind@freebsd.org From owner-freebsd-hackers Sun Feb 23 06:18:55 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id GAA11670 for hackers-outgoing; Sun, 23 Feb 1997 06:18:55 -0800 (PST) Received: from server3.syd.mail.ozemail.net (server3.syd.mail.ozemail.net [203.108.7.41]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id GAA11650; Sun, 23 Feb 1997 06:18:49 -0800 (PST) Received: from shell01.ozemail.com.au (rlyon@shell01.ozemail.com.au [203.2.192.162]) by server3.syd.mail.ozemail.net (8.8.4/8.6.12) with ESMTP id BAA29933; Mon, 24 Feb 1997 01:18:24 +1100 (EST) Received: (from rlyon@localhost) by shell01.ozemail.com.au (8.8.4/8.6.12) id BAA17041; Mon, 24 Feb 1997 01:18:18 +1100 (EST) Date: Mon, 24 Feb 1997 01:18:17 +1100 (EST) From: Richard Lyon To: "Jordan K. Hubbard" cc: Brian Somers , Joerg Wunsch , Mark Mayo , hackers@freebsd.org, questions@freebsd.org Subject: Re: Install to second hard-drive... In-Reply-To: <5770.856702695@time.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Sun, 23 Feb 1997, Jordan K. Hubbard wrote: > Well, my own experience with 2.1.7 and the following configuration: > > Generic 486 blah blah > 2 IDE HDs > 1 AHA 1542 w/HD + CDROM > With 2.1.5 and the following configuration: Generic 486 1 IDE HD 1 AHA 1542 w/HD + CDROM FBSD is on the IDE drive and NT4 is on the SCSI drive. BOOTEASY sees both drives, but of course you can only boot of the first drive because of the limitations of BIOS and the 1542. I use BIOS to switch between NT and FBSD. I always want to be absolutely certain that nothing NT can touch FBSD and vice versa. The current rumour is that a certain NT defragmenter does a lot more than defrag drives (Ref. OP. Alice). Regards ... From owner-freebsd-hackers Sun Feb 23 06:21:23 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id GAA11844 for hackers-outgoing; Sun, 23 Feb 1997 06:21:23 -0800 (PST) Received: from profane.iq.org (profane.iq.org [203.4.184.217]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id GAA11822; Sun, 23 Feb 1997 06:21:14 -0800 (PST) Received: (from proff@localhost) by profane.iq.org (8.8.4/8.8.2) id BAA10178; Mon, 24 Feb 1997 01:16:47 +1100 (EST) From: Julian Assange Message-Id: <199702231416.BAA10178@profane.iq.org> Subject: Re: o [1997/02/01] bin/2634 rtld patches for easy creation of chroot enviroments In-Reply-To: <3.0.32.19970223144902.00c19100@dimaga.com> from Eivind Eklund at "Feb 23, 97 02:49:03 pm" To: eivind@dimaga.com (Eivind Eklund) Date: Mon, 24 Feb 1997 01:16:47 +1100 (EST) Cc: hackers@freebsd.org, security@freebsd.org X-Mailer: ELM [version 2.4ME+ PL28 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > Not quite. If we allow users to do this to setuid binaries, they can make > setuid programs read dangerous config files, and exploit the new behaviour. > A really simple example would be to create a fake /etc with a new > master.passwd and run su. Sure, you have su only in the chroot()ed > environment, but you could easily create a new suid binary... > > There is a reason chroot() is restricted to root, and I think we'd better > keep that. If the patch was changed to restrict use to non-suid only (ie, > root only), I'd be much more comfortable with it. It is restricted to non-suid, just the same as LD_PRELOAD is. There is an "unsafe" field in the scan_tab for all enviromental variables used by ld.so. It's set to on for LD_CHROOT. You may want to have a look at this before presuming I'm a complete fool ;) -- Prof. Julian Assange |If you want to build a ship, don't drum up people |together to collect wood and don't assign them tasks proff@iq.org |and work, but rather teach them to long for the endless proff@gnu.ai.mit.edu |immensity of the sea. -- Antoine de Saint Exupery From owner-freebsd-hackers Sun Feb 23 06:51:39 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id GAA13654 for hackers-outgoing; Sun, 23 Feb 1997 06:51:39 -0800 (PST) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id GAA13648 for ; Sun, 23 Feb 1997 06:51:36 -0800 (PST) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id PAA23444 for hackers@freebsd.org; Sun, 23 Feb 1997 15:51:34 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.8.5/8.8.5) id PAA08689; Sun, 23 Feb 1997 15:49:09 +0100 (MET) Message-ID: Date: Sun, 23 Feb 1997 15:49:08 +0100 From: j@uriah.heep.sax.de (J Wunsch) To: hackers@freebsd.org Subject: Re: Install to second hard-drive... References: <199702231204.MAA14310@awfulhak.demon.co.uk> <5770.856702695@time.cdrom.com> X-Mailer: Mutt 0.55-PL10 Mime-Version: 1.0 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <5770.856702695@time.cdrom.com>; from Jordan K. Hubbard on Feb 23, 1997 04:58:15 -0800 Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk As Jordan K. Hubbard wrote: > So just one bit of first-hand testimony that booteasy may not quite be > a 100% solution. :-( UTSL. BootEasy is only prepared to handle two disks. However, it's also buggy in that it thinks that anything other than two disks must mean `one disk': cmp BYTE PTR DS:NumDisks,2 ; is the second disk present? je have2disks ; have disk 2 The `je' needs to be changed into a `jge' (or is it `jae'? too long ago i've been hacking DOS asm last time) in order to at least do two disks if more than two are present. Fixing it for handling an arbitrary number of disks is more complicated, since it make weird assumptions all over the place. -- 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-hackers Sun Feb 23 06:54:47 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id GAA13809 for hackers-outgoing; Sun, 23 Feb 1997 06:54:47 -0800 (PST) Received: from bofh.cybercity.dk (bofh.cybercity.dk [195.8.128.254]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id GAA13777; Sun, 23 Feb 1997 06:54:41 -0800 (PST) Received: from critter.dk.tfs.com (phk.cybercity.dk [195.8.133.247]) by bofh.cybercity.dk (8.8.3/8.7.3) with ESMTP id PAA06885; Sun, 23 Feb 1997 15:56:54 +0100 (MET) Received: from critter.dk.tfs.com (localhost [127.0.0.1]) by critter.dk.tfs.com (8.8.2/8.8.2) with ESMTP id PAA02532; Sun, 23 Feb 1997 15:57:23 +0100 (MET) To: Julian Assange cc: eivind@dimaga.com (Eivind Eklund), hackers@freebsd.org, security@freebsd.org Subject: Re: o [1997/02/01] bin/2634 rtld patches for easy creation of chroot enviroments In-reply-to: Your message of "Mon, 24 Feb 1997 01:16:47 +1100." <199702231416.BAA10178@profane.iq.org> Date: Sun, 23 Feb 1997 15:57:22 +0100 Message-ID: <2530.856709842@critter.dk.tfs.com> From: Poul-Henning Kamp Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In message <199702231416.BAA10178@profane.iq.org>, Julian Assange writes: >> Not quite. If we allow users to do this to setuid binaries, they can make >> setuid programs read dangerous config files, and exploit the new behaviour. >> A really simple example would be to create a fake /etc with a new >> master.passwd and run su. Sure, you have su only in the chroot()ed >> environment, but you could easily create a new suid binary... >> >> There is a reason chroot() is restricted to root, and I think we'd better >> keep that. If the patch was changed to restrict use to non-suid only (ie, >> root only), I'd be much more comfortable with it. > >It is restricted to non-suid, just the same as LD_PRELOAD is. There >is an "unsafe" field in the scan_tab for all enviromental variables >used by ld.so. It's set to on for LD_CHROOT. You may want to have >a look at this before presuming I'm a complete fool ;) Listen, this patch is maybe or maybe not correct, but it certainly is pointless. For anything as little used as chroot to clobber the one of the most timecritical piece of code in userland is simply not an option, in particular where there isn't any better argumentation that "it would be neat of one could..." Can this discussion please be taken offline now ? -- Poul-Henning Kamp | phk@FreeBSD.ORG FreeBSD Core-team. http://www.freebsd.org/~phk | phk@login.dknet.dk Private mailbox. whois: [PHK] | phk@tfs.com TRW Financial Systems, Inc. Power and ignorance is a disgusting cocktail. From owner-freebsd-hackers Sun Feb 23 07:19:21 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id HAA15053 for hackers-outgoing; Sun, 23 Feb 1997 07:19:21 -0800 (PST) Received: from vinyl.quickweb.com (vinyl.quickweb.com [206.222.77.8]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id HAA15035; Sun, 23 Feb 1997 07:19:17 -0800 (PST) Received: from localhost (mark@localhost) by vinyl.quickweb.com (8.7.5/8.6.12) with SMTP id KAA01248; Sun, 23 Feb 1997 10:19:58 -0500 (EST) Date: Sun, 23 Feb 1997 10:19:58 -0500 (EST) From: Mark Mayo To: "Jordan K. Hubbard" cc: Brian Somers , Joerg Wunsch , hackers@freebsd.org, questions@freebsd.org Subject: Re: Install to second hard-drive... In-Reply-To: <5770.856702695@time.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Sun, 23 Feb 1997, Jordan K. Hubbard wrote: > > > As Joerg Wunsch wrote: > > > > > I don't know whether booteasy can handle more than one drive. I > > > remember somebody saying that os-bs is better in this respect. > > > > > osbs20b8 works with more than one drive, and is pretty (it gives you > > a nice menu), but not with some BIOSs - specifically any laptops I've > > tried (but then, you won't have two disks, so os-bs, the previous version, > > will suffice). > > Well, my own experience with 2.1.7 and the following configuration: > DOS is on 1st HD, FreeBSD on 2nd and 3rd HDs (all 3 of which > DOS can see when doing a "full" DOS install with its defaults). > > When the 2.1.7 system initially comes up off the HD (install goes > great, without a hitch) you get BOOTEASY with the following prompt: > > F? DOS > > And that's it. No other choices! First time I tried selecting just > the first drive for a boot manager. No joy. Then I reinstalled and > said "boot manager" for every drive. No change. Then I tried > installing BOOTEASY by hand by running bootinst.exe with boot.bin. No Same here. I tried every damn combination of boot manager / standard MBR on each drive, but I couldn't get Boot Easy to see the second FreeBSD hard disk.. Bummer. > difference. Then I installed OSBS20BETA and lo-and-behold it saw the > 2nd drive and its FreeBSD partition, allowing me to add it to the > boot menu. I rebooted and now I could get to the FreeBSD boot blocks, > typing in: 1:wd(1,a)/kernel for a successful boot into FreeBSD. > I'll recommend the OSBS20BETA to my friend, and see if that works. I think the hours of frustration have gotten to him, however, and he decided to nuke win95 and use the first disk for FreeBSD. So, in a way, it turned out to be a happy story :-) Last I saw him, he was ranting about the Microsoft philosphy of making it damn near impossible to boot another OS, and how he refused "to accomodate M$" :-) For the record, I've happily used BOOTEASY on a single disk, with two OS's, but all hell breaks loose when you try to setup multiple disks.. -Mark > So just one bit of first-hand testimony that booteasy may not quite be > a 100% solution. :-( > > Jordan > ---------------------------------------------------------------------------- Mark Mayo mark@quickweb.com RingZero Comp. http://vinyl.quickweb.com/mark ---------------------------------------------------------------------------- Nature shows that with the growth of intelligence comes increased capacity for pain, and it is only with the highest degree of intelligence that suffering reaches its supreme point. -- Arthur Schopenhauer From owner-freebsd-hackers Sun Feb 23 07:24:05 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id HAA15338 for hackers-outgoing; Sun, 23 Feb 1997 07:24:05 -0800 (PST) Received: from vinyl.quickweb.com (vinyl.quickweb.com [206.222.77.8]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id HAA15286; Sun, 23 Feb 1997 07:23:58 -0800 (PST) Received: from localhost (mark@localhost) by vinyl.quickweb.com (8.7.5/8.6.12) with SMTP id KAA01269; Sun, 23 Feb 1997 10:24:33 -0500 (EST) Date: Sun, 23 Feb 1997 10:24:33 -0500 (EST) From: Mark Mayo To: Richard Lyon cc: "Jordan K. Hubbard" , Brian Somers , Joerg Wunsch , hackers@freebsd.org, questions@freebsd.org Subject: Re: Install to second hard-drive... In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Mon, 24 Feb 1997, Richard Lyon wrote: > On Sun, 23 Feb 1997, Jordan K. Hubbard wrote: > > > Well, my own experience with 2.1.7 and the following configuration: > > > > Generic 486 blah blah > > 2 IDE HDs > > 1 AHA 1542 w/HD + CDROM > > > With 2.1.5 and the following configuration: > > Generic 486 > 1 IDE HD > 1 AHA 1542 w/HD + CDROM > > FBSD is on the IDE drive and NT4 is on the SCSI drive. > > BOOTEASY sees both drives, but of course you can only boot of the first > drive because of the limitations of BIOS and the 1542. > > I use BIOS to switch between NT and FBSD. I always want to be absolutely > certain that nothing NT can touch FBSD and vice versa. FWIW, I have NT on the first SCSI disk, and FreeBSD on the second - so there is clean separation.. I use the NT boot manager to boot FreeBSD and NT. Works great - just use the "standard MBR" on the FreeBSD disk (sd1), and copy the first 512 bytes of the disk to a file called "BOOTBSD.BIN" on the NT "C:" drive, and edit the BOOT.INI file to add an entry for the BOOTBSD.BIN file. I figured I might as well use the NT boot manager since it was already there, and it has a nice little menu system :-) -Mark > > The current rumour is that a certain NT defragmenter does a lot more than > defrag drives (Ref. OP. Alice). > > Regards ... > ---------------------------------------------------------------------------- Mark Mayo mark@quickweb.com RingZero Comp. http://vinyl.quickweb.com/mark ---------------------------------------------------------------------------- Nature shows that with the growth of intelligence comes increased capacity for pain, and it is only with the highest degree of intelligence that suffering reaches its supreme point. -- Arthur Schopenhauer From owner-freebsd-hackers Sun Feb 23 09:30:07 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id JAA20324 for hackers-outgoing; Sun, 23 Feb 1997 09:30:07 -0800 (PST) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.50]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id JAA20314 for ; Sun, 23 Feb 1997 09:30:04 -0800 (PST) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id KAA06404; Sun, 23 Feb 1997 10:25:40 -0700 From: Terry Lambert Message-Id: <199702231725.KAA06404@phaeton.artisoft.com> Subject: Re: Sun Workshop compiler vs. GCC? To: jamie@inna.net (Jamie Bowden) Date: Sun, 23 Feb 1997 10:25:40 -0700 (MST) Cc: terry@lambert.org, jehamby@lightside.com, nate@mt.sri.com, toneil@visigenic.com, jfieber@indiana.edu, hackers@freebsd.org In-Reply-To: from "Jamie Bowden" at Feb 20, 97 10:20:08 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-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I have just finished an install of the commercial, rathe than the MSDN Windows95 with the driver that Jamie Bowden suggested: device=c:\sb16\sbcd.sys I was incorrect about the Windows95 install process, though it took the commercial install and this exact driver (not a fake) to trigger it leaving a 16 bit driver in the config.sys. I claim that I had to go way off the beaten track to confirm it, and that it is unreasonable to expect me (or any *reasonable* person, who would be using a SCSI CDROM drive) to have travelled that same path, other than unwittingly. I further claim that the fact that I was wrong is irrelevant, since many 16 bit drivers *still* do not work "happily" without serious changes away from the Microsoft defined Windows95 default configuration; any driver which hooks INT 21 rather than INT 13, or the INT 27 "DOS not busy" interrupt, will still fail. 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-hackers Sun Feb 23 09:31:31 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id JAA20448 for hackers-outgoing; Sun, 23 Feb 1997 09:31:31 -0800 (PST) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.50]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id JAA20443 for ; Sun, 23 Feb 1997 09:31:26 -0800 (PST) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id KAA06419; Sun, 23 Feb 1997 10:29:11 -0700 From: Terry Lambert Message-Id: <199702231729.KAA06419@phaeton.artisoft.com> Subject: Re: Alternatives to SYSV IPC? To: matt@lkg.dec.com (Matt Thomas) Date: Sun, 23 Feb 1997 10:29:11 -0700 (MST) Cc: terry@lambert.org, hackers@FreeBSD.ORG In-Reply-To: <3.0.32.19970222213738.006a1cb0@netrix.lkg.dec.com> from "Matt Thomas" at Feb 22, 97 09:37:46 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-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > This can be done today with the BSD4.4 socket framework. With AF_LOCAL > (AF_UNIX) sockets and the use of MSG_EOR with send() and MSG_WAITALL > with recvmsg() it does work. I've attached a small example program > (which works under FreeBSD 2.1.0 and Digital UNIX 4.0). Matt: Thank you for this example! 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-hackers Sun Feb 23 14:53:48 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id OAA06842 for hackers-outgoing; Sun, 23 Feb 1997 14:53:48 -0800 (PST) Received: from whqvax.picker.com (whqvax.picker.com [144.54.1.1]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id OAA06833 for ; Sun, 23 Feb 1997 14:53:44 -0800 (PST) Received: from ct.picker.com by whqvax.picker.com with SMTP; Sun, 23 Feb 1997 17:53:13 -0500 (EST) Received: from elmer.ct.picker.com ([144.54.57.34]) by ct.picker.com (4.1/SMI-4.1) id AA01742; Sun, 23 Feb 97 17:53:11 EST Received: by elmer.ct.picker.com (SMI-8.6/SMI-SVR4) id RAA29677; Sun, 23 Feb 1997 17:50:59 -0500 Message-Id: <19970223175059.45312@ct.picker.com> Date: Sun, 23 Feb 1997 17:50:59 -0500 From: Randall Hopper To: hackers@freebsd.org Subject: dd of=/dev/rwd1s2 -- How? Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.61 Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk # dd if=img of=/dev/rwd1s2 gives me: dd: /dev/rwd1s2: Read-only file system 2+0 records in 1+0 records out 512 bytes transferred in 0.063062 secs (8119 bytes/sec) How do I write a saved slice image directly on top of a slice? Is there a way get a writable raw slice device? Thanks, Randall Hopper From owner-freebsd-hackers Sun Feb 23 15:50:21 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id PAA10481 for hackers-outgoing; Sun, 23 Feb 1997 15:50:21 -0800 (PST) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id PAA10475 for ; Sun, 23 Feb 1997 15:50:18 -0800 (PST) Received: from time.cdrom.com (jkh@localhost [127.0.0.1]) by time.cdrom.com (8.8.5/8.6.9) with ESMTP id PAA15472; Sun, 23 Feb 1997 15:50:05 -0800 (PST) To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) cc: hackers@FreeBSD.ORG Subject: Re: Install to second hard-drive... In-reply-to: Your message of "Sun, 23 Feb 1997 15:49:08 +0100." Date: Sun, 23 Feb 1997 15:50:04 -0800 Message-ID: <15468.856741804@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > UTSL. > > BootEasy is only prepared to handle two disks. However, it's also > buggy in that it thinks that anything other than two disks must mean > `one disk': Doesn't do me a lot of good - I don't have a DOS development environment for recompiling it. :-) Jordan From owner-freebsd-hackers Sun Feb 23 16:21:21 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id QAA11774 for hackers-outgoing; Sun, 23 Feb 1997 16:21:21 -0800 (PST) Received: from mail.calweb.com (mail.calweb.com [208.131.56.11]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id QAA11768 for ; Sun, 23 Feb 1997 16:21:18 -0800 (PST) Received: from hell.gigo.com (hell.gigo.com [207.173.133.59]) by mail.calweb.com (8.8.5/8.8.5) with SMTP id QAA18063; Sun, 23 Feb 1997 16:19:57 -0800 (PST) Message-Id: <3.0.1.32.19970223161919.00714898@pop.calweb.com> X-Sender: jfesler@pop.calweb.com X-Mailer: Windows Eudora Pro Version 3.0.1 (32) Date: Sun, 23 Feb 1997 16:19:19 -0800 To: "Jordan K. Hubbard" , joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) From: Jason Fesler Subject: Re: Install to second hard-drive... Cc: hackers@FreeBSD.ORG In-Reply-To: <15468.856741804@time.cdrom.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk At 03:50 PM 2/23/97 -0800, Jordan K. Hubbard wrote: >> UTSL. >> >> BootEasy is only prepared to handle two disks. However, it's also >> buggy in that it thinks that anything other than two disks must mean >> `one disk': > >Doesn't do me a lot of good - I don't have a DOS development environment >for recompiling it. :-) I'm stepping into this a bit late into the game, sorry ;-). How complex is it? I _do_ have DOS and OS2 here; I can use either Watcom or EMX (gcc). Nearly anything gcc'able, is emx'able (indeed: I run a lot of unix->os2 ported material thanks to emx). EMX is not very friendly to Windows users without the "rsx" extender instead of the EMX standard dll/exe extender. Watcom, on the other hand, has a decent 16 bit and a decent 32 bit system, that is perfectly windows happy. From owner-freebsd-hackers Sun Feb 23 17:01:40 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id RAA14496 for hackers-outgoing; Sun, 23 Feb 1997 17:01:40 -0800 (PST) Received: from bastion.seqeb.gov.au (bastion.seqeb.gov.au [147.209.142.2]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id RAA14485 for ; Sun, 23 Feb 1997 17:01:34 -0800 (PST) Received: by bastion.seqeb.gov.au; (5.65/GJW290197a) id AA29670; Mon, 24 Feb 1997 10:59:40 +1000 Received: from proxy.seqeb.gov.au(147.209.206.2) by bastion.seqeb.gov.au via smap (V1.3) id sma032360; Mon Feb 24 10:59:03 1997 Received: by proxy.seqeb.gov.au; (5.65v3.2/GJW290197a) id AA07644; Mon, 24 Feb 1997 10:59:02 +1000 Received: from relay.seqeb.gov.au(147.209.166.6) by proxy.seqeb.gov.au via smap (V1.3) id sma008080; Mon Feb 24 10:58:26 1997 Received: from svbyo4.seqeb.gov.au by un.seqeb.gov.au; (5.65/GJW070297a) id AA28616; Mon, 24 Feb 1997 10:58:16 +1000 Received: by svbyo4.seqeb.gov.au; (5.65/GJW251095a) id AA17259; Mon, 24 Feb 1997 10:58:15 +1000 Date: Mon, 24 Feb 1997 10:58:14 +1000 (EST) From: patrick collins Subject: Re: Device driver cookbook. To: "Brian J. McGovern" Cc: hackers@freebsd.org In-Reply-To: <199702221509.KAA12718@spoon.beta.com> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I really appreciated your example device driver. Your explanation was very easy to understand and I look forward to further posts on this subject. I am particularly interested in writing a device driver for a digital I/O card I have. This card consists of a couple of 8255 PIO's. I would like my device driver to be able to configure one 8255 for input and the other for output. I would like the device driver to be able to read the inputs every n milliseconds in order to be able to count a 2 Hz pulse train on these inputs. I have a fairly general idea on how to go about this but would appreciate any pointers you might have, especially in the area of how to get the device driver to continually read the input ports without the intervention of the application software. ----------------------------------------------------------------------------- Patrick Collins - Load Survey Technician email : pc012@seqeb.gov.au South East Queensland Electricity Corporation phone : +61 7 3407 5954 Blinzinger Rd, Banyo, 4014 fax : +61 7 3407 5454 Queensland, AUSTRALIA (Best State, Best Country) Viva el Cristo Rey ! ----------------------------------------------------------------------------- From owner-freebsd-hackers Sun Feb 23 17:28:18 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id RAA15700 for hackers-outgoing; Sun, 23 Feb 1997 17:28:18 -0800 (PST) Received: from spoon.beta.com (root@[199.165.180.33]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id RAA15695 for ; Sun, 23 Feb 1997 17:28:10 -0800 (PST) Received: from spoon.beta.com (mcgovern@localhost [127.0.0.1]) by spoon.beta.com (8.8.4/8.6.9) with ESMTP id UAA04260; Sun, 23 Feb 1997 20:27:54 -0500 (EST) Message-Id: <199702240127.UAA04260@spoon.beta.com> To: patrick collins cc: hackers@freebsd.org Subject: Driver question on interval execution (polling?) In-reply-to: Your message of "Mon, 24 Feb 1997 10:58:14 +1000." Date: Sun, 23 Feb 1997 20:27:53 -0500 From: "Brian J. McGovern" Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I'm glad you appreciated the post. Unfortuately, I am using the documentation as a learning tool for myself as much as anything, and I'm strugging to master the interface myself. Based on my reading of several device driver books, I am aware of a mechanism to be able to have the kernel re-enter a particular function after a certain time period is past. Using this system, you should be able to do your poll, and then implement the required code so the function will be restarted some time in the future, and then it should terminate. As I don't have my documentation handy (and I've yet to figure out how the docs I do have would apply to FreeBSD specifically), I am forwarding the message to the FreeBSD hackers list, so that perhaps someone with a bit more insight and experience can describe any existing mechanism, or perhaps a better way to handle the case - and can post a response to both of us, so you may have your answer, and I can document the feature when I see the feature as being useful. -Brian > I really appreciated your example device driver. Your explanation was > very easy to understand and I look forward to further posts on this > subject. > > I am particularly interested in writing a device driver for a > digital I/O card I have. This card consists of a couple of 8255 PIO's. I > would like my device driver to be able to configure one 8255 for input > and the other for output. I would like the device driver to be able to > read the inputs every n milliseconds in order to be able to count a 2 Hz > pulse train on these inputs. > > I have a fairly general idea on how to go about this but would appreciate > any pointers you might have, especially in the area of how to get the device > driver to continually read the input ports without the intervention of the > application software. > > ----------------------------------------------------------------------------- > Patrick Collins - Load Survey Technician email : pc012@seqeb.gov.au > South East Queensland Electricity Corporation phone : +61 7 3407 5954 > Blinzinger Rd, Banyo, 4014 fax : +61 7 3407 5454 > Queensland, AUSTRALIA (Best State, Best Country) Viva el Cristo Rey ! > ----------------------------------------------------------------------------- From owner-freebsd-hackers Sun Feb 23 18:19:42 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id SAA18567 for hackers-outgoing; Sun, 23 Feb 1997 18:19:42 -0800 (PST) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id SAA18548 for ; Sun, 23 Feb 1997 18:19:29 -0800 (PST) Received: (from msmith@localhost) by genesis.atrad.adelaide.edu.au (8.8.5/8.7.3) id MAA04053; Mon, 24 Feb 1997 12:49:06 +1030 (CST) From: Michael Smith Message-Id: <199702240219.MAA04053@genesis.atrad.adelaide.edu.au> Subject: Re: Device driver cookbook. In-Reply-To: from patrick collins at "Feb 24, 97 10:58:14 am" To: pc012@seqeb.gov.au (patrick collins) Date: Mon, 24 Feb 1997 12:49:04 +1030 (CST) Cc: mcgovern@spoon.beta.com, hackers@FreeBSD.org X-Mailer: ELM [version 2.4ME+ PL28 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk patrick collins stands accused of saying: > > I am particularly interested in writing a device driver for a > digital I/O card I have. This card consists of a couple of 8255 PIO's. I > would like my device driver to be able to configure one 8255 for input > and the other for output. I would like the device driver to be able to > read the inputs every n milliseconds in order to be able to count a 2 Hz > pulse train on these inputs. > > I have a fairly general idea on how to go about this but would appreciate > any pointers you might have, especially in the area of how to get the device > driver to continually read the input ports without the intervention of the > application software. You want a polling routine that looks something like this : void zog_poller(void *what) { zog_softc *sc = (zog_softc *)what; static int initted = 0; u_char curr; int bit; /* get port value */ curr = inb(sc->base + PORTA); /* have valid state? */ if (initted) { /* check bits */ for (bit = 0; bit < 8; bit++) { /* bit is set, and was clear? */ if ((curr & (1<state & (1<count[bit]++; } } } sc->state = curr; /* update state */ initted = 1; /* definitely initted now */ timeout(zog_poller, what, hz/ZOG_TIMEOUT); } Then you can start the poller when you want with timeout(zog_poller, sc, hz/ZOG_TIMEOUT); where 'sc' is the softc structure for the device in question. The last argument to timeout() is the number of timer ticks between invocations of the routine; 'hz' is the number of ticks per second. In the above example if your pulse train is coming in every two seconds, you'd want to sample at least four times per second (ZOG_TIMEOUT = 4), but you might want to sample faster to compensate for possible periods where interrupt activity makes you lag. You might want to do this in your open routine. You can kill the timeout routine with untimeout(zog_poller, sc)l for eg. in your close() routine. Then you could write a read() handler that uses printf() into a buffer to return the current counter values, or you could just copy them out to the caller as-is. > Patrick Collins - Load Survey Technician email : pc012@seqeb.gov.au -- ]] Mike Smith, Software Engineer msmith@gsoft.com.au [[ ]] Genesis Software genesis@gsoft.com.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control. (ph) +61-8-8267-3493 [[ ]] Unix hardware collector. "Where are your PEZ?" The Tick [[ From owner-freebsd-hackers Sun Feb 23 18:28:43 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id SAA19285 for hackers-outgoing; Sun, 23 Feb 1997 18:28:43 -0800 (PST) Received: from phoenix.its.rpi.edu (dec@phoenix.its.rpi.edu [128.113.161.45]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id SAA19280 for ; Sun, 23 Feb 1997 18:28:41 -0800 (PST) Received: (from dec@localhost) by phoenix.its.rpi.edu (8.8.4/8.8.3) id VAA03134 for hackers@FreeBSD.ORG; Sun, 23 Feb 1997 21:28:53 -0500 (EST) Date: Sun, 23 Feb 1997 21:28:53 -0500 (EST) From: "David E. Cross" Message-Id: <199702240228.VAA03134@phoenix.its.rpi.edu> To: hackers@FreeBSD.ORG Subject: best way to back up? Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk I am curious as to what the "best" way is to back up to a 8mm tape on a different machine. I have found that (for me) tar seems to be the easiest to use, however, I can't get it to do an incremental backup, and it seems to choke on some of the "special" files in /dev. dump/rdump let you me do differential backups, but I can only do one per tape? -- David Cross ACS Consultant From owner-freebsd-hackers Sun Feb 23 19:14:16 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id TAA21577 for hackers-outgoing; Sun, 23 Feb 1997 19:14:16 -0800 (PST) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id TAA21570 for ; Sun, 23 Feb 1997 19:14:11 -0800 (PST) Received: from current1.whistle.com (current1.whistle.com [207.76.205.22]) by alpo.whistle.com (8.8.5/8.8.4) with SMTP id TAA03793; Sun, 23 Feb 1997 19:11:33 -0800 (PST) Message-ID: <33110665.167EB0E7@whistle.com> Date: Sun, 23 Feb 1997 19:09:25 -0800 From: Julian Elischer Organization: Whistle Communications X-Mailer: Mozilla 3.0Gold (X11; I; FreeBSD 2.2-CURRENT i386) MIME-Version: 1.0 To: "Brian J. McGovern" CC: hackers@freebsd.org Subject: Re: Device driver cookbook. References: <199702221509.KAA12718@spoon.beta.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Brian J. McGovern wrote: > > I promised I'd eventually get to it, and I'll be working on it heavily > this weeknd. Below is the first "installment" where I walk through a simple > pseudo-device driver that you can read from with a fixed buffer. Subsequent > additions will make it more flexable. I'm releasing it to "hackers" now, so > that everyone has a chance to comment, and let me know if they like/don't like/ > would like me to change anything. Thanks for the comments ahead of time. the skeletons I checked in to /usr/share/examples do this as well. you migh include a pointer.. (they also get the device filesystem parts correct etc.) a comment.. if open checks the dev_t then read doesn't need to.. (one reason for open is to verify all thes sorts of things) (why I think you shoul dinclude an open() ) > #include > #include > #include > #include > #include > #include > I'd just have hte driver there at teh bottom and not keep reiincluding parts.. just show the bit you are talking about... > character device driver locally). What we will do now is #define CDEV_MAJOR > to be equal to the number we just chose. This is one of those "standards" that > just make sense. You'll find that doing it this way, rather than just > hard-coding the major number, makes it easier to change later, as well as > lets other developers know what to look for, in case they ever have to work > on your driver. It'll also help stop typos, as well. If I get off my rear end and finish devfs, then major numbers can be assigned dynamically (you give a major of -1 and it will do that now) > > You'll notice that the string is declared static. This is so that it will > not conflict with any other variables called "message" elsewhere in the > kernel. You will see, rather quickly, that nearly all global variables, > or exported functions, are declared static. which means that they are not exported.. everything is referenced via the well know structs cdevsw and isa_driver > > Now, we only have a few more things to set up for our device driver. Since > we'll only be concerned about reading from our driver, we'll only concern > ourselves explicitly with the read routine. We will "fake" the open > and close routines for the time being, so that they will always succeed. Note, > that this can cause problems, simply because they'll be able to open > dozens of "foo" devices. However, we'll add some error checking to our first > read routine to keep from selecting invalid minor numbers. Note, once we > have a working open and close routine, we'll be able to move the error > checking there, and out of the read routine completely. so why put it there now? It's a bad habit to start.. get them used to having an open().. > This is because the > kernel does a certain amount of error checking ahead of time, and won't allow > reads or writes to be performed on not-open minor numbers (more on this later). > > One note on minor numbers. MINOR numbers are used to keep track of seperate > entities within the same device driver. For instance, for serial devices > (the sio driver), the first com port will have a minor number 0, the next, > a minor number of 1, the next, a minor number of 2, and so on. This is how > one logical device will be kept descrete from the others, even though their > major numbers are the same. For our first device driver, we'll support only > one minor device (minor number 0). usually the NFOO number can be used to select how many minors will be acceptable :) you should also mention that interpretation of the minor numbers is TOTALLY up the the driver. > > /* Define our routines in the proper format for a device-driver */ > static d_read_t fooread; It's defined this wa for teh devsw entry.. this is really part of the block that declares the devsw struct and should be kept together with that. > > One note on device drivers I've failed to touch on that suddenly has come > to me. Device driver "names", in our case, "foo", can be anywhere from 1-4 > characters. nonsence.. it can be > 4.. there is no real limit.. it just fits in better if it's kept small as it gets concatinated with things all over the place. >Most systems do not allow numbers (for reasons that will > become obvious later). Once defined, all references to that device driver > will use that name. > > ======= > /* Define our routines in the proper format for a device-driver */ > static d_read_t fooread; > > /* Define the cdewsw structure for our driver */ > static struct cdevsw foo_cdevsw = > { > nullopen, nullclose, fooread, nxwrite, > nxioctl, nxstop, nxreset, nxdevtotty, > nxselect, nxmmap, NULL, "foo", NULL, -1 > }; ====== the above is one logical code block.. > > > > The next routine we'll write is the init routine, which is responsible for > "starting up" our device driver. It can be as simple as stating the driver > is loaded, or it can be very complex. In our case, since we're doing a > pseudo-device driver, and not a regular character device driver, we won't > have probe and attach routines to do the startup work, so we'll have to do > it ourselves in the init routine. Our init routine will look something like: > > static void fooinit(void *unused) > { > dev_t dev; > printf("foo0: Foo test character device driver installed and ready.\n"); > printf("foo0: Configured for 1 device\n"); > dev = makedev(CDEV_MAJOR,0); > cdevsw_add(&dev, &foo_cdevsw, NULL); DEVFS code goes here too :) > } > > This routine basically will print out two lines of notification on boot up, > and then get the device set up in the kernel. > > The last thing we need to do is tell the kernel (from inside the driver) what > routine has to be executed in order to get everything started, as well as give > it a "priority" for loading. As an example of "priority", you can look > at the Ethernet cards defined in the LINT kernel config file. You'll note > it says not to change the order, in order to keep them from > screwing up each other's probes... This is similar. Unless you have a very > good reason to change it, I recommend to use the default priority. With this > in mind, the following default line should work 99% of the time: > > SYSINIT(foodev, SI_SUB_DRIVERS, SI_ORDER_MIDDLE+CDEV_MAJOR, &fooinit, NULL); > > What does it all do? Even I don't know ;) But, it works, so use it. the linker gathers all SYSINIT entries in all linked files into an array at boot time the entries are sorted (a bubble sort in kern_main.c from memory) and the functions pointed to are run in the order specified. this is a specific use of LINKER SETS there are others in the kernel used for other reasons. e.g adding protocol table entries etc. I THINK they are in kernel.h > #include "foo.h" > #if NFOO > 0 ^^^^^^^^^^^^^^^ this is not needed becasue if NFOO were 0 the whole foo.c file wouldn't be in the Makefile it's historical cruft.. (for hysterical raisons?) > /* Include the header files that we'll need */ > Now, thats it for the driver. The next step is to go in to > /usr/src/sys/i386/conf. I modified majors.i386 so that character device > 20 was called "foo". This was not required, but if I had other developers > working on this system, I'd want them to know I used 20 for my device > driver, and its no longer available for them to use until I'm done with it, > and change it back. > > Secondly, you'll need to edit files.i386. Add the line actually if it's not i386 specific it should be in /sys/conf/files > > dev/foo/foo.c optional foo device-driver > > someplace in the file. I usually do it about 25-30 lines down, > where the similar looking lines start. Placement in the file is not critical, > I just like to keep things looking consistent. > > Almost there. Just a couple of more things. Next, create your kernel config > file (getting real close now). Add the line: > > pseudo-device foo 1 > > someplace to the file. This will let the kernel know you need the foo driver, > and it will tell the driver it wants one device (more on this later when > we support multiple devices). > From owner-freebsd-hackers Sun Feb 23 19:15:07 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id TAA21606 for hackers-outgoing; Sun, 23 Feb 1997 19:15:07 -0800 (PST) Received: from Kitten.mcs.com (Kitten.mcs.com [192.160.127.90]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id TAA21600 for ; Sun, 23 Feb 1997 19:15:04 -0800 (PST) Received: from Jupiter.Mcs.Net (karl@Jupiter.mcs.net [192.160.127.88]) by Kitten.mcs.com (8.8.5/8.8.2) with ESMTP id VAA17364; Sun, 23 Feb 1997 21:15:03 -0600 (CST) Received: (from karl@localhost) by Jupiter.Mcs.Net (8.8.5/8.8.2) id VAA02748; Sun, 23 Feb 1997 21:15:03 -0600 (CST) From: Karl Denninger Message-Id: <199702240315.VAA02748@Jupiter.Mcs.Net> Subject: Re: best way to back up? To: dec@phoenix.its.rpi.edu (David E. Cross) Date: Sun, 23 Feb 1997 21:15:02 -0600 (CST) Cc: hackers@FreeBSD.ORG In-Reply-To: <199702240228.VAA03134@phoenix.its.rpi.edu> from "David E. Cross" at Feb 23, 97 09:28:53 pm X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > I am curious as to what the "best" way is to back up to a 8mm tape on a > different machine. I have found that (for me) tar seems to be the easiest > to use, however, I can't get it to do an incremental backup, and it seems to > choke on some of the "special" files in /dev. dump/rdump let you me do > differential backups, but I can only do one per tape? > > -- > David Cross > ACS Consultant Huh? Go to the no-rewind device, and set the tape "size" to a rediculously large number so it never runs out (unless it really does get an "end of media"). We do this all the time, and our regular incremental tapes (run to a DLT) typically have 30-40 savesets on them. Before the 8505 Exabytes (7gig native) got to be too small we used to run these to 8mm; now we go to DLT 30G cartridges, but the only thing that changed was the target. -- -- Karl Denninger (karl@MCS.Net)| MCSNet - The Finest Internet Connectivity http://www.mcs.net/~karl | T1's from $600 monthly to FULL DS-3 Service | 99 Analog numbers, 77 ISDN, Web servers $75/mo Voice: [+1 312 803-MCS1 x219]| Email to "info@mcs.net" WWW: http://www.mcs.net/ Fax: [+1 312 803-4929] | 2 FULL DS-3 Internet links; 400Mbps B/W Internal From owner-freebsd-hackers Sun Feb 23 19:19:54 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id TAA21899 for hackers-outgoing; Sun, 23 Feb 1997 19:19:54 -0800 (PST) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id TAA21894 for ; Sun, 23 Feb 1997 19:19:51 -0800 (PST) Received: from current1.whistle.com (current1.whistle.com [207.76.205.22]) by alpo.whistle.com (8.8.5/8.8.4) with SMTP id TAA03818; Sun, 23 Feb 1997 19:13:32 -0800 (PST) Message-ID: <331106DC.2781E494@whistle.com> Date: Sun, 23 Feb 1997 19:11:24 -0800 From: Julian Elischer Organization: Whistle Communications X-Mailer: Mozilla 3.0Gold (X11; I; FreeBSD 2.2-CURRENT i386) MIME-Version: 1.0 To: "Brian J. McGovern" CC: patrick collins , hackers@freebsd.org Subject: Re: Driver question on interval execution (polling?) References: <199702240127.UAA04260@spoon.beta.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Brian J. McGovern wrote: > > Based on my reading of several device driver books, I am aware of a mechanism > to be able to have the kernel re-enter a particular function after a certain > time period is past. Using this system, you should be able to do your > poll, and then implement the required code so the function will be restarted > some time in the future, and then it should terminate. the calls you want are timeout(9) untimeout(9) tsleep(9) and wakeup(9) not all have man pages yet From owner-freebsd-hackers Sun Feb 23 19:28:21 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id TAA22380 for hackers-outgoing; Sun, 23 Feb 1997 19:28:21 -0800 (PST) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id TAA22374 for ; Sun, 23 Feb 1997 19:28:18 -0800 (PST) Received: from current1.whistle.com (current1.whistle.com [207.76.205.22]) by alpo.whistle.com (8.8.5/8.8.4) with SMTP id TAA03913; Sun, 23 Feb 1997 19:19:42 -0800 (PST) Message-ID: <3311084E.794BDF32@whistle.com> Date: Sun, 23 Feb 1997 19:17:34 -0800 From: Julian Elischer Organization: Whistle Communications X-Mailer: Mozilla 3.0Gold (X11; I; FreeBSD 2.2-CURRENT i386) MIME-Version: 1.0 To: Matt Thomas CC: Terry Lambert , hackers@FreeBSD.ORG Subject: Re: Alternatives to SYSV IPC? References: <3.0.32.19970222213738.006a1cb0@netrix.lkg.dec.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > if (socketpair(AF_UNIX, SOCK_STREAM, 0, fds) < 0) > perror("socketpair"); > how come no-one uses AF_LOCAL with SOCK_DGRAM? > From owner-freebsd-hackers Sun Feb 23 19:36:04 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id TAA22992 for hackers-outgoing; Sun, 23 Feb 1997 19:36:04 -0800 (PST) Received: from monk.via.net (monk.via.net [140.174.204.10]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id TAA22971 for ; Sun, 23 Feb 1997 19:36:00 -0800 (PST) Received: (from joe@localhost) by monk.via.net (8.6.11/8.6.12) id TAA16172 for hackers@freebsd.org; Sun, 23 Feb 1997 19:28:15 -0800 Date: Sun, 23 Feb 1997 19:28:15 -0800 From: Joe McGuckin Message-Id: <199702240328.TAA16172@monk.via.net> To: hackers@freebsd.org Subject: Strange networking problem X-Sun-Charset: US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I have a FreeBSD 2.1.6 web server with about 20 virtual domains (running apache). I needed to feed ethernet to a customer in the building, so I added another ethernet card to the box. I have a static route in our gateway router routing his network to the ethernet address of the freebsd box - 140.174.204.90. 140.174.204.90 ovation.via.net .91 start of virtual domains . . . After a week or so, something wierd happened. Traceroutes that had previously been reporting .90 as the address for the box started reporting some other address that was aliased to the 140.174.204.90 ethernet interface. Why do I care? Well the address it was reporting back belonged to a virtual web site we host that served up links to adult sites. Our ethernet customer was *not* amused ^). If I was forwarding traffic to .90, why would it start reporting back to traceroutes as .101 (or something else)? -joe From owner-freebsd-hackers Sun Feb 23 21:18:12 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id VAA27833 for hackers-outgoing; Sun, 23 Feb 1997 21:18:12 -0800 (PST) Received: from krumm.commline.com (krumm.commline.com [207.78.30.252]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id VAA27828 for ; Sun, 23 Feb 1997 21:18:08 -0800 (PST) Received: from localhost (brian@localhost) by krumm.commline.com (8.8.3/8.8.3) with SMTP id AAA17243; Mon, 24 Feb 1997 00:33:30 -0500 (EST) Date: Mon, 24 Feb 1997 00:33:30 -0500 (EST) From: "Brian L. Heess" Reply-To: "Brian L. Heess" To: "David E. Cross" cc: hackers@FreeBSD.ORG Subject: Re: best way to back up? In-Reply-To: <199702240228.VAA03134@phoenix.its.rpi.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Sun, 23 Feb 1997, David E. Cross wrote: > I am curious as to what the "best" way is to back up to a 8mm tape on a > different machine. I have found that (for me) tar seems to be the easiest > to use, however, I can't get it to do an incremental backup, and it seems to > choke on some of the "special" files in /dev. dump/rdump let you me do > differential backups, but I can only do one per tape? You can probably figure it out from this little script I have on a SunOS machine. You'll probably also see that I had it it doing local backups originally: #!/bin/sh # # Example dump for level 0 - modified dir # # show when we started... date # set vars DUMP=/usr/etc/dump HOST=ickis TAPE=/dev/nrst5 # # Rewind the tape # echo Rewind the tape... ###mt -f $TAPE rewind rsh -n -l root $HOST mt -f $TAPE rewind # # For each partition # #Filesystem kbytes used avail capacity Mounted on #/dev/sd0a 11455 7384 2926 72% / #/dev/sd1g 315163 218950 64697 77% /usr #/dev/sd0g 147685 126657 6260 95% /home #/dev/sd1a 596262 444840 91796 83% /usr/local #/dev/sd2g 1372510 683196 552063 55% /var #/dev/sd2a 460005 32881 381124 8% /var/local/db # BACKUP='/ /usr /home /usr/local /var /var/local/db' pos=0 # Usage: ufsdump [0123456789fustdWwnDCcbavloS [argument]] filesystem for part in $BACKUP; do echo "`date` | File#$pos : Working on $part" # $DUMP 0bdsfu 112b 15000 30000 $TAPE $part $DUMP 0bdsfu 112b 15000 30000 $HOST:$TAPE $part pos=`expr $pos + 1` done # # rewind and eject the tape # echo Rewind and eject the tape... ##mt -f $TAPE rewoffl rsh -n -l root $HOST mt -f $TAPE rewoffl date # EOF -- Brian L. Heess, brian@thru.net | Office: 201.288.1136 VP Technology | Fax: 201.288.0213 Vanguard InterActive, Inc. | Home: 201-387-2574 / 201-287-0739 My personal URLs: brian@commline.com - http://www.commline.com (DM/BONG) Co-founder: EarthLink Net, brian@earthlink.net - http://www.earthlink.net From owner-freebsd-hackers Sun Feb 23 21:35:36 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id VAA28946 for hackers-outgoing; Sun, 23 Feb 1997 21:35:36 -0800 (PST) Received: from agora.rdrop.com (root@agora.rdrop.com [199.2.210.241]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id VAA28940 for ; Sun, 23 Feb 1997 21:35:30 -0800 (PST) Received: from mexico.brainstorm.eu.org by agora.rdrop.com with smtp (Smail3.1.29.1 #17) id m0vyt4G-000904C; Sun, 23 Feb 97 21:35 PST Received: from brasil.brainstorm.eu.org (brasil.brainstorm.fr [193.56.58.33]) by mexico.brainstorm.eu.org (8.8.4/8.8.4) with ESMTP id GAA01611 for ; Mon, 24 Feb 1997 06:31:38 +0100 Received: (from uucp@localhost) by brasil.brainstorm.eu.org (8.8.4/8.6.12) with UUCP id GAA21432 for hackers@freebsd.org; Mon, 24 Feb 1997 06:31:11 +0100 Received: (from roberto@localhost) by keltia.freenix.fr (8.8.5/keltia-uucp-2.9) id BAA01412; Mon, 24 Feb 1997 01:41:09 +0100 (CET) Message-ID: <19970224014109.FD35066@keltia.freenix.fr> Date: Mon, 24 Feb 1997 01:41:09 +0100 From: roberto@keltia.freenix.fr (Ollivier Robert) To: hackers@freebsd.org Subject: Re: Install to second hard-drive... References: X-Mailer: Mutt 0.60,1-3,9 Mime-Version: 1.0 X-Operating-System: FreeBSD 3.0-CURRENT ctm#2999 In-Reply-To: ; from Mark Mayo on Feb 23, 1997 10:24:33 -0500 Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk According to Mark Mayo: > FWIW, I have NT on the first SCSI disk, and FreeBSD on the second - so > there is clean separation.. I use the NT boot manager to boot FreeBSD and > NT. Works great - just use the "standard MBR" on the FreeBSD disk (sd1), > and copy the first 512 bytes of the disk to a file called "BOOTBSD.BIN" on > the NT "C:" drive, and edit the BOOT.INI file to add an entry for the > BOOTBSD.BIN file. I figured I might as well use the NT boot manager since That's what I tried to use for a machine at work which has NT on the first drive and FreeBSD 2.1.6 on the second. I tried what the FAQ said about the NT loader and couldn't get it to boot FreeBSD on the second disk. OS-BS 2.0b8 solved the problem. -- Ollivier ROBERT -=- The daemon is FREE! -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 3.0-CURRENT #39: Sun Feb 2 22:12:44 CET 1997 From owner-freebsd-hackers Sun Feb 23 21:48:18 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id VAA29542 for hackers-outgoing; Sun, 23 Feb 1997 21:48:18 -0800 (PST) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id VAA29537 for ; Sun, 23 Feb 1997 21:48:14 -0800 (PST) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.3/8.6.9) id QAA24231; Mon, 24 Feb 1997 16:44:44 +1100 Date: Mon, 24 Feb 1997 16:44:44 +1100 From: Bruce Evans Message-Id: <199702240544.QAA24231@godzilla.zeta.org.au> To: hackers@FreeBSD.ORG, rhh@ct.picker.com Subject: Re: dd of=/dev/rwd1s2 -- How? Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > # dd if=img of=/dev/rwd1s2 > >gives me: > > dd: /dev/rwd1s2: Read-only file system > 2+0 records in > 1+0 records out > 512 bytes transferred in 0.063062 secs (8119 bytes/sec) > > >How do I write a saved slice image directly on top of a slice? Is there a >way get a writable raw slice device? Remove the BSD label from the slice. This isn't easy. IIRC, the easiest way is to corrupt the label by writing to it via /dev/rwd1. This exploits a bug in the write protection. It should be possible to use disklabel -N to disable the write protection, but this has been broken for a long time. First, the write protection bit is forgotten when all devices on the disk are closed. Second, there is effectively another layer of write protection that isn't controlled by disklabel -N (writes to the label are trapped and ones that would corrupt the label are rejected. Ones that invalidate the magic number probably should be allowed if the label isn't write protected). Bruce From owner-freebsd-hackers Sun Feb 23 21:48:24 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id VAA29562 for hackers-outgoing; Sun, 23 Feb 1997 21:48:24 -0800 (PST) Received: from lightside.com (hamby1.lightside.net [207.67.176.17]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id VAA29550 for ; Sun, 23 Feb 1997 21:48:20 -0800 (PST) Received: by lightside.com (SMI-8.6/SMI-SVR4) id VAA01306; Sun, 23 Feb 1997 21:49:08 -0800 Date: Sun, 23 Feb 1997 21:49:08 -0800 From: jehamby@lightside.com (Jake Hamby) Message-Id: <199702240549.VAA01306@lightside.com> To: hackers@freebsd.org Subject: disallow setuid root shells? Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-MD5: XyZR+bssAJ08MB3V7f3AaA== Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In light of the recent security review, here's something that I've wondered about ever since I noticed it. Often, after hacking the root account, a malicious user will hide a setuid-root shell as a back door to allow future access. Under Solaris, I've discovered that none of the standard shells will allow a user to gain root privileges through a setuid root shell! The sh and ksh shells will run, but the user will have their normal privileges. Csh (and interestingly enough tcsh) print "Permission denied" and exit when run with the setuid bit set. Curiously, when I made a setuid shell owned by nobody, the sh command worked (and gave me, as a normal user, nobody's permissions), while the csh command still printed "Permission denied." I theorize that csh tries to gain control of the user's terminal (for job control purposes), but can't do it while assuming another user's UID. Since I don't have Solaris source code, I'm not sure exactly what these shells are doing, but I imagine a simple: if(geteuid()==0) { /* If this is a setuid-root shell */ setuid(getuid()); /* then silently restore user's permissions * to prevent security backdoor */ } near the beginning of the program would suffice. I don't claim that this will do anything to thwart the knowledgable hacker, but anything to make the system more secure, especially against novice hackers who just found out about the latest bug-of-the-week, would make FreeBSD a more secure system. After all, although a setuid shell owned by a regular user might be useful (though I wouldn't recommend it), it's obvious that a setuid-root shell would be too much of a security risk to be allowable under any circumstances. Comments? While we're on the topic, I've always wondered about Perl 5's configure messages about "secure setuid scripts". What exactly makes an OS capable of hosting "secure" Perl or shell scripts, and what does this have to do with the /dev/fd directory (that Perl searches for)? -- Jake From owner-freebsd-hackers Sun Feb 23 21:50:44 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id VAA29724 for hackers-outgoing; Sun, 23 Feb 1997 21:50:44 -0800 (PST) Received: from dg-rtp.dg.com (dg-rtp.rtp.dg.com [128.222.1.2]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id VAA29715 for ; Sun, 23 Feb 1997 21:50:38 -0800 (PST) Received: by dg-rtp.dg.com (5.4R3.10/dg-rtp-v02) id AA07910; Mon, 24 Feb 1997 00:50:06 -0500 Received: from ponds by dg-rtp.dg.com.rtp.dg.com; Mon, 24 Feb 1997 00:50 EST Received: from lakes.water.net (lakes [10.0.0.3]) by ponds.water.net (8.8.3/8.7.3) with ESMTP id TAA08441; Sun, 23 Feb 1997 19:56:49 -0500 (EST) Received: (from rivers@localhost) by lakes.water.net (8.8.3/8.6.9) id UAA11182; Sun, 23 Feb 1997 20:01:57 -0500 (EST) Date: Sun, 23 Feb 1997 20:01:57 -0500 (EST) From: Thomas David Rivers Message-Id: <199702240101.UAA11182@lakes.water.net> To: ponds!lakes.water.net!phobos.illtel.denver.co.us, ponds!lambert.org!terry Subject: Re: hmm Cc: ponds!freebsd.org!audit-bin, ponds!best.net!dillon, ponds!freebsd.org!FreeBSD-hackers, ponds!gvr.win.tue.nl!guido, ponds!resnet.uoregon.edu!gurney_j, ponds!sonic.cris.net!top Content-Type: text Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > On Sat, 22 Feb 1997, Terry Lambert wrote: > > > > with p="" > > > *p != '\0' && p[strlen(p) - 1] == '[' _still_ will read a byte p[-1]. > > > > What? > > > > IF p = "" > > THEN *p = '\0' > > > > by definition of ""... > > but p[strlen(p) - 1] will be p[-1] > Optimization done by compiler may skip it, but depending on that will be > rather dangerous. > > -- > Alex > > It may not be too clear... but, and at the risk of repeating what other's may have indicated - the C language, by definition, evaluates this from left to right. And, in the situation above (a logical-and) the first 0-valued expression will cause the result of the logical-and to be 0. Furthermore, the a compiler, or optimizer, is forbidden from evaluating the rest of the expression. That is, if *p is equal to '\0' - the remainder of the logical-and will not be evaluated... if an optimizer does cause this to happen, the compiler/optimizer is in error. So, if strlen(p) was 0, it wouldn't matter; p[-1] would never be referenced. In this veign you'll also often see code like: if(p != NULL && !strcmp(p,"some value") ) the left side of logical-and guarantees that the pointer 'p' is not NULL. The right side of the logical-and can then safely dereference 'p'. Again; this isn't a coincedence, C is defined (from the early K&R days) to behave in this manner. In compiler terms it's called short-circuit evaluation of logical expressions... - Dave Rivers - From owner-freebsd-hackers Sun Feb 23 21:54:37 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id VAA29995 for hackers-outgoing; Sun, 23 Feb 1997 21:54:37 -0800 (PST) Received: from lightside.com (hamby1.lightside.net [207.67.176.17]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id VAA29990 for ; Sun, 23 Feb 1997 21:54:33 -0800 (PST) Received: by lightside.com (SMI-8.6/SMI-SVR4) id VAA01312; Sun, 23 Feb 1997 21:55:23 -0800 Date: Sun, 23 Feb 1997 21:55:23 -0800 From: jehamby@lightside.com (Jake Hamby) Message-Id: <199702240555.VAA01312@lightside.com> To: hackers@freebsd.org Subject: Recurring freeze with 2.1.5 system Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-MD5: RsP8+vwYxX6+7rl6UM4t+A== Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk There's a 486 system at my Internet provider that he's set up as a "geek box" for people to hack on. It's a fairly lame configuration (486DX/4 100MHz, 8MB RAM, IDE drives, NE2000 card). Anyway, it has a recurring problem where it will only answer pings. Logins, either remote or from the console, will hang (telnet will connect, but not prompt for username), and the system must be forcibly rebooted. We think it may be a hardware problem, perhaps bad RAM. I'm just curious if there are any known bugs in 2.1.5-RELEASE which might cause this. The systems are similar to a SYN attack, except for the frozen local login. We're going to upgrade it to 2.2-GAMMA next weekend, and hopefully the problems will go away. If not, can we safely conclude that it is a problem of buggy hardware? -- Jake From owner-freebsd-hackers Sun Feb 23 22:10:33 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id WAA00963 for hackers-outgoing; Sun, 23 Feb 1997 22:10:33 -0800 (PST) Received: from lightside.com (hamby1.lightside.net [207.67.176.17]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id WAA00957 for ; Sun, 23 Feb 1997 22:10:26 -0800 (PST) Received: by lightside.com (SMI-8.6/SMI-SVR4) id WAA01315; Sun, 23 Feb 1997 22:11:16 -0800 Date: Sun, 23 Feb 1997 22:11:16 -0800 From: jehamby@lightside.com (Jake Hamby) Message-Id: <199702240611.WAA01315@lightside.com> To: hackers@freebsd.org Subject: Help with nasty BusLogic SCSI card! Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-MD5: X6O16zVzFdldctP0Z+bM8Q== Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk This is not strictly a FreeBSD question, but involves a peculiar hardware configuration which seems to thwart any 32-bit OS. There is a Micron PCI Powerstation (90MHz Pentium) at work with a BusLogic BT-946C SCSI controller. I seem to remember that it is an older revision of the card. Anyway, we have had big problems configuring the card before. Once it is configured, we've had no problems with it, but last Friday I wanted to attempt to upgrade this Exabyte 8mm tape drive's firmware, which uses a DOS program. I was unsuccessful running the program on another PC, and I thought I might try the other system because it has a diferent SCSI controller. Anyway, I made a DOS boot disk (the system was running NT before), and the SCSI driver was searching the wrong port. Rather than fix the CONFIG.SYS, I thought to change the port of the SCSI card in the BusLogic BIOS... big mistake (which I should've known better considering the history of the PC!). Choosing Auto Config resetted the card back to settings which _should_ work but the card refuses to work now! The way in which the card doesn't work is peculiar, as well: It will boot an OS (for example NT, or the FreeBSD boot floppy), and correctly probe for devices, but once it starts to read from the hard drive (i.e. at sysinstall in FreeBSD, or the blue screen in Windows NT) it hangs. Under NT, it seems to repeatedly probe the disks, as the hard drive light will flash every few seconds, and eventually it will blue-screen crash (with the BUSLOGIC.SYS driver mentioned prominently in the crash). I remember that previously, in order to get it to work, we had to change the PCI Interrupt pin (and possibly set it to Edge trigger). But this time, I tried all eight combinations (A, B, C, D, with Level or Edge-trigger), and none of them worked. The PCI guru helping us correctly noted that there should be no reason to change the interrupt if there are no other bus-mastering cards in the system (the only other PCI card is a Matrox Ultima), but that's what needed to be done before. Also, like an idiot, I never wrote down the correct settings for all of the Buslogic parameters, and the "Auto Config" menu tends to reset just about everything. D'oh! Also, I know that this particular motherboard has a Flash BIOS, and I had upgraded it to a newer "Plug-and-Play" BIOS early last year. When I did that, I remember that I had to change the interrupt pin yet again. I will try on Monday down-grading to the older BIOS, but I still don't understand why this might be a factor. Anyway, since I know there are PCI gurus on this list, can somebody give suggestions as to why this card might not work with the default configuration? I feel like such an idiot for changing the BIOS settings knowing the troubled history of this configuration, but I was surprised that, after several hours of testing different things, we were never able to get it to work again! I will try down-grading the flash BIOS to the earlier, non-Plug-and-Play BIOS on Monday if it still doesn't work... Is this just a strange interaction between an old pre-Triton (and possibly not PCI-2.0 compliant) motherboard, and older PCI cards? One final note: The Buslogic card has only two jumpers, to set the memory location for the BIOS. With both jumpers off, the motherboard is supposed to set the location, but with the Micron motherboard, it merely prints "PCI Error" or worse (screen corruption or refuses to boot). The card claims to be PCI 2.0. -- Jake From owner-freebsd-hackers Mon Feb 24 00:15:01 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id AAA07709 for hackers-outgoing; Mon, 24 Feb 1997 00:15:01 -0800 (PST) Received: from cheops.anu.edu.au (avalon@cheops.anu.edu.au [150.203.76.24]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id AAA07697 for ; Mon, 24 Feb 1997 00:14:54 -0800 (PST) Message-Id: <199702240814.AAA07697@freefall.freebsd.org> Received: by cheops.anu.edu.au (1.37.109.16/16.2) id AA288532056; Mon, 24 Feb 1997 19:14:16 +1100 From: Darren Reed Subject: Re: Alternatives to SYSV IPC? To: julian@whistle.com (Julian Elischer) Date: Mon, 24 Feb 1997 19:14:16 +1100 (EDT) Cc: matt@lkg.dec.com, terry@lambert.org, hackers@freebsd.org In-Reply-To: <3311084E.794BDF32@whistle.com> from "Julian Elischer" at Feb 23, 97 07:17:34 pm X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In some mail from Julian Elischer, sie said: > > > if (socketpair(AF_UNIX, SOCK_STREAM, 0, fds) < 0) > > perror("socketpair"); > > > > how come no-one uses AF_LOCAL with SOCK_DGRAM? how portable is AF_LOCAL ? Darren From owner-freebsd-hackers Mon Feb 24 00:23:36 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id AAA08033 for hackers-outgoing; Mon, 24 Feb 1997 00:23:36 -0800 (PST) Received: from parkplace.cet.co.jp (parkplace.cet.co.jp [202.32.64.1]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id AAA08026 for ; Mon, 24 Feb 1997 00:23:31 -0800 (PST) Received: from localhost (michaelh@localhost) by parkplace.cet.co.jp (8.8.5/CET-v2.1) with SMTP id IAA03218; Mon, 24 Feb 1997 08:23:22 GMT Date: Mon, 24 Feb 1997 17:23:22 +0900 (JST) From: Michael Hancock To: Jake Hamby cc: hackers@freebsd.org Subject: Re: Help with nasty BusLogic SCSI card! In-Reply-To: <199702240611.WAA01315@lightside.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Sun, 23 Feb 1997, Jake Hamby wrote: > This is not strictly a FreeBSD question, but involves a peculiar hardware > configuration which seems to thwart any 32-bit OS. There is a Micron PCI > Powerstation (90MHz Pentium) at work with a BusLogic BT-946C SCSI > controller. I seem to remember that it is an older revision of the card. Try Paul Vixie's hardware page, http://www.vix.com/pc-hw/. There's a section on the 946C. Regards, Mike Hancock From owner-freebsd-hackers Mon Feb 24 00:58:15 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id AAA09431 for hackers-outgoing; Mon, 24 Feb 1997 00:58:15 -0800 (PST) Received: from agora.rdrop.com (root@agora.rdrop.com [199.2.210.241]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id AAA09426 for ; Mon, 24 Feb 1997 00:58:10 -0800 (PST) Received: from amadeus.informatik.ba-stuttgart.de by agora.rdrop.com with smtp (Smail3.1.29.1 #17) id m0vywEU-0008sOC; Mon, 24 Feb 97 00:58 PST Received: (from helbig@localhost) by amadeus.informatik.ba-stuttgart.de (8.7.3/8.7.1) id JAA16320; Mon, 24 Feb 1997 09:44:39 +0100 (MET) From: Wolfgang Helbig Message-Id: <199702240844.JAA16320@amadeus.informatik.ba-stuttgart.de> Subject: Re: Recurring freeze with 2.1.5 system To: jehamby@lightside.com (Jake Hamby) Date: Mon, 24 Feb 1997 9:44:39 MET Cc: hackers@freebsd.org In-Reply-To: <199702240555.VAA01312@lightside.com>; from "Jake Hamby" at Feb 23, 97 9:55 pm X-Mailer: Elm [revision: 112.2] Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi, > There's a 486 system at my Internet provider that he's set up as a "geek > box" for people to hack on. It's a fairly lame configuration (486DX/4 > 100MHz, 8MB RAM, IDE drives, NE2000 card). Anyway, it has a recurring > problem where it will only answer pings. Logins, either remote or from the > console, will hang (telnet will connect, but not prompt for username), and > the system must be forcibly rebooted. > This might be your IDE-controller. If you are using the CMD640b-chip and have attached devices on primary and secondary channel the system will freeze. Checkout the hackers mailing list archive. > We're going to upgrade it to 2.2-GAMMA next weekend, and hopefully the > problems will go away. The CMD640b-problem will not go away. But there are work arounds in the said mailing list archives. Wolfgang Helbig From owner-freebsd-hackers Mon Feb 24 01:56:10 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id BAA11436 for hackers-outgoing; Mon, 24 Feb 1997 01:56:10 -0800 (PST) Received: from korin.warman.org.pl (korin.warman.org.pl [148.81.160.10]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id BAA11424 for ; Mon, 24 Feb 1997 01:56:01 -0800 (PST) Received: from localhost (abial@localhost) by korin.warman.org.pl (8.8.3/8.7.3) with SMTP id KAA00285 for ; Mon, 24 Feb 1997 10:55:55 +0100 (MET) Date: Mon, 24 Feb 1997 10:55:54 +0100 (MET) From: Andrzej Bialecki To: freebsd-hackers@FreeBSD.ORG Subject: "stealing" pty/vty Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Hi all! Sometimes I run into following problem: I start a process on a console (or vty) and then go home only to remember that I have to "press any key" for the damn process to continue... But how to do it, even if I log in and su to root? Is there a way to tap into the vty used by process and interact with it? Andy +-------------------------------------------------------------------------+ Andrzej Bialecki _) _) _)_) _)_)_) _) _) --------------------------------------- _)_) _) _) _) _)_) _)_) Research and Academic Network in Poland _) _)_) _)_)_)_) _) _) _) Bartycka 18, 00-716 Warsaw, Poland _) _) _) _) _)_)_) _) _) +-------------------------------------------------------------------------+ From owner-freebsd-hackers Mon Feb 24 01:56:59 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id BAA11469 for hackers-outgoing; Mon, 24 Feb 1997 01:56:59 -0800 (PST) Received: from dawn.ww.net (root@ww.net [193.124.73.50]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id BAA11464 for ; Mon, 24 Feb 1997 01:56:43 -0800 (PST) Received: (from alexis@localhost) by dawn.ww.net (8.7.5/alexis 2.5) id MAA12893 for freebsd-hackers@freebsd.org; Mon, 24 Feb 1997 12:56:28 +0300 (MSK) Message-Id: <199702240956.MAA12893@dawn.ww.net> Subject: "black" interfaces list To: freebsd-hackers@freebsd.org Date: Mon, 24 Feb 1997 12:56:27 +0300 (MSK) From: Alexis Yushin Reply-To: alexis@ww.net (Alexis Yushin) X-Office-Phone: +380 65 2 26.1410 X-Home-Phone: +380 65 2 27.0747 X-NIC-Handle: AY23 X-RIPE-Handle: AY6-RIPE X-Mailer: ELM [version 2.4ME+ PL17 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Greetings, Imagine we have FreeBSD based ip router. There is a number of interfaces with different addresses, from different networks with different routing policy. (The boldest example is p2p interface with reserved addresses assigned for its ends) Now, the default behaviour is to originate packets with ip_src equal to the address of the interface the packets leave the system via. In case of reserved address such packets wont get anywhere, whilst packets originated from other systems (being routed) will find their destination just fine. The idea is very simple and I could be out of date on this issue, so please let me know if I am. So, we would have "black" list of interfaces for which packets should have another source ip address. Probably it could be built into the ifconfig mechanism. Comments? alexis -- I may be drunk but at least I'm not insane. From owner-freebsd-hackers Mon Feb 24 02:10:37 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id CAA11934 for hackers-outgoing; Mon, 24 Feb 1997 02:10:37 -0800 (PST) Received: from obiwan.aceonline.com.au (obiwan.aceonline.com.au [203.103.90.67]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id CAA11816; Mon, 24 Feb 1997 02:05:17 -0800 (PST) Received: from localhost (adrian@localhost) by obiwan.aceonline.com.au (8.8.5/8.8.5) with SMTP id EAA27672; Mon, 8 Jan 1996 04:35:17 +0800 (WST) Date: Mon, 8 Jan 1996 04:35:15 +0800 (WST) From: Adrian Chadd To: Jake Hamby cc: hackers@freebsd.org, auditors@freebsd.org Subject: Re: disallow setuid root shells? In-Reply-To: <199702240549.VAA01306@lightside.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Sun, 23 Feb 1997, Jake Hamby wrote: > In light of the recent security review, here's something that I've wondered > about ever since I noticed it. Often, after hacking the root account, a > malicious user will hide a setuid-root shell as a back door to allow future > access. Under Solaris, I've discovered that none of the standard shells > will allow a user to gain root privileges through a setuid root shell! > > The sh and ksh shells will run, but the user will have their normal > privileges. Csh (and interestingly enough tcsh) print "Permission denied" > and exit when run with the setuid bit set. > Since i'm reviewing /bin/sh and /bin/csh, it might make an interesting addition. Anyone see any use for +s'ed shells ? Anything it can do, sudo can do (and sudo AFAIK is much smaller, so less code to screw around with), and I think its a good idea. Suggestions ? > While we're on the topic, I've always wondered about Perl 5's configure > messages about "secure setuid scripts". What exactly makes an OS capable of > hosting "secure" Perl or shell scripts, and what does this have to do with > the /dev/fd directory (that Perl searches for)? > Well, Linux and FreeBSD (from what I've seen) disable set-uid shell scripts by default - too easy to break though playing with the environment, and stuff like that. From what I remember, perl has a c-wrapper that it runs before running a setuid shell script that fixes up the environment and other nice things, then runs the script. By default, if you use the setuid copy of perl as a script interpreter (#!/usr/bin/sperl) and it detects that the script IS setuid root, it will run it. If not, it won't run the script as root. I simply disable it on my systems. > -- Jake > Adrian Chadd From owner-freebsd-hackers Mon Feb 24 02:41:08 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id CAA12987 for hackers-outgoing; Mon, 24 Feb 1997 02:41:08 -0800 (PST) Received: from cheops.anu.edu.au (avalon@cheops.anu.edu.au [150.203.76.24]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id CAA12978 for ; Mon, 24 Feb 1997 02:41:04 -0800 (PST) Message-Id: <199702241041.CAA12978@freefall.freebsd.org> Received: by cheops.anu.edu.au (1.37.109.16/16.2) id AA020160797; Mon, 24 Feb 1997 21:39:57 +1100 From: Darren Reed Subject: Re: "black" interfaces list To: alexis@ww.net Date: Mon, 24 Feb 1997 21:39:56 +1100 (EDT) Cc: freebsd-hackers@freebsd.org In-Reply-To: <199702240956.MAA12893@dawn.ww.net> from "Alexis Yushin" at Feb 24, 97 12:56:27 pm X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In some mail from Alexis Yushin, sie said: > > Greetings, > > Imagine we have FreeBSD based ip router. There is a number > of interfaces with different addresses, from different networks with > different routing policy. (The boldest example is p2p interface with > reserved addresses assigned for its ends) > > Now, the default behaviour is to originate packets with > ip_src equal to the address of the interface the packets leave the > system via. In case of reserved address such packets wont get > anywhere, whilst packets originated from other systems (being routed) > will find their destination just fine. > > The idea is very simple and I could be out of date on this > issue, so please let me know if I am. So, we would have "black" list > of interfaces for which packets should have another source ip address. > Probably it could be built into the ifconfig mechanism. Comments? Hmmm, you might be able to do this using the NAT features in IP Filter. a picture might help (or an example of some packets) Darren From owner-freebsd-hackers Mon Feb 24 02:42:48 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id CAA13056 for hackers-outgoing; Mon, 24 Feb 1997 02:42:48 -0800 (PST) Received: from panda.hilink.com.au (panda.hilink.com.au [203.2.144.5]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id CAA13050 for ; Mon, 24 Feb 1997 02:42:43 -0800 (PST) Received: (from danny@localhost) by panda.hilink.com.au (8.8.5/8.7.3) id VAA02383; Mon, 24 Feb 1997 21:47:02 +1100 (EST) Date: Mon, 24 Feb 1997 21:47:00 +1100 (EST) From: "Daniel O'Callaghan" To: Alexis Yushin cc: freebsd-hackers@freebsd.org Subject: Re: "black" interfaces list In-Reply-To: <199702240956.MAA12893@dawn.ww.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Mon, 24 Feb 1997, Alexis Yushin wrote: > Greetings, > > Imagine we have FreeBSD based ip router. There is a number > of interfaces with different addresses, from different networks with > different routing policy. (The boldest example is p2p interface with > reserved addresses assigned for its ends) Why are you using reserved IP addresses for the ends? PPP interfaces can use an ethernet interface IP address quite happily, unless you are talking to a box which does not support this, but even NT does (although NT can't use the same IP *subnet* on ethernet and PPP.) Alternatively, use very small subnets (255.255.255.252 netmask) and use real IP addresses. As a last resort you can re-ifconfig a PPP interface with a 'real' IP address after it has been brought up. Danny From owner-freebsd-hackers Mon Feb 24 04:01:42 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id EAA15053 for hackers-outgoing; Mon, 24 Feb 1997 04:01:42 -0800 (PST) Received: from whqvax.picker.com (whqvax.picker.com [144.54.1.1]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id EAA15046 for ; Mon, 24 Feb 1997 04:01:39 -0800 (PST) Received: from ct.picker.com by whqvax.picker.com with SMTP; Mon, 24 Feb 1997 7:00:36 -0500 (EST) Received: from elmer.ct.picker.com ([144.54.57.34]) by ct.picker.com (4.1/SMI-4.1) id AA13139; Mon, 24 Feb 97 07:00:34 EST Received: by elmer.ct.picker.com (SMI-8.6/SMI-SVR4) id GAA01062; Mon, 24 Feb 1997 06:58:19 -0500 Message-Id: <19970224065818.58089@ct.picker.com> Date: Mon, 24 Feb 1997 06:58:18 -0500 From: Randall Hopper To: Bruce Evans Cc: hackers@FreeBSD.ORG Subject: Re: dd of=/dev/rwd1s2 -- How? References: <199702240544.QAA24231@godzilla.zeta.org.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.61 In-Reply-To: <199702240544.QAA24231@godzilla.zeta.org.au>; from Bruce Evans on Feb 02, 1997 at 04:44:44PM Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Bruce Evans: |Randall Hopper: |> # dd if=img of=/dev/rwd1s2 |>gives me: |> dd: /dev/rwd1s2: Read-only file system |> |>How do I write a saved slice image directly on top of a slice? Is there a |>way get a writable raw slice device? | |Remove the BSD label from the slice. This isn't easy. IIRC, the easiest |way is to corrupt the label by writing to it via /dev/rwd1. This exploits |a bug in the write protection. | |It should be possible to use disklabel -N to disable the write protection, |but this has been broken for a long time. First, the write protection bit |is forgotten when all devices on the disk are closed. Second, there is |effectively another layer of write protection that isn't controlled by |disklabel -N (writes to the label are trapped and ones that would corrupt |the label are rejected. Ones that invalidate the magic number probably |should be allowed if the label isn't write protected). I would have thought this would have been easier. I lost my root partition with 2.2-ALPHA Saturday due to it overwriting the boot record and the FreeBSD boot blocks on my root partition (wd1s3), so some piece of code got permission to do this, and given that my other partitions are fine, I wouldn't guess it was via /dev/rwd1. Trying to make it easy to recover from this bug in the future if it bites me again, I've dd'ed an image of my 2.2-GAMMA root slice made in single-user mode so I can dd it right back from the fixit disk. Would sure be nice if it were that easy. Will changing the slice type to something other than A5 with fdisk give me write access on rwd1s3 again? It would make sense -- FreeBSD magic shouldn't be checked for in a non-FreeBSD slice. Speaking of my 2.2-ALPHA corruption, I don't know if this bug has been fixed or not in 2.2-GAMMA, but is there a person I should mail a MIMEd copy of the 1st 16k or so of my corrupted image to. It looks like the corruption is limited to that section, and the content might gives some clues as to the bug at work. (I saved off the whole partition in hopes of being able to re-disklabel it, without success I'm afraid). Thanks for the info Bruce, Randall From owner-freebsd-hackers Mon Feb 24 04:50:34 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id EAA17844 for hackers-outgoing; Mon, 24 Feb 1997 04:50:34 -0800 (PST) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id EAA17839 for ; Mon, 24 Feb 1997 04:50:30 -0800 (PST) Received: (from msmith@localhost) by genesis.atrad.adelaide.edu.au (8.8.5/8.7.3) id XAA07310 for hackers@freebsd.org; Mon, 24 Feb 1997 23:20:13 +1030 (CST) From: Michael Smith Message-Id: <199702241250.XAA07310@genesis.atrad.adelaide.edu.au> Subject: Large File standards? To: hackers@freebsd.org Date: Mon, 24 Feb 1997 23:20:12 +1030 (CST) X-Mailer: ELM [version 2.4ME+ PL28 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk While people are beating on the filesystem and the like, this may be worth looking at : http://www.sas.com/standards/large.file/ It appears to be a 'standard' for support for files > 2^32 bytes in size. -- ]] Mike Smith, Software Engineer msmith@gsoft.com.au [[ ]] Genesis Software genesis@gsoft.com.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control. (ph) +61-8-8267-3493 [[ ]] Unix hardware collector. "Where are your PEZ?" The Tick [[ From owner-freebsd-hackers Mon Feb 24 05:25:40 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id FAA18782 for hackers-outgoing; Mon, 24 Feb 1997 05:25:40 -0800 (PST) Received: from burlco-00.burlco.lib.nj.us (burlco-00.burlco.lib.nj.us [204.91.160.98]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id FAA18772 for ; Mon, 24 Feb 1997 05:25:38 -0800 (PST) Received: from localhost (rcummins@localhost) by burlco-00.burlco.lib.nj.us (8.7.5/8.6.12) with SMTP id IAA12789; Mon, 24 Feb 1997 08:25:08 -0500 (EST) Date: Mon, 24 Feb 1997 08:25:08 -0500 (EST) From: Ray Cummins To: Andrzej Bialecki cc: freebsd-hackers@FreeBSD.ORG Subject: Re: "stealing" pty/vty In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Mon, 24 Feb 1997, Andrzej Bialecki wrote: > Hi all! > > Sometimes I run into following problem: I start a process on a console (or > vty) and then go home only to remember that I have to "press any key" for > the damn process to continue... But how to do it, even if I log in and su > to root? > > Is there a way to tap into the vty used by process and interact with it? > man "watch" From owner-freebsd-hackers Mon Feb 24 05:32:18 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id FAA19071 for hackers-outgoing; Mon, 24 Feb 1997 05:32:18 -0800 (PST) Received: from whqvax.picker.com (whqvax.picker.com [144.54.1.1]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id FAA19052; Mon, 24 Feb 1997 05:32:14 -0800 (PST) Received: from ct.picker.com by whqvax.picker.com with SMTP; Mon, 24 Feb 1997 8:31:41 -0500 (EST) Received: from elmer.ct.picker.com ([144.54.57.34]) by ct.picker.com (4.1/SMI-4.1) id AA15223; Mon, 24 Feb 97 08:31:38 EST Received: by elmer.ct.picker.com (SMI-8.6/SMI-SVR4) id IAA01465; Mon, 24 Feb 1997 08:29:23 -0500 Message-Id: <19970224082923.62035@ct.picker.com> Date: Mon, 24 Feb 1997 08:29:23 -0500 From: Randall Hopper To: Brian Somers Cc: Joerg Wunsch , hackers@FreeBSD.ORG, questions@FreeBSD.ORG Subject: Re: Install to second hard-drive... References: <199702231204.MAA14310@awfulhak.demon.co.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.61 In-Reply-To: <199702231204.MAA14310@awfulhak.demon.co.uk>; from Brian Somers on Feb 02, 1997 at 12:04:52PM Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Brian Somers: |> As Joerg Wunsch wrote: |> I don't know whether booteasy can handle more than one drive. I |> remember somebody saying that os-bs is better in this respect. |> Booteasy handled multiple disks OK on my box. However, it daisy-chains the slices for the second disk as another menu off the initial menu for the first disk. This, plus other things I didn't like about the booteasy menus led me to go with OS/BS 2.0B8. Much nicer interface: 1 menu, color, digit or arrow key selection, timeout freeze, supports multiple disks, it'll even let me boot off my SCSI ZIP drive when I've got my SDMS BIOS enabled. Boots my DOS/95 partitions off Disk 0 and FreeBSD (and a while back Linux) off Drive 1. |heads, and the BIOS only allows up to 15. As osbs20b8 installs through |DOS, and writes to more than the first sector, this causes problems.... Right. DOS always starts its partition at Track 0 Head 1, leaving Track 0 Head 0 empty. OS/BS needs more than just sector 1 (MBR) at the front of the disk. It additionally uses sectors 2-5 on Track 0 Head 0, presuming based on DOS's layout that this space will be available. disk. That is, leave the space from Cylinder 0, Head 0, Sector 2 through Cylinder 0, Head 0, Sector 63 unallocated, and start your first partition at Cylinder 0, Head 1, Sector 1. For what it's worth, Easiest way to avoid trouble here is to skip Track 0 Head 0 when creating FreeBSD partitions, and start them on Track 0 Head 1. If you already have a DOS partition on your disk up-front, you don't need to deal with this. Randall Hopper From owner-freebsd-hackers Mon Feb 24 05:37:12 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id FAA19388 for hackers-outgoing; Mon, 24 Feb 1997 05:37:12 -0800 (PST) Received: from profane.iq.org (profane.iq.org [203.4.184.217]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id FAA19358; Mon, 24 Feb 1997 05:36:36 -0800 (PST) Received: (from proff@localhost) by profane.iq.org (8.8.4/8.8.2) id AAA10815; Tue, 25 Feb 1997 00:28:34 +1100 (EST) From: Julian Assange Message-Id: <199702241328.AAA10815@profane.iq.org> Subject: Re: o [1997/02/01] bin/2634 rtld patches for easy creation of chroot enviroments In-Reply-To: <2530.856709842@critter.dk.tfs.com> from Poul-Henning Kamp at "Feb 23, 97 03:57:22 pm" To: phk@critter.dk.tfs.com (Poul-Henning Kamp) Date: Tue, 25 Feb 1997 00:28:33 +1100 (EST) Cc: hackers@freebsd.org, security@freebsd.org X-Mailer: ELM [version 2.4ME+ PL28 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > >It is restricted to non-suid, just the same as LD_PRELOAD is. There > >is an "unsafe" field in the scan_tab for all enviromental variables > >used by ld.so. It's set to on for LD_CHROOT. You may want to have > >a look at this before presuming I'm a complete fool ;) > > Listen, this patch is maybe or maybe not correct, but it certainly > is pointless. > > For anything as little used as chroot to clobber the one of the most > timecritical piece of code in userland is simply not an option, in > particular where there isn't any better argumentation that "it would > be neat of one could..." > > -- > Poul-Henning Kamp | phk@FreeBSD.ORG FreeBSD Core-team. Have you actually ever looked at rtld.c? Alone it over 53k long. It is full of debug code that is normally never used. A p-100 class machine does around 173,000 getenv("LD_CHROOT")'s a second. What plannet are you on? The primary reason chroot() is rarely used is because it is painful to use. LD_CHROOT makes it very, very easy to use. That said, I have absolutely no doubt chroot() is used more than LD_LIBRARY_PATH, LD_PRELOAD, LD_IGNORE_MISSING_OBJECTS, LD_TRACE_LOADED_OBJECTS, LD_BIND_NOW, LD_SUPPRESS_WARNINGS and LD_WARN_NON_PURE_CODE put together. It would be neat if one could actually use the chroot() facility in a secure and efficient manner, without modifying the source for main() on every binary in the system. You are right. It would be neat. Since when is something being small, fast, secure, neat and providing functionality that wouldn't otherwise be there grounds for rejection of code? I'm quite apalled at this conservative view, expressed without the slightest understanding of the code involved. -- Prof. Julian Assange |If you want to build a ship, don't drum up people |together to collect wood and don't assign them tasks proff@iq.org |and work, but rather teach them to long for the endless proff@gnu.ai.mit.edu |immensity of the sea. -- Antoine de Saint Exupery From owner-freebsd-hackers Mon Feb 24 05:44:15 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id FAA19692 for hackers-outgoing; Mon, 24 Feb 1997 05:44:15 -0800 (PST) Received: from cheops.anu.edu.au (avalon@cheops.anu.edu.au [150.203.76.24]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id FAA19680 for ; Mon, 24 Feb 1997 05:44:12 -0800 (PST) Message-Id: <199702241344.FAA19680@freefall.freebsd.org> Received: by cheops.anu.edu.au (1.37.109.16/16.2) id AA054761839; Tue, 25 Feb 1997 00:43:59 +1100 From: Darren Reed Subject: installing without booting off floppy. To: hackers@freebsd.org Date: Tue, 25 Feb 1997 00:43:59 +1100 (EDT) X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk if I have freebsd running and want to install onto another HD, what can I run ? (can't boot from a floppy) From owner-freebsd-hackers Mon Feb 24 06:50:16 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id GAA22281 for hackers-outgoing; Mon, 24 Feb 1997 06:50:16 -0800 (PST) Received: from rover.village.org (rover.village.org [204.144.255.49]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id GAA22174; Mon, 24 Feb 1997 06:45:56 -0800 (PST) Received: from rover.village.org [127.0.0.1] by rover.village.org with esmtp (Exim 0.56 #1) id E0vz1df-0004dM-00; Mon, 24 Feb 1997 07:44:23 -0700 To: Adrian Chadd Subject: Re: disallow setuid root shells? Cc: Jake Hamby , hackers@freebsd.org, auditors@freebsd.org In-reply-to: Your message of "Mon, 08 Jan 1996 04:35:15 +0800." References: Date: Mon, 24 Feb 1997 07:44:23 -0700 From: Warner Losh Message-Id: Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In message Adrian Chadd writes: : Since i'm reviewing /bin/sh and /bin/csh, it might make an interesting : addition. Anyone see any use for +s'ed shells ? Anything it can do, sudo : can do (and sudo AFAIK is much smaller, so less code to screw around : with), and I think its a good idea. : : Suggestions ? That might not be a bad idea. However, it is fairly easy to work around if I can make a /bin/sh setuid, I can make anything I anything I want setuid and then do a setuid(0); exec /bin/sh (or /bin/csh). It would help firewall somethings, but it wouldn't solve the problem. sudo isn't a shell. It doesn't run scripts or read commands from anything but the command line. Warner From owner-freebsd-hackers Mon Feb 24 07:00:45 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id HAA22692 for hackers-outgoing; Mon, 24 Feb 1997 07:00:45 -0800 (PST) Received: from dawn.ww.net (root@dawn.ww.net [193.124.73.50]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id HAA22684 for ; Mon, 24 Feb 1997 07:00:35 -0800 (PST) Received: (from alexis@localhost) by dawn.ww.net (8.7.5/alexis 2.5) id RAA13457; Mon, 24 Feb 1997 17:58:02 +0300 (MSK) Message-Id: <199702241458.RAA13457@dawn.ww.net> Subject: Re: "black" interfaces list To: danny@panda.hilink.com.au (Daniel O'Callaghan) Date: Mon, 24 Feb 1997 17:58:02 +0300 (MSK) From: Alexis Yushin Cc: alexis@ww.net, freebsd-hackers@freebsd.org In-Reply-To: from Daniel O'Callaghan at "Feb 24, 97 09:47:00 pm" Reply-To: alexis@ww.net (Alexis Yushin) X-Office-Phone: +380 65 2 26.1410 X-Home-Phone: +380 65 2 27.0747 X-NIC-Handle: AY23 X-RIPE-Handle: AY6-RIPE X-Mailer: ELM [version 2.4ME+ PL17 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Once Daniel O'Callaghan wrote: >Why are you using reserved IP addresses for the ends? PPP interfaces can >use an ethernet interface IP address quite happily, unless you are >talking to a box which does not support this, but even NT does (although >NT can't use the same IP *subnet* on ethernet and PPP.) > >Alternatively, use very small subnets (255.255.255.252 netmask) and use >real IP addresses. > >As a last resort you can re-ifconfig a PPP interface with a 'real' IP >address after it has been brought up. I am sorry Danny, but this is not the point of concern. There are pretty much reasons to do what I've described in certain cases. But those cases are out of scope of this thread I guess. alexis -- I may be drunk but at least I'm not insane. From owner-freebsd-hackers Mon Feb 24 07:17:18 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id HAA23436 for hackers-outgoing; Mon, 24 Feb 1997 07:17:18 -0800 (PST) Received: from phobos.illtel.denver.co.us (abelits@phobos.illtel.denver.co.us [207.33.75.1]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id HAA23430 for ; Mon, 24 Feb 1997 07:17:15 -0800 (PST) Received: from localhost (abelits@localhost) by phobos.illtel.denver.co.us (8.8.5/8.6.9) with SMTP id HAA09402; Mon, 24 Feb 1997 07:24:01 -0800 Date: Mon, 24 Feb 1997 07:24:00 -0800 (PST) From: Alex Belits To: Darren Reed cc: hackers@freebsd.org Subject: Re: installing without booting off floppy. In-Reply-To: <199702241344.FAA19680@freefall.freebsd.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Tue, 25 Feb 1997, Darren Reed wrote: > if I have freebsd running and want to install onto another HD, what can > I run ? (can't boot from a floppy) Install second hard drive and boot from first one. Then format second drive and install FreeBSD on it. Of course, if you remove first hard drive and make former second one first, device numbers/names will change for its slices, so be careful when configuring system. -- Alex From owner-freebsd-hackers Mon Feb 24 07:27:38 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id HAA23865 for hackers-outgoing; Mon, 24 Feb 1997 07:27:38 -0800 (PST) Received: from rif2.kconline.com (rif2.kconline.com [207.51.167.115]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id HAA23853 for ; Mon, 24 Feb 1997 07:27:31 -0800 (PST) Received: from localhost (jriffle@localhost) by rif2.kconline.com (8.8.4/8.8.4) with SMTP id KAA06788; Mon, 24 Feb 1997 10:09:34 -0500 (EST) Date: Mon, 24 Feb 1997 10:09:34 -0500 (EST) From: Jim Riffle X-Sender: jriffle@rif2.kconline.com To: Jake Hamby cc: hackers@freebsd.org Subject: Re: Recurring freeze with 2.1.5 system In-Reply-To: <199702240555.VAA01312@lightside.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Sun, 23 Feb 1997, Jake Hamby wrote: > There's a 486 system at my Internet provider that he's set up as a "geek > box" for people to hack on. It's a fairly lame configuration (486DX/4 > 100MHz, 8MB RAM, IDE drives, NE2000 card). Anyway, it has a recurring > problem where it will only answer pings. Logins, either remote or from the > console, will hang (telnet will connect, but not prompt for username), and > the system must be forcibly rebooted. > > We think it may be a hardware problem, perhaps bad RAM. I'm just curious if > there are any known bugs in 2.1.5-RELEASE which might cause this. The > systems are similar to a SYN attack, except for the frozen local login. > We're going to upgrade it to 2.2-GAMMA next weekend, and hopefully the > problems will go away. If not, can we safely conclude that it is a problem > of buggy hardware? I ran into a very similar problem to this some time ago. I am not sure if this is your problem, but it would definatly be worth tring before swapping out your hardware. Add these 2 lines into you kernel config file (you can change the 256 to anything you like) options "CHILD_MAX=256" options "OPEN_MAX=256" I belive the default is 64. My symptoms were similar to where the machine would respond to pings, but would not start anything new. no logins, no web. Name server would continue to function. Basically anything running would still run as long as it didn't have to open any files. Jim From owner-freebsd-hackers Mon Feb 24 07:30:46 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id HAA24100 for hackers-outgoing; Mon, 24 Feb 1997 07:30:46 -0800 (PST) Received: from phobos.illtel.denver.co.us (abelits@phobos.illtel.denver.co.us [207.33.75.1]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id HAA23827; Mon, 24 Feb 1997 07:26:03 -0800 (PST) Received: from localhost (abelits@localhost) by phobos.illtel.denver.co.us (8.8.5/8.6.9) with SMTP id HAA09485; Mon, 24 Feb 1997 07:31:39 -0800 Date: Mon, 24 Feb 1997 07:31:38 -0800 (PST) From: Alex Belits To: Warner Losh cc: Adrian Chadd , Jake Hamby , hackers@freebsd.org, auditors@freebsd.org Subject: Re: disallow setuid root shells? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Mon, 24 Feb 1997, Warner Losh wrote: > In message Adrian Chadd writes: > : Since i'm reviewing /bin/sh and /bin/csh, it might make an interesting > : addition. Anyone see any use for +s'ed shells ? Anything it can do, sudo > : can do (and sudo AFAIK is much smaller, so less code to screw around > : with), and I think its a good idea. > : > : Suggestions ? > > That might not be a bad idea. However, it is fairly easy to work > around if I can make a /bin/sh setuid, I can make anything I anything > I want setuid and then do a setuid(0); exec /bin/sh (or /bin/csh). It > would help firewall somethings, but it wouldn't solve the problem. > > sudo isn't a shell. It doesn't run scripts or read commands from > anything but the command line. IMHO adding "anti-setuid" code into shell will help, but that help won't worth the effort of typing "setuid(getuid());" and recompiling the shell -- it only makes one more step required to get the same result unless the system is stripped down until becoming completely useless (but stripped down until becoming completely useless system isn't vulnerable to most of known security bugs anyway). -- Alex From owner-freebsd-hackers Mon Feb 24 07:38:00 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id HAA24435 for hackers-outgoing; Mon, 24 Feb 1997 07:38:00 -0800 (PST) Received: from cheops.anu.edu.au (avalon@cheops.anu.edu.au [150.203.76.24]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id HAA24423 for ; Mon, 24 Feb 1997 07:37:57 -0800 (PST) Message-Id: <199702241537.HAA24423@freefall.freebsd.org> Received: by cheops.anu.edu.au (1.37.109.16/16.2) id AA087008643; Tue, 25 Feb 1997 02:37:23 +1100 From: Darren Reed Subject: Re: installing without booting off floppy. To: abelits@phobos.illtel.denver.co.us (Alex Belits) Date: Tue, 25 Feb 1997 02:37:22 +1100 (EDT) Cc: avalon@coombs.anu.edu.au, hackers@freebsd.org In-Reply-To: from "Alex Belits" at Feb 24, 97 07:24:00 am X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In some mail from Alex Belits, sie said: > > On Tue, 25 Feb 1997, Darren Reed wrote: > > > if I have freebsd running and want to install onto another HD, what can > > I run ? (can't boot from a floppy) > > Install second hard drive and boot from first one. Then format second > drive and install FreeBSD on it. Of course, if you remove first hard drive > and make former second one first, device numbers/names will change for > its slices, so be careful when configuring system. The trick to all of this is being able to run "sysinstall". Once you've installed a system, this gets deleted...is it worth keeping this around, maybe as a way to install further packages ? Darren From owner-freebsd-hackers Mon Feb 24 08:02:47 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id IAA25600 for hackers-outgoing; Mon, 24 Feb 1997 08:02:47 -0800 (PST) Received: from bofh.cybercity.dk (bofh.cybercity.dk [195.8.128.254]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id IAA25592; Mon, 24 Feb 1997 08:02:42 -0800 (PST) Received: from critter.dk.tfs.com ([140.145.230.252]) by bofh.cybercity.dk (8.8.3/8.7.3) with ESMTP id RAA26167; Mon, 24 Feb 1997 17:04:49 +0100 (MET) Received: from critter.dk.tfs.com (localhost [127.0.0.1]) by critter.dk.tfs.com (8.8.2/8.8.2) with ESMTP id RAA04365; Mon, 24 Feb 1997 17:05:00 +0100 (MET) To: Julian Assange cc: hackers@freebsd.org, security@freebsd.org Subject: Re: o [1997/02/01] bin/2634 rtld patches for easy creation of chroot enviroments In-reply-to: Your message of "Tue, 25 Feb 1997 00:28:33 +1100." <199702241328.AAA10815@profane.iq.org> Date: Mon, 24 Feb 1997 17:05:00 +0100 Message-ID: <4363.856800300@critter.dk.tfs.com> From: Poul-Henning Kamp Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In message <199702241328.AAA10815@profane.iq.org>, Julian Assange writes: >plannet are you on? Earth, 3rd from the center. (Mostly harmless). >The primary reason chroot() is rarely used is because it is painful >to use. No, it's because it doesn't really offer isolation when you have networking and other non-filesystem controlled interfaces to the kernel. Once you have implemented true "virtual machine" semantics for chroot, including local /sbin/init process &c &c it will be useful. >I'm quite apalled at this conservative view, >expressed without the slightest understanding of the code involved. I have a far better understanding of the code than you have. Julian, you need to calm down and work on something different. Your proposed feature isn't the magical bullet it takes to make chroot a safe place to live. If it were I would embrace it. As it is, adding this gruesome hack doesn't really provide us with anything that improves the situation. If you think otherwise, do it on your own systems. Poul-Henning -- Poul-Henning Kamp | phk@FreeBSD.ORG FreeBSD Core-team. http://www.freebsd.org/~phk | phk@login.dknet.dk Private mailbox. whois: [PHK] | phk@tfs.com TRW Financial Systems, Inc. Power and ignorance is a disgusting cocktail. From owner-freebsd-hackers Mon Feb 24 08:19:13 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id IAA26528 for hackers-outgoing; Mon, 24 Feb 1997 08:19:13 -0800 (PST) Received: from whyy.org (root@whyy.org [207.245.67.105]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id IAA26522 for ; Mon, 24 Feb 1997 08:19:09 -0800 (PST) Received: from tvmaster1.whyy.org (tvmaster1.whyy.org [199.234.236.48]) by whyy.org (8.7.5/8.7.3) with SMTP id LAA03302; Mon, 24 Feb 1997 11:19:03 -0500 (EST) Date: Mon, 24 Feb 1997 11:19:03 -0500 (EST) Message-Id: <199702241619.LAA03302@whyy.org> X-Sender: jehrenkrantz@whyy.org X-Mailer: Windows Eudora Pro Version 2.1.2 Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" To: Jim Riffle From: "..je" Subject: Re: Recurring freeze with 2.1.5 system Cc: freebsd-hackers@FreeBSD.ORG Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk At 10:09 AM 2/24/97 -0500, you wrote: > > >On Sun, 23 Feb 1997, Jake Hamby wrote: > >> There's a 486 system at my Internet provider that he's set up as a "geek >> box" for people to hack on. It's a fairly lame configuration (486DX/4 >> 100MHz, 8MB RAM, IDE drives, NE2000 card). Anyway, it has a recurring >> problem where it will only answer pings. Logins, either remote or from the >> console, will hang (telnet will connect, but not prompt for username), and >> the system must be forcibly rebooted. >> >> We think it may be a hardware problem, perhaps bad RAM. I'm just curious if >> there are any known bugs in 2.1.5-RELEASE which might cause this. The >> systems are similar to a SYN attack, except for the frozen local login. >> We're going to upgrade it to 2.2-GAMMA next weekend, and hopefully the >> problems will go away. If not, can we safely conclude that it is a problem >> of buggy hardware? > >I ran into a very similar problem to this some time ago. I am not sure if >this is your problem, but it would definatly be worth tring before >swapping out your hardware. > >Add these 2 lines into you kernel config file (you can change the 256 to >anything you like) > >options "CHILD_MAX=256" >options "OPEN_MAX=256" > > >I belive the default is 64. > >My symptoms were similar to where the machine would respond to pings, but >would not start anything new. no logins, no web. Name server would >continue to function. Basically anything running would still run as long >as it didn't have to open any files. > >Jim > > i had a similar problem it turned out to be the nic a gvc technoligies the only change i made was to replace the nic with an smc-whatever and all problems went away gud luk ..je Regards ..je From owner-freebsd-hackers Mon Feb 24 08:53:53 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id IAA28957 for hackers-outgoing; Mon, 24 Feb 1997 08:53:53 -0800 (PST) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id IAA28905 for ; Mon, 24 Feb 1997 08:52:36 -0800 (PST) Received: (from msmith@localhost) by genesis.atrad.adelaide.edu.au (8.8.5/8.7.3) id DAA07869; Tue, 25 Feb 1997 03:22:15 +1030 (CST) From: Michael Smith Message-Id: <199702241652.DAA07869@genesis.atrad.adelaide.edu.au> Subject: Re: installing without booting off floppy. In-Reply-To: <199702241537.HAA24423@freefall.freebsd.org> from Darren Reed at "Feb 25, 97 02:37:22 am" To: avalon@coombs.anu.edu.au (Darren Reed) Date: Tue, 25 Feb 1997 03:22:13 +1030 (CST) Cc: abelits@phobos.illtel.denver.co.us, avalon@coombs.anu.edu.au, hackers@freebsd.org X-Mailer: ELM [version 2.4ME+ PL28 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Darren Reed stands accused of saying: > > The trick to all of this is being able to run "sysinstall". > > Once you've installed a system, this gets deleted...is it worth keeping > this around, maybe as a way to install further packages ? Try looking in /stand someday, or read the MOTD 8) > Darren -- ]] Mike Smith, Software Engineer msmith@gsoft.com.au [[ ]] Genesis Software genesis@gsoft.com.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control. (ph) +61-8-8267-3493 [[ ]] Unix hardware collector. "Where are your PEZ?" The Tick [[ From owner-freebsd-hackers Mon Feb 24 09:32:33 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id JAA02674 for hackers-outgoing; Mon, 24 Feb 1997 09:32:33 -0800 (PST) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.50]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id JAA02653; Mon, 24 Feb 1997 09:32:23 -0800 (PST) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id KAA24627; Mon, 24 Feb 1997 10:28:40 -0700 From: Terry Lambert Message-Id: <199702241728.KAA24627@phaeton.artisoft.com> Subject: Re: o [1997/02/01] bin/2634 rtld patches for easy creation of chroot enviroments To: proff@iq.org (Julian Assange) Date: Mon, 24 Feb 1997 10:28:40 -0700 (MST) Cc: phk@critter.dk.tfs.com, hackers@freebsd.org, security@freebsd.org In-Reply-To: <199702241328.AAA10815@profane.iq.org> from "Julian Assange" at Feb 25, 97 00:28:33 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-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > The primary reason chroot() is rarely used is because it is painful > to use. LD_CHROOT makes it very, very easy to use. That said, I > have absolutely no doubt chroot() is used more than LD_LIBRARY_PATH, > LD_PRELOAD, LD_IGNORE_MISSING_OBJECTS, LD_TRACE_LOADED_OBJECTS, > LD_BIND_NOW, LD_SUPPRESS_WARNINGS and LD_WARN_NON_PURE_CODE put > together. The chroot/shared library interaction is the only painful element in using chroot(). This should be "fixed" with a loopback mount, rather than by the granting of a path lookup exception. In general, the use of a NULL chroot vp in a proc struct to indicate a non-chroot'ed process to namei(), is a bad thing. This special case code should go (and if it did, so would LD_CHROOT's utility). This would leave each process running on its own root vnode, effectively, and by default that vnode would be the real root. To resolve the mount covering FS geometry change update problem (which is *NOT* resolved in the chroot case currently, and is kludge-resolved in the non-chrooted process by reevaluation of the root vnode in the case of a NULL chroot vnode), you would need to use a vnode pointer pointer for the chroot vnode, and an addref/release mechanism for the pointer pointer reference to the pointer so that a placeholder vnode that wasn't a mount point could be freed when its last reference went away. 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-hackers Mon Feb 24 10:24:08 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id KAA05624 for hackers-outgoing; Mon, 24 Feb 1997 10:24:08 -0800 (PST) Received: from mailhub.aros.net (mailhub.aros.net [207.173.16.17]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id KAA05596 for ; Mon, 24 Feb 1997 10:24:03 -0800 (PST) Received: from fluffy.aros.net (fluffy.aros.net [207.173.16.2]) by mailhub.aros.net (8.8.5/Unknown) with ESMTP id LAA08383; Mon, 24 Feb 1997 11:23:53 -0700 (MST) Received: from fluffy.aros.net (localhost [127.0.0.1]) by fluffy.aros.net (8.8.5/8.6.12) with ESMTP id LAA27302; Mon, 24 Feb 1997 11:23:52 -0700 (MST) Message-Id: <199702241823.LAA27302@fluffy.aros.net> To: Alex Belits cc: hackers@freebsd.org Subject: Re: disallow setuid root shells? Date: Mon, 24 Feb 1997 11:23:51 -0700 From: Dave Andersen Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk -------- [CC: list trimmed] > IMHO adding "anti-setuid" code into shell will help, but that help won't > worth the effort of typing "setuid(getuid());" and recompiling the shell > -- it only makes one more step required to get the same result unless the > system is stripped down until becoming completely useless (but stripped > down until becoming completely useless system isn't vulnerable to most of > known security bugs anyway). I disagree. It's a small thing, and very easy to get around, but it would help reduce the number of breakins by people who don't understand what they're doing aside from running this program-thingy that someone gave them. I freely admit that most of these people will be using widely published exploit code, and that almost any vigilant sysadmin won't be vulnerable to them -- but not everybody is anal about keeping their computer up to date and secure. Forgive me for sounding political, but if even one or two computers are prevented from having a root compromise by this, it seems worthwhile - especially since nobody can think of anything it would actually hurt. -Dave From owner-freebsd-hackers Mon Feb 24 11:06:03 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id LAA08744 for hackers-outgoing; Mon, 24 Feb 1997 11:06:03 -0800 (PST) Received: from bmcgover-pc.cisco.com (bmcgover-pc.cisco.com [171.69.104.147]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id LAA08720 for ; Mon, 24 Feb 1997 11:05:43 -0800 (PST) Received: from bmcgover-pc.cisco.com (localhost.cisco.com [127.0.0.1]) by bmcgover-pc.cisco.com (8.8.5/8.8.2) with ESMTP id OAA00646 for ; Mon, 24 Feb 1997 14:05:08 -0500 (EST) Message-Id: <199702241905.OAA00646@bmcgover-pc.cisco.com> To: hackers@freebsd.org Subject: Pseudo-driver cookbook (phase II) Date: Mon, 24 Feb 1997 14:05:08 -0500 From: Brian McGovern Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Ok. So I'm getting a little bored, and I made a big jump at the end ;) Sue me. Anyhow, here is round two. Its probably (easily) twice as big as the original, and gets in to the topics I only mentioned in the first round. I have corrected a few things that people mentioned (I probably missed a lot more :) :) ). Also, I want to say up front that I discarded several suggestions, just to keep the first part of the document "as completely brain-numbing simple" as I could. Please don't take offense. I just want a quick-to-understand document. As always, suggestions are welcome. I'll probably make at least one or two more passes over it before formally posting it on my web site, and submitting it to the core team for inclusion someplace (handbook?). I'll also probably start work on a character/tty driver, as soon as I get a peice of hardware I'm expecting. To all of those who made it possible to do this document, I thank you - especially Michael Smith, who has managed to so far answer all of my really stupid questions. There will be more. Anyhow, here goes.... -Brian [Ed Note: This document has been written to document what I have learned over the past month about writing pseudo-device drivers for the FreeBSD 2.x and 3.0 operating systems. I realize that it is probably incomplete. However, it is designed to give someone with no knowledge of device drivers a step in the right direction. It is no substitute for a well written manual on writing device drivers. I recommend that all perspective driver-writters take the time to read at least one or two books on the subject cover to cover before using this document to explore the differences between what they've read about, and what FreeBSD uses. I also expect that in the future, I will be doing a similar document for a real character/tty device driver. If you have any questions, you may email me. However, chances are, since I am _just_ learning how to do this myself, I'll have to forward your email to the hackers mailing list. -BJM] Writing a character pseudo-device driver is actually not all that difficult, once you understand all of the steps that are required. Hopefully, this walk through of creating a character pseudo-device driver will set the stage for the understanding of writing other device drivers, with more functionality. The first step is to think about what you want to accomplish with the device driver, and how to go about putting it all together. In our first example, we will create a very simplistic driver - one that will allow you to open the device, close it, and read from it. When you read, it will return part, or all of a specified message, based on the size of your reads. For those of you who have absolutely no background on writing a device driver, I recommend you head off to the nearest book store, and pick up a book or two on the subject. Although the details of "how" to write one for a particular system may not apply, the background and concepts will. I will attempt to replicate the needed information here, but I can not guarentee to cover everything that may play a role in the device driver you wish to write. The first thing you'll need to do is set up a working enviornment in the kernel source tree. I recommend creating a directory (for pseudo-devices) under /usr/src/sys/dev/YOUR_DRIVER_NAME. I'll be calling my driver "foo", so I'll create the directory /usr/src/sys/dev/foo. Now, within this directory, I'm going to create a file called foo.c. I use the name "foo", simply so I know it will relate to my "foo" driver. Make sense? I hope so :) In this file, I'm going to include several headers, right off the bat, so my source will look like: #include #include #include #include #include #include These include files will include everything that we need for our simple device driver (and quite possibly more). Now, the next logical thing to do would be to define a MAJOR NUMBER for our device driver. A major number is merely a unique number to seperate our device driver from all of the other device drivers. You can find the used major numbers in /usr/src/sys/i386/conf/majors.i386. Since our device driver will be character based, we look for the character major numbers, and then look for an unused one. In our case, number 20 is "reserved for local use", so we'll use that number, since our device driver will never be distributed, and therefore, should never conflict (unless we write another character device driver locally). What we will do now is #define CDEV_MAJOR to be equal to the number we just chose. This is one of those "standards" that just make sense. You'll find that doing it this way, rather than just hard-coding the major number, makes it easier to change later, as well as lets other developers know what to look for, in case they ever have to work on your driver. It'll also help stop typos, as well. So, now, your driver code should look like: #include #include #include #include #include #include #define CDEV_MAJOR 20 Not bad. We're making some headway. The next thing that I want to do is define the buffer that we'll be using for our driver. In my case, I want a character buffer with a string of my choice in it (my message). Hence, I'll add one more line to our code, making it look like: #include #include #include #include #include #include #define CDEV_MAJOR 20 static char message[] = "Wow. I really have a device driver here!\n\0"; You'll notice that the string is declared static. This is so that it will not conflict with any other variables called "message" elsewhere in the kernel. You will see, rather quickly, that nearly all global variables, or exported functions, are declared static. Now, we only have a few more things to set up for our device driver. Since we'll only be concerned about reading from our driver, we'll only concern ourselves explicitly with the read routine. We will "fake" the open and close routines for the time being, so that they will always succeed. Note, that this can cause problems, simply because they'll be able to open dozens of "foo" devices. However, we'll add some error checking to our first read routine to keep from selecting invalid minor numbers. Note, once we have a working open and close routine, we'll be able to move the error checking there, and out of the read routine completely. Having error checking in the open routine is the "proper" thing to do. However, I've placed it in the read routine (and left the open routine NULL) in order to create the most simplistic device driver, and still handle the error cases. In all future drivers, error checking will be in the open routine. Note that the kernel does a certain amount of pre-error checking, and will not allow the program to call driver routines with improper (not open) minor numbers. Now, you may ask "What is a minor number?". Minor numbers are used to distinguish subsets of a device from one another. Although the interpretation of the minor device number is left entirely to the descretion of the driver itself, it is usually used to distinguish between physical devices. For instance, all 8250- and 16550- type serial devices will share a major number of 28, while each individual serial port will have its own minor number, or, in the case of the SIO driver, it will have multiple - one for dial in, dial in initial state, dial in lock state, dial out, dial out initial state, and dial out lock state. The point is, this is how you keep track of which specific device needs to be handled. Ok. The next step will be to define some information about our read routine. Again, this is something that "just has to be done", so we'll do it. Basically, it sets up our to-be-defined read routine as an appropriate type of function to be a device-driver read routine. So, now, make your driver code look as follows (I've added comments for clarity at this point): /* Include the header files that we'll need */ #include #include #include #include #include #include /* Define our MAJOR NUMBER for the device driver */ #define CDEV_MAJOR 20 /* Define our message buffer, with a prebuilt message */ static char message[] = "Wow. I really have a device driver here!\n\0"; /* Define our routines in the proper format for a device-driver */ static d_read_t fooread; Now, you'll notice with that last line that we declared something called "fooread" as being of some type "d_read_t". "d_read_t" is the type of function that the kernel expects as a device driver read routine. fooread will be the name of our function. Note it is declared static (See above). One note on device drivers I've failed to touch on that suddenly has come to me. Device driver "names", in our case, "foo", can be anywhere from 1-4 characters. Most systems do not allow numbers (for reasons that will become obvious later). Once defined, all references to that device driver will use that name. Anyhow, to get back on track... The next thing we have to do is set up a block that will define our device driver for the kernel. It is basically a structure that contains pointers to all of our routines that comprise the device driver, plus a few other flags (that I won't get in to here). Note the use of null and nx before the names of the routines. Using null will always make that call "succeed" to your application (although nothing will actually get done). using nx will always make that call "fail" to your application (again, with nothing really getting done). So, now we'll make our code look like this: /* Include the header files that we'll need */ #include #include #include #include #include #include /* Define our MAJOR NUMBER for the device driver */ #define CDEV_MAJOR 20 /* Define our message buffer, with a prebuilt message */ static char message[] = "Wow. I really have a device driver here!\n\0"; /* Define our routines in the proper format for a device-driver */ static d_read_t fooread; /* Define the cdewsw structure for our driver */ static struct cdevsw foo_cdevsw = { nullopen, nullclose, fooread, nxwrite, nxioctl, nxstop, nxreset, nxdevtotty, nxselect, nxmmap, NULL, "foo", NULL, -1 }; You'll note we set the open and close routines to nullopen and nullclose, respectively. This will allow them to always succeed, because we will not be able to read from a device until it is "opened", and most programs will try to close it once its done with it. Therefore, these two calls should always succeed. You'll then note that we have fooread declared as the read routine. Again, this is the function we'll write to actually handle reading from our pseudo-foo device. All other functions have been set nx..., which means that calls to these routines (such as write(), select(), ioctl(), mmap(), etc) will all fail. Itching to go yet? We're almost there. Two functions, and a couple of declarations, and we'll be done. Lets look at the read routine itself now. The read routine is passed three parameters. A dev_t structure which gives device information, a pointer to a struct uio, which defines the transfer to occur, and an integer flag. Since we're keeping things simple, I won't talk about flags right away. The dev_t structure, and the uio structure, however, are critical to our application. The most useful (to our cause) portion of the dev_t structure will be the minor device number. We'll need this to verify whether we have a valid device. Also, as we move forward, and rewrite the device driver to handle more than one pseudo-device, we'll use the minor number to make decisions as to what buffer we'll actually manipulate. The uio structure is a little more complicated. For now, we'll do very little with it, other than use it to work out our read request. However, we will eventually use two of the structures members, so I'll note them now. The first is uio_resid. This is the number of bytes that the application desires to read. We do not have to actually read this much, but its useful in defining how much data we have to move. The second is uio_offset. This is the offset in to the data stream that the read is to take place. In our first pass, we will not use this field at all, as we'll always return reads starting from offset 0 (for the sake of ease). Later, we'll code so that the buffer appears to be a "ring" buffer, repeating the message until the read request is satisfied. Future reads on the same descriptor will also start back up where the prior read left off. You'll note that the function uiomove forms the base of our read routine. Basically, uimove is called with a pointer to the in-kernel data buffer, the number of bytes to move, and the pointer to the uio structure passed to the routine. So, now, to define our read routine, we'll do something like this (note: I will no longer display the full source file again until we are 100% done, in order to save space). static int fooread(dev_t dev, struct uio *myuio, int flag) { int result; /* The result of the uiomove function */ if (minor(dev) != 0) /* If someone tries to read from other than minor # */ return ENODEV; /* 0, reject the request saying there is no device */ result = uiomove(message, MIN(myuio->uio_resid, sizeof(message)), myuio); return result; } You'll notice that I used the MIN of either the amount the user program wanted to read, or the size of our message. This will make both small reads work, as well as returning short reads if they ask for a larger chunk of data. Now, we're 80% there. The last thing we need to do is actually write the code to set up the device, and get us up and running. Once these last two peices are done, we can actually compile the routine, and try it out. The next routine we'll write is the init routine, which is responsible for "starting up" our device driver. It can be as simple as stating the driver is loaded, or it can be very complex. In our case, since we're doing a pseudo-device driver, and not a regular character device driver, we won't have probe and attach routines to do the startup work, so we'll have to do it ourselves in the init routine. Our init routine will look something like: static void fooinit(void *unused) { dev_t dev; printf("foo0: Foo test character device driver installed and ready.\n"); printf("foo0: Configured for 1 device\n"); dev = makedev(CDEV_MAJOR,0); cdevsw_add(&dev, &foo_cdevsw, NULL); } This routine basically will print out two lines of notification on boot up, and then get the device set up in the kernel. The last thing we need to do is tell the kernel (from inside the driver) what routine has to be executed in order to get everything started, as well as give it a "priority" for loading. As an example of "priority", you can look at the Ethernet cards defined in the LINT kernel config file. You'll note it says not to change the order, in order to keep them from screwing up each other's probes... This is similar. Unless you have a very good reason to change it, I recommend to use the default priority. With this in mind, the following default line should work 99% of the time: SYSINIT(foodev, SI_SUB_DRIVERS, SI_ORDER_MIDDLE+CDEV_MAJOR, &fooinit, NULL); What does it all do? Even I don't know ;) But, it works, so use it. Now, all thats left is some touchup. Obviously, we won't want to have our driver load in to a kernel that doesn't have it configured in. When we run the config utility later on, it will generate a .h file in the compilation directory, with a file name thats the same as our device driver name. In that header file will be a single declaration, that will consist of a #define N*, where * is replaced with an all upper-case name of our driver. In our case, it will be a #DEFINE NFOO n, where n is replaced by the number of pseudo devices we configured. In this case, it should never be more than one, but it could be. Therefore, we'll make our whole driver look like this: #include "foo.h" #if NFOO > 0 /* Include the header files that we'll need */ #include #include #include #include #include #include /* Define our MAJOR NUMBER for the device driver */ #define CDEV_MAJOR 20 /* Define our message buffer, with a prebuilt message */ static char message[] = "Wow. I really have a device driver here!\n\0"; /* Define our routines in the proper format for a device-driver */ static d_read_t fooread; /* Define the cdewsw structure for our driver */ static struct cdevsw foo_cdevsw = { nullopen, nullclose, fooread, nxwrite, nxioctl, nxstop, nxreset, nxdevtotty, nxselect, nxmmap, NULL, "foo", NULL, -1 }; static int fooread(dev_t dev, struct uio *myuio, int flag) { int result; /* The result of the uiomove function */ if (minor(dev) != 0) /* If someone tries to read from other than minor # */ return ENODEV; /* 0, reject the request saying there is no device */ /* Now do the real read */ result = uiomove(message, MIN(myuio->uio_resid, sizeof(message)), myuio); return result; } static void fooinit(void *unused) { dev_t dev; /* The device we'll create */ /* Now, put some output to the console, so we know we're here */ printf("foo0: Foo test character device driver installed and ready.\n"); printf("foo0: Configured for 1 device\n"); /* Actually create the device */ dev = makedev(CDEV_MAJOR,0); cdevsw_add(&dev, &foo_cdevsw, NULL); /* All done! */ } /* Tell the kernel how to get us started */ SYSINIT(foodev, SI_SUB_DRIVERS, SI_ORDER_MIDDLE+CDEV_MAJOR, &fooinit, NULL); #endif Now, thats it for the driver. The next step is to go in to /usr/src/sys/i386/conf. I modified majors.i386 so that character device 20 was called "foo". This was not required, but if I had other developers working on this system, I'd want them to know I used 20 for my device driver, and its no longer available for them to use until I'm done with it, and change it back. Secondly, you'll need to edit files.i386. Add the line dev/foo/foo.c optional foo device-driver someplace in the file. I usually do it about 25-30 lines down, where the similar looking lines start. Placement in the file is not critical, I just like to keep things looking consistent. Almost there. Just a couple of more things. Next, create your kernel config file (getting real close now). Add the line: pseudo-device foo 1 someplace to the file. This will let the kernel know you need the foo driver, and it will tell the driver it wants one device (more on this later when we support multiple devices). Now config the kernel, make it as per usual, and install it as per usual. If there are errors or problems, check your source again for typos, unterminated comments, etc. Once you've got it compiled and installed, continue. The last thing to do is to actually create the device in the /dev subdirectory. So, cd to it now. The command for making a device node is called mknod. Its standard format (according to itself when run with no parameters) is: mknod name [b | c] major minor. For our device driver, we'll use something like: mknod foo0 c 20 0 Which tells it to create a device called foo0, which will be a character device with a major number of 20, and a minor number of 0. Guess what. We're done. Reboot the box. You should be able to read from the device now (assuming you saw the banner lines on startup) with cat < /dev/foo0. Your "message" will repeat infinately, until you hit CTRL-C. Also, you should be able to make open() calls to /dev/foo0, and read them with the read() call, as per a normal device. Note, however, that each read() will return the message from the beginning, and if your buffer is too small, you'll never see the end of it. This is also true with the cat case if you make your message too long. However, I know that cat uses a rather large buffer, so this will be difficult to do. Now, we'll create a slightly more full-fledged driver. We'll add open and close routines, and move the minor number error checking to the open routine, where it really belongs. The close routine will be the most straight forward, so we'll do that first. Since close will never be called unless a successful open has occured, and we don't have any real work to do to close the device, the function itself will always just return a success. Heres how it will look. Note, that we could have left the close routine out, and leave the cdevsw structure set to nullclose. However, I've included it to show you how to stub it, so you can add your own features later. static int fooclose(dev_t dev, int flags, int mode struct proc *p) { return 0; } The open routine will be almost as straight forward. All that it has to do is check the minor device number, to see if its valid. If it is, it will return 0 (a success). Otherwise, we'll have it return ENODEV, stating to the caller that there is no such device. static int fooopen(dev_t dev, int flags, int mode struct proc *p) { if (minor(dev) != 0) return ENODEV; else return 0; } Pretty easy. Now, lets glue them in. We'll need to add the routines to our cdevsw structure, as well as declare them properly before the cdevsw structure. Here, again, I've layed the whole device driver out, so you can see what it should look like: #include "foo.h" #if NFOO > 0 /* Include the header files that we'll need */ #include #include #include #include #include #include /* Define our MAJOR NUMBER for the device driver */ #define CDEV_MAJOR 20 /* Define our message buffer, with a prebuilt message */ static char message[] = "Wow. I really have a device driver here!\n\0"; /* Define our routines in the proper format for a device-driver */ static d_read_t fooread; static d_open_t fooopen; /* WE JUST ADDED THESE ! */ static d_close_t fooclose; /* Define the cdewsw structure for our driver */ static struct cdevsw foo_cdevsw = { fooopen, fooclose, fooread, nxwrite,/* Note: changed nullopen and nullclose */ nxioctl, nxstop, nxreset, nxdevtotty, /* to fooopen and fooclose */ nxselect, nxmmap, NULL, "foo", NULL, -1 }; /* New open routine */ static int fooopen(dev_t dev, int flags, int mode struct proc *p) { if (minor(dev) != 0) return ENODEV; else return 0; } /* New close routine */ static int fooclose(dev_t dev, int flags, int mode struct proc *p) { return 0; } /* "Corrected" read routine, to put error checking where it belongs (in open) */ static int fooread(dev_t dev, struct uio *myuio, int flag) { int result; /* The result of the uiomove function */ /* Note the error checking is now gone! See foopen */ /* Now do the real read */ result = uiomove(message, MIN(myuio->uio_resid, sizeof(message)), myuio); return result; } static void fooinit(void *unused) { dev_t dev; /* The device we'll create */ /* Now, put some output to the console, so we know we're here */ printf("foo0: Foo test character device driver installed and ready.\n"); printf("foo0: Configured for 1 device\n"); /* Actually create the device */ dev = makedev(CDEV_MAJOR,0); cdevsw_add(&dev, &foo_cdevsw, NULL); /* All done! */ } /* Tell the kernel how to get us started */ SYSINIT(foodev, SI_SUB_DRIVERS, SI_ORDER_MIDDLE+CDEV_MAJOR, &fooinit, NULL); #endif There. That wasn't so painful. Now that we have a reasonably functioning driver, lets add some flexability. Lets now say that we wanted to implement our message buffer as a ring buffer, so that each read would pick up where the last one left off, and that if a read was big enough to go off the end of the buffer, we'd wrap instead of returning a short read. Since we're changing the operation of how we'll be reading data, we'll obviously be looking at the read routine. Note how we begin to add some complexity. static int fooread(dev_t dev, struct uio *myuio, int flag) { int toread, result, offset; while (myuio->uio_resid) /* Number of characters still in the request pipe */ { offset = myuio->uio_offset % sizeof(message); toread = min(myuio->uio->resid, sizeof(message)); result = uiomove(message + offset, toread, myuio); if (result) return result; } return 0; } These changes allow the buffer to be circular. As mentioned earlier, the uio_resid member of the uio structure maintains the number of bytes to be read. The uio_offset member keeps track of where in the data stream you are. Note that there are no changes to these members themselves. They're only being referenced in the code, not set. This is because the function uiomove handles all of the required housekeeping on these values. Now, lets tackle writing to the message itself. This will require one additional routine for writing, and some changing of how the buffer is manipulated. Lets look at the write routine first. In this example, I'm always going to have the write routine start at the beginning of the buffer, and truncate messages that are too long to fit. It does not have to be this way. However, I'd like to make it a little less confusing, as if I concerned myself with offsets, and allowed writes to "ring" around, its possible I can delete the first portion of my message. Additionally, when a new reader opens the device, I want them to start at the beginning of my message, not part way through. If you'd like to enhance this as an exercise for yourself, feel free. Thats exactly the type of experimentation that will help you learn how these things work. Here is a simple write routine for us to start with. You'll note that there is a define FOOBUFSIZE that we haven't talked about yet. I'll speak more about it after I show you the routine, so don't worry. static int foowrite(dev_t dev, struct uio *myuio, int flag) { int towrite, result; towrite = min(myuio->uio_resid, (FOOBUFSIZE - 1)); uiomove(message, towrite, myuio); message[towrite] = 0; return 0; } Now, we'll also have to change how we declare our message buffer. Currently, its stored in the kernel as a string constant, which, although you COULD change it, it defeats the concept of "constant". Therefore, I'd like to redefine it to a more familar character string. So, we'll change the declaration to: unsigned char message[FOOBUFSIZE]; Now, what is this FOOBUFSIZE? Its something we'll have to define to establish the size of the buffer we'll be using. What I usually do is something like this: #ifndef FOOBUFSIZE #define FOOBUFSIZE 1024 #endif This way, if it isn't previously declared, the buffer will default to 1K. This method allows you to specify a line that looks like the following in your config file, and it will be used by the driver: options FOOBUFSIZE=2048 This will allow you to use 2K buffers. For sanity's sake, it'd be a good idea to put it right before or after the "pseudo-device foo 1" line in your config file. Or, if you're like me, and are anal about keeping the various lines of your config files together (ie - all of your options together, all of your devices, etc), you may want to comment what its for. You'll notice in the code sample below that I also changed the sizeof(message) calls in fooread to using strlen(message). This is keep everything working if you write a short message to your buffer - it will wrap at the first 0 byte it sees, rather than at the end of the message space itself. Note, you can no longer use this driver for binary information. However, it will still work fine with text. The last thing you need to do is add the write routine to your cdevsw structure, and define it just before (as we did with read, open, and close). So, now we should look like this: #include "foo.h" #if NFOO > 0 /* Include the header files that we'll need */ #include #include #include #include #include #include /* Define our MAJOR NUMBER for the device driver */ #define CDEV_MAJOR 20 /* Define our message buffer, with a prebuilt message */ static unsigned char message[FOOBUFSIZE] = "Wow. I really have a device driver here!\n\0"; /* Define our routines in the proper format for a device-driver */ static d_read_t fooread; static d_write_t foowrite; /* Add me here! */ static d_open_t fooopen; static d_close_t fooclose; /* Define the cdewsw structure for our driver */ /* Note we now have foowrite, as well */ static struct cdevsw foo_cdevsw = { fooopen, fooclose, fooread, foowrite, nxioctl, nxstop, nxreset, nxdevtotty, nxselect, nxmmap, NULL, "foo", NULL, -1 }; /* New open routine */ static int fooopen(dev_t dev, int flags, int mode struct proc *p) { if (minor(dev) != 0) return ENODEV; else return 0; } /* New close routine */ static int fooclose(dev_t dev, int flags, int mode struct proc *p) { return 0; } /* Now fooread utilizes a circular queue scheme */ static int fooread(dev_t dev, struct uio *myuio, int flag) { int toread, result, offset; while (myuio->uio_resid) /* Number of characters still in the request pipe */ { offset = myuio->uio_offset % strlen(message); toread = min(myuio->uio->resid, strlen(message)); result = uiomove(message + offset, toread, myuio); if (result) return result; } return 0; } /* Foowrite writes to the string, and zeros the last character */ static int foowrite(dev_t dev, struct uio *myuio, int flag) { int towrite, result; towrite = min(myuio->uio_resid, (FOOBUFSIZE - 1)); uiomove(message, towrite, myuio); message[towrite] = 0; return 0; } static void fooinit(void *unused) { dev_t dev; /* The device we'll create */ /* Now, put some output to the console, so we know we're here */ printf("foo0: Foo test character device driver installed and ready.\n"); printf("foo0: Configured for 1 device\n"); /* Actually create the device */ dev = makedev(CDEV_MAJOR,0); cdevsw_add(&dev, &foo_cdevsw, NULL); /* All done! */ } /* Tell the kernel how to get us started */ SYSINIT(foodev, SI_SUB_DRIVERS, SI_ORDER_MIDDLE+CDEV_MAJOR, &fooinit, NULL); #endif Thats about it for a basic device driver. There are some extras that you can throw in, like supporting multiple buffers, select() and ioctl() call support, etc, but those are all fairly straight forward, especially with a pseudo-device driver (for instance, with select(), you should ALWAYS be able to write). Therefore, I'm going to skip quite a bit, and go to a finished driver that includes some of these features. You'll be able to set your config line (pseudo-device foo X) to any positive value of X you like. Also, you can set FOOBUFSIZE in your config file to get buffers larger or smaller than 1K. Here's the complete code. See what you can do with it. [Ed Note: As of this writing, some code, such as the select routine and ioctl call, has not been fully tested. It has been included merely as an example. At some future time, the code should be tested and debugged properly (although it "appears" to work now)]. #include "foo.h" #if NFOO > 0 #include #include #include #include #include #include #define CDEV_MAJOR 20 #ifndef FOOBUFSIZE # define FOOBUFSIZE 1024 #endif typedef struct { char buffer[FOOBUFSIZE];} msgbuf; msgbuf messagebuf[NFOO]; struct foosoftc { int written; }; struct foosoftc fsc[NFOO]; static d_read_t fooread; static d_write_t foowrite; static d_open_t fooopen; static d_close_t fooclose; static d_select_t fooselect; static d_ioctl_t fooioctl; static struct cdevsw foo_cdevsw = { fooopen, fooclose, fooread, foowrite, fooioctl, nxstop, nxreset, nxdevtotty, fooselect, nxmmap, NULL, "foo", NULL, -1 }; static void fooinit(void *unused) { dev_t dev; int i; printf("Test character driver\n"); dev=makedev(CDEV_MAJOR,0); cdevsw_add(&dev, &foo_cdevsw, NULL); for (i=0;i= NFOO) return ENODEV; else return 0; } static int fooclose(dev_t dev, int flags, int mode, struct proc *p) { return 0; } static int fooselect(dev_t dev, int rw, struct proc *p) { switch (rw) { case FREAD: { if (fsc[minor(dev)] != 0) return 1; else return 0; break; } case FWRITE: { return 1; break; } case 0: { return 0; break; } } return 0; } static int fooioctl(dev_t dev, int cmd, caddr_t data, int flags, struct proc *p) { switch(cmd) { case FIONREAD: { *data = strlen(messagebuf[minor(dev)].buffer); break; } default: { return ENOTTY; break; } } return 0; } static int foowrite(dev_t dev, struct uio *myuio, int flag) { int towrite, result, offset; offset = myuio->uio_resid; towrite = min(myuio->uio_resid, (FOOBUFSIZE - 1)); uiomove(messagebuf[minor(dev)].buffer, towrite, myuio); messagebuf[minor(dev)].buffer[offset] = 0; fsc[minor(dev)] = 1; return 0; } static int fooread(dev_t dev,struct uio *myuio, int flag) { int toread, result, offset; if (strlen(messagebuf[minor(dev)].buffer) == 0) return EAGAIN; while(myuio->uio_resid) { offset = myuio->uio_offset % strlen(messagebuf[minor(dev)].buffer); toread = min(myuio->uio_resid, strlen(messagebuf[minor(dev)].buffer) - offset); result = uiomove(messagebuf[minor(dev)].buffer + offset, toread, myuio); if (result) return result; } return 0; } SYSINIT(foodev, SI_SUB_DRIVERS, SI_ORDER_MIDDLE+CDEV_MAJOR, &fooinit, NULL); #endif /* NFOO */ If you're looking for more information, Julian Elischer has commited several of his device driver models in to the FreeBSD source tree. I suspect you'll find it appearing in the 3.0 development tree shortly. Additionally, I will be posting them on my Web page, as soon as I get around to reworking this document (and others) in to HTML. From owner-freebsd-hackers Mon Feb 24 11:19:08 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id LAA09471 for hackers-outgoing; Mon, 24 Feb 1997 11:19:08 -0800 (PST) Received: from mail.crl.com (mail.crl.com [165.113.1.22]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id LAA09465 for ; Mon, 24 Feb 1997 11:19:05 -0800 (PST) Received: from apollo.it.hq.nasa.gov by mail.crl.com with SMTP id AA09833 (5.65c/IDA-1.5 for ); Mon, 24 Feb 1997 11:17:58 -0800 Received: from wirehead.it.hq.nasa.gov (WireHead.it.hq.nasa.gov [131.182.119.88]) by apollo.it.hq.nasa.gov (8.8.3/8.8.3) with ESMTP id OAA04199 for ; Mon, 24 Feb 1997 14:14:24 -0500 (EST) Received: from localhost (cshenton@localhost) by wirehead.it.hq.nasa.gov (8.6.12/8.6.12) with ESMTP id TAA13136 for ; Mon, 24 Feb 1997 19:16:23 GMT Message-Id: <199702241916.TAA13136@wirehead.it.hq.nasa.gov> X-Authentication-Warning: wirehead.it.hq.nasa.gov: cshenton owned process doing -bs To: hackers@freebsd.org Subject: migrating 2.1.7 -> 2.2: simple or hairy? X-Mailer: Mew version 1.03 on Emacs 19.31.8 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Date: Mon, 24 Feb 1997 14:16:13 -0500 From: Chris Shenton Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk We've got a number of boxes running 2.1.7 and want to migrate to 2.2; is it easy or hard? Ideally I could do: mv /usr/src /usr/src.old cvsup -supfile [whatever's appropriate for 2.2] cd /usr/src make world make install In the past, I've had problems trying to do this: libraries became out of sync and the make, cc, and other failed, leaving me with an unusable system. Also, which cvsup files are appropriate? I've been tracking 'stable', which gives me 2.1.7. Does 'current' give me 2.2 or 3.0? Which would be appropriate? Any other pointers, like maybe building in a separate /usr/src-new tree? Thanks. From owner-freebsd-hackers Mon Feb 24 11:25:50 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id LAA10027 for hackers-outgoing; Mon, 24 Feb 1997 11:25:50 -0800 (PST) Received: from gvr.win.tue.nl (root@gvr.win.tue.nl [131.155.210.19]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id LAA10004; Mon, 24 Feb 1997 11:25:40 -0800 (PST) Received: (from guido@localhost) by gvr.win.tue.nl (8.8.5/8.8.2) id UAA03721; Mon, 24 Feb 1997 20:24:42 +0100 (MET) From: Guido van Rooij Message-Id: <199702241924.UAA03721@gvr.win.tue.nl> Subject: Re: o [1997/02/01] bin/2634 rtld patches for easy creation of chroot enviroments In-Reply-To: <199702241328.AAA10815@profane.iq.org> from Julian Assange at "Feb 25, 97 00:28:33 am" To: proff@iq.org (Julian Assange) Date: Mon, 24 Feb 1997 20:24:42 +0100 (MET) Cc: phk@critter.dk.tfs.com, hackers@freebsd.org, security@freebsd.org X-Mailer: ELM [version 2.4ME+ PL28 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > It would be neat if one could actually use the chroot() facility > in a secure and efficient manner, without modifying the source for > main() on every binary in the system. You are right. It would be > neat. Since when is something being small, fast, secure, neat and > providing functionality that wouldn't otherwise be there grounds > for rejection of code? I'm quite apalled at this conservative view, > expressed without the slightest understanding of the code involved. > I understand your point and partly I do agree. However, seeing the enormous security hole we found lately in having the setlocale() stuff in ld.so, ppl are a bit reluctant to modify such a piece of code. I think that is understandable. What I do when I want a chroot jail is use a simple program, chrootuid, that does almost the same. In my opinion, that is a cleaner solution because whenever something would be broken, it is only this tiny little program that is broken, instead of *all* binaries. The fact that your code is probably correct does not change this fact. Btw: chroouit can be found at ftp.win.tue.nl:/pub/security -Guido From owner-freebsd-hackers Mon Feb 24 11:50:20 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id LAA11872 for hackers-outgoing; Mon, 24 Feb 1997 11:50:20 -0800 (PST) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id LAA11862 for ; Mon, 24 Feb 1997 11:50:13 -0800 (PST) Received: from current1.whistle.com (current1.whistle.com [207.76.205.22]) by alpo.whistle.com (8.8.5/8.8.4) with SMTP id KAA17627; Mon, 24 Feb 1997 10:37:17 -0800 (PST) Message-ID: <3311DF5D.41C67EA6@whistle.com> Date: Mon, 24 Feb 1997 10:35:09 -0800 From: Julian Elischer Organization: Whistle Communications X-Mailer: Mozilla 3.0Gold (X11; I; FreeBSD 2.2-CURRENT i386) MIME-Version: 1.0 To: Darren Reed CC: matt@lkg.dec.com, terry@lambert.org, hackers@FreeBSD.org Subject: Re: Alternatives to SYSV IPC? References: <199702240814.AAA07697@freefall.freebsd.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk Darren Reed wrote: > > In some mail from Julian Elischer, sie said: > > > > > if (socketpair(AF_UNIX, SOCK_STREAM, 0, fds) < 0) > > > perror("socketpair"); > > > > > > > how come no-one uses AF_LOCAL with SOCK_DGRAM? > > how portable is AF_LOCAL ? > > Darren well as people were talking about using as a standin for SYV_IPC I assume they are talking about BSD based systems and they all have AF_LOCAL (== AF_UNIX) From owner-freebsd-hackers Mon Feb 24 11:51:49 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id LAA11960 for hackers-outgoing; Mon, 24 Feb 1997 11:51:49 -0800 (PST) Received: from sendero.i-connect.net ([206.190.144.100]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id LAA11947 for ; Mon, 24 Feb 1997 11:51:43 -0800 (PST) Received: (from shimon@localhost) by sendero.i-connect.net (8.8.5/8.8.4) id MAA10819 for freebsd-hackers@freebsd.org; Mon, 24 Feb 1997 12:51:26 -0800 (PST) Message-ID: X-Mailer: XFMail 1.1-alpha [p0] on FreeBSD Content-Type: text/plain; charset=iso-8859-8 Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Date: Mon, 17 Feb 1997 14:34:45 -0800 (PST) Organization: iConnect Corp. From: Simon Shapiro To: freebsd-hackers@freebsd.org Subject: More fun with 2.2 compiles Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Along the same route, as my previous message; I did: cd /usr/src rm -rf * cvs co -t -r RELENG_2_2 . nohup make world > world.out 2>&1& I got: ===> gnu/usr.bin/perl/x2p cc -O -I/usr/src/gnu/usr.bin/perl/x2p/../perl -c a2p.c In file included from /usr/src/gnu/usr.bin/perl/x2p/a2py.c:34, from /usr/src/gnu/usr.bin/perl/x2p/a2p.y:409: /usr/src/gnu/usr.bin/perl/x2p/util.h:54: conflicting types for `setenv' /usr/include/stdlib.h:118: previous declaration of `setenv' *** Error code 1 Stop. As I would like to make a release too, I tried to change the CVS tree. I did: cd /usr/src/gnu/usr.bin/perl/x2p cvs co -r RELENG_2_2 util.h And Got: cvs checkout: cannot find module `util.h' - ignored Now, if I checkout the -current version, the offending line is removed, along with a comments. The 2.2 checkout of the entire tree brings an incorrect version. What Gives? Simon From owner-freebsd-hackers Mon Feb 24 12:02:22 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id MAA12870 for hackers-outgoing; Mon, 24 Feb 1997 12:02:22 -0800 (PST) Received: from llaic.univ-bpclermont.fr (llaic.univ-bpclermont.fr [192.54.142.163]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id MAA12861 for ; Mon, 24 Feb 1997 12:02:17 -0800 (PST) Message-Id: <199702242002.MAA12861@freefall.freebsd.org> Received: by llaic.univ-bpclermont.fr (1.38.193.4/16.2) id AA06414; Mon, 24 Feb 1997 21:02:08 +0100 From: Roger Espel Llima Subject: Re: disabling setuid sh/csh To: hackers@freefall.freebsd.org Date: Mon, 24 Feb 1997 21:02:08 +0100 (MET) In-Reply-To: <199702241906.LAA08757@freefall.freebsd.org> from "owner-hackers-digest@freefall.freebsd.org" at Feb 24, 97 11:06:07 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-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > I disagree. It's a small thing, and very easy to get around, but > it would help reduce the number of breakins by people who don't > understand what they're doing aside from running this program-thingy > that someone gave them. Except that the "program-thingys" that someone gave them would include a setuid(getuid()) from there on. > I freely admit that most of these people will be using widely > published exploit code, and that almost any vigilant sysadmin won't > be vulnerable to them -- but not everybody is anal about keeping their > computer up to date and secure. Forgive me for sounding political, > but if even one or two computers are prevented from having a root > compromise by this, it seems worthwhile - especially since nobody > can think of anything it would actually hurt. I disagree with that assertion; it's taking out a general possibility in /bin/sh and /bin/csh, while gaining *nothing* in real security. It's the same kind of reasoning that makes Solaris disallow ptrace() on other than child processes (or so says the manpage), and that, if pushed farther, turns Unix into VMS. Real security problems should be fixed; things that make it "a little harder" (read, take 10 seconds more) to break security, without changing at all whether it's possible or not, should stay on the lax side. Roger -- e-mail: roger.espel.llima@ens.fr WWW page & PGP key: http://www.eleves.ens.fr:8080/home/espel/index.html From owner-freebsd-hackers Mon Feb 24 12:08:04 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id MAA13149 for hackers-outgoing; Mon, 24 Feb 1997 12:08:04 -0800 (PST) Received: from os.inf.tu-dresden.de (os.inf.tu-dresden.de [141.76.1.46]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id MAA13120 for ; Mon, 24 Feb 1997 12:07:59 -0800 (PST) Received: (from hohmuth@localhost) by os.inf.tu-dresden.de (8.8.5/8.8.5) id VAA14480; Mon, 24 Feb 1997 21:07:55 +0100 From: Michael Hohmuth To: hackers@freebsd.org Subject: size of cvs repository; doscmd Date: 24 Feb 1997 21:07:55 +0100 In-Reply-To: Terry Lambert's message of Mon, 24 Feb 1997 10:28:40 -0700 (MST) Message-ID: <7su3n2t1b8.fsf@os.inf.tu-dresden.de> Lines: 14 X-Mailer: Gnus v5.3/Emacs 19.34 Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi there! I'm interested in doing some kernel hacking. I noticed that CVSup in checkout mode will happily overwrite files I had changed, so I'm now considering mirroring the whole CVS repository. Can anyone tell me the disk space required for the "sys" CVS subtree (and the whole CVS tree)? Also (on an unrelated subject), what's the status of Doscmd? Michael -- Email: hohmuth@inf.tu-dresden.de WWW: http://www.inf.tu-dresden.de/~mh1/ From owner-freebsd-hackers Mon Feb 24 12:46:14 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id MAA16674 for hackers-outgoing; Mon, 24 Feb 1997 12:46:14 -0800 (PST) Received: from lightside.com (hamby1.lightside.net [207.67.176.17]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id MAA16240; Mon, 24 Feb 1997 12:38:10 -0800 (PST) Received: by lightside.com (SMI-8.6/SMI-SVR4) id MAA00577; Mon, 24 Feb 1997 12:38:23 -0800 Date: Mon, 24 Feb 1997 12:38:23 -0800 From: jehamby@lightside.com (Jake Hamby) Message-Id: <199702242038.MAA00577@lightside.com> To: abelits@phobos.illtel.denver.co.us, angio@aros.net Subject: Re: disallow setuid root shells? Cc: hackers@freebsd.org, auditors@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-MD5: oUESNdzLuXs5Zh+91tyILQ== Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk [auditors added back to CC: list] > > IMHO adding "anti-setuid" code into shell will help, but that help won't > > worth the effort of typing "setuid(getuid());" and recompiling the shell > > -- it only makes one more step required to get the same result unless the > > system is stripped down until becoming completely useless (but stripped > > down until becoming completely useless system isn't vulnerable to most of > > known security bugs anyway). > > I disagree. It's a small thing, and very easy to get around, but > it would help reduce the number of breakins by people who don't > understand what they're doing aside from running this program-thingy > that someone gave them. > > I freely admit that most of these people will be using widely > published exploit code, and that almost any vigilant sysadmin won't > be vulnerable to them -- but not everybody is anal about keeping their > computer up to date and secure. Forgive me for sounding political, > but if even one or two computers are prevented from having a root > compromise by this, it seems worthwhile - especially since nobody > can think of anything it would actually hurt. My sentiments exactly! I would think that if there was a valid reason for setuid root shells, then a commercial OS like Solaris would probably allow them (since paying customers often would rather have functionality than security!). While of course this will only protect against the lamest of system crackers, there really is no compelling reason NOT to do it, and if only one or two computers are saved by this, it's worthwhile (hmm, that seems to be exactly what you said, isn't it :) -- Jake From owner-freebsd-hackers Mon Feb 24 12:52:31 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id MAA16955 for hackers-outgoing; Mon, 24 Feb 1997 12:52:31 -0800 (PST) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id MAA16950 for ; Mon, 24 Feb 1997 12:52:29 -0800 (PST) Received: from time.cdrom.com (jkh@localhost [127.0.0.1]) by time.cdrom.com (8.8.5/8.6.9) with ESMTP id MAA01493; Mon, 24 Feb 1997 12:52:05 -0800 (PST) To: Dave Andersen cc: Alex Belits , hackers@freebsd.org Subject: Re: disallow setuid root shells? In-reply-to: Your message of "Mon, 24 Feb 1997 11:23:51 MST." <199702241823.LAA27302@fluffy.aros.net> Date: Mon, 24 Feb 1997 12:52:05 -0800 Message-ID: <1489.856817525@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > I freely admit that most of these people will be using widely > published exploit code, and that almost any vigilant sysadmin won't > be vulnerable to them -- but not everybody is anal about keeping their > computer up to date and secure. Forgive me for sounding political, > but if even one or two computers are prevented from having a root > compromise by this, it seems worthwhile - especially since nobody > can think of anything it would actually hurt. I sort of agree, if there's nothing it would break. Most crackers are stupid idiots who go from "cookbook" data which someone more clued-in provided them with. If it fails, they're hosed. Jordan From owner-freebsd-hackers Mon Feb 24 13:04:39 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id NAA17790 for hackers-outgoing; Mon, 24 Feb 1997 13:04:39 -0800 (PST) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id NAA17784 for ; Mon, 24 Feb 1997 13:04:35 -0800 (PST) Received: from time.cdrom.com (jkh@localhost [127.0.0.1]) by time.cdrom.com (8.8.5/8.6.9) with ESMTP id NAA01614; Mon, 24 Feb 1997 13:04:27 -0800 (PST) To: Chris Shenton cc: hackers@FreeBSD.ORG Subject: Re: migrating 2.1.7 -> 2.2: simple or hairy? In-reply-to: Your message of "Mon, 24 Feb 1997 14:16:13 EST." <199702241916.TAA13136@wirehead.it.hq.nasa.gov> Date: Mon, 24 Feb 1997 13:04:27 -0800 Message-ID: <1610.856818267@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > We've got a number of boxes running 2.1.7 and want to migrate to 2.2; > is it easy or hard? It depends on how many short-cuts you try to take. :-) Seriously, until there are better transition tools available which radically compare checksum information and try to tell you exactly what was added and what was deleted twixt the two releases (and that's all part of my next project), the most dependable upgrade path is to back up user files or make sure they're always kept on OS-neutral partitions (so you can simply mount rather than newfs those filesystems next time around - I do this all the time) and do a complete reinstallation. I know it sounds painful, but once you get the procedure down to a science it's really not that bad, and the benefits are that you're *sure* you haven't got old-library pollution or out-of-date /etc files or any of the other 101 weird behavior quirks that an update-by-source (or even update-by-upgrade) machine can exhibit. Look at it as a little extra pain up-front in exchange for avoiding it at later, less convenient times. :-) Jordan > > Ideally I could do: > > mv /usr/src /usr/src.old > cvsup -supfile [whatever's appropriate for 2.2] > cd /usr/src > make world > make install > > In the past, I've had problems trying to do this: libraries became out > of sync and the make, cc, and other failed, leaving me with an > unusable system. > > Also, which cvsup files are appropriate? I've been tracking 'stable', > which gives me 2.1.7. Does 'current' give me 2.2 or 3.0? Which would > be appropriate? > > Any other pointers, like maybe building in a separate /usr/src-new > tree? > > Thanks. > > From owner-freebsd-hackers Mon Feb 24 13:07:32 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id NAA17974 for hackers-outgoing; Mon, 24 Feb 1997 13:07:32 -0800 (PST) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id NAA17768; Mon, 24 Feb 1997 13:04:09 -0800 (PST) Received: from current1.whistle.com (current1.whistle.com [207.76.205.22]) by alpo.whistle.com (8.8.5/8.8.4) with SMTP id KAA17994; Mon, 24 Feb 1997 10:48:29 -0800 (PST) Message-ID: <3311E1FD.167EB0E7@whistle.com> Date: Mon, 24 Feb 1997 10:46:21 -0800 From: Julian Elischer Organization: Whistle Communications X-Mailer: Mozilla 3.0Gold (X11; I; FreeBSD 2.2-CURRENT i386) MIME-Version: 1.0 To: Adrian Chadd CC: Jake Hamby , hackers@freebsd.org, auditors@freebsd.org Subject: Re: disallow setuid root shells? References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Adrian Chadd wrote: > > On Sun, 23 Feb 1997, Jake Hamby wrote: > > access. Under Solaris, I've discovered that none of the standard shells > > will allow a user to gain root privileges through a setuid root shell! > > > > The sh and ksh shells will run, but the user will have their normal > > privileges. Csh (and interestingly enough tcsh) print "Permission denied" > > and exit when run with the setuid bit set. > > > > Since i'm reviewing /bin/sh and /bin/csh, it might make an interesting > addition. Anyone see any use for +s'ed shells ? Anything it can do, sudo > can do (and sudo AFAIK is much smaller, so less code to screw around > with), and I think its a good idea. > > Suggestions ? well the security audit should pick up any new suid files each night, and if they broke root they're not going to have any problem writing something simpler, but I guess the question is: Does it make it more inconvenient for them? does it make it more likely that they will slip up? does is also make it much more inconvenient for OTHER people? (legit users) personally it breaks the principle of least surprise.. forces people to develop other methods and thereby muddies the waters.. It's not a bad I dea but I'd vote against it.. (however I MIGHT think about adding LOGGING of such an event? :) (in the same way that su logs.) > From owner-freebsd-hackers Mon Feb 24 13:10:22 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id NAA18307 for hackers-outgoing; Mon, 24 Feb 1997 13:10:22 -0800 (PST) Received: from mexico.brainstorm.eu.org (root@mexico.brainstorm.fr [193.56.58.253]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id NAA18301 for ; Mon, 24 Feb 1997 13:10:17 -0800 (PST) Received: from brasil.brainstorm.eu.org (brasil.brainstorm.fr [193.56.58.33]) by mexico.brainstorm.eu.org (8.8.4/8.8.4) with ESMTP id WAA05095 for ; Mon, 24 Feb 1997 22:10:06 +0100 Received: (from uucp@localhost) by brasil.brainstorm.eu.org (8.8.4/8.6.12) with UUCP id WAA02754 for hackers@freebsd.org; Mon, 24 Feb 1997 22:09:44 +0100 Received: (from roberto@localhost) by keltia.freenix.fr (8.8.5/keltia-uucp-2.9) id WAA04736; Mon, 24 Feb 1997 22:04:22 +0100 (CET) Message-ID: <19970224220421.WY21164@keltia.freenix.fr> Date: Mon, 24 Feb 1997 22:04:21 +0100 From: roberto@keltia.freenix.fr (Ollivier Robert) To: hackers@freebsd.org Subject: Re: size of cvs repository; doscmd References: <7su3n2t1b8.fsf@os.inf.tu-dresden.de> X-Mailer: Mutt 0.60,1-3,9 Mime-Version: 1.0 X-Operating-System: FreeBSD 3.0-CURRENT ctm#2999 In-Reply-To: <7su3n2t1b8.fsf@os.inf.tu-dresden.de>; from Michael Hohmuth on Feb 24, 1997 21:07:55 +0100 Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk According to Michael Hohmuth: > considering mirroring the whole CVS repository. Can anyone tell me > the disk space required for the "sys" CVS subtree (and the whole CVS > tree)? For CVS/src/sys: 44673 . for CVS itself: Filesystem 1K-blocks Used Avail Capacity Mounted on /dev/sd12h 465391 339083 89077 79% /spare ...and growing of course :-) -- Ollivier ROBERT -=- The daemon is FREE! -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 3.0-CURRENT #39: Sun Feb 2 22:12:44 CET 1997 From owner-freebsd-hackers Mon Feb 24 13:22:19 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id NAA19400 for hackers-outgoing; Mon, 24 Feb 1997 13:22:19 -0800 (PST) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.50]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id NAA19384 for ; Mon, 24 Feb 1997 13:22:08 -0800 (PST) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id OAA25018; Mon, 24 Feb 1997 14:20:08 -0700 From: Terry Lambert Message-Id: <199702242120.OAA25018@phaeton.artisoft.com> Subject: Re: disabling setuid sh/csh To: espel@llaic.univ-bpclermont.fr (Roger Espel Llima) Date: Mon, 24 Feb 1997 14:20:08 -0700 (MST) Cc: hackers@freefall.freebsd.org In-Reply-To: <199702242002.MAA12861@freefall.freebsd.org> from "Roger Espel Llima" at Feb 24, 97 09:02:08 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-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > Real security problems should be fixed; things that make it "a little > harder" (read, take 10 seconds more) to break security, without changing > at all whether it's possible or not, should stay on the lax side. I agree. SUID programs, even shells, are easy to catch with an audit. What's harder is hacked /usr/bin/passwd, /usr/bin/login, /sbin/init, /usr/libexec/telnetd, /usr/libexec/rlogind, etc. with the date set back. I personally built an assimilation bacterium: it hooked its code in place of an executable, and put the executable in data, then tried to "infect" other writeable executables as a background task to extracting the data and running the requested executable. When it got a priviledged account, it hooked passwd, and then started removing itself each time it was run after it saw itself on passwd. Eventually, you have the same system with passwd hacked. The intent of the particular bacterium was to compress executables, but the assimilation mechaism could easily be used for breaching a system. If you were serious, you'd set all suid files to be immutable except in single user mode, and all non-suid executables that run as root from inetd or cron or whatever, etc.. You might even want to attribute files so that the only files that had the "can execute" attribute bit are those which were set that way after close by the linker (which would have to be suid to do the job). If you were paranoid, any command that could ever be even potentially run by root would need to be immutable as well, since it could write a password entry or startup yp to allow remote password exposure... etc.. Better to just burn your whole system onto ROM, I suppose... 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-hackers Mon Feb 24 13:24:07 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id NAA19648 for hackers-outgoing; Mon, 24 Feb 1997 13:24:07 -0800 (PST) Received: from rover.village.org (rover.village.org [204.144.255.49]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id NAA18823; Mon, 24 Feb 1997 13:16:37 -0800 (PST) Received: from rover.village.org [127.0.0.1] by rover.village.org with esmtp (Exim 0.56 #1) id E0vz7kq-00059M-00; Mon, 24 Feb 1997 14:16:12 -0700 To: Julian Elischer Subject: Re: disallow setuid root shells? Cc: Adrian Chadd , Jake Hamby , hackers@freebsd.org, auditors@freebsd.org In-reply-to: Your message of "Mon, 24 Feb 1997 10:46:21 PST." <3311E1FD.167EB0E7@whistle.com> References: <3311E1FD.167EB0E7@whistle.com> Date: Mon, 24 Feb 1997 14:16:12 -0700 From: Warner Losh Message-Id: Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In message <3311E1FD.167EB0E7@whistle.com> Julian Elischer writes: : It's not a bad I dea but I'd vote against it.. : (however I MIGHT think about adding LOGGING of such an event? :) : (in the same way that su logs.) I think that I like this better. There are many people that use a setuid/setgid shell program to allow access to other programs on the system. At least this was true before sudo and friends. Warner From owner-freebsd-hackers Mon Feb 24 13:26:35 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id NAA19836 for hackers-outgoing; Mon, 24 Feb 1997 13:26:35 -0800 (PST) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id NAA19501; Mon, 24 Feb 1997 13:23:25 -0800 (PST) Received: from time.cdrom.com (jkh@localhost [127.0.0.1]) by time.cdrom.com (8.8.5/8.6.9) with ESMTP id NAA01739; Mon, 24 Feb 1997 13:22:52 -0800 (PST) To: Warner Losh cc: Julian Elischer , Adrian Chadd , Jake Hamby , hackers@freebsd.org, auditors@freebsd.org Subject: Re: disallow setuid root shells? In-reply-to: Your message of "Mon, 24 Feb 1997 14:16:12 MST." Date: Mon, 24 Feb 1997 13:22:52 -0800 Message-ID: <1735.856819372@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > I think that I like this better. There are many people that use a > setuid/setgid shell program to allow access to other programs on the > system. At least this was true before sudo and friends. I could also live with this. I have thought a bit more about supporting the exit-on-suid shell hack, and I have to also agree with some of the folks who point out that it really *would* violate POLA and veer dangerously close to just breaking something in support of arbitrary principles rather than good engineering. Feh. This is clearly one of those issues with lots of pros-and-cons on either side. :-) How about if we be conservative and just add logging for now? :-) Jordan From owner-freebsd-hackers Mon Feb 24 13:43:42 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id NAA20875 for hackers-outgoing; Mon, 24 Feb 1997 13:43:42 -0800 (PST) Received: from nic.follonett.no (nic.follonett.no [194.198.43.10]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id NAA20516; Mon, 24 Feb 1997 13:36:51 -0800 (PST) Received: (from uucp@localhost) by nic.follonett.no (8.8.5/8.8.3) with UUCP id WAA20924; Mon, 24 Feb 1997 22:34:10 +0100 (MET) Received: from oo7 (oo7.dimaga.com [192.0.0.65]) by dimaga.com (8.8.5/8.7.2) with SMTP id WAA27429; Mon, 24 Feb 1997 22:36:40 +0100 (MET) Message-Id: <3.0.32.19970224223639.00b243d0@dimaga.com> X-Sender: eivind@dimaga.com X-Mailer: Windows Eudora Pro Version 3.0 (32) Date: Mon, 24 Feb 1997 22:36:40 +0100 To: "Jordan K. Hubbard" From: Eivind Eklund Subject: Re: disallow setuid root shells? Cc: Warner Losh , Julian Elischer , Adrian Chadd , Jake Hamby , hackers@freebsd.org, auditors@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk At 01:22 PM 2/24/97 -0800, Jordan K. Hubbard wrote: >> I think that I like this better. There are many people that use a >> setuid/setgid shell program to allow access to other programs on the >> system. At least this was true before sudo and friends. > >I could also live with this. I have thought a bit more about >supporting the exit-on-suid shell hack, and I have to also agree with >some of the folks who point out that it really *would* violate POLA >and veer dangerously close to just breaking something in support of >arbitrary principles rather than good engineering. Feh. This is >clearly one of those issues with lots of pros-and-cons on either >side. :-) > >How about if we be conservative and just add logging for now? :-) I actually think logging could be much more effective than just exiting - with logging (especially remote logging) you'd actually have a trace of how the intruder got in, and standard exploits would probably still use /bin/sh to give a root shell (they're usually made to demonstrate a point, not to create good intruder tools). Any luser that use a standard exploit will end up in the log file on another host *grin*. I'd really like it to log the remote address for the session if available - nice to have for a later manhunt... Eivind Eklund perhaps@yes.no http://maybe.yes.no/perhaps/ eivind@freebsd.org From owner-freebsd-hackers Mon Feb 24 14:29:54 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id OAA24242 for hackers-outgoing; Mon, 24 Feb 1997 14:29:54 -0800 (PST) Received: from phoenix.its.rpi.edu (dec@phoenix.its.rpi.edu [128.113.161.45]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id OAA24237 for ; Mon, 24 Feb 1997 14:29:51 -0800 (PST) Received: (from dec@localhost) by phoenix.its.rpi.edu (8.8.4/8.8.3) id RAA11252 for hackers@freefall.freebsd.org; Mon, 24 Feb 1997 17:30:15 -0500 (EST) Date: Mon, 24 Feb 1997 17:30:15 -0500 (EST) From: "David E. Cross" Message-Id: <199702242230.RAA11252@phoenix.its.rpi.edu> To: hackers@freefall.freebsd.org Subject: Re: disabling setuid sh/csh Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk I have always wondered about the ability of also storing the MD5 of all the suid files on the system, and merge that in with the nightly security audit. Although the real problem is still that of a compromised security database, I cannot think of a "real" way of protecting against that. -- David Cross ACS Consultant From owner-freebsd-hackers Mon Feb 24 14:31:41 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id OAA24406 for hackers-outgoing; Mon, 24 Feb 1997 14:31:41 -0800 (PST) Received: from cougar.aceonline.com.au (adrian@cougar.aceonline.com.au [203.103.81.36]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id OAA24005; Mon, 24 Feb 1997 14:27:43 -0800 (PST) Received: from localhost (adrian@localhost) by cougar.aceonline.com.au (8.8.4/8.7) with SMTP id GAA10582; Tue, 25 Feb 1997 06:28:22 +0800 Date: Tue, 25 Feb 1997 06:28:21 +0800 (WST) From: Adrian Chadd To: auditors@freebsd.org cc: Julian Elischer , hackers@freebsd.org Subject: Re: disallow setuid root shells? In-Reply-To: <1735.856819372@time.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Mon, 24 Feb 1997, Jordan K. Hubbard wrote: > > I think that I like this better. There are many people that use a > > setuid/setgid shell program to allow access to other programs on the > > system. At least this was true before sudo and friends. > > I could also live with this. I have thought a bit more about > supporting the exit-on-suid shell hack, and I have to also agree with > some of the folks who point out that it really *would* violate POLA > and veer dangerously close to just breaking something in support of > arbitrary principles rather than good engineering. Feh. This is > clearly one of those issues with lots of pros-and-cons on either > side. :-) > > How about if we be conservative and just add logging for now? :-) > Yep.. that sounds good :) I thought of the writing-code-to-exec-something, and came up with a mini shell in a few minutes to do it with (but it was late and I have uni :) Yes, I like the idea of logging, but then its done isn't it? And yes, quite a hell of a lot of "hackers" nowdays are people learning to do it, and running your "packaged" exploits. Of course its not going to work for "smart" hackers (eg ones that hang around these lists) but its just one of those nice things we can do and it makes their job just that TAD bit harder. :) My idea now stands at logging AND failing (silently), so the non-thinking hacker would have a greater chance of being picked up. Post thoughts, feelings, etc, and when I get home this evening I'll do what the group feels is right. :) > Jordan > Adrian. Btw - I use sudo a lot - and I've never seen the need for an suid shell script. Does anyone here? (besides maybe adduser, which is done in perl, and perl has inbuilt ways to stop people misusing this) From owner-freebsd-hackers Mon Feb 24 14:36:05 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id OAA24721 for hackers-outgoing; Mon, 24 Feb 1997 14:36:05 -0800 (PST) Received: from biohazard.csc.ncsu.edu (biohazard.csc.ncsu.edu [152.1.57.31]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id OAA24353; Mon, 24 Feb 1997 14:30:52 -0800 (PST) Received: by biohazard.csc.ncsu.edu (5.65/Eos/C-U-09Sep93) id AA03727; Mon, 24 Feb 1997 17:29:54 -0500 Message-Id: <9702242229.AA03727@biohazard.csc.ncsu.edu> Subject: Re: disallow setuid root shells? To: julian@whistle.com (Julian Elischer) Date: Mon, 24 Feb 1997 17:29:54 -0500 (EST) Cc: adrian@obiwan.aceonline.com.au, jehamby@lightside.com, hackers@freebsd.org, auditors@freebsd.org In-Reply-To: <3311E1FD.167EB0E7@whistle.com> from "Julian Elischer" at Feb 24, 97 10:46:21 am Reply-To: nate@ncsu.edu From: nate@ncsu.edu (Nate Johnson) X-Mailer: ELM [version 2.4 PL24/POP] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk %well the security audit should pick up any new suid files each night, Except the case where the hacker truly knows what they're doing, in which case, the security audit will be worthless. root can modify any files he wants, including the database used to compare suid files against. =( nsj -- Nate Johnson / nate@ncsu.edu / nsj@catt.ncsu.edu / nsj@FreeBSD.org Head Systems Administrator, Computer and Technologies Theme Program North Carolina State University, Raleigh, North Carolina From owner-freebsd-hackers Mon Feb 24 14:48:53 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id OAA25469 for hackers-outgoing; Mon, 24 Feb 1997 14:48:53 -0800 (PST) Received: from cougar.aceonline.com.au (adrian@cougar.aceonline.com.au [203.103.81.36]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id OAA25210; Mon, 24 Feb 1997 14:43:29 -0800 (PST) Received: from localhost (adrian@localhost) by cougar.aceonline.com.au (8.8.4/8.7) with SMTP id GAA11554; Tue, 25 Feb 1997 06:43:34 +0800 Date: Tue, 25 Feb 1997 06:43:34 +0800 (WST) From: Adrian Chadd To: Nate Johnson cc: Julian Elischer , jehamby@lightside.com, hackers@freebsd.org, auditors@freebsd.org Subject: Re: disallow setuid root shells? In-Reply-To: <9702242229.AA03727@biohazard.csc.ncsu.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Mon, 24 Feb 1997, Nate Johnson wrote: > %well the security audit should pick up any new suid files each night, > > Except the case where the hacker truly knows what they're doing, in which > case, the security audit will be worthless. root can modify any files he > wants, including the database used to compare suid files against. =( > An extension of what I said before - what about logging ALL setuid programs? And not in the program source (of course), but in the kernel? Tis just an idea. Btw - yes I know adduser isn't suid, sorry, I just woke up .. now I've had my coffee things are clearer. :) Adrian Chadd From owner-freebsd-hackers Mon Feb 24 14:52:18 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id OAA25705 for hackers-outgoing; Mon, 24 Feb 1997 14:52:18 -0800 (PST) Received: from cougar.aceonline.com.au (adrian@cougar.aceonline.com.au [203.103.81.36]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id OAA24572; Mon, 24 Feb 1997 14:33:02 -0800 (PST) Received: from localhost (adrian@localhost) by cougar.aceonline.com.au (8.8.4/8.7) with SMTP id GAA10912; Tue, 25 Feb 1997 06:33:48 +0800 Date: Tue, 25 Feb 1997 06:33:48 +0800 (WST) From: Adrian Chadd To: auditors@freebsd.org cc: hackers@freebsd.org Subject: Re: disallow setuid root shells? In-Reply-To: <3.0.32.19970224223639.00b243d0@dimaga.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Mon, 24 Feb 1997, Eivind Eklund wrote: > I actually think logging could be much more effective than just exiting - > with logging (especially remote logging) you'd actually have a trace of how > the intruder got in, and standard exploits would probably still use /bin/sh > to give a root shell (they're usually made to demonstrate a point, not to > create good intruder tools). Any luser that use a standard exploit will > end up in the log file on another host *grin*. > Heheh.. yep. > I'd really like it to log the remote address for the session if available - > nice to have for a later manhunt... > Use syslog() ? Since it supports the remote logging, there isn't much point in using anything else. Adrian Chadd From owner-freebsd-hackers Mon Feb 24 14:57:40 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id OAA25949 for hackers-outgoing; Mon, 24 Feb 1997 14:57:40 -0800 (PST) Received: from phoenix.its.rpi.edu (dec@phoenix.its.rpi.edu [128.113.161.45]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id OAA25944 for ; Mon, 24 Feb 1997 14:57:38 -0800 (PST) Received: (from dec@localhost) by phoenix.its.rpi.edu (8.8.4/8.8.3) id RAA11686 for hackers@freebsd.org; Mon, 24 Feb 1997 17:57:30 -0500 (EST) Date: Mon, 24 Feb 1997 17:57:30 -0500 (EST) From: "David E. Cross" Message-Id: <199702242257.RAA11686@phoenix.its.rpi.edu> To: hackers@freebsd.org Subject: Re: disallow setuid root shells? Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > How about if we be conservative and just add logging for now? :-) As long as it does not push back 2.2 ;) David Cross ACS Consultant From owner-freebsd-hackers Mon Feb 24 15:04:54 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id PAA26374 for hackers-outgoing; Mon, 24 Feb 1997 15:04:54 -0800 (PST) Received: from anacreon.sol.net (anacreon.sol.net [206.55.64.116]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id PAA26368 for ; Mon, 24 Feb 1997 15:04:50 -0800 (PST) Received: from solaria.sol.net (solaria.sol.net [206.55.65.75]) by anacreon.sol.net (8.8.5/8.6.12) with SMTP id RAA07256 for ; Mon, 24 Feb 1997 17:04:42 -0600 (CST) Received: from localhost by solaria.sol.net (8.5/8.5) id RAA24792; Mon, 24 Feb 1997 17:04:39 -0600 From: Joe Greco Message-Id: <199702242304.RAA24792@solaria.sol.net> Subject: Wow. To: hackers@freebsd.org Date: Mon, 24 Feb 97 17:04:37 CST X-Mailer: ELM [version 2.4dev PL65] MIME-Version: 1.0 Content-Type: text Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I just noticed... 5:03PM up 201 days, 1:46, 1 user, load averages: 0.05, 0.02, 0.01 Let's hear it for FreeBSD :-) ... Joe ------------------------------------------------------------------------------- Joe Greco - Systems Administrator jgreco@ns.sol.net Solaria Public Access UNIX - Milwaukee, WI 414/342-4847 From owner-freebsd-hackers Mon Feb 24 15:05:36 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id PAA26446 for hackers-outgoing; Mon, 24 Feb 1997 15:05:36 -0800 (PST) Received: from relay.nuxi.com (nuxi.ucdavis.edu [128.120.37.176]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id OAA25648; Mon, 24 Feb 1997 14:51:39 -0800 (PST) Received: from dragon.nuxi.com (reqd-087.ucdavis.edu [128.120.251.207]) by relay.nuxi.com (8.8.4/8.6.12) with ESMTP id OAA28811; Mon, 24 Feb 1997 14:53:25 -0800 (PST) Received: (from obrien@localhost) by dragon.nuxi.com (8.8.5/8.7.3) id WAA27013; Mon, 24 Feb 1997 22:51:34 GMT Message-ID: <19970224145134.KZ55495@dragon.nuxi.com> Date: Mon, 24 Feb 1997 14:51:34 -0800 From: obrien@NUXI.com (David O'Brien) To: jehamby@lightside.com (Jake Hamby) Cc: hackers@freebsd.org, auditors@freebsd.org Subject: Re: disallow setuid root shells? References: <199702242038.MAA00577@lightside.com> X-Mailer: Mutt 0.60_p2-3,5,8-9 Mime-Version: 1.0 X-Disclaimer: Mutt Bites! Organization: The NUXI *BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 In-Reply-To: <199702242038.MAA00577@lightside.com>; from Jake Hamby on Feb 24, 1997 12:38:23 -0800 Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Jake Hamby writes: > > My sentiments exactly! I would think that if there was a valid reason > for setuid root shells, then a commercial OS like Solaris would > probably allow them (since paying customers often would rather have > functionality than security!). Solaris *DOES* allow them: >From ``man sh'' on Solaris 2.5: -p If the -p flag is present, the shell will not set the effective user and group IDs to the real user and group IDs. So you just need to envoke a suid0 shell by ``sh -p''. Solaris's ksh does not have this restriction. foo:/tmp> ll *sh -r-sr-xr-x 1 root bin 159796 Oct 25 1995 csh* -r-sr-xr-x 1 root bin 180856 Oct 25 1995 ksh* -r-sr-xr-x 1 root root 87012 Oct 25 1995 sh* foo:/tmp> id uid=1765(obrien) gid=10(staff) foo:/tmp> ./sh $ id uid=1765(obrien) gid=10(staff) $ exit foo:/tmp> ./sh -p # id uid=1765(obrien) gid=10(staff) euid=0(root) # exit foo:/tmp> ./ksh # id uid=1765(obrien) gid=10(staff) euid=0(root) # exit foo:/tmp> ./csh csh: Permission denied > While of course this will only protect against the lamest of system crackers, > there really is no compelling reason NOT to do it, You are changing from what is expected under Unix. Solaris did this with requireing the ``-p'' option. Before people bothered to RTFM, many thought they were no longer vulnerable to suid0 sh shells. And then the truth was found.... -- -- David (obrien@NUXI.com -or- obrien@FreeBSD.org) From owner-freebsd-hackers Mon Feb 24 15:21:32 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id PAA27650 for hackers-outgoing; Mon, 24 Feb 1997 15:21:32 -0800 (PST) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id PAA27645 for ; Mon, 24 Feb 1997 15:21:25 -0800 (PST) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id AAA05842; Tue, 25 Feb 1997 00:21:10 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.8.5/8.8.5) id WAA01295; Mon, 24 Feb 1997 22:18:40 +0100 (MET) Message-ID: Date: Mon, 24 Feb 1997 22:18:40 +0100 From: j@uriah.heep.sax.de (J Wunsch) To: hackers@FreeBSD.org Cc: mcgovern@spoon.beta.com (Brian J. McGovern), pc012@seqeb.gov.au (patrick collins) Subject: Re: Driver question on interval execution (polling?) References: <199702240127.UAA04260@spoon.beta.com> <331106DC.2781E494@whistle.com> X-Mailer: Mutt 0.55-PL10 Mime-Version: 1.0 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <331106DC.2781E494@whistle.com>; from Julian Elischer on Feb 23, 1997 19:11:24 -0800 Sender: owner-hackers@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk As Julian Elischer wrote: > the calls you want are > timeout(9) > untimeout(9) > tsleep(9) > and wakeup(9) > not all have man pages yet This time you err, Julian. :-) All of them have man pages already. OTOH, if your card design is not yet finalized, you might add a timer of your own onto the card, and have it raising an interrupt to your driver. That's probably more efficient than the rather high overhead of the timer queue. -- 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-hackers Mon Feb 24 15:22:25 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id PAA27722 for hackers-outgoing; Mon, 24 Feb 1997 15:22:25 -0800 (PST) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id PAA27703 for ; Mon, 24 Feb 1997 15:22:06 -0800 (PST) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id AAA05866 for hackers@freebsd.org; Tue, 25 Feb 1997 00:21:55 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.8.5/8.8.5) id WAA01316; Mon, 24 Feb 1997 22:21:09 +0100 (MET) Message-ID: Date: Mon, 24 Feb 1997 22:21:09 +0100 From: j@uriah.heep.sax.de (J Wunsch) To: hackers@freebsd.org Subject: Re: best way to back up? References: <199702240228.VAA03134@phoenix.its.rpi.edu> <199702240315.VAA02748@Jupiter.Mcs.Net> X-Mailer: Mutt 0.55-PL10 Mime-Version: 1.0 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199702240315.VAA02748@Jupiter.Mcs.Net>; from Karl Denninger on Feb 23, 1997 21:15:02 -0600 Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk As Karl Denninger wrote: > Go to the no-rewind device, and set the tape "size" to a rediculously large > number so it never runs out (unless it really does get an "end of media"). Btw., Karl, you're running -current? Then the `a' option to dump(8) is for you. I finally got tired of the need to pretend an overly long tape. I've also merged it into 2.2 today. -- 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-hackers Mon Feb 24 15:23:19 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id PAA27817 for hackers-outgoing; Mon, 24 Feb 1997 15:23:19 -0800 (PST) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id PAA27812 for ; Mon, 24 Feb 1997 15:23:12 -0800 (PST) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id AAA05884 for hackers@FreeBSD.ORG; Tue, 25 Feb 1997 00:22:35 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.8.5/8.8.5) id XAA01523; Mon, 24 Feb 1997 23:33:48 +0100 (MET) Message-ID: Date: Mon, 24 Feb 1997 23:33:47 +0100 From: j@uriah.heep.sax.de (J Wunsch) To: hackers@FreeBSD.ORG Subject: Re: Install to second hard-drive... References: <199702231204.MAA14310@awfulhak.demon.co.uk> <19970224082923.62035@ct.picker.com> X-Mailer: Mutt 0.55-PL10 Mime-Version: 1.0 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <19970224082923.62035@ct.picker.com>; from Randall Hopper on Feb 24, 1997 08:29:23 -0500 Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk As Randall Hopper wrote: > Booteasy handled multiple disks OK on my box. Yes, it does, but only as long as ``multiple == 2''. UTSL... -- 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-hackers Mon Feb 24 15:23:28 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id PAA27847 for hackers-outgoing; Mon, 24 Feb 1997 15:23:28 -0800 (PST) Received: from plains.nodak.edu (tinguely@plains.NoDak.edu [134.129.111.64]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id PAA27837 for ; Mon, 24 Feb 1997 15:23:24 -0800 (PST) Received: (from tinguely@localhost) by plains.nodak.edu (8.8.4/8.8.3) id RAA25492; Mon, 24 Feb 1997 17:15:39 -0600 (CST) Date: Mon, 24 Feb 1997 17:15:39 -0600 (CST) From: Mark Tinguely Message-Id: <199702242315.RAA25492@plains.nodak.edu> To: cshenton@it.hq.nasa.gov, jkh@time.cdrom.com Subject: Re: migrating 2.1.7 -> 2.2: simple or hairy? Cc: hackers@freebsd.org Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > I know it sounds painful, but once you get the procedure down to a > science it's really not that bad, and the benefits are that you're > *sure* you haven't got old-library pollution or out-of-date /etc files > or any of the other 101 weird behavior quirks that an update-by-source > (or even update-by-upgrade) machine can exhibit. Look at it as a > little extra pain up-front in exchange for avoiding it at later, less > convenient times. :-) I move the /etc and /var directories, install, and then diff the two etc directories so I know what custom things I added in etc and are needed to be added into the new etc directory. I keep var because I want the cron tabs, logs and printer spools (and know that nothing happens to mail). A quick diff the /var will pick up new files (like /var/log/slip.log a couple releases ago). one way to remove old libraries after installing the compat libraries: # cd /usr/lib/compat for i in * do rm ../$i done After the looping rm, it is wise to to do a "ls -lt /usr/lib". This will flag any really, really old library that maybe needs updating or got moved to another directory. --mark. From owner-freebsd-hackers Mon Feb 24 15:25:02 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id PAA28094 for hackers-outgoing; Mon, 24 Feb 1997 15:25:02 -0800 (PST) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id PAA28079 for ; Mon, 24 Feb 1997 15:24:56 -0800 (PST) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id AAA05946 for hackers@freebsd.org; Tue, 25 Feb 1997 00:24:47 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.8.5/8.8.5) id XAA01490; Mon, 24 Feb 1997 23:21:02 +0100 (MET) Message-ID: Date: Mon, 24 Feb 1997 23:21:02 +0100 From: j@uriah.heep.sax.de (J Wunsch) To: hackers@freebsd.org Subject: Re: Alternatives to SYSV IPC? References: <3311084E.794BDF32@whistle.com> <199702240814.AAA07697@freefall.freebsd.org> X-Mailer: Mutt 0.55-PL10 Mime-Version: 1.0 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199702240814.AAA07697@freefall.freebsd.org>; from Darren Reed on Feb 24, 1997 19:14:16 +1100 Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk As Darren Reed wrote: > > how come no-one uses AF_LOCAL with SOCK_DGRAM? > > how portable is AF_LOCAL ? I think it's the posixized expression that avoids the U-word. It's very portable. :-) #ifndef AF_LOCAL # define AF_LOCAL AF_UNIX #endif -- 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-hackers Mon Feb 24 15:25:26 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id PAA28143 for hackers-outgoing; Mon, 24 Feb 1997 15:25:26 -0800 (PST) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id PAA28132 for ; Mon, 24 Feb 1997 15:25:23 -0800 (PST) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id AAA05953 for hackers@FreeBSD.ORG; Tue, 25 Feb 1997 00:25:01 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.8.5/8.8.5) id WAA01421; Mon, 24 Feb 1997 22:52:15 +0100 (MET) Message-ID: Date: Mon, 24 Feb 1997 22:52:15 +0100 From: j@uriah.heep.sax.de (J Wunsch) To: hackers@FreeBSD.ORG Subject: Re: disallow setuid root shells? References: <199702240549.VAA01306@lightside.com> X-Mailer: Mutt 0.55-PL10 Mime-Version: 1.0 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199702240549.VAA01306@lightside.com>; from Jake Hamby on Feb 23, 1997 21:49:08 -0800 Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk As Jake Hamby wrote: > access. Under Solaris, I've discovered that none of the standard shells > will allow a user to gain root privileges through a setuid root shell! You must have a very weird version of Solaris: sunny% uname -sr SunOS 5.5.1 sunny% ls -l ksh -rwsr-xr-x 1 root other 180816 Feb 24 22:24 ksh sunny% ./ksh # id uid=107(j) gid=2000(netra) euid=0(root) # exit Note also the handling of the -p flag in the Korn shell (and also in our /bin/sh). It is in effect if the shell detects UID != EUID, and resetting it causes a `setuid(getuid())'. Same in our /bin/sh. > Comments? Objected. It won't help very much. I've been working in the past with systems that did it, and thinking about possible ways to defeat this measure didn't take longer than 30 seconds. (For example, make a copy of `vi' setuid, and use its feature to spawn a shell from there.) > While we're on the topic, I've always wondered about Perl 5's configure > messages about "secure setuid scripts". What exactly makes an OS capable of > hosting "secure" Perl or shell scripts, It does a fair amount of `taint checks' against various programmer errors. I think setuid perl scripts are very often much more secure than quickly hacked setuid C wrappers. Perl's taint checks aren't something added afterwards, but they are inherent in all operations it does, and the `tainted' flag is inherited with any variable whose contents is derived from command-line arguments, user input, or envioronment variables. It usually remembers this taintedness much longer than any programmer, passing those strings innocently and unchecked across three levels of subroutines... A few examples: uriah # cat > foo.pl #!/usr/bin/suidperl system("ls"); ^D uriah # ls -l foo.pl -rwsr-xr-x 1 j bin - 35 Feb 24 22:34 foo.pl* uriah # ./foo.pl Insecure PATH at ./foo.pl line 3. No $PATH has been set yet, thus all external commands are prohibited. uriah # cat > foo.pl #!/usr/bin/suidperl $ENV{'PATH'} = "/bin:/usr/bin"; system("ls"); ^D uriah # ./foo.pl #mutta01041# gated ... Now it works. uriah # cat > foo.pl #!/usr/bin/suidperl $ENV{'PATH'} = "/bin:/usr/bin"; open(FOO, ">$ENV{'TERM'}") || die "Cannot open $ENV{'TERM'}.\n"; ^D uriah # ./foo.pl Insecure dependency in open at ./foo.pl line 5. The filename about to be created would have been dependant of the environment. Forbidden. uriah # cat > foo.pl #!/usr/bin/suidperl $ENV{'PATH'} = "/bin:/usr/bin"; $mumble = $ENV{'TERM'}; system "echo $mumble"; ^D uriah # ./foo.pl Insecure dependency in system at ./foo.pl line 6. This system() call might contain shell metacharacters, hence it would actually result in calling /bin/sh, with a `tainted' value. Forbidden. uriah # cat > foo.pl #!/usr/bin/suidperl $ENV{'PATH'} = "/bin:/usr/bin"; $mumble = $ENV{'TERM'}; system "echo", $mumble; ^D uriah # ./foo.pl xterm Now it's allowd. The explicit splitting of the arguments to system() causes it to not use /bin/sh at all. There are quite more of these examples. > and what does this have to do with > the /dev/fd directory (that Perl searches for)? No idea offhand. Our suidperl doesn't seem to be dependant of /dev/fd, but other incarnations might use it. In particular, i think if you compile perl to autodetect the suidness, and automatically invoke suidperl (our compilation doesn't do this), it might use /dev/fd to pass the script down to the taintcheck compiler or such. -- 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-hackers Mon Feb 24 15:25:54 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id PAA28215 for hackers-outgoing; Mon, 24 Feb 1997 15:25:54 -0800 (PST) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id PAA28192 for ; Mon, 24 Feb 1997 15:25:41 -0800 (PST) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id AAA05960 for hackers@freebsd.org; Tue, 25 Feb 1997 00:25:33 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.8.5/8.8.5) id WAA01433; Mon, 24 Feb 1997 22:55:08 +0100 (MET) Message-ID: Date: Mon, 24 Feb 1997 22:55:08 +0100 From: j@uriah.heep.sax.de (J Wunsch) To: hackers@freebsd.org Subject: Re: disallow setuid root shells? References: <199702240549.VAA01306@lightside.com> X-Mailer: Mutt 0.55-PL10 Mime-Version: 1.0 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: ; from Adrian Chadd on Jan 8, 1996 04:35:15 +0800 Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk As Adrian Chadd wrote: > From what I remember, perl has a > c-wrapper that it runs before running a setuid shell script that fixes up > the environment and other nice things, then runs the script. No, that's not just a C-wrapper. See my other posting. > By default, > if you use the setuid copy of perl as a script interpreter > (#!/usr/bin/sperl) and it detects that the script IS setuid root, it will > run it. That's an option, but not FreeBSD's default. On FreeBSD, you need to explicitly mention suidperl in the #! line. > If not, it won't run the script as root. I simply disable it on my > systems. ...and use hand-written setuid C programs instead? :-) I bet there are more security problems in them than in all setuid Perl scripts on the world. :-) -- 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-hackers Mon Feb 24 15:26:13 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id PAA28281 for hackers-outgoing; Mon, 24 Feb 1997 15:26:13 -0800 (PST) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id PAA28270 for ; Mon, 24 Feb 1997 15:26:10 -0800 (PST) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id AAA05962 for hackers@FreeBSD.ORG; Tue, 25 Feb 1997 00:25:53 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.8.5/8.8.5) id XAA01448; Mon, 24 Feb 1997 23:04:13 +0100 (MET) Message-ID: Date: Mon, 24 Feb 1997 23:04:12 +0100 From: j@uriah.heep.sax.de (J Wunsch) To: hackers@FreeBSD.ORG Subject: Re: Recurring freeze with 2.1.5 system References: <199702240555.VAA01312@lightside.com> X-Mailer: Mutt 0.55-PL10 Mime-Version: 1.0 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199702240555.VAA01312@lightside.com>; from Jake Hamby on Feb 23, 1997 21:55:23 -0800 Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk As Jake Hamby wrote: > There's a 486 system at my Internet provider that he's set up as a "geek > box" for people to hack on. It's a fairly lame configuration (486DX/4 > 100MHz, 8MB RAM, IDE drives, NE2000 card). Anyway, it has a recurring > problem where it will only answer pings. Logins, either remote or from the > console, will hang (telnet will connect, but not prompt for username), and > the system must be forcibly rebooted. Configure DDB, and see if it reacts to the DDB hotkey. I would assume this, since interrupts are obviously working. Inside DDB, you even have a `ps' command you could use to examine the process status. If you're using a serial console, don't forget the option BREAK_TO_DEBUGGER. You can then use a BREAK condition on the serial line as the DDB hotkey. (BREAK is an out-of-band signal, you can generate it in Kermit by ^\B, or in cu by ~b.) -- 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-hackers Mon Feb 24 15:26:21 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id PAA28319 for hackers-outgoing; Mon, 24 Feb 1997 15:26:21 -0800 (PST) Received: from hemi.com (hemi.com [204.132.158.10]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id PAA28296 for ; Mon, 24 Feb 1997 15:26:15 -0800 (PST) Received: (from mbarkah@localhost) by hemi.com (8.8.5/8.7.3) id QAA12075; Mon, 24 Feb 1997 16:25:31 -0700 (MST) From: Ade Barkah Message-Id: <199702242325.QAA12075@hemi.com> Subject: Re: disallow setuid root shells? To: angio@aros.net (Dave Andersen) Date: Mon, 24 Feb 1997 16:25:30 -0700 (MST) Cc: abelits@phobos.illtel.denver.co.us, hackers@freebsd.org In-Reply-To: <199702241823.LAA27302@fluffy.aros.net> from Dave Andersen at "Feb 24, 97 11:23:51 am" X-Mailer: ELM [version 2.4ME+ PL22 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Dave wrote: > > IMHO adding "anti-setuid" code into shell will help, but that > > help won't worth the effort of typing "setuid(getuid());" ... > > I disagree. It's a small thing, and very easy to get around, but > it would help reduce the number of breakins by people who don't > understand what they're doing aside from running this program-thingy > that someone gave them. ... The anti-setuid code will not reduce breakins... by the time they're doing 'chmod u+s sh', they _already_have_ root access. What I'd do is to booby-trap the shells, so if it runs setuid, it _seems_ to run but reaaaalllyyyyy slooooowwww, and notifies me in the meantime. =-) Regards, -Ade ------------------------------------------------------------------- Inet: mbarkah@hemi.com - HEMISPHERE ONLINE - ------------------------------------------------------------------- From owner-freebsd-hackers Mon Feb 24 15:26:22 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id PAA28321 for hackers-outgoing; Mon, 24 Feb 1997 15:26:22 -0800 (PST) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id PAA28301 for ; Mon, 24 Feb 1997 15:26:16 -0800 (PST) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id AAA05971 for hackers@freebsd.org; Tue, 25 Feb 1997 00:26:13 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.8.5/8.8.5) id XAA01535; Mon, 24 Feb 1997 23:38:04 +0100 (MET) Message-ID: Date: Mon, 24 Feb 1997 23:38:04 +0100 From: j@uriah.heep.sax.de (J Wunsch) To: hackers@freebsd.org Subject: Re: installing without booting off floppy. References: <199702241537.HAA24423@freefall.freebsd.org> <199702241652.DAA07869@genesis.atrad.adelaide.edu.au> X-Mailer: Mutt 0.55-PL10 Mime-Version: 1.0 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199702241652.DAA07869@genesis.atrad.adelaide.edu.au>; from Michael Smith on Feb 25, 1997 03:22:13 +1030 Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk As Michael Smith wrote: > > The trick to all of this is being able to run "sysinstall". > > > > Once you've installed a system, this gets deleted...is it worth keeping > > this around, maybe as a way to install further packages ? > > Try looking in /stand someday, or read the MOTD 8) Well, but /stand/sysinstall isn't that great to install a complete system onto a second disk. It does a lot of special-casing when it's being run as PID 1. However, Darren, /stand/sysinstall doesn't do anything overly magic. You might even be able to use its disk editor in standalone mode now, if you don't prefer the spartanic disklabel(8) user interface. The distributions itself are simple split .tar.gz files. Most if not all of the post-installation configuration goes in the new /etc/sysconfig file. -- 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-hackers Mon Feb 24 15:28:52 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id PAA28830 for hackers-outgoing; Mon, 24 Feb 1997 15:28:52 -0800 (PST) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id PAA28777 for ; Mon, 24 Feb 1997 15:28:40 -0800 (PST) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id AAA05993; Tue, 25 Feb 1997 00:27:08 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.8.5/8.8.5) id XAA01566; Mon, 24 Feb 1997 23:46:31 +0100 (MET) Message-ID: Date: Mon, 24 Feb 1997 23:46:31 +0100 From: j@uriah.heep.sax.de (J Wunsch) To: cshenton@it.hq.nasa.gov (Chris Shenton) Cc: hackers@FreeBSD.org Subject: Re: migrating 2.1.7 -> 2.2: simple or hairy? References: <199702241916.TAA13136@wirehead.it.hq.nasa.gov> X-Mailer: Mutt 0.55-PL10 Mime-Version: 1.0 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199702241916.TAA13136@wirehead.it.hq.nasa.gov>; from Chris Shenton on Feb 24, 1997 14:16:13 -0500 Sender: owner-hackers@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk As Chris Shenton wrote: > Ideally I could do: > > mv /usr/src /usr/src.old > cvsup -supfile [whatever's appropriate for 2.2] > cd /usr/src > make world > make install Yes, that should work. > In the past, I've had problems trying to do this: libraries became out > of sync and the make, cc, and other failed, leaving me with an > unusable system. Unusable? I doubt. Probably ``not quite out of the box'', but with a little of hand-fiddling, you should be able to get it into shape. It's sometimes also very helpful to run the first `make world' with the -k flag, so not every single error becomes a show-stopper. > Also, which cvsup files are appropriate? I've been tracking 'stable', > which gives me 2.1.7. Does 'current' give me 2.2 or 3.0? Which would > be appropriate? -current is 3.0-current. I don't think we've got a name for RELENG_2_2 yet, but be assured, it will take over the name `-stable' anytime soon. :) > Any other pointers, like maybe building in a separate /usr/src-new > tree? If at all (and if you've got the diskspace), you can try bootstrapping it into a chrooted tree. That's basically what a `make release' does, but i remember that the hosting and target version shouldn't diverge too much there either, or it will require hand-fiddling. Don't forget your /etc updates... -- 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-hackers Mon Feb 24 15:39:13 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id PAA29922 for hackers-outgoing; Mon, 24 Feb 1997 15:39:13 -0800 (PST) Received: from mail2.pilot.net (mail2.pilot.net [198.232.147.11]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id PAA29913 for ; Mon, 24 Feb 1997 15:39:11 -0800 (PST) Received: from u2.pilot.net (unknown-17-117.pilot.net [204.48.17.117]) by mail2.pilot.net with ESMTP id PAA27848 for ; Mon, 24 Feb 1997 15:39:06 -0800 (PST) Received: from dc3.pilot.net (dc3.pilot.net [204.48.17.11]) by u2.pilot.net (8.8.5/) with ESMTP id PAA04408 for ; Mon, 24 Feb 1997 15:39:05 -0800 (PST) Received: from localhost (wadlow@localhost) by dc3.pilot.net (8.7.3/8.7.3) with SMTP id PAA04735 for ; Mon, 24 Feb 1997 15:39:04 -0800 (PST) X-Authentication-Warning: dc3.pilot.net: wadlow owned process doing -bs Date: Mon, 24 Feb 1997 15:39:04 -0800 (PST) From: Tom Wadlow To: hackers@freebsd.org Subject: Ethernet options on 2.2-GAMMA Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi, I'm trying to install 2.2-GAMMA on a Twinhead 5100 486 laptop. I've got a 3Com Etherlink III 3c589 PCMCIA card in PCMCIA slot 0. I've successfully built a boot floppy, and am attempting to do an FTP-based installation. I'm having two problems installing with this configuration, almost certainly related: - The kernel boot messages place the zp0 (the Etherlink III) device init messages just a few lines before the screen clears to start the initialization. Try as I might, I am not fast enough to read those lines to determine if it is successfully finding the zp0 device in the fraction of a second it is visible. - The Media selection option of the installation program does not list zp0 as an option. It lists the SLIP, PPP and parallel options, but not zp0. There seems to be no way to bypass this, or check directly for the presense of the zp0 device. Any thoughts as to how to proceed? My thought is that a "hit space to continue" option before the installation script starts would be helpful, so you could read the rest of the kernel messages. Is the Etherlink III really supported by the boot floppy (it seems to be in the kernel config screens)? --Tom From owner-freebsd-hackers Mon Feb 24 15:52:21 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id PAA01130 for hackers-outgoing; Mon, 24 Feb 1997 15:52:21 -0800 (PST) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id PAA01123 for ; Mon, 24 Feb 1997 15:52:10 -0800 (PST) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id AAA06485; Tue, 25 Feb 1997 00:51:02 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.8.5/8.8.5) id AAA01981; Tue, 25 Feb 1997 00:48:44 +0100 (MET) Message-ID: Date: Tue, 25 Feb 1997 00:48:44 +0100 From: j@uriah.heep.sax.de (J Wunsch) To: Shimon@i-Connect.Net (Simon Shapiro) Cc: freebsd-hackers@freebsd.org Subject: Re: More fun with 2.2 compiles References: X-Mailer: Mutt 0.55-PL10 Mime-Version: 1.0 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: ; from Simon Shapiro on Feb 17, 1997 14:34:45 -0800 Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk As Simon Shapiro wrote: > ===> gnu/usr.bin/perl/x2p > cc -O -I/usr/src/gnu/usr.bin/perl/x2p/../perl -c a2p.c > In file included from /usr/src/gnu/usr.bin/perl/x2p/a2py.c:34, > from /usr/src/gnu/usr.bin/perl/x2p/a2p.y:409: > /usr/src/gnu/usr.bin/perl/x2p/util.h:54: conflicting types for `setenv' > /usr/include/stdlib.h:118: previous declaration of `setenv' You're not watching your commit messages close enough. :-) Already fixed. > cd /usr/src/gnu/usr.bin/perl/x2p > cvs co -r RELENG_2_2 util.h > > And Got: > > cvs checkout: cannot find module `util.h' - ignored cvs update -r RELENG_2_2 util.h For cvs checkout, you can only either specify module names, or full path names in the repository. Both is not what you want here (although you could use the full path together with ``-d .'') -- 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-hackers Mon Feb 24 16:26:36 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id QAA03070 for hackers-outgoing; Mon, 24 Feb 1997 16:26:36 -0800 (PST) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id QAA02875; Mon, 24 Feb 1997 16:23:12 -0800 (PST) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id BAA07391; Tue, 25 Feb 1997 01:22:50 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.8.5/8.8.5) id AAA02010; Tue, 25 Feb 1997 00:51:46 +0100 (MET) Message-ID: Date: Tue, 25 Feb 1997 00:51:45 +0100 From: j@uriah.heep.sax.de (J Wunsch) To: jehamby@lightside.com (Jake Hamby) Cc: abelits@phobos.illtel.denver.co.us, angio@aros.net, hackers@freebsd.org, auditors@freebsd.org Subject: Re: disallow setuid root shells? References: <199702242038.MAA00577@lightside.com> X-Mailer: Mutt 0.55-PL10 Mime-Version: 1.0 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199702242038.MAA00577@lightside.com>; from Jake Hamby on Feb 24, 1997 12:38:23 -0800 Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk As Jake Hamby wrote: > My sentiments exactly! I would think that if there was a valid > reason for setuid root shells, then a commercial OS like Solaris > would probably allow them (since paying customers often would rather > have functionality than security!). You think that's the reason why Solaris indeed allows it? :-) -- 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-hackers Mon Feb 24 16:34:40 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id QAA04139 for hackers-outgoing; Mon, 24 Feb 1997 16:34:40 -0800 (PST) Received: from scanner.worldgate.com (scanner.worldgate.com [198.161.84.3]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id QAA03245; Mon, 24 Feb 1997 16:28:47 -0800 (PST) Received: from znep.com (uucp@localhost) by scanner.worldgate.com (8.8.5/8.7.3) with UUCP id RAA14905; Mon, 24 Feb 1997 17:27:50 -0700 (MST) Received: from localhost (marcs@localhost) by alive.znep.com (8.7.5/8.7.3) with SMTP id RAA15259; Mon, 24 Feb 1997 17:20:23 -0700 (MST) Date: Mon, 24 Feb 1997 17:20:23 -0700 (MST) From: Marc Slemko To: Adrian Chadd cc: hackers@freebsd.org, auditors@freebsd.org Subject: Re: disallow setuid root shells? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Tue, 25 Feb 1997, Adrian Chadd wrote: > On Mon, 24 Feb 1997, Nate Johnson wrote: > > > %well the security audit should pick up any new suid files each night, > > > > Except the case where the hacker truly knows what they're doing, in which > > case, the security audit will be worthless. root can modify any files he > > wants, including the database used to compare suid files against. =( > > > > An extension of what I said before - what about logging ALL setuid > programs? And not in the program source (of course), but in the kernel? > Tis just an idea. > > Btw - yes I know adduser isn't suid, sorry, I just woke up .. now I've had > my coffee things are clearer. :) process accounting sortof does that: lastcomm: (after enabling process accounting, of course) passwd -S marcs ttyp1 0.09 secs Mon Feb 24 17:14 The S says used superuser privs. That is only a partial implementation, though, since process accounting logs aren't the nicest to log remotely, they contain a whole lot of other programs, and the S flag is only set if something the process calls suser(); ie. something it calls ends up resulting in suser being called by something. A lot can be done without doing that. Process accounting may be something to start for that type of logging. From owner-freebsd-hackers Mon Feb 24 16:37:11 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id QAA04377 for hackers-outgoing; Mon, 24 Feb 1997 16:37:11 -0800 (PST) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id QAA04372 for ; Mon, 24 Feb 1997 16:37:08 -0800 (PST) Received: from time.cdrom.com (jkh@localhost [127.0.0.1]) by time.cdrom.com (8.8.5/8.6.9) with ESMTP id QAA02606; Mon, 24 Feb 1997 16:35:30 -0800 (PST) To: Joe Greco cc: hackers@freebsd.org Subject: Re: Wow. In-reply-to: Your message of "Mon, 24 Feb 1997 17:04:37 CST." <199702242304.RAA24792@solaria.sol.net> Date: Mon, 24 Feb 1997 16:35:30 -0800 Message-ID: <2602.856830930@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > I just noticed... > > 5:03PM up 201 days, 1:46, 1 user, load averages: 0.05, 0.02, 0.01 > > Let's hear it for FreeBSD :-) Always include uname -a output for a more meaningful statistic. :-) Jordan From owner-freebsd-hackers Mon Feb 24 16:38:21 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id QAA04515 for hackers-outgoing; Mon, 24 Feb 1997 16:38:21 -0800 (PST) Received: from parkplace.cet.co.jp (parkplace.cet.co.jp [202.32.64.1]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id QAA04506 for ; Mon, 24 Feb 1997 16:38:18 -0800 (PST) Received: from localhost (michaelh@localhost) by parkplace.cet.co.jp (8.8.5/CET-v2.1) with SMTP id AAA08557; Tue, 25 Feb 1997 00:38:07 GMT Date: Tue, 25 Feb 1997 09:38:06 +0900 (JST) From: Michael Hancock To: Terry Lambert cc: FreeBSD Hackers Subject: Immutable files, a false sense of security (Re: disabling setuid , sh/csh) In-Reply-To: <199702242120.OAA25018@phaeton.artisoft.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Mon, 24 Feb 1997, Terry Lambert wrote: > If you were serious, you'd set all suid files to be immutable except > in single user mode, and all non-suid executables that run as root > from inetd or cron or whatever, etc.. There's no switch exported to the sys admin as in BSDI, NETBSD, and OPENBSD, so you would need to modify the source to use it. It gives a false sense of security according to few people on this list. Has anyone tried hacking a system in "secure" mode via something like /dev/io? I wonder how much of a speed bump it would present to an attacker. > You might even want to attribute files so that the only files that > had the "can execute" attribute bit are those which were set that > way after close by the linker (which would have to be suid to do > the job). > > If you were paranoid, any command that could ever be even potentially > run by root would need to be immutable as well, since it could write > a password entry or startup yp to allow remote password exposure... etc.. > > Better to just burn your whole system onto ROM, I suppose... Regards, Mike Hancock From owner-freebsd-hackers Mon Feb 24 16:51:37 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id QAA05625 for hackers-outgoing; Mon, 24 Feb 1997 16:51:37 -0800 (PST) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id QAA05617 for ; Mon, 24 Feb 1997 16:51:26 -0800 (PST) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id BAA07849 for hackers@freebsd.org; Tue, 25 Feb 1997 01:51:08 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.8.5/8.8.5) id BAA02171; Tue, 25 Feb 1997 01:23:32 +0100 (MET) Message-ID: Date: Tue, 25 Feb 1997 01:23:31 +0100 From: j@uriah.heep.sax.de (J Wunsch) To: hackers@freebsd.org Subject: Re: disallow setuid root shells? References: <9702242229.AA03727@biohazard.csc.ncsu.edu> X-Mailer: Mutt 0.55-PL10 Mime-Version: 1.0 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: ; from Adrian Chadd on Feb 25, 1997 06:43:34 +0800 Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk As Adrian Chadd wrote: > An extension of what I said before - what about logging ALL setuid > programs? This would make for a cheap disk-filling service, yeah! :-) -- 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-hackers Mon Feb 24 16:52:19 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id QAA05737 for hackers-outgoing; Mon, 24 Feb 1997 16:52:19 -0800 (PST) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id QAA05726 for ; Mon, 24 Feb 1997 16:52:08 -0800 (PST) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id BAA07861 for hackers@freebsd.org; Tue, 25 Feb 1997 01:51:36 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.8.5/8.8.5) id BAA02182; Tue, 25 Feb 1997 01:24:49 +0100 (MET) Message-ID: Date: Tue, 25 Feb 1997 01:24:48 +0100 From: j@uriah.heep.sax.de (J Wunsch) To: hackers@freebsd.org Subject: Re: disallow setuid root shells? References: <3311E1FD.167EB0E7@whistle.com> <9702242229.AA03727@biohazard.csc.ncsu.edu> X-Mailer: Mutt 0.55-PL10 Mime-Version: 1.0 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <9702242229.AA03727@biohazard.csc.ncsu.edu>; from Nate Johnson on Feb 24, 1997 17:29:54 -0500 Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk As Nate Johnson wrote: > Except the case where the hacker truly knows what they're doing, in which > case, the security audit will be worthless. root can modify any files he > wants, including the database used to compare suid files against. =( chflags schg sysctl -q kern.securelevel=1 -- 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-hackers Mon Feb 24 17:23:45 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id RAA07660 for hackers-outgoing; Mon, 24 Feb 1997 17:23:45 -0800 (PST) Received: from vinyl.quickweb.com (vinyl.quickweb.com [206.222.77.8]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id RAA07654 for ; Mon, 24 Feb 1997 17:23:42 -0800 (PST) Received: from localhost (mark@localhost) by vinyl.quickweb.com (8.7.5/8.6.12) with SMTP id UAA06280; Mon, 24 Feb 1997 20:22:44 -0500 (EST) Date: Mon, 24 Feb 1997 20:22:44 -0500 (EST) From: Mark Mayo To: Joerg Wunsch cc: Chris Shenton , hackers@FreeBSD.org Subject: Re: migrating 2.1.7 -> 2.2: simple or hairy? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk On Mon, 24 Feb 1997, J Wunsch wrote: > As Chris Shenton wrote: > > > Ideally I could do: > > > > mv /usr/src /usr/src.old > > cvsup -supfile [whatever's appropriate for 2.2] > > cd /usr/src > > make world > > make install > > Yes, that should work. > [SNIP] > > Don't forget your /etc updates... > Curious.. is /etc/ updated with a "src-all" line in the cvsup file? For example, I use the following cvsup file: *default tag=RELENG_2_2 *default host=cvsup.freebsd.org *default prefix=/usr *default base=/usr *default release=cvs delete use-rel-suffix compress src-all Will this get me the new /etc entries? Also, will these new entries wipout my custom configs (hosts,rc, etc.)? I'm guessing I should maybe make a backup copy of /etc and diff the directories afterwards to see what's changed if that's the case. TIA, -Mark > -- > 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. ;-) > ---------------------------------------------------------------------------- Mark Mayo mark@quickweb.com RingZero Comp. http://vinyl.quickweb.com/mark ---------------------------------------------------------------------------- Nature shows that with the growth of intelligence comes increased capacity for pain, and it is only with the highest degree of intelligence that suffering reaches its supreme point. -- Arthur Schopenhauer From owner-freebsd-hackers Mon Feb 24 17:25:40 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id RAA07746 for hackers-outgoing; Mon, 24 Feb 1997 17:25:40 -0800 (PST) Received: from sasami.jurai.net (root@sasami.jurai.net [207.172.25.144]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id RAA07194; Mon, 24 Feb 1997 17:15:00 -0800 (PST) Received: from localhost (winter@localhost) by sasami.jurai.net (8.8.5/8.8.3) with SMTP id UAA20229; Mon, 24 Feb 1997 20:14:15 -0500 (EST) Date: Mon, 24 Feb 1997 20:14:15 -0500 (EST) From: "Matthew N. Dodd" To: Nate Johnson cc: Julian Elischer , adrian@obiwan.aceonline.com.au, jehamby@lightside.com, hackers@freebsd.org, auditors@freebsd.org Subject: Re: disallow setuid root shells? In-Reply-To: <9702242229.AA03727@biohazard.csc.ncsu.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Mon, 24 Feb 1997, Nate Johnson wrote: > %well the security audit should pick up any new suid files each night, > Except the case where the hacker truly knows what they're doing, in which > case, the security audit will be worthless. root can modify any files he > wants, including the database used to compare suid files against. =( Tripwire suggests storing the file signature database on a hardware protected read only device. Say a SCSI drive with WP on. I'm not that paranoid so running in secure level 1 with the database set schg is good enough for me. Have a good one. /* Matthew N. Dodd | A memory retaining a love you had for life winter@jurai.net | As cruel as it seems nothing ever seems to http://www.jurai.net/~winter | go right - FLA M 3.1:53 */ From owner-freebsd-hackers Mon Feb 24 17:41:50 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id RAA08577 for hackers-outgoing; Mon, 24 Feb 1997 17:41:50 -0800 (PST) Received: from rover.village.org (rover.village.org [204.144.255.49]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id RAA08439; Mon, 24 Feb 1997 17:39:15 -0800 (PST) Received: from rover.village.org [127.0.0.1] by rover.village.org with esmtp (Exim 0.56 #1) id E0vzBqu-0005Sc-00; Mon, 24 Feb 1997 18:38:44 -0700 To: "Matthew N. Dodd" Subject: Re: disallow setuid root shells? Cc: Nate Johnson , Julian Elischer , adrian@obiwan.aceonline.com.au, jehamby@lightside.com, hackers@freebsd.org, auditors@freebsd.org In-reply-to: Your message of "Mon, 24 Feb 1997 20:14:15 EST." References: Date: Mon, 24 Feb 1997 18:38:44 -0700 From: Warner Losh Message-Id: Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In message "Matthew N. Dodd" writes: : On Mon, 24 Feb 1997, Nate Johnson wrote: : > %well the security audit should pick up any new suid files each night, : > Except the case where the hacker truly knows what they're doing, in which : > case, the security audit will be worthless. root can modify any files he : > wants, including the database used to compare suid files against. =( : : Tripwire suggests storing the file signature database on a hardware : protected read only device. Say a SCSI drive with WP on. : : I'm not that paranoid so running in secure level 1 with the database set : schg is good enough for me. Our next router will boot off a floppy drive and will log to another system. The floppy will be write protected. Only console logins will be allowed. We'll likely run at security level 2 once we come up, if the dynamic interfaces we have on the router will allow that. Warner From owner-freebsd-hackers Mon Feb 24 17:47:32 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id RAA08860 for hackers-outgoing; Mon, 24 Feb 1997 17:47:32 -0800 (PST) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id RAA08855 for ; Mon, 24 Feb 1997 17:47:29 -0800 (PST) Received: from time.cdrom.com (jkh@localhost [127.0.0.1]) by time.cdrom.com (8.8.5/8.6.9) with ESMTP id RAA04221; Mon, 24 Feb 1997 17:43:52 -0800 (PST) To: Tom Wadlow cc: hackers@freebsd.org Subject: Re: Ethernet options on 2.2-GAMMA In-reply-to: Your message of "Mon, 24 Feb 1997 15:39:04 PST." Date: Mon, 24 Feb 1997 17:43:52 -0800 Message-ID: <4217.856835032@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > - The kernel boot messages place the zp0 (the Etherlink III) > device init messages just a few lines before the screen clears > to start the initialization. Try as I might, I am not fast enough > to read those lines to determine if it is successfully finding the > zp0 device in the fraction of a second it is visible. jkh points emphatically at the scroll-lock key and the "Usage" item in the very first sysinstall menu which documents its usage. :-) > - The Media selection option of the installation program does > not list zp0 as an option. It lists the SLIP, PPP and parallel > options, but not zp0. There seems to be no way to bypass this, > or check directly for the presense of the zp0 device. Then it didn't probe it - you can be fairly assured of that. > Any thoughts as to how to proceed? My thought is that a "hit space to Install over a SLIP or PLIP connection? Try a different PCCARD adaptor? :-) You might also try the PAO floppy - It's available from Tatsumi Hosokawa's home page (I don't have an exact URL, but it's an easy net search target) and has better support for PCCARD devices in general. Jordan From owner-freebsd-hackers Mon Feb 24 17:47:59 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id RAA08913 for hackers-outgoing; Mon, 24 Feb 1997 17:47:59 -0800 (PST) Received: from helbig.informatik.ba-stuttgart.de (helbig.informatik.ba-stuttgart.de [141.31.166.22]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id RAA08882; Mon, 24 Feb 1997 17:47:43 -0800 (PST) Received: (from helbig@localhost) by helbig.informatik.ba-stuttgart.de (8.8.5/8.8.5) id CAA00172; Tue, 25 Feb 1997 02:47:35 +0100 (MET) From: Wolfgang Helbig Message-Id: <199702250147.CAA00172@helbig.informatik.ba-stuttgart.de> Subject: Re: CMD640b workaround - final(?) version In-Reply-To: <19970213004131.DV50639@x14.mi.uni-koeln.de> from Stefan Esser at "Feb 13, 97 00:41:31 am" To: se@freebsd.org (Stefan Esser) Date: Tue, 25 Feb 1997 02:47:34 +0100 (MET) Cc: hackers@freebsd.org X-Mailer: ELM [version 2.4ME+ PL30 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi Stefan, I changed the code as you suggested. Now pci.c is clean again. I added a new source pci/wdc_p.c. It is telling wd.c, which pci-devices are probed, so wd.c can adapt to different devices. Up to now only to CMD640b. If there are other IDE-PCI-Chips that need special treatment, they can be easily detected in wd.c now and treated accordingly. I had to add a line in conf/files: pci/wdc_p.c optional wdc device-driver For review, I include the source of wdc_p.c. If you think it's okay now, I will post a diff-file for wd.c, so kern/2305 can be closed. Here is the source of /sys/pci/wdc_p.c /* * * Copyright (c) 1996 Wolfgang Helbig * All rights reserved. * * Redistribution and use in source and binary forms, with or without * modification, are permitted provided that the following conditions * are met: * 1. Redistributions of source code must retain the above copyright * notice immediately at the beginning of the file, without modification, * this list of conditions, and the following disclaimer. * 2. Redistributions in binary form must reproduce the above copyright * notice, this list of conditions and the following disclaimer in the * documentation and/or other materials provided with the distribution. * 3. Absolutely no warranty of function or purpose is made by the author. * 4. Modifications may be freely made to this file if the above conditions * are met. * * $ID$ */ #include "pci.h" #if NPCI > 0 #include #include #include #include #include #include #include "wdc.h" extern char *wdc_pci __P((pcidi_t type)); static char* wdc_pci_probe __P((pcici_t tag, pcidi_t type)); static void wdc_pci_attach __P((pcici_t config_id, int unit)); static u_long wdc_pci_count = 0; static struct pci_device wdc_pci_driver = { "wdc", wdc_pci_probe, wdc_pci_attach, &wdc_pci_count, NULL }; DATA_SET (pcidevice_set, wdc_pci_driver); static char* wdc_pci_probe (pcici_t tag, pcidi_t type) { char *name; if (name = wdc_pci(type)) wdc_pci_count++; return name; } static void wdc_pci_attach(config_id, unit) pcici_t config_id; int unit; { return; } #endif /* NPCI > 0 */ TIA Wolfgang From owner-freebsd-hackers Mon Feb 24 17:49:42 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id RAA09121 for hackers-outgoing; Mon, 24 Feb 1997 17:49:42 -0800 (PST) Received: from cougar.aceonline.com.au (adrian@cougar.aceonline.com.au [203.103.81.36]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id RAA08417; Mon, 24 Feb 1997 17:37:29 -0800 (PST) Received: from localhost (adrian@localhost) by cougar.aceonline.com.au (8.8.4/8.7) with SMTP id JAA22753; Tue, 25 Feb 1997 09:38:10 +0800 Date: Tue, 25 Feb 1997 09:38:09 +0800 (WST) From: Adrian Chadd To: Marc Slemko cc: hackers@freebsd.org, auditors@freebsd.org Subject: Re: disallow setuid root shells? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Mon, 24 Feb 1997, Marc Slemko wrote: > > Btw - yes I know adduser isn't suid, sorry, I just woke up .. now I've had > > my coffee things are clearer. :) > > process accounting sortof does that: > > lastcomm: (after enabling process accounting, of course) > > passwd -S marcs ttyp1 0.09 secs Mon Feb 24 17:14 > > The S says used superuser privs. That is only a partial implementation, > though, since process accounting logs aren't the nicest to log remotely, > they contain a whole lot of other programs, and the S flag is only set if > something the process calls suser(); ie. something it calls ends up > resulting in suser being called by something. A lot can be done without > doing that. > > Process accounting may be something to start for that type of logging. > Ahh ok I'll take a look at that when I get home. I however like the idea of logging all setuid programs when they are run, and at the kernel level as well. The only problem I can see is with the size of the logs, but if people think its a worthwhile thing I might have a look at implementing something, again when I get home. Adrian. From owner-freebsd-hackers Mon Feb 24 18:21:03 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id SAA10872 for hackers-outgoing; Mon, 24 Feb 1997 18:21:03 -0800 (PST) Received: from mail2.pilot.net (mail2.pilot.net [198.232.147.11]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id SAA10864 for ; Mon, 24 Feb 1997 18:21:00 -0800 (PST) Received: from u2.pilot.net (unknown-17-117.pilot.net [204.48.17.117]) by mail2.pilot.net with ESMTP id SAA21365; Mon, 24 Feb 1997 18:20:17 -0800 (PST) Received: from dc3.pilot.net (dc3.pilot.net [204.48.17.11]) by u2.pilot.net (8.8.5/) with ESMTP id SAA04644; Mon, 24 Feb 1997 18:20:16 -0800 (PST) Received: from localhost (wadlow@localhost) by dc3.pilot.net (8.7.3/8.7.3) with SMTP id SAA04834; Mon, 24 Feb 1997 18:20:16 -0800 (PST) X-Authentication-Warning: dc3.pilot.net: wadlow owned process doing -bs Date: Mon, 24 Feb 1997 18:20:15 -0800 (PST) From: Tom Wadlow To: "Jordan K. Hubbard" cc: hackers@freebsd.org Subject: Re: Ethernet options on 2.2-GAMMA In-Reply-To: <4217.856835032@time.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > - The kernel boot messages place the zp0 (the Etherlink III) > > device init messages just a few lines before the screen clears > > to start the initialization. Try as I might, I am not fast enough > > to read those lines to determine if it is successfully finding the > > zp0 device in the fraction of a second it is visible. > > jkh points emphatically at the scroll-lock key and the "Usage" item > in the very first sysinstall menu which documents its usage. :-) Ah, you mean the unusual option at the very *bottom* of the otherwise bland and uninteresting page designed to convince you that it is totally canonical and therefore not worth reading. ;-) Yes, I found it and it was quite helpful. In fact, scrolling back shows that it is somewhat schizophrenic about my Etherlink card. It sees the card in the slot, but does not seem to recognize the fact that it is a zp0 card. > Install over a SLIP or PLIP connection? Try a different PCCARD > adaptor? :-) So....you're saying that you *don't* support the 3c589 Etherlink, your HARDWARE.TXT and install programs to the contrary? > > You might also try the PAO floppy - It's available from Tatsumi > Hosokawa's home page (I don't have an exact URL, but it's an easy net > search target) and has better support for PCCARD devices in general. I'll check it out. Thanks!! --Tom From owner-freebsd-hackers Mon Feb 24 18:52:09 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id SAA12618 for hackers-outgoing; Mon, 24 Feb 1997 18:52:09 -0800 (PST) Received: from narcissus.ml.org (root@brosenga.Pitzer.edu [134.173.120.201]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id SAA12603 for ; Mon, 24 Feb 1997 18:52:04 -0800 (PST) Received: from localhost (ben@localhost) by narcissus.ml.org (8.7.5/8.7.3) with SMTP id SAA04565; Mon, 24 Feb 1997 18:48:13 -0800 (PST) Date: Mon, 24 Feb 1997 18:48:13 -0800 (PST) From: Snob Art Genre To: "Jordan K. Hubbard" cc: Tom Wadlow , hackers@freebsd.org Subject: Re: Ethernet options on 2.2-GAMMA In-Reply-To: <4217.856835032@time.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Mon, 24 Feb 1997, Jordan K. Hubbard wrote: > You might also try the PAO floppy - It's available from Tatsumi > Hosokawa's home page (I don't have an exact URL, but it's an easy net > search target) and has better support for PCCARD devices in general. http://www.jp.freebsd.org/PAO/ > > Jordan > Ben "You have your mind on computers, it seems." From owner-freebsd-hackers Mon Feb 24 18:52:41 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id SAA12744 for hackers-outgoing; Mon, 24 Feb 1997 18:52:41 -0800 (PST) Received: from mail2.pilot.net (mail2.pilot.net [198.232.147.11]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id SAA12730 for ; Mon, 24 Feb 1997 18:52:38 -0800 (PST) Received: from u2.pilot.net (unknown-17-117.pilot.net [204.48.17.117]) by mail2.pilot.net with ESMTP id SAA24617; Mon, 24 Feb 1997 18:51:43 -0800 (PST) Received: from dc3.pilot.net (dc3.pilot.net [204.48.17.11]) by u2.pilot.net (8.8.5/) with ESMTP id SAA04721; Mon, 24 Feb 1997 18:51:42 -0800 (PST) Received: from localhost (wadlow@localhost) by dc3.pilot.net (8.7.3/8.7.3) with SMTP id SAA04870; Mon, 24 Feb 1997 18:51:42 -0800 (PST) X-Authentication-Warning: dc3.pilot.net: wadlow owned process doing -bs Date: Mon, 24 Feb 1997 18:51:42 -0800 (PST) From: Tom Wadlow To: Snob Art Genre cc: "Jordan K. Hubbard" , hackers@freebsd.org Subject: Re: Ethernet options on 2.2-GAMMA In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Thanks!! --Tom On Mon, 24 Feb 1997, Snob Art Genre wrote: > Date: Mon, 24 Feb 1997 18:48:13 -0800 (PST) > From: Snob Art Genre > To: "Jordan K. Hubbard" > Cc: Tom Wadlow , hackers@freebsd.org > Subject: Re: Ethernet options on 2.2-GAMMA > > On Mon, 24 Feb 1997, Jordan K. Hubbard wrote: > > > You might also try the PAO floppy - It's available from Tatsumi > > Hosokawa's home page (I don't have an exact URL, but it's an easy net > > search target) and has better support for PCCARD devices in general. > > http://www.jp.freebsd.org/PAO/ > > > > > Jordan > > > > > > Ben > > "You have your mind on computers, it seems." > > From owner-freebsd-hackers Mon Feb 24 19:12:42 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id TAA15445 for hackers-outgoing; Mon, 24 Feb 1997 19:12:42 -0800 (PST) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id TAA15412 for ; Mon, 24 Feb 1997 19:12:24 -0800 (PST) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.3/8.6.9) id OAA24549; Tue, 25 Feb 1997 14:08:20 +1100 Date: Tue, 25 Feb 1997 14:08:20 +1100 From: Bruce Evans Message-Id: <199702250308.OAA24549@godzilla.zeta.org.au> To: hackers@freebsd.org, j@uriah.heep.sax.de Subject: Re: disallow setuid root shells? Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >> Except the case where the hacker truly knows what they're doing, in which >> case, the security audit will be worthless. root can modify any files he >> wants, including the database used to compare suid files against. =( > >chflags schg >sysctl -q kern.securelevel=1 sysctl: illegal option -- q usage: ... $ sysctl -w kern.securelevel=1 kern.securelevel: -1 -> 2 Securelevel 1 is completely useless under FreeBSD since non-mounted disks can be written to. Use level 2. Bruce From owner-freebsd-hackers Mon Feb 24 19:22:43 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id TAA16225 for hackers-outgoing; Mon, 24 Feb 1997 19:22:43 -0800 (PST) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id TAA16213 for ; Mon, 24 Feb 1997 19:22:37 -0800 (PST) Received: from time.cdrom.com (jkh@localhost [127.0.0.1]) by time.cdrom.com (8.8.5/8.6.9) with ESMTP id TAA04605; Mon, 24 Feb 1997 19:15:19 -0800 (PST) To: Tom Wadlow cc: hackers@freebsd.org Subject: Re: Ethernet options on 2.2-GAMMA In-reply-to: Your message of "Mon, 24 Feb 1997 18:20:15 PST." Date: Mon, 24 Feb 1997 19:15:19 -0800 Message-ID: <4601.856840519@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > So....you're saying that you *don't* support the 3c589 Etherlink, your > HARDWARE.TXT and install programs to the contrary? I'm saying I don't know if it's working at the moment - things break, on the supported list or not. :-) Jordan From owner-freebsd-hackers Mon Feb 24 20:24:56 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id UAA20067 for hackers-outgoing; Mon, 24 Feb 1997 20:24:56 -0800 (PST) Received: from kuoi.asui.uidaho.edu (qmailr@kuoi.asui.uidaho.edu [129.101.191.123]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id UAA20059 for ; Mon, 24 Feb 1997 20:24:49 -0800 (PST) Received: (qmail 12165 invoked by uid 1003); 25 Feb 1997 04:24:12 -0000 Date: Mon, 24 Feb 1997 20:24:11 -0800 (PST) From: faried nawaz Reply-To: faried nawaz To: hackers@freebsd.org Subject: /etc/security change (was Re: disabling setuid sh/csh) In-Reply-To: <199702242120.OAA25018@phaeton.artisoft.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Mon, 24 Feb 1997, Terry Lambert wrote: $ What's harder is hacked /usr/bin/passwd, /usr/bin/login, /sbin/init, $ /usr/libexec/telnetd, /usr/libexec/rlogind, etc. with the date set $ back. This reminds me -- /etc/security currently does [...] find $mount -xdev -type f \ \( -perm -u+x -or -perm -g+x -or -perm -o+x \) \ \( -perm -u+s -or -perm -g+s \) -print0 done | xargs -0 -n 20 ls -lgTd | sort +9 > $TMP [...] How about changing the arguments of ls to "lcTd"? "-g" is obsolete and probably should be removed, too. faried. -- faried nawaz box 3582, moscow id 83843-1914 From owner-freebsd-hackers Mon Feb 24 20:28:10 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id UAA20252 for hackers-outgoing; Mon, 24 Feb 1997 20:28:10 -0800 (PST) Received: from spinner.DIALix.COM (spinner.DIALix.COM [192.203.228.67]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id UAA19938; Mon, 24 Feb 1997 20:21:59 -0800 (PST) Received: from spinner.DIALix.COM (localhost.DIALix.oz.au [127.0.0.1]) by spinner.DIALix.COM (8.8.5/8.8.5) with ESMTP id MAA23422; Tue, 25 Feb 1997 12:15:43 +0800 (WST) Message-Id: <199702250415.MAA23422@spinner.DIALix.COM> X-Mailer: exmh version 2.0gamma 1/27/96 To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) cc: jehamby@lightside.com (Jake Hamby), abelits@phobos.illtel.denver.co.us, angio@aros.net, hackers@freebsd.org, auditors@freebsd.org Subject: Re: disallow setuid root shells? In-reply-to: Your message of "Tue, 25 Feb 1997 00:51:45 +0100." Date: Tue, 25 Feb 1997 12:15:42 +0800 From: Peter Wemm Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk J Wunsch wrote: > As Jake Hamby wrote: > > > My sentiments exactly! I would think that if there was a valid > > reason for setuid root shells, then a commercial OS like Solaris > > would probably allow them (since paying customers often would rather > > have functionality than security!). > > You think that's the reason why Solaris indeed allows it? :-) They are reasonably secure on solaris when the script writer knows what they are doing. Solaris uses /dev/fd/xxx when running setuid interpreted scripts, so it's not vulnerable to symlink races etc. The -p on /bin/sh is to use /etc/suid_profile rather than ~/.profile and to allow suid execution to continue. ksh doesn't require -p to be specified, it detects uid != euid and turns it on automatically. It has the same effect as -p in /bin/sh. In ksh however, you can turn off the 'p' option and ksh will revoke it's setuid right then. The way secure execution works is that the kernel opens the file in the process's context, so it's available on (eg) /dev/fd/3. It then checks the suid/etc stuff. If all is ok, it runs "/bin/sh /dev/fd/3 ". The race is solved, but $0 looks a bit strange to the script because the shell doesn't know the real name of the script. All that's required then for a reasonably secure script is explicitly setting IFS on the first line of the script, and extreme caution. > -- > 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. ;-) Cheers, -Peter From owner-freebsd-hackers Mon Feb 24 20:28:40 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id UAA20300 for hackers-outgoing; Mon, 24 Feb 1997 20:28:40 -0800 (PST) Received: from rocky.mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id UAA20285 for ; Mon, 24 Feb 1997 20:28:30 -0800 (PST) Received: (from nate@localhost) by rocky.mt.sri.com (8.7.5/8.7.3) id VAA20042; Mon, 24 Feb 1997 21:28:24 -0700 (MST) Date: Mon, 24 Feb 1997 21:28:24 -0700 (MST) Message-Id: <199702250428.VAA20042@rocky.mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: "Jordan K. Hubbard" Cc: Tom Wadlow , hackers@freebsd.org Subject: Re: Ethernet options on 2.2-GAMMA In-Reply-To: <4601.856840519@time.cdrom.com> References: <4601.856840519@time.cdrom.com> Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > So....you're saying that you *don't* support the 3c589 Etherlink, your > > HARDWARE.TXT and install programs to the contrary? > > I'm saying I don't know if it's working at the moment - things > break, on the supported list or not. :-) It works fine, but in the same manner as the normal 'ISA' drivers. If the card/driver parameters don't match, then the driver won't find the card. The zp0 is a 'dedicated' driver and doesn't take advantage of the fact that PCMCIA card can be configured to almost anywhere. That code exists in FreeBSD, but isn't documented well enough to use for 'GENERIC' users. Nate From owner-freebsd-hackers Mon Feb 24 20:39:04 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id UAA20900 for hackers-outgoing; Mon, 24 Feb 1997 20:39:04 -0800 (PST) Received: from mail2.pilot.net (mail2.pilot.net [198.232.147.11]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id UAA20889 for ; Mon, 24 Feb 1997 20:38:59 -0800 (PST) Received: from u2.pilot.net (unknown-17-117.pilot.net [204.48.17.117]) by mail2.pilot.net with ESMTP id UAA01936; Mon, 24 Feb 1997 20:37:04 -0800 (PST) Received: from dc3.pilot.net (dc3.pilot.net [204.48.17.11]) by u2.pilot.net (8.8.5/) with ESMTP id UAA04866; Mon, 24 Feb 1997 20:37:03 -0800 (PST) Received: from localhost (wadlow@localhost) by dc3.pilot.net (8.7.3/8.7.3) with SMTP id UAA04885; Mon, 24 Feb 1997 20:37:03 -0800 (PST) X-Authentication-Warning: dc3.pilot.net: wadlow owned process doing -bs Date: Mon, 24 Feb 1997 20:37:02 -0800 (PST) From: Tom Wadlow To: "Jordan K. Hubbard" cc: hackers@freebsd.org Subject: Re: Ethernet options on 2.2-GAMMA In-Reply-To: <4601.856840519@time.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Fair enough. I'll let you know if I do get it to work. --Tom On Mon, 24 Feb 1997, Jordan K. Hubbard wrote: > Date: Mon, 24 Feb 1997 19:15:19 -0800 > From: "Jordan K. Hubbard" > To: Tom Wadlow > Cc: hackers@freebsd.org > Subject: Re: Ethernet options on 2.2-GAMMA > > > So....you're saying that you *don't* support the 3c589 Etherlink, your > > HARDWARE.TXT and install programs to the contrary? > > I'm saying I don't know if it's working at the moment - things > break, on the supported list or not. :-) > > Jordan > From owner-freebsd-hackers Mon Feb 24 20:58:00 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id UAA22509 for hackers-outgoing; Mon, 24 Feb 1997 20:58:00 -0800 (PST) Received: from mail2.pilot.net (mail2.pilot.net [198.232.147.11]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id UAA22496 for ; Mon, 24 Feb 1997 20:57:51 -0800 (PST) Received: from u2.pilot.net (unknown-17-117.pilot.net [204.48.17.117]) by mail2.pilot.net with ESMTP id UAA02844; Mon, 24 Feb 1997 20:55:42 -0800 (PST) Received: from dc3.pilot.net (dc3.pilot.net [204.48.17.11]) by u2.pilot.net (8.8.5/) with ESMTP id UAA04907; Mon, 24 Feb 1997 20:55:41 -0800 (PST) Received: from localhost (wadlow@localhost) by dc3.pilot.net (8.7.3/8.7.3) with SMTP id UAA04901; Mon, 24 Feb 1997 20:55:41 -0800 (PST) X-Authentication-Warning: dc3.pilot.net: wadlow owned process doing -bs Date: Mon, 24 Feb 1997 20:55:41 -0800 (PST) From: Tom Wadlow To: Nate Williams cc: "Jordan K. Hubbard" , hackers@freebsd.org Subject: Re: Ethernet options on 2.2-GAMMA In-Reply-To: <199702250428.VAA20042@rocky.mt.sri.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > I'm saying I don't know if it's working at the moment - things > > break, on the supported list or not. :-) > > It works fine, but in the same manner as the normal 'ISA' drivers. If > the card/driver parameters don't match, then the driver won't find the > card. The zp0 is a 'dedicated' driver and doesn't take advantage of the > fact that PCMCIA card can be configured to almost anywhere. That code > exists in FreeBSD, but isn't documented well enough to use for 'GENERIC' > users. FWIW, I've got it set up using the parameters in the HARDWARE.TXT file (which agree with the ones in the install program). The card is brand new (I bought it for this purpose), and hasn't been set up under any other system before. The FreeBSD default parameters agree with what the Etherlink manual says they should be. Don't have a DOS/Windows system with PCMCIA (or without, for that matter), so I can't try it on there first but it seems like it should work. I've tried it in both PCMCIA slots and it seems to see a card in the appropriate slot, but doesn't recognize it at a zp0. Tried it with all non-essential devices disabled, and with all enabled, and reasonable permutations between. Gotten into the Emergency shell, and looked for it with ifconfig too, just to be sure (though if the kernel doesn't acknowledge it, ifconfig sure as hell isn't gonna see it....) BTW, I don't know what the netiquette of this particular list is, so please advise if I should take this discussion offline from hackers@freebsd.org. If it's annoying, blame Jordan. He convinced me to give FreeBSD a try at Usenix ;-) --Tom From owner-freebsd-hackers Mon Feb 24 21:00:33 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id VAA22940 for hackers-outgoing; Mon, 24 Feb 1997 21:00:33 -0800 (PST) Received: from rocky.mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id VAA22926 for ; Mon, 24 Feb 1997 21:00:27 -0800 (PST) Received: (from nate@localhost) by rocky.mt.sri.com (8.7.5/8.7.3) id WAA20167; Mon, 24 Feb 1997 22:00:23 -0700 (MST) Date: Mon, 24 Feb 1997 22:00:23 -0700 (MST) Message-Id: <199702250500.WAA20167@rocky.mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Tom Wadlow Cc: Nate Williams , hackers@freebsd.org Subject: Re: Ethernet options on 2.2-GAMMA In-Reply-To: References: <199702250428.VAA20042@rocky.mt.sri.com> Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > > I'm saying I don't know if it's working at the moment - things > > > break, on the supported list or not. :-) > > > > It works fine, but in the same manner as the normal 'ISA' drivers. If > > the card/driver parameters don't match, then the driver won't find the > > card. The zp0 is a 'dedicated' driver and doesn't take advantage of the > > fact that PCMCIA card can be configured to almost anywhere. That code > > exists in FreeBSD, but isn't documented well enough to use for 'GENERIC' > > users. > > FWIW, I've got it set up using the parameters in the HARDWARE.TXT file > (which agree with the ones in the install program). The card is brand new > (I bought it for this purpose), and hasn't been set up under any other > system before. That's irellevant. The card comes 'configured' from the factory differently. I don't know why, but it does. :( (And, there are all sorts of different models as well, which behave slightly different.) > The FreeBSD default parameters agree with what the > Etherlink manual says they should be. Don't have a DOS/Windows system > with PCMCIA (or without, for that matter), so I can't try it on there > first but it seems like it should work. I've tried it in both PCMCIA > slots and it seems to see a card in the appropriate slot, but doesn't > recognize it at a zp0. Then the values saved in the card in non-volatile RAM are not the same as what FreeBSD expects. To read these values you must use the DOS supplied program. The other possibility is that the card is a 3C589D, which appears to be different enough so it's not supported with the zp0 driver. > BTW, I don't know what the netiquette of this particular list is, so > please advise if I should take this discussion offline from > hackers@freebsd.org. Nope, this is completely appropriate. Nate From owner-freebsd-hackers Mon Feb 24 21:08:57 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id VAA23382 for hackers-outgoing; Mon, 24 Feb 1997 21:08:57 -0800 (PST) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id VAA23369 for ; Mon, 24 Feb 1997 21:08:50 -0800 (PST) Received: from time.cdrom.com (jkh@localhost [127.0.0.1]) by time.cdrom.com (8.8.5/8.6.9) with ESMTP id VAA06751; Mon, 24 Feb 1997 21:05:44 -0800 (PST) To: Tom Wadlow cc: Nate Williams , hackers@freebsd.org Subject: Re: Ethernet options on 2.2-GAMMA In-reply-to: Your message of "Mon, 24 Feb 1997 20:55:41 PST." Date: Mon, 24 Feb 1997 21:05:44 -0800 Message-ID: <6747.856847144@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > recognize it at a zp0. Tried it with all non-essential devices disabled, > and with all enabled, and reasonable permutations between. Gotten into > the Emergency shell, and looked for it with ifconfig too, just to be sure > (though if the kernel doesn't acknowledge it, ifconfig sure as hell isn't > gonna see it....) Sounds like it's just one of those situations where either the card or the Laptop's PCCARD support is just not what FreeBSD expects. Did you have any different results with the PAO floppy? I'm not sure, but I thought they used a different driver for this over there. Both the ze0 and zp0 drivers are actually kludges in the non-PAO (e.g. the default) code - early versions of ed0 and ep0 were cloned off and hacked into the PCCARD-specific versions you see now as ze0 and zp0. The PAO folks are, unless I'm very much mistaken (and Nate would know a lot better than I about that), undertaking the far more difficult task of making their drivers simply auto-load when a card is inserted. That would make their drivers fairly divergent just by that fact alone. > BTW, I don't know what the netiquette of this particular list is, so > please advise if I should take this discussion offline from I think it's fine - we're talking about the technical aspects of getting an obscure card to work. Perhaps it could be a little more specifically channelled into -hardware, but I think there's more than enough overlap that -hackers is fine too. > hackers@freebsd.org. If it's annoying, blame Jordan. He convinced me to > give FreeBSD a try at Usenix ;-) Hey now, I just rope 'em in, I don't claim responsibility for 'em afterwards. :-) Jordan From owner-freebsd-hackers Mon Feb 24 21:18:45 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id VAA23862 for hackers-outgoing; Mon, 24 Feb 1997 21:18:45 -0800 (PST) Received: from rocky.mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id VAA23855 for ; Mon, 24 Feb 1997 21:18:38 -0800 (PST) Received: (from nate@localhost) by rocky.mt.sri.com (8.7.5/8.7.3) id WAA20211; Mon, 24 Feb 1997 22:13:57 -0700 (MST) Date: Mon, 24 Feb 1997 22:13:57 -0700 (MST) Message-Id: <199702250513.WAA20211@rocky.mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: "Jordan K. Hubbard" Cc: Tom Wadlow , Nate Williams , hackers@freebsd.org Subject: Re: Ethernet options on 2.2-GAMMA In-Reply-To: <6747.856847144@time.cdrom.com> References: <6747.856847144@time.cdrom.com> Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > recognize it at a zp0. Tried it with all non-essential devices disabled, > > and with all enabled, and reasonable permutations between. Gotten into > > the Emergency shell, and looked for it with ifconfig too, just to be sure > > (though if the kernel doesn't acknowledge it, ifconfig sure as hell isn't > > gonna see it....) > > Sounds like it's just one of those situations where either the card or > the Laptop's PCCARD support is just not what FreeBSD expects. The driver and the card aren't agreeing. > The PAO folks are, unless I'm very much mistaken (and Nate would know > a lot better than I about that), undertaking the far more difficult > task of making their drivers simply auto-load when a card is inserted. > That would make their drivers fairly divergent just by that fact > alone. The PAO folks have extended the generic code to do alot of these things, but the code in -current (and 2.2) would work if we could find a clean way to hook things in sysinstall. Both Poul and I hacked on the code, incorporated PAO patches, as well as incorporated external patches. We also need to document how to set things up, but you know how well most developers do that. :( Good documentation could probably be done easier than doing the install thing. The PAO solution is not a long-term workable solution IMHO. Nate From owner-freebsd-hackers Mon Feb 24 21:23:57 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id VAA24034 for hackers-outgoing; Mon, 24 Feb 1997 21:23:57 -0800 (PST) Received: from nemesis.lonestar.org (fw13-5.ppp.iadfw.net [206.138.226.38]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id VAA24028; Mon, 24 Feb 1997 21:23:52 -0800 (PST) Received: by nemesis.lonestar.org (Smail3.1.27.1 #22) id m0vzFKg-000umHC; Mon, 24 Feb 97 23:21 CST Message-Id: Date: Mon, 24 Feb 97 23:21 CST To: hackers@freebsd.org, current@freebsd.org From: uhclem@nemesis.lonestar.org (Frank Durda IV) Sent: Mon Feb 24 1997, 23:21:42 CST Subject: Can mkisofs leave file dates unaltered? [repost] Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk [sorry for the repost, but I got zero response in hackers and no email. Perhaps it was because it was one article buried in the middle of a much larger mkisofs thread] I am trying to use mkisofs to create some backups and it appears to be working fine, except that the stored files all have dates and times of when mkisfos was run instead of the actual date/time stamps on the files I am trying to archive. I know this isn't a restriction of ISO 9660 since I used to use a Meridian CD-ROM mastering system and it had no problem with leaving file dates as they were in the master directories. Only the directory dates reflected the time when the ISO 9660 filesystem was constructed. That's OK. The Windows Easy-CD package also has no problem with leaving the date/times on the files unaltered. Any ideas? The man page for mkisofs doesn't seem to mention anything about controlling dates. I need the CD9660 date/times on files to be unaltered so that a non-Rock Ridge systems (Windoze/DOS) will see the correct dates. Keeping the dates/times correct is important for legal reasons. The system being used is running 2.2-GAMMA, HP4020i burner, and the mkisofs package that 2.2-GAMMA-0215 provides. Thanks for any pointers. Frank Durda IV |"The Knights who say "LETNi" or uhclem%nemesis@rwsystr.nkn.net | demand... A SEGMENT REGISTER!!!" |"A what?" or ...letni!rwsys!nemesis!uhclem |"LETNi! LETNi! LETNi!" - 1983 From owner-freebsd-hackers Mon Feb 24 21:32:17 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id VAA24413 for hackers-outgoing; Mon, 24 Feb 1997 21:32:17 -0800 (PST) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id VAA24373 for ; Mon, 24 Feb 1997 21:31:03 -0800 (PST) Received: from time.cdrom.com (jkh@localhost [127.0.0.1]) by time.cdrom.com (8.8.5/8.6.9) with ESMTP id VAA06896; Mon, 24 Feb 1997 21:28:13 -0800 (PST) To: Nate Williams cc: Tom Wadlow , hackers@freebsd.org Subject: Re: Ethernet options on 2.2-GAMMA In-reply-to: Your message of "Mon, 24 Feb 1997 22:13:57 MST." <199702250513.WAA20211@rocky.mt.sri.com> Date: Mon, 24 Feb 1997 21:28:13 -0800 Message-ID: <6892.856848493@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > The PAO folks have extended the generic code to do alot of these things, > but the code in -current (and 2.2) would work if we could find a clean > way to hook things in sysinstall. Both Poul and I hacked on the code, Hmmm. If you were allowed to play supreme dictator in sysinstall for a day, what would these hooks look like? ;) Jordan From owner-freebsd-hackers Mon Feb 24 22:17:08 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id WAA28657 for hackers-outgoing; Mon, 24 Feb 1997 22:17:08 -0800 (PST) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id WAA28632; Mon, 24 Feb 1997 22:16:56 -0800 (PST) Received: (from msmith@localhost) by genesis.atrad.adelaide.edu.au (8.8.5/8.7.3) id QAA12983; Tue, 25 Feb 1997 16:46:23 +1030 (CST) From: Michael Smith Message-Id: <199702250616.QAA12983@genesis.atrad.adelaide.edu.au> Subject: Re: Can mkisofs leave file dates unaltered? [repost] In-Reply-To: from Frank Durda IV at "Feb 24, 97 11:21:00 pm" To: uhclem@nemesis.lonestar.org (Frank Durda IV) Date: Tue, 25 Feb 1997 16:46:21 +1030 (CST) Cc: hackers@freebsd.org, current@freebsd.org X-Mailer: ELM [version 2.4ME+ PL28 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Frank Durda IV stands accused of saying: > > I am trying to use mkisofs to create some backups and it appears to be > working fine, except that the stored files all have dates and times of > when mkisfos was run instead of the actual date/time stamps on the > files I am trying to archive. Is this the mkisofs left over from your 2.1 system, or the port from sysutils? mkisofs was removes from the base system some time back. > Any ideas? The man page for mkisofs doesn't seem to mention anything > about controlling dates. I need the CD9660 date/times on files to be > unaltered so that a non-Rock Ridge systems (Windoze/DOS) will see the > correct dates. Mkisofs was/is a horrible piece of work, and it's quite possible that the author just got the datestamping completely wrong. A quick eyeball over tree.c makes be queasy but doesn't tell me a lot; you would probably get some good results from a handful of debugging printfs. > Frank Durda IV |"The Knights who say "LETNi" -- ]] Mike Smith, Software Engineer msmith@gsoft.com.au [[ ]] Genesis Software genesis@gsoft.com.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control. (ph) +61-8-8267-3493 [[ ]] Unix hardware collector. "Where are your PEZ?" The Tick [[ From owner-freebsd-hackers Mon Feb 24 22:23:38 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id WAA29065 for hackers-outgoing; Mon, 24 Feb 1997 22:23:38 -0800 (PST) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id WAA29046 for ; Mon, 24 Feb 1997 22:23:24 -0800 (PST) Received: (from msmith@localhost) by genesis.atrad.adelaide.edu.au (8.8.5/8.7.3) id QAA13039; Tue, 25 Feb 1997 16:52:18 +1030 (CST) From: Michael Smith Message-Id: <199702250622.QAA13039@genesis.atrad.adelaide.edu.au> Subject: Re: Ethernet options on 2.2-GAMMA In-Reply-To: <6892.856848493@time.cdrom.com> from "Jordan K. Hubbard" at "Feb 24, 97 09:28:13 pm" To: jkh@time.cdrom.com (Jordan K. Hubbard) Date: Tue, 25 Feb 1997 16:52:17 +1030 (CST) Cc: nate@mt.sri.com, wadlow@pilot.net, hackers@freebsd.org X-Mailer: ELM [version 2.4ME+ PL28 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Jordan K. Hubbard stands accused of saying: > > The PAO folks have extended the generic code to do alot of these things, > > but the code in -current (and 2.2) would work if we could find a clean > > way to hook things in sysinstall. Both Poul and I hacked on the code, > > Hmmm. If you were allowed to play supreme dictator in sysinstall for a day, > what would these hooks look like? ;) There would be a probe for the 'crd0' device having been found, and a prompt saying "please insert any PC-CARD devices to be used for the installation [Continue]". Sysinstall would then listen for card arrival events and play like pccardd until the user cancelled the dialog. The results of insertions/removals should be shown in a scrolling window somewhere. It should then rescan for media devices. This process should also be selectable from a menu somewhere. The relevant code in pccardd is actually fairly small, and the card database ought to compress well. It should be possible to be smarter (ie. handle installation with nonstandard cards), but that would require "insert the floppy containing configuration data for the card XYZZY", which would be More Of A Nuisance. > Jordan -- ]] Mike Smith, Software Engineer msmith@gsoft.com.au [[ ]] Genesis Software genesis@gsoft.com.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control. (ph) +61-8-8267-3493 [[ ]] Unix hardware collector. "Where are your PEZ?" The Tick [[ From owner-freebsd-hackers Mon Feb 24 22:29:04 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id WAA29435 for hackers-outgoing; Mon, 24 Feb 1997 22:29:04 -0800 (PST) Received: from rocky.mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id WAA29428 for ; Mon, 24 Feb 1997 22:29:01 -0800 (PST) Received: (from nate@localhost) by rocky.mt.sri.com (8.7.5/8.7.3) id XAA20730; Mon, 24 Feb 1997 23:28:31 -0700 (MST) Date: Mon, 24 Feb 1997 23:28:31 -0700 (MST) Message-Id: <199702250628.XAA20730@rocky.mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Michael Smith Cc: jkh@time.cdrom.com (Jordan K. Hubbard), nate@mt.sri.com, hackers@freebsd.org Subject: Re: Ethernet options on 2.2-GAMMA In-Reply-To: <199702250622.QAA13039@genesis.atrad.adelaide.edu.au> References: <6892.856848493@time.cdrom.com> <199702250622.QAA13039@genesis.atrad.adelaide.edu.au> Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk [ PCCARD hooks in sysintall ] > > Hmmm. If you were allowed to play supreme dictator in sysinstall for a day, > > what would these hooks look like? ;) > > There would be a probe for the 'crd0' device having been found, and a > prompt saying "please insert any PC-CARD devices to be used for the > installation [Continue]". So far, so good. > Sysinstall would then listen for card arrival events and play like > pccardd until the user cancelled the dialog. The results of > insertions/removals should be shown in a scrolling window somewhere. > It should then rescan for media devices. This process should also be > selectable from a menu somewhere. So far so good. > The relevant code in pccardd is actually fairly small, and the card > database ought to compress well. Actually, this is the hard part. The code in pccardd is *NOT* small, since it has to read all of the darn card TUPLES and such. It's alot of bloat for (IMHO) little gain. > It should be possible to be smarter (ie. handle installation with > nonstandard cards), but that would require "insert the floppy containing > configuration data for the card XYZZY", which would be More Of A Nuisance. No kidding. This is my biggest failing in the current code, but I've been spending more time trying to 'shore up the existing code' than in spending time 'extending'. Alot of this would go away if we could simply re-write the userland code. Hopefully the Nomads are doing this. :) Nate From owner-freebsd-hackers Mon Feb 24 22:37:52 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id WAA00479 for hackers-outgoing; Mon, 24 Feb 1997 22:37:52 -0800 (PST) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id WAA00471 for ; Mon, 24 Feb 1997 22:37:47 -0800 (PST) Received: (from msmith@localhost) by genesis.atrad.adelaide.edu.au (8.8.5/8.7.3) id RAA13163; Tue, 25 Feb 1997 17:03:27 +1030 (CST) From: Michael Smith Message-Id: <199702250633.RAA13163@genesis.atrad.adelaide.edu.au> Subject: Re: Ethernet options on 2.2-GAMMA In-Reply-To: <199702250628.XAA20730@rocky.mt.sri.com> from Nate Williams at "Feb 24, 97 11:28:31 pm" To: nate@mt.sri.com (Nate Williams) Date: Tue, 25 Feb 1997 17:03:26 +1030 (CST) Cc: msmith@atrad.adelaide.edu.au, jkh@time.cdrom.com, nate@mt.sri.com, hackers@freebsd.org X-Mailer: ELM [version 2.4ME+ PL28 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Nate Williams stands accused of saying: > > > The relevant code in pccardd is actually fairly small, and the card > > database ought to compress well. > > Actually, this is the hard part. The code in pccardd is *NOT* small, > since it has to read all of the darn card TUPLES and such. It's alot of > bloat for (IMHO) little gain. Er, I would say that in its current form (about 600 lines) the CIS reading code is not terribly large compared to sysinstall (16,000 lines). I would love to rewrite the CIS parser. I would love to help Jordan with sysinstall, or any of a dozen other things. But I have to eat, and that really cramps your style 8( > No kidding. This is my biggest failing in the current code, but I've > been spending more time trying to 'shore up the existing code' than in > spending time 'extending'. Alot of this would go away if we could > simply re-write the userland code. Hopefully the Nomads are doing > this. :) Indeed. Arg, stress. 8( > Nate -- ]] Mike Smith, Software Engineer msmith@gsoft.com.au [[ ]] Genesis Software genesis@gsoft.com.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control. (ph) +61-8-8267-3493 [[ ]] Unix hardware collector. "Where are your PEZ?" The Tick [[ From owner-freebsd-hackers Mon Feb 24 23:06:36 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id XAA02527 for hackers-outgoing; Mon, 24 Feb 1997 23:06:36 -0800 (PST) Received: from smtp.gte.net (mail1.gte.net [206.124.65.236]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id XAA02520 for ; Mon, 24 Feb 1997 23:06:33 -0800 (PST) Received: from LOCALNAME (Cust57.Max63.Los-Angeles.CA.MS.UU.NET [153.34.101.185]) by smtp.gte.net (SMI-8.6/) via SMTP id BAA12330 for ; Tue, 25 Feb 1997 01:06:26 -0600 Message-ID: <33128F17.5328@mail.gte.net> Date: Mon, 24 Feb 1997 23:04:55 -0800 From: Fred Adorno Reply-To: fadorno@sm1.gte.net Organization: Adorno and Associates X-Mailer: Mozilla 3.01Gold (Win16; I) MIME-Version: 1.0 To: freebsd-hackers@freefall.FreeBSD.org Subject: Exabyte's TR-3 Eagle Nest Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Can someone tell me how to configure this drive in my kernel and how to test the installation? From owner-freebsd-hackers Mon Feb 24 23:54:19 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id XAA06849 for hackers-outgoing; Mon, 24 Feb 1997 23:54:19 -0800 (PST) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id XAA06841 for ; Mon, 24 Feb 1997 23:54:14 -0800 (PST) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id IAA12831; Tue, 25 Feb 1997 08:54:04 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.8.5/8.8.5) id IAA04829; Tue, 25 Feb 1997 08:35:58 +0100 (MET) Message-ID: Date: Tue, 25 Feb 1997 08:35:58 +0100 From: j@uriah.heep.sax.de (J Wunsch) To: mark@quickweb.com (Mark Mayo) Cc: cshenton@it.hq.nasa.gov (Chris Shenton), hackers@freebsd.org Subject: Re: migrating 2.1.7 -> 2.2: simple or hairy? References: X-Mailer: Mutt 0.55-PL10 Mime-Version: 1.0 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: ; from Mark Mayo on Feb 24, 1997 20:22:44 -0500 Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk As Mark Mayo wrote: > > Don't forget your /etc updates... > > > Curious.. is /etc/ updated with a "src-all" line in the cvsup file? No. It will update /usr/src/etc, but (naturally) not /etc. You can wipe out your old /etc by cd /usr/src/etc make distribution -- 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-hackers Mon Feb 24 23:56:20 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id XAA07103 for hackers-outgoing; Mon, 24 Feb 1997 23:56:20 -0800 (PST) Received: from research.gate.nec.co.jp (research.gate.nec.co.jp [202.32.8.49]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id XAA07052 for ; Mon, 24 Feb 1997 23:55:53 -0800 (PST) Received: from sbl-gw.sbl.cl.nec.co.jp by research.gate.nec.co.jp (8.8.5+2.7Wbeta5/950912) with ESMTP id QAA10505; Tue, 25 Feb 1997 16:55:49 +0900 (JST) Received: from sirius.sbl.cl.nec.co.jp by sbl-gw.sbl.cl.nec.co.jp (8.8.5+2.7Wbeta5/3.3W6) with ESMTP id QAA08547; Tue, 25 Feb 1997 16:55:47 +0900 (JST) Received: by sirius.sbl.cl.nec.co.jp (8.7.5+2.6Wbeta6/3.3W6) with UUCP id QAA20017; Tue, 25 Feb 1997 16:55:47 +0900 (JST) Date: Tue, 25 Feb 1997 16:55:47 +0900 (JST) From: Naoki Hamada Message-Id: <199702250755.QAA20017@sirius.sbl.cl.nec.co.jp> To: freebsd-hackers@freefall.freebsd.org Subject: MALLOC(3) writes to stderr... Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Hi. Malloc(3) of 2.2-GAMMA writes error/warning messages to stderr. There is a daemon named jserver, which provides translations between Japanese characters, which does close stderr before opening its dictionary files. Sometimes jserver gets its dictionary file completely damaged by malloc's error/warning message. How should we deal with this anomaly? Yep, fixing jserver's memory allocation thoroughly might be the ultimate solution, but we need a practical solution for now. Must we change jserver to keep stderr open and to put error messages into /var/log/jserver.log or something? Or make malloc(3) keep silent? - nao From owner-freebsd-hackers Mon Feb 24 23:56:36 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id XAA07147 for hackers-outgoing; Mon, 24 Feb 1997 23:56:36 -0800 (PST) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id XAA06769; Mon, 24 Feb 1997 23:53:41 -0800 (PST) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id IAA12829; Tue, 25 Feb 1997 08:53:32 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.8.5/8.8.5) id IAA04815; Tue, 25 Feb 1997 08:33:15 +0100 (MET) Message-ID: Date: Tue, 25 Feb 1997 08:33:14 +0100 From: j@uriah.heep.sax.de (J Wunsch) To: hackers@freebsd.org Cc: jehamby@lightside.com (Jake Hamby), abelits@phobos.illtel.denver.co.us, angio@aros.net, auditors@freebsd.org Subject: Re: disallow setuid root shells? References: <199702250415.MAA23422@spinner.DIALix.COM> X-Mailer: Mutt 0.55-PL10 Mime-Version: 1.0 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199702250415.MAA23422@spinner.DIALix.COM>; from Peter Wemm on Feb 25, 1997 12:15:42 +0800 Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk As Peter Wemm wrote: > ksh doesn't require -p to be specified, it detects uid != euid and turns > it on automatically. It has the same effect as -p in /bin/sh. In ksh > however, you can turn off the 'p' option and ksh will revoke it's setuid > right then. Just for the records: our /bin/sh does the same. > All that's required then for a reasonably secure script is explicitly > setting IFS on the first line of the script, and extreme caution. Ah, having seen so numerous complaints from suidperl about tainted variables, i wouldn't ever in the world try to write a suid shell script. :-) -- 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-hackers Mon Feb 24 23:58:22 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id XAA07293 for hackers-outgoing; Mon, 24 Feb 1997 23:58:22 -0800 (PST) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id XAA06928; Mon, 24 Feb 1997 23:54:36 -0800 (PST) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id IAA12832; Tue, 25 Feb 1997 08:54:20 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.8.5/8.8.5) id IAA04868; Tue, 25 Feb 1997 08:44:30 +0100 (MET) Message-ID: Date: Tue, 25 Feb 1997 08:44:29 +0100 From: j@uriah.heep.sax.de (J Wunsch) To: adrian@cougar.aceonline.com.au (Adrian Chadd) Cc: marcs@znep.com (Marc Slemko), hackers@freebsd.org, auditors@freebsd.org Subject: Re: disallow setuid root shells? References: X-Mailer: Mutt 0.55-PL10 Mime-Version: 1.0 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: ; from Adrian Chadd on Feb 25, 1997 09:38:09 +0800 Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk As Adrian Chadd wrote: > Ahh ok I'll take a look at that when I get home. I however like the idea > of logging all setuid programs when they are run, and at the kernel level > as well. The only problem I can see is with the size of the logs, but if > people think its a worthwhile thing I might have a look at implementing > something, again when I get home. If you do this: . make it configurable via sysctl, . don't turn it on by default. I presume you're gonna log it at auth.info, but i for sure don't wanna see each suid program with the same notification as each login. In an environment where you can basically trust your users, it's pointless to log them, all you have to care is to not get breakins from outside. -- 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-hackers Tue Feb 25 00:10:25 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id AAA08084 for hackers-outgoing; Tue, 25 Feb 1997 00:10:25 -0800 (PST) Received: from aeffle.Stanford.EDU (sequence.Stanford.EDU [171.65.76.7]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id AAA08054 for ; Tue, 25 Feb 1997 00:10:19 -0800 (PST) Received: (from hlew@localhost) by aeffle.Stanford.EDU (8.8.4/8.6.6) id AAA05548; Tue, 25 Feb 1997 00:10:16 -0800 (PST) Date: Tue, 25 Feb 1997 00:10:16 -0800 (PST) From: Howard Lew To: Fred Adorno cc: freebsd-hackers@freefall.freebsd.org Subject: Re: Exabyte's TR-3 Eagle Nest In-Reply-To: <33128F17.5328@mail.gte.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Mon, 24 Feb 1997, Fred Adorno wrote: > Can someone tell me how to configure this drive in my kernel and how to > test the installation? > I don't think it is supported at this time. From owner-freebsd-hackers Tue Feb 25 00:20:58 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id AAA08528 for hackers-outgoing; Tue, 25 Feb 1997 00:20:58 -0800 (PST) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id AAA08521 for ; Tue, 25 Feb 1997 00:20:52 -0800 (PST) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id JAA13232 for hackers@freebsd.org; Tue, 25 Feb 1997 09:20:50 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.8.5/8.8.5) id IAA05045; Tue, 25 Feb 1997 08:54:30 +0100 (MET) Message-ID: Date: Tue, 25 Feb 1997 08:54:28 +0100 From: j@uriah.heep.sax.de (J Wunsch) To: hackers@freebsd.org Subject: Re: Ethernet options on 2.2-GAMMA References: <6892.856848493@time.cdrom.com> <199702250622.QAA13039@genesis.atrad.adelaide.edu.au> <199702250628.XAA20730@rocky.mt.sri.com> X-Mailer: Mutt 0.55-PL10 Mime-Version: 1.0 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199702250628.XAA20730@rocky.mt.sri.com>; from Nate Williams on Feb 24, 1997 23:28:31 -0700 Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk As Nate Williams wrote: > > The relevant code in pccardd is actually fairly small, and the card > > database ought to compress well. > > Actually, this is the hard part. The code in pccardd is *NOT* small, > since it has to read all of the darn card TUPLES and such. It's alot of > bloat for (IMHO) little gain. What about supplying this from a second floppy? Remember, once the kernel has been loaded, the floppy device is available again. -- 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-hackers Tue Feb 25 00:21:02 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id AAA08550 for hackers-outgoing; Tue, 25 Feb 1997 00:21:02 -0800 (PST) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id AAA08536 for ; Tue, 25 Feb 1997 00:20:59 -0800 (PST) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id JAA13239 for Hackers@freebsd.org; Tue, 25 Feb 1997 09:20:57 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.8.5/8.8.5) id JAA05108; Tue, 25 Feb 1997 09:07:02 +0100 (MET) Message-ID: Date: Tue, 25 Feb 1997 09:07:02 +0100 From: j@uriah.heep.sax.de (J Wunsch) To: Hackers@freebsd.org (FreeBSD Hackers) Subject: Re: Immutable files, a false sense of security (Re: disabling setuid , sh/csh) References: <199702242120.OAA25018@phaeton.artisoft.com> X-Mailer: Mutt 0.55-PL10 Mime-Version: 1.0 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: ; from Michael Hancock on Feb 25, 1997 09:38:06 +0900 Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk As Michael Hancock wrote: > Has anyone tried hacking a system in "secure" mode via something like > /dev/io? /dev/io should refuse to be opened if securelevel >= 1 (or at least, >= 2). Naturally, this prevents you from running an Xserver and such. > I wonder how much of a speed bump it would present to an > attacker. You'll have a hard time for any sophisticated attack. Denial of service attacks through /dev/io are certainly easy. If you try to create your favorite setuid program on a disk however, you have to: . emulate the filesystem (simplest part, use fsdb or such as a template) . emulate the disk driver (harder, and not very general) . cope with the fact that the existing disk driver runs concurrently with this; turning off interrupts is not an option unless you can use DDB which is the only thing that can do polled IO to get your input into the system at all. -- 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-hackers Tue Feb 25 00:52:00 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id AAA10497 for hackers-outgoing; Tue, 25 Feb 1997 00:52:00 -0800 (PST) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id AAA10491 for ; Tue, 25 Feb 1997 00:51:57 -0800 (PST) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id JAA13807; Tue, 25 Feb 1997 09:51:46 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.8.5/8.8.5) id JAA20194; Tue, 25 Feb 1997 09:44:24 +0100 (MET) Message-ID: Date: Tue, 25 Feb 1997 09:44:23 +0100 From: j@uriah.heep.sax.de (J Wunsch) To: fadorno@sm1.gte.net Cc: freebsd-hackers@freefall.freebsd.org Subject: Re: Exabyte's TR-3 Eagle Nest References: <33128F17.5328@mail.gte.net> X-Mailer: Mutt 0.55-PL10 Mime-Version: 1.0 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <33128F17.5328@mail.gte.net>; from Fred Adorno on Feb 24, 1997 23:04:55 -0800 Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk As Fred Adorno wrote: > Can someone tell me how to configure this drive in my kernel and how to > test the installation? Sure, if you tell us what kind of beast it is, instead of silently assuming we already knew it? -- 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-hackers Tue Feb 25 01:01:48 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id BAA11051 for hackers-outgoing; Tue, 25 Feb 1997 01:01:48 -0800 (PST) Received: from who.cdrom.com (who.cdrom.com [204.216.27.3]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id BAA11030 for ; Tue, 25 Feb 1997 01:01:43 -0800 (PST) Received: from murrow.prognet.com (prognet.com [205.219.198.1]) by who.cdrom.com (8.7.5/8.6.11) with SMTP id AAA11877 for ; Tue, 25 Feb 1997 00:30:42 -0800 (PST) Received: from peterh (two89.dev.prognet.com) by murrow.prognet.com with SMTP id AA20112 (5.67b/IDA-1.5 for ); Tue, 25 Feb 1997 00:31:06 -0800 Message-Id: <3.0.1.32.19970225003040.00ff58e4@prognet.com> X-Sender: peterh@prognet.com X-Mailer: Windows Eudora Pro Version 3.0.1 (32) Date: Tue, 25 Feb 1997 00:30:40 -0800 To: freebsd-hackers@freebsd.org From: Peter Haight Subject: Static variables in shared libraries Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk While I am doing this stuff on FreeBSD, this is not necessarily FreeBSD related, but I can't seem to find much shared library information on the Web. I have a shared library which has the following definitions: const char* test_3 = "hello"; const char* test_4 = test_3; If I dynamically load this shared library in my program and print the variables, I get: test_3 = "hello" test_4 = 0x0 What's going on? Additionaly, does anyone know a good source of detailed information on the implementation of shared libraries on various platforms? From owner-freebsd-hackers Tue Feb 25 01:07:30 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id BAA11672 for hackers-outgoing; Tue, 25 Feb 1997 01:07:30 -0800 (PST) Received: from engine3.dnet.net.id (engine3.dnet.net.id [202.148.1.212]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id BAA11667 for ; Tue, 25 Feb 1997 01:07:24 -0800 (PST) Received: from christ.dnet.net.id (as24port5.dnet.net.id [202.148.0.196]) by engine3.dnet.net.id (post.office MTA v1.9.3 ID# 0-13255) with ESMTP id AAA3905 for ; Tue, 25 Feb 1997 16:09:56 -0700 From: "CHRISTIANTO" To: Date: Tue, 25 Feb 1997 16:07:05 +0700 X-MSMail-Priority: Normal X-Priority: 3 X-Mailer: Microsoft Internet Mail 4.70.1155 MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Message-ID: <19970225230955.AAA3905@christ.dnet.net.id> Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk unsubscribe From owner-freebsd-hackers Tue Feb 25 01:21:34 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id BAA12433 for hackers-outgoing; Tue, 25 Feb 1997 01:21:34 -0800 (PST) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id BAA12424 for ; Tue, 25 Feb 1997 01:21:29 -0800 (PST) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id KAA14166 for freebsd-hackers@freefall.freebsd.org; Tue, 25 Feb 1997 10:21:27 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.8.5/8.8.5) id JAA04769; Tue, 25 Feb 1997 09:57:28 +0100 (MET) Message-ID: Date: Tue, 25 Feb 1997 09:57:26 +0100 From: j@uriah.heep.sax.de (J Wunsch) To: freebsd-hackers@freefall.freebsd.org Subject: Re: MALLOC(3) writes to stderr... References: <199702250755.QAA20017@sirius.sbl.cl.nec.co.jp> X-Mailer: Mutt 0.55-PL10 Mime-Version: 1.0 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199702250755.QAA20017@sirius.sbl.cl.nec.co.jp>; from Naoki Hamada on Feb 25, 1997 16:55:47 +0900 Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk As Naoki Hamada wrote: > Malloc(3) of 2.2-GAMMA writes error/warning messages to stderr. There > is a daemon named jserver, which provides translations between > Japanese characters, which does close stderr before opening its > dictionary files. Sometimes jserver gets its dictionary file > completely damaged by malloc's error/warning message. Hmm, i think it's a common misconception in Unix that everybody blindly assumes that file descriptors 0, 1, and 2 refer to stdin, stdout, and stderr respectively. OTOH, there's no opportunity for a library module to check where stderr really goes (or whether it has been closed). I bet malloc isn't the only library module that would write there. Your safest bet is to never close these descriptors, but redirect /dev/null on them. So, they remain `reserved'. Of course, you should also fix the malloc problems. Many people tend to use /etc/malloc.conf -> AJ these days, just for grins, and this would cause your daemon to fall over with a coredump, but with no indication for why it actually dumped core. (This also happened with inetd some day.) -- 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-hackers Tue Feb 25 01:36:54 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id BAA13213 for hackers-outgoing; Tue, 25 Feb 1997 01:36:54 -0800 (PST) Received: from engine3.dnet.net.id (engine3.dnet.net.id [202.148.1.212]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id BAA13203 for ; Tue, 25 Feb 1997 01:36:51 -0800 (PST) Received: from christ.dnet.net.id (as19port2.dnet.net.id [202.148.0.113]) by engine3.dnet.net.id (post.office MTA v1.9.3 ID# 0-13255) with ESMTP id AAA5627 for ; Tue, 25 Feb 1997 16:39:23 -0700 From: "CHRISTIANTO" To: Date: Tue, 25 Feb 1997 16:36:42 +0700 X-MSMail-Priority: Normal X-Priority: 3 X-Mailer: Microsoft Internet Mail 4.70.1155 MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Message-ID: <19970225233922.AAA5627@christ.dnet.net.id> Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk how to unsubcribe this mailis From owner-freebsd-hackers Tue Feb 25 02:33:51 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id CAA15559 for hackers-outgoing; Tue, 25 Feb 1997 02:33:51 -0800 (PST) Received: from main.gbdata.com (USR1-1.detnet.com [207.113.12.11]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id CAA15554 for ; Tue, 25 Feb 1997 02:33:47 -0800 (PST) Received: (from gclarkii@localhost) by main.gbdata.com (8.8.5/8.6.9) id EAA07458 for hackers@freebsd.org; Tue, 25 Feb 1997 04:33:42 -0600 (CST) From: Gary Clark II Message-Id: <199702251033.EAA07458@main.gbdata.com> Subject: TurboVision (new port) To: hackers@freebsd.org Date: Tue, 25 Feb 1997 04:33:41 -0600 (CST) X-Mailer: ELM [version 2.4ME+ PL22 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hello, Does anyone know where I can get the borland source for TV? My copy is old and has a different copyright (came with my Borland C++ back in '93). I have a fair amount of apps written with it and would like to port them BUT the unix port of TV is under the GPL so... Gary p.s. Anyone want to help? -- Gary Clark II (N5VMF) | I speak only for myself and "maybe" my company gclarkii@GBData.COM | Member of the FreeBSD Doc Team Providing Internet and ISP startups mail info@GBData.COM for information FreeBSD FAQ at ftp://ftp.FreeBSD.ORG/pub/FreeBSD/docs/freebsd-faq.ascii From owner-freebsd-hackers Tue Feb 25 03:19:22 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id DAA16811 for hackers-outgoing; Tue, 25 Feb 1997 03:19:22 -0800 (PST) Received: from coconut.blueberry.co.uk ([194.70.52.66]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id DAA16806 for ; Tue, 25 Feb 1997 03:19:17 -0800 (PST) Received: (from nik@localhost) by coconut.blueberry.co.uk (8.8.5/8.8.5) id LAA26653; Tue, 25 Feb 1997 11:17:42 GMT Message-ID: <19970225111742.05175@coconut.blueberry.co.uk> Date: Tue, 25 Feb 1997 11:17:42 +0000 From: Nik Clayton To: Joerg Wunsch Cc: Mark Mayo , Chris Shenton , hackers@FreeBSD.ORG Subject: Re: migrating 2.1.7 -> 2.2: simple or hairy? References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.61.1e Organization: Blueberry New Media In-Reply-To: ; from J Wunsch on Feb 02, 1997 at 08:35:58AM +0100 Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Feb 02, 1997 at 08:35:58AM +0100, J Wunsch wrote: > > > Don't forget your /etc updates... > > > > > Curious.. is /etc/ updated with a "src-all" line in the cvsup file? > > No. It will update /usr/src/etc, but (naturally) not /etc. > > You can wipe out your old /etc by > > cd /usr/src/etc > make distribution For more info about this, see the file FBSD_UPGRADE in /pub/FreeBSD/incoming, which is a write up of my recent experiences (I've submitted a PR asking for people to look at it (docs/2810), but I guess appealing to a wider audience isn't going to hurt. Comments and feedback welcome. N -- --+=[ Blueberry Hill Blueberry New Media ]=+-- --+=[ http://www.blueberry.co.uk/ 1/9 Chelsea Harbour Design Centre, ]=+-- --+=[ WebMaster@blueberry.co.uk London, England, SW10 0XE ]=+-- --+=[ It's good to talk. But it's better to do. ]ENTP From owner-freebsd-hackers Tue Feb 25 04:06:54 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id EAA18115 for hackers-outgoing; Tue, 25 Feb 1997 04:06:54 -0800 (PST) Received: from shadows.aeon.net (bsdhack@shadows.aeon.net [194.100.41.1]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id EAA18110 for ; Tue, 25 Feb 1997 04:06:49 -0800 (PST) Received: (from bsdhack@localhost) by shadows.aeon.net (8.8.5/8.8.3) id OAA14970; Tue, 25 Feb 1997 14:05:21 +0200 (EET) From: mika ruohotie Message-Id: <199702251205.OAA14970@shadows.aeon.net> Subject: Re: migrating 2.1.7 -> 2.2: simple or hairy? In-Reply-To: <199702241916.TAA13136@wirehead.it.hq.nasa.gov> from Chris Shenton at "Feb 24, 97 02:16:13 pm" To: cshenton@it.hq.nasa.gov (Chris Shenton) Date: Tue, 25 Feb 1997 14:05:21 +0200 (EET) Cc: hackers@freebsd.org X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > We've got a number of boxes running 2.1.7 and want to migrate to 2.2; > is it easy or hard? > Ideally I could do: > mv /usr/src /usr/src.old > cvsup -supfile [whatever's appropriate for 2.2] but cvsup is not part of ftp-released 2.1.7, actually any 2.1.x lacks it. i havent attempted yet, so i might ask stupid questions, but how hard is it to get CVSup into 2.1.7? (unlike in 2.1.6 the modula3 seems to be part of its /usr/ports) after upgrading my SUP to CVSup several weeks ago (finally, had to do it coz ftp.funet.fi dropped sup-services and it seemed to me sup was "dead" anyway) i'm really impressed. so i'd rather have that on 2.1.7 too... oh, and thanx from putting those nice addons to 2.1.7 (those that werent in the 2.1.6) mickey From owner-freebsd-hackers Tue Feb 25 04:07:18 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id EAA18139 for hackers-outgoing; Tue, 25 Feb 1997 04:07:18 -0800 (PST) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id EAA18132 for ; Tue, 25 Feb 1997 04:07:14 -0800 (PST) Received: (from msmith@localhost) by genesis.atrad.adelaide.edu.au (8.8.5/8.7.3) id WAA15748; Tue, 25 Feb 1997 22:37:08 +1030 (CST) From: Michael Smith Message-Id: <199702251207.WAA15748@genesis.atrad.adelaide.edu.au> Subject: Re: Static variables in shared libraries In-Reply-To: <3.0.1.32.19970225003040.00ff58e4@prognet.com> from Peter Haight at "Feb 25, 97 00:30:40 am" To: peterh@prognet.com (Peter Haight) Date: Tue, 25 Feb 1997 22:37:07 +1030 (CST) Cc: freebsd-hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL28 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Peter Haight stands accused of saying: > > Additionaly, does anyone know a good source of detailed information on the > implementation of shared libraries on various platforms? For FreeBSD, you could start with rtld(1) and link(5) -- ]] Mike Smith, Software Engineer msmith@gsoft.com.au [[ ]] Genesis Software genesis@gsoft.com.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control. (ph) +61-8-8267-3493 [[ ]] Unix hardware collector. "Where are your PEZ?" The Tick [[ From owner-freebsd-hackers Tue Feb 25 04:51:08 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id EAA20180 for hackers-outgoing; Tue, 25 Feb 1997 04:51:08 -0800 (PST) Received: from ns.extech.msk.su (ns.extech.msk.su [193.124.244.33]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id EAA20174; Tue, 25 Feb 1997 04:50:57 -0800 (PST) Received: from Shine.extech.msk.su (shine.extech.msk.su [193.124.244.35]) by ns.extech.msk.su (8.8.5/8.6.12) with ESMTP id PAA23045; Tue, 25 Feb 1997 15:53:19 +0300 (MSK) Message-Id: <199702251253.PAA23045@ns.extech.msk.su> From: "Vnotchenko S.S." To: , Subject: [H] Optimal computer for FreeBSD Date: Tue, 25 Feb 1997 15:53:17 +0300 X-MSMail-Priority: Normal X-Priority: 3 X-Mailer: Microsoft Internet Mail 4.70.1155 Sender: owner-hackers@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk Hi, all! My friends and I planing to use 2.1.7R-FreeBSD as main server (DNS,Web,INND,FTP) for ours ISP network. We want use something like this: PCI, Pentium-PRO ATX CPU, 64 Mb EDO RAM, 2x4.5 Gb SCSI, 8x SCSI CD-ROM, 10Mbit Ethernet. Please, recommend us hardware (firm, model) known as best (reliable, fast) working under 2.1.7R-FreeBSD (PCI devices if possible). --- CPU: Motherboard: SCSI Host adapter: SCSI Hard drives: SCSI CD-ROM: Ethernet card: --- Thanks in advance, Sergey (sergey@extech.msk.su). From owner-freebsd-hackers Tue Feb 25 05:02:12 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id FAA20533 for hackers-outgoing; Tue, 25 Feb 1997 05:02:12 -0800 (PST) Received: from parkplace.cet.co.jp (parkplace.cet.co.jp [202.32.64.1]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id FAA20525 for ; Tue, 25 Feb 1997 05:02:05 -0800 (PST) Received: from localhost (michaelh@localhost) by parkplace.cet.co.jp (8.8.5/CET-v2.1) with SMTP id NAA13943; Tue, 25 Feb 1997 13:01:57 GMT Date: Tue, 25 Feb 1997 22:01:57 +0900 (JST) From: Michael Hancock Reply-To: Michael Hancock To: Peter Haight cc: freebsd-hackers@freebsd.org Subject: Re: Static variables in shared libraries In-Reply-To: <3.0.1.32.19970225003040.00ff58e4@prognet.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Tue, 25 Feb 1997, Peter Haight wrote: > I have a shared library which has the following definitions: > > const char* test_3 = "hello"; > const char* test_4 = test_3; > > If I dynamically load this shared library in my program and print the > variables, I get: > test_3 = "hello" > test_4 = 0x0 > > What's going on? Try news:comp.lang.c. "The C book" is also a necessity. For good jump start, also get "Expert C Programming" from SunPress. It has a coelancanth on the cover. Regards, Mike Hancock From owner-freebsd-hackers Tue Feb 25 05:20:41 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id FAA21023 for hackers-outgoing; Tue, 25 Feb 1997 05:20:41 -0800 (PST) Received: from dg-rtp.dg.com (dg-rtp.rtp.dg.com [128.222.1.2]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id FAA21017 for ; Tue, 25 Feb 1997 05:20:34 -0800 (PST) Received: by dg-rtp.dg.com (5.4R3.10/dg-rtp-v02) id AA06823; Tue, 25 Feb 1997 08:20:02 -0500 Received: from ponds by dg-rtp.dg.com.rtp.dg.com; Tue, 25 Feb 1997 08:20 EST Received: from lakes.water.net (lakes [10.0.0.3]) by ponds.water.net (8.8.3/8.7.3) with ESMTP id HAA00195 for ; Tue, 25 Feb 1997 07:39:17 -0500 (EST) Received: (from rivers@localhost) by lakes.water.net (8.8.3/8.6.9) id HAA17617 for freebsd-hackers@freefall.cdrom.com; Tue, 25 Feb 1997 07:44:30 -0500 (EST) Date: Tue, 25 Feb 1997 07:44:30 -0500 (EST) From: Thomas David Rivers Message-Id: <199702251244.HAA17617@lakes.water.net> To: ponds!freefall.cdrom.com!freebsd-hackers Subject: Today's "dup alloc" panic. Content-Type: text Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Just for logging information to the mail archives; today's "dup alloc" panic turned out to be a "bad dir" panic. I know there are several bugs in gnats that reference a "bad dir" panic on news servers... this is just some anectdotal evidence that the problems are likely the same. - Dave Rivers - From owner-freebsd-hackers Tue Feb 25 05:26:57 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id FAA21161 for hackers-outgoing; Tue, 25 Feb 1997 05:26:57 -0800 (PST) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id FAA21156 for ; Tue, 25 Feb 1997 05:26:50 -0800 (PST) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.3/8.6.9) id AAA10544; Wed, 26 Feb 1997 00:25:57 +1100 Date: Wed, 26 Feb 1997 00:25:57 +1100 From: Bruce Evans Message-Id: <199702251325.AAA10544@godzilla.zeta.org.au> To: bde@zeta.org.au, rhh@ct.picker.com Subject: Re: dd of=/dev/rwd1s2 -- How? Cc: hackers@FreeBSD.ORG Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > |Remove the BSD label from the slice. This isn't easy. IIRC, the easiest > |way is to corrupt the label by writing to it via /dev/rwd1. This exploits > |a bug in the write protection. > |... >I would have thought this would have been easier. It should have been. >I lost my root partition with 2.2-ALPHA Saturday due to it overwriting the >boot record and the FreeBSD boot blocks on my root partition (wd1s3), so >some piece of code got permission to do this, and given that my other >partitions are fine, I wouldn't guess it was via /dev/rwd1. There's an ioctl to do it. Writing directly to the label sector works provided this ioctl is issued and a valid label is written, at least if writing the label would not cause an open partition to move or shrink. You can arrange this for copying partitions something like this: 1. Edit the label on the target to make it identical with the label on the source. This can be difficult if the normal label partition (`c') would move or shrink. The disklabel man page has a hint about what to do: add a dummy partition starting at offset 0 with length >= 2 and run disklabel on that. 2. Keep a device on drive open using something like `cat /dev/rwd1 >/dev/null' followed by ^Z. 3. Disable write protection using disklabel -N. >Will changing the slice type to something other than A5 with fdisk give me >write access on rwd1s3 again? It would make sense -- FreeBSD magic >shouldn't be checked for in a non-FreeBSD slice. No, FreeBSD only uses the type byte for deciding where the compatibility slice is. The label has magic numbers and a checksum so it can be relied on more than the type byte. >Speaking of my 2.2-ALPHA corruption, I don't know if this bug has been >fixed or not in 2.2-GAMMA, but is there a person I should mail a MIMEd copy >of the 1st 16k or so of my corrupted image to. It looks like the >corruption is limited to that section, and the content might gives some >clues as to the bug at work. (I saved off the whole partition in hopes of >being able to re-disklabel it, without success I'm afraid). You can send a uuencoded copy of it to me. Bruce From owner-freebsd-hackers Tue Feb 25 05:28:43 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id FAA21254 for hackers-outgoing; Tue, 25 Feb 1997 05:28:43 -0800 (PST) Received: from narcissus.ml.org (root@brosenga.Pitzer.edu [134.173.120.201]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id FAA21249 for ; Tue, 25 Feb 1997 05:28:41 -0800 (PST) Received: from localhost (ben@localhost) by narcissus.ml.org (8.7.5/8.7.3) with SMTP id FAA03166; Tue, 25 Feb 1997 05:28:09 -0800 (PST) Date: Tue, 25 Feb 1997 05:28:09 -0800 (PST) From: Snob Art Genre To: "Vnotchenko S.S." cc: freebsd-hackers@FreeBSD.org Subject: Re: [H] Optimal computer for FreeBSD In-Reply-To: <199702251253.PAA23045@ns.extech.msk.su> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk On Tue, 25 Feb 1997, Vnotchenko S.S. wrote: > Hi, all! > My friends and I planing to use 2.1.7R-FreeBSD as main server > (DNS,Web,INND,FTP) for ours ISP network. > We want use something like this: PCI, Pentium-PRO ATX CPU, 64 Mb EDO RAM, > 2x4.5 Gb SCSI, > 8x SCSI CD-ROM, 10Mbit Ethernet. Please, recommend us hardware (firm, > model) known as best > (reliable, fast) working under 2.1.7R-FreeBSD (PCI devices if possible). I've had a really good experience with my Micron Millenia Pro Plus. > > --- > CPU: PPro-200 > Motherboard: ATX w/Intel 440FX, as far as I can tell. > SCSI Host adapter: Buslogic BT-948. Its reliability hasn't been perfect, but I don't really have a standard of comparison, as it's the only SCSI host adapter I've ever owned. > SCSI Hard drives: Conner CFP2107S > SCSI CD-ROM: Plextor 8plex internal > Ethernet card: Cheap generic NE2000, probably the least problematic piece of hardware in my system (and it's not a problematic system). > --- > > Thanks in advance, Sergey (sergey@extech.msk.su). > > > > Ben "You have your mind on computers, it seems." From owner-freebsd-hackers Tue Feb 25 05:36:19 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id FAA21640 for hackers-outgoing; Tue, 25 Feb 1997 05:36:19 -0800 (PST) Received: from who.cdrom.com (who.cdrom.com [204.216.27.3]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id FAA21619; Tue, 25 Feb 1997 05:36:15 -0800 (PST) Received: from deepo.prosa.dk ([193.89.187.27]) by who.cdrom.com (8.7.5/8.6.11) with ESMTP id FAA12379 ; Tue, 25 Feb 1997 05:36:11 -0800 (PST) Received: (from regnauld@localhost) by deepo.prosa.dk (8.8.5/8.8.4/prosa-1.1) id OAA09291; Tue, 25 Feb 1997 14:37:34 +0100 (CET) Message-ID: Date: Tue, 25 Feb 1997 14:37:33 +0100 From: regnauld@deepo.prosa.dk (Philippe Regnauld) To: sergey@extech.msk.su (Vnotchenko S.S.) Cc: freebsd-hackers@freebsd.org, freebsd-isp@freebsd.org Subject: Re: [H] Optimal computer for FreeBSD References: <199702251253.PAA23045@ns.extech.msk.su> X-Mailer: Mutt 0.58 Mime-Version: 1.0 X-Operating-System: FreeBSD 2.2-BETA_A i386 In-Reply-To: <199702251253.PAA23045@ns.extech.msk.su>; from Vnotchenko S.S. on Feb 25, 1997 15:53:17 +0300 Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Vnotchenko S.S. (sergey) ecrit/writes: > (reliable, fast) working under 2.1.7R-FreeBSD (PCI devices if possible). > > --- > CPU: No choice: Intel. A round multiple of the board clock. > Motherboard: Asus / Tyan / Giga-byte. Asys has a very good rep. They also all offer an SMP version of their MB's (planning for FreeBSD-SMP :-). They have 4 ISA and 4 PCI if you look for the right one. > SCSI Host adapter: Several NCR 53c8xx is a _very_ good choice -- like 2 controllers (1~2 disks / controller, and use ccd across 2/3 disks for news spool = 10-15 Mb / sec!). PCI. > SCSI Hard drives: Whatever you feel comfortable with. > SCSI CD-ROM: Plextor ? NEC ? Some people hate Sony. > Ethernet card: DEC chipsets, 10 or 100, 100 is cheaper and cheaper. 3Com is a very good card, worth the extra bucks. Both come in PCI. > Thanks in advance, Sergey (sergey@extech.msk.su). For generally top-level tips, see the list archives, search for 'Joe Greco', 'ccd', 'news server' :-))) -- Phil -- -[ Philippe Regnauld / Systems Administrator / regnauld@prosa.dk ]- -[ Location.: +55.4N +11.3E PGP Key: finger regnauld@deepo.prosa.dk ]- From owner-freebsd-hackers Tue Feb 25 05:46:52 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id FAA22073 for hackers-outgoing; Tue, 25 Feb 1997 05:46:52 -0800 (PST) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id FAA22067 for ; Tue, 25 Feb 1997 05:46:47 -0800 (PST) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.3/8.6.9) id AAA10884; Wed, 26 Feb 1997 00:42:13 +1100 Date: Wed, 26 Feb 1997 00:42:13 +1100 From: Bruce Evans Message-Id: <199702251342.AAA10884@godzilla.zeta.org.au> To: freebsd-hackers@freefall.freebsd.org, nao@sbl.cl.nec.co.jp Subject: Re: MALLOC(3) writes to stderr... Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >How should we deal with this anomaly? Yep, fixing jserver's memory >allocation thoroughly might be the ultimate solution, but we need a >practical solution for now. Must we change jserver to keep stderr open >and to put error messages into /var/log/jserver.log or something? Or >make malloc(3) keep silent? Library routines shouldn't write to std* unless instructed to. There should be a malloc option to control the behaviour. However, malloc() only seems to print to stderr after severe errors that might have caused a core dump on other systems. Bruce From owner-freebsd-hackers Tue Feb 25 05:50:37 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id FAA22303 for hackers-outgoing; Tue, 25 Feb 1997 05:50:37 -0800 (PST) Received: from dg-rtp.dg.com (dg-rtp.rtp.dg.com [128.222.1.2]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id FAA22298 for ; Tue, 25 Feb 1997 05:50:35 -0800 (PST) Received: by dg-rtp.dg.com (5.4R3.10/dg-rtp-v02) id AA09324; Tue, 25 Feb 1997 08:50:01 -0500 Received: from ponds by dg-rtp.dg.com.rtp.dg.com; Tue, 25 Feb 1997 08:50 EST Received: from lakes.water.net (lakes [10.0.0.3]) by ponds.water.net (8.8.3/8.7.3) with ESMTP id IAA00509 for ; Tue, 25 Feb 1997 08:03:43 -0500 (EST) Received: (from rivers@localhost) by lakes.water.net (8.8.3/8.6.9) id HAA17612 for freebsd-hackers@freefall.cdrom.com; Tue, 25 Feb 1997 07:41:59 -0500 (EST) Date: Tue, 25 Feb 1997 07:41:59 -0500 (EST) From: Thomas David Rivers Message-Id: <199702251241.HAA17612@lakes.water.net> To: ponds!freefall.cdrom.com!freebsd-hackers Subject: The situation isn't getting better... (dup alloc) Content-Type: text Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Well - I've been experiencing my dup alloc panic's on my news server consistently for several days now. Unfortunately, the panic's are coming a just the right moment so as to wreck the most havoc with the file system... it's getting to where I can't keep up. Now, I've been down this road before - if I just clear everything out and re-install, things will be fantastic for about a month, with a predictable degradation into the sad state I currently find myself (hmmm... back-sliding?) I've not really made any progress in the past few days on determining just where things are wrong - but I didn't want this issue to simply fade away, or I didn't want people to think I wasn't persuing it any longer... I'm still *very* interested in resolving this. - Dave Rivers - From owner-freebsd-hackers Tue Feb 25 05:53:24 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id FAA22407 for hackers-outgoing; Tue, 25 Feb 1997 05:53:24 -0800 (PST) Received: from coconut.blueberry.co.uk ([194.70.52.66]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id FAA22402 for ; Tue, 25 Feb 1997 05:53:05 -0800 (PST) Received: (from nik@localhost) by coconut.blueberry.co.uk (8.8.5/8.8.5) id NAA27425; Tue, 25 Feb 1997 13:51:53 GMT Message-ID: <19970225135153.39368@coconut.blueberry.co.uk> Date: Tue, 25 Feb 1997 13:51:53 +0000 From: Nik Clayton To: mika ruohotie Cc: Chris Shenton , hackers@freebsd.org Subject: Re: migrating 2.1.7 -> 2.2: simple or hairy? References: <199702241916.TAA13136@wirehead.it.hq.nasa.gov> <199702251205.OAA14970@shadows.aeon.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.61.1e Organization: Blueberry New Media In-Reply-To: <199702251205.OAA14970@shadows.aeon.net>; from mika ruohotie on Feb 02, 1997 at 02:05:21PM +0200 Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Feb 02, 1997 at 02:05:21PM +0200, mika ruohotie wrote: > i havent attempted yet, so i might ask stupid questions, but how hard is it > to get CVSup into 2.1.7? (unlike in 2.1.6 the modula3 seems to be part of its > /usr/ports) Very trivial. Download ftp://freefall.freebsd.org/pub/CVSup/cvsup-bin-14.1.1.tar.gz which is the statically linked client mentioned in http://www.freebsd.org/handbook/handbook238.html#479 and install this. Build yourself a sup file and away you go. Round of applause to all involved, I was very impressed with how easy it was. N -- --+=[ Blueberry Hill Blueberry New Media ]=+-- --+=[ http://www.blueberry.co.uk/ 1/9 Chelsea Harbour Design Centre, ]=+-- --+=[ WebMaster@blueberry.co.uk London, England, SW10 0XE ]=+-- --+=[ It's good to talk. But it's better to do. ]ENTP From owner-freebsd-hackers Tue Feb 25 06:07:53 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id GAA23206 for hackers-outgoing; Tue, 25 Feb 1997 06:07:53 -0800 (PST) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id GAA23201 for ; Tue, 25 Feb 1997 06:07:49 -0800 (PST) Received: from time.cdrom.com (jkh@localhost [127.0.0.1]) by time.cdrom.com (8.8.5/8.6.9) with ESMTP id GAA12001; Tue, 25 Feb 1997 06:07:09 -0800 (PST) To: Gary Clark II cc: hackers@freebsd.org Subject: Re: TurboVision (new port) In-reply-to: Your message of "Tue, 25 Feb 1997 04:33:41 CST." <199702251033.EAA07458@main.gbdata.com> Date: Tue, 25 Feb 1997 06:07:09 -0800 Message-ID: <11997.856879629@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Did you consider trying to plead with the author for an alternate copyright, ala PERL with its GPL and "Artistic" copyrights? I think a fair bit of work was put into converting it from a DOS screen I/O paradigm to an ncurses one, and I doubt you'd want to redo it! Jordan > Hello, > > Does anyone know where I can get the borland source for TV? My copy > is old and has a different copyright (came with my Borland C++ back in '93). > > I have a fair amount of apps written with it and would like to port them > BUT the unix port of TV is under the GPL so... > > Gary > > p.s. Anyone want to help? > > -- > Gary Clark II (N5VMF) | I speak only for myself and "maybe" my company > gclarkii@GBData.COM | Member of the FreeBSD Doc Team > Providing Internet and ISP startups mail info@GBData.COM for information > FreeBSD FAQ at ftp://ftp.FreeBSD.ORG/pub/FreeBSD/docs/freebsd-faq.ascii From owner-freebsd-hackers Tue Feb 25 06:22:03 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id GAA24032 for hackers-outgoing; Tue, 25 Feb 1997 06:22:03 -0800 (PST) Received: from seine.cs.umd.edu (10862@seine.cs.umd.edu [128.8.128.59]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id GAA24025 for ; Tue, 25 Feb 1997 06:21:58 -0800 (PST) Received: by seine.cs.umd.edu (8.8.5/UMIACS-0.9/04-05-88) id JAA12173; Tue, 25 Feb 1997 09:21:56 -0500 (EST) Message-Id: <199702251421.JAA12173@seine.cs.umd.edu> To: freebsd-hackers@freebsd.org cc: rohit@cs.umd.edu Subject: Ethernet-like interface statistics and ioctl/sysctl Date: Tue, 25 Feb 1997 09:21:55 -0500 From: Rohit Dube Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi, I am reposting this as I haven't yet received any responses. I would appreciate it if you could mail me directly on the current state of the sysctl interface or the dot3 (ifmib_iso_8802_3) statistics. Thanks. --rohit. [Re-post] Hi, I was wondering if any version of FreeBSD had an ioctl or sysctl interface for collecting the dot3* (ethernet like) statistics from ethernet drivers (allingnment errors, collisions etc). I am looking 2.2 code and man pages. The 'de' drivers seems to maintain the correct (RFC 1643/1650) statistics, but I can't find an interface which exports these to user land in the man pages or in the code. Anybody care to comment on the current or coming support? Or if it already exists, how to access it (ie the ioctl or the sysctl parameters or pointers to docs or code.) Thanks in advance. --rohit. PS: I saw a message in the archives posing a similar question on Jan 4, 1997 but no answers. From owner-freebsd-hackers Tue Feb 25 08:11:15 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id IAA29295 for hackers-outgoing; Tue, 25 Feb 1997 08:11:15 -0800 (PST) Received: from cheops.anu.edu.au (avalon@cheops.anu.edu.au [150.203.76.24]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id IAA29184 for ; Tue, 25 Feb 1997 08:11:09 -0800 (PST) Message-Id: <199702251611.IAA29184@freefall.freebsd.org> Received: by cheops.anu.edu.au (1.37.109.16/16.2) id AA181826895; Wed, 26 Feb 1997 03:08:15 +1100 From: Darren Reed Subject: sysinstall & disk labelling. To: hackers@freebsd.org Date: Wed, 26 Feb 1997 03:08:15 +1100 (EDT) X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Can I mention that the disk labelling which happened straight after you had partitioned was actually very useful ? It appears to now occur at some other time ? Darren From owner-freebsd-hackers Tue Feb 25 08:33:58 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id IAA00590 for hackers-outgoing; Tue, 25 Feb 1997 08:33:58 -0800 (PST) Received: from superior.truenorth.org (ppp011-sm2.sirius.com [205.134.231.11]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id IAA00574; Tue, 25 Feb 1997 08:33:27 -0800 (PST) Received: (from jgrosch@localhost) by superior.truenorth.org (8.8.5/8.7.3) id IAA03327; Tue, 25 Feb 1997 08:31:54 -0800 (PST) From: Josef Grosch Message-Id: <199702251631.IAA03327@superior.truenorth.org> Subject: Re: [H] Optimal computer for FreeBSD In-Reply-To: <199702251253.PAA23045@ns.extech.msk.su> from "Vnotchenko S.S." at "Feb 25, 97 03:53:17 pm" To: sergey@extech.msk.su (Vnotchenko S.S.) Date: Tue, 25 Feb 1997 08:31:53 -0800 (PST) Cc: freebsd-isp@freebsd.org, freebsd-hackers@freebsd.org Reply-To: jgrosch@sirius.com X-Mailer: ELM [version 2.4ME+ PL28 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >Hi, all! >My friends and I planing to use 2.1.7R-FreeBSD as main server >(DNS,Web,INND,FTP) for ours ISP network. >We want use something like this: PCI, Pentium-PRO ATX CPU, 64 Mb EDO RAM, >2x4.5 Gb SCSI, >8x SCSI CD-ROM, 10Mbit Ethernet. Please, recommend us hardware (firm, >model) known as best >(reliable, fast) working under 2.1.7R-FreeBSD (PCI devices if possible). > >--- >CPU: Intel 133Mhz. are a goof buy now. 200Mhz are damn pricey >Motherboard: Asus Motherboards are very good. I have never heard anything bad about them. Make sure the chip set is a Triton-II (Intel's 430HX PCIset) >SCSI Host adapter: I have had very good luck with Adaptec controllers. The 2940 is a very good PCI SCSI controller. >SCSI Hard drives: I have good luck with seagate drives. Others may tell you different. >SCSI CD-ROM: Do you really need 8X speed? If you are just using the CD-ROM drive to pull data off a CD save your money and buy a 4X. I have had good luck with my NEC. >Ethernet card: I have a cheapo NE2000 clone. The DEC PCI ethernet cards are very good. Josef -- Josef Grosch | Laugh while you can, monkey boy ! | FreeBSD 2.1.6 jgrosch@sirius.com | - John Warfin - | UNIX for the masses From owner-freebsd-hackers Tue Feb 25 08:47:12 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id IAA01391 for hackers-outgoing; Tue, 25 Feb 1997 08:47:12 -0800 (PST) Received: from coconut.blueberry.co.uk ([194.70.52.66]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id IAA01386 for ; Tue, 25 Feb 1997 08:47:06 -0800 (PST) Received: (from nik@localhost) by coconut.blueberry.co.uk (8.8.5/8.8.5) id QAA28362; Tue, 25 Feb 1997 16:46:35 GMT Message-ID: <19970225164635.47646@coconut.blueberry.co.uk> Date: Tue, 25 Feb 1997 16:46:35 +0000 From: Nik Clayton To: hackers@freebsd.org Subject: 2.1.7: ncr and de driver increasingly fickle Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.61.1e Organization: Blueberry New Media Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi, Has anyone else noticed an increased fickleness on 2.1.7 with the ncr and the de drivers? On my 2.1.5 system, I never heard a complaint from the de driver, and the ncr driver might occasionally complain /kernel: sd1(ncr0:1:0): extraneous data discarded. during one of the nightly backups. But now it's happening more frequently. In addition, the de driver is sometimes complaining (particularly on system startup) /kernel: de0: abnormal interrupt: receive process stopped I'm not that fussed about these, as they don't seem to be leading to loss of data, but it's intriguing. This is on a 2.1.7 system, 200MHz P6, 64MB, PCI. The devices in question are de0 rev 17 int a irq 10 on pci0:10 and ncr0 rev 2 int a irq 11 on pc i0:12 (ncr0:0:0): "FUJITSU M2952S-512 0124" type 0 fixed SCSI 2 sd0(ncr0:0:0): Direct-Access sd0(ncr0:0:0): FAST SCSI-2 100ns (10 Mb/sec) offset 8. N -- --+=[ Blueberry Hill Blueberry New Media ]=+-- --+=[ http://www.blueberry.co.uk/ 1/9 Chelsea Harbour Design Centre, ]=+-- --+=[ WebMaster@blueberry.co.uk London, England, SW10 0XE ]=+-- --+=[ It's good to talk. But it's better to do. ]ENTP From owner-freebsd-hackers Tue Feb 25 08:48:47 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id IAA01580 for hackers-outgoing; Tue, 25 Feb 1997 08:48:47 -0800 (PST) Received: from chai.plexuscom.com (chai.plexuscom.com [207.87.46.100]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id IAA01575 for ; Tue, 25 Feb 1997 08:48:41 -0800 (PST) Received: from chai.plexuscom.com (localhost [127.0.0.1]) by chai.plexuscom.com (8.8.5/8.6.12) with ESMTP id LAA01376; Tue, 25 Feb 1997 11:50:22 -0500 (EST) Message-Id: <199702251650.LAA01376@chai.plexuscom.com> To: Peter Haight Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Static variables in shared libraries In-reply-to: Your message of "Tue, 25 Feb 1997 00:30:40 PST." <3.0.1.32.19970225003040.00ff58e4@prognet.com> Date: Tue, 25 Feb 1997 11:50:21 -0500 From: Bakul Shah Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > I have a shared library which has the following definitions: > > const char* test_3 = "hello"; > const char* test_4 = test_3; > > If I dynamically load this shared library in my program and print the > variables, I get: > test_3 = "hello" > test_4 = 0x0 > > What's going on? May be shlib linking is broken? > Additionaly, does anyone know a good source of detailed information on the > implementation of shared libraries on various platforms? Other than reading code and man pages, you may want to check out old usenix conference proceedings. Try www.usenix.org to look up which proceedings (if you are a member you can pull off papers). The UW library may also have them. -- bakul From owner-freebsd-hackers Tue Feb 25 09:03:23 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id JAA02221 for hackers-outgoing; Tue, 25 Feb 1997 09:03:23 -0800 (PST) Received: from horst.bfd.com (horst.bfd.com [204.160.242.10]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id JAA02213; Tue, 25 Feb 1997 09:03:20 -0800 (PST) Received: from harlie.bfd.com (bastion.bfd.com [204.160.242.14]) by horst.bfd.com (8.8.5/8.7.3) with SMTP id JAA27449; Tue, 25 Feb 1997 09:02:24 -0800 (PST) Date: Tue, 25 Feb 1997 09:02:24 -0800 (PST) From: "Eric J. Schwertfeger" To: "Vnotchenko S.S." cc: freebsd-isp@FreeBSD.org, freebsd-hackers@FreeBSD.org Subject: Re: [H] Optimal computer for FreeBSD In-Reply-To: <199702251253.PAA23045@ns.extech.msk.su> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk On Tue, 25 Feb 1997, Vnotchenko S.S. wrote: > Hi, all! > My friends and I planing to use 2.1.7R-FreeBSD as main server > (DNS,Web,INND,FTP) for ours ISP network. > We want use something like this: PCI, Pentium-PRO ATX CPU, 64 Mb EDO RAM, > 2x4.5 Gb SCSI, > 8x SCSI CD-ROM, 10Mbit Ethernet. Please, recommend us hardware (firm, > model) known as best > (reliable, fast) working under 2.1.7R-FreeBSD (PCI devices if possible). I'm sure others will recommend 4x2Gb scsi instead. My personal recomendation would be an AHA2940UW, with 2Gb ultrawide drives (IBM makes some good, and suprizingly inexpensive drives in this category). For 10MBit ethernet, I'd recommend something based on the DEC 21041AC. They're fast (only dropped 10 packets out of a million packet flood ping, FTP rages >1MB/Sec), cheap (found mine for $35), and work well with the de driver. Video depends on what you want to use the computer for. If it's an X workstation, look for one of the good accellerated chipsets. Stay away from the S3 Virge chipset if you want to use truecolor (for java, etc), because the XFree Virge drivers are still under development. If this is only going to be a server sitting at the console most of the time, Just about anything will work well. From owner-freebsd-hackers Tue Feb 25 09:06:45 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id JAA02455 for hackers-outgoing; Tue, 25 Feb 1997 09:06:45 -0800 (PST) Received: from minnow.render.com (render.demon.co.uk [158.152.30.118]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id JAA02449 for ; Tue, 25 Feb 1997 09:06:40 -0800 (PST) Received: (from dfr@localhost) by minnow.render.com (8.6.12/8.6.9) id RAA13306; Tue, 25 Feb 1997 17:01:21 GMT To: freebsd-hackers@freebsd.org Subject: FreeBSD advert From: Doug Rabson Date: 25 Feb 1997 17:01:18 +0000 In-Reply-To: Mail Delivery Subsystem's message of Tue, 25 Feb 1997 16:50:30 GMT Message-ID: Lines: 8 X-Mailer: Gnus v5.2.25/XEmacs 19.14 Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I was just surprised to see a FreeBSD advert on Yahoo. That was a pretty cool idea of someone (Jordan?). I hope we can look forward to seeing more of this kind of exposure. -- Doug Rabson, Microsoft RenderMorphics Ltd. Mail: dfr@render.com Phone: +44 171 734 3761 These are not the opinions of Microsoft. FAX: +44 171 734 6426 From owner-freebsd-hackers Tue Feb 25 09:59:04 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id JAA05537 for hackers-outgoing; Tue, 25 Feb 1997 09:59:04 -0800 (PST) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.50]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id JAA05531 for ; Tue, 25 Feb 1997 09:59:01 -0800 (PST) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id KAA26679; Tue, 25 Feb 1997 10:56:01 -0700 From: Terry Lambert Message-Id: <199702251756.KAA26679@phaeton.artisoft.com> Subject: Re: MALLOC(3) writes to stderr... To: nao@sbl.cl.nec.co.jp (Naoki Hamada) Date: Tue, 25 Feb 1997 10:56:01 -0700 (MST) Cc: freebsd-hackers@freefall.freebsd.org In-Reply-To: <199702250755.QAA20017@sirius.sbl.cl.nec.co.jp> from "Naoki Hamada" at Feb 25, 97 04:55:47 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-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > Malloc(3) of 2.2-GAMMA writes error/warning messages to stderr. There > is a daemon named jserver, which provides translations between > Japanese characters, which does close stderr before opening its > dictionary files. Sometimes jserver gets its dictionary file > completely damaged by malloc's error/warning message. malloc should use stderr itself, or it should user fileno(stderr) whereever it is using a manifest 2. If malloc is already doing this, then the error is in closing the descriptor for stderr without closing the file pointer. Output to a closes descriptor or a closed file pointer should return an error to the writer -- EBADF for a bad descriptor or stream (man 2 write, man 2 close, man 2 fclose). I suspect file streams are not correctly invalidated on close in the current implementation. > How should we deal with this anomaly? Yep, fixing jserver's memory > allocation thoroughly might be the ultimate solution, but we need a > practical solution for now. Must we change jserver to keep stderr open > and to put error messages into /var/log/jserver.log or something? Or > make malloc(3) keep silent? Close stderr instead of closing descriptor 2. Correct file pointer using library routines, as necessary. 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-hackers Tue Feb 25 10:04:36 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id KAA06006 for hackers-outgoing; Tue, 25 Feb 1997 10:04:36 -0800 (PST) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.50]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id KAA05998 for ; Tue, 25 Feb 1997 10:04:32 -0800 (PST) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id LAA26691; Tue, 25 Feb 1997 11:01:23 -0700 From: Terry Lambert Message-Id: <199702251801.LAA26691@phaeton.artisoft.com> Subject: Re: Static variables in shared libraries To: bakul@torrentnet.com (Bakul Shah) Date: Tue, 25 Feb 1997 11:01:23 -0700 (MST) Cc: peterh@prognet.com, freebsd-hackers@FreeBSD.ORG In-Reply-To: <199702251650.LAA01376@chai.plexuscom.com> from "Bakul Shah" at Feb 25, 97 11:50:21 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-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > I have a shared library which has the following definitions: > > > > const char* test_3 = "hello"; > > const char* test_4 = test_3; > > > > If I dynamically load this shared library in my program and print the > > variables, I get: > > test_3 = "hello" > > test_4 = 0x0 > > > > What's going on? > > May be shlib linking is broken? Looks more like an agregate initialization problem with consts not being treated as fixed addresses by the compiler the way strings are... in other words, a compiler or linker bug resolving the test_4 address to the address of the agregate initialized data containing the string "hello", and the same address as it resolved test_3 to. On wonder why you want to establish a const alias, actually. The const definition implies noalias. 8-|. 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-hackers Tue Feb 25 10:33:10 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id KAA07361 for hackers-outgoing; Tue, 25 Feb 1997 10:33:10 -0800 (PST) Received: from ns.newreach.net (root@ns.newreach.net [206.25.170.1]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id KAA07350 for ; Tue, 25 Feb 1997 10:32:59 -0800 (PST) Received: from phoenix.aristar.com (inetgw.aristar.com [206.25.171.180]) by ns.newreach.net (8.8.4/8.6.9) with SMTP id NAA13618 for ; Tue, 25 Feb 1997 13:32:51 -0500 (EST) Message-ID: <3313307E.41C67EA6@aristar.com> Date: Tue, 25 Feb 1997 13:33:34 -0500 From: "Matthew A. Gessner" Organization: Aristar, Inc. X-Mailer: Mozilla 3.01Gold (X11; I; FreeBSD 2.1.0-RELEASE i386) MIME-Version: 1.0 To: hackers Subject: Writing a daemon... Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hello, hackers, I'm looking for some really good information on writing a daemon for a) FreeBSD and b) DEC ALPHA OSF/1. I've got Stevens' _Unix_Network_Programming_, and have read that, but in the past have had some problems getting the code to compile properly under FreeBSD. I just want to make sure that nothing's really 'changed' in the 'art' of daemon writing since his book was published. If anyone can add any tips or recommendations (specifically, if anyone has a good source for OSF), please let me know. Maybe you're wondering why I'm doing this? I'll explain quickly. Stevens has a socket server example in his book. It runs fine on FreeBSD, but under OSF, when the first client disconnects, accept() keeps returning a new socket for the old IP address. In /usr/examples/network_programming, I found a file called socketserver.c. The only, ONLY, _O_N_L_Y_ difference in calls is that when the child terminates, it calls return(0) instead of exit(0). Don't you know, that made ALL the difference. Why? "Don't know; can't tell ya." So I'm a little bit suspicious. Thanks, folks, Matt -- Matthew Gessner, Computer Scientist, Aristar, Inc. 302 N. Cleveland-Massillon Rd. Akron, OH 44333 Voice (330) 668-2267, Fax (330) 668-2961 From owner-freebsd-hackers Tue Feb 25 10:38:23 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id KAA07568 for hackers-outgoing; Tue, 25 Feb 1997 10:38:23 -0800 (PST) Received: from misery.sdf.com (misery.sdf.com [204.244.210.193]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id KAA07549; Tue, 25 Feb 1997 10:38:17 -0800 (PST) Received: from misery.sdf.com [204.244.213.33] by misery.sdf.com with smtp (Exim 1.59 #1) id 0vzJzG-0000Xa-00; Tue, 25 Feb 1997 02:19:54 -0800 Date: Tue, 25 Feb 1997 02:19:53 -0800 (PST) From: Tom Samplonius To: "Vnotchenko S.S." cc: freebsd-isp@freebsd.org, freebsd-hackers@freebsd.org Subject: Re: [H] Optimal computer for FreeBSD In-Reply-To: <199702251253.PAA23045@ns.extech.msk.su> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Tue, 25 Feb 1997, Vnotchenko S.S. wrote: ... > We want use something like this: PCI, Pentium-PRO ATX CPU, 64 Mb EDO RAM, ... Always use parity RAM on servers, especially if you are buying everything from scratch. EDO doesn't give you much of a improvement if your motherboard supports pipeline-burst-cache. Tom From owner-freebsd-hackers Tue Feb 25 10:49:36 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id KAA08076 for hackers-outgoing; Tue, 25 Feb 1997 10:49:36 -0800 (PST) Received: from misery.sdf.com (misery.sdf.com [204.244.210.193]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id KAA08064 for ; Tue, 25 Feb 1997 10:49:33 -0800 (PST) Received: from misery.sdf.com [204.244.213.33] by misery.sdf.com with smtp (Exim 1.59 #1) id 0vzKA9-0000ZO-00; Tue, 25 Feb 1997 02:31:09 -0800 Date: Tue, 25 Feb 1997 02:31:09 -0800 (PST) From: Tom Samplonius To: Snob Art Genre cc: "Vnotchenko S.S." , freebsd-hackers@freebsd.org Subject: Re: [H] Optimal computer for FreeBSD In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Tue, 25 Feb 1997, Snob Art Genre wrote: > On Tue, 25 Feb 1997, Vnotchenko S.S. wrote: > > > Hi, all! > > My friends and I planing to use 2.1.7R-FreeBSD as main server > > (DNS,Web,INND,FTP) for ours ISP network. > > We want use something like this: PCI, Pentium-PRO ATX CPU, 64 Mb EDO RAM, > > 2x4.5 Gb SCSI, > > 8x SCSI CD-ROM, 10Mbit Ethernet. Please, recommend us hardware (firm, > > model) known as best > > (reliable, fast) working under 2.1.7R-FreeBSD (PCI devices if possible). > > I've had a really good experience with my Micron Millenia Pro Plus. > > > > > --- > > CPU: > > PPro-200 > > > Motherboard: > > ATX w/Intel 440FX, as far as I can tell. > > > SCSI Host adapter: > > Buslogic BT-948. Its reliability hasn't been perfect, but I don't really > have a standard of comparison, as it's the only SCSI host adapter I've > ever owned. I've used many of the Adaptec controllers (1742, 2742, 2940, and 3940) under FreeBSD, and they are all much better than the Buslogic controller I tried. I've still got on of those ancient 1742 controllers in a production FreeBSD system! The NCR PCI (810) controllers are also very good, and very reliable, and very cheap. I use these two. > > SCSI Hard drives: > > Conner CFP2107S > > > SCSI CD-ROM: > > Plextor 8plex internal > > > Ethernet card: > > Cheap generic NE2000, probably the least problematic piece of hardware in > my system (and it's not a problematic system). Never put a NE2000 into a server. A high-powered server without adequate network resources is a waste of CPU resources. A NE2000 in a PP200 system is a bit of joke. I bet a P5-166 with a good ethernet card would outperform it in many server applications. A DEC-based PCI ethernet card can DMA data right into system memory, while a NE2000 requires expensive PIO for every byte! > > --- > > > > Thanks in advance, Sergey (sergey@extech.msk.su). > > > > > > > > > > > > Ben > > "You have your mind on computers, it seems." > > > Tom From owner-freebsd-hackers Tue Feb 25 10:50:16 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id KAA08182 for hackers-outgoing; Tue, 25 Feb 1997 10:50:16 -0800 (PST) Received: from sujal.prognet.com (sujal.prognet.com [204.255.154.231]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id KAA08171 for ; Tue, 25 Feb 1997 10:50:13 -0800 (PST) Received: from localhost (smpatel@localhost) by sujal.prognet.com (8.8.4/8.8.4) with SMTP id KAA17870 for ; Tue, 25 Feb 1997 10:50:18 -0800 (PST) X-Authentication-Warning: sujal.prognet.com: smpatel owned process doing -bs Date: Tue, 25 Feb 1997 10:50:18 -0800 (PST) From: Sujal Patel To: freebsd-hackers@freebsd.org Subject: Re: Static variables in shared libraries In-Reply-To: <3.0.1.32.19970225003040.00ff58e4@prognet.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Tue, 25 Feb 1997, Peter Haight wrote: > const char* test_3 = "hello"; > const char* test_4 = test_3; > > If I dynamically load this shared library in my program and print the > variables, I get: > test_3 = "hello" > test_4 = 0x0 > > What's going on? The two lines you have written are not handled like C globals. Because test_4 isn't a constant, you need to have the C++ global constructor called when your shared lib is loaded (otherwise test_4 will never be initialized). What you need to do is to include /usr/lib/c++rt.o in the link line for your shared library. This will include the __init function that will run your global c++ constructors. Sujal From owner-freebsd-hackers Tue Feb 25 11:26:35 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id LAA10169 for hackers-outgoing; Tue, 25 Feb 1997 11:26:35 -0800 (PST) Received: from Sisyphos.MI.Uni-Koeln.DE (Sisyphos.MI.Uni-Koeln.DE [134.95.212.10]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id LAA10164 for ; Tue, 25 Feb 1997 11:26:32 -0800 (PST) Received: from x14.mi.uni-koeln.de (annexr3-15.slip.Uni-Koeln.DE) by Sisyphos.MI.Uni-Koeln.DE with SMTP id AA23323 (5.67b/IDA-1.5 for ); Tue, 25 Feb 1997 20:26:26 +0100 Received: (from se@localhost) by x14.mi.uni-koeln.de (8.8.5/8.6.9) id UAA02075; Tue, 25 Feb 1997 20:26:23 +0100 (CET) Message-Id: <19970225202622.HX00195@x14.mi.uni-koeln.de> Date: Tue, 25 Feb 1997 20:26:22 +0100 From: se@freebsd.org (Stefan Esser) To: nik@blueberry.co.uk (Nik Clayton) Cc: hackers@freebsd.org Subject: Re: 2.1.7: ncr and de driver increasingly fickle References: <19970225164635.47646@coconut.blueberry.co.uk> X-Mailer: Mutt 0.60_p2-3,5,8-9 Mime-Version: 1.0 In-Reply-To: <19970225164635.47646@coconut.blueberry.co.uk>; from Nik Clayton on Feb 25, 1997 16:46:35 +0000 Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Feb 25, nik@blueberry.co.uk (Nik Clayton) wrote: > Hi, > > Has anyone else noticed an increased fickleness on 2.1.7 with the ncr and > the de drivers? > > On my 2.1.5 system, I never heard a complaint from the de driver, and the > ncr driver might occasionally complain > > /kernel: sd1(ncr0:1:0): extraneous data discarded. Well, this is not a problem caused by the driver, IMHO ... The number of data transfers requested by the target did not match the transfer count. This normally indicates SCSI cable problems, since it means either zero or two bytes have been sent in a previous bus phase. For synchronous transfers, you may also receive a gross error in such situations. It is caused by a FIFO over- or underflow as a result of a lost or doubled byte ... The driver just counts the bytes transfered, and notices the mismatch ... Regards, STefan From owner-freebsd-hackers Tue Feb 25 11:29:13 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id LAA10423 for hackers-outgoing; Tue, 25 Feb 1997 11:29:13 -0800 (PST) Received: from ceres.bios.unc.edu (ceres.bios.unc.edu [152.2.94.225]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id LAA10412 for ; Tue, 25 Feb 1997 11:29:04 -0800 (PST) Received: from localhost (walter@localhost) by ceres.bios.unc.edu (8.7.5/8.6.12) with SMTP id OAA08489 for ; Tue, 25 Feb 1997 14:34:03 -0500 (EST) X-Authentication-Warning: ceres.bios.unc.edu: walter owned process doing -bs Date: Tue, 25 Feb 1997 14:34:03 -0500 (EST) From: Bruce Walter X-Sender: walter@ceres.bios.unc.edu To: hackers@freebsd.org Subject: Re: 2.1.7: ncr and de driver increasingly fickle In-Reply-To: <19970225164635.47646@coconut.blueberry.co.uk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Tue, 25 Feb 1997, Nik Clayton wrote: > In addition, the de driver is sometimes complaining (particularly on > system startup) > > /kernel: de0: abnormal interrupt: receive process stopped This has been happening to me on a -current system from about 3 weeks ago. The card is a PCI based Kingston EtherRx, and the message appears only on bootup. de0 rev 17 int a irq 11 on pci0:19:0 de0: 21041 [10Mb/s] pass 1.1 de0: address 00:c0:f0:15:e8:ed [...] de0: enabling 10baseT port de0: abnormal interrupt: receive process stopped Other than this message I have had no problems with the card/driver EXCEPT that when the cable is disconnected from the hub or card, the interface is no longer accessible... The system complains about a cable fault and then boom, no more packets. I didn't have a chance to check into this further. (ie: would ifconfig down then ifconfig up fix it) - Bruce ======================================================================== || Bruce M. Walter || 107 Timber Hollow Court #335 || || Senior Network Consultant || Chapel Hill, NC 27514 || || Fortean Technologies, Inc. || Tel: 919-967-4766 || || Information Technology Consultants || Fax: 919-967-4395 || ======================================================================== || BSD Unix -- It's not just a job, it's a way of life! || ======================================================================== From owner-freebsd-hackers Tue Feb 25 12:21:02 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id MAA13346 for hackers-outgoing; Tue, 25 Feb 1997 12:21:02 -0800 (PST) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id MAA13336 for ; Tue, 25 Feb 1997 12:20:54 -0800 (PST) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id VAA26165; Tue, 25 Feb 1997 21:20:49 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.8.5/8.8.5) id VAA13107; Tue, 25 Feb 1997 21:10:12 +0100 (MET) Message-ID: Date: Tue, 25 Feb 1997 21:10:12 +0100 From: j@uriah.heep.sax.de (J Wunsch) To: mgessner@aristar.com (Matthew A. Gessner) Cc: hackers@freebsd.org (hackers) Subject: Re: Writing a daemon... References: <3313307E.41C67EA6@aristar.com> X-Mailer: Mutt 0.55-PL10 Mime-Version: 1.0 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <3313307E.41C67EA6@aristar.com>; from Matthew A. Gessner on Feb 25, 1997 13:33:34 -0500 Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk As Matthew A. Gessner wrote: > I'm looking for some really good information on writing a > daemon for a) FreeBSD and b) DEC ALPHA OSF/1. I don't have any clues for OSF/1. Anyway, there are plenty of daemon source code examples in the BSD trees. Simply pick one. SEE ALSO /usr/share/doc/20.ipctut/ /usr/share/doc/21.ipc/ -- 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-hackers Tue Feb 25 12:26:21 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id MAA13662 for hackers-outgoing; Tue, 25 Feb 1997 12:26:21 -0800 (PST) Received: from Sisyphos.MI.Uni-Koeln.DE (Sisyphos.MI.Uni-Koeln.DE [134.95.212.10]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id MAA13617; Tue, 25 Feb 1997 12:26:03 -0800 (PST) Received: from x14.mi.uni-koeln.de (annexr3-11.slip.Uni-Koeln.DE) by Sisyphos.MI.Uni-Koeln.DE with SMTP id AA23788 (5.67b/IDA-1.5); Tue, 25 Feb 1997 21:23:37 +0100 Received: (from se@localhost) by x14.mi.uni-koeln.de (8.8.5/8.6.9) id VAA02334; Tue, 25 Feb 1997 21:22:54 +0100 (CET) Message-Id: <19970225212134.FB65465@x14.mi.uni-koeln.de> Date: Tue, 25 Feb 1997 21:21:34 +0100 From: se@freebsd.org (Stefan Esser) To: helbig@mx.ba-stuttgart.de (Wolfgang Helbig) Cc: se@freebsd.org (Stefan Esser), hackers@freebsd.org Subject: Re: CMD640b workaround - final(?) version References: <19970213004131.DV50639@x14.mi.uni-koeln.de> <199702250147.CAA00172@helbig.informatik.ba-stuttgart.de> X-Mailer: Mutt 0.60_p2-3,5,8-9 Mime-Version: 1.0 In-Reply-To: <199702250147.CAA00172@helbig.informatik.ba-stuttgart.de>; from Wolfgang Helbig on Feb 25, 1997 02:47:34 +0100 Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Feb 25, helbig@MX.BA-Stuttgart.De (Wolfgang Helbig) wrote: > Hi Stefan, > > I changed the code as you suggested. Now pci.c is clean again. Yes, I seem to like that version a lot more than the previous one :) > I added a new source pci/wdc_p.c. It is telling wd.c, which > pci-devices are probed, so wd.c can adapt to different devices. > Up to now only to CMD640b. If there are other IDE-PCI-Chips that > need special treatment, they can be easily detected in wd.c now and > treated accordingly. You choose to move the PCI ID matching code into the ISA driver (as the public function wdi_pci() returning a long device name), but I'm not convinced, that this is the way to go ... Since I'm not going to maintain that code, I won't object, but I'd rather not have any files under /sys/i386/isa, that depends on PCI device IDs ... I see, that you try to get away with only a probe() being defined, and the attach being a NOP. This is in fact possible, but since the probe message line will be completed after the return from the probe, you can't make the IDE driver print any additional messages regarding its configuration ... **** No, you won't get away this way: The DRIVE probe will print additional messages, and those will precede the controller information ... Please consider using a seperate probe() and attach(), using the default switch statement in the probe, as the other drivers do, and have the attach function actually call wdc_pci() ... > I had to add a line in conf/files: > > pci/wdc_p.c optional wdc device-driver > > For review, I include the source of wdc_p.c. > If you think it's okay now, I will post a diff-file for wd.c, > so kern/2305 can be closed. You can send me a context diff, and I'll import it into -current. But please reconsider the probe message issues I pointed out above! Regards, STefan From owner-freebsd-hackers Tue Feb 25 12:52:40 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id MAA15197 for hackers-outgoing; Tue, 25 Feb 1997 12:52:40 -0800 (PST) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id MAA15180 for ; Tue, 25 Feb 1997 12:52:20 -0800 (PST) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id VAA27118 for hackers@freebsd.org; Tue, 25 Feb 1997 21:52:16 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.8.5/8.8.5) id UAA13057; Tue, 25 Feb 1997 20:51:14 +0100 (MET) Message-ID: Date: Tue, 25 Feb 1997 20:51:14 +0100 From: j@uriah.heep.sax.de (J Wunsch) To: hackers@freebsd.org Subject: Re: sysinstall & disk labelling. References: <199702251611.IAA29184@freefall.freebsd.org> X-Mailer: Mutt 0.55-PL10 Mime-Version: 1.0 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199702251611.IAA29184@freefall.freebsd.org>; from Darren Reed on Feb 26, 1997 03:08:15 +1100 Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk As Darren Reed wrote: > Can I mention that the disk labelling which happened straight after > you had partitioned was actually very useful ? It appears to now > occur at some other time ? Huh? (Just test-installing a 2.2-GAMMA...) -- 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-hackers Tue Feb 25 13:27:49 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id NAA17706 for hackers-outgoing; Tue, 25 Feb 1997 13:27:49 -0800 (PST) Received: from rocky.mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id NAA17691; Tue, 25 Feb 1997 13:27:30 -0800 (PST) Received: (from nate@localhost) by rocky.mt.sri.com (8.7.5/8.7.3) id OAA24299; Tue, 25 Feb 1997 14:27:26 -0700 (MST) Date: Tue, 25 Feb 1997 14:27:26 -0700 (MST) Message-Id: <199702252127.OAA24299@rocky.mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: se@freebsd.org (Stefan Esser) Cc: nik@blueberry.co.uk (Nik Clayton), hackers@freebsd.org Subject: Re: 2.1.7: ncr and de driver increasingly fickle In-Reply-To: <19970225202622.HX00195@x14.mi.uni-koeln.de> References: <19970225164635.47646@coconut.blueberry.co.uk> <19970225202622.HX00195@x14.mi.uni-koeln.de> Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > On my 2.1.5 system, I never heard a complaint from the de driver, and the > > ncr driver might occasionally complain > > > > /kernel: sd1(ncr0:1:0): extraneous data discarded. > > Well, this is not a problem caused by the driver, IMHO ... > > The number of data transfers requested by the target did not > match the transfer count. This normally indicates SCSI cable > problems, since it means either zero or two bytes have been > sent in a previous bus phase. So why did the old driver in 2.1.5 not report this error? (I only get this error in 2.2, and only during bootup). > For synchronous transfers, you may also receive a gross error > in such situations. It is caused by a FIFO over- or underflow > as a result of a lost or doubled byte ... Why would this only happen when I boot the system, and why would it be new to the system? Old kernels don't report/cause this error. Nate From owner-freebsd-hackers Tue Feb 25 15:20:42 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id PAA23522 for hackers-outgoing; Tue, 25 Feb 1997 15:20:42 -0800 (PST) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id PAA23517 for ; Tue, 25 Feb 1997 15:20:38 -0800 (PST) Received: from time.cdrom.com (jkh@localhost [127.0.0.1]) by time.cdrom.com (8.8.5/8.6.9) with ESMTP id PAA13157; Tue, 25 Feb 1997 15:20:04 -0800 (PST) To: Darren Reed cc: hackers@freebsd.org Subject: Re: sysinstall & disk labelling. In-reply-to: Your message of "Wed, 26 Feb 1997 03:08:15 +1100." <199702251611.IAA29184@freefall.freebsd.org> Date: Tue, 25 Feb 1997 15:20:04 -0800 Message-ID: <13153.856912804@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > Can I mention that the disk labelling which happened straight after > you had partitioned was actually very useful ? It appears to now > occur at some other time ? On what do you base this assumption? I haven't changed anything WRT that.. :-) Jordan From owner-freebsd-hackers Tue Feb 25 15:26:51 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id PAA23831 for hackers-outgoing; Tue, 25 Feb 1997 15:26:51 -0800 (PST) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id PAA23825 for ; Tue, 25 Feb 1997 15:26:43 -0800 (PST) Received: from current1.whistle.com (current1.whistle.com [207.76.205.22]) by alpo.whistle.com (8.8.5/8.8.4) with SMTP id PAA23403 for ; Tue, 25 Feb 1997 15:17:55 -0800 (PST) Message-ID: <331372A1.41C67EA6@whistle.com> Date: Tue, 25 Feb 1997 15:15:45 -0800 From: Julian Elischer Organization: Whistle Communications X-Mailer: Mozilla 3.0Gold (X11; I; FreeBSD 2.2-CURRENT i386) MIME-Version: 1.0 To: hackers@freebsd.org Subject: Ethernet driver-H/W Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk does anyone have an ethernet chipset they recommend with the following characteristics? shared memory interface (ala SMC ) ISA interface.. not PCI etc. 10-baseT interface enough ram? (or can support an external ram) preferably with a BSD driver, but I'll write one if I have to. what won't work: DMA programmed IO From owner-freebsd-hackers Tue Feb 25 15:35:35 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id PAA24560 for hackers-outgoing; Tue, 25 Feb 1997 15:35:35 -0800 (PST) Received: from mail11.digital.com (mail11.digital.com [192.208.46.10]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id PAA24553 for ; Tue, 25 Feb 1997 15:35:25 -0800 (PST) Received: from muggsy.lkg.dec.com by mail11.digital.com (8.7.5/UNX 1.5/1.0/WV) id SAA14443; Tue, 25 Feb 1997 18:25:43 -0500 (EST) Received: from usr602.zko.dec.com by muggsy.lkg.dec.com (5.65/DEC-Ultrix/4.3) with SMTP id AA25792; Tue, 25 Feb 1997 18:24:41 -0500 Message-Id: <3.0.32.19970225182022.006daa38@netrix.lkg.dec.com> X-Sender: popmatt@netrix.lkg.dec.com X-Mailer: Windows Eudora Pro Version 3.0 Demo (32) Date: Tue, 25 Feb 1997 18:25:49 -0500 To: Rohit Dube , freebsd-hackers@freebsd.org From: Matt Thomas Subject: Re: Ethernet-like interface statistics and ioctl/sysctl Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk At 09:21 AM 2/25/97 -0500, Rohit Dube wrote: >I was wondering if any version of FreeBSD had an ioctl or >sysctl interface for collecting the dot3* (ethernet like) statistics >from ethernet drivers (allingnment errors, collisions etc). No it doesn;t >I am looking 2.2 code and man pages. The 'de' drivers seems to maintain >the correct (RFC 1643/1650) statistics, but I can't find an interface which >exports these to user land in the man pages or in the code. There isn't one. I've asked for one in the past. The de driver stats are for my use in debugging. >Anybody care to comment on the current or coming support? Or if it >already exists, how to access it (ie the ioctl or the sysctl parameters >or pointers to docs or code.) I was hoping for sysctl support but I'll probably break done and just add an ioctl. -- Matt Thomas Internet: matt@3am-software.com 3am Software Foundry WWW URL: http://www.3am-software.com/bio/matt.html Westford, MA Disclaimer: I disavow all knowledge of this message From owner-freebsd-hackers Tue Feb 25 15:40:19 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id PAA24877 for hackers-outgoing; Tue, 25 Feb 1997 15:40:19 -0800 (PST) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id PAA24872 for ; Tue, 25 Feb 1997 15:40:17 -0800 (PST) Received: from time.cdrom.com (jkh@localhost [127.0.0.1]) by time.cdrom.com (8.8.5/8.6.9) with ESMTP id PAA13258; Tue, 25 Feb 1997 15:39:49 -0800 (PST) To: Doug Rabson cc: freebsd-hackers@freebsd.org Subject: Re: FreeBSD advert In-reply-to: Your message of "25 Feb 1997 17:01:18 GMT." Date: Tue, 25 Feb 1997 15:39:49 -0800 Message-ID: <13254.856913989@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > I was just surprised to see a FreeBSD advert on Yahoo. That was a > pretty cool idea of someone (Jordan?). I hope we can look forward to > seeing more of this kind of exposure. Well, we really have David Filo to thank - I merely suggested a way in which they might give us the most effectve moral support. :-) Jordan From owner-freebsd-hackers Tue Feb 25 16:21:44 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id QAA27949 for hackers-outgoing; Tue, 25 Feb 1997 16:21:44 -0800 (PST) Received: from darling.cs.umd.edu (10862@darling.cs.umd.edu [128.8.128.115]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id QAA27942 for ; Tue, 25 Feb 1997 16:21:38 -0800 (PST) Received: by darling.cs.umd.edu (8.8.5/UMIACS-0.9/04-05-88) id TAA29397; Tue, 25 Feb 1997 19:20:20 -0500 (EST) Message-Id: <199702260020.TAA29397@darling.cs.umd.edu> To: Matt Thomas cc: freebsd-hackers@freebsd.org, rohit@cs.umd.edu Subject: Re: Ethernet-like interface statistics and ioctl/sysctl In-reply-to: Your message of "Tue, 25 Feb 1997 18:25:49 EST." <3.0.32.19970225182022.006daa38@netrix.lkg.dec.com> Date: Tue, 25 Feb 1997 19:20:19 -0500 From: Rohit Dube Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Tue, 25 Feb 1997 18:25:49 -0500 matt@lkg.dec.com writes: =>At 09:21 AM 2/25/97 -0500, Rohit Dube wrote: =>>I am looking 2.2 code and man pages. The 'de' drivers seems to maintain =>>the correct (RFC 1643/1650) statistics, but I can't find an interface which =>>exports these to user land in the man pages or in the code. => =>There isn't one. I've asked for one in the past. The de driver stats are =>for my use in debugging. => =>>Anybody care to comment on the current or coming support? Or if it =>>already exists, how to access it (ie the ioctl or the sysctl parameters =>>or pointers to docs or code.) => =>I was hoping for sysctl support but I'll probably break done and just =>add an ioctl. ____ Matt, How far are you into adding the ioctl? If you are close to done, I would appreciate it if you could let me use the code. I was thinking of adding an ioctl for local use myself. Or a sysctl provided I could figure out how the sysctl interface works. (Any body have notes on the 4.4BSD/FreeBSD sysctl interface?) I guess sysctl would be nicer.... Thanks, --rohit. From owner-freebsd-hackers Tue Feb 25 16:36:17 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id QAA28865 for hackers-outgoing; Tue, 25 Feb 1997 16:36:17 -0800 (PST) Received: from who.cdrom.com (who.cdrom.com [204.216.27.3]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id QAA28856 for ; Tue, 25 Feb 1997 16:36:14 -0800 (PST) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by who.cdrom.com (8.7.5/8.6.11) with ESMTP id QAA13247 for ; Tue, 25 Feb 1997 16:36:09 -0800 (PST) Received: (from msmith@localhost) by genesis.atrad.adelaide.edu.au (8.8.5/8.7.3) id LAA19768; Wed, 26 Feb 1997 11:04:35 +1030 (CST) From: Michael Smith Message-Id: <199702260034.LAA19768@genesis.atrad.adelaide.edu.au> Subject: Re: Ethernet driver-H/W In-Reply-To: <331372A1.41C67EA6@whistle.com> from Julian Elischer at "Feb 25, 97 03:15:45 pm" To: julian@whistle.com (Julian Elischer) Date: Wed, 26 Feb 1997 11:04:35 +1030 (CST) Cc: hackers@freebsd.org X-Mailer: ELM [version 2.4ME+ PL28 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Julian Elischer stands accused of saying: > does anyone have an ethernet chipset they recommend > with the following characteristics? Did you follow my previous suggestions wrt. the NatSemi parts? > shared memory interface (ala SMC ) > ISA interface.. not PCI etc. > 10-baseT interface > enough ram? (or can support an external ram) > preferably with a BSD driver, but I'll write one if I have to. The 'ed' driver will work with the NS8390x parts, several of which have onboard UTP and shared-memory modes. You should be able to cram several on a single board. They take external SRAM to 64K IIRC, certainly at least 16K. You could contribute by teaching the 'ed' driver about cards with more than 16K - get an Artisoft AE2 or a Compex ENP16 (think that number's right), both of which can be configured for 64K. They both use 8390x chips. Have a look at http://www.national.com/pf/DP/DP83905.html and hit the search engine off their homepage for '83905' for lots of other references. Their price breaks look good, and they have a free samples arrangement with Digi-Key. There are also a pile of appnotes that ought to get you going pretty quickly. -- ]] Mike Smith, Software Engineer msmith@gsoft.com.au [[ ]] Genesis Software genesis@gsoft.com.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control. (ph) +61-8-8267-3493 [[ ]] Unix hardware collector. "Where are your PEZ?" The Tick [[ From owner-freebsd-hackers Tue Feb 25 16:41:59 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id QAA29312 for hackers-outgoing; Tue, 25 Feb 1997 16:41:59 -0800 (PST) Received: from ocean.campus.luth.se (ocean.campus.luth.se [130.240.194.116]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id QAA29306 for ; Tue, 25 Feb 1997 16:41:56 -0800 (PST) Received: (from karpen@localhost) by ocean.campus.luth.se (8.7.5/8.7.3) id BAA09889; Wed, 26 Feb 1997 01:46:30 +0100 (MET) From: Mikael Karpberg Message-Id: <199702260046.BAA09889@ocean.campus.luth.se> Subject: Re: Ethernet options on 2.2-GAMMA To: joerg_wunsch@uriah.heep.sax.de Date: Wed, 26 Feb 1997 01:46:30 +0100 (MET) Cc: hackers@freebsd.org In-Reply-To: from J Wunsch at "Feb 25, 97 08:54:28 am" X-Mailer: ELM [version 2.4ME+ PL22 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk According to J Wunsch: > As Nate Williams wrote: > > > > The relevant code in pccardd is actually fairly small, and the card > > > database ought to compress well. > > > > Actually, this is the hard part. The code in pccardd is *NOT* small, > > since it has to read all of the darn card TUPLES and such. It's alot of > > bloat for (IMHO) little gain. > > What about supplying this from a second floppy? Remember, once the > kernel has been loaded, the floppy device is available again. Speaking of the floppy being available again... One BADLY missed option sometimes is the "Start holographic shell" option in the main menu. It'd be really nice to be able to get a shell first thing, and be able to start the install after doing initial work. (Currently the routine is: make install crash, and give you a shell, then do what you want, and retry istallation. Kinda sucks.) I seem to remember there being some problem with that option, like if the shell was launched too early, floppy install, etc wouldn't work. So what? If you're going to install from network and you need to set things up a bit BEFORE you let sysistall at it, you kinda like to have that shell there. So, why not make it an option and simply say: "Are you sure? This will disable floppy install, etc" And if the user says to go ahead, then just disable floppy install, and give the user his long awaited shell. Or? I'm sorry if this is something that is already fixed, or somehow rejected. In the latter case, why? /Mikael From owner-freebsd-hackers Tue Feb 25 17:03:33 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id RAA00805 for hackers-outgoing; Tue, 25 Feb 1997 17:03:33 -0800 (PST) Received: from buffnet4.buffnet.net (root@buffnet4.buffnet.net [205.246.19.13]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id RAA00799 for ; Tue, 25 Feb 1997 17:03:29 -0800 (PST) Received: from buffnet1.buffnet.net (mmdf@buffnet1.buffnet.net [205.246.19.10]) by buffnet4.buffnet.net (8.6.12/8.6.9) with SMTP id TAA12638 for ; Tue, 25 Feb 1997 19:53:53 -0500 Received: from gppp2.buffnet.net by buffnet1.buffnet.net id aa20116; 25 Feb 97 20:03 EST Message-ID: <33138B98.21DB@buffnet.net> Date: Tue, 25 Feb 1997 20:02:16 -0500 From: Joseph Piekarski X-Mailer: Mozilla 3.0Gold (Win95; I) MIME-Version: 1.0 To: hackers@freebsd.org Subject: Install problem Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Help! I have installed FreeBSD 2.1.5, but when I boot, the floppy drive light comes on and I get the message "Read error". I checked the geometry of the hard drive and it matches the numbers reported by Partition Magic. I am using System Commander as my boot manager. Thanks, Joe Piekarski From owner-freebsd-hackers Tue Feb 25 17:44:45 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id RAA03451 for hackers-outgoing; Tue, 25 Feb 1997 17:44:45 -0800 (PST) Received: from fallout.campusview.indiana.edu (fallout.campusview.indiana.edu [149.159.1.1]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id RAA03434 for ; Tue, 25 Feb 1997 17:44:39 -0800 (PST) Received: from localhost (jfieber@localhost) by fallout.campusview.indiana.edu (8.8.5/8.8.5) with SMTP id UAA27966; Tue, 25 Feb 1997 20:44:11 -0500 (EST) Date: Tue, 25 Feb 1997 20:44:10 -0500 (EST) From: John Fieber To: Nik Clayton cc: hackers@FreeBSD.org Subject: Re: 2.1.7: ncr and de driver increasingly fickle In-Reply-To: <19970225164635.47646@coconut.blueberry.co.uk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk On Tue, 25 Feb 1997, Nik Clayton wrote: > On my 2.1.5 system, I never heard a complaint from the de driver, and the > ncr driver might occasionally complain > > /kernel: sd1(ncr0:1:0): extraneous data discarded. .... > ncr0 rev 2 int a irq 11 on pc i0:12 > (ncr0:0:0): "FUJITSU M2952S-512 0124" type 0 fixed SCSI 2 Curious. Am I correct in observing that everyone reporting this problem with the ncr driver, including myself, has a Fujitsu disk? Looking through the mailing list archives I found previous mention that the error might indicate bad cabling, but I tried a bunch of different cables and configurations of devices on the bus with no change in behavior. -john From owner-freebsd-hackers Tue Feb 25 18:13:32 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id SAA05285 for hackers-outgoing; Tue, 25 Feb 1997 18:13:32 -0800 (PST) Received: from root.com (implode.root.com [198.145.90.17]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id SAA05279 for ; Tue, 25 Feb 1997 18:13:29 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by root.com (8.8.5/8.6.5) with SMTP id SAA27939; Tue, 25 Feb 1997 18:13:13 -0800 (PST) Message-Id: <199702260213.SAA27939@root.com> X-Authentication-Warning: implode.root.com: localhost [127.0.0.1] didn't use HELO protocol To: Michael Smith cc: julian@whistle.com (Julian Elischer), hackers@freebsd.org Subject: Re: Ethernet driver-H/W In-reply-to: Your message of "Wed, 26 Feb 1997 11:04:35 +1030." <199702260034.LAA19768@genesis.atrad.adelaide.edu.au> From: David Greenman Reply-To: dg@root.com Date: Tue, 25 Feb 1997 18:13:13 -0800 Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >certainly at least 16K. You could contribute by teaching the 'ed' >driver about cards with more than 16K - get an Artisoft AE2 or a >Compex ENP16 (think that number's right), both of which can be >configured for 64K. They both use 8390x chips. You should be able to set "iosiz 65536" in the kernel config file; there's support for a user-override of the memory size using that. -DG David Greenman Core-team/Principal Architect, The FreeBSD Project From owner-freebsd-hackers Tue Feb 25 18:45:57 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id SAA07313 for hackers-outgoing; Tue, 25 Feb 1997 18:45:57 -0800 (PST) Received: from whqvax.picker.com (whqvax.picker.com [144.54.1.1]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id SAA07306 for ; Tue, 25 Feb 1997 18:45:43 -0800 (PST) Received: from ct.picker.com by whqvax.picker.com with SMTP; Tue, 25 Feb 1997 21:45:09 -0500 (EST) Received: from elmer.ct.picker.com ([144.54.57.34]) by ct.picker.com (4.1/SMI-4.1) id AA20700; Tue, 25 Feb 97 21:45:07 EST Received: by elmer.ct.picker.com (SMI-8.6/SMI-SVR4) id VAA20343; Tue, 25 Feb 1997 21:42:51 -0500 Message-Id: <19970225214251.26667@ct.picker.com> Date: Tue, 25 Feb 1997 21:42:51 -0500 From: Randall Hopper To: Joerg Wunsch Cc: hackers@FreeBSD.ORG Subject: Re: Help correcting corrupted disklabel References: <19970222153631.23537@ct.picker.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.61 In-Reply-To: ; from J Wunsch on Feb 02, 1997 at 11:05:24PM Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk J Wunsch: |> This is a sliced disk with FreeBSD on slices 3 and 4 (wd1a and wd1s3e). | |wd1s3e is slice 3. Are you sure wd1a is another slice? I doubt, but |you didn't show us the fdisk output. My typo. I've got root and swap on wd1s3 with a data slice on wd1s4 (e). | disklabel -Brw wd1s3 |The disklabel is embedded in the (BSD) bootblocks. The above command |will rewrite them. Let's hope you didn't damage the filesystem |structure itself, in this case, you should get away with the above. Thanks for the suggestion. It appears it blew part of the file system so I made an unplanned upgrade to 2.2-GAMMA. Had most of my files backed up but I've been dd'ing my corrupted image to get back what little text data I needed. (Boy could I have used Norton Utilities for UFS... :-). Randall Hopper From owner-freebsd-hackers Tue Feb 25 19:13:15 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id TAA09280 for hackers-outgoing; Tue, 25 Feb 1997 19:13:15 -0800 (PST) Received: from bunyip.cc.uq.edu.au (daemon@bunyip.cc.uq.edu.au [130.102.2.1]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id TAA09271 for ; Tue, 25 Feb 1997 19:12:58 -0800 (PST) Received: (from daemon@localhost) by bunyip.cc.uq.edu.au (8.8.5/8.8.5) id NAA19728; Wed, 26 Feb 1997 13:10:46 +1000 Received: by ogre.devetir.qld.gov.au (8.7.5/DEVETIR-E0.3a) id NAA24882; Wed, 26 Feb 1997 13:11:14 +1000 (EST) Date: Wed, 26 Feb 1997 13:11:14 +1000 (EST) From: Stephen McKay Message-Id: <199702260311.NAA24882@ogre.devetir.qld.gov.au> To: j@uriah.heep.sax.de (J Wunsch), Naoki Hamada cc: freebsd-hackers@freebsd.org, syssgm@devetir.qld.gov.au Subject: Re: MALLOC(3) writes to stderr... X-Newsreader: NN version 6.5.0 #1 (NOV) Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk j@uriah.heep.sax.de (J Wunsch) wrote: >As Naoki Hamada wrote: > >> Malloc(3) of 2.2-GAMMA writes error/warning messages to stderr. There >> is a daemon named jserver, which provides translations between >> Japanese characters, which does close stderr before opening its >> dictionary files. Sometimes jserver gets its dictionary file >> completely damaged by malloc's error/warning message. > >Hmm, i think it's a common misconception in Unix that everybody >blindly assumes that file descriptors 0, 1, and 2 refer to stdin, >stdout, and stderr respectively. OTOH, there's no opportunity for a >library module to check where stderr really goes (or whether it has >been closed). I bet malloc isn't the only library module that would >write there. > >Your safest bet is to never close these descriptors, but redirect >/dev/null on them. So, they remain `reserved'. Although not enforced by the kernel, file descriptors 0, 1 and 2 have a conventional use that should always be respected. If you don't want to see stderr output, open /dev/null as descriptor 2. This should work: fd = open("/dev/null", O_WRONLY); if (fd == -1) { perror("/dev/null"); exit(1); } if (fd != 2) { dup2(fd, 2); close(fd); } The test of fd != 2 is for the unlikely case that descriptor 2 is closed already. If the open of "/dev/null" fails, exiting is probably the kindest result; you've got some repair work to do. Some others responded that stderr and descriptor 2 are logically different and recommend using fileno(stderr) instead of 2. We of the old school all know that stdio is an upstart young library, and will never be allowed to use anything but descriptor 2 on Unix. :-) Feel free to use fileno(stderr) if the hairy revolutionaries have got to you. You might like to use STDERR_FILENO from and/or _PATH_DEVNULL from and/or err() instead of perror()/exit(), but these are upstart newbies too. BTW, the dup2() man page implies that newd will be closed even if it is equal to oldd. In reality, it is not, and (as far as I can remember) never was for any version of Unix. Similarly, newd is not closed if oldd is invalid. I'll update the man page as soon as I get a chance. Stephen. From owner-freebsd-hackers Tue Feb 25 19:20:56 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id TAA09732 for hackers-outgoing; Tue, 25 Feb 1997 19:20:56 -0800 (PST) Received: from dg-rtp.dg.com (dg-rtp.rtp.dg.com [128.222.1.2]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id TAA09727 for ; Tue, 25 Feb 1997 19:20:51 -0800 (PST) Received: by dg-rtp.dg.com (5.4R3.10/dg-rtp-v02) id AA09918; Tue, 25 Feb 1997 22:20:08 -0500 Received: from ponds by dg-rtp.dg.com.rtp.dg.com; Tue, 25 Feb 1997 22:20 EST Received: from lakes.water.net (lakes [10.0.0.3]) by ponds.water.net (8.8.3/8.7.3) with ESMTP id VAA19672 for ; Tue, 25 Feb 1997 21:43:32 -0500 (EST) Received: (from rivers@localhost) by lakes.water.net (8.8.3/8.6.9) id VAA19324 for freebsd-hackers@freefall.cdrom.com; Tue, 25 Feb 1997 21:48:47 -0500 (EST) Date: Tue, 25 Feb 1997 21:48:47 -0500 (EST) From: Thomas David Rivers Message-Id: <199702260248.VAA19324@lakes.water.net> To: ponds!freefall.cdrom.com!freebsd-hackers Subject: Re: More on bad dir panics Content-Type: text Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > > I have been trying to look around the crash dumps, as they are plentiful > these days (twice a day seems to be the current rate). These always happen > at the same point and all crashes are similar, crash occurs on directory > lookup stombling over a block which contains something else than directory > data. This "smells" very similar to my problems... perhaps we can devine the intersection of these two problems and hit on a solution? Things I've determined: o) This can happen in a very light load. o) It happens on several types of hardware (SCSI, IDE, 386-586.) The problem appears to be related to inode allocation - in that an inode is marked in the free inodes array as "available" (the bit isn't set) and then, some other later code reads the data from the disk and checks a field (for the "dup alloc" panic, it's the "mode" field) and discovers that "oops - it, in fact was being used." Does that sound familiar? Some other interesting observations: o) This can happen with a brand-new file system; if you write trash the device, then do a newfs. Newfs believes it has correctly filled in all the inodes with 0, but some (at least one in my tests) aren't correctly zero'd. o) The problem "strikes" and gets progressively worse until the file system simply falls apart. I'm up to twice a day myself on my news server; also, a find in /usr/spool/news now produces a lot of "Bad file descriptor" messages, indicating other file system problems that fsck didn't correct. o) Running fsck once isn't enough to restore a file system to a semi-usuable state; if you fsck it once, try again, you'll sometimes notice more corrections. o) This isn't "new" - it's something I've experience in all 2.1 releases (although, until now, I was about the sole reporter of the problem.) I mention this to try and narrow the scope of what we're looking for. It was something that happened in the 2.1.0 time-frame. - Dave Rivers - From owner-freebsd-hackers Tue Feb 25 19:21:20 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id TAA09768 for hackers-outgoing; Tue, 25 Feb 1997 19:21:20 -0800 (PST) Received: from dg-rtp.dg.com (dg-rtp.rtp.dg.com [128.222.1.2]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id TAA09709 for ; Tue, 25 Feb 1997 19:20:39 -0800 (PST) Received: by dg-rtp.dg.com (5.4R3.10/dg-rtp-v02) id AA09794; Tue, 25 Feb 1997 22:20:04 -0500 Received: from ponds by dg-rtp.dg.com.rtp.dg.com; Tue, 25 Feb 1997 22:20 EST Received: from lakes.water.net (lakes [10.0.0.3]) by ponds.water.net (8.8.3/8.7.3) with ESMTP id TAA18143; Tue, 25 Feb 1997 19:43:45 -0500 (EST) Received: (from rivers@localhost) by lakes.water.net (8.8.3/8.6.9) id TAA19064; Tue, 25 Feb 1997 19:48:58 -0500 (EST) Date: Tue, 25 Feb 1997 19:48:58 -0500 (EST) From: Thomas David Rivers Message-Id: <199702260048.TAA19064@lakes.water.net> To: ponds!freefall.cdrom.com!freebsd-hackers, ponds!nemeton.com.au!giles Subject: Re: dup alloc panic Content-Type: text Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Giles Lean writes: > > On Mon, 17 Feb 1997 19:44:08 -0500 (EST) Thomas David Rivers wrote: > > > 1) Trash inode # 7680. > > 2) newfs the file system > > I ran this in a loop for 24 hours, checking after each newfs for > damage. No dice. > > I'll try it again later with 'make world' or similar running on the > same disk to provide some load. > > Can you send me a dumpfs output for the filesystem? I'd like to see > the geometry. > > Regards, > > Giles > I've got the dumpfs output - I'm cc'ing to hackers so this will go in the archives... I don't see anything particular that "pops out" - but I'm no file system hacker. This is the output of: dumpfs /dev/rsd0a immediately after doing: newfs -b 8192 -f 1024 /dev/rsd0a [The time stamp is wrong because the machine's internal clock is confused, but I just a minute ago did this...] Recall - it's inode #7680 that's causing my problems... Let me know if there's anything I can do... - Dave Rivers - p.s. Giles - a high of 56-degrees F today in comfortable North Carolina :-) Magic 11954 time Sun Feb 9 00:25:05 1997 cylgrp dynamic inodes 4.4BSD nbfree 12308 ndir 1 nifree 30717 nffree 14 ncg 4 ncyl 50 size 102400 blocks 98479 bsize 8192 shift 13 mask 0xffffe000 fsize 1024 shift 10 mask 0xfffffc00 frag 8 shift 3 fsbtodb 1 cpg 16 bpg 4096 fpg 32768 ipg 7680 minfree 8% optim time maxcontig 7 maxbpg 2048 rotdelay 0ms headswitch 0us trackseek 0us rps 60 ntrak 1 nsect 4096 npsect 4096 spc 4096 symlinklen 60 trackskew 0 interleave 1 contigsumsize 7 nindir 2048 inopb 64 nspf 2 sblkno 16 cblkno 24 iblkno 32 dblkno 992 sbsize 2048 cgsize 6144 cgoffset 2048 cgmask 0xffffffff csaddr 992 cssize 1024 shift 9 mask 0xfffffe00 cgrotor 0 fmod 0 ronly 0 clean 1 (no rotational position table) cs[].cs_(nbfree,ndir,nifree,nffree): (3970,1,7677,14) (3974,0,7680,0) (3974,0,7680,0) (390,0,7680,0) cylinders in last group 2 blocks in last group 512 cg 0: magic 90255 tell 6000 time Sun Feb 9 00:25:05 1997 cgx 0 ncyl 16 niblk 7680 ndblk 32768 nbfree 3970 ndir 1 nifree 7677 nffree 14 rotor 0 irotor 0 frotor 0 frsum 0 0 0 0 0 0 2 sum of frsum: 14 clusters 1-6: 0 0 0 0 0 0 clusters size 7 and over: 1 clusters free: 126-4095 iused: 0-2 free: 993-999, 1001-32767 b: c0: (130) 130 c1: (256) 256 c2: (256) 256 c3: (256) 256 c4: (256) 256 c5: (256) 256 c6: (256) 256 c7: (256) 256 c8: (256) 256 c9: (256) 256 c10: (256) 256 c11: (256) 256 c12: (256) 256 c13: (256) 256 c14: (256) 256 c15: (256) 256 cg 1: magic 90255 tell 2006000 time Sun Feb 9 00:25:05 1997 cgx 1 ncyl 16 niblk 7680 ndblk 32768 nbfree 3974 ndir 0 nifree 7680 nffree 0 rotor 0 irotor 0 frotor 0 frsum 0 0 0 0 0 0 0 sum of frsum: 0 clusters 1-6: 0 1 0 0 0 0 clusters size 7 and over: 1 clusters free: 0-1, 124-4095 iused: free: 0-15, 992-32767 b: c0: (134) 134 c1: (256) 256 c2: (256) 256 c3: (256) 256 c4: (256) 256 c5: (256) 256 c6: (256) 256 c7: (256) 256 c8: (256) 256 c9: (256) 256 c10: (256) 256 c11: (256) 256 c12: (256) 256 c13: (256) 256 c14: (256) 256 c15: (256) 256 cg 2: magic 90255 tell 4006000 time Sun Feb 9 00:25:05 1997 cgx 2 ncyl 16 niblk 7680 ndblk 32768 nbfree 3974 ndir 0 nifree 7680 nffree 0 rotor 0 irotor 0 frotor 0 frsum 0 0 0 0 0 0 0 sum of frsum: 0 clusters 1-6: 0 1 0 0 0 0 clusters size 7 and over: 1 clusters free: 0-1, 124-4095 iused: free: 0-15, 992-32767 b: c0: (134) 134 c1: (256) 256 c2: (256) 256 c3: (256) 256 c4: (256) 256 c5: (256) 256 c6: (256) 256 c7: (256) 256 c8: (256) 256 c9: (256) 256 c10: (256) 256 c11: (256) 256 c12: (256) 256 c13: (256) 256 c14: (256) 256 c15: (256) 256 cg 3: magic 90255 tell 6006000 time Sun Feb 9 00:25:05 1997 cgx 3 ncyl 2 niblk 7680 ndblk 4096 nbfree 390 ndir 0 nifree 7680 nffree 0 rotor 0 irotor 0 frotor 0 frsum 0 0 0 0 0 0 0 sum of frsum: 0 clusters 1-6: 0 1 0 0 0 0 clusters size 7 and over: 1 clusters free: 0-1, 124-511 iused: free: 0-15, 992-4095 b: c0: (134) 134 c1: (256) 256 From owner-freebsd-hackers Tue Feb 25 19:30:31 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id TAA10455 for hackers-outgoing; Tue, 25 Feb 1997 19:30:31 -0800 (PST) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id TAA10445 for ; Tue, 25 Feb 1997 19:30:25 -0800 (PST) Received: (from msmith@localhost) by genesis.atrad.adelaide.edu.au (8.8.5/8.7.3) id NAA21108; Wed, 26 Feb 1997 13:59:22 +1030 (CST) From: Michael Smith Message-Id: <199702260329.NAA21108@genesis.atrad.adelaide.edu.au> Subject: Re: Ethernet driver-H/W In-Reply-To: <199702260213.SAA27939@root.com> from David Greenman at "Feb 25, 97 06:13:13 pm" To: dg@root.com Date: Wed, 26 Feb 1997 13:59:19 +1030 (CST) Cc: msmith@atrad.adelaide.edu.au, julian@whistle.com, hackers@freebsd.org X-Mailer: ELM [version 2.4ME+ PL28 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk David Greenman stands accused of saying: > >certainly at least 16K. You could contribute by teaching the 'ed' > >driver about cards with more than 16K - get an Artisoft AE2 or a > >Compex ENP16 (think that number's right), both of which can be > >configured for 64K. They both use 8390x chips. > > You should be able to set "iosiz 65536" in the kernel config file; there's > support for a user-override of the memory size using that. Hmm, I'll have to check the 83905 documentation, but I thought that it paged the RAM rather than increasing the aperture size. > David Greenman -- ]] Mike Smith, Software Engineer msmith@gsoft.com.au [[ ]] Genesis Software genesis@gsoft.com.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control. (ph) +61-8-8267-3493 [[ ]] Unix hardware collector. "Where are your PEZ?" The Tick [[ From owner-freebsd-hackers Tue Feb 25 19:50:37 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id TAA11559 for hackers-outgoing; Tue, 25 Feb 1997 19:50:37 -0800 (PST) Received: from dg-rtp.dg.com (dg-rtp.rtp.dg.com [128.222.1.2]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id TAA11553 for ; Tue, 25 Feb 1997 19:50:34 -0800 (PST) Received: by dg-rtp.dg.com (5.4R3.10/dg-rtp-v02) id AA09491; Tue, 25 Feb 1997 22:50:03 -0500 Received: from ponds by dg-rtp.dg.com.rtp.dg.com; Tue, 25 Feb 1997 22:50 EST Received: from lakes.water.net (lakes [10.0.0.3]) by ponds.water.net (8.8.3/8.7.3) with ESMTP id WAA00283 for ; Tue, 25 Feb 1997 22:15:17 -0500 (EST) Received: (from rivers@localhost) by lakes.water.net (8.8.3/8.6.9) id WAA19559 for freebsd-hackers@freefall.cdrom.com; Tue, 25 Feb 1997 22:14:29 -0500 (EST) Date: Tue, 25 Feb 1997 22:14:29 -0500 (EST) From: Thomas David Rivers Message-Id: <199702260314.WAA19559@lakes.water.net> To: ponds!freefall.cdrom.com!freebsd-hackers Subject: A wild idea on the "dup alloc" and "bad dir" panics... Content-Type: text Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk This is just a wild thought I had... We've eliminated different processors, different disk drives, different memory configurations, etc... in an attempt to determine what's common about the machines experiencing these problems. The item that's common for my two machines experiencing the problem that we haven't investigated is: Hercules Monochrome Monitor I know it's *really* reaching here, but can everyone who's involved let me know what kind of monitor they've got connected... Maybe there's something in that device driver that's trashing some random memory, or this happens during a scroll, or something like that... [It is a far stretch, admitedly, but it would explain why this only occurs on a small subset of machines...] Anyway, just a thought... - Dave Rivers - From owner-freebsd-hackers Tue Feb 25 19:50:42 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id TAA11582 for hackers-outgoing; Tue, 25 Feb 1997 19:50:42 -0800 (PST) Received: from research.gate.nec.co.jp (research.gate.nec.co.jp [202.32.8.49]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id TAA11560; Tue, 25 Feb 1997 19:50:37 -0800 (PST) Received: from sbl-gw.sbl.cl.nec.co.jp by research.gate.nec.co.jp (8.8.5+2.7Wbeta5/950912) with ESMTP id MAA27384; Wed, 26 Feb 1997 12:49:42 +0900 (JST) Received: from sirius.sbl.cl.nec.co.jp by sbl-gw.sbl.cl.nec.co.jp (8.8.5+2.7Wbeta5/3.3W6) with ESMTP id MAA08367; Wed, 26 Feb 1997 12:49:40 +0900 (JST) Received: by sirius.sbl.cl.nec.co.jp (8.7.5+2.6Wbeta6/3.3W6) with UUCP id MAA00204; Wed, 26 Feb 1997 12:49:40 +0900 (JST) Date: Wed, 26 Feb 1997 12:49:40 +0900 (JST) From: Naoki Hamada Message-Id: <199702260349.MAA00204@sirius.sbl.cl.nec.co.jp> References: <199702260311.NAA24882@ogre.devetir.qld.gov.au> To: syssgm@devetir.qld.gov.au CC: j@uriah.heep.sax.de, freebsd-hackers@FreeBSD.ORG, phk@FreeBSD.ORG In-reply-to: Stephen McKay's message of "Wed, 26 Feb 1997 13:11:14 +1000 (EST)" <199702260311.NAA24882@ogre.devetir.qld.gov.au> Subject: Re: MALLOC(3) writes to stderr... Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Stephen wrote: >Although not enforced by the kernel, file descriptors 0, 1 and 2 have a >conventional use that should always be respected. If you don't want to >see stderr output, open /dev/null as descriptor 2. Thanks. I'm going to fix the daemon in this way. Also MALLOC(3) should be changed to keep silent unless explicitly indicated, souldn't it? >Some others responded that stderr and descriptor 2 are logically different >and recommend using fileno(stderr) instead of 2. We of the old school all >know that stdio is an upstart young library, and will never be allowed to >use anything but descriptor 2 on Unix. :-) Absolutely. - nao From owner-freebsd-hackers Tue Feb 25 20:58:50 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id UAA14724 for hackers-outgoing; Tue, 25 Feb 1997 20:58:50 -0800 (PST) Received: from squirrel.tgsoft.com (squirrel.tgsoft.com [207.167.64.183]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id UAA14704 for ; Tue, 25 Feb 1997 20:58:17 -0800 (PST) Received: (from thompson@localhost) by squirrel.tgsoft.com (8.8.5/8.6.12) id UAA10751; Tue, 25 Feb 1997 20:57:33 -0800 (PST) Date: Tue, 25 Feb 1997 20:57:33 -0800 (PST) Message-Id: <199702260457.UAA10751@squirrel.tgsoft.com> From: mark thompson To: jgrosch@superior.truenorth.org CC: hackers@freefall.freebsd.org In-reply-to: message from Josef Grosch on Tue, 25 Feb 1997 08:31:53 -0800 (PST) Subject: Re: [H] Optimal computer for FreeBSD Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk From: Josef Grosch Date: Tue, 25 Feb 1997 08:31:53 -0800 (PST) >Hi, all! >My friends and I planing to use 2.1.7R-FreeBSD as main server >(DNS,Web,INND,FTP) for ours ISP network. >We want use something like this: PCI, Pentium-PRO ATX CPU, 64 Mb EDO RAM, >2x4.5 Gb SCSI, >8x SCSI CD-ROM, 10Mbit Ethernet. Please, recommend us hardware (firm, >model) known as best >(reliable, fast) working under 2.1.7R-FreeBSD (PCI devices if possible). > >--- >CPU: Intel 133Mhz. are a goof buy now. 200Mhz are damn pricey >Motherboard: Asus Motherboards are very good. I have never heard anything bad about them. Make sure the chip set is a Triton-II (Intel's 430HX PCIset) >SCSI Host adapter: I have had very good luck with Adaptec controllers. The 2940 is a very good PCI SCSI controller. I am going to put in a plug for IWILL. They sell motherboards with the SCSI built right in. I got one. It works just fine. -mark From owner-freebsd-hackers Tue Feb 25 21:34:31 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id VAA16199 for hackers-outgoing; Tue, 25 Feb 1997 21:34:31 -0800 (PST) Received: from sendero.i-connect.net ([206.190.144.100]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id VAA16159 for ; Tue, 25 Feb 1997 21:34:26 -0800 (PST) Received: (from shimon@localhost) by sendero.i-connect.net (8.8.5/8.8.4) id WAA26112 for freebsd-hackers@freebsd.org; Tue, 25 Feb 1997 22:34:28 -0800 (PST) Resent-Message-Id: <199702260634.WAA26112@sendero.i-connect.net> Message-ID: X-Mailer: XFMail 1.1-alpha [p0] on FreeBSD Content-Type: text/plain; charset=iso-8859-8 Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Resent-Date: Tue, 25 Feb 1997 22:11:07 -0800 (PST) Resent-From: Simon Shapiro Resent-To: freebsd-scsi@freebsd.org Date: Tue, 25 Feb 1997 22:33:38 -0800 (PST) Organization: iConnect Corp. From: Simon Shapiro To: freebsd-hackers@freebsd.org Subject: FW: SCSI HBA QUESTION - IMPORTANT (long) Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk ----- Forwarded Message ----: SCSI HBA QUESTION - IMPORTANT (long)----- Content-Type: text/plain; charset=iso-8859-8 Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Date: Tue, 25 Feb 1997 22:11:07 -0800 (PST) Organization: iConnect Corp. XFMstatus: 0400 From: Simon Shapiro To: freebsd-scsi@freebsd.org Subject: SCSI HBA QUESTION - IMPORTANT (long) Hi Y'all! I am finally starting to debug the DPT driver. Here is what I have. There is a question at the end: The following is a trace of kernel messages. It has compiled with option SCSIDEBUG, which does not seem to help me much :-( chip2 rev 2 on pci0:7:1 <-- Last before SCSI dpt0 rev 2 int a irq 11 on pci0:17 dpt_alloc(0, ef80, 0xf148ac00) <-- Allocates a softc, etc. Seems OK. get_board_data(ef80, 0) <-- Gets much infor from the DPT. Seems OK dpt_intr_mode(0xef80, 1) <-- Disables interrupts from the DPT dpt_send_immediate(ef80, 0, 4, 0, 0) <-- Sends immediate commands dpt_send_eata_command(f10c7f00, ef80, ff, 0) <-- Sends regular commands dpt_intr_mode(0xef80, 0) <-- Enables interrupts from the DPT dpt_send_immediate(ef80, 0, 4, 1, 0) <-- Sends another immediate command dpt_alloc_freelist(0xf148cc00) <-- Allocates a chunk of CCB's dpt0: Total CCB's increased by 64 to 64 <-- From dpt_alloc_freelist dpt_alloc(0, ef80, 0xf148ac00) <-- End of this function dpt_attach(0xf148cc00) <-- Sets up the scsi_link ndx = 0, channels = 1 <- This DPT has only one channel [597] <-- Just before scbus = scsi_alloc_bus() [600] <-- scsi_alloc_bus() returned non-zero dpt0 waiting for scsi devices to settle <-- From scsi_alloc_bus?? [611] <-- Just after scsi_attachdevs(scbus) returned [614] <-- the scsi-alloc_bus()/scsi_attachdevs() loop exited. ahc0 rev 0 int a irq 10 on pci0:18 ahc0: aic7880 Single Channel, SCSI Id=7, 16 SCBs ahc0 waiting for scsi devices to settle (ahc0:0:0): "SEAGATE ST51080N 0913" type 0 fixed SCSI 2 Now, the conf file for this kernel looks (for the DPT) like: controller ahc0 controller scbus0 at ahc0 controller dpt0 controller scbus1 at dpt0 controller scbus2 at dpt0 controller scbus3 at dpt0 disk sd0 at scbus0 target 0 unit 0 disk sd1 at scbus0 target 1 unit 0 disk sd3 at scbus1 target 0 unit 0 QUESTION: Assuming someone can sort through this, what do I need to do to convince scsi_attachdevs() to actually do something with the DPT? It sees the Adaptec allright, but makes no attempt to call on the DPT. Thanx! Simon -------------End of forwarding message------------------------- From owner-freebsd-hackers Tue Feb 25 21:58:06 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id VAA17207 for hackers-outgoing; Tue, 25 Feb 1997 21:58:06 -0800 (PST) Received: from w2xo.pgh.pa.us (w2xo.pgh.pa.us [206.210.70.5]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id VAA17195 for ; Tue, 25 Feb 1997 21:58:00 -0800 (PST) Received: from w2xo.pgh.pa.us (localhost [127.0.0.1]) by w2xo.pgh.pa.us (8.8.4/8.8.4) with SMTP id AAA13883; Wed, 26 Feb 1997 00:57:55 -0500 (EST) Message-ID: <3313D0E2.446B9B3D@w2xo.pgh.pa.us> Date: Wed, 26 Feb 1997 00:57:54 -0500 From: Jim Durham Organization: Dis- X-Mailer: Mozilla 3.01Gold (X11; I; FreeBSD 2.1.6-RELEASE i386) MIME-Version: 1.0 To: "Jordan K. Hubbard" CC: Chris Shenton , hackers@FreeBSD.org Subject: Re: migrating 2.1.7 -> 2.2: simple or hairy? References: <1610.856818267@time.cdrom.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk Jordan K. Hubbard wrote: > > > We've got a number of boxes running 2.1.7 and want to migrate to 2.2; > > is it easy or hard? > > It depends on how many short-cuts you try to take. :-) > > Seriously, until there are better transition tools available which > radically compare checksum information and try to tell you exactly > what was added and what was deleted twixt the two releases (and that's > all part of my next project), the most dependable upgrade path is to > back up user files or make sure they're always kept on OS-neutral > partitions (so you can simply mount rather than newfs those > filesystems next time around - I do this all the time) and do a > complete reinstallation. > > I know it sounds painful, but once you get the procedure down to a > science it's really not that bad, and the benefits are that you're > *sure* you haven't got old-library pollution or out-of-date /etc files > or any of the other 101 weird behavior quirks that an update-by-source > (or even update-by-upgrade) machine can exhibit. Look at it as a > little extra pain up-front in exchange for avoiding it at later, less > convenient times. :-) > Jordan One thing I do here is let "ls -lt | more" be my friend. Looking at /etc, you can see all the files that have been modified after the system was installed, like sysconfig and services, etc. I save these out to a "safe" place so that I can at least reconstruct the system. I run diffs on the new and old file versions after the new version is installed. If I see only changes I made, I just copy the old file back. If I see it's a new version of the file, then at least I have a guide to modify the new version to do the same job as the old. BTW, it would be a nice addition to "locate" to allow it to search for files later than the install date in directories like /etc and /bin or /sbin. (lots of stuff deleted) > > > > Any other pointers, like maybe building in a separate /usr/src-new > > tree? > > > > Thanks. -Jim Durham From owner-freebsd-hackers Tue Feb 25 22:10:45 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id WAA18163 for hackers-outgoing; Tue, 25 Feb 1997 22:10:45 -0800 (PST) Received: from mx.serv.net (mx.serv.net [199.201.191.10]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id WAA18141; Tue, 25 Feb 1997 22:10:33 -0800 (PST) Received: from MindBender.serv.net by mx.serv.net (8.7.5/SERV Revision: 2.30) id WAA14627; Tue, 25 Feb 1997 22:10:31 -0800 (PST) Received: from localhost.HeadCandy.com (michaelv@localhost.HeadCandy.com [127.0.0.1]) by MindBender.serv.net (8.7.5/8.7.3) with SMTP id WAA29342; Tue, 25 Feb 1997 22:10:16 -0800 (PST) Message-Id: <199702260610.WAA29342@MindBender.serv.net> X-Authentication-Warning: MindBender.serv.net: Host michaelv@localhost.HeadCandy.com [127.0.0.1] didn't use HELO protocol To: Tom Samplonius cc: "Vnotchenko S.S." , freebsd-isp@freebsd.org, freebsd-hackers@freebsd.org Subject: Re: [H] Optimal computer for FreeBSD In-reply-to: Your message of Tue, 25 Feb 97 02:19:53 -0800. Date: Tue, 25 Feb 1997 22:10:15 -0800 From: "Michael L. VanLoon -- HeadCandy.com" Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >> We want use something like this: PCI, Pentium-PRO ATX CPU, 64 Mb EDO RAM, > Always use parity RAM on servers, especially if you are buying >everything from scratch. > EDO doesn't give you much of a improvement if your motherboard supports >pipeline-burst-cache. My guess is that it doesn't, since the cache is built into the CPU... :-) ----------------------------------------------------------------------------- Michael L. VanLoon michaelv@MindBender.serv.net --< Free your mind and your machine -- NetBSD free un*x >-- NetBSD working ports: 386+PC, Mac 68k, Amiga, Atari 68k, HP300, Sun3, Sun4/4c/4m, DEC MIPS, DEC Alpha, PC532, VAX, MVME68k, arm32... NetBSD ports in progress: PICA, others... ----------------------------------------------------------------------------- From owner-freebsd-hackers Tue Feb 25 22:17:08 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id WAA18784 for hackers-outgoing; Tue, 25 Feb 1997 22:17:08 -0800 (PST) Received: from yakko.my.domain (man-as6s43.erols.com [207.96.1.107]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id WAA18779 for ; Tue, 25 Feb 1997 22:17:03 -0800 (PST) Received: (from lee@localhost) by yakko.my.domain (8.8.3/8.8.3) id BAA01703; Wed, 26 Feb 1997 01:16:14 -0500 (EST) From: Lee Cremeans Message-Id: <199702260616.BAA01703@yakko.my.domain> Subject: Re: Ensoniq Soundscape VIVO 90 PnP To: pasqual@hal.t.u-tokyo.ac.jp (Ajith Pasqual) Date: Wed, 26 Feb 1997 01:16:13 -0500 (EST) Cc: freebsd-hackers@freebsd.org Reply-To: mcampbel@erols.com In-Reply-To: <199702260206.LAA19057@mayu.hal.t.u-tokyo.ac.jp> from "Ajith Pasqual" at Feb 26, 97 11:06:01 am X-Mailer: ELM [version 2.4 PL23] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > Hi!, > > Has any one got an Ensoniq SoundScape VIVO 90 PnP working with FreeBSD 2.1.6 > ? I've tried many options in the kernel (following tips from Mailing Archive, > FAQ etc.,) but still couldn't get any sound out of it ? > Boot probe says sb0 not found at 0x220. > > This card has Sound Blaster Emulation at port 0x220. > Are you using Sujal Patel's ISA PnP patches? It sounds like you may need them. Go see http://www.freebsd.org/~smpatel and have a look. Lee C. and yes, my hostname is bogus...darn dynamic IP From owner-freebsd-hackers Tue Feb 25 22:43:57 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id WAA20491 for hackers-outgoing; Tue, 25 Feb 1997 22:43:57 -0800 (PST) Received: from cold.org (cold.org [206.81.134.103]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id WAA20486 for ; Tue, 25 Feb 1997 22:43:55 -0800 (PST) Received: from localhost (brandon@localhost) by cold.org (8.8.5/8.8.3) with SMTP id XAA02054 for ; Tue, 25 Feb 1997 23:43:58 -0700 (MST) Date: Tue, 25 Feb 1997 23:43:58 -0700 (MST) From: Brandon Gillespie To: freebsd-hackers@freebsd.org Subject: what 'dialog' library is used with sysinstall and what not? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Basically, what is the text library used with sysinstall and the pkg_* utils? I was under the impression it was 'dialog', but 'dialog' is rather restricted... My reason for asking is a have a rather robust library for adding/removing/updating users, as well as editing the groups file, shells file and other similar functions--I was thinking of putting it into a windowed interface like the other FreeBSD utils, but 'dialog' is greatly lacking some of the features seen in the above mentioned utils. -Brandon Gillespie From owner-freebsd-hackers Tue Feb 25 23:10:51 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id XAA22622 for hackers-outgoing; Tue, 25 Feb 1997 23:10:51 -0800 (PST) Received: from phoenix.its.rpi.edu (dec@phoenix.its.rpi.edu [128.113.161.45]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id XAA22617 for ; Tue, 25 Feb 1997 23:10:46 -0800 (PST) Received: (from dec@localhost) by phoenix.its.rpi.edu (8.8.4/8.8.3) id CAA04697 for hackers@freebsd.org; Wed, 26 Feb 1997 02:11:14 -0500 (EST) Date: Wed, 26 Feb 1997 02:11:14 -0500 (EST) From: "David E. Cross" Message-Id: <199702260711.CAA04697@phoenix.its.rpi.edu> To: hackers@freebsd.org Subject: crt0.o hole... Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I am finally getting arround to patching that hole... could someone tell me where a sample exploit program is? The one that was originally used against me was "crtbsd". I just want to make sure that I got it right. -- David Cross ACS Consultant From owner-freebsd-hackers Tue Feb 25 23:29:33 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id XAA23446 for hackers-outgoing; Tue, 25 Feb 1997 23:29:33 -0800 (PST) Received: from pahtoh.cwu.edu (root@pahtoh.cwu.edu [198.104.65.27]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id XAA23431 for ; Tue, 25 Feb 1997 23:29:20 -0800 (PST) Received: from opus.cts.cwu.edu (skynyrd@opus.cts.cwu.edu [198.104.92.71]) by pahtoh.cwu.edu (8.6.13/8.6.9) with ESMTP id XAA08589; Tue, 25 Feb 1997 23:29:14 -0800 Received: from localhost (skynyrd@localhost) by opus.cts.cwu.edu (8.8.5/8.8.5) with SMTP id XAA22434; Tue, 25 Feb 1997 23:29:12 -0800 (PST) Date: Tue, 25 Feb 1997 23:29:12 -0800 (PST) From: Chris Timmons To: John Fieber cc: Nik Clayton , hackers@FreeBSD.org Subject: Re: 2.1.7: ncr and de driver increasingly fickle In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk I can tell you that I have beat the death out of a pair of seagate hawks, a (clunky but so far reliable) seagate decathalon, and one of those infamous Micra^Hopolis 3243 4GB screamin' lemons with 2.1.6.1 and 2.2 using SC200's with nary an ncr diagnostic. It seems unlikely that I missed too much between 2.1.6.1 and 2.1.7 for there to have been a significant bug introduced into the ncr code. Has anyone asked Stephan about this yet? I really have been giving ncr a workout and haven't seen this at all. It might be good to look for any firmware upgrades that might be relevent to the fuji disks. I was seeing a problem with the quantum 4GB wide disks which Justin Gibbs ultimately traced back to a firmware problem in the drive itself. In that case many people first believed it was a driver problem when in fact it was the drives themselves! Good luck! -Chris On Tue, 25 Feb 1997, John Fieber wrote: > Curious. Am I correct in observing that everyone reporting this > problem with the ncr driver, including myself, has a Fujitsu > disk? > > Looking through the mailing list archives I found previous > mention that the error might indicate bad cabling, but I tried a > bunch of different cables and configurations of devices on the > bus with no change in behavior. > > -john > From owner-freebsd-hackers Tue Feb 25 23:50:16 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id XAA24339 for hackers-outgoing; Tue, 25 Feb 1997 23:50:16 -0800 (PST) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id XAA24334 for ; Tue, 25 Feb 1997 23:50:13 -0800 (PST) Received: from time.cdrom.com (jkh@localhost [127.0.0.1]) by time.cdrom.com (8.8.5/8.6.9) with ESMTP id XAA14523; Tue, 25 Feb 1997 23:49:59 -0800 (PST) To: Brandon Gillespie cc: freebsd-hackers@FreeBSD.ORG Subject: Re: what 'dialog' library is used with sysinstall and what not? In-reply-to: Your message of "Tue, 25 Feb 1997 23:43:58 MST." Date: Tue, 25 Feb 1997 23:49:59 -0800 Message-ID: <14519.856943399@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > Basically, what is the text library used with sysinstall and the pkg_* > utils? I was under the impression it was 'dialog', but 'dialog' is rather > restricted... It's libdialog(3) (dialog(1) just uses it). > file and other similar functions--I was thinking of putting it into a > windowed interface like the other FreeBSD utils, but 'dialog' is greatly > lacking some of the features seen in the above mentioned utils. Exactly. See /usr/ports/devel/tvision for what I'm currently in the process of moving to. :-) Jordan From owner-freebsd-hackers Wed Feb 26 00:04:04 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id AAA24693 for hackers-outgoing; Wed, 26 Feb 1997 00:04:04 -0800 (PST) Received: from cheops.anu.edu.au (avalon@cheops.anu.edu.au [150.203.76.24]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id AAA24645 for ; Wed, 26 Feb 1997 00:03:57 -0800 (PST) Message-Id: <199702260803.AAA24645@freefall.freebsd.org> Received: by cheops.anu.edu.au (1.37.109.16/16.2) id AA161984197; Wed, 26 Feb 1997 19:03:17 +1100 From: Darren Reed Subject: Re: sysinstall & disk labelling. To: jkh@time.cdrom.com (Jordan K. Hubbard) Date: Wed, 26 Feb 1997 19:03:17 +1100 (EDT) Cc: hackers@freebsd.org In-Reply-To: <13153.856912804@time.cdrom.com> from "Jordan K. Hubbard" at Feb 25, 97 03:20:04 pm X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In some mail from Jordan K. Hubbard, sie said: > > > Can I mention that the disk labelling which happened straight after > > you had partitioned was actually very useful ? It appears to now > > occur at some other time ? > > On what do you base this assumption? I haven't changed anything > WRT that.. :-) Hmmm....I used to have a disk that was Windows-DOS/FreeBSD dual boot, so I installed NT in the Windows-DOS partition and it trashed by booteasy bootblock. I've tried re-partitioning and putting booteasy back there, but to no avail. Darren From owner-freebsd-hackers Wed Feb 26 00:16:36 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id AAA25033 for hackers-outgoing; Wed, 26 Feb 1997 00:16:36 -0800 (PST) Received: from bofh.cybercity.dk (bofh.cybercity.dk [195.8.128.254]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id AAA25028 for ; Wed, 26 Feb 1997 00:16:33 -0800 (PST) Received: from critter.dk.tfs.com ([140.145.230.252]) by bofh.cybercity.dk (8.8.3/8.7.3) with ESMTP id JAA16490; Wed, 26 Feb 1997 09:18:29 +0100 (MET) Received: from critter.dk.tfs.com (localhost [127.0.0.1]) by critter.dk.tfs.com (8.8.2/8.8.2) with ESMTP id JAA07997; Wed, 26 Feb 1997 09:19:33 +0100 (MET) To: Naoki Hamada cc: syssgm@devetir.qld.gov.au, j@uriah.heep.sax.de, freebsd-hackers@FreeBSD.ORG Subject: Re: MALLOC(3) writes to stderr... In-reply-to: Your message of "Wed, 26 Feb 1997 12:49:40 +0900." <199702260349.MAA00204@sirius.sbl.cl.nec.co.jp> Date: Wed, 26 Feb 1997 09:19:33 +0100 Message-ID: <7995.856945173@critter.dk.tfs.com> From: Poul-Henning Kamp Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk In message <199702260349.MAA00204@sirius.sbl.cl.nec.co.jp>, Naoki Hamada writes : >Stephen wrote: >>Although not enforced by the kernel, file descriptors 0, 1 and 2 have a >>conventional use that should always be respected. If you don't want to >>see stderr output, open /dev/null as descriptor 2. > >Thanks. I'm going to fix the daemon in this way. > >Also MALLOC(3) should be changed to keep silent unless explicitly >indicated, souldn't it? Malloc(3) would be in it's good right to simply coredump your process in any case where it will write to fd#2. It only does this after detected interface violations. I have considered adding a callback for reporting these kind of violations so that programs could register other handlers for it. -- Poul-Henning Kamp | phk@FreeBSD.ORG FreeBSD Core-team. http://www.freebsd.org/~phk | phk@login.dknet.dk Private mailbox. whois: [PHK] | phk@tfs.com TRW Financial Systems, Inc. Power and ignorance is a disgusting cocktail. From owner-freebsd-hackers Wed Feb 26 00:22:47 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id AAA25230 for hackers-outgoing; Wed, 26 Feb 1997 00:22:47 -0800 (PST) Received: from aeffle.Stanford.EDU (sequence.Stanford.EDU [171.65.76.7]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id AAA25225 for ; Wed, 26 Feb 1997 00:22:46 -0800 (PST) Received: (from hlew@localhost) by aeffle.Stanford.EDU (8.8.4/8.6.6) id AAA27941; Wed, 26 Feb 1997 00:22:36 -0800 (PST) Date: Wed, 26 Feb 1997 00:22:36 -0800 (PST) From: Howard Lew To: J Wunsch cc: fadorno@sm1.gte.net, freebsd-hackers@freefall.freebsd.org Subject: Re: Exabyte's TR-3 Eagle Nest In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Tue, 25 Feb 1997, J Wunsch wrote: > As Fred Adorno wrote: > > > Can someone tell me how to configure this drive in my kernel and how to > > test the installation? > > Sure, if you tell us what kind of beast it is, instead of silently > assuming we already knew it? I have one too, but it's a floppy port monster and supposed to be compatible with MC3000XL, QIC-Wide, Travan TR-3, and QIC-Extra. It is read/write compatible with TR-3 QIC-3020, TR-2 QIC-3010 and backward read compatible with QIC-80. > > -- > 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-hackers Wed Feb 26 01:38:02 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id BAA27939 for hackers-outgoing; Wed, 26 Feb 1997 01:38:02 -0800 (PST) Received: from luoqi.watermarkgroup.com (ppp-3.ts-1.ptn.idt.net [169.132.64.3]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id BAA27927 for ; Wed, 26 Feb 1997 01:37:56 -0800 (PST) Received: from sabrina (localhost.idt.net [127.0.0.1]) by luoqi.watermarkgroup.com (8.8.4/8.6.12) with SMTP id EAA00391 for ; Wed, 26 Feb 1997 04:37:52 -0500 (EST) Message-ID: <3314046F.167EB0E7@watermarkgroup.com> Date: Wed, 26 Feb 1997 04:37:51 -0500 From: Luoqi Chen X-Mailer: Mozilla 3.0Gold (X11; I; FreeBSD 2.2-GAMMA i386) MIME-Version: 1.0 To: freebsd-hackers@freebsd.org Subject: Adaptec AVA-1515 asserts wrong IRQ?! Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk A while ago, I remembered, someone said that there was no irq coming back from the card. It turned out that the card asserted the wrong irq line! I set both irq jumpers on the AVA-1515 (why it needs two?) to 11, the default. Reboot. As usual, it could detect the hard drive connected to it and return the geometry during booting. But any scsi command sent to it was timed out. But when I looked the pending irq interrupts at 0xa0 (IO_ICU2), it was 0x40, that's irq 10! No wonder there was no interrupt from the card. This also explains why it could mess up with other cards as some people complained. After booted from a recompiled kernel with irq 10, I was able to execute some scsi commands and failed to read anything off the hard drive. I still need to look into that. Now I have a question, I was able to use this card from NT, and if i remembered correctly, NT detected that the irq was 11. How was NT able to do that? -lq From owner-freebsd-hackers Wed Feb 26 01:40:49 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id BAA28077 for hackers-outgoing; Wed, 26 Feb 1997 01:40:49 -0800 (PST) Received: from murkwood.gaffaneys.com (dialup14.gaffaneys.com [134.129.252.33]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id BAA28071 for ; Wed, 26 Feb 1997 01:40:45 -0800 (PST) Received: (from zach@localhost) by murkwood.gaffaneys.com (8.8.5/8.8.5) id DAA25345; Wed, 26 Feb 1997 03:42:57 -0600 (CST) To: Michael Hancock Cc: Peter Haight , freebsd-hackers@FreeBSD.org Subject: Re: Static variables in shared libraries References: Mime-Version: 1.0 (generated by tm-edit 7.103) Content-Type: text/plain; charset=US-ASCII From: Zach Heilig Date: 26 Feb 1997 03:42:56 -0600 In-Reply-To: Michael Hancock's message of Tue, 25 Feb 1997 22:01:57 +0900 (JST) Message-ID: <87rai36gyn.fsf@murkwood.gaffaneys.com> Lines: 15 X-Mailer: Gnus v5.4.15/Emacs 19.34 Sender: owner-hackers@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk >>>>> "Michael" == Michael Hancock writes: > Try news:comp.lang.c. "The C book" is also a necessity. You'll probably be flamed to hell and back there for posting about unix-specific (or -specific) code, a better bet would be news:comp.unix.programmer Of course they all will probably send you back over here, since you are using FreeBSD :-) -- Zach Heilig (zach@blizzard.gaffaneys.com) | ALL unsolicited commercial email Support bacteria -- it's the only | is unwelcome. I avoid dealing form of culture some people have! | with companies that email ads. From owner-freebsd-hackers Wed Feb 26 01:52:37 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id BAA28568 for hackers-outgoing; Wed, 26 Feb 1997 01:52:37 -0800 (PST) Received: from ghpc6.ihf.rwth-aachen.de (ghpc6.ihf.RWTH-Aachen.DE [134.130.90.6]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id BAA28561 for ; Wed, 26 Feb 1997 01:52:30 -0800 (PST) Received: (from thomas@localhost) by ghpc6.ihf.rwth-aachen.de (8.6.12/8.6.9) id KAA10383; Wed, 26 Feb 1997 10:52:08 +0100 From: Thomas Gellekum Message-Id: <199702260952.KAA10383@ghpc6.ihf.rwth-aachen.de> Subject: Re: what 'dialog' library is used with sysinstall and what not? To: jkh@time.cdrom.com (Jordan K. Hubbard) Date: Wed, 26 Feb 1997 10:52:07 +0100 (MET) Cc: brandon@cold.org, freebsd-hackers@freebsd.org In-Reply-To: <14519.856943399@time.cdrom.com> from "Jordan K. Hubbard" at "Feb 25, 97 11:49:59 pm" Organization: Institut f. Hochfrequenztechnik, RWTH Aachen X-Mailer: ELM [version 2.4ME+ PL11 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Jordan K. Hubbard wrote: > > Exactly. See /usr/ports/devel/tvision for what I'm currently in the > process of moving to. :-) tvision is unusable on with a sane terminal setting like cons25l1 (which IMHO should be the default for syscons) or with pcvt or an xterm. libdialog is at least terminal independent. tg From owner-freebsd-hackers Wed Feb 26 02:38:35 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id CAA00224 for hackers-outgoing; Wed, 26 Feb 1997 02:38:35 -0800 (PST) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id CAA00219 for ; Wed, 26 Feb 1997 02:38:32 -0800 (PST) Received: from time.cdrom.com (jkh@localhost [127.0.0.1]) by time.cdrom.com (8.8.5/8.6.9) with ESMTP id CAA25886; Wed, 26 Feb 1997 02:38:12 -0800 (PST) To: Thomas Gellekum cc: brandon@cold.org, freebsd-hackers@freebsd.org Subject: Re: what 'dialog' library is used with sysinstall and what not? In-reply-to: Your message of "Wed, 26 Feb 1997 10:52:07 +0100." <199702260952.KAA10383@ghpc6.ihf.rwth-aachen.de> Date: Wed, 26 Feb 1997 02:38:12 -0800 Message-ID: <25882.856953492@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > tvision is unusable on with a sane terminal setting like cons25l1 > (which IMHO should be the default for syscons) or with pcvt or an > xterm. libdialog is at least terminal independent. libdialog is a terminal independent P.O.S. (no explanation of that acronym should be necessary :) and I've gone as far as I can go with it - it MUST go. tvision works just great with cons25 (which is the default I've always used and will continue to use especially if cons25l1 is broken with tvision :-) and with an standard xterm - it looks not nearly so nice as in a color-xterm, sure, but I'd hardly call it "unusable." I've run many of the demos in monochrome mode and they're perfectly drivable. Certainly no worse than libdialog in monochrome, which I've also tested, given its penchant for using colors which just about disappear on freefall's Hercules graphics card. In any case, the point is moot. I've been waiting for 2 years for a usable CUI library, it's not appeared, and this library is the first serious attempt I've ever seen at trying to make the whole CUI interface usable. The other attempts just took a GUI framework and attempted to cram it into a CUI imitation, something which generally results in a truly horrible looking interface. libtvision looks pretty darn good, considering the limitations it has to work under, and it's *really really* easy to write code for. I'm sold, I'm using it in sysinstall II (setup), better get used to the idea. :-) Jordan From owner-freebsd-hackers Wed Feb 26 04:17:05 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id EAA04309 for hackers-outgoing; Wed, 26 Feb 1997 04:17:05 -0800 (PST) Received: from mail.MCESTATE.COM (vince@mail.MCESTATE.COM [206.171.98.50]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id EAA04304; Wed, 26 Feb 1997 04:16:59 -0800 (PST) Received: from localhost (vince@localhost) by mail.MCESTATE.COM (8.8.5/8.8.5) with SMTP id EAA01580; Wed, 26 Feb 1997 04:14:42 -0800 (PST) Date: Wed, 26 Feb 1997 04:14:41 -0800 (PST) From: Vincent Poy To: "Michael L. VanLoon -- HeadCandy.com" cc: Tom Samplonius , "Vnotchenko S.S." , freebsd-isp@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG Subject: Re: [H] Optimal computer for FreeBSD In-Reply-To: <199702260610.WAA29342@MindBender.serv.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Tue, 25 Feb 1997, Michael L. VanLoon -- HeadCandy.com wrote: > > Always use parity RAM on servers, especially if you are buying > >everything from scratch. > > EDO doesn't give you much of a improvement if your motherboard supports > >pipeline-burst-cache. > > My guess is that it doesn't, since the cache is built into the CPU... > :-) Actually, from what Rodney Grimes had told me, the cache built into the CPU is the L1 (Level 1) cache while the L2 cache is the cache on the motherboard, with Pipeline Burst Caching, it will give like the same improvement EDO ram will give with a non-PBC Cache but if used in conjunction with PBC, the increase isn't that big to make much of a difference. Cheers, Vince - vince@MCESTATE.COM - vince@GAIANET.NET ________ __ ____ Unix Networking Operations - FreeBSD-Real Unix for Free / / / / | / |[__ ] GaiaNet Corporation - M & C Estate / / / / | / | __] ] Beverly Hills, California USA 90210 / / / / / |/ / | __] ] HongKong Stars/Gravis UltraSound Mailing Lists Admin /_/_/_/_/|___/|_|[____] From owner-freebsd-hackers Wed Feb 26 04:28:07 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id EAA04974 for hackers-outgoing; Wed, 26 Feb 1997 04:28:07 -0800 (PST) Received: from parkplace.cet.co.jp (parkplace.cet.co.jp [202.32.64.1]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id EAA04969 for ; Wed, 26 Feb 1997 04:28:03 -0800 (PST) Received: from localhost (michaelh@localhost) by parkplace.cet.co.jp (8.8.5/CET-v2.1) with SMTP id MAA23796; Wed, 26 Feb 1997 12:27:47 GMT Date: Wed, 26 Feb 1997 21:27:47 +0900 (JST) From: Michael Hancock Reply-To: Michael Hancock To: Zach Heilig cc: Peter Haight , freebsd-hackers@FreeBSD.org Subject: Re: Static variables in shared libraries In-Reply-To: <87rai36gyn.fsf@murkwood.gaffaneys.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk On 26 Feb 1997, Zach Heilig wrote: > >>>>> "Michael" == Michael Hancock writes: > > > Try news:comp.lang.c. "The C book" is also a necessity. > > You'll probably be flamed to hell and back there for posting about > unix-specific (or -specific) code, a better bet would be > news:comp.unix.programmer > > Of course they all will probably send you back over here, since you > are using FreeBSD :-) $ vi foo.c #include const char* test_3 = "hello"; const char* test_4 = test_3; main() { printf("test_3 = %s\n", test_3); printf("test_4 = %s\n", test_4); return 0; } :wq $ lint foo.c (4) error: non-constant initializer: op "NAME" lint: errors in foo.c; no output created lint: pass2 not run - errors in foo.c Ok, this doesn't even compile. But if he's using auto-variables then the only thing I can think of is that the printf's are in his program while the variables are in the shared lib so he is trying to print something that's already been released and partially reused for something else. I could be wrong but it just smells more like a C problem than anything to do with the shared library facility. Regards, Mike "That's not a bug, that's a feature." ;-) From owner-freebsd-hackers Wed Feb 26 04:43:20 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id EAA05358 for hackers-outgoing; Wed, 26 Feb 1997 04:43:20 -0800 (PST) Received: from deepo.prosa.dk ([193.89.187.27]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id EAA05350 for ; Wed, 26 Feb 1997 04:43:10 -0800 (PST) Received: (from regnauld@localhost) by deepo.prosa.dk (8.8.5/8.8.4/prosa-1.1) id NAA09314; Wed, 26 Feb 1997 13:44:55 +0100 (CET) Message-ID: Date: Wed, 26 Feb 1997 13:44:55 +0100 From: regnauld@deepo.prosa.dk (Philippe Regnauld) To: vince@mail.MCESTATE.COM (Vincent Poy) Cc: freebsd-hackers@freebsd.org Subject: Re: [H] Optimal computer for FreeBSD References: <199702260610.WAA29342@MindBender.serv.net> X-Mailer: Mutt 0.58 Mime-Version: 1.0 X-Operating-System: FreeBSD 2.2-BETA_A i386 In-Reply-To: ; from Vincent Poy on Feb 26, 1997 04:14:41 -0800 Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Vincent Poy (vince) ecrit/writes: > improvement EDO ram will give with a non-PBC Cache but if used in > conjunction with PBC, the increase isn't that big to make much of a > difference. Conclusion: use Parity RAM, but EDO is unnecessary :-) -- -- Phil -[ Philippe Regnauld / Systems Administrator / regnauld@prosa.dk ]- -[ Location.: +55.4N +11.3E PGP Key: finger regnauld@deepo.prosa.dk ]- From owner-freebsd-hackers Wed Feb 26 05:06:31 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id FAA05923 for hackers-outgoing; Wed, 26 Feb 1997 05:06:31 -0800 (PST) Received: from zwei.siemens.at (zwei.siemens.at [193.81.246.12]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id FAA05918; Wed, 26 Feb 1997 05:06:22 -0800 (PST) Received: from sol1.gud.siemens.co.at (root@[10.1.143.100]) by zwei.siemens.at (8.7.5/8.7.3) with SMTP id OAA12605; Wed, 26 Feb 1997 14:07:44 +0100 (MET) Received: from ws2301.gud.siemens.co.at by sol1.gud.siemens.co.at with smtp (Smail3.1.28.1 #7 for ) id m0vzj38-0001zDC; Wed, 26 Feb 97 14:05 MET Received: by ws2301.gud.siemens.co.at (1.37.109.16/1.37) id AA083142096; Wed, 26 Feb 1997 14:01:36 +0100 From: "Hr.Ladavac" Message-Id: <199702261301.AA083142096@ws2301.gud.siemens.co.at> Subject: Re: [H] Optimal computer for FreeBSD To: vince@mail.MCESTATE.COM (Vincent Poy) Date: Wed, 26 Feb 1997 14:01:36 +0100 (MEZ) Cc: michaelv@MindBender.serv.net, tom@sdf.com, sergey@extech.msk.su, freebsd-isp@freebsd.org, freebsd-hackers@freebsd.org In-Reply-To: from "Vincent Poy" at Feb 26, 97 04:14:41 am X-Mailer: ELM [version 2.4 PL24 ME8a] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk E-mail message from Vincent Poy contained: > On Tue, 25 Feb 1997, Michael L. VanLoon -- HeadCandy.com wrote: > > > > Always use parity RAM on servers, especially if you are buying > > >everything from scratch. > > > EDO doesn't give you much of a improvement if your motherboard supports > > >pipeline-burst-cache. > > > > My guess is that it doesn't, since the cache is built into the CPU... > > :-) > > Actually, from what Rodney Grimes had told me, the cache built > into the CPU is the L1 (Level 1) cache while the L2 cache is the cache on > the motherboard, with Pipeline Burst Caching, it will give like the same > improvement EDO ram will give with a non-PBC Cache but if used in > conjunction with PBC, the increase isn't that big to make much of a > difference. With the slight exception of PPro processors where both L1 and L2 caches reside in the same package, albeit on two separate pieces of sillicon... /Marino > > > Cheers, > Vince - vince@MCESTATE.COM - vince@GAIANET.NET ________ __ ____ > Unix Networking Operations - FreeBSD-Real Unix for Free / / / / | / |[__ ] > GaiaNet Corporation - M & C Estate / / / / | / | __] ] > Beverly Hills, California USA 90210 / / / / / |/ / | __] ] > HongKong Stars/Gravis UltraSound Mailing Lists Admin /_/_/_/_/|___/|_|[____] > > > From owner-freebsd-hackers Wed Feb 26 05:16:24 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id FAA06407 for hackers-outgoing; Wed, 26 Feb 1997 05:16:24 -0800 (PST) Received: from agora.rdrop.com (root@agora.rdrop.com [199.2.210.241]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id FAA06401; Wed, 26 Feb 1997 05:16:22 -0800 (PST) Received: from mail.MCESTATE.COM by agora.rdrop.com with smtp (Smail3.1.29.1 #17) id m0vzjDW-0008zXC; Wed, 26 Feb 97 05:16 PST Received: from localhost (vince@localhost) by mail.MCESTATE.COM (8.8.5/8.8.5) with SMTP id FAA01824; Wed, 26 Feb 1997 05:09:54 -0800 (PST) Date: Wed, 26 Feb 1997 05:09:53 -0800 (PST) From: Vincent Poy To: "Hr.Ladavac" cc: michaelv@MindBender.serv.net, tom@sdf.com, sergey@extech.msk.su, freebsd-isp@freebsd.org, freebsd-hackers@freebsd.org Subject: Re: [H] Optimal computer for FreeBSD In-Reply-To: <199702261301.AA083142096@ws2301.gud.siemens.co.at> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Wed, 26 Feb 1997, Hr.Ladavac wrote: > With the slight exception of PPro processors where both L1 and L2 caches > reside in the same package, albeit on two separate pieces of sillicon... But doesn't PPro motherboards still have external cache? Also, is the PPro actually the P6 chip? if this is the case, what is the code name for the Klamath 300Mhz processor Intel will be releasing? Cheers, Vince - vince@MCESTATE.COM - vince@GAIANET.NET ________ __ ____ Unix Networking Operations - FreeBSD-Real Unix for Free / / / / | / |[__ ] GaiaNet Corporation - M & C Estate / / / / | / | __] ] Beverly Hills, California USA 90210 / / / / / |/ / | __] ] HongKong Stars/Gravis UltraSound Mailing Lists Admin /_/_/_/_/|___/|_|[____] From owner-freebsd-hackers Wed Feb 26 05:24:39 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id FAA06877 for hackers-outgoing; Wed, 26 Feb 1997 05:24:39 -0800 (PST) Received: from agora.rdrop.com (root@agora.rdrop.com [199.2.210.241]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id FAA06870 for ; Wed, 26 Feb 1997 05:24:36 -0800 (PST) Received: from mail.MCESTATE.COM by agora.rdrop.com with smtp (Smail3.1.29.1 #17) id m0vzjLV-0008tQC; Wed, 26 Feb 97 05:24 PST Received: from localhost (vince@localhost) by mail.MCESTATE.COM (8.8.5/8.8.5) with SMTP id FAA01883; Wed, 26 Feb 1997 05:19:15 -0800 (PST) Date: Wed, 26 Feb 1997 05:19:14 -0800 (PST) From: Vincent Poy To: Philippe Regnauld cc: freebsd-hackers@freebsd.org Subject: Re: [H] Optimal computer for FreeBSD In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Wed, 26 Feb 1997, Philippe Regnauld wrote: > Conclusion: use Parity RAM, but EDO is unnecessary :-) Ahhh... The problem is some motherboards don't support the parity anyways and x32 is cheaper than x36. Does anyone know if EDO RAM will work on non-EDO machines? Cheers, Vince - vince@MCESTATE.COM - vince@GAIANET.NET ________ __ ____ Unix Networking Operations - FreeBSD-Real Unix for Free / / / / | / |[__ ] GaiaNet Corporation - M & C Estate / / / / | / | __] ] Beverly Hills, California USA 90210 / / / / / |/ / | __] ] HongKong Stars/Gravis UltraSound Mailing Lists Admin /_/_/_/_/|___/|_|[____] From owner-freebsd-hackers Wed Feb 26 05:34:40 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id FAA07401 for hackers-outgoing; Wed, 26 Feb 1997 05:34:40 -0800 (PST) Received: from zwei.siemens.at (zwei.siemens.at [193.81.246.12]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id FAA07396; Wed, 26 Feb 1997 05:34:33 -0800 (PST) Received: from sol1.gud.siemens.co.at (root@[10.1.143.100]) by zwei.siemens.at (8.7.5/8.7.3) with SMTP id OAA13391; Wed, 26 Feb 1997 14:36:00 +0100 (MET) Received: from ws2301.gud.siemens.co.at by sol1.gud.siemens.co.at with smtp (Smail3.1.28.1 #7 for ) id m0vzjUT-0001zDC; Wed, 26 Feb 97 14:33 MET Received: by ws2301.gud.siemens.co.at (1.37.109.16/1.37) id AA092753791; Wed, 26 Feb 1997 14:29:51 +0100 From: "Hr.Ladavac" Message-Id: <199702261329.AA092753791@ws2301.gud.siemens.co.at> Subject: Re: [H] Optimal computer for FreeBSD To: vince@mail.MCESTATE.COM (Vincent Poy) Date: Wed, 26 Feb 1997 14:29:51 +0100 (MEZ) Cc: lada@ws2301.gud.siemens.co.at, michaelv@MindBender.serv.net, tom@sdf.com, sergey@extech.msk.su, freebsd-isp@freebsd.org, freebsd-hackers@freebsd.org In-Reply-To: from "Vincent Poy" at Feb 26, 97 05:09:53 am X-Mailer: ELM [version 2.4 PL24 ME8a] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk E-mail message from Vincent Poy contained: > On Wed, 26 Feb 1997, Hr.Ladavac wrote: > > > With the slight exception of PPro processors where both L1 and L2 caches > > reside in the same package, albeit on two separate pieces of sillicon... > > But doesn't PPro motherboards still have external cache? Also, is > the PPro actually the P6 chip? if this is the case, what is the code name > for the Klamath 300Mhz processor Intel will be releasing? None that I have seen--agreed, I have only seen ASUS motherboards. AFAIK, no PC motherboard supports L3 cache. Yes, it used to be known as P6, but iNTEL had trademark problems with that name. /Marino > > > Cheers, > Vince - vince@MCESTATE.COM - vince@GAIANET.NET ________ __ ____ > Unix Networking Operations - FreeBSD-Real Unix for Free / / / / | / |[__ ] > GaiaNet Corporation - M & C Estate / / / / | / | __] ] > Beverly Hills, California USA 90210 / / / / / |/ / | __] ] > HongKong Stars/Gravis UltraSound Mailing Lists Admin /_/_/_/_/|___/|_|[____] > > > From owner-freebsd-hackers Wed Feb 26 06:02:56 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id GAA08813 for hackers-outgoing; Wed, 26 Feb 1997 06:02:56 -0800 (PST) Received: from ravenock.cybercity.dk (ravenock.cybercity.dk [194.16.57.32]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id GAA08804 for ; Wed, 26 Feb 1997 06:02:46 -0800 (PST) Received: (from sos@localhost) by ravenock.cybercity.dk (8.8.5/8.7.3) id PAA05079; Wed, 26 Feb 1997 15:02:46 +0100 (MET) From: Søren Schmidt Message-Id: <199702261402.PAA05079@ravenock.cybercity.dk> Subject: Re: what 'dialog' library is used with sysinstall and what not? In-Reply-To: <25882.856953492@time.cdrom.com> from "Jordan K. Hubbard" at "Feb 26, 97 02:38:12 am" To: jkh@time.cdrom.com (Jordan K. Hubbard) Date: Wed, 26 Feb 1997 15:02:36 +0100 (MET) Cc: thomas@ghpc8.ihf.rwth-aachen.de, brandon@cold.org, freebsd-hackers@freebsd.org X-Mailer: ELM [version 2.4ME+ PL30 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In reply to Jordan K. Hubbard who wrote: > > tvision is unusable on with a sane terminal setting like cons25l1 > > (which IMHO should be the default for syscons) or with pcvt or an > > xterm. libdialog is at least terminal independent. > > libdialog is a terminal independent P.O.S. (no explanation of that > acronym should be necessary :) and I've gone as far as I can go with > it - it MUST go. No argument there :) > In any case, the point is moot. I've been waiting for 2 years for a > usable CUI library, it's not appeared, and this library is the first > serious attempt I've ever seen at trying to make the whole CUI > interface usable. The other attempts just took a GUI framework and > attempted to cram it into a CUI imitation, something which generally > results in a truly horrible looking interface. libtvision looks > pretty darn good, considering the limitations it has to work under, > and it's *really really* easy to write code for. I'm sold, I'm > using it in sysinstall II (setup), better get used to the idea. :-) Erhm, what about the somewhat funny license tvision is under ?? I dont like that is has been copythefted, the original seems to be free for the taking (Havn't seen any actual Borland docs though) and now pieces are GPL'd :( :(. If this is resolved I have absolutely no problems with it (hey it could even be used as an API to a GUI for those with "real" videocards, I could be talked into doing some of that, remember) Anybody have a pointer to the genuine Borlan turbo vision 2.0 this is taken from ?? -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Søren Schmidt (sos@FreeBSD.org) FreeBSD Core Team Even more code to hack -- will it ever end .. From owner-freebsd-hackers Wed Feb 26 06:20:21 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id GAA09753 for hackers-outgoing; Wed, 26 Feb 1997 06:20:21 -0800 (PST) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id GAA09748 for ; Wed, 26 Feb 1997 06:20:19 -0800 (PST) Received: from time.cdrom.com (jkh@localhost [127.0.0.1]) by time.cdrom.com (8.8.5/8.6.9) with ESMTP id GAA26697; Wed, 26 Feb 1997 06:18:33 -0800 (PST) To: S ren Schmidt cc: thomas@ghpc8.ihf.rwth-aachen.de, brandon@cold.org, freebsd-hackers@freebsd.org Subject: Re: what 'dialog' library is used with sysinstall and what not? In-reply-to: Your message of "Wed, 26 Feb 1997 15:02:36 +0100." <199702261402.PAA05079@ravenock.cybercity.dk> Date: Wed, 26 Feb 1997 06:18:33 -0800 Message-ID: <26693.856966713@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > Erhm, what about the somewhat funny license tvision is under ?? > I dont like that is has been copythefted, the original seems to > be free for the taking (Havn't seen any actual Borland docs though) > and now pieces are GPL'd :( :(. If this is resolved I have absolutely Yes, I read the same license stuff and I'm not entirely happy that the original Borland stuff isn't easily locatable on the net (unless someone has a pointer stashed away) so we can't even really see the full extent of the changes, perhaps to diff them out and make them into some sort of add-on pack. I'd also be really happy if the author would consider some sort of dual copyright arrangement for his changes, but frankly I haven't lately had the time or energy to go argue it to him so I'm also in no position to judge him over an issue I've yet to even discussed with him. As I said to Mr. Clark, if someone else with more time/energy than I were to take it upon themselves to plead such a case to the author right now, I'd certainly not stand in their way. What's important to me is that I get up to speed on this thing and make some PROGRESS right now and right away. The GPL question is not particularly exciting to me since, at worst, it represents a net-zero movement for me on the GPL usage issue. I throw out one GPL'd library, libdialog, and replace it with a partially-GPL'd library, libtvision. I've actually probably reduced my amount of GNU code when measured by weight, and none would argue that turbovision represents a far better byte-for-buck value than libdialog. :-) Again, that's not to say that I wouldn't welcome some parallel efforts to find a non-GPL alternative to this conversion (or do it over - you probably won't like their GPM-inspired interface when you attempt to make it work with moused anyway :-), just that I have enough on my plate just trying to use the damn thing. My C++ is a little rusty. :) Jordan From owner-freebsd-hackers Wed Feb 26 06:42:28 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id GAA10684 for hackers-outgoing; Wed, 26 Feb 1997 06:42:28 -0800 (PST) Received: from ravenock.cybercity.dk (ravenock.cybercity.dk [194.16.57.32]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id GAA10669 for ; Wed, 26 Feb 1997 06:42:21 -0800 (PST) Received: (from sos@localhost) by ravenock.cybercity.dk (8.8.5/8.7.3) id PAA05200; Wed, 26 Feb 1997 15:42:45 +0100 (MET) From: Søren Schmidt Message-Id: <199702261442.PAA05200@ravenock.cybercity.dk> Subject: Re: what 'dialog' library is used with sysinstall and what not? In-Reply-To: <26693.856966713@time.cdrom.com> from "Jordan K. Hubbard" at "Feb 26, 97 06:18:33 am" To: jkh@time.cdrom.com (Jordan K. Hubbard) Date: Wed, 26 Feb 1997 15:42:35 +0100 (MET) Cc: thomas@ghpc8.ihf.rwth-aachen.de, brandon@cold.org, freebsd-hackers@freebsd.org X-Mailer: ELM [version 2.4ME+ PL30 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In reply to Jordan K. Hubbard who wrote: > > Erhm, what about the somewhat funny license tvision is under ?? > > I dont like that is has been copythefted, the original seems to > > be free for the taking (Havn't seen any actual Borland docs though) > > and now pieces are GPL'd :( :(. If this is resolved I have absolutely > > Yes, I read the same license stuff and I'm not entirely happy that the > original Borland stuff isn't easily locatable on the net (unless > someone has a pointer stashed away) so we can't even really see the > full extent of the changes, perhaps to diff them out and make them > into some sort of add-on pack. I'd also be really happy if the author > would consider some sort of dual copyright arrangement for his > changes, but frankly I haven't lately had the time or energy to go > argue it to him so I'm also in no position to judge him over an issue > I've yet to even discussed with him. As I said to Mr. Clark, if > someone else with more time/energy than I were to take it upon > themselves to plead such a case to the author right now, I'd certainly > not stand in their way. Hmm, I have looked pretty hard for the sources on the net too, and have only come up with the 1.x versions, so.... I'm going to try find out what the deal is, we DONT want to use a lib that Borland afterwards tells us is not for public consumption. > What's important to me is that I get up to speed on this thing and > make some PROGRESS right now and right away. The GPL question is not > particularly exciting to me since, at worst, it represents a net-zero > movement for me on the GPL usage issue. I throw out one GPL'd > library, libdialog, and replace it with a partially-GPL'd library, > libtvision. I've actually probably reduced my amount of GNU code when > measured by weight, and none would argue that turbovision represents a > far better byte-for-buck value than libdialog. :-) yeah yeah :), I'd like us to get rid of ALL GPL code, but you all know that by now.... > Again, that's not to say that I wouldn't welcome some parallel efforts > to find a non-GPL alternative to this conversion (or do it over - you > probably won't like their GPM-inspired interface when you attempt to > make it work with moused anyway :-), just that I have enough on my plate > just trying to use the damn thing. My C++ is a little rusty. :) Hmm, maybe I could learn some C++ too in the process too, I havn't touched that for a loooong time. And if we are going to use it, I'd better get support for our mousestuff in there. I'll go find a virgin turbo vision 2.0 lib and see what they have done (some of it looks like REAL dirty hacks to me). Also I've seen refs to graphical versions of it (only in binary of cause as is the rule in the messydos world, boy do they wear small shoes over there), that could be an idea for my (slowly progressing) native HGA/CGA/VGA GUI.... Have you played with any of the CUI designers thats floating around, or do you use "bare hands" ?? -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Søren Schmidt (sos@FreeBSD.org) FreeBSD Core Team Even more code to hack -- will it ever end .. From owner-freebsd-hackers Wed Feb 26 06:51:02 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id GAA11054 for hackers-outgoing; Wed, 26 Feb 1997 06:51:02 -0800 (PST) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id GAA11049 for ; Wed, 26 Feb 1997 06:50:58 -0800 (PST) Received: from time.cdrom.com (jkh@localhost [127.0.0.1]) by time.cdrom.com (8.8.5/8.6.9) with ESMTP id GAA26874; Wed, 26 Feb 1997 06:49:00 -0800 (PST) To: S ren Schmidt cc: thomas@ghpc8.ihf.rwth-aachen.de, brandon@cold.org, freebsd-hackers@freebsd.org Subject: Re: what 'dialog' library is used with sysinstall and what not? In-reply-to: Your message of "Wed, 26 Feb 1997 15:42:35 +0100." <199702261442.PAA05200@ravenock.cybercity.dk> Date: Wed, 26 Feb 1997 06:48:59 -0800 Message-ID: <26870.856968539@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > Hmm, I have looked pretty hard for the sources on the net too, and > have only come up with the 1.x versions, so.... > I'm going to try find out what the deal is, we DONT want to use a > lib that Borland afterwards tells us is not for public consumption. Well, I read that license of theirs several times, and unless it's purely forged, I dunno. It looks and sounds very much to me like a "this is not strategic, give it away" sort of decision and I can definitely see Borland making it, considering how small the market for DOS CUI development is. > Hmm, maybe I could learn some C++ too in the process too, I havn't touched > that for a loooong time. And if we are going to use it, I'd better get > support for our mousestuff in there. I was hoping you would say that. :-) > I'll go find a virgin turbo vision 2.0 lib and see what they have done > (some of it looks like REAL dirty hacks to me). Well, anyone on this list with a passing assocation with Borland (and there's gotta be *someone*) and a knowledge of the TurboVision situation care to enlighten us? ;-) > Also I've seen refs to graphical versions of it (only in binary of > cause as is the rule in the messydos world, boy do they wear small > shoes over there), that could be an idea for my (slowly progressing) > native HGA/CGA/VGA GUI.... Hmmm! > Have you played with any of the CUI designers thats floating around, or > do you use "bare hands" ?? There aren't all that many CUI designers around anymore, but what few survive I've generally tried to use. This stuff is head and shoulders above anything I've seen to date, which isn't to say that TV is exceptionally great but some of the alternatives *are* exceptionally bad. :-) Jordan From owner-freebsd-hackers Wed Feb 26 07:51:30 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id HAA13949 for hackers-outgoing; Wed, 26 Feb 1997 07:51:30 -0800 (PST) Received: from out2.ibm.net (out2.ibm.net [165.87.201.252]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id HAA13944 for ; Wed, 26 Feb 1997 07:51:27 -0800 (PST) Received: (from uucp@localhost) by out2.ibm.net (8.6.9/8.6.9) id PAA27088 for ; Wed, 26 Feb 1997 15:51:23 GMT Message-Id: <199702261551.PAA27088@out2.ibm.net> Received: from slip166-72-229-98.va.us.ibm.net(166.72.229.98) by out2.ibm.net via smap (V1.3mjr) id smaeasDe7; Wed Feb 26 15:51:17 1997 Reply-To: From: "Steve Sims" To: "Hackers" Subject: Building PAO kernel on non-PAO system Date: Wed, 26 Feb 1997 10:50:30 -0500 X-MSMail-Priority: Normal X-Priority: 3 X-Mailer: Microsoft Internet Mail 4.70.1155 MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Greetings, FreeBSD Dudes & Dudettes.... I've got an old laptop that I'd like to run Our Favorite OS(tm) on, but it **definitely** requires the PAO package to sort out some laptop-esque "features" that Compaq decided to implement. I've got 2.1.6 loaded on the laptop right now (with PAO) and it works pretty well.... (Thanks, Hosokawa-san!) The laptop is only a 486/33, so building a new kernel takes just a few ticks shy of FOREVER on the thing. I'd like to play around with different kernel configs and the like, but I lose interest an hour or so into the make.... My desktop machine is a P5 with gobs of RAM and disk (running [pretty]-current, FWIW) and it occurs to me that one approach might be to build the PAO-enabled 2.1.6 kernel on the desktop and just NFS it back to the laptop (thereby saving tons o' time). Is there an easy way to do this? I notice that PAO mungs a whole lot of different sources as well as some included files, and (complicating the problem, I admit) the P-5 "build" machine is running a newer version of FreeBSD than the laptop anyway. Obviously, (?) I don't want to load PAO on the desktop box, I can't juggle PAO against the -current distribution... Can someone show me the way? `chroot`? A parallel /sys hierarchy? Signed, Confused in Laptop-land ...sjs... From owner-freebsd-hackers Wed Feb 26 08:13:37 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id IAA15341 for hackers-outgoing; Wed, 26 Feb 1997 08:13:37 -0800 (PST) Received: from mx.serv.net (mx.serv.net [199.201.191.10]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id IAA15303; Wed, 26 Feb 1997 08:13:27 -0800 (PST) Received: from MindBender.serv.net by mx.serv.net (8.7.5/SERV Revision: 2.30) id IAA26301; Wed, 26 Feb 1997 08:13:18 -0800 (PST) Received: from localhost.HeadCandy.com (michaelv@localhost.HeadCandy.com [127.0.0.1]) by MindBender.serv.net (8.7.5/8.7.3) with SMTP id IAA03753; Wed, 26 Feb 1997 08:13:13 -0800 (PST) Message-Id: <199702261613.IAA03753@MindBender.serv.net> X-Authentication-Warning: MindBender.serv.net: Host michaelv@localhost.HeadCandy.com [127.0.0.1] didn't use HELO protocol To: Vincent Poy cc: Tom Samplonius , "Vnotchenko S.S." , freebsd-isp@freebsd.org, freebsd-hackers@freebsd.org Subject: Re: [H] Optimal computer for FreeBSD In-reply-to: Your message of Wed, 26 Feb 97 04:14:41 -0800. Date: Wed, 26 Feb 1997 08:13:12 -0800 From: "Michael L. VanLoon -- HeadCandy.com" Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >> > Always use parity RAM on servers, especially if you are buying >> >everything from scratch. >> > EDO doesn't give you much of a improvement if your motherboard supports >> >pipeline-burst-cache. >> My guess is that it doesn't, since the cache is built into the CPU... >> :-) > Actually, from what Rodney Grimes had told me, the cache built >into the CPU is the L1 (Level 1) cache while the L2 cache is the cache on >the motherboard, with Pipeline Burst Caching, it will give like the same Nope, you are completely wrong. Go read the specs for yourself sometime. You can find them at http://www.intel.com/. The Pentium Pro (sometimes known as the P6) has a dual-well carrier design that has both the L1 and the L2 cache in the "chip". I. e., there are two separate pieces of silicon, but they are both in the same package. There is no L3 cache on the motherboard. Note that the Klamath will be different. The L2 cache will not be in the same chip carrier. But it will not be on the "motherboard", either. The Klamath will be delivered in some kind of funky "cartridge" that contains the CPU, cache, and supposedly some other support circuitry. ----------------------------------------------------------------------------- Michael L. VanLoon michaelv@MindBender.serv.net --< Free your mind and your machine -- NetBSD free un*x >-- NetBSD working ports: 386+PC, Mac 68k, Amiga, Atari 68k, HP300, Sun3, Sun4/4c/4m, DEC MIPS, DEC Alpha, PC532, VAX, MVME68k, arm32... NetBSD ports in progress: PICA, others... ----------------------------------------------------------------------------- From owner-freebsd-hackers Wed Feb 26 08:14:34 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id IAA15419 for hackers-outgoing; Wed, 26 Feb 1997 08:14:34 -0800 (PST) Received: from aries.bb.cc.wa.us (root@[208.8.136.11]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id IAA15413 for ; Wed, 26 Feb 1997 08:14:31 -0800 (PST) Received: from localhost (chris@localhost) by aries.bb.cc.wa.us (8.8.3/8.6.9) with SMTP id IAA26798; Wed, 26 Feb 1997 08:11:59 -0800 (PST) Date: Wed, 26 Feb 1997 08:11:59 -0800 (PST) From: Chris Coleman To: Joerg Wunsch cc: hackers@freebsd.org Subject: Re: migrating 2.1.7 -> 2.2: simple or hairy? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Tue, 25 Feb 1997, J Wunsch wrote: > As Chris Coleman wrote: > > > Do you have to do a make install after a make world, or does make world > > install the binaries. > > It implies a `make install' (actually, even more than once). But it > doesn't install anything at all in /etc, except i think the symlinks > for /etc/rmt and /etc/termcap. > > -- > 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. ;-) > What about the kernel, does sup install new kernel files? New GENERIC, or LINT? Does make world install a new GENERIC kernel? Christopher J. Coleman (chris@aries.bb.cc.wa.us) Computer Support Technician I (509)-766-8873 Big Bend Community College Internet Instructor FreeBSD Book Project: http://www.bb.cc.wa.us/~chris/book.html I may Be inaffective, but atleast I am good at it. From owner-freebsd-hackers Wed Feb 26 08:32:24 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id IAA16494 for hackers-outgoing; Wed, 26 Feb 1997 08:32:24 -0800 (PST) Received: from po2.glue.umd.edu (root@po2.glue.umd.edu [129.2.128.45]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id IAA16487 for ; Wed, 26 Feb 1997 08:32:19 -0800 (PST) Received: from timer.eng.umd.edu (timer.eng.umd.edu [129.2.98.109]) by po2.glue.umd.edu (8.8.5/8.8.5) with ESMTP id LAA26977; Wed, 26 Feb 1997 11:32:13 -0500 (EST) Received: from localhost (chuckr@localhost) by timer.eng.umd.edu (8.8.5/8.6.4) with SMTP id LAA10807; Wed, 26 Feb 1997 11:32:10 -0500 X-Authentication-Warning: timer.eng.umd.edu: chuckr owned process doing -bs Date: Wed, 26 Feb 1997 11:31:48 -0500 (EST) From: Chuck Robey X-Sender: chuckr@timer.eng.umd.edu To: Vincent Poy cc: Philippe Regnauld , freebsd-hackers@FreeBSD.ORG Subject: Re: [H] Optimal computer for FreeBSD In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Wed, 26 Feb 1997, Vincent Poy wrote: > On Wed, 26 Feb 1997, Philippe Regnauld wrote: > > > Conclusion: use Parity RAM, but EDO is unnecessary :-) > > Ahhh... The problem is some motherboards don't support the parity > anyways and x32 is cheaper than x36. Does anyone know if EDO RAM will > work on non-EDO machines? Huh? What has the number of bits got to do with the FPM vs. EDO question? They can both come in parity or non-parity, the EDO thing just modifies some of the timing parameters. I think that EDO is cheaper right now than FPM, because of volume questions, anyways, so you get EDO even tho there's no benefit from it, because there's no loss from getting it. ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@eng.umd.edu | communications topic, C programming, and Unix. 9120 Edmonston Ct #302 | Greenbelt, MD 20770 | I run Journey2 and picnic, both FreeBSD (301) 220-2114 | version 3.0 current -- and great FUN! ----------------------------+----------------------------------------------- From owner-freebsd-hackers Wed Feb 26 08:52:51 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id IAA17524 for hackers-outgoing; Wed, 26 Feb 1997 08:52:51 -0800 (PST) Received: from rocky.mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id IAA17505 for ; Wed, 26 Feb 1997 08:52:46 -0800 (PST) Received: (from nate@localhost) by rocky.mt.sri.com (8.7.5/8.7.3) id JAA29381; Wed, 26 Feb 1997 09:52:33 -0700 (MST) Date: Wed, 26 Feb 1997 09:52:33 -0700 (MST) Message-Id: <199702261652.JAA29381@rocky.mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Cc: "Hackers" Subject: Re: Building PAO kernel on non-PAO system In-Reply-To: <199702261551.PAA27088@out2.ibm.net> References: <199702261551.PAA27088@out2.ibm.net> Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > I've got an old laptop that I'd like to run Our Favorite OS(tm) on, but it > **definitely** requires the PAO package to sort out some laptop-esque > "features" that Compaq decided to implement. I've got 2.1.6 loaded on the > laptop right now (with PAO) and it works pretty well.... (Thanks, > Hosokawa-san!) You could install 2.2 on it and it would *probably* work. > My desktop machine is a P5 with gobs of RAM and disk (running > [pretty]-current, FWIW) and it occurs to me that one approach might be to > build the PAO-enabled 2.1.6 kernel on the desktop and just NFS it back to the > laptop (thereby saving tons o' time). One of the reasons the PAO code isn't in the FreeBSD source tree is because it affects 'desktop' functionality. I would caution against applying the PAO patches to the -current box. Have you tried making a kernel with -current and seeing it it works? The PAO patches add support for some new ethernet cards, SCSI cards, and the Wavelan, plus make some things easier but other than that it's pretty much the same functionality as in 2.2 and -current (modulo they actually *document* things better. :( ) Nate From owner-freebsd-hackers Wed Feb 26 09:30:02 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id JAA20463 for hackers-outgoing; Wed, 26 Feb 1997 09:30:02 -0800 (PST) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.50]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id JAA20430; Wed, 26 Feb 1997 09:29:57 -0800 (PST) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id KAA28299; Wed, 26 Feb 1997 10:20:00 -0700 From: Terry Lambert Message-Id: <199702261720.KAA28299@phaeton.artisoft.com> Subject: Re: [H] Optimal computer for FreeBSD To: lada@ws2301.gud.siemens.co.at (Hr.Ladavac) Date: Wed, 26 Feb 1997 10:20:00 -0700 (MST) Cc: vince@mail.MCESTATE.COM, michaelv@MindBender.serv.net, tom@sdf.com, sergey@extech.msk.su, freebsd-isp@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG In-Reply-To: <199702261301.AA083142096@ws2301.gud.siemens.co.at> from "Hr.Ladavac" at Feb 26, 97 02: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-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > With the slight exception of PPro processors where both L1 and L2 caches > reside in the same package, albeit on two separate pieces of sillicon... What a neat idea. Then if you want a larger L2, I can make you buy a whole new processor. 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-hackers Wed Feb 26 09:31:17 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id JAA20631 for hackers-outgoing; Wed, 26 Feb 1997 09:31:17 -0800 (PST) Received: from zwei.siemens.at (zwei.siemens.at [193.81.246.12]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id JAA20597; Wed, 26 Feb 1997 09:31:05 -0800 (PST) Received: from sol1.gud.siemens.co.at (root@[10.1.143.100]) by zwei.siemens.at (8.7.5/8.7.3) with SMTP id SAA19954; Wed, 26 Feb 1997 18:32:39 +0100 (MET) Received: from ws2301.gud.siemens.co.at by sol1.gud.siemens.co.at with smtp (Smail3.1.28.1 #7 for ) id m0vznBU-0001zDC; Wed, 26 Feb 97 18:30 MET Received: by ws2301.gud.siemens.co.at (1.37.109.16/1.37) id AA177037988; Wed, 26 Feb 1997 18:26:28 +0100 From: "Hr.Ladavac" Message-Id: <199702261726.AA177037988@ws2301.gud.siemens.co.at> Subject: Re: [H] Optimal computer for FreeBSD To: terry@lambert.org (Terry Lambert) Date: Wed, 26 Feb 1997 18:26:28 +0100 (MEZ) Cc: lada@ws2301.gud.siemens.co.at, vince@mail.MCESTATE.COM, michaelv@MindBender.serv.net, tom@sdf.com, sergey@extech.msk.su, freebsd-isp@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG In-Reply-To: <199702261720.KAA28299@phaeton.artisoft.com> from "Terry Lambert" at Feb 26, 97 10:20:00 am X-Mailer: ELM [version 2.4 PL24 ME8a] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk E-mail message from Terry Lambert contained: > > With the slight exception of PPro processors where both L1 and L2 caches > > reside in the same package, albeit on two separate pieces of sillicon... > > What a neat idea. Then if you want a larger L2, I can make you > buy a whole new processor. And charge you double: after all, you're getting twice as many transistors in the cache... /Marino > > 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-hackers Wed Feb 26 09:35:21 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id JAA21031 for hackers-outgoing; Wed, 26 Feb 1997 09:35:21 -0800 (PST) Received: from zwei.siemens.at (zwei.siemens.at [193.81.246.12]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id JAA21004; Wed, 26 Feb 1997 09:35:08 -0800 (PST) Received: from sol1.gud.siemens.co.at (root@[10.1.143.100]) by zwei.siemens.at (8.7.5/8.7.3) with SMTP id SAA20059; Wed, 26 Feb 1997 18:36:41 +0100 (MET) Received: from ws2301.gud.siemens.co.at by sol1.gud.siemens.co.at with smtp (Smail3.1.28.1 #7 for ) id m0vznFP-0001zDC; Wed, 26 Feb 97 18:34 MET Received: by ws2301.gud.siemens.co.at (1.37.109.16/1.37) id AA177658232; Wed, 26 Feb 1997 18:30:32 +0100 From: "Hr.Ladavac" Message-Id: <199702261730.AA177658232@ws2301.gud.siemens.co.at> Subject: Re: [H] Optimal computer for FreeBSD To: lada@ws2313.gud.siemens.co.at (Hr.Ladavac) Date: Wed, 26 Feb 1997 18:30:32 +0100 (MEZ) Cc: terry@lambert.org, lada@ws2301.gud.siemens.co.at, vince@mail.MCESTATE.COM, michaelv@MindBender.serv.net, tom@sdf.com, sergey@extech.msk.su, freebsd-isp@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG In-Reply-To: <199702261726.AA177037988@ws2301.gud.siemens.co.at> from "Hr.Ladavac" at Feb 26, 97 06:26:28 pm X-Mailer: ELM [version 2.4 PL24 ME8a] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk E-mail message from Hr.Ladavac contained: > E-mail message from Terry Lambert contained: > > > With the slight exception of PPro processors where both L1 and L2 caches > > > reside in the same package, albeit on two separate pieces of sillicon... > > > > What a neat idea. Then if you want a larger L2, I can make you > > buy a whole new processor. > > And charge you double: after all, you're getting twice as many > transistors in the cache... My brain fart: you should consider it a bargain, since you're getting at least *four* time as many transistors (the cache is static, idiot :) /Marino > > /Marino > > > > 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-hackers Wed Feb 26 09:48:52 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id JAA21614 for hackers-outgoing; Wed, 26 Feb 1997 09:48:52 -0800 (PST) Received: from mailhub.aros.net (mailhub.aros.net [207.173.16.17]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id JAA21602 for ; Wed, 26 Feb 1997 09:48:43 -0800 (PST) Received: from fluffy.aros.net (fluffy.aros.net [207.173.16.2]) by mailhub.aros.net (8.8.5/Unknown) with ESMTP id KAA14726; Wed, 26 Feb 1997 10:48:39 -0700 (MST) Received: from fluffy.aros.net (localhost [127.0.0.1]) by fluffy.aros.net (8.8.5/8.6.12) with ESMTP id KAA26747; Wed, 26 Feb 1997 10:48:36 -0700 (MST) Message-Id: <199702261748.KAA26747@fluffy.aros.net> To: "Matthew A. Gessner" cc: hackers Subject: Re: Writing a daemon... In-reply-to: Your message of "Tue, 25 Feb 1997 13:33:34 EST." <3313307E.41C67EA6@aristar.com> Date: Wed, 26 Feb 1997 10:48:36 -0700 From: Dave Andersen Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > Hello, hackers, > > I'm looking for some really good information on writing a daemon for a) > FreeBSD and b) DEC ALPHA OSF/1. I've got Stevens' Couldn't help on the second, sorry. :) > some problems getting the code to compile properly under FreeBSD. I > just want to make sure that nothing's really 'changed' in the 'art' of > daemon writing since his book was published. The only thing that would be different are some header files. Stevens' books are nicely BSD-centric. > If anyone can add any tips or recommendations (specifically, if anyone > has a good source for OSF), please let me know. Yes - don't use the Network programming book as a daemon book. Get _Advanced_Programming_In_the_UNIX_Environment (W. Richard Stevens). It's got a nice little section on daemons and other critters. Or, for some real life examples, look in the source tree. :) -Dave From owner-freebsd-hackers Wed Feb 26 10:29:35 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id KAA23743 for hackers-outgoing; Wed, 26 Feb 1997 10:29:35 -0800 (PST) Received: from sovcom.kiae.su (sovcom.kiae.su [193.125.152.1]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id KAA23729; Wed, 26 Feb 1997 10:29:26 -0800 (PST) Received: by sovcom.kiae.su id AA19728 (5.65.kiae-1 ); Wed, 26 Feb 1997 20:58:58 +0300 Received: by sovcom.KIAE.su (UUMAIL/2.0); Wed, 26 Feb 97 20:58:58 +0300 Received: (from ache@localhost) by nagual.ru (8.8.5/8.8.5) id VAA00537; Wed, 26 Feb 1997 21:13:54 +0300 (MSK) Date: Wed, 26 Feb 1997 21:13:48 +0300 (MSK) From: =?KOI8-R?B?4c7E0sXKIP7F0s7P1w==?= To: "Eric J. Schwertfeger" Cc: "Vnotchenko S.S." , freebsd-isp@freebsd.org, freebsd-hackers@freebsd.org Subject: Re: [H] Optimal computer for FreeBSD In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Tue, 25 Feb 1997, Eric J. Schwertfeger wrote: > Video depends on what you want to use the computer for. If it's an X > workstation, look for one of the good accellerated chipsets. Stay away > from the S3 Virge chipset if you want to use truecolor (for java, etc), > because the XFree Virge drivers are still under development. If this is > only going to be a server sitting at the console most of the time, Just > about anything will work well. Could you provide more details please, what wrong with Virge/VX driver now? What Xfree86 version you mean? -- Andrey A. Chernov http://www.nagual.ru/~ache/ From owner-freebsd-hackers Wed Feb 26 10:33:11 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id KAA24044 for hackers-outgoing; Wed, 26 Feb 1997 10:33:11 -0800 (PST) Received: from plains.nodak.edu (tinguely@plains.NoDak.edu [134.129.111.64]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id KAA24030 for ; Wed, 26 Feb 1997 10:32:54 -0800 (PST) Received: (from tinguely@localhost) by plains.nodak.edu (8.8.4/8.8.3) id MAA13652; Wed, 26 Feb 1997 12:32:33 -0600 (CST) Date: Wed, 26 Feb 1997 12:32:33 -0600 (CST) From: Mark Tinguely Message-Id: <199702261832.MAA13652@plains.nodak.edu> To: chuckr@glue.umd.edu, vince@mail.MCESTATE.COM Subject: Re: [H] Optimal computer for FreeBSD Cc: freebsd-hackers@freebsd.org, regnauld@deepo.prosa.dk Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > I think that EDO is cheaper right now than FPM, because of volume > questions, anyways, so you get EDO even tho there's no benefit from it, > because there's no loss from getting it. parity EDO is more expensive than parity FPM (40-50% more expensive at Megatrends Technology). For those that believe parity is important and is worth the money (and most in this group would be in that camp). As I read this thread of conversation, the debate is if parity EDO is worth the expense considering performance differences. --mark. From owner-freebsd-hackers Wed Feb 26 10:47:57 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id KAA25038 for hackers-outgoing; Wed, 26 Feb 1997 10:47:57 -0800 (PST) Received: from usr06.primenet.com (root@usr06.primenet.com [206.165.5.106]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id KAA25033; Wed, 26 Feb 1997 10:47:52 -0800 (PST) Received: from primenet.com (root@mailhost01.primenet.com [206.165.5.52]) by usr06.primenet.com (8.8.5/8.8.5) with ESMTP id LAA16869; Wed, 26 Feb 1997 11:45:26 -0700 (MST) Received: from conceptual.com (consys.com [207.218.17.187]) by primenet.com (8.8.5/8.8.5) with ESMTP id LAA03159; Wed, 26 Feb 1997 11:45:19 -0700 (MST) Received: from conceptual.com (localhost [127.0.0.1]) by conceptual.com (8.8.5/8.6.9) with ESMTP id LAA02550; Wed, 26 Feb 1997 11:45:07 -0700 (MST) Message-Id: <199702261845.LAA02550@conceptual.com> X-Mailer: exmh version 2.0gamma 1/27/96 To: "Michael L. VanLoon -- HeadCandy.com" cc: Vincent Poy , Tom Samplonius , "Vnotchenko S.S." , freebsd-isp@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG Subject: Re: [H] Optimal computer for FreeBSD In-reply-to: Your message of "Wed, 26 Feb 1997 08:13:12 PST." <199702261613.IAA03753@MindBender.serv.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 26 Feb 1997 11:45:07 -0700 From: "Russell L. Carter" Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > >> > Always use parity RAM on servers, especially if you are buying > >> >everything from scratch. > >> > EDO doesn't give you much of a improvement if your motherboard supports > >> >pipeline-burst-cache. > > >> My guess is that it doesn't, since the cache is built into the CPU... > >> :-) > > > Actually, from what Rodney Grimes had told me, the cache built > >into the CPU is the L1 (Level 1) cache while the L2 cache is the cache on > >the motherboard, with Pipeline Burst Caching, it will give like the same > > Nope, you are completely wrong. Go read the specs for yourself > sometime. You can find them at http://www.intel.com/. Look guys, the only chip that has PB-SRAM is P5, and for *that* chip the original comment is correct. And Rodney is correct. And Michael is correct, for P6. Sheesh! Anyway, I don't think EDO gives you much for P6 either, and all the ASUS motherboards I've seen in the last 6 months for P5 and P6 support ECC if you have parity RAM, which is a big win for a server if it works. Later, Russell From owner-freebsd-hackers Wed Feb 26 10:50:07 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id KAA25350 for hackers-outgoing; Wed, 26 Feb 1997 10:50:07 -0800 (PST) Received: from horst.bfd.com (horst.bfd.com [204.160.242.10]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id KAA25317; Wed, 26 Feb 1997 10:49:53 -0800 (PST) Received: from harlie.bfd.com (bastion.bfd.com [204.160.242.14]) by horst.bfd.com (8.8.5/8.7.3) with SMTP id KAA02500; Wed, 26 Feb 1997 10:49:19 -0800 (PST) Date: Wed, 26 Feb 1997 10:49:19 -0800 (PST) From: "Eric J. Schwertfeger" To: =?KOI8-R?B?4c7E0sXKIP7F0s7P1w==?= cc: "Vnotchenko S.S." , freebsd-isp@freebsd.org, freebsd-hackers@freebsd.org Subject: Re: [H] Optimal computer for FreeBSD In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from QUOTED-PRINTABLE to 8bit by freefall.freebsd.org id KAA25342 Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Wed, 26 Feb 1997, [KOI8-R] áÎÄÒÅÊ þÅÒÎÏ× wrote: > On Tue, 25 Feb 1997, Eric J. Schwertfeger wrote: > > > Video depends on what you want to use the computer for. If it's an X > > workstation, look for one of the good accellerated chipsets. Stay away > > from the S3 Virge chipset if you want to use truecolor (for java, etc), > > because the XFree Virge drivers are still under development. If this is > > only going to be a server sitting at the console most of the time, Just > > about anything will work well. > > Could you provide more details please, what wrong with Virge/VX driver > now? What Xfree86 version you mean? The latest alpha driver (XF32A) available to non-betatesters from XFree. XF32 won't do truecolor with either Virge chipset, and has a few quirks that I haven't noticed, and only know about because they're mentioned in the XF32A release notes. Also, it sounds like the Virge driver works better with the Virge than with the Virge/VX.. XF32A will do packed (24 bit) truecolor on the Virge, but not the Virge/VX, and some problems are reported with certain applications. I haven't installed XF32A yet, though I want to to get truecolor (for Java development), but supposedly Netscape has problems with the truecolor mode of the Virge driver in XF32A. Most of this info is all available in the readmes and other documentation on www.xfree86.org, Though I don't know if the XF32A readmes are available on their web server. From owner-freebsd-hackers Wed Feb 26 11:02:37 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id LAA26060 for hackers-outgoing; Wed, 26 Feb 1997 11:02:37 -0800 (PST) Received: from rocky.mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id LAA26055 for ; Wed, 26 Feb 1997 11:02:34 -0800 (PST) Received: (from nate@localhost) by rocky.mt.sri.com (8.7.5/8.7.3) id LAA29967; Wed, 26 Feb 1997 11:58:48 -0700 (MST) Date: Wed, 26 Feb 1997 11:58:48 -0700 (MST) Message-Id: <199702261858.LAA29967@rocky.mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Terry Lambert Cc: lada@ws2301.gud.siemens.co.at (Hr.Ladavac), freebsd-hackers@freebsd.org Subject: Re: [H] Optimal computer for FreeBSD In-Reply-To: <199702261720.KAA28299@phaeton.artisoft.com> References: <199702261301.AA083142096@ws2301.gud.siemens.co.at> <199702261720.KAA28299@phaeton.artisoft.com> Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk [ Reduced the CC list ] > > With the slight exception of PPro processors where both L1 and L2 caches > > reside in the same package, albeit on two separate pieces of sillicon... > > What a neat idea. Then if you want a larger L2, I can make you > buy a whole new processor. Playing Devil's advocate, how many times in recent years (since the 486 at least) have you upgraded your cache and not touched the processor. It doesn't happen. Nate From owner-freebsd-hackers Wed Feb 26 11:19:33 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id LAA26761 for hackers-outgoing; Wed, 26 Feb 1997 11:19:33 -0800 (PST) Received: from who.cdrom.com (who.cdrom.com [204.216.27.3]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id LAA26756 for ; Wed, 26 Feb 1997 11:19:31 -0800 (PST) Received: from hauki.clinet.fi (hauki.clinet.fi [194.100.0.1]) by who.cdrom.com (8.7.5/8.6.11) with ESMTP id LAA14754 for ; Wed, 26 Feb 1997 11:19:26 -0800 (PST) Received: from news.clinet.fi (root@news.clinet.fi [194.100.0.3]) by hauki.clinet.fi (8.8.5/8.6.4) with ESMTP id VAA21268; Wed, 26 Feb 1997 21:13:39 +0200 (EET) Received: (hsu@localhost) by news.clinet.fi (8.8.5/8.6.4) id VAA08941; Wed, 26 Feb 1997 21:13:54 +0200 (EET) Date: Wed, 26 Feb 1997 21:13:54 +0200 (EET) Message-Id: <199702261913.VAA08941@news.clinet.fi> From: Heikki Suonsivu To: Thomas David Rivers Cc: freebsd-hackers@freebsd.org In-reply-to: Thomas David Rivers's message of 26 Feb 1997 06:14:28 +0200 Subject: Re: A wild idea on the "dup alloc" and "bad dir" panics... Organization: Clinet Ltd, Espoo, Finland References: <199702260314.WAA19559@lakes.water.net> Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk From: Thomas David Rivers This is just a wild thought I had... We've eliminated different processors, different disk drives, different memory configurations, etc... in an attempt to determine what's common about the machines experiencing these problems. The item that's common for my two machines experiencing the problem that we haven't investigated is: Hercules Monochrome Monitor I know it's *really* reaching here, but can everyone who's involved let me know what kind of monitor they've got connected... Maybe there's something in that device driver that's trashing some random memory, or this happens during a scroll, or something like that... [It is a far stretch, admitedly, but it would explain why this only occurs on a small subset of machines...] Anyway, just a thought... We have mostly vga cards (most of them ISA, but I think this also happens in PCI display adapter systems). I do not think any of the offending machines has a hercules mono card. - Dave Rivers - -- Heikki Suonsivu, T{ysikuu 10 C 83/02210 Espoo/FINLAND, hsu@clinet.fi mobile +358-40-5519679 work +358-9-43542270 fax -4555276 From owner-freebsd-hackers Wed Feb 26 11:36:20 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id LAA27894 for hackers-outgoing; Wed, 26 Feb 1997 11:36:20 -0800 (PST) Received: from odin.visigenic.com (odin.visigenic.com [204.179.98.2]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id LAA27889 for ; Wed, 26 Feb 1997 11:36:17 -0800 (PST) Received: from VSI48 (vsi48.visigenic.com [206.64.15.185]) by odin.visigenic.com (Netscape Mail Server v2.02) with SMTP id AAA26986 for ; Wed, 26 Feb 1997 11:33:20 -0800 Message-Id: <3.0.32.19970226113632.008f4eb0@visigenic.com> X-Sender: toneil@visigenic.com X-Mailer: Windows Eudora Pro Version 3.0 (32) Date: Wed, 26 Feb 1997 11:36:32 -0800 To: hackers@freebsd.org From: "Tim Oneil" Subject: Re: [H] Optimal computer for FreeBSD Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk At 12:32 PM 2/26/97 -0600, you wrote: >> I think that EDO is cheaper right now than FPM, because of volume >> questions, anyways, so you get EDO even tho there's no benefit from it, >> because there's no loss from getting it. > >parity EDO is more expensive than parity FPM (40-50% more expensive at >Megatrends Technology). For those that believe parity is important and >is worth the money (and most in this group would be in that camp). >As I read this thread of conversation, the debate is if parity EDO >is worth the expense considering performance differences. If anyone cares, I've put together three machines this year alone, and never used parity chips. No problems. From owner-freebsd-hackers Wed Feb 26 11:50:54 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id LAA28654 for hackers-outgoing; Wed, 26 Feb 1997 11:50:54 -0800 (PST) Received: from phoenix.its.rpi.edu (dec@phoenix.its.rpi.edu [128.113.161.45]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id LAA28648 for ; Wed, 26 Feb 1997 11:50:51 -0800 (PST) Received: (from dec@localhost) by phoenix.its.rpi.edu (8.8.3/8.8.3) id OAA00417 for freebsd-hackers@freebsd.org; Wed, 26 Feb 1997 14:50:14 -0500 (EST) Date: Wed, 26 Feb 1997 14:50:14 -0500 (EST) From: "David E. Cross" Message-Id: <199702261950.OAA00417@phoenix.its.rpi.edu> To: freebsd-hackers@freebsd.org Subject: crtbsd Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Could someone point me to the crt0 exploit program, I think I have patched my system against it, and just want to give it a shakedown. -- David Cross ACS Consultant From owner-freebsd-hackers Wed Feb 26 11:53:56 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id LAA28875 for hackers-outgoing; Wed, 26 Feb 1997 11:53:56 -0800 (PST) Received: from out1.ibm.net (out1.ibm.net [165.87.194.252]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id LAA28861 for ; Wed, 26 Feb 1997 11:53:51 -0800 (PST) Received: (from uucp@localhost) by out1.ibm.net (8.6.9/8.6.9) id TAA172572; Wed, 26 Feb 1997 19:53:26 GMT Message-Id: <199702261953.TAA172572@out1.ibm.net> Received: from slip166-72-229-183.va.us.ibm.net(166.72.229.183) by out1.ibm.net via smap (V1.3mjr) id sma8gQDmb; Wed Feb 26 19:53:16 1997 Reply-To: From: "Steve Sims" To: "Nate Williams" Cc: "Hackers" Subject: Re: Building PAO kernel on non-PAO system Date: Wed, 26 Feb 1997 14:52:11 -0500 X-MSMail-Priority: Normal X-Priority: 3 X-Mailer: Microsoft Internet Mail 4.70.1155 MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Nate Williams says: | | > I've got an old laptop that I'd like to run Our Favorite OS(tm) on, but it | > **definitely** requires the PAO package to sort out some laptop-esque | > "features" that Compaq decided to implement. I've got 2.1.6 loaded on the | > laptop right now (with PAO) and it works pretty well.... (Thanks, | > Hosokawa-san!) | | You could install 2.2 on it and it would *probably* work. Well, it didn't work the *last* time I tried. (About 3 months ago; Same-old Same-old with the silly sio probes failing was the biggest headache.) | One of the reasons the PAO code isn't in the FreeBSD source tree is | because it affects 'desktop' functionality. I would caution against | applying the PAO patches to the -current box. Yeah, this would be a bad idea, one of last resort. | Have you tried making a kernel with -current and seeing it it works? | The PAO patches add support for some new ethernet cards, SCSI cards, and | the Wavelan, plus make some things easier but other than that it's | pretty much the same functionality as in 2.2 and -current (modulo they | actually *document* things better. :( ) I'll try my luck with a plain vanilla 2.2-GAMMA and see what happens. (I'm not optimistic, but I may be surprised.) What does surprise me is that there isn't a *obvious* way to build kernels or, for that matter, hardware- and kernel-structure-specific apps for various architectures, versions and configurations on a single machine and distribute them to one or more "client" machines. I've run shops where this would have been a REQUIREMENT (e.g.: a farm of diskless workstations in a variety of interfaces, processors, etc...) ...sjs... From owner-freebsd-hackers Wed Feb 26 11:58:05 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id LAA29226 for hackers-outgoing; Wed, 26 Feb 1997 11:58:05 -0800 (PST) Received: from rocky.mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id LAA29221 for ; Wed, 26 Feb 1997 11:58:02 -0800 (PST) Received: (from nate@localhost) by rocky.mt.sri.com (8.7.5/8.7.3) id MAA00183; Wed, 26 Feb 1997 12:57:45 -0700 (MST) Date: Wed, 26 Feb 1997 12:57:45 -0700 (MST) Message-Id: <199702261957.MAA00183@rocky.mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Cc: "Nate Williams" , "Hackers" Subject: Re: Building PAO kernel on non-PAO system In-Reply-To: <199702261953.TAA172572@out1.ibm.net> References: <199702261953.TAA172572@out1.ibm.net> Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > | > I've got an old laptop that I'd like to run Our Favorite OS(tm) on, but > it > | > **definitely** requires the PAO package to sort out some laptop-esque > | > "features" that Compaq decided to implement. I've got 2.1.6 loaded on > the > | > laptop right now (with PAO) and it works pretty well.... (Thanks, > | > Hosokawa-san!) > | > | You could install 2.2 on it and it would *probably* work. > > Well, it didn't work the *last* time I tried. (About 3 months ago; Same-old > Same-old with the silly sio probes failing was the biggest headache.) Hmm, the sio patches in PAO have changed a ton lately. I don't think the ones in PAO are *that* much different, although with PAO it adds the ability to use the serial ports w/out knowing the specifics of the card itself. But, if you do *know* the specifics the 2.2 code should work. > What does surprise me is that there isn't a *obvious* way to build kernels > or, for that matter, hardware- and kernel-structure-specific apps for various > architectures, versions and configurations on a single machine and distribute > them to one or more "client" machines. I've run shops where this would have > been a REQUIREMENT (e.g.: a farm of diskless workstations in a variety of > interfaces, processors, etc...) What do you mean? Copy the config to a new name, edit it, build the kernel and you're donne. What more do you want? Nate From owner-freebsd-hackers Wed Feb 26 12:08:55 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id MAA29986 for hackers-outgoing; Wed, 26 Feb 1997 12:08:55 -0800 (PST) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.50]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id MAA29979 for ; Wed, 26 Feb 1997 12:08:52 -0800 (PST) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id NAA28589; Wed, 26 Feb 1997 13:06:10 -0700 From: Terry Lambert Message-Id: <199702262006.NAA28589@phaeton.artisoft.com> Subject: Re: [H] Optimal computer for FreeBSD To: toneil@visigenic.com (Tim Oneil) Date: Wed, 26 Feb 1997 13:06:10 -0700 (MST) Cc: hackers@freebsd.org In-Reply-To: <3.0.32.19970226113632.008f4eb0@visigenic.com> from "Tim Oneil" at Feb 26, 97 11:36:32 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-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > If anyone cares, I've put together three machines this year alone, and > never used parity chips. No problems. That you could detect, that resulted in a "parity error". 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-hackers Wed Feb 26 12:09:21 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id MAA00136 for hackers-outgoing; Wed, 26 Feb 1997 12:09:21 -0800 (PST) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.50]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id MAA00126 for ; Wed, 26 Feb 1997 12:09:12 -0800 (PST) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id NAA28578; Wed, 26 Feb 1997 13:05:17 -0700 From: Terry Lambert Message-Id: <199702262005.NAA28578@phaeton.artisoft.com> Subject: Re: [H] Optimal computer for FreeBSD To: nate@mt.sri.com (Nate Williams) Date: Wed, 26 Feb 1997 13:05:17 -0700 (MST) Cc: terry@lambert.org, lada@ws2301.gud.siemens.co.at, freebsd-hackers@freebsd.org In-Reply-To: <199702261858.LAA29967@rocky.mt.sri.com> from "Nate Williams" at Feb 26, 97 11:58:48 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-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > > With the slight exception of PPro processors where both L1 and L2 caches > > > reside in the same package, albeit on two separate pieces of sillicon... > > > > What a neat idea. Then if you want a larger L2, I can make you > > buy a whole new processor. > > Playing Devil's advocate, how many times in recent years (since the 486 > at least) have you upgraded your cache and not touched the processor. > > It doesn't happen. When I went from 16M of ram to 32M of RAM on my 486/50, I had to increase the cache as well. I guess the answer is "once" and depends highly on your definition of "recent" going back at least 3 years... 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-hackers Wed Feb 26 12:33:03 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id MAA01314 for hackers-outgoing; Wed, 26 Feb 1997 12:33:03 -0800 (PST) Received: from out1.ibm.net (out1.ibm.net [165.87.194.252]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id MAA01281 for ; Wed, 26 Feb 1997 12:32:37 -0800 (PST) Received: (from uucp@localhost) by out1.ibm.net (8.6.9/8.6.9) id UAA71641; Wed, 26 Feb 1997 20:32:28 GMT Message-Id: <199702262032.UAA71641@out1.ibm.net> Received: from slip166-72-229-228.va.us.ibm.net(166.72.229.228) by out1.ibm.net via smap (V1.3mjr) id smaprACrx; Wed Feb 26 20:32:11 1997 Reply-To: From: "Steve Sims" To: "Nate Williams" Cc: "Hackers" Subject: Re: Building PAO kernel on non-PAO system Date: Wed, 26 Feb 1997 15:32:03 -0500 X-MSMail-Priority: Normal X-Priority: 3 X-Mailer: Microsoft Internet Mail 4.70.1155 MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Nate Williams says: | > What does surprise me is that there isn't a *obvious* way to build kernels | > or, for that matter, hardware- and kernel-structure-specific apps for various | > architectures, versions and configurations on a single machine and distribute | > them to one or more "client" machines. I've run shops where this would have | > been a REQUIREMENT (e.g.: a farm of diskless workstations in a variety of | > interfaces, processors, etc...) | | What do you mean? Copy the config to a new name, edit it, build the | kernel and you're donne. What more do you want? I think you missed my point - It's not possible (or I'm not smart enough to know how) to build, say, 2.1.7, 2.2 *AND* -current kernels on a single "super server" and then blow them out amongst the unsuspecting users depending on their needs (and possibly their threshold for pain). Can such a thing be done? Obviously, I can build different *configurations* of a single release version, but I can't (easily) have different versions of the OS all build from the same source tree. This is the point I'm trying to make in my own inept fashion - I can't build a PAO-enabled kernel to distribute to another machine on a (non-PAO configured) desktop that's running a different rev of FreeBSD source. Or can I? ...sjs... From owner-freebsd-hackers Wed Feb 26 12:41:28 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id MAA01747 for hackers-outgoing; Wed, 26 Feb 1997 12:41:28 -0800 (PST) Received: from rocky.mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id MAA01739 for ; Wed, 26 Feb 1997 12:41:25 -0800 (PST) Received: (from nate@localhost) by rocky.mt.sri.com (8.7.5/8.7.3) id NAA00507; Wed, 26 Feb 1997 13:41:21 -0700 (MST) Date: Wed, 26 Feb 1997 13:41:21 -0700 (MST) Message-Id: <199702262041.NAA00507@rocky.mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Cc: "Nate Williams" , "Hackers" Subject: Re: Building PAO kernel on non-PAO system In-Reply-To: <199702262032.UAA71641@out1.ibm.net> References: <199702262032.UAA71641@out1.ibm.net> Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > I think you missed my point Yep, I did. :) >- It's not possible (or I'm not smart enough to > know how) to build, say, 2.1.7, 2.2 *AND* -current kernels on a single "super > server" and then blow them out amongst the unsuspecting users depending on > their needs (and possibly their threshold for pain). Can such a thing be > done? Sure, but it really goes against the grain. Why can't these unsuspecting users all use the GENERIC kernel and be happy with it? It supports everything they need, and there's no need for the super-server. That's supposedly the purpose of the GENERIC kernel. > This is the point I'm trying to make in my own inept fashion - I can't build > a PAO-enabled kernel to distribute to another machine on a (non-PAO > configured) desktop that's running a different rev of FreeBSD source. Or can > I? One could argue that you shouldn't be placing PAO-kernels on unsuspecting users. You should only run *release* code on machines except where people are aware of the problems, and then they should build their own systems so they can 'fix' bugs that arise. (This isn't a solution, but an explanation of the thinking.) In any case, you can build kernels for any release like you can with *any* software project. You just need to setup the environment that each release requires. Man 'chroot' for some hints. Nate From owner-freebsd-hackers Wed Feb 26 12:55:27 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id MAA02546 for hackers-outgoing; Wed, 26 Feb 1997 12:55:27 -0800 (PST) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.50]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id MAA02537 for ; Wed, 26 Feb 1997 12:55:21 -0800 (PST) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id NAA28695; Wed, 26 Feb 1997 13:52:07 -0700 From: Terry Lambert Message-Id: <199702262052.NAA28695@phaeton.artisoft.com> Subject: Re: Building PAO kernel on non-PAO system To: nate@mt.sri.com (Nate Williams) Date: Wed, 26 Feb 1997 13:52:07 -0700 (MST) Cc: SimsS@IBM.Net, nate@mt.sri.com, Hackers@freebsd.org In-Reply-To: <199702261957.MAA00183@rocky.mt.sri.com> from "Nate Williams" at Feb 26, 97 12:57:45 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-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > What does surprise me is that there isn't a *obvious* way to > > build kernels or, for that matter, hardware- and kernel- > > structure-specific apps for various architectures, versions > > and configurations on a single machine and distribute them > > to one or more "client" machines. I've run shops where > > this would have been a REQUIREMENT (e.g.: a farm of diskless > > workstations in a variety of interfaces, processors, etc...) > > What do you mean? Copy the config to a new name, edit it, build the > kernel and you're donne. What more do you want? Building the right ifconfig, the right ps, the right w, the right netstat, the right vmstat, the right config itself, the right install, the right login, etc.. 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-hackers Wed Feb 26 13:00:18 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id NAA02930 for hackers-outgoing; Wed, 26 Feb 1997 13:00:18 -0800 (PST) Received: from odin.visigenic.com (odin.visigenic.com [204.179.98.2]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id NAA02924 for ; Wed, 26 Feb 1997 13:00:15 -0800 (PST) Received: from VSI48 (vsi48.visigenic.com [206.64.15.185]) by odin.visigenic.com (Netscape Mail Server v2.02) with SMTP id AAA3422 for ; Wed, 26 Feb 1997 12:57:19 -0800 Message-Id: <3.0.32.19970226130030.009087b0@visigenic.com> X-Sender: toneil@visigenic.com X-Mailer: Windows Eudora Pro Version 3.0 (32) Date: Wed, 26 Feb 1997 13:00:30 -0800 To: hackers@FreeBSD.ORG From: "Tim Oneil" Subject: Re: [H] Optimal computer for FreeBSD Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >Date: Wed, 26 Feb 1997 12:57:29 -0800 >To: Terry Lambert >From: Tim O'Neil >Subject: Re: [H] Optimal computer for FreeBSD > >At 01:06 PM 2/26/97 -0700, you wrote: >>> If anyone cares, I've put together three machines this year alone, and >>> never used parity chips. No problems. >> >>That you could detect, that resulted in a "parity error". 8-). > >True enough! Absolutely. However, these machines are still going >strong after some use, no problems. ===================================================== Tim O'Neil toneil@visigenic.com Technical Support Engineer support@visigenic.com Visigenic Software, Inc. http://www.visigenic.com ===================================================== From owner-freebsd-hackers Wed Feb 26 13:07:11 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id NAA03325 for hackers-outgoing; Wed, 26 Feb 1997 13:07:11 -0800 (PST) Received: from alpha.xerox.com (alpha.Xerox.COM [13.1.64.93]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id NAA03317 for ; Wed, 26 Feb 1997 13:07:04 -0800 (PST) Received: from www.sdsp.mc.xerox.com ([13.231.132.18]) by alpha.xerox.com with SMTP id <16344(6)>; Wed, 26 Feb 1997 13:06:21 PST Received: from gnu.sdsp.mc.xerox.com (gnu.sdsp.mc.xerox.com [13.231.133.90]) by www.sdsp.mc.xerox.com (8.8.5/8.8.5) with SMTP id QAA05872; Wed, 26 Feb 1997 16:07:59 -0500 (EST) Received: by gnu.sdsp.mc.xerox.com (4.1/client-1.3) id AA16436; Wed, 26 Feb 97 16:07:43 EST Message-Id: <9702262107.AA16436@gnu.sdsp.mc.xerox.com> X-Mailer: exmh version 2.0gamma 1/27/96 To: Darren Reed Cc: julian@whistle.com (Julian Elischer), matt@lkg.dec.com, terry@lambert.org, hackers@freebsd.org Subject: Re: Alternatives to SYSV IPC? In-Reply-To: Your message of "Mon, 24 Feb 1997 00:14:16 PST." <199702240814.AAA07697@freefall.freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 26 Feb 1997 13:07:42 PST From: "Marty Leisner" Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > In some mail from Julian Elischer, sie said: > > > > > if (socketpair(AF_UNIX, SOCK_STREAM, 0, fds) < 0) > > > perror("socketpair"); > > > > > > > how come no-one uses AF_LOCAL with SOCK_DGRAM? > > how portable is AF_LOCAL ? > > Darren Is AF_LOCAL/SOCK_DGRAM posix 1003.1g? -- marty leisner@sdsp.mc.xerox.com From owner-freebsd-hackers Wed Feb 26 13:37:10 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id NAA04889 for hackers-outgoing; Wed, 26 Feb 1997 13:37:10 -0800 (PST) Received: (from mpp@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id NAA04882 for freebsd-hackers; Wed, 26 Feb 1997 13:37:08 -0800 (PST) From: Mike Pritchard Message-Id: <199702262137.NAA04882@freefall.freebsd.org> Subject: sig*set macros in To: freebsd-hackers Date: Wed, 26 Feb 1997 13:37:08 -0800 (PST) X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Is there a good reason for having the sig*set macros defined in and the equivalent functions in libc? The macros are only defined if _ANSI_SOURCE isn't. Plus it doesn't looks like they are used that much anyways (about 2 dozen programs). -- Mike Pritchard mpp@FreeBSD.org "Go that way. Really fast. If something gets in your way, turn" From owner-freebsd-hackers Wed Feb 26 14:26:18 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id OAA07252 for hackers-outgoing; Wed, 26 Feb 1997 14:26:18 -0800 (PST) Received: from atlantis.ping.at (a013.static.Vienna.AT.EU.net [193.154.186.13]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id OAA07247 for ; Wed, 26 Feb 1997 14:26:13 -0800 (PST) Received: from atlantis (localhost.ping.at [127.0.0.1]) by atlantis.ping.at (8.7.6/8.6.12) with SMTP id XAA00387; Wed, 26 Feb 1997 23:25:34 +0100 (MET) Message-ID: <3314B85D.167EB0E7@ping.at> Date: Wed, 26 Feb 1997 23:25:33 +0100 From: "Helmut F. Wirth" X-Mailer: Mozilla 3.0 (X11; I; FreeBSD 2.1.7-RELEASE i386) MIME-Version: 1.0 To: freebsd-hackers@FreeBSD.ORG Subject: Pentium MMX Extensions, Changes to (g)as and gdb Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Hello, I made some changes to gas and gdb to support the new MMX extensions for the Pentium P55C. The changes are only in some files. I am currently in the process of testing them. I have added support for all new opcodes in the assembler and in the disassembler part of the debugger. With the assembler one is able to use gcc _asm statements to utilize the new opcodes. Question: Are you interested in these changes ? If yes, please drop me a line. The changes, a short description and a description of the tests they passed will probably be ready at the end of this week. As I have 2.1.7-stable yet, the changes are against this sources. But all changes are in files wich themselves have not changed for quite a time (I think). So if you need changes against 3.0-current, please say so. I will obtain the sources and work with them. Regards Helmut -- Helmut F. Wirth Email: hfwirth@ping.at From owner-freebsd-hackers Wed Feb 26 14:35:44 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id OAA07714 for hackers-outgoing; Wed, 26 Feb 1997 14:35:44 -0800 (PST) Received: from vinyl.quickweb.com (vinyl.quickweb.com [206.222.77.8]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id OAA07708 for ; Wed, 26 Feb 1997 14:35:42 -0800 (PST) Received: from localhost (mark@localhost) by vinyl.quickweb.com (8.7.5/8.6.12) with SMTP id RAA12909; Wed, 26 Feb 1997 17:35:46 -0500 (EST) Date: Wed, 26 Feb 1997 17:35:46 -0500 (EST) From: Mark Mayo To: Amancio Hasty cc: hackers@FreeBSD.ORG Subject: Re: CTPPRO? In-Reply-To: <199702230935.BAA05670@rah.star-gate.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Sun, 23 Feb 1997, Amancio Hasty wrote: > > Hi, > > I found a device driver called perfmon in -current. It can read the > model specific registers and write them (rdmsr and wrmsr). > Additionally, if you search the web for Intel Secrets and look up > Pentium Pro Family Developer's Manual in Appendix C it has a description > for the Model specific registers. The filename is 242692_1.pdf . Got it. I'll peek at Appendix C. > > I think that these are all the bits that we need to implement fastvid 8) > I gave the code for ctppro.pas to my friend who will translate for us - should have the english version back real soon. So do you think we should do this in userland through /dev/io, or write a device driver that fires up the correct registers during bootup? -Mark > > Enjoy, > Amancio > > > > > ---------------------------------------------------------------------------- Mark Mayo mark@quickweb.com RingZero Comp. http://vinyl.quickweb.com/mark ---------------------------------------------------------------------------- Nature shows that with the growth of intelligence comes increased capacity for pain, and it is only with the highest degree of intelligence that suffering reaches its supreme point. -- Arthur Schopenhauer From owner-freebsd-hackers Wed Feb 26 14:43:38 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id OAA08069 for hackers-outgoing; Wed, 26 Feb 1997 14:43:38 -0800 (PST) Received: from monorail.net-tel.co.uk (monorail.net-tel.co.uk [193.122.171.247]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id OAA08056 for ; Wed, 26 Feb 1997 14:43:27 -0800 (PST) From: Andrew.Gordon@net-tel.co.uk Received: (from root@localhost) by monorail.net-tel.co.uk (8.8.4/8.8.4) id WAA19697; Wed, 26 Feb 1997 22:42:39 GMT Received: from "/PRMD=NET-TEL/ADMD=GOLD 400/C=GB/" by net-tel.co.uk (Route400-RFCGate); Wed, 26 Feb 97 22:38:52 +0000 X400-Received: by mta "net-tel cambridge" in "/PRMD=net-tel/ADMD=gold 400/C=gb/"; Relayed; Wed, 26 Feb 97 22:38:52 +0000 X400-Received: by "/PRMD=NET-TEL/ADMD=Gold 400/C=GB/"; Relayed; Wed, 26 Feb 97 22:38:52 +0000 X400-MTS-Identifier: ["/PRMD=NET-TEL/ADMD=Gold 400/C=GB/";hst:7086-970226223852-7E55] X400-Content-Type: P2-1984 (2) X400-Originator: Andrew.Gordon@net-tel.co.uk Original-Encoded-Information-Types: IA5-Text X400-Recipients: non-disclosure:; Date: Wed, 26 Feb 97 22:38:52 +0000 X400-Content-Identifier: Re(2): Building Message-Id: <"2818-970226224035-BC18*/G=Andrew/S=Gordon/O=NET-TEL Computer Systems Ltd/PRMD=NET-TEL/ADMD=Gold 400/C=GB/"@MHS> To: SimsS Cc: Hackers In-Reply-To: <199702262032.UAA71641@out1.ibm.net> Subject: Re(2): Building PAO kernel on non-PAO system Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > I think you missed my point - It's not possible (or I'm not smart enough to > know how) to build, say, 2.1.7, 2.2 *AND* -current kernels on a single > "super > server" and then blow them out amongst the unsuspecting users depending on > their needs (and possibly their threshold for pain). Can such a thing be > done? Obviously, I can build different *configurations* of a single > release > version, but I can't (easily) have different versions of the OS all build > from the same source tree. I have had success in the past with working in a chroot environment. My reason for wanting to do this was that I had a fast-ish machine used for real work and hence running -stable, plus an old 386sx available for hacking on, clearly quite unsuitable for doing 'make world'! Since I was adding an extra drive to hold the -current sources, I took the easy option for getting it initialised: I just used sysinstall to do a basic install, such that the new drive contained a bootable system. I then did as follows: mount the new drive as /current install -current source on /current/usr/src chroot /current cd /usr/src make world build kernel On the 386: NFS mount big_machine:/current/usr/src on /usr/src cd /usr/src make install The only minor snag I ran into was that 'make install' left /usr/include/* as symlinks into the /usr/src, which needed to be undone if I didn't want to leave the NFS mounts in place permanently. Maybe there are other snags, but it was remarkably painless for me. From owner-freebsd-hackers Wed Feb 26 15:10:14 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id PAA09971 for hackers-outgoing; Wed, 26 Feb 1997 15:10:14 -0800 (PST) Received: from huey.cadvision.com (huey.cadvision.com [204.50.1.2]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id PAA09956 for ; Wed, 26 Feb 1997 15:10:07 -0800 (PST) Received: from default.cadvision.com (ts21ip243.cadvision.com [207.228.68.243]) by huey.cadvision.com (8.7.5/8.7.5/DCX/TRI) with ESMTP id QAA17332 for ; Wed, 26 Feb 1997 16:08:12 -0700 Message-Id: <199702262308.QAA17332@huey.cadvision.com> From: "Shane Rohof" To: Subject: can you teach me to hack Date: Wed, 26 Feb 1997 16:09:32 -0700 X-MSMail-Priority: Normal X-Priority: 3 X-Mailer: Microsoft Internet Mail 4.70.1155 MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk hey, I am interested in learning how to hack. I was ondering if you could tech me how this is done. THANK YOU Eagle From owner-freebsd-hackers Wed Feb 26 15:46:06 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id PAA11794 for hackers-outgoing; Wed, 26 Feb 1997 15:46:06 -0800 (PST) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.50]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id PAA11785 for ; Wed, 26 Feb 1997 15:46:03 -0800 (PST) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id QAA28992; Wed, 26 Feb 1997 16:41:30 -0700 From: Terry Lambert Message-Id: <199702262341.QAA28992@phaeton.artisoft.com> Subject: Re: can you teach me to hack To: rohofs@cadvision.com (Shane Rohof) Date: Wed, 26 Feb 1997 16:41:30 -0700 (MST) Cc: hackers@freebsd.org In-Reply-To: <199702262308.QAA17332@huey.cadvision.com> from "Shane Rohof" at Feb 26, 97 04:09:32 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-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > hey, I am interested in learning how to hack. I was ondering if you could > tech me how this is done. THANK YOU The best way to learn to "hack" is to buy yourself an axe, some good wood, and watch "The New Yankee Workshop" on PBS. 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-hackers Wed Feb 26 15:49:38 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id PAA12244 for hackers-outgoing; Wed, 26 Feb 1997 15:49:38 -0800 (PST) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id PAA12158 for ; Wed, 26 Feb 1997 15:49:18 -0800 (PST) Received: from current1.whistle.com (current1.whistle.com [207.76.205.22]) by alpo.whistle.com (8.8.5/8.8.4) with SMTP id PAA21587; Wed, 26 Feb 1997 15:41:54 -0800 (PST) Message-ID: <3314C9BE.4487EB71@whistle.com> Date: Wed, 26 Feb 1997 15:39:42 -0800 From: Julian Elischer Organization: Whistle Communications X-Mailer: Mozilla 3.0Gold (X11; I; FreeBSD 2.2-CURRENT i386) MIME-Version: 1.0 To: hackers@freebsd.org CC: julian@alpo.whistle.com Subject: [RFC] Networking diffs Content-Type: multipart/mixed; boundary="------------62319AC452BFA1D76201DD56" Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk This is a multi-part message in MIME format. --------------62319AC452BFA1D76201DD56 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Since we got the ability of having many addresses per interface, (with the creation of the ifaddr struct) there has been a gradual cleanup of things that were affected. Here is another set. Basically the rtentry structure has (now had) an entry rt_ifp. this is a problem because what it REALLY is linked to is an ifaddr, which (usually) is linked to an ifnet. In the case where an address if taken away from an interface, there can remain floating references to this ifaddr, which can be cleaned up as encountered, however the ifnet pointer bypases this and continues to point to the ifnet that the adress was originally made on. This may no longer be a valid assumption, especially in the light of interfaces becoming transient opjects. (due to removable hardware, or virtual interfaces on multiple channnel links e.g. frame relay). This set of patches totally removes the (historical) ifnet direct pointer from the rtentry struct, (replacing it with a dummy for spacing) and uses the sequence rt_ifa->ifa_ifp instead.. there are several problems: 1/ rt_ifa must not be null for this to not core-dump.. I have added many test for this case, and hopefully they make sense.. (I NEED FEEDBACK ON WHAT I HAVE DONE HERE) 2/ rtalloc (and friends) now ensure that when they return an entry they check to see that this is valid, so immediatly after an rtalloc(), it is safe to assume that it is non NULL. comments? --------------62319AC452BFA1D76201DD56 Content-Type: text/plain; charset=us-ascii; name="netdiffs" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="netdiffs" ? netgraph/copyright ? netgraph/rm_interface.patches Index: net/if.c =================================================================== RCS file: /cvs/freebsd/src/sys/net/if.c,v retrieving revision 1.36 diff -u -r1.36 if.c --- 1.36 1996/08/07 04:09:05 +++ if.c 1997/02/26 23:26:47 @@ -363,15 +363,12 @@ if_up(ifp) register struct ifnet *ifp; { + register struct ifaddr *ifa; ifp->if_flags |= IFF_UP; microtime(&ifp->if_lastchange); -#ifdef notyet - register struct ifaddr *ifa; - /* this has no effect on IP, and will kill all iso connections XXX */ for (ifa = ifp->if_addrlist; ifa; ifa = ifa->ifa_next) pfctlinput(PRC_IFUP, ifa->ifa_addr); -#endif rt_ifmsg(ifp); } Index: net/if_loop.c =================================================================== RCS file: /cvs/freebsd/src/sys/net/if_loop.c,v retrieving revision 1.22 diff -u -r1.22 if_loop.c --- 1.22 1996/06/19 16:24:10 +++ if_loop.c 1997/02/26 23:26:47 @@ -233,8 +233,8 @@ struct rtentry *rt; struct sockaddr *sa; { - if (rt) { - rt->rt_rmx.rmx_mtu = rt->rt_ifp->if_mtu; /* for ISO */ + if (rt) { /* XXX should check for null pointers here */ + rt->rt_rmx.rmx_mtu = rt->rt_ifa->ifa_ifp->if_mtu; /* for ISO */ /* * For optimal performance, the send and receive buffers * should be at least twice the MTU plus a little more for Index: net/if_tun.h =================================================================== RCS file: /cvs/freebsd/src/sys/net/if_tun.h,v retrieving revision 1.6.2.2 diff -u -r1.6.2.2 if_tun.h --- 1.6.2.2 1996/12/04 19:07:52 +++ if_tun.h 1997/02/26 23:26:47 @@ -39,7 +39,7 @@ }; /* Maximum packet size */ -#define TUNMTU 1500 +#define TUNMTU 1600 struct tuninfo { int baudrate; /* linespeed */ Index: net/route.c =================================================================== RCS file: /cvs/freebsd/src/sys/net/route.c,v retrieving revision 1.37 diff -u -r1.37 route.c --- 1.37 1996/09/10 07:10:05 +++ route.c 1997/02/26 23:26:47 @@ -93,8 +93,19 @@ rtalloc(ro) register struct route *ro; { - if (ro->ro_rt && ro->ro_rt->rt_ifp && (ro->ro_rt->rt_flags & RTF_UP)) + if (ro->ro_rt && ro->ro_rt->rt_ifa + && (ro->ro_rt->rt_ifa->ifa_ifp) + && (ro->ro_rt->rt_flags & RTF_UP)) return; /* XXX */ + /* + * check to see if the reason we got here was due to an + * out of date route/ifaddr. + */ + if(ro->ro_rt && ro->ro_rt->rt_ifa + && (ro->ro_rt->rt_ifa->ifa_ifp == NULL)) { + IFAFREE(ro->ro_rt->rt_ifa); + /* XXX shouldn't we free the rt? */ + } ro->ro_rt = rtalloc1(&ro->ro_dst, 1, 0UL); } @@ -103,8 +114,19 @@ register struct route *ro; u_long ignore; { - if (ro->ro_rt && ro->ro_rt->rt_ifp && (ro->ro_rt->rt_flags & RTF_UP)) + if (ro->ro_rt && ro->ro_rt->rt_ifa + && (ro->ro_rt->rt_ifa->ifa_ifp) + && (ro->ro_rt->rt_flags & RTF_UP)) return; /* XXX */ + /* + * check to see if the reason we got here was due to an + * out of date route/ifaddr. + */ + if(ro->ro_rt && ro->ro_rt->rt_ifa + && (ro->ro_rt->rt_ifa->ifa_ifp == NULL)) { + IFAFREE(ro->ro_rt->rt_ifa); + /* XXX shouldn't we free the rt? */ + } ro->ro_rt = rtalloc1(&ro->ro_dst, 1, ignore); } @@ -113,22 +135,23 @@ * Or, at least try.. Create a cloned route if needed. */ struct rtentry * -rtalloc1(dst, report, ignflags) - register struct sockaddr *dst; - int report; - u_long ignflags; +rtalloc1(struct sockaddr *dst, int report, u_long ignflags) { register struct radix_node_head *rnh = rt_tables[dst->sa_family]; register struct rtentry *rt; register struct radix_node *rn; - struct rtentry *newrt = 0; + struct rtentry *newrt; struct rt_addrinfo info; u_long nflags; - int s = splnet(), err = 0, msgtype = RTM_MISS; + int s, err = 0, msgtype = RTM_MISS; + + s = splnet(); /* * Look up the address in the table for that Address Family */ +retry: + newrt = NULL; if (rnh && (rn = rnh->rnh_matchaddr((caddr_t)dst, rnh)) && ((rn->rn_flags & RNF_ROOT) == 0)) { /* @@ -136,6 +159,22 @@ * get a refernce on the rtentry associated. */ newrt = rt = (struct rtentry *)rn; + /* + * hosekeeping: + * Check that this doesn't refer to an ifaddr + * that is now invalid. + */ + if ((rt->rt_ifa == NULL) || (rt->rt_ifa->ifa_ifp == NULL)) { + if ( rt->rt_ifa ) { + IFAFREE( rt->rt_ifa ); + rt->rt_ifa = NULL; + } + /* + * throw this out of the tree! + */ + rtfree(rt); + goto retry; + } nflags = rt->rt_flags & ~ignflags; if (report && (nflags & (RTF_CLONING | RTF_PRCLONING))) { /* @@ -533,7 +572,8 @@ */ ifa->ifa_refcnt++; rt->rt_ifa = ifa; - rt->rt_ifp = ifa->ifa_ifp; + rt->rt_ifx = NULL; + /* rt->rt_ifp = ifa->ifa_ifp; */ /* XXX get rid of this */ rn = rnh->rnh_addaddr((caddr_t)ndst, (caddr_t)netmask, rnh, rt->rt_nodes); @@ -940,7 +980,7 @@ * we are adding. */ rt->rt_ifa = ifa; - rt->rt_ifp = ifa->ifa_ifp; + rt->rt_ifx = NULL ; /* get rid of this asap */ /*XXX*/ ifa->ifa_refcnt++; /* * Now add it to the routing table Index: net/route.h =================================================================== RCS file: /cvs/freebsd/src/sys/net/route.h,v retrieving revision 1.23 diff -u -r1.23 route.h --- 1.23 1996/10/09 18:35:10 +++ route.h 1997/02/26 23:26:47 @@ -104,7 +104,7 @@ short rt_filler; /* was short flags field */ short rt_refcnt; /* # held references */ u_long rt_flags; /* up/down?, host/net */ - struct ifnet *rt_ifp; /* the answer: interface to use */ + struct ifnet *rt_ifx; /* the answer: interface to use */ struct ifaddr *rt_ifa; /* the answer: interface to use */ struct sockaddr *rt_genmask; /* for generation of cloned routes */ caddr_t rt_llinfo; /* pointer to link level info cache */ Index: net/rtsock.c =================================================================== RCS file: /cvs/freebsd/src/sys/net/rtsock.c,v retrieving revision 1.20 diff -u -r1.20 rtsock.c --- 1.20 1996/07/10 01:34:36 +++ rtsock.c 1997/02/26 23:26:47 @@ -233,7 +233,9 @@ netmask = rt_mask(rt); genmask = rt->rt_genmask; if (rtm->rtm_addrs & (RTA_IFP | RTA_IFA)) { - ifp = rt->rt_ifp; + ifp = NULL; + if (rt->rt_ifa) + ifp = rt->rt_ifa->ifa_ifp; if (ifp) { ifpaddr = ifp->if_addrlist->ifa_addr; ifaaddr = rt->rt_ifa->ifa_addr; @@ -294,7 +296,7 @@ IFAFREE(rt->rt_ifa); rt->rt_ifa = ifa; ifa->ifa_refcnt++; - rt->rt_ifp = ifp; + rt->rt_ifx = NULL; /* XXX kill me */ } } rt_setmetrics(rtm->rtm_inits, &rtm->rtm_rmx, @@ -665,7 +667,8 @@ rtm->rtm_flags = rt->rt_flags; rtm->rtm_use = rt->rt_use; rtm->rtm_rmx = rt->rt_rmx; - rtm->rtm_index = rt->rt_ifp->if_index; + rtm->rtm_index = ((rt->rt_ifa)? + (rt->rt_ifa->ifa_ifp->if_index) : (0)); rtm->rtm_errno = rtm->rtm_pid = rtm->rtm_seq = 0; rtm->rtm_addrs = info.rti_addrs; error = SYSCTL_OUT(w->w_req, (caddr_t)rtm, size); Index: netatalk/at_extern.h =================================================================== RCS file: /cvs/freebsd/src/sys/netatalk/at_extern.h,v retrieving revision 1.1 diff -u -r1.1 at_extern.h --- 1.1 1996/05/24 01:35:23 +++ at_extern.h 1997/02/26 23:26:47 @@ -27,7 +27,9 @@ extern struct ifaddr *at_ifawithnet __P((struct sockaddr_at *, struct ifaddr *)); #ifdef _NETATALK_DDP_VAR_H_ -extern int ddp_output __P(( struct ddpcb *ddp, struct mbuf *m)); +extern int ddp_output __P((struct mbuf *m, struct socket *so)); + +/*extern int ddp_output __P(( struct ddpcb *ddp, struct mbuf *m));*/ #endif #if defined (_NETATALK_DDP_VAR_H_) && defined(_NETATALK_AT_VAR_H_) extern struct ddpcb *ddp_search __P((struct sockaddr_at *, Index: netatalk/at_proto.c =================================================================== RCS file: /cvs/freebsd/src/sys/netatalk/at_proto.c,v retrieving revision 1.4 diff -u -r1.4 at_proto.c --- 1.4 1996/09/10 08:23:10 +++ at_proto.c 1997/02/26 23:26:47 @@ -54,7 +54,10 @@ * pr_output can be used by higher level appletalk protocols, should * they be included in the kernel. */ - 0, ddp_output, 0, 0, + 0, +ddp_output, +0, +0, /* socket-protocol interface. */ ddp_usrreq, /* utility routines. */ Index: netatalk/ddp_input.c =================================================================== RCS file: /cvs/freebsd/src/sys/netatalk/ddp_input.c,v retrieving revision 1.3 diff -u -r1.3 ddp_input.c --- 1.3 1996/09/10 08:23:11 +++ ddp_input.c 1997/02/26 23:26:47 @@ -253,7 +253,8 @@ forwro.ro_rt = (struct rtentry *)0; } if ( forwro.ro_rt == (struct rtentry *)0 || - forwro.ro_rt->rt_ifp == (struct ifnet *)0 ) { + forwro.ro_rt->rt_ifa == (struct ifaddr *)0 || + forwro.ro_rt->rt_ifa->ifa_ifp == (struct ifnet *)0 ) { forwro.ro_dst.sa_len = sizeof( struct sockaddr_at ); forwro.ro_dst.sa_family = AF_APPLETALK; satosat( &forwro.ro_dst )->sat_addr.s_net = to.sat_addr.s_net; @@ -268,7 +269,9 @@ } if ( ddp_firewall && - ( forwro.ro_rt == NULL || forwro.ro_rt->rt_ifp != ifp )) { + ( forwro.ro_rt == NULL + || forwro.ro_rt->rt_ifa == NULL + || forwro.ro_rt->rt_ifa->ifa_ifp != ifp )) { m_freem( m ); return; } Index: netatalk/ddp_output.c =================================================================== RCS file: /cvs/freebsd/src/sys/netatalk/ddp_output.c,v retrieving revision 1.3 diff -u -r1.3 ddp_output.c --- 1.3 1996/09/10 08:23:13 +++ ddp_output.c 1997/02/26 23:26:47 @@ -26,6 +26,7 @@ #include #include #include +#include #include #include @@ -46,9 +47,11 @@ int ddp_cksum = 1; int -ddp_output( struct ddpcb *ddp, struct mbuf *m) +/*ddp_output( struct ddpcb *ddp, struct mbuf *m)*/ +ddp_output( struct mbuf *m, struct socket *so) { struct ddpehdr *deh; + struct ddpcb *ddp = sotoddpcb( so ); M_PREPEND( m, sizeof( struct ddpehdr ), M_WAIT ); @@ -116,7 +119,8 @@ struct ifnet *ifp = NULL; u_short net; - if ( ro->ro_rt && ( ifp = ro->ro_rt->rt_ifp )) { + if ( ro->ro_rt && ro->ro_rt->rt_ifa + && (ifp = ro->ro_rt->rt_ifa->ifa_ifp )) { net = satosat( ro->ro_rt->rt_gateway )->sat_addr.s_net; for ( aa = at_ifaddr; aa; aa = aa->aa_next ) { if ( aa->aa_ifp == ifp && Index: netatalk/ddp_usrreq.c =================================================================== RCS file: /cvs/freebsd/src/sys/netatalk/ddp_usrreq.c,v retrieving revision 1.4 diff -u -r1.4 ddp_usrreq.c --- 1.4 1996/09/10 08:23:15 +++ ddp_usrreq.c 1997/02/26 23:26:48 @@ -133,7 +133,7 @@ } } - error = ddp_output( ddp, m ); + error = ddp_output( m, so ); m = NULL; if ( addr ) { at_pcbdisconnect( ddp ); @@ -331,7 +331,8 @@ net = sat->sat_addr.s_net; } aa = 0; - if ( ifp = ro->ro_rt->rt_ifp ) { + if ( ro->ro_rt && ro->ro_rt->rt_ifa + && (ifp = ro->ro_rt->rt_ifa->ifa_ifp)) { for ( aa = at_ifaddr; aa; aa = aa->aa_next ) { if ( aa->aa_ifp == ifp && ntohs( net ) >= ntohs( aa->aa_firstnet ) && @@ -352,8 +353,9 @@ /* * If we've got no route for this interface, try to find one. */ - if ( ro->ro_rt == (struct rtentry *)0 || - ro->ro_rt->rt_ifp == (struct ifnet *)0 ) { + if ( ro->ro_rt == NULL || + ro->ro_rt->rt_ifa == NULL || + ro->ro_rt->rt_ifa->ifa_ifp == NULL ) { ro->ro_dst.sa_len = sizeof( struct sockaddr_at ); ro->ro_dst.sa_family = AF_APPLETALK; if ( hintnet ) { @@ -369,7 +371,8 @@ * Make sure any route that we have has a valid interface. */ aa = 0; - if ( ro->ro_rt && ( ifp = ro->ro_rt->rt_ifp )) { + if ( ro->ro_rt && ro->ro_rt->rt_ifa + && ( ifp = ro->ro_rt->rt_ifa->ifa_ifp )) { for ( aa = at_ifaddr; aa; aa = aa->aa_next ) { if ( aa->aa_ifp == ifp ) { break; Index: netinet/if_ether.c =================================================================== RCS file: /cvs/freebsd/src/sys/netinet/if_ether.c,v retrieving revision 1.34.2.1 diff -u -r1.34.2.1 if_ether.c --- 1.34.2.1 1996/11/16 21:17:49 +++ if_ether.c 1997/02/26 23:26:48 @@ -154,6 +154,16 @@ } if (rt->rt_flags & RTF_GATEWAY) return; + /* XXX + * not sure what to do here.. + * We've come in here with an rt that points ot an invalid ifaddr.. + * if we don't do this here, we need to test it in 7 places below. + */ + if (rt->rt_ifa->ifa_ifp == NULL ) { + IFAFREE(rt->rt_ifa); + rt->rt_ifa = NULL; + req = RTM_DELETE; /* XXX */ + } switch (req) { case RTM_ADD: @@ -172,14 +182,14 @@ rt_setgate(rt, rt_key(rt), (struct sockaddr *)&null_sdl); gate = rt->rt_gateway; - SDL(gate)->sdl_type = rt->rt_ifp->if_type; - SDL(gate)->sdl_index = rt->rt_ifp->if_index; + SDL(gate)->sdl_type = rt->rt_ifa->ifa_ifp->if_type; + SDL(gate)->sdl_index = rt->rt_ifa->ifa_ifp->if_index; rt->rt_expire = time.tv_sec; break; } /* Announce a new entry if requested. */ if (rt->rt_flags & RTF_ANNOUNCE) - arprequest((struct arpcom *)rt->rt_ifp, + arprequest((struct arpcom *)rt->rt_ifa->ifa_ifp, &SIN(rt_key(rt))->sin_addr.s_addr, &SIN(rt_key(rt))->sin_addr.s_addr, (u_char *)LLADDR(SDL(gate))); @@ -190,8 +200,8 @@ log(LOG_DEBUG, "arp_rtrequest: bad gateway value\n"); break; } - SDL(gate)->sdl_type = rt->rt_ifp->if_type; - SDL(gate)->sdl_index = rt->rt_ifp->if_index; + SDL(gate)->sdl_type = rt->rt_ifa->ifa_ifp->if_type; + SDL(gate)->sdl_index = rt->rt_ifa->ifa_ifp->if_index; if (la != 0) break; /* This happens on a route change */ /* @@ -221,7 +231,8 @@ SDL(gate)->sdl_alen = 6; rt->rt_expire = 0; } - if (in_broadcast(SIN(rt_key(rt))->sin_addr, rt->rt_ifp)) { + if (in_broadcast(SIN(rt_key(rt))->sin_addr, + rt->rt_ifa->ifa_ifp)) { memcpy(LLADDR(SDL(gate)), etherbroadcastaddr, 6); SDL(gate)->sdl_alen = 6; rt->rt_expire = 0; @@ -240,11 +251,10 @@ * the route to force traffic out to the hardware. */ rt->rt_expire = 0; - Bcopy(((struct arpcom *)rt->rt_ifp)->ac_enaddr, + Bcopy(((struct arpcom *)rt->rt_ifa->ifa_ifp)->ac_enaddr, LLADDR(SDL(gate)), SDL(gate)->sdl_alen = 6); if (useloopback) - rt->rt_ifp = loif; - + rt->rt_ifa = loif->if_addrlist; /* XXX */ } break; @@ -535,7 +545,7 @@ * as this one came out of, or we'll get into a fight * over who claims what Ether address. */ - if (rt->rt_ifp == &ac->ac_if) { + if (rt->rt_ifa && (rt->rt_ifa->ifa_ifp == &ac->ac_if)) { rtfree(rt); m_freem(m); return; Index: netinet/in.c =================================================================== RCS file: /cvs/freebsd/src/sys/netinet/in.c,v retrieving revision 1.25 diff -u -r1.25 in.c --- 1.25 1996/09/09 20:17:24 +++ in.c 1997/02/26 23:26:48 @@ -70,7 +70,6 @@ static void in_socktrim __P((struct sockaddr_in *)); static int in_ifinit __P((struct ifnet *, struct in_ifaddr *, struct sockaddr_in *, int)); -static void in_ifscrub __P((struct ifnet *, struct in_ifaddr *)); static int subnetsarelocal = 0; SYSCTL_INT(_net_inet_ip, OID_AUTO, subnets_are_local, CTLFLAG_RW, @@ -453,7 +452,7 @@ /* * Delete any existing route for an interface. */ -static void +void in_ifscrub(ifp, ia) register struct ifnet *ifp; register struct in_ifaddr *ia; Index: netinet/in_pcb.c =================================================================== RCS file: /cvs/freebsd/src/sys/netinet/in_pcb.c,v retrieving revision 1.23 diff -u -r1.23 in_pcb.c --- 1.23 1996/10/30 06:13:09 +++ in_pcb.c 1997/02/26 23:26:48 @@ -324,7 +324,8 @@ } if ((inp->inp_socket->so_options & SO_DONTROUTE) == 0 && /*XXX*/ (ro->ro_rt == (struct rtentry *)0 || - ro->ro_rt->rt_ifp == (struct ifnet *)0)) { + ro->ro_rt->rt_ifa == (struct ifaddr *)0 || + ro->ro_rt->rt_ifa->ifa_ifp == (struct ifnet *)0)) { /* No route yet, so try to acquire one */ ro->ro_dst.sa_family = AF_INET; ro->ro_dst.sa_len = sizeof(struct sockaddr_in); @@ -338,7 +339,8 @@ * unless it is the loopback (in case a route * to our address on another net goes to loopback). */ - if (ro->ro_rt && !(ro->ro_rt->rt_ifp->if_flags & IFF_LOOPBACK)) + if (ro->ro_rt && + !(ro->ro_rt->rt_ifa->ifa_ifp->if_flags & IFF_LOOPBACK)) ia = ifatoia(ro->ro_rt->rt_ifa); if (ia == 0) { u_short fport = sin->sin_port; Index: netinet/in_proto.c =================================================================== RCS file: /cvs/freebsd/src/sys/netinet/in_proto.c,v retrieving revision 1.33 diff -u -r1.33 in_proto.c --- 1.33 1996/07/11 16:32:31 +++ in_proto.c 1997/02/26 23:26:48 @@ -110,7 +110,7 @@ &tcp_usrreqs }, { SOCK_RAW, &inetdomain, IPPROTO_RAW, PR_ATOMIC|PR_ADDR, - rip_input, 0, 0, rip_ctloutput, + rip_input, 0, rip_ctlinput, rip_ctloutput, rip_usrreq, 0, 0, 0, 0, }, Index: netinet/in_rmx.c =================================================================== RCS file: /cvs/freebsd/src/sys/netinet/in_rmx.c,v retrieving revision 1.26 diff -u -r1.26 in_rmx.c --- 1.26 1996/06/20 15:41:23 +++ in_rmx.c 1997/02/26 23:26:48 @@ -108,7 +108,7 @@ * is done above.) */ if (rt->rt_flags & RTF_HOST) { - if (in_broadcast(sin->sin_addr, rt->rt_ifp)) { + if (in_broadcast(sin->sin_addr, rt->rt_ifa->ifa_ifp)) { rt->rt_flags |= RTF_BROADCAST; } else { #define satosin(sa) ((struct sockaddr_in *)sa) @@ -137,8 +137,8 @@ rt->rt_rmx.rmx_recvpipe = tcp_recvspace; if (!rt->rt_rmx.rmx_mtu && !(rt->rt_rmx.rmx_locks & RTV_MTU) - && rt->rt_ifp) - rt->rt_rmx.rmx_mtu = rt->rt_ifp->if_mtu; + && rt->rt_ifa && rt->rt_ifa->ifa_ifp ) + rt->rt_rmx.rmx_mtu = rt->rt_ifa->ifa_ifp->if_mtu; ret = rn_addroute(v_arg, n_arg, head, treenodes); if (ret == NULL && rt->rt_flags & RTF_HOST) { @@ -382,3 +382,44 @@ return 1; } + +/* + * This zaps old routes when the interface goes down. + */ +struct in_ifadown_arg { + struct radix_node_head *rnh; + struct ifaddr *ifa; +}; + +static int +in_ifadownkill(struct radix_node *rn, void *xap) +{ + struct in_ifadown_arg *ap = xap; + struct rtentry *rt = (struct rtentry *)rn; + int err; + + if (rt->rt_ifa == ap->ifa) { + err = rtrequest(RTM_DELETE, (struct sockaddr *)rt_key(rt), + rt->rt_gateway, rt_mask(rt), rt->rt_flags, 0); + if (err) { + log(LOG_WARNING, "in_ifadownkill: error %d\n", err); + } + } + return 0; +} + +int +in_ifadown(struct ifaddr *ifa) +{ + struct in_ifadown_arg arg; + struct radix_node_head *rnh; + + if (ifa->ifa_addr->sa_family != AF_INET) + return 1; + + arg.rnh = rnh = rt_tables[AF_INET]; + arg.ifa = ifa; + rnh->rnh_walktree(rnh, in_ifadownkill, &arg); + ifa->ifa_flags &= ~IFA_ROUTE; + return 0; +} Index: netinet/in_var.h =================================================================== RCS file: /cvs/freebsd/src/sys/netinet/in_var.h,v retrieving revision 1.17 diff -u -r1.17 in_var.h --- 1.17 1996/03/14 16:59:19 +++ in_var.h 1997/02/26 23:26:48 @@ -229,6 +229,8 @@ int in_control __P((struct socket *, u_long, caddr_t, struct ifnet *)); void in_rtqdrain __P((void)); void ip_input __P((struct mbuf *)); +int in_ifadown __P((struct ifaddr *ifa)); +void in_ifscrub __P((struct ifnet *, struct in_ifaddr *)); #endif /* KERNEL */ Index: netinet/ip_icmp.c =================================================================== RCS file: /cvs/freebsd/src/sys/netinet/ip_icmp.c,v retrieving revision 1.22 diff -u -r1.22 ip_icmp.c --- 1.22 1996/09/20 08:23:54 +++ ip_icmp.c 1997/02/26 23:26:48 @@ -350,7 +350,8 @@ #endif if (mtu < 296) { /* rt->rt_rmx.rmx_mtu = - rt->rt_ifp->if_mtu; */ + rt->rt_ifa->ifa_ifp->if_mtu; */ +/*XXX what if rt->rt_ifa->ifa_ifp is NULL? */ rt->rt_rmx.rmx_locks |= RTV_MTU; } else if (rt->rt_rmx.rmx_mtu > mtu) { rt->rt_rmx.rmx_mtu = mtu; Index: netinet/ip_input.c =================================================================== RCS file: /cvs/freebsd/src/sys/netinet/ip_input.c,v retrieving revision 1.50.2.1 diff -u -r1.50.2.1 ip_input.c --- 1.50.2.1 1996/11/11 23:40:45 +++ ip_input.c 1997/02/26 23:26:48 @@ -1244,7 +1244,7 @@ * or a route modified by a redirect. */ #define satosin(sa) ((struct sockaddr_in *)(sa)) - if (rt->rt_ifp == m->m_pkthdr.rcvif && + if (rt->rt_ifa && (rt->rt_ifa->ifa_ifp == m->m_pkthdr.rcvif) && (rt->rt_flags & (RTF_DYNAMIC|RTF_MODIFIED)) == 0 && satosin(rt_key(rt))->sin_addr.s_addr != 0 && ipsendredirects && !srcrt) { @@ -1303,8 +1303,8 @@ case EMSGSIZE: type = ICMP_UNREACH; code = ICMP_UNREACH_NEEDFRAG; - if (ipforward_rt.ro_rt) - destifp = ipforward_rt.ro_rt->rt_ifp; + if (ipforward_rt.ro_rt && ipforward_rt.ro_rt->rt_ifa) + destifp = ipforward_rt.ro_rt->rt_ifa->ifa_ifp; ipstat.ips_cantfrag++; break; Index: netinet/ip_output.c =================================================================== RCS file: /cvs/freebsd/src/sys/netinet/ip_output.c,v retrieving revision 1.44.2.1 diff -u -r1.44.2.1 ip_output.c --- 1.44.2.1 1996/11/11 23:40:49 +++ ip_output.c 1997/02/26 23:26:48 @@ -171,7 +171,8 @@ * the link layer, as this is probably required in all cases * for correct operation (as it is for ARP). */ - if (ro->ro_rt == 0) + if (ro->ro_rt == 0 || ro->ro_rt->rt_ifa == NULL || + ro->ro_rt->rt_ifa->ifa_ifp == NULL) rtalloc_ign(ro, RTF_PRCLONING); if (ro->ro_rt == 0) { ipstat.ips_noroute++; @@ -179,7 +180,7 @@ goto bad; } ia = ifatoia(ro->ro_rt->rt_ifa); - ifp = ro->ro_rt->rt_ifp; + ifp = ro->ro_rt->rt_ifa->ifa_ifp; ro->ro_rt->rt_use++; if (ro->ro_rt->rt_flags & RTF_GATEWAY) dst = (struct sockaddr_in *)ro->ro_rt->rt_gateway; @@ -1052,10 +1053,9 @@ splx(s); break; } - ifp = ro.ro_rt->rt_ifp; + ifp = ro.ro_rt->rt_ifa->ifa_ifp; rtfree(ro.ro_rt); - } - else { + } else { INADDR_TO_IFP(mreq->imr_interface, ifp); } Index: netinet/ip_var.h =================================================================== RCS file: /cvs/freebsd/src/sys/netinet/ip_var.h,v retrieving revision 1.24.2.2 diff -u -r1.24.2.2 ip_var.h --- 1.24.2.2 1996/11/12 11:28:59 +++ ip_var.h 1997/02/26 23:26:48 @@ -185,6 +185,7 @@ ip_srcroute __P((void)); void ip_stripoptions __P((struct mbuf *, struct mbuf *)); int rip_ctloutput __P((int, struct socket *, int, int, struct mbuf **)); +void rip_ctlinput __P((int, struct sockaddr *, void *)); void rip_init __P((void)); void rip_input __P((struct mbuf *, int)); int rip_output __P((struct mbuf *, struct socket *, u_long)); Index: netinet/raw_ip.c =================================================================== RCS file: /cvs/freebsd/src/sys/netinet/raw_ip.c,v retrieving revision 1.37.2.1 diff -u -r1.37.2.1 raw_ip.c --- 1.37.2.1 1996/11/11 23:40:55 +++ raw_ip.c 1997/02/26 23:26:48 @@ -314,6 +314,70 @@ return (ip_ctloutput(op, so, level, optname, m)); } +/* + * This function exists solely to receive the PRC_IFDOWN messages which + * are sent by if_down(). It looks for an ifaddr whose ifa_addr is sa, + * and calls in_ifadown() to remove all routes corresponding to that address. + * It also receives the PRC_IFUP messages from if_up() and reinstalls the + * interface routes. + */ +void +rip_ctlinput(cmd, sa, vip) + int cmd; + struct sockaddr *sa; + void *vip; +{ + struct in_ifaddr *ia; + struct ifnet *ifp; + int err; + int flags; + + switch(cmd) { + case PRC_IFDOWN: + for (ia = in_ifaddr; ia; ia = ia->ia_next) + /*for (ia = in_ifaddrhead.tqh_first; ia; + ia = ia->ia_link.tqe_next)*/ { + if (ia->ia_ifa.ifa_addr == sa + && (ia->ia_flags & IFA_ROUTE)) { + /* + * in_ifscrub kills the interface route. + */ + in_ifscrub(ia->ia_ifp, ia); + /* + * in_ifadown gets rid of all the rest of + * the routes. This is not quite the right + * thing to do, but at least if we are running + * a routing process they will come back. + */ + in_ifadown(&ia->ia_ifa); + break; + } + } + break; + + case PRC_IFUP: + for (ia = in_ifaddr; ia; ia = ia->ia_next) + /*for (ia = in_ifaddrhead.tqh_first; ia; + ia = ia->ia_link.tqe_next)*/ { + if (ia->ia_ifa.ifa_addr == sa) + break; + } + if (ia == 0 || (ia->ia_flags & IFA_ROUTE)) + return; + flags = RTF_UP; + ifp = ia->ia_ifa.ifa_ifp; + + if ((ifp->if_flags & IFF_LOOPBACK) + || (ifp->if_flags & IFF_POINTOPOINT)) + flags |= RTF_HOST; + + err = rtinit(&ia->ia_ifa, RTM_ADD, flags); + if (err == 0) + ia->ia_flags |= IFA_ROUTE; + break; + } +} + static u_long rip_sendspace = RIPSNDQ; /* XXX sysctl ? */ static u_long rip_recvspace = RIPRCVQ; /* XXX sysctl ? */ Index: netinet/tcp_input.c =================================================================== RCS file: /cvs/freebsd/src/sys/netinet/tcp_input.c,v retrieving revision 1.54.2.1 diff -u -r1.54.2.1 tcp_input.c --- 1.54.2.1 1996/11/11 23:40:57 +++ tcp_input.c 1997/02/26 23:26:48 @@ -1971,7 +1971,8 @@ tp->t_maxopd = tp->t_maxseg = tcp_mssdflt; return; } - ifp = rt->rt_ifp; +/* XXX assume at this time that tcp_rtlookup() will ensure thai is safe */ + ifp = rt->rt_ifa->ifa_ifp; so = inp->inp_socket; taop = rmx_taop(rt->rt_rmx); @@ -2124,9 +2125,9 @@ struct rtentry *rt; rt = tcp_rtlookup(tp->t_inpcb); - if (rt == NULL) + if (rt == NULL || rt->rt_ifa->ifa_ifp == NULL) return tcp_mssdflt; - return rt->rt_ifp->if_mtu - sizeof(struct tcpiphdr); + return rt->rt_ifa->ifa_ifp->if_mtu - sizeof(struct tcpiphdr); } #endif /* TUBA_INCLUDE */ Index: netipx/ipx_input.c =================================================================== RCS file: /cvs/freebsd/src/sys/netipx/ipx_input.c,v retrieving revision 1.9 diff -u -r1.9 ipx_input.c --- 1.9 1996/08/18 08:38:15 +++ ipx_input.c 1997/02/26 23:26:48 @@ -390,9 +390,11 @@ goto cleanup; } if (ipx_droute.ro_rt && - (ifp=ipx_droute.ro_rt->rt_ifp) && + ipx_droute.ro_rt->rt_ifa && + (ifp=ipx_droute.ro_rt->rt_ifa->ifa_ifp) && ipx_sroute.ro_rt && - (ifp!=ipx_sroute.ro_rt->rt_ifp)) { + ipx_sroute.ro_rt->rt_ifa && + (ifp!=ipx_sroute.ro_rt->rt_ifa->ifa_ifp)) { flags |= IPX_ALLOWBROADCAST; } else { type = IPX_ERR_UNREACH_HOST, code = 0; @@ -476,7 +478,8 @@ dst->sipx_addr = *src; dst->sipx_addr.x_port = 0; rtalloc(ro); - if (ro->ro_rt == 0 || ro->ro_rt->rt_ifp == 0) { + if (ro->ro_rt == 0 || ro->ro_rt->rt_ifa == 0 + || ro->ro_rt->rt_ifa->ifa_ifp ) { return (0); } ro->ro_rt->rt_use++; Index: netipx/ipx_ip.c =================================================================== RCS file: /cvs/freebsd/src/sys/netipx/ipx_ip.c,v retrieving revision 1.9 diff -u -r1.9 ipx_ip.c --- 1.9 1996/06/12 05:10:27 +++ ipx_ip.c 1997/02/26 23:26:48 @@ -322,7 +322,8 @@ bzero((caddr_t)&ro, sizeof (ro)); ro.ro_dst = *(struct sockaddr *)ip_dst; rtalloc(&ro); - if (ro.ro_rt == 0 || ro.ro_rt->rt_ifp == 0) { + if (ro.ro_rt == 0 || ro.ro_rt->rt_ifa == 0 + || ro.ro_rt->rt_ifa->ifa_ifp == 0) { return (ENETUNREACH); } @@ -332,7 +333,7 @@ */ { register struct in_ifaddr *ia; - struct ifnet *ifp = ro.ro_rt->rt_ifp; + struct ifnet *ifp = ro.ro_rt->rt_ifa->ifa_ifp; for (ia = in_ifaddr; ia; ia = ia->ia_next) if (ia->ia_ifp == ifp) Index: netipx/ipx_outputfl.c =================================================================== RCS file: /cvs/freebsd/src/sys/netipx/ipx_outputfl.c,v retrieving revision 1.4 diff -u -r1.4 ipx_outputfl.c --- 1.4 1996/03/11 15:13:52 +++ ipx_outputfl.c 1997/02/26 23:26:49 @@ -115,7 +115,8 @@ ro->ro_rt = NULL; rtalloc(ro); } - if (ro->ro_rt == 0 || (ifp = ro->ro_rt->rt_ifp) == 0) { + if (ro->ro_rt == 0 || ro->ro_rt->rt_ifa == 0 + || (ifp = ro->ro_rt->rt_ifa->ifa_ifp) == 0) { error = ENETUNREACH; goto bad; } Index: netipx/ipx_pcb.c =================================================================== RCS file: /cvs/freebsd/src/sys/netipx/ipx_pcb.c,v retrieving revision 1.5 diff -u -r1.5 ipx_pcb.c --- 1.5 1996/03/11 15:13:53 +++ ipx_pcb.c 1997/02/26 23:26:49 @@ -173,7 +173,8 @@ ipxp->ipxp_lastdst = sipx->sipx_addr; if ((ipxp->ipxp_socket->so_options & SO_DONTROUTE) == 0 && /*XXX*/ (ro->ro_rt == (struct rtentry *)0 || - ro->ro_rt->rt_ifp == (struct ifnet *)0)) { + ro->ro_rt->rt_ifa == (struct ifaddr *)0 || + ro->ro_rt->rt_ifa->ifa_ifp == (struct ifnet *)0)) { /* No route yet, so try to acquire one */ ro->ro_dst.sa_family = AF_IPX; ro->ro_dst.sa_len = sizeof(ro->ro_dst); @@ -192,7 +193,8 @@ * If we found a route, use the address * corresponding to the outgoing interface */ - if (ro->ro_rt && (ifp = ro->ro_rt->rt_ifp)) + if (ro->ro_rt && ro->ro_rt->rt_ifa + && (ifp = ro->ro_rt->rt_ifa->ifa_ifp)) for (ia = ipx_ifaddr; ia; ia = ia->ia_next) if (ia->ia_ifp == ifp) break; Index: netkey/key_debug.c =================================================================== RCS file: /cvs/freebsd/src/sys/netkey/key_debug.c,v retrieving revision 1.1 diff -u -r1.1 key_debug.c --- 1.1 1996/06/14 17:22:05 +++ key_debug.c 1997/02/26 23:26:49 @@ -539,8 +539,6 @@ printf("rt_rmx.rmx_mtu = %d ",rt->rt_rmx.rmx_mtu); printf("rt_refcnt = %d ",rt->rt_refcnt); printf("rt_flags = 0x%x\n",rt->rt_flags); - printf("rt_ifp is:\n"); - dump_ifp(rt->rt_ifp); printf("rt_ifa is:\n"); dump_ifa(rt->rt_ifa); } Index: netns/ns_input.c =================================================================== RCS file: /cvs/freebsd/src/sys/netns/ns_input.c,v retrieving revision 1.8 diff -u -r1.8 ns_input.c --- 1.8 1996/10/17 18:41:59 +++ ns_input.c 1997/02/26 23:26:49 @@ -367,9 +367,11 @@ goto cleanup; } if (idp_droute.ro_rt && - (ifp=idp_droute.ro_rt->rt_ifp) && + idp_droute.ro_rt->rt_ifa && + (ifp=idp_droute.ro_rt->rt_ifa->ifa_ifp) && idp_sroute.ro_rt && - (ifp!=idp_sroute.ro_rt->rt_ifp)) { + idp_sroute.ro_rt->rt_ifa && + (ifp!=idp_sroute.ro_rt->rt_ifa->ifa_ifp)) { flags |= NS_ALLOWBROADCAST; } else { type = NS_ERR_UNREACH_HOST, code = 0; @@ -442,7 +444,7 @@ dst->sns_addr = *src; dst->sns_addr.x_port = 0; rtalloc(ro); - if (ro->ro_rt == 0 || ro->ro_rt->rt_ifp == 0) { + if (ro->ro_rt == 0 || ro->ro_rt->rt_ifa->ifa_ifp == 0) { return (0); } ro->ro_rt->rt_use++; Index: netns/ns_ip.c =================================================================== RCS file: /cvs/freebsd/src/sys/netns/ns_ip.c,v retrieving revision 1.6 diff -u -r1.6 ns_ip.c --- 1.6 1996/10/17 18:42:02 +++ ns_ip.c 1997/02/26 23:26:49 @@ -330,7 +330,7 @@ bzero((caddr_t)&ro, sizeof (ro)); ro.ro_dst = *(struct sockaddr *)ip_dst; rtalloc(&ro); - if (ro.ro_rt == 0 || ro.ro_rt->rt_ifp == 0) { + if (ro.ro_rt == 0 || ro.ro_rt->rt_ifa->ifa_ifp == 0) { return (ENETUNREACH); } @@ -340,7 +340,7 @@ */ { register struct in_ifaddr *ia; - struct ifnet *ifp = ro.ro_rt->rt_ifp; + struct ifnet *ifp = ro.ro_rt->rt_ifa->ifa_ifp; for (ia = in_ifaddr; ia; ia = ia->ia_next) if (ia->ia_ifp == ifp) Index: netns/ns_output.c =================================================================== RCS file: /cvs/freebsd/src/sys/netns/ns_output.c,v retrieving revision 1.4 diff -u -r1.4 ns_output.c --- 1.4 1996/10/17 18:42:06 +++ ns_output.c 1997/02/26 23:26:49 @@ -111,7 +111,8 @@ ro->ro_rt = NULL; rtalloc(ro); } - if (ro->ro_rt == 0 || (ifp = ro->ro_rt->rt_ifp) == 0) { + if (ro->ro_rt == 0 || ro->ro_rt->rt_ifa == 0 + || (ifp = ro->ro_rt->rt_ifa->ifa_ifp) == 0) { error = ENETUNREACH; goto bad; } Index: netns/ns_pcb.c =================================================================== RCS file: /cvs/freebsd/src/sys/netns/ns_pcb.c,v retrieving revision 1.6 diff -u -r1.6 ns_pcb.c --- 1.6 1996/10/17 18:42:11 +++ ns_pcb.c 1997/02/26 23:26:49 @@ -167,7 +167,8 @@ nsp->nsp_lastdst = sns->sns_addr; if ((nsp->nsp_socket->so_options & SO_DONTROUTE) == 0 && /*XXX*/ (ro->ro_rt == (struct rtentry *)0 || - ro->ro_rt->rt_ifp == (struct ifnet *)0)) { + ro->ro_rt->rt_ifa == (struct ifaddr *)0 || + ro->ro_rt->rt_ifa->ifa_ifp == (struct ifnet *)0)) { /* No route yet, so try to acquire one */ ro->ro_dst.sa_family = AF_NS; ro->ro_dst.sa_len = sizeof(ro->ro_dst); @@ -186,7 +187,8 @@ * If we found a route, use the address * corresponding to the outgoing interface */ - if (ro->ro_rt && (ifp = ro->ro_rt->rt_ifp)) + if (ro->ro_rt && ro->ro_rt->rt_ifa && + (ifp = ro->ro_rt->rt_ifa->ifa_ifp)) for (ia = ns_ifaddr; ia; ia = ia->ia_next) if (ia->ia_ifp == ifp) break; --------------62319AC452BFA1D76201DD56-- From owner-freebsd-hackers Wed Feb 26 16:21:56 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id QAA14244 for hackers-outgoing; Wed, 26 Feb 1997 16:21:56 -0800 (PST) Received: from dg-rtp.dg.com (dg-rtp.rtp.dg.com [128.222.1.2]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id QAA14229 for ; Wed, 26 Feb 1997 16:21:53 -0800 (PST) Received: by dg-rtp.dg.com (5.4R3.10/dg-rtp-v02) id AA17049; Wed, 26 Feb 1997 19:20:03 -0500 Received: from ponds by dg-rtp.dg.com.rtp.dg.com; Wed, 26 Feb 1997 19:20 EST Received: from lakes.water.net (lakes [10.0.0.3]) by ponds.water.net (8.8.3/8.7.3) with ESMTP id SAA02479; Wed, 26 Feb 1997 18:50:34 -0500 (EST) Received: (from rivers@localhost) by lakes.water.net (8.8.3/8.6.9) id SAA21454; Wed, 26 Feb 1997 18:55:53 -0500 (EST) Date: Wed, 26 Feb 1997 18:55:53 -0500 (EST) From: Thomas David Rivers Message-Id: <199702262355.SAA21454@lakes.water.net> To: ponds!clinet.fi!hsu, ponds!lakes.water.net!rivers Subject: Re: A wild idea on the "dup alloc" and "bad dir" panics... Cc: ponds!freebsd.org!freebsd-hackers Content-Type: text Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > We have mostly vga cards (most of them ISA, but I think this also happens > in PCI display adapter systems). I do not think any of the offending > machines has a hercules mono card. > > - Dave Rivers - > > -- > Heikki Suonsivu, T{ysikuu 10 C 83/02210 Espoo/FINLAND, hsu@clinet.fi Oh well - it was just a shot in the dark... - Dave Rivers - From owner-freebsd-hackers Wed Feb 26 16:41:52 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id QAA15979 for hackers-outgoing; Wed, 26 Feb 1997 16:41:52 -0800 (PST) Received: from tulpi.interconnect.com.au (root@tulpi.interconnect.com.au [192.189.54.18]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id QAA15973 for ; Wed, 26 Feb 1997 16:41:48 -0800 (PST) Received: from dcallan.interconnect.com.au (acc2-ppp40.bri.interconnect.com.au [210.8.4.40]) by tulpi.interconnect.com.au with SMTP id LAA17029 (8.7.6/IDA-1.6 for ); Thu, 27 Feb 1997 11:41:42 +1100 (EST) Message-Id: <1.5.4.32.19970226234505.0070a054@192.168.0.1> X-Sender: dcallan#mail.interconnect.com.au@192.168.0.1 X-Mailer: Windows Eudora Light Version 1.5.4 (32) Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Thu, 27 Feb 1997 10:45:05 +1100 To: freebsd-hackers@FreeBSD.ORG From: Daniel Callan Subject: Re: can you teach me to hack Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk At 16:09 26/02/97 -0700, you wrote: >hey, I am interested in learning how to hack. I was ondering if you could >tech me how this is done. THANK YOU > Eagle > Let me guess, did someone just hire the *ULTRA-REALISTIC*, "hack-on-a-Mac" Hollywood "Hackers" video??? Go back to playing Duke Nukem! :-} From owner-freebsd-hackers Wed Feb 26 16:51:06 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id QAA16820 for hackers-outgoing; Wed, 26 Feb 1997 16:51:06 -0800 (PST) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id QAA16813 for ; Wed, 26 Feb 1997 16:51:01 -0800 (PST) Received: from current1.whistle.com (current1.whistle.com [207.76.205.22]) by alpo.whistle.com (8.8.5/8.8.4) with SMTP id QAA22945; Wed, 26 Feb 1997 16:40:27 -0800 (PST) Message-ID: <3314D778.13728473@whistle.com> Date: Wed, 26 Feb 1997 16:38:16 -0800 From: Julian Elischer Organization: Whistle Communications X-Mailer: Mozilla 3.0Gold (X11; I; FreeBSD 2.2-CURRENT i386) MIME-Version: 1.0 To: Shane Rohof CC: hackers@freebsd.org Subject: Re: can you teach me to hack References: <199702262308.QAA17332@huey.cadvision.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Shane Rohof wrote: > > hey, I am interested in learning how to hack. I was ondering if you could > tech me how this is done. THANK YOU > Eagle Use the source luke, but keep away from the dark side! 1/ Hackers is an old computer term meaning "master of the field" 2/'Hackers' in the media are "the master's apprentice" who goes wild with knowing a little and not understanding a lot.. THIS hackers mailing list is a mailng list for type (1) in other words here hang out those who create and understand the freeBSD system. We don't want to "HACK" in the media sense. HOWEVER most of group (2) are definitly welcome to try doing constructive work (1) From owner-freebsd-hackers Wed Feb 26 17:09:33 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id RAA17878 for hackers-outgoing; Wed, 26 Feb 1997 17:09:33 -0800 (PST) Received: from mail2.pilot.net (mail2.pilot.net [198.232.147.11]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id RAA17870 for ; Wed, 26 Feb 1997 17:09:28 -0800 (PST) Received: from u2.pilot.net (unknown-17-117.pilot.net [204.48.17.117]) by mail2.pilot.net with ESMTP id RAA15713; Wed, 26 Feb 1997 17:08:32 -0800 (PST) Received: from dc3.pilot.net (dc3.pilot.net [204.48.17.11]) by u2.pilot.net (8.8.5/) with ESMTP id RAA08869; Wed, 26 Feb 1997 17:08:20 -0800 (PST) Received: from localhost (wadlow@localhost) by dc3.pilot.net (8.7.3/8.7.3) with SMTP id RAA05299; Wed, 26 Feb 1997 17:08:36 -0800 (PST) X-Authentication-Warning: dc3.pilot.net: wadlow owned process doing -bs Date: Wed, 26 Feb 1997 17:08:35 -0800 (PST) From: Tom Wadlow Reply-To: Tom Wadlow To: Nate Williams cc: hackers@freebsd.org Subject: Re: Ethernet options on 2.2-GAMMA In-Reply-To: <199702250500.WAA20167@rocky.mt.sri.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > The other possibility is that the card is a 3C589D, which appears to be > different enough so it's not supported with the zp0 driver. Yup, that's it. A 3C589D. Bummer. I've tried the PAO package, and that helped somewhat. I'm able to install with a Megahertz card from another Laptop, (which wasn't documented in www.freebsd.org, which is why I bought the 3C589, which was) but still can't get my 3C589D to work. That at least gets me to the point where I can play with the cards and see what can be done. I'll let you know how it comes out. While I'm here, some comments on the install process, FWIW: - Generally quite good. Once you get a net connection the overall install is quite painless. - Since the installation package asks for the name of your machine, it should at least offer to put it in /etc/sysconfig rather than assuming you'll figure it out later. - Using sysinstall to install packages: * The index of packages doesn't seem related to the packages that are installable. Under 2.2-GAMMA you get a nice big long list, but many of them aren't installable. If you set your release to 2.1.7-RELEASE you get a very similar (but not identical) list that is installable. * When a package is not installable, the sysinstall tool sometimes likes to hang forever. * When it is installing a big package, it sometimes appears to hang, but is just slow. A "heartbeat" or completion bargraph would be nice here too. * It'd be nice if you could ask a package "What are you dependent on?" rather than having to install it just to see. --Tom From owner-freebsd-hackers Wed Feb 26 17:39:56 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id RAA19903 for hackers-outgoing; Wed, 26 Feb 1997 17:39:56 -0800 (PST) Received: from who.cdrom.com (who.cdrom.com [204.216.27.3]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id RAA19895 for ; Wed, 26 Feb 1997 17:39:54 -0800 (PST) Received: from guacari.udem.edu.co ([200.25.37.5]) by who.cdrom.com (8.7.5/8.6.11) with ESMTP id RAA15304 for ; Wed, 26 Feb 1997 17:39:40 -0800 (PST) Received: (from root@localhost) by guacari.udem.edu.co (8.7.5/8.7.3) id UAA00730 for hackers@freebsd.org; Wed, 26 Feb 1997 20:36:46 -0500 (EST) Date: Wed, 26 Feb 1997 20:36:46 -0500 (EST) From: Lucas Adri n G¢mez Bland¢n Message-Id: <199702270136.UAA00730@guacari.udem.edu.co> To: hackers@freebsd.org Subject: How i can log with uid 0 out of console??? Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Dear Sir. I need log in a FreeBSD 2.2-960801-SNAP out of console, i need run a program with uid 0 but, when I log in the server appear "Connection refused on this terminal". Please, sendme your comments, thanks for all!!!!!! bye!!!! =-) root@guacari.udem.edu.co From owner-freebsd-hackers Wed Feb 26 17:48:20 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id RAA20516 for hackers-outgoing; Wed, 26 Feb 1997 17:48:20 -0800 (PST) Received: from micron.efn.org (resnet.uoregon.edu [128.223.170.28]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id RAA20502 for ; Wed, 26 Feb 1997 17:48:04 -0800 (PST) Received: (from mini@localhost) by micron.efn.org (8.8.3/8.7.3) id RAA19649; Wed, 26 Feb 1997 17:39:29 -0800 (PST) Date: Wed, 26 Feb 1997 17:39:28 -0800 (PST) From: Jonathan Mini Reply-To: Jonathan Mini To: John-Mark Gurney cc: hackers@freebsd.org Subject: Re: can you teach me to hack In-Reply-To: <199702262308.QAA17332@huey.cadvision.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Wed, 26 Feb 1997, Shane Rohof wrote: This is tooo funy. Notice also how he used an alias, but his real name is in the header. =) > hey, I am interested in learning how to hack. I was ondering if you could > tech me how this is done. THANK YOU > Eagle > Jonathan Mini (j_mini@efn.org) ... bleakness ... desolation ... plastic forks ... From owner-freebsd-hackers Wed Feb 26 18:18:17 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id SAA22513 for hackers-outgoing; Wed, 26 Feb 1997 18:18:17 -0800 (PST) Received: from panda.hilink.com.au (panda.hilink.com.au [203.2.144.5]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id SAA22505 for ; Wed, 26 Feb 1997 18:18:10 -0800 (PST) Received: (from danny@localhost) by panda.hilink.com.au (8.8.5/8.7.3) id NAA17709; Thu, 27 Feb 1997 13:27:41 +1100 (EST) Date: Thu, 27 Feb 1997 13:27:39 +1100 (EST) From: "Daniel O'Callaghan" To: Lucas Adri n G¢mez Bland¢n cc: hackers@FreeBSD.ORG Subject: Re: How i can log with uid 0 out of console??? In-Reply-To: <199702270136.UAA00730@guacari.udem.edu.co> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from QUOTED-PRINTABLE to 8bit by freefall.freebsd.org id SAA22507 Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Wed, 26 Feb 1997, Lucas Adri n G¢mez Bland¢n wrote: > I need log in a FreeBSD 2.2-960801-SNAP out of console, i need run a program > with uid 0 but, when I log in the server appear "Connection refused on this terminal". If you *really* want to open your system to root logins on a network pty, edit /etc/ttys and add 'secure' keyword to lines for ttyp0 etc. Then save the file and 'kill -HUP 1' Danny From owner-freebsd-hackers Wed Feb 26 18:19:34 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id SAA22614 for hackers-outgoing; Wed, 26 Feb 1997 18:19:34 -0800 (PST) Received: from awfulhak.demon.co.uk (awfulhak.demon.co.uk [158.152.17.1]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id SAA22597; Wed, 26 Feb 1997 18:19:13 -0800 (PST) Received: from awfulhak.demon.co.uk (localhost.lan.awfulhak.org [127.0.0.1]) by awfulhak.demon.co.uk (8.8.5/8.8.5) with ESMTP id BAA04393; Thu, 27 Feb 1997 01:23:31 GMT Message-Id: <199702270123.BAA04393@awfulhak.demon.co.uk> X-Mailer: exmh version 1.6.9 8/22/96 To: hackers@freebsd.org cc: eivind@freebsd.org, bde@zeta.org.au, brian@utell.co.uk Subject: Include files (in ppp) Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 27 Feb 1997 01:23:31 +0000 From: Brian Somers Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Sorry to approach things like this, but I'm too green to argue. I think a vote would be more in order. In one corner, we have the argument that (iij)ppp has got so many #ifs #buts and #thens, that the additional osreldate.h dependency doesn't make things any worse. It has ifs for bsdi, NetBSD and even FreeBSD, not to mention _BSDI_VERSION and BSD... The advantage of the __FreeBSD_version inclusion is that the -current version compiles on 2.1.* In the other corner, we have the argument that as ppp is part of the system, it shouldn't have all this stuff in there. osreldate et. al. is for ports, not the system itself. I'd suggest one of the following: - Leave it as it is (with osreldate.h adding partially to the chaos) - Remove all of the #ifs buts and whys (rationalle: If osreldate isn't in there, All the #if BSD etc stuff is useless anyway) I'm going to (hide in) Munich for the weekend, I'll be back Tuesday and will go with whatever's decided. -- Brian , Don't _EVER_ lose your sense of humour.... From owner-freebsd-hackers Wed Feb 26 19:20:54 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id TAA28408 for hackers-outgoing; Wed, 26 Feb 1997 19:20:54 -0800 (PST) Received: from dg-rtp.dg.com (dg-rtp.rtp.dg.com [128.222.1.2]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id TAA28396 for ; Wed, 26 Feb 1997 19:20:50 -0800 (PST) Received: by dg-rtp.dg.com (5.4R3.10/dg-rtp-v02) id AA12920; Wed, 26 Feb 1997 22:20:03 -0500 Received: from ponds by dg-rtp.dg.com.rtp.dg.com; Wed, 26 Feb 1997 22:20 EST Received: from lakes.water.net (lakes [10.0.0.3]) by ponds.water.net (8.8.3/8.7.3) with ESMTP id UAA01051 for ; Wed, 26 Feb 1997 20:35:55 -0500 (EST) Received: (from root@localhost) by lakes.water.net (8.8.3/8.6.9) id UAA24345 for freebsd-hackers@freefall.cdrom.com; Wed, 26 Feb 1997 20:41:13 -0500 (EST) Date: Wed, 26 Feb 1997 20:41:13 -0500 (EST) From: Thomas David Rivers Message-Id: <199702270141.UAA24345@lakes.water.net> To: ponds!freefall.cdrom.com!freebsd-hackers Subject: disksort (bad dir/dup alloc research) Content-Type: text Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk While researching the dup alloc/bad dir problem; I thought perhaps disksort() was loosing something (which would explain why newfs thinks it's written 0's and no 0's appear on the disk.) I noticed that in 2.0, disksort() works (mostly) on cylinder values, but in 2.0.5 and later this was rewritten to simply use the pblkno [physical block number] field. Just glancing through disksort(), I didn't see anything that would have caused a I/O to "go missing" - but I plan on adding some printf's just to make sure... [The reason for this is, I believe, my research indicates that, sometimes, I/O does seem to "go missing."] - Dave Rivers - From owner-freebsd-hackers Wed Feb 26 19:33:46 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id TAA29220 for hackers-outgoing; Wed, 26 Feb 1997 19:33:46 -0800 (PST) Received: from who.cdrom.com (who.cdrom.com [204.216.27.3]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id TAA29205 for ; Wed, 26 Feb 1997 19:33:42 -0800 (PST) Received: from cs.utah.edu (cs.utah.edu [128.110.4.21]) by who.cdrom.com (8.7.5/8.6.11) with ESMTP id SAA15491 for ; Wed, 26 Feb 1997 18:58:28 -0800 (PST) Received: from bottles.cs.utah.edu by cs.utah.edu (8.8.4/utah-2.21-cs) id TAA09669; Wed, 26 Feb 1997 19:58:19 -0700 (MST) Received: by bottles.cs.utah.edu (8.6.10/utah-2.15-leaf) id TAA00540; Wed, 26 Feb 1997 19:58:13 -0700 From: sclawson@bottles.cs.utah.edu (steve clawson) Message-Id: <199702270258.TAA00540@bottles.cs.utah.edu> Subject: Re: Re(2): Building PAO kernel on non-PAO system To: Andrew.Gordon@net-tel.co.uk Date: Wed, 26 Feb 1997 19:58:13 -0700 (MST) Cc: SimsS@ibm.net, Hackers@FreeBSD.ORG In-Reply-To: <"2818-970226224035-BC18*/G=Andrew/S=Gordon/O=NET-TEL Computer from "Andrew.Gordon@net-tel.co.uk" at Feb 26, 97 10:38:52 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Andrew.Gordon@net-tel.co.uk uttered: > The only minor snag I ran into was that 'make install' left > /usr/include/* as symlinks into the /usr/src, which needed to be > undone if I didn't want to leave the NFS mounts in place permanently. There's a configuration option for this. =) Uncomment the `SHARED= copies' line in /usr/src/include/Makefile, or (preferably), add it to /etc/make.conf on the machine that you're installing on. That way when you install your headers they will be copied instead of just symlinked. steve -- // stephen clawson sclawson@cs.utah.edu // university of utah From owner-freebsd-hackers Wed Feb 26 20:27:14 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id UAA01837 for hackers-outgoing; Wed, 26 Feb 1997 20:27:14 -0800 (PST) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id UAA01828; Wed, 26 Feb 1997 20:27:09 -0800 (PST) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.3/8.6.9) id PAA13463; Thu, 27 Feb 1997 15:21:55 +1100 Date: Thu, 27 Feb 1997 15:21:55 +1100 From: Bruce Evans Message-Id: <199702270421.PAA13463@godzilla.zeta.org.au> To: freebsd-hackers@freefall.freebsd.org, mpp@freefall.freebsd.org Subject: Re: sig*set macros in Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >Is there a good reason for having the sig*set macros defined >in and the equivalent functions in libc? Yes. ANSI requires function versions for almost all function-like interfaces, so that applications can use the function version if necessary (*). sig*set are POSIX functions, not ANSI. I'm not sure if POSIX has the same rule, but it's a good rule. (*) The function version is necessary for calls through a function pointer. For the few function-like interfaces that may have side effects on their args, the function version is necessary for avoiding side effects. >The macros >are only defined if _ANSI_SOURCE isn't. Neither are prototypes for the sig*set functions declared. This is because they aren't ANSI functions. >Plus it doesn't looks like >they are used that much anyways (about 2 dozen programs). This is because most programs in /usr/src that use signals assume BSD signal semantics, so they can get away with using signal() instead of sigaction(). Bruce From owner-freebsd-hackers Wed Feb 26 21:24:17 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id VAA04327 for hackers-outgoing; Wed, 26 Feb 1997 21:24:17 -0800 (PST) Received: from spyder.webstar5.com (root@spyder.webstar5.com [207.194.110.245]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id VAA04319 for ; Wed, 26 Feb 1997 21:24:13 -0800 (PST) Received: from earwig.webstar5.com (earwig.webstar5.com [207.194.110.1]) by spyder.webstar5.com (8.8.3/8.7.2) with SMTP id VAA16035 for ; Wed, 26 Feb 1997 21:21:24 -0800 (PST) Message-ID: <33151AC8.41C67EA6@webstar5.com> Date: Wed, 26 Feb 1997 21:25:28 -0800 From: Greg MacKay Organization: Webstar5 Internet Group X-Mailer: Mozilla 3.01Gold (X11; I; FreeBSD 2.1.7-RELEASE i386) MIME-Version: 1.0 To: freebsd-hackers@freebsd.org Subject: Problem with ld under gcc... Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I am trying to build s/w with gcc while linking to the Mini-SQL library (libmsql.a). All of my source compiles fine until the link stage. Then I get the following error: ld: symbol __GLOBAL_OFFSET_TABLE_ remains undefined I have checked all the dependencies in my makefile, and ensured that I put the "-lmsql" after everything that needs it. I end up with an executable which works fine until any calls are made to msql functions - then it dumps core. gdb indicates that any calls to msql functions generate seg faults... I also giving ld "-u _GLOBAL_OFFSET_TABLE_", but to no avail. As an aside, I took the code and compiled it on an SGI Indy (IRIX 5.3), and everything worked fine, with msql built on the SGI box. Anyone out there who has found a workaround for something like this.....? Greg Mackay greg@webstar5.com From owner-freebsd-hackers Wed Feb 26 21:50:45 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id VAA06835 for hackers-outgoing; Wed, 26 Feb 1997 21:50:45 -0800 (PST) Received: from dg-rtp.dg.com (dg-rtp.rtp.dg.com [128.222.1.2]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id VAA06815 for ; Wed, 26 Feb 1997 21:50:36 -0800 (PST) Received: by dg-rtp.dg.com (5.4R3.10/dg-rtp-v02) id AA26705; Thu, 27 Feb 1997 00:50:05 -0500 Received: from ponds by dg-rtp.dg.com.rtp.dg.com; Thu, 27 Feb 1997 00:50 EST Received: from lakes.water.net (lakes [10.0.0.3]) by ponds.water.net (8.8.3/8.7.3) with ESMTP id XAA04904 for ; Wed, 26 Feb 1997 23:30:37 -0500 (EST) Received: (from rivers@localhost) by lakes.water.net (8.8.3/8.6.9) id XAA29550 for freebsd-hackers@freefall.cdrom.com; Wed, 26 Feb 1997 23:35:55 -0500 (EST) Date: Wed, 26 Feb 1997 23:35:55 -0500 (EST) From: Thomas David Rivers Message-Id: <199702270435.XAA29550@lakes.water.net> To: ponds!freefall.cdrom.com!freebsd-hackers Subject: Perhaps an interesting point with the dup-alloc panics.. Content-Type: text Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Ok - This is 2.1.6.1 - no patches, except for a couple of printf()'s to see what's going on. One of the key items I've just discovered comes from the following printf() in ufs_disksubr.c. It's simply a printf() at the top of disksort() to indicate what block number is being added to the queue. *** ufs_disksubr.c.ori Mon Sep 18 02:15:15 1995 --- ufs_disksubr.c Wed Feb 26 22:21:51 1997 *************** *** 81,86 **** --- 81,88 ---- { register struct buf *bq; + printf("disksort: adding blkno %d to the queue\n", bp->b_pblkno); + /* If the queue is empty, then it's easy. */ if (ap->b_actf == NULL) { bp->b_actf = NULL; Now, when I run this, I expect to see something like (on the console): disksort: adding blkno 131904 to the queue disksort: adding blkno 131920 to the queue disksort: adding blkno 131936 to the queue disksort: adding blkno 131952 to the queue ... nice; simple lines - especially since disksort() should be splbio()'d. However, if we continue down, I'm seeing output like: disksort: adding blkno 131984 to the queue disksort: adding blkno 132000 to thedisksort: adding blkno 197712 to the queue disksort: adding blkno 197728 to the queue - now, the second line there isn't a typo - the printf() didn't finish before another disksort() printf started. Doesn't this imply that disksort was re-entered? With potentially terrible results to the buf-queues? Or, is there some other explanation for the strange output? Such a re-entrancy/buf-list problem would readily explain this. And, could simply be a missing splbio() before calling disksort()... [although, I scanned wd.c and didn't see it.] Again, I'm working with unaltered, except that previous diff; 2.1.6.1. Finally, I notice that if I put the newfs in a loop (so it presumably isn't read from anywhere and is in memory) I don't get this scenario. That could simply mean that disksort() was called to sort a different queue (in this case, the file system on the floppy.)... I'll have to check on that. - Dave Rivers - From owner-freebsd-hackers Wed Feb 26 22:51:51 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id WAA08668 for hackers-outgoing; Wed, 26 Feb 1997 22:51:51 -0800 (PST) Received: from obiwan.aceonline.com.au (obiwan.aceonline.com.au [203.103.90.67]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id WAA08569; Wed, 26 Feb 1997 22:48:07 -0800 (PST) Received: from localhost (adrian@localhost) by obiwan.aceonline.com.au (8.8.5/8.8.5) with SMTP id BAA07028; Thu, 11 Jan 1996 01:18:19 +0800 (WST) Date: Thu, 11 Jan 1996 01:18:18 +0800 (WST) From: Adrian Chadd To: Joerg Wunsch cc: Adrian Chadd , Marc Slemko , hackers@FreeBSD.ORG, auditors@FreeBSD.ORG Subject: Re: disallow setuid root shells? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > . make it configurable via sysctl, > . don't turn it on by default. > Yep, and yep. > I presume you're gonna log it at auth.info, but i for sure don't wanna > see each suid program with the same notification as each login. In an > environment where you can basically trust your users, it's pointless > to log them, all you have to care is to not get breakins from outside. > > See here is the problem. External breakins are a worry, yes, but the thing is in some environments (eg shell access server at an ISP) most break attempts come from either "eleet" hacker/users who buy accounts, or hacked accounts. Most hackers see the best way is to get a shell account on the box first, THEN hack root via a wide range of exploits (from my experiance anyway). For the record, I'm mounting/usr/home, /tmp, /var/spool/mail (and anything else they have r/w access to) as non-executable, making internal exploits run on the local box nearly impossible to run (any ideas how you could overflow something in perl / *sh ? :) First I'll ahve a ply and see whats logged. Cya. Adrian Chadd From owner-freebsd-hackers Wed Feb 26 23:01:15 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id XAA09040 for hackers-outgoing; Wed, 26 Feb 1997 23:01:15 -0800 (PST) Received: from narcissus.ml.org (root@brosenga.Pitzer.edu [134.173.120.201]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id XAA09035 for ; Wed, 26 Feb 1997 23:01:12 -0800 (PST) Received: from localhost (ben@localhost) by narcissus.ml.org (8.7.5/8.7.3) with SMTP id WAA09842; Wed, 26 Feb 1997 22:59:49 -0800 (PST) Date: Wed, 26 Feb 1997 22:59:49 -0800 (PST) From: Snob Art Genre To: Lucas Adri n G¢mez Bland¢n cc: hackers@freebsd.org Subject: Re: How i can log with uid 0 out of console??? In-Reply-To: <199702270136.UAA00730@guacari.udem.edu.co> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from QUOTED-PRINTABLE to 8bit by freefall.freebsd.org id XAA09036 Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Wed, 26 Feb 1997, Lucas Adri n G¢mez Bland¢n wrote: > Dear Sir. > > I need log in a FreeBSD 2.2-960801-SNAP out of console, i need run a program > with uid 0 but, when I log in the server appear "Connection refused on this terminal". Don't log in as root, give yourself a user account in group wheel and use "su" to become root for only as long as you need to be. This is much safer. I could for instance tell someone my root password and unless they had access to one of five accounts on my system in group wheel, it wouldn't do them any good at all. > > Please, sendme your comments, thanks for all!!!!!! bye!!!! =-) > > > root@guacari.udem.edu.co > Ben "You have your mind on computers, it seems." From owner-freebsd-hackers Wed Feb 26 23:02:43 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id XAA09108 for hackers-outgoing; Wed, 26 Feb 1997 23:02:43 -0800 (PST) Received: from donald.iafrica.com (donald.iafrica.com [196.31.1.30]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id XAA09099 for ; Wed, 26 Feb 1997 23:02:39 -0800 (PST) Received: from donald.iafrica.com [127.0.0.1] by donald.iafrica.com with smtp (Exim 1.598 #1) id 0vzzrA-0006Id-00; Thu, 27 Feb 1997 09:02:21 +0200 Date: Thu, 27 Feb 1997 09:02:20 +0200 (SAT) From: Ryan Loots Reply-To: Ryan Loots To: Shane Rohof cc: hackers@freebsd.org Subject: Re: can you teach me to hack In-Reply-To: <199702262308.QAA17332@huey.cadvision.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi There > hey, I am interested in learning how to hack. I was ondering if you could > tech me how this is done. THANK YOU Try warez.phantom.com, this is an excellent site to practice on. --Ryan From owner-freebsd-hackers Wed Feb 26 23:03:01 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id XAA09150 for hackers-outgoing; Wed, 26 Feb 1997 23:03:01 -0800 (PST) Received: from mailmule1.mindspring.com (mailmule1.mindspring.com [204.180.128.192]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id XAA09145 for ; Wed, 26 Feb 1997 23:02:57 -0800 (PST) Received: from bogus.mindspring.com (borg.mindspring.com [204.180.128.14]) by mailmule1.mindspring.com (8.8.4/8.8.4) with SMTP id CAA15892; Thu, 27 Feb 1997 02:02:51 -0500 (EST) Message-Id: <1.5.4.32.19970227070248.0089c5f0@mindspring.com> X-Sender: kpneal@mindspring.com X-Mailer: Windows Eudora Light Version 1.5.4 (32) Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Thu, 27 Feb 1997 02:02:48 -0500 To: Thomas David Rivers From: "Kevin P. Neal" Subject: Re: More on bad dir panics Cc: freebsd-hackers@freebsd.org Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk At 09:48 PM 2/25/97 -0500, Thomas David Rivers wrote: > o) Running fsck once isn't enough to restore a file system to > a semi-usuable state; if you fsck it once, try again, > you'll sometimes notice more corrections. Don't some fscks repeat the check (or parts of it) if they find errors? Because it's not terribly uncommon (in my experience) for one fsck to not correct all the errors on a disk (on some of the Unixes I've used -- I've never fsck'd a FreeBSD box). Would looping until a clean check be a bad idea? With some timeout value, to prevent from fscking eternally? Say, 5-10 times then die? Would this be a useful addition? -- XCOMM Kevin P. Neal, Junior, Comp. Sci. - House of Retrocomputing XCOMM mailto:kpneal@pobox.com - http://www.pobox.com/~kpn/ XCOMM kpneal@eos.ncsu.edu " *** StarDOS makes great coffee! ***" XCOMM From a mid-80's advertisement in "Compute's GAZETTE", a C64/C128 mag From owner-freebsd-hackers Wed Feb 26 23:05:16 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id XAA09314 for hackers-outgoing; Wed, 26 Feb 1997 23:05:16 -0800 (PST) Received: from obiwan.aceonline.com.au (obiwan.aceonline.com.au [203.103.90.67]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id XAA09307; Wed, 26 Feb 1997 23:05:10 -0800 (PST) Received: from localhost (adrian@localhost) by obiwan.aceonline.com.au (8.8.5/8.8.5) with SMTP id BAA07064; Thu, 11 Jan 1996 01:36:12 +0800 (WST) Date: Thu, 11 Jan 1996 01:36:11 +0800 (WST) From: Adrian Chadd To: questions@freebsd.org cc: hackers@freebsd.org Subject: Java binary support in FreeBSD ... In-Reply-To: <3312D296.41C67EA6@earthlink.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I as just wondering if there was any plans to introduce java binary compatibility into the FreeBSD kernel. Not a java compiler / appletviewer in the KERNEL itself, but something like what LInux does, ie you echo the paths of the java executer and appletview into /proc/sys/kernel/java-interpreter and ../applet-viewer, and everytime a java binary is run, it runs the appropriate program with the right arguements, and there is your nice java binary running. :) Adrian Chadd From owner-freebsd-hackers Wed Feb 26 23:54:09 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id XAA11298 for hackers-outgoing; Wed, 26 Feb 1997 23:54:09 -0800 (PST) Received: (from mpp@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id XAA11288; Wed, 26 Feb 1997 23:54:03 -0800 (PST) From: Mike Pritchard Message-Id: <199702270754.XAA11288@freefall.freebsd.org> Subject: Re: sig*set macros in To: bde@zeta.org.au (Bruce Evans) Date: Wed, 26 Feb 1997 23:54:02 -0800 (PST) Cc: freebsd-hackers@freefall.freebsd.org In-Reply-To: <199702270421.PAA13463@godzilla.zeta.org.au> from "Bruce Evans" at Feb 27, 97 03:21:55 pm X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Bruce Evans wrote: > > >Is there a good reason for having the sig*set macros defined > >in and the equivalent functions in libc? > > Yes. ANSI requires function versions for almost all function-like > interfaces, so that applications can use the function version if > necessary (*). sig*set are POSIX functions, not ANSI. I'm not sure > if POSIX has the same rule, but it's a good rule. > > (*) The function version is necessary for calls through a function > pointer. For the few function-like interfaces that may have side > effects on their args, the function version is necessary for avoiding > side effects. > > >The macros > >are only defined if _ANSI_SOURCE isn't. > > Neither are prototypes for the sig*set functions declared. This is > because they aren't ANSI functions. > > >Plus it doesn't looks like > >they are used that much anyways (about 2 dozen programs). > > This is because most programs in /usr/src that use signals assume BSD > signal semantics, so they can get away with using signal() instead of > sigaction(). > > Bruce Let's try this again. Can we remove the macro definitions, and just rely on the functions? -- Mike Pritchard mpp@FreeBSD.org "Go that way. Really fast. If something gets in your way, turn" From owner-freebsd-hackers Thu Feb 27 01:16:14 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id BAA13925 for hackers-outgoing; Thu, 27 Feb 1997 01:16:14 -0800 (PST) Received: from alcatel.fr (ns.alcatel.fr [194.133.58.131]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id BAA13920 for ; Thu, 27 Feb 1997 01:16:10 -0800 (PST) Received: from alcatel.fr (gatekeeper-ssn.alcatel.fr [155.132.180.244]) by mailgate.alcatel.fr (8.8.5/8.8.5) with ESMTP id LAA03384; Thu, 27 Feb 1997 11:19:32 +0100 Received: from dnscit.cit.alcatel.fr (dnscit.cit.alcatel.fr [139.54.100.2]) by nsfhh5.alcatel.fr (8.7.3/8.7.3) with SMTP id KAA05690; Thu, 27 Feb 1997 10:14:07 +0100 (MET) Received: from dnsvz.vz.cit.alcatel.fr by dnscit.cit.alcatel.fr (SMI-8.6/SMI-SVR4) id KAA17130; Thu, 27 Feb 1997 10:12:34 +0100 Received: from bcv64s3e.vz.cit.alcatel.fr by dnsvz.vz.cit.alcatel.fr (SMI-8.6/SMI-SVR4) id JAA09109; Thu, 27 Feb 1997 09:51:50 +0100 Received: from bcv64wc1.velizy by bcv64s3e.vz.cit.alcatel.fr (SMI-8.6/SMI-SVR4) id KAA05010; Thu, 27 Feb 1997 10:04:14 +0100 From: luc.lewy@vz.cit.alcatel.fr (Luc.LEWY) Message-Id: <199702270904.KAA05010@bcv64s3e.vz.cit.alcatel.fr> Subject: Re: How i can log with uid 0 out of console??? To: danny@panda.hilink.com.au (Daniel O'Callaghan) Date: Thu, 27 Feb 1997 10:04:13 +0100 (MET) Cc: lgomez@guacari.udem.edu.co, hackers@FreeBSD.ORG In-Reply-To: from "Daniel O'Callaghan" at Feb 27, 97 01:27:39 pm MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Daniel O'Callaghan wrote: > If you *really* want to open your system to root logins on a network pty,= > =20 > edit /etc/ttys and add 'secure' keyword to lines for ttyp0 etc. > Then save the file and 'kill -HUP 1' mm.. Nope.. he shouldn't do this.. 'su' is the best way to keep as secure as possible his machine.. > Danny fifi... -- Guezou "fifi..." Philippe email: guezou_p@epita.fr pguezou@iway.fr luc.lewy@vz.cit.alcatel.fr *** M$-Windows is not a Virus - Viruses do something *** From owner-freebsd-hackers Thu Feb 27 01:24:53 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id BAA14321 for hackers-outgoing; Thu, 27 Feb 1997 01:24:53 -0800 (PST) Received: from shadows.aeon.net (bsdhack@shadows.aeon.net [194.100.41.1]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id BAA14301 for ; Thu, 27 Feb 1997 01:24:48 -0800 (PST) Received: (from bsdhack@localhost) by shadows.aeon.net (8.8.5/8.8.3) id LAA07796; Thu, 27 Feb 1997 11:23:10 +0200 (EET) From: mika ruohotie Message-Id: <199702270923.LAA07796@shadows.aeon.net> Subject: Re: Pentium MMX Extensions, Changes to (g)as and gdb In-Reply-To: <3314B85D.167EB0E7@ping.at> from "Helmut F. Wirth" at "Feb 26, 97 11:25:33 pm" To: hfwirth@ping.at (Helmut F. Wirth) Date: Thu, 27 Feb 1997 11:23:10 +0200 (EET) Cc: freebsd-hackers@freebsd.org X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > Hello, > I made some changes to gas and gdb to support the new MMX extensions > for the Pentium P55C. gee, cool. i didnt think we'd something about that this fast... what i'm interested in is, does the mmx cpu run normal freebsd any faster? the 'make world' is probably the only thing one could use for measuring it in the "reality" level... i would assume just coz of larger L1 cache it is already faster. any test results welcome. mickey From owner-freebsd-hackers Thu Feb 27 02:45:18 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id CAA17984 for hackers-outgoing; Thu, 27 Feb 1997 02:45:18 -0800 (PST) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id CAA17978; Thu, 27 Feb 1997 02:45:12 -0800 (PST) Received: from time.cdrom.com (jkh@localhost [127.0.0.1]) by time.cdrom.com (8.8.5/8.6.9) with ESMTP id CAA11119; Thu, 27 Feb 1997 02:44:59 -0800 (PST) To: Brian Somers cc: hackers@freebsd.org, eivind@freebsd.org, bde@zeta.org.au, brian@utell.co.uk Subject: Re: Include files (in ppp) In-reply-to: Your message of "Thu, 27 Feb 1997 01:23:31 GMT." <199702270123.BAA04393@awfulhak.demon.co.uk> Date: Thu, 27 Feb 1997 02:44:58 -0800 Message-ID: <11116.857040298@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > I'd suggest one of the following: > > - Leave it as it is (with osreldate.h adding partially to the chaos) > - Remove all of the #ifs buts and whys (rationalle: If osreldate isn't > in there, All the #if BSD etc stuff is useless anyway) > > I'm going to (hide in) Munich for the weekend, I'll be back Tuesday > and will go with whatever's decided. Well, since you're also the listed maintainer of ppp, don't be too shocked if the decision is to let Brian decide and not trouble us with too many of the details. :-) Jordan From owner-freebsd-hackers Thu Feb 27 02:50:44 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id CAA18232 for hackers-outgoing; Thu, 27 Feb 1997 02:50:44 -0800 (PST) Received: from zwei.siemens.at (zwei.siemens.at [193.81.246.12]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id CAA18226 for ; Thu, 27 Feb 1997 02:50:35 -0800 (PST) Received: from sol1.gud.siemens.co.at (root@[10.1.143.100]) by zwei.siemens.at (8.7.5/8.7.3) with SMTP id LAA06575 for ; Thu, 27 Feb 1997 11:51:56 +0100 (MET) Received: from ws2301.gud.siemens.co.at by sol1.gud.siemens.co.at with smtp (Smail3.1.28.1 #7 for ) id m0w03PI-0001zDC; Thu, 27 Feb 97 11:49 MET Received: by ws2301.gud.siemens.co.at (1.37.109.16/1.37) id AA155500347; Thu, 27 Feb 1997 11:45:47 +0100 From: "Hr.Ladavac" Message-Id: <199702271045.AA155500347@ws2301.gud.siemens.co.at> Subject: Re: can you teach me to hack To: rohofs@cadvision.com (Shane Rohof) Date: Thu, 27 Feb 1997 11:45:47 +0100 (MEZ) Cc: hackers@freebsd.org In-Reply-To: <199702262308.QAA17332@huey.cadvision.com> from "Shane Rohof" at Feb 26, 97 04:09:32 pm X-Mailer: ELM [version 2.4 PL24 ME8a] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk E-mail message from Shane Rohof contained: > hey, I am interested in learning how to hack. I was ondering if you could > tech me how this is done. THANK YOU > Eagle > Hack as hack or hack as crack? If you did not actually send this e-mail, then do not leave your terminal unattended while logged in. If you wish to hack the code, feel free, but you will have to learn some C to say the least. Sources are available in the source distribution which unpacks in /usr/src. If you wish to crack systems, it's easy: 1) You take a gun. Any gun will do; it doesn't have to be big. 2) You load it. Please do not use blanks. 3) You shoot yourself in the head, thus saving us some trouble in the future. Try not to miss. 4) Thanks for leaving us your address--it will make finding you later much easier. /Marino From owner-freebsd-hackers Thu Feb 27 03:18:17 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id DAA19551 for hackers-outgoing; Thu, 27 Feb 1997 03:18:17 -0800 (PST) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id DAA19544; Thu, 27 Feb 1997 03:18:10 -0800 (PST) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.3/8.6.9) id WAA28126; Thu, 27 Feb 1997 22:14:34 +1100 Date: Thu, 27 Feb 1997 22:14:34 +1100 From: Bruce Evans Message-Id: <199702271114.WAA28126@godzilla.zeta.org.au> To: bde@zeta.org.au, mpp@freefall.freebsd.org Subject: Re: sig*set macros in Cc: freebsd-hackers@freefall.freebsd.org Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >> >Is there a good reason for having the sig*set macros defined >> >in and the equivalent functions in libc? >> [Long answer.] >Let's try this again. >Can we remove the macro definitions, and just rely on the functions? Not so long answer: why do you want to? Some versions of Linux removed them because they are buggy, but the FreeBSD libc versions are equally buggy. Short answer: no. Bruce From owner-freebsd-hackers Thu Feb 27 03:58:48 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id DAA20926 for hackers-outgoing; Thu, 27 Feb 1997 03:58:48 -0800 (PST) Received: from helpdesk.euronet.nl (helpdesk.euronet.nl [194.134.1.147]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id DAA20919; Thu, 27 Feb 1997 03:58:45 -0800 (PST) Received: (from sake@localhost) by helpdesk.euronet.nl (8.8.4/8.6.12) id MAA20644; Thu, 27 Feb 1997 12:54:43 +0100 (MET) From: Sake Blok Message-Id: <199702271154.MAA20644@helpdesk.euronet.nl> Subject: Re: [H] Optimal computer for FreeBSD To: lada@ws2301.gud.siemens.co.at (Hr.Ladavac) Date: Thu, 27 Feb 1997 12:54:43 +0100 (MET) Cc: lada@ws2313.gud.siemens.co.at, terry@lambert.org, lada@ws2301.gud.siemens.co.at, vince@mail.MCESTATE.COM, michaelv@MindBender.serv.net, tom@sdf.com, sergey@extech.msk.su, freebsd-isp@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG Reply-To: sake@euronet.nl In-Reply-To: <199702261730.AA177658232@ws2301.gud.siemens.co.at> from "Hr.Ladavac" at Feb 26, 97 06:30:32 pm X-Mailer: ELM [version 2.4 PL24 ME8b] Content-Type: text Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk [...] > > > What a neat idea. Then if you want a larger L2, I can make you > > > buy a whole new processor. > > > > And charge you double: after all, you're getting twice as many > > transistors in the cache... > > My brain fart: you should consider it a bargain, since you're getting > at least *four* time as many transistors (the cache is static, idiot :) Boy, this brings back elementary school exercises... For dynamic Ram you need one transistor per bit so if you have X bits of Ram and you want to double that, you need 2 * X transistors. --> Result: Doubling Ram costs (2 * X) / X = 2 times as much transistors (and some more for the matrices but that amount is neglicable) For static Ram you need two transistors per bit so if you have X bits of Ram and you want to double that, you need 2 * (2 * X) transistors. --> Result: Doubling Ram costs (2 * (2 * X)) / (2 * X) = 2 times as much transistors. (and some more for the matrices but that amount is neglicable) :-) Sake -- +------------------- There is a purpose to time: --------------------+ | Sake Blok (sake@euronet.nl) EuroNet Internet BV | | http://www.euronet.nl/~sake Herengracht 208-214 | | phone: +31 (0)20 625 6161 1016 BS Amsterdam | | fax : +31 (0)20 625 7435 The Netherlands | +---------- It prevents everything from happening at once.-----------+ From owner-freebsd-hackers Thu Feb 27 04:24:10 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id EAA22031 for hackers-outgoing; Thu, 27 Feb 1997 04:24:10 -0800 (PST) Received: from maelstrom.cc.mcgill.ca (maelstrom.CC.McGill.CA [132.206.35.2]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id EAA22023 for ; Thu, 27 Feb 1997 04:24:06 -0800 (PST) Received: (from yves@localhost) by maelstrom.cc.mcgill.ca (8.8.5/8.8.5) id HAA28592 for freebsd-hackers@freebsd.org; Thu, 27 Feb 1997 07:24:03 -0500 (EST) Message-Id: <199702271224.HAA28592@maelstrom.cc.mcgill.ca> MIME-Version: 1.0 (NeXT Mail 3.3 v118.2) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Received: by NeXT.Mailer (1.118.2) From: Yves Lepage Date: Thu, 27 Feb 97 07:24:00 -0500 To: freebsd-hackers@freebsd.org Subject: Re: can you teach me to hack Reply-To: yves@CC.McGill.CA References: <1.5.4.32.19970226234505.0070a054@192.168.0.1> Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hmmm, Try the official hacking practice machine: langnese.nvg.unit.no Just telnet to it and login using your own username and password. Yves Lepage From owner-freebsd-hackers Thu Feb 27 04:41:18 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id EAA23178 for hackers-outgoing; Thu, 27 Feb 1997 04:41:18 -0800 (PST) Received: from vinyl.quickweb.com (vinyl.quickweb.com [206.222.77.8]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id EAA23170; Thu, 27 Feb 1997 04:41:15 -0800 (PST) Received: from localhost (mark@localhost) by vinyl.quickweb.com (8.7.5/8.6.12) with SMTP id HAA14828; Thu, 27 Feb 1997 07:41:53 -0500 (EST) Date: Thu, 27 Feb 1997 07:41:53 -0500 (EST) From: Mark Mayo To: Adrian Chadd cc: questions@freebsd.org, hackers@freebsd.org Subject: Re: Java binary support in FreeBSD ... In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Thu, 11 Jan 1996, Adrian Chadd wrote: > I as just wondering if there was any plans to introduce java binary > compatibility into the FreeBSD kernel. Not a java compiler / appletviewer > in the KERNEL itself, but something like what LInux does, ie you echo the > paths of the java executer and appletview into > /proc/sys/kernel/java-interpreter and ../applet-viewer, and everytime a > java binary is run, it runs the appropriate program with the right > arguements, and there is your nice java binary running. :) Why bother??? It's not so hard to type 'java Class'...... I like my users to be aware that they are running through an interpreter, and that there are command line options to the interpreter. BTW, there's no such thing as a 'java binary'. It's just a bytecode class file that has to be interpreted. > > Adrian Chadd > > ---------------------------------------------------------------------------- Mark Mayo mark@quickweb.com RingZero Comp. http://vinyl.quickweb.com/mark ---------------------------------------------------------------------------- Nature shows that with the growth of intelligence comes increased capacity for pain, and it is only with the highest degree of intelligence that suffering reaches its supreme point. -- Arthur Schopenhauer From owner-freebsd-hackers Thu Feb 27 04:57:16 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id EAA23818 for hackers-outgoing; Thu, 27 Feb 1997 04:57:16 -0800 (PST) Received: from narcissus.ml.org (root@brosenga.Pitzer.edu [134.173.120.201]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id EAA23813 for ; Thu, 27 Feb 1997 04:57:14 -0800 (PST) Received: from localhost (ben@localhost) by narcissus.ml.org (8.7.5/8.7.3) with SMTP id EAA11592; Thu, 27 Feb 1997 04:56:56 -0800 (PST) Date: Thu, 27 Feb 1997 04:56:56 -0800 (PST) From: Snob Art Genre To: Yves Lepage cc: freebsd-hackers@freebsd.org Subject: Re: can you teach me to hack In-Reply-To: <199702271224.HAA28592@maelstrom.cc.mcgill.ca> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Thu, 27 Feb 1997, Yves Lepage wrote: > Hmmm, > > Try the official hacking practice machine: > > langnese.nvg.unit.no > > Just telnet to it and login using your own username and password. Where does this odd alias come from? I've never seen it before. > Yves Lepage > Ben "You have your mind on computers, it seems." From owner-freebsd-hackers Thu Feb 27 05:01:53 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id FAA24075 for hackers-outgoing; Thu, 27 Feb 1997 05:01:53 -0800 (PST) Received: from anacreon.sol.net (anacreon.sol.net [206.55.64.116]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id EAA23699; Thu, 27 Feb 1997 04:55:36 -0800 (PST) Received: from solaria.sol.net (solaria.sol.net [206.55.65.75]) by anacreon.sol.net (8.8.5/8.6.12) with SMTP id GAA18291; Thu, 27 Feb 1997 06:55:06 -0600 (CST) Received: from localhost by solaria.sol.net (8.5/8.5) id GAA22830; Thu, 27 Feb 1997 06:55:04 -0600 From: Joe Greco Message-Id: <199702271255.GAA22830@solaria.sol.net> Subject: Re: disallow setuid root shells? To: adrian@obiwan.aceonline.com.au (Adrian Chadd) Date: Thu, 27 Feb 97 6:55:03 CST Cc: joerg_wunsch@uriah.heep.sax.de, adrian@cougar.aceonline.com.au, marcs@znep.com, hackers@FreeBSD.ORG, auditors@FreeBSD.ORG In-Reply-To: from "Adrian Chadd" at Jan 11, 96 01:18:18 am X-Mailer: ELM [version 2.4dev PL65] MIME-Version: 1.0 Content-Type: text Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > For the record, I'm mounting/usr/home, /tmp, /var/spool/mail (and anything > else they have r/w access to) as non-executable, making internal exploits > run on the local box nearly impossible to run (any ideas how you could > overflow something in perl / *sh ? :) This, incidentally, is a pretty good strategy. Filesystems where there shouldn't be executables should be mounted nodev,noexec,nosuid (/home should be at least mounted nodev,nosuid as it may be legit for users to have executables and shell scripts). Included, I think, should be all of /var - not just var/spool/mail. I don't (yet) do this myself, but am thinking of it as I have yet to see a reason not to do it. Maybe it could become "standard"...? Comments? ... Joe ------------------------------------------------------------------------------- Joe Greco - Systems Administrator jgreco@ns.sol.net Solaria Public Access UNIX - Milwaukee, WI 414/342-4847 From owner-freebsd-hackers Thu Feb 27 05:26:30 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id FAA25729 for hackers-outgoing; Thu, 27 Feb 1997 05:26:30 -0800 (PST) Received: from obiwan.aceonline.com.au (obiwan.aceonline.com.au [203.103.90.67]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id FAA25724 for ; Thu, 27 Feb 1997 05:26:26 -0800 (PST) Received: from localhost (adrian@localhost) by obiwan.aceonline.com.au (8.8.5/8.8.5) with SMTP id HAA07693; Thu, 11 Jan 1996 07:57:11 +0800 (WST) Date: Thu, 11 Jan 1996 07:57:11 +0800 (WST) From: Adrian Chadd To: Ryan Loots cc: Shane Rohof , hackers@freebsd.org Subject: Re: can you teach me to hack In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I think ftp.warez.org is another great place to grab those latest warez and leet stuff from. Adrian. On Thu, 27 Feb 1997, Ryan Loots wrote: > Hi There > > > hey, I am interested in learning how to hack. I was ondering if you could > > tech me how this is done. THANK YOU > > Try warez.phantom.com, this is an excellent site to practice on. > > --Ryan > > From owner-freebsd-hackers Thu Feb 27 05:29:05 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id FAA25919 for hackers-outgoing; Thu, 27 Feb 1997 05:29:05 -0800 (PST) Received: from nic.follonett.no (nic.follonett.no [194.198.43.10]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id FAA25885; Thu, 27 Feb 1997 05:28:28 -0800 (PST) Received: (from uucp@localhost) by nic.follonett.no (8.8.5/8.8.3) with UUCP id OAA03643; Thu, 27 Feb 1997 14:26:31 +0100 (MET) Received: from oo7 (oo7.dimaga.com [192.0.0.65]) by dimaga.com (8.8.5/8.7.2) with SMTP id OAA14618; Thu, 27 Feb 1997 14:29:02 +0100 (MET) Message-Id: <3.0.32.19970227142902.00bccd30@dimaga.com> X-Sender: eivind@dimaga.com X-Mailer: Windows Eudora Pro Version 3.0 (32) Date: Thu, 27 Feb 1997 14:29:03 +0100 To: Brian Somers From: Eivind Eklund Subject: Re: Include files (in ppp) Cc: hackers@freebsd.org, eivind@freebsd.org, bde@zeta.org.au, brian@utell.co.uk Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk At 01:23 AM 2/27/97 +0000, Brian Somers wrote: >I'd suggest one of the following: > >- Leave it as it is (with osreldate.h adding partially to the chaos) >- Remove all of the #ifs buts and whys (rationalle: If osreldate isn't > in there, All the #if BSD etc stuff is useless anyway) I'd say this depend on a few things: (A) How many patches to IIJ-PPP do we recieve? If there are a lot of these, removing #ifdefs might disrupt merging. (Doesn't look like it from the amount of commits, though.) (B) Is IIJ-PPP actively developed anywhere outside FreeBSD? See (A). (PPP+pktAlias doesn't count - I'll merge any changes from -current) (C) Is IIJ-PPP from FreeBSD actively used by non-FreeBSD people? In this case, we could pay them the courtesy of leaving it in. If none of these factors give us trouble, I'd say we cut the #ifdef's - they clutter the code. However, the final choice is in Brian's hands - as well as the responsibility for adding himself as maintainer in the Makefile ;-) Eivind Eklund perhaps@yes.no http://maybe.yes.no/perhaps/ eivind@freebsd.org From owner-freebsd-hackers Thu Feb 27 05:35:31 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id FAA26280 for hackers-outgoing; Thu, 27 Feb 1997 05:35:31 -0800 (PST) Received: from who.cdrom.com (who.cdrom.com [204.216.27.3]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id FAA26260; Thu, 27 Feb 1997 05:35:27 -0800 (PST) Received: from obiwan.aceonline.com.au (obiwan.aceonline.com.au [203.103.90.67]) by who.cdrom.com (8.7.5/8.6.11) with ESMTP id FAA17010 ; Thu, 27 Feb 1997 05:35:20 -0800 (PST) Received: from localhost (adrian@localhost) by obiwan.aceonline.com.au (8.8.5/8.8.5) with SMTP id IAA07708; Thu, 11 Jan 1996 08:04:58 +0800 (WST) Date: Thu, 11 Jan 1996 08:04:55 +0800 (WST) From: Adrian Chadd To: Mark Mayo cc: questions@freebsd.org, hackers@freebsd.org Subject: Re: Java binary support in FreeBSD ... In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > Why bother??? It's not so hard to type 'java Class'...... > I like my users to be aware that they are running through an interpreter, > and that there are command line options to the interpreter. > Well some of my users like being able to run java "binaries" without invoking the interpreter on the command line, later on if (when?) say DOS and Win16/32 binaries are supported, I think it would look better if you could just type "progname" and it ran it. > BTW, there's no such thing as a 'java binary'. It's just a bytecode class > file that has to be interpreted. > Aside from the fact that I remember a java-processor out there that runs native java bytecode, you're right. Remember - users don't want to know half the time how things work. They just want it to. :) If a user sees in a blurb that FreeBSD supports executing java "binaries" when you add the jdk package/port, they'll say "wow!". Just another crazy idea. Adrian. From owner-freebsd-hackers Thu Feb 27 05:36:58 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id FAA26424 for hackers-outgoing; Thu, 27 Feb 1997 05:36:58 -0800 (PST) Received: from nic.follonett.no (nic.follonett.no [194.198.43.10]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id FAA26418 for ; Thu, 27 Feb 1997 05:36:53 -0800 (PST) Received: (from uucp@localhost) by nic.follonett.no (8.8.5/8.8.3) with UUCP id OAA03763; Thu, 27 Feb 1997 14:35:03 +0100 (MET) Received: from oo7 (oo7.dimaga.com [192.0.0.65]) by dimaga.com (8.8.5/8.7.2) with SMTP id OAA14729; Thu, 27 Feb 1997 14:36:36 +0100 (MET) Message-Id: <3.0.32.19970227143636.00aede00@dimaga.com> X-Sender: eivind@dimaga.com X-Mailer: Windows Eudora Pro Version 3.0 (32) Date: Thu, 27 Feb 1997 14:36:37 +0100 To: Snob Art Genre From: Eivind Eklund Subject: Re: can you teach me to hack Cc: freebsd-hackers@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk At 04:56 AM 2/27/97 -0800, Snob Art Genre wrote: >On Thu, 27 Feb 1997, Yves Lepage wrote: > >> Hmmm, >> >> Try the official hacking practice machine: >> >> langnese.nvg.unit.no >> >> Just telnet to it and login using your own username and password. > >Where does this odd alias come from? I've never seen it before. langnese = long nose - a norwegian metaphor for "you've been had" is "you've been left with a long nose". The origin is an old folk myth, probably the originally the same as Pinoccio. nvg.unit.no is the networking group (a students association) at the university of Trondheim, Norway. Please direct any followups to freebsd-chat. Eivind Eklund perhaps@yes.no http://maybe.yes.no/perhaps/ eivind@freebsd.org From owner-freebsd-hackers Thu Feb 27 05:58:17 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id FAA27518 for hackers-outgoing; Thu, 27 Feb 1997 05:58:17 -0800 (PST) Received: from verdi.nethelp.no (verdi.nethelp.no [193.91.212.2]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id FAA27499 for ; Thu, 27 Feb 1997 05:57:54 -0800 (PST) From: sthaug@nethelp.no Received: (qmail 16336 invoked by uid 1001); 27 Feb 1997 13:56:56 +0000 (GMT) To: ben@narcissus.ml.org Cc: yves@CC.McGill.CA, freebsd-hackers@freebsd.org Subject: Re: can you teach me to hack In-Reply-To: Your message of "Thu, 27 Feb 1997 04:56:56 -0800 (PST)" References: X-Mailer: Mew version 1.05+ on Emacs 19.28.2 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Date: Thu, 27 Feb 1997 14:56:56 +0100 Message-ID: <16334.857051816@verdi.nethelp.no> Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > Try the official hacking practice machine: > > > > langnese.nvg.unit.no > > > > Just telnet to it and login using your own username and password. > > Where does this odd alias come from? I've never seen it before. "langnese" means "long nose" in Norwegian, ie. thumbing your nose at somebody. If you look up the IP address of the machine you'll see why. Steinar Haug, Nethelp consulting, sthaug@nethelp.no From owner-freebsd-hackers Thu Feb 27 06:44:24 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id GAA29719 for hackers-outgoing; Thu, 27 Feb 1997 06:44:24 -0800 (PST) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id GAA29712; Thu, 27 Feb 1997 06:44:21 -0800 (PST) Received: from time.cdrom.com (jkh@localhost [127.0.0.1]) by time.cdrom.com (8.8.5/8.6.9) with ESMTP id GAA13307; Thu, 27 Feb 1997 06:43:46 -0800 (PST) To: Adrian Chadd cc: Mark Mayo , questions@freebsd.org, hackers@freebsd.org Subject: Re: Java binary support in FreeBSD ... In-reply-to: Your message of "Thu, 11 Jan 1996 08:04:55 +0800." Date: Thu, 27 Feb 1997 06:43:45 -0800 Message-ID: <13303.857054625@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > Remember - users don't want to know half the time how things work. They > just want it to. :) If a user sees in a blurb that FreeBSD supports > executing java "binaries" when you add the jdk package/port, they'll say > "wow!". > > Just another crazy idea. Well, go do it and then come back with your proof-of-concept for us to comment on. Anything else is just blue-sky dreaming, and we've got more than enough of that to last us through the remainder of this century. :-) Jordan From owner-freebsd-hackers Thu Feb 27 07:28:16 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id HAA01775 for hackers-outgoing; Thu, 27 Feb 1997 07:28:16 -0800 (PST) Received: from thelab.hub.org (hal-ns1-43.netcom.ca [207.181.94.107]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id HAA01769; Thu, 27 Feb 1997 07:28:11 -0800 (PST) Received: from thelab.hub.org (LOCALHOST [127.0.0.1]) by thelab.hub.org (8.8.4/8.8.2) with SMTP id LAA09565; Thu, 27 Feb 1997 11:26:54 -0400 (AST) Date: Thu, 27 Feb 1997 11:26:54 -0400 (AST) From: The Hermit Hacker To: Adrian Chadd cc: Mark Mayo , questions@freebsd.org, hackers@freebsd.org Subject: Re: Java binary support in FreeBSD ... In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Thu, 11 Jan 1996, Adrian Chadd wrote: > > Why bother??? It's not so hard to type 'java Class'...... > > I like my users to be aware that they are running through an interpreter, > > and that there are command line options to the interpreter. > > > > Well some of my users like being able to run java "binaries" without > invoking the interpreter on the command line, later on if (when?) say DOS > and Win16/32 binaries are supported, I think it would look better if you > could just type "progname" and it ran it. > vi "progname" #!/bin/sh java Class From owner-freebsd-hackers Thu Feb 27 07:54:10 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id HAA03333 for hackers-outgoing; Thu, 27 Feb 1997 07:54:10 -0800 (PST) Received: from dyson.iquest.net (dyson.iquest.net [198.70.144.127]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id HAA03321; Thu, 27 Feb 1997 07:54:03 -0800 (PST) Received: (from root@localhost) by dyson.iquest.net (8.8.4/8.6.9) id KAA01146; Thu, 27 Feb 1997 10:53:20 -0500 (EST) From: "John S. Dyson" Message-Id: <199702271553.KAA01146@dyson.iquest.net> Subject: Re: Java binary support in FreeBSD ... To: jkh@time.cdrom.com (Jordan K. Hubbard) Date: Thu, 27 Feb 1997 10:53:20 -0500 (EST) Cc: adrian@obiwan.aceonline.com.au, mark@quickweb.com, questions@freebsd.org, hackers@freebsd.org In-Reply-To: <13303.857054625@time.cdrom.com> from "Jordan K. Hubbard" at Feb 27, 97 06:43:45 am 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-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > > Remember - users don't want to know half the time how things work. They > > just want it to. :) If a user sees in a blurb that FreeBSD supports > > executing java "binaries" when you add the jdk package/port, they'll say > > "wow!". > > > > Just another crazy idea. > > Well, go do it and then come back with your proof-of-concept for us to > comment on. Anything else is just blue-sky dreaming, and we've got > more than enough of that to last us through the remainder of this > century. :-) > Actually, writing the image activator for Java wouldn't be too hard, and could be an excellent first-kernel-project. I think that the normal kernel hackers are totally overloaded as Jordan says, so any volunteers? John From owner-freebsd-hackers Thu Feb 27 08:12:14 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id IAA04557 for hackers-outgoing; Thu, 27 Feb 1997 08:12:14 -0800 (PST) Received: from usr11.primenet.com (root@usr11.primenet.com [206.165.5.111]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id IAA04552 for ; Thu, 27 Feb 1997 08:12:10 -0800 (PST) Received: from primenet.com (root@mailhost01.primenet.com [206.165.5.52]) by usr11.primenet.com (8.8.5/8.8.5) with ESMTP id JAA11245; Thu, 27 Feb 1997 09:11:20 -0700 (MST) Received: from conceptual.com (consys.com [207.218.17.187]) by primenet.com (8.8.5/8.8.5) with ESMTP id JAA07965; Thu, 27 Feb 1997 09:11:15 -0700 (MST) Received: from conceptual.com (localhost [127.0.0.1]) by conceptual.com (8.8.5/8.6.9) with ESMTP id JAA15971; Thu, 27 Feb 1997 09:11:08 -0700 (MST) Message-Id: <199702271611.JAA15971@conceptual.com> X-Mailer: exmh version 2.0gamma 1/27/96 To: mika ruohotie cc: hfwirth@ping.at (Helmut F. Wirth), freebsd-hackers@freebsd.org Subject: Re: Pentium MMX Extensions, Changes to (g)as and gdb In-reply-to: Your message of "Thu, 27 Feb 1997 11:23:10 +0200." <199702270923.LAA07796@shadows.aeon.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 27 Feb 1997 09:11:08 -0700 From: "Russell L. Carter" Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > Hello, > > I made some changes to gas and gdb to support the new MMX extensions > > for the Pentium P55C. > > gee, cool. i didnt think we'd something about that this fast... > > what i'm interested in is, does the mmx cpu run normal freebsd any > faster? the 'make world' is probably the only thing one could use > for measuring it in the "reality" level... i would assume just coz of > larger L1 cache it is already faster. > The MMX instructions themselves will not affect the speed of anything resembling a "normal" code. Intel's P5 cpus with MMX run faster because they have a 2x bigger level1 cache and a few of the scheduling enhancements that first showed up in P6. Interestingly, the P6++ cpus with MMX (so-called Pentium II) run slower than P6 at the same clock rate because of the psuedo-on-chip level2 cache. It's conceivable that pd libraries could start showing up that use these instructions in specific assembly coded routines. I like the idea of putting the MMX instructions in though. Russell From owner-freebsd-hackers Thu Feb 27 08:35:32 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id IAA05627 for hackers-outgoing; Thu, 27 Feb 1997 08:35:32 -0800 (PST) Received: from lonewolf.hostworld.com ([207.79.98.1]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id IAA05578 for ; Thu, 27 Feb 1997 08:34:51 -0800 (PST) Message-Id: <199702271634.LAA08156@lonewolf.hostworld.com> X-Authentication-Warning: happy.webcreations.com: Host localhost.webcreations.com [127.0.0.1] didn't use HELO protocol To: hackers@freebsd.org From: Richard Hwang Reply-to: Richard Hwang Subject: [Q]: multiple lun probe not working on aic7880 Date: Thu, 27 Feb 1997 11:34:35 -0500 Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I am trying to get FreeBSD to probe for multiple luns on a aic7880 controller on a Dell PowerEdge 4100 server connected to a CMD Daytona RAIDarray (SCSI ID 0), but it only ever finds the 2G partition on lun 0, and can't find the 10G partition on lun1. FreeBSD seems to ignore the fact that lun 1 exists. When I boot the machine, the controller bios correctly reports the existance of lun 0 and lun 1. (I have multiple lun support turned on) I remapped the 10G partition as lun 0, and the 2G partition as lun 1, and it finds the 10G partition successfully but doesn't pick up the 2G partition. I compiled a kernel where I specifically stated that there was something on lun 1, but that didn't seem to help. I turned on SCSIDEBUG; here are the bootup messages: FreeBSD 2.1.7-RELEASE #0: Tue Feb 25 19:44:02 EST 1997 root@foo.bar.com:/usr/src/sys/compile/FOO CPU: 199-MHz unknown (Pentium-class CPU) Origin = "GenuineIntel" Id = 0x619 Stepping=9 Features=0xfbff,MTRR,PGE,MCA,CMOV> real memory = 134217728 (131072K bytes) avail memory = 127934464 (124936K bytes) eisa0: Probing for devices on the EISA bus Probing for devices on PCI bus 0: chip0 rev 2 on pci0:0 chip1 rev 1 on pci0:13 chip2 rev 21 on pci0:15:0 vga0 rev 64 on pci0:20 Probing for devices on PCI bus 1: ahc0 rev 0 int a irq 14 on pci1:10 ahc0: aic7880 Wide Channel, SCSI Id=7, 16 SCBs ahc0 waiting for scsi devices to settle (ahc0:0:0): "CMD TECH DAYTONA A4-2" type 0 fixed SCSI 2 sd0(ahc0:0:0): Direct-Access 1999MB (4095936 512 byte sectors) probe0(ahc0:9:0): scsi_cmd probe0(ahc0:9:0): ahc_scsi_cmd probe0(ahc0:9:0): ahc_done probe0(ahc0:9:0): scsi_done (ahc0:9:0): command: 0,0,0,0,0,0-[0 bytes] probe0(ahc0:9:0): scsi_cmd probe0(ahc0:9:0): ahc_scsi_cmd probe0(ahc0:9:0): ahc_done probe0(ahc0:9:0): scsi_done (ahc0:9:0): command: 12,0,0,0,2c,0-[44 bytes] ------------------------------ 000: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 016: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 032: 00 00 00 00 00 00 00 00 00 00 00 00 ------------------------------ ahc1 rev 1 int a irq 14 on pci1:11 ahc1: aic7860 Single Channel, SCSI Id=7, 3 SCBs ahc1 waiting for scsi devices to settle (ahc1:5:0): "NEC CD-ROM DRIVE:462 1.14" type 5 removable SCSI 2 cd0(ahc1:5:0): CD-ROM cd0(ahc1:5:0): NOT READY asc:3a,0 Medium not present can't get the size fxp0 rev 1 int a irq 15 on pci1:13 pci_map_mem failed: device's memrange 0xfbffe000-0xfbffefff is incompatible with its bridge's memrange 0xfde00000-0xfdffffff fxp0: Ethernet address 00:a0:c9:2e:5e:ab Probing for devices on the ISA bus: sc0 at 0x60-0x6f irq 1 on motherboard sc0: VGA color <16 virtual consoles, flags=0x0> sio0 at 0x3f8-0x3ff irq 4 on isa sio0: type 16550A sio1 at 0x2f8-0x2ff irq 3 on isa sio1: type 16550A sio2: disabled, not probed. sio3: disabled, not probed. lpt0 at 0x378-0x37f irq 7 on isa lpt0: Interrupt-driven port lp0: TCP/IP capable interface psm0 not found at 0x60 fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa fdc0: NEC 72065B fd0: 1.44MB 3.5in npx0 on motherboard npx0: INT 16 interface changing root device to sd0a Here is the kernel configuration file: machine "i386" #cpu "I386_CPU" #cpu "I486_CPU" cpu "I586_CPU" ident FOO maxusers 64 #options MATH_EMULATE #Support for x87 emulation 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 MAXMEM="131072" #we have more than 64M options SCSIDEBUG options USERCONFIG #boot -c editor options VISUAL_USERCONFIG #visual boot -c editor options SYSVSHM options SYSVSEM options SYSVMSG config kernel root on wd0 controller isa0 controller eisa0 controller pci0 controller fdc0 at isa? port "IO_FD1" bio irq 6 drq 2 vector fdintr disk fd0 at fdc0 drive 0 #disk fd1 at fdc0 drive 1 #tape ft0 at fdc0 drive 2 #controller wdc0 at isa? port "IO_WD1" bio irq 14 vector wdintr #disk wd0 at wdc0 drive 0 #disk wd1 at wdc0 drive 1 #controller wdc1 at isa? port "IO_WD2" bio irq 15 vector wdintr #disk wd2 at wdc1 drive 0 #disk wd3 at wdc1 drive 1 #options ATAPI #Enable ATAPI support for IDE bus #device wcd0 #IDE CD-ROM #controller ncr0 #controller ahb0 controller ahc0 controller ahc1 #controller bt0 at isa? port "IO_BT0" bio irq ? vector bt_isa_intr #controller uha0 at isa? port "IO_UHA0" bio irq ? drq 5 vector uhaintr #controller aha0 at isa? port "IO_AHA0" bio irq ? drq 5 vector ahaintr #controller aic0 at isa? port 0x340 bio irq 11 vector aicintr #controller nca0 at isa? port 0x1f88 bio irq 10 vector ncaintr #controller nca1 at isa? port 0x350 bio irq 5 vector ncaintr #controller sea0 at isa? bio irq 5 iomem 0xc8000 iosiz 0x2000 vector seaintr controller scbus0 at ahc0 controller scbus1 at ahc1 device sd0 device st0 device cd0 #Only need one of these, the code dynamically grows disk sd0 at scbus0 target 0 unit 0 disk sd1 at scbus0 target 0 unit 1 #device wt0 at isa? port 0x300 bio irq 5 drq 1 vector wtintr #device mcd0 at isa? port 0x300 bio irq 10 vector mcdintr #controller matcd0 at isa? port 0x230 bio #device scd0 at isa? port 0x230 bio # syscons is the default console driver, resembling an SCO console device sc0 at isa? port "IO_KBD" tty irq 1 vector scintr # Enable this and PCVT_FREEBSD for pcvt vt220 compatible console driver #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 # If you have a ThinkPAD, uncomment this along with the rest of the PCVT lines #options PCVT_SCANSET=2 # IBM keyboards are non-std # Mandatory, don't remove device npx0 at isa? port "IO_NPX" irq 13 vector npxintr # # Laptop support (see LINT for more options) # #device apm0 at isa? # Advanced Power Management #options APM_BROKEN_STATCLOCK # Workaround some buggy APM BIOS 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 sio2 at isa? disable port "IO_COM3" tty irq 5 vector siointr device sio3 at isa? disable port "IO_COM4" tty irq 9 vector siointr device lpt0 at isa? port? tty irq 7 vector lptintr #device lpt1 at isa? port? tty #device mse0 at isa? port 0x23c tty irq 5 vector mseintr device psm0 at isa? port "IO_KBD" conflicts tty irq 12 vector psmintr # Order is important here due to intrusive probes, do *not* alphabetize # this list of network interfaces until the probes have been fixed. # Right now it appears that the ie0 must be probed before ep0. See # revision 1.20 of this file. #device de0 device fxp0 #device vx0 #device ed0 at isa? port 0x280 net irq 5 iomem 0xd8000 vector edintr #device ed1 at isa? port 0x300 net irq 5 iomem 0xd8000 vector edintr #device ie0 at isa? port 0x360 net irq 7 iomem 0xd0000 vector ieintr #device ep0 at isa? port 0x300 net irq 10 vector epintr #device ix0 at isa? port 0x300 net irq 10 iomem 0xd0000 iosiz 32768 vector ixintr #device le0 at isa? port 0x300 net irq 5 iomem 0xd0000 vector le_intr #device lnc0 at isa? port 0x280 net irq 10 drq 0 vector lncintr #device ze0 at isa? port 0x300 net irq 5 iomem 0xd8000 vector zeintr #device zp0 at isa? port 0x300 net irq 10 iomem 0xd8000 vector zpintr pseudo-device loop pseudo-device ether pseudo-device log pseudo-device sl 1 # ijppp uses tun instead of ppp device #pseudo-device ppp 1 pseudo-device tun 1 pseudo-device pty 64 pseudo-device gzip # Exec gzipped a.out's --- Richard Hwang rhwang@bigpanda.com Big Panda House http://www.bigpanda.com From owner-freebsd-hackers Thu Feb 27 08:40:44 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id IAA05988 for hackers-outgoing; Thu, 27 Feb 1997 08:40:44 -0800 (PST) Received: from rocky.mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id IAA05950; Thu, 27 Feb 1997 08:40:26 -0800 (PST) Received: (from nate@localhost) by rocky.mt.sri.com (8.7.5/8.7.3) id JAA07016; Thu, 27 Feb 1997 09:39:37 -0700 (MST) Date: Thu, 27 Feb 1997 09:39:37 -0700 (MST) Message-Id: <199702271639.JAA07016@rocky.mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Adrian Chadd Cc: questions@freebsd.org, hackers@freebsd.org Subject: Re: Java binary support in FreeBSD ... In-Reply-To: References: <3312D296.41C67EA6@earthlink.net> Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > I as just wondering if there was any plans to introduce java binary > compatibility into the FreeBSD kernel. As someone who is heavily involved in Java right now, I think doing that is the *wrong* thing to do. First of all, JDK 1.1 is released, and until someone ports it to FreeBSD your binaries may not work correctly if they are compiled with the newer compiler. Second of all, it means that someone must really 'own' the JDK and support bugs in it, and I don't think we have anyone willing to do that (especially given that the group can't maintain it due to licensing restrictions). Next, how do you setup the CLASSPATH? You *must* assume the JDK lives in a specified directory, but the *entire* thing is in so much flux most of the time that you can't rely on this. The classes.zip file (effectively libc under unix) might not be found to have tons of bugs, and trying to keep -current with it and such as a user would be a nightmare, since it would require sticking things in the 'FreeBSD' expected locations vs. right now with the JDK being pretty much a stand-alone product. Finally, the legality of it could be in question. The folks at Blackdown.org who did the original Linux port question bundling the run-time with Linux, and having support w/out the runtime being bundled by default in the OS seems to be pretty bogus in my eyes. Sun is going to be providing a 'run-time' that everyone can use. When they do that (and if someone ports it to FreeBSD) we can possibly re-visit the issue, but I don't see the first two portions changing. Nate From owner-freebsd-hackers Thu Feb 27 09:13:31 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id JAA07345 for hackers-outgoing; Thu, 27 Feb 1997 09:13:31 -0800 (PST) Received: from ref.tfs.com (ref.tfs.com [206.245.251.1]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id JAA07339 for ; Thu, 27 Feb 1997 09:13:29 -0800 (PST) Received: (from julian@localhost) by ref.tfs.com (8.8.5/8.7.3) id JAA23356 for hackers@freebsd.org; Thu, 27 Feb 1997 09:13:04 -0800 (PST) Date: Thu, 27 Feb 1997 09:13:04 -0800 (PST) From: Julian Elischer Message-Id: <199702271713.JAA23356@ref.tfs.com> To: hackers@freebsd.org Subject: uptime Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk unfortunatly not actually FreeBSD, but a BSD43/MACH combination system (but running a lot of the same code) 10:36am up 500 days, 13:08, 2 users, load average: 0.20, 0.03, 0.02 From owner-freebsd-hackers Thu Feb 27 09:15:34 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id JAA07491 for hackers-outgoing; Thu, 27 Feb 1997 09:15:34 -0800 (PST) Received: from minnow.render.com (render.demon.co.uk [158.152.30.118]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id JAA07458; Thu, 27 Feb 1997 09:15:22 -0800 (PST) Received: (from dfr@localhost) by minnow.render.com (8.6.12/8.6.9) id RAA20263; Thu, 27 Feb 1997 17:09:37 GMT To: Adrian Chadd Cc: questions@freebsd.org, hackers@freebsd.org Subject: Re: Java binary support in FreeBSD ... References: From: Doug Rabson Date: 27 Feb 1997 17:09:34 +0000 In-Reply-To: Adrian Chadd's message of Thu, 11 Jan 1996 01:36:11 +0800 (WST) Message-ID: Lines: 18 X-Mailer: Gnus v5.2.25/XEmacs 19.14 Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Adrian Chadd writes: > > I as just wondering if there was any plans to introduce java binary > compatibility into the FreeBSD kernel. Not a java compiler / appletviewer > in the KERNEL itself, but something like what LInux does, ie you echo the > paths of the java executer and appletview into > /proc/sys/kernel/java-interpreter and ../applet-viewer, and everytime a > java binary is run, it runs the appropriate program with the right > arguements, and there is your nice java binary running. :) If this happens at all, it should probably use sysctl to give the interpreter names to the kernel. -- Doug Rabson, Microsoft RenderMorphics Ltd. Mail: dfr@render.com Phone: +44 171 734 3761 These are not the opinions of Microsoft. FAX: +44 171 734 6426 From owner-freebsd-hackers Thu Feb 27 09:18:42 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id JAA07692 for hackers-outgoing; Thu, 27 Feb 1997 09:18:42 -0800 (PST) Received: from cold.org (cold.org [206.81.134.103]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id JAA07687 for ; Thu, 27 Feb 1997 09:18:37 -0800 (PST) Received: from localhost (brandon@localhost) by cold.org (8.8.5/8.8.3) with SMTP id KAA05356 for ; Thu, 27 Feb 1997 10:18:50 -0700 (MST) Date: Thu, 27 Feb 1997 10:18:49 -0700 (MST) From: Brandon Gillespie To: freebsd-hackers@freebsd.org Subject: usermod/userdel/useradd groupmod/groupdel/groupadd Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I have these commands for FreeBSD, but they are written in perl5 (rather than perl4--for security and cleanliness). They all hook into a p5 library for handling the password file, group file and shells file. I would like to submit these, as well as an additional 'muser' which also uses the pwd.ph library (its a do-it-all add/del/modify users/groups and shells program); but since FreeBSD doesn't have p5 by default I don't know what to do. Frankly, I think it should have perl5 by default--not just as a package.. -Brandon Gillespie From owner-freebsd-hackers Thu Feb 27 09:22:20 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id JAA07907 for hackers-outgoing; Thu, 27 Feb 1997 09:22:20 -0800 (PST) Received: from paranoid.convey.ru (ws02.convey.ru [195.182.128.17]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id JAA07899 for ; Thu, 27 Feb 1997 09:22:10 -0800 (PST) Received: (from ark@localhost) by paranoid.convey.ru (8.7.5/8.7.3) id UAA02387; Thu, 27 Feb 1997 20:21:39 +0300 From: ArkanoiD Message-Id: <199702271721.UAA02387@paranoid.convey.ru> Subject: re: Fatal traps 12 == shitty motherboard | memory ??? To: rashid@idt.net Date: Thu, 27 Feb 1997 20:21:35 +0300 (MSK) Cc: hackers@freebsd.org X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 8bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk nuqneH, i've found your message while browsing mailing list archives - trying to find solution to the similar problem (triton hx + 2*dec21041 eth + aha2940 scuzzy).. so.. what did you do with that shi^H^H^Hthing? -- _ _ _ _ _ _ _ {::} {::} {::} CU in Hell _| o |_ | | _|| | / _||_| |_ |_ |_ (##) (##) (##) /Arkan#iD |_ o _||_| _||_| / _| | o |_||_||_| [||] [||] [||] Do i believe in Bible? Hell,man,i've seen one! From owner-freebsd-hackers Thu Feb 27 09:31:28 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id JAA08500 for hackers-outgoing; Thu, 27 Feb 1997 09:31:28 -0800 (PST) Received: from ns.extech.msk.su (ns.extech.msk.su [193.124.244.33]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id JAA08479; Thu, 27 Feb 1997 09:31:20 -0800 (PST) Received: from Shine.extech.msk.su (shine.extech.msk.su [193.124.244.35]) by ns.extech.msk.su (8.8.5/8.6.12) with ESMTP id UAA20701; Thu, 27 Feb 1997 20:33:30 +0300 (MSK) Message-Id: <199702271733.UAA20701@ns.extech.msk.su> From: "Vnotchenko S.S." To: , Subject: Re: Re: [H] Optimal computer for FreeBSD Date: Thu, 27 Feb 1997 20:33:28 +0300 X-MSMail-Priority: Normal X-Priority: 3 X-Mailer: Microsoft Internet Mail 4.70.1155 Sender: owner-hackers@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk Hi! Great thanks to everybody, who takes part in the discussion! I've made attempt to summarize answers and choosen following configuration for ours main host: --- CPU: PPRO 200Mhz, 256K cache MB: ASUSTEK P65UP5 RAM: 64 Mb EDO RAM SCSI HA: Adaptec 2940UW SCSI HDD: 4x2GB Seagate barracuda SCSI CD-ROM: 8x NEC SCSI Ethernet: 3c595 --- Best regards, Sergey (sergey@extech.msk.su). From owner-freebsd-hackers Thu Feb 27 09:41:26 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id JAA09271 for hackers-outgoing; Thu, 27 Feb 1997 09:41:26 -0800 (PST) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.50]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id JAA09266 for ; Thu, 27 Feb 1997 09:41:22 -0800 (PST) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id KAA00316; Thu, 27 Feb 1997 10:37:37 -0700 From: Terry Lambert Message-Id: <199702271737.KAA00316@phaeton.artisoft.com> Subject: Re: More on bad dir panics To: kpneal@pobox.com (Kevin P. Neal) Date: Thu, 27 Feb 1997 10:37:37 -0700 (MST) Cc: ponds!rivers@dg-rtp.dg.com, freebsd-hackers@freebsd.org In-Reply-To: <1.5.4.32.19970227070248.0089c5f0@mindspring.com> from "Kevin P. Neal" at Feb 27, 97 02:02:48 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-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > At 09:48 PM 2/25/97 -0500, Thomas David Rivers wrote: > > o) Running fsck once isn't enough to restore a file system to > > a semi-usuable state; if you fsck it once, try again, > > you'll sometimes notice more corrections. > > Don't some fscks repeat the check (or parts of it) if they find errors? > Because it's not terribly uncommon (in my experience) for one fsck to > not correct all the errors on a disk (on some of the Unixes I've used -- > I've never fsck'd a FreeBSD box). > > Would looping until a clean check be a bad idea? With some timeout value, > to prevent from fscking eternally? Say, 5-10 times then die? > > Would this be a useful addition? The current fsck used to have a problem where it incorrectly held the wrong reference count on the root directory if it had to create the lost+found directory. I fixed this problem. It may or may not have been reintroduced by the Lite2 integration. Running fsck once *is* enough to restore a file system to a semi-useful state. If you look at the output of the subsequent fcsk's, there is a possibility (rare) that there will be blocks in the allocation bitmap which aren't actually allocated. If these are directories, then it's possible that a reference to a file held in the directory will appear to be there. In general, there is a tiny case where this can happen, and the worst it does is make some blocks temporarily unusable. The case is because the directory name/inode pass doesn't occur before the blocks containing a directory entry are removed from the map. This will happen if the system crashes during a large delete operation during the process of truncating a directory back. While there are a lot of potential problems caused by truncating a directory back (the main one being that you can't preallocate an 8k lost+found directory because it will be truncated back, so there is the potential of needing to allocate a directory block for the entry for lost+found for inode 2, and none are available), these are all very rare fail-safe modes. The resulting FS following the fsck setting the clean bit *is* consistent, and therefore *is* safe to use. The one exception is when root goes over the hard allocation limit, which will push an allocation past the end of the FS. If you have another FS following the first, without a 1 cylinder buffer zone, then you can end up stomping the second FS. If your FS butts up to the end of the disk, you will get "block out of range" errors if you were smart enough to buy SCSI, or undefined errors (including possible cylinder wrap and corruption of the front of the disk) if you weren't. In general, this is not a problem because people don't run disk-gobblers as root except in special cases. The soloution to this problem is to employ logical-to-physical translation layers for enforcement of logical device boundries. In any case, as long as you don't set your reserve to 0, or habitually run as root, fsck should be able to recover any FS to usability in a single run, even if it doesn't recover all unallocated blocks for reuse (if you insist on fixing it, the place to start is pass 4). 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-hackers Thu Feb 27 09:50:17 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id JAA09718 for hackers-outgoing; Thu, 27 Feb 1997 09:50:17 -0800 (PST) Received: from snail.slow.net (lancelot@snail.slow.net [204.50.80.175]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id JAA09709 for ; Thu, 27 Feb 1997 09:50:12 -0800 (PST) Received: (from lancelot@localhost) by snail.slow.net (8.8.5/8.7.3) id MAA28984; Thu, 27 Feb 1997 12:49:41 -0500 (EST) Date: Thu, 27 Feb 1997 12:49:37 -0500 (EST) From: Sire Lancelot du Lac To: Ryan Loots cc: Shane Rohof , hackers@freebsd.org Subject: Re: can you teach me to hack In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Thu, 27 Feb 1997, Ryan Loots wrote: > Hi There > > > hey, I am interested in learning how to hack. I was ondering if you could > > tech me how this is done. THANK YOU > > Try warez.phantom.com, this is an excellent site to practice on. > > --Ryan > > May I suggest warez.slow.net and porn.slow.net as very good sites to practice on too :) -- Christian Doucet lancelot@slow.net work: +1 514 728 1618 Freelance "Sysadmin-Programmer-UNIX-Internet" guru! home: +1 514 728 1618 Y'a rien de plus troublant qu'un trou noir. -- Sol (Marc Favreau) This sentance has threee errors. -- trurl@yakko.nceye.net This sentence no verb. -- someone The answer to life, the universe and sendmail is 25 -- chimmy@knott12.ncl.ac.uk From owner-freebsd-hackers Thu Feb 27 10:31:53 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id KAA11872 for hackers-outgoing; Thu, 27 Feb 1997 10:31:53 -0800 (PST) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.50]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id KAA11866 for ; Thu, 27 Feb 1997 10:31:49 -0800 (PST) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id LAA00400; Thu, 27 Feb 1997 11:28:10 -0700 From: Terry Lambert Message-Id: <199702271828.LAA00400@phaeton.artisoft.com> Subject: Re: [Q]: multiple lun probe not working on aic7880 To: rhwang@bigpanda.com Date: Thu, 27 Feb 1997 11:28:09 -0700 (MST) Cc: hackers@freebsd.org In-Reply-To: <199702271634.LAA08156@lonewolf.hostworld.com> from "Richard Hwang" at Feb 27, 97 11:34:35 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-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > I am trying to get FreeBSD to probe for multiple luns on a aic7880 > controller on a Dell PowerEdge 4100 server connected to a CMD Daytona > RAIDarray (SCSI ID 0), but it only ever finds the 2G partition on lun 0, > and can't find the 10G partition on lun1. FreeBSD seems to ignore > the fact that lun 1 exists. Look at /sys/i386/conf/LINT: # Beginning with FreeBSD 2.0.5 you can wire down your SCSI devices so # that a given bus, target, and LUN always come on line as the same # device unit. In earlier versions the unit numbers were assigned # in the order that the devices were probed on the SCSI bus. This # means that if you removed a disk drive, you may have had to rewrite # your /etc/fstab file, and also that you had to be careful when adding # a new disk as it may have been probed earlier and moved your device # configuration around. Which suggests something like: disk sd0 at scbus0 target 0 unit 0 disk sd1 at scbus0 target 0 unit 1 Should work (and it's what you have). HOWEVER, you don't wire down the cdrom -- I think you have to: device cd0 at scbus? Also, you should look at the exception list in the SCSI driver for the LUN's: by default, multiple luns are not probed for most devices that may have CDROM's on them. It could be that the array is not identifying itself as a fixed disk? 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-hackers Thu Feb 27 11:29:52 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id LAA14581 for hackers-outgoing; Thu, 27 Feb 1997 11:29:52 -0800 (PST) Received: from smtp1.xs4all.nl (smtp1.xs4all.nl [194.109.6.51]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id LAA14570 for ; Thu, 27 Feb 1997 11:29:45 -0800 (PST) Received: from asterix.xs4all.nl (root@asterix.xs4all.nl [194.109.6.11]) by smtp1.xs4all.nl (8.7.6/XS4ALL) with ESMTP id UAA23409 for ; Thu, 27 Feb 1997 20:29:23 +0100 (MET) Received: from plm.xs4all.nl (uucp@localhost) by asterix.xs4all.nl (8.7.5/8.7.2) with UUCP id UAA01643 for freebsd-hackers@freebsd.org; Thu, 27 Feb 1997 20:23:49 +0100 (MET) Received: (from plm@localhost) by plm.xs4all.nl (8.8.4/8.7.3) id SAA11613; Thu, 27 Feb 1997 18:31:18 +0100 (MET) To: freebsd-hackers@freebsd.org Subject: Re: Java binary support in FreeBSD ... From: Peter Mutsaers Date: 27 Feb 1997 18:31:18 +0100 In-Reply-To: Mark Mayo's message of Thu, 27 Feb 1997 07:41:53 -0500 (EST) Message-ID: <87bu96gnq1.fsf@plm.xs4all.nl> Lines: 27 X-Mailer: Gnus v5.4.15/Emacs 19.34 Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >> On Thu, 27 Feb 1997 07:41:53 -0500 (EST), Mark Mayo >> said: >> in the KERNEL itself, but something like what LInux does, ie >> you echo the paths of the java executer and appletview into >> /proc/sys/kernel/java-interpreter and ../applet-viewer, and >> everytime a java binary is run, it runs the appropriate program >> with the right arguements, and there is your nice java binary >> running. :) MM> Why bother??? It's not so hard to type 'java Class'...... I MM> like my users to be aware that they are running through an MM> interpreter, and that there are command line options to the MM> interpreter. I don't think it is so strange. There are also shell scripts that are automatically executed by /bin/sh. It would be very nice either to type 'sh' in front of every shell script. Since it is impossible to put #!/usr/local/bin/java at the first line of a java "binary" (because it is a binary file) this addition would be quite neat. Especially when Java apps will become more common it is a must I think. -- Peter Mutsaers | Abcoude (Utrecht), | Trust is a good quality plm@xs4all.nl | the Netherlands | for other people to have From owner-freebsd-hackers Thu Feb 27 12:02:38 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id MAA15913 for hackers-outgoing; Thu, 27 Feb 1997 12:02:38 -0800 (PST) Received: from titan.cs.mci.com (titan.cs.mci.com [166.37.6.15]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id MAA15897 for ; Thu, 27 Feb 1997 12:02:20 -0800 (PST) Received: from localhost by titan.cs.mci.com; (5.65v3.2/1.1.8.2/22Aug96-0234PM) id AA01129; Thu, 27 Feb 1997 12:59:40 -0700 Date: Thu, 27 Feb 1997 12:59:39 -0700 (MST) From: "Thomas S. Traylor" To: Terry Lambert Cc: Shane Rohof , hackers@freebsd.org Subject: Re: can you teach me to hack In-Reply-To: <199702262341.QAA28992@phaeton.artisoft.com> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Wed, 26 Feb 1997, Terry Lambert wrote: > > hey, I am interested in learning how to hack. I was ondering if you could > > tech me how this is done. THANK YOU > > The best way to learn to "hack" is to buy yourself an axe, some good > wood, and watch "The New Yankee Workshop" on PBS. The axe is kinda low tech. What you really need is Norm's laser guided miter saw. Tom > > Terry Lambert > terry@lambert.org > --- > Any opinions in this posting are my own and not those of my present > or previous employers. > -- Thomas Traylor Thomas.Traylor@mci.com ttraylor@titan.cs.mci.com (719) 535-1269 From owner-freebsd-hackers Thu Feb 27 13:18:06 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id NAA19078 for hackers-outgoing; Thu, 27 Feb 1997 13:18:06 -0800 (PST) Received: from wall.olivetti.nl (inetgate.olsy.nl [193.67.10.65]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id NAA19067 for ; Thu, 27 Feb 1997 13:17:54 -0800 (PST) Received: (from nobody@localhost) by wall.olivetti.nl (8.6.12/8.6.9) id WAA03832 for ; Thu, 27 Feb 1997 22:17:47 +0100 Received: from oli1.olivetti.nl(192.87.20.30) by wall.olivetti.nl via smap (V1.3) id sma003826; Thu Feb 27 22:17:30 1997 Received: from olivaw.olivetti.nl by oli1.olivetti.nl with bsmtp (Smail3.1.28.1 #6) id m0w0DCk-000Qf6C; Thu, 27 Feb 97 22:17 MET Received: by olivaw.olivetti.nl (Smail3.1.28.1 #5) id m0w0D8k-000SG9C; Thu, 27 Feb 97 22:13 MET Message-Id: Content-Type: text/plain MIME-Version: 1.0 (NeXT Mail 3.3 v118.2) X-Nextstep-Mailer: Mail 3.3 (Enhance 1.3) Received: by NeXT.Mailer (1.118.2) From: Paul van der Zwan Date: Thu, 27 Feb 97 22:13:21 +0100 To: freebsd-hackers@freebsd.org Subject: 2.2 ctms Reply-To: paulzn@olivetti.nl Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk src-2.2.0187.gz appears to break dbm support. It replaces lib/libc/db/hash/ndbm.c by a 0 byte file. THis causes a make world to fail on perl. Paul PS I don't know if this list is the right one for the src-2.2 ctm's , if it isn't please let me know what is. --- Paul van der Zwan paulzn@olivetti.nl (NeXT/MIME OK) "I think I'll move to theory, everything works in theory..." From owner-freebsd-hackers Thu Feb 27 13:25:59 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id NAA19403 for hackers-outgoing; Thu, 27 Feb 1997 13:25:59 -0800 (PST) Received: from merix.merix.com (merix.merix.com [198.145.172.40]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id NAA19388 for ; Thu, 27 Feb 1997 13:25:54 -0800 (PST) Received: from sandy.merix.com by merix.merix.com with SMTP (1.38.110.45/16.2) id AA008319242; Thu, 27 Feb 1997 13:34:02 -0800 Received: by sandy.merix.com (4.1/8.0) id AA25781; Thu, 27 Feb 97 13:22:35 PST Date: Thu, 27 Feb 97 13:22:35 PST Subject: Re: Java binary support in FreeBSD ... To: freebsd-hackers@freebsd.org From: Troy Curtiss Message-Id: In-Reply-To: <87bu96gnq1.fsf@plm.xs4all.nl> Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Does the Java VM bytecode have a magic number at the beginning of the file? This would make it easy to detect (for the image activation stuff). Just use a sysctl variable to point to the java VM executable and/or appletviewer?? -- /-----------------------------------------------------------\ | Troy Curtiss, HW/SW Engineer | Email: troyc@merix.com | | Merix Corporation, CL-302 | Phone: (970) 203-6643 | | Loveland, CO 80537 | Fax : (970) 203-6610 | \-----------------------------------------------------------/ From owner-freebsd-hackers Thu Feb 27 13:49:51 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id NAA20458 for hackers-outgoing; Thu, 27 Feb 1997 13:49:51 -0800 (PST) Received: from hemi.com (hemi.com [204.132.158.10]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id NAA20453 for ; Thu, 27 Feb 1997 13:49:49 -0800 (PST) Received: (from mbarkah@localhost) by hemi.com (8.8.5/8.7.3) id OAA13852; Thu, 27 Feb 1997 14:49:32 -0700 (MST) From: Ade Barkah Message-Id: <199702272149.OAA13852@hemi.com> Subject: Re: uptime To: julian@ref.tfs.com (Julian Elischer) Date: Thu, 27 Feb 1997 14:49:32 -0700 (MST) Cc: hackers@freebsd.org In-Reply-To: <199702271713.JAA23356@ref.tfs.com> from Julian Elischer at "Feb 27, 97 09:13:04 am" X-Mailer: ELM [version 2.4ME+ PL22 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > unfortunatly not actually FreeBSD, but a BSD43/MACH combination system > (but running a lot of the same code) > > 10:36am up 500 days, 13:08, 2 users, load average: 0.20, 0.03, 0.02 Wow, 500 days... imagine how many security holes it has. =-) That's great, though. Regards, -Ade ------------------------------------------------------------------- Inet: mbarkah@hemi.com - HEMISPHERE ONLINE - ------------------------------------------------------------------- From owner-freebsd-hackers Thu Feb 27 15:13:00 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id PAA23476 for hackers-outgoing; Thu, 27 Feb 1997 15:13:00 -0800 (PST) Received: from csla.csl.sri.com (csla.csl.sri.com [192.12.33.2]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id PAA23471 for ; Thu, 27 Feb 1997 15:12:56 -0800 (PST) Received: from japonica.csl.sri.com (japonica.csl.sri.com [130.107.15.17]) by csla.csl.sri.com (8.7.3/8.7.3) with ESMTP id PAA23967 for ; Thu, 27 Feb 1997 15:09:32 -0800 (PST) Received: from japonica.csl.sri.com (localhost.csl.sri.com [127.0.0.1]) by japonica.csl.sri.com (8.8.5/8.8.5) with ESMTP id PAA06638 for ; Thu, 27 Feb 1997 15:08:55 -0800 (PST) Message-Id: <199702272308.PAA06638@japonica.csl.sri.com> To: hackers@freebsd.org Subject: Re: can you teach me to hack In-reply-to: Your message of "Wed, 26 Feb 1997 17:39:28 PST." Date: Thu, 27 Feb 1997 15:08:54 -0800 From: Fred Gilham Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Jonathan Mini wrote: ---------------------------------------- This is tooo funy. Notice also how he used an alias, but his real name is in the header. =) > hey, I am interested in learning how to hack. I was ondering if you could > tech me how this is done. THANK YOU > Eagle > ---------------------------------------- The giveaway is in the mail header of Eagle's message: > X-Mailer: Microsoft Internet Mail 4.70.1155 What do you expect? :-) -Fred Gilham gilham@csl.sri.com From owner-freebsd-hackers Thu Feb 27 15:26:06 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id PAA23929 for hackers-outgoing; Thu, 27 Feb 1997 15:26:06 -0800 (PST) Received: from noc.msc.edu (noc.msc.edu [137.66.12.254]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id PAA23922 for ; Thu, 27 Feb 1997 15:26:03 -0800 (PST) Received: from ww.msc.edu by noc.msc.edu (5.65/MSC/v3.0.1(920324)) id AA08194; Thu, 27 Feb 97 17:25:58 -0600 From: jpt@msc.edu (Joseph Thomas) Received: (jpt@localhost) by ww.msc.edu (8.7.1/8.6.6) id RAA01886 for hackers@freebsd.org; Thu, 27 Feb 1997 17:26:00 -0600 (CST) Message-Id: <199702272326.RAA01886@ww.msc.edu> Subject: Assumptions about kmem_malloc()... To: hackers@freebsd.org Date: Thu, 27 Feb 1997 17:25:59 -0600 (CST) X-Mailer: ELM [version 2.4 PL25] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk We are working on an ATM device driver and have the requirment of needing to allocate somewhat large memory chunks (more then one page in length) which are used for DMA. We've discovered the hard way (okay - maybe I should looked better) that adjacent virtual pages are not necessarily adjacent physically. Questions: o When using kmem_malloc(), do virtual and physical boundaries always align to a page start? Real experience seems to say that new allocs always align to a virtual and physical page boundaries but I may just be "getting lucky". o Other then contigmalloc(), is there a way to malloc contiguous physical memory greater then one page? The driver waits to malloc memory until microcode is downloaded to the NIC (Fore PCA200E). Since the download is user initiated, and because we'd like to move toward loadable modules, the prospect of having large amounts of contiguous memory is greatly dimished by the time we ask for it. o What other hidden gotchas are there in working with DMA and device drivers? Except for when I was asking for more then one page of memory (that is, I reduce structure sizes to be small enough to fit in one page) everything seems to be working great. However, there's a vast wealth of experience out there which I'd like to tap if I've missed something more suttle... Thanks. -- Joseph Thomas E/Mail: jpt@msc.edu Minnesota Supercomputer Center, Inc. jpt@magic.net 1200 Washington Ave So. Tel: +1 612 337 3558 Minneapolis, MN 55415-1227 FAX: +1 612 337 3400 An elephant is a mouse with an operating system. From owner-freebsd-hackers Thu Feb 27 16:56:17 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id QAA28554 for hackers-outgoing; Thu, 27 Feb 1997 16:56:17 -0800 (PST) Received: from parkplace.cet.co.jp (parkplace.cet.co.jp [202.32.64.1]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id QAA28416; Thu, 27 Feb 1997 16:53:39 -0800 (PST) Received: from localhost (michaelh@localhost) by parkplace.cet.co.jp (8.8.5/CET-v2.1) with SMTP id AAA07248; Fri, 28 Feb 1997 00:53:14 GMT Date: Fri, 28 Feb 1997 09:53:14 +0900 (JST) From: Michael Hancock To: Eivind Eklund cc: Brian Somers , hackers@freebsd.org, eivind@freebsd.org, bde@zeta.org.au, brian@utell.co.uk Subject: Re: Include files (in ppp) In-Reply-To: <3.0.32.19970227142902.00bccd30@dimaga.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk You might want to compare with what's on IIJ's server, ftp.iij.ad.jp. As I recall tony-o wrote IIJ-PPP and he is no longer at IIJ. I haven't been following it so I'm not sure how actively it's maintained. Regards, Mike On Thu, 27 Feb 1997, Eivind Eklund wrote: > At 01:23 AM 2/27/97 +0000, Brian Somers wrote: > >I'd suggest one of the following: > > > >- Leave it as it is (with osreldate.h adding partially to the chaos) > >- Remove all of the #ifs buts and whys (rationalle: If osreldate isn't > > in there, All the #if BSD etc stuff is useless anyway) > > I'd say this depend on a few things: > (A) How many patches to IIJ-PPP do we recieve? If there are a lot of > these, removing #ifdefs might disrupt merging. (Doesn't look like it from > the amount of commits, though.) > (B) Is IIJ-PPP actively developed anywhere outside FreeBSD? See (A). > (PPP+pktAlias doesn't count - I'll merge any changes from -current) > (C) Is IIJ-PPP from FreeBSD actively used by non-FreeBSD people? In this > case, we could pay them the courtesy of leaving it in. > > If none of these factors give us trouble, I'd say we cut the #ifdef's - > they clutter the code. However, the final choice is in Brian's hands - as > well as the responsibility for adding himself as maintainer in the Makefile > ;-) > > > Eivind Eklund perhaps@yes.no http://maybe.yes.no/perhaps/ eivind@freebsd.org > From owner-freebsd-hackers Thu Feb 27 17:17:59 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id RAA29394 for hackers-outgoing; Thu, 27 Feb 1997 17:17:59 -0800 (PST) Received: from sasami.jurai.net (winter@sasami.jurai.net [207.172.25.144]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id RAA29389 for ; Thu, 27 Feb 1997 17:17:55 -0800 (PST) Received: from localhost (winter@localhost) by sasami.jurai.net (8.8.5/8.8.3) with SMTP id UAA15239; Thu, 27 Feb 1997 20:18:40 -0500 (EST) Date: Thu, 27 Feb 1997 20:18:40 -0500 (EST) From: "Matthew N. Dodd" To: Ade Barkah cc: Julian Elischer , hackers@freebsd.org Subject: Re: uptime In-Reply-To: <199702272149.OAA13852@hemi.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Thu, 27 Feb 1997, Ade Barkah wrote: > > unfortunatly not actually FreeBSD, but a BSD43/MACH combination system > > (but running a lot of the same code) > > 10:36am up 500 days, 13:08, 2 users, load average: 0.20, 0.03, 0.02 > Wow, 500 days... imagine how many security holes it has. =-) > That's great, though. Someone I was talking to today told me of a VMS box that had 11 -years- of uptime. No kidding. /* Matthew N. Dodd | A memory retaining a love you had for life winter@jurai.net | As cruel as it seems nothing ever seems to http://www.jurai.net/~winter | go right - FLA M 3.1:53 */ From owner-freebsd-hackers Thu Feb 27 17:29:47 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id RAA29789 for hackers-outgoing; Thu, 27 Feb 1997 17:29:47 -0800 (PST) Received: from root.com (implode.root.com [198.145.90.17]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id RAA29782 for ; Thu, 27 Feb 1997 17:29:44 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by root.com (8.8.5/8.6.5) with SMTP id RAA05746; Thu, 27 Feb 1997 17:29:28 -0800 (PST) Message-Id: <199702280129.RAA05746@root.com> X-Authentication-Warning: implode.root.com: localhost [127.0.0.1] didn't use HELO protocol To: jpt@msc.edu (Joseph Thomas) cc: hackers@FreeBSD.ORG Subject: Re: Assumptions about kmem_malloc()... In-reply-to: Your message of "Thu, 27 Feb 1997 17:25:59 CST." <199702272326.RAA01886@ww.msc.edu> From: David Greenman Reply-To: dg@root.com Date: Thu, 27 Feb 1997 17:29:28 -0800 Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > o Other then contigmalloc(), is there a way to malloc contiguous >physical memory greater then one page? No; we created vm_page_alloc_contig/contigmalloc specifically for this purpose, and it's the only mechanism that exists to do this. > The driver waits to malloc memory until microcode is > downloaded to the NIC (Fore PCA200E). Since the download is > user initiated, and because we'd like to move toward loadable > modules, the prospect of having large amounts of contiguous > memory is greatly dimished by the time we ask for it. The memory allocated with contigmalloc can be released later via kmem_free(). > o What other hidden gotchas are there in working with DMA and >device drivers? Well, contiguous allocation is always the most common thing to get people. :-) The only other thing you should be aware of is that allocation of contiguous memory during normal system operation isn't guaranteed (in fact, will likely fail)...so you should allocate whatever you need contiguous during the device attach and olny release it later if you know you won't need it. -DG David Greenman Core-team/Principal Architect, The FreeBSD Project From owner-freebsd-hackers Thu Feb 27 17:32:13 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id RAA29955 for hackers-outgoing; Thu, 27 Feb 1997 17:32:13 -0800 (PST) Received: from obiwan.aceonline.com.au (obiwan.aceonline.com.au [203.103.90.67]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id RAA29950 for ; Thu, 27 Feb 1997 17:32:09 -0800 (PST) Received: from localhost (adrian@localhost) by obiwan.aceonline.com.au (8.8.5/8.8.5) with SMTP id UAA09933; Thu, 11 Jan 1996 20:03:13 +0800 (WST) Date: Thu, 11 Jan 1996 20:03:12 +0800 (WST) From: Adrian Chadd To: Troy Curtiss cc: freebsd-hackers@freebsd.org Subject: Re: Java binary support in FreeBSD ... In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Yep, the linux binfmt_java.c file does this to check: if ((ucp[0] != 0xca) || (ucp[1] != 0xfe) || (ucp[2] != 0xba) || (ucp[3] != 0xbe)) return -ENOEXEC; I'm looking at it now. Adrian. On Thu, 27 Feb 1997, Troy Curtiss wrote: > > Does the Java VM bytecode have a magic number at the beginning of > the file? This would make it easy to detect (for the image activation > stuff). Just use a sysctl variable to point to the java VM executable > and/or appletviewer?? > > -- > /-----------------------------------------------------------\ > | Troy Curtiss, HW/SW Engineer | Email: troyc@merix.com | > | Merix Corporation, CL-302 | Phone: (970) 203-6643 | > | Loveland, CO 80537 | Fax : (970) 203-6610 | > \-----------------------------------------------------------/ > From owner-freebsd-hackers Thu Feb 27 17:32:40 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id RAA00118 for hackers-outgoing; Thu, 27 Feb 1997 17:32:40 -0800 (PST) Received: from obiwan.aceonline.com.au (obiwan.aceonline.com.au [203.103.90.67]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id RAA00110 for ; Thu, 27 Feb 1997 17:32:36 -0800 (PST) Received: from localhost (adrian@localhost) by obiwan.aceonline.com.au (8.8.5/8.8.5) with SMTP id RAA09736; Thu, 11 Jan 1996 17:00:43 +0800 (WST) Date: Thu, 11 Jan 1996 17:00:43 +0800 (WST) From: Adrian Chadd To: Doug Rabson cc: hackers@freebsd.org Subject: Re: Java binary support in FreeBSD ... In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > I as just wondering if there was any plans to introduce java binary > > compatibility into the FreeBSD kernel. Not a java compiler / appletviewer > > in the KERNEL itself, but something like what LInux does, ie you echo the > > paths of the java executer and appletview into > > /proc/sys/kernel/java-interpreter and ../applet-viewer, and everytime a > > java binary is run, it runs the appropriate program with the right > > arguements, and there is your nice java binary running. :) > > If this happens at all, it should probably use sysctl to give the > interpreter names to the kernel. > Well yep, thats how things are done in FreeBSD vs. Linux. And to set stuff like CLASSPATH, just another sysctl call. Note we aren't incoporating the *INTERPRETER* into the kernel, just the support to RUN the interpreter whenever a java image is executed. Again, I'll look at the linux source for it tonight. Adrian From owner-freebsd-hackers Thu Feb 27 17:33:17 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id RAA00191 for hackers-outgoing; Thu, 27 Feb 1997 17:33:17 -0800 (PST) Received: (from mpp@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id RAA00137; Thu, 27 Feb 1997 17:32:42 -0800 (PST) From: Mike Pritchard Message-Id: <199702280132.RAA00137@freefall.freebsd.org> Subject: Re: sig*set macros in To: bde@zeta.org.au (Bruce Evans) Date: Thu, 27 Feb 1997 17:32:42 -0800 (PST) Cc: bde@zeta.org.au, freebsd-hackers@freefall.freebsd.org In-Reply-To: <199702271114.WAA28126@godzilla.zeta.org.au> from "Bruce Evans" at Feb 27, 97 10:14:34 pm X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Bruce Evans wrote: > > >> >Is there a good reason for having the sig*set macros defined > >> >in and the equivalent functions in libc? > > >> [Long answer.] > > >Let's try this again. > > >Can we remove the macro definitions, and just rely on the functions? > > Not so long answer: why do you want to? Some versions of Linux > removed them because they are buggy, but the FreeBSD libc versions > are equally buggy. > > Short answer: no. I've got a PR I was fixing, and it says that POSIX requires that these functions check the value of the signal number that was passed in, and return -1 if it is out of range, and set errno to EINVAL. Doing this in the macro versions now causes name space polution in signal.h, because they now depend on errno.h for EINVAL and errno. Removing the macros and just using the functions solves this problem. -- Mike Pritchard mpp@FreeBSD.org "Go that way. Really fast. If something gets in your way, turn" From owner-freebsd-hackers Thu Feb 27 17:33:29 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id RAA00235 for hackers-outgoing; Thu, 27 Feb 1997 17:33:29 -0800 (PST) Received: from obiwan.aceonline.com.au (obiwan.aceonline.com.au [203.103.90.67]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id RAA00221; Thu, 27 Feb 1997 17:33:24 -0800 (PST) Received: from localhost (adrian@localhost) by obiwan.aceonline.com.au (8.8.5/8.8.5) with SMTP id QAA09728; Thu, 11 Jan 1996 16:57:31 +0800 (WST) Date: Thu, 11 Jan 1996 16:57:31 +0800 (WST) From: Adrian Chadd To: "John S. Dyson" cc: "Jordan K. Hubbard" , mark@quickweb.com, questions@freebsd.org, hackers@freebsd.org Subject: Re: Java binary support in FreeBSD ... In-Reply-To: <199702271553.KAA01146@dyson.iquest.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > Well, go do it and then come back with your proof-of-concept for us to > > comment on. Anything else is just blue-sky dreaming, and we've got > > more than enough of that to last us through the remainder of this > > century. :-) > > > Actually, writing the image activator for Java wouldn't be too hard, > and could be an excellent first-kernel-project. I think that the > normal kernel hackers are totally overloaded as Jordan says, so any > volunteers? > I'll look at the Linux source for it today during a break at uni. (along with the other couple of things I'm meant to do to the kernel sometime). > John > Adrian Chadd From owner-freebsd-hackers Thu Feb 27 19:26:58 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id TAA07464 for hackers-outgoing; Thu, 27 Feb 1997 19:26:58 -0800 (PST) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id TAA07435; Thu, 27 Feb 1997 19:26:54 -0800 (PST) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.3/8.6.9) id OAA26377; Fri, 28 Feb 1997 14:23:19 +1100 Date: Fri, 28 Feb 1997 14:23:19 +1100 From: Bruce Evans Message-Id: <199702280323.OAA26377@godzilla.zeta.org.au> To: bde@zeta.org.au, mpp@freefall.freebsd.org Subject: Re: sig*set macros in Cc: freebsd-hackers@freefall.freebsd.org Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >I've got a PR I was fixing, and it says that POSIX requires that these >functions check the value of the signal number that was passed in, and >return -1 if it is out of range, and set errno to EINVAL. If you fix this, then it is reasonable to remove the macros. However, POSIX doesn't require that these functions detect errors, and it only requires errno to be set if an error is detected. It does require that sigismember() returns the following values: -1: an error was detected 0: the signal number is not in the set 1: the signal number is in the set The current implementation is broken here. It returns 1 for some invalid signal numbers. Invalid signal number can reasonably be interpreted as non-errors, but they can't reasonably be interpreted as being in the set. I think POSIX also requires that invalid signal numbers don't cause undefined behaviour. Shifts of < 0 or >= the size of the scalar type sigset_t cause undefined behaviour, but this doesn't matter because the actual behaviour is harmless on all supported machines. >Doing this in the macro versions now causes name space polution in signal.h, >because they now depend on errno.h for EINVAL and errno. I think the letter and even the spirit of POSIX would be satisfied if you just changed sigemptyset() to return 0 for invalid signal numbers. Something like: return ((signo) <= 0 || (signo) > NSIG ? 0 : same_value_as_now()) This needs more work: 1. NSIG pollutes the namespace. Use a new identifier _NSIG. 2. signo is multiply evaluated. I think it is impossible to write a correct macro for sigemptyset() in C :-(. It is easy in GNU C using a statement expression :-). Note that signo is usually a literal constant so gcc would not generate any code for the range checking. Bruce From owner-freebsd-hackers Thu Feb 27 19:43:07 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id TAA11398 for hackers-outgoing; Thu, 27 Feb 1997 19:43:07 -0800 (PST) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id TAA11392 for ; Thu, 27 Feb 1997 19:43:04 -0800 (PST) Received: from current1.whistle.com (current1.whistle.com [207.76.205.22]) by alpo.whistle.com (8.8.5/8.8.4) with SMTP id TAA22712; Thu, 27 Feb 1997 19:01:12 -0800 (PST) Message-ID: <331649F3.167EB0E7@whistle.com> Date: Thu, 27 Feb 1997 18:58:59 -0800 From: Julian Elischer Organization: Whistle Communications X-Mailer: Mozilla 3.0Gold (X11; I; FreeBSD 2.2-CURRENT i386) MIME-Version: 1.0 To: dg@root.com CC: Joseph Thomas , hackers@FreeBSD.ORG Subject: Re: Assumptions about kmem_malloc()... References: <199702280129.RAA05746@root.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk David Greenman wrote: > > > o Other then contigmalloc(), is there a way to malloc contiguous > >physical memory greater then one page? > > No; we created vm_page_alloc_contig/contigmalloc specifically for this > purpose, and it's the only mechanism that exists to do this. > > > The driver waits to malloc memory until microcode is > > downloaded to the NIC (Fore PCA200E). someone was saying they already had a driver for this.. you might check on the freebsd-atm list also, I wonder if we couldn't make a memory de-fragger that could be kicked off by a process when it knows it's going to need some contiguous space.... From owner-freebsd-hackers Thu Feb 27 20:53:56 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id UAA14983 for hackers-outgoing; Thu, 27 Feb 1997 20:53:56 -0800 (PST) Received: from metrocon.com (root@metrocon.com [208.9.142.32]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id UAA14973 for ; Thu, 27 Feb 1997 20:53:53 -0800 (PST) Received: from dialup055.metrocon.com (prophet@dialup055.metrocon.com [208.17.65.55]) by metrocon.com (8.8.3/8.8.3) with SMTP id XAA04449 for ; Thu, 27 Feb 1997 23:52:25 GMT Received: by dialup055.metrocon.com with Microsoft Mail id <01BC2509.CA578D00@dialup055.metrocon.com>; Thu, 27 Feb 1997 23:56:03 -0500 Message-ID: <01BC2509.CA578D00@dialup055.metrocon.com> From: Charles Chao To: "'freebsd-hackers@freebsd.org'" Date: Thu, 27 Feb 1997 23:49:24 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Unsubscribe freebsd-hackers@freebsd.org cchao@metrocon.com From owner-freebsd-hackers Thu Feb 27 20:53:57 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id UAA14986 for hackers-outgoing; Thu, 27 Feb 1997 20:53:57 -0800 (PST) Received: from metrocon.com (root@metrocon.com [208.9.142.32]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id UAA14974 for ; Thu, 27 Feb 1997 20:53:53 -0800 (PST) Received: from dialup055.metrocon.com (prophet@dialup055.metrocon.com [208.17.65.55]) by metrocon.com (8.8.3/8.8.3) with SMTP id XAA04445 for ; Thu, 27 Feb 1997 23:52:23 GMT Received: by dialup055.metrocon.com with Microsoft Mail id <01BC2509.C57761C0@dialup055.metrocon.com>; Thu, 27 Feb 1997 23:55:55 -0500 Message-ID: <01BC2509.C57761C0@dialup055.metrocon.com> From: Charles Chao To: "'hackers@freebsd.org'" Date: Thu, 27 Feb 1997 23:48:00 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Unsubscribe hackers@freebsd.org cchao@metrocon.com From owner-freebsd-hackers Thu Feb 27 21:50:38 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id VAA18592 for hackers-outgoing; Thu, 27 Feb 1997 21:50:38 -0800 (PST) Received: from dg-rtp.dg.com (dg-rtp.rtp.dg.com [128.222.1.2]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id VAA18570 for ; Thu, 27 Feb 1997 21:50:35 -0800 (PST) Received: by dg-rtp.dg.com (5.4R3.10/dg-rtp-v02) id AA00857; Fri, 28 Feb 1997 00:50:02 -0500 Received: from ponds by dg-rtp.dg.com.rtp.dg.com; Fri, 28 Feb 1997 00:50 EST Received: from lakes.water.net (lakes [10.0.0.3]) by ponds.water.net (8.8.3/8.7.3) with ESMTP id WAA18889; Thu, 27 Feb 1997 22:29:12 -0500 (EST) Received: (from rivers@localhost) by lakes.water.net (8.8.3/8.6.9) id WAA03821; Thu, 27 Feb 1997 22:34:33 -0500 (EST) Date: Thu, 27 Feb 1997 22:34:33 -0500 (EST) From: Thomas David Rivers Message-Id: <199702280334.WAA03821@lakes.water.net> To: ponds!root.com!dg, ponds!freefall.cdrom.com!freebsd-hackers Subject: Another installment of the "dup alloc"/"bad dir" panic problems. Content-Type: text Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Recall, this is with 2.1.6.1; but it's also been reported with 2.2; on varying processors and with SCSI and IDE disks. The new information is that my previous idea of disksort() being re-entered; and thus messing up the buffer chains is likely not correct. I think the reason my kernel printf()'s looked funny was because I was using cntrl-S on the console (perhaps a syscons buffering issue.) I'm pretty confident nothing is wrong with disksort(). However, I've tentatively determined that adding these printf's to disksort() have affected the problem. [I took Jordan's advice and also added printf()'s for entering disksort() and leaving it, as well as printing the block number for the buffer element being added to the queue. - other than that, it's a stock 2.1.6.1 kernel) If you recall; I could trash a particular inode; run newfs and discover the inode was not properly zero'd out (sometimes) although I had verified that the write() for that particular block, with a buffer full of zeros, had been issued. It now appears that having the printf()s in disksort() affects the problem in a positive manner (that is, I'm not able to demonstrate the previous "non-writing" behaviour I had seen; the inode in question is reliably filled with zeros.) I'm not sure what this means; does it point to some critical timing situation required for causing the problem? Does it point to missing splXXX() call... would anyone care to comment? - Thanks - - Dave Rivers - From owner-freebsd-hackers Fri Feb 28 01:41:00 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id BAA13715 for hackers-outgoing; Fri, 28 Feb 1997 01:41:00 -0800 (PST) Received: from deepo.prosa.dk ([193.89.187.27]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id BAA13683 for ; Fri, 28 Feb 1997 01:40:54 -0800 (PST) Received: (from regnauld@localhost) by deepo.prosa.dk (8.8.5/8.8.4/prosa-1.1) id KAA04091; Fri, 28 Feb 1997 10:37:24 +0100 (CET) Message-ID: Date: Fri, 28 Feb 1997 10:37:23 +0100 From: regnauld@deepo.prosa.dk (Philippe Regnauld) To: mbarkah@hemi.com (Ade Barkah) Cc: freebsd-hackers@freebsd.org Subject: Re: uptime References: <199702271713.JAA23356@ref.tfs.com> <199702272149.OAA13852@hemi.com> X-Mailer: Mutt 0.58 Mime-Version: 1.0 X-Operating-System: FreeBSD 2.2-BETA_A i386 In-Reply-To: <199702272149.OAA13852@hemi.com>; from Ade Barkah on Feb 27, 1997 14:49:32 -0700 Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Ade Barkah (mbarkah) ecrit/writes: > > 10:36am up 500 days, 13:08, 2 users, load average: 0.20, 0.03, 0.02 > > Wow, 500 days... imagine how many security holes it has. =-) Friend o' mine had a 3/60 running as WWW server for 643 days. Power failure took it down. -- -- Phil -[ Philippe Regnauld / Systems Administrator / regnauld@prosa.dk ]- -[ Location.: +55.4N +11.3E PGP Key: finger regnauld@deepo.prosa.dk ]- From owner-freebsd-hackers Fri Feb 28 02:27:43 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id CAA19313 for hackers-outgoing; Fri, 28 Feb 1997 02:27:43 -0800 (PST) Received: from obiwan.aceonline.com.au (obiwan.aceonline.com.au [203.103.90.67]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id CAA19308 for ; Fri, 28 Feb 1997 02:27:38 -0800 (PST) Received: from localhost (adrian@localhost) by obiwan.aceonline.com.au (8.8.5/8.8.5) with SMTP id AAA02326; Sat, 1 Mar 1997 00:30:08 +0800 (WST) Date: Sat, 1 Mar 1997 00:30:07 +0800 (WST) From: Adrian Chadd To: Philippe Regnauld cc: Ade Barkah , freebsd-hackers@freebsd.org Subject: Re: uptime In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > Ade Barkah (mbarkah) ecrit/writes: > > > > 10:36am up 500 days, 13:08, 2 users, load average: 0.20, 0.03, 0.02 > > > > Wow, 500 days... imagine how many security holes it has. =-) > > Friend o' mine had a 3/60 running as WWW server for 643 days. > > Power failure took it down. > Wasn't it on a UPS? *grin* Cya. Adrian. From owner-freebsd-hackers Fri Feb 28 02:30:08 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id CAA19466 for hackers-outgoing; Fri, 28 Feb 1997 02:30:08 -0800 (PST) Received: from deepo.prosa.dk ([193.89.187.27]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id CAA19461 for ; Fri, 28 Feb 1997 02:30:03 -0800 (PST) Received: (from regnauld@localhost) by deepo.prosa.dk (8.8.5/8.8.4/prosa-1.1) id LAA09242; Fri, 28 Feb 1997 11:33:12 +0100 (CET) Message-ID: Date: Fri, 28 Feb 1997 11:33:12 +0100 From: regnauld@deepo.prosa.dk (Philippe Regnauld) To: adrian@obiwan.aceonline.com.au (Adrian Chadd) Cc: mbarkah@hemi.com (Ade Barkah), freebsd-hackers@freebsd.org Subject: Re: uptime References: X-Mailer: Mutt 0.58 Mime-Version: 1.0 X-Operating-System: FreeBSD 2.2-BETA_A i386 In-Reply-To: ; from Adrian Chadd on Mar 1, 1997 00:30:07 +0800 Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Adrian Chadd (adrian) ecrit/writes: > > Wasn't it on a UPS? *grin* No :-( Actually, I get to a point (with BSDish systems) where I'm more amazed by the reliability of the local power company than that of the OS -- I really get surprised when the OS fails :-) -- -- Phil -[ Philippe Regnauld / Systems Administrator / regnauld@prosa.dk ]- -[ Location.: +55.4N +11.3E PGP Key: finger regnauld@deepo.prosa.dk ]- From owner-freebsd-hackers Fri Feb 28 02:39:44 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id CAA19675 for hackers-outgoing; Fri, 28 Feb 1997 02:39:44 -0800 (PST) Received: from melbourne.DIALix.oz.au (melbourne.DIALix.oz.au [192.203.228.98]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id CAA19670 for ; Fri, 28 Feb 1997 02:39:36 -0800 (PST) Received: (from uucp@localhost) by melbourne.DIALix.oz.au with UUCP id VAA07723 for freebsd-hackers@freebsd.org; Fri, 28 Feb 1997 21:39:21 +1100 (EST) Received: (from mark@localhost) by doorway.seeware.DIALix.oz.au (8.7.5/8.7.3) id UAA16766; Fri, 28 Feb 1997 20:42:00 +1100 (EST) Date: Fri, 28 Feb 1997 20:41:59 +1100 (EST) From: Mark Hannon To: freebsd-hackers@freebsd.org Subject: Alt key in syscons Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi, I looked through the mailing list archives for info on how to setup emacs to use the meta-key in syscons and saw the question, some answers and the comment that a modified syscons keymap is required. However, nobody posted the keymap. Can someone do that please? Regards/mark +-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-+ | Mark Hannon,| FreeBSD, Free Unix for your PC | mark@seeware.DIALix.oz.au| | Melbourne, | PGP key available by fingering | epamha@epa.ericsson.se | | Australia | seeware@melbourne.DIALix.oz.au | | +-=-=-=-=-=-=-+-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-+ From owner-freebsd-hackers Fri Feb 28 02:44:02 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id CAA19896 for hackers-outgoing; Fri, 28 Feb 1997 02:44:02 -0800 (PST) Received: from obiwan.aceonline.com.au (obiwan.aceonline.com.au [203.103.90.67]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id CAA19858 for ; Fri, 28 Feb 1997 02:43:54 -0800 (PST) Received: from localhost (adrian@localhost) by obiwan.aceonline.com.au (8.8.5/8.8.5) with SMTP id AAA00312; Sat, 1 Mar 1997 00:45:53 +0800 (WST) Date: Sat, 1 Mar 1997 00:45:52 +0800 (WST) From: Adrian Chadd To: Philippe Regnauld cc: Ade Barkah , freebsd-hackers@freebsd.org Subject: Re: uptime In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Fri, 28 Feb 1997, Philippe Regnauld wrote: > No :-( Actually, I get to a point (with BSDish systems) where I'm > more amazed by the reliability of the local power company than > that of the OS -- I really get surprised when the OS fails :-) > hehe. :) I seem to remember a bug (feature? :) in Linux systems that took them down at (around) a certain uptime *grin* Anyone confirm / deny this? Cya. Adrian. From owner-freebsd-hackers Fri Feb 28 04:10:44 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id EAA22931 for hackers-outgoing; Fri, 28 Feb 1997 04:10:44 -0800 (PST) Received: from server21.digital.fr (server21.digital.fr [193.56.15.21]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id EAA22918 for ; Fri, 28 Feb 1997 04:10:21 -0800 (PST) Received: from mail.vbo.dec.com (mail.vbo.dec.com [16.36.208.34]) by server21.digital.fr (8.7.5/8.7) with ESMTP id NAA28226 for ; Fri, 28 Feb 1997 13:10:54 +0100 (MET) Received: from vbormc.vbo.dec.com (vbormc.vbo.dec.com [16.36.208.94]) by mail.vbo.dec.com (8.7.3/8.7) with ESMTP id NAA21359 for ; Fri, 28 Feb 1997 13:07:51 +0100 (MET) Received: from wilkux.jgo.dec.com (wilkux.jgo.dec.com [16.183.208.192]) by vbormc.vbo.dec.com (8.7.3/8.7) with ESMTP id NAA16118 for ; Fri, 28 Feb 1997 13:03:00 +0100 Received: (from wilko@localhost) by wilkux.jgo.dec.com (8.6.12/8.6.12) id NAA12748 for freebsd-hackers@freebsd.org; Fri, 28 Feb 1997 13:04:08 +0100 From: Wilko Bulte Message-Id: <199702281204.NAA12748@wilkux.jgo.dec.com> Subject: inappropriate use of the list but you'll like this :-) To: freebsd-hackers@freebsd.org Date: Fri, 28 Feb 1997 13:04:08 +0100 (MET) X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Maybe I should not do this, but I could not resist after seeing this on the web: http://edge.ml.org/no-msie/ Enjoy! Wilko From owner-freebsd-hackers Fri Feb 28 04:37:46 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id EAA24764 for hackers-outgoing; Fri, 28 Feb 1997 04:37:46 -0800 (PST) Received: from paranoid.convey.ru (ws02.convey.ru [195.182.128.17]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id EAA24751 for ; Fri, 28 Feb 1997 04:37:30 -0800 (PST) Received: (from ark@localhost) by paranoid.convey.ru (8.7.5/8.7.3) id PAA03850; Fri, 28 Feb 1997 15:36:32 +0300 From: ArkanoiD Message-Id: <199702281236.PAA03850@paranoid.convey.ru> Subject: Re: Fatal traps 12 == shitty motherboard | memory ??? To: rashid@rk.wbs.com (Rashid Karimov) Date: Fri, 28 Feb 1997 15:36:31 +0300 (MSK) Cc: hackers@freebsd.org In-Reply-To: <199702271929.OAA00290@rk.wbs.com> from "Rashid Karimov" at Feb 27, 97 02:29:04 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 8bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk nuqneH, > It's been quite a time since that posting , wasn't it ? > Anyway, it's mostly related to the bad memory when you have > infamous Trap 12: using anything but 60ns with 133Mhz > Pentiums or just plain bad memory ( in this case it will > usually fail himem.exe test). > :( no i'm sure memory is not the problem. the machine was heavy tested and i even tried to replace memory with another SIMMs.. and i tried changing motherboard too - to another HX a bit earlier version.. It increased stability somehow but did not solve the problem completely. (i mean it was motherboard change that helped,not replacing SIMMs). btw i forgot to mention - mine is p100,not p133 - it was said it is more reliable so i chose to use p100.. -- _ _ _ _ _ _ _ {::} {::} {::} CU in Hell _| o |_ | | _|| | / _||_| |_ |_ |_ (##) (##) (##) /Arkan#iD |_ o _||_| _||_| / _| | o |_||_||_| [||] [||] [||] Do i believe in Bible? Hell,man,i've seen one! From owner-freebsd-hackers Fri Feb 28 04:54:48 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id EAA25193 for hackers-outgoing; Fri, 28 Feb 1997 04:54:48 -0800 (PST) Received: from obiwan.aceonline.com.au (obiwan.aceonline.com.au [203.103.90.67]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id EAA25188 for ; Fri, 28 Feb 1997 04:54:44 -0800 (PST) Received: from localhost (adrian@localhost) by obiwan.aceonline.com.au (8.8.5/8.8.5) with SMTP id CAA00317 for ; Sat, 1 Mar 1997 02:57:53 +0800 (WST) Date: Sat, 1 Mar 1997 02:57:52 +0800 (WST) From: Adrian Chadd To: freebsd-hackers@freebsd.org Subject: Re : java support in FreeBSD.. Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I'll have a working tester for anyone to play with in a day or so. You set the path to the java interpreter, appletviwer and classfile using sysctl (kern.java.interpreter/appletviewer/classpath) and it will execute things for you. There isn't ANY java interpreter stuff in the kernel, just the bit to detect a java binary. Thanks, Adrian Chadd From owner-freebsd-hackers Fri Feb 28 06:12:07 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id GAA27478 for hackers-outgoing; Fri, 28 Feb 1997 06:12:07 -0800 (PST) Received: from murkwood.gaffaneys.com (dialup4.gaffaneys.com [134.129.252.23]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id GAA27469 for ; Fri, 28 Feb 1997 06:12:02 -0800 (PST) Received: (from zach@localhost) by murkwood.gaffaneys.com (8.8.5/8.8.5) id IAA03179; Fri, 28 Feb 1997 08:10:22 -0600 (CST) From: Zach Heilig Message-ID: <19970228081022.42769@gaffaneys.com> Date: Fri, 28 Feb 1997 08:10:22 -0600 To: Mark Hannon Cc: freebsd-hackers@freebsd.org Subject: Re: Alt key in syscons References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.61.1 In-Reply-To: ; from Mark Hannon on Feb 02, 1997 at 08:41:59PM +1100 Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Feb 02, 1997 at 08:41:59PM +1100, Mark Hannon wrote: > I looked through the mailing list archives for info on how to setup > emacs to use the meta-key in syscons and saw the question, some answers > and the comment that a modified syscons keymap is required. > However, nobody posted the keymap. Can someone do that please? Here is the one I use. It is basically the standard keymap (from 2.1.0) with the boot commands removed and the alt key mapped to meta. # alt # scan cntrl alt alt cntrl lock # code base shift cntrl shift alt shift cntrl shift state # ------------------------------------------------------------------ 000 nop nop nop nop nop nop nop nop O 001 esc esc nop nop 0x9b 0x9b nop nop O 002 '1' '!' nop nop 0xb1 0xa1 nop nop O 003 '2' '@' nul nul 0xb2 0xc0 0x80 0x80 O 004 '3' '#' nop nop 0xb3 0xa3 nop nop O 005 '4' '$' nop nop 0xb4 0xa4 nop nop O 006 '5' '%' nop nop 0xb5 0xa5 nop nop O 007 '6' '^' rs rs 0xb6 0xde 0x9e 0x9e O 008 '7' '&' nop nop 0xb7 0xa6 nop nop O 009 '8' '*' nop nop 0xb8 0xaa nop nop O 010 '9' '(' nop nop 0xb9 0xa8 nop nop O 011 '0' ')' nop nop 0xb0 0xa9 nop nop O 012 '-' '_' ns ns 0xad 0xdf 0x9f 0x9f O 013 '=' '+' nop nop 0xbd 0xab nop nop O 014 del del bs bs 0xff 0xff 0x88 0x88 O 015 ht btab nop nop 0x89 btab nop nop O 016 'q' 'Q' dc1 dc1 0xf1 0xd1 0x91 0x91 C 017 'w' 'W' etb etb 0xf7 0xd7 0x97 0x97 C 018 'e' 'E' enq enq 0xe5 0xc5 0x85 0x85 C 019 'r' 'R' dc2 dc2 0xf2 0xd2 0x92 0x92 C 020 't' 'T' dc4 dc4 0xf4 0xd4 0x94 0x94 C 021 'y' 'Y' em em 0xf9 0xd9 0x99 0x99 C 022 'u' 'U' nak nak 0xf5 0xd5 0x95 0x95 C 023 'i' 'I' ht ht 0xe9 0xc9 0x88 0x88 C 024 'o' 'O' si si 0xef 0xcf 0x8f 0x8f C 025 'p' 'P' dle dle 0xf0 0xd0 0x90 0x90 C 026 '[' '{' esc esc 0xdb 0xfb 0x9b 0x9b O 027 ']' '}' gs gs 0xdd 0xfd 0x9d 0x9d O 028 cr cr nl nl 0x8d 0x8d 0x8a 0x8a O 029 lctrl lctrl lctrl lctrl lctrl lctrl lctrl lctrl O 030 'a' 'A' soh soh 0xe1 0xc1 0x81 0x81 C 031 's' 'S' dc3 dc3 0xf3 0xd3 0x93 0x93 C 032 'd' 'D' eot eot 0xe4 0xc4 0x04 0x04 C 033 'f' 'F' ack ack 0xe6 0xc6 0x86 0x86 C 034 'g' 'G' bel bel 0xe7 0xc7 0x87 0x87 C 035 'h' 'H' bs bs 0xe8 0xc8 0x88 0x88 C 036 'j' 'J' nl nl 0xea 0xca 0x8a 0x8a C 037 'k' 'K' vt vt 0xeb 0xcb 0x8b 0x8b C 038 'l' 'L' ff ff 0xec 0xcc 0x8c 0x8c C 039 ';' ':' nop nop 0xbb 0xba nop nop O 040 ''' '"' nop nop 0xa7 0xa2 nop nop O 041 '`' '~' nop nop 0xe0 0xfe nop nop O 042 lshift lshift lshift lshift lshift lshift lshift lshift O 043 '\' '|' fs fs 0xdc 0xfc 0x9c 0x9c O 044 'z' 'Z' sub sub 0xfa 0xda 0x9a 0x9a C 045 'x' 'X' can can 0xf8 0xd8 0x98 0x98 C 046 'c' 'C' etx etx 0xe3 0xc3 0x83 0x83 C 047 'v' 'V' syn syn 0xf6 0xd6 0x96 0x96 C 048 'b' 'B' stx stx 0xe2 0xc2 0x82 0x82 C 049 'n' 'N' so so 0xee 0xce 0x8e 0x8e C 050 'm' 'M' cr cr 0xed 0xcd 0x8d 0x8d C 051 ',' '<' nop nop 0xac 0xbc nop nop O 052 '.' '>' nop nop 0xae 0xbe nop nop O 053 '/' '?' nop nop 0xaf 0xbf nop nop O 054 rshift rshift rshift rshift rshift rshift rshift rshift O 055 '*' '*' nscr nscr 0xaa 0xaa nscr nscr O 056 lalt lalt lalt lalt lalt lalt lalt lalt O 057 ' ' ' ' nul nul 0xa0 0xa0 0x80 0x80 O 058 clock clock clock clock clock clock clock clock O 059 fkey01 fkey13 fkey25 fkey37 scr01 scr11 scr01 scr11 O 060 fkey02 fkey14 fkey26 fkey38 scr02 scr12 scr02 scr12 O 061 fkey03 fkey15 fkey27 fkey39 scr03 scr13 scr03 scr13 O 062 fkey04 fkey16 fkey28 fkey40 scr04 scr14 scr04 scr14 O 063 fkey05 fkey17 fkey29 fkey41 scr05 scr15 scr05 scr15 O 064 fkey06 fkey18 fkey30 fkey42 scr06 scr16 scr06 scr16 O 065 fkey07 fkey19 fkey31 fkey43 scr07 scr07 scr07 scr07 O 066 fkey08 fkey20 fkey32 fkey44 scr08 scr08 scr08 scr08 O 067 fkey09 fkey21 fkey33 fkey45 scr09 scr09 scr09 scr09 O 068 fkey10 fkey22 fkey34 fkey46 scr10 scr10 scr10 scr10 O 069 nlock nlock nlock nlock nlock nlock nlock nlock O 070 slock slock slock slock slock slock slock slock O 071 fkey49 '7' '7' '7' '7' '7' '7' '7' N 072 fkey50 '8' '8' '8' '8' '8' '8' '8' N 073 fkey51 '9' '9' '9' '9' '9' '9' '9' N 074 fkey52 '-' '-' '-' '-' '-' '-' '-' N 075 fkey53 '4' '4' '4' '4' '4' '4' '4' N 076 fkey54 '5' '5' '5' '5' '5' '5' '5' N 077 fkey55 '6' '6' '6' '6' '6' '6' '6' N 078 fkey56 '+' '+' '+' '+' '+' '+' '+' N 079 fkey57 '1' '1' '1' '1' '1' '1' '1' N 080 fkey58 '2' '2' '2' '2' '2' '2' '2' N 081 fkey59 '3' '3' '3' '3' '3' '3' '3' N 082 fkey60 '0' '0' '0' '0' '0' '0' '0' N 083 del '.' '.' '.' '.' '.' '.' '.' N 084 ns ns ns ns ns ns ns ns O 085 nop nop nop nop nop nop nop nop O 086 nop nop nop nop nop nop nop nop O 087 fkey11 fkey23 fkey35 fkey47 scr11 scr11 scr11 scr11 O 088 fkey12 fkey24 fkey36 fkey48 scr12 scr12 scr12 scr12 O 089 cr cr nl nl cr cr nl nl N 090 rctrl rctrl rctrl rctrl rctrl rctrl rctrl rctrl O 091 '/' '/' '/' '/' '/' '/' '/' '/' N 092 nscr nop debug nop nop nop nop nop O 093 ralt ralt ralt ralt ralt ralt ralt ralt O 094 fkey49 fkey49 fkey49 fkey49 fkey49 fkey49 fkey49 fkey49 O 095 fkey50 fkey50 fkey50 fkey50 fkey50 fkey50 fkey50 fkey50 O 096 fkey51 fkey51 fkey51 fkey51 fkey51 fkey51 fkey51 fkey51 O 097 fkey53 fkey53 fkey53 fkey53 fkey53 fkey53 fkey53 fkey53 O 098 fkey55 fkey55 fkey55 fkey55 fkey55 fkey55 fkey55 fkey55 O 099 fkey57 fkey57 fkey57 fkey57 fkey57 fkey57 fkey57 fkey57 O 100 fkey58 fkey58 fkey58 fkey58 fkey58 fkey58 fkey58 fkey58 O 101 fkey59 fkey59 fkey59 fkey59 fkey59 fkey59 fkey59 fkey59 O 102 fkey60 fkey60 fkey60 fkey60 fkey60 fkey60 fkey60 fkey60 O 103 fkey61 fkey61 fkey61 fkey61 fkey61 fkey61 fkey61 fkey61 O 104 slock slock slock slock slock slock slock slock O 105 fkey62 fkey62 fkey62 fkey62 fkey62 fkey62 fkey62 fkey62 O 106 fkey63 fkey63 fkey63 fkey63 fkey63 fkey63 fkey63 fkey63 O 107 fkey64 fkey64 fkey64 fkey64 fkey64 fkey64 fkey64 fkey64 O From owner-freebsd-hackers Fri Feb 28 07:42:26 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id HAA01707 for hackers-outgoing; Fri, 28 Feb 1997 07:42:26 -0800 (PST) Received: from time.cdrom.com (jkh@time.cdrom.com [204.216.27.226]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id HAA01702; Fri, 28 Feb 1997 07:42:19 -0800 (PST) Received: (from jkh@localhost) by time.cdrom.com (8.8.5/8.6.9) id HAA29897; Fri, 28 Feb 1997 07:42:12 -0800 (PST) Date: Fri, 28 Feb 1997 07:42:12 -0800 (PST) From: "Jordan K. Hubbard" Message-Id: <199702281542.HAA29897@time.cdrom.com> To: bde@freebsd.org Subject: Will the real uid_t please stand up? Cc: hackers@freebsd.org Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Following some of the discussion in port-i386@NetBSD.org about this, I decided to look into FreeBSD's own uid_t situation and noticed the following "interesting things" in 2.2 and -current: /usr/include/g++/_G_config.h:typedef unsigned int _G_uid_t; OK, one vote for unsigned int. /usr/include/kerberosIV/krb.h:typedef unsigned short uid_t; Ooh, and one for unsigned short! Fortunately, this one is disabled by an ifdef but it probably should still be changed. /usr/include/sys/types.h:typedef u_int32_t uid_t; /* user And that looks reasonable. But here's the clincher: Adding this user to the password file: test:*:1048576:32766::0:0:Just Testing:/tmp:/sbin/nologin Results in this: vipw: rebuilding the database... pwd_mkdb: 1048576 > max uid value (65535) vipw: done And the check in /usr/src/usr.sbin/pwd_mkdb/pw_scan.c does indeed say: if (id > USHRT_MAX) { warnx("%s > max uid value (%d)", p, USHRT_MAX); /*return (0);*/ /* THIS SHOULD NOT BE FATAL! */ } (same mistake made for gid_t). It's not fatal, but it certainly doesn't seem right. Does the following patch seem appropriate or are there reasons for artificially limiting uid_t to a ushort which I still don't know about? Jordan --- /usr/src/usr.sbin/pwd_mkdb/pw_scan.c.orig Fri Feb 28 07:37:48 1997 +++ /usr/src/usr.sbin/pwd_mkdb/pw_scan.c Fri Feb 28 07:37:49 1997 @@ -81,8 +81,8 @@ warnx("root uid should be 0"); return (0); } - if (id > USHRT_MAX) { - warnx("%s > max uid value (%d)", p, USHRT_MAX); + if (id > UINT_MAX) { + warnx("%s > max uid value (%d)", p, UINT_MAX); /*return (0);*/ /* THIS SHOULD NOT BE FATAL! */ } pw->pw_uid = id; @@ -91,8 +91,8 @@ goto fmt; if(p[0]) pw->pw_fields |= _PWF_GID; id = atol(p); - if (id > USHRT_MAX) { - warnx("%s > max gid value (%d)", p, USHRT_MAX); + if (id > UINT_MAX) { + warnx("%s > max gid value (%d)", p, UINT_MAX); /* return (0); This should not be fatal! */ } pw->pw_gid = id; From owner-freebsd-hackers Fri Feb 28 07:46:48 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id HAA01893 for hackers-outgoing; Fri, 28 Feb 1997 07:46:48 -0800 (PST) Received: from wgold.demon.co.uk (wgold.demon.co.uk [158.152.96.124]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id HAA01876 for ; Fri, 28 Feb 1997 07:46:45 -0800 (PST) Received: from wgold.demon.co.uk by wgold.demon.co.uk (NTMail 3.02.10) with ESMTP id ca001224 for ; Thu, 27 Feb 1997 13:43:52 +0000 Message-ID: <33158F97.6664@wgold.demon.co.uk> Date: Thu, 27 Feb 1997 13:43:51 +0000 From: James Mansion Organization: Westongold Ltd X-Mailer: Mozilla 3.01Gold (WinNT; I) MIME-Version: 1.0 To: Mark Mayo CC: hackers@freebsd.org Subject: Re: Java binary support in FreeBSD ... References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Info: Westongold Ltd: +44 1992 620025 www.westongold.com Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Mark Mayo wrote: > Why bother??? It's not so hard to type 'java Class'...... > I like my users to be aware that they are running through an interpreter, > and that there are command line options to the interpreter. I can't imagine why anyone would take this view personally. A program is a program is a program. If I run a program, I don't care to know what language it is implemented in. UNIX gets this right with its shell scripts. Even VB gets this right! It doesn't make sense (to me) to require the use of a shell script wrapper that will then start the program under the interpreter. How kludgy - inconvenient and expensive at runtime. As for wanting to know that they are using an interpreter, well, why, apart from the very occaisonal case where you want to supply arguments to it? Most arguments go to the app, after all. And must Java runtimes are or soon will be JIT based, and its not as if there is an efficiency issue that users might wish to be aware of. James From owner-freebsd-hackers Fri Feb 28 08:05:16 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id IAA03218 for hackers-outgoing; Fri, 28 Feb 1997 08:05:16 -0800 (PST) Received: from vinyl.quickweb.com (vinyl.quickweb.com [206.222.77.8]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id IAA03213 for ; Fri, 28 Feb 1997 08:05:10 -0800 (PST) Received: from localhost (mark@localhost) by vinyl.quickweb.com (8.8.5/8.6.12) with SMTP id KAA00698; Fri, 28 Feb 1997 10:59:12 -0500 (EST) Date: Fri, 28 Feb 1997 10:59:12 -0500 (EST) From: Mark Mayo To: James Mansion cc: hackers@freebsd.org Subject: Re: Java binary support in FreeBSD ... In-Reply-To: <33158F97.6664@wgold.demon.co.uk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Thu, 27 Feb 1997, James Mansion wrote: > Mark Mayo wrote: > > Why bother??? It's not so hard to type 'java Class'...... > > I like my users to be aware that they are running through an interpreter, > > and that there are command line options to the interpreter. > > I can't imagine why anyone would take this view personally. I can't either, now that I think about it :-) Of course, shell scripts are the best example. I would truly consider it a pain in the ass if I had to type "sh script" everytime.. The only think that makes java different is that the 'binary' is a bytecode file - and it normally has the extension .class. Take for example I had a class called Mark.class; naturally, I would want to run 'Mark'. So the kernel needs to recognize that I really mean I want the interpreter to run 'Mark.class'. I gather this is possible with sysctrl.. For now, I think we should wait until the JDK 1.1 stuff stabalizes, and then look into it. Also, as the kernel threading in 3.0 comes along, and the re-entrant libraries are finished up, it should be possible to do a really nice port of the JDK - better than Solaris's perhaps?! -Mark > > A program is a program is a program. > > If I run a program, I don't care to know what language it is implemented > in. > > UNIX gets this right with its shell scripts. > > Even VB gets this right! > > It doesn't make sense (to me) to require the use of a > shell script wrapper that will then start the program > under the interpreter. How kludgy - inconvenient and > expensive at runtime. > > As for wanting to know that they are using an interpreter, well, why, > apart from the very occaisonal case where you want to supply arguments > to it? Most arguments go to the app, after all. And must Java runtimes > are or soon will > be JIT based, and its not as if there is an efficiency issue > that users might wish to be aware of. > > James > ---------------------------------------------------------------------------- Mark Mayo mark@quickweb.com RingZero Comp. http://vinyl.quickweb.com/mark ---------------------------------------------------------------------------- Nature shows that with the growth of intelligence comes increased capacity for pain, and it is only with the highest degree of intelligence that suffering reaches its supreme point. -- Arthur Schopenhauer From owner-freebsd-hackers Fri Feb 28 08:25:44 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id IAA04225 for hackers-outgoing; Fri, 28 Feb 1997 08:25:44 -0800 (PST) Received: from cold.org (cold.org [206.81.134.103]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id IAA04210 for ; Fri, 28 Feb 1997 08:25:35 -0800 (PST) Received: from localhost (brandon@localhost) by cold.org (8.8.5/8.8.3) with SMTP id JAA07549 for ; Fri, 28 Feb 1997 09:25:36 -0700 (MST) Date: Fri, 28 Feb 1997 09:25:36 -0700 (MST) From: Brandon Gillespie To: freebsd-hackers@freebsd.org Subject: Perl libpwd and (user|group)(add|mod|del) available Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Due to the various people asking for it, you can get the alpha version of this at: ftp://ftp.cold.org/pub/brandon/libpwd.tar.gz It includes the sysv useradd/del/mod/etc commands, as well as the generic 'libpwd' library which allows for full password and group file editing, as well as the shells file, and an additional module for generic adding / removing user modification. I would like to eventually submit these to the FreeBSD distribution, with an additional 'muser' program which is not currently included in the distribution--but which uses these libraries for a do-it-all add/modify/remove system for users and groups (I broke it, which is why its not currently included). The only problem is libpwd and company is written in perl5--not perl4. Comments and suggestions for fixes/improvements are more than welcome. -Brandon Gillespie From owner-freebsd-hackers Fri Feb 28 08:52:00 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id IAA05221 for hackers-outgoing; Fri, 28 Feb 1997 08:52:00 -0800 (PST) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id IAA05212; Fri, 28 Feb 1997 08:51:43 -0800 (PST) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.3/8.6.9) id DAA20965; Sat, 1 Mar 1997 03:47:38 +1100 Date: Sat, 1 Mar 1997 03:47:38 +1100 From: Bruce Evans Message-Id: <199702281647.DAA20965@godzilla.zeta.org.au> To: bde@freebsd.org, jkh@time.cdrom.com Subject: Re: Will the real uid_t please stand up? Cc: hackers@freebsd.org Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >Following some of the discussion in port-i386@NetBSD.org about this, >I decided to look into FreeBSD's own uid_t situation and noticed the >following "interesting things" in 2.2 and -current: > >/usr/include/g++/_G_config.h:typedef unsigned int _G_uid_t; > >OK, one vote for unsigned int. > >/usr/include/kerberosIV/krb.h:typedef unsigned short uid_t; > >Ooh, and one for unsigned short! Fortunately, this one is disabled >by an ifdef but it probably should still be changed. > >/usr/include/sys/types.h:typedef u_int32_t uid_t; /* user Ony is authoritative. >And the check in /usr/src/usr.sbin/pwd_mkdb/pw_scan.c does indeed say: > > if (id > USHRT_MAX) { > warnx("%s > max uid value (%d)", p, USHRT_MAX); > /*return (0);*/ /* THIS SHOULD NOT BE FATAL! */ > } > >(same mistake made for gid_t). It's not fatal, but it certainly doesn't >seem right. We decided not to change this, partly because large ids cause problems. E.g., the quota system attempts to create a 256GB (?) sparse file to hold data for uid 0xfffffffe. It fails due to overflow bugs and creates a measly 4GB file. >Does the following patch seem appropriate or are there reasons >for artificially limiting uid_t to a ushort which I still don't >know about? >--- /usr/src/usr.sbin/pwd_mkdb/pw_scan.c.orig Fri Feb 28 07:37:48 1997 >+++ /usr/src/usr.sbin/pwd_mkdb/pw_scan.c Fri Feb 28 07:37:49 1997 >@@ -81,8 +81,8 @@ > warnx("root uid should be 0"); > return (0); > } >- if (id > USHRT_MAX) { >- warnx("%s > max uid value (%d)", p, USHRT_MAX); >+ if (id > UINT_MAX) { >+ warnx("%s > max uid value (%d)", p, UINT_MAX); > /*return (0);*/ /* THIS SHOULD NOT BE FATAL! */ > } > pw->pw_uid = id; Both versions are quite buggy. `id' has type long. On i386's, USHRT_MAX has type int, so the first test fails to detect negative ids. On i386's sizeof(long) == sizeof(int), so the second test never succeeds. If longs are larger than ints, then the second test has the same bug as the first test. The second warning uses the wrong format specifier for printing an unsigned int and would usually say that the max is -1. If sizeof(short) == sizeof(int), then USHRT_MAX has type unsigned int and the first warning has the same bug. Bruce From owner-freebsd-hackers Fri Feb 28 09:13:17 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id JAA06174 for hackers-outgoing; Fri, 28 Feb 1997 09:13:17 -0800 (PST) Received: from rocky.mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id JAA06169 for ; Fri, 28 Feb 1997 09:13:14 -0800 (PST) Received: (from nate@localhost) by rocky.mt.sri.com (8.7.5/8.7.3) id KAA15049; Fri, 28 Feb 1997 10:12:37 -0700 (MST) Date: Fri, 28 Feb 1997 10:12:37 -0700 (MST) Message-Id: <199702281712.KAA15049@rocky.mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Adrian Chadd Cc: freebsd-hackers@freebsd.org Subject: Re: uptime In-Reply-To: References: Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > I seem to remember a bug (feature? :) in Linux systems that took them down > at (around) a certain uptime *grin* Anyone confirm / deny this? Yep, but it was with older kernels. The jiffies valued overflowe after a year or so, and required you to reboot the machine. In reality, I doubt anyone ever reached the goal. Nate From owner-freebsd-hackers Fri Feb 28 09:19:31 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id JAA06422 for hackers-outgoing; Fri, 28 Feb 1997 09:19:31 -0800 (PST) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.50]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id JAA06415 for ; Fri, 28 Feb 1997 09:19:29 -0800 (PST) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id KAA02143; Fri, 28 Feb 1997 10:15:22 -0700 From: Terry Lambert Message-Id: <199702281715.KAA02143@phaeton.artisoft.com> Subject: Re: Assumptions about kmem_malloc()... To: dg@root.com Date: Fri, 28 Feb 1997 10:15:22 -0700 (MST) Cc: jpt@msc.edu, hackers@FreeBSD.ORG In-Reply-To: <199702280129.RAA05746@root.com> from "David Greenman" at Feb 27, 97 05:29:28 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-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > o What other hidden gotchas are there in working with DMA and > >device drivers? > > Well, contiguous allocation is always the most common thing to get people. > :-) The only other thing you should be aware of is that allocation of > contiguous memory during normal system operation isn't guaranteed (in fact, > will likely fail)...so you should allocate whatever you need contiguous > during the device attach and olny release it later if you know you won't > need it. Why doesn't it push pages around to get a contiguous space so that it won't fail? 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-hackers Fri Feb 28 09:27:11 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id JAA06796 for hackers-outgoing; Fri, 28 Feb 1997 09:27:11 -0800 (PST) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.50]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id JAA06786 for ; Fri, 28 Feb 1997 09:27:09 -0800 (PST) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id KAA02159; Fri, 28 Feb 1997 10:23:38 -0700 From: Terry Lambert Message-Id: <199702281723.KAA02159@phaeton.artisoft.com> Subject: Re: Another installment of the "dup alloc"/"bad dir" panic problems. To: ponds!rivers@dg-rtp.dg.com (Thomas David Rivers) Date: Fri, 28 Feb 1997 10:23:37 -0700 (MST) Cc: hackers@freebsd.org In-Reply-To: <199702280334.WAA03821@lakes.water.net> from "Thomas David Rivers" at Feb 27, 97 10:34:33 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-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > If you recall; I could trash a particular inode; run newfs and discover > the inode was not properly zero'd out (sometimes) although I had > verified that the write() for that particular block, with a buffer > full of zeros, had been issued. > > It now appears that having the printf()s in disksort() affects the problem > in a positive manner (that is, I'm not able to demonstrate the previous > "non-writing" behaviour I had seen; the inode in question is reliably > filled with zeros.) > > I'm not sure what this means; does it point to some critical timing > situation required for causing the problem? Does it point to missing > splXXX() call... would anyone care to comment? Are you running IDE? If so, is your IDE controller an RZ1000 or a CMB640b? Both of these are known to fail undectably if they get an interrupt during a transfer operation. Your printf's would "fix" this by allowing the transfer to complete by delaying the operation (probably significantly delaying it, in fact). I have always been suspicious that the FreeBSD IDE driver "never exhibited the bug", even though no special steps were taken in coding it. 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-hackers Fri Feb 28 09:30:34 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id JAA07001 for hackers-outgoing; Fri, 28 Feb 1997 09:30:34 -0800 (PST) Received: from rover.village.org (rover.village.org [204.144.255.49]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id JAA06973; Fri, 28 Feb 1997 09:30:25 -0800 (PST) Received: from rover.village.org [127.0.0.1] by rover.village.org with esmtp (Exim 0.56 #1) id E0w0W7K-0002wa-00; Fri, 28 Feb 1997 10:29:10 -0700 To: "Jordan K. Hubbard" Subject: Re: Java binary support in FreeBSD ... Cc: Adrian Chadd , Mark Mayo , questions@freebsd.org, hackers@freebsd.org In-reply-to: Your message of "Thu, 27 Feb 1997 06:43:45 PST." <13303.857054625@time.cdrom.com> References: <13303.857054625@time.cdrom.com> Date: Fri, 28 Feb 1997 10:29:10 -0700 From: Warner Losh Message-Id: Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In message <13303.857054625@time.cdrom.com> "Jordan K. Hubbard" writes: : Well, go do it and then come back with your proof-of-concept for us to : comment on. Anything else is just blue-sky dreaming, and we've got : more than enough of that to last us through the remainder of this : century. :-) Unfortunately, the blue-sky dreaming isn't limited to this century, nor even the time that time_t will fit into 32 bits :-(. If you go off and do this, it might not be bad to make this generalized so that I can run my old CP/M programs through the z80 emulator that I have laying around, or the MS-DOS programs through DOSEMU or whatever. Warner From owner-freebsd-hackers Fri Feb 28 09:58:28 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id JAA08358 for hackers-outgoing; Fri, 28 Feb 1997 09:58:28 -0800 (PST) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.50]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id JAA08346; Fri, 28 Feb 1997 09:58:15 -0800 (PST) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id KAA02211; Fri, 28 Feb 1997 10:54:14 -0700 From: Terry Lambert Message-Id: <199702281754.KAA02211@phaeton.artisoft.com> Subject: Re: Will the real uid_t please stand up? To: jkh@time.cdrom.com (Jordan K. Hubbard) Date: Fri, 28 Feb 1997 10:54:14 -0700 (MST) Cc: bde@freebsd.org, hackers@freebsd.org In-Reply-To: <199702281542.HAA29897@time.cdrom.com> from "Jordan K. Hubbard" at Feb 28, 97 07:42:12 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-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > Does the following patch seem appropriate or are there reasons > for artificially limiting uid_t to a ushort which I still don't > know about? yp. 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-hackers Fri Feb 28 10:48:36 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id KAA10788 for hackers-outgoing; Fri, 28 Feb 1997 10:48:36 -0800 (PST) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id KAA10783 for ; Fri, 28 Feb 1997 10:48:32 -0800 (PST) Received: from current1.whistle.com (current1.whistle.com [207.76.205.22]) by alpo.whistle.com (8.8.5/8.8.4) with SMTP id JAA06003; Fri, 28 Feb 1997 09:54:01 -0800 (PST) Message-ID: <33171B33.167EB0E7@whistle.com> Date: Fri, 28 Feb 1997 09:51:47 -0800 From: Julian Elischer Organization: Whistle Communications X-Mailer: Mozilla 3.0Gold (X11; I; FreeBSD 2.2-CURRENT i386) MIME-Version: 1.0 To: Simon Shapiro CC: freebsd-hackers@freebsd.org Subject: Re: FW: SCSI HBA QUESTION - IMPORTANT (long) References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Simon Shapiro wrote: > > I am finally starting to debug the DPT driver. Here is what I have. There > is a question at the end: > > The following is a trace of kernel messages. It has compiled with option > SCSIDEBUG, which does not seem to help me much :-( > you need to TURN IT ON at run time see scsi(4) and scsi(8) also; you can enable it from boot time from scsiconf.c with some #defines you will find in there.. From owner-freebsd-hackers Fri Feb 28 10:58:09 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id KAA11383 for hackers-outgoing; Fri, 28 Feb 1997 10:58:09 -0800 (PST) Received: from dirac.phys.washington.edu (dirac.phys.washington.edu [128.95.93.1]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id KAA11377 for ; Fri, 28 Feb 1997 10:58:07 -0800 (PST) Received: by dirac.phys.washington.edu (951211.SGI.8.6.12.PATCH1042/UW-NDC Revision: 2.25 ) id KAA08836; Fri, 28 Feb 1997 10:58:05 -0800 From: "William R. Somsky" Message-Id: <199702281858.KAA08836@dirac.phys.washington.edu> Subject: Re: Java binary support in FreeBSD ... To: hackers@freefall.freebsd.org Date: Fri, 28 Feb 1997 10:58:05 -0800 (PST) In-Reply-To: <199702281546.HAA01905@freefall.freebsd.org> from "owner-hackers-digest@freefall.freebsd.org" at Feb 28, 97 07:46:51 am X-Mailer: ELM [version 2.4 PL25] Content-Type: text Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > Remember - users don't want to know half the time how things work. They > > just want it to. :) If a user sees in a blurb that FreeBSD supports > > executing java "binaries" when you add the jdk package/port, they'll say > > "wow!". > > > > Just another crazy idea. > > Well, go do it and then come back with your proof-of-concept for us to > comment on. Anything else is just blue-sky dreaming, and we've got > more than enough of that to last us through the remainder of this > century. :-) Hmm... Interesting... Well, just to toss a little more sky into the pot, how about something like this: :-) Now, I don't claim to be a kernel wizard (a kernel wizard is lower than a general wizard, but above a major wizard or a captain wizard :-) -- sorry, I digress...), but my understanding of what a general Unix or Unixoid kernel does when it's asked to execute a file is that it does something along these lines: 1) it looks to see if it's a native binary executable file. If it is, it loads and runs it. 1b) ??? Hmm... what about compatibility modes and such ??? I assume it recognizes "compatibility-mode" executables and then DTRT to execute them. (Is something like this going on for FreeBSD's elf compatibility?) 2) If it wasn't a binary executable file, it assumes it's a script file of some sort, and reads the first line looking for a "shebang" (#!) comment to say which interperter to use to run the script. If it finds one, it starts the specified interpreter w/ the script file as it's input. 2b) If there wasn't a shebang line, assume it's a Bourne shell script and start up "sh" with the file as its input. If we're going to get into things like being able to execute java files "directly", ie, having the kernel recognize that it is a java file and automatically invoking the appropriate java interpreter code, "we" (by which I mean whoever writes this thing), we will need to have it hooked in in the 1b) area above. But if we're going to add a bit to recognize java code and automatically invoke the appropriate interpreter, shouldn't we consider that we may eventually want something similar for some other file type? Shouldn't we make it a bit more general? Now, I don't know of all the details, about when various file sytems become available during the boot process, etc. But for a very rough first cut, consider something sort of like this as a strawman that can be kicked about, disected and probed for any useful bits: Suppose that at some point during the boot process (or after boot as part of a loadable kernel module?), the kernel reads and loads into a table in memory a file /etc/interpreters, which contains magic-number/interpreter pairs. Then we add to the above kernel-execution process a 1c) the kernel compares the file with the magic-numbers in the magic-number/interpreter table to see if it is a recognized interpretable file type. If a match is found, it invokes the matching interpreter and feeds the file to the interpreter. Something like this would give us the ability to run java files directly, and also any other magic tagged files that one deems useful in the future. (Hmm... maybe this is starting down that slippery slope of identifying all kinds of different file types with their appropriate application uses to run/read/handle them ala MacOS or Windows. YUCK! Well, what I'm suggesting here would only work for files marked as executable, and would hopefully be limited to some small select set.) Now, the table will have to be loaded at/near boot time, or when the kernel is poked by some external event/signal/etc, 'cause we definitely do _not_ want the kernel to have to read this /etc/interpreters file (or even look to see if it has changed) each time it tries to execute a file that isn't a native binary. Well, anyway, there's my $0.02 on the subject. Or maybe it's only worth $0.00000002. (Or maybe even -$0.02?) But if anyone's going to look into this, feel free to take these ideas and kick them about and see if there is anything of worth in them that might be useful. ________________________________________________________________________ Dr. William R. Somsky somsky@phys.washington.edu Department of Physics, Box 351560 B432 Physics-Astro Bldg Univ. of Washington, Seattle WA 98195-1560 206/616-2954 From owner-freebsd-hackers Fri Feb 28 11:12:41 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id LAA12275 for hackers-outgoing; Fri, 28 Feb 1997 11:12:41 -0800 (PST) Received: from alpha.xerox.com (alpha.Xerox.COM [13.1.64.93]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id LAA11979 for ; Fri, 28 Feb 1997 11:08:36 -0800 (PST) Received: from www.sdsp.mc.xerox.com ([13.231.132.18]) by alpha.xerox.com with SMTP id <16352(2)>; Fri, 28 Feb 1997 11:06:59 PST Received: from gnu.sdsp.mc.xerox.com (gnu.sdsp.mc.xerox.com [13.231.133.90]) by www.sdsp.mc.xerox.com (8.8.5/8.8.5) with SMTP id OAA21169; Fri, 28 Feb 1997 14:08:40 -0500 (EST) Received: by gnu.sdsp.mc.xerox.com (4.1/client-1.3) id AA21759; Fri, 28 Feb 97 14:08:24 EST Message-Id: <9702281908.AA21759@gnu.sdsp.mc.xerox.com> X-Mailer: exmh version 2.0gamma 1/27/96 To: mika ruohotie Cc: hfwirth@ping.at (Helmut F. Wirth), freebsd-hackers@freebsd.org Subject: Re: Pentium MMX Extensions, Changes to (g)as and gdb In-Reply-To: Your message of "Thu, 27 Feb 1997 01:23:10 PST." <199702270923.LAA07796@shadows.aeon.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 28 Feb 1997 11:08:18 PST From: "Marty Leisner" Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Can the alpha gdb's on ftp.cygnus.com be built on freebsd? I've tried for about 6 months and its hasn't seemed to work very well... -- marty leisner@sdsp.mc.xerox.com The Feynman problem solving Algorithm 1) Write down the problem 2) Think real hard 3) Write down the answer Murray Gel-mann in the NY Times From owner-freebsd-hackers Fri Feb 28 13:25:14 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id NAA18769 for hackers-outgoing; Fri, 28 Feb 1997 13:25:14 -0800 (PST) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id NAA18763 for ; Fri, 28 Feb 1997 13:25:08 -0800 (PST) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id WAA06973 for hackers@freebsd.org; Fri, 28 Feb 1997 22:24:34 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.8.5/8.8.5) id WAA26606; Fri, 28 Feb 1997 22:10:02 +0100 (MET) Message-ID: Date: Fri, 28 Feb 1997 22:10:02 +0100 From: j@uriah.heep.sax.de (J Wunsch) To: hackers@freebsd.org Subject: Re: Ethernet options on 2.2-GAMMA References: <199702260046.BAA09889@ocean.campus.luth.se> X-Mailer: Mutt 0.55-PL10 Mime-Version: 1.0 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199702260046.BAA09889@ocean.campus.luth.se>; from Mikael Karpberg on Feb 26, 1997 01:46:30 +0100 Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk As Mikael Karpberg wrote: > Speaking of the floppy being available again... > One BADLY missed option sometimes is the "Start holographic shell" option > in the main menu. It'd be really nice to be able to get a shell first thing, > and be able to start the install after doing initial work. It's all there already. :-)) In case you wonder, it's one of the three possible choices if you select `Fixit' now: 1) use the second ``live'' CD-ROM, 2) use a fixit floppy, 3) (Re-)start the EHS. -- 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-hackers Fri Feb 28 13:25:18 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id NAA18788 for hackers-outgoing; Fri, 28 Feb 1997 13:25:18 -0800 (PST) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id NAA18777 for ; Fri, 28 Feb 1997 13:25:15 -0800 (PST) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id WAA06994 for hackers@freebsd.org; Fri, 28 Feb 1997 22:25:11 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.8.5/8.8.5) id WAA26639; Fri, 28 Feb 1997 22:20:27 +0100 (MET) Message-ID: Date: Fri, 28 Feb 1997 22:20:27 +0100 From: j@uriah.heep.sax.de (J Wunsch) To: hackers@freebsd.org Subject: Re: migrating 2.1.7 -> 2.2: simple or hairy? References: X-Mailer: Mutt 0.55-PL10 Mime-Version: 1.0 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: ; from Chris Coleman on Feb 26, 1997 08:11:59 -0800 Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk As Chris Coleman wrote: > What about the kernel, does sup install new kernel files? > New GENERIC, or LINT? > > Does make world install a new GENERIC kernel? No, No, No, and No. :-) -- 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-hackers Fri Feb 28 13:58:08 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id NAA20334 for hackers-outgoing; Fri, 28 Feb 1997 13:58:08 -0800 (PST) Received: from plains.nodak.edu (plains.NoDak.edu [134.129.111.64]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id NAA20326 for ; Fri, 28 Feb 1997 13:58:05 -0800 (PST) Received: (from tinguely@localhost) by plains.nodak.edu (8.8.4/8.8.3) id PAA20337; Fri, 28 Feb 1997 15:57:36 -0600 (CST) Date: Fri, 28 Feb 1997 15:57:36 -0600 (CST) From: Mark Tinguely Message-Id: <199702282157.PAA20337@plains.nodak.edu> To: dg@root.com, terry@lambert.org Subject: Re: Assumptions about kmem_malloc()... Cc: hackers@freebsd.org, jpt@msc.edu Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > Why doesn't it push pages around to get a contiguous space so that > it won't fail? that would work if everything is swappable. It is hard to fight those holes when drivers that need wired contigous memory come and go through lkm loads/unloads. Most driver allocations would puke if their memory got moved unless we go to a double pointer arrangement, but (aaaaaaaaaahhhhhgg) I would not have to be the one to have to debug VM problems). --mark. From owner-freebsd-hackers Fri Feb 28 14:38:32 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id OAA22146 for hackers-outgoing; Fri, 28 Feb 1997 14:38:32 -0800 (PST) Received: from aries.bb.cc.wa.us (root@[208.8.136.11]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id OAA22141 for ; Fri, 28 Feb 1997 14:38:30 -0800 (PST) Received: from localhost (chris@localhost) by aries.bb.cc.wa.us (8.8.3/8.6.9) with SMTP id OAA18619; Fri, 28 Feb 1997 14:37:02 -0800 (PST) Date: Fri, 28 Feb 1997 14:37:02 -0800 (PST) From: Chris Coleman Reply-To: Chris Coleman To: Joerg Wunsch cc: hackers@freebsd.org Subject: Re: migrating 2.1.7 -> 2.2: simple or hairy? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Fri, 28 Feb 1997, J Wunsch wrote: > As Chris Coleman wrote: > > > What about the kernel, does sup install new kernel files? What about /usr/src/sys files, are they updated? > > New GENERIC, or LINT? > > > > Does make world install a new GENERIC kernel? > > No, No, No, and No. :-) This is good :-), but how do I get new kernel files? Before I have just been using my old ones and adding lines that i find useful later, but I think It would be useful to get a new LINT file once in a while to keep up. Does it cause any problems if I let the kernel get out of date and keep upgrading the system binaries with "make world" ? For example I have my kernel at 2.1.5-RELEASE and I sup the -current or -stable tree and make world. Am I forced to rebuild the kernel becuase the binaries have changed? Sorry to be so picky, but It makes a difference when trying to upgrade properly. thanks so much. |Chris > -- > 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. ;-) > Christopher J. Coleman (chris@aries.bb.cc.wa.us) Computer Support Technician I (509)-766-8873 Big Bend Community College Internet Instructor FreeBSD Book Project: http://www.bb.cc.wa.us/~chris/book.html I may Be inaffective, but atleast I am good at it. From owner-freebsd-hackers Fri Feb 28 14:42:41 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id OAA22341 for hackers-outgoing; Fri, 28 Feb 1997 14:42:41 -0800 (PST) Received: from atlantis.ping.at (a013.static.Vienna.AT.EU.net [193.154.186.13]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id OAA22333 for ; Fri, 28 Feb 1997 14:42:34 -0800 (PST) Received: from atlantis (localhost.ping.at [127.0.0.1]) by atlantis.ping.at (8.7.6/8.6.12) with SMTP id XAA04354; Fri, 28 Feb 1997 23:42:31 +0100 (MET) Message-ID: <33175F57.41C67EA6@ping.at> Date: Fri, 28 Feb 1997 23:42:31 +0100 From: "Helmut F. Wirth" X-Mailer: Mozilla 3.0 (X11; I; FreeBSD 2.1.7-RELEASE i386) MIME-Version: 1.0 To: freebsd-hackers@FreeBSD.ORG Subject: Changes to gas and gdb for MMX instructions Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Hello, As I promised, the changes to gas and gdb are ready. I submitted the patches and some documentation via send-pr today. If there is enough interest I could post the patches to this list too, so you could give it a try. If you are interested in information regarding the new MMX instructions you can find the Developers Manual, the Programmers Reference Manual, some Application Notes and other useful information at Intel's web site: URL hhtp://developer.intel.com/drg/mmx/ I used the material from this site for my changes. Regards Helmut From owner-freebsd-hackers Fri Feb 28 14:44:15 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id OAA22492 for hackers-outgoing; Fri, 28 Feb 1997 14:44:15 -0800 (PST) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.50]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id OAA22484 for ; Fri, 28 Feb 1997 14:44:13 -0800 (PST) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id PAA02461; Fri, 28 Feb 1997 15:39:32 -0700 From: Terry Lambert Message-Id: <199702282239.PAA02461@phaeton.artisoft.com> Subject: Re: Assumptions about kmem_malloc()... To: tinguely@plains.nodak.edu (Mark Tinguely) Date: Fri, 28 Feb 1997 15:39:32 -0700 (MST) Cc: dg@root.com, terry@lambert.org, hackers@freebsd.org, jpt@msc.edu In-Reply-To: <199702282157.PAA20337@plains.nodak.edu> from "Mark Tinguely" at Feb 28, 97 03:57: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-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > Why doesn't it push pages around to get a contiguous space so that > > it won't fail? > > that would work if everything is swappable. It is hard to fight those holes > when drivers that need wired contigous memory come and go through lkm > loads/unloads. > > Most driver allocations would puke if their memory got moved unless we go > to a double pointer arrangement, but (aaaaaaaaaahhhhhgg) I would not have > to be the one to have to debug VM problems). The kernel is an virtual-to-physical address space map, isn't it? You wouldn't need to introduce "handles" to do it, I think. It's not the kernel eating all the physical memory anyway. 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-hackers Fri Feb 28 15:08:34 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id PAA24136 for hackers-outgoing; Fri, 28 Feb 1997 15:08:34 -0800 (PST) Received: from plains.nodak.edu (tinguely@plains.NoDak.edu [134.129.111.64]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id PAA24130 for ; Fri, 28 Feb 1997 15:08:29 -0800 (PST) Received: (from tinguely@localhost) by plains.nodak.edu (8.8.4/8.8.3) id RAA25795; Fri, 28 Feb 1997 17:08:18 -0600 (CST) Date: Fri, 28 Feb 1997 17:08:18 -0600 (CST) From: Mark Tinguely Message-Id: <199702282308.RAA25795@plains.nodak.edu> To: terry@lambert.org Subject: Re: Assumptions about kmem_malloc()... Cc: dg@root.com, hackers@freebsd.org, jpt@msc.edu Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > The kernel is an virtual-to-physical address space map, isn't it? You > wouldn't need to introduce "handles" to do it, I think. I agree most kernel operations do not need wired contiguous physical memory, a virtual contiguous would suit most operations. I was thinking of the device drivers that require a physical contiguous address (or in the case of the IDT ATM card it requires several physical addresses of contiguous buffer addresses) programmed into it for long-term DMA. It seems to me, that with our new devices using host memory to save board costs, we need larger and larger chunks of contiguous physical memory because the DMA can't page fault a missing virtual page. > > It's not the kernel eating all the physical memory anyway. agreed, but as we allocate/release smaller chunks of physical unwired memory for DMA operations, can we keep the holes large enough for future allocations? --mark. From owner-freebsd-hackers Fri Feb 28 15:40:17 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id PAA26169 for hackers-outgoing; Fri, 28 Feb 1997 15:40:17 -0800 (PST) Received: from obiwan.aceonline.com.au (obiwan.aceonline.com.au [203.103.90.67]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id PAA26159; Fri, 28 Feb 1997 15:40:12 -0800 (PST) Received: from localhost (adrian@localhost) by obiwan.aceonline.com.au (8.8.5/8.8.5) with SMTP id NAA01571; Sat, 1 Mar 1997 13:42:50 +0800 (WST) Date: Sat, 1 Mar 1997 13:42:50 +0800 (WST) From: Adrian Chadd To: Warner Losh cc: questions@freebsd.org, hackers@freebsd.org Subject: Re: Java binary support in FreeBSD ... In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Fri, 28 Feb 1997, Warner Losh wrote: > If you go off and do this, it might not be bad to make this > generalized so that I can run my old CP/M programs through the z80 > emulator that I have laying around, or the MS-DOS programs through > DOSEMU or whatever. > > Warner > Again - its just one file (imgact_java.c) which has the code to recognise java binaries, and then do some magic to execute it with the right interpreter and command args, etc. Extending it to cover DOS binaries, etc, wouldn't be hard (for dos .EXE Dont' you look for 'MZ' at the beginning of the file? Com files will be different, since they are just an image of a segment of code to throw in memory, with no real discernable headers. Anyways, back to work. Adrian. From owner-freebsd-hackers Fri Feb 28 15:50:00 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id PAA26655 for hackers-outgoing; Fri, 28 Feb 1997 15:50:00 -0800 (PST) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.50]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id PAA26649 for ; Fri, 28 Feb 1997 15:49:54 -0800 (PST) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id QAA02574; Fri, 28 Feb 1997 16:45:20 -0700 From: Terry Lambert Message-Id: <199702282345.QAA02574@phaeton.artisoft.com> Subject: Re: Assumptions about kmem_malloc()... To: tinguely@plains.nodak.edu (Mark Tinguely) Date: Fri, 28 Feb 1997 16:45:20 -0700 (MST) Cc: terry@lambert.org, dg@root.com, hackers@freebsd.org, jpt@msc.edu In-Reply-To: <199702282308.RAA25795@plains.nodak.edu> from "Mark Tinguely" at Feb 28, 97 05:08:18 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-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > The kernel is an virtual-to-physical address space map, isn't it? You > > wouldn't need to introduce "handles" to do it, I think. > > I agree most kernel operations do not need wired contiguous physical memory, > a virtual contiguous would suit most operations. I was thinking of the device > drivers that require a physical contiguous address (or in the case of the > IDT ATM card it requires several physical addresses of contiguous buffer > addresses) programmed into it for long-term DMA. It seems to me, that with > our new devices using host memory to save board costs, we need larger and > larger chunks of contiguous physical memory because the DMA can't page fault > a missing virtual page. > > > > > It's not the kernel eating all the physical memory anyway. > > agreed, but as we allocate/release smaller chunks of physical unwired memory > for DMA operations, can we keep the holes large enough for future allocations? The reason I mentioned the virtual mapping is that it's possible to move everything virtual around in physical pages in order to create contiguous memory regions. Because of the reverse lookup problem, this would be generally useful only if the allocated regions were held for a relatively long time, once allocated. In effect, the reverse lookup and the space mapping act as a handle already. It's shuffling the mappings, and doing the physical page copies before the shuffle is put into effect that is the hard part. When an I/O request from a user process is DMA'ed in on an ISA machine with more than 16M of memory, it must always be bounced because the user address space may have been swapped, and if it were paged in for the write to the process space, then the page may find it has moved to high memory. Maybe it's time to look at preferential page location as an attribute of the request to page in? 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-hackers Fri Feb 28 16:33:24 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id QAA29778 for hackers-outgoing; Fri, 28 Feb 1997 16:33:24 -0800 (PST) Received: from odin.visigenic.com (odin.visigenic.com [204.179.98.2]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id QAA29769 for ; Fri, 28 Feb 1997 16:33:20 -0800 (PST) Received: from VSI48 (vsi48.visigenic.com [206.64.15.185]) by odin.visigenic.com (Netscape Mail Server v2.02) with SMTP id AAA11378; Fri, 28 Feb 1997 16:30:13 -0800 Message-Id: <3.0.32.19970228163329.00ac4480@visigenic.com> X-Sender: toneil@visigenic.com X-Mailer: Windows Eudora Pro Version 3.0 (32) Date: Fri, 28 Feb 1997 16:33:29 -0800 To: Adrian Chadd From: "Tim Oneil" Subject: Re: Java binary support in FreeBSD ... Cc: hackers@FreeBSD.ORG Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk At 01:42 PM 3/1/97 +0800, you wrote: >Extending it to cover DOS binaries, etc, wouldn't be hard (for dos .EXE >Dont' you look for 'MZ' at the beginning of the file? Com files will be >different, since they are just an image of a segment of code to throw in >memory, with no real discernable headers. Its more than looking for the executable module signature of DOS binaries, isn't it? I mean, DOS binaries have some pretty funky and backward memory management requirements. You've got to create a virtual chunk of so-called "real memory" for it, becuase dos will load an address selector/offset, turn around and do something else in its brief, broken, sickly way that only it can manage, then come back to that selector and due to the ravages (to DOS) of virtual memory management, suddenly find what it expected to be in that selector gone, and break. I mean, theres just a whole lot more to emulating DOS than that. From owner-freebsd-hackers Fri Feb 28 16:41:27 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id QAA00398 for hackers-outgoing; Fri, 28 Feb 1997 16:41:27 -0800 (PST) Received: from obiwan.aceonline.com.au (obiwan.aceonline.com.au [203.103.90.67]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id QAA00391 for ; Fri, 28 Feb 1997 16:41:20 -0800 (PST) Received: from localhost (adrian@localhost) by obiwan.aceonline.com.au (8.8.5/8.8.5) with SMTP id OAA01928; Sat, 1 Mar 1997 14:44:29 +0800 (WST) Date: Sat, 1 Mar 1997 14:44:28 +0800 (WST) From: Adrian Chadd To: Tim Oneil cc: hackers@FreeBSD.ORG Subject: Re: Java binary support in FreeBSD ... In-Reply-To: <3.0.32.19970228163329.00ac4480@visigenic.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk This is LOOKING for the binary. Once you know you have a .EXE, you stick it into the dos emulator and let IT do the rest. :) Adrian. On Fri, 28 Feb 1997, Tim Oneil wrote: > At 01:42 PM 3/1/97 +0800, you wrote: > >Extending it to cover DOS binaries, etc, wouldn't be hard (for dos .EXE > >Dont' you look for 'MZ' at the beginning of the file? Com files will be > >different, since they are just an image of a segment of code to throw in > >memory, with no real discernable headers. > > Its more than looking for the executable module signature of DOS binaries, > isn't it? I mean, DOS binaries have some pretty funky and backward memory > management requirements. You've got to create a virtual chunk of so-called > "real memory" for it, becuase dos will load an address selector/offset, > turn around and do something else in its brief, broken, sickly way that > only it can manage, then come back to that selector and due to the > ravages (to DOS) of virtual memory management, suddenly find what it > expected to be in that selector gone, and break. I mean, theres just > a whole lot more to emulating DOS than that. > > From owner-freebsd-hackers Fri Feb 28 17:20:51 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id RAA02053 for hackers-outgoing; Fri, 28 Feb 1997 17:20:51 -0800 (PST) Received: from dg-rtp.dg.com (dg-rtp.rtp.dg.com [128.222.1.2]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id RAA02042 for ; Fri, 28 Feb 1997 17:20:42 -0800 (PST) Received: by dg-rtp.dg.com (5.4R3.10/dg-rtp-v02) id AA02248; Fri, 28 Feb 1997 20:20:05 -0500 Received: from ponds by dg-rtp.dg.com.rtp.dg.com; Fri, 28 Feb 1997 20:20 EST Received: from lakes.water.net (lakes [10.0.0.3]) by ponds.water.net (8.8.3/8.7.3) with ESMTP id TAA11907; Fri, 28 Feb 1997 19:55:42 -0500 (EST) Received: (from rivers@localhost) by lakes.water.net (8.8.3/8.6.9) id UAA05470; Fri, 28 Feb 1997 20:01:01 -0500 (EST) Date: Fri, 28 Feb 1997 20:01:01 -0500 (EST) From: Thomas David Rivers Message-Id: <199703010101.UAA05470@lakes.water.net> To: ponds!lakes.water.net!rivers, ponds!lambert.org!terry Subject: Re: Another installment of the "dup alloc"/"bad dir" panic problems. Cc: ponds!freebsd.org!hackers Content-Type: text Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Terry Lambert writes: > > > If you recall; I could trash a particular inode; run newfs and discover > > the inode was not properly zero'd out (sometimes) although I had > > verified that the write() for that particular block, with a buffer > > full of zeros, had been issued. > > > > It now appears that having the printf()s in disksort() affects the problem > > in a positive manner (that is, I'm not able to demonstrate the previous > > "non-writing" behaviour I had seen; the inode in question is reliably > > filled with zeros.) > > > > I'm not sure what this means; does it point to some critical timing > > situation required for causing the problem? Does it point to missing > > splXXX() call... would anyone care to comment? > > Are you running IDE? > > If so, is your IDE controller an RZ1000 or a CMB640b? > > Both of these are known to fail undectably if they get an interrupt > during a transfer operation. Your printf's would "fix" this by > allowing the transfer to complete by delaying the operation (probably > significantly delaying it, in fact). I have always been suspicious > that the FreeBSD IDE driver "never exhibited the bug", even though > no special steps were taken in coding it. > Yes, I wish it was that, I'd love to be done with this :-) However, this particular reproduction of the dup-alloc problem is with an AHA 1542B and Micropolis ~500meg drive... So, now the question I'm considering is "what could be some timing dependent that it affects both IDE and SCSI drivers?" - Dave Rivers - From owner-freebsd-hackers Fri Feb 28 17:34:46 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id RAA02764 for hackers-outgoing; Fri, 28 Feb 1997 17:34:46 -0800 (PST) Received: from rah.star-gate.com (rah.star-gate.com [204.188.121.18]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id RAA02749 for ; Fri, 28 Feb 1997 17:34:41 -0800 (PST) Received: from rah.star-gate.com (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.8.5/8.7.3) with ESMTP id RAA12119; Fri, 28 Feb 1997 17:34:47 -0800 (PST) Message-Id: <199703010134.RAA12119@rah.star-gate.com> X-Mailer: exmh version 1.6.9 8/22/96 To: Mark Mayo cc: hackers@FreeBSD.ORG Subject: Re: CTPPRO? In-reply-to: Your message of "Wed, 26 Feb 1997 17:35:46 EST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 28 Feb 1997 17:34:47 -0800 From: Amancio Hasty Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk I would first write a userland program to experiment with. Then I would move the code to the console driver thats because thats where the X server interfaces to the kernel to change the scan codes, etc.. so it is a natural place to put this sort of code in . Is just that for future reference with respect to the X server it is kind of nice to have all the code which requires kernel support to be in one module. Regards, Amancio >From The Desk Of Mark Mayo : > On Sun, 23 Feb 1997, Amancio Hasty wrote: > > > > > Hi, > > > > I found a device driver called perfmon in -current. It can read the > > model specific registers and write them (rdmsr and wrmsr). > > Additionally, if you search the web for Intel Secrets and look up > > Pentium Pro Family Developer's Manual in Appendix C it has a description > > for the Model specific registers. The filename is 242692_1.pdf . > > Got it. I'll peek at Appendix C. > > > > > I think that these are all the bits that we need to implement fastvid 8) > > > > I gave the code for ctppro.pas to my friend who will translate for us - > should have the english version back real soon. > > So do you think we should do this in userland through /dev/io, or write a > device driver that fires up the correct registers during bootup? > > -Mark > > > > > Enjoy, > > Amancio > > > > > > > > > > > > ---------------------------------------------------------------------------- > Mark Mayo mark@quickweb.com > RingZero Comp. http://vinyl.quickweb.com/mark > ---------------------------------------------------------------------------- > Nature shows that with the growth of intelligence comes increased capacity > for pain, and it is only with the highest degree of intelligence that > suffering reaches its supreme point. -- Arthur Schopenhauer > From owner-freebsd-hackers Fri Feb 28 17:54:20 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id RAA03688 for hackers-outgoing; Fri, 28 Feb 1997 17:54:20 -0800 (PST) Received: from pegasus.rutgers.edu (pegasus.rutgers.edu [128.6.10.45]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id RAA03596 for ; Fri, 28 Feb 1997 17:51:24 -0800 (PST) Received: from hell ([165.230.177.4]) by pegasus.rutgers.edu (8.6.12+bestmx+oldruq+newsunq/8.5) with SMTP id UAA09626; Fri, 28 Feb 1997 20:50:44 -0500 Message-Id: <3.0.1.32.19970228205137.00922200@pegasus.rutgers.edu> X-Sender: paradox@pegasus.rutgers.edu X-Mailer: Windows Eudora Pro Version 3.0.1 (32) Date: Fri, 28 Feb 1997 20:51:37 -0500 To: hackers@freebsd.org From: Red Barchetta Subject: DOS binary support for FreeBSD Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Is anyone currently working on adding DOS binary support to FreeBSD? If not (hell, even if so!) I am interested in taking a shot at this project. If anyone can give me some suggestions regarding the specifics involved in this task (i.e. what must be done at the system level to allow a DOS program to run under FreeBSD) and maybe some references to relevant materials (online or offline), it would be much appreciated. I intend to look through the code for the "PCEMU" port, but I imagine it won't be of *too* much use since its main purpose appears to be to emulate DOS on non-Intel architectures. Thanks! Ernie Pistor From owner-freebsd-hackers Fri Feb 28 18:07:38 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id SAA04130 for hackers-outgoing; Fri, 28 Feb 1997 18:07:38 -0800 (PST) Received: from obiwan.aceonline.com.au (obiwan.aceonline.com.au [203.103.90.67]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id SAA04125 for ; Fri, 28 Feb 1997 18:07:33 -0800 (PST) Received: from localhost (adrian@localhost) by obiwan.aceonline.com.au (8.8.5/8.8.5) with SMTP id QAA00275 for ; Sat, 1 Mar 1997 16:10:39 +0800 (WST) Date: Sat, 1 Mar 1997 16:10:39 +0800 (WST) From: Adrian Chadd To: freebsd-hackers@freebsd.org Subject: Re : java support under FreeBSD. Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk hi. Just a quick question bout something I'm trying to do to get Java to run under FreeBSD. Basically I'm looking at the source for imgact_shell.c and I've got it to recognise a java binary, doing the sysctl stuff, etc, but I fail to see how you can play with the argc and environment space. When you execute a java class, the interpreter expects the NAME of the class, not the path. So I have to crreate a new classpath every time I run the interpreter. That bit is easy. The hard bit is deciding where to put it. I can either set an environment variable CLASSPATH everytime, or on the command line do this : java -classpath /usr/local/java/classes.zip:/path/to/java/class classname or just set the envir variable CLASSPATH. Now I don't know which overrides which, or if they augment each other, but I do know that if I set the env variable then the user wont' be able to override it, which may or may not be a good thing. Question is, how would I do either? :) Thanks. Adrian. From owner-freebsd-hackers Fri Feb 28 19:51:06 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id TAA07045 for hackers-outgoing; Fri, 28 Feb 1997 19:51:06 -0800 (PST) Received: from parkplace.cet.co.jp (parkplace.cet.co.jp [202.32.64.1]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id TAA07036 for ; Fri, 28 Feb 1997 19:51:03 -0800 (PST) Received: from localhost (michaelh@localhost) by parkplace.cet.co.jp (8.8.5/CET-v2.1) with SMTP id DAA16099; Sat, 1 Mar 1997 03:50:54 GMT Date: Sat, 1 Mar 1997 12:50:53 +0900 (JST) From: Michael Hancock To: Thomas David Rivers cc: FreeBSD Hackers Subject: Re: Another installment of the "dup alloc"/"bad dir" panic problems. In-Reply-To: <199703010101.UAA05470@lakes.water.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Fri, 28 Feb 1997, Thomas David Rivers wrote: > > > It now appears that having the printf()s in disksort() affects the problem > > > in a positive manner (that is, I'm not able to demonstrate the previous > > > "non-writing" behaviour I had seen; the inode in question is reliably > > > filled with zeros.) The old "printf's makes the problem go away effect". I hate when that happens. ;-) Can you do a gcc -v and show us the flags you use to compile the kernel? If missed these, in case you've already posted them. Regards, Mike From owner-freebsd-hackers Fri Feb 28 19:53:51 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id TAA07198 for hackers-outgoing; Fri, 28 Feb 1997 19:53:51 -0800 (PST) Received: from crh.cl.msu.edu (crh.cl.msu.edu [35.8.1.24]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id TAA07193 for ; Fri, 28 Feb 1997 19:53:48 -0800 (PST) Received: (from henrich@localhost) by crh.cl.msu.edu (8.8.5/8.8.4) id WAA08081 for freebsd-hackers@freebsd.org; Fri, 28 Feb 1997 22:53:44 -0500 (EST) From: Charles Henrich Message-Id: <199703010353.WAA08081@crh.cl.msu.edu> Subject: ALR information tools? To: freebsd-hackers@freebsd.org Date: Fri, 28 Feb 1997 22:53:44 -0500 (EST) X-Mailer: ELM [version 2.4ME+ PL22 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Has anyone managed to reverse engineer or find some tools to read the ALR system information (cpu temp, fan speeds etc..) somehow? -Crh Charles Henrich Michigan State University henrich@msu.edu http://pilot.msu.edu/~henrich From owner-freebsd-hackers Fri Feb 28 20:12:23 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id UAA07978 for hackers-outgoing; Fri, 28 Feb 1997 20:12:23 -0800 (PST) Received: from pdx1.world.net (pdx1.world.net [192.243.32.18]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id UAA07967 for ; Fri, 28 Feb 1997 20:12:17 -0800 (PST) Received: from suburbia.net (suburbia.net [203.4.184.1]) by pdx1.world.net (8.7.5/8.7.3) with SMTP id UAA11494 for ; Fri, 28 Feb 1997 20:13:28 -0800 (PST) Received: (qmail 2761 invoked by uid 110); 1 Mar 1997 04:10:50 -0000 MBOX-Line: From owner-netdev@roxanne.nuclecu.unam.mx Sat Mar 01 03:11:01 1997 remote from suburbia.net Delivered-To: proff@suburbia.net Received: (qmail 16480 invoked from network); 1 Mar 1997 03:10:43 -0000 Received: from roxanne.nuclecu.unam.mx (132.248.29.2) by suburbia.net with SMTP; 1 Mar 1997 03:10:43 -0000 Received: (from root@localhost) by roxanne.nuclecu.unam.mx (8.6.12/8.6.11) id UAA11742 for netdev-outgoing; Fri, 28 Feb 1997 20:29:48 -0600 Received: from caipfs.rutgers.edu (caipfs.rutgers.edu [128.6.37.100]) by roxanne.nuclecu.unam.mx (8.6.12/8.6.11) with ESMTP id UAA11736 for ; Fri, 28 Feb 1997 20:29:39 -0600 Received: from jenolan.caipgeneral (jenolan.rutgers.edu [128.6.111.5]) by caipfs.rutgers.edu (8.8.5/8.8.5) with SMTP id VAA19774 for ; Fri, 28 Feb 1997 21:27:10 -0500 (EST) Received: by jenolan.caipgeneral (SMI-8.6/SMI-SVR4) id VAA08431; Fri, 28 Feb 1997 21:26:57 -0500 Date: Fri, 28 Feb 1997 21:26:57 -0500 Message-Id: <199703010226.VAA08431@jenolan.caipgeneral> From: "David S. Miller" To: netdev@roxanne.nuclecu.unam.mx Subject: overview of socket hashing changes, plus new patch Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Eric Schenk pointed out some problems to me that caused IP transparent proxy to not even compile, this is believed to be fixed and it should actually work. Fetch the new patch from: vger.rutgers.edu:/pub/linux/Net/patches/fordyson2.diff.gz A brief overview of the changes, with some insight into my design decisions where applicable: 1) Anything referring to SOCK_ARRAY_SIZE and code which used that was essentially just deleted. 2) Socket demultiplexing, I determined, was a per protocol problem. Therefore I added the following methods to struct proto: void hash(struct sock *sk) This is where a socket is added to a protocols lookup tables, the method by which this is done and the tables used are completely opaque to the af_inet/af_inet6 code, it really doesn't care how you arrange things. For example if you wanted to use a DP trie for TCP sockets (I considered this approach, but decided against it, see below) the callers simply would not care. void unhash(struct sock *sk) This removes a sock from the protocols lookup tables. void rehash(struct sock *sk) Here we get called when the "identity" of a sock has changed in some way, yet it still exists and lookups should find it just fine. The theory here is that a quick routine needs to be present when we just change the address/port elements of a sock, since the hash is probably different then. unsigned short good_socknum(unsigned short base) The idea here is that a protocol knows best how to choose the best possible port number. For example, it can exploit some properties of it's lookup tables and thus choose a port which will seed better in those tables. int verify_bind(struct sock *sk, unsigned short snum) This just verifies that attaching SK to the passed local port is "ok" and doesn't conflict with any other existing connection in that protocol. To aide in the support of these things two elements were added to struct sock: struct sock **hashtable; int hashent; This allows the af_inet code to do things more freely and only force it to call the rehash routine after all of it's identity changes have been completed. This way the per protocol hashing code, during a rehash, can easily find where the sock was beforehand even though the new hash computation might be different. Alas it was found that there still needed to exist a way to walk the entire socket list. But happily, this is only needed in one place, the procfs stuff. So who cares ;-) This was implemented by adding: struct sock *sklist_next, *sklist_prev; to the front of both struct sock and struct proto. 3) Socket hash table protection. It is very simple, when things need to be changed, a BH atomic section is entered. For the lookup code, during incoming packet processing, since you know you are running within a BH you can safely avoid even doing this and run full speed with no locking. Eric Schenk has informed me that he thinks this can be made to scream for fine grained SMP as well. This is good. 4) The af_inet code was fast pathed, and some special cases were completely removed. The code is generally much cleaner now and easier to understand. In particular the RAW protocols for v4 and v6 were given their own bind method, eliminating a lot of excess comparisons in the af_inet bind code. The implementations: SOCK_RAW They did not need the full 256 entry hash tables they previously did. The size of the hash was chosen to be MAX_INET_PROTOS, this simplified and speeded up the raw packet delivery. The hash is on sk->num, simple, stupid, nothing fancy necessary at all. SOCK_PACKET No lookups, in the sense we are discussing here, are even ever necessary. Therefore this protocol lacks a table and also lacks the hash methods etc. SOCK_UDP The algorithm is the same as previous, hash on the local port number. For UDP the one behind sock cache was retained as for UDP there are two things to exploit: 1) Nearly all UDP sockets on a system are wildcarded out the wazoo, so hashing on anything other than the local port will only make it more complex and cause the lookups to take longer. 2) Numerous research papers and studies have shown that the one behind UDP socket cache can have hit rates approaching %80, this is the main reason it was in fact retained. SOCK_TCP Ok, this one is a doozy, and it was the incentive behind all of this work I did, hold on to your seats. There are some nice properties about TCP which you can exploit, in particular: 1) The overwhelming majority of TCP sockets have a full identity, that is they are completely bound to a unique [local address, local port], [foreign address, foreign port] identity. Furthermore, the only TCP sockets which possess wildcards and can get hit during a demultiplex for an incoming packet are those in the listening state, we exploit this heavily. 2) And for these listening connections, due to limitations in the BSD sockets API, only the local address and port can be non-wildcard. The foreign port and address can never be bound to anything for listening TCP socket, so don't even bother checking for it. Note the protocol does allow for a listening socket to be bound, yet as stated the API lacks any way in which you can actually do this. With that in mind, there are three hash tables for TCP sockets. One for LISTENING sockets, one for sockets with a full identity yet not dead/TCP_CLOSE, and one further hash whose purpose will be described shortly. Sockets in the full identity hash are hashed based upon all four of laddr, lport, faddr, fport. This seems to hash the tables rather nicely. Listening sockets are only hashed based upon the local port, since this is the only thing we can guarentee is not wildcarded, in fact as just stated we in fact know that the foreign port and address are wildcarded. The algorithm for incoming socket lookup is essentially: 1) Try to find perfect match in established hash table. 2) If nothing found, look in listening table for closest match. Step (1) need only check for perfect matches (that is all it could ever find in there!), and step (2) need only prioritize a lookup by "local port and local address match" then "local port match, yet local address wildcarded". And this is all you need to check. Possible improvement for the listening lookups. When we add a socket to the listening hash (rare occurrance, does not happen all that often, except for ftp clients in non-passive mode) we look for a "perfect listener" on our selected port. If one is found, we place ourselves after him. The lookup code for the listening case can thus be simplified to return the first socket where the local port matches, and this will always be correct due the way in which we have layed things out. Ok, that made incoming packet demultiplexing scale extremely well. Let's see how I covered some other issues where performance sucked previously. TCP timers, one was tricky to solve the other was simple. Every 75 seconds the keepalive timer goes off and previously (FreeBSD does this as well, but much worse, I'll describe this is mass detail later) the entire socket list was walked to find TCP's which need a keepalive probe sent. The fix here is to walk the established hash chains 4 times every 75 seconds. Each time only examining 1/4 of the chains. 1/4 was chosen because for a HZ of at least 100, this has no lost of accuracy whatsoever. Also note how it is only the established hash which is examined, listening sockets do not have keepalives go off, this saves a bunch of stupid checks. Second issue, the SYN reception timeout. Again, we previously walked the entire socket list when this fired off, no longer! Only listening sockets need to be checked (and as I mentioned this is an extremely small portion of the TCP socket space on a machine) so we only walk the TCP listening hash table. This case was a piece of cake to deal with. ;-) I will describe the good socket and bind verification techniques at some other point in time. It is quick but there are some bad corner cases I'd like to eliminate before I explain my intentions ;-) Suffice to say though that the third hash not yet described helps make these operations go like smoke. Comparison with FreeBSD for TCP (I love this, in fact once you read this you will wonder where their claims of scalability even come from): 1) Socket demultiplexing: FreeBSD - Single hash for entire TCP socket space. Listening sockets pollute the established connections. Hash function involves a mod instruction because the table size is a prime. Extraneous testing in the hash lookup because this code in in_pcb.c must be generic and cannot exploit nice properties present in TCP. Linux - Dual hash, listening sockets do not pollute the perfectly unique sockets. For the listening case, only the necessary pieces of the socket identity are examined to determine a match. Hash table size is a power of 2, eliminating the need of a costly multi cycle modulo instruction. (Some minutae, I have approximately 50 or so samples from some of the largest ftp and web servers that I know about (some of these samples have 5,000 or more connections), listing the socket connections during high load. A comparison of the current bound hash function under Linux and the one under FreeBSD shows them to distribute about the same, if not better for Linux (in particular Linux is better on machines which run many clients as well as large single port servers) the prime size of the hash does not seem to help FreeBSD and they eat the multi-cycle modulo instrucion on top of it all, so stupid) 2) Timers: FreeBSD - Every 500ms, and every 200ms, the _ENTIRE_ TCP socket list is walked, yes in it's entirety. How the fuck does this scale? Linux - Most TCP timers go off with the socket in question is an argument to the timer. And due to Finne Gangstad's scalable timer implementation the setting and deletion of these timers are near zero overhead. This also has the nice effect that our timers are also much more accurate than BSD. (this avoids the retransmit "explosions of death" every 200ms as seen on large BSD derived servers) For the timers which need not be that accurate, we either walk the small listener hash chains every half second, and every (75 / 4) seconds we walk (128 / 4) of the established hash chains. Now those are scalable TCP timers, beat that. ;-) 3) Port selection, and bind verification. I will discuss this issue at a later time, suffice to say that for FreeBSD they essentially walk the entire socket list for both operations looking for a match/miss. ---------------------------------------------//// Yow! 11.26 MB/s remote host TCP bandwidth & //// 199 usec remote TCP latency over 100Mb/s //// ethernet. Beat that! //// -----------------------------------------////__________ o David S. Miller, davem@caip.rutgers.edu /_____________/ / // /_/ >< From owner-freebsd-hackers Fri Feb 28 20:53:57 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id UAA09766 for hackers-outgoing; Fri, 28 Feb 1997 20:53:57 -0800 (PST) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id UAA09755 for ; Fri, 28 Feb 1997 20:53:54 -0800 (PST) Received: (from msmith@localhost) by genesis.atrad.adelaide.edu.au (8.8.5/8.7.3) id PAA16897; Sat, 1 Mar 1997 15:23:08 +1030 (CST) From: Michael Smith Message-Id: <199703010453.PAA16897@genesis.atrad.adelaide.edu.au> Subject: Re: DOS binary support for FreeBSD In-Reply-To: <3.0.1.32.19970228205137.00922200@pegasus.rutgers.edu> from Red Barchetta at "Feb 28, 97 08:51:37 pm" To: paradox@pegasus.rutgers.edu (Red Barchetta) Date: Sat, 1 Mar 1997 15:23:00 +1030 (CST) Cc: hackers@freebsd.org X-Mailer: ELM [version 2.4ME+ PL28 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Red Barchetta stands accused of saying: > Is anyone currently working on adding DOS binary support to FreeBSD? If > not (hell, even if so!) I am interested in taking a shot at this project. Before you get too carried away, grab ftp://gsoft.com.au/pub/doscmd/doscmd_fbsd-970228.tar.gz and join the emulation mailing list. Patches (even bug reports) are welcome. > If anyone can give me some suggestions regarding the specifics involved in > this task (i.e. what must be done at the system level to allow a DOS > program to run under FreeBSD) and maybe some references to relevant > materials (online or offline), it would be much appreciated. Read the archives of the emulation list 8) At a bare minimum, you want a 486 reference manual and a copy of Ralf Brown's Interrupt List. > look through the code for the "PCEMU" port, but I imagine it won't be of > *too* much use since its main purpose appears to be to emulate DOS on > non-Intel architectures. PCEMU doesn't emulate DOS at all, it emulates the PC hardware and allows you to run DOS. DOScmd can do that, or it can emulate DOS (reasonably well) for the purpose of running a single DOS binary (eg. an assembler or compiler). > Ernie Pistor -- ]] Mike Smith, Software Engineer msmith@gsoft.com.au [[ ]] Genesis Software genesis@gsoft.com.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control. (ph) +61-8-8267-3493 [[ ]] Unix hardware collector. "Where are your PEZ?" The Tick [[ From owner-freebsd-hackers Sat Mar 1 01:21:31 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id BAA25410 for hackers-outgoing; Sat, 1 Mar 1997 01:21:31 -0800 (PST) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id BAA25402 for ; Sat, 1 Mar 1997 01:21:27 -0800 (PST) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id KAA19436 for hackers@freebsd.org; Sat, 1 Mar 1997 10:21:21 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.8.5/8.8.5) id JAA29770; Sat, 1 Mar 1997 09:25:47 +0100 (MET) Message-ID: Date: Sat, 1 Mar 1997 09:25:47 +0100 From: j@uriah.heep.sax.de (J Wunsch) To: hackers@freebsd.org Subject: Re: migrating 2.1.7 -> 2.2: simple or hairy? References: X-Mailer: Mutt 0.55-PL10 Mime-Version: 1.0 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: ; from Chris Coleman on Feb 28, 1997 14:37:02 -0800 Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk As Chris Coleman wrote: > What about /usr/src/sys files, are they updated? Of course, they're part of /usr/src. It's only that a `make world' doesn't recompile your (or any other, FWIW) kernel. If you're already using a custom kernel, and you didn't forget to run `make depend', it's usually a simple matter of recompiling the bits there. Sometimes, it's also necessary to run config(8) again, first. In this case, it's safe to run `config -n', but don't forget to run `make depend' again. > Does it cause any problems if I let the kernel get out of date and keep > upgrading the system binaries with "make world" ? Over time, yes, it will cause you problems. All the binaries that rely on kernel-internal data structure cease working correctly (ps(1), netstat(1), w(1) etc.). -- 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-hackers Sat Mar 1 01:21:41 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id BAA25435 for hackers-outgoing; Sat, 1 Mar 1997 01:21:41 -0800 (PST) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id BAA25428 for ; Sat, 1 Mar 1997 01:21:36 -0800 (PST) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id KAA19447; Sat, 1 Mar 1997 10:21:34 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.8.5/8.8.5) id JAA29788; Sat, 1 Mar 1997 09:29:11 +0100 (MET) Message-ID: Date: Sat, 1 Mar 1997 09:29:11 +0100 From: j@uriah.heep.sax.de (J Wunsch) To: freebsd-hackers@freefall.freebsd.org Cc: fadorno@sm1.gte.net Subject: Re: Exabyte's TR-3 Eagle Nest References: X-Mailer: Mutt 0.55-PL10 Mime-Version: 1.0 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: ; from Howard Lew on Feb 26, 1997 00:22:36 -0800 Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk As Howard Lew wrote: > > > Can someone tell me how to configure this drive in my kernel and how to > > > test the installation? > > > > Sure, if you tell us what kind of beast it is, instead of silently > > assuming we already knew it? > > I have one too, but it's a floppy port monster and supposed to be > compatible with MC3000XL, QIC-Wide, Travan TR-3, and QIC-Extra. That means it's most likely unsupported, though one could give it a try to use the ft(4) driver. If there's anybody outside feeling challenged to improve (i.e., essentially rething and rewrite) the ft(4) driver, please speak up! -- 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-hackers Sat Mar 1 03:51:16 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id DAA29633 for hackers-outgoing; Sat, 1 Mar 1997 03:51:16 -0800 (PST) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id DAA29625 for ; Sat, 1 Mar 1997 03:51:12 -0800 (PST) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id MAA02228 for hackers@freebsd.org; Sat, 1 Mar 1997 12:51:10 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.8.5/8.8.5) id MAA00721; Sat, 1 Mar 1997 12:39:35 +0100 (MET) Message-ID: Date: Sat, 1 Mar 1997 12:39:34 +0100 From: j@uriah.heep.sax.de (J Wunsch) To: hackers@freebsd.org Subject: Re: Java binary support in FreeBSD ... References: X-Mailer: Mutt 0.55-PL10 Mime-Version: 1.0 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: ; from Adrian Chadd on Mar 1, 1997 13:42:50 +0800 Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk As Adrian Chadd wrote: > Again - its just one file (imgact_java.c) which has the code to recognise > java binaries, and then do some magic to execute it with the right > interpreter and command args, etc. So easy said -- so hard to accomplish. If i'm not very mistaken, the image activator gets a vnode, but it doesn't have the slightest idea about the pathname that caused this vnode reference. (Heck, the pathname might even no longer exist at all already.) However, since the java interpreter doesn't allow reading off stdin, it _needs_ to be passed a pathname, and even worse, it _needs_ to be done by tweaking the $CLASSPATH environment setting. That's quite a little more than 15 minutes of work. -- 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-hackers Sat Mar 1 04:07:33 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id EAA00488 for hackers-outgoing; Sat, 1 Mar 1997 04:07:33 -0800 (PST) Received: from korin.warman.org.pl (korin.warman.org.pl [148.81.160.10]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id EAA00483 for ; Sat, 1 Mar 1997 04:07:27 -0800 (PST) Received: from localhost (abial@localhost) by korin.warman.org.pl (8.8.3/8.7.3) with SMTP id NAA04180 for ; Sat, 1 Mar 1997 13:07:22 +0100 (MET) Date: Sat, 1 Mar 1997 13:07:21 +0100 (MET) From: Andrzej Bialecki To: freebsd-hackers@FreeBSD.ORG Subject: 2.2, 3.0 pkg_manage - where are you :-( Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Hello! Well, the subject says all... I really miss it. I didn't try yet to get the 2.1.7 ver and see if it works under 2.2 & current, but shouldn't it be included with the release? Andy +-------------------------------------------------------------------------+ Andrzej Bialecki _) _) _)_) _)_)_) _) _) --------------------------------------- _)_) _) _) _) _)_) _)_) Research and Academic Network in Poland _) _)_) _)_)_)_) _) _) _) Bartycka 18, 00-716 Warsaw, Poland _) _) _) _) _)_)_) _) _) +-------------------------------------------------------------------------+ From owner-freebsd-hackers Sat Mar 1 04:51:00 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id EAA03695 for hackers-outgoing; Sat, 1 Mar 1997 04:51:00 -0800 (PST) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id EAA03680 for ; Sat, 1 Mar 1997 04:50:55 -0800 (PST) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id NAA02961; Sat, 1 Mar 1997 13:50:48 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.8.5/8.8.5) id NAA00841; Sat, 1 Mar 1997 13:38:47 +0100 (MET) Message-ID: Date: Sat, 1 Mar 1997 13:38:47 +0100 From: j@uriah.heep.sax.de (J Wunsch) To: dec@phoenix.its.rpi.edu (David E. Cross) Cc: hackers@freebsd.org Subject: Re: crt0.o hole... References: <199702260711.CAA04697@phoenix.its.rpi.edu> X-Mailer: Mutt 0.55-PL10 Mime-Version: 1.0 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199702260711.CAA04697@phoenix.its.rpi.edu>; from David E. Cross on Feb 26, 1997 02:11:14 -0500 Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk As David E. Cross wrote: > I am finally getting arround to patching that hole... could someone tell me > where a sample exploit program is? The one that was originally used against > me was "crtbsd". I just want to make sure that I got it right. The exploit isn't that simple, since you need to dump i386 binary code onto a very specific part of the overflown stack array. However, if you've made sure that you have removed all traces of ENABLE_STARTUP_LOCALE, and you have removed the getenv("LOCALE_PATH") in libc, you can be sure to have plugged that hole. The latter is basically needed to ensure older but shared linked binaries also benefit from the change. You must make absolutely sure that you don't have any setuid or setgid old (FreeBSD 2.1 through 2.1.6.1) binaries around that are statically linked. Extend this to non-set[ug]id binaries as well if you've got setuid wrappers around (suidperl, sudo etc.). file /usr/X11R6/bin/* /usr/local/bin/* /usr/local/sbin/* \ /usr/local/libexec/*| fgrep -v dynamically | fgrep -v script |\ fgrep -v 'commands text' | fgrep -v 'symbolic link' -- 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-hackers Sat Mar 1 04:51:13 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id EAA03774 for hackers-outgoing; Sat, 1 Mar 1997 04:51:13 -0800 (PST) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id EAA03759 for ; Sat, 1 Mar 1997 04:51:10 -0800 (PST) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id NAA02973 for Hackers@FreeBSD.ORG; Sat, 1 Mar 1997 13:51:08 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.8.5/8.8.5) id NAA00871; Sat, 1 Mar 1997 13:48:56 +0100 (MET) Message-ID: Date: Sat, 1 Mar 1997 13:48:56 +0100 From: j@uriah.heep.sax.de (J Wunsch) To: Hackers@FreeBSD.ORG (Hackers) Subject: Re: Building PAO kernel on non-PAO system References: <199702261551.PAA27088@out2.ibm.net> X-Mailer: Mutt 0.55-PL10 Mime-Version: 1.0 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199702261551.PAA27088@out2.ibm.net>; from Steve Sims on Feb 26, 1997 10:50:30 -0500 Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk As Steve Sims wrote: > My desktop machine is a P5 with gobs of RAM and disk (running > [pretty]-current, FWIW) and it occurs to me that one approach might be to > build the PAO-enabled 2.1.6 kernel on the desktop and just NFS it back to the > laptop (thereby saving tons o' time). If you've got NFS, you can of course already use your desktop machine to compile it anyway. I'm doing this all day with my old 386/40 scratchbox's kernel. Simply NFS-export /usr/src/sys on the client. The kernel build is mostly self-contained, so it's fairly version independant. config(8) is much more version dependant, so run it on the notebook, not on the desktop box. -- 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-hackers Sat Mar 1 05:20:38 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id FAA04674 for hackers-outgoing; Sat, 1 Mar 1997 05:20:38 -0800 (PST) Received: from dg-rtp.dg.com (dg-rtp.rtp.dg.com [128.222.1.2]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id FAA04667 for ; Sat, 1 Mar 1997 05:20:34 -0800 (PST) Received: by dg-rtp.dg.com (5.4R3.10/dg-rtp-v02) id AA11179; Sat, 1 Mar 1997 08:20:03 -0500 Received: from ponds by dg-rtp.dg.com.rtp.dg.com; Sat, 1 Mar 1997 08:20 EST Received: from lakes.water.net (lakes [10.0.0.3]) by ponds.water.net (8.8.3/8.7.3) with ESMTP id IAA27309; Sat, 1 Mar 1997 08:04:47 -0500 (EST) Received: (from rivers@localhost) by lakes.water.net (8.8.3/8.6.9) id IAA10154; Sat, 1 Mar 1997 08:10:13 -0500 (EST) Date: Sat, 1 Mar 1997 08:10:13 -0500 (EST) From: Thomas David Rivers Message-Id: <199703011310.IAA10154@lakes.water.net> To: ponds!cet.co.jp!michaelh, ponds!lakes.water.net!rivers Subject: Re: Another installment of the "dup alloc"/"bad dir" panic problems. Cc: ponds!freebsd.org!freebsd-hackers Content-Type: text Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > On Fri, 28 Feb 1997, Thomas David Rivers wrote: > > > > > It now appears that having the printf()s in disksort() affects the problem > > > > in a positive manner (that is, I'm not able to demonstrate the previous > > > > "non-writing" behaviour I had seen; the inode in question is reliably > > > > filled with zeros.) > > The old "printf's makes the problem go away effect". I hate when that > happens. ;-) > > Can you do a gcc -v and show us the flags you use to compile the kernel? > I missed these, in case you've already posted them. Good idea - I'll have to dig this up. To explain more, I'm using a boot floppy image made with the "release" target of the standard makefiles. So, this is a BOOTMFS kernel. What I do is change a kernel file (usually adding printf()s) and then "make release". Boot from the resulting floppy image; insert a fixit floppy and then start up newfs's to test things... [rather involved; but the file system that gives me the reliable reproduction happens to be the root one on my test machine...] Here's an example of one of the kernel compiles that results from that (chopped up to fit 80 columns): cc -c -O -W -Wreturn-type -Wcomment -Wredundant-decls -Wimplicit -nostdinc -I. -I../.. -I../../sys -I../../../include -DBOOTMFS -DI586_CPU -DI486_CPU -DI386_CPU -DMFS_ROOT=1450 -DUSERCONFIG_BOOT -DMAXCONS=4 -DNFS_NOSERVER -DMFS -DATAPI -DVISUAL_USERCONFIG -DUSERCONFIG -DUCONSOLE -DBOUNCE_BUFFERS -DSCSI_DELAY=15 -DCOMPAT_43 -DCD9660 -DMSDOSFS -DNFS -DFFS -DINET -DMATH_EMULATE -DKERNEL -Di386 -DLOAD_ADDRESS=0xF0100000 ../../i386/i386/trap.c However, I was skeptical myself. So; I removed *every* printf() from my sources (retrieving the original sources) and remade my kernel. This resulted in a kernel that would demonstrate the problem; and, of course, has gcc flags as you see above. This means I can rebuild a kernel that fails, and, to some extent, indicates my build process is consistent. My next idea is to add the printf()s back, one-at-a-time, to see which one (or combinations) mask the problem. I have a difficult time believing that slowing down disksort() (especially since this isn't an appreciable slow-down) does anything. But, it would add delay to it's calling routine (in this case, the SCSI driver) which may be significant.... But, again, this happens with SCSI and IDE, so I'm guessing the problem lies outside of the low-level drivers and is to be found at some common level (which is what lead me to the shared disksort() routine.) Because of this commonality, I'm betting it's something in /sys/ufs/ufs - which is where I'm investigating... (well, blindly stumbling.) > > Regards, > > > Mike - Dave Rivers - From owner-freebsd-hackers Sat Mar 1 05:24:42 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id FAA04763 for hackers-outgoing; Sat, 1 Mar 1997 05:24:42 -0800 (PST) Received: from pdx1.world.net (pdx1.world.net [192.243.32.18]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id FAA04758 for ; Sat, 1 Mar 1997 05:24:40 -0800 (PST) Received: from suburbia.net (suburbia.net [203.4.184.1]) by pdx1.world.net (8.7.5/8.7.3) with SMTP id FAA18704 for ; Sat, 1 Mar 1997 05:26:21 -0800 (PST) Received: (qmail 9950 invoked by uid 110); 1 Mar 1997 10:44:39 -0000 MBOX-Line: From owner-netdev@roxanne.nuclecu.unam.mx Sat Mar 01 09:52:35 1997 remote from suburbia.net Delivered-To: proff@suburbia.net Received: (qmail 8779 invoked from network); 1 Mar 1997 09:52:29 -0000 Received: from roxanne.nuclecu.unam.mx (132.248.29.2) by suburbia.net with SMTP; 1 Mar 1997 09:52:29 -0000 Received: (from root@localhost) by roxanne.nuclecu.unam.mx (8.6.12/8.6.11) id DAA14241 for netdev-outgoing; Sat, 1 Mar 1997 03:35:34 -0600 Received: from caipfs.rutgers.edu (caipfs.rutgers.edu [128.6.37.100]) by roxanne.nuclecu.unam.mx (8.6.12/8.6.11) with ESMTP id DAA14236 for ; Sat, 1 Mar 1997 03:35:28 -0600 Received: from jenolan.caipgeneral (jenolan.rutgers.edu [128.6.111.5]) by caipfs.rutgers.edu (8.8.5/8.8.5) with SMTP id EAA12376 for ; Sat, 1 Mar 1997 04:33:00 -0500 (EST) Received: by jenolan.caipgeneral (SMI-8.6/SMI-SVR4) id EAA09015; Sat, 1 Mar 1997 04:32:49 -0500 Date: Sat, 1 Mar 1997 04:32:49 -0500 Message-Id: <199703010932.EAA09015@jenolan.caipgeneral> From: "David S. Miller" To: netdev@roxanne.nuclecu.unam.mx Subject: ok, final sockhash changes, new diff Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Ok, I've made the final major change I wanted to make, and fixed hopefully the last bug or two (a corner case where a port already in use would be given to a connect() request): vger.rutgers.edu:/pub/linux/Net/patches/fordyson3.diff.gz I believe I've made the TCP good port selection rather good. Here is approximately how it works. The third hash table I had previously mentioned is called the "bound" hash, it contains all sockets which are holding onto a local port and !(sk->dead && (sk->state == TCP_CLOSE). It is there just to make good socket selection and bind verification faster, it really serves no other purpose whatsoever. Choosing a good TCP local port goes something like this. The "start" static local to the routine tries to keep track of things so the next search is faster. It works most of the time, it is only updated when we hit a best possible match in the bound hash (ie. chain is empty). If an empty chain is found, the port we have gotten to is used, this is the fast case under low or zero load. When all chains have at least one entry, a different strategy kicks in. We keep track of how deep the smallest chains tend to be. I call this static local "binding_contour" just to be silly ;-) It tries to short circuit the search. It says essentially "if you find a chain with a length less than or equal to the binding contour, and the binding contour is non-zero, it is almost certainly the best you will find so just return it now" Another nice side effect of the binding contour technique is that it should spread out the bound hash table evenly, and as sockets begin to go away it automatically adjusts to this changing load, perhaps going back to the fast path mode if chains become entirely empty. There is one issue I still have with it, it's state is only updated every time a port selection occurs. There is potentially a really bad case where hundreds of sockets disappear in between two selection attempts, thus causing potentially an extremely poor selection (it's idea of load is 500 sockets old ;-) I considered adding a timer to adjust things so this doesn't happen, but I found that to be a rediculious idea. Nevertheless, I've beat up my machine and I'm rather confident with the changes. In particular I exhausted the entire TCP port space completely 30 or 40 times with connections on my test box. All I got was one stuck socket which timed out and disappeared just fine. ;-) Can you say "tcpcrashme" ;-) ---------------------------------------------//// Yow! 11.26 MB/s remote host TCP bandwidth & //// 199 usec remote TCP latency over 100Mb/s //// ethernet. Beat that! //// -----------------------------------------////__________ o David S. Miller, davem@caip.rutgers.edu /_____________/ / // /_/ >< From owner-freebsd-hackers Sat Mar 1 05:52:46 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id FAA05654 for hackers-outgoing; Sat, 1 Mar 1997 05:52:46 -0800 (PST) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id FAA05648; Sat, 1 Mar 1997 05:52:42 -0800 (PST) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id OAA04229; Sat, 1 Mar 1997 14:52:09 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.8.5/8.8.5) id OAA01155; Sat, 1 Mar 1997 14:45:08 +0100 (MET) Message-ID: Date: Sat, 1 Mar 1997 14:45:07 +0100 From: j@uriah.heep.sax.de (J Wunsch) To: sergey@extech.msk.su (Vnotchenko S.S.) Cc: freebsd-hackers@freebsd.org, freebsd-isp@freebsd.org Subject: Re: Re: [H] Optimal computer for FreeBSD References: <199702271733.UAA20701@ns.extech.msk.su> X-Mailer: Mutt 0.55-PL10 Mime-Version: 1.0 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199702271733.UAA20701@ns.extech.msk.su>; from Vnotchenko S.S. on Feb 27, 1997 20:33:28 +0300 Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk As Vnotchenko S.S. wrote: > Ethernet: 3c595 Make sure you've got the latest FreeBSD for this (2.2 will do fine as well). Note that 3Com chips aren't among the best these days (by design). -- 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-hackers Sat Mar 1 05:52:59 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id FAA05692 for hackers-outgoing; Sat, 1 Mar 1997 05:52:59 -0800 (PST) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id FAA05687 for ; Sat, 1 Mar 1997 05:52:56 -0800 (PST) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id OAA04240; Sat, 1 Mar 1997 14:52:45 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.8.5/8.8.5) id OAA01170; Sat, 1 Mar 1997 14:48:19 +0100 (MET) Message-ID: Date: Sat, 1 Mar 1997 14:48:19 +0100 From: j@uriah.heep.sax.de (J Wunsch) To: paulzn@olivetti.nl, phk@critter.tfs.com (Poul-Henning Kamp) Cc: freebsd-hackers@freebsd.org Subject: Re: 2.2 ctms References: X-Mailer: Mutt 0.55-PL10 Mime-Version: 1.0 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: ; from Paul van der Zwan on Feb 27, 1997 22:13:21 +0100 Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk As Paul van der Zwan wrote: > src-2.2.0187.gz appears to break dbm support. It replaces > lib/libc/db/hash/ndbm.c by a 0 byte file. THis causes a make world to fail > on perl. The CVS tree is as it should be. So it must be a CTM problem here, maybe the CTM master tree fell over. Poul? -- 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-hackers Sat Mar 1 05:53:13 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id FAA05733 for hackers-outgoing; Sat, 1 Mar 1997 05:53:13 -0800 (PST) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id FAA05728 for ; Sat, 1 Mar 1997 05:53:11 -0800 (PST) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id OAA04251; Sat, 1 Mar 1997 14:52:59 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.8.5/8.8.5) id OAA01133; Sat, 1 Mar 1997 14:41:33 +0100 (MET) Message-ID: Date: Sat, 1 Mar 1997 14:41:32 +0100 From: j@uriah.heep.sax.de (J Wunsch) To: rhwang@bigpanda.com (Richard Hwang) Cc: hackers@freebsd.org Subject: Re: [Q]: multiple lun probe not working on aic7880 References: <199702271634.LAA08156@lonewolf.hostworld.com> X-Mailer: Mutt 0.55-PL10 Mime-Version: 1.0 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199702271634.LAA08156@lonewolf.hostworld.com>; from Richard Hwang on Feb 27, 1997 11:34:35 -0500 Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk As Richard Hwang wrote: > I am trying to get FreeBSD to probe for multiple luns on a aic7880 > controller on a Dell PowerEdge 4100 server connected to a CMD Daytona > RAIDarray (SCSI ID 0), but it only ever finds the 2G partition on lun 0, > and can't find the 10G partition on lun1. FreeBSD seems to ignore > the fact that lun 1 exists. That's since there are too many broken devices that erroneously respond on LUNs > 0 even though they shouldn't. This policy is enforced in /sys/scsi/scsiconf.c with the following entry: #if NSD > 0 { T_DIRECT, T_DIRECT, T_FIXED, "*", "*", "*", "sd", SC_ONE_LU }, #endif /* NSD */ So now, go into this file, and add a record for your disk array saying it actually can do more than one LUN correctly: { T_DIRECT, T_DIRECT, T_FIXED, "CMD TECH", "DAYTONA", "*", "sd", SC_MORE_LUS }, If it works, let us know. (freebsd-scsi@freebsd.org is a better name of a list for this, or even better, use send-pr.) -- 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-hackers Sat Mar 1 05:58:42 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id FAA05982 for hackers-outgoing; Sat, 1 Mar 1997 05:58:42 -0800 (PST) Received: from bofh.cybercity.dk (bofh.cybercity.dk [195.8.128.254]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id FAA05977 for ; Sat, 1 Mar 1997 05:58:39 -0800 (PST) Received: from critter.dk.tfs.com (phk.cybercity.dk [195.8.133.247]) by bofh.cybercity.dk (8.8.3/8.7.3) with ESMTP id PAA19521; Sat, 1 Mar 1997 15:01:15 +0100 (MET) Received: from critter.dk.tfs.com (localhost [127.0.0.1]) by critter.dk.tfs.com (8.8.2/8.8.2) with ESMTP id PAA16089; Sat, 1 Mar 1997 15:02:18 +0100 (MET) To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) cc: paulzn@olivetti.nl, freebsd-hackers@freebsd.org Cc: Richard Wackerbarth Subject: Re: 2.2 ctms In-reply-to: Your message of "Sat, 01 Mar 1997 14:48:19 +0100." Date: Sat, 01 Mar 1997 15:02:18 +0100 Message-ID: <16087.857224938@critter.dk.tfs.com> From: Poul-Henning Kamp Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In message , J Wunsch writes: >As Paul van der Zwan wrote: > >> src-2.2.0187.gz appears to break dbm support. It replaces >> lib/libc/db/hash/ndbm.c by a 0 byte file. THis causes a make world to fail >> on perl. > >The CVS tree is as it should be. So it must be a CTM problem here, >maybe the CTM master tree fell over. src-2.2 is maintained by Richard Wackerbarth -- Poul-Henning Kamp | phk@FreeBSD.ORG FreeBSD Core-team. http://www.freebsd.org/~phk | phk@login.dknet.dk Private mailbox. whois: [PHK] | phk@tfs.com TRW Financial Systems, Inc. Power and ignorance is a disgusting cocktail. From owner-freebsd-hackers Sat Mar 1 06:03:22 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id GAA06162 for hackers-outgoing; Sat, 1 Mar 1997 06:03:22 -0800 (PST) Received: from profane.iq.org (profane.iq.org [203.4.184.217]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id GAA06144 for ; Sat, 1 Mar 1997 06:03:05 -0800 (PST) Received: (from proff@localhost) by profane.iq.org (8.8.4/8.8.2) id AAA10816 for hackers@freebsd.org; Sun, 2 Mar 1997 00:59:25 +1100 (EST) From: Julian Assange Message-Id: <199703011359.AAA10816@profane.iq.org> Subject: optimised ip_input To: hackers@freebsd.org Date: Sun, 2 Mar 1997 00:59:24 +1100 (EST) X-Mailer: ELM [version 2.4ME+ PL28 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk ip_input() is appalling slow for multi-homed hosts, taking around 2 x num_interface_addresses comparisons to detect if a packet is locally destined. I've addressed this with address caching, hashing, and intelligent handling of broadcast addresses. Interested? -- Prof. Julian Assange |If you want to build a ship, don't drum up people |together to collect wood and don't assign them tasks proff@iq.org |and work, but rather teach them to long for the endless proff@gnu.ai.mit.edu |immensity of the sea. -- Antoine de Saint Exupery From owner-freebsd-hackers Sat Mar 1 06:51:17 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id GAA07355 for hackers-outgoing; Sat, 1 Mar 1997 06:51:17 -0800 (PST) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id GAA07350 for ; Sat, 1 Mar 1997 06:51:14 -0800 (PST) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id PAA05656; Sat, 1 Mar 1997 15:51:04 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.8.5/8.8.5) id PAA01380; Sat, 1 Mar 1997 15:36:35 +0100 (MET) Message-ID: Date: Sat, 1 Mar 1997 15:36:34 +0100 From: j@uriah.heep.sax.de (J Wunsch) To: abial@korin.warman.org.pl (Andrzej Bialecki) Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: 2.2, 3.0 pkg_manage - where are you :-( References: X-Mailer: Mutt 0.55-PL10 Mime-Version: 1.0 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: ; from Andrzej Bialecki on Mar 1, 1997 13:07:21 +0100 Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk As Andrzej Bialecki wrote: > Well, the subject says all... I really miss it. #define pkg_manage "/stand/sysinstall configPackages" -- 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-hackers Sat Mar 1 08:00:11 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id IAA11177 for hackers-outgoing; Sat, 1 Mar 1997 08:00:11 -0800 (PST) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id IAA11165 for ; Sat, 1 Mar 1997 08:00:07 -0800 (PST) Received: from time.cdrom.com (jkh@localhost [127.0.0.1]) by time.cdrom.com (8.8.5/8.6.9) with ESMTP id HAA17170; Sat, 1 Mar 1997 07:59:50 -0800 (PST) To: Andrzej Bialecki cc: freebsd-hackers@FreeBSD.ORG Subject: Re: 2.2, 3.0 pkg_manage - where are you :-( In-reply-to: Your message of "Sat, 01 Mar 1997 13:07:21 +0100." Date: Sat, 01 Mar 1997 07:59:50 -0800 Message-ID: <17166.857231990@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk It's been replaced by ``/stand/sysinstall configPackages'' > Hello! > > Well, the subject says all... I really miss it. I didn't try yet to get > the 2.1.7 ver and see if it works under 2.2 & current, but shouldn't it be > included with the release? > > Andy > > +-------------------------------------------------------------------------+ > Andrzej Bialecki _) _) _)_) _)_)_) _) _) > --------------------------------------- _)_) _) _) _) _)_) _)_) > Research and Academic Network in Poland _) _)_) _)_)_)_) _) _) _) > Bartycka 18, 00-716 Warsaw, Poland _) _) _) _) _)_)_) _) _) > +-------------------------------------------------------------------------+ > > From owner-freebsd-hackers Sat Mar 1 08:19:48 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id IAA14431 for hackers-outgoing; Sat, 1 Mar 1997 08:19:48 -0800 (PST) Received: from root.com (implode.root.com [198.145.90.17]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id IAA14425 for ; Sat, 1 Mar 1997 08:19:44 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by root.com (8.8.5/8.6.5) with SMTP id IAA05139; Sat, 1 Mar 1997 08:21:00 -0800 (PST) Message-Id: <199703011621.IAA05139@root.com> X-Authentication-Warning: implode.root.com: localhost [127.0.0.1] didn't use HELO protocol To: Julian Assange cc: hackers@freebsd.org Subject: Re: optimised ip_input In-reply-to: Your message of "Sun, 02 Mar 1997 00:59:24 +1100." <199703011359.AAA10816@profane.iq.org> From: David Greenman Reply-To: dg@root.com Date: Sat, 01 Mar 1997 08:21:00 -0800 Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >ip_input() is appalling slow for multi-homed hosts, taking around >2 x num_interface_addresses comparisons to detect if a packet is >locally destined. > >I've addressed this with address caching, hashing, and intelligent >handling of broadcast addresses. Interested? Certainly...I'd like to see the diffs... -DG David Greenman Core-team/Principal Architect, The FreeBSD Project From owner-freebsd-hackers Sat Mar 1 08:27:18 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id IAA15368 for hackers-outgoing; Sat, 1 Mar 1997 08:27:18 -0800 (PST) Received: from root.com (implode.root.com [198.145.90.17]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id IAA15363 for ; Sat, 1 Mar 1997 08:27:15 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by root.com (8.8.5/8.6.5) with SMTP id IAA05199 for ; Sat, 1 Mar 1997 08:28:29 -0800 (PST) Message-Id: <199703011628.IAA05199@root.com> X-Authentication-Warning: implode.root.com: localhost [127.0.0.1] didn't use HELO protocol To: hackers@freebsd.org Subject: Re: overview of socket hashing changes, plus new patch From: David Greenman Reply-To: dg@root.com Date: Sat, 01 Mar 1997 08:28:29 -0800 Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk ------- Forwarded Message To: "David S. Miller" cc: netdev@roxanne.nuclecu.unam.mx Subject: Re: overview of socket hashing changes, plus new patch In-reply-to: Your message of "Fri, 28 Feb 1997 21:26:57 EST." <199703010226.VAA08431@jenolan.caipgeneral> From: David Greenman Reply-To: dg@root.com - -------- A couple of comments: > FreeBSD - Single hash for entire TCP socket > space. Listening sockets pollute > the established connections. I didn't see a significant amount of overhead due to this when I implemented the PCB hashing in FreeBSD. Almost all of the overhead was in the per-packet linear list searches...so creating a seperate hash list for listening/wildcard PCBs didn't seem worth it at the time. > Hash > function involves a mod instruction > because the table size is a prime. > (Some minutae, I have approximately 50 or so samples from some > of the largest ftp and web servers that I know about (some > of these samples have 5,000 or more connections), listing > the socket connections during high load. A comparison of the > current bound hash function under Linux and the one > under FreeBSD shows them to distribute about the same, if not > better for Linux (in particular Linux is better on machines > which run many clients as well as large single port servers) > the prime size of the hash does not seem to help FreeBSD and > they eat the multi-cycle modulo instrucion on top of it all, > so stupid) My analysis showed that an add or shift+add didn't provide adequate distribution. I actually went to a lot of trouble to write the prime number based hashing code because of this. If you've found a good way to get similarly good distribution, I'm certainly interested. > 2) Timers: > > FreeBSD - Every 500ms, and every 200ms, the > _ENTIRE_ TCP socket list is walked, > yes in it's entirety. How the fuck > does this scale? It doesn't, and it's one of the biggest problems with the code. It is, however, a second order problem (7/second compared to 1000's/second in the first order linear list search per packet case). I plan to re-visit this eventually, but it's not been very high priority. - -DG David Greenman Core-team/Principal Architect, The FreeBSD Project ------- End of Forwarded Message From owner-freebsd-hackers Sat Mar 1 08:27:50 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id IAA15445 for hackers-outgoing; Sat, 1 Mar 1997 08:27:50 -0800 (PST) Received: from root.com (implode.root.com [198.145.90.17]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id IAA15433 for ; Sat, 1 Mar 1997 08:27:46 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by root.com (8.8.5/8.6.5) with SMTP id IAA05207 for ; Sat, 1 Mar 1997 08:28:58 -0800 (PST) Message-Id: <199703011628.IAA05207@root.com> X-Authentication-Warning: implode.root.com: localhost [127.0.0.1] didn't use HELO protocol To: hackers@freebsd.org Subject: Re: overview of socket hashing changes, plus new patch From: David Greenman Reply-To: dg@root.com Date: Sat, 01 Mar 1997 08:28:58 -0800 Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk ------- Forwarded Message To: "David S. Miller" cc: netdev@roxanne.nuclecu.unam.mx Subject: Re: overview of socket hashing changes, plus new patch In-reply-to: Your message of "Sat, 01 Mar 1997 02:06:53 EST." <199703010706.CAA08811@jenolan.caipgeneral> From: David Greenman Reply-To: dg@root.com - -------- > From: David Greenman > Date: Fri, 28 Feb 1997 22:57:41 -0800 > > If you've found a good way to get similarly good distribution, I'm > certainly interested. > >I certainly did, in all cases the distribution (as I stated) is nearly >the same: Okay, so what are you doing then? - -DG David Greenman Core-team/Principal Architect, The FreeBSD Project ------- End of Forwarded Message From owner-freebsd-hackers Sat Mar 1 08:29:17 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id IAA15661 for hackers-outgoing; Sat, 1 Mar 1997 08:29:17 -0800 (PST) Received: from shrimp.dataplex.net (shrimp.dataplex.net [208.2.87.3]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id IAA15653 for ; Sat, 1 Mar 1997 08:29:14 -0800 (PST) Received: from [208.2.87.4] (cod.dataplex.net [208.2.87.4]) by shrimp.dataplex.net (8.8.5/8.8.5) with ESMTP id KAA05685; Sat, 1 Mar 1997 10:29:09 -0600 (CST) X-Sender: rkw@shrimp.dataplex.net Message-Id: In-Reply-To: <16087.857224938@critter.dk.tfs.com> References: Your message of "Sat, 01 Mar 1997 14:48:19 +0100." Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Sat, 1 Mar 1997 10:26:42 -0600 To: Poul-Henning Kamp From: Richard Wackerbarth Subject: Re: 2.2 ctms Cc: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch), paulzn@olivetti.nl, freebsd-hackers@freebsd.org Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk At 8:02 AM -0600 3/1/97, Poul-Henning Kamp wrote: >In message , J Wunsch writes: >>As Paul van der Zwan wrote: >> >>> src-2.2.0187.gz appears to break dbm support. It replaces >>> lib/libc/db/hash/ndbm.c by a 0 byte file. >>The CVS tree is as it should be. So it must be a CTM problem here, >>maybe the CTM master tree fell over. Actually, my copy of the CVS tree is the problem. :-( CVSup didn't catch it. I am restoring the CVS tree from scratch. That will propogate the "fix" to the next delta. From owner-freebsd-hackers Sat Mar 1 08:35:27 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id IAA16253 for hackers-outgoing; Sat, 1 Mar 1997 08:35:27 -0800 (PST) Received: from w2xo.pgh.pa.us (w2xo.pgh.pa.us [206.210.70.5]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id IAA16243 for ; Sat, 1 Mar 1997 08:35:20 -0800 (PST) Received: from w2xo.pgh.pa.us (localhost [127.0.0.1]) by w2xo.pgh.pa.us (8.8.4/8.8.4) with SMTP id LAA10629 for ; Sat, 1 Mar 1997 11:35:30 -0500 (EST) Message-ID: <33185AD1.41C67EA6@w2xo.pgh.pa.us> Date: Sat, 01 Mar 1997 11:35:29 -0500 From: Jim Durham Organization: Dis- X-Mailer: Mozilla 3.01Gold (X11; I; FreeBSD 2.1.6-RELEASE i386) MIME-Version: 1.0 To: freebsd-hackers@freebsd.org Subject: floppy install still broken? Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hey guys, A long time ago, (2.1.0 times) , I reported that the floppy installation was broken. It appears to me that it's still broken in 2.1.7. 8-( . Why am I installing from floppies? Laptop with no ethernet.... 8-(( . Anyhow, I have tried both MS-DOS and Unix formatted floppies, with the bin.a.. files in the floppy / and /bin directories. In all cases cases, install reports it can't find the distribution. I even tried making it /dist/bin/bin.a.. on the floppy. -- Jim Durham From owner-freebsd-hackers Sat Mar 1 08:58:50 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id IAA17853 for hackers-outgoing; Sat, 1 Mar 1997 08:58:50 -0800 (PST) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id IAA17845 for ; Sat, 1 Mar 1997 08:58:47 -0800 (PST) Received: from time.cdrom.com (jkh@localhost [127.0.0.1]) by time.cdrom.com (8.8.5/8.6.9) with ESMTP id IAA17391; Sat, 1 Mar 1997 08:58:40 -0800 (PST) To: Jim Durham cc: freebsd-hackers@freebsd.org Subject: Re: floppy install still broken? In-reply-to: Your message of "Sat, 01 Mar 1997 11:35:29 EST." <33185AD1.41C67EA6@w2xo.pgh.pa.us> Date: Sat, 01 Mar 1997 08:58:40 -0800 Message-ID: <17388.857235520@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I think you might have failed to read ABOUT.TXT. :-) You also need the bin.inf file. Jordan > Hey guys, > > A long time ago, (2.1.0 times) , I reported that the floppy installation > was > broken. It appears to me that it's still broken in 2.1.7. 8-( . > > Why am I installing from floppies? Laptop with no ethernet.... 8-(( . > > Anyhow, I have tried both MS-DOS and Unix formatted floppies, with > the bin.a.. files in the floppy / and /bin directories. In all cases > cases, install reports it can't find the distribution. I even tried > making it /dist/bin/bin.a.. on the floppy. > > -- > Jim Durham From owner-freebsd-hackers Sat Mar 1 09:02:22 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id JAA18110 for hackers-outgoing; Sat, 1 Mar 1997 09:02:22 -0800 (PST) Received: from root.com (implode.root.com [198.145.90.17]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id JAA18104 for ; Sat, 1 Mar 1997 09:02:19 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by root.com (8.8.5/8.6.5) with SMTP id JAA05291; Sat, 1 Mar 1997 09:03:20 -0800 (PST) Message-Id: <199703011703.JAA05291@root.com> X-Authentication-Warning: implode.root.com: localhost [127.0.0.1] didn't use HELO protocol To: "David S. Miller" cc: netdev@roxanne.nuclecu.unam.mx, hackers@freebsd.org Subject: Re: ok, final sockhash changes, new diff In-reply-to: Your message of "Sat, 01 Mar 1997 04:32:49 EST." <199703010932.EAA09015@jenolan.caipgeneral> From: David Greenman Reply-To: dg@root.com Date: Sat, 01 Mar 1997 09:03:20 -0800 Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi, David. I just looked at the hash algorithm you're using in tcp_hashfn()...I think it looks pretty good, and it's easy to see why it would have good distribution properties. I didn't think about using xor when I wrote the stuff for FreeBSD. :-( ...Anyway, I hope you don't mind if I change the algorithm in FreeBSD to use xor's. :-) It seems like the laddr/faddr would likely have a not-very-unique low order portion (since most hosts are assigned addresses in the low range of class A/B/C's), so it seems like this could perhaps be improved by combining the upper word of the IP address with the lower word...but perhaps this would be just extra overhead (since your analysis seems to show the distribution is already quite good). I've had other improvements to the FreeBSD code on my whiteboard since last summer ("DELACK queue", for example), but haven't had the time to work on implementing them. BTW, one thing I didn't see in your code that was suggested to me a few months ago (and is also on my whiteboard), is another queue to move connections that have closed and are just waiting for the 2MSL wait to expire. In the case of busy WWW servers, it's common for the majority of the connections to be in this state, so by moving them off of the regular hashed queue and on to a private hashed queue, you can speed up the lookups for the active connections. -DG David Greenman Core-team/Principal Architect, The FreeBSD Project From owner-freebsd-hackers Sat Mar 1 09:28:14 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id JAA20106 for hackers-outgoing; Sat, 1 Mar 1997 09:28:14 -0800 (PST) Received: from etinc.com (et-gw-fr1.etinc.com [204.141.244.98]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id JAA20087 for ; Sat, 1 Mar 1997 09:28:07 -0800 (PST) Received: from ntws (ntws.etinc.com [204.141.95.142]) by etinc.com (8.8.3/8.6.9) with SMTP id MAA25024; Sat, 1 Mar 1997 12:35:29 -0500 (EST) Message-Id: <3.0.32.19970301122709.00b1f390@etinc.com> X-Sender: dennis@etinc.com X-Mailer: Windows Eudora Pro Version 3.0 (32) Date: Sat, 01 Mar 1997 12:27:13 -0500 To: dg@root.com, Julian Assange From: dennis Subject: Re: optimised ip_input Cc: hackers@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk At 08:21 AM 3/1/97 -0800, you wrote: >>ip_input() is appalling slow for multi-homed hosts, taking around >>2 x num_interface_addresses comparisons to detect if a packet is >>locally destined. >> >>I've addressed this with address caching, hashing, and intelligent >>handling of broadcast addresses. Interested? > > Certainly...I'd like to see the diffs... A better way of handing the overhead and the complexity issue is to keep local addresses in the routing table with a LOCAL flag. This eliminates the overhead altogether and simplifies the process: route=routelookup() if (route.flags & localflag) deal_withit_locally() else forward() You can argue that in some cases this is more overhead for locally destined packets, but in todays world (where routing speed is a primary concern) this is faster most of the time and makes life easier as it centralizes the structure dependencies. Just a thought. Dennis > >-DG > >David Greenman >Core-team/Principal Architect, The FreeBSD Project > > From owner-freebsd-hackers Sat Mar 1 09:40:49 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id JAA21303 for hackers-outgoing; Sat, 1 Mar 1997 09:40:49 -0800 (PST) Received: from phoenix.its.rpi.edu (root@phoenix.its.rpi.edu [128.113.161.45]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id JAA21281 for ; Sat, 1 Mar 1997 09:40:26 -0800 (PST) Received: (from dec@localhost) by phoenix.its.rpi.edu (8.8.3/8.8.3) id MAA14501 for freebsd-hackers@freebsd.org; Sat, 1 Mar 1997 12:19:21 -0500 (EST) Date: Sat, 1 Mar 1997 12:19:21 -0500 (EST) From: "David E. Cross" Message-Id: <199703011719.MAA14501@phoenix.its.rpi.edu> To: freebsd-hackers@freebsd.org Subject: 2.2 request Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I am not sure if this is too late to make it into 2.2-RELEASE, but adding a kerberized ftpd as part of the kerberos packaged would be really nice :) -- David Cross ACS Consultant From owner-freebsd-hackers Sat Mar 1 10:10:15 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id KAA23431 for hackers-outgoing; Sat, 1 Mar 1997 10:10:15 -0800 (PST) Received: from jump.net (serv1-2.jump.net [204.238.120.19]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id KAA23424 for ; Sat, 1 Mar 1997 10:10:11 -0800 (PST) Received: from benjamin.adonai.com by jump.net (8.8.4/BERK-6.8.11) id MAA11699; Sat, 1 Mar 1997 12:10:07 -0600 (CST) Message-Id: <1.5.4.32.19970301181002.006bc48c@jump.net> X-Sender: adonai@jump.net X-Mailer: Windows Eudora Light Version 1.5.4 (32) Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Sat, 01 Mar 1997 12:10:02 -0600 To: hackers@freebsd.org From: Lee Crites Subject: Please help with digiboard switch settings... Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I finally did it. I upgraded to 2.2 so I could use my digiboard. Now that I am up and (hopefully) stable, I am trying, once again, to get my digiboard up and running. Actually the upgrade from 2.1.5 to 2.2-GAMMA went much, much smoother than I had anticipated. I guess the three backups was what did it. (If I hadn't had a good backup, according to Murphy, the upgrade would have crashed everything!) Well, needless to say, it didn't fix my digiboard problem, or at least hasn't yet. When I boot up, I get an error message telling me that dgb cannot be found at 0x220 (or whatever address I have tried that time). So, I just need to set the proper dip-switches and go on, right? Right! However, the man who built my server, which included installing my digiboard, has lost the installation docu for the digiboard. [WARNING MODE ON] Before going on, let me first admit that I am *not* a hardware type. I have, from time to time, been able to plug boards in and install drivers, etc, but that's about it. So if what I describe below is useless garbage, I'm sorry... [WARNING MODE OFF] So, I have the board in question in my hand, so here's what I can tell you: on the end (you see out the back of the computer): * one 78-pin female connector * one four-toggle dip-switch on the back (the side without the 'stuff' on it): * sticker states "PC/8e ISA" with "REV:H" printed on it as well * sticker states "55-405", "9630", "REV G", and "B85665" * card has "DI 30001752 REV B" stamped on it (under green film) on the front: * card has "DI AN 30001754 REV _____" stamped on it, on top of the green film, with "G" handwritten in the blank That's it... My first thought was to try their web site. No luck. The hardware documentation which they have on-line, while it looks good, does not describe anything like my card. And, of course, the supplied utility just doesn't work on FreeBSD. If you can provide any assistance, I would sing your praises... Lee From owner-freebsd-hackers Sat Mar 1 10:22:32 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id KAA23844 for hackers-outgoing; Sat, 1 Mar 1997 10:22:32 -0800 (PST) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id KAA23839 for ; Sat, 1 Mar 1997 10:22:28 -0800 (PST) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id TAA12502 for freebsd-hackers@freebsd.org; Sat, 1 Mar 1997 19:22:26 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.8.5/8.8.5) id TAA02328; Sat, 1 Mar 1997 19:15:56 +0100 (MET) Message-ID: Date: Sat, 1 Mar 1997 19:15:56 +0100 From: j@uriah.heep.sax.de (J Wunsch) To: freebsd-hackers@freebsd.org (FreeBSD hackers) Subject: truncated-ip - 101 bytes missing... X-Mailer: Mutt 0.55-PL10 Mime-Version: 1.0 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I think we already had this discussion at some point. I've tried to fetch the linux_lib distfile from my closes mirror. After transferring 4019200 bytes, the transfer stalled. I tried to `reget' the file using a new ftp session, still fail. I ran tcpdump on the sl0 interface, and much to my surprise: 18:08:08.656147 truncated-ip - 101 bytes missing!141.30.61.11.20 > 193.175.26.65.40005: . 4225129474:4225129986(512) ack 4005312101 win 16384 [tos 0x8] 18:08:09.176515 truncated-ip - 101 bytes missing!141.30.61.11.20 > 193.175.26.65.40006: . 4245673474:4245673986(512) ack 4030228811 win 16384 [tos 0x8] 18:08:09.523537 truncated-ip - 91 bytes missing!137.226.31.2.20 > 193.175.26.65.40007: . 684563218:684563710(492) ack 4039732364 win 17280 (DF) [tos 0x8] 18:08:15.177871 truncated-ip - 101 bytes missing!141.30.61.11.20 > 193.175.26.65.40003: . 4186222594:4186223106(512) ack 3960042550 win 16384 [tos 0x8] The FTP server i ran this against was totally irrelevant, the above machine announces itself as AIX 3.2.5, but i've also tried to reget the file from ftp.de.freebsd.org (which i think is a FreeBSD machine). The SLIP interface ran with an MTU of 552. I stopped the SLIP session and started a PPP session -- everything's ok. Isn't it a little surprising that the above behaviour happens at exact the same spot in the file? -- 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-hackers Sat Mar 1 10:30:22 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id KAA24102 for hackers-outgoing; Sat, 1 Mar 1997 10:30:22 -0800 (PST) Received: from korin.warman.org.pl (korin.warman.org.pl [148.81.160.10]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id KAA24095 for ; Sat, 1 Mar 1997 10:30:14 -0800 (PST) Received: from localhost (abial@localhost) by korin.warman.org.pl (8.8.3/8.7.3) with SMTP id TAA04649 for ; Sat, 1 Mar 1997 19:28:50 +0100 (MET) Date: Sat, 1 Mar 1997 19:28:50 +0100 (MET) From: Andrzej Bialecki To: freebsd-hackers@FreeBSD.ORG Subject: StarOffice /Linux - emul speed? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Hello! I'd like to mention that I managed to run StarOffice Beta3(Linux ELF bin + Motif static) on the latest SNAP. Many thanks to Andreas Kohout! ( http://www.augusta.de/~shanee/StarOffice.html). This package is a real breakthrough for me - I'm immediately starting to replace some Win boxes with FBSD +StarOffice, as it seems to be much more powerful than M$Office (+ all the benefits of the OS). However, one thing is bugging me: I run it on P133 64M RAM, and it runs somewhat slooow. Does it have something to do with the linuxulator performance, or is it just a feature? I'd be glad if someone could compare the speed under both OSes. TIA Andy, PS. I hope this is not too off topic of this list. Excuse me if it is. +-------------------------------------------------------------------------+ Andrzej Bialecki _) _) _)_) _)_)_) _) _) --------------------------------------- _)_) _) _) _) _)_) _)_) Research and Academic Network in Poland _) _)_) _)_)_)_) _) _) _) Bartycka 18, 00-716 Warsaw, Poland _) _) _) _) _)_)_) _) _) +-------------------------------------------------------------------------+ From owner-freebsd-hackers Sat Mar 1 11:20:30 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id LAA25388 for hackers-outgoing; Sat, 1 Mar 1997 11:20:30 -0800 (PST) Received: from zeus.xtalwind.net (slipper20b.xtalwind.net [205.160.242.90]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id LAA25383 for ; Sat, 1 Mar 1997 11:20:26 -0800 (PST) Received: from localhost (zeus.xtalwind.net [127.0.0.1]) by zeus.xtalwind.net (8.8.5/8.8.5) with SMTP id OAA00409; Sat, 1 Mar 1997 14:20:09 -0500 (EST) Date: Sat, 1 Mar 1997 14:20:09 -0500 (EST) From: jack X-Sender: jack@zeus.xtalwind.net To: J Wunsch cc: freebsd-hackers@freefall.freebsd.org Subject: Re: Exabyte's TR-3 Eagle Nest In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Sat, 1 Mar 1997, J Wunsch wrote: > > I have one too, but it's a floppy port monster and supposed to be > > compatible with MC3000XL, QIC-Wide, Travan TR-3, and QIC-Extra. > > That means it's most likely unsupported, though one could give it a > try to use the ft(4) driver. I've got one of these drives. ft/lft can retention or rewind it but thats about all. They read the header but can't recognize the info of the 3010 or 3020 format tapes. -------------------------------------------------------------------------- Jack O'Neill Finger jacko@diamond.xtalwind.net or jack@xtalwind.net http://www.xtalwind.net/~jacko/pubpgp.html #include for my PGP key. PGP Key fingerprint = F6 C4 E6 D4 2F 15 A7 67 FD 09 E9 3C 5F CC EB CD -------------------------------------------------------------------------- From owner-freebsd-hackers Sat Mar 1 12:11:35 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id MAA27178 for hackers-outgoing; Sat, 1 Mar 1997 12:11:35 -0800 (PST) Received: from alpha.xerox.com (alpha.Xerox.COM [13.1.64.93]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id MAA27171 for ; Sat, 1 Mar 1997 12:11:30 -0800 (PST) Received: from www.sdsp.mc.xerox.com ([13.231.132.18]) by alpha.xerox.com with SMTP id <15718(3)>; Sat, 1 Mar 1997 12:10:55 PST Received: from gnu.sdsp.mc.xerox.com (gnu.sdsp.mc.xerox.com [13.231.133.90]) by www.sdsp.mc.xerox.com (8.8.5/8.8.5) with SMTP id PAA13190; Sat, 1 Mar 1997 15:12:40 -0500 (EST) Received: by gnu.sdsp.mc.xerox.com (4.1/client-1.3) id AA23110; Sat, 1 Mar 97 15:12:23 EST Message-Id: <9703012012.AA23110@gnu.sdsp.mc.xerox.com> Cc: Darren Reed , julian@whistle.com (Julian Elischer), matt@lkg.dec.com, terry@lambert.org, hackers@freebsd.org To: To: To: To: To: Subject: Re: Alternatives to SYSV IPC? In-Reply-To: Your message of "Wed, 26 Feb 1997 13:07:42 PST." <9702262107.AA16436@gnu.sdsp.mc.xerox.com> Date: Sat, 1 Mar 1997 12:12:21 PST From: "Marty Leisner" Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In message <9702262107.AA16436@gnu.sdsp.mc.xerox.com>, you write: >> In some mail from Julian Elischer, sie said: >> > >> > > if (socketpair(AF_UNIX, SOCK_STREAM, 0, fds) < 0) >> > > perror("socketpair"); >> > >> > how come no-one uses AF_LOCAL with SOCK_DGRAM? >> >> how portable is AF_LOCAL ? >> >> Darren > >Is AF_LOCAL/SOCK_DGRAM posix 1003.1g? > In socket, you should use PF_* (protocol family). In bind or sendto, you use the AF_*(address family). Posix 1003.1g changed it from _UNIX to _LOCAL. (methinks). This is the explanation by Dan Lanciani (from http://www.noao.edu/~rstevens/lanciani.96apr10.txt Article: 49920 of comp.protocols.tcp-ip From: ddl@harvard.edu (Dan Lanciani) Newsgroups: comp.protocols.tcp-ip Subject: Re: sockets: AF_INET vs. PF_INET Message-ID: <3561@news.IPSWITCH.COM> Date: 10 Apr 96 01:27:20 GMT In article <3169B256.41C6@engr.sgi.com>, sam@engr.sgi.com (Sam Leffler) writes: | Dan Lanciani wrote: |> |> In article <4k1grt$5gq@noao.edu>, rstevens@noao.edu (W. Richard Stevens) writes: |> | > So why the difference? |> | > AF vs PF? |> | > What does the difference mean? |> | |> | AF = address family. These constants go into the sin_family member of the |> | socket address structure. |> | |> | PF = protocol family. These constants are the first argument to socket(). |> |> There is a little more to it than that. Although I don't have the ancient |> sources handy to check (and my memory of this particular aspect is fading), |> I recall that the original socket code (4.1c/2.8/2.9BSD) employed a protocol |> structure similar in concept to the sockaddr structure. The protocol |> structure contained a family element and a family-specific protocol number. |> The PF_ constants were used for the family element of the protocol structure. |> A protocol structure (or, rather, the address of one) could be passed to the |> socket() call to serve a purpose similar to that of the last (integer) |> argument |> of the current socket() call. (Keep in mind that the old socket() call did |> not |> take a family/domain argument at all, so interpretation of the protocol |> number |> would not have been possible without the PF_ cue.) Originally, then, the PF_ |> and AF_ constants had a much more parallel purpose as structure tags. When |> socket() started requiring a family/domain argument, the protocol structure |> was dropped. | | Well, actually your memory is a bit off. While that may well be true in general, I was correct on this issue. :) | The original socket design included | a concept termed a "communications domain" (or "communication domain", never | could decide which was correct :-)). A domain encapsulated many aspects of | communication including the protocol family and address format. Sockets were | to be created "within a domain" and carried with them the semantics of the | domain. This was originally to be carried out using a domain() system call | that | returned a descriptor that was then passed as the first argument to socket(). The above may describe the original *concept*, but it was not the implementation in 4.1c/2.9BSD. Whether what you describe ever existed in an implementation, I can't say. I do remember that early 4.2 manuals described all sorts of neat IPC mechanisms that did not exist in the operating system. Something about ``portals'' comes to mind. | Along the way we decided this was not worthwhile and replaced the descriptor | with a manifest constant (PF_*) that referenced a fixed set of domains with | the associated semantics. No, the evolution really did include the version I described. It did not jump from the (hypothetical?) domain() semantics to the current state. Here is an excerpt from the socket() man page of old: ----------------------------------------------------------------------------- SOCKET(2X) UNIX Programmer's Manual SOCKET(2X) NAME socket - create an endpoint for communication SYNOPSIS #include s = socket(type, pf, addr, options); int type; struct sockproto *pf; struct sockaddr *addr; int options; ----------------------------------------------------------------------------- The type is what you would expect. The pf is the object of interest. The addr was used in place of a separate bind() and the options argument encoded bits similar to those used in current setsockopt() calls (plus the important SO_ACCEPTCONN which pre-dated listen()). Here is the interesting section from sys/socket.h: ----------------------------------------------------------------------------- struct sockproto { short sp_family; /* protocol family */ short sp_protocol; /* protocol within family */ }; #define PF_UNSPEC 0 /* unspecified */ #define PF_UNIX 1 /* UNIX internal protocol */ #define PF_INET 2 /* internetwork: UDP, TCP, etc. */ #define PF_IMPLINK 3 /* imp link protocols */ #define PF_PUP 4 /* pup protocols: e.g. BSP */ #define PF_CHAOS 5 /* mit CHAOS protocols */ #define PF_OISCP 6 /* ois communication protocols */ #define PF_NBS 7 /* nbs protocols */ #define PF_ECMA 8 /* european computer manufacturers */ #define PF_DATAKIT 9 /* datakit protocols */ #define PF_CCITT 10 /* CCITT protocols, X.25 etc */ ----------------------------------------------------------------------------- I programmed to these interfaces extensively; I assure you they were/are real. [...] |> Now, I would argue that the AF_ family is the correct set of constants |> for the first argument of socket(). My reason is simply that the constants |> in the tables in the socket code itself are AF_ values, and the first |> argument |> of socket() is compared to these to find the correct domain structure for |> the request. | | The correct parameter is a PF_foo. Why? | In practice however AF_foo = PF_foo and | at this point any implementation that does not maintain this will break lots |of code. FWIW my fingers automatically type AF_ when making a socket call :-). Good, you are doing the right thing. :) Dan Lanciani ddl@harvard.* From owner-freebsd-hackers Sat Mar 1 12:33:38 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id MAA28110 for hackers-outgoing; Sat, 1 Mar 1997 12:33:38 -0800 (PST) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id MAA28105 for ; Sat, 1 Mar 1997 12:33:35 -0800 (PST) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id VAA15642 for freebsd-hackers@FreeBSD.ORG; Sat, 1 Mar 1997 21:33:25 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.8.5/8.8.5) id VAA02981; Sat, 1 Mar 1997 21:06:52 +0100 (MET) Message-ID: Date: Sat, 1 Mar 1997 21:06:51 +0100 From: j@uriah.heep.sax.de (J Wunsch) To: freebsd-hackers@FreeBSD.ORG Subject: Re: StarOffice /Linux - emul speed? References: X-Mailer: Mutt 0.55-PL10 Mime-Version: 1.0 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: ; from Andrzej Bialecki on Mar 1, 1997 19:28:50 +0100 Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk As Andrzej Bialecki wrote: > However, one thing is bugging me: I run it on P133 64M RAM, and it runs > somewhat slooow. Does it have something to do with the linuxulator > performance, or is it just a feature? I'd be glad if someone could compare > the speed under both OSes. I wouldn't even be surprised if it ran faster on FreeBSD, due to its high resource consumption (and FreeBSD probably behaving better under load). I think StarOffice is known to be slow, 64 MB RAM is said to be the minimum. I've got a copy of Applixware for testing lately, and it seems to do fine. I can't complain about performance problems, and that's with a 32 MB machine. (The only thing now is that i'm totally unable to make any sense out of this kind of kindergarten-age applications. Fancy picture icons everywhere...) -- 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-hackers Sat Mar 1 12:34:36 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id MAA28164 for hackers-outgoing; Sat, 1 Mar 1997 12:34:36 -0800 (PST) Received: from ns.ge.com (ns.ge.com [192.35.39.24]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id MAA28158 for ; Sat, 1 Mar 1997 12:34:33 -0800 (PST) Received: from thomas.ge.com (thomas.ge.com [3.47.28.21]) by ns.ge.com (8.8.4/8.7.3) with ESMTP id PAA19387 for ; Sat, 1 Mar 1997 15:32:28 -0500 (EST) Received: from burg.is.ge.com (burg.is.ge.com [3.19.120.24]) by thomas.ge.com (8.8.4/8.7.5) with ESMTP id PAA17703 for ; Sat, 1 Mar 1997 15:35:21 -0500 (EST) Received: (from burg@localhost) by burg.is.ge.com (8.8.4/8.8.4) id VAA20143; Sat, 1 Mar 1997 21:27:13 +0100 (MET) Date: Sat, 1 Mar 1997 21:27:13 +0100 (MET) Message-Id: <199703012027.VAA20143@burg.is.ge.com> From: Dick van den Burg To: freebsd-hackers@freebsd.org Subject: cvsup Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I am trying to get cvsup to run through a TIS firewall. This firewall supports a plug-gw, where a connection from a host to a port can be accepted from one side of the firwall and re-established to another host at the other side: my-host:xxxx -> firewall:5999 -> firewall:xxx -> cvsup.freebsd:5999 I had set up a rule to allow cvsup.freebsd.org:xxx -> firewall:5998 -> firewall:xxx -> my-host:5998 and I called cvsup -P 5998 Unfortunately the PORT command sent by cvsup has 'my-host' IP address and port 5998 in there, so cvsup.freebsd tries to connect there, and of course my-host is unknown on the internet. Passive mode does not work because it will connect to a port that can be different with each invocation and I need to instruct the plug-gw which ports to connect to. Is there any way whereby I can tell the server to connect to the firewall (in stead of my-host) on a given port or is there any way I can specify a portnumber I can connect to on the server in passive mode? Any other suggestions ? Thanks, Dick van den Burg From owner-freebsd-hackers Sat Mar 1 13:32:22 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id NAA00515 for hackers-outgoing; Sat, 1 Mar 1997 13:32:22 -0800 (PST) Received: from sumatra.americantv.com (sumatra.americantv.com [199.184.181.250]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id NAA00502 for ; Sat, 1 Mar 1997 13:32:17 -0800 (PST) Received: from right.PCS (right.pcs. [148.105.10.31]) by sumatra.americantv.com (8.7.6/8.7.3) with ESMTP id QAA28906; Sat, 1 Mar 1997 16:05:30 -0600 (CST) Received: (jlemon@localhost) by right.PCS (8.6.13/8.6.4) id VAA28591; Sat, 1 Mar 1997 21:32:28 GMT Message-ID: <19970301153228.55044@right.PCS> Date: Sat, 1 Mar 1997 15:32:28 -0600 From: Jonathan Lemon To: Dick van den Burg Cc: freebsd-hackers@freebsd.org Subject: Re: cvsup References: <199703012027.VAA20143@burg.is.ge.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.61.1 In-Reply-To: <199703012027.VAA20143@burg.is.ge.com>; from Dick van den Burg on Mar 03, 1997 at 09:27:13PM +0100 Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Mar 03, 1997 at 09:27:13PM +0100, Dick van den Burg wrote: > I am trying to get cvsup to run through a TIS firewall. > > Is there any way whereby I can tell the server to connect to the > firewall (in stead of my-host) on a given port or is there any way I > can specify a portnumber I can connect to on the server in passive > mode? > > Any other suggestions ? I submitted patches to the socks5 maintainer a while ago that permits CVSUP to be used through a socks5 firewall. It works pretty well; you could try using that instead of the TIS toolkit, if you have that option. -- Jonathan From owner-freebsd-hackers Sat Mar 1 13:55:51 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id NAA01431 for hackers-outgoing; Sat, 1 Mar 1997 13:55:51 -0800 (PST) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id NAA01426 for ; Sat, 1 Mar 1997 13:55:48 -0800 (PST) Received: from current1.whistle.com (current1.whistle.com [207.76.205.22]) by alpo.whistle.com (8.8.5/8.8.4) with SMTP id NAA03315; Sat, 1 Mar 1997 13:48:45 -0800 (PST) Message-ID: <3318A3B6.41C67EA6@whistle.com> Date: Sat, 01 Mar 1997 13:46:30 -0800 From: Julian Elischer Organization: Whistle Communications X-Mailer: Mozilla 3.0Gold (X11; I; FreeBSD 2.2-CURRENT i386) MIME-Version: 1.0 To: "David S. Miller" CC: hackers@freebsd.org Subject: Re: overview of socket hashing changes, plus new patch References: <199703010226.VAA08431@jenolan.caipgeneral> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk David (Miller) Are you on any FreeBSD lists..? There has been some discussion going on and I am so encouraged by what seems like a civilised proffesional dialog between Linux and BSD camps on this topic that I just want to make sure that we endevour to keep the lines of communications open. I spoke with Alan Cox (and Linus) at USENIX, and from what he told me it seems that the linux and BSD systems have now very similar philosophies in how they approach networking.. It seems to me that Alan and others involved (such as yourself) have very carefully examined the "grand old lady" of networking (the BSD stuff) and are detirmined to learn from our mistakes and improve on what is good about it. This is EXACTLY what we in BSD want! The original Linux networking seemed to us a bit of a slap in the face, ("You guys don't know what you are doing, we can do it better in Linux and further more we don't want to talk to you about it") The new attitude and work is a breath of fresh air and I hope it leads to a friendly air of competative co-operation. Maybe we can even make some efforts to deliberatly widen the dialogue, and make it more frequent. BSD networking is not "the last word". It has been very much a "work in progress" for the last 15 years and will continue to be so for many more. We respect good work from any source and are happy when our work is useful to others, whether as a benchmark, a direct source, or a learning tool. I'm not speaking "officially" for the various people involved in BSD, but I know I'm speaking the thoughts of many I personally know. julian p.s. From owner-freebsd-hackers Sat Mar 1 14:20:34 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id OAA02053 for hackers-outgoing; Sat, 1 Mar 1997 14:20:34 -0800 (PST) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.50]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id OAA02048 for ; Sat, 1 Mar 1997 14:20:30 -0800 (PST) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id PAA05668; Sat, 1 Mar 1997 15:16:33 -0700 From: Terry Lambert Message-Id: <199703012216.PAA05668@phaeton.artisoft.com> Subject: Re: Java binary support in FreeBSD ... To: joerg_wunsch@uriah.heep.sax.de Date: Sat, 1 Mar 1997 15:16:33 -0700 (MST) Cc: hackers@FreeBSD.ORG In-Reply-To: from "J Wunsch" at Mar 1, 97 12:31:24 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-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > Geeze, why didn't they implement a ``script is on fd 0'' feature. > That would have made it very easy to implement the image activator. We could even invent a name for the feature. For instance, we could call it "portals". 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-hackers Sat Mar 1 14:31:10 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id OAA02356 for hackers-outgoing; Sat, 1 Mar 1997 14:31:10 -0800 (PST) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.50]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id OAA02351 for ; Sat, 1 Mar 1997 14:31:07 -0800 (PST) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id PAA05697 for hackers@freebsd.org; Sat, 1 Mar 1997 15:27:15 -0700 From: Terry Lambert Message-Id: <199703012227.PAA05697@phaeton.artisoft.com> Subject: Re: Another installment of the "dup alloc"/"bad dir" panic problems. To: hackers@freebsd.org Date: Sat, 1 Mar 1997 15:27:15 -0700 (MST) X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > Yes, I wish it was that, I'd love to be done with this :-) > > However, this particular reproduction of the dup-alloc problem > is with an AHA 1542B and Micropolis ~500meg drive... > > So, now the question I'm considering is "what could be some > timing dependent that it affects both IDE and SCSI drivers?" 1542B? How much RAM do you have? If you have more than 16M ... it's bouncing. Try backing down to 16M and not bouncing and see if that's where it is... 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-hackers Sat Mar 1 14:42:51 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id OAA02777 for hackers-outgoing; Sat, 1 Mar 1997 14:42:51 -0800 (PST) Received: from chai.plexuscom.com (chai.plexuscom.com [207.87.46.100]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id OAA02765 for ; Sat, 1 Mar 1997 14:42:30 -0800 (PST) Received: from chai.plexuscom.com (localhost.torrentnet.com [127.0.0.1]) by chai.plexuscom.com (8.8.5/8.8.5) with ESMTP id RAA04265; Sat, 1 Mar 1997 17:42:33 -0500 (EST) Message-Id: <199703012242.RAA04265@chai.plexuscom.com> To: dennis Cc: dg@root.com, Julian Assange , hackers@freebsd.org Subject: Re: optimised ip_input In-reply-to: Your message of "Sat, 01 Mar 1997 12:27:13 EST." <3.0.32.19970301122709.00b1f390@etinc.com> Date: Sat, 01 Mar 1997 17:42:33 -0500 From: Bakul Shah Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > A better way of handing the overhead and the complexity issue is to > keep local addresses in the routing table with a LOCAL flag. This > eliminates the overhead altogether and simplifies the process: > route=routelookup() > if (route.flags & localflag) > deal_withit_locally() > else > forward() > You can argue that in some cases this is more overhead for locally > destined packets, but in todays world (where routing speed is a > primary concern) this is faster most of the time and makes life > easier as it centralizes the structure dependencies. The vast majority of the hosts have one or two interfaces so what you suggest above is likely to be a `pessimization' -- route lookup is not cheap. Perhaps a different version of ip_input() can be used depending on whether the host is acting as a router or not. The host version can use a more efficient match code. Some comments on the topic of networking code optimization: 1) There are a number of areas where things are being done suboptimally in the networking code: - things are checked multiple times - mbuf manipulation is expensive. - copying multiple times - things are `handed over' via queues more than once. - the cost of manipulating certain data structures can scale more than linearly with increased use. - certain things are done in mainline code when they should be done offline or via use of specialized functions. - new code is bolted on top of existing structure where it should have been added by simplifying/generalizing the existing structure. [Too general? Well, start with any 200 lines worth of functions and see how many things you can think of optimizing!] 2) Profiling the networking code in a production environment ought to point out the `hot spots' where much of the time is spent under various conditions. Measure various costs by changing data structure sizes and feeding similar traffic. Find out *why* the hot spots are the way they are; gain a deeper understanding of the structure and behavior of the networking code. Next optimize the hell out of the top N offenders. Without this sort of _prioritization_ you are likely to spend much time on optimizing less travelled roads. If and when such profiling is done, publish the results (and conditions under which the numbers were obtained). Brainstorm about various solutions & analyze how they will stand up under load and corner cases. 3) There is also the danger of destabilizing working code by making too many changes, which is another reason for making only those changes that yield substantial improvement and only after peer reviewing. -- bakul From owner-freebsd-hackers Sat Mar 1 15:13:43 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id PAA03766 for hackers-outgoing; Sat, 1 Mar 1997 15:13:43 -0800 (PST) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id PAA03749 for ; Sat, 1 Mar 1997 15:13:27 -0800 (PST) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id AAA20040 for hackers@freebsd.org; Sun, 2 Mar 1997 00:13:23 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.8.5/8.8.5) id AAA03773; Sun, 2 Mar 1997 00:06:41 +0100 (MET) Message-ID: Date: Sun, 2 Mar 1997 00:06:40 +0100 From: j@uriah.heep.sax.de (J Wunsch) To: hackers@freebsd.org Subject: Re: Another installment of the "dup alloc"/"bad dir" panic problems. References: <199703012227.PAA05697@phaeton.artisoft.com> X-Mailer: Mutt 0.55-PL10 Mime-Version: 1.0 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199703012227.PAA05697@phaeton.artisoft.com>; from Terry Lambert on Mar 1, 1997 15:27:15 -0700 Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk As Terry Lambert wrote: > > So, now the question I'm considering is "what could be some > > timing dependent that it affects both IDE and SCSI drivers?" > > 1542B? > > How much RAM do you have? > > If you have more than 16M ... it's bouncing. Try backing down to > 16M and not bouncing and see if that's where it is... Moot point, try again. I have seen it on a 1542A with 8 MB of RAM. Heikki has experienced it on his news servers, which are much larger machines that certainly don't suffer from ISA bus braindeadness (in this respect). No, if it were that simple, we'd be happy. -- 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-hackers Sat Mar 1 15:30:10 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id PAA04217 for hackers-outgoing; Sat, 1 Mar 1997 15:30:10 -0800 (PST) Received: from tyger.inna.net (root@tyger.inna.net [206.151.66.1]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id PAA04212 for ; Sat, 1 Mar 1997 15:30:07 -0800 (PST) Received: from dolphin.inna.net (jamie@dolphin.inna.net [206.151.66.2]) by tyger.inna.net (8.8.3/8.7.3) with SMTP id SAA05104; Sat, 1 Mar 1997 18:33:14 -0500 (EST) Date: Sat, 1 Mar 1997 18:29:46 -0500 (EST) From: Jamie Bowden To: "Jordan K. Hubbard" cc: Andrzej Bialecki , freebsd-hackers@FreeBSD.ORG Subject: Re: 2.2, 3.0 pkg_manage - where are you :-( In-Reply-To: <17166.857231990@time.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Shame that seems to be broken. On three different installs now, two over ftp, and one from a cd I burned, sysinstall will freeze during package installation. Everything seems to be fine, and it starts installing packages okay, but it will freeze up after about 10 packages or so. Everything else in sysinstall appears to be working flawlessly. On Sat, 1 Mar 1997, Jordan K. Hubbard wrote: > It's been replaced by ``/stand/sysinstall configPackages'' > > > Hello! > > > > Well, the subject says all... I really miss it. I didn't try yet to get > > the 2.1.7 ver and see if it works under 2.2 & current, but shouldn't it be > > included with the release? > > > > Andy > > > > +-------------------------------------------------------------------------+ > > Andrzej Bialecki _) _) _)_) _)_)_) _) _) > > --------------------------------------- _)_) _) _) _) _)_) _)_) > > Research and Academic Network in Poland _) _)_) _)_)_)_) _) _) _) > > Bartycka 18, 00-716 Warsaw, Poland _) _) _) _) _)_)_) _) _) > > +-------------------------------------------------------------------------+ > > > > > > Jamie Bowden Network Administrator, TBI Ltd. From owner-freebsd-hackers Sat Mar 1 16:12:05 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id QAA06137 for hackers-outgoing; Sat, 1 Mar 1997 16:12:05 -0800 (PST) Received: from labs.usn.blaze.net.au (labs.usn.blaze.net.au [203.17.53.30]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id QAA06107 for ; Sat, 1 Mar 1997 16:11:52 -0800 (PST) Received: (from davidn@localhost) by labs.usn.blaze.net.au (8.8.5/8.8.5) id LAA01133; Sun, 2 Mar 1997 11:11:43 +1100 (EST) Message-ID: <19970302111142.35178@usn.blaze.net.au> Date: Sun, 2 Mar 1997 11:11:42 +1100 From: David Nugent To: Lee Crites Cc: hackers@freebsd.org Subject: Re: Please help with digiboard switch settings... References: <1.5.4.32.19970301181002.006bc48c@jump.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.61 In-Reply-To: <1.5.4.32.19970301181002.006bc48c@jump.net>; from Lee Crites on Mar 03, 1997 at 12:10:02PM Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Mar 03, 1997 at 12:10:02PM, Lee Crites wrote: > When I boot up, I get an error message telling me that dgb cannot be found > at 0x220 (or whatever address I have tried that time). So, I just need to > set the proper dip-switches and go on, right? Right! However, the man who > built my server, which included installing my digiboard, has lost the > installation docu for the digiboard. See ftp.digiboard.com. As you say their web server also has most of the documentation for their boards on-line, although I've never looked there. > My first thought was to try their web site. No luck. The hardware > documentation which they have on-line, while it looks good, does not > describe anything like my card. And, of course, the supplied utility > just doesn't work on FreeBSD. Get a DOS disk and boot it, run the dos digiboard diagnostic from there. It probes for the card directly, so at least you should be able to find out what the card is set to. Failing that, contact Daniel Taylor . Regards, David Nugent - Unique Computing Pty Ltd - Melbourne, Australia Voice +61-3-9791-9547 Data/BBS +61-3-9792-3507 3:632/348@fidonet davidn@freebsd.org davidn@blaze.net.au http://www.blaze.net.au/~davidn/ From owner-freebsd-hackers Sat Mar 1 16:32:21 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id QAA07629 for hackers-outgoing; Sat, 1 Mar 1997 16:32:21 -0800 (PST) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.50]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id QAA07618 for ; Sat, 1 Mar 1997 16:32:15 -0800 (PST) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id RAA05832; Sat, 1 Mar 1997 17:28:16 -0700 From: Terry Lambert Message-Id: <199703020028.RAA05832@phaeton.artisoft.com> Subject: Re: Another installment of the "dup alloc"/"bad dir" panic problems. To: joerg_wunsch@uriah.heep.sax.de Date: Sat, 1 Mar 1997 17:28:16 -0700 (MST) Cc: hackers@freebsd.org In-Reply-To: from "J Wunsch" at Mar 2, 97 00:06: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-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > How much RAM do you have? > > > > If you have more than 16M ... it's bouncing. Try backing down to > > 16M and not bouncing and see if that's where it is... > > Moot point, try again. I have seen it on a 1542A with 8 MB of RAM. > Heikki has experienced it on his news servers, which are much larger > machines that certainly don't suffer from ISA bus braindeadness (in > this respect). > > No, if it were that simple, we'd be happy. It's not a moot point if it's being bounced. Wasn't it you who pointed me out to be wrong about whether or not the "BOUNCE_BUFFERS" option was necessary any more? 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-hackers Sat Mar 1 16:41:57 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id QAA08937 for hackers-outgoing; Sat, 1 Mar 1997 16:41:57 -0800 (PST) Received: from caipfs.rutgers.edu (root@caipfs.rutgers.edu [128.6.37.100]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id QAA08929 for ; Sat, 1 Mar 1997 16:41:51 -0800 (PST) Received: from jenolan.caipgeneral (jenolan.rutgers.edu [128.6.111.5]) by caipfs.rutgers.edu (8.8.5/8.8.5) with SMTP id TAA08715; Sat, 1 Mar 1997 19:41:02 -0500 (EST) Received: by jenolan.caipgeneral (SMI-8.6/SMI-SVR4) id TAA09403; Sat, 1 Mar 1997 19:40:50 -0500 Date: Sat, 1 Mar 1997 19:40:50 -0500 Message-Id: <199703020040.TAA09403@jenolan.caipgeneral> From: "David S. Miller" To: dg@root.com CC: netdev@roxanne.nuclecu.unam.mx, hackers@freebsd.org In-reply-to: <199703011703.JAA05291@root.com> (message from David Greenman on Sat, 01 Mar 1997 09:03:20 -0800) Subject: Re: ok, final sockhash changes, new diff Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk From: David Greenman Reply-To: dg@root.com Hi, David. I just looked at the hash algorithm you're using in tcp_hashfn()...I think it looks pretty good, and it's easy to see why it would have good distribution properties. I didn't think about using xor when I wrote the stuff for FreeBSD. :-( ...Anyway, I hope you don't mind if I change the algorithm in FreeBSD to use xor's. :-) It seems like the laddr/faddr would likely have a not-very-unique low order portion (since most hosts are assigned addresses in the low range of class A/B/C's), so it seems like this could perhaps be improved by combining the upper word of the IP address with the lower word...but perhaps this would be just extra overhead (since your analysis seems to show the distribution is already quite good). Keep in mind that if you don't consider the local address in the hash you'll get screwed on machines with thousands of IP aliases doing virtual web service for many blocks of class C's. BTW, one thing I didn't see in your code that was suggested to me a few months ago (and is also on my whiteboard), is another queue to move connections that have closed and are just waiting for the 2MSL wait to expire. In the case of busy WWW servers, it's common for the majority of the connections to be in this state, so by moving them off of the regular hashed queue and on to a private hashed queue, you can speed up the lookups for the active connections. Yes, I know about this issue. I didn't want to do it right now. It is an obvious problem, but there are cases where it would actually hurt to go through this effort. In reality my test data shows me: ? egrep TIME_WAIT best.com.1 | wc -l 238 ? egrep TIME_WAIT best.com.2 | wc -l 166 ? egrep TIME_WAIT best.com.3 | wc -l 321 ? egrep TIME_WAIT zero.genx.net.1 | wc -l 39 ? egrep FIN_WAIT zero.genx.net.1 | wc -l 614 ? A lot of machines get killed with stunk FIN_WAIT sockets as well as connections in 2MSL. As shown for zero, the TIME_WAIT connections aren't even worthwhile to deal with as the FIN_WAIT's are eating up most of the connection space. ---------------------------------------------//// Yow! 11.26 MB/s remote host TCP bandwidth & //// 199 usec remote TCP latency over 100Mb/s //// ethernet. Beat that! //// -----------------------------------------////__________ o David S. Miller, davem@caip.rutgers.edu /_____________/ / // /_/ >< From owner-freebsd-hackers Sat Mar 1 16:43:30 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id QAA09074 for hackers-outgoing; Sat, 1 Mar 1997 16:43:30 -0800 (PST) Received: from caipfs.rutgers.edu (root@caipfs.rutgers.edu [128.6.37.100]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id QAA09064 for ; Sat, 1 Mar 1997 16:43:24 -0800 (PST) Received: from jenolan.caipgeneral (jenolan.rutgers.edu [128.6.111.5]) by caipfs.rutgers.edu (8.8.5/8.8.5) with SMTP id TAA08766; Sat, 1 Mar 1997 19:43:17 -0500 (EST) Received: by jenolan.caipgeneral (SMI-8.6/SMI-SVR4) id TAA09413; Sat, 1 Mar 1997 19:43:05 -0500 Date: Sat, 1 Mar 1997 19:43:05 -0500 Message-Id: <199703020043.TAA09413@jenolan.caipgeneral> From: "David S. Miller" To: julian@whistle.com CC: hackers@freebsd.org In-reply-to: <3318A3B6.41C67EA6@whistle.com> (message from Julian Elischer on Sat, 01 Mar 1997 13:46:30 -0800) Subject: Re: overview of socket hashing changes, plus new patch Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Date: Sat, 01 Mar 1997 13:46:30 -0800 From: Julian Elischer David (Miller) Are you on any FreeBSD lists..? Yes I am. There has been some discussion going on and I am so encouraged by what seems like a civilised proffesional dialog between Linux and BSD camps on this topic that I just want to make sure that we endevour to keep the lines of communications open. I was actually impressed with the lack of fiery response when both my postings got forwarded here. ---------------------------------------------//// Yow! 11.26 MB/s remote host TCP bandwidth & //// 199 usec remote TCP latency over 100Mb/s //// ethernet. Beat that! //// -----------------------------------------////__________ o David S. Miller, davem@caip.rutgers.edu /_____________/ / // /_/ >< From owner-freebsd-hackers Sat Mar 1 16:51:57 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id QAA09661 for hackers-outgoing; Sat, 1 Mar 1997 16:51:57 -0800 (PST) Received: from caipfs.rutgers.edu (root@caipfs.rutgers.edu [128.6.37.100]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id QAA09648 for ; Sat, 1 Mar 1997 16:51:51 -0800 (PST) Received: from jenolan.caipgeneral (jenolan.rutgers.edu [128.6.111.5]) by caipfs.rutgers.edu (8.8.5/8.8.5) with SMTP id TAA08897; Sat, 1 Mar 1997 19:50:07 -0500 (EST) Received: by jenolan.caipgeneral (SMI-8.6/SMI-SVR4) id TAA09426; Sat, 1 Mar 1997 19:49:54 -0500 Date: Sat, 1 Mar 1997 19:49:54 -0500 Message-Id: <199703020049.TAA09426@jenolan.caipgeneral> From: "David S. Miller" To: bakul@chai.plexuscom.com CC: dennis@etinc.com, dg@root.com, proff@iq.org, hackers@FreeBSD.ORG In-reply-to: <199703012242.RAA04265@chai.plexuscom.com> (message from Bakul Shah on Sat, 01 Mar 1997 17:42:33 -0500) Subject: Re: optimised ip_input Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Date: Sat, 01 Mar 1997 17:42:33 -0500 From: Bakul Shah 2) Profiling the networking code in a production environment ought to point out the `hot spots' where much of the time is spent under various conditions. Measure various costs by changing data structure sizes and feeding similar traffic. Find out *why* the hot spots are the way they are; gain a deeper understanding of the structure and behavior of the networking code. Just a heads up, and this is from my own experience profiling this stuff. For freely running connections (ie. application at receiving end or sending end is continually filling a healthy pipe which is being kept reasonably full) the kernel spends a significant portion of time in soreceive() and sosend(). Unfortunatly, last time I checked, those are not fun functions to hack on and optimize due to their complexity. ---------------------------------------------//// Yow! 11.26 MB/s remote host TCP bandwidth & //// 199 usec remote TCP latency over 100Mb/s //// ethernet. Beat that! //// -----------------------------------------////__________ o David S. Miller, davem@caip.rutgers.edu /_____________/ / // /_/ >< From owner-freebsd-hackers Sat Mar 1 16:58:10 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id QAA10111 for hackers-outgoing; Sat, 1 Mar 1997 16:58:10 -0800 (PST) Received: from root.com (implode.root.com [198.145.90.17]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id QAA10105 for ; Sat, 1 Mar 1997 16:58:07 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by root.com (8.8.5/8.6.5) with SMTP id QAA00208; Sat, 1 Mar 1997 16:59:21 -0800 (PST) Message-Id: <199703020059.QAA00208@root.com> X-Authentication-Warning: implode.root.com: localhost [127.0.0.1] didn't use HELO protocol To: "David S. Miller" cc: netdev@roxanne.nuclecu.unam.mx, hackers@freebsd.org Subject: Re: ok, final sockhash changes, new diff In-reply-to: Your message of "Sat, 01 Mar 1997 19:40:50 EST." <199703020040.TAA09403@jenolan.caipgeneral> From: David Greenman Reply-To: dg@root.com Date: Sat, 01 Mar 1997 16:59:21 -0800 Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >Keep in mind that if you don't consider the local address in the hash >you'll get screwed on machines with thousands of IP aliases doing >virtual web service for many blocks of class C's. Hmmm. It seems that it might be better to add in the laddr if it contains additional variable information, but I don't see how not doing so would be a degenerate case when having a lot of IP aliases. The faddr, lport, and fport are still just as variable as in the non-lots-of-aliases case, so the hash distribution should be the same. -DG David Greenman Core-team/Principal Architect, The FreeBSD Project From owner-freebsd-hackers Sat Mar 1 17:03:40 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id RAA10397 for hackers-outgoing; Sat, 1 Mar 1997 17:03:40 -0800 (PST) Received: from caipfs.rutgers.edu (root@caipfs.rutgers.edu [128.6.37.100]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id RAA10381 for ; Sat, 1 Mar 1997 17:03:25 -0800 (PST) Received: from jenolan.caipgeneral (jenolan.rutgers.edu [128.6.111.5]) by caipfs.rutgers.edu (8.8.5/8.8.5) with SMTP id UAA09197; Sat, 1 Mar 1997 20:03:08 -0500 (EST) Received: by jenolan.caipgeneral (SMI-8.6/SMI-SVR4) id UAA09468; Sat, 1 Mar 1997 20:02:55 -0500 Date: Sat, 1 Mar 1997 20:02:55 -0500 Message-Id: <199703020102.UAA09468@jenolan.caipgeneral> From: "David S. Miller" To: dg@root.com CC: netdev@roxanne.nuclecu.unam.mx, hackers@freebsd.org In-reply-to: <199703020059.QAA00208@root.com> (message from David Greenman on Sat, 01 Mar 1997 16:59:21 -0800) Subject: Re: ok, final sockhash changes, new diff Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Reply-To: dg@root.com Date: Sat, 01 Mar 1997 16:59:21 -0800 Hmmm. It seems that it might be better to add in the laddr if it contains additional variable information, but I don't see how not doing so would be a degenerate case when having a lot of IP aliases. The faddr, lport, and fport are still just as variable as in the non-lots-of-aliases case, so the hash distribution should be the same. Good point, but alas there was a reason I considered it useful to add in the laddr to the hash, give me some time and I'll remember what the reason exactly was (it happens to cost nothing anyways ;-). ---------------------------------------------//// Yow! 11.26 MB/s remote host TCP bandwidth & //// 199 usec remote TCP latency over 100Mb/s //// ethernet. Beat that! //// -----------------------------------------////__________ o David S. Miller, davem@caip.rutgers.edu /_____________/ / // /_/ >< From owner-freebsd-hackers Sat Mar 1 17:52:33 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id RAA12760 for hackers-outgoing; Sat, 1 Mar 1997 17:52:33 -0800 (PST) Received: from pdx1.world.net (pdx1.world.net [192.243.32.18]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id RAA12755 for ; Sat, 1 Mar 1997 17:52:31 -0800 (PST) From: proff@suburbia.net Received: from suburbia.net (suburbia.net [203.4.184.1]) by pdx1.world.net (8.7.5/8.7.3) with SMTP id RAA28013 for ; Sat, 1 Mar 1997 17:54:15 -0800 (PST) Received: (qmail 2161 invoked by uid 110); 2 Mar 1997 01:51:40 -0000 Message-ID: <19970302015140.2160.qmail@suburbia.net> Subject: Re: ok, final sockhash changes, new diff In-Reply-To: <199703020040.TAA09403@jenolan.caipgeneral> from "David S. Miller" at "Mar 1, 97 07:40:50 pm" To: davem@jenolan.rutgers.edu (David S. Miller) Date: Sun, 2 Mar 1997 12:51:40 +1100 (EST) Cc: dg@root.com, netdev@roxanne.nuclecu.unam.mx, hackers@freebsd.org X-Mailer: ELM [version 2.4ME+ PL28 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > address with the lower word...but perhaps this would be just extra > overhead (since your analysis seems to show the distribution is > already quite good). > > Keep in mind that if you don't consider the local address in the hash > you'll get screwed on machines with thousands of IP aliases doing > virtual web service for many blocks of class C's. No, you only need 8 bits of entropy if your hash table is 256 entries long. This is easily contained in the remote addr, remote port and local port. It doesn't matter how many thousands of virtual addr port 80's you have, because the same port at the same remote will not be connecting to them all at the same time. Infact you could probably get away with just using the remote port and remote addr. -- Prof. Julian Assange |If you want to build a ship, don't drum up people |together to collect wood and don't assign them tasks proff@iq.org |and work, but rather teach them to long for the endless proff@gnu.ai.mit.edu |immensity of the sea. -- Antoine de Saint Exupery From owner-freebsd-hackers Sat Mar 1 17:55:11 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id RAA12918 for hackers-outgoing; Sat, 1 Mar 1997 17:55:11 -0800 (PST) Received: from root.com (implode.root.com [198.145.90.17]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id RAA12913 for ; Sat, 1 Mar 1997 17:55:09 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by root.com (8.8.5/8.6.5) with SMTP id RAA00329; Sat, 1 Mar 1997 17:56:24 -0800 (PST) Message-Id: <199703020156.RAA00329@root.com> X-Authentication-Warning: implode.root.com: localhost [127.0.0.1] didn't use HELO protocol To: "David S. Miller" cc: netdev@roxanne.nuclecu.unam.mx, hackers@FreeBSD.ORG Subject: Re: ok, final sockhash changes, new diff In-reply-to: Your message of "Sat, 01 Mar 1997 20:02:55 EST." <199703020102.UAA09468@jenolan.caipgeneral> From: David Greenman Reply-To: dg@root.com Date: Sat, 01 Mar 1997 17:56:24 -0800 Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > Reply-To: dg@root.com > Date: Sat, 01 Mar 1997 16:59:21 -0800 > > Hmmm. It seems that it might be better to add in the laddr if it > contains additional variable information, but I don't see how not > doing so would be a degenerate case when having a lot of IP > aliases. The faddr, lport, and fport are still just as variable as > in the non-lots-of-aliases case, so the hash distribution should be > the same. > >Good point, but alas there was a reason I considered it useful to add >in the laddr to the hash, give me some time and I'll remember what the >reason exactly was (it happens to cost nothing anyways ;-). The reason just occured to me: In the case of a server with googols of IP aliases, the {faddr, lport, fport} are all the same (faddr and fport are wildcards) for the listening sockets of a given service (say http)...so the only thing unique is the laddr, which if not included in the hash, will cause all of the listening sockets to be hashed to the same bucket. -DG David Greenman Core-team/Principal Architect, The FreeBSD Project From owner-freebsd-hackers Sat Mar 1 17:56:12 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id RAA13004 for hackers-outgoing; Sat, 1 Mar 1997 17:56:12 -0800 (PST) Received: from caipfs.rutgers.edu (root@caipfs.rutgers.edu [128.6.37.100]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id RAA12999 for ; Sat, 1 Mar 1997 17:56:10 -0800 (PST) Received: from jenolan.caipgeneral (jenolan.rutgers.edu [128.6.111.5]) by caipfs.rutgers.edu (8.8.5/8.8.5) with SMTP id UAA10333; Sat, 1 Mar 1997 20:55:47 -0500 (EST) Received: by jenolan.caipgeneral (SMI-8.6/SMI-SVR4) id UAA09547; Sat, 1 Mar 1997 20:55:35 -0500 Date: Sat, 1 Mar 1997 20:55:35 -0500 Message-Id: <199703020155.UAA09547@jenolan.caipgeneral> From: "David S. Miller" To: proff@suburbia.net CC: dg@root.com, netdev@roxanne.nuclecu.unam.mx, hackers@freebsd.org In-reply-to: <19970302015140.2160.qmail@suburbia.net> (proff@suburbia.net) Subject: Re: ok, final sockhash changes, new diff Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk From: proff@suburbia.net Date: Sun, 2 Mar 1997 12:51:40 +1100 (EST) No, you only need 8 bits of entropy if your hash table is 256 entries long. This is easily contained in the remote addr, remote port and local port. It doesn't matter how many thousands of virtual addr port 80's you have, because the same port at the same remote will not be connecting to them all at the same time. Infact you could probably get away with just using the remote port and remote addr. What if you have a seperate listening socket for port 80 on each of those IP aliases? I've seen people actually do this. ---------------------------------------------//// Yow! 11.26 MB/s remote host TCP bandwidth & //// 199 usec remote TCP latency over 100Mb/s //// ethernet. Beat that! //// -----------------------------------------////__________ o David S. Miller, davem@caip.rutgers.edu /_____________/ / // /_/ >< From owner-freebsd-hackers Sat Mar 1 17:56:50 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id RAA13064 for hackers-outgoing; Sat, 1 Mar 1997 17:56:50 -0800 (PST) Received: from caipfs.rutgers.edu (root@caipfs.rutgers.edu [128.6.37.100]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id RAA13059 for ; Sat, 1 Mar 1997 17:56:47 -0800 (PST) Received: from jenolan.caipgeneral (jenolan.rutgers.edu [128.6.111.5]) by caipfs.rutgers.edu (8.8.5/8.8.5) with SMTP id UAA10352; Sat, 1 Mar 1997 20:56:33 -0500 (EST) Received: by jenolan.caipgeneral (SMI-8.6/SMI-SVR4) id UAA09551; Sat, 1 Mar 1997 20:56:20 -0500 Date: Sat, 1 Mar 1997 20:56:20 -0500 Message-Id: <199703020156.UAA09551@jenolan.caipgeneral> From: "David S. Miller" To: dg@root.com CC: netdev@roxanne.nuclecu.unam.mx, hackers@FreeBSD.ORG In-reply-to: <199703020156.RAA00329@root.com> (message from David Greenman on Sat, 01 Mar 1997 17:56:24 -0800) Subject: Re: ok, final sockhash changes, new diff Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk From: David Greenman Date: Sat, 01 Mar 1997 17:56:24 -0800 The reason just occured to me: In the case of a server with googols of IP aliases, the {faddr, lport, fport} are all the same (faddr and fport are wildcards) for the listening sockets of a given service (say http)...so the only thing unique is the laddr, which if not included in the hash, will cause all of the listening sockets to be hashed to the same bucket. Jinx, you'll see that I just made a posting stating this as well ;) ---------------------------------------------//// Yow! 11.26 MB/s remote host TCP bandwidth & //// 199 usec remote TCP latency over 100Mb/s //// ethernet. Beat that! //// -----------------------------------------////__________ o David S. Miller, davem@caip.rutgers.edu /_____________/ / // /_/ >< From owner-freebsd-hackers Sat Mar 1 17:57:02 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id RAA13092 for hackers-outgoing; Sat, 1 Mar 1997 17:57:02 -0800 (PST) Received: from melbourne.DIALix.oz.au (uucp@melbourne.DIALix.oz.au [192.203.228.98]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id RAA13069 for ; Sat, 1 Mar 1997 17:56:50 -0800 (PST) Received: (from uucp@localhost) by melbourne.DIALix.oz.au with UUCP id MAA22104; Sun, 2 Mar 1997 12:55:57 +1100 (EST) Received: (from mark@localhost) by doorway.seeware.DIALix.oz.au (8.7.5/8.7.3) id MAA27932; Sun, 2 Mar 1997 12:47:15 +1100 (EST) Date: Sun, 2 Mar 1997 12:47:13 +1100 (EST) From: Mark Hannon To: Zach Heilig cc: freebsd-hackers@freebsd.org Subject: Re: Alt key in syscons In-Reply-To: <19970228081022.42769@gaffaneys.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Fri, 28 Feb 1997, Zach Heilig wrote: > > I looked through the mailing list archives for info on how to setup > > emacs to use the meta-key in syscons and saw the question, some answers > Here is the one I use. It is basically the standard keymap (from 2.1.0) > with the boot commands removed and the alt key mapped to meta. > > # alt > # scan cntrl alt alt cntrl lock > # code base shift cntrl shift alt shift cntrl shift state > # ------------------------------------------------------------------ > 000 nop nop nop nop nop nop nop nop O > 001 esc esc nop nop 0x9b 0x9b nop nop O > Hi, Well I've installed this keymap (changing back to the default boot behaviour & backspace behaviour) and hey presto not only does xemacs work on the console, but I can also use the Meta key in tcsh. Is there any reason why this shouldn't be the default keymap? Does it break something? If not I can go through all the standard keymaps and modify them for this and send it to ?? for submission. Regards/Mark +-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-+ | Mark Hannon,| FreeBSD, Free Unix for your PC | mark@seeware.DIALix.oz.au| | Melbourne, | PGP key available by fingering | epamha@epa.ericsson.se | | Australia | seeware@melbourne.DIALix.oz.au | | +-=-=-=-=-=-=-+-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-+ From owner-freebsd-hackers Sat Mar 1 18:14:12 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id SAA13893 for hackers-outgoing; Sat, 1 Mar 1997 18:14:12 -0800 (PST) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id SAA13888 for ; Sat, 1 Mar 1997 18:14:10 -0800 (PST) Received: from time.cdrom.com (jkh@localhost [127.0.0.1]) by time.cdrom.com (8.8.5/8.6.9) with ESMTP id SAA18781; Sat, 1 Mar 1997 18:13:51 -0800 (PST) To: Jamie Bowden cc: Andrzej Bialecki , freebsd-hackers@FreeBSD.ORG Subject: Re: 2.2, 3.0 pkg_manage - where are you :-( In-reply-to: Your message of "Sat, 01 Mar 1997 18:29:46 EST." Date: Sat, 01 Mar 1997 18:13:51 -0800 Message-ID: <18778.857268831@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > Shame that seems to be broken. On three different installs now, two over > ftp, and one from a cd I burned, sysinstall will freeze during package > installation. Everything seems to be fine, and it starts installing > packages okay, but it will freeze up after about 10 packages or so. > Everything else in sysinstall appears to be working flawlessly. Hmmmm. Weird! I thought that was all working again now, at least it seems to work for me. I'll do some more testing this weekend and see what I can do. If I find a genuine bug, I can at least get it fixed for 2.2. Jordan From owner-freebsd-hackers Sat Mar 1 19:07:04 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id TAA16033 for hackers-outgoing; Sat, 1 Mar 1997 19:07:04 -0800 (PST) Received: from chai.plexuscom.com (chai.plexuscom.com [207.87.46.100]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id TAA16018 for ; Sat, 1 Mar 1997 19:06:58 -0800 (PST) Received: from chai.plexuscom.com (localhost.torrentnet.com [127.0.0.1]) by chai.plexuscom.com (8.8.5/8.8.5) with ESMTP id WAA10813; Sat, 1 Mar 1997 22:06:42 -0500 (EST) Message-Id: <199703020306.WAA10813@chai.plexuscom.com> To: "David S. Miller" CC: dennis@etinc.com, dg@root.com, proff@suburbia.net, hackers@FreeBSD.ORG Subject: Re: optimised ip_input In-reply-to: Your message of "Sat, 01 Mar 1997 19:49:54 EST." <199703020049.TAA09426@jenolan.caipgeneral> Date: Sat, 01 Mar 1997 22:06:42 -0500 From: Bakul Shah Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > From: Bakul Shah > 2) Profiling the networking code in a production environment ought > to point out the `hot spots' where much of the time is spent > under various conditions. Measure various costs by changing data > structure sizes and feeding similar traffic. Find out *why* the > hot spots are the way they are; gain a deeper understanding of > the structure and behavior of the networking code. > Just a heads up, and this is from my own experience profiling this > stuff. For freely running connections (ie. application at receiving > end or sending end is continually filling a healthy pipe which is > being kept reasonably full) the kernel spends a significant portion of > time in soreceive() and sosend(). Unfortunatly, last time I checked, > those are not fun functions to hack on and optimize due to their > complexity. That is good to know. Is this for Linux or for BSD derived stacks? What does a finer grained profiling of so{receive,send} show? It would be interesting to know the top time consuming functions that add up to >90% of the time. I don't see how complexity be reduced without some restructuring.... soreceive() has too many paths through it. One trick to untangle funtions like soreceive() is to fold parts of the function into smaller inline functions. May be some of these inline functions can be used at the call sites of soreceive() so as to reduce the number of arguments. This in turn will obviate the need to decide in soreceive() which code path to take. Depending on what gets done in the paths that are most common, one can also define two (or more) specialized version of a function and cache a ptr to the appropriate one in the caller's data structure. While this sort of equivalent transformations are not fun, what one learns about the needs of the `clients' of a function is essential for the next step of a real restructuring. Also, this next step becomes somewhat easier, and more fun thanks to the reduced clutter. For some reason the BSD kernel seems to favor generalized functions to specialized ones -- perhaps because decomposition of a big function is costly if functions are used and error prone if macros are used and inline functions are not a standard feature of C. Anyway, using specialized functions one can much more easily customize a system depending on its primary functions (a router/a web-server for zillion addresses/address translation/ highly secure communication/a plain old boring host etc.) without turning the kernel into a kitchen sink. -- bakul From owner-freebsd-hackers Sat Mar 1 21:14:19 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id VAA21737 for hackers-outgoing; Sat, 1 Mar 1997 21:14:19 -0800 (PST) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id VAA21732 for ; Sat, 1 Mar 1997 21:14:13 -0800 (PST) Received: (from msmith@localhost) by genesis.atrad.adelaide.edu.au (8.8.5/8.7.3) id PAA19629; Sun, 2 Mar 1997 15:43:58 +1030 (CST) From: Michael Smith Message-Id: <199703020513.PAA19629@genesis.atrad.adelaide.edu.au> Subject: Re: truncated-ip - 101 bytes missing... In-Reply-To: from J Wunsch at "Mar 1, 97 07:15:56 pm" To: joerg_wunsch@uriah.heep.sax.de Date: Sun, 2 Mar 1997 15:43:50 +1030 (CST) Cc: freebsd-hackers@freebsd.org X-Mailer: ELM [version 2.4ME+ PL28 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk J Wunsch stands accused of saying: > I think we already had this discussion at some point. Yes! > I've tried to fetch the linux_lib distfile from my closes mirror. > After transferring 4019200 bytes, the transfer stalled. I tried to Same here. For those curious, I replaced the modems in use with completely different models. Same problem. > The SLIP interface ran with an MTU of 552. Likewise. > I stopped the SLIP session and started a PPP session -- everything's ok. I haven't tried PPP yet; looks like we have a bogon in the SLIP code. Can you try without the VJ header compression? (I have trouble playing with the link I was having problems with as it's our office's only link to the rest of the world, and whn it goes down people start clustering around my desk and whining 8() > Isn't it a little surprising that the above behaviour happens at exact > the same spot in the file? Er yeah. Sounds like a bogon in the SLIP code somewhere 8( Is your PPP link using the kernel PPP or user-mode PPP? > cheers, J"org -- ]] Mike Smith, Software Engineer msmith@gsoft.com.au [[ ]] Genesis Software genesis@gsoft.com.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control. (ph) +61-8-8267-3493 [[ ]] Unix hardware collector. "Where are your PEZ?" The Tick [[ From owner-freebsd-hackers Sat Mar 1 22:18:58 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id WAA24183 for hackers-outgoing; Sat, 1 Mar 1997 22:18:58 -0800 (PST) Received: from becker2.u.washington.edu (spaz@becker2.u.washington.edu [140.142.12.68]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id WAA24177 for ; Sat, 1 Mar 1997 22:18:55 -0800 (PST) Received: from localhost (spaz@localhost) by becker2.u.washington.edu (8.8.4+UW96.12/8.8.4+UW97.02) with SMTP id WAA25935 for ; Sat, 1 Mar 1997 22:18:53 -0800 (PST) Date: Sat, 1 Mar 1997 22:18:53 -0800 (PST) From: John Utz To: hackers@freebsd.org Subject: ip-aliasing and X, a fix! sortof... Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hello everybody; I have found that it is possible to toss up displays on my fake network from outside clients using ijppp+Aliasing-1.9 and dxpc-3.4.0. The dxpc compression utility evidently turns X-packets into standard ip type packets ( i guess ) and then ships them out. This allows them to be shipped via the aliasing feature. So all one needs to do is start the two dxpc processes on each end. Then it all sort of just works... result? a xload initiated on 128.95.120.1 shows up on 10.0.0.1! yippee! just thought somebody might want to know..... ******************************************************************************* John Utz spaz@u.washington.edu idiocy is the impulse function in the convolution of life From owner-freebsd-hackers Sat Mar 1 22:22:57 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id WAA24334 for hackers-outgoing; Sat, 1 Mar 1997 22:22:57 -0800 (PST) Received: from asstdc.scgt.oz.au (root@asstdc.scgt.oz.au [202.14.234.65]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id WAA24328 for ; Sat, 1 Mar 1997 22:22:42 -0800 (PST) Received: (from imb@localhost) by asstdc.scgt.oz.au (8.8.5/BSD4.4) id RAA12400 Sun, 2 Mar 1997 17:21:36 +1100 (EST) From: michael butler Message-Id: <199703020621.RAA12400@asstdc.scgt.oz.au> Subject: Re: ok, final sockhash changes, new diff In-Reply-To: <199703020156.RAA00329@root.com> from David Greenman at "Mar 1, 97 05:56:24 pm" To: dg@root.com Date: Sun, 2 Mar 1997 17:21:35 +1100 (EST) Cc: davem@jenolan.rutgers.edu, netdev@roxanne.nuclecu.unam.mx, hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL28 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk David Greenman writes: > The reason just occured to me: In the case of a server with googols of > IP aliases, the {faddr, lport, fport} are all the same (faddr and fport > are wildcards) for the listening sockets of a given service (say > http)...so the only thing unique is the laddr, which if not included in > the hash, will cause all of the listening sockets to be hashed to the same > bucket. This being the case, a simple counter (number of listens performed) added to the hash would help redistribute across buckets - don't care about wrap-around .. or am I off the planet ? :-) michael From owner-freebsd-hackers Sat Mar 1 22:28:18 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id WAA24567 for hackers-outgoing; Sat, 1 Mar 1997 22:28:18 -0800 (PST) Received: from caipfs.rutgers.edu (root@caipfs.rutgers.edu [128.6.37.100]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id WAA24533 for ; Sat, 1 Mar 1997 22:28:06 -0800 (PST) Received: from jenolan.caipgeneral (jenolan.rutgers.edu [128.6.111.5]) by caipfs.rutgers.edu (8.8.5/8.8.5) with SMTP id BAA17101; Sun, 2 Mar 1997 01:27:59 -0500 (EST) Received: by jenolan.caipgeneral (SMI-8.6/SMI-SVR4) id BAA09925; Sun, 2 Mar 1997 01:27:46 -0500 Date: Sun, 2 Mar 1997 01:27:46 -0500 Message-Id: <199703020627.BAA09925@jenolan.caipgeneral> From: "David S. Miller" To: imb@scgt.oz.au CC: dg@root.com, netdev@roxanne.nuclecu.unam.mx, hackers@FreeBSD.ORG In-reply-to: <199703020621.RAA12400@asstdc.scgt.oz.au> (message from michael butler on Sun, 2 Mar 1997 17:21:35 +1100 (EST)) Subject: Re: ok, final sockhash changes, new diff Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk From: michael butler Date: Sun, 2 Mar 1997 17:21:35 +1100 (EST) This being the case, a simple counter (number of listens performed) added to the hash would help redistribute across buckets - don't care about wrap-around .. or am I off the planet ? :-) Huh? The placement within the tables is a product of the hash, and thus the length of the chains is as well. No counter can help change this situation. The only solution is to hash in the local IP address contained in the socket's identity. ---------------------------------------------//// Yow! 11.26 MB/s remote host TCP bandwidth & //// 199 usec remote TCP latency over 100Mb/s //// ethernet. Beat that! //// -----------------------------------------////__________ o David S. Miller, davem@caip.rutgers.edu /_____________/ / // /_/ >< From owner-freebsd-hackers Sat Mar 1 22:31:39 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id WAA24784 for hackers-outgoing; Sat, 1 Mar 1997 22:31:39 -0800 (PST) Received: from asstdc.scgt.oz.au (root@asstdc.scgt.oz.au [202.14.234.65]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id WAA24767 for ; Sat, 1 Mar 1997 22:31:24 -0800 (PST) Received: (from imb@localhost) by asstdc.scgt.oz.au (8.8.5/BSD4.4) id RAA12630 Sun, 2 Mar 1997 17:30:17 +1100 (EST) From: michael butler Message-Id: <199703020630.RAA12630@asstdc.scgt.oz.au> Subject: Re: ok, final sockhash changes, new diff In-Reply-To: <199703020627.BAA09925@jenolan.caipgeneral> from "David S. Miller" at "Mar 2, 97 01:27:46 am" To: davem@jenolan.rutgers.edu (David S. Miller) Date: Sun, 2 Mar 1997 17:30:16 +1100 (EST) Cc: dg@root.com, netdev@roxanne.nuclecu.unam.mx, hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL28 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk David S. Miller writes: > Huh? .. I was right second time .. off the planet .. should know better than to go near keyboard on large mailing list with too little sleep, sorry :-( michael