From owner-freebsd-hackers Sun Sep 26 0: 1: 1 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from scotty.masternet.it (scotty.masternet.it [194.184.65.2]) by hub.freebsd.org (Postfix) with ESMTP id 3F6CA14A26 for ; Sun, 26 Sep 1999 00:00:54 -0700 (PDT) (envelope-from gmarco@scotty.masternet.it) Received: from suzy (modem11.masternet.it [194.184.65.21]) by scotty.masternet.it (8.9.3/8.9.3) with ESMTP id JAA21610 for ; Sun, 26 Sep 1999 09:00:53 +0200 (CEST) (envelope-from gmarco@scotty.masternet.it) Message-Id: <4.2.0.58.19990926090211.009e0dd0@194.184.65.4> X-Sender: gmarco@scotty.masternet.it X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.58 Date: Sun, 26 Sep 1999 09:05:20 +0200 To: freebsd-hackers@FreeBSD.ORG From: Gianmarco Giovannelli Subject: Re: A new package fetching utility, pkg_get In-Reply-To: <199909252352.BAA26437@dorifer.heim3.tu-clausthal.de> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 26/09/99, you wrote: >The second script is called "pkg_rm"; it can be used to delete >packages like pkg_delete, but you can use arguments in the same >way as for pkg_ls above (i.e. "pkg_rm lynx"). Think of it like >pkg_info | grep | pkg_delete. > >It might more sense to implement these features in pkg_info and >pkg_delete, resprectively, but I don't have the time to do that >(and these scripts work fine, so I have no incentive to bother >with the C sources of pkg_{info,delete}). What about to extend the pkg_delete to use a syntax like : pkg_delete /var/db/pkg/netscape-communicator-4.61/ it can help so much everyone that can automagically complete file/path names with the shell :-) Best Regards, Gianmarco Giovannelli , "Unix expert since yesterday" http://www.giovannelli.it/~gmarco http://www2.masternet.it To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Sep 26 1:24:52 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id D0C9C14C97 for ; Sun, 26 Sep 1999 01:24:49 -0700 (PDT) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id KAA65733; Sun, 26 Sep 1999 10:24:04 +0200 (CEST) (envelope-from sos) From: Soren Schmidt Message-Id: <199909260824.KAA65733@freebsd.dk> Subject: Re: wormcontrol write speed In-Reply-To: <19990926020604.A21048@netmonger.net> from Christopher Masto at "Sep 26, 1999 02:06:04 am" To: chris@netmonger.net (Christopher Masto) Date: Sun, 26 Sep 1999 10:24:03 +0200 (CEST) Cc: doconnor@gsoft.com.au (Daniel O'Connor), freebsd-hackers@FreeBSD.ORG, paulo@nlink.com.br X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems Christopher Masto wrote: > On Wed, Sep 22, 1999 at 09:27:37AM +0200, Soren Schmidt wrote: > > Anyhow, I have some changes to the worm stuff, it needs to be dealt with > > to handle modern HW, and to deal with all the possible block formats > > thats possible on a CD nowadays. It will probably mean the death of > > the worm stuff as is now, but I'm the last user anyways so.... > > Any chance of getting a passthrough or "SCSI emulation" so that > cdrecord could be used instead? (Then you won't have to worry about > different CD-R quirks) If somebody writes it there is a chance. I dont have this on my TODO list. I could maybe be talked into providing a generic ATAPI interface that would give you a method of injecting ATAPI commands directly into the systemi, cdrecord etc could use that then. > I have an Acer CRW 6202A which doesn't seem to work with FreeBSD > (current as of five minutes ago, including the rev 1.19 of > atapi-cd.c). "wormcontrol blank" (with a CD-RW of course) runs for a > little while, then aborts with an I/O error. Also, all IDE devices > are completely locked up while it's running. What I/O error ?? its impossible to diagnose on no data... > The dd also sort of works for a while, then gets an I/O error. Same > with fixate (which also locks up the IDE busses). What I/O error ?? its impossible to diagnose on no data... > I'm currently recompiling with ATAPI_DEBUG and ACD_DEBUG in the hopes > that I'll be able to produce a better bug report. Any suggestions? Provide data, the system spits out lots of sensekey things and the like on errors, those are invaluable data to diagnose this... -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Sep 26 2:19:37 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id B5F5114C83 for ; Sun, 26 Sep 1999 02:19:35 -0700 (PDT) (envelope-from jkh@zippy.cdrom.com) Received: from localhost (localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id CAA15229; Sun, 26 Sep 1999 02:19:20 -0700 (PDT) (envelope-from jkh@zippy.cdrom.com) To: Chris Piazza Cc: "Jordan K. Hubbard" , Bill Fumerola , Jaakko Salomaa , hackers@FreeBSD.ORG Subject: Re: A new package fetching utility, pkg_get In-reply-to: Your message of "Fri, 24 Sep 1999 14:03:57 PDT." <19990924140357.A71450@norn.ca.eu.org> Date: Sun, 26 Sep 1999 02:19:20 -0700 Message-ID: <15226.938337560@localhost> From: "Jordan K. Hubbard" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Erm, I must admit, I've never actually tried it or Debian Linux. It merely seemed reasonable humor-fodder. :) - Jordan > On Fri, Sep 24, 1999 at 12:54:32PM -0700, Jordan K. Hubbard wrote: > > > Most of what you've shown can be accomplished with 'pkg_add -r' and > > > some enviromental variables. > > > > In its current incarnation, that's pretty much true. However, we also > > intend to throw feature upon feature request onto his pile until > > Jaakko ends up reproducing the Debian package manager for us! :-) > ^^^^^^^^^^^^^^^^^^^^^^ > > Have you actually used that? If so, and you want to reproduce it, > I question your sanity. > > -Chris > -- > :Chris Piazza : Abbotsford, BC: > :cpiazza@home.net : cpiazza@FreeBSD.org: > : : : > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Sep 26 3:14:59 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from akat.civ.cvut.cz (akat.civ.cvut.cz [147.32.235.105]) by hub.freebsd.org (Postfix) with SMTP id E751D14D4D for ; Sun, 26 Sep 1999 03:14:52 -0700 (PDT) (envelope-from pechy@hp735.cvut.cz) Received: from localhost (pechy@localhost) by akat.civ.cvut.cz (950413.SGI.8.6.12/950213.SGI.AUTOCF) via ESMTP id MAA15741; Sun, 26 Sep 1999 12:14:37 +0200 Date: Sun, 26 Sep 1999 12:14:37 +0200 From: Jan Pechanec X-Sender: pechy@akat.civ.cvut.cz To: andrew@ugh.net.au Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Corrupt File System In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 26 Sep 1999 andrew@ugh.net.au wrote: Isn't you partition table corrupted? What does it mean ``No bootmanager sees it''? If BootEasy doesn't display FBSD partition in its menu, the partition table in MBR is bad. If BootEasy can see it, but refuses to load the system, the problem is with the FreeBSD partition itself, probably. Jan. >Hi, > >I have an 8GB IDE HD with FreeBSD on the last (4th) partition. I tried to >install Rhapsody (MacOS X) DR2 the other day and now I cant find FreeBSD >(No bootmanager sees it)...If I boot FReeBSD from a seperate HD and >try and mount the partions I get: > >incorrect super block > >I have tried the dd and vnconfig trick posted to the list a while ago. > >I get outputs like: > > >fs at block # 526784 last mounted on /usr f->fs_ncyl=1840 > (1 4096 4096 = 7536640) >fs at block # 526800 last mounted on f->fs_ncyl=1840 > (1 4096 4096 = 7536640) >fs at block # 592336 last mounted on f->fs_ncyl=1840 > (1 4096 4096 = 7536640) > > >I then type: > >dd if=/dev/rwd2s4 of=usr.raw bs=512 skip=526783 count=7536640 >vnconfig /dev/vn0c usr.raw > >skip is one less than the number given in the output to make sure the >first block is included. When I try to fsck /dev/rvn0c I get: > >** /dev/rvn0 >BAD SUPER BLOCK: VALUES IN SUPER BLOCK DISAGREE WITH THOSE IN FIRST >ALTERNATE >ioctl (GCINFO): Inappropriate ioctl for device >fsck: /dev/rvn0: can't read disk label > >Trying to mount /dev/vn0 Produces a file /mnt (not a directory) > > >Any suggestions? > >Thanks, > >Andrew > > > > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-hackers" in the body of the message > -- Jan PECHANEC (mailto:pechy@hp735.cvut.cz) Computing Center CTU (Zikova 4, Praha 6, 166 35, Czech Republic) http://www.civ.cvut.cz, tel: +420 2 2435 2969, http://pechy.civ.cvut.cz To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Sep 26 4:53:45 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from ns.skylink.it (ns.skylink.it [194.177.113.1]) by hub.freebsd.org (Postfix) with ESMTP id BD8B8151BD for ; Sun, 26 Sep 1999 04:53:41 -0700 (PDT) (envelope-from hibma@skylink.it) Received: from heidi.plazza.it (va-154.skylink.it [194.185.55.154]) by ns.skylink.it (8.9.1/8.8.8) with ESMTP id NAA08543; Sun, 26 Sep 1999 13:54:15 +0200 Received: from localhost (localhost [127.0.0.1]) by heidi.plazza.it (8.9.3/8.8.5) with ESMTP id LAA29741; Sun, 26 Sep 1999 11:49:11 GMT X-No-Spam: Neither the receipients nor the senders email address(s) are to be used for Unsolicited (Commercial) Email without the explicit written consent of either party; as a per-message fee is incurred for inbound and outbound traffic to the originator. Posted-Date: Sun, 26 Sep 1999 11:49:11 GMT Date: Sun, 26 Sep 1999 13:49:11 +0200 (CEST) From: Nick Hibma X-Sender: n_hibma@heidi.plazza.it Reply-To: Nick Hibma To: Soren Schmidt Cc: Christopher Masto , "Daniel O'Connor" , freebsd-hackers@FreeBSD.ORG, paulo@nlink.com.br Subject: Re: wormcontrol write speed In-Reply-To: <199909260824.KAA65733@freebsd.dk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=X-UNKNOWN Content-Transfer-Encoding: QUOTED-PRINTABLE Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG And, oh while you are at it, why not create a CAM SIM that makes IDE available through CAM. That would save me a lot of work :-) Nick On Sun, 26 Sep 1999, Soren Schmidt wrote: > It seems Christopher Masto wrote: > > On Wed, Sep 22, 1999 at 09:27:37AM +0200, Soren Schmidt wrote: > > > Anyhow, I have some changes to the worm stuff, it needs to be dealt w= ith > > > to handle modern HW, and to deal with all the possible block formats > > > thats possible on a CD nowadays. It will probably mean the death of > > > the worm stuff as is now, but I'm the last user anyways so.... > >=20 > > Any chance of getting a passthrough or "SCSI emulation" so that > > cdrecord could be used instead? (Then you won't have to worry about > > different CD-R quirks) >=20 > If somebody writes it there is a chance. I dont have this on my TODO > list. I could maybe be talked into providing a generic ATAPI interface > that would give you a method of injecting ATAPI commands directly > into the systemi, cdrecord etc could use that then. >=20 > > I have an Acer CRW 6202A which doesn't seem to work with FreeBSD > > (current as of five minutes ago, including the rev 1.19 of > > atapi-cd.c). "wormcontrol blank" (with a CD-RW of course) runs for a > > little while, then aborts with an I/O error. Also, all IDE devices > > are completely locked up while it's running. >=20 > What I/O error ?? its impossible to diagnose on no data... > =20 > > The dd also sort of works for a while, then gets an I/O error. Same > > with fixate (which also locks up the IDE busses). >=20 > What I/O error ?? its impossible to diagnose on no data... > =20 > > I'm currently recompiling with ATAPI_DEBUG and ACD_DEBUG in the hopes > > that I'll be able to produce a better bug report. Any suggestions? >=20 > Provide data, the system spits out lots of sensekey things and the > like on errors, those are invaluable data to diagnose this... >=20 > -S=F8ren >=20 >=20 >=20 > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message >=20 >=20 --=20 e-Mail: hibma@skylink.it To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Sep 26 5: 5:39 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from nothing-going-on.demon.co.uk (nothing-going-on.demon.co.uk [193.237.89.66]) by hub.freebsd.org (Postfix) with ESMTP id 4715614BE2 for ; Sun, 26 Sep 1999 05:05:20 -0700 (PDT) (envelope-from nik@nothing-going-on.demon.co.uk) Received: (from nik@localhost) by nothing-going-on.demon.co.uk (8.9.3/8.9.3) id BAA50540; Sun, 26 Sep 1999 01:23:52 +0100 (BST) (envelope-from nik) Date: Sun, 26 Sep 1999 01:23:52 +0100 From: Nik Clayton To: Christian Carstensen Cc: Chris Costello , freebsd-hackers@FreeBSD.ORG Subject: Re: updating packages automatically... Message-ID: <19990926012352.A49346@catkin.nothing-going-on.org> References: <19990925180201.C76486@holly.calldei.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: ; from Christian Carstensen on Sun, Sep 26, 1999 at 01:11:32AM +0200 Organization: FreeBSD Project Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Sep 26, 1999 at 01:11:32AM +0200, Christian Carstensen wrote: > On Sat, 25 Sep 1999, Chris Costello wrote: > > Aah! No! I tried that with GNOME once and it drove me insane > > for about two weeks. > > > > Auto-upgrades on ports would be _very_ _very_ bad, especially > > for those using apache from ports! > > that's right. i thought about having some kind of exclude list for ports > that shall never be upgraded automatically. anyway, the script will just > generate a shell script output. it should not replace packages without > manual intervention. If you're interested, I've got patches for sysutils/pkg_version that support a '-c' flag (for 'commands') that show you the commands you should run to update any out of date ports. I cron this and mail the output out once a week. You could have it automatically create and execute a shell script if you wanted. Sample output from one of my boxes is: # # ORBit # needs updating (index has 0.4.93) # cd /usr/ports/devel/ORBit make clean all pkg_delete -f ORBit-0.4.3 make install # # docbook-xml # needs updating (index has 3.1.5) # cd /usr/ports/textproc/docbook-xml make clean all pkg_delete -f docbook-xml-3.1.4 make install # # fetchmail # needs updating (index has 5.0.8) # cd /usr/ports/mail/fetchmail make clean all pkg_delete -f fetchmail-5.0.3 make install # # less # needs updating (index has 340) # cd /usr/ports/misc/less make clean all pkg_delete -f less-337 make install [...] I sent these to the maintainer/author a while back, but they were never integrated. N -- [intentional self-reference] can be easily accommodated using a blessed, non-self-referential dummy head-node whose own object destructor severs the links. -- Tom Christiansen in <375143b5@cs.colorado.edu> To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Sep 26 5:19:45 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id 266D714C3E for ; Sun, 26 Sep 1999 05:19:42 -0700 (PDT) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id OAA66073; Sun, 26 Sep 1999 14:19:26 +0200 (CEST) (envelope-from sos) From: Soren Schmidt Message-Id: <199909261219.OAA66073@freebsd.dk> Subject: Re: wormcontrol write speed In-Reply-To: from Nick Hibma at "Sep 26, 1999 01:49:11 pm" To: hibma@skylink.it (Nick Hibma) Date: Sun, 26 Sep 1999 14:19:26 +0200 (CEST) Cc: chris@netmonger.net (Christopher Masto), doconnor@gsoft.com.au (Daniel O'Connor), freebsd-hackers@FreeBSD.ORG, paulo@nlink.com.br X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems Nick Hibma wrote: >And, oh while you are at it, why not create a CAM SIM that makes IDE >available through CAM. That would save me a lot of work :-) Its not on my current TODO list, I want all the lowlevel things done first. If somebody writes the support I'll consider putting it in, but no promises... -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Sep 26 6:49:40 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from beebite.ugh.net.au (beebite.ugh.net.au [203.31.238.37]) by hub.freebsd.org (Postfix) with ESMTP id 818FE14BDA for ; Sun, 26 Sep 1999 06:49:37 -0700 (PDT) (envelope-from andrew@ugh.net.au) Received: by beebite.ugh.net.au (Postfix, from userid 1000) id 016D255; Sun, 26 Sep 1999 23:49:36 +1000 (EST) Received: from localhost (localhost [127.0.0.1]) by beebite.ugh.net.au (Postfix) with ESMTP id A4E2644; Sun, 26 Sep 1999 23:49:36 +1000 (EST) Date: Sun, 26 Sep 1999 23:49:36 +1000 (EST) From: andrew@ugh.net.au To: Jan Pechanec Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Corrupt File System In-Reply-To: Message-ID: X-WonK: *wibble* MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 26 Sep 1999, Jan Pechanec wrote: > On Sun, 26 Sep 1999 andrew@ugh.net.au wrote: > > Isn't you partition table corrupted? That may well be...I'm not really sure...the data is still there as I can dd parts of the disk to a file then use beav to view it...I can read ascii text but it would be an extremely ling job to try and extart it that way. > What does it mean ``No > bootmanager sees it''? If BootEasy doesn't display FBSD partition in > its menu, the partition table in MBR is bad. This is whats happened then although in my attempts to reserect it I have probably done more harm than good... Thanks, Andrew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Sep 26 7: 1:53 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (Postfix) with ESMTP id C7B3514BDA; Sun, 26 Sep 1999 07:01:49 -0700 (PDT) (envelope-from dcs@newsguy.com) Received: from newsguy.com by peach.ocn.ne.jp (8.9.1a/OCN) id XAA01994; Sun, 26 Sep 1999 23:01:11 +0900 (JST) Message-ID: <37EE0D35.6D0A0343@newsguy.com> Date: Sun, 26 Sep 1999 21:10:29 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.6 [en] (Win98; I) X-Accept-Language: en,pt-BR,ja MIME-Version: 1.0 To: Alexander Bezroutchko Cc: Poul-Henning Kamp , freebsd-security@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG Subject: Re: about jail References: <19990925171712.A80535@zenon.net> <11744.938266471@critter.freebsd.dk> <19990926015928.C22850@zenon.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Alexander Bezroutchko wrote: > > > > And > > > /proc//status must show this value. > > > > It already does. > > ....................................... > vm1# cat /proc/$$/status > zsh 480 479 479 440 5,2 ctty 938282449,544330 0,55195 0,55194 pause 0 0 0,0,0,2,3,4,5,20,31 vm1 > ^^^^ > vm1# hostname qwerty > ^^^^^^ > vm1# cat /proc/$$/status > zsh 480 479 479 440 5,2 ctty 938282449,544330 0,72515 0,56401 pause 0 0 0,0,0,2,3,4,5,20,31 qwerty > ^^^^^^^ > vm1# uname -a > FreeBSD qwerty 4.0-19990918-CURRENT FreeBSD 4.0-19990918-CURRENT #0: Sat Sep 25 18:18:50 MSD 1999 > ^^^^^^^^^^^^^^^^^^^^ > vm1# And your point is? Do the base system or another jail show qwerty too? -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org Rule 69: Do unto other's code as you'd have it do unto yours To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Sep 26 7: 2: 5 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (Postfix) with ESMTP id 52B2A1534D for ; Sun, 26 Sep 1999 07:02:01 -0700 (PDT) (envelope-from dcs@newsguy.com) Received: from newsguy.com by peach.ocn.ne.jp (8.9.1a/OCN) id XAA02125; Sun, 26 Sep 1999 23:01:48 +0900 (JST) Message-ID: <37EE0F61.CF386BA9@newsguy.com> Date: Sun, 26 Sep 1999 21:19:45 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.6 [en] (Win98; I) X-Accept-Language: en,pt-BR,ja MIME-Version: 1.0 To: Bill Fumerola , Jaakko Salomaa , hackers@FreeBSD.ORG Subject: Re: A new package fetching utility, pkg_get References: <37ECF0F4.2A30E31B@newsguy.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Daniel C. Sobral" wrote: > > That's because you are not a loser. Losers want plug-and-play. This > pkg_get is plug and play, pkg_add isn't. It doesn't, for instance, > automatically retrives a list of the packages available fromt he net > and show them to you. I meant luser, of course. With this, and one sig11 message I answer, I'm now sure I must have passive-smoked something... -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org Rule 69: Do unto other's code as you'd have it do unto yours To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Sep 26 7:52:23 1999 Delivered-To: freebsd-hackers@hub.freebsd.org Received: from november.jaded.net (november.jaded.net [216.94.113.4]) by hub.freebsd.org (Postfix) with ESMTP id 3255C1508E; Sun, 26 Sep 1999 07:52:20 -0700 (PDT) (envelope-from dan@november.jaded.net) Received: (from dan@localhost) by november.jaded.net (8.9.3/8.9.3+trinsec_nospam) id LAA18494; Sun, 26 Sep 1999 11:10:55 -0400 (EDT) Date: Sun, 26 Sep 1999 11:10:55 -0400 From: Dan Moschuk To: Nik Clayton Cc: Christian Carstensen , Chris Costello , freebsd-hackers@hub.FreeBSD.ORG Subject: Re: updating packages automatically... Message-ID: <19990926111055.A18290@november.jaded.net> References: <19990925180201.C76486@holly.calldei.com> <19990926012352.A49346@catkin.nothing-going-on.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <19990926012352.A49346@catkin.nothing-going-on.org>; from Nik Clayton on Sun, Sep 26, 1999 at 01:23:52AM +0100 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG | If you're interested, I've got patches for sysutils/pkg_version | that support a '-c' flag (for 'commands') that show you the commands | you should run to update any out of date ports. I cron this and mail | the output out once a week. | | You could have it automatically create and execute a shell script if | you wanted. Sample output from one of my boxes is: [snip] I think this is a great idea, and certainly one of the things (the only thing?) I actually liked debian. I would much rather see this integrated somewhere in /etc/periodic/weekly, and have it output a shell script that can be run manually. -- Dan Moschuk (TFreak!dan@freebsd.org) "Try not. Do, or do not. There is no try." -- Yoda To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Sep 26 8:18:57 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from relay2.aha.ru (relay2.aha.ru [195.2.64.35]) by hub.freebsd.org (Postfix) with ESMTP id 53D0F14C2B; Sun, 26 Sep 1999 08:18:52 -0700 (PDT) (envelope-from abb@zenon.net) Received: from pb.hq.zenon.net (pb [195.2.64.18]) by relay2.aha.ru (8.9.3/8.9.3/aha-r/0.04B) with ESMTP id TAA84042; Sun, 26 Sep 1999 19:18:05 +0400 (MSD) Received: from mp.hq.zenon.net (mp [192.168.9.150]) by pb.hq.zenon.net (8.9.3/8.9.3) with ESMTP id TAA24369; Sun, 26 Sep 1999 19:18:05 +0400 (MSD) Received: (from abb@localhost) by mp.hq.zenon.net (8.9.3/8.9.3) id TAA65181; Sun, 26 Sep 1999 19:18:05 +0400 (MSD) Message-ID: <19990926191804.B57967@zenon.net> Date: Sun, 26 Sep 1999 19:18:04 +0400 From: Alexander Bezroutchko To: "Daniel C. Sobral" Cc: Poul-Henning Kamp , freebsd-security@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG Subject: Re: about jail References: <19990925171712.A80535@zenon.net> <11744.938266471@critter.freebsd.dk> <19990926015928.C22850@zenon.net> <37EE0D35.6D0A0343@newsguy.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <37EE0D35.6D0A0343@newsguy.com>; from Daniel C. Sobral on Sun, Sep 26, 1999 at 09:10:29PM +0900 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > And your point is? Do the base system or another jail show qwerty too? I think we are talking about slightly different things. I know that jailed process can not change base system's hostname. But it can change it's own. Sometimes it is necessary to obtain the list of processes which belongs to some jail. How will you obtain it ? You can not rely on last field in /proc/PID/status file because it is writable for jailed process. How can you identify a jail the process belongs to ? > > -- > Daniel C. Sobral (8-DCS) > dcs@newsguy.com > dcs@freebsd.org > > Rule 69: Do unto other's code as you'd have it do unto yours > -- Alexander Bezroutchko, Systems Administrator, Zenon N.S.P. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Sep 26 8:30:13 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from gw-nl4.philips.com (gw-nl4.philips.com [192.68.44.36]) by hub.freebsd.org (Postfix) with ESMTP id 9A5BE14C48 for ; Sun, 26 Sep 1999 08:30:09 -0700 (PDT) (envelope-from Jos.Backus@nl.origin-it.com) Received: from smtprelay-nl1.philips.com (localhost.philips.com [127.0.0.1]) by gw-nl4.philips.com with ESMTP id RAA17275 for ; Sun, 26 Sep 1999 17:30:08 +0200 (MEST) (envelope-from Jos.Backus@nl.origin-it.com) Received: from smtprelay-eur1.philips.com(130.139.36.3) by gw-nl4.philips.com via mwrap (4.0a) id xma017273; Sun, 26 Sep 99 17:30:08 +0200 Received: from hal.mpn.cp.philips.com (hal.mpn.cp.philips.com [130.139.64.195]) by smtprelay-nl1.philips.com (8.9.3/8.8.5-1.2.2m-19990317) with SMTP id RAA20613 for ; Sun, 26 Sep 1999 17:30:07 +0200 (MET DST) Received: (qmail 76695 invoked by uid 666); 26 Sep 1999 15:30:28 -0000 Date: Sun, 26 Sep 1999 17:30:28 +0200 From: Jos Backus To: Gianmarco Giovannelli Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: A new package fetching utility, pkg_get Message-ID: <19990926173028.B75622@hal.mpn.cp.philips.com> Reply-To: Jos Backus References: <199909252352.BAA26437@dorifer.heim3.tu-clausthal.de> <4.2.0.58.19990926090211.009e0dd0@194.184.65.4> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre2i In-Reply-To: <4.2.0.58.19990926090211.009e0dd0@194.184.65.4> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Sep 26, 1999 at 09:05:20AM +0200, Gianmarco Giovannelli wrote: > What about to extend the pkg_delete to use a syntax like : > > pkg_delete /var/db/pkg/netscape-communicator-4.61/ > > it can help so much everyone that can automagically complete file/path > names with the shell :-) zsh users can do this already: zsh# compctl -g '/var/db/pkg/*(/:t)' pkg_delete pkg_info -- Jos Backus _/ _/_/_/ "Reliability means never _/ _/ _/ having to say you're sorry." _/ _/_/_/ -- D. J. Bernstein _/ _/ _/ _/ Jos.Backus@nl.origin-it.com _/_/ _/_/_/ use Std::Disclaimer; To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Sep 26 8:33:22 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp1.kolumbus.fi (smtp1.kolumbus.fi [193.229.0.36]) by hub.freebsd.org (Postfix) with ESMTP id 7943114D55 for ; Sun, 26 Sep 1999 08:33:11 -0700 (PDT) (envelope-from jsalomaa@saunalahti.fi) Received: from kone (kd103u1hel.dial.kolumbus.fi [193.229.11.103]) by smtp1.kolumbus.fi (8.9.0/8.9.0) with ESMTP id SAA27756 for ; Sun, 26 Sep 1999 18:33:09 +0300 (EET DST) Date: Sun, 26 Sep 1999 18:31:08 +0300 (EEST) From: Jaakko Salomaa X-Sender: jsalomaa@kone.kala.net To: hackers@freebsd.org Subject: FTP directory listing with ftpio(3) and fetch(3) Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hey, how am I supposed to fetch directory listing with ftpio(3) or fecth(3)? ftpio doesn't seem to contain necessary functions for it, and fetch's ones aren't implemented. % ./test test: fetchListFTP(): not implemented And all other listing functions seem to be front-ends for this one. They seem to be good for fetching files pointed by urls, but how about this sort of functionality? May you live long and prosper. Jaakko Salomaa To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Sep 26 8:52:40 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.HiWAAY.net (fly.HiWAAY.net [208.147.154.56]) by hub.freebsd.org (Postfix) with ESMTP id CC1C815297 for ; Sun, 26 Sep 1999 08:52:36 -0700 (PDT) (envelope-from kris@airnet.net) Received: from airnet.net (tc14-216-180-35-59.dialup.HiWAAY.net [216.180.35.59] (may be forged)) by mail.HiWAAY.net (8.9.1a/8.9.0) with ESMTP id KAA14554; Sun, 26 Sep 1999 10:52:27 -0500 (CDT) Message-ID: <37EE4138.883BA273@airnet.net> Date: Sun, 26 Sep 1999 10:52:24 -0500 From: Kris Kirby Organization: Non Illegitemus Carborundum. X-Mailer: Mozilla 4.08 [en] (X11; U; FreeBSD 3.2-RELEASE i386) MIME-Version: 1.0 To: andrew@ugh.net.au Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Corrupt File System References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG andrew@ugh.net.au wrote: > Trying to mount /dev/vn0 Produces a file /mnt (not a directory) I do believe you want the directory to exist before you attempt to mount to it. (mkdir /mnt) -- Kris Kirby ------------------------------------------- TGIFreeBSD... 'Nuff said. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Sep 26 8:56:12 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.HiWAAY.net (fly.HiWAAY.net [208.147.154.56]) by hub.freebsd.org (Postfix) with ESMTP id 81F91150FB for ; Sun, 26 Sep 1999 08:56:10 -0700 (PDT) (envelope-from kris@airnet.net) Received: from airnet.net (tc14-216-180-35-59.dialup.HiWAAY.net [216.180.35.59] (may be forged)) by mail.HiWAAY.net (8.9.1a/8.9.0) with ESMTP id KAA15384; Sun, 26 Sep 1999 10:56:03 -0500 (CDT) Message-ID: <37EE4213.FC5F304F@airnet.net> Date: Sun, 26 Sep 1999 10:56:03 -0500 From: Kris Kirby Organization: Non Illegitemus Carborundum. X-Mailer: Mozilla 4.08 [en] (X11; U; FreeBSD 3.2-RELEASE i386) MIME-Version: 1.0 To: Wes Peters Cc: hackers@FreeBSD.ORG Subject: Re: A new package fetching utility, pkg_get References: <6575.938200554@localhost> <37EC05EC.757D92E4@softweyr.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Wes Peters wrote: > > "Jordan K. Hubbard" wrote: > > > > > Boy, we're having fun asking you to rewrite your program. It's good training > > > for you, though, this is what it's like to be a programmer in "The Real > > > World". ;^) > > > > You bet! And we haven't even gotten to the topic of the interactive > > package selection menu yet! :-) > > Let alone the Java-based GUI. > > Of course, somebody needs to do a market survey and write the Product > Requirements Document first. Wait a minute, aren't YOU the "Product > Manager" for FreeBSD? Hah! Now YOU'RE trapped, too! > > Wes, you've walked away and forgot to logout again. I suspect Dogbert has been seen around your home/office lately. -- Kris Kirby ------------------------------------------- TGIFreeBSD... 'Nuff said. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Sep 26 10:20:18 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from matrix.42.org (matrix.42.org [194.246.250.200]) by hub.freebsd.org (Postfix) with ESMTP id 70B7D14DFD for ; Sun, 26 Sep 1999 10:20:14 -0700 (PDT) (envelope-from sec@42.org) Received: (from sec@localhost) by matrix.42.org (8.8.8/8.8.5) id TAA09506 (sender ); Sun, 26 Sep 1999 19:19:51 +0200 (CEST) Date: Sun, 26 Sep 1999 19:19:50 +0200 From: Stefan `Sec` Zehl To: Gianmarco Giovannelli Cc: freebsd-hackers@freebsd.org Subject: Re: A new package fetching utility, pkg_get Message-ID: <19990926191950.A9492@matrix.42.org> References: <199909252352.BAA26437@dorifer.heim3.tu-clausthal.de> <4.2.0.58.19990926090211.009e0dd0@194.184.65.4> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre3i In-Reply-To: <4.2.0.58.19990926090211.009e0dd0@194.184.65.4> I-love-doing-this: really Accept-Languages: de, en X-URL: http://sec.42.org/ Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Sep 26, 1999 at 09:05:20AM +0200, Gianmarco Giovannelli wrote: > What about to extend the pkg_delete to use a syntax like : > > pkg_delete /var/db/pkg/netscape-communicator-4.61/ > > it can help so much everyone that can automagically complete file/path > names with the shell :-) If you use zsh, use this: #pkg_delete completion (according to the manpage) compctl -g '/var/db/pkg/*(:t)' -x \ 's[-]' -k (v D n f p) - \ 'c[-1,-p]' -g '*(D-/)' -- \ pkg_delete CU, Sec -- Win16, Win32s, Win32c, Win32 - Which API do you want to go today? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Sep 26 11:53:37 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from pauling.research.devcon.net (pauling.research.devcon.net [212.15.193.194]) by hub.freebsd.org (Postfix) with ESMTP id 94F9A14E47; Sun, 26 Sep 1999 11:53:33 -0700 (PDT) (envelope-from cc@devcon.net) Received: from localhost (cc@localhost) by pauling.research.devcon.net (8.9.3/8.9.2) with ESMTP id UAA78473; Sun, 26 Sep 1999 20:53:33 +0200 (CEST) (envelope-from cc@devcon.net) Date: Sun, 26 Sep 1999 20:53:32 +0200 (CEST) From: Christian Carstensen X-Sender: cc@pauling.research.devcon.net To: Nik Clayton Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: updating packages automatically... In-Reply-To: <19990926012352.A49346@catkin.nothing-going-on.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 26 Sep 1999, Nik Clayton wrote: > If you're interested, I've got patches for sysutils/pkg_version > that support a '-c' flag (for 'commands') that show you the commands > you should run to update any out of date ports. I cron this and mail > the output out once a week. Nick, in deed, i am very interested in it. having your patches, do you think, there's any need for a tool in perl? i'm recently testing my version and it seems to work as expected. could you possibly send me your patches? -- christian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Sep 26 12:14:52 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from nothing-going-on.demon.co.uk (nothing-going-on.demon.co.uk [193.237.89.66]) by hub.freebsd.org (Postfix) with ESMTP id 2AEDB153F5; Sun, 26 Sep 1999 12:14:48 -0700 (PDT) (envelope-from nik@nothing-going-on.demon.co.uk) Received: (from nik@localhost) by nothing-going-on.demon.co.uk (8.9.3/8.9.3) id UAA89606; Sun, 26 Sep 1999 20:14:43 +0100 (BST) (envelope-from nik) Date: Sun, 26 Sep 1999 20:14:43 +0100 From: Nik Clayton To: Christian Carstensen Cc: Nik Clayton , freebsd-hackers@FreeBSD.ORG Subject: Re: updating packages automatically... Message-ID: <19990926201443.A88824@catkin.nothing-going-on.org> References: <19990926012352.A49346@catkin.nothing-going-on.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: ; from Christian Carstensen on Sun, Sep 26, 1999 at 08:53:32PM +0200 Organization: FreeBSD Project Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Sep 26, 1999 at 08:53:32PM +0200, Christian Carstensen wrote: > On Sun, 26 Sep 1999, Nik Clayton wrote: > > If you're interested, I've got patches for sysutils/pkg_version > > that support a '-c' flag (for 'commands') that show you the commands > > you should run to update any out of date ports. I cron this and mail > > the output out once a week. > > in deed, i am very interested in it. having your patches, do you think, > there's any need for a tool in perl? i'm recently testing my version and > it seems to work as expected. > could you possibly send me your patches? Various people have asked for these. http://www.freebsd.org/~nik/pkg_version.diff pkg_version.1.diff N -- [intentional self-reference] can be easily accommodated using a blessed, non-self-referential dummy head-node whose own object destructor severs the links. -- Tom Christiansen in <375143b5@cs.colorado.edu> To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Sep 26 13:15: 4 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from panix.com (panix.com [166.84.1.66]) by hub.freebsd.org (Postfix) with ESMTP id 2FAB014C3B for ; Sun, 26 Sep 1999 13:15:00 -0700 (PDT) (envelope-from rsi@panix.com) Received: (from rsi@localhost) by panix.com (8.8.5/8.8.8/PanixU1.4) id QAA14926; Sun, 26 Sep 1999 16:14:55 -0400 (EDT) Message-Id: <199909262014.QAA14926@panix.com> To: Tony Finch Cc: freebsd-hackers@freebsd.org Subject: Re: A new package fetching utility, pkg_get References: <6939.938202872@localhost> <19990924140357.A71450@norn.ca.eu.org> From: Rajappa Iyer Date: 26 Sep 1999 16:14:54 -0400 Reply-To: rsi@panix.com MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Tony Finch writes: > Rajappa Iyer wrote: > >1. It does a terrible job at tracking dependencies, IMHO. If you > > install packages A, B and C at the same time and A depends on C, > > it's not smart enough to install C first. pkg_order | tsort should > > do the job, one would presume. > > > >2. It does an even more terrible job at fetching dependencies. Try > > installing a complex set of programs and files (e.g. gnome) and see > > how many individual components you have to fetch. Contrast with > > "cd /usr/ports/x11/gnome; make install". > > Both of those are handled by the apt-get program, and were in the past > handled by dselect (but dselect is horrid for a whole load of other > reasons). apt-get does a better job at collections, true, but in my experience still does not do a proper package ordering before installation. And if component packages have inconsistent dependencies, apt-get puts your system in a state that is hard to recover from. I've had both of these things happen to me while installing gnome. Now one can argue that this reflects a problem with the individual package rather than the infrastructure, but I feel that if a package manager deals with a bundle in a manner similar to a package, it should deal with consistency issues of the component packages. Don't get me wrong. I think that the problem that Debian package manager is trying to solve is not an easy one to solve in a completely bulletproof manner and I don't have a solution to offer offhand, either. apt-get is undoubtedly an improvement on dselect, but I think it builds on a fundamentally shaky infrastructure, IMHO. My gut feeling is that one would be better off building a super-duper package management system on top of the ports mechanism and extending the existing pkg_* tools. Regards, Rajappa -- a.k.a. Rajappa Iyer. New York, New York. We're too busy mopping the floor to turn off the faucet. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Sep 26 13:47:44 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from dt014n8c.san.rr.com (dt014n8c.san.rr.com [24.30.129.140]) by hub.freebsd.org (Postfix) with ESMTP id 4C42414CF1 for ; Sun, 26 Sep 1999 13:47:41 -0700 (PDT) (envelope-from Doug@gorean.org) Received: from gorean.org (master [10.0.0.2]) by dt014n8c.san.rr.com (8.9.3/8.8.8) with ESMTP id OAA17662; Sun, 26 Sep 1999 14:04:15 -0700 (PDT) (envelope-from Doug@gorean.org) Message-ID: <37EE8718.ED6092FD@gorean.org> Date: Sun, 26 Sep 1999 13:50:32 -0700 From: Doug Organization: Triborough Bridge & Tunnel Authority X-Mailer: Mozilla 4.61 [en] (X11; U; FreeBSD 4.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: Gianmarco Giovannelli Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: A new package fetching utility, pkg_get References: <4.2.0.58.19990926090211.009e0dd0@194.184.65.4> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Gianmarco Giovannelli wrote: > > At 26/09/99, you wrote: > >The second script is called "pkg_rm"; it can be used to delete > >packages like pkg_delete, but you can use arguments in the same > >way as for pkg_ls above (i.e. "pkg_rm lynx"). Think of it like > >pkg_info | grep | pkg_delete. > > > >It might more sense to implement these features in pkg_info and > >pkg_delete, resprectively, but I don't have the time to do that > >(and these scripts work fine, so I have no incentive to bother > >with the C sources of pkg_{info,delete}). > > What about to extend the pkg_delete to use a syntax like : > > pkg_delete /var/db/pkg/netscape-communicator-4.61/ A hearty "Me too" for this option. It's something I've often wished for. I can 'cd /var/db/pkg' a lot easier than I can reprogram zsh, but it'd still be nice to have this option. Thanks, Doug -- "Stop it, I'm gettin' misty." - Mel Gibson as Porter, "Payback" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Sep 26 14:15:25 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mauibuilt.com (mauibuilt.com [205.166.249.50]) by hub.freebsd.org (Postfix) with ESMTP id E4EE614BFC; Sun, 26 Sep 1999 14:15:19 -0700 (PDT) (envelope-from puga@mauibuilt.com) Received: from mauibuilt.com (puga.mauibuilt.com [205.166.10.2]) by mauibuilt.com (8.8.8/8.8.7) with ESMTP id LAA26304; Sun, 26 Sep 1999 11:32:04 -1000 (HST) (envelope-from puga@mauibuilt.com) Message-ID: <37EE8CA2.452A6318@mauibuilt.com> Date: Sun, 26 Sep 1999 11:14:11 -1000 From: Richard Puga X-Mailer: Mozilla 4.61 [en] (X11; I; FreeBSD 3.1-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-hackers@freebsd.org, freebsd-questions@freebsd.org Subject: XFCom_SiS for Xfree86 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Xfree86/Linux emulation question. I have a SIS 6326 AGP based motherboard and undstand that it is supported by XFCom_SiS located at ftp://ftp.suse.com/pub/SuSE-Linux/suse_update/X/XFCom/xsis/glibc2/xsis.tgz Has anyone gotten this to work under FreeBSD? Thanks in advance Richard Puga puga@mauibuilt.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Sep 26 15: 5:24 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from arnold.neland.dk (mail.neland.dk [194.255.12.232]) by hub.freebsd.org (Postfix) with ESMTP id C6C8314DED for ; Sun, 26 Sep 1999 15:05:16 -0700 (PDT) (envelope-from leifn@neland.dk) Received: from gina (gina.neland.dk [192.168.0.14]) by arnold.neland.dk (8.9.3/8.9.3) with SMTP id AAA79773; Mon, 27 Sep 1999 00:02:42 +0200 (CEST) (envelope-from leifn@neland.dk) Message-ID: <02fb01bf086a$dae8aae0$0e00a8c0@neland.dk> From: "Leif Neland" To: Cc: Subject: mrtg,FreeBSD, asus p2b temperature Date: Mon, 27 Sep 1999 00:02:37 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2314.1300 X-Mimeole: Produced By Microsoft MimeOLE V5.00.2314.1300 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Does anybody have any tips for using the above combination for graphing = temperatures? Leif To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Sep 26 15:34:21 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from medulla.hippocampus.net (medulla.hippocampus.net [204.138.241.6]) by hub.freebsd.org (Postfix) with ESMTP id B6FE4158A2 for ; Sun, 26 Sep 1999 15:33:01 -0700 (PDT) (envelope-from marc@netstor.com) Received: from localhost (marc@localhost) by medulla.hippocampus.net (8.9.3/8.9.2) with ESMTP id SAA29897; Sun, 26 Sep 1999 18:32:40 -0400 (EDT) Date: Sun, 26 Sep 1999 18:32:40 -0400 (EDT) From: Marc Nicholas X-Sender: marc@medulla.hippocampus.net To: Leif Neland Cc: mrtg@list.ee.ethz.ch, freebsd-hackers@FreeBSD.ORG Subject: Re: mrtg,FreeBSD, asus p2b temperature In-Reply-To: <02fb01bf086a$dae8aae0$0e00a8c0@neland.dk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Specifically, what 'tips' are you looking for? -marc ------------------------------------------------------------------- Marc Nicholas netSTOR Technologies, Inc. http://www.netstor.com "Fast, Expandable and Affordable Internet Caching Products" 1.877.464.4776 416.979.9000x11 fax: 416.979.8223 cell: 416.346.9255 On Mon, 27 Sep 1999, Leif Neland wrote: > Does anybody have any tips for using the above combination for graphing temperatures? > > Leif > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Sep 26 15:48:24 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from tinker.com (troll.tinker.com [204.214.7.146]) by hub.freebsd.org (Postfix) with ESMTP id EE3F414C44; Sun, 26 Sep 1999 15:48:17 -0700 (PDT) (envelope-from carol@tinker.com) Received: by localhost (8.8.5/8.8.5) Received: by mail.tinker.com via smap (V2.0) id xma008455; Sun Sep 26 17:25:55 1999 Received: by localhost (8.8.8/8.8.8) id RAA19535; Sun, 26 Sep 1999 17:48:03 -0500 (CDT) Message-ID: <37EEA27E.244DCF9A@tinker.com> Date: Sun, 26 Sep 1999 17:47:26 -0500 From: Carol Deihl Organization: Shrier and Deihl X-Mailer: Mozilla 4.5 [en] (X11; U; FreeBSD 2.2.8-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-security@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG Subject: chroot could chdir? (was Re: about jail) References: <199909251302.RAA58030@grendel.sovlink.ru> <19990925171712.A80535@zenon.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Alexander Bezroutchko wrote: > it is possible to escape from jail > Following program escapes from jail (tested under 4.0-19990918-CURRENT): [snip program code that chroot's but doesn't then chdir inside the new area] As we all know, the chroot can be escaped because the sample program doesn't change the current working directory, and it's still pointing outside the chrooted area. What if chroot itself chdir'ed to it's new root directory? Would this break existing programs? I'd expect that well-behaved programs would chdir someplace useful before continuing anyway. At the very end of chroot(), could it just vrele(fdp->fd_cdir); fdp->fd_cdir = nd.ni_vp; before it returns, setting the current dir to the same place it just chrooted to? Carol -- Carol Deihl - principal, Shrier and Deihl - mailto:carol@tinker.com Remote Unix Network Admin, Security, Internet Software Development Tinker Internet Services - Superior FreeBSD-based Web Hosting http://www.tinker.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Sep 26 16: 1:41 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from bekool.com (ns2.netquick.net [216.48.34.2]) by hub.freebsd.org (Postfix) with ESMTP id 2C9F414C25; Sun, 26 Sep 1999 16:01:34 -0700 (PDT) (envelope-from trouble@hackfurby.com) Received: from angelsguardian.netquick.net ([199.72.47.239] helo=hackfurby.com) by bekool.com with esmtp (Exim 3.03 #1) id 11VNb5-0008Zg-00; Sun, 26 Sep 1999 23:20:48 +0000 Message-ID: <37F00602.96D098D3@hackfurby.com> Date: Mon, 27 Sep 1999 19:04:19 -0500 From: TrouBle Reply-To: trouble@hackfurby.com X-Mailer: Mozilla 4.61 [en] (X11; I; FreeBSD 3.3-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: Carol Deihl Cc: freebsd-security@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG Subject: Re: chroot could chdir? (was Re: about jail) References: <199909251302.RAA58030@grendel.sovlink.ru> <19990925171712.A80535@zenon.net> <37EEA27E.244DCF9A@tinker.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Ummm sorry but i think you have goten this backwards it is more secure to chdir, then chrrot, not chroot then chdir.... I believe what you have here is backwards > > As we all know, the chroot can be escaped because the sample > program doesn't change the current working directory, and it's > still pointing outside the chrooted area. > > What if chroot itself chdir'ed to it's new root directory? Would > this break existing programs? I'd expect that well-behaved > programs would chdir someplace useful before continuing anyway. > > At the very end of chroot(), could it just > vrele(fdp->fd_cdir); > fdp->fd_cdir = nd.ni_vp; > before it returns, setting the current dir to the same place it > just chrooted to? > > Carol > -- > Carol Deihl - principal, Shrier and Deihl - mailto:carol@tinker.com > Remote Unix Network Admin, Security, Internet Software Development > Tinker Internet Services - Superior FreeBSD-based Web Hosting > http://www.tinker.com/ > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-security" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Sep 26 16: 3:23 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from bekool.com (ns2.netquick.net [216.48.34.2]) by hub.freebsd.org (Postfix) with ESMTP id 733EA153F2; Sun, 26 Sep 1999 16:03:18 -0700 (PDT) (envelope-from trouble@hackfurby.com) Received: from angelsguardian.netquick.net ([199.72.47.239] helo=hackfurby.com) by bekool.com with esmtp (Exim 3.03 #1) id 11VNco-0008ab-00; Sun, 26 Sep 1999 23:22:34 +0000 Message-ID: <37F00675.67D198FD@hackfurby.com> Date: Mon, 27 Sep 1999 19:06:13 -0500 From: TrouBle Reply-To: trouble@hackfurby.com X-Mailer: Mozilla 4.61 [en] (X11; I; FreeBSD 3.3-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: Carol Deihl Cc: freebsd-security@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG Subject: Re: chroot could chdir? (was Re: about jail) References: <199909251302.RAA58030@grendel.sovlink.ru> <19990925171712.A80535@zenon.net> <37EEA27E.244DCF9A@tinker.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Umm I think you have gotten this backwards, it is more secure to chdir first then chroot.... I think you have this backwards..... in my virtual environment i chdir working dir, then chroot....... ive not been able to escape my chrooted jail setup yet..... nor have i seen any code that will > > > As we all know, the chroot can be escaped because the sample > program doesn't change the current working directory, and it's > still pointing outside the chrooted area. > > What if chroot itself chdir'ed to it's new root directory? Would > this break existing programs? I'd expect that well-behaved > programs would chdir someplace useful before continuing anyway. > > At the very end of chroot(), could it just > vrele(fdp->fd_cdir); > fdp->fd_cdir = nd.ni_vp; > before it returns, setting the current dir to the same place it > just chrooted to? > > Carol > -- > Carol Deihl - principal, Shrier and Deihl - mailto:carol@tinker.com > Remote Unix Network Admin, Security, Internet Software Development > Tinker Internet Services - Superior FreeBSD-based Web Hosting > http://www.tinker.com/ > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-security" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Sep 26 16: 8:50 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from bekool.com (ns2.netquick.net [216.48.34.2]) by hub.freebsd.org (Postfix) with ESMTP id 9E6BD14A0B; Sun, 26 Sep 1999 16:08:44 -0700 (PDT) (envelope-from trouble@hackfurby.com) Received: from angelsguardian.netquick.net ([199.72.47.239] helo=hackfurby.com) by bekool.com with esmtp (Exim 3.03 #1) id 11VNi9-0008bZ-00; Sun, 26 Sep 1999 23:28:06 +0000 Message-ID: <37F007C0.C068FB21@hackfurby.com> Date: Mon, 27 Sep 1999 19:11:44 -0500 From: TrouBle Reply-To: trouble@hackfurby.com X-Mailer: Mozilla 4.61 [en] (X11; I; FreeBSD 3.3-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: Carol Deihl , freebsd-security@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG Subject: Re: chroot could chdir? (was Re: about jail) References: <199909251302.RAA58030@grendel.sovlink.ru> <19990925171712.A80535@zenon.net> <37EEA27E.244DCF9A@tinker.com> <37F00602.96D098D3@hackfurby.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I actually currently use -----SNIP - EDITED FOR SECURITY ------------- syslog (LOG_NOTICE,"Changing directory/root to %s",path if (chdir (path) || chroot (path)) return 1; }else{ syslog (LOG_NOTICE,"No ("EDITED FOR SECURITY" ) directory for %s: using main" } } execv (argv[0],argv+1); return 1; } -------END - SNIP -------------------------- > > > At the very end of chroot(), could it just > > vrele(fdp->fd_cdir); > > fdp->fd_cdir = nd.ni_vp; > > before it returns, setting the current dir to the same place it > > just chrooted to? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Sep 26 17: 1:56 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (Postfix) with ESMTP id 1CC0114F89; Sun, 26 Sep 1999 17:01:51 -0700 (PDT) (envelope-from julian@whistle.com) Received: from home.elischer.org (home.elischer.org [207.76.204.203]) by alpo.whistle.com (8.9.1a/8.9.1) with ESMTP id RAA92968; Sun, 26 Sep 1999 17:01:35 -0700 (PDT) Date: Sun, 26 Sep 1999 17:01:35 -0700 (PDT) From: Julian Elischer X-Sender: julian@home.elischer.org To: Carol Deihl Cc: freebsd-security@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG Subject: Re: chroot could chdir? (was Re: about jail) In-Reply-To: <37EEA27E.244DCF9A@tinker.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG You have to examine ALL fd's in case one has a directory open that is outside the chroot.. (see man fchdir(2)) julian On Sun, 26 Sep 1999, Carol Deihl wrote: > Alexander Bezroutchko wrote: > > it is possible to escape from jail > > Following program escapes from jail (tested under 4.0-19990918-CURRENT): > [snip program code that chroot's but doesn't then chdir inside > the new area] > > As we all know, the chroot can be escaped because the sample > program doesn't change the current working directory, and it's > still pointing outside the chrooted area. > > What if chroot itself chdir'ed to it's new root directory? Would > this break existing programs? I'd expect that well-behaved > programs would chdir someplace useful before continuing anyway. > > At the very end of chroot(), could it just > vrele(fdp->fd_cdir); > fdp->fd_cdir = nd.ni_vp; > before it returns, setting the current dir to the same place it > just chrooted to? > > Carol > -- > Carol Deihl - principal, Shrier and Deihl - mailto:carol@tinker.com > Remote Unix Network Admin, Security, Internet Software Development > Tinker Internet Services - Superior FreeBSD-based Web Hosting > http://www.tinker.com/ > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Sep 26 17:22:47 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from m4.c2.telstra-mm.net.au (m4.c2.telstra-mm.net.au [24.192.3.19]) by hub.freebsd.org (Postfix) with ESMTP id 348D9152F8 for ; Sun, 26 Sep 1999 17:22:43 -0700 (PDT) (envelope-from areilly@nsw.bigpond.net.au) Received: from m5.c2.telstra-mm.net.au (m5.c2.telstra-mm.net.au [24.192.3.20]) by m4.c2.telstra-mm.net.au (8.8.6 (PHNE_14041)/8.8.6) with ESMTP id KAA08574 for ; Mon, 27 Sep 1999 10:22:36 +1000 (EST) X-BPC-Relay-Envelope-From: areilly@nsw.bigpond.net.au X-BPC-Relay-Envelope-To: X-BPC-Relay-Sender-Host: m5.c2.telstra-mm.net.au [24.192.3.20] X-BPC-Relay-Info: Message delivered directly. Received: from areilly.bpc-users.org (CPE-24-192-49-170.nsw.bigpond.net.au [24.192.49.170]) by m5.c2.telstra-mm.net.au (8.8.6 (PHNE_14041)/8.8.6) with SMTP id KAA15989 for ; Mon, 27 Sep 1999 10:22:34 +1000 (EST) Received: (qmail 63987 invoked by uid 1000); 27 Sep 1999 00:22:34 -0000 From: "Andrew Reilly" Date: Mon, 27 Sep 1999 10:22:34 +1000 To: freebsd-hackers@FreeBSD.ORG Subject: Re: A new package fetching utility, pkg_get Message-ID: <19990927102234.A53880@gurney.reilly.home> References: <199909252352.BAA26437@dorifer.heim3.tu-clausthal.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre1i In-Reply-To: <199909252352.BAA26437@dorifer.heim3.tu-clausthal.de> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Sep 26, 1999 at 01:52:36AM +0200, Oliver Fromme wrote: > While we're talking about making package handling easier for > newbies, I'd like to present two simple shell scripts that I > wrote quite some time ago. Yeah, I know I could send-pr this, > but I'm not sure if they're really worth it (if someone thinks > they are, then I'll send-pr them). Here's a bit of me-too-erism, and (I hope) some food for thought and discussion: I've longed for a mechanism to keep the ports that I use as up-to-date as the rest of my FreeBSD system. Unfortunately, some ports I don't use very often, and so forget that they're there. Unfortunately (again), the port name-version_number identifier isn't _quite_ unique enough to use as a key for tracking ports. For example: ssh and docbook have multiple versions for the same base name installed concurrently. What I'd like is a little weekly crontab script that runs after my weekly ports cvsup, and tells me which of the ports that I "subscribe to" has changed, so that I can think about rebuilding it. This is the closest I've come, so far. Comments and suggestions welcome, of course: pkg_info -a -q -I > tags pkg_info -a -I | awk '{print $1}' | paste -d\| - tags | sort -t\| -k 2 > alist sort -t\| -k 4 /usr/ports/INDEX |\ join -t\| -o1.1,2.1 -1 2 -2 4 alist - |\ awk -F\| '{if ($1 != $2) print $1 "-->" $2}' This throws up some obvious candidates, like: mutt-1.0b1-->mutt-1.0b2 But also some dubious ones: bzip2-0.9.0c-->bzip-0.21 bzip2-0.9.0c-->bzip2-0.9.5c And some that seem to have different pkg_* names from the values in the INDEX file: squid-2.2-->squid-2.0 squid-2.2-->squid-2.1 This probably also loses for any ports where the comment field has changed... I've thought about parsing the "updated ports" list that gets posted to usenet every (?) month or so, but that seems hard too. -- Andrew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Sep 26 18:23:34 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from dingo.cdrom.com (castles530.castles.com [208.214.165.94]) by hub.freebsd.org (Postfix) with ESMTP id 074FD14F86 for ; Sun, 26 Sep 1999 18:23:28 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.3/8.8.8) with ESMTP id SAA15376; Sun, 26 Sep 1999 18:16:10 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199909270116.SAA15376@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Brian Reichert Cc: freebsd-hackers@freebsd.org Subject: Re: 3.3-R on Dell w/ DPT RAID In-reply-to: Your message of "Fri, 24 Sep 1999 15:09:56 EDT." <19990924150956.C5560@numachi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 26 Sep 1999 18:16:09 -0700 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I've pored over -question, to no avail, so here goes. > > We are trying to install FreeBSD 3.3-RELEASE on a Dell PowerEdge > 6300. > > Said beast has a DPT SmartRAID IV controller, and 2G of memory. > > We've told this machine via it's BIOS to pretend it only has 256M. > > When we try an install from the floppies, the mfsroot floppies > panics with an 'pmap_enter: invalid page directory, pdir=0x601063, > va=0xc2400000'. > > I have no idea what this error message means. It suggests that you have memory problems; have you tried physically extracting most of the memory from the system? -- \\ The mind's the standard \\ Mike Smith \\ of the man. \\ msmith@freebsd.org \\ -- Joseph Merrick \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Sep 26 18:33:34 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from dingo.cdrom.com (castles530.castles.com [208.214.165.94]) by hub.freebsd.org (Postfix) with ESMTP id E4B2615382 for ; Sun, 26 Sep 1999 18:33:31 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.3/8.8.8) with ESMTP id SAA15450; Sun, 26 Sep 1999 18:26:07 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199909270126.SAA15450@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: "Juan Lorenzana" Cc: hackers@FreeBSD.org Subject: Re: [Fwd: Bsd Problem] In-reply-to: Your message of "Thu, 23 Sep 1999 21:36:29 PDT." <37EAFFCD.6F9F4B0D@agcs.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 26 Sep 1999 18:26:07 -0700 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > I was wondering if I could get help. Doug Madderom is a developer at > AGCS and has asked me to forward this to the FreeBSD newsgroup. Any > help is appreciated. Thanks. Commentary follows: > I wrote a character device driver using ioct as the method to pass data in a > structure to and from the device driver. If I do not include either a printf or > scanf in the application program that uses the driver the pointer the OS passes > to the ioctl in the driver is not set up right and the driver panics. What am I > doing wrong ? I don't think the use or non-use of printf/scanf have anything to do with the problem here. You've probably made several changes at the same time and missed the significant one. > Program that fails ( works if first line in program is a printf) The program is OK. > Device driver: > ---------------------------------------------- > /* alarmio driver for free BDS */ It's "FreeBSD". 8) > struct Ioctl_args *tmp; ... > *tmp=*(struct Ioctl_args *)arg; You never point (tmp) at anything, and the code above (which is wrong) attempts a structure copy of the structure that (arg) points to into random space. This line should read tmp = (struct Ioctl_args *)arg; Normal programming convention would have you make the assignment in the declaration of tmp: static int alarmioioctl(dev_t dev, int cmd, caddr_t arg, int flag, struct proc *p) { struct Ioctl_args *tmp = (struct Ioctl_args *)arg; Hope this helps. -- \\ The mind's the standard \\ Mike Smith \\ of the man. \\ msmith@freebsd.org \\ -- Joseph Merrick \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Sep 26 20:37: 6 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 680AD157AE for ; Sun, 26 Sep 1999 20:37:02 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id UAA76806; Sun, 26 Sep 1999 20:36:59 -0700 (PDT) (envelope-from dillon) Date: Sun, 26 Sep 1999 20:36:59 -0700 (PDT) From: Matthew Dillon Message-Id: <199909270336.UAA76806@apollo.backplane.com> To: "Daniel C. Sobral" Cc: Nate Williams , Alfred Perlstein , Chuck Robey , Ivan , freebsd-hackers@FreeBSD.ORG Subject: Re: Out of swap handling and X lockups in 3.2R References: <199909221727.LAA14290@mt.sri.com> <199909221738.KAA16257@apollo.backplane.com> <37E9AB80.C67E1B1D@newsguy.com> <199909231626.JAA27920@apollo.backplane.com> <37EAE9CC.99A4F4AF@newsguy.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG : :Matthew Dillon wrote: :> :> What it all comes down to is a juxtaposition of what people believe :> is appropriate verses what people are actually willing to code up. :> I'm willing to code up my importance mechanism idea. The question is :> whether it's a good enough idea to throw into the tree. : :I think it's a good idea. It lets the admin introduce bias in the :system to protect people/processes who are more likely to use huge :amount of memory. Alas, taking the swap space into account in :addition to RSS seems more important to me. But then, I'm happy with :the way things are right now. : :-- :Daniel C. Sobral (8-DCS) I'm going to implement and commit this idea into -CURRENT unless someone screams. I think it would be an excellent base on top of which future sohpistication can be added. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Sep 26 21:14:20 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from kiwi.mail.easynet.net (kiwi.mail.easynet.net [195.40.1.40]) by hub.freebsd.org (Postfix) with ESMTP id 844C914EEB; Sun, 26 Sep 1999 21:14:16 -0700 (PDT) (envelope-from frankrj@netscape.net) Received: from netscape.net (alister.w.easynet.co.uk [212.212.251.86]) by kiwi.mail.easynet.net (Postfix) with ESMTP id DC353DAF45; Mon, 27 Sep 1999 05:14:14 +0100 (BST) Message-ID: <37EEFE11.F0267A7A@netscape.net> Date: Mon, 27 Sep 1999 05:18:09 +0000 From: Francis Jordan X-Mailer: Mozilla 4.5 [en] (X11; U; FreeBSD 4.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: Richard Puga Cc: freebsd-hackers@freebsd.org, freebsd-questions@freebsd.org Subject: Re: XFCom_SiS for Xfree86 References: <37EE8CA2.452A6318@mauibuilt.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Richard Puga wrote: > Xfree86/Linux emulation question. > > I have a SIS 6326 AGP based motherboard and undstand that it is > supported by XFCom_SiS located at > ftp://ftp.suse.com/pub/SuSE-Linux/suse_update/X/XFCom/xsis/glibc2/xsis.tgz > > Has anyone gotten this to work under FreeBSD? No, and no-one ever will, because there is no need for Linux emulation. Support for SiS 6326 AGP was added in v.3.3.4 of XFree86 (FYI, the latest version is 3.3.5). The above Web site was just a temporary solution. Update your ports tree, rebuild X, and you'll be ok (the SiS driver is part of XF86_SVGA). Frank To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Sep 26 21:52:31 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mauibuilt.com (mauibuilt.com [205.166.249.50]) by hub.freebsd.org (Postfix) with ESMTP id B386314C32; Sun, 26 Sep 1999 21:52:27 -0700 (PDT) (envelope-from puga@mauibuilt.com) Received: from mauibuilt.com (puga.mauibuilt.com [205.166.10.2]) by mauibuilt.com (8.8.8/8.8.7) with ESMTP id TAA27244; Sun, 26 Sep 1999 19:09:31 -1000 (HST) (envelope-from puga@mauibuilt.com) Message-ID: <37EEF7C5.C553622C@mauibuilt.com> Date: Sun, 26 Sep 1999 18:51:17 -1000 From: Richard Puga X-Mailer: Mozilla 4.61 [en] (X11; I; FreeBSD 3.1-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-hackers@freebsd.org, freebsd-questions@freebsd.org Subject: Re: XFCom_SiS for Xfree86 References: <37EE8CA2.452A6318@mauibuilt.com> <37EEFE11.F0267A7A@netscape.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG thank you for your reply. I am running FreeBSD 3.3-Release which I installed Xfree86 3.3.5 I have played around with all the settings such as turning off Accelorated graphics and such and I stll get the problem.. which btw is; the windows seem to draw ok as well as the text in the title bars but the text at the prompt is solid black squares. but other than that it does seem to work. so I guess there is somthing funkey with thease motherboards (this happens on 2 differant systems) I have.. bummer their cool boards. Francis Jordan wrote: > Richard Puga wrote: > > > Xfree86/Linux emulation question. > > > > I have a SIS 6326 AGP based motherboard and undstand that it is > > supported by XFCom_SiS located at > > > ftp://ftp.suse.com/pub/SuSE-Linux/suse_update/X/XFCom/xsis/glibc2/xsis.tgz > > > > > Has anyone gotten this to work under FreeBSD? > > No, and no-one ever will, because there is no need for Linux > emulation. > Support for SiS 6326 AGP was added in v.3.3.4 of XFree86 (FYI, the > latest version is 3.3.5). The above Web site was just a temporary > solution. Update your ports tree, rebuild X, and you'll be ok (the > SiS > driver is part of XF86_SVGA). > > Frank To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Sep 26 22:46:32 1999 Delivered-To: freebsd-hackers@hub.freebsd.org Received: from november.jaded.net (november.jaded.net [216.94.113.4]) by hub.freebsd.org (Postfix) with ESMTP id AA135150EC for ; Sun, 26 Sep 1999 22:46:30 -0700 (PDT) (envelope-from dan@november.jaded.net) Received: (from dan@localhost) by november.jaded.net (8.9.3/8.9.3+trinsec_nospam) id CAA27285; Mon, 27 Sep 1999 02:03:38 -0400 (EDT) Date: Mon, 27 Sep 1999 02:03:35 -0400 From: Dan Moschuk To: Leif Neland Cc: mrtg@list.ee.ethz.ch, freebsd-hackers@hub.FreeBSD.ORG Subject: Re: mrtg,FreeBSD, asus p2b temperature Message-ID: <19990927020335.A26862@november.jaded.net> References: <02fb01bf086a$dae8aae0$0e00a8c0@neland.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <02fb01bf086a$dae8aae0$0e00a8c0@neland.dk>; from Leif Neland on Mon, Sep 27, 1999 at 12:02:37AM +0200 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG | Does anybody have any tips for using the above combination for graphing temperatures? | | Leif As far as I know, MRTG is only able to fetch data from SNMP MIBs. Which, in order to get the information you're looking for, two things have to happen. You need to first have the kernel fetch that information from the motherboard, and then some userland program to return it in the form of an SNMP response. So, unless you are prepared to dust off that C compiler, you're out of luck. -- Dan Moschuk (TFreak!dan@freebsd.org) "Try not. Do, or do not. There is no try." -- Yoda To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Sep 26 23: 4:43 1999 Delivered-To: freebsd-hackers@hub.freebsd.org Received: from lily.ezo.net (lily.ezo.net [206.102.130.13]) by hub.freebsd.org (Postfix) with ESMTP id 16C5E14E69; Sun, 26 Sep 1999 23:04:41 -0700 (PDT) (envelope-from jflowers@ezo.net) Received: from lily.ezo.net (jflowers@localhost.ezo.net [127.0.0.1]) by lily.ezo.net (8.8.7/8.8.7) with SMTP id CAA26024; Mon, 27 Sep 1999 02:04:29 -0400 (EDT) Date: Mon, 27 Sep 1999 02:04:28 -0400 (EDT) From: Jim Flowers To: Dan Moschuk Cc: Leif Neland , mrtg@list.ee.ethz.ch, freebsd-hackers@hub.FreeBSD.ORG Subject: Re: mrtg,FreeBSD, asus p2b temperature In-Reply-To: <19990927020335.A26862@november.jaded.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG MRTG is capable of graphing anything that can be expressed as a number. For an example look at the contributed example that graphs estimated bandwidth. I modified this to run with nttcp and use it to track the capability of all my circuits. Someone has a method of monitoring temperatures via a probe at a reasonable cost and inputting it to the computer but I don't remember where I saw it. Jim Flowers #4 ISP on C|NET, #1 in Ohio On Mon, 27 Sep 1999, Dan Moschuk wrote: > > | Does anybody have any tips for using the above combination for graphing temperatures? > | > | Leif > > As far as I know, MRTG is only able to fetch data from SNMP MIBs. Which, > in order to get the information you're looking for, two things have to happen. > You need to first have the kernel fetch that information from the > motherboard, and then some userland program to return it in the form of an SNMP > response. > > So, unless you are prepared to dust off that C compiler, you're out of > luck. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Sep 26 23: 5:46 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (Postfix) with ESMTP id 781B714E69; Sun, 26 Sep 1999 23:05:40 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.2) with ESMTP id IAA18591; Mon, 27 Sep 1999 08:05:14 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: Julian Elischer Cc: Carol Deihl , freebsd-security@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG Subject: Re: chroot could chdir? (was Re: about jail) In-reply-to: Your message of "Sun, 26 Sep 1999 17:01:35 PDT." Date: Mon, 27 Sep 1999 08:05:14 +0200 Message-ID: <18589.938412314@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message , Julian Elischer writes: >You have to examine ALL fd's in case one has a directory open that is >outside the chroot.. >(see man fchdir(2)) We do. See source. -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Sep 26 23:29:55 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from dorifer.heim3.tu-clausthal.de (dorifer.heim3.tu-clausthal.de [139.174.243.252]) by hub.freebsd.org (Postfix) with ESMTP id B5E68150F4 for ; Sun, 26 Sep 1999 23:29:43 -0700 (PDT) (envelope-from olli@dorifer.heim3.tu-clausthal.de) Received: (from olli@localhost) by dorifer.heim3.tu-clausthal.de (8.8.8/8.8.8) id IAA24988 for freebsd-hackers@FreeBSD.ORG; Mon, 27 Sep 1999 08:29:43 +0200 (CEST) (envelope-from olli) Date: Mon, 27 Sep 1999 08:29:43 +0200 (CEST) From: Oliver Fromme Message-Id: <199909270629.IAA24988@dorifer.heim3.tu-clausthal.de> To: freebsd-hackers@FreeBSD.ORG Subject: Re: mrtg,FreeBSD, asus p2b temperature Organization: Administration Heim 3 Reply-To: freebsd-hackers@FreeBSD.ORG MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Newsreader: TIN [version 1.2 RZTUC(3) PL2] Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Jim Flowers wrote in list.freebsd-hackers: > MRTG is capable of graphing anything that can be expressed as a number. > For an example look at the contributed example that graphs estimated > bandwidth. I modified this to run with nttcp and use it to track the > capability of all my circuits. > > Someone has a method of monitoring temperatures via a probe at a > reasonable cost and inputting it to the computer but I don't remember > where I saw it. Not necessary. The mainboards of the ASUS P2B series have everything onboard that you need. We have it working with the intpm0 driver and a tool called "lm" that I donwloaded from somewhere in Japan (forgot the URL, sorry). However, the problem is, it only works with 3.0-current from around January. It doesn't work with any recent -stable or -current. I suspected it was because of newbus, so I tried to port it, but without success. :-( Regards Oliver -- Oliver Fromme, Leibnizstr. 18/61, 38678 Clausthal, Germany (Info: finger userinfo:olli@dorifer.heim3.tu-clausthal.de) "In jedem Stück Kohle wartet ein Diamant auf seine Geburt" (Terry Pratchett) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Sep 27 0: 6:38 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from shidahara1.planet.sci.kobe-u.ac.jp (shidahara1.planet.sci.kobe-u.ac.jp [133.30.50.200]) by hub.freebsd.org (Postfix) with ESMTP id 4F4F71520F; Mon, 27 Sep 1999 00:06:33 -0700 (PDT) (envelope-from takawata@shidahara1.planet.sci.kobe-u.ac.jp) Received: from shidahara1.planet.sci.kobe-u.ac.jp (localhost [127.0.0.1]) by shidahara1.planet.sci.kobe-u.ac.jp (8.8.8+2.7Wbeta7/8.8.8) with ESMTP id QAA05840; Mon, 27 Sep 1999 16:06:21 +0900 (JST) Message-Id: <199909270706.QAA05840@shidahara1.planet.sci.kobe-u.ac.jp> To: freebsd-hackers@FreeBSD.ORG Cc: nsouch@FreeBSD.ORG Subject: Re: mrtg,FreeBSD, asus p2b temperature In-reply-to: Your message of "Mon, 27 Sep 1999 08:29:43 +0200" References: <199909270629.IAA24988@dorifer.heim3.tu-clausthal.de> Date: Mon, 27 Sep 1999 16:06:20 +0900 From: Takanori Watanabe Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199909270629.IAA24988@dorifer.heim3.tu-clausthal.de>, Oliver Fromme wrote: > > Someone has a method of monitoring temperatures via a probe at a > > reasonable cost and inputting it to the computer but I don't remember > > where I saw it. > >Not necessary. The mainboards of the ASUS P2B series have >everything onboard that you need. We have it working with >the intpm0 driver and a tool called "lm" that I donwloaded >from somewhere in Japan (forgot the URL, sorry). Call me?;-) If you mention lm.c, it is available from http://www.planet.sci.kobe-u.ac.jp/~takawata/smbus/examples/ . >However, the problem is, it only works with 3.0-current from >around January. It doesn't work with any recent -stable or >-current. I suspected it was because of newbus, so I tried >to port it, but without success. :-( It *does* work on recent CURRENT.You need not to patch for CURRENT kernel,just config(8) with controller intpm0 controller smbus0 device smb0 . But will not work on STABLE or RELEASE because intpm(4) is not merged. I port it to 3.2-STABLE , and I send it for Nicolas,the GURU of IICBus/SMbus. There is another tool to monitor Templature as an applet for Window Maker. (sysutils/wmhm/) Takanori Watanabe Public Key Key fingerprint = 2C 51 E2 78 2C E1 C5 2D 0F F1 20 A3 11 3A 62 2A To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Sep 27 0:18:30 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from verdi.nethelp.no (verdi.nethelp.no [158.36.41.162]) by hub.freebsd.org (Postfix) with SMTP id CC3291524B for ; Mon, 27 Sep 1999 00:18:27 -0700 (PDT) (envelope-from sthaug@nethelp.no) Received: (qmail 14975 invoked by uid 1001); 27 Sep 1999 07:18:26 +0000 (GMT) To: takawata@shidahara1.planet.sci.kobe-u.ac.jp Cc: freebsd-hackers@FreeBSD.ORG, nsouch@FreeBSD.ORG Subject: Re: mrtg,FreeBSD, asus p2b temperature From: sthaug@nethelp.no In-Reply-To: Your message of "Mon, 27 Sep 1999 16:06:20 +0900" References: <199909270706.QAA05840@shidahara1.planet.sci.kobe-u.ac.jp> X-Mailer: Mew version 1.05+ on Emacs 19.34.2 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Date: Mon, 27 Sep 1999 09:18:25 +0200 Message-ID: <14973.938416705@verdi.nethelp.no> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > >However, the problem is, it only works with 3.0-current from > >around January. It doesn't work with any recent -stable or > >-current. I suspected it was because of newbus, so I tried > >to port it, but without success. :-( > > It *does* work on recent CURRENT.You need not to patch for CURRENT kernel,just > config(8) with > controller intpm0 > controller smbus0 > device smb0 > . > But will not work on STABLE or RELEASE because intpm(4) is not merged. > I port it to 3.2-STABLE , and I send it for Nicolas,the GURU of IICBus/SMbus. Could you post the 3.2-STABLE changes to the list also? Thanks! Steinar Haug, Nethelp consulting, sthaug@nethelp.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Sep 27 0:31:20 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (Postfix) with ESMTP id AFD7C14D6E; Mon, 27 Sep 1999 00:31:10 -0700 (PDT) (envelope-from julian@whistle.com) Received: from home.elischer.org (home.elischer.org [207.76.204.203]) by alpo.whistle.com (8.9.1a/8.9.1) with ESMTP id AAA01431; Mon, 27 Sep 1999 00:30:29 -0700 (PDT) Date: Mon, 27 Sep 1999 00:30:29 -0700 (PDT) From: Julian Elischer X-Sender: julian@home.elischer.org To: Poul-Henning Kamp Cc: Carol Deihl , freebsd-security@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG Subject: Re: chroot could chdir? (was Re: about jail) In-Reply-To: <18589.938412314@critter.freebsd.dk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I read it as her talking about chroot in general. On Mon, 27 Sep 1999, Poul-Henning Kamp wrote: > In message , Julian > Elischer writes: > > >You have to examine ALL fd's in case one has a directory open that is > >outside the chroot.. > >(see man fchdir(2)) > > We do. See source. > > -- > Poul-Henning Kamp FreeBSD coreteam member > phk@FreeBSD.ORG "Real hackers run -current on their laptop." > FreeBSD -- It will take a long time before progress goes too far! > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Sep 27 0:37:21 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (Postfix) with ESMTP id 3069114E28; Mon, 27 Sep 1999 00:37:16 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.2) with ESMTP id JAA19099; Mon, 27 Sep 1999 09:36:24 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: Julian Elischer Cc: Carol Deihl , freebsd-security@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG Subject: Re: chroot could chdir? (was Re: about jail) In-reply-to: Your message of "Mon, 27 Sep 1999 00:30:29 PDT." Date: Mon, 27 Sep 1999 09:36:24 +0200 Message-ID: <19097.938417784@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message , Julian Elischer writes: >I read it as her talking about chroot in general. We do. See source. :-) > >On Mon, 27 Sep 1999, Poul-Henning Kamp wrote: > >> In message , Julian >> Elischer writes: >> >> >You have to examine ALL fd's in case one has a directory open that is >> >outside the chroot.. >> >(see man fchdir(2)) >> >> We do. See source. >> >> -- >> Poul-Henning Kamp FreeBSD coreteam member >> phk@FreeBSD.ORG "Real hackers run -current on their laptop." >> FreeBSD -- It will take a long time before progress goes too far! >> > > -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Sep 27 0:49:23 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from shidahara1.planet.sci.kobe-u.ac.jp (shidahara1.planet.sci.kobe-u.ac.jp [133.30.50.200]) by hub.freebsd.org (Postfix) with ESMTP id 4B86514D6E; Mon, 27 Sep 1999 00:49:18 -0700 (PDT) (envelope-from takawata@shidahara1.planet.sci.kobe-u.ac.jp) Received: from shidahara1.planet.sci.kobe-u.ac.jp (localhost [127.0.0.1]) by shidahara1.planet.sci.kobe-u.ac.jp (8.8.8+2.7Wbeta7/8.8.8) with ESMTP id QAA06271; Mon, 27 Sep 1999 16:49:01 +0900 (JST) Message-Id: <199909270749.QAA06271@shidahara1.planet.sci.kobe-u.ac.jp> To: sthaug@nethelp.no Cc: hackers@freebsd.org, nsouch@freebsd.org Subject: Re: mrtg,FreeBSD, asus p2b temperature In-reply-to: Your message of "Mon, 27 Sep 1999 09:18:25 +0200" References: <199909270706.QAA05840@shidahara1.planet.sci.kobe-u.ac.jp> <14973.938416705@verdi.nethelp.no> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----- =_aaaaaaaaaa0" Content-ID: <6227.938418279.0@shidahara1.planet.sci.kobe-u.ac.jp> Date: Mon, 27 Sep 1999 16:49:00 +0900 From: Takanori Watanabe Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG ------- =_aaaaaaaaaa0 Content-Type: text/plain; charset="iso-2022-jp" Content-ID: <6227.938418279.1@shidahara1.planet.sci.kobe-u.ac.jp> In message <14973.938416705@verdi.nethelp.no>, sthaug@nethelp.no wrote: >> But will not work on STABLE or RELEASE because intpm(4) is not merged. >> I port it to 3.2-STABLE , and I send it for Nicolas,the GURU of IICBus/SMbus >. Not perfectly yet. I only pointed out the bug that was containd in the patch he send to me.I checked by my spd.c .But I don't sure whether the code was correct. Basically,import Revision 1.4 of intpm.c and newest version of intpmreg.h , and add the imported file to conf/files . ------- =_aaaaaaaaaa0 Content-Type: application/octet-stream Content-ID: <6227.938418279.2@shidahara1.planet.sci.kobe-u.ac.jp> Content-Description: The patch he send to me(gziped) Content-Transfer-Encoding: base64 H4sICN8c7zcAAzExNy4zLnR4dADdGmtz2kjys/gVHbvOBQGMJMCA9pINxuwuFQJewEnurq5UQhqM KkJiJWHIZfPfr3tGgCSEcbKb3IOy9Zjp13T3dPfMqOdabKOB6bmzysx2WJB78cd/uVFnDERNg8rc W7CKaz4ElcA3K8HHoLLnVXrI+Sz0bfZgu/fg4y2wPReUS6UlX6qXipKz7NkMyiso+/tGEHKWy2Xx JCmtVqsiNytqDeSaJitaVZZiNIrFYhrwCpS6Vpe1ajX36hWUrxS5dAVFujXg1ascLE27Ys/09fTS lCRvGaJUhgPrKVgoo8nKlm8/MH8Ht3EScBsnEy5Y6nhPQGJbCrTIQd1wuUgCUksW1QULmecnYEVT FrBrJiHxPQssLSW+p8CE0hpCac2Y0vA/WC2Xnh8ihTgB0b22TH2Z1KllZokQ2AsvSADylixlGU5K V9SQRXPjL1dJO2HDAaAX2JtaRdz0hU0eEISGaxm+te9VZLmqK4m+XmwiCQ7faypF3I5PJlXJmExR I2xlpekUPUfzpFGR66DKGv7VG1KMDk2oJKiYUleaXNfUK+4daoNPKbo1uXcM7vr9n8b6Ta/982A4 nvQ6ZAfdYtPVve6uHGcWXM5zMO7pN93ru5+lWG9gU0+ueA7BYroKcGiOETJrJ3mxO2hf97t6u98e TQSimECEBecwmbOAgWms6Do33HsWoI844KHBIZwz+MB8lzk5iDhzCveONzUcJBHZFd2kYtsm8qfb pfntbZvmeNS+VwnDXoGQj+zJnyITKRW5BUpTk5uaWpMIi8wYhxBGbGhVDKAKN6Jy1SopKhT5XUxy yZ5BPjDLLwNTN72VG8KLFyAXsENC6Va+C/lub/C23S/8QDbj4Hnm+xiQXoAYju6z31YsCHV8zovp p9+zUF8aPnPDPAJhY6EE4qEEvV5HvxkOJu/avUmhUECiO1acMHIqIv9IGljYbn5le+WXeEFWgW2V 4Prup3Hv712SScLmBZp+O4jpajZjfgk4egmwl0sOUkroqeOZH/S1b4fsMaEjqoZl+SVSCv6yGV0E iLdV0lYvDjMC9jS9RKMWmtgpAj4jQW66lkrzT2k1Sor8X205GkXlOSyMDRgLLpc3A8sIDQg9dHPD gucVBHGYe9q4IvTIfOiqokShhw8F1R/Y/2LwEpL4XAFLw7XN/NlfAg2ZerBYmXMhAvF/dlYCXf/p btCZ9IYDXf+zjAb5lCvaLgpZgkhS4Ytxm6oi46pqk2blbmTPAvNbWpGsJuVnjnEfwAUM9cFwcN0f dl4X4MeEgUHjkARMzbzpdw7RG0xGhUftH6ztEFWeNxdWAT7RZEaVQk/tjCcY0zUaXWoMmHf9MC9E xlmH+nOMB9SZjDS5rmoK11W9uXUCi82MlRMmiHUHw5vuW4oKn0mSr7UpxGwam4mZqQNv3z97cKZH E0gjkUAasJMyyiH85UgaaWzTSBxol0mwImhwczSusEgs8isZA57TP7x//x481/mIF0bJHUQVBsHc WzkWsI0dhDBDSzEDvQPdgepg5s8MkxF+JVcOQn9lhlunELbavplz27HQYv/4J1r6U66ILhPaJnwB Ckif4Ay7ULQzHs2u77CCGfXedkd6p98ej0twRlJhoBq/uYapb1v37Aw+l3aYj6LdM5f5VB6vfCws 0d8rQ4F8jrNWznYfLPi+v/twpkfdp4ZVYTXhQrwFdtJGbsRfIg9RK3INlJqGf3yxJmhErhQH3LlS FYtQkdlkLEYUTG3izuc2/1GoGXV/veuOJzpqvIThhNKwHhYu5t6a534eDsUM5VipoLL0HAeDcQkE fFn6DGv0CBYLV6kmeIZB5N3wrn8jYqKIBRHEM4HFHUkKkE2wdOb2/Txf+EFC4ruE7K3RDwismGqD iwvYvyArCjeCnIS0NvkgYnhqJFxvapVXBHjbq21PRdrHZlm8i5BIuXnmMwaG+5HKZs/kxTfmTm/l 48zBWVhM6LUoTEE+32n3+9ftzuuMIIpCFkSBMOr2u+1xl5ssyiCHhvucGWNjM4QvDej6vWZHjOGT K3MhHk0H/rQLqUoNVFWr1zW5uqvM4xDbSaA2NEXlxqzWyZZ4FfH03HZNZ2Ux+CuJhwXE5fxluhWr iYzWBTcpdRSTHTPTDR2OEEdZYCC2XVYxqRoWvdy3muhbGOCVZq3UqCdKE/j9d3gWHC9Q0L22XsUX Y7TC4z6VqFy4thOFyy71L6anqhSMzbEqBfL0HpUn9Ph4eXKsOCHMX+96ndf6u1Fv0tVoQnOsF0LW 31a2+SGjQOF4HIVHGOnew+zBXItii5QcLn/LP5kcD0/SFEvWDyIqpOQcdds3XyYmYaSlxKD4R0Tl JFOSlh9R8bg7uLk+kBrXTtY0gwU+EYkTAp7AFtEvS4+jbuftoTA+Mx+yyF08TZpT6MfF4WY/lIev UY+Pj99pcXM5/RiyU9KdIrat+RM0T4j8Llvk9RNEXnv+SYUeIxYT9ZDmY0ZvkwdGxUN8nPoyxHxX ltLuYDziXSUOn9YYp8SH9aijZBI+Nqwd3ceH9u5gaKSP40N7qpWePKQvtNSJId1SzXEwpKXvmSwI Ln16OxzX0sQUdMpkaVoBve1lS7I4NfBTHItfzPG4Sq6jBLXXidj+oeLypDdPxY7XozYXO1pf79jH eGS4QbR59gU+fi3S3tcNnvzzG489m8VXD12SnrjVgXVXtM2RLLu2E3O/A5KstHjZVsYMqmVvekBm Vf49160ppsfXrck1K+zFjCr0xEI0vvFBVXptW6VnLldpXdsSpXGpjnVxSRTFleflXBmeQ8dbfvRx JRhiyVMARG3CANe9jhHA2FuZ81WumAlVomsrDUtbKW3HAQ5L5yMB8x+YdbnbZxkxyw5QBdMVnZjg Ss4COgyxXYgWcdQytV3D/0jbLYugBFiQzQEdh+7eKuRDqfMFJF6rNT4aviirPOeyxj27QC3RCNwH 5qNMhhsd3gh3xGLSgJVrb8T7JQGj89lumCvGKWED4enbpSUtkalt69TyD2Lbjmb2Foy2tWnio8N3 R6NEVS/z6XiAcCGWBIgwGd/d3haipXh65tDanzmktyPYuNI9xH3fG55EnfTedId3kwPk/cbCSRK4 ev7bAT41xjCTnXwRxnu5Dg9WPry5IhxI2ISv03hIKOxcq71duxngsjUPIzghXGbSJgGamWLLvf3A XBBhJDpvTe7kVBvJnRxRm3zVTk6UXv/3N3IyBxLfx6kr334fBw3xlG0cYa8/dRuHR9X5fyJhzI8m DJWOvxNJg7fAXtx44phHKaFaUaogyxpmBVmRtlTiyWOeOkVXFU2p/98ljxqdAOA1ctpzLFJsl8VC tSRv5FQ7OpPoUA4QeKjGHjVXTvWgp2J7NVfMbK+l2jvDfr+H7c1Ue/t6OJoQZznVEQVrYp3uonhL LOQoMZL6fvHW8CvtiGBcXCxIVzZmwQ0zVzj9xNkI/1KiUYv28tgmZDg7otSXfVyH1dj+yRbnyBl4 B6dYMbwYyrbpIMzHYIsH5PcZelf97Sg+eLYVgSGAH2O/0s25QafgeAXHW0dPFE35SGLEssLC9zs8 S7B88tHZVsQoEJw8OEvC7L5Mq2qq2OdV6q1SjYI93cg7omOkN8Obu35XrCH4QSQ+lSKNi0O03Rt7 MHG6I5QsTkezSUxDWzX/EAU03tOFKGeSwNvDEwkUMwkYztNFiNzLrjavxHdU/d5g8u19K8nvqGPV qy06ElMT/rVtBC4q+Rg9xL9/xOxRUzF7SDEK5GdJOOFkNU2NskyjdlVqopfRPfqy4BzG4js+rBF2 h66BRh3C2+Dg4FOEfSovxCFU/LD2HKYfQh9XqZ6Hd8aatSYngHPfWmMpEYMtnouvHaUeNjlw2+u9 r8Gtt8bC6Y3hGvdsQWXknWuHBEof+0ltEzvbDlYbtlvuva28rdz6nnoECc5zVKKGPpZWdNZM3oGB PNbE2SebiA2P6tF5MWLJkhGFwh/3wSr9DeS396c0x6Me1bxCd2gl/Ek0QUJg8qrEV5zCa67owFZW tVpLfAwYUSPfyoDe+liNFsviwKpZ4ydWeIu+x9h+unRG1usb0wDe1NVaA247vTL+59s/3+59sLA9 XOdlJN/ckTcIXlXkaUvD0paeIWBsEYBjf2D03ijhkgTdd+Fx/5p55K6W/WBbjH9RlC1AdStAjGNx y7GhyArnGF9VxvCV+qaa7XZnUYGPonawLtsAqhlXRRZWSVRjNJriK6eIj4w/atRy/waZhlwmoC0A AA== ------- =_aaaaaaaaaa0 Content-Type: text/plain; charset="iso-2022-jp" Content-ID: <6227.938418279.3@shidahara1.planet.sci.kobe-u.ac.jp> This contains bug in the patch applied to smbconf.c @@ -109,11 +137,11 @@ . This will cause infinite loop when you issue request. 'while(error !=EWOULDBLOCK)' is wrong because this loop should be ended when error==0 . And here is the merged version of intpm.c ------- =_aaaaaaaaaa0 Content-Type: application/octet-stream Content-ID: <6227.938418279.4@shidahara1.planet.sci.kobe-u.ac.jp> Content-Description: The merged from current version of intpm.c(gziped) Content-Transfer-Encoding: base64 H4sICDx52DcAA2ludHBtLmMA7Fx9d9rG0v8bPsXG98YFohicNm1ih+RgkBOdYqAIx8np06MrS4ut Y5CoJPzS2P3sd2ZW7y8YHOfe+/SUNgnsy+zM7OxvZlarbTaeV1mDdZ3FjWudnfusZtTZ7uvXryT8 +zWb6Be67bgWO9F93dZPObbuzGaMWnvM5R53L7m5A+VYNeam5fmudbr0Lcdmum2ypceZZTPPWboG p5JTy9bdGzZ13LknsSvLP2eOS/86Sx+pzB3TmlqGjjQkprucLbg7t3yfm2zhOpeWCV/8c92HvzjQ mc2cK8s+Y4ZjmxZ28pAK9ptzfw+/7+5kWPOYMw15MhwTWi49H8TxdeAVqeqnziVWBYpBIsHHdnzL 4BK0sjw2A5pIKh6aREzzBQMbM92acxf1xF7kmYFBE1oJmQFZzSUw+O34YULaBDXTMZZzbvt6OIFN mBsH2rhsrvvctfSZF08CTR4ST4oTGsPkg6IydXg4OemMZQbfR+PhR6Un99jBZ6iUWed48mE4Zp1B j3WHg8lYOTieDMcq+9e/Oiq0/+47rCKLG3xm8qfRWFZVBh2Uo1FfATJAd9wZTBRZlZgy6PaPe8rg vcSAChsMJ6yvHCkTaDYZSjgcEsr3ZMNDdiSPux/gZ+dA6SuTz8TQoTIZ4HCHyCAbdcYTpXvc74zZ 6Hg8GqpEDcXqKWq331GO5N4Oqk8ZwNBM/igPJkz90On3k4LC/yk5D2TgsXPQJ2I0EMjZU8Zyd4IC xd+6oDVgry8xdSR3Ffwif5JBls74sxSQVeVfjqERVCK1Xueo8x6kq92jF5iS7vFYPkJ+QRPq8YE6 USbHE5m9Hw57KpIC8qo8/qh0ZXWf9YcqqexYlSUYZNKh4YEK6Auq4fvBsaqQ5pTBRB6Pj0cTZTio I6EPwxNQDDDbgd490vJwQDKDjobjz0gX9UGTILGTDzKUj1GlpLUO6kIF7XUnSC3REkYFfU4SwrKB /L6vvJcHXRlrh0joRFHlOsyZomIDRYx80vlMMh6T+DhXwJv4mjBeiWaUKYes0/uoIPNBY7AEVQms ZniIlNTj7odA+8E6qPxTMfdgofmL+Y4hXQIW/UDg2mztNl+8Yq3W3suf9l5+D0sI1qfN5OsF+yd0 a1ar/7BsY7YEcNpaGNbO+VaiQJCDIiibssGoq7C3rCV+gOJHR+xtK27+xrvxmgvd1aHL20wx/PEL ii+4a/NZunyuG+eWzZunS09bWE555ZzPV1RjRUGNMXOMizwjyywlLAQPsZzxfHlAPV0IWDgtIKGD uo0iEtMMgya/bHpzII1/h8QSc0F1mjWl6Wg2JojDHviyGbg6DjA+B+Q2GcwMYLvBNZhLba4vNJhC 5i0XC8cFvwbTnWYDarnrLhd+hhno3YQ/Lj9Lsx6UX+puvpyMJeiR4NtZ+FpsRx5CvsEAxpeGz4BL zzKrX6qhXwA6pqWBx71Z8P1qxTjX3UrD5J6xX73DSs0yvV9/Y23oUvnCWtc/7e5+/6r16kdpSwFJ ZuzVi+9/2u0csJFzRa7E1s84+hn0VL4Lrom7W3dStSJ6t4KPVBkc9/sV/NxV7/ZDJlF18AcUr4Er OuU1mCLwgZpfL2qi+z6YWEGbS8cyYzrwRQNLnJlRS4kl+hQQhn/cqDG2LRzem12uaEg8RJzO3PVo GmC8p7pxkWopBS1Mfi0xQzdNF8shcCsk8fvSyvVfajivzJvpl1xQO3euioXitnm6sjd9P73xeWF/ lxuXa/RvlBK4ci2fr0HBmJv38UKkrtYkBQvb9dmV45olcunr6CXmqlxCJLUZV41SthZoMBvR8tBw IsJuqRmdkvbWJB2UG87S9iP5l9Niwij/Y9FNrnQocv004bA/0EIObAdXYbHd+85ijSUPrbSFk1F5 YdOpy3lJqwCKCaLJa3jO1DdYQxSQ+6ohpaVtJUAN8BRSAJSnEXZFiGSaNqrVgIpBKK6fSSlIr+d1 hWMQcqa7ogO0zgDuBUDQ4HFnEABSC8/TIgHDkhhBA2khNzt3TC0UUPwEH9KOnU5P/ngEQeCwF2qI RJGS0F+XylsL9sPm4he0L+hAEU3sAaQCr5AYqICAiAFCWA6HDH8XMim6EAyH7enHisaEumFj+rGi MUGsZCXwdkVjAadha/HrvuZXqeZXK1nRzQQr+j18A+4lG6+iTMAWGQT+WNFYYFXYWvxa1RwHj1rj j0TjLy2pRSHJ6tUa2zLN30LHZa6fgdUDUc/fL6g+h6R7xoMW5xBrZXsu5tixUtADas73kyGbWLHT M2geYQwj6SBsi1j9VaQMv4Ew1VgMsrG0DGWIRF+NImECWe8RNMF0xGbAZVhOkOlB0c1+IhA0XeuS uxGGiJ+szWKWt4QkW1KSUgw3idkfK5CcapPPI1k7gqQ+rvGsP7gzrRVoBuwh5mWpQfp2FpAnV8Sy 1lFBRQkJQ47FD+S4IpI65LSSAG6IiZNgDD+3E0OQBWIerqkyJMAI6UKBHvel1BiZELZaGD+TA6oW TXgkM2t4BmsXaYM16uH0nXFflNWER4voGc/f0sS2xRIjJ6bBt0w7SJZqT6LG9ag8/LjcX7o2q8nK 4GOnX9/HsmaDffr0iZmO/Z3PLmznil3RFqETtuYzj2NenTE10JSGiQyyEGYrI0X59ANTjw6OVYYl 7hQMdivBYDXLSUswIT5rs3KXmJJwRjLpytpTwkrmZI0pEeu3vR0jQqITenjq81u6k1iN7RZgC83U eTsmRRNH4EXf/VyVH1QlysAoYJQcEpCBagAVoWJis9jH/Q6TT5k8wF00rdPvjCfVSrMh2/rpjLOO C5EeaDkBlYT52q4g4kuCcYmmW4PpVvsfu4MJrLFKhbFMKZCfyAMcFBwvGGiRCcCEJsOoeJHlk0sE wjjBDGe5Qk2ntS3m2Oyp99TckpJrytbnHIOVeqqUZghLgYGK4GY/ZVrRat8wb0SGsI67roOwinON ofFc9y4QonES295iZnO/hmN7V5YP8WKNaNUR0wwdDB1UqI1xe1KdaLCi9kC96E4v9lP1fbmjytl6 mF19OfOxKGRCrHmou4MBF7PrmheLzWrUiiai2SCE5O4CrIC2++en/rUWBt1gF4GCYr8QqikflH9J uo+E/N9qVVrTWi22Wow9yo32gzqB/+rb1Qr2TBd3SOOf68UrBZrf3q49DiyDxDjp9QEV4UC0OgLa CaAoBXEZ+4WWdG6dndfqhUCzu49Lu2d5tLYBlWl7jJ4tYT7IFmKxg6B2XtJNEaAVrfOIlWZjzMFX 4L72mB3O9DPE84XLF/igCQs3QhoxaQHS1HKThvRuRWV+RuVxeR0os1taedhR+nWopLUaLp3MdLSS IJZYE/mNKUSHx7J7ghkcdEmgQl/aGy4ApIJhGvbdLl4GwHGIFGhOFQKRuNOKeaiUzkK+JpqDfBXN ALGBAvvzBXIB/2wiK9gnyrqRrYVeDcwCRtv+M1NHcpJzq5A64lWLrOb8PZRc6Rd8uYCW1Ocu1mtL IHOkZYiFBo7Pus58MeNip7so6incJX1MC0vgd2BoEvB4qc+E84AviDAxnm9kgQE0FltgCh4jPUWD l/cg7AqNJbM/TGoP+CaVU0gZ0/qzVkjtNluq9k5eCLgoqtqth0smGgdBWAChSiOxMT+zPHCzmwZa CH/FPObDr5DTQh7L2vc/JgKDUN3pAG3lxvvj49vs0rD9kqg1irMix4Oaxp1EdsZt7gLPkF2S85m6 zpxRN9S5oLqJqQoAKeTiYZGyYCGBKqmImUUSVXpyv/O59rJOrhyCKAyCITdymO55HKI0yw+PK9gM q+E3Zk7feXTIYA4ZAHd3IHGqFHNP+mtngrhgVT4RkeGXXBiyCYx2ej0JvoFcY1kd5UjlP7d99UCg ambzOYvO2mg8BM/xeSJLuyEMP6mlBErtKtfFyqxcOjOwDAiIluihX4HpNjCCRwoV/HKfXZBTyAZ0 wFKvM2kRH1FGQjrWUG48bLDHni7+z4bsBAcJfQCB0JcwPmQs7AqucjiG1nUCEIEgz7lI0gos+muM 8LbUBhPGFy2wXLKUzNqKHhTYnnVmc5MVPS94VLxIjyQChYfFCejvIXW75i3xg922kfPoR9YQwcrH E1qgJ+doWLZDQba+9B2x9790xeGgKAQX6TZ6drJaw5mZt7dPQq1USsYRIcf+ZjEzTjeQE5l2szGC 1YCw2HVMvsPCX5ZHTHMbEkBXPwMl4smMU27oeBhNwY1E8Ae/Ly0Xz5E5EMsAzkwhuaSTTGJHDiYE keEGD3HUXrxu/fj9y9bLnYU5FbZK20R0quVgCaaxdHHcU8fx0SCEVgzdRi5OOR6BoxNyzHPoONwi 4JMOnl2RkosUvCNOgZRmqSVPmVKpqnApkvX4mWoFLQSWeoOBMkRuHWzHMkm1INi7Ib2CnDuiFZ2L mDnOwmO7rdbzF60W860596gaTAcmoGZBjGG9aV3/NJ1O961nzwrg+gGZcVUAXElOUDBG5BrELkS2 +I7CoBJ+K+lU5uG5jPAAK9MZ4QKywXngBku7AhrX38nKkO0R+K8aogsNcaR7WlJWgyT3BAPAueCh 3dreLpcBESCQIfIySxv3S20m1urV+c27LeGGMMUIg7kgThI+p1ohjxPnU7l0hXKeByDnZrFB7Inu zbHi/Ah0JvaqYK1HMGSIXCk8QRtFsN5y5gtQWIkJ98LBNwCDzK4gGAB6AZrbZkN1xGldi0CRIDBA 2QA4cY+XDqaKUpAbtLb0dhAWKitioP1qziTCEIRWj+/NOMckVaqNTjrKpH476nYm3Q/SFtCHgi3p /I/mq8AE08v2K9bt2gt3w4W6wUpdf6k+ZK1Gi1VMylNzL79qMTZMxpa5/WqKYQULd8XRfOX+LQ4x Qn6vPhsiZvbuqVsWSwhh7oIMdwKeyQHPPnIdg4OVcsq0kjuUWdhNxrTecgGr1eOUX4pogKKG1Ebl WsKtL1nphl4AMQV7LusfAasWoAhKHRYGvfChwbfbE0fqbWKM1P0Lco9YOUeQhNgi3OfvQEYC2peY gmfi7YvEIz/xgKKGIsUSRc8gfjkZKxN5L+fvceDt9p+Qyu3Hjybyvcdyp1fc+bZNfbNVGUrRs45s O6Hu8LlHWHqXfFgQZbeVdKd8Lpwlvio1jhhdaxmmE0hMlYNTY5V1099fjpXuz7T3XsZJzhmUSHWX UFPuQV38jKhoI3KDk41Fy+Lb2f99M/qYmxwk6vafYvfia4h1j3pScMRxo02QIiO4b/LvVsx0fqI3 OoL6F5/p4NHAbfF8f+W0Fe9kRZtYge8fy92PmqJCoKGBzVSjuIE1G33LXl6LkBBUvZxOmT6DVNp3 nSV4W0/4yYMwvcfM/DuPcNc755DGX1mzGW0IzPULzowZ190d6pNwDNkPzfome2csY/QUa0Ao+o1G CLbnMo8ow8/dA5fEAw9V/8UXx2PBIGjtK6ngrG+MpvSW1reH04eeov/beP6TxhMAPWp+u3U9nX49 zd2QZg2Jvn37qh4SXtdCT76JhRZ6/Ae9nPEXt9ASp/8wA/16VLonWojjgkdxoNnRH+o5H/qyzt+2 9fi2VY4n99hWtnlkaThVm+wEknERDJZnskT0tr3JswxE2wBd37x59VDjpb1m1oPwmIn4mO4C8KIt Wnx2Q69mehBmz9h0aRviIobTpS8Cb9EBqRT0+SnqQZvXFHdDBf4edTv9/g5THaYkzkYjnatzTlcM WEG0Drq5SO10J5ba47zLVo0SD3wFHhnTJrI6+Uuvxv+xWISm5dGikFqCHEYhD01j8+iR3mjbAD+E qT0WcAhqj4MYOXyITh5hypo4yhckmEUu71He/Czyf9/iaXVIb401Rzy+Bf0d9IfdnyfjzkDVjjqf bm+pot1u5U8yF2/Qrlq/4Rk6Cw+o2/qM6a6r34hD+AXbEg84Hfr/ATLiR+ik25In/huPedD/GQxf Avv61fptZZD3EHEIu4jfh2+VoWX9JzKex3iJ+u8l+r+9RB81xv4aKv/VhbHOjEZC/cFdB9zoNOS2 2VA8jD1tzk1uvluxLywM7L7JDh5Lr5FvJtgm0k/wKTx9e9PO2bd4/B52KQbPRLrLBACWxh8Bl5VK musE3wJIo6f09FeZBOG5i/BUAz12LmscPWoPCwrQLHgh92jYO+7LNTHzEnMdSCiiN1vpvFn0tr4Z XDUgsRb8XxevM2fvNMAn8uJGAyps6O4ZnkMouD6haiWuT1hxdUL+5Uxxe06lwResHdyNE+tCHPir 8cXzt9idbW+z6PuTdkAyq7Bnz/gi92SfaOCrqyn43+jaiC9JKMSSN+Jd8NK3tRLviGLzxDuhhU87 gl54i09wZFPV55zpHkteg4SZJV1fZ53Zjss9PBQ8Ugap9C9/e1It8YK7JO4gsn18qRwPQWMSKrFo isG9hQdqG3hOaSHO60bCJw7fi6ywM1K6mjJMtbD5tb+wIBOeL6/FQf7gNEmzwdQFN4rzaXooNf6F vU7AClKz3N/BR76OFSiYBSMGOUBum94LD6y0/nx3P3ytGAmCyDj1l5gShP0T9EUnS9zPFBbGo2M5 0MaloBkACiKMj4aVkDeJCRWS8gKViVUVTXjwQqYg49g2N/yaFdhjbFbBokbbLvDLiVSjWPGB0mEc /KbpC8vQgL0a/KkXyQbjhV3erBhwt6Av6Ddu3mAd3+fzhc/ongI8nkZXRoL1nrrOBbfZfAFggA8g dxK9kgQUfHFh+DMeMb7hsxnEQ5YdXOcY9aVrKgXBepJOipMPun1GB5vF3ZR4zjg85Dz8OdGwmZdJ mCpo78X+vSoNyus5rAqIvGEvEa3C7m9xQlnezYrWz57l4X/9ge9SExqMDwO+LBowPI526pwtPXY0 EqoFqwUswWVosx+YMiTLYjCMxwJjFae/UaMeghJeoheeQHSZonaaMvwl4j88wyVeYMgOHhtwnvfq fRw+NR+JsRCTipbEeisomOr7Jvd+7IhQMsaPKCopxJHwsxaeJM1iFa6UT092TsL310DpwLmrx3oV K5+7dCgXIRumq4Yn9U1xtypOkiiu0xREkqc1e988FFl/5sF+DFq5N1Wim0FqiZuZyLeL3rl7m4Jh oGsFm+1n3OClPlvyAisSCSFGF3Fl3jzKgg/PsCwjr5IoM4XwzQrv2cg3I54okgK/RyltLCssDu0A bw6AhGiMQav0Q4Huafx2MgQKbs3KNqS3X7FtG2OWFUlE+OpQthzfb6oQieCmi3aN2N/erb9Tvn/1 Ix7W1dRRpyuDl9vLlBzJR/tVOjPd1cU7ImG8g9dEIuafcnoHDt86KbhJB9YCPiFrUDfsgpcYevF+ O26dh5dOQii99C07fANF9Itpvnv3Lt8S9+YhGNYXi+AQTdEZmoTw520he+3P6KW2VG07L3/yGV+z 0TEMxzVRESEgQpwV3HUcnetxDGPplidtaNXmcj6/2Y8ph2qd8/lKW9pOsittE5ngbbfsMIlD0Yv5 U3OPPfXY02u2JaGlSfHQtZRxZDWgDOvvtpTmEKASlGxu7W0dcfBjN1sJCkmexIucdOPBYKjhNcbv ZQ3k6A4Hh9AjWDNiqzYl6BiPdPeVgSy1rluv6aXDnESlnTXIaLXu4XvSEYuyUqzBg+JYrEHM+/o2 VSKOd9NQ0TnsiOzzt6A4MPkV6zxmWVhT/GYipMlyj6JsgOgtKU+0QLr7QCUpYpF2grPEwsBb17wA K+hscEoF6pGSP98bUfTd9ha02CpPnEveSMoPhNq/ZyRKSjYfq/SYcor4wfD9sVpAfOW6cWnNeDCD QEOqxcDJtsTJelwPprgBxNyqP2BSx/JHpVc6pSErLrglDx38UxMdOxFN3u8kPgU7hnmdQBaAkREg FckH67PXl8fsHOKNgsZ5DAPEzCe+sUzxnoZEqCBt29zXLIyz6rgPWu6/cnB1qIMboMAThiFuUfYS N5mfxqQHbwd+HQKl4NYj3LbBe76k6D42QkXysaVhQf7qp8QYhcnC+oHCvxfgi9JOwAiNAF9o+Q0L BB1EasRePsMKgrS0NGTHYd1ijDQWhTQMhfWUL/R2FNLAezLyMWyo6jSB5kG2ZcHPbimGVBngc7Pg Kymgp26gyHHBmp+gDjHsaHFQ2oQW2gA7fP31NWIAAA== ------- =_aaaaaaaaaa0-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Sep 27 2:33:51 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from rucus.ru.ac.za (rucus.ru.ac.za [146.231.29.2]) by hub.freebsd.org (Postfix) with SMTP id 67E3314E4D for ; Mon, 27 Sep 1999 02:33:44 -0700 (PDT) (envelope-from nbm@rucus.ru.ac.za) Received: (qmail 54791 invoked by uid 1003); 27 Sep 1999 09:35:50 -0000 Date: Mon, 27 Sep 1999 11:35:50 +0200 From: Neil Blakey-Milner To: Andrew Reilly Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: A new package fetching utility, pkg_get Message-ID: <19990927113550.A53070@rucus.ru.ac.za> References: <199909252352.BAA26437@dorifer.heim3.tu-clausthal.de> <19990927102234.A53880@gurney.reilly.home> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre2i In-Reply-To: <19990927102234.A53880@gurney.reilly.home> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon 1999-09-27 (10:22), Andrew Reilly wrote: > I've longed for a mechanism to keep the ports that I use as > up-to-date as the rest of my FreeBSD system. Unfortunately, > some ports I don't use very often, and so forget that they're > there. > > Unfortunately (again), the port name-version_number identifier > isn't _quite_ unique enough to use as a key for tracking ports. > For example: ssh and docbook have multiple versions for the same > base name installed concurrently. > > What I'd like is a little weekly crontab script that runs after > my weekly ports cvsup, and tells me which of the ports that I > "subscribe to" has changed, so that I can think about rebuilding it. I have patches to pkg_version that teach it to handle multiple versions installed and in the ports INDEX, which works pretty well in my use, albeit a bit slower than pkg_version. They are at http://rucus.ru.ac.za/~nbm/pkg_version-patch I've got a local patch at home that can take a list of packages (like "pkg_version gtk docbook ssh") and checks only those packages for changes - it does break current command-line interpretation - usually pkg_version takes a path to the INDEX as its only argument, my patches use a -f location option. Plug in those patches Nik has, and you can have intelligent automatic updating (although sometimes you'll clobber your configuration files). Neil -- Neil Blakey-Milner nbm@rucus.ru.ac.za To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Sep 27 4:16:16 1999 Delivered-To: freebsd-hackers@hub.freebsd.org Received: from freesbee.wheel.dk (freesbee.wheel.dk [193.162.159.97]) by hub.freebsd.org (Postfix) with ESMTP id 3287314F12 for ; Mon, 27 Sep 1999 04:16:13 -0700 (PDT) (envelope-from jesper@wheel.dk) Received: by freesbee.wheel.dk (Postfix, from userid 1001) id C1A6C3E1B; Mon, 27 Sep 1999 13:16:12 +0200 (CEST) Date: Mon, 27 Sep 1999 13:16:12 +0200 From: Jesper Skriver To: Dan Moschuk Cc: Leif Neland , mrtg@list.ee.ethz.ch, freebsd-hackers@hub.FreeBSD.ORG Subject: Re: mrtg,FreeBSD, asus p2b temperature Message-ID: <19990927131612.F2429@skriver.dk> References: <02fb01bf086a$dae8aae0$0e00a8c0@neland.dk> <19990927020335.A26862@november.jaded.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii User-Agent: Mutt/0.96.2i In-Reply-To: <19990927020335.A26862@november.jaded.net>; from Dan Moschuk on Mon, Sep 27, 1999 at 02:03:35AM -0400 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Sep 27, 1999 at 02:03:35AM -0400, Dan Moschuk wrote: > > | Does anybody have any tips for using the above combination for graphing temperatures? > | > | Leif > > As far as I know, MRTG is only able to fetch data from SNMP MIBs. Which, > in order to get the information you're looking for, two things have to happen. > You need to first have the kernel fetch that information from the > motherboard, and then some userland program to return it in the form of an SNMP > response. > > So, unless you are prepared to dust off that C compiler, you're out of > luck. In the past I've used a syntax like Target[abc]: `cat file` or Target[abc]: `program` Where the program has output like (or the file contains) ---- First number\n Second number\n \n \n ---- /Jesper -- Jesper Skriver (JS4261-RIPE), Network manager Tele Danmark DataNet, IP section (AS3292) One Unix to rule them all, One Resolver to find them, One IP to bring them all and in the zone to bind them. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Sep 27 4:24:34 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from pawn.primelocation.net (pawn.primelocation.net [205.161.238.235]) by hub.freebsd.org (Postfix) with ESMTP id 4106414E28 for ; Mon, 27 Sep 1999 04:24:32 -0700 (PDT) (envelope-from jedgar@fxp.org) Received: from earth.fxp (oca-p1-5.hitter.net [207.192.76.5]) by pawn.primelocation.net (Postfix) with ESMTP id EBE9AF80F; Mon, 27 Sep 1999 07:24:30 -0400 (EDT) Date: Mon, 27 Sep 1999 07:24:30 -0400 (EDT) From: "Chris D. Faulhaber" X-Sender: jedgar@earth.fxp To: Leif Neland Cc: mrtg@list.ee.ethz.ch, freebsd-hackers@FreeBSD.ORG Subject: Re: mrtg,FreeBSD, asus p2b temperature In-Reply-To: <02fb01bf086a$dae8aae0$0e00a8c0@neland.dk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 27 Sep 1999, Leif Neland wrote: > Does anybody have any tips for using the above combination for graphing temperatures? > You can start with: http://www.fxp.org/~jedgar/lmmon-0.52.tar.gz http://www.fxp.org/~jedgar/wmlmmon-0.52.tar.gz I'm sure you could add snmp hooks in somewhere :) ----- Chris D. Faulhaber | All the true gurus I've met never System/Network Administrator, | claimed they were one and always Reality Check Information, Inc. | pointed to someone better. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Sep 27 7: 6:15 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from acl.lanl.gov (acl.lanl.gov [128.165.147.1]) by hub.freebsd.org (Postfix) with ESMTP id 7315414E13 for ; Mon, 27 Sep 1999 07:06:14 -0700 (PDT) (envelope-from rminnich@lanl.gov) Received: from localhost (rminnich@localhost) by acl.lanl.gov (8.8.8/8.8.5) with ESMTP id IAA130654; Mon, 27 Sep 1999 08:06:04 -0600 (MDT) X-Authentication-Warning: acl.lanl.gov: rminnich owned process doing -bs Date: Mon, 27 Sep 1999 08:06:03 -0600 From: "Ronald G. Minnich" To: Zhihui Zhang Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: NFS and RPC In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG You have a lot mixed up here. On Thu, 23 Sep 1999, Zhihui Zhang wrote: > Once inside the kernel, the NFS daemons can not use RPC library any more, > they must create/interprete RPC format messages themselves. My guess this > is for performance reason and because there is no kernel-to-kernel RPC. There is kernel-to-kernel RPC. NFS in the kernel on both client and server sides use RPC. They don't use -lrpc though ... > Since the kernel part of NFS code does not use RPC library routines, why > FreeBSD still conforms to the RPC format for NFS requests/replies? Is > this for compatibily with other NFS servers/clients that are implemented > entirely as user-level code and with RPC library routines? Because some NFS servers run in user mode (automount, amd, early linux, even *very* early sunos). Some clients run in user mode too (mostly evil hacker software ... but also Bigfoot, see www.acl.lanl.gov/~rminnich) > One more question is about how to assembly a RPC request from several > mbufs? I notice that there is a check for 0x80000000 in the routine > nfsrv_getstream() for the last fragment. that's to support rpc over tcp. You need to look at the code again. ron To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Sep 27 7:18:14 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from marithe.recluse.net (marithe.recluse.net [216.200.139.86]) by hub.freebsd.org (Postfix) with ESMTP id BA53A14EDF for ; Mon, 27 Sep 1999 07:18:12 -0700 (PDT) (envelope-from brandon@recluse.net) Received: by marithe.recluse.net (Postfix, from userid 2000) id 95327584C; Mon, 27 Sep 1999 07:18:34 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by marithe.recluse.net (Postfix) with ESMTP id 8F48876; Mon, 27 Sep 1999 07:18:34 -0700 (PDT) Date: Mon, 27 Sep 1999 07:18:34 -0700 (PDT) From: brandon huey To: "Chris D. Faulhaber" Cc: Leif Neland , mrtg@list.ee.ethz.ch, freebsd-hackers@FreeBSD.ORG Subject: Re: mrtg,FreeBSD, asus p2b temperature In-Reply-To: Message-ID: X-Copyright: (C)1999 Brandon Huey; Forwarding prohibited MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG actually, mrtg will take input from an application with four output lines: in out uptime label this is how i'm getting temperature information graphed from my thermochron iButton :) On Mon, 27 Sep 1999, Chris D. Faulhaber wrote: > On Mon, 27 Sep 1999, Leif Neland wrote: > > > Does anybody have any tips for using the above combination for graphing temperatures? > > > > You can start with: > http://www.fxp.org/~jedgar/lmmon-0.52.tar.gz > http://www.fxp.org/~jedgar/wmlmmon-0.52.tar.gz > > I'm sure you could add snmp hooks in somewhere :) > > ----- > Chris D. Faulhaber | All the true gurus I've met never > System/Network Administrator, | claimed they were one and always > Reality Check Information, Inc. | pointed to someone better. > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Sep 27 8:48:26 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from web307.mail.yahoo.com (web307.mail.yahoo.com [128.11.68.238]) by hub.freebsd.org (Postfix) with SMTP id 1B63F15037 for ; Mon, 27 Sep 1999 08:48:22 -0700 (PDT) (envelope-from noeldamonmiller@yahoo.com) Message-ID: <19990927154833.2316.rocketmail@web307.mail.yahoo.com> Received: from [207.138.28.180] by web307.mail.yahoo.com; Mon, 27 Sep 1999 08:48:33 PDT Date: Mon, 27 Sep 1999 08:48:33 -0700 (PDT) From: Noel Miller Subject: here to help To: freebsd-hackers@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Freebsd crew, I'm here to help. My skills are primarily sys admin experience and limited perl programming. Please let me know what I can do. Noel __________________________________________________ Do You Yahoo!? Bid and sell for free at http://auctions.yahoo.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Sep 27 9:54: 9 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.numachi.com (numachi.numachi.com [198.175.254.2]) by hub.freebsd.org (Postfix) with SMTP id A048714F94 for ; Mon, 27 Sep 1999 09:54:03 -0700 (PDT) (envelope-from reichert@numachi.com) Received: (qmail 23966 invoked by uid 1001); 27 Sep 1999 16:53:57 -0000 Date: Mon, 27 Sep 1999 12:53:57 -0400 From: Brian Reichert To: Mike Smith Cc: Brian Reichert , freebsd-hackers@freebsd.org Subject: Re: 3.3-R on Dell w/ DPT RAID Message-ID: <19990927125356.A23727@numachi.com> References: <19990924150956.C5560@numachi.com> <199909270116.SAA15376@dingo.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95i In-Reply-To: <199909270116.SAA15376@dingo.cdrom.com>; from Mike Smith on Sun, Sep 26, 1999 at 06:16:09PM -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Sep 26, 1999 at 06:16:09PM -0700, Mike Smith wrote: > > We've told this machine via it's BIOS to pretend it only has 256M. > > > > When we try an install from the floppies, the mfsroot floppies > > panics with an 'pmap_enter: invalid page directory, pdir=0x601063, > > va=0xc2400000'. > > > > I have no idea what this error message means. > > It suggests that you have memory problems; have you tried physically > extracting most of the memory from the system? No; I instead used the BIOS's mechanism for artifically restricting available memory. (I had in fact also tried removing all but 512M from the machine, but to no avail.) I do have an update, however, I re-generated the kern.flp and mfsroot.flp floppies, and now, I can successfully launch the install program. We are re-configuring the RIAD controller now; once we have a core OS, with all memory enabled, I'll repor back... > -- > \\ The mind's the standard \\ Mike Smith > \\ of the man. \\ msmith@freebsd.org > \\ -- Joseph Merrick \\ msmith@cdrom.com -- Brian 'you Bastard' Reichert reichert@numachi.com 37 Crystal Ave. #303 Daytime number: (781) 899-7484 x704 Derry NH 03038-1713 USA Intel architecture: the left-hand path To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Sep 27 9:54:52 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from bingnet2.cc.binghamton.edu (bingnet2.cc.binghamton.edu [128.226.1.18]) by hub.freebsd.org (Postfix) with ESMTP id C2FC3156A9 for ; Mon, 27 Sep 1999 09:54:44 -0700 (PDT) (envelope-from zzhang@cs.binghamton.edu) Received: from sol.cs.binghamton.edu (cs1-gw.cs.binghamton.edu [128.226.171.72]) by bingnet2.cc.binghamton.edu (8.9.3/8.9.3) with SMTP id MAA29310 for ; Mon, 27 Sep 1999 12:54:41 -0400 (EDT) Date: Mon, 27 Sep 1999 12:40:25 -0400 (EDT) From: Zhihui Zhang To: freebsd-hackers@freebsd.org Subject: Register a RPC service with inetd Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have typed in the source code of rls (remote directory list) from the book "Power programming with RPC" and run it under FreeBSD successfully. But I can not get the rls server registered with inetd so that it can be started *automatically* during bootup. What I have done is as follows: (1) Use the -I option on rpcgen to generate inetd compatible server code: > rpcget -I rls.x (I wonder if -I is only used for SunOS) (2) Modify the file /etc/inetd.conf to contain the following line: rls/1 stream rpc/tcp nowait root /usr/libexec/rls_svc rls_svc where 1 in the version number. (3) Modify the file /etc/rpc to contain the following line: rls 20000001 where 20000001 in the program number of the rls. However, when I type "./rls host-address directory" on a client machine, it response "RPC: program not registered". I even modify the file /etc/defaults/rc.conf to set inetd_flags to be "-d" (debug). This makes sure that inetd does register rls during bootup. After bootup, the "rpcinfo -p localhost" on server also shows rls is there. Can anyone tell me what I am missing? Thanks a lot. -------------------------------------------------- Zhihui Zhang. Please visit http://www.freebsd.org -------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Sep 27 11: 4:15 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mg-20425427-16.ricochet.net (mg-20425427-16.ricochet.net [204.254.27.16]) by hub.freebsd.org (Postfix) with ESMTP id C61CB150C9 for ; Mon, 27 Sep 1999 11:03:59 -0700 (PDT) (envelope-from gurney_j@efn.org) Received: (from jmg@localhost) by mg-20425427-16.ricochet.net (8.9.1/8.8.7) id LAA27667; Mon, 27 Sep 1999 11:03:35 -0700 (PDT) Message-ID: <19990927110332.31201@hydrogen.fircrest.net> Date: Mon, 27 Sep 1999 11:03:32 -0700 From: John-Mark Gurney To: andrew@ugh.net.au Cc: Jan Pechanec , freebsd-hackers@FreeBSD.ORG Subject: Re: Corrupt File System References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.69 In-Reply-To: ; from andrew@ugh.net.au on Sun, Sep 26, 1999 at 11:49:36PM +1000 Reply-To: John-Mark Gurney Organization: Cu Networking X-Operating-System: FreeBSD 3.0-RELEASE i386 X-PGP-Fingerprint: B7 EC EF F8 AE ED A7 31 96 7A 22 B3 D8 56 36 F4 X-Files: The truth is out there X-URL: http://resnet.uoregon.edu/~gurney_j/ Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG andrew@ugh.net.au scribbled this message on Sep 26: > That may well be...I'm not really sure...the data is still there as I can > dd parts of the disk to a file then use beav to view it...I can read ascii > text but it would be an extremely ling job to try and extart it that way. that's why I wrote ffsrecov... but you should be able to recover the fs's assuming you haven't writen anything to the slice of the disk that contained your data... ffsrecov is in ports... -- John-Mark Gurney Voice: +1 408 975 9651 Cu Networking "The soul contains in itself the event that shall presently befall it. The event is only the actualizing of its thought." -- Ralph Waldo Emerson To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Sep 27 11:51:33 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from nothing-going-on.demon.co.uk (nothing-going-on.demon.co.uk [193.237.89.66]) by hub.freebsd.org (Postfix) with ESMTP id B4ABE1542C for ; Mon, 27 Sep 1999 11:50:28 -0700 (PDT) (envelope-from nik@nothing-going-on.demon.co.uk) Received: from kilt.nothing-going-on.org (kilt.nothing-going-on.org [192.168.1.18]) by nothing-going-on.demon.co.uk (8.9.3/8.9.3) with ESMTP id TAA60839; Mon, 27 Sep 1999 19:34:06 +0100 (BST) (envelope-from nik@catkin.nothing-going-on.org) Received: (from nik@localhost) by kilt.nothing-going-on.org (8.9.3/8.9.3) id IAA03122; Mon, 27 Sep 1999 08:09:13 +0100 (BST) (envelope-from nik@catkin.nothing-going-on.org) Date: Mon, 27 Sep 1999 08:09:13 +0100 From: Nik Clayton To: Andrew Reilly Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: A new package fetching utility, pkg_get Message-ID: <19990927080912.A2944@kilt.nothing-going-on.org> References: <199909252352.BAA26437@dorifer.heim3.tu-clausthal.de> <19990927102234.A53880@gurney.reilly.home> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <19990927102234.A53880@gurney.reilly.home>; from Andrew Reilly on Mon, Sep 27, 1999 at 10:22:34AM +1000 Organization: FreeBSD Project Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Sep 27, 1999 at 10:22:34AM +1000, Andrew Reilly wrote: > What I'd like is a little weekly crontab script that runs after > my weekly ports cvsup, and tells me which of the ports that I > "subscribe to" has changed, so that I can think about rebuilding it. ports/sysutils/pkg_version. Then apply the patches at http://www.freebsd.org/~nik/pkg_version.diff pkg_version.1.diff and use the -c flag. N -- [intentional self-reference] can be easily accommodated using a blessed, non-self-referential dummy head-node whose own object destructor severs the links. -- Tom Christiansen in <375143b5@cs.colorado.edu> To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Sep 27 12:56:35 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from imo-d09.mx.aol.com (imo-d09.mx.aol.com [205.188.157.41]) by hub.freebsd.org (Postfix) with ESMTP id E0D6915776 for ; Mon, 27 Sep 1999 12:56:21 -0700 (PDT) (envelope-from Scm486@aol.com) Received: from Scm486@aol.com by imo-d09.mx.aol.com (mail_out_v22.4.) id nLWEDYtfy_ (3973) for ; Mon, 27 Sep 1999 15:56:18 -0400 (EDT) From: Scm486@aol.com Message-ID: <49064d67.252125e1@aol.com> Date: Mon, 27 Sep 1999 15:56:17 EDT Subject: Netscape Bus Error To: freebsd-hackers@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: AOL 4.0 for Windows 95 sub 22 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Does anyone know what "Bus Error" means from Netscape? I have never seen this before. Its very annoying it usually happens at random times while visiting web pages it also causes netscape to core dump and closes all the pages I am visiting. Thanks Sam To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Sep 27 13:10:20 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from ns.mt.sri.com (ns.mt.sri.com [206.127.79.91]) by hub.freebsd.org (Postfix) with ESMTP id C7709152E0 for ; Mon, 27 Sep 1999 13:10:15 -0700 (PDT) (envelope-from nate@mt.sri.com) Received: from mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by ns.mt.sri.com (8.9.3/8.9.3) with SMTP id OAA28261; Mon, 27 Sep 1999 14:10:14 -0600 (MDT) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id OAA12060; Mon, 27 Sep 1999 14:10:13 -0600 Date: Mon, 27 Sep 1999 14:10:13 -0600 Message-Id: <199909272010.OAA12060@mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Scm486@aol.com Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Netscape Bus Error In-Reply-To: <49064d67.252125e1@aol.com> References: <49064d67.252125e1@aol.com> X-Mailer: VM 6.34 under 19.16 "Lille" XEmacs Lucid Reply-To: nate@mt.sri.com (Nate Williams) Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Does anyone know what "Bus Error" means from Netscape? It means that the program has a bug in it that caused it to write/read from memory that it invalid. This can happen is you try to read from free'd memory, or write to NULL pointers, etc..... It can also happen if a program assumes a routine uses a particular implementation, and that implementation changes w/out an API change (say a shared library update), the program may be doing something 'illegal' that once worked. In short, it's a netscape bug.... Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Sep 27 13:39:10 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from tinker.com (troll.tinker.com [204.214.7.146]) by hub.freebsd.org (Postfix) with ESMTP id 37F4814D0E; Mon, 27 Sep 1999 13:39:04 -0700 (PDT) (envelope-from carol@tinker.com) Received: by localhost (8.8.5/8.8.5) Received: by mail.tinker.com via smap (V2.0) id xma012399; Mon Sep 27 15:16:02 1999 Received: by localhost (8.8.8/8.8.8) id PAA13704; Mon, 27 Sep 1999 15:38:09 -0500 (CDT) Message-ID: <37EFD593.A6900748@tinker.com> Date: Mon, 27 Sep 1999 15:37:39 -0500 From: Carol Deihl Organization: Shrier and Deihl X-Mailer: Mozilla 4.5 [en] (X11; U; FreeBSD 2.2.8-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: trouble@hackfurby.com Cc: freebsd-security@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG Subject: Re: chroot could chdir? (was Re: about jail) References: <199909251302.RAA58030@grendel.sovlink.ru> <19990925171712.A80535@zenon.net> <37EEA27E.244DCF9A@tinker.com> <37F00602.96D098D3@hackfurby.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello, I was referring to the practice of chdir-ing to someplace within the chrooted area right *after* doing the chroot, before doing anything else. Otherwise, the current working directory may be pointing to a directory *outside* the chrooted area. Of course, if you set the current working directory to someplace inside the chrooted area *before* doing the chroot, that's fine too. However, it is a danger that some programmers are not careful (or are malicious), and neither set an appropriate current dir before chrooting, nor afterwards. Since this allows one to break out of a chrooted area, I'm looking for a solution to this security problem. Carol TrouBle wrote: > > Ummm sorry but i think you have goten this backwards it is more secure to > chdir, then chrrot, not chroot then chdir.... I believe what you have here is > backwards > > > > > As we all know, the chroot can be escaped because the sample > > program doesn't change the current working directory, and it's > > still pointing outside the chrooted area. > > > > What if chroot itself chdir'ed to it's new root directory? Would > > this break existing programs? I'd expect that well-behaved > > programs would chdir someplace useful before continuing anyway. > > > > At the very end of chroot(), could it just > > vrele(fdp->fd_cdir); > > fdp->fd_cdir = nd.ni_vp; > > before it returns, setting the current dir to the same place it > > just chrooted to? -- Carol Deihl - principal, Shrier and Deihl - mailto:carol@tinker.com Remote Unix Network Admin, Security, Internet Software Development Tinker Internet Services - Superior FreeBSD-based Web Hosting http://www.tinker.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Sep 27 13:41:55 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from tinker.com (troll.tinker.com [204.214.7.146]) by hub.freebsd.org (Postfix) with ESMTP id BDBD115362; Mon, 27 Sep 1999 13:41:36 -0700 (PDT) (envelope-from carol@tinker.com) Received: by localhost (8.8.5/8.8.5) Received: by mail.tinker.com via smap (V2.0) id xma012420; Mon Sep 27 15:18:42 1999 Received: by localhost (8.8.8/8.8.8) id PAA14572; Mon, 27 Sep 1999 15:40:52 -0500 (CDT) Message-ID: <37EFD638.528A5C9@tinker.com> Date: Mon, 27 Sep 1999 15:40:24 -0500 From: Carol Deihl Organization: Shrier and Deihl X-Mailer: Mozilla 4.5 [en] (X11; U; FreeBSD 2.2.8-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: Poul-Henning Kamp Cc: Julian Elischer , freebsd-security@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG Subject: Re: chroot could chdir? (was Re: about jail) References: <19097.938417784@critter.freebsd.dk> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Poul-Henning Kamp wrote: > > In message , Julian Elischer writes: > >I read it as her talking about chroot in general. Yep, I was. > We do. See source. :-) Are you talking about the new jail() call only, or does this apply to chroot() (especially in 3.2) ? (And I am looking in the source now, I'm just not too familiar with it... :-) ) Carol > >> >You have to examine ALL fd's in case one has a directory open that is > >> >outside the chroot.. > >> >(see man fchdir(2)) > >> > >> We do. See source. -- Carol Deihl - principal, Shrier and Deihl - mailto:carol@tinker.com Remote Unix Network Admin, Security, Internet Software Development Tinker Internet Services - Superior FreeBSD-based Web Hosting http://www.tinker.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Sep 27 14:22:34 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from bingnet2.cc.binghamton.edu (bingnet2.cc.binghamton.edu [128.226.1.18]) by hub.freebsd.org (Postfix) with ESMTP id 9184514FE9 for ; Mon, 27 Sep 1999 14:22:30 -0700 (PDT) (envelope-from zzhang@cs.binghamton.edu) Received: from sol.cs.binghamton.edu (cs1-gw.cs.binghamton.edu [128.226.171.72]) by bingnet2.cc.binghamton.edu (8.9.3/8.9.3) with SMTP id RAA06485 for ; Mon, 27 Sep 1999 17:21:23 -0400 (EDT) Date: Mon, 27 Sep 1999 17:07:03 -0400 (EDT) From: Zhihui Zhang To: freebsd-hackers@freebsd.org Subject: Register a RPC service with inetd Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 27 Sep 1999, Alfred Perlstein wrote: > > On Mon, 27 Sep 1999, Zhihui Zhang wrote: > > > > > I have typed in the source code of rls (remote directory list) from the book > > "Power programming with RPC" and run it under FreeBSD successfully. > > > > But I can not get the rls server registered with inetd so that it can be > > started *automatically* during bootup. What I have done is as follows: > > ... > > Is portmap running? > I think so. On the server side: now4# rpcinfo -p localhost program vers proto port 100000 2 tcp 111 portmapper 100000 2 udp 111 portmapper 100005 3 udp 1023 mountd 100005 3 tcp 1023 mountd 100005 1 udp 1023 mountd 100005 1 tcp 1023 mountd 100003 2 udp 2049 nfs 100003 3 udp 2049 nfs 100003 2 tcp 2049 nfs 100003 3 tcp 2049 nfs 100024 1 udp 1011 status 100024 1 tcp 1022 status 20000001 1 tcp 1024 rls <-- this is the service now4# On the client side: > newrpc/rls now4 / now4: RPC: Program not registered -Zhihui -------------------------------------------------- Zhihui Zhang. Please visit http://www.freebsd.org -------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Sep 27 15: 9:17 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from uni4nn.gn.iaf.nl (osmium.gn.iaf.nl [193.67.144.12]) by hub.freebsd.org (Postfix) with ESMTP id 592BB154A5 for ; Mon, 27 Sep 1999 15:09:10 -0700 (PDT) (envelope-from wilko@yedi.iaf.nl) Received: from yedi.iaf.nl (uucp@localhost) by uni4nn.gn.iaf.nl (8.9.2/8.9.2) with UUCP id AAA22149 for FreeBSD-hackers@freebsd.org; Tue, 28 Sep 1999 00:04:14 +0200 (MET DST) Received: (from wilko@localhost) by yedi.iaf.nl (8.9.3/8.9.3) id WAA04128 for FreeBSD-hackers@freebsd.org; Mon, 27 Sep 1999 22:39:06 +0200 (CEST) (envelope-from wilko) From: Wilko Bulte Message-Id: <199909272039.WAA04128@yedi.iaf.nl> Subject: 2.88Mb floppies To: FreeBSD-hackers@freebsd.org (FreeBSD hackers list) Date: Mon, 27 Sep 1999 22:39:06 +0200 (CEST) X-Organisation: Private FreeBSD site - Arnhem, The Netherlands X-pgp-info: PGP public key at 'finger wilko@freefall.freebsd.org' X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi there, Just having installed a 2.88Mb floppy drive in one of my axp boxes I wonder if FreeBSD can do 2.88Mb floppy disks. From the looks of the contents of /sys/i386/isa/fd.c: static struct fd_type fd_types[NUMTYPES] = { { 21,2,0xFF,0x04,82,3444,1,FDC_500KBPS,2,0x0C,2 }, /* 1.72M in HD 3.5in */ { 18,2,0xFF,0x1B,82,2952,1,FDC_500KBPS,2,0x6C,1 }, /* 1.48M in HD 3.5in */ { 18,2,0xFF,0x1B,80,2880,1,FDC_500KBPS,2,0x6C,1 }, /* 1.44M in HD 3.5in */ it appears it cannot. Is this true? Is there anything that stops one from adding an appropriate line to this struct? And to dev/MAKEDEV of course? TIA Wilko -- | / o / / _ Arnhem, The Netherlands - Powered by FreeBSD - |/|/ / / /( (_) Bulte WWW : http://www.tcja.nl http://www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Sep 27 15:17:57 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from dt014n8c.san.rr.com (dt014n8c.san.rr.com [24.30.129.140]) by hub.freebsd.org (Postfix) with ESMTP id 0E087156BC for ; Mon, 27 Sep 1999 15:17:45 -0700 (PDT) (envelope-from Doug@gorean.org) Received: from localhost (doug@localhost) by dt014n8c.san.rr.com (8.9.3/8.8.8) with ESMTP id PAA09996; Mon, 27 Sep 1999 15:17:33 -0700 (PDT) (envelope-from Doug@gorean.org) Date: Mon, 27 Sep 1999 15:17:32 -0700 (PDT) From: Doug X-Sender: doug@dt014n8c.san.rr.com To: Noel Miller Cc: freebsd-hackers@freebsd.org Subject: Re: here to help In-Reply-To: <19990927154833.2316.rocketmail@web307.mail.yahoo.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 27 Sep 1999, Noel Miller wrote: > Freebsd crew, > > I'm here to help. My skills are primarily sys admin > experience and limited perl programming. Please let me > know what I can do. Welcome aboard. Start by reading the FAQ and the Handbook on the web site. One of the things you will see in there are instructions for new users who want to contribute to the project. Good luck, Doug -- "Stop it, I'm gettin' misty." - Mel Gibson as Porter, "Payback" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Sep 27 15:31:47 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from m4.c2.telstra-mm.net.au (m4.c2.telstra-mm.net.au [24.192.3.19]) by hub.freebsd.org (Postfix) with ESMTP id 3D99214F25 for ; Mon, 27 Sep 1999 15:31:37 -0700 (PDT) (envelope-from areilly@nsw.bigpond.net.au) Received: from m5.c2.telstra-mm.net.au (m5.c2.telstra-mm.net.au [24.192.3.20]) by m4.c2.telstra-mm.net.au (8.8.6 (PHNE_14041)/8.8.6) with ESMTP id IAA06466 for ; Tue, 28 Sep 1999 08:31:35 +1000 (EST) X-BPC-Relay-Envelope-From: areilly@nsw.bigpond.net.au X-BPC-Relay-Envelope-To: X-BPC-Relay-Sender-Host: m5.c2.telstra-mm.net.au [24.192.3.20] X-BPC-Relay-Info: Message delivered directly. Received: from areilly.bpc-users.org (CPE-24-192-49-170.nsw.bigpond.net.au [24.192.49.170]) by m5.c2.telstra-mm.net.au (8.8.6 (PHNE_14041)/8.8.6) with SMTP id IAA20829 for ; Tue, 28 Sep 1999 08:31:34 +1000 (EST) Received: (qmail 74739 invoked by uid 1000); 27 Sep 1999 22:31:34 -0000 From: "Andrew Reilly" Date: Tue, 28 Sep 1999 08:31:34 +1000 To: Nik Clayton Cc: Andrew Reilly , freebsd-hackers@FreeBSD.ORG Subject: Re: A new package fetching utility, pkg_get Message-ID: <19990928083134.A73274@gurney.reilly.home> References: <199909252352.BAA26437@dorifer.heim3.tu-clausthal.de> <19990927102234.A53880@gurney.reilly.home> <19990927080912.A2944@kilt.nothing-going-on.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre2i In-Reply-To: <19990927080912.A2944@kilt.nothing-going-on.org> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Sep 27, 1999 at 08:09:13AM +0100, Nik Clayton wrote: > On Mon, Sep 27, 1999 at 10:22:34AM +1000, Andrew Reilly wrote: > > What I'd like is a little weekly crontab script that runs after > > my weekly ports cvsup, and tells me which of the ports that I > > "subscribe to" has changed, so that I can think about rebuilding it. > > ports/sysutils/pkg_version. > > Then apply the patches at > > http://www.freebsd.org/~nik/pkg_version.diff > pkg_version.1.diff > > and use the -c flag. This is lovely. And it re-inforces one of my pet theories: if you want a program badly enough that you're prepared to write it, someone else almost certainly has... Thanks. -- Andrew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Sep 27 18:54:59 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.xmission.com (mail.xmission.com [198.60.22.22]) by hub.freebsd.org (Postfix) with ESMTP id 6B68214DDF for ; Mon, 27 Sep 1999 18:54:57 -0700 (PDT) (envelope-from wes@softweyr.com) Received: from [204.68.178.39] (helo=softweyr.com) by mail.xmission.com with esmtp (Exim 2.12 #2) id 11VmTn-00003Y-00; Mon, 27 Sep 1999 19:54:55 -0600 Message-ID: <37F02000.654DDFEA@softweyr.com> Date: Mon, 27 Sep 1999 19:55:12 -0600 From: Wes Peters Organization: Softweyr LLC X-Mailer: Mozilla 4.5 [en] (X11; U; FreeBSD 3.1-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: Ben Rosengart Cc: hackers@FreeBSD.ORG Subject: Re: A new package fetching utility, pkg_get References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Ben Rosengart wrote: > > On Fri, 24 Sep 1999, Bill Fumerola wrote: > > > I don't see why we need a pkg_get or whatever when pkg_add already has > > remote (with or without -r) functions, and adds dependencies just fine. > > Well, I for one would like a command that fetches a package without > installing it. I don't see any option to pkg_add for that. See fetch(1). ;^) (Sorry, catching up after a weekend of the flu.) -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC wes@softweyr.com http://softweyr.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Sep 27 18:55:32 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from bingsun2.cc.binghamton.edu (bingsun2.cc.binghamton.edu [128.226.6.4]) by hub.freebsd.org (Postfix) with ESMTP id 481BA15716 for ; Mon, 27 Sep 1999 18:55:23 -0700 (PDT) (envelope-from bf20761@binghamton.edu) Received: from localhost (bf20761@localhost) by bingsun2.cc.binghamton.edu (8.9.3/8.9.3) with ESMTP id VAA00519; Mon, 27 Sep 1999 21:55:17 -0400 (EDT) X-Authentication-Warning: bingsun2.cc.binghamton.edu: bf20761 owned process doing -bs Date: Mon, 27 Sep 1999 21:55:17 -0400 (EDT) From: Zhihui Zhang X-Sender: bf20761@bingsun2 To: Alfred Perlstein , freebsd-hackers@FreeBSD.ORG Subject: Re: Register a RPC service with inetd Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 27 Sep 1999, Alfred Perlstein wrote: > > On Mon, 27 Sep 1999, Zhihui Zhang wrote: > > > > > I have typed in the source code of rls (remote directory list) from the book > > "Power programming with RPC" and run it under FreeBSD successfully. > > > > But I can not get the rls server registered with inetd so that it can be > > started *automatically* during bootup. What I have done is as follows: > > ... > > Is portmap running? > I think so. On the server side: now4# rpcinfo -p localhost program vers proto port 100000 2 tcp 111 portmapper 100000 2 udp 111 portmapper 100005 3 udp 1023 mountd 100005 3 tcp 1023 mountd 100005 1 udp 1023 mountd 100005 1 tcp 1023 mountd 100003 2 udp 2049 nfs 100003 3 udp 2049 nfs 100003 2 tcp 2049 nfs 100003 3 tcp 2049 nfs 100024 1 udp 1011 status 100024 1 tcp 1022 status 20000001 1 tcp 1024 rls <-- this is the service now4# On the client side: > newrpc/rls now4 / now4: RPC: Program not registered -Zhihui -------------------------------------------------- | Zhihui Zhang, http://cs.binghamton.edu/~zzhang | | Dept. of Computer Science, SUNY at Binghamton | -------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Sep 27 20:43:44 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from beebite.ugh.net.au (beebite.ugh.net.au [203.31.238.37]) by hub.freebsd.org (Postfix) with ESMTP id CA90E14F85 for ; Mon, 27 Sep 1999 20:43:38 -0700 (PDT) (envelope-from andrew@ugh.net.au) Received: by beebite.ugh.net.au (Postfix, from userid 1000) id 4FEAB61; Tue, 28 Sep 1999 13:43:37 +1000 (EST) Received: from localhost (localhost [127.0.0.1]) by beebite.ugh.net.au (Postfix) with ESMTP id 34FD456; Tue, 28 Sep 1999 13:43:37 +1000 (EST) Date: Tue, 28 Sep 1999 13:43:37 +1000 (EST) From: andrew@ugh.net.au To: John-Mark Gurney Cc: Jan Pechanec , freebsd-hackers@FreeBSD.ORG Subject: Re: Corrupt File System In-Reply-To: <19990927110332.31201@hydrogen.fircrest.net> Message-ID: X-WonK: *wibble* MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 27 Sep 1999, John-Mark Gurney wrote: > that's why I wrote ffsrecov... but you should be able to recover the fs's > assuming you haven't writen anything to the slice of the disk that > contained your data... I tried it on both the var and usr partitions..not that var is too important but it is much smaller. With var it dumps up to inode 136 and core dumps with sig11: #0 0x280baa02 in memcpy () #1 0xefbfda2c in ?? () #2 0x8049f31 in dumpall (pi={fs = 0x280d6000, map = 0x280d4000, st = { st_dev = 131077, st_ino = 1420575, st_mode = 33188, st_nlink = 1, st_uid = 0, st_gid = 5, st_rdev = 5866536, st_atimespec = { tv_sec = 938523740, tv_nsec = 0}, st_mtimespec = { tv_sec = 895067625, tv_nsec = 0}, st_ctimespec = { tv_sec = 895067625, tv_nsec = 0}, st_size = 0x0000000001400000, st_blocks = 0x000000000000a030, st_blksize = 8192, st_flags = 0, st_gen = 1796484062, st_lspare = -188160832, st_qspare = { 0xf01be1a0f4c8e4c0, 0xf01be75800000002}}}) at main.c:450 #3 0x8048e0e in main (argc=1, argv=0xefbfdc5c) at main.c:179 #4 0x80489a9 in _start () With usr I have the problem with the image being greater than 2Gb and so mmap fails. Any ideas? Thanks for all your help, Andrew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Sep 27 21: 7:33 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mg-20425427-16.ricochet.net (mg-20425427-16.ricochet.net [204.254.27.16]) by hub.freebsd.org (Postfix) with ESMTP id D96F815011 for ; Mon, 27 Sep 1999 21:07:27 -0700 (PDT) (envelope-from gurney_j@efn.org) Received: (from jmg@localhost) by mg-20425427-16.ricochet.net (8.9.1/8.8.7) id VAA06143; Mon, 27 Sep 1999 21:07:09 -0700 (PDT) Message-ID: <19990927210703.25786@hydrogen.fircrest.net> Date: Mon, 27 Sep 1999 21:07:03 -0700 From: John-Mark Gurney To: andrew@ugh.net.au Cc: Jan Pechanec , freebsd-hackers@FreeBSD.ORG Subject: Re: Corrupt File System References: <19990927110332.31201@hydrogen.fircrest.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.69 In-Reply-To: ; from andrew@ugh.net.au on Tue, Sep 28, 1999 at 01:43:37PM +1000 Reply-To: John-Mark Gurney Organization: Cu Networking X-Operating-System: FreeBSD 3.0-RELEASE i386 X-PGP-Fingerprint: B7 EC EF F8 AE ED A7 31 96 7A 22 B3 D8 56 36 F4 X-Files: The truth is out there X-URL: http://resnet.uoregon.edu/~gurney_j/ Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG andrew@ugh.net.au scribbled this message on Sep 28: > On Mon, 27 Sep 1999, John-Mark Gurney wrote: > > > that's why I wrote ffsrecov... but you should be able to recover the fs's > > assuming you haven't writen anything to the slice of the disk that > > contained your data... > > I tried it on both the var and usr partitions..not that var is too > important but it is much smaller. With var it dumps up to inode 136 and > core dumps with sig11: > > #0 0x280baa02 in memcpy () > #1 0xefbfda2c in ?? () interesting, this must be getinode, as that is what is called at 450.. if this is the case, then it could be that my size calculation is messed up around the for loop, the block is out of range, I didn't allocate enough data (shouldn't happen, if it does, the inode is corrupt), or I didn't map enough of file system... (to small of size for the partition) > #2 0x8049f31 in dumpall (pi={fs = 0x280d6000, map = 0x280d4000, st = { > st_dev = 131077, st_ino = 1420575, st_mode = 33188, st_nlink = 1, > st_uid = 0, st_gid = 5, st_rdev = 5866536, st_atimespec = { > tv_sec = 938523740, tv_nsec = 0}, st_mtimespec = { > tv_sec = 895067625, tv_nsec = 0}, st_ctimespec = { > tv_sec = 895067625, tv_nsec = 0}, st_size = 0x0000000001400000, > st_blocks = 0x000000000000a030, st_blksize = 8192, st_flags = 0, > st_gen = 1796484062, st_lspare = -188160832, st_qspare = { > 0xf01be1a0f4c8e4c0, 0xf01be75800000002}}}) at main.c:450 > #3 0x8048e0e in main (argc=1, argv=0xefbfdc5c) at main.c:179 > #4 0x80489a9 in _start () > > With usr I have the problem with the image being greater than 2Gb and so > mmap fails. yeh, I know about this... I'm thinking about writing a bit of code that mmap's a cylindar group as needed, and then if an mmap fails, it will throw the oldest cylindar group away (I could even do a really stupid linked list for this)... > Any ideas? > > Thanks for all your help, it's hard to say... I'd need to get a fuller dump of ffsrecov at the segfault, like a dump of the inode that it's segfaulting on... -- John-Mark Gurney Voice: +1 408 975 9651 Cu Networking "The soul contains in itself the event that shall presently befall it. The event is only the actualizing of its thought." -- Ralph Waldo Emerson To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Sep 28 1:49: 0 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from herring.nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (Postfix) with ESMTP id 6C54115463 for ; Tue, 28 Sep 1999 01:48:56 -0700 (PDT) (envelope-from dfr@nlsystems.com) Received: from salmon.nlsystems.com (salmon.nlsystems.com [10.0.0.3]) by herring.nlsystems.com (8.9.3/8.8.8) with ESMTP id JAA05549; Tue, 28 Sep 1999 09:51:08 +0100 (BST) (envelope-from dfr@nlsystems.com) Date: Tue, 28 Sep 1999 09:51:08 +0100 (BST) From: Doug Rabson To: Wilko Bulte Cc: FreeBSD hackers list Subject: Re: 2.88Mb floppies In-Reply-To: <199909272039.WAA04128@yedi.iaf.nl> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 27 Sep 1999, Wilko Bulte wrote: > Hi there, > > Just having installed a 2.88Mb floppy drive in one of my axp boxes > I wonder if FreeBSD can do 2.88Mb floppy disks. From the looks > of the contents of /sys/i386/isa/fd.c: > > static struct fd_type fd_types[NUMTYPES] = > { > { 21,2,0xFF,0x04,82,3444,1,FDC_500KBPS,2,0x0C,2 }, /* 1.72M in HD 3.5in */ > { 18,2,0xFF,0x1B,82,2952,1,FDC_500KBPS,2,0x6C,1 }, /* 1.48M in HD 3.5in */ > { 18,2,0xFF,0x1B,80,2880,1,FDC_500KBPS,2,0x6C,1 }, /* 1.44M in HD 3.5in */ > > it appears it cannot. > > Is this true? Is there anything that stops one from adding an appropriate > line to this struct? And to dev/MAKEDEV of course? I have no idea whether that driver can cope with 2.88mb floppies to be honest. There is only one way to find out... -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Sep 28 5:46:11 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp01.wxs.nl (smtp01.wxs.nl [195.121.6.61]) by hub.freebsd.org (Postfix) with ESMTP id 34E0A14F73; Tue, 28 Sep 1999 05:46:07 -0700 (PDT) (envelope-from asmodai@wxs.nl) Received: from daemon.ninth-circle.org ([195.121.197.30]) by smtp01.wxs.nl (Netscape Messaging Server 3.61) with ESMTP id AAA21D; Tue, 28 Sep 1999 14:46:06 +0200 Received: (from asmodai@localhost) by daemon.ninth-circle.org (8.9.3/8.9.3) id OAA35308; Tue, 28 Sep 1999 14:46:51 +0200 (CEST) (envelope-from asmodai) Date: Tue, 28 Sep 1999 14:46:51 +0200 From: Jeroen Ruigrok/Asmodai To: hackers@freebsd.org, current@freebsd.org Subject: Call for projects Message-ID: <19990928144651.B35262@daemon.ninth-circle.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre3i Organisation: Ninth-Circle Enterprises Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Since no-one except Poul-Henning gave a start with this I thought I might try my hand at this. Given FreeBSD's rapid development over the last year a lot of things around the releases have changed. Nik Clayton and his team are doing a terrific job to keep up with the documentation. However, what has been lacking, at least in my opinion, is the lack of alerting less advanced, more time-restrained, however you wish to call it, hackers of tasks which need to be fixed in FreeBSD. The PR system is nice and works pretty well [thanks to a lot of people] but it is not what I meant with my above words. What I did mean though, is that when someone messes with source code at large in FreeBSD to let the hacker/developer-community know of these changes plus point out some areas which need to be fixed/looked-out with these patches in place. Small-term projects. Also, put out more patches on either -hackers or -current [depending on what platform the patches aim at] and call for more test reviews to eliminate more and more initial bugs upon introducing. Plus, let the doc guys know what changes have been made and in which places the docs should be altered. Doesn't take much, but remember that not every docperson is a kernel hacker and vice versa, so UTSL, how well intended doesn't always help in these cases. All of this is merely a call for clearer communication between the diverse efforts within the project as a whole and external hackers with no access to the repository but who wish to send-pr diffs/patches to fix up forgotten/neglected/overseen areas in the code. Thanking you all in advance for helping on this. It's together we make this project work... -- Jeroen Ruigrok van der Werven/Asmodai asmodai(at)wxs.nl The BSD Programmer's Documentation Project Network/Security Specialist BSD: Technical excellence at its best Any fool can make a rule And every fool will mind it. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Sep 28 6:42: 9 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from alpha.netvision.net.il (alpha.netvision.net.il [194.90.1.13]) by hub.freebsd.org (Postfix) with ESMTP id ED57814F5D; Tue, 28 Sep 1999 06:42:03 -0700 (PDT) (envelope-from danhil@cwnt.com) Received: from unspecified.host (RAS4-p71.hfa.netvision.net.il [62.0.146.199]) by alpha.netvision.net.il (8.9.3/8.8.6) with SMTP id PAA01377; Tue, 28 Sep 1999 15:42:01 +0200 (IST) Received: from 192.168.0.46 ([192.168.0.46]) by 192.168.0.1 (WinRoute 3.04g) with SMTP; Tue, 28 Sep 1999 15:40:23 +0200 Message-ID: <01ca01bf09bf$642e9080$2e00a8c0@nt46daniel> From: "Daniel Hilevich" To: Cc: Subject: The sppp driver Date: Tue, 28 Sep 1999 15:40:21 +0100 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_01C7_01BF09C7.C5ECB6F0" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2014.211 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2014.211 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a multi-part message in MIME format. ------=_NextPart_000_01C7_01BF09C7.C5ECB6F0 Content-Type: text/plain; charset="windows-1255" Content-Transfer-Encoding: quoted-printable I'm currently working on a driver that provides point to point = connection and I would like to use the sppp driver in order to get PPP = stack over it. I have few questions about the sppp driver: - As I understood from the code, the sppp driver prepends the ppp frame = over the given data to sppp_output and than calls if_start (which should = do the actual sending). The same goes with control messages in the = sppp_cp_send func. But, in the later case, the control messages are = queued to the control queue=20 (sp->pp_cpq) which the if_start functions doesn't have access to. Should = I implement the access? - How do you recommend connecting my ioctrl functions to the sppp ioctrl = function (I have to call the ioctrl function because, as I understood = it, this is the way to start the lcp messaging). I think the best way is = to do this in the sppp_attach function. - Is there any resource about using the sppp driver. The sppp man page = isn't satisfying at all. Thank you, -- Daniel Hilevich =20 mailto:danhil@cwnt.com Charlotte's Web Networks LTD. Tel: +972-4-9592203 ext. 214 =20 ------=_NextPart_000_01C7_01BF09C7.C5ECB6F0 Content-Type: text/html; charset="windows-1255" Content-Transfer-Encoding: quoted-printable
I'm currently working on a driver that=20 provides point to point connection and I would like to use the sppp = driver=20 in order to get PPP stack over it.
I have few questions about the sppp=20 driver:
 
 - As I understood from = the code,=20 the sppp driver prepends the ppp frame over the given data to = sppp_output and=20 than calls if_start (which should do the actual sending). The same goes=20 with control messages in the sppp_cp_send func. But, in the later = case, the=20 control messages are queued to the control queue
(sp->pp_cpq) which the = if_start=20 functions doesn't have access to. Should I implement the = access?
 
- How do you recommend connecting = my ioctrl=20 functions to the sppp ioctrl function (I have to call the ioctrl = function=20 because, as I understood it, this is the way to start the lcp = messaging). I=20 think the best way is to do this in the sppp_attach = function.
 
- Is there any resource = about using the=20 sppp driver. The sppp man page isn't satisfying at all.
 
Thank you,
--
Daniel Hilevich   =
mailto:danhil@cwnt.com
Charlotte's= Web=20 Networks LTD.
Tel: +972-4-9592203 ext. 214    =20
------=_NextPart_000_01C7_01BF09C7.C5ECB6F0-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Sep 28 7:58:48 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from nimitz.ca.sandia.gov (nimitz.ca.sandia.gov [146.246.243.56]) by hub.freebsd.org (Postfix) with ESMTP id 27D411550F; Tue, 28 Sep 1999 07:58:46 -0700 (PDT) (envelope-from bmah@nimitz.ca.sandia.gov) Received: (from bmah@localhost) by nimitz.ca.sandia.gov (8.9.3/8.9.3) id HAA07317; Tue, 28 Sep 1999 07:58:40 -0700 (PDT) Message-Id: <199909281458.HAA07317@nimitz.ca.sandia.gov> X-Mailer: exmh version 2.1.0 09/18/1999 To: "Andrew Reilly" Cc: Nik Clayton , freebsd-hackers@FreeBSD.ORG Subject: Re: A new package fetching utility, pkg_get In-Reply-To: Your message of "Tue, 28 Sep 1999 08:31:34 +1000." <19990928083134.A73274@gurney.reilly.home> From: bmah@CA.Sandia.GOV (Bruce A. Mah) Reply-To: bmah@CA.Sandia.GOV X-Face: g~c`.{#4q0"(V*b#g[i~rXgm*w;:nMfz%_RZLma)UgGN&=j`5vXoU^@n5v4:OO)c["!w)nD/!!~e4Sj7LiT'6*wZ83454H""lb{CC%T37O!!'S$S&D}sem7I[A 2V%N&+ X-Url: http://www.ca.sandia.gov/~bmah/ Mime-Version: 1.0 Content-Type: multipart/signed; boundary="==_Exmh_-83037056P"; micalg=pgp-sha1; protocol="application/pgp-signature" Content-Transfer-Encoding: 7bit Date: Tue, 28 Sep 1999 07:58:40 -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --==_Exmh_-83037056P Content-Type: text/plain; charset=us-ascii If memory serves me right, "Andrew Reilly" wrote: > On Mon, Sep 27, 1999 at 08:09:13AM +0100, Nik Clayton wrote: > > On Mon, Sep 27, 1999 at 10:22:34AM +1000, Andrew Reilly wrote: > > > What I'd like is a little weekly crontab script that runs after > > > my weekly ports cvsup, and tells me which of the ports that I > > > "subscribe to" has changed, so that I can think about rebuilding it. > > > > ports/sysutils/pkg_version. > > > > Then apply the patches at > > > > http://www.freebsd.org/~nik/pkg_version.diff > > pkg_version.1.diff > > > > and use the -c flag. > > This is lovely. And it re-inforces one of my pet theories: if > you want a program badly enough that you're prepared to write > it, someone else almost certainly has... FYI: I've kind of dropped the ball on further revisions to pkg_version, mostly since it does what I need it to do right now, there are other people whose Perl hacking skills far surpass mine, and I suffer from the same chronic lack of time that most people around here have. However... pkg_version is supposed to go into -STABLE once billf gets some time to import it, and then hopefully it'll be easier for people to add bugfixes and functionality (i.e. whomever reads PRs will probably be more responsive than I've been). Cheers, Bruce. (instigator of pkg_version) --==_Exmh_-83037056P Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: PGPfreeware 5.0i for non-commercial use MessageID: QUjsogox/L6BEmWDnWlDLRfKtfxseeWP iQA/AwUBN/DXoNjKMXFboFLDEQKmhgCgvkociq00kizwxPYqlzj50b8uwu4AnR8g nU/trvZPcON+UJjVakMLYPAM =/BFx -----END PGP SIGNATURE----- --==_Exmh_-83037056P-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Sep 28 8:16: 7 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from phoenix.calderasystems.com (phoenix.calderasystems.com [207.179.18.7]) by hub.freebsd.org (Postfix) with ESMTP id AFDCD15567 for ; Tue, 28 Sep 1999 08:16:03 -0700 (PDT) (envelope-from drdavis@calderasystems.com) Received: from calderasystems.com (drdavis@buddha.calderasystems.com [207.179.18.42]) by phoenix.calderasystems.com (8.8.7/8.8.7) with ESMTP id JAA23455; Tue, 28 Sep 1999 09:15:53 -0600 Message-ID: <37F0DC3D.7F4A969D@calderasystems.com> Date: Tue, 28 Sep 1999 09:18:21 -0600 From: "Darren R. Davis" X-Mailer: Mozilla 4.61C-CCK-MCD Caldera Systems OpenLinux [en] (X11; I; Linux 2.2.10 i686) X-Accept-Language: en MIME-Version: 1.0 To: Nate Williams Cc: Scm486@aol.com, freebsd-hackers@FreeBSD.ORG Subject: Re: Netscape Bus Error References: <49064d67.252125e1@aol.com> <199909272010.OAA12060@mt.sri.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Nate Williams wrote: > > Does anyone know what "Bus Error" means from Netscape? > > It means that the program has a bug in it that caused it to write/read > from memory that it invalid. > > This can happen is you try to read from free'd memory, or write to NULL > pointers, etc..... > > It can also happen if a program assumes a routine uses a particular > implementation, and that implementation changes w/out an API change (say > a shared library update), the program may be doing something 'illegal' > that once worked. > > In short, it's a netscape bug.... > > Nate > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message I believe that a Bus Error is specifically referencing miss aligned data vs segmentation violation (SIGSEGV) which is accessing data that is either free'd or not yours, etc. I always thought it strange on an Intel processor, since this was more a 68K/RISC thing. The only penalty on Intel was taking many more cycles to complete. Of course I haven't looked that deeply at what the code handling for the bus error signal really detects. But, never the less, it is still a Netscape bug. Darren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Sep 28 8:30:29 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from penelope.skunk.org (penelope.skunk.org [208.133.204.51]) by hub.freebsd.org (Postfix) with ESMTP id 2C21D14D52 for ; Tue, 28 Sep 1999 08:30:26 -0700 (PDT) (envelope-from ben@penelope.skunk.org) Received: from localhost (ben@localhost) by penelope.skunk.org (8.9.3/8.9.3) with ESMTP id LAA45292; Tue, 28 Sep 1999 11:34:15 -0400 (EDT) Date: Tue, 28 Sep 1999 11:34:15 -0400 (EDT) From: Ben Rosengart To: Wes Peters Cc: hackers@FreeBSD.ORG Subject: Re: A new package fetching utility, pkg_get In-Reply-To: <37F02000.654DDFEA@softweyr.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 27 Sep 1999, Wes Peters wrote: > Ben Rosengart wrote: > > > > Well, I for one would like a command that fetches a package without > > installing it. I don't see any option to pkg_add for that. > > See fetch(1). ;^) > > (Sorry, catching up after a weekend of the flu.) But pkg_add knows where to find the packages, and fetch doesn't. -- Ben Rosengart UNIX Systems Engineer, Skunk Group StarMedia Network, Inc. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Sep 28 8:57:24 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from dingo.cdrom.com (castles556.castles.com [208.214.165.120]) by hub.freebsd.org (Postfix) with ESMTP id 54F6515732 for ; Tue, 28 Sep 1999 08:56:39 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.3/8.8.8) with ESMTP id IAA00787; Tue, 28 Sep 1999 08:49:23 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199909281549.IAA00787@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Brian Reichert Cc: freebsd-hackers@freebsd.org Subject: Re: 3.3-R on Dell w/ DPT RAID In-reply-to: Your message of "Mon, 27 Sep 1999 12:53:57 EDT." <19990927125356.A23727@numachi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 28 Sep 1999 08:49:22 -0700 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Sun, Sep 26, 1999 at 06:16:09PM -0700, Mike Smith wrote: > > > We've told this machine via it's BIOS to pretend it only has 256M. > > > > > > When we try an install from the floppies, the mfsroot floppies > > > panics with an 'pmap_enter: invalid page directory, pdir=0x601063, > > > va=0xc2400000'. > > > > > > I have no idea what this error message means. > > > > It suggests that you have memory problems; have you tried physically > > extracting most of the memory from the system? > > No; I instead used the BIOS's mechanism for artifically restricting > available memory. (I had in fact also tried removing all but 512M > from the machine, but to no avail.) The reason I asked about physically removing memory is simply that we've seen a lot of problems with systems that fail due to being electrically overloaded with large memory configurations. -- \\ The mind's the standard \\ Mike Smith \\ of the man. \\ msmith@freebsd.org \\ -- Joseph Merrick \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Sep 28 9: 0:55 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mailhub.psn.ie (mailhub.psn.ie [194.106.150.254]) by hub.freebsd.org (Postfix) with ESMTP id 4C85414F4C for ; Tue, 28 Sep 1999 09:00:46 -0700 (PDT) (envelope-from cillian@psn.ie) Received: from alto.internal ([192.168.0.254]) by mailhub.psn.ie with esmtp (Exim 2.12 #3) id 11VzLK-0001OS-00 for hackers@freebsd.org; Tue, 28 Sep 1999 16:39:02 +0100 Received: from cillian (helo=localhost) by alto.internal with local-esmtp (Exim 2.12 #1) id 11VzLK-0005PK-00 for hackers@freebsd.org; Tue, 28 Sep 1999 16:39:02 +0100 Date: Tue, 28 Sep 1999 16:39:01 +0100 (IST) From: Cillian Sharkey X-Sender: cillian@alto.internal To: hackers@freebsd.org Subject: NFS & /usr/ports Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, When doing a make world upgrade, one can do the compiling on one machine, and then NFS mount /usr/src and /usr/obj from it onto the other machines to do the upgrade, however when doing the same with /usr/ports, it doesn't work quite as well. For example, once you have installed a port on the master machine, you can't do a 'make install' again, unless you delete the file "work/.install_done" for the port in question. Any suggestions ? Cillian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Sep 28 9:28:34 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from lorax.ubergeeks.com (lorax.ubergeeks.com [209.145.74.241]) by hub.freebsd.org (Postfix) with ESMTP id 1181215559 for ; Tue, 28 Sep 1999 09:28:28 -0700 (PDT) (envelope-from adrian@ubergeeks.com) Received: from localhost (adrian@localhost) by lorax.ubergeeks.com (8.8.8/8.8.8) with SMTP id MAA04508; Tue, 28 Sep 1999 12:27:50 -0400 (EDT) (envelope-from adrian@ubergeeks.com) Date: Tue, 28 Sep 1999 12:27:49 -0400 (EDT) From: Adrian Filipi-Martin Reply-To: Adrian Filipi-Martin To: Poul-Henning Kamp Cc: Alexander Bezroutchko , FreeBSD Hackers List Subject: Re: about jail In-Reply-To: <11744.938266471@critter.freebsd.dk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 25 Sep 1999, Poul-Henning Kamp wrote: > In message <19990925171712.A80535@zenon.net>, Alexander Bezroutchko writes: > > >* scheduling > > Scheduler must provide equal time quantum to each jail. I think > > something like "fair share scheduler" required. Is there any plans > > to implement such scheme in FreeBSD ? > > Not from me. Check out: "Retrofitting Quality of Service into a Time-Sharing Operating System" John Bruno, Jos Brustoloni, Eran Gabber, Banu zden, and Abraham Silberschatz, Lucent Technologies--Bell Laboratories This was an interesting paper from the 99 USENIX Technical Conference that seems applicable. I don't know if the sources have been made available, but alot of the hierarchical stuff is very similar to H. Zhang's QoS networking work and that _is_ available under CMU's license. Adrian -- [ adrian@ubergeeks.com -- Ubergeeks Consulting -- http://www.ubergeeks.com/ ] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Sep 28 9:30:39 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from pawn.primelocation.net (pawn.primelocation.net [205.161.238.235]) by hub.freebsd.org (Postfix) with ESMTP id 8DC9C15775 for ; Tue, 28 Sep 1999 09:30:30 -0700 (PDT) (envelope-from cdf.lists@fxp.org) Received: by pawn.primelocation.net (Postfix, from userid 1016) id EBFA2F81C; Tue, 28 Sep 1999 12:30:29 -0400 (EDT) Received: from localhost (localhost [127.0.0.1]) by pawn.primelocation.net (Postfix) with ESMTP id E29269B09; Tue, 28 Sep 1999 12:30:29 -0400 (EDT) Date: Tue, 28 Sep 1999 12:30:29 -0400 (EDT) From: "Chris D. Faulhaber" X-Sender: cdf.lists@pawn.primelocation.net To: Cillian Sharkey Cc: hackers@freebsd.org Subject: Re: NFS & /usr/ports In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 28 Sep 1999, Cillian Sharkey wrote: > Hi, > > When doing a make world upgrade, one can do the compiling on one machine, > and then NFS mount /usr/src and /usr/obj from it onto the other machines > to do the upgrade, however when doing the same with /usr/ports, it doesn't > work quite as well. For example, once you have installed a port on the > master machine, you can't do a 'make install' again, unless you delete the > file "work/.install_done" for the port in question. > > Any suggestions ? > Try 'make reinstall' ----- Chris D. Faulhaber | All the true gurus I've met never System/Network Administrator, | claimed they were one, and always Reality Check Information, Inc. | pointed to someone better. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Sep 28 9:45:19 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from relay.ucb.crimea.ua (relay.ucb.crimea.ua [212.110.138.1]) by hub.freebsd.org (Postfix) with ESMTP id C79CF1558A for ; Tue, 28 Sep 1999 09:42:23 -0700 (PDT) (envelope-from ru@ucb.crimea.ua) Received: (from ru@localhost) by relay.ucb.crimea.ua (8.9.3/8.9.3/UCB) id TAA53060; Tue, 28 Sep 1999 19:23:57 +0300 (EEST) (envelope-from ru) Date: Tue, 28 Sep 1999 19:23:57 +0300 From: Ruslan Ermilov To: Cillian Sharkey Cc: hackers@FreeBSD.ORG Subject: Re: NFS & /usr/ports Message-ID: <19990928192357.A51819@relay.ucb.crimea.ua> Mail-Followup-To: Cillian Sharkey , hackers@FreeBSD.ORG References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.3i In-Reply-To: ; from Cillian Sharkey on Tue, Sep 28, 1999 at 04:39:01PM +0100 X-Operating-System: FreeBSD 3.2-STABLE i386 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Sep 28, 1999 at 04:39:01PM +0100, Cillian Sharkey wrote: > Hi, > > When doing a make world upgrade, one can do the compiling on one machine, > and then NFS mount /usr/src and /usr/obj from it onto the other machines > to do the upgrade, however when doing the same with /usr/ports, it doesn't > work quite as well. For example, once you have installed a port on the > master machine, you can't do a 'make install' again, unless you delete the > file "work/.install_done" for the port in question. > > Any suggestions ? > Use `make reinstall'. -- Ruslan Ermilov Sysadmin and DBA of the ru@ucb.crimea.ua United Commercial Bank, ru@FreeBSD.org FreeBSD committer, +380.652.247.647 Simferopol, Ukraine http://www.FreeBSD.org The Power To Serve http://www.oracle.com Enabling The Information Age To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Sep 28 9:56:21 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from acl.lanl.gov (acl.lanl.gov [128.165.147.1]) by hub.freebsd.org (Postfix) with ESMTP id 96282157B1 for ; Tue, 28 Sep 1999 09:56:19 -0700 (PDT) (envelope-from rminnich@lanl.gov) Received: from localhost (rminnich@localhost) by acl.lanl.gov (8.8.8/8.8.5) with ESMTP id KAA186499 for ; Tue, 28 Sep 1999 10:56:19 -0600 (MDT) X-Authentication-Warning: acl.lanl.gov: rminnich owned process doing -bs Date: Tue, 28 Sep 1999 10:56:18 -0600 From: "Ronald G. Minnich" To: freebsd-hackers@FreeBSD.ORG Subject: Re: Netscape Bus Error In-Reply-To: <37F0DC3D.7F4A969D@calderasystems.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 28 Sep 1999, Darren R. Davis wrote: > Nate Williams wrote: > I believe that a Bus Error is specifically referencing miss aligned data vs > segmentation violation > (SIGSEGV) which is accessing data that is either free'd or not yours, etc. > I always thought > it strange on an Intel processor, since this was more a 68K/RISC thing. Original meaning, from the original machine: Bus error: you got a literal bus error when doing a read or write operation on the I/O bus. Usually a bus timeout, i.e. you referenced an address on the bus (well, Unibus back then) and nothing came back in the timeout period. Nowadays it includes the bus timeout type of thing (which has a different name on PCI, but same meaning) as well as other things: for example on SGIs you can get a bus error signal when you use bad pointer alignment. Segv: you referenced memory for which you had no mapping. usually a reference through 0, but also lots of other fun stuff, like trashed return addresses on the stack. Funny but true: in the early days freebsd had the meaning of these reversed, as did most of the bsds descended from 386bsd. This got fixed in openbsd first. I don't know if/when freebsd followed suit. Does anyone out there? I haven't checked lately ... ron To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Sep 28 10: 1:48 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from xenet.harz.de. (xenet.harz.de [193.159.181.111]) by hub.freebsd.org (Postfix) with ESMTP id 366461553A for ; Tue, 28 Sep 1999 10:01:16 -0700 (PDT) (envelope-from Meyser@xenet.de) Received: (from matthias@localhost) by xenet.harz.de. (8.9.3/8.9.3) id TAA25676 for freebsd-hackers@freebsd.org; Tue, 28 Sep 1999 19:01:10 +0200 (CEST) (envelope-from matthias) Date: Tue, 28 Sep 1999 19:01:10 +0200 From: Matthias Meyser To: freebsd-hackers@freebsd.org Subject: Re: NFS & /usr/ports Message-ID: <19990928190110.A25648@server.intern> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.6i In-Reply-To: ; from Cillian Sharkey on Tue, Sep 28, 1999 at 04:39:01PM +0100 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi On Tue, Sep 28, 1999 at 04:39:01PM +0100, Cillian Sharkey wrote: > When doing a make world upgrade, one can do the compiling on one machine, > and then NFS mount /usr/src and /usr/obj from it onto the other machines > to do the upgrade, however when doing the same with /usr/ports, it doesn't > work quite as well. For example, once you have installed a port on the > master machine, you can't do a 'make install' again, unless you delete the > file "work/.install_done" for the port in question. Do a mkdir /usr/ports/packages then use "make package" to compile & install a port you can then mount /usr/ports/packages on another machine to install ports. -- \\ // N N EEE TTT Matthias Meyser, Meyser@harz.de \\ // eee NN N E T Gesellschaft fuer Informations- und \X/ e e N N N EE T Kommunikationssysteme mbH // \\ e ee N NN E T 38678 Clausthal-Zellerfeld, Burgstaetter Strasse 6 // \\ eeee N N EEE T Telefon: +49-5323-94018 Fax: +49-5323-94011 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Sep 28 11:13:46 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id ABEB314CBE for ; Tue, 28 Sep 1999 11:13:44 -0700 (PDT) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.3/8.9.3) with ESMTP id LAA11181; Tue, 28 Sep 1999 11:13:43 -0700 (PDT) (envelope-from jdp@polstra.com) From: John Polstra Received: (from jdp@localhost) by vashon.polstra.com (8.9.3/8.9.1) id LAA12154; Tue, 28 Sep 1999 11:13:42 -0700 (PDT) (envelope-from jdp@polstra.com) Date: Tue, 28 Sep 1999 11:13:42 -0700 (PDT) Message-Id: <199909281813.LAA12154@vashon.polstra.com> To: drdavis@calderasystems.com Subject: Re: Netscape Bus Error In-Reply-To: <37F0DC3D.7F4A969D@calderasystems.com> References: <49064d67.252125e1@aol.com> <199909272010.OAA12060@mt.sri.com> <37F0DC3D.7F4A969D@calderasystems.com> Organization: Polstra & Co., Seattle, WA Cc: hackers@freebsd.org Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <37F0DC3D.7F4A969D@calderasystems.com>, Darren R. Davis wrote: > I believe that a Bus Error is specifically referencing miss aligned > data vs segmentation violation (SIGSEGV) which is accessing data > that is either free'd or not yours, etc. That was the traditional distinction, but it's different on FreeBSD/i386. SIGSEGV means you accessed memory that is unmapped. SIGBUS means you accessed memory that is mapped, but protected (unwritable and/or unreadable). To further confuse matters, FreeBSD/alpha generates SIGSEGV for both cases. John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "No matter how cynical I get, I just can't keep up." -- Nora Ephron To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Sep 28 11:16: 3 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.numachi.com (numachi.numachi.com [198.175.254.2]) by hub.freebsd.org (Postfix) with SMTP id 301E71574A for ; Tue, 28 Sep 1999 11:15:57 -0700 (PDT) (envelope-from reichert@numachi.com) Received: (qmail 2246 invoked by uid 1001); 28 Sep 1999 18:15:55 -0000 Date: Tue, 28 Sep 1999 14:15:55 -0400 From: Brian Reichert To: Mike Smith Cc: Brian Reichert , freebsd-hackers@freebsd.org Subject: Re: 3.3-R on Dell w/ DPT RAID Message-ID: <19990928141555.A2197@numachi.com> References: <19990927125356.A23727@numachi.com> <199909281549.IAA00787@dingo.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95i In-Reply-To: <199909281549.IAA00787@dingo.cdrom.com>; from Mike Smith on Tue, Sep 28, 1999 at 08:49:22AM -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Sep 28, 1999 at 08:49:22AM -0700, Mike Smith wrote: > > On Sun, Sep 26, 1999 at 06:16:09PM -0700, Mike Smith wrote: > > > > We've told this machine via it's BIOS to pretend it only has 256M. > > > > > > > > When we try an install from the floppies, the mfsroot floppies > > > > panics with an 'pmap_enter: invalid page directory, pdir=0x601063, > > > > va=0xc2400000'. > > > > > > > > I have no idea what this error message means. At this point, I can report full success in getting FreeBSD 3.3-R installed on this machine, with the full @g of physical memory. It would seem that the issue was a bad install lfoppty, but I don't see how, as both disks' compressed kernels were able to boot, uncompress the kernels, and start loading. _That_ was when the the icky trap was happening. Were the boot floppy images updated during the last couple of weeks? -- Brian 'you Bastard' Reichert reichert@numachi.com 37 Crystal Ave. #303 Daytime number: (781) 899-7484 x704 Derry NH 03038-1713 USA Intel architecture: the left-hand path To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Sep 28 11:49: 5 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from proxy2.ba.best.com (proxy2.ba.best.com [206.184.139.14]) by hub.freebsd.org (Postfix) with ESMTP id D8F5214EBB for ; Tue, 28 Sep 1999 11:49:02 -0700 (PDT) (envelope-from shepard@MetaThink.COM) Received: from MetaThink.COM (dynamic59.pm02.mv.best.com [209.24.240.123]) by proxy2.ba.best.com (8.9.3/8.9.2/best.out) with ESMTP id LAA13839; Tue, 28 Sep 1999 11:42:01 -0700 (PDT) Received: (from shepard@localhost) by MetaThink.COM (8.9.2/8.8.7) id LAA41568; Tue, 28 Sep 1999 11:41:51 -0700 (PDT) (envelope-from shepard) Date: Tue, 28 Sep 1999 11:41:45 -0700 From: Mark Shepard To: Patryk Zadarnowski Cc: Christian Carstensen , Chris Costello , freebsd-hackers@FreeBSD.ORG Subject: Re: updating packages automatically... Message-ID: <19990928114145.A41493@ed209.home> Reply-To: mns@MetaThink.COM Mail-Followup-To: Patryk Zadarnowski , Christian Carstensen , Chris Costello , freebsd-hackers@FreeBSD.ORG References: <199909260056.KAA10829@mycenae.ilion.eu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.3i In-Reply-To: <199909260056.KAA10829@mycenae.ilion.eu.org>; from Patryk Zadarnowski on Sun, Sep 26, 1999 at 10:56:31AM +1000 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Patryk Zadarnowski said: > > On Sat, 25 Sep 1999, Chris Costello wrote: > > > > > Aah! No! I tried that with GNOME once and it drove me insane > > > for about two weeks. > > > > > > Auto-upgrades on ports would be _very_ _very_ bad, especially > > > for those using apache from ports! > > > > that's right. i thought about having some kind of exclude list for ports > > that shall never be upgraded automatically. anyway, the script will just > > generate a shell script output. it should not replace packages without > > manual intervention. > > If most FreeBSD users are like me, you should set up an include list > instead. Then, it could actually be sort of useful. Most people would > use it to auto-upgrade packages for beta and other unstable software. > > However, I think that an /etc/periodic/weekly script that reports on > which packages are outdated in the weekly report would be a much more > welcome utility ;) I also don't think I would actually use an auto-upgrade feature, or at best I'd only use it on a very few ports (can't think of any at the moment). The biggest problem I see would be coordinating the update with any currently executing instances of the old port -- could cause unexpected crashes because a config file format or shared library has changed, for instance. I _like_ the idea of a email-summary of "What's New in the World of Ports". Some suggestions: - Automatic (background) downloading of distfiles for updated packages, so that when I see the "What's New" email and feel "in the mood" for some sysadmin, I don't have to wait to download the distfiles. Everything I need is already at hand, so I can just "make install." I save time, and possibly bandwidth charges also (assuming downloads happen at night). This should fetch the primary distfile and all updated dependency distfiles. It should check for free disk space, and also allow a include/exclude list since it's really the big ports (like gnome-*) where the download/thumb twiddling time becomes a significant part of the "install" time. - Since I'm wishing :-) In the What's New email, I'd like to see a paragraph summary of what's changed for each port I have installed. Ideally (and unrealistically), all software authors would put this info in a standard format for each release... More pragmatically, the port maintainer could update the information (downside is this requires scarce human labor AND changing human habits, but perhaps a compromise would be to define a standard for conveying this info and let the port maintainers choose to do so or not... for instance, in each port, in addition to pkg/DESCR and pkg/COMMENTS, there could be a pkg/WHATSNEW file which would summarize features/bugs new in the _current_ version of the port... a port maintainer could simply copy the announcement email into this file). As a last resort, the pkg_version tool could apply a heuristic of looking for common files like ChangeLog or README in the newly downloaded distfile, extracting said file(s) and diff'ing against the same files from the previous version of the port. This "What's Changed" summary would be very useful for me -- without this, I don't know if it's worthwhile to upgrade and I expect many users of FBSD, as opposed to hackers (who I expect track the latest version of everything), would feel as I do. If it ain't broken, I don't want to waste time "fixing" it :-) Finally, one other feature I've been thinking of (shouldn't necessarily be part of the above): - Before I do a "make install", is there some way to find out exactly which dependencies of the port I'm installing are also going to need to be upgraded? Ideally, "make install -n" would show this, but the output is cluttered with shell-commands... Basically, I'd like some simple way to estimate the work actually required in upgrading a port before I start the "make install" process. It doesn't have to be exact... (for instance, upgrading pgp requires knowing how USA_RESIDENT will be defined.) This lets me better estimate if I can upgrade _now_, or if I need to put it off 'til I have more time. Of course, if such a feature was available, it would make sense to include this info for each port in the automatically-generated "What's New" email. Mark Shepard mns@metathink.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Sep 28 12:11:41 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from phobos.illtel.denver.co.us (dsl-206.169.4.82.wenet.com [206.169.4.82]) by hub.freebsd.org (Postfix) with ESMTP id 8A32F14F9D for ; Tue, 28 Sep 1999 12:11:38 -0700 (PDT) (envelope-from abelits@phobos.illtel.denver.co.us) Received: from localhost (abelits@localhost) by phobos.illtel.denver.co.us (8.9.1a/8.6.9) with SMTP id MAA18477; Tue, 28 Sep 1999 12:10:49 -0700 Date: Tue, 28 Sep 1999 12:10:49 -0700 (PDT) From: Alex Belits To: "Darren R. Davis" Cc: Nate Williams , Scm486@aol.com, freebsd-hackers@FreeBSD.ORG Subject: Re: Netscape Bus Error In-Reply-To: <37F0DC3D.7F4A969D@calderasystems.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 28 Sep 1999, Darren R. Davis wrote: > I believe that a Bus Error is specifically referencing miss aligned data vs > segmentation violation > (SIGSEGV) which is accessing data that is either free'd or not yours, etc. > I always thought > it strange on an Intel processor, since this was more a 68K/RISC thing. > The only penalty on Intel > was taking many more cycles to complete. Of course I haven't looked that > deeply at what the > code handling for the bus error signal really detects. But, never the > less, it is still a Netscape bug. It's SIGSEGV in disguise -- netscape intercepts it and generates SIGBUS: ---8<--- abelits@es1840$ netscape& [1] 67114 abelits@es1840$ kill -SEGV 67114 abelits@es1840$ [1]+ Bus error netscape abelits@es1840$ --->8--- -- Alex ---------------------------------------------------------------------- Excellent.. now give users the option to cut your hair you hippie! -- Anonymous Coward To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Sep 28 14:19:54 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from pauling.research.devcon.net (pauling.research.devcon.net [212.15.193.194]) by hub.freebsd.org (Postfix) with ESMTP id 2502515800 for ; Tue, 28 Sep 1999 14:19:47 -0700 (PDT) (envelope-from cc@devcon.net) Received: from localhost (cc@localhost) by pauling.research.devcon.net (8.9.3/8.9.2) with ESMTP id XAA08667; Tue, 28 Sep 1999 23:19:43 +0200 (CEST) (envelope-from cc@devcon.net) Date: Tue, 28 Sep 1999 23:19:43 +0200 (CEST) From: Christian Carstensen X-Sender: cc@pauling.research.devcon.net To: freebsd-hackers@freebsd.org Cc: mns@metathink.com Subject: updating packages automatically, etc.pp. Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG so far, so good, first of all, thanks for giving me this much input on my idea. i've had a look at the pkg_version tool, which, with Nik Clayton's patch, does more or less what i've been thinking of, when i decided to post the initial message to this list. as Mark Shepard discussed in detail, there are a lot of useful features, pkg_version is still lacking. (mark, special thanks to you for taking down these useful notes!) i'm interested in implementing at least some of this functionality using perl, if enough of you regard this as a useful tool for system admin. otherwise, i'll put it on the stack of things to do, when nothing else has to done ;) how do you think about it? -- christian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Sep 28 15:24:49 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from uni4nn.gn.iaf.nl (osmium.gn.iaf.nl [193.67.144.12]) by hub.freebsd.org (Postfix) with ESMTP id 7DDFE14F1A for ; Tue, 28 Sep 1999 15:24:39 -0700 (PDT) (envelope-from wilko@yedi.iaf.nl) Received: from yedi.iaf.nl (uucp@localhost) by uni4nn.gn.iaf.nl (8.9.2/8.9.2) with UUCP id AAA31781; Wed, 29 Sep 1999 00:12:29 +0200 (MET DST) Received: (from wilko@localhost) by yedi.iaf.nl (8.9.3/8.9.3) id XAA97702; Tue, 28 Sep 1999 23:56:04 +0200 (CEST) (envelope-from wilko) From: Wilko Bulte Message-Id: <199909282156.XAA97702@yedi.iaf.nl> Subject: Re: 2.88Mb floppies In-Reply-To: from Doug Rabson at "Sep 28, 1999 9:51: 8 am" To: dfr@nlsystems.com (Doug Rabson) Date: Tue, 28 Sep 1999 23:56:04 +0200 (CEST) Cc: FreeBSD-hackers@FreeBSD.ORG X-Organisation: Private FreeBSD site - Arnhem, The Netherlands X-pgp-info: PGP public key at 'finger wilko@freefall.freebsd.org' X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG As Doug Rabson wrote ... > On Mon, 27 Sep 1999, Wilko Bulte wrote: > > > Hi there, > > > > Just having installed a 2.88Mb floppy drive in one of my axp boxes > > I wonder if FreeBSD can do 2.88Mb floppy disks. From the looks > > of the contents of /sys/i386/isa/fd.c: > > > > static struct fd_type fd_types[NUMTYPES] = > > { > > { 21,2,0xFF,0x04,82,3444,1,FDC_500KBPS,2,0x0C,2 }, /* 1.72M in HD 3.5in */ > > { 18,2,0xFF,0x1B,82,2952,1,FDC_500KBPS,2,0x6C,1 }, /* 1.48M in HD 3.5in */ > > { 18,2,0xFF,0x1B,80,2880,1,FDC_500KBPS,2,0x6C,1 }, /* 1.44M in HD 3.5in */ > > > > it appears it cannot. > > > > Is this true? Is there anything that stops one from adding an appropriate > > line to this struct? And to dev/MAKEDEV of course? > > I have no idea whether that driver can cope with 2.88mb floppies to be > honest. There is only one way to find out... Right. I'll give it a try asap. Somebody sent me a sample entry to add to fd_type. But I want to do a bit of study on the fd source to see if I can understand what all the fields mean. Wilko -- | / o / / _ Arnhem, The Netherlands - Powered by FreeBSD - |/|/ / / /( (_) Bulte WWW : http://www.tcja.nl http://www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Sep 28 16:48:11 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id D286F14E04; Tue, 28 Sep 1999 16:48:08 -0700 (PDT) (envelope-from jkh@zippy.cdrom.com) Received: from localhost (localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id QAA25162; Tue, 28 Sep 1999 16:47:26 -0700 (PDT) (envelope-from jkh@zippy.cdrom.com) To: Adrian Penisoara Cc: Mark Powell , freebsd-stable@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG Subject: Re: -stable (in)stability (was Re: Best version of FBSD for INN ?) In-reply-to: Your message of "Sat, 25 Sep 1999 18:58:41 +0300." Date: Tue, 28 Sep 1999 16:47:26 -0700 Message-ID: <25158.938562446@localhost> From: "Jordan K. Hubbard" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'd suggest trying a 3.3-stable snapshot, just as soon as I can get those rolling off of releng3.freebsd.org again. If it still occurs, we're now at least debugging the latest and greatest. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Sep 28 20:40:57 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from resnet.uoregon.edu (resnet.uoregon.edu [128.223.144.32]) by hub.freebsd.org (Postfix) with ESMTP id 39C06154DA for ; Tue, 28 Sep 1999 20:40:52 -0700 (PDT) (envelope-from dwhite@resnet.uoregon.edu) Received: from localhost (dwhite@localhost) by resnet.uoregon.edu (8.9.3/8.9.3) with ESMTP id UAA91933; Tue, 28 Sep 1999 20:40:50 -0700 (PDT) (envelope-from dwhite@resnet.uoregon.edu) Date: Tue, 28 Sep 1999 20:40:50 -0700 (PDT) From: Doug White To: Mark Shepard Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: updating packages automatically... In-Reply-To: <19990928114145.A41493@ed209.home> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 28 Sep 1999, Mark Shepard wrote: > I _like_ the idea of a email-summary of "What's New in the World of Ports". We used to have this. I think it morphed into the webpage mutation we have now (note you can request all the changed ports in the last X time frame). Maybe it's posted to the -ports mailing list? > - Before I do a "make install", is there some way to > find out exactly which dependencies of the port I'm installing are also > going to need to be upgraded? I think a 'make checkdep' type target to run the dependency check w/o actually building them would be a plus. This should be very easy to do w/ the current bsd.port.mk frame. Doug White Internet: dwhite@resnet.uoregon.edu | FreeBSD: The Power to Serve http://gladstone.uoregon.edu/~dwhite | www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Sep 28 21: 5:45 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from norn.ca.eu.org (cr965240-b.abtsfd1.bc.wave.home.com [24.113.19.137]) by hub.freebsd.org (Postfix) with ESMTP id DF88714F87 for ; Tue, 28 Sep 1999 21:05:32 -0700 (PDT) (envelope-from cpiazza@norn.ca.eu.org) Received: by norn.ca.eu.org (Postfix, from userid 1002) id D02DF65; Tue, 28 Sep 1999 21:05:31 -0700 (PDT) Date: Tue, 28 Sep 1999 21:05:31 -0700 From: Chris Piazza To: Doug White Cc: Mark Shepard , freebsd-hackers@FreeBSD.ORG Subject: Re: updating packages automatically... Message-ID: <19990928210531.A734@norn.ca.eu.org> References: <19990928114145.A41493@ed209.home> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre1i In-Reply-To: X-Operating-System: FreeBSD 4.0-CURRENT Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Sep 28, 1999 at 08:40:50PM -0700, Doug White wrote: > On Tue, 28 Sep 1999, Mark Shepard wrote: > > > I _like_ the idea of a email-summary of "What's New in the World of Ports". > > We used to have this. I think it morphed into the webpage mutation we > have now (note you can request all the changed ports in the last X time > frame). > > Maybe it's posted to the -ports mailing list? http://docs.freebsd.org/cgi/getmsg.cgi?fetch=580888+0+archive/1999/freebsd-ports/19990919.freebsd-ports > > > - Before I do a "make install", is there some way to > > find out exactly which dependencies of the port I'm installing are also > > going to need to be upgraded? > > I think a 'make checkdep' type target to run the dependency check w/o > actually building them would be a plus. This should be very easy to do w/ > the current bsd.port.mk frame. make package-depends might be what you're looking for. -Chris -- :Chris Piazza : Abbotsford, BC: :cpiazza@home.net : cpiazza@FreeBSD.org: : : : To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Sep 28 21:46:19 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from picnic.mat.net (picnic.mat.net [206.246.122.133]) by hub.freebsd.org (Postfix) with ESMTP id 2001514D28 for ; Tue, 28 Sep 1999 21:44:53 -0700 (PDT) (envelope-from chuckr@mat.net) Received: from localhost (localhost [127.0.0.1]) by picnic.mat.net (8.9.3/8.9.3) with ESMTP id AAA65100 for ; Wed, 29 Sep 1999 00:45:14 -0400 (EDT) (envelope-from chuckr@mat.net) Date: Wed, 29 Sep 1999 00:45:13 -0400 (EDT) From: Chuck Robey To: FreeBSD Hackers List Subject: Midi info Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've been researching music, and since I found what I consider to be a *great* midi intro document (pdf file) I thought I'd stick it up for everyone else, at http://www.freebsd.org/~chuckr/cs-an27.pdf It's an application note by Crystal Semiconductor, but it's written quite generally, and covers just about anything you'd want to know about midi (that 24 pages allows). If you care about midi but haven't ever learned enough to figure it all out, here's where to go. ---------------------------------------------------------------------------- Chuck Robey | Interests include C programming, Electronics, 213 Lakeside Dr. Apt. T-1 | communications, and signal processing. Greenbelt, MD 20770 | I run picnic.mat.net: FreeBSD-current(i386) and (301) 220-2114 | jaunt.mat.net : FreeBSD-current(Alpha) ---------------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Sep 29 0: 9:35 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from rnocserv.urc.ac.ru (rnocserv.urc.ac.ru [193.233.85.2]) by hub.freebsd.org (Postfix) with ESMTP id CE86A14E6B for ; Wed, 29 Sep 1999 00:07:19 -0700 (PDT) (envelope-from joy@urc.ac.ru) Received: from urc.ac.ru (y.urc.ac.ru [193.233.85.7]) by rnocserv.urc.ac.ru (8.9.3/8.9.3) with ESMTP id NAA69775; Wed, 29 Sep 1999 13:01:33 +0600 (ESS) (envelope-from joy@urc.ac.ru) Message-ID: <37F1B94D.7B215AF4@urc.ac.ru> Date: Wed, 29 Sep 1999 13:01:33 +0600 From: Konstantin Chuguev Organization: Southern Ural Regional Center of FREEnet X-Mailer: Mozilla 4.6 [en] (X11; I; FreeBSD 3.3-STABLE i386) X-Accept-Language: ru, en MIME-Version: 1.0 To: Alex Belits Cc: "Darren R. Davis" , Nate Williams , Scm486@aol.com, freebsd-hackers@FreeBSD.ORG Subject: Re: Netscape Bus Error References: Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Alex Belits wrote: > On Tue, 28 Sep 1999, Darren R. Davis wrote: > > > I believe that a Bus Error is specifically referencing miss aligned data vs > > segmentation violation > > (SIGSEGV) which is accessing data that is either free'd or not yours, etc. > > I always thought > > it strange on an Intel processor, since this was more a 68K/RISC thing. > > The only penalty on Intel > > was taking many more cycles to complete. Of course I haven't looked that > > deeply at what the > > code handling for the bus error signal really detects. But, never the > > less, it is still a Netscape bug. > > It's SIGSEGV in disguise -- netscape intercepts it and generates SIGBUS: > ---8<--- > abelits@es1840$ netscape& > [1] 67114 > abelits@es1840$ kill -SEGV 67114 > abelits@es1840$ [1]+ Bus error netscape > > abelits@es1840$ > --->8--- > Or Netscape crashes with SIGBUS in SIGSEGV handler? :-) -- Konstantin V. Chuguev. System administrator of Southern http://www.urc.ac.ru/~joy/ Ural Regional Center of FREEnet, mailto:joy@urc.ac.ru Chelyabinsk, Russia. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Sep 29 0:33:55 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from dt014n8c.san.rr.com (dt011n66.san.rr.com [204.210.13.102]) by hub.freebsd.org (Postfix) with ESMTP id 744DE14D1A for ; Wed, 29 Sep 1999 00:33:38 -0700 (PDT) (envelope-from Doug@gorean.org) Received: from gorean.org (master [10.0.0.2]) by dt014n8c.san.rr.com (8.9.3/8.8.8) with ESMTP id AAA27106; Wed, 29 Sep 1999 00:33:35 -0700 (PDT) (envelope-from Doug@gorean.org) Message-ID: <37F1C0CF.756F7B54@gorean.org> Date: Wed, 29 Sep 1999 00:33:35 -0700 From: Doug Organization: Triborough Bridge & Tunnel Authority X-Mailer: Mozilla 4.61 [en] (X11; U; FreeBSD 4.0-CURRENT-0927 i386) X-Accept-Language: en MIME-Version: 1.0 To: Takanori Watanabe , freebsd-hackers@freebsd.org Subject: Re: mrtg,FreeBSD, asus p2b temperature References: <199909270629.IAA24988@dorifer.heim3.tu-clausthal.de> <199909270706.QAA05840@shidahara1.planet.sci.kobe-u.ac.jp> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Takanori Watanabe wrote: > >Not necessary. The mainboards of the ASUS P2B series have > >everything onboard that you need. We have it working with > >the intpm0 driver and a tool called "lm" that I donwloaded > >from somewhere in Japan (forgot the URL, sorry). > > Call me?;-) > If you mention lm.c, it is available from > http://www.planet.sci.kobe-u.ac.jp/~takawata/smbus/examples/ Ok, first of all this is VERY cool! Thank you. You have no idea how long I have wanted exactly this. One question. Is it necessary to open the smb device read/write? I would like to be able to open it read only so that non-root users can start lmmon without needing to change the privs on /dev/smb0, but having read your warnings about the delicacy of the smb device I didn't want to just go changing things willy-nilly. As far as I can see nothing is ever written to it. Doug -- "Stop it, I'm gettin' misty." - Mel Gibson as Porter, "Payback" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Sep 29 0:35:56 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from phobos.illtel.denver.co.us (dsl-206.169.4.82.wenet.com [206.169.4.82]) by hub.freebsd.org (Postfix) with ESMTP id 204D115090 for ; Wed, 29 Sep 1999 00:35:48 -0700 (PDT) (envelope-from abelits@phobos.illtel.denver.co.us) Received: from localhost (abelits@localhost) by phobos.illtel.denver.co.us (8.9.1a/8.6.9) with SMTP id AAA21135; Wed, 29 Sep 1999 00:27:52 -0700 Date: Wed, 29 Sep 1999 00:27:52 -0700 (PDT) From: Alex Belits To: Konstantin Chuguev Cc: "Darren R. Davis" , Nate Williams , Scm486@aol.com, freebsd-hackers@FreeBSD.ORG Subject: Re: Netscape Bus Error In-Reply-To: <37F1B94D.7B215AF4@urc.ac.ru> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 29 Sep 1999, Konstantin Chuguev wrote: > Or Netscape crashes with SIGBUS in SIGSEGV handler? :-) This is what I mean "in disguise" -- however SIGBUS seems to be intentional. strace output on Linux (21116 is netscape's pid): ---8<--- oldselect(9, [8], NULL, NULL, {1, 0}) = ? ERESTARTNOHAND (To be restarted) --- SIGSEGV (Segmentation fault) --- getpid() = 21116 kill(21116, SIGBUS) = 0 --- SIGBUS (Bus error) --- --->8--- -- Alex ---------------------------------------------------------------------- Excellent.. now give users the option to cut your hair you hippie! -- Anonymous Coward To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Sep 29 0:51:12 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from dt014n8c.san.rr.com (dt011n66.san.rr.com [204.210.13.102]) by hub.freebsd.org (Postfix) with ESMTP id 0AD2F14BFD for ; Wed, 29 Sep 1999 00:50:23 -0700 (PDT) (envelope-from Doug@gorean.org) Received: from gorean.org (master [10.0.0.2]) by dt014n8c.san.rr.com (8.9.3/8.8.8) with ESMTP id AAA27425; Wed, 29 Sep 1999 00:50:20 -0700 (PDT) (envelope-from Doug@gorean.org) Message-ID: <37F1C4BC.981970D3@gorean.org> Date: Wed, 29 Sep 1999 00:50:20 -0700 From: Doug Organization: Triborough Bridge & Tunnel Authority X-Mailer: Mozilla 4.61 [en] (X11; U; FreeBSD 4.0-CURRENT-0927 i386) X-Accept-Language: en MIME-Version: 1.0 To: Takanori Watanabe , freebsd-hackers@freebsd.org Subject: Re: mrtg,FreeBSD, asus p2b temperature References: <199909270629.IAA24988@dorifer.heim3.tu-clausthal.de> <199909270706.QAA05840@shidahara1.planet.sci.kobe-u.ac.jp> <37F1C0CF.756F7B54@gorean.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Doug wrote: > > Takanori Watanabe wrote: > > > >Not necessary. The mainboards of the ASUS P2B series have > > >everything onboard that you need. We have it working with > > >the intpm0 driver and a tool called "lm" that I donwloaded > > >from somewhere in Japan (forgot the URL, sorry). > > > > Call me?;-) > > If you mention lm.c, it is available from > > http://www.planet.sci.kobe-u.ac.jp/~takawata/smbus/examples/ > > Ok, first of all this is VERY cool! Thank you. You have no idea how > long I have wanted exactly this. One question. Is it necessary to open > the smb device read/write? You know, I really shouldn't ask questions when I'm this tired. Of course it dawned on me that in all likelihood you are writing when you use ioctl. Sorry to trouble you. *Yawn* Doug To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Sep 29 0:56:48 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from herring.nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (Postfix) with ESMTP id 8C53F15192 for ; Wed, 29 Sep 1999 00:56:16 -0700 (PDT) (envelope-from dfr@nlsystems.com) Received: from salmon.nlsystems.com (salmon.nlsystems.com [10.0.0.3]) by herring.nlsystems.com (8.9.3/8.8.8) with ESMTP id IAA23437; Wed, 29 Sep 1999 08:59:23 +0100 (BST) (envelope-from dfr@nlsystems.com) Date: Wed, 29 Sep 1999 08:59:23 +0100 (BST) From: Doug Rabson To: John Polstra Cc: drdavis@calderasystems.com, hackers@freebsd.org Subject: Re: Netscape Bus Error In-Reply-To: <199909281813.LAA12154@vashon.polstra.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 28 Sep 1999, John Polstra wrote: > In article <37F0DC3D.7F4A969D@calderasystems.com>, > Darren R. Davis wrote: > > > I believe that a Bus Error is specifically referencing miss aligned > > data vs segmentation violation (SIGSEGV) which is accessing data > > that is either free'd or not yours, etc. > > That was the traditional distinction, but it's different on > FreeBSD/i386. SIGSEGV means you accessed memory that is unmapped. > SIGBUS means you accessed memory that is mapped, but protected > (unwritable and/or unreadable). To further confuse matters, > FreeBSD/alpha generates SIGSEGV for both cases. And it generates SIGBUS for unaligned accesses (when traps for that are enabled). -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Sep 29 1:17:21 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from ady.warpnet.ro (ady.warpnet.ro [194.102.224.1]) by hub.freebsd.org (Postfix) with ESMTP id 9759E15064; Wed, 29 Sep 1999 01:17:04 -0700 (PDT) (envelope-from ady@warpnet.ro) Received: from localhost (ady@localhost) by ady.warpnet.ro (8.9.3/8.9.3) with ESMTP id LAA02497; Wed, 29 Sep 1999 11:16:37 +0300 (EEST) (envelope-from ady@warpnet.ro) Date: Wed, 29 Sep 1999 11:16:36 +0300 (EEST) From: Adrian Penisoara To: "Jordan K. Hubbard" Cc: freebsd-stable@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG Subject: Re: -stable (in)stability (was Re: Best version of FBSD for INN ?) In-Reply-To: <25158.938562446@localhost> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, On Tue, 28 Sep 1999, Jordan K. Hubbard wrote: > I'd suggest trying a 3.3-stable snapshot, just as soon as I can > get those rolling off of releng3.freebsd.org again. If it still > occurs, we're now at least debugging the latest and greatest. Isn't -STABLE tracking OK ? Unfortunately I don't think I can afford reinstalling a new release (this is a production server). Do you think the installation got somehow trashed during these succesive updates (with 'make [build|install]world') ? I've been thinking about remote attacks too (there are no user shells), could this be a cause ? BTW, this morning my co-workers caught another freeze; luckily I left a top running on a VTY; they told me that the majority of the processes were in the "idle" STATE -- strange, I haven't seen this in top until now. Could this be a hint ? > > - Jordan > Thanks, Ady (@warpnet.ro) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Sep 29 5:25: 9 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from caxton.correionet.com.br (caxton.correionet.com.br [200.246.35.7]) by hub.freebsd.org (Postfix) with ESMTP id 1E0CF14FCF for ; Wed, 29 Sep 1999 05:24:32 -0700 (PDT) (envelope-from morte@correionet.com.br) Received: from caxton.correionet.com.br (caxton.correionet.com.br [200.246.35.7]) by caxton.correionet.com.br (8.9.3/8.9.3) with ESMTP id JAA61864; Wed, 29 Sep 1999 09:24:04 -0300 (EST) Date: Wed, 29 Sep 1999 09:24:04 -0300 (EST) From: Luiz Morte da Costa Junior To: Mark Newton Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: SMP motherboards In-Reply-To: <199909220327.MAA44119@gizmo.internode.com.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG What is your disk? I have a Intel L440GX and I had performance problem using a Seagate ST39140LW. Look the dmesg command: da1: Fixed Direct Access SCSI-2 device da1: 40.000MB/s transfers (20.000MHz, offset 15, 16bit), Tagged Queueing Enabled da1: 8683MB (17783240 512 byte sectors: 255H 63S/T 1106C) I changed to quantum and my problem is solved. Look the dmesg command: da0 at ahc0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-2 device da0: 80.000MB/s transfers (40.000MHz, offset 31, 16bit), Tagged Queueing Enabled da0: 8683MB (17783250 512 byte sectors: 255H 63S/T 1106C) []s, Luiz Morte da Costa Junior Analista de Redes E-mail: morte@correionet.com.br Telefone: +55 19 754-2532 Fax: +55 19 255-7576 CorreioNet - Correio Popular Campinas - SP - Brazil On Wed, 22 Sep 1999, Mark Newton wrote: > > Has anyone had any problems running FreeBSD-SMP on Intel GX-chipset > motherboards? > > Conversely, does anyone have any recommendations for other motherboards > to buy? > > - mark > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Sep 29 5:29: 9 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from laurasia.com.au (lauras.lnk.telstra.net [139.130.93.142]) by hub.freebsd.org (Postfix) with ESMTP id 0928F14FCF for ; Wed, 29 Sep 1999 05:29:04 -0700 (PDT) (envelope-from mike@laurasia.com.au) Received: (from mike@localhost) by laurasia.com.au (8.9.3/8.9.3) id UAA92505 for freebsd-hackers@freebsd.org; Wed, 29 Sep 1999 20:29:03 +0800 (WST) (envelope-from mike) From: Michael Kennett Message-Id: <199909291229.UAA92505@laurasia.com.au> Subject: Passing descriptors over local domain sockets To: freebsd-hackers@freebsd.org Date: Wed, 29 Sep 1999 20:29:03 +0800 (WST) X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello All, I have a program that passes descriptors over local domain sockets. It works fantastically on FreeBSD, but I've got to port the program over to Linux (sigh). Unfortunately, the program doesn't work on Linux -- is this because of problems with the Linux implementation of passing file descriptors? If anyone has I'd really appreciate any feedback on this! I've also noticed that the linux 'struct sockaddr_in' doesn't include the field 'sin_len' -- indeed, it appears that the (BSD) character fields 'sin_len' and 'sin_family' have been merged into the linux 'u_short sin_ family' field. What is the proper way of handling this incompatibility? Regards, Mike Kennett (mike@laurasia.com.au) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Sep 29 6:22:57 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from beelzebubba.sysabend.org (beelzebubba.sysabend.org [209.201.74.6]) by hub.freebsd.org (Postfix) with ESMTP id AB06414CE9 for ; Wed, 29 Sep 1999 06:22:41 -0700 (PDT) (envelope-from ragnar@sysabend.org) Received: by beelzebubba.sysabend.org (Postfix, from userid 1004) id 4E285428D; Wed, 29 Sep 1999 09:22:42 -0400 (EDT) Received: from localhost (localhost [127.0.0.1]) by beelzebubba.sysabend.org (Postfix) with SMTP id 384D79C7C; Wed, 29 Sep 1999 09:22:42 -0400 (EDT) Date: Wed, 29 Sep 1999 09:22:42 -0400 (EDT) From: Jamie Bowden To: Chris Costello Cc: Nate Williams , Wes Peters , "Jordan K. Hubbard" , Jaakko Salomaa , "Daniel C. Sobral" , hackers@FreeBSD.ORG Subject: Re: A new package fetching utility, pkg_get In-Reply-To: <19990925231532.F76486@holly.calldei.com> Message-ID: Approved: yep X-representing: Only myself. X-badge: We don't need no stinking badges. X-obligatory-profanity: Fuck X-moo: Moo. MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 25 Sep 1999, Chris Costello wrote: :On Fri, Sep 24, 1999, Nate Williams wrote: :> Unfortunately, as with all 'slick' products we've talked about, it still :> requires a working X setup in order to run. You could do one as a CUI, :> but doing it in Java would be just as hard as anything else at this :> point. :( : : There's nothing keeping it from being a port or being an :optional part of a distribution that can be installed if X is :installed (emphasis on ``optional''). : : We've got what we need behind-the-scenes, now we need to put a :good show on stage. Let's show Linux what package management is :all about. :) I know I'm not the only Irix admin on this list. If you really want to see a tight clean package management system, with CLI and GUI interfaces, look at inst/swmgr in Irix. Jamie Bowden -- If we've got to fight over grep, sign me up. But boggle can go. -Ted Faber (on Hasbro's request for removal of /usr/games/boggle) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Sep 29 7:53:58 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from alpha.netvision.net.il (alpha.netvision.net.il [194.90.1.13]) by hub.freebsd.org (Postfix) with ESMTP id 8A5C61529C; Wed, 29 Sep 1999 07:53:48 -0700 (PDT) (envelope-from danhil@cwnt.com) Received: from unspecified.host (RAS4-p71.hfa.netvision.net.il [62.0.146.199]) by alpha.netvision.net.il (8.9.3/8.8.6) with SMTP id QAA31333; Wed, 29 Sep 1999 16:53:44 +0200 (IST) Received: from 192.168.0.46 ([192.168.0.46]) by 192.168.0.1 (WinRoute 3.04g) with SMTP; Wed, 29 Sep 1999 16:52:01 +0200 Message-ID: <033a01bf0a92$8fe1b4e0$2e00a8c0@nt46daniel> From: "Daniel Hilevich" To: , Subject: A bug in the sppp driver? Date: Wed, 29 Sep 1999 16:51:58 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="windows-1255" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2014.211 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2014.211 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG While trying to use the sppp, I came across this situation and I think it's a bug: When you trying to establish connection from one peer (local) to another (remote), you sent a CONF_REQ message to the remote peer. The remote peer should answer with a CONF_ACK message. In the code of the sppp driver (net/if_spppsubr.c, lines 1321 - 1357) you can see that the remote peer send's a CONF_ACK message to the local peer (in the line: rv = (cp->RCR)(sp, h, len);) but doesn't change it state to STATE_ACK_SENT (as I think it should do) . Further more, you can see that after a few lines, there are these strange lines: case STATE_ACK_SENT: case STATE_REQ_SENT: sppp_cp_change_state(cp, sp, rv? STATE_ACK_SENT: STATE_REQ_SENT); break; Question: if you are in the STATE_ACK_SENT why change the state to the same one according to the value of rv? As I understand, the state should be changed according to the value of rv, but it should be done right after the call to cp->RCR. The it is implemented now, the state won't be changed. (I have a lot of problems with this driver and any help will be appreciative) Thank you, -- Daniel Hilevich mailto:danhil@cwnt.com Charlotte's Web Networks LTD. Tel: +972-4-9592203 ext. 214 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Sep 29 8: 9:47 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from plains.NoDak.edu (plains.NoDak.edu [134.129.111.64]) by hub.freebsd.org (Postfix) with ESMTP id 7297314DB4; Wed, 29 Sep 1999 08:09:42 -0700 (PDT) (envelope-from tinguely@plains.NoDak.edu) Received: (from tinguely@localhost) by plains.NoDak.edu (8.9.3/8.9.3) id KAA14058; Wed, 29 Sep 1999 10:09:40 -0500 (CDT) Date: Wed, 29 Sep 1999 10:09:40 -0500 (CDT) From: Mark Tinguely Message-Id: <199909291509.KAA14058@plains.NoDak.edu> To: danhil@cwnt.com, phk@FreeBSD.ORG Subject: Re: The sppp driver Cc: hackers@FreeBSD.ORG Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG (deletes and edits) > But, in the later case, the control messages are queued to > the control queue (sp->pp_cpq) which the if_start functions > doesn't have access to. in the ISDN (sys/i4b/driver) code, the interface target of the if_start(), there is a call to sppp_dequeue() which gets the top packet, by first searching the control, then the priority and finally the normal queues (the last two queue are checked only if the PPP is in the NCP mode). > - How do you recommend connecting my ioctrl functions to the sppp ioctrl > function (I have to call the ioctrl function because, as I understood > it, this is the way to start the lcp messaging). I think the best way is > to do this in the sppp_attach function. I am confused here. by default the LCP is started when the physical IDSN link is started sppp_lcp_up(). This changes to the Open state. If you are using the manual mode, then you need to follow the man page and specify when you want the PPP to start the LCP. ------- The best way to learn sppp is to get a copy of RFC 1661, understand it and then follow how that maps into sppp code (aka, RTFS). The sppp is more efficient than ppp and pppd because it does not have to map the packets from kernel space to user space and then back again, plus the advatages not having to service interrupts on each character, the synchronous link does not need to map Asynchronous-Control-Character-Map characters and Frame Check Sums. IMHO, Joerg Wunsch should be commended for the work of adding the RFC 1661 support. For this reason, I would suggest starting with the FreeBSD-3.2 or FreeBSD-3.3 (which has one minor state correction) version of sppp. sppp would make an excellent starting point for any PPP over permanent packet oriented connection medium such as DSL over ATM, ATM, possibly Ethernet or UDP. --mark. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Sep 29 8:10:34 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from etinc.com (et-gw.etinc.com [207.252.1.2]) by hub.freebsd.org (Postfix) with ESMTP id AB46514D62; Wed, 29 Sep 1999 08:10:30 -0700 (PDT) (envelope-from dennis@etinc.com) Received: from dbsys (dbsys.etinc.com [207.252.1.18]) by etinc.com (8.9.3/8.9.3) with SMTP id LAA07913; Wed, 29 Sep 1999 11:07:09 -0400 (EDT) Message-Id: <199909291507.LAA07913@etinc.com> X-Sender: dennis@etinc.com X-Mailer: QUALCOMM Windows Eudora Pro Version 4.0 Date: Wed, 29 Sep 1999 10:05:16 -0400 To: "Daniel Hilevich" , , From: Dennis Subject: Re: A bug in the sppp driver? In-Reply-To: <033a01bf0a92$8fe1b4e0$2e00a8c0@nt46daniel> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 04:51 PM 9/29/99 +0100, Daniel Hilevich wrote: >While trying to use the sppp, I came across this situation and I think it's >a bug: >When you trying to establish connection from one peer (local) to another >(remote), you sent a CONF_REQ message to the remote peer. The remote peer >should answer with a CONF_ACK message. In the code of the sppp driver >(net/if_spppsubr.c, lines 1321 - 1357) you can see that the remote peer >send's a CONF_ACK message to the local peer >(in the line: rv = (cp->RCR)(sp, h, len);) but doesn't change it state to >STATE_ACK_SENT (as I think it should do) . Further more, you can see that >after a few lines, there are these strange lines: > case STATE_ACK_SENT: > case STATE_REQ_SENT: > sppp_cp_change_state(cp, sp, rv? > STATE_ACK_SENT: STATE_REQ_SENT); > break; > >Question: if you are in the STATE_ACK_SENT why change the state to the same >one according to the value of rv? > >As I understand, the state should be changed according to the value of rv, >but it should be done right after the call to cp->RCR. The it is implemented >now, the state won't be changed. the state is dependent on what state you are in, given the event. Have you verified that you are in ack_sent? doing state machines with switch statements is a big mess. Dennis To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Sep 29 8:25:50 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from alpha.netvision.net.il (alpha.netvision.net.il [194.90.1.13]) by hub.freebsd.org (Postfix) with ESMTP id C23AF14DBB; Wed, 29 Sep 1999 08:25:28 -0700 (PDT) (envelope-from danhil@cwnt.com) Received: from unspecified.host (RAS4-p71.hfa.netvision.net.il [62.0.146.199]) by alpha.netvision.net.il (8.9.3/8.8.6) with SMTP id RAA02864; Wed, 29 Sep 1999 17:25:18 +0200 (IST) Received: from 192.168.0.46 ([192.168.0.46]) by 192.168.0.1 (WinRoute 3.04g) with SMTP; Wed, 29 Sep 1999 17:25:18 +0200 Message-ID: <038d01bf0a97$3652f8d0$2e00a8c0@nt46daniel> From: "Daniel Hilevich" To: "Dennis" Cc: , References: <199909291507.LAA07913@etinc.com> Subject: Re: A bug in the sppp driver? Date: Wed, 29 Sep 1999 17:25:15 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2014.211 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2014.211 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG As I understand from rfc1661, the state, which the remote machine should be after sending a CONF_ACK message, is ack_send. The sppp driver doesn't work properly and I think that this is on of the reasons. ----- Original Message ----- From: Dennis To: Daniel Hilevich ; ; Sent: Wednesday, September 29, 1999 3:05 PM Subject: Re: A bug in the sppp driver? > At 04:51 PM 9/29/99 +0100, Daniel Hilevich wrote: > >While trying to use the sppp, I came across this situation and I think it's > >a bug: > >When you trying to establish connection from one peer (local) to another > >(remote), you sent a CONF_REQ message to the remote peer. The remote peer > >should answer with a CONF_ACK message. In the code of the sppp driver > >(net/if_spppsubr.c, lines 1321 - 1357) you can see that the remote peer > >send's a CONF_ACK message to the local peer > >(in the line: rv = (cp->RCR)(sp, h, len);) but doesn't change it state to > >STATE_ACK_SENT (as I think it should do) . Further more, you can see that > >after a few lines, there are these strange lines: > > case STATE_ACK_SENT: > > case STATE_REQ_SENT: > > sppp_cp_change_state(cp, sp, rv? > > STATE_ACK_SENT: STATE_REQ_SENT); > > break; > > > >Question: if you are in the STATE_ACK_SENT why change the state to the same > >one according to the value of rv? > > > >As I understand, the state should be changed according to the value of rv, > >but it should be done right after the call to cp->RCR. The it is implemented > >now, the state won't be changed. > > the state is dependent on what state you are in, given the event. Have you > verified that you are in ack_sent? > > doing state machines with switch statements is a big mess. > > Dennis > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Sep 29 8:34: 7 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from bingnet2.cc.binghamton.edu (bingnet2.cc.binghamton.edu [128.226.1.18]) by hub.freebsd.org (Postfix) with ESMTP id C6A6C15128 for ; Wed, 29 Sep 1999 08:33:56 -0700 (PDT) (envelope-from zzhang@cs.binghamton.edu) Received: from sol.cs.binghamton.edu (cs1-gw.cs.binghamton.edu [128.226.171.72]) by bingnet2.cc.binghamton.edu (8.9.3/8.9.3) with SMTP id LAA25982; Wed, 29 Sep 1999 11:33:39 -0400 (EDT) Date: Wed, 29 Sep 1999 11:19:21 -0400 (EDT) From: Zhihui Zhang To: Michael Kennett Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Passing descriptors over local domain sockets In-Reply-To: <199909291229.UAA92505@laurasia.com.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 29 Sep 1999, Michael Kennett wrote: > Hello All, > > I have a program that passes descriptors over local domain sockets. > It works fantastically on FreeBSD, but I've got to port the program over > to Linux (sigh). Unfortunately, the program doesn't work on Linux -- is > this because of problems with the Linux implementation of passing file > descriptors? > > If anyone has I'd really appreciate any feedback on this! > > I've also noticed that the linux 'struct sockaddr_in' doesn't include the > field 'sin_len' -- indeed, it appears that the (BSD) character fields > 'sin_len' and 'sin_family' have been merged into the linux 'u_short sin_ > family' field. What is the proper way of handling this incompatibility? > I could be wrong. But the socket layer code of FreeBSD is different from that of Linux. Even if Linux has something called socket, that is only the interface. The internal mechanims can be different. -Zhihui To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Sep 29 9:23:23 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from trooper.velocet.ca (trooper.velocet.net [216.126.82.226]) by hub.freebsd.org (Postfix) with ESMTP id E9C2D15599 for ; Wed, 29 Sep 1999 09:23:10 -0700 (PDT) (envelope-from dgilbert@trooper.velocet.ca) Received: (from dgilbert@localhost) by trooper.velocet.ca (8.9.3/8.9.3) id MAA20187; Wed, 29 Sep 1999 12:23:09 -0400 (EDT) (envelope-from dgilbert) From: David Gilbert MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14322.15597.505566.676863@trooper.velocet.ca> Date: Wed, 29 Sep 1999 12:23:09 -0400 (EDT) To: freebsd-hackers@freebsd.org Subject: PPPoE offer. X-Mailer: VM 6.71 under 20.4 "Emerald" XEmacs Lucid Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've got some real $$$ available to encourage someone to make PPPoE work efficiently enough on the FreeBSD platform to handle a substantial number of users. Is anyone interested? Dave. -- ============================================================================ |David Gilbert, Velocet Communications. | Two things can only be | |Mail: dgilbert@velocet.net | equal if and only if they | |http://www.velocet.net/~dgilbert | are precisely opposite. | =========================================================GLO================ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Sep 29 9:27:43 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from isbalham.ist.co.uk (isbalham.ist.co.uk [192.31.26.1]) by hub.freebsd.org (Postfix) with ESMTP id 1536514D9E; Wed, 29 Sep 1999 09:25:58 -0700 (PDT) (envelope-from rb@gid.co.uk) Received: from gid.co.uk (uucp@localhost) by isbalham.ist.co.uk (8.9.2/8.8.7) with UUCP id RAA29223; Wed, 29 Sep 1999 17:09:14 +0100 (BST) (envelope-from rb@gid.co.uk) Received: from [194.32.164.2] by seagoon.gid.co.uk; Wed, 29 Sep 1999 16:58:37 +0100 (BST) X-Sender: rb@194.32.164.1 Message-Id: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Wed, 29 Sep 1999 16:58:34 +0000 To: current@freebsd.org, hackers@freebsd.org From: Bob Bishop Subject: my repository is broken (more) Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I wrote: > ===> usr.sbin/lpr/filters.ru > ===> usr.sbin/lpr/filters.ru/koi2alt > make: don't know how to make koi2alt.c. Stop > >Apparently because... > > ache 1999/09/22 19:54:45 PDT > > Removed files: > usr.sbin/lpr/filters.ru koi2alt.c > Log: > moved to koi2alt > >...never made it here. What's the easiest way to get back in step? TIA I now suspect that cvsup.uk.freebsd.org isn't up-to-date. Anyone know anything? -- Bob Bishop (0118) 977 4017 international code +44 118 rb@gid.co.uk fax (0118) 989 4254 between 0800 and 1800 UK To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Sep 29 9:42:26 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from nomis.simon-shapiro.org (nomis.simon-shapiro.org [209.86.126.163]) by hub.freebsd.org (Postfix) with SMTP id 5F7E61557E for ; Wed, 29 Sep 1999 09:42:17 -0700 (PDT) (envelope-from shimon@simon-shapiro.org) Received: (qmail 10850 invoked from network); 29 Sep 1999 16:42:12 -0000 Received: from localhost.simon-shapiro.org (HELO simon-shapiro.org) (127.0.0.1) by localhost.simon-shapiro.org with SMTP; 29 Sep 1999 16:42:12 -0000 Message-ID: <37F24164.F344FFD9@simon-shapiro.org> Date: Wed, 29 Sep 1999 12:42:12 -0400 From: Simon Shapiro as Himself Organization: Simon's Garage X-Mailer: Mozilla 4.6 [en] (X11; I; FreeBSD 3.3-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: hackers@FreeBSD.ORG Subject: Apology Content-Type: multipart/signed; protocol="application/x-pkcs7-signature"; micalg=sha1; boundary="------------ms1BA66C6B6C082D32B80AA800" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a cryptographically signed message in MIME format. --------------ms1BA66C6B6C082D32B80AA800 Content-Type: text/plain; charset= Content-Transfer-Encoding: 7bit I sincerely apologize to all the super patient people who depended on me for the delivery of an i2o subsystem and a DPT Generation V support with it. People, I stood you up and I am sorry for it. Excuse: I have been rather sick and my hands full with other health issues in my family. Since my last progress report I was in the hospital one more time for a Thyroid surgery. A tumor the size of my fist was removed and a nasty scar left in its place. In addition, two of my daughters (Sara and Noelle) had surgery too (we are a knify type of a family here :-). In addition, I switched jobs at work and started a highly prioritized and complex project. It sucked up any free cycles I had. Much of the project will be released under BSD type license and many of you will be rather pleased with it. Future: I would still like, very much, to complete this project. I actually got some time from work to spend on finishing the driver. This is what I am doing now. IF anyone can and is willing to help me with coding and testing, please let me know. Things are a bit early for just ``PnP'', as the code is not in any shape to actually boot with, etc. Status: * I moved the code from RELENG2_2 to RELENG_3; The big urgency in 2.2 was solved by Mark (from DPT) and I think the 3 branch is more viable for most of us. It compiles cleanly. * I am setting up a test machine (Lost 2 of them when I had to return to my previous boss the Alphas I was using). Will be done in about two hours. * Last I visited the code it was doing all the initialization correctly and also doing READ operations from raw disks without a hitch. * I am still in the dark a bit IRT to disklabel & Co. Mike Smith patched some code in for me (thanx again!) but it still panics the system. I could use some help again. * Much of the PCI code has changed from 2.2 (as if you did not know that :-) but I will find out today how it does. * The IOCTL for the dptmgr still has to be worked in. I have the code from DPT, so it is just a matter of getting to do it. Again, sorry for the endless delays and another promise to try and finish this project. -- Sincerely Yours, Shimon@Simon-Shapiro.ORG 404.644.6401 Simon Shapiro Unwritten code has no bugs and executes at twice the speed of mouth --------------ms1BA66C6B6C082D32B80AA800 Content-Type: application/x-pkcs7-signature; name="smime.p7s" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="smime.p7s" Content-Description: S/MIME Cryptographic Signature MIIJ7QYJKoZIhvcNAQcCoIIJ3jCCCdoCAQExCzAJBgUrDgMCGgUAMAsGCSqGSIb3DQEHAaCC B+8wggS5MIIEIqADAgECAhAClV7YnhihCwqregXjjrdfMA0GCSqGSIb3DQEBBAUAMIHMMRcw FQYDVQQKEw5WZXJpU2lnbiwgSW5jLjEfMB0GA1UECxMWVmVyaVNpZ24gVHJ1c3QgTmV0d29y azFGMEQGA1UECxM9d3d3LnZlcmlzaWduLmNvbS9yZXBvc2l0b3J5L1JQQSBJbmNvcnAuIEJ5 IFJlZi4sTElBQi5MVEQoYyk5ODFIMEYGA1UEAxM/VmVyaVNpZ24gQ2xhc3MgMSBDQSBJbmRp dmlkdWFsIFN1YnNjcmliZXItUGVyc29uYSBOb3QgVmFsaWRhdGVkMB4XDTk5MDkyNjAwMDAw MFoXDTAwMDkyNTIzNTk1OVowggEYMRcwFQYDVQQKEw5WZXJpU2lnbiwgSW5jLjEfMB0GA1UE CxMWVmVyaVNpZ24gVHJ1c3QgTmV0d29yazFGMEQGA1UECxM9d3d3LnZlcmlzaWduLmNvbS9y ZXBvc2l0b3J5L1JQQSBJbmNvcnAuIGJ5IFJlZi4sTElBQi5MVEQoYyk5ODEeMBwGA1UECxMV UGVyc29uYSBOb3QgVmFsaWRhdGVkMTMwMQYDVQQLEypEaWdpdGFsIElEIENsYXNzIDEgLSBO ZXRzY2FwZSBGdWxsIFNlcnZpY2UxFjAUBgNVBAMUDVNpbW9uIFNoYXBpcm8xJzAlBgkqhkiG 9w0BCQEWGHNoaW1vbkBzaW1vbi1zaGFwaXJvLm9yZzBcMA0GCSqGSIb3DQEBAQUAA0sAMEgC QQCWapJrHdDp0fdP9CDHrTEk6VbRBTk+X3UtU97HWiZooLH/Yp3//NmneAUOsjRj4kHygf3n LNqmQE040B3QdNQzAgMBAAGjggGPMIIBizAJBgNVHRMEAjAAMIGsBgNVHSAEgaQwgaEwgZ4G C2CGSAGG+EUBBwEBMIGOMCgGCCsGAQUFBwIBFhxodHRwczovL3d3dy52ZXJpc2lnbi5jb20v Q1BTMGIGCCsGAQUFBwICMFYwFRYOVmVyaVNpZ24sIEluYy4wAwIBARo9VmVyaVNpZ24ncyBD UFMgaW5jb3JwLiBieSByZWZlcmVuY2UgbGlhYi4gbHRkLiAoYyk5NyBWZXJpU2lnbjARBglg hkgBhvhCAQEEBAMCB4AwgYYGCmCGSAGG+EUBBgMEeBZ2ZDQ2NTJiZDYzZjIwNDcwMjkyOTg3 NjNjOWQyZjI3NTA2OWM3MzU5YmVkMWIwNTlkYTc1YmM0YmM5NzAxNzQ3ZGE1ZDNmMjE0MWJl YWRiMmJkMmU4OTIxNWFkNmFmNGQ1MTE0ODllYTJiMjQ3ZmRmM2VhNDUwYzAzBgNVHR8ELDAq MCigJqAkhiJodHRwOi8vY3JsLnZlcmlzaWduLmNvbS9jbGFzczEuY3JsMA0GCSqGSIb3DQEB BAUAA4GBAJGOv032Cr1u64/mnEHi0uKZb6uS4GQbed8jzBVRs+Y7zruO4R/gnXBEH0OrvE4Z oTqZ00gjnbVCT/rpjARmswNOU+hFI/kcn+HyKS0fw1A9Ppfm8Mp9iHSkYgTRT/MOuC2ck7z5 POETXZ68J14y368tXGd+Ako2n3RNHqOuSmXUMIIDLjCCApegAwIBAgIRANJ2Lo0UDD19sqgl Xa/uDXUwDQYJKoZIhvcNAQECBQAwXzELMAkGA1UEBhMCVVMxFzAVBgNVBAoTDlZlcmlTaWdu LCBJbmMuMTcwNQYDVQQLEy5DbGFzcyAxIFB1YmxpYyBQcmltYXJ5IENlcnRpZmljYXRpb24g QXV0aG9yaXR5MB4XDTk4MDUxMjAwMDAwMFoXDTA4MDUxMjIzNTk1OVowgcwxFzAVBgNVBAoT DlZlcmlTaWduLCBJbmMuMR8wHQYDVQQLExZWZXJpU2lnbiBUcnVzdCBOZXR3b3JrMUYwRAYD VQQLEz13d3cudmVyaXNpZ24uY29tL3JlcG9zaXRvcnkvUlBBIEluY29ycC4gQnkgUmVmLixM SUFCLkxURChjKTk4MUgwRgYDVQQDEz9WZXJpU2lnbiBDbGFzcyAxIENBIEluZGl2aWR1YWwg U3Vic2NyaWJlci1QZXJzb25hIE5vdCBWYWxpZGF0ZWQwgZ8wDQYJKoZIhvcNAQEBBQADgY0A MIGJAoGBALtaRIoEFrtV/QN6ii2UTxV4NrgNSrJvnFS/vOh3Kp258Gi7ldkxQXB6gUu5SBNW LccI4YRCq8CikqtEXKpC8IIOAukv+8I7u77JJwpdtrA2QjO1blSIT4dKvxna+RXoD4e2HOPM xpqOf2okkuP84GW6p7F+78nbN2rISsgJBuSZAgMBAAGjfDB6MBEGCWCGSAGG+EIBAQQEAwIB BjBHBgNVHSAEQDA+MDwGC2CGSAGG+EUBBwEBMC0wKwYIKwYBBQUHAgEWH3d3dy52ZXJpc2ln bi5jb20vcmVwb3NpdG9yeS9SUEEwDwYDVR0TBAgwBgEB/wIBADALBgNVHQ8EBAMCAQYwDQYJ KoZIhvcNAQECBQADgYEAiLg3O93alDcAraqf4YEBcR6Sam0v9vGd08pkONwbmAwHhluFFWoP uUmFpJXxF31ntH8tLN2aQp7DPrSOquULBt7yVir6M8e+GddTTMO9yOMXtaRJQmPswqYXD11Y Gkk8kFxVo2UgAP0YIOVfgqaxqJLFWGrBjQM868PNBaKQrm4xggHGMIIBwgIBATCB4TCBzDEX MBUGA1UEChMOVmVyaVNpZ24sIEluYy4xHzAdBgNVBAsTFlZlcmlTaWduIFRydXN0IE5ldHdv cmsxRjBEBgNVBAsTPXd3dy52ZXJpc2lnbi5jb20vcmVwb3NpdG9yeS9SUEEgSW5jb3JwLiBC eSBSZWYuLExJQUIuTFREKGMpOTgxSDBGBgNVBAMTP1ZlcmlTaWduIENsYXNzIDEgQ0EgSW5k aXZpZHVhbCBTdWJzY3JpYmVyLVBlcnNvbmEgTm90IFZhbGlkYXRlZAIQApVe2J4YoQsKq3oF 4463XzAJBgUrDgMCGgUAoH0wGAYJKoZIhvcNAQkDMQsGCSqGSIb3DQEHATAcBgkqhkiG9w0B CQUxDxcNOTkwOTI5MTY0MjEyWjAeBgkqhkiG9w0BCQ8xETAPMA0GCCqGSIb3DQMCAgEoMCMG CSqGSIb3DQEJBDEWBBTMA11NTdc+TT0frTvRdlky0scaFjANBgkqhkiG9w0BAQEFAARAIl6p Nd73lBbrKpt/ZCEwa9U3HnzKE/zDc1+jiiRVUdJVLHjXz2qyG/J8l+w2M4kg4LI71dPcSjnR GhQ1ipAIyw== --------------ms1BA66C6B6C082D32B80AA800-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Sep 29 10:10:22 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from plains.NoDak.edu (plains.NoDak.edu [134.129.111.64]) by hub.freebsd.org (Postfix) with ESMTP id 9968C15890; Wed, 29 Sep 1999 10:10:05 -0700 (PDT) (envelope-from tinguely@plains.NoDak.edu) Received: (from tinguely@localhost) by plains.NoDak.edu (8.9.3/8.9.3) id MAA20873; Wed, 29 Sep 1999 12:10:00 -0500 (CDT) Date: Wed, 29 Sep 1999 12:10:00 -0500 (CDT) From: Mark Tinguely Message-Id: <199909291710.MAA20873@plains.NoDak.edu> To: danhil@cwnt.com, freebsd-hackers@FreeBSD.ORG, freebsd-questions@FreeBSD.ORG Subject: Re: A bug in the sppp driver? Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > When you trying to establish connection from one peer (local) to another > (remote), you sent a CONF_REQ message to the remote peer. The remote peer > should answer with a CONF_ACK message. In the code of the sppp driver > (net/if_spppsubr.c, lines 1321 - 1357) you can see that the remote peer > send's a CONF_ACK message to the local peer > (in the line: rv = (cp->RCR)(sp, h, len);) but doesn't change it state to > STATE_ACK_SENT (as I think it should do) . Further more, you can see that after you sent the configuration request, you are in state REQ_SENT. the Receive Config Ack will cause you to state ACK_SENT on line 1327. > Question: if you are in the STATE_ACK_SENT why change the state to the same > one according to the value of rv? STATE_ACK_SENT is the state before we recieved this configuration packet. the sppp_lcp_RCR will send a REJ, NAK, or ACK, and reflect the packet sent in the return value rv. RFC 1661 page 12 states what state to go into ACK_SENT (for RCR+) or REQ_SENT (for RCR-). this make sense we can recieve a RCR while still ACK the last RCR. And in the other case, if we reject a parameter in the RCR, we expect them to either remove the objectional item or give us a value that we can use (hense the REQ_SENT). > As I understand, the state should be changed according to the value of rv, > but it should be done right after the call to cp->RCR. The it is implemented > now, the state won't be changed. I requested that a minor state change be made on the FreeBSD-3.2 version (and from a diff of the two drivers, it appears it has been corrected, but I haven't studied the 3.3-RELEASE version that closely and the change was a very minor state that should not happen very often). Besides the above mentioned state, I thought sppp floowed RFC 1661 very well. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Sep 29 10:10:27 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from umbra.uran.net.ua (umbra.uran.net.ua [212.111.192.34]) by hub.freebsd.org (Postfix) with ESMTP id 9A9F9155B0 for ; Wed, 29 Sep 1999 10:10:06 -0700 (PDT) (envelope-from simon@comsys.ntu-kpi.kiev.ua) Received: from relay1.ntu-kpi.kiev.ua (oberon.ntu-kpi.kiev.ua [195.178.136.20]) by umbra.uran.net.ua (Postfix) with ESMTP id 9E3478F60A for ; Wed, 29 Sep 1999 20:10:05 +0300 (EEST) Received: from comsys.ntu-kpi.kiev.ua (eth0.comsys.ntu-kpi.kiev.ua [10.0.1.184]) by relay1.ntu-kpi.kiev.ua (Postfix) with ESMTP id ADF032FA30 for ; Wed, 29 Sep 1999 20:10:04 +0300 (EEST) Received: from comsys.ntu-kpi.kiev.ua (c514-8.comsys.ntu-kpi.kiev.ua [10.18.54.58]) by comsys.ntu-kpi.kiev.ua (8.9.2/8.8.7) with ESMTP id UAA13750 for ; Wed, 29 Sep 1999 20:09:51 +0300 (EEST) (envelope-from simon@comsys.ntu-kpi.kiev.ua) Message-ID: <37F23AED.586E8304@comsys.ntu-kpi.kiev.ua> Date: Wed, 29 Sep 1999 20:14:37 +0400 From: Andrey Simonenko X-Mailer: Mozilla 4.07 [en] (Win98; I) MIME-Version: 1.0 To: hackers@freebsd.org Subject: UNILOAD v.1.1 - new boot loader/manager is available on following site... Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG If you are interesting in UNILOAD - new boot loader/manager with user friendly interface (I've posted UNILOAD v.1.0 here in uuencoded message), you can download it on following URL in 'Software' menu item: http://comsys.ntu-kpi.kiev.ua/~simon On this URL online documentation for UNILOAD is also available, *please read it before install UNILOAD on your system*. If you have problem with access to this site (our university has problem with outgoing channel) please inform me about it. Some people asked me to add some features in UNILOAD, I added them (timeout, default boot, last selected partition boot) in UNILOAD v.1.1. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Sep 29 10:20:14 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from acl.lanl.gov (acl.lanl.gov [128.165.147.1]) by hub.freebsd.org (Postfix) with ESMTP id 2C01915980 for ; Wed, 29 Sep 1999 10:17:58 -0700 (PDT) (envelope-from rminnich@lanl.gov) Received: from localhost (rminnich@localhost) by acl.lanl.gov (8.8.8/8.8.5) with ESMTP id LAA226218 for ; Wed, 29 Sep 1999 11:17:58 -0600 (MDT) X-Authentication-Warning: acl.lanl.gov: rminnich owned process doing -bs Date: Wed, 29 Sep 1999 11:17:58 -0600 From: "Ronald G. Minnich" To: hackers@freebsd.org Subject: return to real mode Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG anybody got some reliable, tested, known-good code for getting back to real mode? I'm to the point where I have a working GDT, and paging is turned off, but the last step -- turning off protection enable -- is not working for me. This is on a PII. Thanks ron To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Sep 29 11:24:37 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mg-20425427-16.ricochet.net (mg-20425427-16.ricochet.net [204.254.27.16]) by hub.freebsd.org (Postfix) with ESMTP id BFC281596B for ; Wed, 29 Sep 1999 11:23:51 -0700 (PDT) (envelope-from gurney_j@efn.org) Received: (from jmg@localhost) by mg-20425427-16.ricochet.net (8.9.1/8.8.7) id LAA05277; Wed, 29 Sep 1999 11:23:11 -0700 (PDT) Message-ID: <19990929112305.10957@hydrogen.fircrest.net> Date: Wed, 29 Sep 1999 11:23:05 -0700 From: John-Mark Gurney To: Mark Tinguely Cc: hackers@FreeBSD.ORG Subject: Re: The sppp driver References: <199909291509.KAA14058@plains.NoDak.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.69 In-Reply-To: <199909291509.KAA14058@plains.NoDak.edu>; from Mark Tinguely on Wed, Sep 29, 1999 at 10:09:40AM -0500 Reply-To: John-Mark Gurney Organization: Cu Networking X-Operating-System: FreeBSD 3.0-RELEASE i386 X-PGP-Fingerprint: B7 EC EF F8 AE ED A7 31 96 7A 22 B3 D8 56 36 F4 X-Files: The truth is out there X-URL: http://resnet.uoregon.edu/~gurney_j/ Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mark Tinguely scribbled this message on Sep 29: > The sppp > is more efficient than ppp and pppd because it does not have to map > the packets from kernel space to user space and then back again, plus the > advatages not having to service interrupts on each character, the > synchronous link does not need to map Asynchronous-Control-Character-Map > characters and Frame Check Sums. pppd only map packets from kernel space to user space when they are control packets... all data packets get passed directly from the ppp tty driver to the network layer.... so, pppd may not be as efficient as sppp, but the parts that matter (data latency) is just as efficient... -- John-Mark Gurney Voice: +1 408 975 9651 Cu Networking "The soul contains in itself the event that shall presently befall it. The event is only the actualizing of its thought." -- Ralph Waldo Emerson To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Sep 29 11:46:11 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mailc.telia.com (mailc.telia.com [194.22.190.4]) by hub.freebsd.org (Postfix) with ESMTP id 132E115145; Wed, 29 Sep 1999 11:45:54 -0700 (PDT) (envelope-from stefan@syprix.se) Received: from d1o49.telia.com (root@d1o49.telia.com [195.198.194.241]) by mailc.telia.com (8.8.8/8.8.8) with ESMTP id UAA10377; Wed, 29 Sep 1999 20:45:53 +0200 (CEST) Received: from syprix.se (t6o49p34.telia.com [195.198.195.94]) by d1o49.telia.com (8.8.8/8.8.5) with ESMTP id UAA21867; Wed, 29 Sep 1999 20:45:52 +0200 (CEST) Message-ID: <37F261E0.23C5163F@syprix.se> Date: Wed, 29 Sep 1999 21:00:48 +0200 From: Stefan Lindgren Reply-To: stefan@syprix.se Organization: Syprix AB X-Mailer: Mozilla 4.6 [en] (Win98; I) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-hardware@freebsd.org Cc: freebsd-hackers@freebsd.org Subject: Tyan Dual PPRO Bios 5.1 problem... Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, Is there anyone out there with a TYAN 1668-S(ATX) Dual PPRO wich have upgraded to Bios 5.1? I can't run the machine with the UDMA disk(should be supported in Bios 5.1). Works OK with a EIDE Quantum ~ 3 GB disk. Setup: FreeBSD 3.0; 196 RAM SB 64 Awe M Millenium 1 4 MB UDMA Seagate Medalist ~ 6 GB Tyan 1668-S Dual PPRO Bios 5.1 MP v 1.4 Regards /stefan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Sep 29 11:56:38 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from bingsun2.cc.binghamton.edu (bingsun2.cc.binghamton.edu [128.226.6.4]) by hub.freebsd.org (Postfix) with ESMTP id 73AE61592A for ; Wed, 29 Sep 1999 11:56:01 -0700 (PDT) (envelope-from bf20761@binghamton.edu) Received: from localhost (bf20761@localhost) by bingsun2.cc.binghamton.edu (8.9.3/8.9.3) with ESMTP id OAA13810 for ; Wed, 29 Sep 1999 14:56:00 -0400 (EDT) X-Authentication-Warning: bingsun2.cc.binghamton.edu: bf20761 owned process doing -bs Date: Wed, 29 Sep 1999 14:56:00 -0400 (EDT) From: Zhihui Zhang X-Sender: bf20761@bingsun2 To: freebsd-hackers@FreeBSD.ORG Subject: Help with registering RPC with inetd Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have been able to register a RPC service with the inetd deamon by modifying the /etc/inetd.conf and /etc/rpc files. The RPC code is generated with the -I option, i.e., by using rpcgen -I myfile.x. (For those who have read my previous post, I made a mistake there. The program number is a hex 0x20000001, I should use its correcponding decimal number in /etc/rpc, which is 536870913.) Everything works fine. But the process of the PRC service does not exit after 120 seconds as expected (120 seconds is the default value, I actually waited much longer time for it to die). To find out the reason, I look into the server stub created by rpcgen, especially the closedown() routine that is invoked by the SIGALRM signal. The following code in this closedown() routine explains the reason why the RPC service process refuses to die: for (i = 0, openfd = 0; i < size && openfd < 2; i++) if (FD_ISSET(i, &svc_fdset)) openfd++ if (openfd <= 1) exit(0); I add some syslog() statements in them and find out that besides descriptor 0, descriptor 1063 is also set (the size is 1064, why this large?). Who could possibly FD_SET() the descriptor 1063 into svc_fdset? This makes openfd == 2. Therefore the RPC service process will not die even after it has been idle for a long time. I hope some one can give me a hint on this mystery. Any help is appreciated. -Zhihui To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Sep 29 12:28:23 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from zibbi.mikom.csir.co.za (zibbi.mikom.csir.co.za [146.64.24.58]) by hub.freebsd.org (Postfix) with ESMTP id 280751562F; Wed, 29 Sep 1999 12:25:20 -0700 (PDT) (envelope-from jhay@zibbi.mikom.csir.co.za) Received: (from jhay@localhost) by zibbi.mikom.csir.co.za (8.9.3/8.9.3) id VAA65012; Wed, 29 Sep 1999 21:25:08 +0200 (SAT) (envelope-from jhay) From: John Hay Message-Id: <199909291925.VAA65012@zibbi.mikom.csir.co.za> Subject: Re: A bug in the sppp driver? In-Reply-To: <033a01bf0a92$8fe1b4e0$2e00a8c0@nt46daniel> from Daniel Hilevich at "Sep 29, 1999 04:51:58 pm" To: danhil@cwnt.com (Daniel Hilevich) Date: Wed, 29 Sep 1999 21:25:08 +0200 (SAT) Cc: freebsd-questions@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Are you busy with a leased line driver or a dialup/isdn kind of driver? I have been busy fixing sppp to work properly with leased line drivers again, but am not finished with it yet. :-/ Hopefully I won't break the isdn handling at the same time. > While trying to use the sppp, I came across this situation and I think it's > a bug: > When you trying to establish connection from one peer (local) to another > (remote), you sent a CONF_REQ message to the remote peer. The remote peer > should answer with a CONF_ACK message. In the code of the sppp driver > (net/if_spppsubr.c, lines 1321 - 1357) you can see that the remote peer > send's a CONF_ACK message to the local peer > (in the line: rv = (cp->RCR)(sp, h, len);) but doesn't change it state to > STATE_ACK_SENT (as I think it should do) . Further more, you can see that > after a few lines, there are these strange lines: > case STATE_ACK_SENT: > case STATE_REQ_SENT: > sppp_cp_change_state(cp, sp, rv? > STATE_ACK_SENT: STATE_REQ_SENT); > break; My patch for this part looks like this, carefull I have just cut and paste it, so the tabs got lost: --------- @@ -1298,6 +1299,16 @@ /* fall through... */ case STATE_ACK_SENT: case STATE_REQ_SENT: + /* + * sppp_cp_change_state() have the side effect of + * restarting the timeouts. We want to avoid that + * if the state don't change, otherwise we won't + * ever timeout and resend a configuration request + * that got lost. + */ + if (sp->state[cp->protoidx] == (rv ? STATE_ACK_SENT: + STATE_REQ_SENT)) + break; sppp_cp_change_state(cp, sp, rv? STATE_ACK_SENT: STATE_REQ_SENT); break; -------- > > Question: if you are in the STATE_ACK_SENT why change the state to the same > one according to the value of rv? Because the state transition table on page 13 of rfc1661 says that if you are in "Ack-Sent" and receive a +RCR, you send a sca and stay in the same state? > > As I understand, the state should be changed according to the value of rv, > but it should be done right after the call to cp->RCR. The it is implemented > now, the state won't be changed. Like it is, it does work under ideal (no packet loss) conditions. My patch is just for the case where a scr packet got lost. > > (I have a lot of problems with this driver and any help will be > appreciative) There are two other "big" problems that I know of. If the line is down long enough, sppp will give up and go in a illegal state. It should just keep on trying to establish the link again. I have a fix that I'm testing for this. The loopback handling are broken. It just go in a transmit frenzy. I have tried the solution in gnats 11238, but I'm not happy with it, because it stops sppp when loopback is detected, which is also not what I want. But appart from these and a few minor problems sppp is working just fine here. John -- John Hay -- John.Hay@mikom.csir.co.za To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Sep 29 12:39:55 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mail-01.cdsnet.net (mail-01.cdsnet.net [206.107.16.35]) by hub.freebsd.org (Postfix) with SMTP id 26C11159E7 for ; Wed, 29 Sep 1999 12:36:45 -0700 (PDT) (envelope-from mrcpu@internetcds.com) Received: (qmail 27435 invoked from network); 29 Sep 1999 19:36:45 -0000 Received: from schizo.cdsnet.net (204.118.244.32) by mail.cdsnet.net with SMTP; 29 Sep 1999 19:36:45 -0000 Date: Wed, 29 Sep 1999 12:36:24 -0700 (PDT) From: Jaye Mathisen X-Sender: mrcpu@schizo.cdsnet.net To: hackers@freebsd.org Subject: Overriding NPROC w/o bumping maxusers? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG What's the danger in changing the NPROC define in param.c to be ifdef'd, and an option in the kernel config file? it looks like the only way to change the # of allowed processes is via changing maxusers, but is that only by convention? Or is there some other reason I can't override it? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Sep 29 13:11: 3 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from florence.pavilion.net (florence.pavilion.net [194.242.128.25]) by hub.freebsd.org (Postfix) with ESMTP id C8ECC15961; Wed, 29 Sep 1999 13:10:26 -0700 (PDT) (envelope-from joe@florence.pavilion.net) Received: (from joe@localhost) by florence.pavilion.net (8.9.3/8.8.8) id VAA01818; Wed, 29 Sep 1999 21:10:19 +0100 (BST) (envelope-from joe) Date: Wed, 29 Sep 1999 21:10:19 +0100 From: Josef Karthauser To: Bob Bishop Cc: current@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: my repository is broken (more) Message-ID: <19990929211018.G86792@florence.pavilion.net> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre2i In-Reply-To: X-NCC-RegID: uk.pavilion Organisation: Pavilion Internet plc, 24 The Old Steine, Brighton, BN1 1EL, England Phone: +44-845-333-5000 Fax: +44-845-333-5001 Mobile: +44-403-596893 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Sep 29, 1999 at 04:58:34PM +0000, Bob Bishop wrote: > Hi, > > I wrote: > > ===> usr.sbin/lpr/filters.ru > > ===> usr.sbin/lpr/filters.ru/koi2alt > > make: don't know how to make koi2alt.c. Stop > > > >Apparently because... > > > > ache 1999/09/22 19:54:45 PDT > > > > Removed files: > > usr.sbin/lpr/filters.ru koi2alt.c > > Log: > > moved to koi2alt > > > >...never made it here. What's the easiest way to get back in step? TIA > > I now suspect that cvsup.uk.freebsd.org isn't up-to-date. Anyone know anything? Oops, it's public now. (bows head in shame.) Yes, there was a problem with the main UK cvsup server, from about the 19th. I updated the machine to 3.3, and reinstalled all the ports. Unfortunately the cvsup-mirror port hadn't been updated (John did it today) to reflect the changes made earlier in the year. We now pull from cvsup-master, not freefall! Thus, since the 19th we've been failing authentication and I didn't notice, cause the internat stuff, which happens first, was working, and secondly, my home machine doesn't currently have an internet connection because the I4B code hasn't been ported to Stable and thus PPPoISDN doesn't work anymore. I say anymore because the other machine that it _was_ working on was running Brian's development copy and the harddrive went *bang* for reasons of old age! In summary - sorry, try again. 'Tis working now :) Joe -- Josef Karthauser FreeBSD: How many times have you booted today? Technical Manager Viagra for your server (http://www.uk.freebsd.org) Pavilion Internet plc. [joe@pavilion.net, joe@uk.freebsd.org, joe@tao.org.uk] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Sep 29 13:12:28 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from florence.pavilion.net (florence.pavilion.net [194.242.128.25]) by hub.freebsd.org (Postfix) with ESMTP id 5AB9414E3F for ; Wed, 29 Sep 1999 13:12:20 -0700 (PDT) (envelope-from joe@florence.pavilion.net) Received: (from joe@localhost) by florence.pavilion.net (8.9.3/8.8.8) id VAA02006; Wed, 29 Sep 1999 21:12:10 +0100 (BST) (envelope-from joe) Date: Wed, 29 Sep 1999 21:12:10 +0100 From: Josef Karthauser To: David Gilbert Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: PPPoE offer. Message-ID: <19990929211210.H86792@florence.pavilion.net> References: <14322.15597.505566.676863@trooper.velocet.ca> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre2i In-Reply-To: <14322.15597.505566.676863@trooper.velocet.ca> X-NCC-RegID: uk.pavilion Organisation: Pavilion Internet plc, 24 The Old Steine, Brighton, BN1 1EL, England Phone: +44-845-333-5000 Fax: +44-845-333-5001 Mobile: +44-403-596893 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Sep 29, 1999 at 12:23:09PM -0400, David Gilbert wrote: > I've got some real $$$ available to encourage someone to make PPPoE > work efficiently enough on the FreeBSD platform to handle a > substantial number of users. Is anyone interested? > > Dave. Dave, As far as I'm aware it _does_ work - in the form of user-ppp (/usr/sbin/ppp), maintained by Brian. Why do you need to use kernel ppp - it's a mess :) Joe -- Josef Karthauser FreeBSD: How many times have you booted today? Technical Manager Viagra for your server (http://www.uk.freebsd.org) Pavilion Internet plc. [joe@pavilion.net, joe@uk.freebsd.org, joe@tao.org.uk] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Sep 29 13:18: 0 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from hotmail.com (f176.law4.hotmail.com [216.33.149.176]) by hub.freebsd.org (Postfix) with SMTP id 85826158DD for ; Wed, 29 Sep 1999 13:17:53 -0700 (PDT) (envelope-from zzhangsuny@hotmail.com) Received: (qmail 28462 invoked by uid 0); 29 Sep 1999 20:17:53 -0000 Message-ID: <19990929201753.28461.qmail@hotmail.com> Received: from 128.226.3.47 by www.hotmail.com with HTTP; Wed, 29 Sep 1999 13:17:49 PDT X-Originating-IP: [128.226.3.47] From: "Zhihui Zhang" To: freebsd-hackers@freebsd.org Subject: Help with registering RPC with inetd Date: Wed, 29 Sep 1999 16:17:49 EDT Mime-Version: 1.0 Content-Type: text/plain; format=flowed Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have been able to register a RPC service with the inetd deamon by modifying the /etc/inetd.conf and /etc/rpc files. The RPC code is generated with the -I option, i.e., by using rpcgen -I myfile.x. (For those who have read my previous post, I made a mistake there. The program number is a hex 0x20000001, I should use its correcponding decimal number in /etc/rpc, which is 536870913.) Everything works fine. But the process of the PRC service does not exit after 120 seconds as expected (120 seconds is the default value, I actually waited much longer time for it to die). To find out the reason, I look into the server stub created by rpcgen, especially the closedown() routine that is invoked by the SIGALRM signal. The following code in this closedown() routine explains the reason why the RPC service process refuses to die: for (i = 0, openfd = 0; i < size && openfd < 2; i++) if (FD_ISSET(i, &svc_fdset)) openfd++ if (openfd <= 1) exit(0); I add some syslog() statements in them and find out that besides descriptor 0, descriptor 1063 is also set (the size is 1064, why this large?). Who could possibly FD_SET() the descriptor 1063 into svc_fdset? This makes openfd == 2. Therefore the RPC service process will not die even after it has been idle for a long time. I hope some one can give me a hint on this mystery. Any help is appreciated. -Zhihui ______________________________________________________ Get Your Private, Free Email at http://www.hotmail.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Sep 29 13:18:10 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from server.baldwin.cx (jobaldwi.campus.vt.edu [198.82.67.146]) by hub.freebsd.org (Postfix) with ESMTP id 0295014A31 for ; Wed, 29 Sep 1999 13:17:51 -0700 (PDT) (envelope-from jobaldwi@vt.edu) Received: from john.baldwin.cx (john [10.0.0.2]) by server.baldwin.cx (8.9.3/8.9.3) with ESMTP id QAA79832; Wed, 29 Sep 1999 16:18:04 -0400 (EDT) (envelope-from jobaldwi@vt.edu) Message-Id: <199909292018.QAA79832@server.baldwin.cx> X-Mailer: XFMail 1.3.1 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Wed, 29 Sep 1999 16:18:02 -0400 (EDT) From: John Baldwin To: "Ronald G. Minnich" Subject: RE: return to real mode Cc: hackers@freebsd.org Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 29-Sep-99 Ronald G. Minnich wrote: > anybody got some reliable, tested, known-good code for getting back > to > real mode? I'm to the point where I have a working GDT, and paging is > turned off, but the last step -- turning off protection enable -- is > not > working for me. Well, initialize all of your selectors to descriptors that have 64k limits (0xffff). Jump into a 16bit code segment with a 64k limit on the CS selector, turn off bit 0 in cr0 to actually enter real mode, then jump to the next instruction so that the cache is flushed. I believe it needs to be a far jmp, and then you should be fine. For example: (this is TASM, so it's Intel syntax and not AT&T) GROUP CodeGroup _TEXT32, _TEXT16 ASSUME CS:CodeGroup, DS:_PMDATA .... SEGMENT _TEXT32 Byte Public Use32 'CODE' .... db 0EAh dd OFFSET ExitPM dw Sel_CS16 ENDP ENDS SEGMENT _TEXT16 Word Public Use16 'CODE' ExitPM: mov ax,Sel_ESeg mov es,ax mov fs,ax mov gs,ax ; mov ss,ax mov eax,cr0 xor eax,eax ;clear bit 0, (i.e. leave PM) mov cr0,eax ;leave protected mode ; jmp FAR CleanUp db 0EAh ;jmp far CleanUp dw OFFSET CleanUp dw CodeGroup ..... CleanUp: mov ax,_PMDATA mov ds,ax ;restore DS lss sp,[DWORD PTR OFFSET SaveSP] ;restore SS:SP ..... Now you are in Real Mode > This is on a PII. This code has been tested (and works) on 386, 386, and Pentium. Presumably it should work on later chips as well. > Thanks > > ron --- John Baldwin -- http://www.cslab.vt.edu/~jobaldwi/ PGP Key: http://www.cslab.vt.edu/~jobaldwi/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Sep 29 13:25:42 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from trooper.velocet.ca (trooper.velocet.net [216.126.82.226]) by hub.freebsd.org (Postfix) with ESMTP id B7D1E14ED2 for ; Wed, 29 Sep 1999 13:25:24 -0700 (PDT) (envelope-from dgilbert@trooper.velocet.ca) Received: (from dgilbert@localhost) by trooper.velocet.ca (8.9.3/8.9.3) id QAA28377; Wed, 29 Sep 1999 16:25:13 -0400 (EDT) (envelope-from dgilbert) From: David Gilbert MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14322.30121.178080.621999@trooper.velocet.ca> Date: Wed, 29 Sep 1999 16:25:13 -0400 (EDT) To: Josef Karthauser Cc: David Gilbert , freebsd-hackers@FreeBSD.ORG Subject: Re: PPPoE offer. In-Reply-To: <19990929211210.H86792@florence.pavilion.net> References: <14322.15597.505566.676863@trooper.velocet.ca> <19990929211210.H86792@florence.pavilion.net> X-Mailer: VM 6.71 under 20.4 "Emerald" XEmacs Lucid Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >>>>> "Josef" == Josef Karthauser writes: Josef> As far as I'm aware it _does_ work - in the form of user-ppp Josef> (/usr/sbin/ppp), maintained by Brian. Why do you need to use Josef> kernel ppp - it's a mess :) In some discussions with some local BSD hackers, many claimed that I would never get the performance I required out of user-ppp. The basic requirement is that we handle somewhere between 5k and 10K connections (on some amount of CPU). Were would I find recent patches to user-ppp to receive PPPoE streams? Dave. -- ============================================================================ |David Gilbert, Velocet Communications. | Two things can only be | |Mail: dgilbert@velocet.net | equal if and only if they | |http://www.velocet.net/~dgilbert | are precisely opposite. | =========================================================GLO================ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Sep 29 13:27:56 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from chele.cais.net (chele.cais.com [199.0.216.212]) by hub.freebsd.org (Postfix) with ESMTP id AEF6515866 for ; Wed, 29 Sep 1999 13:27:03 -0700 (PDT) (envelope-from brian@chele.cais.net) Received: from localhost (brian@localhost) by chele.cais.net (8.9.1/8.9.1) with ESMTP id QAA03581 for ; Wed, 29 Sep 1999 16:22:09 -0400 (EDT) Date: Wed, 29 Sep 1999 16:22:08 -0400 (EDT) From: Brian Mitchell To: freebsd-hackers@freebsd.org Subject: KLD dependencies Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG How do I specify dependencies in modules? I can find no documentation on this, is it done automatically (doubtful)? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Sep 29 13:32:41 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id 21BAD14CD0; Wed, 29 Sep 1999 13:31:55 -0700 (PDT) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id WAA22795; Wed, 29 Sep 1999 22:31:53 +0200 (CEST) (envelope-from sos) From: Soren Schmidt Message-Id: <199909292031.WAA22795@freebsd.dk> Subject: Re: Tyan Dual PPRO Bios 5.1 problem... In-Reply-To: <37F261E0.23C5163F@syprix.se> from Stefan Lindgren at "Sep 29, 1999 09:00:48 pm" To: stefan@syprix.se Date: Wed, 29 Sep 1999 22:31:53 +0200 (CEST) Cc: freebsd-hardware@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems Stefan Lindgren wrote: > Hi, > > Is there anyone out there with a TYAN 1668-S(ATX) Dual PPRO wich have > upgraded to Bios 5.1? I run a 1662D (the AT version of the same board) no problems... What goes wrong ?? The TYAN is a bit harsh on timing and I've seen a few early UDMA disk that are not rally up to the task. -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Sep 29 13:53:34 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from maild.telia.com (maild.telia.com [194.22.190.3]) by hub.freebsd.org (Postfix) with ESMTP id AAAF81501E; Wed, 29 Sep 1999 13:53:21 -0700 (PDT) (envelope-from stefan@syprix.se) Received: from d1o49.telia.com (root@d1o49.telia.com [195.198.194.241]) by maild.telia.com (8.8.8/8.8.8) with ESMTP id WAA11717; Wed, 29 Sep 1999 22:53:20 +0200 (CEST) Received: from syprix.se (t2o49p52.telia.com [195.198.194.112]) by d1o49.telia.com (8.8.8/8.8.5) with ESMTP id WAA13244; Wed, 29 Sep 1999 22:53:18 +0200 (CEST) Message-ID: <37F27FBC.DE71E5BB@syprix.se> Date: Wed, 29 Sep 1999 23:08:12 +0200 From: Stefan Lindgren Reply-To: stefan@syprix.se Organization: Syprix AB X-Mailer: Mozilla 4.6 [en] (Win98; I) X-Accept-Language: en MIME-Version: 1.0 Cc: freebsd-hackers@freebsd.org, freebsd-hardware@freebsd.org Subject: [Fwd: Tyan Dual PPRO Bios 5.1 problem...] Content-Type: multipart/mixed; boundary="------------AB4D18FE0B71AC3914D01C7E" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a multi-part message in MIME format. --------------AB4D18FE0B71AC3914D01C7E Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit --------------AB4D18FE0B71AC3914D01C7E Content-Type: message/rfc822 Content-Transfer-Encoding: 8bit Content-Disposition: inline X-Mozilla-Status2: 00000000 Message-ID: <37F27F47.E46A4F87@syprix.se> Date: Wed, 29 Sep 1999 23:06:15 +0200 From: Stefan Lindgren Reply-To: stefan@syprix.se Organization: Syprix AB X-Mailer: Mozilla 4.6 [en] (Win98; I) X-Accept-Language: en MIME-Version: 1.0 To: Soren Schmidt Subject: Re: Tyan Dual PPRO Bios 5.1 problem... References: <199909292031.WAA22795@freebsd.dk> Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit I get page faults, kernel panic(trap 12) and the system won't boot. It looks that it could be memory related, but the system works fine with the EIDE disk. Soren Schmidt wrote: > > It seems Stefan Lindgren wrote: > > Hi, > > > > Is there anyone out there with a TYAN 1668-S(ATX) Dual PPRO wich have > > upgraded to Bios 5.1? > > I run a 1662D (the AT version of the same board) no problems... > > What goes wrong ?? The TYAN is a bit harsh on timing and I've seen > a few early UDMA disk that are not rally up to the task. > > -Søren --------------AB4D18FE0B71AC3914D01C7E-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Sep 29 14: 7:33 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from proxy2.ba.best.com (proxy2.ba.best.com [206.184.139.14]) by hub.freebsd.org (Postfix) with ESMTP id 21D7114EA7 for ; Wed, 29 Sep 1999 14:07:24 -0700 (PDT) (envelope-from shepard@MetaThink.COM) Received: from MetaThink.COM (dynamic24.pm11.mv.best.com [209.24.242.152]) by proxy2.ba.best.com (8.9.3/8.9.2/best.out) with ESMTP id OAA24614; Wed, 29 Sep 1999 14:00:29 -0700 (PDT) Received: (from shepard@localhost) by MetaThink.COM (8.9.2/8.8.7) id NAA64831; Wed, 29 Sep 1999 13:59:52 -0700 (PDT) (envelope-from shepard) Date: Wed, 29 Sep 1999 13:59:46 -0700 From: Mark Shepard To: Doug White , Christian Carstensen , Chris Piazza , Chris Costello , Patryk Zadarnowski , freebsd-hackers@FreeBSD.ORG Subject: Re: updating packages automatically... Message-ID: <19990929135946.A56245@ed209.home> Reply-To: mns@MetaThink.COM Mail-Followup-To: Doug White , Christian Carstensen , Chris Piazza , Chris Costello , Patryk Zadarnowski , freebsd-hackers@FreeBSD.ORG References: <19990928114145.A41493@ed209.home> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.3i In-Reply-To: ; from Doug White on Tue, Sep 28, 1999 at 08:40:50PM -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Doug White said: > On Tue, 28 Sep 1999, Mark Shepard wrote: > > I _like_ the idea of a email-summary of "What's New in the World of Ports". > > We used to have this. I think it morphed into the webpage mutation we > have now (note you can request all the changed ports in the last X time > frame). > > Maybe it's posted to the -ports mailing list? Is this information the same as the periodic postings to comp.os.bsd.freebsd.announce? In the context of this thread (automatically updating/maintaining the ports one has chosen to install) I'd want the information filtered based on the ports I actually had installed. As a sysadmin, I may certainly be interested in reading about new ports, but I'm _more_ interested in reading about any updates to the ports I'm actually using, and in particular seeing _why_ the update occurred (was it a critical bug fix or just a few more features?) so that I can prioritize correctly. I imagine the email sent by the automatic ports maintainence program might look like this (one entry for each port/package which has been updated): | fetchmail-5.0.8 | Batch mail retrieval/forwarding utility for pop2, pop3, apop, imap | Maintained by: ve@sci.fi | | fetchmail-4.7.0 is currently installed. | Changes from 4.7.0 to 5.0.8: | blah | blah | blah | (this could be generated by diffing ChangeLog or README files) | | Updating this port will also require updating: | port1 | port2 | port3 | (fetchmail's doesn't depend on anything..., but if it did | I'd want to see not simply _all_ the dependencies, but _only_ | those which were out of date/would need to be updated). | | All necessary distfiles have been downloaded. | (or, an error msg indicating which distfiles couldn't be | downloaded from any of the mirrors. This gives you an idea of | how long it'll take to do the update, just 'make install' or | will you have to grovel around to find the files...) | | To update this port, click here | or give the commands "cd /usr/ports/*, make install, blah blah blah." This seems like a feature which would be very useful to people using FreeBSD commercially as an application platform, who unlike the hobbyists or developers may not have time, inclination or reason to experiment with every new port and instead want to focus on maintaining only the ports they are actually using. Another way to look at it -- installing a port automatically "subscribes" you to maintainence information about that port. Currently when I install a s/w package I also subscribe to the developer's announce list (if there is one) or to the general list (and filter for announcements), which takes time. OTOH, what I'm proposing isn't an ideal way to get information on critical bugs in s/w packages one may be using because of the time-lag between a bug being discovered, fixed and then the fix being incorporated into the FBSD port and picked up via CVSup. Still, for less-critical s/w packages (or for users who are less critical of their s/w :-) this mechanism seems like it'd still be a time-saver. Don't take this the wrong way - The periodic postings of _all_ additions to the ports collection are _great_! Wonderful! Fastastic! :-) But in the context of this thread (automatically updating/maintaining the ports one has installed), I think some additional features could be even more useful. Doug White said: > I think a 'make checkdep' type target to run the dependency check w/o > actually building them would be a plus. This should be very easy to do w/ > the current bsd.port.mk frame. Chris Piazza said: > make package-depends might be what you're looking for. Thanks. package-depends could be a starting point for the mechanism I'd like. It seems to return all the dependencies (including duplicates, easily uniq'd), but I'd want to know which dependencies have actually been superceded. BTW, perhaps this has already been discussed elsewhere, but would it be reasonable for an "automatic package maintainer" to allow the option of downloading and building from (source) distfiles, or (binary) packages? "That's an issue with the ports makefile system and/or pkg_add", you may say, but since I've also proposed that the "automatic package maintainer" download distfiles in the background (so the sysadmin doesn't have to wait for the downloads in the foreground), the "automatic package maintainer" would need to know your preference of using distfiles or pre-built packages. Mark To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Sep 29 14:34:34 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from nomis.simon-shapiro.org (nomis.simon-shapiro.org [209.86.126.163]) by hub.freebsd.org (Postfix) with SMTP id D4CA515609 for ; Wed, 29 Sep 1999 14:34:24 -0700 (PDT) (envelope-from shimon@simon-shapiro.org) Received: (qmail 13724 invoked from network); 29 Sep 1999 21:34:23 -0000 Received: from localhost.simon-shapiro.org (HELO simon-shapiro.org) (127.0.0.1) by localhost.simon-shapiro.org with SMTP; 29 Sep 1999 21:34:23 -0000 Message-ID: <37F285DF.46A239B4@simon-shapiro.org> Date: Wed, 29 Sep 1999 17:34:23 -0400 From: Simon Shapiro as Himself Organization: Simon's Garage X-Mailer: Mozilla 4.6 [en] (X11; I; FreeBSD 3.3-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: hackers@freebsd.org Subject: SYSINIT question Content-Type: multipart/signed; protocol="application/x-pkcs7-signature"; micalg=sha1; boundary="------------ms472127EEB42963A99204F343" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a cryptographically signed message in MIME format. --------------ms472127EEB42963A99204F343 Content-Type: text/plain; charset= Content-Transfer-Encoding: 7bit Hi Y'll Am noticing that adding: SYSINIT(i2o_dev, SI_SUB_DRIVERS, SI_ORDER_MIDDLE+CDEV_MAJOR, i2o_drvinit, NULL) to one's driver causes the init routine (i2o_drvinit to run very early, as in: real memory = 402653184 (393216K bytes) avail memory = 388120576 (379024K bytes) Preloaded elf kernel "kernel.i2o" at 0xc034d000. register_swi Pentium Pro MTRR support enabled ../../i2o/i2o_drv.c.1063 drvinit I2O: Trying to initialize too early Probing for devices on PCI bus 0: While I really would like it to run AFETR the PCI scan, so that I have IOPs to talk to etc., Other than ugly hacs in main(), is there a way? This is all in RELENG_3... -- Sincerely Yours, Shimon@Simon-Shapiro.ORG 404.644.6401 Simon Shapiro Unwritten code has no bugs and executes at twice the speed of mouth --------------ms472127EEB42963A99204F343 Content-Type: application/x-pkcs7-signature; name="smime.p7s" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="smime.p7s" Content-Description: S/MIME Cryptographic Signature MIIJ7QYJKoZIhvcNAQcCoIIJ3jCCCdoCAQExCzAJBgUrDgMCGgUAMAsGCSqGSIb3DQEHAaCC B+8wggS5MIIEIqADAgECAhAClV7YnhihCwqregXjjrdfMA0GCSqGSIb3DQEBBAUAMIHMMRcw FQYDVQQKEw5WZXJpU2lnbiwgSW5jLjEfMB0GA1UECxMWVmVyaVNpZ24gVHJ1c3QgTmV0d29y azFGMEQGA1UECxM9d3d3LnZlcmlzaWduLmNvbS9yZXBvc2l0b3J5L1JQQSBJbmNvcnAuIEJ5 IFJlZi4sTElBQi5MVEQoYyk5ODFIMEYGA1UEAxM/VmVyaVNpZ24gQ2xhc3MgMSBDQSBJbmRp dmlkdWFsIFN1YnNjcmliZXItUGVyc29uYSBOb3QgVmFsaWRhdGVkMB4XDTk5MDkyNjAwMDAw MFoXDTAwMDkyNTIzNTk1OVowggEYMRcwFQYDVQQKEw5WZXJpU2lnbiwgSW5jLjEfMB0GA1UE CxMWVmVyaVNpZ24gVHJ1c3QgTmV0d29yazFGMEQGA1UECxM9d3d3LnZlcmlzaWduLmNvbS9y ZXBvc2l0b3J5L1JQQSBJbmNvcnAuIGJ5IFJlZi4sTElBQi5MVEQoYyk5ODEeMBwGA1UECxMV UGVyc29uYSBOb3QgVmFsaWRhdGVkMTMwMQYDVQQLEypEaWdpdGFsIElEIENsYXNzIDEgLSBO ZXRzY2FwZSBGdWxsIFNlcnZpY2UxFjAUBgNVBAMUDVNpbW9uIFNoYXBpcm8xJzAlBgkqhkiG 9w0BCQEWGHNoaW1vbkBzaW1vbi1zaGFwaXJvLm9yZzBcMA0GCSqGSIb3DQEBAQUAA0sAMEgC QQCWapJrHdDp0fdP9CDHrTEk6VbRBTk+X3UtU97HWiZooLH/Yp3//NmneAUOsjRj4kHygf3n LNqmQE040B3QdNQzAgMBAAGjggGPMIIBizAJBgNVHRMEAjAAMIGsBgNVHSAEgaQwgaEwgZ4G C2CGSAGG+EUBBwEBMIGOMCgGCCsGAQUFBwIBFhxodHRwczovL3d3dy52ZXJpc2lnbi5jb20v Q1BTMGIGCCsGAQUFBwICMFYwFRYOVmVyaVNpZ24sIEluYy4wAwIBARo9VmVyaVNpZ24ncyBD UFMgaW5jb3JwLiBieSByZWZlcmVuY2UgbGlhYi4gbHRkLiAoYyk5NyBWZXJpU2lnbjARBglg hkgBhvhCAQEEBAMCB4AwgYYGCmCGSAGG+EUBBgMEeBZ2ZDQ2NTJiZDYzZjIwNDcwMjkyOTg3 NjNjOWQyZjI3NTA2OWM3MzU5YmVkMWIwNTlkYTc1YmM0YmM5NzAxNzQ3ZGE1ZDNmMjE0MWJl YWRiMmJkMmU4OTIxNWFkNmFmNGQ1MTE0ODllYTJiMjQ3ZmRmM2VhNDUwYzAzBgNVHR8ELDAq MCigJqAkhiJodHRwOi8vY3JsLnZlcmlzaWduLmNvbS9jbGFzczEuY3JsMA0GCSqGSIb3DQEB BAUAA4GBAJGOv032Cr1u64/mnEHi0uKZb6uS4GQbed8jzBVRs+Y7zruO4R/gnXBEH0OrvE4Z oTqZ00gjnbVCT/rpjARmswNOU+hFI/kcn+HyKS0fw1A9Ppfm8Mp9iHSkYgTRT/MOuC2ck7z5 POETXZ68J14y368tXGd+Ako2n3RNHqOuSmXUMIIDLjCCApegAwIBAgIRANJ2Lo0UDD19sqgl Xa/uDXUwDQYJKoZIhvcNAQECBQAwXzELMAkGA1UEBhMCVVMxFzAVBgNVBAoTDlZlcmlTaWdu LCBJbmMuMTcwNQYDVQQLEy5DbGFzcyAxIFB1YmxpYyBQcmltYXJ5IENlcnRpZmljYXRpb24g QXV0aG9yaXR5MB4XDTk4MDUxMjAwMDAwMFoXDTA4MDUxMjIzNTk1OVowgcwxFzAVBgNVBAoT DlZlcmlTaWduLCBJbmMuMR8wHQYDVQQLExZWZXJpU2lnbiBUcnVzdCBOZXR3b3JrMUYwRAYD VQQLEz13d3cudmVyaXNpZ24uY29tL3JlcG9zaXRvcnkvUlBBIEluY29ycC4gQnkgUmVmLixM SUFCLkxURChjKTk4MUgwRgYDVQQDEz9WZXJpU2lnbiBDbGFzcyAxIENBIEluZGl2aWR1YWwg U3Vic2NyaWJlci1QZXJzb25hIE5vdCBWYWxpZGF0ZWQwgZ8wDQYJKoZIhvcNAQEBBQADgY0A MIGJAoGBALtaRIoEFrtV/QN6ii2UTxV4NrgNSrJvnFS/vOh3Kp258Gi7ldkxQXB6gUu5SBNW LccI4YRCq8CikqtEXKpC8IIOAukv+8I7u77JJwpdtrA2QjO1blSIT4dKvxna+RXoD4e2HOPM xpqOf2okkuP84GW6p7F+78nbN2rISsgJBuSZAgMBAAGjfDB6MBEGCWCGSAGG+EIBAQQEAwIB BjBHBgNVHSAEQDA+MDwGC2CGSAGG+EUBBwEBMC0wKwYIKwYBBQUHAgEWH3d3dy52ZXJpc2ln bi5jb20vcmVwb3NpdG9yeS9SUEEwDwYDVR0TBAgwBgEB/wIBADALBgNVHQ8EBAMCAQYwDQYJ KoZIhvcNAQECBQADgYEAiLg3O93alDcAraqf4YEBcR6Sam0v9vGd08pkONwbmAwHhluFFWoP uUmFpJXxF31ntH8tLN2aQp7DPrSOquULBt7yVir6M8e+GddTTMO9yOMXtaRJQmPswqYXD11Y Gkk8kFxVo2UgAP0YIOVfgqaxqJLFWGrBjQM868PNBaKQrm4xggHGMIIBwgIBATCB4TCBzDEX MBUGA1UEChMOVmVyaVNpZ24sIEluYy4xHzAdBgNVBAsTFlZlcmlTaWduIFRydXN0IE5ldHdv cmsxRjBEBgNVBAsTPXd3dy52ZXJpc2lnbi5jb20vcmVwb3NpdG9yeS9SUEEgSW5jb3JwLiBC eSBSZWYuLExJQUIuTFREKGMpOTgxSDBGBgNVBAMTP1ZlcmlTaWduIENsYXNzIDEgQ0EgSW5k aXZpZHVhbCBTdWJzY3JpYmVyLVBlcnNvbmEgTm90IFZhbGlkYXRlZAIQApVe2J4YoQsKq3oF 4463XzAJBgUrDgMCGgUAoH0wGAYJKoZIhvcNAQkDMQsGCSqGSIb3DQEHATAcBgkqhkiG9w0B CQUxDxcNOTkwOTI5MjEzNDIzWjAeBgkqhkiG9w0BCQ8xETAPMA0GCCqGSIb3DQMCAgEoMCMG CSqGSIb3DQEJBDEWBBTlU/HZkzthGE97AhKoLduQZ/eVHTANBgkqhkiG9w0BAQEFAARAcMKP bIEnp0ToY6uvSHfCzXq27lMN7EujJ5S90PA+8Kugm5eg1DlEsjMQZaP+BDC2JKyibI6ClwNX l7kW4pID8A== --------------ms472127EEB42963A99204F343-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Sep 29 15: 8:45 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from server.baldwin.cx (jobaldwi.campus.vt.edu [198.82.67.146]) by hub.freebsd.org (Postfix) with ESMTP id E388914D95 for ; Wed, 29 Sep 1999 15:08:42 -0700 (PDT) (envelope-from jobaldwi@vt.edu) Received: from john.baldwin.cx (john [10.0.0.2]) by server.baldwin.cx (8.9.3/8.9.3) with ESMTP id SAA96192; Wed, 29 Sep 1999 18:08:58 -0400 (EDT) (envelope-from jobaldwi@vt.edu) Message-Id: <199909292208.SAA96192@server.baldwin.cx> X-Mailer: XFMail 1.3.1 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <199909292018.QAA79832@server.baldwin.cx> Date: Wed, 29 Sep 1999 18:08:58 -0400 (EDT) From: John Baldwin To: "Ronald G. Minnich" Subject: RE: return to real mode Cc: hackers@freebsd.org Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 29-Sep-99 John Baldwin wrote: > GROUP CodeGroup _TEXT32, _TEXT16 > > ASSUME CS:CodeGroup, DS:_PMDATA > > .... > > SEGMENT _TEXT32 Byte Public Use32 'CODE' > > .... > > db 0EAh > dd OFFSET ExitPM > dw Sel_CS16 Here's the missing comment for the above: ; jmp far ExitPM > This code has been tested (and works) on 386, 386, and Pentium. > Presumably it should work on later chips as well. Should read: "386, 486, and Pentium..." ^^^ --- John Baldwin -- http://www.cslab.vt.edu/~jobaldwi/ PGP Key: http://www.cslab.vt.edu/~jobaldwi/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Sep 29 16: 5:21 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from cx344940-a.meta1.la.home.com (cx344940-a.meta1.la.home.com [24.6.21.74]) by hub.freebsd.org (Postfix) with ESMTP id 9284914E0C for ; Wed, 29 Sep 1999 16:05:09 -0700 (PDT) (envelope-from conrads@cx344940-a.meta1.la.home.com) Received: (from conrads@localhost) by cx344940-a.meta1.la.home.com (8.9.3/8.9.2) id SAA40614; Wed, 29 Sep 1999 18:04:57 -0500 (CDT) (envelope-from conrads) Message-ID: X-Mailer: XFMail 1.3.2pre1 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Wed, 29 Sep 1999 18:04:56 -0500 (CDT) Organization: @Home Network From: Conrad Sabatier To: Christian Carstensen Subject: RE: updating packages automatically, etc.pp. Cc: mns@metathink.com, freebsd-hackers@FreeBSD.ORG Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 28-Sep-99 Christian Carstensen wrote: > > so far, so good, > > first of all, thanks for giving me this much input on my idea. > i've had a look at the pkg_version tool, which, with Nik Clayton's > patch, does more or less what i've been thinking of, when i decided > to post the initial message to this list. as Mark Shepard > discussed in detail, there are a lot of useful features, > pkg_version is still lacking. (mark, special thanks to you for > taking down these useful notes!) i'm interested in implementing > at least some of this functionality using perl, if enough of you > regard this as a useful tool for system admin. otherwise, i'll > put it on the stack of things to do, when nothing else has to > done ;) how do you think about it? Here's a simple little Bourne shell script I threw together the other day to automatically upgrade installed ports. I've already used it myself, and it works just as expected. The script relies on you having an up-to-date INDEX file; do "make index" first to be sure (which reminds me, why is the INDEX file always out of sync after a cvsup?). It only tries to upgrade ports which have a single version installed, basically because I haven't gotten around yet to handling the parsing of pkg_version's output where more than one version of a port is installed. :-) The script checks to make sure that the new version builds successfully and is ready to be installed before deleting the old version (the reason for all those "&&" thingies). It should probably also check to see whether a port is interactive or not, but that's another thing I have yet to do. :-) Ignore the line wrap, by the way: #!/bin/sh for old_pkg in `pkg_version -v | grep '<' | awk '{print $1}'` do new_pkg=`echo $old_pkg | sed 's/-[0-9].*$//'` echo Upgrading $old_pkg cd /usr/ports/*/${new_pkg} && make && pkg_delete -f $old_pkg && make install clean done -- Conrad Sabatier http://members.home.net/conrads/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Sep 29 16:46:54 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from dorifer.heim3.tu-clausthal.de (dorifer.heim3.tu-clausthal.de [139.174.243.252]) by hub.freebsd.org (Postfix) with ESMTP id 10D5B1515B for ; Wed, 29 Sep 1999 16:46:44 -0700 (PDT) (envelope-from olli@dorifer.heim3.tu-clausthal.de) Received: (from olli@localhost) by dorifer.heim3.tu-clausthal.de (8.8.8/8.8.8) id BAA03499 for freebsd-hackers@FreeBSD.ORG; Thu, 30 Sep 1999 01:46:41 +0200 (CEST) (envelope-from olli) Date: Thu, 30 Sep 1999 01:46:41 +0200 (CEST) From: Oliver Fromme Message-Id: <199909292346.BAA03499@dorifer.heim3.tu-clausthal.de> To: freebsd-hackers@FreeBSD.ORG Subject: Re: 2.88Mb floppies Organization: Administration Heim 3 Reply-To: freebsd-hackers@FreeBSD.ORG MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Newsreader: TIN [version 1.2 RZTUC(3) PL2] Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Wilko Bulte wrote in list.freebsd-hackers: > As Doug Rabson wrote ... > > On Mon, 27 Sep 1999, Wilko Bulte wrote: > > > static struct fd_type fd_types[NUMTYPES] = > > > { > > > { 21,2,0xFF,0x04,82,3444,1,FDC_500KBPS,2,0x0C,2 }, /* 1.72M in HD 3.5in */ > > > { 18,2,0xFF,0x1B,82,2952,1,FDC_500KBPS,2,0x6C,1 }, /* 1.48M in HD 3.5in */ > > > { 18,2,0xFF,0x1B,80,2880,1,FDC_500KBPS,2,0x6C,1 }, /* 1.44M in HD 3.5in */ > > > > I have no idea whether that driver can cope with 2.88mb floppies to be > > honest. There is only one way to find out... > > Right. I'll give it a try asap. Somebody sent me a sample entry to > add to fd_type. But I want to do a bit of study on the fd source to see > if I can understand what all the fields mean. I once programmed low-level FDC stuff under DOS, so I'm a bit familiar with this... The difference between 1.44 and 2.88 Mb floppies is that the latter use 36 sectors per track and twice the data rate (1 MBit/s). So the entry should look like this: {36, 2, 0xff, 0x1b, 80, 5760, 1, FDC_125KBPS, 2, 0x6c, 1} Actually, there should be a #define FDC_1MBPS FDC_125KBPS Regards Oliver -- Oliver Fromme, Leibnizstr. 18/61, 38678 Clausthal, Germany (Info: finger userinfo:olli@dorifer.heim3.tu-clausthal.de) "In jedem Stück Kohle wartet ein Diamant auf seine Geburt" (Terry Pratchett) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Sep 29 17:48:15 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from xylan.com (postal.xylan.com [208.8.0.248]) by hub.freebsd.org (Postfix) with ESMTP id BD2A215264 for ; Wed, 29 Sep 1999 17:48:07 -0700 (PDT) (envelope-from wes@softweyr.com) Received: from mailhub.xylan.com by xylan.com (8.8.7/SMI-SVR4 (ind.alcatel.com 2.3 [OUT])) id RAA28207; Wed, 29 Sep 1999 17:48:04 -0700 (PDT) Received: from omni.xylan.com by mailhub.xylan.com (SMI-8.6/SMI-SVR4 (mailhub 2.1 [HUB])) id RAA16876; Wed, 29 Sep 1999 17:48:04 -0700 Received: from softweyr.com (dyn0.utah.xylan.com) by omni.xylan.com (4.1/SMI-4.1 (xylan engr [SPOOL])) id AA08623; Wed, 29 Sep 99 17:47:56 PDT Message-Id: <37F2B342.39A37A04@softweyr.com> Date: Wed, 29 Sep 1999 18:48:02 -0600 From: Wes Peters Organization: Softweyr LLC X-Mailer: Mozilla 4.5 [en] (X11; U; FreeBSD 3.1-RELEASE i386) X-Accept-Language: en Mime-Version: 1.0 To: David Gilbert Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: PPPoE offer. References: <14322.15597.505566.676863@trooper.velocet.ca> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG David Gilbert wrote: > > I've got some real $$$ available to encourage someone to make PPPoE > work efficiently enough on the FreeBSD platform to handle a > substantial number of users. Is anyone interested? Brian? ;^) -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC wes@softweyr.com http://softweyr.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Sep 29 18:40:48 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from nomis.simon-shapiro.org (nomis.simon-shapiro.org [209.86.126.163]) by hub.freebsd.org (Postfix) with SMTP id 0B9B614E0B for ; Wed, 29 Sep 1999 18:40:35 -0700 (PDT) (envelope-from shimon@simon-shapiro.org) Received: (qmail 23079 invoked from network); 30 Sep 1999 01:40:31 -0000 Received: from localhost.simon-shapiro.org (HELO simon-shapiro.org) (127.0.0.1) by localhost.simon-shapiro.org with SMTP; 30 Sep 1999 01:40:31 -0000 Message-ID: <37F2BF8F.820F951F@simon-shapiro.org> Date: Wed, 29 Sep 1999 21:40:31 -0400 From: Simon Shapiro as Himself Organization: Simon's Garage X-Mailer: Mozilla 4.6 [en] (X11; I; FreeBSD 3.3-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: hackers@freebsd.org Subject: Kernel Printf and unsigned long long Content-Type: multipart/signed; protocol="application/x-pkcs7-signature"; micalg=sha1; boundary="------------msE89C93D0ADBE9950375779B8" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a cryptographically signed message in MIME format. --------------msE89C93D0ADBE9950375779B8 Content-Type: text/plain; charset= Content-Transfer-Encoding: 7bit Well, assume u_int64_t foo = ~0; printf("Foo is equal %qx\n", produces Foo is equal %qx And printf("Foo is equal %x\n"); produces: ../../i2o/i2o_drv.c:1260: warning: unsigned int format, different type arg (arg 4) You are damned if you do and damned if you don't :-) What is the official correct way to handle this? RELENG_3, i386 CURRENT Alpha -- Sincerely Yours, Shimon@Simon-Shapiro.ORG 404.644.6401 Simon Shapiro Unwritten code has no bugs and executes at twice the speed of mouth --------------msE89C93D0ADBE9950375779B8 Content-Type: application/x-pkcs7-signature; name="smime.p7s" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="smime.p7s" Content-Description: S/MIME Cryptographic Signature MIIJ7QYJKoZIhvcNAQcCoIIJ3jCCCdoCAQExCzAJBgUrDgMCGgUAMAsGCSqGSIb3DQEHAaCC B+8wggS5MIIEIqADAgECAhAClV7YnhihCwqregXjjrdfMA0GCSqGSIb3DQEBBAUAMIHMMRcw FQYDVQQKEw5WZXJpU2lnbiwgSW5jLjEfMB0GA1UECxMWVmVyaVNpZ24gVHJ1c3QgTmV0d29y azFGMEQGA1UECxM9d3d3LnZlcmlzaWduLmNvbS9yZXBvc2l0b3J5L1JQQSBJbmNvcnAuIEJ5 IFJlZi4sTElBQi5MVEQoYyk5ODFIMEYGA1UEAxM/VmVyaVNpZ24gQ2xhc3MgMSBDQSBJbmRp dmlkdWFsIFN1YnNjcmliZXItUGVyc29uYSBOb3QgVmFsaWRhdGVkMB4XDTk5MDkyNjAwMDAw MFoXDTAwMDkyNTIzNTk1OVowggEYMRcwFQYDVQQKEw5WZXJpU2lnbiwgSW5jLjEfMB0GA1UE CxMWVmVyaVNpZ24gVHJ1c3QgTmV0d29yazFGMEQGA1UECxM9d3d3LnZlcmlzaWduLmNvbS9y ZXBvc2l0b3J5L1JQQSBJbmNvcnAuIGJ5IFJlZi4sTElBQi5MVEQoYyk5ODEeMBwGA1UECxMV UGVyc29uYSBOb3QgVmFsaWRhdGVkMTMwMQYDVQQLEypEaWdpdGFsIElEIENsYXNzIDEgLSBO ZXRzY2FwZSBGdWxsIFNlcnZpY2UxFjAUBgNVBAMUDVNpbW9uIFNoYXBpcm8xJzAlBgkqhkiG 9w0BCQEWGHNoaW1vbkBzaW1vbi1zaGFwaXJvLm9yZzBcMA0GCSqGSIb3DQEBAQUAA0sAMEgC QQCWapJrHdDp0fdP9CDHrTEk6VbRBTk+X3UtU97HWiZooLH/Yp3//NmneAUOsjRj4kHygf3n LNqmQE040B3QdNQzAgMBAAGjggGPMIIBizAJBgNVHRMEAjAAMIGsBgNVHSAEgaQwgaEwgZ4G C2CGSAGG+EUBBwEBMIGOMCgGCCsGAQUFBwIBFhxodHRwczovL3d3dy52ZXJpc2lnbi5jb20v Q1BTMGIGCCsGAQUFBwICMFYwFRYOVmVyaVNpZ24sIEluYy4wAwIBARo9VmVyaVNpZ24ncyBD UFMgaW5jb3JwLiBieSByZWZlcmVuY2UgbGlhYi4gbHRkLiAoYyk5NyBWZXJpU2lnbjARBglg hkgBhvhCAQEEBAMCB4AwgYYGCmCGSAGG+EUBBgMEeBZ2ZDQ2NTJiZDYzZjIwNDcwMjkyOTg3 NjNjOWQyZjI3NTA2OWM3MzU5YmVkMWIwNTlkYTc1YmM0YmM5NzAxNzQ3ZGE1ZDNmMjE0MWJl YWRiMmJkMmU4OTIxNWFkNmFmNGQ1MTE0ODllYTJiMjQ3ZmRmM2VhNDUwYzAzBgNVHR8ELDAq MCigJqAkhiJodHRwOi8vY3JsLnZlcmlzaWduLmNvbS9jbGFzczEuY3JsMA0GCSqGSIb3DQEB BAUAA4GBAJGOv032Cr1u64/mnEHi0uKZb6uS4GQbed8jzBVRs+Y7zruO4R/gnXBEH0OrvE4Z oTqZ00gjnbVCT/rpjARmswNOU+hFI/kcn+HyKS0fw1A9Ppfm8Mp9iHSkYgTRT/MOuC2ck7z5 POETXZ68J14y368tXGd+Ako2n3RNHqOuSmXUMIIDLjCCApegAwIBAgIRANJ2Lo0UDD19sqgl Xa/uDXUwDQYJKoZIhvcNAQECBQAwXzELMAkGA1UEBhMCVVMxFzAVBgNVBAoTDlZlcmlTaWdu LCBJbmMuMTcwNQYDVQQLEy5DbGFzcyAxIFB1YmxpYyBQcmltYXJ5IENlcnRpZmljYXRpb24g QXV0aG9yaXR5MB4XDTk4MDUxMjAwMDAwMFoXDTA4MDUxMjIzNTk1OVowgcwxFzAVBgNVBAoT DlZlcmlTaWduLCBJbmMuMR8wHQYDVQQLExZWZXJpU2lnbiBUcnVzdCBOZXR3b3JrMUYwRAYD VQQLEz13d3cudmVyaXNpZ24uY29tL3JlcG9zaXRvcnkvUlBBIEluY29ycC4gQnkgUmVmLixM SUFCLkxURChjKTk4MUgwRgYDVQQDEz9WZXJpU2lnbiBDbGFzcyAxIENBIEluZGl2aWR1YWwg U3Vic2NyaWJlci1QZXJzb25hIE5vdCBWYWxpZGF0ZWQwgZ8wDQYJKoZIhvcNAQEBBQADgY0A MIGJAoGBALtaRIoEFrtV/QN6ii2UTxV4NrgNSrJvnFS/vOh3Kp258Gi7ldkxQXB6gUu5SBNW LccI4YRCq8CikqtEXKpC8IIOAukv+8I7u77JJwpdtrA2QjO1blSIT4dKvxna+RXoD4e2HOPM xpqOf2okkuP84GW6p7F+78nbN2rISsgJBuSZAgMBAAGjfDB6MBEGCWCGSAGG+EIBAQQEAwIB BjBHBgNVHSAEQDA+MDwGC2CGSAGG+EUBBwEBMC0wKwYIKwYBBQUHAgEWH3d3dy52ZXJpc2ln bi5jb20vcmVwb3NpdG9yeS9SUEEwDwYDVR0TBAgwBgEB/wIBADALBgNVHQ8EBAMCAQYwDQYJ KoZIhvcNAQECBQADgYEAiLg3O93alDcAraqf4YEBcR6Sam0v9vGd08pkONwbmAwHhluFFWoP uUmFpJXxF31ntH8tLN2aQp7DPrSOquULBt7yVir6M8e+GddTTMO9yOMXtaRJQmPswqYXD11Y Gkk8kFxVo2UgAP0YIOVfgqaxqJLFWGrBjQM868PNBaKQrm4xggHGMIIBwgIBATCB4TCBzDEX MBUGA1UEChMOVmVyaVNpZ24sIEluYy4xHzAdBgNVBAsTFlZlcmlTaWduIFRydXN0IE5ldHdv cmsxRjBEBgNVBAsTPXd3dy52ZXJpc2lnbi5jb20vcmVwb3NpdG9yeS9SUEEgSW5jb3JwLiBC eSBSZWYuLExJQUIuTFREKGMpOTgxSDBGBgNVBAMTP1ZlcmlTaWduIENsYXNzIDEgQ0EgSW5k aXZpZHVhbCBTdWJzY3JpYmVyLVBlcnNvbmEgTm90IFZhbGlkYXRlZAIQApVe2J4YoQsKq3oF 4463XzAJBgUrDgMCGgUAoH0wGAYJKoZIhvcNAQkDMQsGCSqGSIb3DQEHATAcBgkqhkiG9w0B CQUxDxcNOTkwOTMwMDE0MDMxWjAeBgkqhkiG9w0BCQ8xETAPMA0GCCqGSIb3DQMCAgEoMCMG CSqGSIb3DQEJBDEWBBTw7cZqEyJ9wjbMmL/UKEEp5JchEzANBgkqhkiG9w0BAQEFAARAcFNe Mst7fILuoSJancyYKc5+5jGyviO9T4C6F1qie890/e4e4oCHyESrvej62oy6xbOMg3qPpJ8C 1J6W0OItsA== --------------msE89C93D0ADBE9950375779B8-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Sep 29 18:41:13 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from lion.butya.kz (butya-gw.butya.kz [194.87.112.252]) by hub.freebsd.org (Postfix) with ESMTP id 56D1C1551A for ; Wed, 29 Sep 1999 18:41:00 -0700 (PDT) (envelope-from bp@butya.kz) Received: from bp (helo=localhost) by lion.butya.kz with local-esmtp (Exim 2.12 #1) id 11WVD5-000DxY-00; Thu, 30 Sep 1999 08:40:39 +0700 Date: Thu, 30 Sep 1999 08:40:39 +0700 (ALMST) From: Boris Popov To: Brian Mitchell Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: KLD dependencies In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 29 Sep 1999, Brian Mitchell wrote: > How do I specify dependencies in modules? I can find no documentation on > this, is it done automatically (doubtful)? You need to add variable KMODDEPS=modulename to KLD makefile. This will generate dependency on 'modulename'. -- Boris Popov http://www.butya.kz/~bp/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Sep 29 19:17:22 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by hub.freebsd.org (Postfix) with ESMTP id 79CBB15983; Wed, 29 Sep 1999 19:17:03 -0700 (PDT) (envelope-from grog@freebie.lemis.com) Received: (from grog@localhost) by freebie.lemis.com (8.9.3/8.9.0) id LAA84978; Thu, 30 Sep 1999 11:48:29 +0930 (CST) Date: Thu, 30 Sep 1999 11:48:28 +0930 From: Greg Lehey To: FreeBSD Questions , FreeBSD Hackers Subject: HEADS UP! Problems upgrading Vinum to 3.3-RELEASE Message-ID: <19990930114828.A488@freebie.lemis.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i WWW-Home-Page: http://www.lemis.com/~grog X-PGP-Fingerprint: 6B 7B C3 8C 61 CD 54 AF 13 24 52 F8 6D A4 95 EF Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've just found and fixed a bug in Vinum which can cause the system to crash on start. It didn't exist in 3.2, and is fixed in 3.3-STABLE. Briefly, 3.3 now allows you to put Vinum drives on any partition on any slice, and it checks these slices on start. If you don't have any slice entries (/dev/da0s1a and friends), however, it will panic after (incorrectly) reporting some subdisks to be crashed. This bug does not cause data corruption. This bug has been fixed in 3.3-STABLE. A copy of the kld is available at ftp://ftp.lemis.com/pub/vinum/vinum.ko-3.3-STABLE-30Sep1999. Note also that when upgrading from FreeBSD 3.2 to FreeBSD 3.3, you must ensure that your Vinum drives are of type Vinum. disklabel(8) should show: 3 partitions: # size offset fstype [fsize bsize bps/cpg] a: 2048000 0 vinum # (Cyl. 0 - 1042) c: 2048000 0 unused 0 0 # (Cyl. 0 - 1042) If your partition is of type 'unused', change it with 'disklabel -e'. To find out about current bugs in Vinum, see http://www.lemis.com/vinum/bugs.html. Greg -- When replying to this message, please copy the original recipients. For more information, see http://www.lemis.com/questions.html See complete headers for address, home page and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Sep 29 19:35: 8 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from nomis.simon-shapiro.org (nomis.simon-shapiro.org [209.86.126.163]) by hub.freebsd.org (Postfix) with SMTP id 3A8A314D4A for ; Wed, 29 Sep 1999 19:34:55 -0700 (PDT) (envelope-from shimon@simon-shapiro.org) Received: (qmail 23926 invoked from network); 30 Sep 1999 02:34:55 -0000 Received: from localhost.simon-shapiro.org (HELO simon-shapiro.org) (127.0.0.1) by localhost.simon-shapiro.org with SMTP; 30 Sep 1999 02:34:55 -0000 Message-ID: <37F2CC4F.DE308A4B@simon-shapiro.org> Date: Wed, 29 Sep 1999 22:34:55 -0400 From: Simon Shapiro as Himself Organization: Simon's Garage X-Mailer: Mozilla 4.6 [en] (X11; I; FreeBSD 3.3-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: hackers@freebsd.org Subject: Re: SYSINIT question References: <37F285DF.46A239B4@simon-shapiro.org> Content-Type: multipart/signed; protocol="application/x-pkcs7-signature"; micalg=sha1; boundary="------------ms075C1DB599B942E75F2AA0C7" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a cryptographically signed message in MIME format. --------------ms075C1DB599B942E75F2AA0C7 Content-Type: text/plain; charset= Content-Transfer-Encoding: 7bit Simon Shapiro as Himself wrote: RTFM. sys/kernel.h Sorry! > > Hi Y'll > > Am noticing that adding: > > SYSINIT(i2o_dev, SI_SUB_DRIVERS, SI_ORDER_MIDDLE+CDEV_MAJOR, > i2o_drvinit, NULL) > > to one's driver causes the init routine (i2o_drvinit to run very early, > as in: > > real memory = 402653184 (393216K bytes) > avail memory = 388120576 (379024K bytes) > Preloaded elf kernel "kernel.i2o" at 0xc034d000. > register_swi > Pentium Pro MTRR support enabled > ../../i2o/i2o_drv.c.1063 drvinit > I2O: Trying to initialize too early > Probing for devices on PCI bus 0: > > While I really would like it to run AFETR the PCI scan, so that I have > IOPs > to talk to etc., > > Other than ugly hacs in main(), is there a way? > > This is all in RELENG_3... > > -- > > Sincerely Yours, Shimon@Simon-Shapiro.ORG > 404.644.6401 > Simon Shapiro > > Unwritten code has no bugs and executes at twice the speed of mouth -- Sincerely Yours, Shimon@Simon-Shapiro.ORG 404.644.6401 Simon Shapiro Unwritten code has no bugs and executes at twice the speed of mouth --------------ms075C1DB599B942E75F2AA0C7 Content-Type: application/x-pkcs7-signature; name="smime.p7s" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="smime.p7s" Content-Description: S/MIME Cryptographic Signature MIIJ7QYJKoZIhvcNAQcCoIIJ3jCCCdoCAQExCzAJBgUrDgMCGgUAMAsGCSqGSIb3DQEHAaCC B+8wggS5MIIEIqADAgECAhAClV7YnhihCwqregXjjrdfMA0GCSqGSIb3DQEBBAUAMIHMMRcw FQYDVQQKEw5WZXJpU2lnbiwgSW5jLjEfMB0GA1UECxMWVmVyaVNpZ24gVHJ1c3QgTmV0d29y azFGMEQGA1UECxM9d3d3LnZlcmlzaWduLmNvbS9yZXBvc2l0b3J5L1JQQSBJbmNvcnAuIEJ5 IFJlZi4sTElBQi5MVEQoYyk5ODFIMEYGA1UEAxM/VmVyaVNpZ24gQ2xhc3MgMSBDQSBJbmRp dmlkdWFsIFN1YnNjcmliZXItUGVyc29uYSBOb3QgVmFsaWRhdGVkMB4XDTk5MDkyNjAwMDAw MFoXDTAwMDkyNTIzNTk1OVowggEYMRcwFQYDVQQKEw5WZXJpU2lnbiwgSW5jLjEfMB0GA1UE CxMWVmVyaVNpZ24gVHJ1c3QgTmV0d29yazFGMEQGA1UECxM9d3d3LnZlcmlzaWduLmNvbS9y ZXBvc2l0b3J5L1JQQSBJbmNvcnAuIGJ5IFJlZi4sTElBQi5MVEQoYyk5ODEeMBwGA1UECxMV UGVyc29uYSBOb3QgVmFsaWRhdGVkMTMwMQYDVQQLEypEaWdpdGFsIElEIENsYXNzIDEgLSBO ZXRzY2FwZSBGdWxsIFNlcnZpY2UxFjAUBgNVBAMUDVNpbW9uIFNoYXBpcm8xJzAlBgkqhkiG 9w0BCQEWGHNoaW1vbkBzaW1vbi1zaGFwaXJvLm9yZzBcMA0GCSqGSIb3DQEBAQUAA0sAMEgC QQCWapJrHdDp0fdP9CDHrTEk6VbRBTk+X3UtU97HWiZooLH/Yp3//NmneAUOsjRj4kHygf3n LNqmQE040B3QdNQzAgMBAAGjggGPMIIBizAJBgNVHRMEAjAAMIGsBgNVHSAEgaQwgaEwgZ4G C2CGSAGG+EUBBwEBMIGOMCgGCCsGAQUFBwIBFhxodHRwczovL3d3dy52ZXJpc2lnbi5jb20v Q1BTMGIGCCsGAQUFBwICMFYwFRYOVmVyaVNpZ24sIEluYy4wAwIBARo9VmVyaVNpZ24ncyBD UFMgaW5jb3JwLiBieSByZWZlcmVuY2UgbGlhYi4gbHRkLiAoYyk5NyBWZXJpU2lnbjARBglg hkgBhvhCAQEEBAMCB4AwgYYGCmCGSAGG+EUBBgMEeBZ2ZDQ2NTJiZDYzZjIwNDcwMjkyOTg3 NjNjOWQyZjI3NTA2OWM3MzU5YmVkMWIwNTlkYTc1YmM0YmM5NzAxNzQ3ZGE1ZDNmMjE0MWJl YWRiMmJkMmU4OTIxNWFkNmFmNGQ1MTE0ODllYTJiMjQ3ZmRmM2VhNDUwYzAzBgNVHR8ELDAq MCigJqAkhiJodHRwOi8vY3JsLnZlcmlzaWduLmNvbS9jbGFzczEuY3JsMA0GCSqGSIb3DQEB BAUAA4GBAJGOv032Cr1u64/mnEHi0uKZb6uS4GQbed8jzBVRs+Y7zruO4R/gnXBEH0OrvE4Z oTqZ00gjnbVCT/rpjARmswNOU+hFI/kcn+HyKS0fw1A9Ppfm8Mp9iHSkYgTRT/MOuC2ck7z5 POETXZ68J14y368tXGd+Ako2n3RNHqOuSmXUMIIDLjCCApegAwIBAgIRANJ2Lo0UDD19sqgl Xa/uDXUwDQYJKoZIhvcNAQECBQAwXzELMAkGA1UEBhMCVVMxFzAVBgNVBAoTDlZlcmlTaWdu LCBJbmMuMTcwNQYDVQQLEy5DbGFzcyAxIFB1YmxpYyBQcmltYXJ5IENlcnRpZmljYXRpb24g QXV0aG9yaXR5MB4XDTk4MDUxMjAwMDAwMFoXDTA4MDUxMjIzNTk1OVowgcwxFzAVBgNVBAoT DlZlcmlTaWduLCBJbmMuMR8wHQYDVQQLExZWZXJpU2lnbiBUcnVzdCBOZXR3b3JrMUYwRAYD VQQLEz13d3cudmVyaXNpZ24uY29tL3JlcG9zaXRvcnkvUlBBIEluY29ycC4gQnkgUmVmLixM SUFCLkxURChjKTk4MUgwRgYDVQQDEz9WZXJpU2lnbiBDbGFzcyAxIENBIEluZGl2aWR1YWwg U3Vic2NyaWJlci1QZXJzb25hIE5vdCBWYWxpZGF0ZWQwgZ8wDQYJKoZIhvcNAQEBBQADgY0A MIGJAoGBALtaRIoEFrtV/QN6ii2UTxV4NrgNSrJvnFS/vOh3Kp258Gi7ldkxQXB6gUu5SBNW LccI4YRCq8CikqtEXKpC8IIOAukv+8I7u77JJwpdtrA2QjO1blSIT4dKvxna+RXoD4e2HOPM xpqOf2okkuP84GW6p7F+78nbN2rISsgJBuSZAgMBAAGjfDB6MBEGCWCGSAGG+EIBAQQEAwIB BjBHBgNVHSAEQDA+MDwGC2CGSAGG+EUBBwEBMC0wKwYIKwYBBQUHAgEWH3d3dy52ZXJpc2ln bi5jb20vcmVwb3NpdG9yeS9SUEEwDwYDVR0TBAgwBgEB/wIBADALBgNVHQ8EBAMCAQYwDQYJ KoZIhvcNAQECBQADgYEAiLg3O93alDcAraqf4YEBcR6Sam0v9vGd08pkONwbmAwHhluFFWoP uUmFpJXxF31ntH8tLN2aQp7DPrSOquULBt7yVir6M8e+GddTTMO9yOMXtaRJQmPswqYXD11Y Gkk8kFxVo2UgAP0YIOVfgqaxqJLFWGrBjQM868PNBaKQrm4xggHGMIIBwgIBATCB4TCBzDEX MBUGA1UEChMOVmVyaVNpZ24sIEluYy4xHzAdBgNVBAsTFlZlcmlTaWduIFRydXN0IE5ldHdv cmsxRjBEBgNVBAsTPXd3dy52ZXJpc2lnbi5jb20vcmVwb3NpdG9yeS9SUEEgSW5jb3JwLiBC eSBSZWYuLExJQUIuTFREKGMpOTgxSDBGBgNVBAMTP1ZlcmlTaWduIENsYXNzIDEgQ0EgSW5k aXZpZHVhbCBTdWJzY3JpYmVyLVBlcnNvbmEgTm90IFZhbGlkYXRlZAIQApVe2J4YoQsKq3oF 4463XzAJBgUrDgMCGgUAoH0wGAYJKoZIhvcNAQkDMQsGCSqGSIb3DQEHATAcBgkqhkiG9w0B CQUxDxcNOTkwOTMwMDIzNDU1WjAeBgkqhkiG9w0BCQ8xETAPMA0GCCqGSIb3DQMCAgEoMCMG CSqGSIb3DQEJBDEWBBSRmBzXNo5LyuVaNO3MSvOFZC3glzANBgkqhkiG9w0BAQEFAARAa+7M Gkgmpbmo4LUtohiW9c7nEBLfDxnyyNQRAJHdaE0EMHV68anA40sdAVBP5P95bRjp71jge+NU /xYf50xbwg== --------------ms075C1DB599B942E75F2AA0C7-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Sep 29 19:39:24 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from nomis.simon-shapiro.org (nomis.simon-shapiro.org [209.86.126.163]) by hub.freebsd.org (Postfix) with SMTP id AC22E155A1 for ; Wed, 29 Sep 1999 19:37:35 -0700 (PDT) (envelope-from shimon@simon-shapiro.org) Received: (qmail 23957 invoked from network); 30 Sep 1999 02:37:34 -0000 Received: from localhost.simon-shapiro.org (HELO simon-shapiro.org) (127.0.0.1) by localhost.simon-shapiro.org with SMTP; 30 Sep 1999 02:37:34 -0000 Message-ID: <37F2CCEE.9F2DF6DF@simon-shapiro.org> Date: Wed, 29 Sep 1999 22:37:34 -0400 From: Simon Shapiro as Himself Organization: Simon's Garage X-Mailer: Mozilla 4.6 [en] (X11; I; FreeBSD 3.3-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: Rene de Vries Cc: Christoph Kukulies , FreeBSD hackers Subject: Re: de0 strangenesses References: <200009141810.UAA00578@canyon.demon.nl> Content-Type: multipart/signed; protocol="application/x-pkcs7-signature"; micalg=sha1; boundary="------------msA3427E48A6790D4688D9A101" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a cryptographically signed message in MIME format. --------------msA3427E48A6790D4688D9A101 Content-Type: text/plain; charset= Content-Transfer-Encoding: 7bit Rene de Vries wrote: > > I think i've got a similar problem. This involves a DE500 (de0 driver) > ethernet card and a 100 Mbit UTP. The problem was that somehow the driver > didn't detect the 100Mbit and always switched to 10Mbit. The workaround that > I use is a simple script "/etc/start_if.de0" with the following contents: > > # workaround 10/100Mbit start problem > ifconfig de0 192.168.1.2 media 100baseTX > ifconfig de0 down > sleep 2 > ifconfig de0 up > > Since I started using this script the machine always started with the > 100baseTX interface active. Not always. Some boards resist that, and yet others will hang the hub (or the switch port) they are plugged into. Those need to see a 100MHz beat before they do something useful. I.e. Do NOT have them the first to turn on on a hub. Most switches are OK. I suspect some differences between revisions... > > Rene > > > On a 3.0-current of October 1998 I'm having often trouble with de0. > > The machine often reboots over night (when either the locate db is built or > > some other big job - like mirror - is running). Anyway, after the reboot, > > often de0 is dead. > > > > This happend today again. When I came into the office I could not > > ping said machine. I sat at the console, logged in. The machine was > > perfectly alive, only the de0 interface didn't work at the BNC network. > > > > I did a ifconfig de0 down and exactly with doing that I got a kernel message > > from the driver: de0 BNC interface enabled (or something like that). > > Doing an ifconfig de0 up right after that the interface continued working > > at the BNC port. > > > > Can the driver writer(s) comment whether there have been changes to the driver > > WRT that behaviour so I can expect that with either 3.2 or -current > > the problem would be gone? > > -- > Rene de Vries http://www.tcja.nl/~rene; mailto:rene@tcja.nl > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message -- Sincerely Yours, Shimon@Simon-Shapiro.ORG 404.644.6401 Simon Shapiro Unwritten code has no bugs and executes at twice the speed of mouth --------------msA3427E48A6790D4688D9A101 Content-Type: application/x-pkcs7-signature; name="smime.p7s" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="smime.p7s" Content-Description: S/MIME Cryptographic Signature MIIJ7QYJKoZIhvcNAQcCoIIJ3jCCCdoCAQExCzAJBgUrDgMCGgUAMAsGCSqGSIb3DQEHAaCC B+8wggS5MIIEIqADAgECAhAClV7YnhihCwqregXjjrdfMA0GCSqGSIb3DQEBBAUAMIHMMRcw FQYDVQQKEw5WZXJpU2lnbiwgSW5jLjEfMB0GA1UECxMWVmVyaVNpZ24gVHJ1c3QgTmV0d29y azFGMEQGA1UECxM9d3d3LnZlcmlzaWduLmNvbS9yZXBvc2l0b3J5L1JQQSBJbmNvcnAuIEJ5 IFJlZi4sTElBQi5MVEQoYyk5ODFIMEYGA1UEAxM/VmVyaVNpZ24gQ2xhc3MgMSBDQSBJbmRp dmlkdWFsIFN1YnNjcmliZXItUGVyc29uYSBOb3QgVmFsaWRhdGVkMB4XDTk5MDkyNjAwMDAw MFoXDTAwMDkyNTIzNTk1OVowggEYMRcwFQYDVQQKEw5WZXJpU2lnbiwgSW5jLjEfMB0GA1UE CxMWVmVyaVNpZ24gVHJ1c3QgTmV0d29yazFGMEQGA1UECxM9d3d3LnZlcmlzaWduLmNvbS9y ZXBvc2l0b3J5L1JQQSBJbmNvcnAuIGJ5IFJlZi4sTElBQi5MVEQoYyk5ODEeMBwGA1UECxMV UGVyc29uYSBOb3QgVmFsaWRhdGVkMTMwMQYDVQQLEypEaWdpdGFsIElEIENsYXNzIDEgLSBO ZXRzY2FwZSBGdWxsIFNlcnZpY2UxFjAUBgNVBAMUDVNpbW9uIFNoYXBpcm8xJzAlBgkqhkiG 9w0BCQEWGHNoaW1vbkBzaW1vbi1zaGFwaXJvLm9yZzBcMA0GCSqGSIb3DQEBAQUAA0sAMEgC QQCWapJrHdDp0fdP9CDHrTEk6VbRBTk+X3UtU97HWiZooLH/Yp3//NmneAUOsjRj4kHygf3n LNqmQE040B3QdNQzAgMBAAGjggGPMIIBizAJBgNVHRMEAjAAMIGsBgNVHSAEgaQwgaEwgZ4G C2CGSAGG+EUBBwEBMIGOMCgGCCsGAQUFBwIBFhxodHRwczovL3d3dy52ZXJpc2lnbi5jb20v Q1BTMGIGCCsGAQUFBwICMFYwFRYOVmVyaVNpZ24sIEluYy4wAwIBARo9VmVyaVNpZ24ncyBD UFMgaW5jb3JwLiBieSByZWZlcmVuY2UgbGlhYi4gbHRkLiAoYyk5NyBWZXJpU2lnbjARBglg hkgBhvhCAQEEBAMCB4AwgYYGCmCGSAGG+EUBBgMEeBZ2ZDQ2NTJiZDYzZjIwNDcwMjkyOTg3 NjNjOWQyZjI3NTA2OWM3MzU5YmVkMWIwNTlkYTc1YmM0YmM5NzAxNzQ3ZGE1ZDNmMjE0MWJl YWRiMmJkMmU4OTIxNWFkNmFmNGQ1MTE0ODllYTJiMjQ3ZmRmM2VhNDUwYzAzBgNVHR8ELDAq MCigJqAkhiJodHRwOi8vY3JsLnZlcmlzaWduLmNvbS9jbGFzczEuY3JsMA0GCSqGSIb3DQEB BAUAA4GBAJGOv032Cr1u64/mnEHi0uKZb6uS4GQbed8jzBVRs+Y7zruO4R/gnXBEH0OrvE4Z oTqZ00gjnbVCT/rpjARmswNOU+hFI/kcn+HyKS0fw1A9Ppfm8Mp9iHSkYgTRT/MOuC2ck7z5 POETXZ68J14y368tXGd+Ako2n3RNHqOuSmXUMIIDLjCCApegAwIBAgIRANJ2Lo0UDD19sqgl Xa/uDXUwDQYJKoZIhvcNAQECBQAwXzELMAkGA1UEBhMCVVMxFzAVBgNVBAoTDlZlcmlTaWdu LCBJbmMuMTcwNQYDVQQLEy5DbGFzcyAxIFB1YmxpYyBQcmltYXJ5IENlcnRpZmljYXRpb24g QXV0aG9yaXR5MB4XDTk4MDUxMjAwMDAwMFoXDTA4MDUxMjIzNTk1OVowgcwxFzAVBgNVBAoT DlZlcmlTaWduLCBJbmMuMR8wHQYDVQQLExZWZXJpU2lnbiBUcnVzdCBOZXR3b3JrMUYwRAYD VQQLEz13d3cudmVyaXNpZ24uY29tL3JlcG9zaXRvcnkvUlBBIEluY29ycC4gQnkgUmVmLixM SUFCLkxURChjKTk4MUgwRgYDVQQDEz9WZXJpU2lnbiBDbGFzcyAxIENBIEluZGl2aWR1YWwg U3Vic2NyaWJlci1QZXJzb25hIE5vdCBWYWxpZGF0ZWQwgZ8wDQYJKoZIhvcNAQEBBQADgY0A MIGJAoGBALtaRIoEFrtV/QN6ii2UTxV4NrgNSrJvnFS/vOh3Kp258Gi7ldkxQXB6gUu5SBNW LccI4YRCq8CikqtEXKpC8IIOAukv+8I7u77JJwpdtrA2QjO1blSIT4dKvxna+RXoD4e2HOPM xpqOf2okkuP84GW6p7F+78nbN2rISsgJBuSZAgMBAAGjfDB6MBEGCWCGSAGG+EIBAQQEAwIB BjBHBgNVHSAEQDA+MDwGC2CGSAGG+EUBBwEBMC0wKwYIKwYBBQUHAgEWH3d3dy52ZXJpc2ln bi5jb20vcmVwb3NpdG9yeS9SUEEwDwYDVR0TBAgwBgEB/wIBADALBgNVHQ8EBAMCAQYwDQYJ KoZIhvcNAQECBQADgYEAiLg3O93alDcAraqf4YEBcR6Sam0v9vGd08pkONwbmAwHhluFFWoP uUmFpJXxF31ntH8tLN2aQp7DPrSOquULBt7yVir6M8e+GddTTMO9yOMXtaRJQmPswqYXD11Y Gkk8kFxVo2UgAP0YIOVfgqaxqJLFWGrBjQM868PNBaKQrm4xggHGMIIBwgIBATCB4TCBzDEX MBUGA1UEChMOVmVyaVNpZ24sIEluYy4xHzAdBgNVBAsTFlZlcmlTaWduIFRydXN0IE5ldHdv cmsxRjBEBgNVBAsTPXd3dy52ZXJpc2lnbi5jb20vcmVwb3NpdG9yeS9SUEEgSW5jb3JwLiBC eSBSZWYuLExJQUIuTFREKGMpOTgxSDBGBgNVBAMTP1ZlcmlTaWduIENsYXNzIDEgQ0EgSW5k aXZpZHVhbCBTdWJzY3JpYmVyLVBlcnNvbmEgTm90IFZhbGlkYXRlZAIQApVe2J4YoQsKq3oF 4463XzAJBgUrDgMCGgUAoH0wGAYJKoZIhvcNAQkDMQsGCSqGSIb3DQEHATAcBgkqhkiG9w0B CQUxDxcNOTkwOTMwMDIzNzM0WjAeBgkqhkiG9w0BCQ8xETAPMA0GCCqGSIb3DQMCAgEoMCMG CSqGSIb3DQEJBDEWBBQmDDo6edAB4kHP1SYCrwuxbFB3IzANBgkqhkiG9w0BAQEFAARAg33p m1+FjfOGSk46M1fnJY0u+uBmvSOnT3zSJLGuik7fr8+AEHSZcxy+yAAXMKdYD4S8+7K2mRH3 NzXZl4KdEQ== --------------msA3427E48A6790D4688D9A101-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Sep 29 19:47:57 1999 Delivered-To: freebsd-hackers@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 758) id 6516914D8E; Wed, 29 Sep 1999 19:47:51 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id 59E291CD464; Wed, 29 Sep 1999 19:47:50 -0700 (PDT) (envelope-from kris@hub.freebsd.org) Date: Wed, 29 Sep 1999 19:47:50 -0700 (PDT) From: Kris Kennaway To: Conrad Sabatier Cc: Christian Carstensen , mns@metathink.com, freebsd-hackers@FreeBSD.ORG Subject: RE: updating packages automatically, etc.pp. In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 29 Sep 1999, Conrad Sabatier wrote: > The script relies on you having an up-to-date INDEX file; do "make > index" first to be sure (which reminds me, why is the INDEX file > always out of sync after a cvsup?). It only tries to upgrade ports Because it's only generated periodically, not every time someone adds or modifies a port, which would be very wasteful. Kris To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Sep 29 19:52:30 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from pop3-3.enteract.com (pop3-3.enteract.com [207.229.143.32]) by hub.freebsd.org (Postfix) with SMTP id 8CCD514D43 for ; Wed, 29 Sep 1999 19:52:24 -0700 (PDT) (envelope-from jedi@enteract.com) Received: (qmail 7870 invoked from network); 30 Sep 1999 02:52:22 -0000 Received: from 207-229-172-61.d.enteract.com (HELO arrubin) (207.229.172.61) by pop3-3.enteract.com with SMTP; 30 Sep 1999 02:52:22 -0000 Message-ID: <004f01bf0aef$4384c760$010210ac@arrubin> From: "Anthony Rubin" To: , Subject: FreeBSD driver for DPT SmartRAID V Date: Wed, 29 Sep 1999 21:55:32 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2314.1300 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG With the release of the Linux driver for the DPT SmartRAID V cards I imagine it is just a matter of time before we have a FreeBSD driver. I sent the following message to DPT. >I know this may be a long shot, but here goes. What would be the >possibilites of a FreeBSD driver for your SmartRAID V series? I know one >will probably be created eventually now that you released your Linux driver >with source, but I was hoping for one in the next month or so that I could >purchase a SmartRAID V for use in a FreeBSD box that I have. Thanks in >advance. > >Anthony Rubin >jedi@enteract.com >Hoffman Estates, IL Anthony Rubin jedi@enteract.com Hoffman Estates, IL To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Sep 29 22: 7:23 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from teapot32.domain8.bigpond.com (teapot32.domain8.bigpond.com [139.134.5.180]) by hub.freebsd.org (Postfix) with SMTP id 35F3415015 for ; Wed, 29 Sep 1999 22:07:17 -0700 (PDT) (envelope-from tpnelson@echidna.stu.cowan.edu.au) Received: from localhost (localhost [127.0.0.1]) by teapot32.domain8.bigpond.com (NTMail 3.02.13) with ESMTP id ta967947 for ; Thu, 30 Sep 1999 15:04:42 +1000 Received: from WEBH-T-001-p-143-6.tmns.net.au ([139.134.143.6]) by mail8.bigpond.com (Claudes-Coppertone-MailRouter V2.5 17/2857591); 30 Sep 1999 15:04:42 Message-ID: <37F2F035.1EFCC779@echidna.stu.cowan.edu.au> Date: Thu, 30 Sep 1999 13:08:05 +0800 From: Trent Nelson X-Mailer: Mozilla 4.6 [en] (Win98; I) X-Accept-Language: en MIME-Version: 1.0 To: FreeBSD-hackers@FreeBSD.org Subject: Vinum/SoftUpdates query. Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I was planning on sending this to FreeBSD-newbies@, but due to the nature of the question, decided against it and sent it here. I currently have a 3.2GB Quantum HDD as my primary master, and an 8.4GB Quantum HDD as my primary slave. What I want to do is create an exact image of the 3.2GB drive as a partition on the 8.4GB drive, and basically set up vinum using this array of two 3.2GB drives/partitions. 1.) Is this possible? The 8.4GB HDD is about two years newer than the 3.2GB HDD which leads me to the understanding that there'd be obvious access time discrepancies. The main thing I'm interested in is the fact I won't have two 3.2GB HDDs, I'll have one 3.2GB HDD, and another drive with a 3.2GB partition on it. 2.) If it is possible, would the performance gain be worth the effort to get it working? Note, I'm more interested in the experience I'd get out of it rather than huge performance gains. 3.) Is it possible to get SoftUpdates working with vinum? Has anyone tried this? Thanks in advance. Regards, Trent. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Sep 29 22:37:35 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by hub.freebsd.org (Postfix) with ESMTP id E811C152D6; Wed, 29 Sep 1999 22:37:21 -0700 (PDT) (envelope-from grog@freebie.lemis.com) Received: (from grog@localhost) by freebie.lemis.com (8.9.3/8.9.0) id PAA18119; Thu, 30 Sep 1999 15:07:08 +0930 (CST) Date: Thu, 30 Sep 1999 15:07:07 +0930 From: Greg Lehey To: Trent Nelson Cc: FreeBSD Questions Subject: Re: Vinum/SoftUpdates query. Message-ID: <19990930150707.J496@freebie.lemis.com> References: <37F2F035.1EFCC779@echidna.stu.cowan.edu.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <37F2F035.1EFCC779@echidna.stu.cowan.edu.au>; from Trent Nelson on Thu, Sep 30, 1999 at 01:08:05PM +0800 WWW-Home-Page: http://www.lemis.com/~grog X-PGP-Fingerprint: 6B 7B C3 8C 61 CD 54 AF 13 24 52 F8 6D A4 95 EF Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [following up to -questions] On Thursday, 30 September 1999 at 13:08:05 +0800, Trent Nelson wrote: > Hi, > > I was planning on sending this to FreeBSD-newbies@, but due to the > nature of the question, decided against it and sent it here. You would have done better to send it to -questions. I'm following up there. > I currently have a 3.2GB Quantum HDD as my primary master, and > an 8.4GB Quantum HDD as my primary slave. What I want to do is > create an exact image of the 3.2GB drive as a partition on the 8.4GB > drive, and basically set up vinum using this array of two 3.2GB > drives/partitions. You should put it on the secondary controller. The performance will be much better. > 1.) Is this possible? Yes. > The 8.4GB HDD is about two years newer than the 3.2GB HDD which > leads me to the understanding that there'd be obvious access time > discrepancies. That's not so serious. Vinum doesn't make any assumptions about relative speed. Obviously overall performance will be less than that of two faster disks. > The main thing I'm interested in is the fact I won't have two 3.2GB > HDDs, I'll have one 3.2GB HDD, and another drive with a 3.2GB > partition on it. Well, you'll have as many Vinum volumes as you want. You can divide up the space just about any way you want. > 2.) If it is possible, would the performance gain be worth the effort > to get it working? Note, I'm more interested in the experience I'd get > out of it rather than huge performance gains. That depends on how much effort it takes you :-) > 3.) Is it possible to get SoftUpdates working with vinum? Yes. > Has anyone tried this? Yes. We're currently seeing some problems with soft updates in connection with RAID-5, but that's not of any great relevance to your system, since you need at least 3 disks for RAID-5. Greg -- When replying to this message, please copy the original recipients. For more information, see http://www.lemis.com/questions.html See complete headers for address, home page and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Sep 30 0:15: 9 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from rucus.ru.ac.za (rucus.ru.ac.za [146.231.29.2]) by hub.freebsd.org (Postfix) with SMTP id 82267159EF for ; Thu, 30 Sep 1999 00:14:59 -0700 (PDT) (envelope-from nbm@rucus.ru.ac.za) Received: (qmail 86951 invoked by uid 1003); 30 Sep 1999 07:17:06 -0000 Date: Thu, 30 Sep 1999 09:17:06 +0200 From: Neil Blakey-Milner To: Conrad Sabatier Cc: Christian Carstensen , mns@metathink.com, freebsd-hackers@FreeBSD.ORG Subject: Re: updating packages automatically, etc.pp. Message-ID: <19990930091706.A85599@rucus.ru.ac.za> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre2i In-Reply-To: Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed 1999-09-29 (18:04), Conrad Sabatier wrote: > It only tries to upgrade ports which have a single version installed, > basically because I haven't gotten around yet to handling the parsing > of pkg_version's output where more than one version of a port is > installed. :-) Patch at http://rucus.ru.ac.za/~nbm/pkg_version-patch > The script checks to make sure that the new version builds > successfully and is ready to be installed before deleting the old > version (the reason for all those "&&" thingies). There may be a problem if pkg_delete returns an error code if it is missing files, or something. You also lose if make install fails, which isn't very often, admittedly. One solution I've got working is running pkg_create using the information in /var/db/pkg/foo-1.0/ much like the fake-pkg target in ports. Then you can "make install clean || pkg_add foo-1.0" to make sure you at least get a working copy in the end. (This ties in with plans to make changing and upgrading ports back-out-able, which was mentioned as something nice we should aim for.) > It should probably also check to see > whether a port is interactive or not, but that's another thing I have > yet to do. :-) Ignore the line wrap, by the way: "make BATCH=1", instead of just "make". > #!/bin/sh > > for old_pkg in `pkg_version -v | grep '<' | awk '{print $1}'` > do > new_pkg=`echo $old_pkg | sed 's/-[0-9].*$//'` > > echo Upgrading $old_pkg > > cd /usr/ports/*/${new_pkg} && make && pkg_delete -f $old_pkg > && make install clean > done You also lose any "dependency" information, which isn't too great. You can find the directory of alternate version ports in /usr/ports/INDEX (much like pkg_version) - grep for the exact version specified in the return from pkg_version, and you pick up the correct ports directory as a bonus. Neil -- Neil Blakey-Milner nbm@rucus.ru.ac.za To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Sep 30 0:18:31 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from florence.pavilion.net (florence.pavilion.net [194.242.128.25]) by hub.freebsd.org (Postfix) with ESMTP id 387C2155C7 for ; Thu, 30 Sep 1999 00:18:22 -0700 (PDT) (envelope-from joe@florence.pavilion.net) Received: (from joe@localhost) by florence.pavilion.net (8.9.3/8.8.8) id IAA51163; Thu, 30 Sep 1999 08:18:16 +0100 (BST) (envelope-from joe) Date: Thu, 30 Sep 1999 08:18:16 +0100 From: Josef Karthauser To: Josh Tiefenbach Cc: David Gilbert , freebsd-hackers@FreeBSD.ORG Subject: Re: PPPoE offer. Message-ID: <19990930081816.K86792@florence.pavilion.net> References: <14322.15597.505566.676863@trooper.velocet.ca> <19990929211210.H86792@florence.pavilion.net> <19990929200309.A96281@zipperup.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre2i In-Reply-To: <19990929200309.A96281@zipperup.org> X-NCC-RegID: uk.pavilion Organisation: Pavilion Internet plc, 24 The Old Steine, Brighton, BN1 1EL, England Phone: +44-845-333-5000 Fax: +44-845-333-5001 Mobile: +44-403-596893 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Sep 29, 1999 at 08:03:09PM -0400, Josh Tiefenbach wrote: > > Dave, > > > > As far as I'm aware it _does_ work - in the form of user-ppp (/usr/sbin/ppp), > > maintained by Brian. Why do you need to use kernel ppp - it's a mess :) > > Really? I was under the impression that it doesnt. I'll have to go check the > -current code, but last I heard from Brian was that adding PPPoE to user-ppp > was problematic from a design standpoint, and that he'd have to contemplate it > a bit. I havent seen anything in the commit messages since to indicate that > he's added it. > > If he has, that'll mean my weekend project of adding client support will have > been obviated :) > > josh Maybe I've got it wrong then, but he can definitely use user-ppp to make ppp over IP tunnels - is PPPoE mac address to mac address connectivity? Joe -- Josef Karthauser FreeBSD: How many times have you booted today? Technical Manager Viagra for your server (http://www.uk.freebsd.org) Pavilion Internet plc. [joe@pavilion.net, joe@uk.freebsd.org, joe@tao.org.uk] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Sep 30 0:43:42 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from alpha.netvision.net.il (alpha.netvision.net.il [194.90.1.13]) by hub.freebsd.org (Postfix) with ESMTP id B7D0A14E8E; Thu, 30 Sep 1999 00:43:35 -0700 (PDT) (envelope-from danhil@cwnt.com) Received: from unspecified.host (RAS4-p71.hfa.netvision.net.il [62.0.146.199]) by alpha.netvision.net.il (8.9.3/8.8.6) with SMTP id JAA06083; Thu, 30 Sep 1999 09:43:30 +0200 (IST) Received: from 192.168.0.46 ([192.168.0.46]) by 192.168.0.1 (WinRoute 3.04g) with SMTP; Thu, 30 Sep 1999 09:41:14 +0200 Message-ID: <047c01bf0b1f$8c8b89f0$2e00a8c0@nt46daniel> From: "Daniel Hilevich" To: "Mark Tinguely" Cc: , References: <199909291710.MAA20873@plains.NoDak.edu> Subject: Re: A bug in the sppp driver? Date: Thu, 30 Sep 1999 09:41:11 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="windows-1255" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2014.211 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2014.211 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > When you trying to establish connection from one peer (local) to another > > (remote), you sent a CONF_REQ message to the remote peer. The remote peer > > should answer with a CONF_ACK message. In the code of the sppp driver > > (net/if_spppsubr.c, lines 1321 - 1357) you can see that the remote peer > > send's a CONF_ACK message to the local peer > > (in the line: rv = (cp->RCR)(sp, h, len);) but doesn't change it state to > > STATE_ACK_SENT (as I think it should do) . Further more, you can see that > > after you sent the configuration request, you are in state REQ_SENT. > the Receive Config Ack will cause you to state ACK_SENT on line 1327. > The case I was referring to is as follows: When you get the first CONF_REQ message from a remote peer, you are in STATE_INITIAL. The call to the RCR functions ends with the decision that the situation is legal and the return value is 1. The problem seems to be that no one changes the state from STATE_INITIAL to STATE_ACK_SENT. This way you won't reach line 1327. The fix (for my opinion) should be like this (line 1274) : .... rv = (cp->RCR)(sp, h, len); /* Daniel - fix */ if (rv && sp->state[cp->protoidx] == STATE_INITIAL) sppp_cp_change_state(cp, sp, STATE_ACK_SENT); sp->rst_counter[cp->protoidx] = sp->lcp.max_configure; /* End of fix */ switch (sp->state[cp->protoidx]) { case STATE_OPENED: ... Thanks for the help Daniel To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Sep 30 0:53:19 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from alpha.netvision.net.il (alpha.netvision.net.il [194.90.1.13]) by hub.freebsd.org (Postfix) with ESMTP id 2A69215148; Thu, 30 Sep 1999 00:53:01 -0700 (PDT) (envelope-from danhil@cwnt.com) Received: from unspecified.host (RAS4-p71.hfa.netvision.net.il [62.0.146.199]) by alpha.netvision.net.il (8.9.3/8.8.6) with SMTP id JAA13568; Thu, 30 Sep 1999 09:52:43 +0200 (IST) Received: from 192.168.0.46 ([192.168.0.46]) by 192.168.0.1 (WinRoute 3.04g) with SMTP; Thu, 30 Sep 1999 09:50:50 +0200 Message-ID: <049401bf0b20$e3621c20$2e00a8c0@nt46daniel> From: "Daniel Hilevich" To: "John Hay" Cc: , References: <199909291925.VAA65012@zibbi.mikom.csir.co.za> Subject: Re: A bug in the sppp driver? Date: Thu, 30 Sep 1999 09:50:47 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2014.211 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2014.211 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Are you busy with a leased line driver or a dialup/isdn kind of driver? > I have been busy fixing sppp to work properly with leased line drivers > again, but am not finished with it yet. :-/ Hopefully I won't break > the isdn handling at the same time. > I'm writing this pseudo driver with lots of interfaces. Each interface can be configured to work with a variety of protocols. Currently I'm working on the connection to the PPP protocol. > > While trying to use the sppp, I came across this situation and I think it's > > a bug: > > When you trying to establish connection from one peer (local) to another > > (remote), you sent a CONF_REQ message to the remote peer. The remote peer > > should answer with a CONF_ACK message. In the code of the sppp driver > > (net/if_spppsubr.c, lines 1321 - 1357) you can see that the remote peer > > send's a CONF_ACK message to the local peer > > (in the line: rv = (cp->RCR)(sp, h, len);) but doesn't change it state to > > STATE_ACK_SENT (as I think it should do) . Further more, you can see that > > after a few lines, there are these strange lines: > > case STATE_ACK_SENT: > > case STATE_REQ_SENT: > > sppp_cp_change_state(cp, sp, rv? > > STATE_ACK_SENT: STATE_REQ_SENT); > > break; > > My patch for this part looks like this, carefull I have just cut and > paste it, so the tabs got lost: > > --------- > @@ -1298,6 +1299,16 @@ > /* fall through... */ > case STATE_ACK_SENT: > case STATE_REQ_SENT: > + /* > + * sppp_cp_change_state() have the side effect of > + * restarting the timeouts. We want to avoid that > + * if the state don't change, otherwise we won't > + * ever timeout and resend a configuration request > + * that got lost. > + */ > + if (sp->state[cp->protoidx] == (rv ? STATE_ACK_SENT: > + STATE_REQ_SENT)) > + break; > sppp_cp_change_state(cp, sp, rv? > STATE_ACK_SENT: STATE_REQ_SENT); > break; > -------- My problem is that when you get the first CONF_REQ message, the driver's state is INITIAL. The call to the RCR function return with the value 1 but, no one changes the state to STATE_ACK_SENT. I think the fix should be like this (line 1274): .... rv = (cp->RCR)(sp, h, len); /* Daniel - fix */ if (rv && sp->state[cp->protoidx] == STATE_INITIAL) sppp_cp_change_state(cp, sp, STATE_ACK_SENT); sp->rst_counter[cp->protoidx] = sp->lcp.max_configure; /* End of fix */ switch (sp->state[cp->protoidx]) { case STATE_OPENED: ... Thanks for the help Daniel To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Sep 30 1:12:49 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mail-01.cdsnet.net (mail-01.cdsnet.net [206.107.16.35]) by hub.freebsd.org (Postfix) with SMTP id 7D9B7155BF for ; Thu, 30 Sep 1999 01:12:47 -0700 (PDT) (envelope-from mrcpu@internetcds.com) Received: (qmail 2262 invoked from network); 30 Sep 1999 08:12:47 -0000 Received: from schizo.cdsnet.net (204.118.244.32) by mail.cdsnet.net with SMTP; 30 Sep 1999 08:12:47 -0000 Date: Thu, 30 Sep 1999 01:12:26 -0700 (PDT) From: Jaye Mathisen X-Sender: mrcpu@schizo.cdsnet.net To: hackers@freebsd.org Subject: Speeding up time... Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I would like to play around with some y2k testing. While setting dates and such works, I'd really like to be able to disable xntpd, and have time move faster. So I could set the date to 12/28/99 or somesuch, and have time run at 4:1 or 10:1, or something that lets me run through a few days of operation in a few hours... Is there an obviously trivial way to do this? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Sep 30 2:35:37 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from isbalham.ist.co.uk (isbalham.ist.co.uk [192.31.26.1]) by hub.freebsd.org (Postfix) with ESMTP id 0E7731525F; Thu, 30 Sep 1999 02:35:28 -0700 (PDT) (envelope-from rb@gid.co.uk) Received: from gid.co.uk (uucp@localhost) by isbalham.ist.co.uk (8.9.2/8.8.7) with UUCP id KAA41374; Thu, 30 Sep 1999 10:35:28 +0100 (BST) (envelope-from rb@gid.co.uk) Received: from [194.32.164.2] by seagoon.gid.co.uk; Thu, 30 Sep 1999 10:30:58 +0100 (BST) X-Sender: rb@194.32.164.1 Message-Id: In-Reply-To: <19990929211018.G86792@florence.pavilion.net> References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Thu, 30 Sep 1999 10:30:55 +0000 To: Josef Karthauser From: Bob Bishop Subject: Re: my repository is broken (more) Cc: current@FreeBSD.ORG, hackers@FreeBSD.ORG Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 9:10 pm +0100 29/9/99, Josef Karthauser wrote: >On Wed, Sep 29, 1999 at 04:58:34PM +0000, Bob Bishop wrote: >> [...] >> I now suspect that cvsup.uk.freebsd.org isn't up-to-date. Anyone know >>anything? > >[...] > >In summary - sorry, try again. 'Tis working now :) Yup, looks like we're back in business - thanks! -- Bob Bishop (0118) 977 4017 international code +44 118 rb@gid.co.uk fax (0118) 989 4254 between 0800 and 1800 UK To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Sep 30 2:41:22 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from zibbi.mikom.csir.co.za (zibbi.mikom.csir.co.za [146.64.24.58]) by hub.freebsd.org (Postfix) with ESMTP id 5DBD21525F; Thu, 30 Sep 1999 02:41:09 -0700 (PDT) (envelope-from jhay@zibbi.mikom.csir.co.za) Received: (from jhay@localhost) by zibbi.mikom.csir.co.za (8.9.3/8.9.3) id LAA77105; Thu, 30 Sep 1999 11:41:00 +0200 (SAT) (envelope-from jhay) From: John Hay Message-Id: <199909300941.LAA77105@zibbi.mikom.csir.co.za> Subject: Re: A bug in the sppp driver? In-Reply-To: <049401bf0b20$e3621c20$2e00a8c0@nt46daniel> from Daniel Hilevich at "Sep 30, 1999 09:50:47 am" To: danhil@cwnt.com (Daniel Hilevich) Date: Thu, 30 Sep 1999 11:41:00 +0200 (SAT) Cc: jhay@mikom.csir.co.za (John Hay), freebsd-hackers@FreeBSD.ORG, freebsd-questions@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > My problem is that when you get the first CONF_REQ message, the driver's > state is INITIAL. > The call to the RCR function return with the value 1 but, no one changes the > state to STATE_ACK_SENT. I think the fix should be like this (line 1274): > > .... > rv = (cp->RCR)(sp, h, len); > > /* Daniel - fix */ > if (rv && sp->state[cp->protoidx] == STATE_INITIAL) > sppp_cp_change_state(cp, sp, STATE_ACK_SENT); > > sp->rst_counter[cp->protoidx] = sp->lcp.max_configure; > /* End of fix */ > > switch (sp->state[cp->protoidx]) { > case STATE_OPENED: > ... I think you are trying to bypass things. Look at rfc1661 on page 6 and 12-13. If you are in state initial, you are not supposed to react to anything except Up, Open and Close events. Have a look at the other drivers like ar(4), cx(4) and sr(4) to see how they use it. Also remember that they need an ifconfig to get started. That help them trough a lot of the states. Ifconfig will have the effect of giving an Up and then an Open event, which will take sppp from the Initial(0) state to Closed(2) and then to Req-Sent(6). John -- John Hay -- John.Hay@mikom.csir.co.za To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Sep 30 2:48:29 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp01.wxs.nl (smtp01.wxs.nl [195.121.6.61]) by hub.freebsd.org (Postfix) with ESMTP id 5585E159AE; Thu, 30 Sep 1999 02:48:25 -0700 (PDT) (envelope-from asmodai@wxs.nl) Received: from daemon.ninth-circle.org ([195.121.196.181]) by smtp01.wxs.nl (Netscape Messaging Server 3.61) with ESMTP id AAA34EF; Thu, 30 Sep 1999 11:48:22 +0200 Received: (from asmodai@localhost) by daemon.ninth-circle.org (8.9.3/8.9.3) id LAA07312; Thu, 30 Sep 1999 11:22:40 +0200 (CEST) (envelope-from asmodai) Date: Thu, 30 Sep 1999 11:22:39 +0200 From: Jeroen Ruigrok/Asmodai To: Anthony Rubin Cc: advocacy@freebsd.org, hackers@freebsd.org Subject: Re: FreeBSD driver for DPT SmartRAID V Message-ID: <19990930112239.B6954@daemon.ninth-circle.org> References: <004f01bf0aef$4384c760$010210ac@arrubin> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre3i In-Reply-To: <004f01bf0aef$4384c760$010210ac@arrubin> Organisation: Ninth-Circle Enterprises Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On [19990930 08:14], Anthony Rubin (jedi@enteract.com) wrote: >With the release of the Linux driver for the DPT SmartRAID V cards I imagine >it is just a matter of time before we have a FreeBSD driver. I sent the >following message to DPT. > >>I know this may be a long shot, but here goes. What would be the >>possibilites of a FreeBSD driver for your SmartRAID V series? I know one >>will probably be created eventually now that you released your Linux driver >>with source, but I was hoping for one in the next month or so that I could >>purchase a SmartRAID V for use in a FreeBSD box that I have. Thanks in >>advance. If not, bug for tech-docs to be released free of NDA, whereas the FreeBSD hacker community will code the driver. This will impose no support for the driver upon DPT. Make sure to emphasize that. Another long shot. But it worked for other companies =) -- Jeroen Ruigrok van der Werven/Asmodai asmodai(at)wxs.nl The BSD Programmer's Documentation Project Network/Security Specialist BSD: Technical excellence at its best Fame is the perfume of heroic deeds. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Sep 30 2:49:43 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mail1.atl.bellsouth.net (mail1.atl.bellsouth.net [205.152.0.28]) by hub.freebsd.org (Postfix) with ESMTP id 4551C15AA4 for ; Thu, 30 Sep 1999 02:49:38 -0700 (PDT) (envelope-from wghicks@bellsouth.net) Received: from wghicks.bellsouth.net (host-216-78-101-28.asm.bellsouth.net [216.78.101.28]) by mail1.atl.bellsouth.net (3.3.4alt/0.75.2) with ESMTP id FAA28249; Thu, 30 Sep 1999 05:45:24 -0400 (EDT) Received: from wghicks.bellsouth.net (IDENT:wghicks@localhost [127.0.0.1]) by wghicks.bellsouth.net (8.9.3/8.9.2) with ESMTP id FAA02650; Thu, 30 Sep 1999 05:54:49 -0400 (EDT) (envelope-from wghicks@wghicks.bellsouth.net) Message-Id: <199909300954.FAA02650@bellsouth.net> To: "Dennis" Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: A bug in the sppp driver? In-reply-to: Your message of "Wed, 29 Sep 1999 17:25:15 BST." <038d01bf0a97$3652f8d0$2e00a8c0@nt46daniel> Date: Thu, 30 Sep 1999 05:54:49 -0400 From: W Gerald Hicks Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > doing state machines with switch statements is a big mess. Still, you'll find a lot of them around. Do you have a favored technique for coding complex state machines? (I'm a collector :) One scheme I've been using for quite some time is to use a function pointer as a 'state variable', sometimes making a stack of them for a more flexible machine. Sometimes I use a transition matrix for selection of the 'state function' but more often the functions themselves perform 'next state' selection. To be honest though, most of the time the machinery I need for an application has from four to six states. Anything more than a simple switch on a state variable seems to be overkill for those. Cheers, Jerry Hicks wghicks@bellsouth.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Sep 30 3:52:48 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from alpha.netvision.net.il (alpha.netvision.net.il [194.90.1.13]) by hub.freebsd.org (Postfix) with ESMTP id 9312815955; Thu, 30 Sep 1999 03:52:44 -0700 (PDT) (envelope-from danhil@cwnt.com) Received: from unspecified.host (RAS4-p71.hfa.netvision.net.il [62.0.146.199]) by alpha.netvision.net.il (8.9.3/8.8.6) with SMTP id MAA27248; Thu, 30 Sep 1999 12:52:42 +0200 (IST) Received: from 192.168.0.46 ([192.168.0.46]) by 192.168.0.1 (WinRoute 3.04g) with SMTP; Thu, 30 Sep 1999 12:51:09 +0200 Message-ID: <050001bf0b3a$13e078b0$2e00a8c0@nt46daniel> From: "Daniel Hilevich" To: , References: <199909300941.LAA77105@zibbi.mikom.csir.co.za> Subject: Re: A bug in the sppp driver? Date: Thu, 30 Sep 1999 12:51:05 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2014.211 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2014.211 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > I think you are trying to bypass things. Look at rfc1661 on page 6 and > 12-13. If you are in state initial, you are not supposed to react to > anything except Up, Open and Close events. > > Have a look at the other drivers like ar(4), cx(4) and sr(4) to see > how they use it. Also remember that they need an ifconfig to get > started. That help them trough a lot of the states. Ifconfig will > have the effect of giving an Up and then an Open event, which will > take sppp from the Initial(0) state to Closed(2) and then to > Req-Sent(6). > > John You are absolutely right when it comes to handling the sppp driver in manual mode. The user creates a Up event using ifconfig and a Open event moves the fsm from Starting(1) to Req-Sent(6). In my case, although, I want to use the IFF_AUTO (dial on demand) option and this is where ifconfig can not help me. In the auto mode, the sppp driver should initialize the lcp machine when it gets a new message to send. In line 646 (sppp_output) you can see a call to Open the lcp but because there was no previous Up event, the fsm moved from the Initial(0) state to the Starting(1) state and not to the Req-Sent(6) state. I think that in the auto mode, there should be an automatic call to the Up event, no? Thanks Daniel To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Sep 30 5:17:17 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.uni-bielefeld.de (mail.uni-bielefeld.de [129.70.4.90]) by hub.freebsd.org (Postfix) with ESMTP id AB4F614FFD; Thu, 30 Sep 1999 05:17:07 -0700 (PDT) (envelope-from bfischer@Techfak.uni-bielefeld.de) Received: from frolic.no-support.loc (ppp36-136.hrz.uni-bielefeld.de) by mail.uni-bielefeld.de (Sun Internet Mail Server sims.3.5.1999.05.24.18.28.p7) with ESMTP id <0FIV00F0HGRZ7N@mail.uni-bielefeld.de>; Thu, 30 Sep 1999 14:16:48 +0200 (MET DST) Received: (from bjoern@localhost) by frolic.no-support.loc (8.9.3/8.9.3) id NAA01731; Thu, 30 Sep 1999 13:30:04 +0200 (CEST envelope-from bjoern) Date: Thu, 30 Sep 1999 13:30:04 +0200 From: Bjoern Fischer Subject: Has anyone tried Erez Zadok's FIST? To: freebsd-fs@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG Message-id: <19990930133004.B325@frolic.no-support.loc> MIME-version: 1.0 X-Mailer: Mutt 1.0pre3i Content-type: text/plain; charset=iso-8859-1 Content-transfer-encoding: quoted-printable Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello, has anyone tried to use Erez Zadok's FIST software on FreeBSD3.x? FIST is a system for generating stackable file systems in an OS transparent way. I am looking for a method to get something like Solaris cachefs: A filesystem usually mounted upon an NFS which replicates all NFS reads to a local disk which is used as a cache. Bj=F6rn --=20 -----BEGIN GEEK CODE BLOCK----- GCS d--(+) s++: a- C+++(-) UB++++OSI++++$ P+++(-) L+++(--) !E W- N+ o>+ K- !w !O !M !V PS++ PE- PGP++ t+++ !5 X++ tv- b+++ D++ G e+ h-- y+=20 ------END GEEK CODE BLOCK------ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Sep 30 5:52:25 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from gw.nectar.com (gw.nectar.com [209.98.143.44]) by hub.freebsd.org (Postfix) with ESMTP id 88CFC15A50 for ; Thu, 30 Sep 1999 05:52:09 -0700 (PDT) (envelope-from nectar@nectar.com) Received: from spawn.nectar.com (localhost [127.0.0.1]) by gw.nectar.com (Postfix) with ESMTP id D466DBE87; Thu, 30 Sep 1999 07:52:01 -0500 (CDT) X-Mailer: exmh version 2.0.2 2/24/98 X-PGP-RSAfprint: 00 F9 E6 A2 C5 4D 0A 76 26 8B 8B 57 73 D0 DE EE X-PGP-RSAkey: http://www.nectar.com/nectar-rsa.txt X-PGP-DSSfprint: AB2F 8D71 A4F4 467D 352E 8A41 5D79 22E4 71A2 8C73 X-PGP-DHfprint: 2D50 12E5 AB38 60BA AF4B 0778 7242 4460 1C32 F6B1 X-PGP-DH-DSSkey: http://www.nectar.com/nectar-dh-dss.txt From: Jacques Vidrine To: Josef Karthauser Cc: freebsd-hackers@FreeBSD.ORG In-reply-to: <19990930081816.K86792@florence.pavilion.net> References: <14322.15597.505566.676863@trooper.velocet.ca> <19990929211210.H86792@florence.pavilion.net> <19990929200309.A96281@zipperup.org> <19990930081816.K86792@florence.pavilion.net> Subject: Re: PPPoE offer. Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 30 Sep 1999 07:52:01 -0500 Message-Id: <19990930125201.D466DBE87@gw.nectar.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Yes. The boxes from Redback (www.redback.com) support this mode of operation, which is primarily for sane deployment of DSL over an infrastructure built on bridging. Alcatel DSL products, used by BellSouth and others, operate in this mode (see RFC 1483 section 4.2). Jacques Vidrine / n@nectar.com / nectar@FreeBSD.org On 30 September 1999 at 8:18, Josef Karthauser wrote: > Maybe I've got it wrong then, but he can definitely use user-ppp to > make ppp over IP tunnels - is PPPoE mac address to mac address > connectivity? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Sep 30 6:34:50 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mv.egroups.com (mv.egroups.com [207.138.41.150]) by hub.freebsd.org (Postfix) with SMTP id 80A91159CF for ; Thu, 30 Sep 1999 06:34:42 -0700 (PDT) (envelope-from francis.lam@leitch.com) Received: from [10.1.2.6] by mv.egroups.com with NNFMP; 30 Sep 1999 14:34:42 -0000 Date: Thu, 30 Sep 1999 06:34:32 -0700 From: francis.lam@leitch.com To: freebsd-hackers@freebsd.org Subject: Kerberos 5 KDC with Kerberos IV client Message-ID: <7svot8$mk3j@eGroups.com> User-Agent: eGroups-EW/0.76 Content-Length: 986 X-Mailer: eGroups Message Poster Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I am working on upgrading our servers to Y2K. I am building a test bed with three(3) boxes called A, B and C. Box A installed with FreeBSD 3.2, Kerberos 5 and setup as KDC. Box B installed with FreeBSD 3.2 and Kerberos 5. Box C installed with FreeBSD 2.2.6 and Kerberos IV. The Kerberos 5 datebase setup is done. All three boxes are be able to issue a ticket from KDC. Rlogin from box B and C to box A works fine. Rlogin from box A to box B works OK. Rlogin from box C to box B works OK too. But rlogin from box A or box B to box C was rejected. The messages was: Couldn't authenticate to server: Bad sendauth version was sent rlogin: kcmd to host bitter failed - Bad sendauth version was sent trying normal rlogin (/usr/bin/rlogin) usage: rlogin [ -8DEKLx] [-k realm] [-e char] [ -l username ] host The srvtab on box C was created by kadmin: ktadd and converted to srvtab using: ktutil: rst krb5.keytab ktutil: wkt srvtab Any idea what was wrong. Thanks Francis To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Sep 30 8:40:59 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (Postfix) with ESMTP id E632814DBB for ; Thu, 30 Sep 1999 08:40:53 -0700 (PDT) (envelope-from julian@whistle.com) Received: from home.elischer.org (home.elischer.org [207.76.204.203]) by alpo.whistle.com (8.9.1a/8.9.1) with ESMTP id IAA39930; Thu, 30 Sep 1999 08:40:31 -0700 (PDT) Date: Thu, 30 Sep 1999 08:40:29 -0700 (PDT) From: Julian Elischer X-Sender: julian@home.elischer.org To: "Ronald G. Minnich" Cc: hackers@FreeBSD.ORG Subject: Re: return to real mode In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG the old boot code did it for calling the bios did it not? julian On Wed, 29 Sep 1999, Ronald G. Minnich wrote: > anybody got some reliable, tested, known-good code for getting back to > real mode? I'm to the point where I have a working GDT, and paging is > turned off, but the last step -- turning off protection enable -- is not > working for me. > > This is on a PII. > > Thanks > > ron > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Sep 30 9:22: 6 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from acl.lanl.gov (acl.lanl.gov [128.165.147.1]) by hub.freebsd.org (Postfix) with ESMTP id 5A36614C10 for ; Thu, 30 Sep 1999 09:22:04 -0700 (PDT) (envelope-from rminnich@lanl.gov) Received: from mini.acl.lanl.gov (root@mini.acl.lanl.gov [128.165.147.34]) by acl.lanl.gov (8.8.8/8.8.5) with ESMTP id KAA270790 for ; Thu, 30 Sep 1999 10:22:03 -0600 (MDT) Received: from localhost (rminnich@localhost) by mini.acl.lanl.gov (8.9.3/8.8.8) with ESMTP id KAA17916 for ; Thu, 30 Sep 1999 10:22:03 -0600 X-Authentication-Warning: mini.acl.lanl.gov: rminnich owned process doing -bs Date: Thu, 30 Sep 1999 10:22:03 -0600 (MDT) From: "Ronald G. Minnich" X-Sender: rminnich@mini.acl.lanl.gov To: hackers@FreeBSD.ORG Subject: Re: return to real mode In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG well, I'll go check that. I'm finding that there is fair amounts of code out there that is broken. Thanks to the wonderful PC bios you have a hard time sometimes telling the difference between code that crashes into the bios and code that actually works right, since the result is the same either way :-) rn To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Sep 30 9:51:46 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from etinc.com (et-gw.etinc.com [207.252.1.2]) by hub.freebsd.org (Postfix) with ESMTP id 3C460158B9 for ; Thu, 30 Sep 1999 09:51:37 -0700 (PDT) (envelope-from dennis@etinc.com) Received: from dbsys (dbsys.etinc.com [207.252.1.18]) by etinc.com (8.9.3/8.9.3) with SMTP id MAA12186; Thu, 30 Sep 1999 12:48:34 -0400 (EDT) Message-Id: <199909301648.MAA12186@etinc.com> X-Sender: dennis@etinc.com (Unverified) X-Mailer: QUALCOMM Windows Eudora Pro Version 4.0 Date: Thu, 30 Sep 1999 11:46:30 -0400 To: W Gerald Hicks From: Dennis Subject: Re: A bug in the sppp driver? Cc: freebsd-hackers@FreeBSD.ORG In-Reply-To: <199909300954.FAA02650@bellsouth.net> References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 05:54 AM 9/30/99 -0400, W Gerald Hicks wrote: > >> doing state machines with switch statements is a big mess. > >Still, you'll find a lot of them around. Do you have a favored >technique for coding complex state machines? (I'm a collector :) yes, state tables. Clean and easy to modify. > >One scheme I've been using for quite some time is to use a function >pointer as a 'state variable', sometimes making a stack of them for >a more flexible machine. > >Sometimes I use a transition matrix for selection of the 'state function' >but more often the functions themselves perform 'next state' selection. then your back to switch statements, because you have actions that are used in multiple states. event=decode_event(cur_state,pdata); do_action(cur_state[event][action]); new_state=cur_state[event][newstate]; Dennis To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Sep 30 12:41:25 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from nomis.simon-shapiro.org (nomis.simon-shapiro.org [209.86.126.163]) by hub.freebsd.org (Postfix) with SMTP id 5D3BF14CB1 for ; Thu, 30 Sep 1999 12:41:20 -0700 (PDT) (envelope-from shimon@simon-shapiro.org) Received: (qmail 46378 invoked from network); 30 Sep 1999 19:41:20 -0000 Received: from localhost.simon-shapiro.org (HELO simon-shapiro.org) (127.0.0.1) by localhost.simon-shapiro.org with SMTP; 30 Sep 1999 19:41:20 -0000 Message-ID: <37F3BCE0.A7D1E168@simon-shapiro.org> Date: Thu, 30 Sep 1999 15:41:20 -0400 From: Simon Shapiro as Himself Organization: Simon's Garage X-Mailer: Mozilla 4.6 [en] (X11; I; FreeBSD 3.3-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: hackers@freebsd.org Subject: Kernel cdevsw.size Content-Type: text/plain; charset= Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi Y'll The function pointer (entry point, etc.) that indicates a device size is defined in sys/conf.h as: typedef int d_psize_t __P((dev_t dev)); The problem I have is that i2o devices express size as 64bit unsigned value (this is in bytes). This means that a device with more than 2billion sectors will fail to work correctly. While I realize this is not a very practical worry to most, such devices are not purely imaginary, nor inconcievable. Just casting the data will intruduce a latent and undocumented bug, sort of y2k of device sizes. Suggestions? -- Sincerely Yours, Shimon@Simon-Shapiro.ORG 404.644.6401 Simon Shapiro Unwritten code has no bugs and executes at twice the speed of mouth To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Sep 30 12:54:14 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from gvr.gvr.org (gvr.gvr.org [194.151.74.97]) by hub.freebsd.org (Postfix) with ESMTP id 906BA14DA2 for ; Thu, 30 Sep 1999 12:54:04 -0700 (PDT) (envelope-from guido@gvr.org) Received: by gvr.gvr.org (Postfix, from userid 657) id 0A9C9A84A; Thu, 30 Sep 1999 21:54:02 +0200 (CEST) Date: Thu, 30 Sep 1999 21:54:02 +0200 From: Guido van Rooij To: FreeBSD-hackers Subject: booting from a second slice Message-ID: <19990930215402.A449@gvr.gvr.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.6i Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG what is the correct way (if at all) to boot off a second FreeBSD slice, given the following fdisk table (see below)? I thought that the three stage boot would make such a think possible. F2 in the boot manager does not work, but I would have thought that the loader would enable me to say currdev=disk1s2a: but an ls gives an error (lik unable to open xxx or something like that). I know about the 1024 cylinder limit, however I would expect loader to be able to work beyond that limit.. (btw: I take it that nextboot does not work with the btx stuff (couldn't locate any such stuff in the sources). If so, it should probably be removed in the i386 case (not in pc98 case though). fdisk table: ******* Working on device /dev/rwd0 ******* parameters extracted from in-core disklabel are: cylinders=12595 heads=16 sectors/track=63 (1008 blks/cyl) Figures below won't work with BIOS for partitions not in cyl 1 parameters to be used for BIOS calculations are: cylinders=12595 heads=16 sectors/track=63 (1008 blks/cyl) Media sector size is 512 Warning: BIOS sector numbering starts with sector 1 Information from DOS bootblock is: The data for partition 1 is: sysid 165,(FreeBSD/NetBSD/386BSD) start 63, size 3071313 (1499 Meg), flag 80 (active) beg: cyl 0/ sector 1/ head 1; end: cyl 1023/ sector 63/ head 15 The data for partition 2 is: sysid 165,(FreeBSD/NetBSD/386BSD) start 3071376, size 3071376 (1499 Meg), flag 0 beg: cyl 1023/ sector 63/ head 255; end: cyl 1023/ sector 63/ head 15 The data for partition 3 is: sysid 165,(FreeBSD/NetBSD/386BSD) start 6142752, size 3071376 (1499 Meg), flag 0 beg: cyl 1023/ sector 63/ head 255; end: cyl 1023/ sector 63/ head 15 The data for partition 4 is: sysid 165,(FreeBSD/NetBSD/386BSD) start 9214128, size 3481632 (1700 Meg), flag 0 beg: cyl 1023/ sector 63/ head 255; end: cyl 1023/ sector 63/ head 15 -Guido To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Sep 30 14: 7:25 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from caladan.tdx.co.uk (caladan.tdx.co.uk [195.188.177.4]) by hub.freebsd.org (Postfix) with ESMTP id 4FC2A153B0 for ; Thu, 30 Sep 1999 14:07:10 -0700 (PDT) (envelope-from kpielorz@caladan.tdx.co.uk) Received: from localhost (kpielorz@localhost) by caladan.tdx.co.uk (8.9.3/8.9.3/Kp) with ESMTP id WAA38942 for ; Thu, 30 Sep 1999 22:07:09 +0100 (BST) Date: Thu, 30 Sep 1999 22:07:09 +0100 (BST) From: Karl Pielorz To: hackers@freebsd.org Subject: Drivers, templates and beyond 2.2.X Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi All, It's now getting to the point where I _have_ to port my old, 2.2.X custom driver to run under 3.X/4.X. I'm a reasnably competant programmer, and creating the driver under 2.2.X wasn't too hard, thanks to help from friends, a ~10 year old book - and the files in /usr/share/examples/drivers A lot has changed since 2.2.X (i.e. probes, handlers, the way ISA drivers are attached etc. - and God knows what else). My questions are: 1. Has anyone got any updated 'skeleton drivers' for ISA devices under 3.X/4.X? (i.e. more up to date files than those in /usr/share/examples/drivers?) 2. Failing #1, which driver is the best driver to print out, and pull apart as an example of "How writing a simple port-mapped ISA card driver" should be done?. I've looked at things like the joystick driver, and some of the sound code etc. - there seems to be a lot of difference in the way the drivers are set out etc. (At least, that seems to be the case to me!). This leaves me a little confused, if I'm going to model my driver on one of the existing ones - which is best? Thanks in advance for any info, Regards, Karl Pielorz To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Sep 30 14:14:21 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from r84aap011262.sbo-smr.ma.cable.rcn.com (r84aap011262.sbo-smr.ma.cable.rcn.com [209.6.194.47]) by hub.freebsd.org (Postfix) with ESMTP id CC3C314E62 for ; Thu, 30 Sep 1999 14:14:14 -0700 (PDT) (envelope-from huff@r84aap011262.sbo-smr.ma.cable.rcn.com) Received: (from huff@localhost) by r84aap011262.sbo-smr.ma.cable.rcn.com (8.9.3/8.9.3) id RAA11471; Thu, 30 Sep 1999 17:14:14 -0400 (EDT) (envelope-from huff) From: Robert Huff MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14323.53925.815819.699822@r84aap011262.sbo-smr.ma.cable.rcn.com> Date: Thu, 30 Sep 1999 17:14:13 -0400 (EDT) To: freebsd-hackers@FreeBSD.org Subject: RE: updating packages automatically, etc.pp. In-Reply-To: <101308237@toto.iv> X-Mailer: VM 6.72 under 21.1 "20 Minutes to Nikko" XEmacs Lucid (patch 2) Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Kris Kennaway writes: > > The script relies on you having an up-to-date INDEX file; do "make > > index" first to be sure (which reminds me, why is the INDEX file > > always out of sync after a cvsup?). It only tries to upgrade ports > > Because it's only generated periodically, not every time someone > adds or modifies a port, which would be very wasteful. How often is periodically? While I read the output of my CVSup sessions, it had been my impression that INDEX was an accurate (+/- epsilon) snapshot of the ports tree. Are you telling me it could be, oh, two or three weeks out of date ...? Robert Huff To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Sep 30 15: 8:25 1999 Delivered-To: freebsd-hackers@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 758) id 8C66714E9B; Thu, 30 Sep 1999 15:08:23 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id 7D4501CD485; Thu, 30 Sep 1999 15:08:23 -0700 (PDT) (envelope-from kris@hub.freebsd.org) Date: Thu, 30 Sep 1999 15:08:23 -0700 (PDT) From: Kris Kennaway To: Robert Huff Cc: freebsd-hackers@FreeBSD.org Subject: RE: updating packages automatically, etc.pp. In-Reply-To: <14323.53925.815819.699822@r84aap011262.sbo-smr.ma.cable.rcn.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 30 Sep 1999, Robert Huff wrote: > > > The script relies on you having an up-to-date INDEX file; do "make > > > index" first to be sure (which reminds me, why is the INDEX file > > > always out of sync after a cvsup?). It only tries to upgrade ports > > > > Because it's only generated periodically, not every time someone > > adds or modifies a port, which would be very wasteful. > > How often is periodically? > While I read the output of my CVSup sessions, it had been my > impression that INDEX was an accurate (+/- epsilon) snapshot of the > ports tree. Are you telling me it could be, oh, two or three weeks > out of date ...? Yes. Check the commit logs. Kris To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Sep 30 17:15:15 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from pop3-3.enteract.com (pop3-3.enteract.com [207.229.143.32]) by hub.freebsd.org (Postfix) with SMTP id EAA5F14D4E for ; Thu, 30 Sep 1999 17:15:11 -0700 (PDT) (envelope-from jedi@enteract.com) Received: (qmail 14404 invoked from network); 1 Oct 1999 00:15:10 -0000 Received: from 207-229-172-200.d.enteract.com (HELO arrubin) (207.229.172.200) by pop3-3.enteract.com with SMTP; 1 Oct 1999 00:15:10 -0000 Message-ID: <000501bf0ba2$6dfbf6e0$010210ac@arrubin> From: "Anthony Rubin" To: , Subject: Fw: FreeBSD Case # J69309N Date: Thu, 30 Sep 1999 19:18:03 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2314.1300 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Here is the response I got from DPT about FreeBSD drivers for their SmartRAID V cards. It looks as if they will be releasing a driver eventually. Anthony Rubin jedi@enteract.com Hoffman Estates, IL ----- Original Message ----- From: To: Anthony Rubin Sent: Thursday, September 30, 1999 1:02 PM Subject: Re: FreeBSD Case # J69309N > > > Hello Anthony, > > Thank you for your message regarding the DPT SCSI host adapter.. At this time > we do not have a BETA driver to release. We > have had reports that there is one available on the web. If you go to Deja.com > and search for FreeBDS and DPT you should find > several links and messages. We will have drivers for FreeBSD in the near future. > > > If you have any questions or if I can be of further assistance regarding this > issue, please feel free to contact me using the case > number (J69309N) that has been assigned in the SUBJECT line of this message. > > Best Regards, > Joe Niderost > Technical Support Engineer, DPT To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Sep 30 17:17:23 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id E775014D4E; Thu, 30 Sep 1999 17:17:19 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from beppo.feral.com (beppo [192.67.166.79]) by feral.com (8.8.7/8.8.7) with ESMTP id RAA14591; Thu, 30 Sep 1999 17:16:59 -0700 Date: Thu, 30 Sep 1999 17:16:50 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: Anthony Rubin Cc: hackers@FreeBSD.ORG, advocacy@FreeBSD.ORG Subject: Re: Fw: FreeBSD Case # J69309N In-Reply-To: <000501bf0ba2$6dfbf6e0$010210ac@arrubin> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 30 Sep 1999, Anthony Rubin wrote: > Here is the response I got from DPT about FreeBSD drivers for their > SmartRAID V cards. It looks as if they will be releasing a driver > eventually. Forgive me for a possibly stupid comment, but isn't this the board that Simon Shapiro has been working on (interrupted until recently by illness I believe...) > Anthony Rubin > jedi@enteract.com > Hoffman Estates, IL > > ----- Original Message ----- > From: > To: Anthony Rubin > Sent: Thursday, September 30, 1999 1:02 PM > Subject: Re: FreeBSD Case # J69309N > > > > > > > > Hello Anthony, > > > > Thank you for your message regarding the DPT SCSI host adapter.. At this > time > > we do not have a BETA driver to release. We > > have had reports that there is one available on the web. If you go to > Deja.com > > and search for FreeBDS and DPT you should find > > several links and messages. We will have drivers for FreeBSD in the near > future. > > > > > > If you have any questions or if I can be of further assistance regarding > this > > issue, please feel free to contact me using the case > > number (J69309N) that has been assigned in the SUBJECT line of this > message. > > > > Best Regards, > > Joe Niderost > > Technical Support Engineer, DPT > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Sep 30 17:48: 7 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from resnet.uoregon.edu (resnet.uoregon.edu [128.223.144.32]) by hub.freebsd.org (Postfix) with ESMTP id 27B7314C1F for ; Thu, 30 Sep 1999 17:48:05 -0700 (PDT) (envelope-from dwhite@resnet.uoregon.edu) Received: from localhost (dwhite@localhost) by resnet.uoregon.edu (8.9.3/8.9.3) with ESMTP id RAA31013; Thu, 30 Sep 1999 17:47:55 -0700 (PDT) (envelope-from dwhite@resnet.uoregon.edu) Date: Thu, 30 Sep 1999 17:47:55 -0700 (PDT) From: Doug White To: Jacques Vidrine Cc: Josef Karthauser , freebsd-hackers@FreeBSD.ORG Subject: Re: PPPoE offer. In-Reply-To: <19990930125201.D466DBE87@gw.nectar.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 30 Sep 1999, Jacques Vidrine wrote: > > Yes. The boxes from Redback (www.redback.com) support this mode > of operation, which is primarily for sane deployment of DSL over > an infrastructure built on bridging. Alcatel DSL products, used > by BellSouth and others, operate in this mode (see RFC 1483 section > 4.2). Well, not *ALL* the Alcatels (thank goodness PacBell hasn't figured this out :-) ) If you have a grasp of DHCP, then PPPoE will look awfully familiar. There is a fairly detailed RFC out on it, although it lacks in the philosophy department which does influence your design. I actually hacked userppp to talk to RedBacks (and even had development gear to do it) about a year ago. That code is quite ugly and doesn't belong to me anyway. I've itched to reimplement it after Brian's changes to the lower-end device handling about 6 months ago since I had to make nasty, nasty hacks. I don't think dialup worked afterwards and doubt it ever would again on that code. If someone wanted to pick it up, I'd really try to get a demo SMS-500 with the appropriate firmware (AOS 2.2 or later) to hack it with. I can also lend advice. It took me 2 months to design & code it, and that was working part-time through school. Doug White Internet: dwhite@resnet.uoregon.edu | FreeBSD: The Power to Serve http://gladstone.uoregon.edu/~dwhite | www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Sep 30 18:21: 1 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from resnet.uoregon.edu (resnet.uoregon.edu [128.223.144.32]) by hub.freebsd.org (Postfix) with ESMTP id A716B14E20 for ; Thu, 30 Sep 1999 18:20:57 -0700 (PDT) (envelope-from dwhite@resnet.uoregon.edu) Received: from localhost (dwhite@localhost) by resnet.uoregon.edu (8.9.3/8.9.3) with ESMTP id SAA41570; Thu, 30 Sep 1999 18:20:48 -0700 (PDT) (envelope-from dwhite@resnet.uoregon.edu) Date: Thu, 30 Sep 1999 18:20:48 -0700 (PDT) From: Doug White To: Guido van Rooij Cc: FreeBSD-hackers Subject: Re: booting from a second slice In-Reply-To: <19990930215402.A449@gvr.gvr.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 30 Sep 1999, Guido van Rooij wrote: > > what is the correct way (if at all) to boot off a second FreeBSD > slice, given the following fdisk table (see below)? > I thought that the three stage boot would make such a think possible. > F2 in the boot manager does not work, but I would have thought that > the loader would enable me to say currdev=disk1s2a: set curdev=disk1s2a You may need to force the root directory too with set rootdev=disk1s2a Doug White Internet: dwhite@resnet.uoregon.edu | FreeBSD: The Power to Serve http://gladstone.uoregon.edu/~dwhite | www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Sep 30 20:40:10 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from uni4nn.gn.iaf.nl (osmium.gn.iaf.nl [193.67.144.12]) by hub.freebsd.org (Postfix) with ESMTP id 1BFF814DCC for ; Thu, 30 Sep 1999 20:40:05 -0700 (PDT) (envelope-from wilko@yedi.iaf.nl) Received: from yedi.iaf.nl (uucp@localhost) by uni4nn.gn.iaf.nl (8.9.2/8.9.2) with UUCP id FAA24264 for freebsd-hackers@FreeBSD.ORG; Fri, 1 Oct 1999 05:27:05 +0200 (MET DST) Received: (from wilko@localhost) by yedi.iaf.nl (8.9.3/8.9.3) id AAA44099; Fri, 1 Oct 1999 00:07:47 +0200 (CEST) (envelope-from wilko) From: Wilko Bulte Message-Id: <199909302207.AAA44099@yedi.iaf.nl> Subject: Re: 2.88Mb floppies In-Reply-To: <199909292346.BAA03499@dorifer.heim3.tu-clausthal.de> from Oliver Fromme at "Sep 30, 1999 1:46:41 am" To: freebsd-hackers@FreeBSD.ORG Date: Fri, 1 Oct 1999 00:07:47 +0200 (CEST) Cc: freebsd-hackers@FreeBSD.ORG X-Organisation: Private FreeBSD site - Arnhem, The Netherlands X-pgp-info: PGP public key at 'finger wilko@freefall.freebsd.org' X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG As Oliver Fromme wrote ... > Wilko Bulte wrote in list.freebsd-hackers: > > As Doug Rabson wrote ... > > > On Mon, 27 Sep 1999, Wilko Bulte wrote: > > > > static struct fd_type fd_types[NUMTYPES] = > > > > { > > > > { 21,2,0xFF,0x04,82,3444,1,FDC_500KBPS,2,0x0C,2 }, /* 1.72M in HD 3.5in */ > > > > { 18,2,0xFF,0x1B,82,2952,1,FDC_500KBPS,2,0x6C,1 }, /* 1.48M in HD 3.5in */ > > > > { 18,2,0xFF,0x1B,80,2880,1,FDC_500KBPS,2,0x6C,1 }, /* 1.44M in HD 3.5in */ > > > > > > I have no idea whether that driver can cope with 2.88mb floppies to be > > > honest. There is only one way to find out... > > > > Right. I'll give it a try asap. Somebody sent me a sample entry to > > add to fd_type. But I want to do a bit of study on the fd source to see > > if I can understand what all the fields mean. > > I once programmed low-level FDC stuff under DOS, so I'm a bit > familiar with this... The difference between 1.44 and 2.88 Mb > floppies is that the latter use 36 sectors per track and twice > the data rate (1 MBit/s). So the entry should look like this: > > {36, 2, 0xff, 0x1b, 80, 5760, 1, FDC_125KBPS, 2, 0x6c, 1} > > Actually, there should be a #define FDC_1MBPS FDC_125KBPS Eh, I guess you mean: {36, 2, 0xff, 0x1b, 80, 5760, 1, FDC_1MBPS, 2, 0x6c, 1} ? I hope to give it a shot sometime next week. -- | / o / / _ Arnhem, The Netherlands - Powered by FreeBSD - |/|/ / / /( (_) Bulte WWW : http://www.tcja.nl http://www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Sep 30 22:58: 6 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (Postfix) with ESMTP id 691D314D4A for ; Thu, 30 Sep 1999 22:57:42 -0700 (PDT) (envelope-from julian@whistle.com) Received: from current1.whistle.com (current1.whistle.com [207.76.205.22]) by alpo.whistle.com (8.9.1a/8.9.1) with SMTP id WAA68357 for ; Thu, 30 Sep 1999 22:57:42 -0700 (PDT) Date: Thu, 30 Sep 1999 22:57:42 -0700 (PDT) From: Julian Elischer To: hackers@freebsd.org Subject: Huge Binaries.. Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Has anyone looked at netscape Communicator 4.7 for FreeBSD??? I just installed it. the binary is 13234176 bytes long!! yes folks, that's 13 MB! stripped! current1# ldd netscape netscape: -lXt.6 => /usr/X11R6/lib/libXt.so.6.0 (0x20b5c000) -lXmu.6 => /usr/X11R6/lib/libXmu.so.6.0 (0x20b98000) -lX11.6 => /usr/X11R6/lib/libX11.so.6.1 (0x20ba8000) -lXext.6 => /usr/X11R6/lib/libXext.so.6.3 (0x20c39000) -lSM.6 => /usr/X11R6/lib/libSM.so.6.0 (0x20c42000) -lICE.6 => /usr/X11R6/lib/libICE.so.6.3 (0x20c4a000) -lg++.4 => /usr/lib/libg++.so.4.0 (0x20c5b000) -lstdc++.2 => /usr/lib/libstdc++.so.2.0 (0x20c97000) -lm.2 => /usr/lib/libm.so.2.0 (0x20ccd000) -lc.3 => /usr/lib/libc.so.3.1 (0x20ce7000) With shared libraries! It runs but it's quite easy to make your xserver run out of memory (or something (Sig 11)) One has to wonder what on earth they have in there? (My machine has 32 MB so it can run, but it's a bit of a squeez!) julian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Sep 30 23:50:39 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.HiWAAY.net (fly.HiWAAY.net [208.147.154.56]) by hub.freebsd.org (Postfix) with ESMTP id 2638814D44 for ; Thu, 30 Sep 1999 23:50:35 -0700 (PDT) (envelope-from kris@airnet.net) Received: from airnet.net (tc14-216-180-35-157.dialup.HiWAAY.net [216.180.35.157]) by mail.HiWAAY.net (8.9.1a/8.9.0) with ESMTP id BAA13201; Fri, 1 Oct 1999 01:50:31 -0500 (CDT) Message-ID: <37F459B6.98AD62EC@airnet.net> Date: Fri, 01 Oct 1999 01:50:30 -0500 From: Kris Kirby Organization: Non Illegitemus Carborundum. X-Mailer: Mozilla 4.08 [en] (X11; U; FreeBSD 3.2-RELEASE i386) MIME-Version: 1.0 To: Julian Elischer Cc: hackers@FreeBSD.ORG Subject: Re: Huge Binaries.. References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Julian Elischer wrote: > > Has anyone looked at netscape Communicator 4.7 for FreeBSD??? > > I just installed it. > the binary is 13234176 bytes long!! > yes folks, that's 13 MB! Is the mailer / newsreader still screwed up? I prefer them seperated, but they don't give me the choice. (4.08 land...) -- Kris Kirby ------------------------------------------- TGIFreeBSD... 'Nuff said. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Oct 1 0:50:31 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from dingo.cdrom.com (castles532.castles.com [208.214.165.96]) by hub.freebsd.org (Postfix) with ESMTP id EFAAF150DC for ; Fri, 1 Oct 1999 00:50:28 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.3/8.8.8) with ESMTP id AAA02418; Fri, 1 Oct 1999 00:43:11 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199910010743.AAA02418@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: "Ronald G. Minnich" Cc: hackers@freebsd.org Subject: Re: return to real mode In-reply-to: Your message of "Wed, 29 Sep 1999 11:17:58 MDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 01 Oct 1999 00:43:11 -0700 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > anybody got some reliable, tested, known-good code for getting back to > real mode? I'm to the point where I have a working GDT, and paging is > turned off, but the last step -- turning off protection enable -- is not > working for me. You want to be more explicit about why you want to get back? There are possibly alternatives, or other collateral damage issues that might be worth commenting on. -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Oct 1 8:57:13 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.rdc1.sfba.home.com (ha1.rdc1.sfba.home.com [24.0.0.66]) by hub.freebsd.org (Postfix) with ESMTP id 1509014E43 for ; Fri, 1 Oct 1999 08:56:57 -0700 (PDT) (envelope-from adsharma@c62443-a.frmt1.sfba.home.com) Received: from c62443-a.frmt1.sfba.home.com ([24.0.69.165]) by mail.rdc1.sfba.home.com (InterMail v4.01.01.00 201-229-111) with ESMTP id <19991001155656.BLVK5242.mail.rdc1.sfba.home.com@c62443-a.frmt1.sfba.home.com>; Fri, 1 Oct 1999 08:56:56 -0700 Received: (from adsharma@localhost) by c62443-a.frmt1.sfba.home.com (8.9.3/8.9.3) id IAA15716; Fri, 1 Oct 1999 08:40:46 -0700 Date: Fri, 1 Oct 1999 08:40:45 -0700 From: Arun Sharma To: Julian Elischer Cc: hackers@FreeBSD.ORG Subject: Re: Huge Binaries.. Message-ID: <19991001084045.A15705@home.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.6i In-Reply-To: ; from Julian Elischer on Thu, Sep 30, 1999 at 10:57:42PM -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Sep 30, 1999 at 10:57:42PM -0700, Julian Elischer wrote: > I just installed it. > the binary is 13234176 bytes long!! > yes folks, that's 13 MB! That's an improvement from 4.61! $ ls -l /usr/local/lib/netscape/communicator-4.61.bin -r-xr-xr-x 1 root wheel 13271040 Jun 10 10:00 /usr/local/lib/netscape/communicator-4.61.bin -Arun To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Oct 1 9:35:46 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (Postfix) with ESMTP id B33A714C8A for ; Fri, 1 Oct 1999 09:35:42 -0700 (PDT) (envelope-from dcs@newsguy.com) Received: from newsguy.com (p02-dn02kiryunisiki.gunma.ocn.ne.jp [210.163.200.99]) by peach.ocn.ne.jp (8.9.1a/OCN) with ESMTP id BAA12841; Sat, 2 Oct 1999 01:35:16 +0900 (JST) Message-ID: <37F4DDE8.7D452D32@newsguy.com> Date: Sat, 02 Oct 1999 01:14:32 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.6 [en] (Win98; I) X-Accept-Language: en,pt-BR,ja MIME-Version: 1.0 To: Guido van Rooij Cc: FreeBSD-hackers Subject: Re: booting from a second slice References: <19990930215402.A449@gvr.gvr.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Guido van Rooij wrote: > > I know about the 1024 cylinder limit, however I would expect loader > to be able to work beyond that limit.. Loader uses BIOS and, thus, has all of BIOS limits. -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org Rule 69: Do unto other's code as you'd have it do unto yours To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Oct 1 10: 4: 1 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31]) by hub.freebsd.org (Postfix) with ESMTP id B9EFF15A97 for ; Fri, 1 Oct 1999 10:03:56 -0700 (PDT) (envelope-from des@flood.ping.uio.no) Received: (from des@localhost) by flood.ping.uio.no (8.9.3/8.9.3) id TAA17078; Fri, 1 Oct 1999 19:03:54 +0200 (CEST) (envelope-from des) To: Jaakko Salomaa Cc: hackers@FreeBSD.ORG Subject: Re: FTP directory listing with ftpio(3) and fetch(3) References: From: Dag-Erling Smorgrav Date: 01 Oct 1999 19:03:52 +0200 In-Reply-To: Jaakko Salomaa's message of "Sun, 26 Sep 1999 18:31:08 +0300 (EEST)" Message-ID: Lines: 12 X-Mailer: Gnus v5.5/Emacs 19.34 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Jaakko Salomaa writes: > Hey, how am I supposed to fetch directory listing with ftpio(3) or > fecth(3)? ftpio doesn't seem to contain necessary functions for it, and > fetch's ones aren't implemented. Type 'man 3 fetch', scroll down to the BUGS section, and see the light. Next, scroll back up to the AUTHORS section and find out who to contact :) DES -- Dag-Erling Smorgrav - des@flood.ping.uio.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Oct 1 10:11:16 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from postal1.lbl.gov (postal1.lbl.gov [128.3.7.82]) by hub.freebsd.org (Postfix) with ESMTP id AD08215A9D for ; Fri, 1 Oct 1999 10:10:25 -0700 (PDT) (envelope-from jin@george.lbl.gov) Received: from SpamWall.lbl.gov (localhost [127.0.0.1]) by postal1.lbl.gov (8.9.3/8.9.3) with ESMTP id KAA09430 for ; Fri, 1 Oct 1999 10:10:24 -0700 (PDT) From: jin@george.lbl.gov Received: from george.lbl.gov (george.lbl.gov [131.243.2.12]) by SpamWall.lbl.gov (8.9.3/8.9.3) with ESMTP id KAA09416 for ; Fri, 1 Oct 1999 10:10:23 -0700 (PDT) Received: (from jin@localhost) by george.lbl.gov (8.9.1b+Sun/8.9.1) id KAA18313 for hackers@freebsd.org; Fri, 1 Oct 1999 10:10:23 -0700 (PDT) Date: Fri, 1 Oct 1999 10:10:23 -0700 (PDT) Message-Id: <199910011710.KAA18313@george.lbl.gov> To: hackers@freebsd.org Subject: SCSI disk naming problem Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Current FreeBSD SCSi disk naming mechanism is problem for using more than one disks in the chain during the disk failure. The problem is that the name is not fixed with is SCSI ID. e.g., if one disk is presented in the chain, regardless its SCSI ID, it is always named "da0"; if two disks are installed, the one with lower ID is named da0 and the other will be named as da1. When the lower ID one is crashed, then the other disk will be named as da0 (from da1) after reboot, and it is not mountable due to the name changing. If a system has a UW SCSI controller with 15 disks in the chain, when the first disk (ID = 0) crashed, all rest 14 disks will be useless until either fstab modified or another disk is added with SCSI ID = 0. Why not we use a fixed name corresponding the SCSI ID. That is, disk with ID 0 will be always named as da0, and disk with ID 1 will be always named da1, etc.? Is there problem with fixed disk naming mechanism? -Jin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Oct 1 10:39:21 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from haldjas.folklore.ee (Haldjas.folklore.ee [193.40.6.121]) by hub.freebsd.org (Postfix) with ESMTP id E781715A2E for ; Fri, 1 Oct 1999 10:39:10 -0700 (PDT) (envelope-from narvi@haldjas.folklore.ee) Received: from localhost (narvi@localhost) by haldjas.folklore.ee (8.9.3/8.9.3) with SMTP id UAA20464; Fri, 1 Oct 1999 20:38:48 +0300 (EEST) (envelope-from narvi@haldjas.folklore.ee) Date: Fri, 1 Oct 1999 20:38:48 +0300 (EEST) From: Narvi To: jin@george.lbl.gov Cc: hackers@FreeBSD.ORG Subject: Re: SCSI disk naming problem In-Reply-To: <199910011710.KAA18313@george.lbl.gov> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG See LINT on details of how to wire down scsi devices... Your proposal doesn't take adding a second scsi card into account. On Fri, 1 Oct 1999 jin@george.lbl.gov wrote: > Current FreeBSD SCSi disk naming mechanism is problem for using more than > one disks in the chain during the disk failure. > > The problem is that the name is not fixed with is SCSI ID. e.g., > if one disk is presented in the chain, regardless its SCSI ID, it is > always named "da0"; > > if two disks are installed, the one with lower ID is named da0 and the > other will be named as da1. When the lower ID one is crashed, then the > other disk will be named as da0 (from da1) after reboot, and it is not > mountable due to the name changing. > > If a system has a UW SCSI controller with 15 disks in the chain, > when the first disk (ID = 0) crashed, all rest 14 disks will be > useless until either fstab modified or another disk is added with > SCSI ID = 0. > > Why not we use a fixed name corresponding the SCSI ID. That is, > disk with ID 0 will be always named as da0, and disk with ID 1 > will be always named da1, etc.? > > Is there problem with fixed disk naming mechanism? > > -Jin > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Oct 1 10:40: 6 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from peloton.runet.edu (peloton.runet.edu [137.45.96.205]) by hub.freebsd.org (Postfix) with ESMTP id C986914D4A for ; Fri, 1 Oct 1999 10:40:01 -0700 (PDT) (envelope-from brett@peloton.runet.edu) Received: from localhost (brett@localhost) by peloton.runet.edu (8.9.3/8.9.3) with ESMTP id NAA02435; Fri, 1 Oct 1999 13:39:55 -0400 (EDT) (envelope-from brett@peloton.runet.edu) Date: Fri, 1 Oct 1999 13:39:55 -0400 (EDT) From: Brett Taylor To: Julian Elischer Cc: hackers@FreeBSD.ORG Subject: Re: Huge Binaries.. In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi Julian, On Thu, 30 Sep 1999, Julian Elischer wrote: > Has anyone looked at netscape Communicator 4.7 for FreeBSD??? > > I just installed it. the binary is 13234176 bytes long!! Is this much bigger than before? I usually use Navigator instead as I don't want all the bloat. The 4.61 version of navigator is 7712768 bytes. That's about 1/2 the size and if you're not using the composer, news reader or mailer you might as well toss Communicator in favor of Navigator. Brett ***************************************************** Brett Taylor brett@peloton.runet.edu * Dept of Chem and Physics * Curie 39A (540) 831-6147 * ***************************************************** To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Oct 1 10:55:30 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from postal1.lbl.gov (postal1.lbl.gov [128.3.7.82]) by hub.freebsd.org (Postfix) with ESMTP id B13061518E for ; Fri, 1 Oct 1999 10:55:24 -0700 (PDT) (envelope-from jin@george.lbl.gov) Received: from SpamWall.lbl.gov (localhost [127.0.0.1]) by postal1.lbl.gov (8.9.3/8.9.3) with ESMTP id KAA23854 for ; Fri, 1 Oct 1999 10:55:23 -0700 (PDT) From: jin@george.lbl.gov Received: from george.lbl.gov (george.lbl.gov [131.243.2.12]) by SpamWall.lbl.gov (8.9.3/8.9.3) with ESMTP id KAA23353; Fri, 1 Oct 1999 10:54:00 -0700 (PDT) Received: (from jin@localhost) by george.lbl.gov (8.9.1b+Sun/8.9.1) id KAA19866; Fri, 1 Oct 1999 10:54:00 -0700 (PDT) Date: Fri, 1 Oct 1999 10:54:00 -0700 (PDT) Message-Id: <199910011754.KAA19866@george.lbl.gov> To: narvi@haldjas.folklore.ee Subject: Re: SCSI disk naming problem Cc: hackers@FreeBSD.ORG Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > See LINT on details of how to wire down scsi devices... > > Your proposal doesn't take adding a second scsi card into account. Well, I did not mean that has to be da0, da1, etc., but similar thing like dac0t0d0, dac0t1d0, ... dac3t4d0, etc. which is much clear what disk is. A few people does not like this one because the name is long, and it is like some commerical configuration. They said that this is Free software. Manually wiring down disks is OK for a small set of hosts. 100+ hosts with two or three controllers with 100 TB disks will be terribly pain during the setup and maintenance. -Jin > On Fri, 1 Oct 1999 jin@george.lbl.gov wrote: > > > Current FreeBSD SCSi disk naming mechanism is problem for using more than > > one disks in the chain during the disk failure. > > > > The problem is that the name is not fixed with is SCSI ID. e.g., > > if one disk is presented in the chain, regardless its SCSI ID, it is > > always named "da0"; > > > > if two disks are installed, the one with lower ID is named da0 and the > > other will be named as da1. When the lower ID one is crashed, then the > > other disk will be named as da0 (from da1) after reboot, and it is not > > mountable due to the name changing. > > > > If a system has a UW SCSI controller with 15 disks in the chain, > > when the first disk (ID = 0) crashed, all rest 14 disks will be > > useless until either fstab modified or another disk is added with > > SCSI ID = 0. > > > > Why not we use a fixed name corresponding the SCSI ID. That is, > > disk with ID 0 will be always named as da0, and disk with ID 1 > > will be always named da1, etc.? > > > > Is there problem with fixed disk naming mechanism? , To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Oct 1 11:12:57 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from nimitz.ca.sandia.gov (nimitz.ca.sandia.gov [146.246.243.56]) by hub.freebsd.org (Postfix) with ESMTP id 51A5415AB4 for ; Fri, 1 Oct 1999 11:12:48 -0700 (PDT) (envelope-from bmah@nimitz.ca.sandia.gov) Received: (from bmah@localhost) by nimitz.ca.sandia.gov (8.9.3/8.9.3) id LAA78411; Fri, 1 Oct 1999 11:11:27 -0700 (PDT) Message-Id: <199910011811.LAA78411@nimitz.ca.sandia.gov> X-Mailer: exmh version 2.1.0 09/18/1999 To: jin@george.lbl.gov Cc: narvi@haldjas.folklore.ee, hackers@FreeBSD.ORG Subject: Re: SCSI disk naming problem In-Reply-To: Your message of "Fri, 01 Oct 1999 10:54:00 PDT." <199910011754.KAA19866@george.lbl.gov> From: bmah@CA.Sandia.GOV (Bruce A. Mah) Reply-To: bmah@CA.Sandia.GOV X-Face: g~c`.{#4q0"(V*b#g[i~rXgm*w;:nMfz%_RZLma)UgGN&=j`5vXoU^@n5v4:OO)c["!w)nD/!!~e4Sj7LiT'6*wZ83454H""lb{CC%T37O!!'S$S&D}sem7I[A 2V%N&+ X-Url: http://www.ca.sandia.gov/~bmah/ Mime-Version: 1.0 Content-Type: multipart/signed; boundary="==_Exmh_1773480329P"; micalg=pgp-sha1; protocol="application/pgp-signature" Content-Transfer-Encoding: 7bit Date: Fri, 01 Oct 1999 11:11:27 -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --==_Exmh_1773480329P Content-Type: text/plain; charset=us-ascii If memory serves me right, jin@george.lbl.gov wrote: > > See LINT on details of how to wire down scsi devices... > > > > Your proposal doesn't take adding a second scsi card into account. > > Well, I did not mean that has to be da0, da1, etc., but similar thing > like dac0t0d0, dac0t1d0, ... dac3t4d0, etc. which is much clear what > disk is. > A few people does not like this one because the name is long, and it > is like some commerical configuration. They said that this is Free > software. That's an interesting argument on the part of a few people. The commercial UNIX I first adminned had wired down, short names for disks (rz0, rz1, rz2, ... ). This was very nice. > Manually wiring down disks is OK for a small set of hosts. 100+ hosts > with two or three controllers with 100 TB disks will be terribly pain > during the setup and maintenance. It depends on what you mean by "manually". Presumably, these 100+ hosts have fairly similar kernel configurations, so you only need to build a small number of "wired down" kernels, and then distribute these out to the hosts. I've found that that having wired down SCSI devices is a Good Thing (TM), and it's one of the first things that I fix when I start building kernels for a new version of FreeBSD. I guess I've just gotten used to it. Bruce. --==_Exmh_1773480329P Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: PGPfreeware 5.0i for non-commercial use MessageID: LUlwlEqos4FKUwuTyJe6dOjm71Z501J+ iQA/AwUBN/T5T9jKMXFboFLDEQKZTACfV0f4P7b1WTBqgKINiB/OCsOiOWQAnjh7 eIJZOFOBd5sTIvG5r6eaNhyq =t+w5 -----END PGP SIGNATURE----- --==_Exmh_1773480329P-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Oct 1 11:35:29 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from postal1.lbl.gov (postal1.lbl.gov [128.3.7.82]) by hub.freebsd.org (Postfix) with ESMTP id A7EA3153EF for ; Fri, 1 Oct 1999 11:35:12 -0700 (PDT) (envelope-from jin@george.lbl.gov) Received: from SpamWall.lbl.gov (localhost [127.0.0.1]) by postal1.lbl.gov (8.9.3/8.9.3) with ESMTP id LAA06829 for ; Fri, 1 Oct 1999 11:35:09 -0700 (PDT) From: jin@george.lbl.gov Received: from george.lbl.gov (george.lbl.gov [131.243.2.12]) by SpamWall.lbl.gov (8.9.3/8.9.3) with ESMTP id LAA06210; Fri, 1 Oct 1999 11:33:46 -0700 (PDT) Received: (from jin@localhost) by george.lbl.gov (8.9.1b+Sun/8.9.1) id LAA20871; Fri, 1 Oct 1999 11:33:46 -0700 (PDT) Date: Fri, 1 Oct 1999 11:33:46 -0700 (PDT) Message-Id: <199910011833.LAA20871@george.lbl.gov> To: bmah@CA.Sandia.GOV Subject: Re: SCSI disk naming problem Cc: hackers@FreeBSD.ORG, narvi@haldjas.folklore.ee Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG bmah@CA.Sandia.GOV wrote: > If memory serves me right, jin@george.lbl.gov wrote: > > > See LINT on details of how to wire down scsi devices... > > > > > > Your proposal doesn't take adding a second scsi card into account. > > > > Well, I did not mean that has to be da0, da1, etc., but similar thing > > like dac0t0d0, dac0t1d0, ... dac3t4d0, etc. which is much clear what > > disk is. > > A few people does not like this one because the name is long, and it > > is like some commerical configuration. They said that this is Free > > software. > > That's an interesting argument on the part of a few people. The > commercial UNIX I first adminned had wired down, short names for disks > (rz0, rz1, rz2, ... ). This was very nice. This one does not resolve the controller problem either as narvi@haldjas.folklore.ee said. So, I guess dac0t0, dac0t1, ... dac3t4, will be good enough if we want to be short, but anything shorter than this will be meaningless. > > Manually wiring down disks is OK for a small set of hosts. 100+ hosts > > with two or three controllers with 100 TB disks will be terribly pain > > during the setup and maintenance. > > It depends on what you mean by "manually". Presumably, these 100+ > hosts have fairly similar kernel configurations, so you only need to > build a small number of "wired down" kernels, and then distribute these > out to the hosts. > > I've found that that having wired down SCSI devices is a Good Thing > (TM), and it's one of the first things that I fix when I start building > kernels for a new version of FreeBSD. I guess I've just gotten used to > it. > > Bruce. I guess you missed the point that I do want to wire down the name. This is the original debate. But, I do not want to wire down the name by hand. The system should be able to take care this simple thing. As you mentioned, digit UNIX does it, Solaris does it, why not FreeBSD? Because it is FreeWare so we cannot do some thing good as commercial UNIXs do? -Jin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Oct 1 11:58:49 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from panzer.kdm.org (panzer.kdm.org [216.160.178.169]) by hub.freebsd.org (Postfix) with ESMTP id C4DC314C4F for ; Fri, 1 Oct 1999 11:58:43 -0700 (PDT) (envelope-from ken@panzer.kdm.org) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id MAA41083; Fri, 1 Oct 1999 12:56:57 -0600 (MDT) (envelope-from ken) Message-Id: <199910011856.MAA41083@panzer.kdm.org> Subject: Re: SCSI disk naming problem In-Reply-To: <199910011754.KAA19866@george.lbl.gov> from "jin@george.lbl.gov" at "Oct 1, 1999 10:54:00 am" To: jin@george.lbl.gov Date: Fri, 1 Oct 1999 12:56:57 -0600 (MDT) Cc: narvi@haldjas.folklore.ee, hackers@FreeBSD.ORG From: "Kenneth D. Merry" X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG jin@george.lbl.gov wrote... > > On Fri, 1 Oct 1999 jin@george.lbl.gov wrote: > > > > > Current FreeBSD SCSi disk naming mechanism is problem for using more than > > > one disks in the chain during the disk failure. > > > > > > The problem is that the name is not fixed with is SCSI ID. e.g., > > > if one disk is presented in the chain, regardless its SCSI ID, it is > > > always named "da0"; > > > > > > if two disks are installed, the one with lower ID is named da0 and the > > > other will be named as da1. When the lower ID one is crashed, then the > > > other disk will be named as da0 (from da1) after reboot, and it is not > > > mountable due to the name changing. > > > > > > If a system has a UW SCSI controller with 15 disks in the chain, > > > when the first disk (ID = 0) crashed, all rest 14 disks will be > > > useless until either fstab modified or another disk is added with > > > SCSI ID = 0. > > > > > > Why not we use a fixed name corresponding the SCSI ID. That is, > > > disk with ID 0 will be always named as da0, and disk with ID 1 > > > will be always named da1, etc.? > > > > > > Is there problem with fixed disk naming mechanism? [ ... ] > > See LINT on details of how to wire down scsi devices... > > > > Your proposal doesn't take adding a second scsi card into account. > > Well, I did not mean that has to be da0, da1, etc., but similar thing > like dac0t0d0, dac0t1d0, ... dac3t4d0, etc. which is much clear what > disk is. > A few people does not like this one because the name is long, and it > is like some commerical configuration. They said that this is Free > software. You can pretty easily write a script to create device nodes named whatever you want. As long as the major and minor numbers are correct, you can call what would be /dev/da0a /dev/dac0t0d0a or whatever you like. I think it is possible, however, to come up with a somewhat reasonable naming scheme within the current framework. > Manually wiring down disks is OK for a small set of hosts. 100+ hosts > with two or three controllers with 100 TB disks will be terribly pain > during the setup and maintenance. I would suggest that you come up with a standard naming scheme, and then use it across all of your machines. You could do something like: controller ahc0 controller ahc1 controller ahc2 controller scbus0 at ahc0 controller scbus1 at ahc1 controller scbus2 at ahc2 device da0 at scbus0 target 0 unit 0 device da1 at scbus0 target 1 unit 0 device da2 at scbus0 target 2 unit 0 ... device da14 at scbus0 target 14 unit 0 device da20 at scbus1 target 0 unit 0 device da21 at scbus1 target 1 unit 0 ... device da34 at scbus1 target 14 unit 0 device da40 at scbus2 target 0 unit 0 device da41 at scbus2 target 1 unit 0 ... device da54 at scbus2 target 14 unit 0 If you've got reasonably consistent controller hardware across the machines, you could use one wiring setup like the one above for all the machines. If you have different controller drivers on the different machines, you could probably just elminate the controller<->bus wiring and go from there. You can design a maximal wire-down configuration for your largest machine, and it should just work on smaller machines. For instance, if your large machine has 7 SCSI busses and 15 disks per chain, you could set them up as da0 through da134 or so. The wiring configuration, though, would work even for a machine with one disk. Ken -- Kenneth Merry ken@kdm.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Oct 1 12:10:13 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id D20E3150BB for ; Fri, 1 Oct 1999 12:10:05 -0700 (PDT) (envelope-from bright@wintelcom.net) Received: from localhost (bright@localhost) by fw.wintelcom.net (8.9.3/8.9.3) with ESMTP id MAA01774; Fri, 1 Oct 1999 12:28:10 -0700 (PDT) Date: Fri, 1 Oct 1999 12:28:10 -0700 (PDT) From: Alfred Perlstein To: jin@george.lbl.gov Cc: hackers@FreeBSD.ORG Subject: Re: SCSI disk naming problem In-Reply-To: <199910011710.KAA18313@george.lbl.gov> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 1 Oct 1999 jin@george.lbl.gov wrote: > Current FreeBSD SCSi disk naming mechanism is problem for using more than > one disks in the chain during the disk failure. > > The problem is that the name is not fixed with is SCSI ID. e.g., > if one disk is presented in the chain, regardless its SCSI ID, it is > always named "da0"; > > if two disks are installed, the one with lower ID is named da0 and the > other will be named as da1. When the lower ID one is crashed, then the > other disk will be named as da0 (from da1) after reboot, and it is not > mountable due to the name changing. > > If a system has a UW SCSI controller with 15 disks in the chain, > when the first disk (ID = 0) crashed, all rest 14 disks will be > useless until either fstab modified or another disk is added with > SCSI ID = 0. > > Why not we use a fixed name corresponding the SCSI ID. That is, > disk with ID 0 will be always named as da0, and disk with ID 1 > will be always named da1, etc.? > > Is there problem with fixed disk naming mechanism? no, read the kernel LINT config file. -Alfred Perlstein - [bright@rush.net|alfred@freebsd.org] Wintelcom systems administrator and programmer - http://www.wintelcom.net/ [bright@wintelcom.net] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Oct 1 12:25:21 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from white.dogwood.com (white.dogwood.com [209.24.60.226]) by hub.freebsd.org (Postfix) with ESMTP id E279314C9B for ; Fri, 1 Oct 1999 12:24:55 -0700 (PDT) (envelope-from dave@dogwood.com) Received: (from dave@localhost) by white.dogwood.com (8.9.3/8.9.3) id MAA36618; Fri, 1 Oct 1999 12:24:21 -0700 (PDT) (envelope-from dave) From: Dave Cornejo Message-Id: <199910011924.MAA36618@white.dogwood.com> Subject: Re: Netscape Bus Error In-Reply-To: <199909272010.OAA12060@mt.sri.com> from Nate Williams at "Sep 27, 1999 02:10:13 pm" To: Nate Williams Date: Fri, 1 Oct 1999 12:24:21 -0700 (PDT) Cc: Scm486@aol.com, freebsd-hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL61 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Nate Williams wrote: > In short, it's a netscape bug.... maybe not - i recently received buckets of these on a system i was experimenting with overclocking on - an upgraded heatsink fixed it. I've also seen it when I tweak the BIOS settings a bit too aggresively... -- Dave Cornejo - Dogwood Media, Fremont, California General Magician & Registered Be Developer To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Oct 1 12:39:58 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from bingnet2.cc.binghamton.edu (bingnet2.cc.binghamton.edu [128.226.1.18]) by hub.freebsd.org (Postfix) with ESMTP id 97197152B5 for ; Fri, 1 Oct 1999 12:39:51 -0700 (PDT) (envelope-from zzhang@cs.binghamton.edu) Received: from sol.cs.binghamton.edu (cs1-gw.cs.binghamton.edu [128.226.171.72]) by bingnet2.cc.binghamton.edu (8.9.3/8.9.3) with SMTP id PAA08041 for ; Fri, 1 Oct 1999 15:39:51 -0400 (EDT) Date: Fri, 1 Oct 1999 15:25:25 -0400 (EDT) From: Zhihui Zhang To: freebsd-hackers@freebsd.org Subject: block I/O on a locked vnode Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG The following is copied from the comments of FFS code: "Block devices associated with filesystems may have new I/O requests posted for them even if the vnode is *locked*, so no amount of trying will get them clean. Thus we give block devices a good effort, then just give up. For all other file types, go around and try again until it is clean." Can anyone explain to me when this situation will occur and, preferrably, point to the place of the related source code? Any help is appreciated. -------------------------------------------------- Zhihui Zhang. Please visit http://www.freebsd.org -------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Oct 1 12:40:28 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from maild.telia.com (maild.telia.com [194.22.190.3]) by hub.freebsd.org (Postfix) with ESMTP id 12F7E14EA4; Fri, 1 Oct 1999 12:40:24 -0700 (PDT) (envelope-from stefan@syprix.se) Received: from d1o49.telia.com (root@d1o49.telia.com [195.198.194.241]) by maild.telia.com (8.9.3/8.9.3) with ESMTP id VAA22492; Fri, 1 Oct 1999 21:40:23 +0200 (CEST) Received: from syprix.se (t4o49p21.telia.com [195.198.194.201]) by d1o49.telia.com (8.8.8/8.8.5) with ESMTP id VAA22462; Fri, 1 Oct 1999 21:40:21 +0200 (CEST) Message-ID: <37F511AE.1400BCB8@syprix.se> Date: Fri, 01 Oct 1999 21:55:26 +0200 From: Stefan Lindgren Reply-To: stefan@syprix.se Organization: Syprix AB X-Mailer: Mozilla 4.6 [en] (Win98; I) X-Accept-Language: en MIME-Version: 1.0 To: Soren Schmidt Cc: freebsd-hackers@freebsd.org, freebsd-hardware@freebsd.org Subject: Re: Tyan Dual PPRO Bios 5.1 problem... References: <199909300633.IAA29925@freebsd.dk> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Thanks for the help Soren, The disk is a Seagate Medalist 6.2 GB UDMA But now I have tested all PIO modes(0 - 4 and auto) and disabled udma. It still doesn't work. I get different results when I change PIO. Once I got some message like: Page fault: Couldn't init disk...(something) Any clue? /stefan Soren Schmidt wrote: > > It seems Stefan Lindgren wrote: > > I get page faults, kernel panic(trap 12) and the system won't boot. > > > > It looks that it could be memory related, but the system works fine with > > the EIDE disk. > > Hmm, probably because the system is getting bad data from the drive. > Are you using (U)DMA ??, try to switch that off in the driver, or try to > "dumb down" the drive in the BIOS (you can set the speed to PIO3 > there and still run DMA allthough slower) that helped me and the > drive I couldn't get to work otherwise. BTW what make/type of drive > is it, it might be a known bad one.... > > -Soren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Oct 1 13: 2:46 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id 2AB3F14CB2; Fri, 1 Oct 1999 13:02:33 -0700 (PDT) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id WAA64288; Fri, 1 Oct 1999 22:02:32 +0200 (CEST) (envelope-from sos) From: Soren Schmidt Message-Id: <199910012002.WAA64288@freebsd.dk> Subject: Re: Tyan Dual PPRO Bios 5.1 problem... In-Reply-To: <37F511AE.1400BCB8@syprix.se> from Stefan Lindgren at "Oct 1, 1999 09:55:26 pm" To: stefan@syprix.se Date: Fri, 1 Oct 1999 22:02:32 +0200 (CEST) Cc: freebsd-hackers@FreeBSD.ORG, freebsd-hardware@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems Stefan Lindgren wrote: > Thanks for the help Soren, > > The disk is a Seagate Medalist 6.2 GB UDMA > But now I have tested all PIO modes(0 - 4 and auto) and disabled udma. > It still doesn't work. > I get different results when I change PIO. Once I got some message like: > Page fault: Couldn't init disk...(something) > > Any clue? Not really, have you tried with another disk ?? As said I had an older Maxtor that wouldn't work, but I've never had a problem since... -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Oct 1 13:10:45 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from ihemlsrv.firewall.lucent.com (ihemail1.lucent.com [192.11.222.161]) by hub.freebsd.org (Postfix) with ESMTP id 0D0D314D24 for ; Fri, 1 Oct 1999 13:10:31 -0700 (PDT) (envelope-from gsrmdr@lucent.com) Received: from ihemlsrv.firewall.lucent.com (localhost [127.0.0.1]) by ihemlsrv.firewall.lucent.com (Pro-8.9.3/8.9.3) with ESMTP id QAA25409 for ; Fri, 1 Oct 1999 16:10:29 -0400 (EDT) Received: from bighorn.dr.lucent.com (h135-9-1-59.lucent.com [135.9.1.59]) by ihemlsrv.firewall.lucent.com (Pro-8.9.3/8.9.3) with SMTP id QAA25377 for ; Fri, 1 Oct 1999 16:10:29 -0400 (EDT) Received: by bighorn.dr.lucent.com (SMI-8.6/EMS-1.5 sol2) id OAA05112; Fri, 1 Oct 1999 14:10:26 -0600 Received: from drgpaxon by bighorn.dr.lucent.com (SMI-8.6/EMS-1.5 sol2) id OAA05090; Fri, 1 Oct 1999 14:10:23 -0600 Received: from lucent.com by drgpaxon (8.8.8+Sun/EMS-L SunOS) id OAA04749; Fri, 1 Oct 1999 14:10:22 -0600 (MDT) Message-ID: <37F51525.55BDEF23@lucent.com> Date: Fri, 01 Oct 1999 14:10:13 -0600 From: Gary Ruwaldt X-Mailer: Mozilla 4.08 [en] (WinNT; U) MIME-Version: 1.0 To: freebsd-hackers@freeBSD.org Subject: radix.c, Hey is this a bug ? Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hey is this a bug ? I downloaded the code for radix.c and radix.h and was trying to get a tree that looks like the one in TCP/IP Illustrated V.2 page 563 A.K.A "the book". I set up a test program to put the same data into the tree, page 560 and noticed a couple of differences. This is a copy of the data I placed in the tree: struct myStuff MyStuff [MaxEntries] = { "127.0.0.0", 0xff000000, "127.0.0.1", 0xffffffff, "128.32.33.5", 0xffffffff, "140.252.13.32", 0xffffffe0, "140.252.13.33", 0xffffffff, "140.252.13.34", 0xffffffff, "140.252.13.35", 0xffffffff, "140.252.13.65", 0xffffffff, "224.0.0.0", 0xff000000, "224.0.0.1", 0xffffffff, "0.0.0.0", 0x00000000, }; For the first entry 127.0.0.0 with a subnet mask of 0xff 000000 the radix node entry's mask pointer pointed to the one's entry i.e. radix node in the mask tree. This caused a problem with the search i.e. rn_matchaddr of 127.0.0.0, because the length of the key was taken from this mask entry as 0xff. I have modified the code to get the tree to look like the one in "the book" but I have eliminated the benifit of removing trailing zeros. A couple of questions; 1. Can someone explain how the removal of trailing zeros is suppose to work.? 2. Is this a real bug or pilot error. If pilot error what did I do wrong? If it is a real bug the explaintion for question one (1) might help me implement a solution, ya think? My next step is to turn this code into a C++ class, has anyone already done this? Yea, I look around on the WWW, although maybe not in the right sites. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Oct 1 13:23: 2 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from hotmail.com (f116.law4.hotmail.com [216.33.149.116]) by hub.freebsd.org (Postfix) with SMTP id 1215514CD1 for ; Fri, 1 Oct 1999 13:22:52 -0700 (PDT) (envelope-from zzhangsuny@hotmail.com) Received: (qmail 65549 invoked by uid 0); 1 Oct 1999 20:22:47 -0000 Message-ID: <19991001202246.65548.qmail@hotmail.com> Received: from 128.226.3.130 by www.hotmail.com with HTTP; Fri, 01 Oct 1999 13:22:46 PDT X-Originating-IP: [128.226.3.130] From: "Zhihui Zhang" To: freebsd-hackers@freebsd.org Subject: block, I/O, on, locked, vnode Date: Fri, 01 Oct 1999 16:22:46 EDT Mime-Version: 1.0 Content-Type: text/plain; format=flowed Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG The following is copied from the comments of FFS code: "Block devices associated with filesystems may have new I/O requests posted for them even if the vnode is *locked*, so no amount of trying will get them clean. Thus we give block devices a good effort, then just give up. For all other file types, go around and try again until it is clean." Can anyone explain to me when this situation will occur and, preferrably, point to the place of the related source code? Any help is appreciated. -Zhihui ______________________________________________________ Get Your Private, Free Email at http://www.hotmail.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Oct 1 13:35:22 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from nimitz.ca.sandia.gov (nimitz.ca.sandia.gov [146.246.243.56]) by hub.freebsd.org (Postfix) with ESMTP id 3315014A17 for ; Fri, 1 Oct 1999 13:35:18 -0700 (PDT) (envelope-from bmah@nimitz.ca.sandia.gov) Received: (from bmah@localhost) by nimitz.ca.sandia.gov (8.9.3/8.9.3) id NAA81193; Fri, 1 Oct 1999 13:33:58 -0700 (PDT) Message-Id: <199910012033.NAA81193@nimitz.ca.sandia.gov> X-Mailer: exmh version 2.1.0 09/18/1999 To: jin@george.lbl.gov Cc: bmah@california.sandia.gov, hackers@FreeBSD.ORG, narvi@haldjas.folklore.ee Subject: Re: SCSI disk naming problem In-Reply-To: Your message of "Fri, 01 Oct 1999 11:33:46 PDT." <199910011833.LAA20871@george.lbl.gov> From: bmah@CA.Sandia.GOV (Bruce A. Mah) Reply-To: bmah@CA.Sandia.GOV X-Face: g~c`.{#4q0"(V*b#g[i~rXgm*w;:nMfz%_RZLma)UgGN&=j`5vXoU^@n5v4:OO)c["!w)nD/!!~e4Sj7LiT'6*wZ83454H""lb{CC%T37O!!'S$S&D}sem7I[A 2V%N&+ X-Url: http://www.ca.sandia.gov/~bmah/ Mime-Version: 1.0 Content-Type: multipart/signed; boundary="==_Exmh_-853294958P"; micalg=pgp-sha1; protocol="application/pgp-signature" Content-Transfer-Encoding: 7bit Date: Fri, 01 Oct 1999 13:33:58 -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --==_Exmh_-853294958P Content-Type: text/plain; charset=us-ascii If memory serves me right, jin@george.lbl.gov wrote: > bmah@CA.Sandia.GOV wrote: > > If memory serves me right, jin@george.lbl.gov wrote: > > > > See LINT on details of how to wire down scsi devices... > > > > > > > > Your proposal doesn't take adding a second scsi card into account. > > > > > > Well, I did not mean that has to be da0, da1, etc., but similar thing > > > like dac0t0d0, dac0t1d0, ... dac3t4d0, etc. which is much clear what > > > disk is. > > > A few people does not like this one because the name is long, and it > > > is like some commerical configuration. They said that this is Free > > > software. > > > > That's an interesting argument on the part of a few people. The > > commercial UNIX I first adminned had wired down, short names for disks > > (rz0, rz1, rz2, ... ). This was very nice. > > This one does not resolve the controller problem either as > narvi@haldjas.folklore.ee said. > > So, I guess dac0t0, dac0t1, ... dac3t4, will be good enough if we want > to be short, but anything shorter than this will be meaningless. Well...I personally prefer the short names. On systems with multiple controllers, the commercial UNIX I used (Ultrix) just continued its numbering with rz0, rz1, rz2, ..., rz6, rz7, rz8, ... FreeBSD lets you do exactly the same thing. Having long device names is confusing to users who only have one disk controller (and I'd bet this is the vast majority). It took me a long time to grok the syntax of Solaris device names and I still get confused about this. Commercial or free doesn't have anything to do with this issue...this scheme would force users to remember and type extra characters that many of them don't need. (/dev/da0s1a is long enough, but /dev/dac0t0d0s1a is a little ridiculous for someone that has only one controller and one drive.) > I guess you missed the point that I do want to wire down the name. > This is the original debate. But, I do not want to wire down the > name by hand. The system should be able to take care this simple > thing. As you mentioned, digit UNIX does it, Solaris does it, why > not FreeBSD? No, I was agreeing with you that wiring down names is good. (I did miss a message or two in the middle of your discussion, apparently, and that may have contributed to my apparently confusion.) But I think your proposed long names are confusing, and I claim that that rebuilding a kernel to get wired-down device names is easy. Perhaps I am misunderstanding what you mean when you say "by hand". I'm envisioning an environment where you have a lot of similarly-configured machines. So you build a kernel (based on GENERIC) to wire down devices ONE TIME, and distribute that kernel out to all the different machines. > Because it is FreeWare so we cannot do some thing good > as commercial UNIXs do? I don't understand this argument. "Free" (i.e. open source) vs. commercial doesn't have anything to do with this issue. Cheers, Bruce. --==_Exmh_-853294958P Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: PGPfreeware 5.0i for non-commercial use MessageID: XLuZVhwPyj0B/Y81yQVEKvp0xbeOI6It iQA/AwUBN/UattjKMXFboFLDEQLa1ACeN1vOjgtY0XgxpbhQYz/ih0qNfT8AnRoE IXhhuQFcWdm7QcJnhAL+Lu60 =XfH0 -----END PGP SIGNATURE----- --==_Exmh_-853294958P-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Oct 1 14:32: 0 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from frmug.org (frmug-gw.frmug.org [193.56.58.252]) by hub.freebsd.org (Postfix) with ESMTP id 1B76614A01 for ; Fri, 1 Oct 1999 14:31:42 -0700 (PDT) (envelope-from roberto@keltia.freenix.fr) Received: (from uucp@localhost) by frmug.org (8.9.3/frmug-2.5/nospam) with UUCP id XAA28745 for hackers@FreeBSD.ORG; Fri, 1 Oct 1999 23:31:36 +0200 (CEST) (envelope-from roberto@keltia.freenix.fr) Received: by keltia.freenix.fr (Postfix, from userid 101) id DA9B28711; Fri, 1 Oct 1999 22:09:31 +0200 (CEST) Date: Fri, 1 Oct 1999 22:09:31 +0200 From: Ollivier Robert To: hackers@FreeBSD.ORG Subject: Re: Huge Binaries.. Message-ID: <19991001220931.A71530@keltia.freenix.fr> Mail-Followup-To: hackers@FreeBSD.ORG References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii User-Agent: Mutt/1.0pre2i In-Reply-To: X-Operating-System: FreeBSD 4.0-CURRENT/ELF AMD-K6/200 & 2x PPro/200 SMP Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG According to Brett Taylor: > That's about 1/2 the size and if you're not using the composer, news > reader or mailer you might as well toss Communicator in favor of > Navigator. Yes but with the navigator, you can't even mail a link or a page... -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 4.0-CURRENT #74: Thu Sep 9 00:20:51 CEST 1999 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Oct 1 14:37: 5 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from postal1.lbl.gov (postal1.lbl.gov [128.3.7.82]) by hub.freebsd.org (Postfix) with ESMTP id 788E714A01 for ; Fri, 1 Oct 1999 14:36:51 -0700 (PDT) (envelope-from jin@george.lbl.gov) Received: from SpamWall.lbl.gov (localhost [127.0.0.1]) by postal1.lbl.gov (8.9.3/8.9.3) with ESMTP id OAA25337 for ; Fri, 1 Oct 1999 14:36:49 -0700 (PDT) From: jin@george.lbl.gov Received: from george.lbl.gov (george.lbl.gov [131.243.2.12]) by SpamWall.lbl.gov (8.9.3/8.9.3) with ESMTP id OAA24997; Fri, 1 Oct 1999 14:35:26 -0700 (PDT) Received: (from jin@localhost) by george.lbl.gov (8.9.1b+Sun/8.9.1) id OAA24213; Fri, 1 Oct 1999 14:35:26 -0700 (PDT) Date: Fri, 1 Oct 1999 14:35:26 -0700 (PDT) Message-Id: <199910012135.OAA24213@george.lbl.gov> To: bmah@CA.Sandia.GOV Subject: Re: SCSI disk naming problem Cc: bmah@california.sandia.gov, hackers@FreeBSD.ORG, narvi@haldjas.folklore.ee Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG bmah@CA.Sandia.GOV wrote: } > > That's an interesting argument on the part of a few people. The } > > commercial UNIX I first adminned had wired down, short names for disks } > > (rz0, rz1, rz2, ... ). This was very nice. } > } > This one does not resolve the controller problem either as } > narvi@haldjas.folklore.ee said. } > } > So, I guess dac0t0, dac0t1, ... dac3t4, will be good enough if we want } > to be short, but anything shorter than this will be meaningless. } } Well...I personally prefer the short names. On systems with multiple } controllers, the commercial UNIX I used (Ultrix) just continued its } numbering with rz0, rz1, rz2, ..., rz6, rz7, rz8, ... FreeBSD lets you } do exactly the same thing. The thing is what is rz44 representing? If kernel spits: "rz44 hardware error 105: write failure -- replace it" Which disk are you going to shutdown and replace without looking at /etc/fstab or /sys/i386/conf/CRUEENT_RUN ? What happens if when you see the message and the host is hosed and needs to be rebooted -- at this time both above files are not available -- ? I do not think dac5t4 is that worse than rz44 (just two charaters long). Maybe it is better. You immediately know the disk with ID 4 on the SCSI controller 5 is one having trouble. If you have just one disk, I think two charaters will not be a big deal anyway. However, it will be great help to identify the disk by this two charaters. } Having long device names is confusing to users who only have one disk } controller (and I'd bet this is the vast majority). It took me a long Yes or No. I know at least 7-10 sites running 50 - 100 nodes of FreeBSD. I believe there are much more than I know. How many FreeBSD servers are running in this world? A single node FreeBSD server on this planet can be a lot. A single disk FreeBSD users could be the majority at this monment, do we want more and more FreeBSD servers runnning around the world? So, we should think about the future. } time to grok the syntax of Solaris device names and I still get confused } about this. Commercial or free doesn't have anything to do with this } issue...this scheme would force users to remember and type extra } is good. (I did } miss a message or two in the middle of your discussion, apparently, and } that may have contributed to my apparently confusion.) } } But I think your proposed long names are confusing, and I claim that } that rebuilding a kernel to get wired-down device names is easy. } } Perhaps I am misunderstanding what you mean when you say "by hand". I'm } envisioning an environment where you have a lot of similarly-configured } machines. So you build a kernel (based on GENERIC) to wire down } devices ONE TIME, and distribute that kernel out to all the different } machines. If kernel can do this automatically, no one has to rebuild the kernel any more, and no one has to remember every thing that may reduce sys-admin costs. This is special for new users/sys-admins. I personal built 1MB script to setup FreeBSD over the 10 years. It is easy for me to add a couple of lines for wired down the SCSI disk name. But, what is about for the new suers and new sys-admins. Should we make things more easier for them? } > Because it is FreeWare so we cannot do some thing good } > as commercial UNIXs do? } } I don't understand this argument. "Free" (i.e. open source) vs. } commercial doesn't have anything to do with this issue. This was some one screamed a couple of years ago. When I pointed out we can do something good like commercial company doing, and one person jumped on top of me and said that Hey, this is FreeWare,but not commercial software, why we should do things like commercial company does? I was scared I had bad approching for FreeWare. Now I think there is nothing wrong if we can use some good idea from any one including commercial sector. So, that is why I would like to tune the name on SCSI disks. -Jin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Oct 1 15:11:30 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from nimitz.ca.sandia.gov (nimitz.ca.sandia.gov [146.246.243.56]) by hub.freebsd.org (Postfix) with ESMTP id E98BF14E7E for ; Fri, 1 Oct 1999 15:11:26 -0700 (PDT) (envelope-from bmah@nimitz.ca.sandia.gov) Received: (from bmah@localhost) by nimitz.ca.sandia.gov (8.9.3/8.9.3) id PAA82111; Fri, 1 Oct 1999 15:10:06 -0700 (PDT) Message-Id: <199910012210.PAA82111@nimitz.ca.sandia.gov> X-Mailer: exmh version 2.1.0 09/18/1999 To: jin@george.lbl.gov Cc: bmah@california.sandia.gov, hackers@FreeBSD.ORG, narvi@haldjas.folklore.ee Subject: Re: SCSI disk naming problem In-Reply-To: Your message of "Fri, 01 Oct 1999 14:35:26 PDT." <199910012135.OAA24213@george.lbl.gov> From: bmah@CA.Sandia.GOV (Bruce A. Mah) Reply-To: bmah@CA.Sandia.GOV X-Face: g~c`.{#4q0"(V*b#g[i~rXgm*w;:nMfz%_RZLma)UgGN&=j`5vXoU^@n5v4:OO)c["!w)nD/!!~e4Sj7LiT'6*wZ83454H""lb{CC%T37O!!'S$S&D}sem7I[A 2V%N&+ X-Url: http://www.ca.sandia.gov/~bmah/ Mime-Version: 1.0 Content-Type: multipart/signed; boundary="==_Exmh_470993314P"; micalg=pgp-sha1; protocol="application/pgp-signature" Content-Transfer-Encoding: 7bit Date: Fri, 01 Oct 1999 15:10:06 -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --==_Exmh_470993314P Content-Type: text/plain; charset=us-ascii If memory serves me right, jin@george.lbl.gov wrote: > bmah@CA.Sandia.GOV wrote: > } Well...I personally prefer the short names. On systems with multiple > } controllers, the commercial UNIX I used (Ultrix) just continued its > } numbering with rz0, rz1, rz2, ..., rz6, rz7, rz8, ... FreeBSD lets you > } do exactly the same thing. > > The thing is what is rz44 representing? If kernel spits: > > "rz44 hardware error 105: write failure -- replace it" > > Which disk are you going to shutdown and replace without looking at > /etc/fstab or /sys/i386/conf/CRUEENT_RUN ? > What happens if when you see the message and the host is hosed and > needs to be rebooted -- at this time both above files are not available -- ? You have a good point, but I also believe that part of any good disaster recovery scheme is having critical system information (like /etc/fstab, dmesg output, etc.) in hardcopy form. And believe me, we've had enough disasters around here the past six months to see the value of that. :-( > I do not think dac5t4 is that worse than rz44 (just two charaters long). > Maybe it is better. You immediately know the disk with ID 4 on the SCSI > controller 5 is one having trouble. And there's also two more characters you need to remember to type correctly. > } Perhaps I am misunderstanding what you mean when you say "by hand". I'm > } envisioning an environment where you have a lot of similarly-configured > } machines. So you build a kernel (based on GENERIC) to wire down > } devices ONE TIME, and distribute that kernel out to all the different > } machines. > > If kernel can do this automatically, no one has to rebuild the kernel > any more, and no one has to remember every thing that may reduce sys-admin > costs. OK. I'm almost convinced on this point, but I still think that if you're managing 100+ machines, you probably already have an easy mechanism for distributing out kernels to them (think "security patches"). > This is special for new users/sys-admins. I personal built 1MB script to > setup FreeBSD over the 10 years. It is easy for me to add a couple of lines > for wired down the SCSI disk name. But, what is about for the new suers and > new sys-admins. Should we make things more easier for them? Making things more easier for new users seems (IMHO) inconsistent with device names that are much longer than they need to be for the common case. > } > Because it is FreeWare so we cannot do some thing good > } > as commercial UNIXs do? > } > } I don't understand this argument. "Free" (i.e. open source) vs. > } commercial doesn't have anything to do with this issue. > > This was some one screamed a couple of years ago. When I pointed out > we can do something good like commercial company doing, and one person > jumped on top of me and said that Hey, this is FreeWare,but not commercial > software, why we should do things like commercial company does? Please don't apply the thinking of one person to an entire community. We've worked together before, and I know you're smarter than that. :-) I'm going to summarize my position, make one final remark, and then get out of the way. 1. I agree that wiring device names down is a good thing. 2. I think that this probably should be the default behavior, but I haven't put enough thought into it to be completely convinced. 3. I disagree with your proposal for longer, more descriptive, device names. I think that it will make the system harder to use for a majority of installations. Ultimately, changing the status quo is going to involve someone (either yourself or someone else) writing up some patches and submitting them for -core's approval. Cheers, Bruce. --==_Exmh_470993314P Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: PGPfreeware 5.0i for non-commercial use MessageID: Vq5j3tXgN/lSJME0XKRw/51Jdt6xuJF+ iQA/AwUBN/UxPtjKMXFboFLDEQJPDwCfe0lDCCfrqraUqVZksM3782mpA38AnjGz mNTBSkRde4fH1W36W+WAJCwP =YGMi -----END PGP SIGNATURE----- --==_Exmh_470993314P-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Oct 1 15:22:42 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from xylan.com (postal.xylan.com [208.8.0.248]) by hub.freebsd.org (Postfix) with ESMTP id D25CD151ED for ; Fri, 1 Oct 1999 15:22:39 -0700 (PDT) (envelope-from wes@softweyr.com) Received: from mailhub.xylan.com by xylan.com (8.8.7/SMI-SVR4 (ind.alcatel.com 2.3 [OUT])) id PAA01327; Fri, 1 Oct 1999 15:21:30 -0700 (PDT) Received: from omni.xylan.com by mailhub.xylan.com (SMI-8.6/SMI-SVR4 (mailhub 2.1 [HUB])) id PAA00309; Fri, 1 Oct 1999 15:21:31 -0700 Received: from softweyr.com (dyn0.utah.xylan.com) by omni.xylan.com (4.1/SMI-4.1 (xylan engr [SPOOL])) id AA17112; Fri, 1 Oct 99 15:21:18 PDT Message-Id: <37F533E5.32A27814@softweyr.com> Date: Fri, 01 Oct 1999 16:21:25 -0600 From: Wes Peters Organization: Softweyr LLC X-Mailer: Mozilla 4.5 [en] (X11; U; FreeBSD 3.1-RELEASE i386) X-Accept-Language: en Mime-Version: 1.0 To: Dag-Erling Smorgrav Cc: Jaakko Salomaa , hackers@FreeBSD.ORG Subject: Re: FTP directory listing with ftpio(3) and fetch(3) References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Dag-Erling Smorgrav wrote: > > Jaakko Salomaa writes: > > > Hey, how am I supposed to fetch directory listing with ftpio(3) or > > fecth(3)? ftpio doesn't seem to contain necessary functions for it, and > > fetch's ones aren't implemented. > > Type 'man 3 fetch', scroll down to the BUGS section, and see the > light. Next, scroll back up to the AUTHORS section and find out who to > contact :) When you contact him, don't applaud, just throw money. Or was that fish? -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC wes@softweyr.com http://softweyr.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Oct 1 15:54:40 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from scam.xcf.berkeley.edu (scam.XCF.Berkeley.EDU [128.32.43.201]) by hub.freebsd.org (Postfix) with SMTP id 4745014E1D for ; Fri, 1 Oct 1999 15:54:31 -0700 (PDT) (envelope-from nordwick@scam.xcf.berkeley.edu) Received: (qmail 53880 invoked by uid 27268); 1 Oct 1999 22:51:27 -0000 Message-ID: <19991001225126.53878.qmail@scam.xcf.berkeley.edu> To: freebsd-hackers@freebsd.org Subject: I was accepted to LokiHack '99 at Atlanta Linux Showcase MIME-Version: 1.0 Content-Type: text/plain; charset="x-unknown" Content-ID: <53875.938818286.1@scam.XCF.Berkeley.EDU> Content-Transfer-Encoding: quoted-printable Date: Fri, 01 Oct 1999 15:51:26 -0700 From: "Jason Nordwick" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This wouldn't seem -hackers worthy, except I offfered to try to port it to freebsd-current. I thought that this would be interesting to people and that I might be abl= e to get some advice from around here. Following is the email thread that happened between Scott Draeker (president of Loki) and Sam Lantinga (Lead Programmer at Loki). After that is the official offer letter with the library specifications (such as what sound library is used and graphics packages). If anybody has any suggestions it would help me greatly. I have already started looking at the sound library, since that = it my weekest area. >>>> save:71 > > >Date: Thu, 30 Sep 1999 13:40:44 PDT >To: nordwick@xcf.berkeley.edu >cc: Scott Draeker , > Sam Lantinga >From: Sam Lantinga >Subject: Re: Loki Hack 1999 Registration > >Return-Path: hercules@lokigames.com >Delivery-Date: Thu Sep 30 13:48:11 1999 >Return-Path: >Delivered-To: nordwick@xcf.berkeley.edu >Sender: hercules@mail.lokigames.com >Organization: Loki Entertainment Software >X-Mailer: Mozilla 4.6 [en] (X11; I; Linux 2.2.12 i686) >X-Accept-Language: en >MIME-Version: 1.0 >References: <199909172205.PAA23305@mail.lokigames.com> >X-UIDL: 1309d17516e3077a05fb7010bee48ba9 > >Nobody wrote: >> = >> Name: >> Jason Nordwick >> = >> E-mail: >> nordwick@xcf.berkeley.edu >> = >> Address: >> 2530 hilleghass #310 >> berkeley, ca 94704 >> = >> Telephone: (510) 5486818 >> = >> Owns CivCTP? No >> = >> Why I Should Participate: I will port C:CtP to FreeBSD-current. > >We will not have FreeBSD machines on-site, but thanks for applying! :) >-- = > -Sam Lantinga, Lead Programmer, Loki Entertainment Software > > > >>>> save:72 > > >Date: Thu, 30 Sep 1999 14:53:34 PDT >To: "Sam Lantinga" , >cc: "Sigyn" >From: Scott Draeker >Subject: Re: Loki Hack 1999 Registration > >Return-Path: highlander@mail.lokigames.com >Delivery-Date: Thu Sep 30 15:10:10 1999 >Return-Path: >Delivered-To: nordwick@xcf.berkeley.edu >x-sender: highlander@mail.lokigames.com >x-mailer: Claris Emailer 2.0v3, January 22, 1998 >Mime-Version: 1.0 >X-UIDL: b14a543c8550012478ca16d822a5d267 > >>> Why I Should Participate: I will port C:CtP to FreeBSD-current. >> >>We will not have FreeBSD machines on-site, but thanks for applying! :) > >Sam. I think this is a legitimate endeavor. We can't set up FreeBSD for = >this gentleman, but if he's willing to do all the work I say have at it! > > > >Scott Draeker >President >Loki Entertainment Software > > > > >>>> save:74 > > >Date: Thu, 30 Sep 1999 15:49:46 PDT >To: nordwick@xcf.berkeley.edu >cc: Scott Draeker , > Sam Lantinga >From: Sam Lantinga >Subject: LokiHack '99 > >Return-Path: hercules@lokigames.com >Delivery-Date: Thu Sep 30 15:57:06 1999 >Return-Path: >Delivered-To: nordwick@xcf.berkeley.edu >Sender: hercules@mail.lokigames.com >Organization: Loki Entertainment Software >X-Mailer: Mozilla 4.6 [en] (X11; I; Linux 2.2.12 i686) >X-Accept-Language: en >MIME-Version: 1.0 >X-UIDL: 4f8c80131644d3c6ab5571a906c054d1 > > >Scott says you're in! >You'll need to bring your own FreeBSD and tools, since we will not have >network access on the contest LAN. > >CivCTP uses threads extensively, and displays to X11. The contest >development systems will have XPERT 98 video cards. We will have source >to all the libraries used in CivCTP available on-site. > >Good luck! :) >-- = > -Sam Lantinga, Lead Programmer, Loki Entertainment Software >(Message save:73) >Date: Fri, 01 Oct 1999 13:47:10 PDT >From: Kayt Sorhaindo >Subject: Welcome to Loki Hack '99 > >Return-Path: sigyn@lokigames.com >Delivery-Date: Fri Oct 1 13:57:05 1999 >Return-Path: >Delivered-To: nordwick@xcf.berkeley.edu >x-mailer: Claris Emailer 2.0v3, January 22, 1998 >Bcc: = >Mime-Version: 1.0 >X-UIDL: 00fe1bd6f5a287838b42aed9cca71142 >X-MIME-Autoconverted: from quoted-printable to 8bit by erdos.hq.askjeeves= .com i > ***d NAA14548 > >part text/plain 6267 >=1B[7mPress to show content...=1B[m >Congratulations! > >We have reviewed your entry form, and would now like to extend an = >official invitation to you to participate in the first annual Loki Hack = >to be held October 11-13 in Atlanta, GA. > >Please: > >* Let us know by the morning of Tuesday, October 5, if you accept or = >decline this invitation. You may email me at sigyn@lokigames.com. > >* Register by Monday, October 4, at https://www.cmsusa.com/linux/ for the= = >free Exhibits Only pass to the Atlanta Linux Showscase. We will = >coordinate the upgrade to a complimentary Three Day Technical pass for = >you to enjoy upon completion of the Hack. > >* Review the Hack FAQ below, and let us know if you have any additional = >questions or concerns. > >We look forward to seeing you in Atlanta! > >Sincerely, > >Kayt Sorhaindo >Loki Entertainment Software > >-------------------------------------------------- > > >WHY IS LOKI SPONSORING THIS EVENT? > >With Loki Hack, we want to give our customers a chance to see the source = >code for a commercial game -- modify it, change the rules the way they = >like, and/or add something they think is missing. We know that many games= = >these days come with sophisticated editing tools, but nothing says "hack"= = >quite like source code... > >This is the closest we can get to open source with our products. The = >world won't see the source, but the contestants will. And all the hacks, = >mods, changes will be posted in binary form for free download. This is = >our chance to show the gaming world what the open source community can = >accomplish. > >WHEN WILL WE SELECT THE GROUP OF 30 HACKERS? > >We will begin to notify contestants on October 1. We will continue = >reviewing new entries until all 30 slots are filled, but no entries = >should be posted after October 4. > >HOW WILL WE SELECT THE HACKERS? > >We will heavily favor people with strong C++ backgrounds. We also prefer = >applicants who are already familiar with the game. = > >WILL WE ACCEPT INTERNATIONAL HACKERS? > >Yes! This contest is not limited to U.S. citizens. In fact, we hope to = >have a strong international contingent. > >WILL THERE BE ANY REGISTRATION DISCOUNT TO THE LINUX SHOWCASE FOR THE = >HACKERS? > >We will provide, free of charge, a Three Day Technical Pass to the ALS (a= = >$300 value). > >WHAT ARE THE HOURS/DATES OF THE HACK? > >It will begin at 3pm on Monday, October 11, and will end on Wednesday, = >October 13, at 3pm. = > >WILL WE PROVIDE ANY HELP TO THE HACKERS? > >We will kick off the event with an "Introduction to the Code" session led= = >by our two Civilization: Call to Power programmers, Sam Lantinga and Matt= = >Carlson. These programmers will also be on site to answer questions for = >the duration of the Hack. > >HOW CAN A HACKER MAKE ANY SWEEPING CHANGES TO CIVCTP IN JUST 48 HOURS? > >They can=B9t. Contestants should focus on a particular aspect of the game= . = >The better the contestant is able to define the proposed change, the more= = >likely they are to complete it in time. And Loki=B9s developers will be o= n = >site during the entire Hack to help avoid lots of time spent looking for = >stuff in the source. If you know what you want to do, we=B9ll give you th= e = >tools to do it. > >CAN WE DESCRIBE THE TECHNICAL INNARDS OF THE GAME? > >The game is approximately half a million lines of C++ code. It is split = >into several sections: UI, networking, sound, and AI. Templates and = >classes are heavily used in the AI, user interface, and networking. There= = >is no documentation other than source comments (and Sam and Matt = >themselves). = > >The game makes use of the following libraries: = > >Simple DirectMedia Layer - http://www.devolution.com/~slouken/SDL >SMPEG - http://www.lokigames.com/development/smpeg.php3 >Zlib - http://www.cdrom.com/pub/infozip/zlib/ >Pthreads - http://pauillac.inria.fr/~xleroy/linuxthreads/ >A subset of the Miles sound API - http://www.radgametools.com/miles.htm > >The game also uses Anet (Activision=B9s networking library). The networki= ng = >drivers and map generators are dynamically loaded using the C dlopen() = >interface. > >We would like to point out that we are also accepting changes that can be= = >accomplished only with datafiles -- i.e. adding a new civilization or a = >new unit. This is not a "fix Civ:CTP bugs" session, but a chance for = >Linux users to express their creativity with the source code. You=B9ve = >played the game. Now show us what you would have done differently! > >WILL WE LOCK THE HACKERS AWAY? > >They will be in a secure room, but will be free to come and go as they = >please. > >WILL WE REQUIRE THE HACKERS TO SIGN LEGAL AGREEMENTS? > >Yes, there will be non-disclosure forms. We are, however, working with = >Activision to make the forms as palatable as possible. > >DO WE PERMIT GROUP COLLABORATION? > >Yes, but it will be up to the winning group to divide any prize. > >WHO ARE THE JUDGES? > >Sam Lantinga, Lead Programmer, Loki >A Producer from Activision >Jeff "Hemos" Bates, Slashdot > >HOW WILL WE JUDGE THE HACKS? > >Judges will take into account many criteria -- usefulness, novelty, = >originality, the degree to which game play is enhanced or modified, etc. = = >Other factors may be more subjective. For example, we may not understand = >or appreciate the addition of a web-browser to the game. > >WHEN IS THE AWARD CEREMONY? > >There will be an open bar reception once the Hack concludes on Wednesday,= = >October 13. Place and time to be provided to the contestants. > >The award ceremony is tentatively scheduled for the afternoon of Friday, = >October 15. Winners need not be present to win. = > >WHAT ARE THE PRIZES? > >All contestants will receive a complimentary copy of Civilization: Call = >to Power for Linux (can be traded for another Loki game if you have this = >one), a Three Day Technical Pass to the Atlanta Linux Showcase (a $300 = >value), a collector=B9s t-shirt, and complimentary food/drinks during th= e = >Hack. > >First Prize: VA Dual Pentium Workstation > >Runners up will received SCSI cards, Voodoo3 cards and soundblaster Live = >cards. > >WILL WE HIRE THE WINNERS? > >We=B9re not sure it=B9s legal to promise to hire a contest winner =8B but= we=B9re = >obviously interested in hiring just that sort of talented individual. > >WILL CIVCTP CUSTOMERS HAVE ACCESS TO THE HACKS? > >Yes! As soon as we return from the Atlanta Linux Showcase (the week of = >October 17), we will post on our website all functional hacks in binary = >form for free download. > >CHEERS! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Oct 1 16: 6:57 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from dt011n66.san.rr.com (dt011n66.san.rr.com [204.210.13.102]) by hub.freebsd.org (Postfix) with ESMTP id 230A514DF5 for ; Fri, 1 Oct 1999 16:06:27 -0700 (PDT) (envelope-from Doug@gorean.org) Received: from localhost (doug@localhost) by dt011n66.san.rr.com (8.9.3/8.8.8) with ESMTP id QAA09932 for ; Fri, 1 Oct 1999 16:06:27 -0700 (PDT) (envelope-from Doug@gorean.org) Date: Fri, 1 Oct 1999 16:06:26 -0700 (PDT) From: Doug X-Sender: doug@dt011n66.san.rr.com To: freebsd-hackers@freebsd.org Subject: Weird sockname errors with -current and apache Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG No response on -current and I have an update. After moving to -current source via cvs -D (1999//D99.08.28.21.00.00) the servers are infinitely more stable, running continuously for three days, and showing no signs of dying. I get sockname errors once in a great while, and only one at a time. I get the VM error mentioned below once in a great while, but I'm fairly certain I've tracked that down to a problem with the miva processing engine binary itself. I haven't had any of the errant apache children not dying errors, and only one of the calcru errors. I have come up with a theory on this and I'd appreciate if someone could comment on it. We get pre-compiled binaries from the Miva Corp. people that I'm 99.99% sure are built on a 2.2.x or 3.x machine (waiting on confirmation now). So what I'm thinking (based mostly on the sockname error) is that there is a sort of "library creep" happening where small incompatibilities between the version of the library that the binary is expecting and the version it's finding are just a bit out of synch. I am wondering if adding the appropriate compat libraries to these systems would help, and if so how would I specify that this specific binary use those libraries as opposed to the ones in /usr/lib? Any insights on this would be greatly appreciated. Here are some details on the binaries, let know if anything else is needed. Thanks, Doug ldd miva miva: libcrypt.so.2 => /usr/lib/libcrypt.so.2 (0x280d3000) libc.so.3 => /usr/lib/libc.so.3 (0x280e9000) libm.so.2 => /usr/lib/libm.so.2 (0x2816c000) file miva miva: setuid sticky ELF 32-bit LSB executable, Intel 80386, version 1 (FreeBSD), dynamically linked, stripped -- "Stop it, I'm gettin' misty." - Mel Gibson as Porter, "Payback" ---------- Forwarded message ---------- Date: Wed, 29 Sep 1999 12:28:59 -0700 (PDT) From: Doug To: freebsd-current@freebsd.org Subject: Weird sockname errors with -current and apache Greetings, I'm using -current on some web server/CGI processing machines. Yes I know all about using -current on production stuff, but we need the NFS, et al fixes due to the heavy NFS client activity on these systems, and I'm willing to take the good with the bad. I cvsup'ed and built world and kernel on or about 8/26 and these boxes ran fine for about 26 days. On 9/22 (Wednesday) I cvsup'ed and built world and kernel on one machine in order to take advantage of Matt's latest round of NFS, etc. fixes. That box ran well for two days so I updated the rest of them on Friday (9/24) and took off for a happy weekend. Well, you know what happened, one box locked up on saturday, I came in and rebooted it, then the other 4 boxes locked up on sunday. *sigh* The really annoying thing here is that there isn't ONE clear problem that I can point to. Also, when the boxes die they wedge solid. No console, serial or otherwise, and no DDB so I can't find out exactly what they are doing when they die. I have the DDB_UNATTENDED option in the kernel because I have the boxes set up to recover themselves on boot and go back into service (previous to the 26 day uptime panics were common). I'm starting to think I should disable that, however as far as I can see they aren't panic'ing, they are just freezing up; although they are ping'able. We started out this project with Apache 1.3.6, and on Sept. 7 we moved to 1.3.9. These are dual PIII 500 machines with a half gig of ram each. The other annoying thing is that while I was checking the kernel, etc. logs for signs of problems, it hadn't occured to me to check the apache error log. Once I did I noticed that at least some of the symptoms I'm seeing go back as far as I have logs, even before the blessed 26 day uptime period. Here is what I've seen. The first errror I can find in any of the logs I have that seems related to the problem is this from apache's error log: [Fri Aug 20 10:59:34 1999] [error] (22)Invalid argument: getsockname consequently I've noticed that we get this error a LOT, usually coinciding with a period of time where the machine is wedged, after which it sometimes comes back, and sometimes doesn't (i.e., it stays wedged). When this happens it usually repeats about 15-20 times, followed by: Virtual memory exceeded in `new' then a NULL character (^@) in the apache log. Those errors are usually accompanied by a slew of "Premature end of script headers" messages, apparently related to CGI process that these web servers run dying off before it finishes writing out its data. We also have a slew of these errors in the apache logs at various times (doesn't *seem* to be a correlation with the others, but I'm not sure) that look like: [Mon Sep 13 12:51:03 1999] [warn] child process 82600 still did not exit, sending a SIGTERM [Mon Sep 13 12:51:03 1999] [warn] child process 83437 still did not exit, sending a SIGTERM [Mon Sep 13 12:51:03 1999] [warn] child process 84136 still did not exit, sending a SIGTERM [Mon Sep 13 12:51:03 1999] [warn] child process 83698 still did not exit, sending a SIGTERM [Mon Sep 13 12:51:03 1999] [warn] child process 83703 still did not exit, sending a SIGTERM Sometimes these happen at the same time, sometimes they don't. When this one happens we get about 40 of them in a row. In the system logs the only unusual thing I've seen (and I enable a LOT of logging) are these messages, which started over this past weekend. /kernel: calcru: negative time of 4347162 usec for pid 6806 (httpd) Once again, when these come they come in bunches, sometimes with a positive time value like this one, sometimes with a negative one. I'm used to seeing calcru messages related to the kernel misjudging the speed of the processor, but the recently added code that tells you the speed on SMP systems says that I have CPU: Pentium III (498.75-MHz 686-class CPU), which looks right to me. Now, as if the above were not annoying enough, all of these problems could very well be related to the third party CGI processing engine (a program called Miva) which we have tracked down some bugs in before. Of course the machines freezing up is my main concern at this point, but the errors themselves could be coming from miva. Any suggestions on how to debug this problem further would be greatly appreciated. I'm going to start up some boxes today that don't have the DDB_UNATTENDED option enabled to see if they will in fact panic and drop to the debugger. Beyond that, I'm at a bit of a loss here. TIA, Doug To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Oct 1 16:59: 1 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp02.teb1.iconnet.net (smtp02.teb1.iconnet.net [209.3.218.43]) by hub.freebsd.org (Postfix) with ESMTP id E863314A12 for ; Fri, 1 Oct 1999 16:58:58 -0700 (PDT) (envelope-from babkin@bellatlantic.net) Received: from bellatlantic.net (client-151-198-135-40.bellatlantic.net [151.198.135.40]) by smtp02.teb1.iconnet.net (8.9.1/8.9.1) with ESMTP id TAA01906; Fri, 1 Oct 1999 19:58:53 -0400 (EDT) Message-ID: <37F54BD0.9F3CD201@bellatlantic.net> Date: Fri, 01 Oct 1999 20:03:28 -0400 From: Sergey Babkin X-Mailer: Mozilla 4.07 [en] (X11; I; FreeBSD 3.0-980222-SNAP i386) MIME-Version: 1.0 To: Julian Elischer Cc: hackers@FreeBSD.ORG Subject: Re: Huge Binaries.. References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Julian Elischer wrote: > > Has anyone looked at netscape Communicator 4.7 for FreeBSD??? > > I just installed it. > the binary is 13234176 bytes long!! > yes folks, that's 13 MB! > > stripped! > With shared libraries! > > It runs but it's quite easy to make your xserver run out of memory (or > something (Sig 11)) > > One has to wonder what on earth they have in there? > > (My machine has 32 MB so it can run, but it's a bit of a squeez!) I guess you may need a bigger swap space. A while ago yet with Netscape 3.x and 16MB machine I have found that the smallest acceptable swap size was 50MB or it runs out of memory real quick. Now I my machine has 64MB of memory and 150MB of swap but still Netscape 4.07 occasionally runs out of space. I think it has a big memory leak in the forms code (sometimes it consumes tens of kilobytes per each letter typed) and also big problems with Java support. 4.61 seemed to support Java OK (I was able to run a few games in Java!) but crashed every time I tried to send an e-mail, so I returned back to 4.07. -SB To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Oct 1 17:27:33 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp02.teb1.iconnet.net (smtp02.teb1.iconnet.net [209.3.218.43]) by hub.freebsd.org (Postfix) with ESMTP id 4C4AD14C25 for ; Fri, 1 Oct 1999 17:27:30 -0700 (PDT) (envelope-from babkin@bellatlantic.net) Received: from bellatlantic.net (client-151-198-135-40.bellatlantic.net [151.198.135.40]) by smtp02.teb1.iconnet.net (8.9.1/8.9.1) with ESMTP id UAA03302; Fri, 1 Oct 1999 20:26:05 -0400 (EDT) Message-ID: <37F5522F.A12B8582@bellatlantic.net> Date: Fri, 01 Oct 1999 20:30:39 -0400 From: Sergey Babkin X-Mailer: Mozilla 4.07 [en] (X11; I; FreeBSD 3.0-980222-SNAP i386) MIME-Version: 1.0 To: Narvi Cc: jin@george.lbl.gov, hackers@FreeBSD.ORG Subject: Re: SCSI disk naming problem References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Narvi wrote: > > See LINT on details of how to wire down scsi devices... > > Your proposal doesn't take adding a second scsi card into account. UnixWare has a kind od solution for this: when they create the VTOC table (an analog of the BSD disk label) on the disk they have a field in it that contains some piece of random-generated junk that works as a disk ID. The association of the disk number and this ID is also written into resmanager. Resmanager is a thing like sysctl but much more braindamaged and difficult to use, and its contents is saved to disk when the system is stopped. So when the system boots next time it reads in the resmanager database and tries to associate the disks with known ID to the same number which was assigned to them last time. The problem of this method is getting rid of the stale disk ID left in the resmanager, so some way should be provided to do that (and better it be better than in UnixWare). I guess this thing would be rather easy to implement in FreeBSD: instead of the on-disk resmanager database we can use the already existing mechanism of the 3rd stage loader configuration files. And the changes to the SCSI disk driver should be not too complex too. Such a mechanism has also the second (and I suppose the main) use in UnixWare: it is absolutely neccessary for the MultiPath I/O. That is, a disk may be connected to more than one SCSI card and if one of the access paths crashes another one can still be used. There are two problems: first, how do we know that this is the same disk accessible by two paths ? second, if one of the path crashes what are we going to do on the next reboot not to let the disk get re-assigned to another name ? Both of them are resolved by these disk IDs in the VTOCs. -SB > On Fri, 1 Oct 1999 jin@george.lbl.gov wrote: > > > Current FreeBSD SCSi disk naming mechanism is problem for using more than > > one disks in the chain during the disk failure. > > > > The problem is that the name is not fixed with is SCSI ID. e.g., > > if one disk is presented in the chain, regardless its SCSI ID, it is > > always named "da0"; > > > > if two disks are installed, the one with lower ID is named da0 and the > > other will be named as da1. When the lower ID one is crashed, then the > > other disk will be named as da0 (from da1) after reboot, and it is not > > mountable due to the name changing. > > > > If a system has a UW SCSI controller with 15 disks in the chain, > > when the first disk (ID = 0) crashed, all rest 14 disks will be > > useless until either fstab modified or another disk is added with > > SCSI ID = 0. > > > > Why not we use a fixed name corresponding the SCSI ID. That is, > > disk with ID 0 will be always named as da0, and disk with ID 1 > > will be always named da1, etc.? > > > > Is there problem with fixed disk naming mechanism? > > > > -Jin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Oct 1 17:38: 3 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp02.teb1.iconnet.net (smtp02.teb1.iconnet.net [209.3.218.43]) by hub.freebsd.org (Postfix) with ESMTP id 58E6114C8F for ; Fri, 1 Oct 1999 17:38:00 -0700 (PDT) (envelope-from babkin@bellatlantic.net) Received: from bellatlantic.net (client-151-198-135-40.bellatlantic.net [151.198.135.40]) by smtp02.teb1.iconnet.net (8.9.1/8.9.1) with ESMTP id UAA03830; Fri, 1 Oct 1999 20:37:35 -0400 (EDT) Message-ID: <37F554E1.486FD7C8@bellatlantic.net> Date: Fri, 01 Oct 1999 20:42:09 -0400 From: Sergey Babkin X-Mailer: Mozilla 4.07 [en] (X11; I; FreeBSD 3.0-980222-SNAP i386) MIME-Version: 1.0 To: Mike Smith Cc: "Ronald G. Minnich" , hackers@FreeBSD.ORG Subject: Re: return to real mode References: <199910010743.AAA02418@dingo.cdrom.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mike Smith wrote: > > > anybody got some reliable, tested, known-good code for getting back to > > real mode? I'm to the point where I have a working GDT, and paging is > > turned off, but the last step -- turning off protection enable -- is not > > working for me. > > You want to be more explicit about why you want to get back? There are > possibly alternatives, or other collateral damage issues that might be > worth commenting on. I have an almost-working code written yet in the 2.0.5 days. Then there was a guy Wee Teck who asked a similar question and I sent my code to him. He has found the final bug and got it working. Maybe he is still on the list and can provide some information. I'm going to send my code and his fix off the list. -SB To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Oct 1 23:48:35 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mentisworks.com (ro03-24-29-246-167.ce.mediaone.net [24.29.246.167]) by hub.freebsd.org (Postfix) with ESMTP id 6AB7815166 for ; Fri, 1 Oct 1999 23:45:39 -0700 (PDT) (envelope-from nathank@mentisworks.com) Received: from [192.168.245.111] (HELO mentisworks.com) by mentisworks.com (CommuniGate Pro SMTP 3.1) with ESMTP id 50510 for freebsd-hackers@freebsd.org; Sat, 02 Oct 1999 01:47:26 -0500 Message-ID: <37F5AA7D.5E9FF2CE@mentisworks.com> Date: Sat, 02 Oct 1999 01:47:25 -0500 From: Nathan Kinsman X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 3.3-STABLE i386) X-Accept-Language: en,de MIME-Version: 1.0 To: freebsd-hackers@freebsd.org Subject: Re: Huge Binaries.. References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Julian Elischer wrote: > > Has anyone looked at netscape Communicator 4.7 for FreeBSD??? > > I just installed it. > the binary is 13234176 bytes long!! > yes folks, that's 13 MB! Not sure if anyone has tried this, but I run the BSDI version of 4.7. I've been running BSDI versions of Netscape for some time now without problems. The binary size for BSDI version of 4.7 is only 10711040 bytes long, which is significantly smaller then Linux or FreeBSD 2.2 versions. Also comparing Linux 4.7 to BSDI 4.7 in top, Linux reads 20404K displaying start copyright notice, BSDI version uses 14788K. Not sure what the additional memory requirements of use BSDI emulation are, but I can notice the speed difference between Linux and BSDI versions due to less paging. - Nathan Kinsman To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Oct 2 3:16:19 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from haldjas.folklore.ee (Haldjas.folklore.ee [193.40.6.121]) by hub.freebsd.org (Postfix) with ESMTP id 567EB14A23 for ; Sat, 2 Oct 1999 03:16:13 -0700 (PDT) (envelope-from narvi@haldjas.folklore.ee) Received: from localhost (narvi@localhost) by haldjas.folklore.ee (8.9.3/8.9.3) with SMTP id NAA31408; Sat, 2 Oct 1999 13:15:53 +0300 (EEST) (envelope-from narvi@haldjas.folklore.ee) Date: Sat, 2 Oct 1999 13:15:53 +0300 (EEST) From: Narvi To: jin@george.lbl.gov Cc: bmah@CA.Sandia.GOV, hackers@FreeBSD.ORG Subject: Re: SCSI disk naming problem In-Reply-To: <199910011833.LAA20871@george.lbl.gov> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 1 Oct 1999 jin@george.lbl.gov wrote: > bmah@CA.Sandia.GOV wrote: [snip] > > > > That's an interesting argument on the part of a few people. The > > commercial UNIX I first adminned had wired down, short names for disks > > (rz0, rz1, rz2, ... ). This was very nice. > > This one does not resolve the controller problem either as > narvi@haldjas.folklore.ee said. > > So, I guess dac0t0, dac0t1, ... dac3t4, will be good enough if we want > to be short, but anything shorter than this will be meaningless. > As long as you don't move a hard disk from one bus on the controller to the other 8-) > > -Jin > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Oct 2 5:17: 5 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mailb.telia.com (mailb.telia.com [194.22.194.6]) by hub.freebsd.org (Postfix) with ESMTP id A3BCF151D5; Sat, 2 Oct 1999 05:16:25 -0700 (PDT) (envelope-from stefan@syprix.se) Received: from d1o49.telia.com (root@d1o49.telia.com [195.198.194.241]) by mailb.telia.com (8.9.3/8.9.3) with ESMTP id OAA18790; Sat, 2 Oct 1999 14:16:24 +0200 (CEST) Received: from syprix.se (t1o49p40.telia.com [195.198.194.40]) by d1o49.telia.com (8.8.8/8.8.5) with ESMTP id OAA11162; Sat, 2 Oct 1999 14:16:22 +0200 (CEST) Message-ID: <37F5FB23.564BBB28@syprix.se> Date: Sat, 02 Oct 1999 14:31:31 +0200 From: Stefan Lindgren Reply-To: stefan@syprix.se Organization: Syprix AB X-Mailer: Mozilla 4.6 [en] (Win98; I) X-Accept-Language: en MIME-Version: 1.0 To: Soren Schmidt Cc: freebsd-hackers@freebsd.org, freebsd-hardware@freebsd.org Subject: Re: Tyan Dual PPRO Bios 5.1 problem... References: <199910012002.WAA64288@freebsd.dk> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Well, this UDMA story has finally come to an end. I got this wierd(!) ide to test my developer version of BeOS 4.5 on the machine. I have had no problem with BeOS on the machine before this UDMA disk thing. Did it work? No. The BeOS couldn't even find the CD-ROM when I had the UDMA crap whitin it! It seems like something is really buggy with that disk(Seagate Medalist 6531A). Anyway, I have now replaced it with the god old EIDE. No problemo. Runs good... Thanks for the help /stefan Soren Schmidt wrote: > > It seems Stefan Lindgren wrote: > > Thanks for the help Soren, > > > > The disk is a Seagate Medalist 6.2 GB UDMA > > But now I have tested all PIO modes(0 - 4 and auto) and disabled udma. > > It still doesn't work. > > I get different results when I change PIO. Once I got some message like: > > Page fault: Couldn't init disk...(something) > > > > Any clue? > > Not really, have you tried with another disk ?? > > As said I had an older Maxtor that wouldn't work, but I've never had > a problem since... > > -Sxren > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hardware" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Oct 2 7:15:42 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (Postfix) with ESMTP id D7E621528D; Sat, 2 Oct 1999 07:14:17 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.2) with ESMTP id QAA18240; Sat, 2 Oct 1999 16:14:11 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) Date: Sat, 02 Oct 1999 16:14:10 +0200 Message-ID: <18238.938873650.1@critter.freebsd.dk> From: Poul-Henning Kamp Subject: A bike shed (any colour will do) on greener grass... MIME-Version: 1.0 Content-Type: multipart/digest; boundary="----- =_aaaaaaaaaa" Content-Description: Blind Carbon Copy Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG ------- =_aaaaaaaaaa Content-Type: message/rfc822 Content-Description: Original Message Subject: A bike shed (any colour will do) on greener grass... From: Poul-Henning Kamp Date: Sat, 02 Oct 1999 16:14:10 +0200 Message-ID: <18238.938873650@critter.freebsd.dk> Sender: phk@critter.freebsd.dk Bcc: Blind Distribution List: ; MIME-Version: 1.0 [bcc'ed to committers, hackers] My last pamphlet was sufficiently well received that I was not scared away from sending another one, and today I have the time and inclination to do so. I've had a little trouble with deciding on the right distribution of this kind of stuff, this time it is bcc'ed to committers and hackers, that is probably the best I can do. I'm not subscribed to hackers myself but more on that later. The thing which have triggered me this time is the "sleep(1) should do fractional seconds" thread, which have pestered our lives for many days now, it's probably already a couple of weeks, I can't even be bothered to check. To those of you who have missed this particular thread: Congratulations. It was a proposal to make sleep(1) DTRT if given a non-integer argument that set this particular grass-fire off. I'm not going to say anymore about it than that, because it is a much smaller item than one would expect from the length of the thread, and it has already received far more attention than some of the *problems* we have around here. The sleep(1) saga is the most blatant example of a bike shed discussion we have had ever in FreeBSD. The proposal was well thought out, we would gain compatibility with OpenBSD and NetBSD, and still be fully compatible with any code anyone ever wrote. Yet so many objections, proposals and changes were raised and launched that one would think the change would have plugged all the holes in swiss cheese or changed the taste of Coca Cola or something similar serious. "What is it about this bike shed ?" Some of you have asked me. It's a long story, or rather it's an old story, but it is quite short actually. C. Northcote Parkinson wrote a book in the early 1960'ies, called "Parkinson's Law", which contains a lot of insight into the dynamics of management. You can find it on Amazon, and maybe also in your dads book-shelf, it is well worth its price and the time to read it either way, if you like Dilbert, you'll like Parkinson. Somebody recently told me that he had read it and found that only about 50% of it applied these days. That is pretty darn good I would say, many of the modern management books have hit-rates a lot lower than that, and this one is 35+ years old. In the specific example involving the bike shed, the other vital component is an atomic power-plant, I guess that illustrates the age of the book. Parkinson shows how you can go in to the board of directors and get approval for building a multi-million or even billion dollar atomic power plant, but if you want to build a bike shed you will be tangled up in endless discussions. Parkinson explains that this is because an atomic plant is so vast, so expensive and so complicated that people cannot grasp it, and rather than try, they fall back on the assumption that somebody else checked all the details before it got this far. Richard P. Feynmann gives a couple of interesting, and very much to the point, examples relating to Los Alamos in his books. A bike shed on the other hand. Anyone can build one of those over a weekend, and still have time to watch the game on TV. So no matter how well prepared, no matter how reasonable you are with your proposal, somebody will seize the chance to show that he is doing his job, that he is paying attention, that he is *here*. In Denmark we call it "setting your fingerprint". It is about personal pride and prestige, it is about being able to point somewhere and say "There! *I* did that." It is a strong trait in politicians, but present in most people given the chance. Just think about footsteps in wet cement. I bow my head in respect to the original proposer because he stuck to his guns through this carpet blanking from the peanut gallery, and the change is in our tree today. I would have turned my back and walked away after less than a handful of messages in that thread. And that brings me, as I promised earlier, to why I am not subscribed to -hackers: I un-subscribed from -hackers several years ago, because I could not keep up with the email load. Since then I have dropped off several other lists as well for the very same reason. And I still get a lot of email. A lot of it gets routed to /dev/null by filters: People like Brett Glass will never make it onto my screen, commits to documents in languages I don't understand likewise, commits to ports as such. All these things and more go the winter way without me ever even knowing about it. But despite these sharp teeth under my mailbox I still get too much email. This is where the greener grass comes into the picture: I wish we could reduce the amount of noise in our lists and I wish we could let people build a bike shed every so often, and I don't really care what colour they paint it. The first of these wishes is about being civil, sensitive and intelligent in our use of email. If I could concisely and precisely define a set of criteria for when one should and when one should not reply to an email so that everybody would agree and abide by it, I would be a happy man, but I am too wise to even attempt that. But let me suggest a few pop-up windows I would like to see mail-programs implement whenever people send or reply to email to the lists they want me to subscribe to: +------------------------------------------------------------+ | Your email is about to be sent to several hundred thousand | | people, who will have to spend at least 10 seconds reading | | it before they can decide if it is interesting. At least | | two man-weeks will be spent reading your email. Many of | | the recipients will have to pay to download your email. | | | | Are you absolutely sure that your email is of sufficient | | importance to bother all these people ? | | | | [YES] [REVISE] [CANCEL] | +------------------------------------------------------------+ +------------------------------------------------------------+ | Warning: You have not read all emails in this thread yet. | | Somebody else may already have said what you are about to | | say in your reply. Please read the entire thread before | | replying to any email in it. | | | | [CANCEL] | +------------------------------------------------------------+ +------------------------------------------------------------+ | Warning: Your mail program have not even shown you the | | entire message yet. Logically it follows that you cannot | | possibly have read it all and understood it. | | | | It is not polite to reply to an email until you have | | read it all and thought about it. | | | | A cool off timer for this thread will prevent you from | | replying to any email in this thread for the next one hour | | | | [Cancel] | +------------------------------------------------------------+ +------------------------------------------------------------+ | You composed this email at a rate of more than N.NN cps | | It is generally not possible to think and type at a rate | | faster than A.AA cps, and therefore you reply is likely to | | incoherent, badly thought out and/or emotional. | | | | A cool off timer will prevent you from sending any email | | for the next one hour. | | | | [Cancel] | +------------------------------------------------------------+ The second part of my wish is more emotional. Obviously, the capacities we had manning the unfriendly fire in the sleep(1) thread, despite their many years with the project, never cared enough to do this tiny deed, so why are they suddenly so enflamed by somebody else so much their junior doing it ? I wish I knew. I do know that reasoning will have no power to stop such "reactionaire conservatism". It may be that these people are frustrated about their own lack of tangible contribution lately or it may be a bad case of "we're old and grumpy, WE know how youth should behave". Either way it is very unproductive for the project, but I have no suggestions for how to stop it. The best I can suggest is to refrain from fuelling the monsters that lurk in the mailing lists: Ignore them, don't answer them, forget they're there. I hope we can get a stronger and broader base of contributors in FreeBSD, and I hope we together can prevent the grumpy old men and the Brett Glasses of the world from chewing them up, spitting them out and scaring them away before they ever get a leg to the ground. For the people who have been lurking out there, scared away from participating by the gargoyles: I can only apologise and encourage you to try anyway, this is not the way I want the environment in the project to be. Poul-Henning ------- =_aaaaaaaaaa-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Oct 2 8: 4:17 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from haldjas.folklore.ee (Haldjas.folklore.ee [193.40.6.121]) by hub.freebsd.org (Postfix) with ESMTP id C5F4F14D9F for ; Sat, 2 Oct 1999 08:03:26 -0700 (PDT) (envelope-from narvi@haldjas.folklore.ee) Received: from localhost (narvi@localhost) by haldjas.folklore.ee (8.9.3/8.9.3) with SMTP id SAA35196; Sat, 2 Oct 1999 18:03:14 +0300 (EEST) (envelope-from narvi@haldjas.folklore.ee) Date: Sat, 2 Oct 1999 18:03:14 +0300 (EEST) From: Narvi To: "Bruce A. Mah" Cc: jin@george.lbl.gov, bmah@california.sandia.gov, hackers@FreeBSD.ORG Subject: Re: SCSI disk naming problem In-Reply-To: <199910012033.NAA81193@nimitz.ca.sandia.gov> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 1 Oct 1999, Bruce A. Mah wrote: > If memory serves me right, jin@george.lbl.gov wrote: > > > > This one does not resolve the controller problem either as > > narvi@haldjas.folklore.ee said. > > > > So, I guess dac0t0, dac0t1, ... dac3t4, will be good enough if we want > > to be short, but anything shorter than this will be meaningless. > > Well...I personally prefer the short names. On systems with multiple > controllers, the commercial UNIX I used (Ultrix) just continued its > numbering with rz0, rz1, rz2, ..., rz6, rz7, rz8, ... FreeBSD lets you > do exactly the same thing. > > Having long device names is confusing to users who only have one disk > controller (and I'd bet this is the vast majority). It took me a long The vast majority has just one disk. Given the fast growth in disk sizes, that majority will not decrease. > time to grok the syntax of Solaris device names and I still get confused > about this. Commercial or free doesn't have anything to do with this > issue...this scheme would force users to remember and type extra > characters that many of them don't need. (/dev/da0s1a is long enough, > but /dev/dac0t0d0s1a is a little ridiculous for someone that has only > one controller and one drive.) > If you want to *SOLVE* the problem, then make the disk wiring happen before the kernel is booted. After all, we have a real cute boot loader that can definately load the /boot/disk.wire file 8-) The problem after all is *NOT* one of names but that disks not change names unless the administrator wishes so. It doesn't matter the least how we call them. [snip] > Cheers, > > Bruce. > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Oct 2 8:59:50 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.uni-bielefeld.de (mail.uni-bielefeld.de [129.70.4.90]) by hub.freebsd.org (Postfix) with ESMTP id 4B20D14D6E for ; Sat, 2 Oct 1999 08:59:41 -0700 (PDT) (envelope-from bfischer@Techfak.uni-bielefeld.de) Received: from frolic.no-support.loc (ppp36-68.hrz.uni-bielefeld.de) by mail.uni-bielefeld.de (Sun Internet Mail Server sims.3.5.1999.05.24.18.28.p7) with ESMTP id <0FIZ00MKCGFEPL@mail.uni-bielefeld.de> for hackers@FreeBSD.ORG; Sat, 2 Oct 1999 17:59:39 +0200 (MET DST) Received: (from bjoern@localhost) by frolic.no-support.loc (8.9.3/8.9.3) id MAA00998; Sat, 02 Oct 1999 12:15:09 +0200 (CEST envelope-from bjoern) Date: Sat, 02 Oct 1999 12:15:09 +0200 From: Bjoern Fischer Subject: Re: Huge Binaries.. In-reply-to: <19991001220931.A71530@keltia.freenix.fr> To: Ollivier Robert Cc: hackers@FreeBSD.ORG Message-id: <19991002121509.A355@frolic.no-support.loc> MIME-version: 1.0 X-Mailer: Mutt 1.0pre3i Content-type: text/plain; charset=iso-8859-1 Content-transfer-encoding: quoted-printable References: <19991001220931.A71530@keltia.freenix.fr> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Oct 01, 1999 at 10:09:31PM +0200, Ollivier Robert wrote: [...] > Yes but with the navigator, you can't even mail a link or a page... With Netscape's mail and news sdk you can use your favorite mail and news clients transparently from navigator (like mailto:, news:, or mail page, etc.). The sdk consists of some C headers, docs and a small example. You simply build a small shared library that is loaded by navigator. The shared library uses hooks in navigator and you may perform any action you like (start /usr/bin/mail, mutt, emacs, ...). Bj=F6rn --=20 -----BEGIN GEEK CODE BLOCK----- GCS d--(+) s++: a- C+++(-) UB++++OSI++++$ P+++(-) L+++(--) !E W- N+ o>+ K- !w !O !M !V PS++ PE- PGP++ t+++ !5 X++ tv- b+++ D++ G e+ h-- y+=20 ------END GEEK CODE BLOCK------ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Oct 2 9:39:50 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from florence.pavilion.net (florence.pavilion.net [194.242.128.25]) by hub.freebsd.org (Postfix) with ESMTP id 3FF921544B for ; Sat, 2 Oct 1999 09:37:53 -0700 (PDT) (envelope-from joe@florence.pavilion.net) Received: (from joe@localhost) by florence.pavilion.net (8.9.3/8.8.8) id RAA71075; Sat, 2 Oct 1999 17:37:25 +0100 (BST) (envelope-from joe) Date: Sat, 2 Oct 1999 17:37:25 +0100 From: Josef Karthauser To: Bjoern Fischer Cc: Ollivier Robert , hackers@FreeBSD.ORG Subject: Re: Huge Binaries.. Message-ID: <19991002173725.T86792@florence.pavilion.net> References: <19991001220931.A71530@keltia.freenix.fr> <19991002121509.A355@frolic.no-support.loc> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre2i In-Reply-To: <19991002121509.A355@frolic.no-support.loc> X-NCC-RegID: uk.pavilion Organisation: Pavilion Internet plc, 24 The Old Steine, Brighton, BN1 1EL, England Phone: +44-845-333-5000 Fax: +44-845-333-5001 Mobile: +44-403-596893 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, Oct 02, 1999 at 12:15:09PM +0200, Bjoern Fischer wrote: > On Fri, Oct 01, 1999 at 10:09:31PM +0200, Ollivier Robert wrote: > [...] > > Yes but with the navigator, you can't even mail a link or a page... > > With Netscape's mail and news sdk you can use your favorite > mail and news clients transparently from navigator (like > mailto:, news:, or mail page, etc.). > > The sdk consists of some C headers, docs and a small example. > You simply build a small shared library that is loaded by > navigator. The shared library uses hooks in navigator and > you may perform any action you like (start /usr/bin/mail, > mutt, emacs, ...). Do you know anything about their Enterprise Calendar server support that they've introduced in 4.7? Is this their own protocol, or is it something fairly standard under the bonnet? Joe -- Josef Karthauser FreeBSD: How many times have you booted today? Technical Manager Viagra for your server (http://www.uk.freebsd.org) Pavilion Internet plc. [joe@pavilion.net, joe@uk.freebsd.org, joe@tao.org.uk] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Oct 2 11:28: 1 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from frmug.org (frmug-gw.frmug.org [193.56.58.252]) by hub.freebsd.org (Postfix) with ESMTP id EC1971522A for ; Sat, 2 Oct 1999 11:27:33 -0700 (PDT) (envelope-from roberto@keltia.freenix.fr) Received: (from uucp@localhost) by frmug.org (8.9.3/frmug-2.5/nospam) with UUCP id UAA19784 for hackers@FreeBSD.ORG; Sat, 2 Oct 1999 20:27:29 +0200 (CEST) (envelope-from roberto@keltia.freenix.fr) Received: by keltia.freenix.fr (Postfix, from userid 101) id 81B1B87AB; Sat, 2 Oct 1999 19:15:12 +0200 (CEST) Date: Sat, 2 Oct 1999 19:15:12 +0200 From: Ollivier Robert To: hackers@FreeBSD.ORG Subject: Re: Huge Binaries.. Message-ID: <19991002191512.A78716@keltia.freenix.fr> Mail-Followup-To: hackers@FreeBSD.ORG References: <19991001220931.A71530@keltia.freenix.fr> <19991002121509.A355@frolic.no-support.loc> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii User-Agent: Mutt/1.0pre2i In-Reply-To: <19991002121509.A355@frolic.no-support.loc> X-Operating-System: FreeBSD 4.0-CURRENT/ELF AMD-K6/200 & 2x PPro/200 SMP Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG According to Bjoern Fischer: > The sdk consists of some C headers, docs and a small example. > You simply build a small shared library that is loaded by > navigator. The shared library uses hooks in navigator and > you may perform any action you like (start /usr/bin/mail, > mutt, emacs, ...). Wow! I didn't know that. I'll have a look. Anyone has already done the work of running Mutt from Netscape ? :-) -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 4.0-CURRENT #74: Thu Sep 9 00:20:51 CEST 1999 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Oct 2 12: 6:43 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from dorifer.heim3.tu-clausthal.de (dorifer.heim3.tu-clausthal.de [139.174.243.252]) by hub.freebsd.org (Postfix) with ESMTP id AECDA153EC for ; Sat, 2 Oct 1999 12:04:59 -0700 (PDT) (envelope-from olli@dorifer.heim3.tu-clausthal.de) Received: (from olli@localhost) by dorifer.heim3.tu-clausthal.de (8.8.8/8.8.8) id VAA16526 for freebsd-hackers@FreeBSD.ORG; Sat, 2 Oct 1999 21:04:59 +0200 (CEST) (envelope-from olli) Date: Sat, 2 Oct 1999 21:04:59 +0200 (CEST) From: Oliver Fromme Message-Id: <199910021904.VAA16526@dorifer.heim3.tu-clausthal.de> To: freebsd-hackers@FreeBSD.ORG Subject: Re: 2.88Mb floppies Organization: Administration Heim 3 Reply-To: freebsd-hackers@FreeBSD.ORG MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Newsreader: TIN [version 1.2 RZTUC(3) PL2] Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Wilko Bulte wrote in list.freebsd-hackers: > As Oliver Fromme wrote ... > > I once programmed low-level FDC stuff under DOS, so I'm a bit > > familiar with this... The difference between 1.44 and 2.88 Mb > > floppies is that the latter use 36 sectors per track and twice > > the data rate (1 MBit/s). So the entry should look like this: > > > > {36, 2, 0xff, 0x1b, 80, 5760, 1, FDC_125KBPS, 2, 0x6c, 1} > > > > Actually, there should be a #define FDC_1MBPS FDC_125KBPS > > Eh, I guess you mean: > > {36, 2, 0xff, 0x1b, 80, 5760, 1, FDC_1MBPS, 2, 0x6c, 1} ? No, FDC_1MBPS is not defined (that's why I said that it _should_ be defined). Actually, FD controllers use a 2bit flag to indicate the transfer speed, and traditional controllers interpreted those four values as 125, 250, 300 and 500 kbps. Newer controllers dumped the 125 kbps support and interpret the same bits as 1000 kbps. So using FDC_125KBPS is OK. Beware, I have not actually tried this with FreeBSD, and there might be bugs that prevent using 2.88 Mb floppies. Regards Oliver -- Oliver Fromme, Leibnizstr. 18/61, 38678 Clausthal, Germany (Info: finger userinfo:olli@dorifer.heim3.tu-clausthal.de) "In jedem Stück Kohle wartet ein Diamant auf seine Geburt" (Terry Pratchett) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Oct 2 13:15:54 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.du.gtn.com (mail.du.gtn.com [194.77.9.57]) by hub.freebsd.org (Postfix) with ESMTP id 135B015386 for ; Sat, 2 Oct 1999 13:15:34 -0700 (PDT) (envelope-from ticso@cicely8.cicely.de) Received: from mail.cicely.de (cicely.de [194.231.9.142]) by mail.du.gtn.com (8.9.3/8.9.3) with ESMTP id WAA14134; Sat, 2 Oct 1999 22:07:32 +0200 (MET DST) Received: from cicely8.cicely.de (cicely8.cicely.de [10.1.2.10]) by mail.cicely.de (8.9.0/8.9.0) with ESMTP id WAA51701; Sat, 2 Oct 1999 22:11:56 +0200 (CEST) Received: (from ticso@localhost) by cicely8.cicely.de (8.9.3/8.9.2) id WAA92207; Sat, 2 Oct 1999 22:11:52 +0200 (CEST) (envelope-from ticso) Date: Sat, 2 Oct 1999 22:11:52 +0200 From: Bernd Walter To: Narvi Cc: jin@george.lbl.gov, bmah@CA.Sandia.GOV, hackers@FreeBSD.ORG Subject: Re: SCSI disk naming problem Message-ID: <19991002221151.B92132@cicely8.cicely.de> References: <199910011833.LAA20871@george.lbl.gov> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.3i In-Reply-To: ; from Narvi on Sat, Oct 02, 1999 at 01:15:53PM +0300 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, Oct 02, 1999 at 01:15:53PM +0300, Narvi wrote: > > On Fri, 1 Oct 1999 jin@george.lbl.gov wrote: > > > bmah@CA.Sandia.GOV wrote: > > [snip] > > > > > > > That's an interesting argument on the part of a few people. The > > > commercial UNIX I first adminned had wired down, short names for disks > > > (rz0, rz1, rz2, ... ). This was very nice. > > > > This one does not resolve the controller problem either as > > narvi@haldjas.folklore.ee said. > > > > So, I guess dac0t0, dac0t1, ... dac3t4, will be good enough if we want > > to be short, but anything shorter than this will be meaningless. > > > > As long as you don't move a hard disk from one bus on the controller to > the other 8-) Yes something like dac0t0... is realy nice - but AFAIK it's not general enough for fibre channel. The main point is that I only see this problem with removeable disks and other kind of SCSI-devices, which I usually wire down. Most of my fixed disks are running with vinum. vinum is able to handle if a drive has changed it's ID and/or name. It's an important thing to have something like this if you want to be able to hotplug a drive (or power up later). Sometimes it's getting another name than it would have after reboot! -- B.Walter COSMO-Project http://www.cosmo-project.de ticso@cicely.de Usergroup info@cosmo-project.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Oct 2 15:11:15 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.imp.ch (mail.imp.ch [157.161.1.2]) by hub.freebsd.org (Postfix) with ESMTP id 894241542C; Sat, 2 Oct 1999 15:10:40 -0700 (PDT) (envelope-from mb@imp.ch) Received: from mephisto.imp.ch (mb@mephisto.imp.ch [157.161.1.22]) by mail.imp.ch (8.9.3/8.9.3) with ESMTP id AAA18822; Sun, 3 Oct 1999 00:10:36 +0200 (MET DST) Received: from localhost (mb@localhost) by mephisto.imp.ch (8.9.3/8.9.3) with ESMTP id AAA05671; Sun, 3 Oct 1999 00:10:34 +0200 (MES) Date: Sun, 3 Oct 1999 00:10:34 +0200 From: Martin Blapp To: freebsd-hackers@freebsd.org Cc: cvs-committers@freebsd.org Subject: umount(8) or unmount(2) ? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, Since about 5 weeks I'm working on sanity checks and bug fixes for umount(8), mount(8) and mount_xxx(8). Poul Henning told me to mail to cvs-committers too, cause many clued people read it. You'll find my patch and the readme for it on : http://www.attic.ch/patches/MOUNTPATCH-CURRENT-02101999-01 http://www.attic.ch/patches/MOUNTPATCH-README My problem is, that all fixes do their work. But it is not clear, if some work should be in kernel- or user-land. Some people just like to have umount(8) as a wrapper to unmount(2) and don't like umount(8) to do sanity checks. This is the case for this part of umount(8) I've replaced: - origname = name; - if (stat(name, &sb) < 0) { - mntpt = rname; - if ((getmntname(rname, MNTFROM, &type) == NULL) && - ((mntpt = getmntname(name, MNTON, &type)) == NULL)) { - warnx("%s: not currently mounted", name); - return (1); - } I've replaced stat() and realpath() on the mountpoint with () realpath on the basedir of the mointpoint and added some sanity checks. Most of my mount-order checks I added in umount(8) relay on a resolved mountpoint. I've implemented this as an idea from phk and it works very well. If we unmount a hanged nfs-mount - it hangs no in kernel (if busy), not in userland. This is a little step forward. Some side-effects of this part of my patch are, that some other PR's are fixed too : o [1999/02/03] bin/9893 NFS umount of regular file impossible s [1995/11/27] bin/841 stale nfs mounts cannot be umounted If we find the mntonname or mntfromname in the mounttable, we just go ahead and unmount it. No stat() or anything else is needed. Please tell me what you're thinking about these ideas and the work I've done and show me why I am wrong. Thank you very much ! Martin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Oct 2 16: 8: 1 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from uni4nn.gn.iaf.nl (osmium.gn.iaf.nl [193.67.144.12]) by hub.freebsd.org (Postfix) with ESMTP id 2E6CC14C0A for ; Sat, 2 Oct 1999 16:07:58 -0700 (PDT) (envelope-from wilko@yedi.iaf.nl) Received: from yedi.iaf.nl (uucp@localhost) by uni4nn.gn.iaf.nl (8.9.2/8.9.2) with UUCP id AAA29193 for freebsd-hackers@FreeBSD.ORG; Sun, 3 Oct 1999 00:48:49 +0200 (MET DST) Received: (from wilko@localhost) by yedi.iaf.nl (8.9.3/8.9.3) id AAA56167; Sun, 3 Oct 1999 00:33:58 +0200 (CEST) (envelope-from wilko) From: Wilko Bulte Message-Id: <199910022233.AAA56167@yedi.iaf.nl> Subject: Re: 2.88Mb floppies In-Reply-To: <199910021904.VAA16526@dorifer.heim3.tu-clausthal.de> from Oliver Fromme at "Oct 2, 1999 9: 4:59 pm" To: freebsd-hackers@freebsd.org Date: Sun, 3 Oct 1999 00:33:57 +0200 (CEST) Cc: freebsd-hackers@freebsd.org X-Organisation: Private FreeBSD site - Arnhem, The Netherlands X-pgp-info: PGP public key at 'finger wilko@freefall.freebsd.org' X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG As Oliver Fromme wrote ... > Wilko Bulte wrote in list.freebsd-hackers: > > As Oliver Fromme wrote ... > > > I once programmed low-level FDC stuff under DOS, so I'm a bit > > > familiar with this... The difference between 1.44 and 2.88 Mb > > > floppies is that the latter use 36 sectors per track and twice > > > the data rate (1 MBit/s). So the entry should look like this: > > > > > > {36, 2, 0xff, 0x1b, 80, 5760, 1, FDC_125KBPS, 2, 0x6c, 1} > > > > > > Actually, there should be a #define FDC_1MBPS FDC_125KBPS > > > > Eh, I guess you mean: > > > > {36, 2, 0xff, 0x1b, 80, 5760, 1, FDC_1MBPS, 2, 0x6c, 1} ? > > No, FDC_1MBPS is not defined (that's why I said that it > _should_ be defined). > Actually, FD controllers use a 2bit flag to indicate the > transfer speed, and traditional controllers interpreted those > four values as 125, 250, 300 and 500 kbps. Newer controllers > dumped the 125 kbps support and interpret the same bits as > 1000 kbps. So using FDC_125KBPS is OK. Ah.. talking about confusing. It's been a long time since I had to design a FDC on a SCSI adapter card. Project got scrapped too :-( > Beware, I have not actually tried this with FreeBSD, and there > might be bugs that prevent using 2.88 Mb floppies. I hope to give it a quick try next week. -- | / o / / _ Arnhem, The Netherlands - Powered by FreeBSD - |/|/ / / /( (_) Bulte WWW : http://www.tcja.nl http://www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Oct 2 16:57: 5 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from tardis.patho.gen.nz (tardis.patho.gen.nz [203.97.2.226]) by hub.freebsd.org (Postfix) with ESMTP id 53448154E4 for ; Sat, 2 Oct 1999 16:56:29 -0700 (PDT) (envelope-from jabley@tardis.patho.gen.nz) Received: (from jabley@localhost) by tardis.patho.gen.nz (8.9.3/8.9.3) id MAA23109 for freebsd-hackers@freebsd.org; Sun, 3 Oct 1999 12:56:28 +1300 (NZDT) Date: Sun, 3 Oct 1999 12:56:27 +1300 From: Joe Abley To: freebsd-hackers@freebsd.org Subject: Cosmetic changes to whois(1) Message-ID: <19991003125627.A24147@patho.gen.nz> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.5i X-Files: the Truth is Out There Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've just made two very minor (cosmetic) modifications to whois(1): 1. Added -m option, which selects whois.ra.net as the whois server. This server publishes routing policy for a large number of network operators, and is currently run by Merit (see www.ra.net for more details). 2. Added -q option, which constructs a whois server to use based on the TLD of the (single) argument, with ".whois-servers.net" appended. The whois-servers.net zone is run by the people at ultradns.com. This allows, for example, queries like whois -q patho.gen.nz whois -q microsoft.com whois -q nasa.gov whois -q nic.fr whois -q demon.co.uk to all provide meaningful output without having to worry about different whois switches for different registries. Small, simple patch included in bin/14095. Comments welcome :) Joe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Oct 2 22:27:35 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from altair.mayn.de (altair.mayn.de [194.95.209.137]) by hub.freebsd.org (Postfix) with ESMTP id 1CBC514CAF; Sat, 2 Oct 1999 22:27:29 -0700 (PDT) (envelope-from mkb@altair.mayn.de) Received: (from mkb@localhost) by altair.mayn.de (8.9.3/8.9.3) id HAA01204; Sun, 3 Oct 1999 07:22:19 +0200 (CEST) (envelope-from mkb) Date: Sun, 3 Oct 1999 07:22:19 +0200 From: Matthias Buelow To: hackers@freebsd.org Cc: freebsd-questions@freebsd.org Message-ID: <19991003072219.F728@altair.mayn.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre3i Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Bcc: Subject: Re: FTP directory listing with ftpio(3) and fetch(3) Reply-To: In-Reply-To: Dag-Erling Smorgrav wrote: >Type 'man 3 fetch', scroll down to the BUGS section, and see the >light. Next, scroll back up to the AUTHORS section and find out who to >contact :) (fetch stuff) BTW.. although risking to be off-topic by miles, I always liked the way how NetBSD's ftp(1) (since 1.4 or so) implemented http and ftp URL fetching and thus eliminated the need for a fetch(1) command. Couldn't the FreeBSD ftp(1) be enhanced that way, [ObTopic, slime slime] to use fetch(3) for that purpose? (Or just "steal" the NetBSD implementation, FreeBSD aren't the Knights who say NIH, I would hope.) I'd really love to have yet another superfluous userland tool like fetch(1) go away, especially because it collides in namespace with another fetch program and the functionality could be very well integrated with the ftp utility. Personally, I find fetch(1) a bad idea. Cc'ied to -questions, for obvious reasons, thanks for your attention :). mkb To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Oct 2 22:47:24 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from rucus.ru.ac.za (rucus.ru.ac.za [146.231.29.2]) by hub.freebsd.org (Postfix) with SMTP id C658714DD0 for ; Sat, 2 Oct 1999 22:47:17 -0700 (PDT) (envelope-from bvi@rucus.ru.ac.za) Received: (qmail 16957 invoked by uid 374); 3 Oct 1999 05:49:34 -0000 Date: Sun, 3 Oct 1999 07:49:34 +0200 From: Barry Irwin To: Matthias Buelow Cc: hackers@FreeBSD.ORG, freebsd-questions@FreeBSD.ORG Subject: Re: your mail Message-ID: <19991003074934.C47240@rucus.ru.ac.za> References: <19991003072219.F728@altair.mayn.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre2i In-Reply-To: <19991003072219.F728@altair.mayn.de> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun 1999-10-03 (07:22), Matthias Buelow wrote: > Bcc: > Subject: Re: FTP directory listing with ftpio(3) and fetch(3) > Reply-To: > In-Reply-To: > > > BTW.. although risking to be off-topic by miles, I always liked the way > how NetBSD's ftp(1) (since 1.4 or so) implemented http and ftp URL > fetching and thus eliminated the need for a fetch(1) command. > Couldn't the FreeBSD ftp(1) be enhanced that way, [ObTopic, slime slime] > to use fetch(3) for that purpose? This is where a useful tool like wget comes into play. Wget can be pretty much used as an automated replacement for fetch, or FTP URL retrieval. Can also be plugged into the whole ports system so that it can retrieve the ports data packages. > > I'd really love to have yet another superfluous userland tool like > fetch(1) go away, especially because it collides in namespace with > another fetch program and the functionality could be very well > integrated with the ftp utility. Personally, I find fetch(1) a bad idea. > root@rucus:~# ls -lad `which fetch` -r-xr-xr-x 1 root wheel 35300 Jun 11 22:10 /usr/bin/fetch root@rucus:~# ls -lad `which wget` -r-xr-xr-x 1 root wheel 103240 Dec 23 1998 /usr/local/bin/wget root@rucus:~# ls -lad `which ftp` -r-xr-xr-x 3 root wheel 72312 Jun 11 22:10 /usr/bin/ftp as this shows fetch is a far more leightweight implementation. Important when considering its use in systems like picobsd, or other small projects. The whole *nix philosophy is to have a myrid of tools that all do a job, and the joy/pain, comes in the blending, and linking of these tools together in order to perform a complex task. Barry -- -------------------------------------------------------------------------- Barry Irwin IRC: balin@zanet (#linux) bvi@moria.org http://rucus.ru.ac.za/~bvi Whois BI414 - PMPN8EZ - http://moria.org -------------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message