From owner-freebsd-hackers@FreeBSD.ORG Sun Oct 17 11:50:17 2004 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 698B916A4CE for ; Sun, 17 Oct 2004 11:50:17 +0000 (GMT) Received: from excalibur.ronald.org (excalibur.ronald.org [83.120.8.12]) by mx1.FreeBSD.org (Postfix) with ESMTP id 84C0943D1D for ; Sun, 17 Oct 2004 11:50:14 +0000 (GMT) (envelope-from nz@thiemo.net) Received: from styx.ham01.thiemo.net (port-212-202-20-245.dynamic.qsc.de [212.202.20.245])i9HBoCeO004346 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Sun, 17 Oct 2004 13:50:13 +0200 (CEST) Received: from mygiea.ham01.thiemo.net (localhost [127.0.0.1]) by styx.ham01.thiemo.net (8.13.1/8.13.1) with ESMTP id i9HBoBAZ022827 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Sun, 17 Oct 2004 13:50:12 +0200 (CEST) Received: (from thiemo@localhost) by mygiea.ham01.thiemo.net (8.13.1/8.13.1/Submit) id i9HBoB0r022822 for freebsd-hackers@freebsd.org; Sun, 17 Oct 2004 13:50:11 +0200 (CEST) Date: Sun, 17 Oct 2004 13:50:11 +0200 From: Thiemo Nordenholz To: freebsd-hackers@freebsd.org Message-ID: <20041017115011.GA22744@mygiea.ham01.thiemo.net> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="gBBFr7Ir9EOA20Yy" Content-Disposition: inline User-Agent: Mutt/1.4.1i Subject: How to access a device on LPC bus? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 17 Oct 2004 11:50:17 -0000 --gBBFr7Ir9EOA20Yy Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hi there, beginner's question, maybe: How do I, from a device driver point of view, access a device attached to the "Low Pincount" (LPC) bus?=20 I have a Winbond W83L518D card reader controller in a notebook that I want to access. The only way I see this device at all is (on 5.3-BETA7) in "pnpinfo -v" output, where it shows up as=20 unknown pnpinfo _HID=3DWEC0518 _UID=3D0 at handle=3D\_SB_.C046.C059.C140 -- I have identified it then by the Hardware ID. I do not see any more information, especially no resource usage. As far as I have read, the LPC bus devices can accessed just like ISA devices. Actually, what seems to be the ACPI parent of this Winbond chip (with handle \_SB_.C046.C059) is shown as isab0 in the devinfo output. Now, to implement an identify function in a driver for this, I need to access data in the controller - but I don't have any information about its memory attachments...=20 Could anyone give me a hint what to do here, some driver to look into for an example, or just tell me that my idea of an ISA driver on fBSD is completely wrong? Thanks in advance, Thiemo --=20 Query a PGP key server (e.g. http://www.pgp.net/) for my public key 4106862= 9. --gBBFr7Ir9EOA20Yy Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (FreeBSD) iQCVAwUBQXJcc6JjBr5BBoYpAQGjJgP/Vf74Ulguckhjp8mIaCvtcI8WuPYTM17k qttJahpfvL0aD3V/jMJru0gYMeLBoMNqUaiIfnDM5LlSionoNnl2nH/vsCiaGX6P i3GQvOT8HRMK+IrPjbh6P8QgMR/MuhM1xkPz3xTiQVM7Ze95KQ2ARRv38DAOsI0A tV4lbpvFgik= =kDhz -----END PGP SIGNATURE----- --gBBFr7Ir9EOA20Yy-- From owner-freebsd-hackers@FreeBSD.ORG Sat Oct 16 19:03:45 2004 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7C85316A4D4 for ; Sat, 16 Oct 2004 19:03:45 +0000 (GMT) Received: from relay03.roc.ny.frontiernet.net (relay03.roc.ny.frontiernet.net [66.133.131.36]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3E60E43D1F for ; Sat, 16 Oct 2004 19:03:45 +0000 (GMT) (envelope-from adam@redprince.net) Received: from filter01.roc.ny.frontiernet.net (filter01.roc.ny.frontiernet.net [66.133.131.176]) by relay03.roc.ny.frontiernet.net (Postfix) with ESMTP id B13DC191E74 for ; Sat, 16 Oct 2004 19:03:44 +0000 (UTC) Received: from relay03.roc.ny.frontiernet.net ([66.133.131.36]) [66.133.131.176]) (amavisd-new, port 10024) with LMTP id 14487-36-47 for ; Sat, 16 Oct 2004 19:03:44 +0000 (UTC) Received: from adamsatoms.redprince.net (65-73-73-165.bras01.rnd.wi.frontiernet.net [65.73.73.165]) by relay03.roc.ny.frontiernet.net (Postfix) with ESMTP id 63A971920C2 for ; Sat, 16 Oct 2004 19:03:43 +0000 (UTC) Message-Id: <6.0.1.1.1.20041016135943.0353fb90@adamsatoms.com> X-Sender: adam@adamsatoms.com (Unverified) X-Mailer: QUALCOMM Windows Eudora Version 6.0.1.1 Date: Sat, 16 Oct 2004 14:03:39 -0500 To: freebsd-hackers@freebsd.org From: Jan Opacki (by way of "G. Adam Stanislav" ) Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-Virus-Scanned: by amavisd-new-20040701 (2.0) (Debian) at filter01.roc.ny.frontiernet.net X-Mailman-Approved-At: Sun, 17 Oct 2004 12:20:46 +0000 Subject: Freebsd assembly programming - IN/OUT commands. X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 16 Oct 2004 19:03:45 -0000 Hi Adam, AT the beggining i want to sorry about my poor english. I had a short look at your fbd assembly tutorial. I'm have a such problem useing IN, OUT commands. In my case i want to "speak" with cmos by port 70 and 71. We both know that fbsd as same as linux works in safe mode. So we need a permission to use each port. In linux it's a system call sys_ioperm (http://www.die.net/doc/linux/man/man2/ioperm.2.html). How to ask FreeBSD to allow us to use those ports ? And then we could simply do: mov al, 0 out 70h, al nop nop nop nop in al, 71h Do you haveny any idea ? Best regards, Jan Opacki. From owner-freebsd-hackers@FreeBSD.ORG Sun Oct 17 13:01:03 2004 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 25A7416A4CE for ; Sun, 17 Oct 2004 13:01:03 +0000 (GMT) Received: from kane.otenet.gr (kane.otenet.gr [195.170.0.27]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5597543D39 for ; Sun, 17 Oct 2004 13:01:02 +0000 (GMT) (envelope-from keramida@freebsd.org) Received: from gothmog.gr (patr530-b205.otenet.gr [212.205.244.213]) i9HD0woZ029887; Sun, 17 Oct 2004 16:00:59 +0300 Received: from gothmog.gr (gothmog [127.0.0.1]) by gothmog.gr (8.13.1/8.13.1) with ESMTP id i9HD0v2p001294; Sun, 17 Oct 2004 16:00:57 +0300 (EEST) (envelope-from keramida@freebsd.org) Received: (from giorgos@localhost) by gothmog.gr (8.13.1/8.13.1/Submit) id i9HD0v6N001293; Sun, 17 Oct 2004 16:00:57 +0300 (EEST) (envelope-from keramida@freebsd.org) Date: Sun, 17 Oct 2004 16:00:57 +0300 From: Giorgos Keramidas To: Jan Opacki Message-ID: <20041017130057.GA1132@gothmog.gr> References: <6.0.1.1.1.20041016135943.0353fb90@adamsatoms.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <6.0.1.1.1.20041016135943.0353fb90@adamsatoms.com> cc: freebsd-hackers@freebsd.org Subject: Re: Freebsd assembly programming - IN/OUT commands. X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 17 Oct 2004 13:01:03 -0000 On 2004-10-16 14:03, Jan Opacki wrote: > I had a short look at your fbd assembly tutorial. I'm have a such > problem useing IN, OUT commands. In my case i want to "speak" with cmos > by port 70 and 71. We both know that fbsd as same as linux works in safe > mode. So we need a permission to use each port. In linux it's a system > call sys_ioperm (http://www.die.net/doc/linux/man/man2/ioperm.2.html). > How to ask FreeBSD to allow us to use those ports ? And then we could > simply do: > mov al, 0 > out 70h, al > nop > nop > nop > nop > in al, 71h > Do you haveny any idea ? Look at the io(4) manpage. You need superuser access to work with /dev/io and even then your program should be very careful about not messing up badly with the hardware, but I think it does what you need. A typical use of /dev/io would look like: if ((iofd = open("/dev/io", O_RDONLY)) == -1) err(1, "open: /dev/io"); __asm__("insert your inline asm here"); if (close(iofd) == -1) err(1, "close: /dev/io"); From owner-freebsd-hackers@FreeBSD.ORG Sun Oct 17 14:43:46 2004 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6F07616A4CE for ; Sun, 17 Oct 2004 14:43:46 +0000 (GMT) Received: from gandalf.online.bg (gandalf.online.bg [217.75.128.9]) by mx1.FreeBSD.org (Postfix) with SMTP id C3EAB43D58 for ; Sun, 17 Oct 2004 14:43:44 +0000 (GMT) (envelope-from roam@ringlet.net) Received: (qmail 15577 invoked from network); 17 Oct 2004 14:43:37 -0000 Received: from unknown (HELO straylight.m.ringlet.net) (217.75.135.134) by gandalf.online.bg with SMTP; 17 Oct 2004 14:43:37 -0000 Received: (qmail 18530 invoked by uid 1000); 17 Oct 2004 14:43:53 -0000 Date: Sun, 17 Oct 2004 17:43:53 +0300 From: Peter Pentchev To: Xin LI Message-ID: <20041017144353.GA4639@straylight.m.ringlet.net> Mail-Followup-To: Xin LI , freebsd-hackers@FreeBSD.org References: <20041016172302.GA2764@frontfree.net> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="EVF5PPMfhYS0aIcm" Content-Disposition: inline In-Reply-To: <20041016172302.GA2764@frontfree.net> User-Agent: Mutt/1.5.6i cc: freebsd-hackers@FreeBSD.org Subject: Re: [PATCH] add '-' glibc extension to strftime(3) X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 17 Oct 2004 14:43:46 -0000 --EVF5PPMfhYS0aIcm Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, Oct 17, 2004 at 01:23:02AM +0800, Xin LI wrote: > Hi, folks, >=20 > It turns out that the GNU extension '-' in their strftime(3) implementati= on > is somewhat popular in several applications. The patch in the last part = of > this e-mail will add a simulate implementation for it. Thanks for taking this up! Just a couple of comments further down... > My question is: > (1) Am I doing things cleanly and correctly? I have attempted to > keep the code style consistent with the old one and style(9) > but maybe I have missed something else, or did not do it > sufficently? > (2) Is the way of implementing it clean enough? >=20 > Thanks for any comments! >=20 > Index: strftime.3 > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > RCS file: /home/fcvs/src/lib/libc/stdtime/strftime.3,v > retrieving revision 1.34 > diff -u -r1.34 strftime.3 > --- strftime.3 2 Jul 2004 23:52:12 -0000 1.34 > +++ strftime.3 16 Oct 2004 17:13:08 -0000 > @@ -36,7 +36,7 @@ > .\" @(#)strftime.3 8.1 (Berkeley) 6/4/93 > .\" $FreeBSD: src/lib/libc/stdtime/strftime.3,v 1.34 2004/07/02 23:52:12= ru Exp $ > .\" > -.Dd January 4, 2003 > +.Dd October 17, 2004 > .Dt STRFTIME 3 > .Os > .Sh NAME > @@ -216,6 +216,8 @@ > is replaced by national representation of the date and time > (the format is similar to that produced by > .Xr date 1 ) . > +.It Cm %-* > +GLIBC extensions. Do not do padding when making output. In mdoc manual pages, it is customary to start new sentences on a new line, avoiding the so-called "hard sentence break" of two spaces :) > + pt =3D _conv(t->tm_mday, (Palternative =3D=3D PAD_LESS) ? > + "%d" : "%2d", In view of future extensions (PAD_SPACE, etc), could this not be done better with an array of printf format specifiers, indexed by Palternative? Thanks for doing the work, though! G'luck, Peter --=20 Peter Pentchev roam@ringlet.net roam@cnsys.bg roam@FreeBSD.org PGP key: http://people.FreeBSD.org/~roam/roam.key.asc Key fingerprint FDBA FD79 C26F 3C51 C95E DF9E ED18 B68D 1619 4553 What would this sentence be like if pi were 3? --EVF5PPMfhYS0aIcm Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQFBcoUp7Ri2jRYZRVMRAv8lAKCuzO0gfl22HX9PbqaQqgj4KgJOCACdGkwM d4kqzhAGHtKUbU1emdrxRUA= =/cok -----END PGP SIGNATURE----- --EVF5PPMfhYS0aIcm-- From owner-freebsd-hackers@FreeBSD.ORG Sun Oct 17 14:46:01 2004 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A138016A4CE for ; Sun, 17 Oct 2004 14:46:01 +0000 (GMT) Received: from gandalf.online.bg (gandalf.online.bg [217.75.128.9]) by mx1.FreeBSD.org (Postfix) with SMTP id 8AF1043D2F for ; Sun, 17 Oct 2004 14:46:00 +0000 (GMT) (envelope-from roam@ringlet.net) Received: (qmail 16283 invoked from network); 17 Oct 2004 14:45:54 -0000 Received: from unknown (HELO straylight.m.ringlet.net) (217.75.135.134) by gandalf.online.bg with SMTP; 17 Oct 2004 14:45:54 -0000 Received: (qmail 18755 invoked by uid 1000); 17 Oct 2004 14:46:10 -0000 Date: Sun, 17 Oct 2004 17:46:10 +0300 From: Peter Pentchev To: Giorgos Keramidas Message-ID: <20041017144610.GB4639@straylight.m.ringlet.net> Mail-Followup-To: Giorgos Keramidas , Jan Opacki , freebsd-hackers@freebsd.org References: <6.0.1.1.1.20041016135943.0353fb90@adamsatoms.com> <20041017130057.GA1132@gothmog.gr> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="61jdw2sOBCFtR2d/" Content-Disposition: inline In-Reply-To: <20041017130057.GA1132@gothmog.gr> User-Agent: Mutt/1.5.6i cc: Jan Opacki cc: freebsd-hackers@freebsd.org Subject: Re: Freebsd assembly programming - IN/OUT commands. X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 17 Oct 2004 14:46:01 -0000 --61jdw2sOBCFtR2d/ Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, Oct 17, 2004 at 04:00:57PM +0300, Giorgos Keramidas wrote: > On 2004-10-16 14:03, Jan Opacki wrote: > > I had a short look at your fbd assembly tutorial. I'm have a such > > problem useing IN, OUT commands. In my case i want to "speak" with cmos > > by port 70 and 71. We both know that fbsd as same as linux works in safe > > mode. So we need a permission to use each port. In linux it's a system > > call sys_ioperm (http://www.die.net/doc/linux/man/man2/ioperm.2.html). > > How to ask FreeBSD to allow us to use those ports ? And then we could > > simply do: > > mov al, 0 > > out 70h, al > > nop > > nop > > nop > > nop > > in al, 71h > > Do you haveny any idea ? >=20 > Look at the io(4) manpage. You need superuser access to work with > /dev/io and even then your program should be very careful about not > messing up badly with the hardware, but I think it does what you need. Of course, a bit more controlled way (as described in the io(4) manpage, too), would be to use the i386_set_ioperm(2) syscall :) It is a bit non-portable, true, but since Jan uses MASM-style assembly and mentions ports 70h and 71h, I think it would do what he needs. G'luck, Peter --=20 Peter Pentchev roam@ringlet.net roam@cnsys.bg roam@FreeBSD.org PGP key: http://people.FreeBSD.org/~roam/roam.key.asc Key fingerprint FDBA FD79 C26F 3C51 C95E DF9E ED18 B68D 1619 4553 This inert sentence is my body, but my soul is alive, dancing in the sparks= of your brain. --61jdw2sOBCFtR2d/ Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQFBcoWy7Ri2jRYZRVMRAphmAJ4m7h1Rn5p9Plu45cSoxAUxHytAWwCguxOT dj17H7F6o2R/2MfyNJE69Xs= =knZl -----END PGP SIGNATURE----- --61jdw2sOBCFtR2d/-- From owner-freebsd-hackers@FreeBSD.ORG Sun Oct 17 14:47:19 2004 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6C71716A4D1 for ; Sun, 17 Oct 2004 14:47:19 +0000 (GMT) Received: from gandalf.online.bg (gandalf.online.bg [217.75.128.9]) by mx1.FreeBSD.org (Postfix) with SMTP id 785D543D1D for ; Sun, 17 Oct 2004 14:47:18 +0000 (GMT) (envelope-from roam@ringlet.net) Received: (qmail 16684 invoked from network); 17 Oct 2004 14:47:13 -0000 Received: from unknown (HELO straylight.m.ringlet.net) (217.75.135.134) by gandalf.online.bg with SMTP; 17 Oct 2004 14:47:13 -0000 Received: (qmail 18811 invoked by uid 1000); 17 Oct 2004 14:47:29 -0000 Date: Sun, 17 Oct 2004 17:47:29 +0300 From: Peter Pentchev To: Xin LI , freebsd-hackers@FreeBSD.org Message-ID: <20041017144729.GC4639@straylight.m.ringlet.net> Mail-Followup-To: Xin LI , freebsd-hackers@FreeBSD.org References: <20041016172302.GA2764@frontfree.net> <20041017144353.GA4639@straylight.m.ringlet.net> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="S1BNGpv0yoYahz37" Content-Disposition: inline In-Reply-To: <20041017144353.GA4639@straylight.m.ringlet.net> User-Agent: Mutt/1.5.6i Subject: Re: [PATCH] add '-' glibc extension to strftime(3) X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 17 Oct 2004 14:47:19 -0000 --S1BNGpv0yoYahz37 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, Oct 17, 2004 at 05:43:53PM +0300, Peter Pentchev wrote: > On Sun, Oct 17, 2004 at 01:23:02AM +0800, Xin LI wrote: > > Hi, folks, > >=20 > > It turns out that the GNU extension '-' in their strftime(3) implementa= tion > > is somewhat popular in several applications. The patch in the last par= t of > > this e-mail will add a simulate implementation for it. >=20 > Thanks for taking this up! Just a couple of comments further down... [snip] > > + pt =3D _conv(t->tm_mday, (Palternative =3D=3D PAD_LESS) ? > > + "%d" : "%2d", >=20 > In view of future extensions (PAD_SPACE, etc), could this not be done > better with an array of printf format specifiers, indexed by > Palternative? Just in case this was a bit unclear, I mean something like pt =3D _conv(t->tm_mday, fmt_mday[Palternative], ...); G'luck, Peter --=20 Peter Pentchev roam@ringlet.net roam@cnsys.bg roam@FreeBSD.org PGP key: http://people.FreeBSD.org/~roam/roam.key.asc Key fingerprint FDBA FD79 C26F 3C51 C95E DF9E ED18 B68D 1619 4553 I am the meaning of this sentence. --S1BNGpv0yoYahz37 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQFBcoYB7Ri2jRYZRVMRAg02AJ0Zjt/xZ9OeJM+oWhoQHivHnwf6LQCeNRKX JIZlYDu+XaJHSO/BdJGYlhY= =TrNR -----END PGP SIGNATURE----- --S1BNGpv0yoYahz37-- From owner-freebsd-hackers@FreeBSD.ORG Sun Oct 17 15:21:46 2004 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 59B6B16A4CE for ; Sun, 17 Oct 2004 15:21:46 +0000 (GMT) Received: from mail.freebsd.org.cn (dns3.freebsd.org.cn [61.129.66.75]) by mx1.FreeBSD.org (Postfix) with SMTP id 6976C43D31 for ; Sun, 17 Oct 2004 15:21:42 +0000 (GMT) (envelope-from delphij@frontfree.net) Received: (qmail 65407 invoked by uid 0); 17 Oct 2004 15:16:59 -0000 Received: from unknown (HELO beastie.frontfree.net) (219.239.98.7) by mail.freebsd.org.cn with SMTP; 17 Oct 2004 15:16:59 -0000 Received: from localhost (localhost.frontfree.net [127.0.0.1]) by beastie.frontfree.net (Postfix) with ESMTP id 81A02132B80; Sun, 17 Oct 2004 23:21:38 +0800 (CST) Received: from beastie.frontfree.net ([127.0.0.1]) by localhost (beastie.frontfree.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 00870-03; Sun, 17 Oct 2004 23:21:31 +0800 (CST) Received: by beastie.frontfree.net (Postfix, from userid 1001) id 640771329B0; Sun, 17 Oct 2004 23:21:30 +0800 (CST) Date: Sun, 17 Oct 2004 23:21:30 +0800 From: Xin LI To: Peter Pentchev Message-ID: <20041017152130.GA2927@frontfree.net> References: <20041016172302.GA2764@frontfree.net> <20041017144353.GA4639@straylight.m.ringlet.net> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="lrZ03NoBR/3+SXJZ" Content-Disposition: inline In-Reply-To: <20041017144353.GA4639@straylight.m.ringlet.net> User-Agent: Mutt/1.4.2.1i X-GPG-key-ID/Fingerprint: 0xCAEEB8C0 / 43B8 B703 B8DD 0231 B333 DC28 39FB 93A0 CAEE B8C0 X-GPG-Public-Key: http://www.delphij.net/delphij.asc X-Operating-System: FreeBSD beastie.frontfree.net 5.3-delphij FreeBSD 5.3-delphij #4: Mon Sep 13 12:44:05 CST 2004 delphij@beastie.frontfree.net:/usr/obj/usr/src/sys/BEASTIE i386 X-URL: http://www.delphij.net X-By: delphij@beastie.frontfree.net X-Location: Beijing, China X-Virus-Scanned: by amavisd-new at frontfree.net cc: freebsd-hackers@FreeBSD.org Subject: Re: [PATCH] add '-' glibc extension to strftime(3) X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 17 Oct 2004 15:21:46 -0000 --lrZ03NoBR/3+SXJZ Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hi, Peter, On Sun, Oct 17, 2004 at 05:43:53PM +0300, Peter Pentchev wrote: > > It turns out that the GNU extension '-' in their strftime(3) implementa= tion > > is somewhat popular in several applications. The patch in the last par= t of > > this e-mail will add a simulate implementation for it. >=20 [snip] > > @@ -216,6 +216,8 @@ > > is replaced by national representation of the date and time > > (the format is similar to that produced by > > .Xr date 1 ) . > > +.It Cm %-* > > +GLIBC extensions. Do not do padding when making output. >=20 > In mdoc manual pages, it is customary to start new sentences on a new > line, avoiding the so-called "hard sentence break" of two spaces :) Hmm... So I really need to read more mdoc(7) :-) Thanks! > > + pt =3D _conv(t->tm_mday, (Palternative =3D=3D PAD_LESS) ? > > + "%d" : "%2d", >=20 > In view of future extensions (PAD_SPACE, etc), could this not be done > better with an array of printf format specifiers, indexed by > Palternative? Yes for sure. I will make these changes ASAP. I'm looking for a piece of code example in our library because I seemed to need multiple dimensional array, and I wanted to keep the code more readable (and easier to extend). Cheers, --=20 Xin LI http://www.delphij.net/ See complete headers for GPG key and other information. --lrZ03NoBR/3+SXJZ Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQFBco36/cVsHxFZiIoRAmqYAKCAcmMLSy1x/LYrDXjlH8bSW6mzPwCfT0kE MEJp+x82ctm60AXdwvgAqJ4= =9Cmy -----END PGP SIGNATURE----- --lrZ03NoBR/3+SXJZ-- From owner-freebsd-hackers@FreeBSD.ORG Sun Oct 17 19:45:13 2004 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5F5B716A4CE; Sun, 17 Oct 2004 19:45:13 +0000 (GMT) Received: from mail2.astercity.net (mail2.aster.pl [212.76.33.39]) by mx1.FreeBSD.org (Postfix) with ESMTP id 87D6D43D1D; Sun, 17 Oct 2004 19:45:12 +0000 (GMT) (envelope-from opacki@acn.waw.pl) Received: from [62.121.87.200] (200-ego-4.acn.waw.pl [62.121.87.200]) by mail2.astercity.net (sendmail) with ESMTP id AA539AA2CB; Sun, 17 Oct 2004 21:45:10 +0200 (CEST) From: Jan Opacki To: Peter Pentchev In-Reply-To: <20041017144610.GB4639@straylight.m.ringlet.net> References: <6.0.1.1.1.20041016135943.0353fb90@adamsatoms.com> <20041017130057.GA1132@gothmog.gr> <20041017144610.GB4639@straylight.m.ringlet.net> Content-Type: text/plain Message-Id: <1098042389.372.33.camel@200-ego-4.acn.waw.pl> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.6 Date: Sun, 17 Oct 2004 21:46:29 +0200 Content-Transfer-Encoding: 7bit cc: freebsd-hackers@freebsd.org cc: Giorgos Keramidas Subject: Re: Freebsd assembly programming - IN/OUT commands. X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: opacki@acn.waw.pl List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 17 Oct 2004 19:45:13 -0000 Hi, Thanks for help. i386_set_ioperm() is exactly what i need. Regards, Jan Opacki On Sun, 2004-10-17 at 16:46, Peter Pentchev wrote: > On Sun, Oct 17, 2004 at 04:00:57PM +0300, Giorgos Keramidas wrote: > > On 2004-10-16 14:03, Jan Opacki wrote: > > > I had a short look at your fbd assembly tutorial. I'm have a such > > > problem useing IN, OUT commands. In my case i want to "speak" with cmos > > > by port 70 and 71. We both know that fbsd as same as linux works in safe > > > mode. So we need a permission to use each port. In linux it's a system > > > call sys_ioperm (http://www.die.net/doc/linux/man/man2/ioperm.2.html). > > > How to ask FreeBSD to allow us to use those ports ? And then we could > > > simply do: > > > mov al, 0 > > > out 70h, al > > > nop > > > nop > > > nop > > > nop > > > in al, 71h > > > Do you haveny any idea ? > > > > Look at the io(4) manpage. You need superuser access to work with > > /dev/io and even then your program should be very careful about not > > messing up badly with the hardware, but I think it does what you need. > > Of course, a bit more controlled way (as described in the io(4) manpage, > too), would be to use the i386_set_ioperm(2) syscall :) It is a bit > non-portable, true, but since Jan uses MASM-style assembly and mentions > ports 70h and 71h, I think it would do what he needs. > > G'luck, > Peter From owner-freebsd-hackers@FreeBSD.ORG Sun Oct 17 21:00:54 2004 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3664C16A4DF; Sun, 17 Oct 2004 21:00:54 +0000 (GMT) Received: from arginine.spc.org (arginine.spc.org [195.206.69.236]) by mx1.FreeBSD.org (Postfix) with ESMTP id 691B443D46; Sun, 17 Oct 2004 21:00:53 +0000 (GMT) (envelope-from bms@spc.org) Received: from localhost (localhost [127.0.0.1]) by arginine.spc.org (Postfix) with ESMTP id 30A7365491; Sun, 17 Oct 2004 22:00:51 +0100 (BST) Received: from arginine.spc.org ([127.0.0.1]) by localhost (arginine.spc.org [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 01186-01-2; Sun, 17 Oct 2004 22:00:50 +0100 (BST) Received: from empiric.dek.spc.org (adsl-67-121-95-134.dsl.snfc21.pacbell.net [67.121.95.134]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by arginine.spc.org (Postfix) with ESMTP id E6DD46548D; Sun, 17 Oct 2004 22:00:49 +0100 (BST) Received: by empiric.dek.spc.org (Postfix, from userid 1001) id 0BEC964BD; Sun, 17 Oct 2004 14:00:42 -0700 (PDT) Date: Sun, 17 Oct 2004 14:00:42 -0700 From: Bruce M Simpson To: Jan Opacki Message-ID: <20041017210042.GA18249@empiric.icir.org> Mail-Followup-To: Jan Opacki , Peter Pentchev , freebsd-hackers@freebsd.org, Giorgos Keramidas References: <6.0.1.1.1.20041016135943.0353fb90@adamsatoms.com> <20041017130057.GA1132@gothmog.gr> <20041017144610.GB4639@straylight.m.ringlet.net> <1098042389.372.33.camel@200-ego-4.acn.waw.pl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1098042389.372.33.camel@200-ego-4.acn.waw.pl> cc: freebsd-hackers@freebsd.org cc: Giorgos Keramidas Subject: Re: Freebsd assembly programming - IN/OUT commands. X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 17 Oct 2004 21:00:54 -0000 On Sun, Oct 17, 2004 at 09:46:29PM +0200, Jan Opacki wrote: > Thanks for help. i386_set_ioperm() is exactly what i need. I have to say though I've had processes dump core the first time I've tried doing I/O port accesses after calling i386_set_ioperm() on 5.x since 5.0. This behaviour is sporadic. With opening /dev/io, I have had no problem. Also, the /dev/io method appears to work on amd64, whereas the i386_set_ioperm() method does not. BMS From owner-freebsd-hackers@FreeBSD.ORG Sun Oct 17 21:11:15 2004 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9CCA616A4CE for ; Sun, 17 Oct 2004 21:11:15 +0000 (GMT) Received: from arginine.spc.org (arginine.spc.org [195.206.69.236]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4D6F543D1D for ; Sun, 17 Oct 2004 21:11:15 +0000 (GMT) (envelope-from bms@spc.org) Received: from localhost (localhost [127.0.0.1]) by arginine.spc.org (Postfix) with ESMTP id 5142C653E6; Sun, 17 Oct 2004 22:11:14 +0100 (BST) Received: from arginine.spc.org ([127.0.0.1]) by localhost (arginine.spc.org [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 01351-01; Sun, 17 Oct 2004 22:11:13 +0100 (BST) Received: from empiric.dek.spc.org (adsl-67-121-95-134.dsl.snfc21.pacbell.net [67.121.95.134]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by arginine.spc.org (Postfix) with ESMTP id AF6EF652FE; Sun, 17 Oct 2004 22:11:12 +0100 (BST) Received: by empiric.dek.spc.org (Postfix, from userid 1001) id 53F9064BD; Sun, 17 Oct 2004 14:11:06 -0700 (PDT) Date: Sun, 17 Oct 2004 14:11:06 -0700 From: Bruce M Simpson To: Thiemo Nordenholz Message-ID: <20041017211106.GA19515@empiric.icir.org> Mail-Followup-To: Thiemo Nordenholz , freebsd-hackers@freebsd.org References: <20041017115011.GA22744@mygiea.ham01.thiemo.net> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="yrj/dFKFPuw6o+aM" Content-Disposition: inline In-Reply-To: <20041017115011.GA22744@mygiea.ham01.thiemo.net> cc: freebsd-hackers@freebsd.org Subject: Re: How to access a device on LPC bus? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 17 Oct 2004 21:11:15 -0000 --yrj/dFKFPuw6o+aM Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, Oct 17, 2004 at 01:50:11PM +0200, Thiemo Nordenholz wrote: > beginner's question, maybe: How do I, from a device driver point of view, > access a device attached to the "Low Pincount" (LPC) bus?=20 Treat it as an ISA bus but write an ACPI attachment for it. Look at src/sys/dev/fdc/fdc_acpi.c:fdc_acpi_probe() for an example. > unknown pnpinfo _HID=3DWEC0518 _UID=3D0 at handle=3D\_SB_.C046.C059.C= 140 There appears to be a Linux driver for this, which gives you something to work from. > Now, to implement an identify function in a driver for this, I need to > access data in the controller - but I don't have any information about its > memory attachments...=20 I'd suggest looking at that driver and accessing the registers you need to identify the device sub-type in your attach function. BMS --yrj/dFKFPuw6o+aM Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Comment: '' iD8DBQFBct/pueUpAYYNtTsRAttJAKClyFArAYzQkon8+/PFsVtbCqyS7ACeMZWD UeTQCd4UA9J2F7Qyr3eaAow= =Xhhl -----END PGP SIGNATURE----- --yrj/dFKFPuw6o+aM-- From owner-freebsd-hackers@FreeBSD.ORG Mon Oct 18 08:44:27 2004 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D5EF816A4CE for ; Mon, 18 Oct 2004 08:44:27 +0000 (GMT) Received: from mail.freebsd.org.cn (dns3.freebsd.org.cn [61.129.66.75]) by mx1.FreeBSD.org (Postfix) with SMTP id 7500043D77 for ; Mon, 18 Oct 2004 08:44:24 +0000 (GMT) (envelope-from delphij@frontfree.net) Received: (qmail 71023 invoked by uid 0); 18 Oct 2004 08:39:39 -0000 Received: from unknown (HELO beastie.frontfree.net) (219.239.98.7) by mail.freebsd.org.cn with SMTP; 18 Oct 2004 08:39:39 -0000 Received: from localhost (localhost.frontfree.net [127.0.0.1]) by beastie.frontfree.net (Postfix) with ESMTP id 70F7D1346E3 for ; Mon, 18 Oct 2004 16:44:19 +0800 (CST) Received: from beastie.frontfree.net ([127.0.0.1]) by localhost (beastie.frontfree.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 01494-07 for ; Mon, 18 Oct 2004 16:44:09 +0800 (CST) Received: by beastie.frontfree.net (Postfix, from userid 1001) id 2DD121346CC; Mon, 18 Oct 2004 16:44:09 +0800 (CST) Date: Mon, 18 Oct 2004 16:44:08 +0800 From: Xin LI To: freebsd-hackers@FreeBSD.org Message-ID: <20041018084408.GA1475@frontfree.net> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="OgqxwSJOaUobr8KG" Content-Disposition: inline User-Agent: Mutt/1.4.2.1i X-GPG-key-ID/Fingerprint: 0xCAEEB8C0 / 43B8 B703 B8DD 0231 B333 DC28 39FB 93A0 CAEE B8C0 X-GPG-Public-Key: http://www.delphij.net/delphij.asc X-Operating-System: FreeBSD beastie.frontfree.net 5.3-delphij FreeBSD 5.3-delphij #4: Mon Sep 13 12:44:05 CST 2004 delphij@beastie.frontfree.net:/usr/obj/usr/src/sys/BEASTIE i386 X-URL: http://www.delphij.net X-By: delphij@beastie.frontfree.net X-Location: Beijing, China X-Virus-Scanned: by amavisd-new at frontfree.net Subject: [PATCH] Second attempt: Add glibc-style '-', '_', '0' strftime(3) functionalities X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 18 Oct 2004 08:44:27 -0000 --OgqxwSJOaUobr8KG Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hi folks, I have adopted roam@'s suggestions and the latest patch is available at: http://people.freebsd.org/~delphij/patch-libc Please let me know your comments, concerns and suggestions. I would like to commit it to -HEAD if nobody objects it in one week. Thanks in advance! Cheers, --=20 Xin LI http://www.delphij.net/ See complete headers for GPG key and other information. --OgqxwSJOaUobr8KG Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQFBc4JY/cVsHxFZiIoRAn1/AJ9vXJTIs0A/GYo3CP7CkS7A5kz+6gCfcvGq ck97cjYsJYDpA176BCna/F8= =yJR/ -----END PGP SIGNATURE----- --OgqxwSJOaUobr8KG-- From owner-freebsd-hackers@FreeBSD.ORG Sun Oct 17 23:48:03 2004 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CFC7816A4CE for ; Sun, 17 Oct 2004 23:48:03 +0000 (GMT) Received: from web53301.mail.yahoo.com (web53301.mail.yahoo.com [206.190.39.230]) by mx1.FreeBSD.org (Postfix) with SMTP id 5D03143D45 for ; Sun, 17 Oct 2004 23:48:03 +0000 (GMT) (envelope-from non_secure@yahoo.com) Message-ID: <20041017234802.33563.qmail@web53301.mail.yahoo.com> Received: from [24.94.23.114] by web53301.mail.yahoo.com via HTTP; Sun, 17 Oct 2004 16:48:02 PDT Date: Sun, 17 Oct 2004 16:48:02 -0700 (PDT) From: Joe Schmoe To: freebsd-hackers@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailman-Approved-At: Mon, 18 Oct 2004 12:12:32 +0000 Subject: passwordless ssh logins with shared _HOST_ keys - not working. X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 17 Oct 2004 23:48:04 -0000 (I have asked this several times on -questions and gotten nothing ...) I am trying to allow _all users_ on CLIENT to login to SERVER without a password. IMPORTANT: I am not interested in user keys _at all_ - at no point in this process should I ever be dealing with any keys in /home/user/.ssh - I am only interested in doing this with HOST keys - where I copy one key between SERVER and CLIENT, and _all_ users on CLIENT can login to SERVER without a password. Don't even mention user keys. My /etc/sshd/sshd_config is exactly the same on both SERVER and CLIENT: #VersionAddendum FreeBSD-20020629 #Port 22 #Protocol 2,1 #ListenAddress 0.0.0.0 #ListenAddress :: # Authentication: IgnoreRhosts yes #RhostsRSAAuthentication no HostbasedAuthentication yes IgnoreUserKnownHosts yes ChallengeResponseAuthentication no Further, SERVER has CLIENT in its /etc/hosts.equiv, and CLIENT has SERVER in its /etc/hosts.equiv Finally, I have run: ssh-keyscan SERVER >> /etc/ssh/ssh_known_hosts on the CLIENT, and run: ssh-keyscan CLIENT >> /etc/ssh/ssh_known_hosts on the SERVER. So the keys are properly shared. The permissions on /etc/ssh/known_hosts on each system are: 2 -rw-r--r-- 1 root wheel So that's it. The options are set in sshd_config, the keys have been exchanged, hosts.equiv are populated and permissions are correct. SO now I go to CLIENT and run: ssh user@SERVER and I get a password prompt!!! So what am I doing wrong ? Again - NO user keys are used and I am not interested in user keys _AT ALL_. DOn't even mention the /home/user/.ssh directory. The goal here is to share one public key between SERVER and CLIENT and allow _all_ users on CLIENT to log into SERVER without a password. So what am I doing wrong ? thanks. __________________________________ Do you Yahoo!? Yahoo! Mail Address AutoComplete - You start. We finish. http://promotions.yahoo.com/new_mail From owner-freebsd-hackers@FreeBSD.ORG Mon Oct 18 14:14:00 2004 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 85C1A16A4CE for ; Mon, 18 Oct 2004 14:14:00 +0000 (GMT) Received: from pc5.i.0x5.de (n.0x5.de [217.197.85.142]) by mx1.FreeBSD.org (Postfix) with ESMTP id CCD8943D39 for ; Mon, 18 Oct 2004 14:13:58 +0000 (GMT) (envelope-from nicolas@i.0x5.de) Received: from pc5.i.0x5.de (nicolas@localhost [127.0.0.1]) by pc5.i.0x5.de (8.12.11/8.12.11) with ESMTP id i9IEDuNu006693; Mon, 18 Oct 2004 16:13:56 +0200 (CEST) (envelope-from nicolas@pc5.i.0x5.de) Received: (from nicolas@localhost) by pc5.i.0x5.de (8.12.11/8.12.11/Submit) id i9IEDtvo006691; Mon, 18 Oct 2004 16:13:55 +0200 (CEST) (envelope-from nicolas) Date: Mon, 18 Oct 2004 16:13:55 +0200 From: Nicolas Rachinsky To: Joe Schmoe Message-ID: <20041018141355.GB5824@pc5.i.0x5.de> Mail-Followup-To: Joe Schmoe , freebsd-hackers@freebsd.org References: <20041017234802.33563.qmail@web53301.mail.yahoo.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20041017234802.33563.qmail@web53301.mail.yahoo.com> X-Powered-by: FreeBSD X-Homepage: http://www.rachinsky.de X-PGP-Keyid: C11ABC0E X-PGP-Fingerprint: 19DB 8392 8FE0 814A 7362 EEBD A53B 526A C11A BC0E X-PGP-Key: http://www.rachinsky.de/nicolas/nicolas_rachinsky.asc User-Agent: Mutt/1.5.6i cc: freebsd-hackers@freebsd.org Subject: Re: passwordless ssh logins with shared _HOST_ keys - not working. X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 18 Oct 2004 14:14:00 -0000 * Joe Schmoe [2004-10-17 16:48 -0700]: > I am trying to allow _all users_ on CLIENT to login to > SERVER without a password. Is your ssh setuid root? Is UsePrivilegedPort set? UsePrivilegedPort Specifies whether to use a privileged port for outgoing connec- tions. The argument must be ``yes'' or ``no''. The default is ``no''. If set to ``yes'' ssh must be setuid root. Note that this option must be set to ``yes'' if RhostsAuthentication and RhostsRSAAuthentication authentications are needed with older servers. Nicolas From owner-freebsd-hackers@FreeBSD.ORG Mon Oct 18 17:41:22 2004 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DCE0B16A4CE for ; Mon, 18 Oct 2004 17:41:22 +0000 (GMT) Received: from maile.cesta.com (maile.cesta.com [64.65.85.11]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8A2AB43D53 for ; Mon, 18 Oct 2004 17:41:22 +0000 (GMT) (envelope-from julian@lava.net) Received: from [192.168.1.100] (tesla.cesta.com [64.65.85.14]) by maile.cesta.com (Postfix) with ESMTP id 24B3053C017 for ; Mon, 18 Oct 2004 07:41:21 -1000 (HST) Mime-Version: 1.0 (Apple Message framework v619) In-Reply-To: <20041017234802.33563.qmail@web53301.mail.yahoo.com> References: <20041017234802.33563.qmail@web53301.mail.yahoo.com> Content-Type: text/plain; charset=US-ASCII; format=flowed Message-Id: Content-Transfer-Encoding: 7bit From: Julian Cowley Date: Mon, 18 Oct 2004 07:41:19 -1000 To: freebsd-hackers@freebsd.org X-Mailer: Apple Mail (2.619) Subject: Re: [Hackers] passwordless ssh logins with shared _HOST_ keys - not working. X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 18 Oct 2004 17:41:23 -0000 On 17 Oct, 2004, at 13:48, Joe Schmoe wrote: > (I have asked this several times on -questions and > gotten nothing ...) > > I am trying to allow _all users_ on CLIENT to login to > SERVER without a password. > > IMPORTANT: I am not interested in user keys _at all_ > - at no point in this process should I ever be dealing > with any keys in /home/user/.ssh - I am only > interested in doing this with HOST keys - where I copy > one key between SERVER and CLIENT, and _all_ users on > CLIENT can login to SERVER without a password. Don't > even mention user keys. > > My /etc/sshd/sshd_config is exactly the same on both > SERVER and CLIENT: > > #VersionAddendum FreeBSD-20020629 > > #Port 22 > #Protocol 2,1 > #ListenAddress 0.0.0.0 > #ListenAddress :: > > # Authentication: > > IgnoreRhosts yes > #RhostsRSAAuthentication no > HostbasedAuthentication yes > IgnoreUserKnownHosts yes > > ChallengeResponseAuthentication no If you are using OpenSSH 3.6 or later, turn on the EnableSSHKeysign option (see ssh-keysign for more information). Also, make sure your forward and reverse DNS is correct on both the client and the server. > Further, SERVER has CLIENT in its /etc/hosts.equiv, > and CLIENT has SERVER in its /etc/hosts.equiv > > Finally, I have run: > > ssh-keyscan SERVER >> /etc/ssh/ssh_known_hosts > > on the CLIENT, and run: > > ssh-keyscan CLIENT >> /etc/ssh/ssh_known_hosts > > on the SERVER. So the keys are properly shared. > > The permissions on /etc/ssh/known_hosts on each system > are: > > 2 -rw-r--r-- 1 root wheel > > So that's it. The options are set in sshd_config, the > keys have been exchanged, hosts.equiv are populated > and permissions are correct. > > SO now I go to CLIENT and run: > > ssh user@SERVER > > and I get a password prompt!!! > > So what am I doing wrong ? Again - NO user keys are > used and I am not interested in user keys _AT ALL_. > DOn't even mention the /home/user/.ssh directory. The > goal here is to share one public key between SERVER > and CLIENT and allow _all_ users on CLIENT to log into > SERVER without a password. > > So what am I doing wrong ? > > thanks. > > > > __________________________________ > Do you Yahoo!? > Yahoo! Mail Address AutoComplete - You start. We finish. > http://promotions.yahoo.com/new_mail > _______________________________________________ > freebsd-hackers@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to > "freebsd-hackers-unsubscribe@freebsd.org" From owner-freebsd-hackers@FreeBSD.ORG Tue Oct 19 05:17:07 2004 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B216316A4CE for ; Tue, 19 Oct 2004 05:17:07 +0000 (GMT) Received: from harmony.village.org (rover.village.org [168.103.84.182]) by mx1.FreeBSD.org (Postfix) with ESMTP id 31A7243D1D for ; Tue, 19 Oct 2004 05:17:07 +0000 (GMT) (envelope-from imp@bsdimp.com) Received: from localhost (harmony.village.org [10.0.0.6]) by harmony.village.org (8.13.1/8.13.1) with ESMTP id i9J5FoEb005826; Mon, 18 Oct 2004 23:15:50 -0600 (MDT) (envelope-from imp@bsdimp.com) Date: Mon, 18 Oct 2004 23:16:06 -0600 (MDT) Message-Id: <20041018.231606.33009893.imp@bsdimp.com> To: listmember@thiemo.net From: "M. Warner Losh" In-Reply-To: <20041017115011.GA22744@mygiea.ham01.thiemo.net> References: <20041017115011.GA22744@mygiea.ham01.thiemo.net> X-Mailer: Mew version 3.3 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit cc: freebsd-hackers@freebsd.org Subject: Re: How to access a device on LPC bus? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 19 Oct 2004 05:17:07 -0000 In message: <20041017115011.GA22744@mygiea.ham01.thiemo.net> Thiemo Nordenholz writes: : Hi there, : : beginner's question, maybe: How do I, from a device driver point of view, : access a device attached to the "Low Pincount" (LPC) bus? : : I have a Winbond W83L518D card reader controller in a notebook that I want : to access. The only way I see this device at all is (on 5.3-BETA7) in : "pnpinfo -v" output, where it shows up as : : unknown pnpinfo _HID=WEC0518 _UID=0 at handle=\_SB_.C046.C059.C140 : : -- I have identified it then by the Hardware ID. I do not see any more : information, especially no resource usage. : : As far as I have read, the LPC bus devices can accessed just like ISA : devices. Actually, what seems to be the ACPI parent of this Winbond chip : (with handle \_SB_.C046.C059) is shown as isab0 in the devinfo output. : : Now, to implement an identify function in a driver for this, I need to : access data in the controller - but I don't have any information about its : memory attachments... : Could anyone give me a hint what to do here, some driver to look into for an : example, or just tell me that my idea of an ISA driver on fBSD is completely : wrong? If there's a HID, you don't need an identify routine. Just match the pnp id. You can have ISA and/or ACPI attachments to cover both cases. Warner From owner-freebsd-hackers@FreeBSD.ORG Tue Oct 19 08:05:33 2004 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D6AF416A4E3 for ; Tue, 19 Oct 2004 08:05:33 +0000 (GMT) Received: from excalibur.ronald.org (excalibur.ronald.org [83.120.8.12]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8A95E43D53 for ; Tue, 19 Oct 2004 08:05:32 +0000 (GMT) (envelope-from nz@thiemo.net) Received: from styx.ham01.thiemo.net (port-212-202-20-245.dynamic.qsc.de [212.202.20.245])i9J85TeO003922 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Tue, 19 Oct 2004 10:05:30 +0200 (CEST) Received: from mygiea.ham01.thiemo.net (localhost [127.0.0.1]) by styx.ham01.thiemo.net (8.13.1/8.13.1) with ESMTP id i9J85SXe057287 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Tue, 19 Oct 2004 10:05:28 +0200 (CEST) Received: (from thiemo@localhost) by mygiea.ham01.thiemo.net (8.13.1/8.13.1/Submit) id i9J85Stv057286 for freebsd-hackers@freebsd.org; Tue, 19 Oct 2004 10:05:28 +0200 (CEST) Date: Tue, 19 Oct 2004 10:05:28 +0200 From: Thiemo Nordenholz To: freebsd-hackers@freebsd.org Message-ID: <20041019080528.GA57209@mygiea.ham01.thiemo.net> References: <20041017115011.GA22744@mygiea.ham01.thiemo.net> <20041018.231606.33009893.imp@bsdimp.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="lrZ03NoBR/3+SXJZ" Content-Disposition: inline In-Reply-To: <20041018.231606.33009893.imp@bsdimp.com> User-Agent: Mutt/1.4.1i Subject: Re: (solved) How to access a device on LPC bus? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 19 Oct 2004 08:05:34 -0000 --lrZ03NoBR/3+SXJZ Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Thanks for the hints - identifying through ACPI is working fine. Best wishes, Thiemo --=20 Query a PGP key server (e.g. http://www.pgp.net/) for my public key 4106862= 9. --lrZ03NoBR/3+SXJZ Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (FreeBSD) iQCVAwUBQXTKyKJjBr5BBoYpAQG/kQP/fAMHxZ6CeyYwG+tgPy1jTcCEPO/9qK6e bBAuVgtFXCvYL+8Vf4GGpx5GKF64dx8gStIIi/DuBjvzzE4rtQETjDPfvq57Mhdh 0vo+ZYlmFbDcQQYgNnDizQopAlP0haLb1FFmk4m/sRxVynUUbwvW+Q/x1hhSeUXR uO5C27Mwauk= =q3A1 -----END PGP SIGNATURE----- --lrZ03NoBR/3+SXJZ-- From owner-freebsd-hackers@FreeBSD.ORG Tue Oct 19 11:36:34 2004 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 060DD16A4CE; Tue, 19 Oct 2004 11:36:34 +0000 (GMT) Received: from r3p34.chello.upc.cz (r3p34.chello.upc.cz [213.220.207.34]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5306843D3F; Tue, 19 Oct 2004 11:36:33 +0000 (GMT) (envelope-from plusik@pohoda.cz) Received: from r3p34.chello.upc.cz (localhost [127.0.0.1]) by r3p34.chello.upc.cz (8.12.10/8.12.10) with ESMTP id i9JBaWPu000970; Tue, 19 Oct 2004 13:36:32 +0200 (CEST) (envelope-from plusik@pohoda.cz) Received: from localhost (plusik@localhost)i9JBaWBM000967; Tue, 19 Oct 2004 13:36:32 +0200 (CEST) (envelope-from plusik@pohoda.cz) X-Authentication-Warning: r3p34.chello.upc.cz: plusik owned process doing -bs Date: Tue, 19 Oct 2004 13:36:32 +0200 (CEST) From: Tomas Pluskal X-X-Sender: plusik@localhost To: freebsd-security@freebsd.org, freebsd-hackers@freebsd.org Message-ID: <20041019133439.X604@localhost> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Subject: new intrusion detection system X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 19 Oct 2004 11:36:34 -0000 Hello to all, I have implemented a new type of intrusion detection system for my Master thesis. I would like to announce this information, in case anyone would be interested in this research. The IDS system is designed as a kernel module for FreeBSD 5.2. It is inspired by the SpamAssassin program, which detects spam by applying a set of tests to every email message and counting a sum of point score generated by each test. My IDS system applies a set of tests to every running process in the OS and counts its score generated by the tests. Therefore, the purpose of the IDS is not to monitor the network traffic, but rather to monitor the process activity. The current system status is a "working prototype" - it is not ready for production usage, but it may serve as a good base for an interesting research. If you are interested in this topic, please read the details here: http://plusik.pohoda.cz/thesis/ Thanks, Tomas From owner-freebsd-hackers@FreeBSD.ORG Mon Oct 18 13:36:16 2004 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 85E7916A4CE; Mon, 18 Oct 2004 13:36:16 +0000 (GMT) Received: from r3p34.chello.upc.cz (r3p34.chello.upc.cz [213.220.207.34]) by mx1.FreeBSD.org (Postfix) with ESMTP id A008443D31; Mon, 18 Oct 2004 13:36:15 +0000 (GMT) (envelope-from plusik@pohoda.cz) Received: from eddie.chello.cz (localhost [127.0.0.1]) by eddie.chello.cz (8.12.10/8.12.10) with ESMTP id i9IDIVY3001356; Mon, 18 Oct 2004 15:18:31 +0200 (CEST) (envelope-from plusik@pohoda.cz) Received: from localhost (plusik@localhost)i9IDIVkG001353; Mon, 18 Oct 2004 15:18:31 +0200 (CEST) (envelope-from plusik@pohoda.cz) X-Authentication-Warning: eddie.chello.cz: plusik owned process doing -bs Date: Mon, 18 Oct 2004 15:18:31 +0200 (CEST) From: Tomas Pluskal X-X-Sender: plusik@localhost To: freebsd-security@freebsd.org, freebsd-hackers@freebsd.org Message-ID: <20041018150025.E578@localhost> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Mailman-Approved-At: Tue, 19 Oct 2004 12:18:31 +0000 Subject: intrusion detection system X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 18 Oct 2004 13:36:16 -0000 Hello to all, I have implemented a new type of intrusion detection system for my Master thesis. I would like to announce this information, in case anyone would be interested in this research. The IDS system is designed as a kernel module for FreeBSD 5.2. It is inspired by the SpamAssassin program, which detects spam by applying a set of tests to every email message and counting a sum of point score generated by each test. My IDS system applies a set of tests to every running process in the OS and counts its score generated by the tests. Therefore, the purpose of the IDS is not to monitor the network traffic, but rather to monitor the process activity. The current system status is a "working prototype" - it is more a research than a real IDS. If you are interested in this, please read the details here: http://plusik.pohoda.cz/thesis/ Thanks, Tomas From owner-freebsd-hackers@FreeBSD.ORG Mon Oct 18 18:26:55 2004 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D655016A4CE for ; Mon, 18 Oct 2004 18:26:55 +0000 (GMT) Received: from web53303.mail.yahoo.com (web53303.mail.yahoo.com [206.190.39.232]) by mx1.FreeBSD.org (Postfix) with SMTP id 1C4AC43D2D for ; Mon, 18 Oct 2004 18:26:55 +0000 (GMT) (envelope-from non_secure@yahoo.com) Message-ID: <20041018182654.94465.qmail@web53303.mail.yahoo.com> Received: from [24.94.23.114] by web53303.mail.yahoo.com via HTTP; Mon, 18 Oct 2004 11:26:54 PDT Date: Mon, 18 Oct 2004 11:26:54 -0700 (PDT) From: Joe Schmoe To: Nicolas Rachinsky In-Reply-To: <20041018141355.GB5824@pc5.i.0x5.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailman-Approved-At: Tue, 19 Oct 2004 12:18:31 +0000 cc: freebsd-hackers@freebsd.org Subject: Re: passwordless ssh logins with shared _HOST_ keys - not working. X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 18 Oct 2004 18:26:55 -0000 --- Nicolas Rachinsky wrote: > Is your ssh setuid root? Is UsePrivilegedPort set? > > UsePrivilegedPort > Specifies whether to use a privileged > port for outgoing connec- > tions. The argument must be ``yes'' or > ``no''. The default is > ``no''. If set to ``yes'' ssh must be > setuid root. Note that > this option must be set to ``yes'' if > RhostsAuthentication and > RhostsRSAAuthentication authentications > are needed with older > servers. > > Nicolas > No, neither. And rightly so, since I am not using either RhostsAuthentication or RhostsRSAAuthentication. The config I pasted is the _entire_ config file - that's all there is. I am using neither of those options, so I shouldn't need suidroot or Privileged port. Is host based keys just broken in ssh on FreeBSD ? I wish someone would just confirm this so I can stop wasting my time ... or deny it and tell me what I am doing wrong - _all_ information regarding my setup is in my original post ... thanks. __________________________________ Do you Yahoo!? Yahoo! Mail Address AutoComplete - You start. We finish. http://promotions.yahoo.com/new_mail From owner-freebsd-hackers@FreeBSD.ORG Tue Oct 19 12:32:58 2004 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0E84E16A4CE for ; Tue, 19 Oct 2004 12:32:58 +0000 (GMT) Received: from gw.gbch.net (gw.gbch.net [203.143.238.93]) by mx1.FreeBSD.org (Postfix) with SMTP id F004B43D4C for ; Tue, 19 Oct 2004 12:32:55 +0000 (GMT) (envelope-from gjb@gbch.net) Received: (qmail 39769 invoked from network); 19 Oct 2004 22:32:53 +1000 Received: from gecko.gbch.net (172.16.1.7) by bambi.gbch.net with SMTP; 19 Oct 2004 22:32:53 +1000 Received: (qmail 1142 invoked by uid 1001); 19 Oct 2004 22:32:53 +1000 Message-ID: Date: Tue, 19 Oct 2004 22:32:53 +1000 From: Greg Black To: Joe Schmoe References: <20041018141355.GB5824@pc5.i.0x5.de> <20041018182654.94465.qmail@web53303.mail.yahoo.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20041018182654.94465.qmail@web53303.mail.yahoo.com> User-Agent: Mutt/1.4.2.1i; gjb-muttsend.sh 1.7 2004-10-05 X-Uptime: 49 days X-Operating-System: FreeBSD 4.10-RELEASE i386 X-Location: Brisbane, Australia; 27.49841S 152.98439E X-URL: http://www.gbch.net/gjb.html X-Blog: http://www.gbch.net/gjb/blog/ X-Image-URL: http://www.gbch.net/gjb/gjb-auug048.gif X-PGP-Key-Fingerprint: EBB2 2A92 A79D 1533 AC00 3C46 5D83 B6FB 4B04 B7D6 X-Request-PGP: http://www.gbch.net/keys/4B04B7D6.asc cc: freebsd-hackers@freebsd.org Subject: Re: passwordless ssh logins with shared _HOST_ keys - not working. X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 19 Oct 2004 12:32:58 -0000 On 2004-10-18, Joe Schmoe wrote: > Is host based keys just broken in ssh on FreeBSD ? I > wish someone would just confirm this so I can stop > wasting my time ... or deny it and tell me what I am > doing wrong - _all_ information regarding my setup is > in my original post ... Can't recall the details and it doesn't help that you expect people to do that. Anyway, are you using ssh protocol 1 or protocol 2? If you're using 2, then you're probably wasting your time, assuming I remember the question. Greg From owner-freebsd-hackers@FreeBSD.ORG Tue Oct 19 12:51:42 2004 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7A7B116A4CE for ; Tue, 19 Oct 2004 12:51:42 +0000 (GMT) Received: from asmtp-a063f29.pas.sa.earthlink.net (asmtp-a063f29.pas.sa.earthlink.net [207.217.120.131]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2C4A943D46 for ; Tue, 19 Oct 2004 12:51:42 +0000 (GMT) (envelope-from martes.wigglesworth@earthlink.net) Received: from [213.209.169.198] (helo=[192.168.1.50]) (TLSv1:AES256-SHA:256) (Exim 4.34) id 1CJtSg-0005qh-06 for freebsd-hackers@freebsd.org; Tue, 19 Oct 2004 05:51:41 -0700 From: Martes Wigglesworth To: freebsd-hackers@freebsd.org In-Reply-To: <20041007120126.CB4A816A529@hub.freebsd.org> References: <20041007120126.CB4A816A529@hub.freebsd.org> Content-Type: text/plain Message-Id: <1098190266.9678.133.camel@Mobile1.276NET> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.5 Date: Tue, 19 Oct 2004 15:51:07 +0300 Content-Transfer-Encoding: 7bit X-ELNK-Trace: 532caf459ba90ce6996df0496707a79d9bea09fe345ed53d9ef193a6bfc3dd48a97b898e0e510232b09f65c2022ef2df900f0771c95f4286350badd9bab72f9c X-Originating-IP: 213.209.169.198 Subject: Problems with flash and native mozilla X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: martes.wigglesworth@earthlink.net List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 19 Oct 2004 12:51:42 -0000 Greetings. I have an issue with my mozilla install. I am unable to figure out how, or what people get flash7 to work with mozilla. And I also have trouble getting anything to work that I need, while maintaining a working desktop. Hence, if I want to install mplayer, I have to upgrade everthing that also makes my desktop, KDE 3.1.4, work with the initial install. Also, the only reliable desktop/production applications seem to be the few that come on the iso install cd. Anyone have any advice on this? Respectfully, Martes From owner-freebsd-hackers@FreeBSD.ORG Tue Oct 19 13:47:08 2004 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9AF8C16A4CE; Tue, 19 Oct 2004 13:47:08 +0000 (GMT) Received: from smtpq1.home.nl (smtpq1.home.nl [213.51.128.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id D129E43D31; Tue, 19 Oct 2004 13:47:07 +0000 (GMT) (envelope-from dodell@sitetronics.com) Received: from [213.51.128.136] (port=45891 helo=smtp5.home.nl) by smtpq1.home.nl with esmtp (Exim 4.30) id 1CJuKQ-0004DD-EK; Tue, 19 Oct 2004 15:47:06 +0200 Received: from cc740438-a.deven1.ov.home.nl ([82.75.136.183]:3983) by smtp5.home.nl with esmtp (Exim 4.30) id 1CJuKP-0000TS-8f; Tue, 19 Oct 2004 15:47:05 +0200 Message-ID: <41751ADA.40107@sitetronics.com> Date: Tue, 19 Oct 2004 15:47:06 +0200 From: "Devon H. O'Dell" User-Agent: Mozilla Thunderbird 0.8 (Windows/20040913) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Tomas Pluskal References: <20041019133439.X604@localhost> In-Reply-To: <20041019133439.X604@localhost> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-AtHome-MailScanner-Information: Please contact support@home.nl for more information X-AtHome-MailScanner: Found to be clean cc: freebsd-security@freebsd.org cc: freebsd-hackers@freebsd.org Subject: Re: new intrusion detection system X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 19 Oct 2004 13:47:08 -0000 Tomas Pluskal wrote: > > Hello to all, > > I have implemented a new type of intrusion detection system for my > Master thesis. I would like to announce this information, in case anyone > would be interested in this research. > > The IDS system is designed as a kernel module for FreeBSD 5.2. It is > inspired by the SpamAssassin program, which detects spam by applying a > set of tests to every email message and counting a sum of point score > generated by each test. My IDS system applies a set of tests to every > running process in the OS and counts its score generated by the tests. > Therefore, the purpose of the IDS is not to monitor the network traffic, > but rather to monitor the process activity. > > The current system status is a "working prototype" - it is not ready for > production usage, but it may serve as a good base for an interesting > research. > > If you are interested in this topic, please read the details here: > http://plusik.pohoda.cz/thesis/ > > Thanks, > > Tomas Hello Tomas, At a first glance of this email, I thought ``An IDS based upon SpamAssassin ideology? Intrusions differ too much from spam for this to be accurate!'' After reading your thesis, my ideas were changed. This work is certainly very interesting, and I encourage you to continue its development. Certainly one thing that would be desirable that I did not see listed in the improvements section (and many other IDS systems, such as Bro) would be the ability to carry out some action (instead of pure reporting) based upon behavior; this would allow for IDS as well as IPS behavior. I'm quite interested and impressed by the work you've done here. Do you have any plans of setting this up as a collaborative project? Can I help you by providing a place for you to do this? At the moment, I'm not able to provide much help for implementing any of the features listed in your thesis (although I am interested in working on and with this software at some point in the not-too-far future :)), but please let me know if I can help by providing resources, as this is something that I can do with little effort and in little time. Congratulations, and good luck with your study! Kind Regards, Devon H. O'Dell From owner-freebsd-hackers@FreeBSD.ORG Tue Oct 19 16:18:27 2004 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DEB7E16A4CE; Tue, 19 Oct 2004 16:18:27 +0000 (GMT) Received: from r3p34.chello.upc.cz (r3p34.chello.upc.cz [213.220.207.34]) by mx1.FreeBSD.org (Postfix) with ESMTP id F1E2543D2D; Tue, 19 Oct 2004 16:18:26 +0000 (GMT) (envelope-from plusik@pohoda.cz) Received: from eddie.chello.cz (localhost [127.0.0.1]) by eddie.chello.cz (8.12.10/8.12.10) with ESMTP id i9JG3BSF001222; Tue, 19 Oct 2004 18:03:11 +0200 (CEST) (envelope-from plusik@pohoda.cz) Received: from localhost (plusik@localhost)i9JG3BZw001219; Tue, 19 Oct 2004 18:03:11 +0200 (CEST) (envelope-from plusik@pohoda.cz) X-Authentication-Warning: eddie.chello.cz: plusik owned process doing -bs Date: Tue, 19 Oct 2004 18:03:11 +0200 (CEST) From: Tomas Pluskal X-X-Sender: plusik@localhost To: "Devon H. O'Dell" In-Reply-To: <41751ADA.40107@sitetronics.com> Message-ID: <20041019174231.S958@localhost> References: <20041019133439.X604@localhost> <41751ADA.40107@sitetronics.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed cc: freebsd-security@freebsd.org cc: freebsd-hackers@freebsd.org Subject: Re: new intrusion detection system X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 19 Oct 2004 16:18:28 -0000 > > At a first glance of this email, I thought ``An IDS based upon SpamAssassin > ideology? Intrusions differ too much from spam for this to be accurate!'' > After reading your thesis, my ideas were changed. I agree with you that this approach for IDS cannot be as accurate as SpamAssassin is accurate with spam detection, because the intrusion detection problem is more complex and has many complications (I have also mentioned this in the thesis). But still this approach has its benefits. > This work is certainly very interesting, and I encourage you to continue its > development. Certainly one thing that would be desirable that I did not see > listed in the improvements section (and many other IDS systems, such as Bro) > would be the ability to carry out some action (instead of pure reporting) > based upon behavior; this would allow for IDS as well as IPS behavior. It is not listed in the improvements section, because it is already a part of the IDS - it has 6 configurable actions to invoke when the process score reaches defined level. It is also possible to add new actions as "submodules". > > I'm quite interested and impressed by the work you've done here. Do you have > any plans of setting this up as a collaborative project? Can I help you by > providing a place for you to do this? I have made this public right now, and looking at the responses, I am thinking about starting a project. Perhaps SourceForge would be a good place where to start. Looking for volunteers, of course :) Tomas From owner-freebsd-hackers@FreeBSD.ORG Tue Oct 19 21:55:03 2004 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 51AB716A4CE; Tue, 19 Oct 2004 21:55:03 +0000 (GMT) Received: from smtpq3.home.nl (smtpq3.home.nl [213.51.128.198]) by mx1.FreeBSD.org (Postfix) with ESMTP id B412243D45; Tue, 19 Oct 2004 21:55:02 +0000 (GMT) (envelope-from dodell@sitetronics.com) Received: from [213.51.128.134] (port=52420 helo=smtp3.home.nl) by smtpq3.home.nl with esmtp (Exim 4.30) id 1CK1wa-0001nI-FF; Tue, 19 Oct 2004 23:55:00 +0200 Received: from cc740438-a.deven1.ov.home.nl ([82.75.136.183]:4279) by smtp3.home.nl with esmtp (Exim 4.30) id 1CK1wZ-0006gI-LR; Tue, 19 Oct 2004 23:54:59 +0200 Message-ID: <41758D35.2070708@sitetronics.com> Date: Tue, 19 Oct 2004 23:55:01 +0200 From: "Devon H. O'Dell" User-Agent: Mozilla Thunderbird 0.8 (Windows/20040913) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Brian Barto References: <20041019133439.X604@localhost> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-AtHome-MailScanner-Information: Please contact support@home.nl for more information X-AtHome-MailScanner: Found to be clean cc: freebsd-hackers@freebsd.org cc: Tomas Pluskal cc: freebsd-security@freebsd.org Subject: Re: new intrusion detection system X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 19 Oct 2004 21:55:03 -0000 Brian Barto wrote: > Very interesting stuff. Certainly worth more investigation. > > Something occurred to me while I read your thesis. Though maybe it was > worth a mention. The TTL (time to live) could potentially cause the IDS > module to be easily beaten. An attack could begin and immediately go > into a sleep state with the intent to expire the TTL. Later resuming > with it's actions going unnoticed. > > I hope to see more on this. I think it is a very creative and useful idea. > > Thanks, > Brian This is certainly something that will need to be researched and tuned in practical environments. In many cases, it's not practical to wait for over a certain period of time to perform the combination of commands needed to exploit software due to network or file issues. But it is a very valid point. --Devon From owner-freebsd-hackers@FreeBSD.ORG Tue Oct 19 21:43:45 2004 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 12CD716A4CE; Tue, 19 Oct 2004 21:43:45 +0000 (GMT) Received: from sccrmhc11.comcast.net (sccrmhc11.comcast.net [204.127.202.55]) by mx1.FreeBSD.org (Postfix) with ESMTP id 80A6943D2D; Tue, 19 Oct 2004 21:43:44 +0000 (GMT) (envelope-from bartobri@comcast.net) Received: from [192.168.0.104] (c-24-11-10-106.client.comcast.net[24.11.10.106]) by comcast.net (sccrmhc11) with SMTP id <20041019214343011007dvp3e>; Tue, 19 Oct 2004 21:43:44 +0000 In-Reply-To: <20041019133439.X604@localhost> References: <20041019133439.X604@localhost> Mime-Version: 1.0 (Apple Message framework v619) Content-Type: text/plain; charset=US-ASCII; format=flowed Message-Id: Content-Transfer-Encoding: 7bit From: Brian Barto Date: Tue, 19 Oct 2004 17:43:43 -0400 To: Tomas Pluskal X-Mailer: Apple Mail (2.619) X-Mailman-Approved-At: Wed, 20 Oct 2004 12:24:40 +0000 cc: freebsd-hackers@freebsd.org cc: freebsd-security@freebsd.org Subject: Re: new intrusion detection system X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 19 Oct 2004 21:43:45 -0000 Very interesting stuff. Certainly worth more investigation. Something occurred to me while I read your thesis. Though maybe it was worth a mention. The TTL (time to live) could potentially cause the IDS module to be easily beaten. An attack could begin and immediately go into a sleep state with the intent to expire the TTL. Later resuming with it's actions going unnoticed. I hope to see more on this. I think it is a very creative and useful idea. Thanks, Brian On Oct 19, 2004, at 7:36 AM, Tomas Pluskal wrote: > > Hello to all, > > I have implemented a new type of intrusion detection system for my > Master thesis. I would like to announce this information, in case > anyone would be interested in this research. > > The IDS system is designed as a kernel module for FreeBSD 5.2. It is > inspired by the SpamAssassin program, which detects spam by applying a > set of tests to every email message and counting a sum of point score > generated by each test. My IDS system applies a set of tests to every > running process in the OS and counts its score generated by the tests. > Therefore, the purpose of the IDS is not to monitor the network > traffic, but rather to monitor the process activity. > > The current system status is a "working prototype" - it is not ready > for production usage, but it may serve as a good base for an > interesting research. > > If you are interested in this topic, please read the details here: > http://plusik.pohoda.cz/thesis/ > > Thanks, > > Tomas > _______________________________________________ > freebsd-security@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-security > To unsubscribe, send any mail to > "freebsd-security-unsubscribe@freebsd.org" > From owner-freebsd-hackers@FreeBSD.ORG Thu Oct 21 04:59:42 2004 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5D0B816A4CE for ; Thu, 21 Oct 2004 04:59:42 +0000 (GMT) Received: from cydem.org (S0106000103ce4c9c.ed.shawcable.net [68.149.254.167]) by mx1.FreeBSD.org (Postfix) with ESMTP id EF9D043D53 for ; Thu, 21 Oct 2004 04:59:41 +0000 (GMT) (envelope-from soralx@cydem.org) Received: from S01060020ed3972ba.ed.shawcable.net (S01060020ed3972ba.ed.shawcable.net [68.149.254.42]) by cydem.org (Postfix/FreeBSD) with ESMTP id CB72538A16 for ; Wed, 20 Oct 2004 22:59:41 -0600 (MDT) From: To: freebsd-hackers@freebsd.org Date: Wed, 20 Oct 2004 22:59:50 -0600 User-Agent: KMail/1.5.4 References: <200410132110.09915.soralx@cydem.org> In-Reply-To: <200410132110.09915.soralx@cydem.org> MIME-Version: 1.0 Content-Disposition: inline Message-Id: <200410171122.28021.soralx@cydem.org> Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Subject: [PATCH] Re: Linksys PCM200 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 21 Oct 2004 04:59:42 -0000 [got no answer on hardware@] I've tested this on 5.3-BETA7 - works OK, no more watchdog timeouts. So could someone review those patches and add them to the source tree? It's probably a good idea to update dc(4) and supported hw list also. /usr/src/sys/pci/if_dc.c udiff: --- ./if_dc.c Sat Jan 24 22:23:21 2004 +++ /fd0/if_dc.c Wed Oct 13 20:56:08 2004 @@ -217,6 +217,10 @@ "Microsoft MN-130 10/100" }, { DC_VENDORID_MICROSOFT, DC_DEVICEID_MSMN130_FAKE, "Microsoft MN-130 10/100" }, + { DC_VENDORID_LINKSYS, DC_DEVICEID_PCM200_AB08, + "Linksys PCM200 EtherFast 10/100 CardBus ethernet adapter, v.03 (ADMtek Centaur-C)" }, + { DC_VENDORID_LINKSYS, DC_DEVICEID_PCM200_AB09, + "Linksys PCM200 EtherFast 10/100 CardBus ethernet adapter, v.03 (ADMtek Centaur-C)" }, { 0, 0, NULL } }; @@ -1978,6 +1982,7 @@ case DC_DEVICEID_3CSOHOB: case DC_DEVICEID_MSMN120: case DC_DEVICEID_MSMN130_FAKE: /* XXX avoid collision with PNIC*/ + case DC_DEVICEID_PCM200_AB09: sc->dc_type = DC_TYPE_AN985; sc->dc_flags |= DC_64BIT_HASH; sc->dc_flags |= DC_TX_USE_TX_INTR; /usr/src/sys/pci/if_dcreg.h udiff: --- ./if_dcreg.h Fri Jan 9 14:13:56 2004 +++ /fd0/if_dcreg.h Wed Oct 13 20:44:50 2004 @@ -1002,6 +1002,18 @@ #define DC_DEVICEID_MSMN130 0x0002 #define DC_DEVICEID_MSMN130_FAKE 0xFFF2 +/* + * Linksys vendor ID + */ +#define DC_VENDORID_LINKSYS 0x1737 + +/* + * Linksys device IDs + */ +#define DC_DEVICEID_PCM200_AB08 0xab08 +#define DC_DEVICEID_PCM200_AB09 0xab09 + /* * PCI low memory base and low I/O base register, and * other PCI registers. Timestamp: 0x4172A6A5 [SorAlx] http://cydem.org.ua/ ridin' VN1500-B2 From owner-freebsd-hackers@FreeBSD.ORG Thu Oct 21 07:21:56 2004 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1FF9016A4CE for ; Thu, 21 Oct 2004 07:21:56 +0000 (GMT) Received: from www.hexe.com.pl (www.hexe.com.pl [212.160.230.130]) by mx1.FreeBSD.org (Postfix) with ESMTP id 24D8C43D4C for ; Thu, 21 Oct 2004 07:21:55 +0000 (GMT) (envelope-from clamav@www.hexe.com.pl) Received: from www.hexe.com.pl (smmsp@localhost [127.0.0.1]) i9L6pkSH015037; Thu, 21 Oct 2004 08:51:48 +0200 Received: (from clamav@localhost) by www.hexe.com.pl (8.12.3/8.12.3/Debian-6.6) id i9L6S2WC014832; Thu, 21 Oct 2004 08:28:02 +0200 Date: Thu, 21 Oct 2004 08:28:02 +0200 Message-Id: <200410210628.i9L6S2WC014832@www.hexe.com.pl> From: To: Auto-Submitted: auto-submitted (antivirus notify) X-Infected-Received-From: ajb43.neoplus.adsl.tpnet.pl [83.25.235.43] X-Virus-Scanned: clamd / ClamAV version 0.75-1, clamav-milter version 0.74a on www X-Virus-Status: Clean cc: postmaster@www.hexe.com.pl cc: ravms@www.hexe.com.pl Subject: Virus intercepted X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 21 Oct 2004 07:21:56 -0000 A message you sent to contained Worm.SomeFool.X and has not been delivered. From owner-freebsd-hackers@FreeBSD.ORG Thu Oct 21 11:39:17 2004 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 801D316A4CE for ; Thu, 21 Oct 2004 11:39:17 +0000 (GMT) Received: from straylight.ringlet.net (discworld.nanolink.com [217.75.135.134]) by mx1.FreeBSD.org (Postfix) with SMTP id 0089043D5A for ; Thu, 21 Oct 2004 11:39:14 +0000 (GMT) (envelope-from roam@ringlet.net) Received: (qmail 44945 invoked by uid 1000); 21 Oct 2004 11:37:10 -0000 Date: Thu, 21 Oct 2004 14:37:10 +0300 From: Peter Pentchev To: freebsd-hackers@FreeBSD.org Message-ID: <20041021113709.GB7732@straylight.m.ringlet.net> Mail-Followup-To: freebsd-hackers@FreeBSD.org Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="KFztAG8eRSV9hGtP" Content-Disposition: inline User-Agent: Mutt/1.5.6i Subject: [CFR] Specify the lock(1) timeout unit X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 21 Oct 2004 11:39:17 -0000 --KFztAG8eRSV9hGtP Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hi, Here's a little patch that teaches lock(1) about timeouts specified in seconds, hours, or days in addition to the minutes it currently assumes. I could commit this in a week if there are no objections. G'luck, Peter Index: src/usr.bin/lock/lock.1 =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D RCS file: /home/ncvs/src/usr.bin/lock/lock.1,v retrieving revision 1.11 diff -u -r1.11 lock.1 --- src/usr.bin/lock/lock.1 2 Jul 2004 22:22:27 -0000 1.11 +++ src/usr.bin/lock/lock.1 21 Oct 2004 10:39:13 -0000 @@ -42,6 +42,7 @@ .Nm .Op Fl npv .Op Fl t Ar timeout +.Op Fl u Ar unit .Sh DESCRIPTION The .Nm @@ -63,7 +64,22 @@ .It Fl t Ar timeout The time limit (default 15 minutes) is changed to .Ar timeout -minutes. +minutes, or units specified by the +.Fl u +option. +.It Fl u Ar unit +Specify the time measurement unit for the time limit. +The +.Ar unit +argument may be one of +.Sq s +for seconds, +.Sq m +for minutes (the default), +.Sq h +for hours, or +.Sq d +for days. .It Fl v Disable switching virtual terminals while this terminal is locked. This option is implemented in a way similar to the Index: src/usr.bin/lock/lock.c =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D RCS file: /home/ncvs/src/usr.bin/lock/lock.c,v retrieving revision 1.18 diff -u -r1.18 lock.c --- src/usr.bin/lock/lock.c 22 Jan 2004 04:24:15 -0000 1.18 +++ src/usr.bin/lock/lock.c 21 Oct 2004 11:07:36 -0000 @@ -85,6 +85,20 @@ long nexttime; /* keep the timeout time */ int no_timeout; /* lock terminal forever */ int vtyunlock; /* Unlock flag and code. */ +const char *timeout_str =3D "minute"; +int timeout_mul =3D 60; + +struct timeout_spec { + char spec; + int mul; + const char *str; +} timeout_spec[] =3D { + {'s', 1, "second"}, + {'m', 60, "minute"}, + {'h', 3600, "hour"}, + {'d', 86400, "day"}, + {'\0', 0, NULL}, +}; =20 /*ARGSUSED*/ int @@ -98,20 +112,31 @@ int ch, failures, sectimeout, usemine, vtylock; char *ap, *mypw, *ttynam, *tzn; char hostname[MAXHOSTNAMELEN], s[BUFSIZ], s1[BUFSIZ]; + struct timeout_spec *ts; =20 openlog("lock", LOG_ODELAY, LOG_AUTH); =20 sectimeout =3D TIMEOUT; + timeout_mul =3D 60; mypw =3D NULL; usemine =3D 0; no_timeout =3D 0; vtylock =3D 0; - while ((ch =3D getopt(argc, argv, "npt:v")) !=3D -1) + while ((ch =3D getopt(argc, argv, "npt:u:v")) !=3D -1) switch((char)ch) { case 't': if ((sectimeout =3D atoi(optarg)) <=3D 0) errx(1, "illegal timeout value"); break; + case 'u': + for (ts =3D timeout_spec; ts->spec !=3D '\0'; ts++) + if (ts->spec =3D=3D optarg[0]) + break; + if (ts->spec =3D=3D '\0') + errx(1, "illegal timeout unit specifier"); + timeout_mul =3D ts->mul; + timeout_str =3D ts->str; + break; case 'p': usemine =3D 1; if (!(pw =3D getpwuid(getuid()))) @@ -128,7 +153,7 @@ default: usage(); } - timeout.tv_sec =3D sectimeout * 60; + timeout.tv_sec =3D sectimeout * timeout_mul; =20 setuid(getuid()); /* discard privs */ =20 @@ -139,7 +164,7 @@ errx(1, "not a terminal?"); if (gettimeofday(&timval, (struct timezone *)NULL)) err(1, "gettimeofday"); - nexttime =3D timval.tv_sec + (sectimeout * 60); + nexttime =3D timval.tv_sec + (sectimeout * timeout_mul); timval_sec =3D timval.tv_sec; timp =3D localtime(&timval_sec); ap =3D asctime(timp); @@ -200,8 +225,8 @@ if (no_timeout) (void)printf(" no timeout."); else - (void)printf(" timeout in %d minute%s.", sectimeout, - sectimeout !=3D 1 ? "s" : ""); + (void)printf(" timeout in %d %s%s.", sectimeout, + timeout_str, sectimeout !=3D 1 ? "s" : ""); if (vtylock) (void)printf(" vty locked."); (void)printf("\ntime now is %.20s%s%s", ap, tzn, ap + 19); @@ -243,7 +268,7 @@ static void usage(void) { - (void)fprintf(stderr, "usage: lock [-npv] [-t timeout]\n"); + (void)fprintf(stderr, "usage: lock [-npv] [-t timeout] [-u unit]\n"); exit(1); } =20 --=20 Peter Pentchev roam@ringlet.net roam@cnsys.bg roam@FreeBSD.org PGP key: http://people.FreeBSD.org/~roam/roam.key.asc Key fingerprint FDBA FD79 C26F 3C51 C95E DF9E ED18 B68D 1619 4553 If I were you, who would be reading this sentence? --KFztAG8eRSV9hGtP Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQFBd59l7Ri2jRYZRVMRAtbsAKC2Vyv4b8rruBt4uRQW+eFuY+tI2QCZATdU 79nx74bZnL8qfU0+ai3maaI= =C7+u -----END PGP SIGNATURE----- --KFztAG8eRSV9hGtP-- From owner-freebsd-hackers@FreeBSD.ORG Wed Oct 20 16:12:57 2004 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CE27E16A4CE for ; Wed, 20 Oct 2004 16:12:57 +0000 (GMT) Received: from dastardly.newsbastards.org.72.27.172.IN-addr.ARPA.NOSPAM.dyndns.dk (80-219-160-253.dclient.hispeed.ch [80.219.160.253]) by mx1.FreeBSD.org (Postfix) with ESMTP id ED64043D49 for ; Wed, 20 Oct 2004 16:12:53 +0000 (GMT) (envelope-from bounce@NOSPAM.dyndns.dk) Received: from Mail.NOSPAM.DynDNS.dK (ipv6.NOSPAM.dyndns.dk [2002:50db:a0fd:0:220:afff:fed4:dbcb]) (8.11.6/8.11.6-SPAMMERS-DeLiGHt) with ESMTP id i9KGCmi05230 verified NO) for ; Wed, 20 Oct 2004 18:12:51 +0200 (CEST) (envelope-from bounce@NOSPAM.dyndns.dk) Received: (from beer@localhost) by Mail.NOSPAM.DynDNS.dK (8.11.6/FNORD) id i9KGClg05229; Wed, 20 Oct 2004 18:12:47 +0200 (CEST) (envelope-from bounce@NOSPAM.dyndns.dk) Date: Wed, 20 Oct 2004 18:12:47 +0200 (CEST) Message-Id: <200410201612.i9KGClg05229@Mail.NOSPAM.DynDNS.dK> X-Authentication-Warning: localhost.newsbastards.org.72.27.172.IN-addr.A: beer set sender to bounce@NOSPAM.dyndns.dk using -f X-Authentication-Warning: localhost.newsbastards.org.72.27.172.IN-addr.A: Processed from queue /tmp X-Authentication-Warning: localhost.newsbastards.org.72.27.172.IN-addr.A: Processed by beer with -C /etc/mail/sendmail.cf-LOCAL From: Barry Bouwsma To: freebsd-hackers@freebsd.org X-Mailman-Approved-At: Thu, 21 Oct 2004 12:20:41 +0000 Subject: USB OHCI problems... X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 20 Oct 2004 16:12:57 -0000 Apologies for this posting, as so far as I know it's a known issue that the USB OHCI code has some problems, or perhaps that there have been code commits in the last weeks so this is no longer a problem... Anyway, under FreeBSD-4 with kernel modules built 10.August from source that I believe is based on FreeBSD-5-current of that era, I'm seeing corruption of data read from umass devices attached to an OHCI controller card. Use of a UHCI controller card instead seems mostly free of problems. In comparison, I accessed the data with NetBSD-current of similar vintage, and in the files copied with the identical hardware, the data is intact. The point at which the corruption begins is at some multiple of 16384 bytes into the file. The corruption is not consistent, as it is less likely to occur when the machine is somewhat idle, and as the below shows, also occurs at different points into the same file. I haven't looked to see for how long this corruption is present (it's more than a few hundred bytes, at least) or how the file appears after this, or whether this corruption follows any particular pattern of the rest of the file. The below is `cmp' output under my FreeBSD, compared against the files previously downloaded with NetBSD (and verified that all the images are intact). /cdrom/dcim/100dscim/pict0681.jpg pict0681.jpg differ: char 524289, line 2284 /cdrom/dcim/100dscim/pict0683.jpg pict0683.jpg differ: char 507905, line 2116 /cdrom/dcim/100dscim/pict0684.jpg pict0684.jpg differ: char 1163265, line 3323 /cdrom/dcim/100dscim/pict0685.jpg pict0685.jpg differ: char 294913, line 1402 /cdrom/dcim/100dscim/pict0686.jpg pict0686.jpg differ: char 393217, line 1716 /cdrom/dcim/100dscim/pict0687.jpg pict0687.jpg differ: char 753665, line 2606 /cdrom/dcim/100dscim/pict0686.jpg pict0686.jpg differ: char 983041, line 3648 This is just a sample -- note that the last line is the same file that I had previously `cmp'ed two lines above. In fairness, the files copied from NetBSD were done with the machine mostly idle, so I don't know if NetBSD suffers the same if I were pounding the machine. If this issue hasn't been handled, perhaps the fact that NetBSD doesn't seem to have problems might give someone some ideas as to where the problem might lie. As usual, apologies for the untimeliness of this, as well as my lack of detailed testing with fresh -current or with code fresher than two months ago. thanks barry bouwsma From owner-freebsd-hackers@FreeBSD.ORG Thu Oct 21 14:32:11 2004 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 446B816A4CE for ; Thu, 21 Oct 2004 14:32:11 +0000 (GMT) Received: from zaphod.nitro.dk (port324.ds1-khk.adsl.cybercity.dk [212.242.113.79]) by mx1.FreeBSD.org (Postfix) with ESMTP id B486643D2D for ; Thu, 21 Oct 2004 14:32:10 +0000 (GMT) (envelope-from simon@zaphod.nitro.dk) Received: by zaphod.nitro.dk (Postfix, from userid 3000) id F3F1911A79; Thu, 21 Oct 2004 16:32:08 +0200 (CEST) Date: Thu, 21 Oct 2004 16:32:08 +0200 From: "Simon L. Nielsen" To: freebsd-hackers@FreeBSD.org Message-ID: <20041021143208.GA769@zaphod.nitro.dk> References: <20041021113709.GB7732@straylight.m.ringlet.net> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="opJtzjQTFsWo+cga" Content-Disposition: inline In-Reply-To: <20041021113709.GB7732@straylight.m.ringlet.net> User-Agent: Mutt/1.5.6i Subject: Re: [CFR] Specify the lock(1) timeout unit X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 21 Oct 2004 14:32:11 -0000 --opJtzjQTFsWo+cga Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On 2004.10.21 14:37:10 +0300, Peter Pentchev wrote: > Here's a little patch that teaches lock(1) about timeouts specified in > seconds, hours, or days in addition to the minutes it currently assumes. > I could commit this in a week if there are no objections. Wouldn't it be more natural to just append the time-unit type to the argument given to -t, e.g. "-t 10s" or "-t 10h". That just seem like the more intuitive way to handle it to me... Note: this is a suggestion, not an objection to the original patch. --=20 Simon L. Nielsen FreeBSD Documentation Team --opJtzjQTFsWo+cga Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQFBd8hoh9pcDSc1mlERAtkFAKCAbSdC+18o+yBlvvB1d1Yo7+HxtwCgw2O3 1PRCOkEi6/HYZ0v0l3B1DU0= =yQAS -----END PGP SIGNATURE----- --opJtzjQTFsWo+cga-- From owner-freebsd-hackers@FreeBSD.ORG Thu Oct 21 17:06:40 2004 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7B1FF16A4CE; Thu, 21 Oct 2004 17:06:40 +0000 (GMT) Received: from tigra.ip.net.ua (tigra.ip.net.ua [82.193.96.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id C41C543D1D; Thu, 21 Oct 2004 17:06:39 +0000 (GMT) (envelope-from ru@ip.net.ua) Received: from localhost (rocky.ip.net.ua [82.193.96.2]) by tigra.ip.net.ua (8.12.11/8.12.11) with ESMTP id i9LH6c98092062; Thu, 21 Oct 2004 20:06:38 +0300 (EEST) (envelope-from ru@ip.net.ua) Received: from tigra.ip.net.ua ([82.193.96.10]) by localhost (rocky.ipnet [82.193.96.2]) (amavisd-new, port 10024) with LMTP id 93321-11; Thu, 21 Oct 2004 20:06:38 +0300 (EEST) Received: from heffalump.ip.net.ua (heffalump.ip.net.ua [82.193.96.213]) by tigra.ip.net.ua (8.12.11/8.12.11) with ESMTP id i9LH6XVV092058; Thu, 21 Oct 2004 20:06:36 +0300 (EEST) (envelope-from ru@ip.net.ua) Received: (from ru@localhost) by heffalump.ip.net.ua (8.13.1/8.13.1) id i9LH6BiP049966; Thu, 21 Oct 2004 20:06:11 +0300 (EEST) (envelope-from ru) Date: Thu, 21 Oct 2004 20:06:11 +0300 From: Ruslan Ermilov To: "Simon L. Nielsen" Message-ID: <20041021170611.GB49881@ip.net.ua> References: <20041021113709.GB7732@straylight.m.ringlet.net> <20041021143208.GA769@zaphod.nitro.dk> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="H+4ONPRPur6+Ovig" Content-Disposition: inline In-Reply-To: <20041021143208.GA769@zaphod.nitro.dk> User-Agent: Mutt/1.5.6i X-Virus-Scanned: by amavisd-new at ip.net.ua cc: freebsd-hackers@FreeBSD.org Subject: Re: [CFR] Specify the lock(1) timeout unit X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 21 Oct 2004 17:06:40 -0000 --H+4ONPRPur6+Ovig Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Oct 21, 2004 at 04:32:08PM +0200, Simon L. Nielsen wrote: > On 2004.10.21 14:37:10 +0300, Peter Pentchev wrote: >=20 > > Here's a little patch that teaches lock(1) about timeouts specified in > > seconds, hours, or days in addition to the minutes it currently assumes. > > I could commit this in a week if there are no objections. >=20 > Wouldn't it be more natural to just append the time-unit type to the > argument given to -t, e.g. "-t 10s" or "-t 10h". That just seem like > the more intuitive way to handle it to me... >=20 > Note: this is a suggestion, not an objection to the original patch. >=20 Yes, please. :-) Cheers, --=20 Ruslan Ermilov ru@FreeBSD.org FreeBSD committer --H+4ONPRPur6+Ovig Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQFBd+yDqRfpzJluFF4RAkP6AJ9pdXFbgpOTi0G10kzRsoJbx7svsgCdH284 dav+wtfUHub0L3FqXDXP66o= =5Zwn -----END PGP SIGNATURE----- --H+4ONPRPur6+Ovig-- From owner-freebsd-hackers@FreeBSD.ORG Thu Oct 21 17:13:50 2004 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8276016A4CE for ; Thu, 21 Oct 2004 17:13:50 +0000 (GMT) Received: from zaphod.nitro.dk (port324.ds1-khk.adsl.cybercity.dk [212.242.113.79]) by mx1.FreeBSD.org (Postfix) with ESMTP id D26EA43D31 for ; Thu, 21 Oct 2004 17:13:49 +0000 (GMT) (envelope-from simon@zaphod.nitro.dk) Received: by zaphod.nitro.dk (Postfix, from userid 3000) id 3BE7A11A79; Thu, 21 Oct 2004 19:13:48 +0200 (CEST) Date: Thu, 21 Oct 2004 19:13:48 +0200 From: "Simon L. Nielsen" To: soralx@cydem.org Message-ID: <20041021171347.GF769@zaphod.nitro.dk> References: <200410132110.09915.soralx@cydem.org> <200410171122.28021.soralx@cydem.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="oPmsXEqKQNHCSXW7" Content-Disposition: inline In-Reply-To: <200410171122.28021.soralx@cydem.org> User-Agent: Mutt/1.5.6i cc: freebsd-hackers@freebsd.org Subject: Re: [PATCH] Re: Linksys PCM200 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 21 Oct 2004 17:13:50 -0000 --oPmsXEqKQNHCSXW7 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On 2004.10.20 22:59:50 -0600, soralx@cydem.org wrote: >=20 > [got no answer on hardware@] >=20 > I've tested this on 5.3-BETA7 - works OK, no more watchdog timeouts. > So could someone review those patches and add them to the source tree? > It's probably a good idea to update dc(4) and supported hw list also. >=20 > /usr/src/sys/pci/if_dc.c udiff: [...] Unless a src committer picks this up within the next couple of days I would suggest filing a PR with the patch so it does not get lost. --=20 Simon L. Nielsen FreeBSD Documentation Team --oPmsXEqKQNHCSXW7 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQFBd+5Lh9pcDSc1mlERAvADAKDJOfMrBErD1+aqluw8MlzLSRS/tQCfXWkc tpLg9IwBqTdZn/O9yWpUp9A= =7A6f -----END PGP SIGNATURE----- --oPmsXEqKQNHCSXW7-- From owner-freebsd-hackers@FreeBSD.ORG Thu Oct 21 17:35:03 2004 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1660A16A4CE for ; Thu, 21 Oct 2004 17:35:03 +0000 (GMT) Received: from odin.ac.hmc.edu (Odin.AC.HMC.Edu [134.173.32.75]) by mx1.FreeBSD.org (Postfix) with ESMTP id EADFB43D4C for ; Thu, 21 Oct 2004 17:35:02 +0000 (GMT) (envelope-from brdavis@odin.ac.hmc.edu) Received: from odin.ac.hmc.edu (localhost.localdomain [127.0.0.1]) by odin.ac.hmc.edu (8.13.0/8.13.0) with ESMTP id i9LHYuEd021672; Thu, 21 Oct 2004 10:34:56 -0700 Received: (from brdavis@localhost) by odin.ac.hmc.edu (8.13.0/8.13.0/Submit) id i9LHYusw021671; Thu, 21 Oct 2004 10:34:56 -0700 Date: Thu, 21 Oct 2004 10:34:56 -0700 From: Brooks Davis To: soralx@cydem.org Message-ID: <20041021173456.GA20517@odin.ac.hmc.edu> References: <200410132110.09915.soralx@cydem.org> <200410171122.28021.soralx@cydem.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="UlVJffcvxoiEqYs2" Content-Disposition: inline In-Reply-To: <200410171122.28021.soralx@cydem.org> User-Agent: Mutt/1.4.1i X-Virus-Scanned: by amavisd-new X-Spam-Status: No, hits=0.0 required=8.0 tests=none autolearn=no version=2.63 X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on odin.ac.hmc.edu cc: freebsd-hackers@freebsd.org Subject: Re: [PATCH] Re: Linksys PCM200 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 21 Oct 2004 17:35:03 -0000 --UlVJffcvxoiEqYs2 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Oct 20, 2004 at 10:59:50PM -0600, soralx@cydem.org wrote: >=20 > [got no answer on hardware@] >=20 > I've tested this on 5.3-BETA7 - works OK, no more watchdog timeouts. > So could someone review those patches and add them to the source tree? > It's probably a good idea to update dc(4) and supported hw list also. I'm looking at this, though I have no hardware to test with. This patch suffers from cut-n-paste dammage and can not be applied directly. Please be more careful with this sort of thing in the future. > @@ -1978,6 +1982,7 @@ > case DC_DEVICEID_3CSOHOB: > case DC_DEVICEID_MSMN120: > case DC_DEVICEID_MSMN130_FAKE: /* XXX avoid collision with PNIC*/ > + case DC_DEVICEID_PCM200_AB09: > sc->dc_type =3D DC_TYPE_AN985; > sc->dc_flags |=3D DC_64BIT_HASH; > sc->dc_flags |=3D DC_TX_USE_TX_INTR; Should there be an DC_DEVICEID_PCM200_AB08 here? It certaintly looks like it won't work otherwise. Thanks for you submission. -- Brooks --=20 Any statement of the form "X is the one, true Y" is FALSE. PGP fingerprint 655D 519C 26A7 82E7 2529 9BF0 5D8E 8BE9 F238 1AD4 --UlVJffcvxoiEqYs2 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQFBd/M/XY6L6fI4GtQRAllRAJ4vaQbzYBV38XXBSyqMqi3GBk6+/QCgsE2+ q/A0lE42UhbYZ++s8R5oWEw= =cbjx -----END PGP SIGNATURE----- --UlVJffcvxoiEqYs2-- From owner-freebsd-hackers@FreeBSD.ORG Thu Oct 21 17:43:46 2004 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3BDBD16A4CE for ; Thu, 21 Oct 2004 17:43:46 +0000 (GMT) Received: from odin.ac.hmc.edu (Odin.AC.HMC.Edu [134.173.32.75]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1CFC543D1D for ; Thu, 21 Oct 2004 17:43:46 +0000 (GMT) (envelope-from brdavis@odin.ac.hmc.edu) Received: from odin.ac.hmc.edu (localhost.localdomain [127.0.0.1]) by odin.ac.hmc.edu (8.13.0/8.13.0) with ESMTP id i9LHhiG5023415; Thu, 21 Oct 2004 10:43:44 -0700 Received: (from brdavis@localhost) by odin.ac.hmc.edu (8.13.0/8.13.0/Submit) id i9LHhi5w023414; Thu, 21 Oct 2004 10:43:44 -0700 Date: Thu, 21 Oct 2004 10:43:44 -0700 From: Brooks Davis To: Brooks Davis Message-ID: <20041021174344.GB20517@odin.ac.hmc.edu> References: <200410132110.09915.soralx@cydem.org> <200410171122.28021.soralx@cydem.org> <20041021173456.GA20517@odin.ac.hmc.edu> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="KFztAG8eRSV9hGtP" Content-Disposition: inline In-Reply-To: <20041021173456.GA20517@odin.ac.hmc.edu> User-Agent: Mutt/1.4.1i X-Virus-Scanned: by amavisd-new X-Spam-Status: No, hits=0.3 required=8.0 tests=UPPERCASE_25_50 autolearn=no version=2.63 X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on odin.ac.hmc.edu cc: freebsd-hackers@freebsd.org Subject: Re: [PATCH] Re: Linksys PCM200 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 21 Oct 2004 17:43:46 -0000 --KFztAG8eRSV9hGtP Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Oct 21, 2004 at 10:34:56AM -0700, Brooks Davis wrote: > On Wed, Oct 20, 2004 at 10:59:50PM -0600, soralx@cydem.org wrote: > > @@ -1978,6 +1982,7 @@ > > case DC_DEVICEID_3CSOHOB: > > case DC_DEVICEID_MSMN120: > > case DC_DEVICEID_MSMN130_FAKE: /* XXX avoid collision with PNIC= */ > > + case DC_DEVICEID_PCM200_AB09: > > sc->dc_type =3D DC_TYPE_AN985; > > sc->dc_flags |=3D DC_64BIT_HASH; > > sc->dc_flags |=3D DC_TX_USE_TX_INTR; >=20 > Should there be an DC_DEVICEID_PCM200_AB08 here? It certaintly looks > like it won't work otherwise. Eww, I see why this works. I'll see if I can't at least document this bit. -- Brooks --=20 Any statement of the form "X is the one, true Y" is FALSE. PGP fingerprint 655D 519C 26A7 82E7 2529 9BF0 5D8E 8BE9 F238 1AD4 --KFztAG8eRSV9hGtP Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQFBd/VPXY6L6fI4GtQRAim7AJ9gFpAYIS8pqmry12SS+7M8L+NskQCffYTr LWatvLo/52uzz1F4+Hm8MBQ= =z1Ii -----END PGP SIGNATURE----- --KFztAG8eRSV9hGtP-- From owner-freebsd-hackers@FreeBSD.ORG Thu Oct 21 20:38:27 2004 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6A6DF16A4CE for ; Thu, 21 Oct 2004 20:38:27 +0000 (GMT) Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id ECCD743D58 for ; Thu, 21 Oct 2004 20:38:26 +0000 (GMT) (envelope-from robert@fledge.watson.org) Received: from fledge.watson.org (localhost [127.0.0.1]) by fledge.watson.org (8.13.1/8.13.1) with ESMTP id i9LKcBLk032107; Thu, 21 Oct 2004 16:38:11 -0400 (EDT) (envelope-from robert@fledge.watson.org) Received: from localhost (robert@localhost)i9LKcAM8032104; Thu, 21 Oct 2004 16:38:11 -0400 (EDT) (envelope-from robert@fledge.watson.org) Date: Thu, 21 Oct 2004 16:38:10 -0400 (EDT) From: Robert Watson X-Sender: robert@fledge.watson.org To: Peter Pentchev In-Reply-To: <20041021113709.GB7732@straylight.m.ringlet.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-hackers@FreeBSD.org Subject: Re: [CFR] Specify the lock(1) timeout unit X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 21 Oct 2004 20:38:27 -0000 On Thu, 21 Oct 2004, Peter Pentchev wrote: > Here's a little patch that teaches lock(1) about timeouts specified in > seconds, hours, or days in addition to the minutes it currently assumes. > I could commit this in a week if there are no objections. I think the normal convention here (see also shutdown(8), etc) is to have the unit be specified as part of the time specification rather than as a separate argument. I.e., lock -t 5m rather than lock -t 5 -u m. If we don't already have it, maybe we need humanize and dehumanize functions for time as well as disk storage? Robert N M Watson FreeBSD Core Team, TrustedBSD Projects robert@fledge.watson.org Principal Research Scientist, McAfee Research > > G'luck, > Peter > > Index: src/usr.bin/lock/lock.1 > =================================================================== > RCS file: /home/ncvs/src/usr.bin/lock/lock.1,v > retrieving revision 1.11 > diff -u -r1.11 lock.1 > --- src/usr.bin/lock/lock.1 2 Jul 2004 22:22:27 -0000 1.11 > +++ src/usr.bin/lock/lock.1 21 Oct 2004 10:39:13 -0000 > @@ -42,6 +42,7 @@ > .Nm > .Op Fl npv > .Op Fl t Ar timeout > +.Op Fl u Ar unit > .Sh DESCRIPTION > The > .Nm > @@ -63,7 +64,22 @@ > .It Fl t Ar timeout > The time limit (default 15 minutes) is changed to > .Ar timeout > -minutes. > +minutes, or units specified by the > +.Fl u > +option. > +.It Fl u Ar unit > +Specify the time measurement unit for the time limit. > +The > +.Ar unit > +argument may be one of > +.Sq s > +for seconds, > +.Sq m > +for minutes (the default), > +.Sq h > +for hours, or > +.Sq d > +for days. > .It Fl v > Disable switching virtual terminals while this terminal is locked. > This option is implemented in a way similar to the > Index: src/usr.bin/lock/lock.c > =================================================================== > RCS file: /home/ncvs/src/usr.bin/lock/lock.c,v > retrieving revision 1.18 > diff -u -r1.18 lock.c > --- src/usr.bin/lock/lock.c 22 Jan 2004 04:24:15 -0000 1.18 > +++ src/usr.bin/lock/lock.c 21 Oct 2004 11:07:36 -0000 > @@ -85,6 +85,20 @@ > long nexttime; /* keep the timeout time */ > int no_timeout; /* lock terminal forever */ > int vtyunlock; /* Unlock flag and code. */ > +const char *timeout_str = "minute"; > +int timeout_mul = 60; > + > +struct timeout_spec { > + char spec; > + int mul; > + const char *str; > +} timeout_spec[] = { > + {'s', 1, "second"}, > + {'m', 60, "minute"}, > + {'h', 3600, "hour"}, > + {'d', 86400, "day"}, > + {'\0', 0, NULL}, > +}; > > /*ARGSUSED*/ > int > @@ -98,20 +112,31 @@ > int ch, failures, sectimeout, usemine, vtylock; > char *ap, *mypw, *ttynam, *tzn; > char hostname[MAXHOSTNAMELEN], s[BUFSIZ], s1[BUFSIZ]; > + struct timeout_spec *ts; > > openlog("lock", LOG_ODELAY, LOG_AUTH); > > sectimeout = TIMEOUT; > + timeout_mul = 60; > mypw = NULL; > usemine = 0; > no_timeout = 0; > vtylock = 0; > - while ((ch = getopt(argc, argv, "npt:v")) != -1) > + while ((ch = getopt(argc, argv, "npt:u:v")) != -1) > switch((char)ch) { > case 't': > if ((sectimeout = atoi(optarg)) <= 0) > errx(1, "illegal timeout value"); > break; > + case 'u': > + for (ts = timeout_spec; ts->spec != '\0'; ts++) > + if (ts->spec == optarg[0]) > + break; > + if (ts->spec == '\0') > + errx(1, "illegal timeout unit specifier"); > + timeout_mul = ts->mul; > + timeout_str = ts->str; > + break; > case 'p': > usemine = 1; > if (!(pw = getpwuid(getuid()))) > @@ -128,7 +153,7 @@ > default: > usage(); > } > - timeout.tv_sec = sectimeout * 60; > + timeout.tv_sec = sectimeout * timeout_mul; > > setuid(getuid()); /* discard privs */ > > @@ -139,7 +164,7 @@ > errx(1, "not a terminal?"); > if (gettimeofday(&timval, (struct timezone *)NULL)) > err(1, "gettimeofday"); > - nexttime = timval.tv_sec + (sectimeout * 60); > + nexttime = timval.tv_sec + (sectimeout * timeout_mul); > timval_sec = timval.tv_sec; > timp = localtime(&timval_sec); > ap = asctime(timp); > @@ -200,8 +225,8 @@ > if (no_timeout) > (void)printf(" no timeout."); > else > - (void)printf(" timeout in %d minute%s.", sectimeout, > - sectimeout != 1 ? "s" : ""); > + (void)printf(" timeout in %d %s%s.", sectimeout, > + timeout_str, sectimeout != 1 ? "s" : ""); > if (vtylock) > (void)printf(" vty locked."); > (void)printf("\ntime now is %.20s%s%s", ap, tzn, ap + 19); > @@ -243,7 +268,7 @@ > static void > usage(void) > { > - (void)fprintf(stderr, "usage: lock [-npv] [-t timeout]\n"); > + (void)fprintf(stderr, "usage: lock [-npv] [-t timeout] [-u unit]\n"); > exit(1); > } > > > -- > Peter Pentchev roam@ringlet.net roam@cnsys.bg roam@FreeBSD.org > PGP key: http://people.FreeBSD.org/~roam/roam.key.asc > Key fingerprint FDBA FD79 C26F 3C51 C95E DF9E ED18 B68D 1619 4553 > If I were you, who would be reading this sentence? > From owner-freebsd-hackers@FreeBSD.ORG Thu Oct 21 22:35:25 2004 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DC6DB16A4CE for ; Thu, 21 Oct 2004 22:35:24 +0000 (GMT) Received: from odin.ac.hmc.edu (Odin.AC.HMC.Edu [134.173.32.75]) by mx1.FreeBSD.org (Postfix) with ESMTP id B797643D2F for ; Thu, 21 Oct 2004 22:35:24 +0000 (GMT) (envelope-from brdavis@odin.ac.hmc.edu) Received: from odin.ac.hmc.edu (localhost.localdomain [127.0.0.1]) by odin.ac.hmc.edu (8.13.0/8.13.0) with ESMTP id i9LMZPXn008536; Thu, 21 Oct 2004 15:35:25 -0700 Received: (from brdavis@localhost) by odin.ac.hmc.edu (8.13.0/8.13.0/Submit) id i9LMZPKL008535; Thu, 21 Oct 2004 15:35:25 -0700 Date: Thu, 21 Oct 2004 15:35:25 -0700 From: Brooks Davis To: Brooks Davis Message-ID: <20041021223525.GB4730@odin.ac.hmc.edu> References: <200410132110.09915.soralx@cydem.org> <200410171122.28021.soralx@cydem.org> <20041021173456.GA20517@odin.ac.hmc.edu> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="A6N2fC+uXW/VQSAv" Content-Disposition: inline In-Reply-To: <20041021173456.GA20517@odin.ac.hmc.edu> User-Agent: Mutt/1.4.1i X-Virus-Scanned: by amavisd-new X-Spam-Status: No, hits=0.3 required=8.0 tests=UPPERCASE_25_50 autolearn=no version=2.63 X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on odin.ac.hmc.edu cc: freebsd-hackers@freebsd.org Subject: Re: [PATCH] Re: Linksys PCM200 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 21 Oct 2004 22:35:25 -0000 --A6N2fC+uXW/VQSAv Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Oct 21, 2004 at 10:34:56AM -0700, Brooks Davis wrote: > On Wed, Oct 20, 2004 at 10:59:50PM -0600, soralx@cydem.org wrote: > >=20 > > [got no answer on hardware@] > >=20 > > I've tested this on 5.3-BETA7 - works OK, no more watchdog timeouts. > > So could someone review those patches and add them to the source tree? > > It's probably a good idea to update dc(4) and supported hw list also. >=20 > I'm looking at this, though I have no hardware to test with. Could some people with dc(4) devices please test the following patch? It compiles for me and is trivial, but a quick test is probalby in order before I commit it. This differs from soralx's patch in that it adds comments on the 0xab08 collisions and shortens the description string to something that will fit in one line on the console. Thanks, Brooks Index: if_dc.c =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D RCS file: /home/ncvs/src/sys/pci/if_dc.c,v retrieving revision 1.152 diff -u -p -r1.152 if_dc.c --- if_dc.c 1 Oct 2004 15:23:31 -0000 1.152 +++ if_dc.c 21 Oct 2004 22:32:39 -0000 @@ -218,6 +218,10 @@ static struct dc_type dc_devs[] =3D { "Microsoft MN-130 10/100" }, { DC_VENDORID_MICROSOFT, DC_DEVICEID_MSMN130_FAKE, "Microsoft MN-130 10/100" }, + { DC_VENDORID_LINKSYS, DC_DEVICEID_PCM200_AB08, + "Linksys PCM200 EtherFast CardBus 10/100" }, + { DC_VENDORID_LINKSYS, DC_DEVICEID_PCM200_AB09, + "Linksys PCM200 EtherFast CardBus 10/100" }, { 0, 0, NULL } }; =20 @@ -1917,10 +1921,16 @@ dc_attach(device_t dev) case DC_DEVICEID_FA511: case DC_DEVICEID_FE2500: case DC_DEVICEID_EN2242: - case DC_DEVICEID_HAWKING_PN672TX: + case DC_DEVICEID_HAWKING_PN672TX:=09 +#if 0 /* DC_DEVICEID_HAWKING_PN672TX has the same ID as the following */ + case DC_DEVICEID_FE2500MX: + case DC_DEVICEID_FNW3602T: + case DC_DEVICEID_PCM200_AB08: +#endif case DC_DEVICEID_3CSOHOB: case DC_DEVICEID_MSMN120: case DC_DEVICEID_MSMN130_FAKE: /* XXX avoid collision with PNIC*/ + case DC_DEVICEID_PCM200_AB09: sc->dc_type =3D DC_TYPE_AN985; sc->dc_flags |=3D DC_64BIT_HASH; sc->dc_flags |=3D DC_TX_USE_TX_INTR; Index: if_dcreg.h =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D RCS file: /home/ncvs/src/sys/pci/if_dcreg.h,v retrieving revision 1.42 diff -u -p -r1.42 if_dcreg.h --- if_dcreg.h 29 Jun 2004 20:38:44 -0000 1.42 +++ if_dcreg.h 21 Oct 2004 22:32:40 -0000 @@ -998,6 +998,17 @@ struct dc_softc { #define DC_DEVICEID_MSMN130_FAKE 0xFFF2 =20 /* + * Linksys vendor ID + */ +#define DC_VENDORID_LINKSYS 0x1737 + +/* + * Linksys device IDs + */ +#define DC_DEVICEID_PCM200_AB08 0xab08 +#define DC_DEVICEID_PCM200_AB09 0xab09 + +/* * PCI low memory base and low I/O base register, and * other PCI registers. */ --=20 Any statement of the form "X is the one, true Y" is FALSE. PGP fingerprint 655D 519C 26A7 82E7 2529 9BF0 5D8E 8BE9 F238 1AD4 --A6N2fC+uXW/VQSAv Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQFBeDmsXY6L6fI4GtQRAq8CAKDSAzixBQOrWoBlWSvnyU7vRMYuswCdGWLO SDTQvy/R41NdK3iNVAJASOw= =IGaH -----END PGP SIGNATURE----- --A6N2fC+uXW/VQSAv-- From owner-freebsd-hackers@FreeBSD.ORG Thu Oct 21 23:33:05 2004 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 73A2E16A4CE for ; Thu, 21 Oct 2004 23:33:05 +0000 (GMT) Received: from straylight.ringlet.net (discworld.nanolink.com [217.75.135.134]) by mx1.FreeBSD.org (Postfix) with SMTP id 6CF8D43D5D for ; Thu, 21 Oct 2004 23:33:00 +0000 (GMT) (envelope-from roam@ringlet.net) Received: (qmail 19837 invoked by uid 1000); 21 Oct 2004 23:33:02 -0000 Date: Fri, 22 Oct 2004 02:33:02 +0300 From: Peter Pentchev To: Robert Watson Message-ID: <20041021233302.GE7732@straylight.m.ringlet.net> Mail-Followup-To: Robert Watson , freebsd-hackers@FreeBSD.org References: <20041021113709.GB7732@straylight.m.ringlet.net> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="wTWi5aaYRw9ix9vO" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.6i cc: freebsd-hackers@FreeBSD.org Subject: Re: [CFR] Specify the lock(1) timeout unit X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 21 Oct 2004 23:33:05 -0000 --wTWi5aaYRw9ix9vO Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Oct 21, 2004 at 04:38:10PM -0400, Robert Watson wrote: > On Thu, 21 Oct 2004, Peter Pentchev wrote: >=20 > > Here's a little patch that teaches lock(1) about timeouts specified in > > seconds, hours, or days in addition to the minutes it currently assumes= =2E=20 > > I could commit this in a week if there are no objections.=20 >=20 > I think the normal convention here (see also shutdown(8), etc) is to have > the unit be specified as part of the time specification rather than as a > separate argument. I.e., lock -t 5m rather than lock -t 5 -u m. If we > don't already have it, maybe we need humanize and dehumanize functions for > time as well as disk storage? [randomly picking this message to reply to, since the others voiced the same concern and suggestion] Yep, on second thought it only seems natural to append the unit to the time specification; guess I wasn't thinking straight earlier today when I whipped this up in a hurry... Thanks everyone for pointing out the blindingly obvious - in this case, it *was* needed! :) Attached is an almost trivial patch that implements this, parsing things like '10s', '2m', '15h', or '2d' just as the previous version did - seconds, minutes, hours, days. As to factoring out the time specification parsing, it may not be just as easy as with disk storage units. The main problem here is that the utilites that parse time specifiers do so for a variety of different reasons, and then use the result in different ways. The secondary problem, maybe even more severe, is that the different utilities parse very different time formats, e.g. date(1) pretty much only understands +/-num[ymwdHMS], shutdown(8) takes either +minutes or a full or partial [[[yy]mm]dd]hhmmss specification, and find(1) and cvs(1) use the GNU getdate.y thing which is... well, let me say 'hairy' lest I use a stronger word. (As a side note, wow, I never knew that find(1) could do 'last year', 'a fortnight ago', or '22:00 IDLW'; makes sense, though, since they use the same code.) Sooo.. if we should create a unified time parsing function, what should it parse - an interval, an absolute time, or what? That is, what should it *return* - an interval in seconds, or the absolute time (time_t or struct tm) that the input specifies either directly or as an offset from the current time, both, neither, or the air velocity of an unladen swallow? How should it deal with nonexistent times - return an error, try to round them up, try to round them down, or silently convert them to the Antartica/South_Pole zone and snicker behind the curtain? How should it deal with month specifications? (gee, I hope no one tries to use a month unit as a lock(1) timeout, but you never know with some people) Anyway, here's the lock(1) patch that lets it handle 's', 'm', 'h', or 'd' appended to the timeout value. G'luck, Peter Index: src/usr.bin/lock/lock.1 =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D RCS file: /home/ncvs/src/usr.bin/lock/lock.1,v retrieving revision 1.11 diff -u -r1.11 lock.1 --- src/usr.bin/lock/lock.1 2 Jul 2004 22:22:27 -0000 1.11 +++ src/usr.bin/lock/lock.1 21 Oct 2004 23:05:25 -0000 @@ -64,6 +64,21 @@ The time limit (default 15 minutes) is changed to .Ar timeout minutes. +The timeout value may optionally be followed by a time unit specifier, +one of=20 +.Sq s +for seconds, +.Sq m +for minutes (the default), +.Sq h +for hours, or +.Sq d +for days. +Thus, +.Sq -t 2 +would specify a timeout of two minutes, while +.Sq -t 10s +would specify a timeout of ten seconds. .It Fl v Disable switching virtual terminals while this terminal is locked. This option is implemented in a way similar to the Index: src/usr.bin/lock/lock.c =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D RCS file: /home/ncvs/src/usr.bin/lock/lock.c,v retrieving revision 1.18 diff -u -r1.18 lock.c --- src/usr.bin/lock/lock.c 22 Jan 2004 04:24:15 -0000 1.18 +++ src/usr.bin/lock/lock.c 21 Oct 2004 23:06:59 -0000 @@ -85,6 +85,20 @@ long nexttime; /* keep the timeout time */ int no_timeout; /* lock terminal forever */ int vtyunlock; /* Unlock flag and code. */ +const char *timeout_str =3D "minute"; +int timeout_mul =3D 60; + +struct timeout_spec { + char spec; + int mul; + const char *str; +} timeout_spec[] =3D { + {'s', 1, "second"}, + {'m', 60, "minute"}, + {'h', 3600, "hour"}, + {'d', 86400, "day"}, + {'\0', 0, NULL}, +}; =20 /*ARGSUSED*/ int @@ -96,8 +110,9 @@ struct itimerval ntimer, otimer; struct tm *timp; int ch, failures, sectimeout, usemine, vtylock; - char *ap, *mypw, *ttynam, *tzn; + char *ap, *mypw, *ttynam, *tzn, *endarg; char hostname[MAXHOSTNAMELEN], s[BUFSIZ], s1[BUFSIZ]; + struct timeout_spec *ts; =20 openlog("lock", LOG_ODELAY, LOG_AUTH); =20 @@ -109,8 +124,19 @@ while ((ch =3D getopt(argc, argv, "npt:v")) !=3D -1) switch((char)ch) { case 't': - if ((sectimeout =3D atoi(optarg)) <=3D 0) + if ((sectimeout =3D strtol(optarg, &endarg, 10)) <=3D 0) errx(1, "illegal timeout value"); + if (*endarg =3D=3D '\0') + break; + if (endarg[1] !=3D '\0') + errx(1, "illegal timeout specifier"); + for (ts =3D timeout_spec; ts->spec !=3D '\0'; ts++) + if (ts->spec =3D=3D *endarg) + break; + if (ts->spec =3D=3D '\0') + errx(1, "illegal timeout specifier"); + timeout_mul =3D ts->mul; + timeout_str =3D ts->str; break; case 'p': usemine =3D 1; @@ -128,7 +154,7 @@ default: usage(); } - timeout.tv_sec =3D sectimeout * 60; + timeout.tv_sec =3D sectimeout * timeout_mul; =20 setuid(getuid()); /* discard privs */ =20 @@ -139,7 +165,7 @@ errx(1, "not a terminal?"); if (gettimeofday(&timval, (struct timezone *)NULL)) err(1, "gettimeofday"); - nexttime =3D timval.tv_sec + (sectimeout * 60); + nexttime =3D timval.tv_sec + (sectimeout * timeout_mul); timval_sec =3D timval.tv_sec; timp =3D localtime(&timval_sec); ap =3D asctime(timp); @@ -200,8 +226,8 @@ if (no_timeout) (void)printf(" no timeout."); else - (void)printf(" timeout in %d minute%s.", sectimeout, - sectimeout !=3D 1 ? "s" : ""); + (void)printf(" timeout in %d %s%s.", sectimeout, + timeout_str, sectimeout !=3D 1 ? "s" : ""); if (vtylock) (void)printf(" vty locked."); (void)printf("\ntime now is %.20s%s%s", ap, tzn, ap + 19); --=20 Peter Pentchev roam@ringlet.net roam@cnsys.bg roam@FreeBSD.org PGP key: http://people.FreeBSD.org/~roam/roam.key.asc Key fingerprint FDBA FD79 C26F 3C51 C95E DF9E ED18 B68D 1619 4553 The rest of this sentence is written in Thailand, on --wTWi5aaYRw9ix9vO Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQFBeEcu7Ri2jRYZRVMRAr+BAKClCigdWoW5uKvZgTFXQOCSVOs9ZQCeIZOJ RHCu3hldpolkQ8wvL+QIkzA= =mTVV -----END PGP SIGNATURE----- --wTWi5aaYRw9ix9vO-- From owner-freebsd-hackers@FreeBSD.ORG Fri Oct 22 07:46:14 2004 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BFC0616A4CE for ; Fri, 22 Oct 2004 07:46:14 +0000 (GMT) Received: from mail.nativenerds.com (host-70-0-111-24.midco.net [24.111.0.70]) by mx1.FreeBSD.org (Postfix) with ESMTP id 40FAE43D2D for ; Fri, 22 Oct 2004 07:46:14 +0000 (GMT) (envelope-from estover@nativenerds.com) Received: from [192.168.1.89] (host-14-37-230-24.midco.net [24.230.37.14]) i9M7las1021959 for ; Fri, 22 Oct 2004 01:47:37 -0600 (MDT) (envelope-from estover@nativenerds.com) From: Ed Stover To: freebsd-hackers@freebsd.org In-Reply-To: <20041021120107.5F9CC16A4D2@hub.freebsd.org> References: <20041021120107.5F9CC16A4D2@hub.freebsd.org> Content-Type: text/plain Organization: Native Nerds Message-Id: <1098431171.26119.27.camel@red> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.5 (1.4.5-7) Date: Fri, 22 Oct 2004 01:46:12 -0600 Content-Transfer-Encoding: 7bit X-Virus-Scanned: clamd / ClamAV version 0.70, clamav-milter version 0.70j Subject: help with poppassd X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: estover@nativenerds.com List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 22 Oct 2004 07:46:14 -0000 Problems with poppassd on 4.10, I can talk to poppassd 106 from telnet both on and off localhost. but for some odd reason i can't get it to change my password. ok, here are the steps that i have taken all ready cd /usr/ports/mail/poppassd/ && make install (it install perfectly) (added this line to /etc/inetd.conf ) pop3pw stream tcp nowait root /usr/local/libexec/poppassd poppassd (checked to see if folling line was in /etc/services, and it was there) pop3pw 106/tcp 3com-tsmux #Eudora compatible PW changer (added following line to /etc/hosts.allow in the appropriate place) poppassd : ALL : allow (restarted inetd) telnet from local host to port 106 and found it running. telnet from remote machines port 106and was able to talk to daemon. Now, I can talk to the daemon but it wont change my password. Any clues? From owner-freebsd-hackers@FreeBSD.ORG Fri Oct 22 08:16:42 2004 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1008916A4CE for ; Fri, 22 Oct 2004 08:16:42 +0000 (GMT) Received: from cydem.org (S0106000103ce4c9c.ed.shawcable.net [68.149.254.167]) by mx1.FreeBSD.org (Postfix) with ESMTP id 848AA43D39 for ; Fri, 22 Oct 2004 08:16:41 +0000 (GMT) (envelope-from soralx@cydem.org) Received: from S01060020ed3972ba.ed.shawcable.net (S01060020ed3972ba.ed.shawcable.net [68.149.254.42]) by cydem.org (Postfix/FreeBSD) with ESMTP id DC73D39387 for ; Fri, 22 Oct 2004 02:16:40 -0600 (MDT) From: To: freebsd-hackers@freebsd.org Date: Fri, 22 Oct 2004 02:16:54 -0600 User-Agent: KMail/1.5.4 References: <200410132110.09915.soralx@cydem.org> <20041021173456.GA20517@odin.ac.hmc.edu> <20041021223525.GB4730@odin.ac.hmc.edu> In-Reply-To: <20041021223525.GB4730@odin.ac.hmc.edu> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200410220216.54868.soralx@cydem.org> Subject: [PATCH] Re: Linksys PCM200 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 22 Oct 2004 08:16:42 -0000 > Could some people with dc(4) devices please test the following patch? > It compiles for me and is trivial, but a quick test is probalby in order > before I commit it. It's rather necessary to test it well, because I didn't actually remove the card's case to see the chip; I relied on my own tests and info from the INet, thus some problems may appear if Linksys modified the chipset Linksys PCM200 is the only 32-bit PCMCIA NIC available in Compusmart - I'm sure that soon someone will buy the card, find the patch, and test it. It's better to wait for feedback before committing the patch. > This differs from soralx's patch in that it adds > comments on the 0xab08 collisions and shortens the description string to > something that will fit in one line on the console. I suggest that you change the description to: "Linksys PCM200 EtherFast 10/100 CardBus NIC, v.03 (ADMtek Centaur-C)" Card's versions differ between each other significantly. Also, there will be no easy way to find out card's chipset if it won't be stated in the description. The string will fit on console even better: dc0: port 0x1000-0x10ff mem 0x88002000-0x880023ff irq 9 at device 0.0 on cardbus1 Timestamp: 0x4178A3E1 [SorAlx] http://cydem.org.ua/ ridin' VN1500-B2 From owner-freebsd-hackers@FreeBSD.ORG Fri Oct 22 12:19:56 2004 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A911516A4CE for ; Fri, 22 Oct 2004 12:19:56 +0000 (GMT) Received: from mail.squidge.com (mail0.squidge.com [195.10.252.14]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9862643D45 for ; Fri, 22 Oct 2004 12:19:55 +0000 (GMT) (envelope-from stewart@nameless-uk.com) Received: from [10.0.2.15] (nameless-uk.demon.co.uk [62.49.20.115]) (authenticated bits=0) by mail.squidge.com (8.12.11/8.12.9) with ESMTP id i9MCJlAw010314 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Fri, 22 Oct 2004 13:19:48 +0100 (BST) Message-ID: <4178FAE2.7040402@nameless-uk.com> Date: Fri, 22 Oct 2004 13:19:46 +0100 From: Stewart Morgan Organization: Nameless Media Group Ltd User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-GB; rv:1.7.3) Gecko/20040910 X-Accept-Language: en, en-us MIME-Version: 1.0 To: freebsd-hackers@freebsd.org X-Enigmail-Version: 0.86.0.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: multipart/mixed; boundary="------------060806080309010702080508" X-Virus-Scanned: by AMaViS at mail.squidge.com X-Spam-Level: -2.0 Subject: ServerWorks and PM/SMB X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: stewart@nameless-uk.com List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 22 Oct 2004 12:19:56 -0000 This is a multi-part message in MIME format. --------------060806080309010702080508 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello, I'm running a 4-STABLE kernel build from last night's CVS-sources. Trying to get some sort of power/temp/fan system monitoring running on an ASUS PR-DLSR533, dual Xeon based on the ServerWorks chipset. Attached is a dump of "pciconf -vl" and the dmesg.boot file. Neither the ichsmb(4) nor intpm(4) drivers detect anything. That said, I couldn't immediately see any matching PCI IDs in the source :( I have read/heard something like ASUS disabling their PM/SMB by default? If that's the case, how can I tell or turn this back on? The page at the following URL suggests that the CSB6 chip is practically the same as the PIIX4, but adding the chip's ID to the intpm(4) driver fails on the bus_allocate_resource() call. I've tried an alternative base-address with no luck. http://www2.lm-sensors.nu/~lm78/cvs/lm_sensors2/doc/busses/i2c-piix4 Any help/experience would be appreciated. I'm happy to test things and help out where possible. Please also let me know if there's any other information needed/forgotten. Thanks. Stewart. - -- Stewart Morgan MEng MIEE Technical Director, Nameless-UK Phone : +44 870 757 1625 | A: Nameless-UK Fax : +44 870 168 0210 | The Production House Email : stewart@nameless-uk.com | 147a Saint Michael's Hill Web : www.nameless-uk.com | Bristol PGP ID: 0xECD5CE64 | BS2 8DB - --------------------------------x--------------------------------- PGP Fingerprint: 89DE F8C3 CA14 598C 30DB 504A 3055 DDD7 ECD5 CE64 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.5 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFBePriMFXd1+zVzmQRAqo2AJwLKzg9EHln7pnHIlTRfsOtCXlT9gCdFwzD LeIPqxN1FYe0ZQzVIzR6y88= =lB3I -----END PGP SIGNATURE----- --------------060806080309010702080508 Content-Type: text/plain; name="pciconf.txt" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="pciconf.txt" chip0@pci0:0:0: class=0x060000 card=0x00000000 chip=0x00141166 rev=0x33 hdr=0x00 vendor = 'ServerWorks (Was: Reliance Computer Corp)' device = 'CNB20-HE Host Bridge' class = bridge subclass = HOST-PCI chip1@pci0:0:1: class=0x060000 card=0x00000000 chip=0x00141166 rev=0x00 hdr=0x00 vendor = 'ServerWorks (Was: Reliance Computer Corp)' device = 'CNB20-HE Host Bridge' class = bridge subclass = HOST-PCI chip2@pci0:0:2: class=0x060000 card=0x00000000 chip=0x00141166 rev=0x00 hdr=0x00 vendor = 'ServerWorks (Was: Reliance Computer Corp)' device = 'CNB20-HE Host Bridge' class = bridge subclass = HOST-PCI em0@pci0:2:0: class=0x020000 card=0x100e8086 chip=0x100e8086 rev=0x02 hdr=0x00 vendor = 'Intel Corporation' device = '82544XT PRO/1000 MT Gigabit Ethernet Controller' class = network subclass = ethernet none0@pci0:3:0: class=0x030000 card=0x80081002 chip=0x47521002 rev=0x27 hdr=0x00 vendor = 'ATI Technologies' device = 'Rage XL PCI' class = display subclass = VGA isab0@pci0:15:0: class=0x060100 card=0x02011166 chip=0x02011166 rev=0x93 hdr=0x00 vendor = 'ServerWorks (Was: Reliance Computer Corp)' device = 'CSB5 PCI to ISA Bridge' class = bridge subclass = PCI-ISA ohci0@pci0:15:2: class=0x0c0310 card=0x02201166 chip=0x02201166 rev=0x05 hdr=0x00 vendor = 'ServerWorks (Was: Reliance Computer Corp)' device = 'OSB4 OpenHCI Compliant USB Controller' class = serial bus subclass = USB chip3@pci0:15:3: class=0x060000 card=0x02301166 chip=0x02251166 rev=0x00 hdr=0x00 vendor = 'ServerWorks (Was: Reliance Computer Corp)' device = 'CSB5 PCI Bridge' class = bridge subclass = HOST-PCI chip4@pci0:17:0: class=0x060000 card=0x00000000 chip=0x01011166 rev=0x05 hdr=0x00 vendor = 'ServerWorks (Was: Reliance Computer Corp)' device = 'CIOB-X2' class = bridge subclass = HOST-PCI chip5@pci0:17:2: class=0x060000 card=0x00000000 chip=0x01011166 rev=0x05 hdr=0x00 vendor = 'ServerWorks (Was: Reliance Computer Corp)' device = 'CIOB-X2' class = bridge subclass = HOST-PCI em1@pci1:2:0: class=0x020000 card=0x110d8086 chip=0x100d8086 rev=0x02 hdr=0x00 vendor = 'Intel Corporation' device = '82544GC Gigabit Ethernet Controller (LOM)' class = network subclass = ethernet aac0@pci2:3:0: class=0x010400 card=0x02859005 chip=0x02859005 rev=0x01 hdr=0x00 vendor = 'Adaptec' device = 'AAC-RAID RAID Controller' class = mass storage subclass = RAID --------------060806080309010702080508 Content-Type: text/plain; name="dmesg.txt" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="dmesg.txt" Copyright (c) 1992-2004 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 4.10-STABLE #14: Thu Oct 21 18:47:10 BST 2004 root@laxmi.bristol.squidge.com:/usr/obj.i686/usr/src/sys/NEWSERVER Calibrating clock(s) ... TSC clock: 2391938824 Hz, i8254 clock: 1193136 Hz Timecounter "i8254" frequency 1193136 Hz CPU: Intel(R) Xeon(TM) CPU 2.40GHz (2391.94-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0xf25 Stepping = 5 Features=0xbfebfbff Hyperthreading: 2 logical CPUs real memory = 2147463168 (2097132K bytes) Physical memory chunk(s): 0x000001000 - 0x00009dfff, 643072 bytes (157 pages) 0x000427000 - 0x07fff0fff, 2143068160 bytes (523210 pages) avail memory = 2086989824 (2038076K bytes) Changing APIC ID for IO APIC #0 from 8 to 4 in MP table Changing APIC ID for IO APIC #1 from 9 to 5 in MP table Changing APIC ID for IO APIC #2 from 6 to 10 on chip Programming 16 pins in IOAPIC #0 IOAPIC #0 intpin 2 -> irq 0 Programming 16 pins in IOAPIC #1 Programming 16 pins in IOAPIC #2 SMP: CPU0 apic_initialize(): lint0: 0x00000700 lint1: 0x00010400 TPR: 0x00000000 SVR: 0x000001ff FreeBSD/SMP: Multiprocessor motherboard: 4 CPUs cpu0 (BSP): apic id: 0, version: 0x00050014, at 0xfee00000 cpu1 (AP): apic id: 6, version: 0x00050014, at 0xfee00000 cpu2 (AP): apic id: 1, version: 0x00050014, at 0xfee00000 cpu3 (AP): apic id: 7, version: 0x00050014, at 0xfee00000 io0 (APIC): apic id: 4, version: 0x000f0011, at 0xfec00000 io1 (APIC): apic id: 5, version: 0x000f0011, at 0xfec01000 io2 (APIC): apic id: 10, version: 0x000f0011, at 0xfec02000 bios32: Found BIOS32 Service Directory header at 0xc00f1f70 bios32: Entry = 0xf18b0 (c00f18b0) Rev = 0 Len = 1 pcibios: PCI BIOS entry at 0x18e0 pnpbios: Found PnP BIOS data at 0xc00f96b0 pnpbios: Entry = f0000:96e0 Rev = 1.0 pnpbios: OEM ID cd041 Other BIOS signatures found: ACPI: 000f55a0 Preloaded elf kernel "kernel" at 0xc03fd000. Warning: Pentium 4 CPU: PSE disabled Pentium Pro MTRR support enabled SMP: CPU0 bsp_apic_configure(): lint0: 0x00010700 lint1: 0x00000400 TPR: 0x00000000 SVR: 0x000001ff pci_open(1): mode 1 addr port (0x0cf8) is 0x800078ac pci_open(1a): mode1res=0x80000000 (0x80000000) pci_cfgcheck: device 0 [class=060000] [hdr=80] is there (id=00141166) Using $PIR table, 12 entries at 0xc00f1e80 pcib-: pcib0 exists, using next available unit number pcib-: pcib0 exists, using next available unit number pcib-: pcib0 exists, using next available unit number pcib-: pcib1 exists, using next available unit number pcib-: pcib2 exists, using next available unit number apm0: on motherboard apm0: found APM BIOS v1.2, connected at v1.2 npx0: on motherboard npx0: INT 16 interface pcib0: on motherboard found-> vendor=0x1166, dev=0x0014, revid=0x33 class=06-00-00, hdrtype=0x00, mfdev=1 subordinatebus=0 secondarybus=0 found-> vendor=0x1166, dev=0x0014, revid=0x00 class=06-00-00, hdrtype=0x00, mfdev=1 subordinatebus=0 secondarybus=0 found-> vendor=0x1166, dev=0x0014, revid=0x00 class=06-00-00, hdrtype=0x00, mfdev=1 subordinatebus=0 secondarybus=0 IOAPIC #1 intpin 2 -> irq 2 Freeing (NOT implemented) redirected PCI irq 12. found-> vendor=0x8086, dev=0x100e, revid=0x02 class=02-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=a, irq=2 map[10]: type 1, range 32, base f7000000, size 17 map[18]: type 1, range 32, base 0000d800, size 6 IOAPIC #1 intpin 1 -> irq 10 found-> vendor=0x1002, dev=0x4752, revid=0x27 class=03-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=a, irq=10 map[10]: type 1, range 32, base f6000000, size 24 map[14]: type 1, range 32, base 0000d400, size 8 map[18]: type 1, range 32, base f5800000, size 12 found-> vendor=0x1166, dev=0x0201, revid=0x93 class=06-01-00, hdrtype=0x00, mfdev=1 subordinatebus=0 secondarybus=0 found-> vendor=0x1166, dev=0x0220, revid=0x05 class=0c-03-10, hdrtype=0x00, mfdev=1 subordinatebus=0 secondarybus=0 intpin=a, irq=11 map[10]: type 1, range 32, base f5000000, size 12 found-> vendor=0x1166, dev=0x0225, revid=0x00 class=06-00-00, hdrtype=0x00, mfdev=1 subordinatebus=0 secondarybus=0 found-> vendor=0x1166, dev=0x0101, revid=0x05 class=06-00-00, hdrtype=0x00, mfdev=1 subordinatebus=0 secondarybus=0 found-> vendor=0x1166, dev=0x0101, revid=0x05 class=06-00-00, hdrtype=0x00, mfdev=1 subordinatebus=0 secondarybus=0 pci0: on pcib0 em0: port 0xd800-0xd83f mem 0xf7000000-0xf701ffff irq 2 at device 2.0 on pci0 bpf: em0 attached em0: Speed:N/A Duplex:N/A pci0: (vendor=0x1002, dev=0x4752) at 3.0 irq 10 isab0: at device 15.0 on pci0 isa0: on isab0 ohci0: mem 0xf5000000-0xf5000fff irq 11 at device 15.2 on pci0 ohci0: (New OHCI DeviceId=0x02201166) usb0: OHCI version 1.0, legacy support usb0: on ohci0 usb0: USB revision 1.0 uhub0: (0x1166) OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 4 ports with 4 removable, self powered pcib1: on motherboard IOAPIC #1 intpin 8 -> irq 12 Freeing (NOT implemented) redirected PCI irq 15. found-> vendor=0x8086, dev=0x100d, revid=0x02 class=02-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=a, irq=12 map[10]: type 1, range 64, base f4800000, size 17 map[18]: type 1, range 64, base f4000000, size 17 map[20]: type 1, range 32, base 0000a400, size 5 pci1: on pcib1 em1: port 0xa400-0xa41f mem 0xf4000000-0xf401ffff,0xf4800000-0xf481ffff irq 12 at device 2.0 on pci1 bpf: em1 attached em1: Speed:N/A Duplex:N/A pcib2: on motherboard IOAPIC #1 intpin 6 -> irq 14 found-> vendor=0x9005, dev=0x0285, revid=0x01 class=01-04-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=a, irq=14 map[10]: type 1, range 32, base f8000000, size 26 pci2: on pcib2 aac0: mem 0xf8000000-0xfbffffff irq 14 at device 3.0 on pci2 aac0: Unknown processor 100MHz, 48MB cache memory, optional battery not installed aac0: Kernel 4.1-0, Build 7244, S/N bc1521 aac0: Supported Options=11d7e aacp0: on aac0 aacp1: on aac0 pcib3: on motherboard pci3: on pcib3 pcib4: on motherboard pci4: on pcib4 pcib5: on motherboard pci5: on pcib5 Trying Read_Port at 203 Trying Read_Port at 243 Trying Read_Port at 283 Trying Read_Port at 2c3 Trying Read_Port at 303 Trying Read_Port at 343 Trying Read_Port at 383 Trying Read_Port at 3c3 isa_probe_children: disabling PnP devices isa_probe_children: probing non-PnP devices orm0: