From owner-freebsd-hackers@FreeBSD.ORG Sun Dec 16 03:02:53 2007 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 108F016A419 for ; Sun, 16 Dec 2007 03:02:53 +0000 (UTC) (envelope-from chuckr@chuckr.org) Received: from mail5.sea5.speakeasy.net (mail5.sea5.speakeasy.net [69.17.117.7]) by mx1.freebsd.org (Postfix) with ESMTP id E56C113C447 for ; Sun, 16 Dec 2007 03:02:52 +0000 (UTC) (envelope-from chuckr@chuckr.org) Received: (qmail 21159 invoked from network); 16 Dec 2007 03:02:52 -0000 Received: from april.chuckr.org (chuckr@[66.92.151.30]) (envelope-sender ) by mail5.sea5.speakeasy.net (qmail-ldap-1.03) with AES256-SHA encrypted SMTP for ; 16 Dec 2007 03:02:52 -0000 Message-ID: <476494C7.6090808@chuckr.org> Date: Sat, 15 Dec 2007 22:00:23 -0500 From: Chuck Robey User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.8.1.9) Gecko/20071107 SeaMonkey/1.1.6 MIME-Version: 1.0 To: Alex Dupre References: <1196470143.4750af7f6accf@webmail.rawbw.com> <4752F825.8020505@chuckr.org> <20071203144159.irjelm2c0c8o8csw@webmail.leidinger.net> <47544B5A.9080903@chuckr.org> <20071205122123.phwu6uh7jksgcwk8@webmail.leidinger.net> <4760A7FE.9070409@chuckr.org> <20071213100821.bet532peog8g488s@webmail.leidinger.net> <4762989F.9070507@FreeBSD.org> <4762DEEA.2070703@chuckr.org> <4762FA4E.9040103@FreeBSD.org> In-Reply-To: <4762FA4E.9040103@FreeBSD.org> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Mailman-Approved-At: Sun, 16 Dec 2007 04:21:29 +0000 Cc: Alexander Leidinger , Yuri , freebsd-hackers@freebsd.org Subject: Re: Linux executable picks up FreeBSD library over linux one and breaks X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 16 Dec 2007 03:02:53 -0000 Alex Dupre wrote: > Chuck Robey wrote: >> I guess I might be wrong, but I have to say, wrapping everything really >> does seem to me to be the hack. > > Call it a wrapper, call it a symlink, but it seems to me that you don't > like linux libs in LOCALBASE *and* you don't like executable references > in LOCALBASE (and these are the only two possibilities exposed by > Alexander). I prefer the wrapper/symlink, because I think all linux > stuff should be in /compat/linux. What do you propose, instead? > (Until tomorrow, I won't be able to get my mail fixed to the point that my mail will get thru to hackers, but I will send this anyhow, in the hopes that maybe ...) I'm sorry if I was not clear, I wish to do what hier(7) seems to be telling me. to put all linux executeables into the compat tree, into /compat, which is a symlink to /usr/compat, and underneath there, the correct name for each executable type, in this case into /compat/linux. For example, llibraries would go into /compat/linux/usr/lib (realize that most Linux software ignores /usr/local/, I don't care for that, but if it's restricted to happening in /compat/linux then it's acceptable to me at least). This makes for a single name that needs to go into linux's ldconfig list instread of the mess that's mismanaged now, and an equally simple setup for the linux PATH. Easy was to segrregate all binaries, by their arch, nice and predictable, not needing to be extended for each new library. This just seems like an obvioous thing to me, I'm sorry if I let that make me skip details. No use oif LOCALBASE or LINUXBASE, unless you wanted to define LINUXBASE to be "linux" and then vector things into /compat/$(LINUXBASE), something like that would make sense. But no use of LOCALBASE. > -- > Alex Dupre > _______________________________________________ > 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 Sun Dec 16 12:44:51 2007 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 505B516A41B for ; Sun, 16 Dec 2007 12:44:51 +0000 (UTC) (envelope-from xistence@0x58.com) Received: from mailexchange.osnn.net (1e.66.5646.static.theplanet.com [70.86.102.30]) by mx1.freebsd.org (Postfix) with SMTP id F0F0F13C474 for ; Sun, 16 Dec 2007 12:44:50 +0000 (UTC) (envelope-from xistence@0x58.com) Received: (qmail 56371 invoked by uid 0); 16 Dec 2007 12:14:23 -0000 Received: from unknown (HELO wideload.network.lan) (xistence@0x58.com@68.228.228.123) by mailexchange.osnn.net with SMTP; 16 Dec 2007 12:14:23 -0000 Cc: FreeBSD Hackers Message-Id: <0D37AA11-3C3F-45AD-90EE-F0E2BB0CF7FD@0x58.com> From: Bert JW Regeer In-Reply-To: Content-Type: multipart/signed; boundary=Apple-Mail-2-456967346; micalg=sha1; protocol="application/pkcs7-signature" Mime-Version: 1.0 (Apple Message framework v915) Date: Sun, 16 Dec 2007 05:18:19 -0700 References: <4763A398.2040109@mansionfamily.plus.com> X-Mailer: Apple Mail (2.915) X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: Re: kqueue and libev X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 16 Dec 2007 12:44:51 -0000 --Apple-Mail-2-456967346 Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit On Dec 15, 2007, at 08:47 , Kip Macy wrote: > On 12/15/07, James Mansion wrote: >> Any idea what the author of libev is on about here (from >> http://pod.tst.eu/http://cvs.schmorp.de/libev/ev.pod): >> >> unsigned int ev_recommended_backends () >> >> Return the set of all backends compiled into this binary of libev >> and also recommended for this platform. This set is often smaller >> than the one returned by |ev_supported_backends|, as for example >> kqueue is broken on most BSDs and will not be autodetected unless >> you explicitly request it (assuming you know what you are doing). >> >> and >> >> |EVBACKEND_KQUEUE| (value 8, most BSD clones) >> >> Kqueue deserves special mention, as at the time of this writing, >> it >> was broken on all BSDs except NetBSD (usually it doesn't work with >> anything but sockets and pipes, except on Darwin, where of course >> its completely useless). For this reason its not being >> "autodetected" unless you explicitly specify it explicitly in the >> flags (i.e. using |EVBACKEND_KQUEUE|). >> >> It looks like a decent library, but these comments seem unfortunate. >> Does anyone know what the author is concerned about? >> >> James >> > Actually, until recently it was broken on pipes. We've never received > any PRs to that effect so there is no way of knowing. You'll have > better luck asking the author himself. > > -Kip How recently? I have been using kqueue with pipes in several programs for the last year or so. Bert JW Regeer --Apple-Mail-2-456967346-- From owner-freebsd-hackers@FreeBSD.ORG Sun Dec 16 14:37:52 2007 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C395616A41A for ; Sun, 16 Dec 2007 14:37:52 +0000 (UTC) (envelope-from freebsd-hackers@m.gmane.org) Received: from ciao.gmane.org (main.gmane.org [80.91.229.2]) by mx1.freebsd.org (Postfix) with ESMTP id 54E5E13C459 for ; Sun, 16 Dec 2007 14:37:51 +0000 (UTC) (envelope-from freebsd-hackers@m.gmane.org) Received: from list by ciao.gmane.org with local (Exim 4.43) id 1J3ucb-0004vt-TF for freebsd-hackers@freebsd.org; Sun, 16 Dec 2007 14:37:37 +0000 Received: from 89-172-51-229.adsl.net.t-com.hr ([89.172.51.229]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sun, 16 Dec 2007 14:37:37 +0000 Received: from ivoras by 89-172-51-229.adsl.net.t-com.hr with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sun, 16 Dec 2007 14:37:37 +0000 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-hackers@freebsd.org From: Ivan Voras Date: Sun, 16 Dec 2007 15:37:23 +0100 Lines: 29 Message-ID: Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enig2E0F0E5C0112D1EFF27F061B" X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: 89-172-51-229.adsl.net.t-com.hr User-Agent: Thunderbird 2.0.0.9 (Windows/20071031) X-Enigmail-Version: 0.95.5 Sender: news Subject: Behaviour of send() X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 16 Dec 2007 14:37:52 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig2E0F0E5C0112D1EFF27F061B Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Hi, If the SO_SNDBUF option is set on a TCP socket with some size N, and assuming nothing is queued for sending yet, is it safe to assume send() won't block while attempting to send a block whose size is <=3D N, even i= f the socket is in "blocking" mode? --------------enig2E0F0E5C0112D1EFF27F061B Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.5 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFHZTgqldnAQVacBcgRAuCnAJ4si2hWcke0anDoPsrRZX50MHgEcACeOlMI UXv9ZqctLI53iZpW5X//CE8= =eefa -----END PGP SIGNATURE----- --------------enig2E0F0E5C0112D1EFF27F061B-- From owner-freebsd-hackers@FreeBSD.ORG Sun Dec 16 22:30:54 2007 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2852B16A419 for ; Sun, 16 Dec 2007 22:30:54 +0000 (UTC) (envelope-from janm@transactionware.com) Received: from mail.transactionware.com (mail.transactionware.com [203.14.245.7]) by mx1.freebsd.org (Postfix) with SMTP id 6471013C457 for ; Sun, 16 Dec 2007 22:30:53 +0000 (UTC) (envelope-from janm@transactionware.com) Received: (qmail 81174 invoked from network); 16 Dec 2007 22:04:33 -0000 Received: from midgard.transactionware.com (192.168.1.55) by dm.transactionware.com with SMTP; 16 Dec 2007 22:04:33 -0000 Received: (qmail 95377 invoked by uid 907); 16 Dec 2007 22:04:10 -0000 Received: from midgard.transactionware.com (HELO STUDYPC) (192.168.1.55) by midgard.transactionware.com (qpsmtpd/0.32) with ESMTP; Mon, 17 Dec 2007 09:04:10 +1100 From: "Jan Mikkelsen" To: "'Julian Elischer'" , "'James Mansion'" Date: Mon, 17 Dec 2007 09:04:13 +1100 Message-ID: <000c01c8402f$9819d710$0301a8c0@STUDYPC> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.6822 In-Reply-To: <47644F93.5080201@elischer.org> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3198 Importance: Normal Thread-Index: Acg/ZuWFvKyhl5bvRAenwXTVoJ70CAAx+RCw X-Mailman-Approved-At: Mon, 17 Dec 2007 00:02:50 +0000 Cc: freebsd-hackers@freebsd.org Subject: RE: kqueue and libev X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 16 Dec 2007 22:30:54 -0000 Julian Elischer wrote: > Julian Elischer wrote: > > James Mansion wrote: > >> [ On the libev being unhappy with kqueue ] > >> ... > >> It looks like a decent library, but these comments seem=20 > unfortunate. > >> Does anyone know what the author is concerned about? > >=20 > > he's just plain misinformed > >=20 >=20 > kqueue works well with aio to files and raw devices for=20 > example. (Only using AIO really makes sense in these cases=20 > anyhow, so I've never really tried using kqueue with non-aio calls.) It also depends what version of FreeBSD. For example, in FreeBSD 4, = kqueue was non-functional with USB serial devices. I ran into that exact = problem with kqueue when porting my event library. Problems like that can make = life difficult for a library author; having a special case for one kind of = handle is a pain, to the point of leading to comments like this. Of course, in this case the best thing to do is to ask the author, and = to see if the situation has changed. Regards, Jan Mikkelsen From owner-freebsd-hackers@FreeBSD.ORG Mon Dec 17 01:22:28 2007 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id F0D4816A419 for ; Mon, 17 Dec 2007 01:22:28 +0000 (UTC) (envelope-from freebsd-hackers@m.gmane.org) Received: from ciao.gmane.org (main.gmane.org [80.91.229.2]) by mx1.freebsd.org (Postfix) with ESMTP id 993A713C468 for ; Mon, 17 Dec 2007 01:22:28 +0000 (UTC) (envelope-from freebsd-hackers@m.gmane.org) Received: from list by ciao.gmane.org with local (Exim 4.43) id 1J44gV-0004Dy-IG for freebsd-hackers@freebsd.org; Mon, 17 Dec 2007 01:22:19 +0000 Received: from www.creo.hu ([217.113.62.14]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Mon, 17 Dec 2007 01:22:19 +0000 Received: from csaba-ml by www.creo.hu with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Mon, 17 Dec 2007 01:22:19 +0000 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-hackers@freebsd.org From: Csaba Henk Date: Mon, 17 Dec 2007 01:22:08 +0000 (UTC) Lines: 120 Message-ID: References: <20071211001828.54e1da6b@deimos.mars.bsd> <20071212134316.3d65f102@deimos.mars.bsd> X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: www.creo.hu User-Agent: slrn/0.9.8.1 (FreeBSD) Sender: news Subject: Re: Disk sync at shutdown and fusefs filesystems X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 17 Dec 2007 01:22:29 -0000 On 2007-12-12, Alejandro Pulver wrote: > On Wed, 12 Dec 2007 03:00:07 +0100 > Csaba Henk wrote: > >> On 2007-12-11, Alejandro Pulver wrote: >> > The problem with NTFS-3G (and all other FUSE based drivers maybe) is >> > that it doesn't flush the cache data to the disk at shutdown, but it >> > does when unmounted (and I guess this doesn't happen automatically). I >> > noticed this when files I write before manually unmounting persist, and >> > otherwise sometimes they don't. >> >> I just happen to discuss this issue with Szaka (ntfs-3g developer) and >> Miklos Szeredi (FUSE developer). At least, we're discussing something >> which might have a relevance here. >> >> They have already discovered issues with system shutdown on Linux, and >> Miklos has implemented a solution for this dubbed as "synchronous >> umount". According to this, the protocol is enhanced with a new message >> called DESTROY. Upon unmounting the fs, the kernel sends a DESTROY to >> the daemon and waits for answer. That is, unmount(2) won't complete >> until the fs says to the kernel "OK, I'm done". >> >> This was introduced in the following commit (as seen in my HG mirror): >> >> http://mercurial.creo.hu/repos/fuse-hg/?rev/a5df6fb4a0e6 >> >> and it's already included in the current sysutils/fusefs-libs port. >> >> And it wouldn't be hard to add kernel side support for FreeBSD. There >> are some questions though: >> >> - Do you think it could be actually useful for solving the shutdown >> issue on FreeBSD? >> > > Hmm, I don't know much of this, but isn't the Linux problem related to > flushing its own block device cache? In FreeBSD it doesn't exist (i.e. > ublio is only user-space), so I wonder if just unmounting before > shutdown solves the issue. I mean, does the kernel still keep > information after a FUSE filesystem is unmounted? > > Please correct me if I'm wrong. > > At least the currently discussed trick only works because it waits a few > seconds after unmounting to let it flush the cache (but I think it's a > common fact that filesystems get registered/unregistered with a small > delay, and may not be related to that). The point in synch umount is that you don't need to wait for an ad hoc amount of time in order to have the various caches flushed / media sync'd -- it enables the filesystem daemon itself to notify the umount procedure that it's done and the world can go on. The exact nature of caches (userspace / in-kernel) doesn't really make a difference from this POV. (Implementing the appropriate synchronization mechanisms is up to the fs daemon.) >> - Some "got hung in unmount" issues are to be sorted out (these >> appeared on Linux, and they might or might not appear on FreeBSD). >> > > Never seen this, but also never unmounted at shutdown before. I have a > patch for it (see thread). Then we could easily see if it get stalled > at shutdown (or when manually stopping the rc.d script). Of course you've never seen this! -- these have appeared as consequences of the synchronous umount (ie., the DESTROY message) which is not yet implemented on FreeBSD. The actual question is whether it is worth to implement it. For me it seems "yes", but I don't know the ins and outs of the FreeBSD init/shutdown system, that's why I'd like to hear the opinion of people like you about this before I go and code it. Whether hangs occur or not if fuse4bsd does sync umount is not that important. I mean, first I would code a basic implementation of DESTROY (that's pretty simple to do!) and we'd see how well that works and if we see problems I try to tune the implementation. That's just business as usual. The next issue is more important... >> - Security issue: with synch unmount, any user who can mount (w/ synch >> unmount), is capable of making the unmount stuck (which is easy to >> fix when the system is up -- just kill the fs daemon -- but can >> make the shutdown process hopelessly stuck). So we'd have to >> decide who/when shall be able to do mounts for which the unmount is >> synchronous. (The current criteria for this on Linux -- ie., >> is the fuseblk fs variant being used? -- is N/A to FreeBSD for >> reasons which are OT here. However, Miklos decided to >> change this so that sych unmount will be tied to the "allow_other" >> option, which is tied to root privileges, and does make sense >> on FreeBSD, too. I'd be happy to hear more suitable criteria. >> > > This would depend on the previous point. It's more important to specify a suitable security policy -- who/when should be capable of mounting an fs in a way so that the umount will be synchronous? (Short term for this: "mounting with synch umount"). I think it's quite a "standalone" question, it depends on nothing else. If a FUSE fs is mounted with synch umount its daemon can block the umount command/syscall, and therefore it can probably block the whole shutdown sequence (killing the process or umounting with -f might help, but these probably won't happen during the normal shutdown course). A possible compromise is letting only the superuser to mount with synch umount. That would mean only superuser mounted ntfs fs-es will be cleanly unmounted during shutdown (I mean, without resorting to hacks in the shutdown scripts). ("Tying synch umount to 'allow_other'", as mentioned above, is practically the same choice.) This of course can be refined, eg. make it configurable with a sysctl, etc. Either case, it's a design issue and not just an implementation detail so it would be clever to try to make up our mind about this. Csaba From owner-freebsd-hackers@FreeBSD.ORG Mon Dec 17 02:27:02 2007 Return-Path: Delivered-To: freebsd-hackers@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E4F7216A417 for ; Mon, 17 Dec 2007 02:27:02 +0000 (UTC) (envelope-from alepulver@FreeBSD.org) Received: from relay02.pair.com (relay02.pair.com [209.68.5.16]) by mx1.freebsd.org (Postfix) with SMTP id A1E4313C4D9 for ; Mon, 17 Dec 2007 02:27:02 +0000 (UTC) (envelope-from alepulver@FreeBSD.org) Received: (qmail 7758 invoked by uid 0); 17 Dec 2007 02:27:01 -0000 Received: from unknown (HELO deimos.mars.bsd) (unknown) by unknown with SMTP; 17 Dec 2007 02:27:01 -0000 X-pair-Authenticated: 200.127.63.61 Date: Sun, 16 Dec 2007 23:26:55 -0300 From: Alejandro Pulver To: Csaba Henk Message-ID: <20071216232655.5d829d41@deimos.mars.bsd> In-Reply-To: References: <20071211001828.54e1da6b@deimos.mars.bsd> <20071212134316.3d65f102@deimos.mars.bsd> X-Mailer: Claws Mail 3.0.2 (GTK+ 2.12.1; i386-portbld-freebsd6.2) Mime-Version: 1.0 Content-Type: multipart/signed; boundary="Sig_/7qQfa=PYKBYRvo95L7r/r7V"; protocol="application/pgp-signature"; micalg=PGP-SHA1 Cc: freebsd-hackers@FreeBSD.org Subject: Re: Disk sync at shutdown and fusefs filesystems X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 17 Dec 2007 02:27:03 -0000 --Sig_/7qQfa=PYKBYRvo95L7r/r7V Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable On Mon, 17 Dec 2007 02:21:53 +0100 Csaba Henk wrote: > >> They have already discovered issues with system shutdown on Linux, and > >> Miklos has implemented a solution for this dubbed as "synchronous > >> umount". According to this, the protocol is enhanced with a new message > >> called DESTROY. Upon unmounting the fs, the kernel sends a DESTROY to > >> the daemon and waits for answer. That is, unmount(2) won't complete > >> until the fs says to the kernel "OK, I'm done". > >> [...] > > Hmm, I don't know much of this, but isn't the Linux problem related to > > flushing its own block device cache? In FreeBSD it doesn't exist (i.e. > > ublio is only user-space), so I wonder if just unmounting before > > shutdown solves the issue. I mean, does the kernel still keep > > information after a FUSE filesystem is unmounted? > > > > Please correct me if I'm wrong. > > > > At least the currently discussed trick only works because it waits a few > > seconds after unmounting to let it flush the cache (but I think it's a > > common fact that filesystems get registered/unregistered with a small > > delay, and may not be related to that). >=20 > The point in synch umount is that you don't need to wait for an ad hoc > amount of time in order to have the various caches flushed / media > sync'd -- it enables the filesystem daemon itself to notify the umount > procedure that it's done and the world can go on. >=20 > The exact nature of caches (userspace / in-kernel) doesn't really make a > difference from this POV. (Implementing the appropriate synchronization > mechanisms is up to the fs daemon.) >=20 I see, thanks for the clarification. > >> - Some "got hung in unmount" issues are to be sorted out (these > >> appeared on Linux, and they might or might not appear on FreeBSD). > >> > > > > Never seen this, but also never unmounted at shutdown before. I have a > > patch for it (see thread). Then we could easily see if it get stalled > > at shutdown (or when manually stopping the rc.d script). >=20 > Of course you've never seen this! -- these have appeared as consequences > of the synchronous umount (ie., the DESTROY message) which is not yet > implemented on FreeBSD. >=20 That's logical. I missed the point. > The actual question is whether it is worth to implement it. For me it > seems "yes", but I don't know the ins and outs of the FreeBSD > init/shutdown system, that's why I'd like to hear the opinion of people > like you about this before I go and code it. >=20 I'm not in the kernel side, but I think it's the correct thing to do. The kernel syncer does the same with other filesystems, so... > Whether hangs occur or not if fuse4bsd does sync umount is not that > important. I mean, first I would code a basic implementation of DESTROY > (that's pretty simple to do!) and we'd see how well that works and if we > see problems I try to tune the implementation. That's just business as > usual. >=20 For what you said, we won't know if there are hangs until we have an implementation of DESTROY. So this will be attended later as you said. > The next issue is more important... >=20 > >> - Security issue: with synch unmount, any user who can mount (w/ synch > >> unmount), is capable of making the unmount stuck (which is easy to > >> fix when the system is up -- just kill the fs daemon -- but can > >> make the shutdown process hopelessly stuck). So we'd have to > >> decide who/when shall be able to do mounts for which the unmount is > >> synchronous. (The current criteria for this on Linux -- ie., > >> is the fuseblk fs variant being used? -- is N/A to FreeBSD for > >> reasons which are OT here. However, Miklos decided to > >> change this so that sych unmount will be tied to the "allow_other" > >> option, which is tied to root privileges, and does make sense > >> on FreeBSD, too. I'd be happy to hear more suitable criteria. > >> > > > > This would depend on the previous point. >=20 > It's more important to specify a suitable security policy -- who/when > should be capable of mounting an fs in a way so that the umount will > be synchronous? (Short term for this: "mounting with synch umount"). >=20 > I think it's quite a "standalone" question, it depends on nothing else. - Some "got hung in unmount" issues are to be sorted out (these appeared on Linux, and they might or might not appear on FreeBSD). IIRC you are saying that any user could make umount hang. And you said this is an unintended behavior caused by the implementation, which appeared on Linux and we don't know if it will happen on FreeBSD. Otherwise the daemon would synchronize the fs and let umount return normally, and this wouldn't happen, right? If this always happens then what is the difference between happening on a root/non-root mount, as it will hang anyways? If I missed the point again please correct me, and clarify the following: Does the hang (point 2)/umount stuck (point 3) issues consist of the same (I assumed so)? If not, please point out the differences. > If a FUSE fs is mounted with synch umount its daemon can block the umount > command/syscall, and therefore it can probably block the whole shutdown > sequence (killing the process or umounting with -f might help, but these > probably won't happen during the normal shutdown course). >=20 > A possible compromise is letting only the superuser to mount with synch > umount. That would mean only superuser mounted ntfs fs-es will be > cleanly unmounted during shutdown (I mean, without resorting to hacks in > the shutdown scripts). ("Tying synch umount to 'allow_other'", as > mentioned above, is practically the same choice.)=20 >=20 > This of course can be refined, eg. make it configurable with a sysctl, > etc. >=20 > Either case, it's a design issue and not just an implementation detail > so it would be clever to try to make up our mind about this. >=20 > Csaba Best Regards, Ale --Sig_/7qQfa=PYKBYRvo95L7r/r7V Content-Type: application/pgp-signature; name=signature.asc Content-Disposition: attachment; filename=signature.asc -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (FreeBSD) iD8DBQFHZd5viV05EpRcP2ERAtehAJ98s/KKO2ukVEFk4XYMSDdok1TrfQCgipYQ CLL1Ni7WL0Uarnbj08uDPx0= =DkN5 -----END PGP SIGNATURE----- --Sig_/7qQfa=PYKBYRvo95L7r/r7V-- From owner-freebsd-hackers@FreeBSD.ORG Mon Dec 17 05:57:10 2007 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C8C3D16A502 for ; Mon, 17 Dec 2007 05:57:10 +0000 (UTC) (envelope-from doconnor@gsoft.com.au) Received: from cain.gsoft.com.au (cain.gsoft.com.au [203.31.81.10]) by mx1.freebsd.org (Postfix) with ESMTP id 640CA13C458 for ; Mon, 17 Dec 2007 05:57:10 +0000 (UTC) (envelope-from doconnor@gsoft.com.au) Received: from inchoate.gsoft.com.au (inchoate.gsoft.com.au [203.31.81.30]) (authenticated bits=0) by cain.gsoft.com.au (8.13.8/8.13.8) with ESMTP id lBH5v729042292 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 17 Dec 2007 16:27:07 +1030 (CST) (envelope-from doconnor@gsoft.com.au) From: "Daniel O'Connor" To: freebsd-hackers@freebsd.org Date: Mon, 17 Dec 2007 16:26:58 +1030 User-Agent: KMail/1.9.7 MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart3916742.FIz2rp8VCQ"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200712171626.59808.doconnor@gsoft.com.au> X-Spam-Score: -3.977 () ALL_TRUSTED,BAYES_00 X-Scanned-By: MIMEDefang 2.58 on 203.31.81.10 Subject: Linux version of libusb that works with FreeBSD X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 17 Dec 2007 05:57:10 -0000 --nextPart3916742.FIz2rp8VCQ Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline I am wondering if anyone has tried building such a beast? ie a Lunux libusb that will be able to access devices in FreeBSD.. The reason I'd like it is that I want to use this=20 http://rmdir.de/~michael/xilinx/ in FreeBSD so I can talk to a USB JTAG=20 cable. The thing I am not sure about is how ioctl's would get mangled on the=20 way through. I guess the other approach would be to use a standard Linux libusb but=20 emulate the device tree it uses in Linux.. Would be a lot of work=20 though I think. =2D-=20 Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C --nextPart3916742.FIz2rp8VCQ Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4 (FreeBSD) iD8DBQBHZg+r5ZPcIHs/zowRAk+2AJ97yHRBqYP/0IHDRm37n+0bSeG3uQCbBZkI VLX+179rTZyAEHhn9XX1IvI= =NM8n -----END PGP SIGNATURE----- --nextPart3916742.FIz2rp8VCQ-- From owner-freebsd-hackers@FreeBSD.ORG Mon Dec 17 06:28:28 2007 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0B50816A417 for ; Mon, 17 Dec 2007 06:28:28 +0000 (UTC) (envelope-from mwm-keyword-freebsdhackers2.e313df@mired.org) Received: from mired.org (bhuda.mired.org [66.92.153.74]) by mx1.freebsd.org (Postfix) with SMTP id 9AC2D13C458 for ; Mon, 17 Dec 2007 06:28:27 +0000 (UTC) (envelope-from mwm-keyword-freebsdhackers2.e313df@mired.org) Received: (qmail 30225 invoked by uid 1001); 17 Dec 2007 06:27:58 -0000 Received: from bhuda.mired.org (localhost.localdomain [127.0.0.1]) by bhuda.mired.org (tmda-ofmipd) with ESMTP; Mon, 17 Dec 2007 01:27:58 -0500 Date: Mon, 17 Dec 2007 01:27:57 -0500 To: freebsd-hackers@freebsd.org Message-ID: <20071217012757.5210e27c@bhuda.mired.org> In-Reply-To: <200712171626.59808.doconnor@gsoft.com.au> References: <200712171626.59808.doconnor@gsoft.com.au> Organization: Meyer Consulting X-Mailer: Claws Mail 2.9.1 (GTK+ 2.10.12; amd64-portbld-freebsd6.2) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Delivery-Agent: TMDA/1.1.11 (Ladyburn) From: Mike Meyer Subject: Re: Linux version of libusb that works with FreeBSD X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 17 Dec 2007 06:28:28 -0000 On Mon, 17 Dec 2007 16:26:58 +1030 "Daniel O'Connor" wrote: > I am wondering if anyone has tried building such a beast? > ie a Lunux libusb that will be able to access devices in FreeBSD.. Well, the devel/libusb port builds out of the box for me. It's used by a number of image grabbing tools (gphoto, sane and hplib), and by tools like nut for talking to UPS systems. http://www.mired.org/consulting.html Independent Network/Unix/Perforce consultant, email for more information. From owner-freebsd-hackers@FreeBSD.ORG Mon Dec 17 11:11:42 2007 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5D32816A41A for ; Mon, 17 Dec 2007 11:11:42 +0000 (UTC) (envelope-from doconnor@gsoft.com.au) Received: from cain.gsoft.com.au (cain.gsoft.com.au [203.31.81.10]) by mx1.freebsd.org (Postfix) with ESMTP id 0017613C4D5 for ; Mon, 17 Dec 2007 11:11:41 +0000 (UTC) (envelope-from doconnor@gsoft.com.au) Received: from inchoate.gsoft.com.au (ppp121-45-30-69.lns10.adl2.internode.on.net [121.45.30.69]) (authenticated bits=0) by cain.gsoft.com.au (8.13.8/8.13.8) with ESMTP id lBHBAnG8053248 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 17 Dec 2007 21:41:30 +1030 (CST) (envelope-from doconnor@gsoft.com.au) From: "Daniel O'Connor" To: Alexander Leidinger Date: Mon, 17 Dec 2007 21:39:39 +1030 User-Agent: KMail/1.9.7 References: <200712171626.59808.doconnor@gsoft.com.au> <20071217100608.sti502z4skk4g4g8@webmail.leidinger.net> In-Reply-To: <20071217100608.sti502z4skk4g4g8@webmail.leidinger.net> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart4717716.bnAj4HipSe"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200712172139.54481.doconnor@gsoft.com.au> X-Spam-Score: -2.312 () BAYES_00 X-Scanned-By: MIMEDefang 2.58 on 203.31.81.10 Cc: freebsd-hackers@freebsd.org Subject: Re: Linux version of libusb that works with FreeBSD X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 17 Dec 2007 11:11:42 -0000 --nextPart4717716.bnAj4HipSe Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Mon, 17 Dec 2007, Alexander Leidinger wrote: > > The thing I am not sure about is how ioctl's would get mangled on > > the way through. > > They get interpreted as linux ioctl, as they are handled by the > linuxulator. You could try to write a wrapper there... Yeah.. Maybe an FS approach would be simpler since there is already a=20 framework. > > I guess the other approach would be to use a standard Linux libusb > > but emulate the device tree it uses in Linux.. Would be a lot of > > work though I think. > > As long as you can specify the devices in the linux app, it's enough > to translate the ioctl's. Apart from that, there's some kind of > translation layer for devices already, but I don't know if it just a > Linux major/minor -> FreeBSD dev mapping, or if you can map linux dev > -> FreeBSD dev. Not sure I can specify the devices, but there's always ln :) > AFAIR HPS' USB stack has linux compatibility, maybe you should ask > him / have a look at it. I had a look at the code but I can't see any Linux related code. =2D-=20 Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C --nextPart4717716.bnAj4HipSe Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4 (FreeBSD) iD8DBQBHZlkC5ZPcIHs/zowRApQ+AJ9eaw/HFJEWv2WsjzLH7ZI4HzniTwCfXSin +uKPYIiGERa6RRj5YH4oA8s= =CJFc -----END PGP SIGNATURE----- --nextPart4717716.bnAj4HipSe-- From owner-freebsd-hackers@FreeBSD.ORG Mon Dec 17 11:07:20 2007 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1993416A540 for ; Mon, 17 Dec 2007 11:07:20 +0000 (UTC) (envelope-from yuri@rawbw.com) Received: from mail0.rawbw.com (mail0.rawbw.com [198.144.192.41]) by mx1.freebsd.org (Postfix) with ESMTP id EAB4713C45A for ; Mon, 17 Dec 2007 11:07:19 +0000 (UTC) (envelope-from yuri@rawbw.com) Received: from mail0.rawbw.com (localhost [127.0.0.1]) by mail0.rawbw.com (8.13.8/8.13.8) with ESMTP id lBHB72Vu066406; Mon, 17 Dec 2007 03:07:02 -0800 (PST) Received: (from www@localhost) by mail0.rawbw.com (8.13.8/8.13.8/Submit) id lBHB72dj066404; Mon, 17 Dec 2007 03:07:02 -0800 (PST) X-Authentication-Warning: mail0.rawbw.com: www set sender to yuri@rawbw.com using -f Received: from ip224.carlyle.sfo.ygnition.net (ip224.carlyle.sfo.ygnition.net [24.219.144.224]) by webmail.rawbw.com (IMP) with HTTP for ; Mon, 17 Dec 2007 03:07:02 -0800 Message-ID: <1197889622.4766585626a92@webmail.rawbw.com> Date: Mon, 17 Dec 2007 03:07:02 -0800 From: Yuri To: freebsd-hackers@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit User-Agent: Internet Messaging Program (IMP) 3.2.1 X-Originating-IP: 24.219.144.224 X-Mailman-Approved-At: Mon, 17 Dec 2007 12:20:10 +0000 Subject: Stale mount on disconnected device: how to delete it? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 17 Dec 2007 11:07:20 -0000 I had USB camera connected and recognized as umass0 and mounted as /mnt/camera on /dev/da0s1. Camera was disconnected while it was still mounted. Now 'mount' command shows: /dev/da0s1 on /mnt/camera (msdosfs, local) 'umount /dev/da0s1' command tells that device is not configured correctly. 'umount -f /dev/da0s1' causes the system to hang. And when I try to reconnect the camera it shows up as /dev/da1s1. How to delete stale mount and stale device? Should I file a PR for this system hang? I use 7.0-BETA4. Yuri From owner-freebsd-hackers@FreeBSD.ORG Mon Dec 17 09:06:24 2007 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2085F16A417 for ; Mon, 17 Dec 2007 09:06:24 +0000 (UTC) (envelope-from alexander@leidinger.net) Received: from redbull.bpaserver.net (redbullneu.bpaserver.net [213.198.78.217]) by mx1.freebsd.org (Postfix) with ESMTP id D517913C44B for ; Mon, 17 Dec 2007 09:06:23 +0000 (UTC) (envelope-from alexander@leidinger.net) Received: from outgoing.leidinger.net (p54A56241.dip.t-dialin.net [84.165.98.65]) by redbull.bpaserver.net (Postfix) with ESMTP id 3F6BF2E060; Mon, 17 Dec 2007 10:06:14 +0100 (CET) Received: from webmail.leidinger.net (webmail.Leidinger.net [192.168.1.102]) by outgoing.leidinger.net (Postfix) with ESMTP id 378E762AAB; Mon, 17 Dec 2007 10:06:09 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=Leidinger.net; s=outgoing-alex; t=1197882370; bh=5qysj05onGhvp2KntOOiYrhsvjaLwzKPg biKLD4oWqA=; h=Message-ID:X-Priority:Date:From:To:Cc:Subject: References:In-Reply-To:MIME-Version:Content-Type: Content-Disposition:Content-Transfer-Encoding:User-Agent; b=Ec6O/f hgbDTTpqOVUdZAKPhWZ8RQ31aVLLQligPN8KvZPFw8OyLi+LPt9whFvyvqKXlwKWs3b itoZ26NDD4sFF5fbyqOihfYeUZLUCtUe6rJKcS3aY7D2Yf31D8w6vE2hdylwwSDaaTS SyD3Cfsr/2XX1A9PDp2bb/jvMETOLwzHqZRqJiM6yqqedCnp6p63t9GDYtZEekT/uUB euQrC4g+OoJq9FwxVXpl1IeaF3SIU6Z/A6vuPzhBCSFYNYfo8OrRQCaHfeGYzDi+lQB hVMm6G6gA3a/YddVrNhiM98sCYJtm2JAtO4ch0JF8lCul8LL9P2xXY+GtOFYuRbW5rE A== Received: (from www@localhost) by webmail.leidinger.net (8.14.1/8.13.8/Submit) id lBH969Vx060767; Mon, 17 Dec 2007 10:06:09 +0100 (CET) (envelope-from Alexander@Leidinger.net) Received: from pslux.cec.eu.int (pslux.cec.eu.int [158.169.9.14]) by webmail.leidinger.net (Horde MIME library) with HTTP; Mon, 17 Dec 2007 10:06:08 +0100 Message-ID: <20071217100608.sti502z4skk4g4g8@webmail.leidinger.net> X-Priority: 3 (Normal) Date: Mon, 17 Dec 2007 10:06:08 +0100 From: Alexander Leidinger To: "Daniel O'Connor" References: <200712171626.59808.doconnor@gsoft.com.au> In-Reply-To: <200712171626.59808.doconnor@gsoft.com.au> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; DelSp="Yes"; format="flowed" Content-Disposition: inline Content-Transfer-Encoding: quoted-printable User-Agent: Internet Messaging Program (IMP) H3 (4.1.4) / FreeBSD-7.0 X-BPAnet-MailScanner-Information: Please contact the ISP for more information X-BPAnet-MailScanner: Found to be clean X-BPAnet-MailScanner-SpamCheck: not spam, SpamAssassin (not cached, score=-14.9, required 6, BAYES_00 -15.00, DKIM_SIGNED 0.00, DKIM_VERIFIED -0.00, RDNS_DYNAMIC 0.10) X-BPAnet-MailScanner-From: alexander@leidinger.net X-Spam-Status: No X-Mailman-Approved-At: Mon, 17 Dec 2007 12:20:32 +0000 Cc: freebsd-hackers@freebsd.org Subject: Re: Linux version of libusb that works with FreeBSD X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 17 Dec 2007 09:06:24 -0000 Quoting Daniel O'Connor (from Mon, 17 Dec 2007 =20 16:26:58 +1030): > I am wondering if anyone has tried building such a beast? > ie a Lunux libusb that will be able to access devices in FreeBSD.. > > The reason I'd like it is that I want to use this > http://rmdir.de/~michael/xilinx/ in FreeBSD so I can talk to a USB JTAG > cable. > > The thing I am not sure about is how ioctl's would get mangled on the > way through. They get interpreted as linux ioctl, as they are handled by the =20 linuxulator. You could try to write a wrapper there... > I guess the other approach would be to use a standard Linux libusb but > emulate the device tree it uses in Linux.. Would be a lot of work > though I think. As long as you can specify the devices in the linux app, it's enough =20 to translate the ioctl's. Apart from that, there's some kind of =20 translation layer for devices already, but I don't know if it just a =20 Linux major/minor -> FreeBSD dev mapping, or if you can map linux dev =20 -> FreeBSD dev. AFAIR HPS' USB stack has linux compatibility, maybe you should ask him =20 / have a look at it. Bye, Alexander. --=20 Power is poison. http://www.Leidinger.net Alexander @ Leidinger.net: PGP ID =3D B0063FE7 http://www.FreeBSD.org netchild @ FreeBSD.org : PGP ID =3D 72077137 From owner-freebsd-hackers@FreeBSD.ORG Mon Dec 17 13:53:42 2007 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9605E16A418 for ; Mon, 17 Dec 2007 13:53:42 +0000 (UTC) (envelope-from dimitry@andric.com) Received: from tensor.andric.com (cl-327.ede-01.nl.sixxs.net [IPv6:2001:7b8:2ff:146::2]) by mx1.freebsd.org (Postfix) with ESMTP id 6AFC313C478 for ; Mon, 17 Dec 2007 13:53:42 +0000 (UTC) (envelope-from dimitry@andric.com) Received: from [IPv6:2001:7b8:3a7:0:7c22:262a:205a:91b6] (unknown [IPv6:2001:7b8:3a7:0:7c22:262a:205a:91b6]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by tensor.andric.com (Postfix) with ESMTP id EE6763E; Mon, 17 Dec 2007 14:53:40 +0100 (CET) Message-ID: <47667F64.8070505@andric.com> Date: Mon, 17 Dec 2007 14:53:40 +0100 From: Dimitry Andric User-Agent: Thunderbird 2.0.0.12pre (Windows/20071214) MIME-Version: 1.0 To: Yuri References: <1197889622.4766585626a92@webmail.rawbw.com> In-Reply-To: <1197889622.4766585626a92@webmail.rawbw.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-hackers@freebsd.org Subject: Re: Stale mount on disconnected device: how to delete it? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 17 Dec 2007 13:53:42 -0000 Yuri wrote: > I had USB camera connected and recognized as umass0 and mounted as /mnt/camera > on /dev/da0s1. > > Camera was disconnected while it was still mounted. I've understood that the only solution to this currently is "don't do that then". :) From owner-freebsd-hackers@FreeBSD.ORG Mon Dec 17 14:11:34 2007 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5B89D16A419 for ; Mon, 17 Dec 2007 14:11:34 +0000 (UTC) (envelope-from m.girish.rao@gmail.com) Received: from wa-out-1112.google.com (wa-out-1112.google.com [209.85.146.180]) by mx1.freebsd.org (Postfix) with ESMTP id 4525113C46A for ; Mon, 17 Dec 2007 14:11:34 +0000 (UTC) (envelope-from m.girish.rao@gmail.com) Received: by wa-out-1112.google.com with SMTP id k17so3535427waf.3 for ; Mon, 17 Dec 2007 06:11:31 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:user-agent:mime-version:to:subject:content-type:content-transfer-encoding; bh=jyDCaIKiFXygldX4y/aWY45C1Sq4f4CwjEi1V/+JYI8=; b=dPMmGiQQodc8sMVvkC5PL/qKYx8s3+SWnXuz/UtFc6t6obmvQWTmK2OOMlJMxCv8y1aFOEQs8QqQlgq9bNWuypzID/jWjJQ6Pjf2Gzc2RKHvPmdNPNgBjK+TnjTyFczPbFcpR2vb4BlvNEv16Lm95LWJUfahSxBAJ/JkMsYwdbE= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:subject:content-type:content-transfer-encoding; b=MBjfiXRgTMswc9dMVdy5cTj1l3HfyYPtVCh2R3kxqrgwATPL7z+DfjpzPfmAO3wMY8mH88XAA1ZkAVTiE+reONxllxvG6R9G95cQ8yckOmy9AUgfvsPRagtlEGUvVptAiItUniG2x5HSGX51qDrjVZh9V8s8AuX40npbRCpUWNg= Received: by 10.114.152.17 with SMTP id z17mr2171378wad.128.1197899181155; Mon, 17 Dec 2007 05:46:21 -0800 (PST) Received: from ?192.168.1.2? ( [122.162.157.214]) by mx.google.com with ESMTPS id v25sm18196288wah.2007.12.17.05.46.18 (version=TLSv1/SSLv3 cipher=RC4-MD5); Mon, 17 Dec 2007 05:46:20 -0800 (PST) Message-ID: <47667D9A.8070300@gmail.com> Date: Mon, 17 Dec 2007 19:16:02 +0530 From: "M.Girish Rao" User-Agent: Thunderbird 2.0.0.6 (X11/20071101) MIME-Version: 1.0 To: freebsd-hackers@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Mailman-Approved-At: Mon, 17 Dec 2007 14:19:34 +0000 Subject: boot0 code mystery X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 17 Dec 2007 14:11:34 -0000 Hi, I am reading the code for boot0 (/usr/src/sys/boot/i386/boot0/boot0.S). This is the part i am trying to understand: -------------------------------------------------------------------------------------------------------- /* * Initialise segments and registers to known values. * segments start at 0. * The stack is immediately below the address we were loaded to. */ start: cld # String ops inc xorw %ax,%ax # Zero movw %ax,%es # Address movw %ax,%ds # data movw %ax,%ss # Set up movw $LOAD,%sp # stack /* * Copy this code to the address it was linked for */ movw %sp,%si # Source movw $start,%di # Destination movw $0x100,%cx # Word count rep # Relocate movsw # code /* * Set address for variable space beyond code, and clear it. * Notice that this is also used to point to the values embedded in the block, * by using negative offsets. */ movw %di,%bp # Address variables movb $0x8,%cl # Words to clear rep # Zero stosw # them /* * Relocate to the new copy of the code. */ incb -0xe(%di) # Sector number jmp main-LOAD+ORIGIN # To relocated code ---------------------------------------------------------------------------------------------------------------- This is all the information I could gather: From this first disk's first sector, 512 bytes are read into the memory location of 0x7C00. After that, the BIOS will check for the number 0xAA55 at the memory location of 0x7DFE (the last two bytes of the boot block code). After the boot0 program is loaded and control is transferred to it, it will set up its registers and stack information. Then, boot0 relocates itself into a lower memory location and jumps to the new address offset to its main routine. Whats the memory location of start? what's this for incb -0xe(%di) ? where are we jumping to in jmp main-LOAD+ORIGIN? whats ORIGIN? I would really appreciate if some could kindly help me out with this. From owner-freebsd-hackers@FreeBSD.ORG Mon Dec 17 14:47:07 2007 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D9E8C16A417 for ; Mon, 17 Dec 2007 14:47:07 +0000 (UTC) (envelope-from romain@blogreen.org) Received: from postfix2-g20.free.fr (postfix2-g20.free.fr [212.27.60.43]) by mx1.freebsd.org (Postfix) with ESMTP id 9AAAF13C447 for ; Mon, 17 Dec 2007 14:47:07 +0000 (UTC) (envelope-from romain@blogreen.org) Received: from smtp3-g19.free.fr (smtp3-g19.free.fr [212.27.42.29]) by postfix2-g20.free.fr (Postfix) with ESMTP id A6BA22147275 for ; Mon, 17 Dec 2007 13:25:48 +0100 (CET) Received: from smtp3-g19.free.fr (localhost.localdomain [127.0.0.1]) by smtp3-g19.free.fr (Postfix) with ESMTP id 4E34F17B5B1; Mon, 17 Dec 2007 15:26:34 +0100 (CET) Received: from marvin.blogreen.org (marvin.blogreen.org [82.247.213.140]) by smtp3-g19.free.fr (Postfix) with ESMTP id B018617B52E; Mon, 17 Dec 2007 15:26:33 +0100 (CET) Received: by marvin.blogreen.org (Postfix, from userid 1001) id 4FABC5C053; Mon, 17 Dec 2007 15:26:33 +0100 (CET) Date: Mon, 17 Dec 2007 15:26:33 +0100 From: Romain =?iso-8859-1?Q?Tarti=E8re?= To: freebsd-hackers@freebsd.org Message-ID: <20071217142633.GA18284@marvin.blogreen.org> Mail-Followup-To: freebsd-hackers@freebsd.org, Yuri References: <1197889622.4766585626a92@webmail.rawbw.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="oyUTqETQ0mS9luUI" Content-Disposition: inline In-Reply-To: <1197889622.4766585626a92@webmail.rawbw.com> User-Agent: Mutt/1.4.2.3i Cc: Yuri Subject: Re: Stale mount on disconnected device: how to delete it? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 17 Dec 2007 14:47:07 -0000 --oyUTqETQ0mS9luUI Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hi On Mon, Dec 17, 2007 at 03:07:02AM -0800, Yuri wrote : > I had USB camera connected and recognized as umass0 and mounted as /mnt/c= amera > on /dev/da0s1. >=20 > Camera was disconnected while it was still mounted. Personal recipe when this kind of things happens (generally caused by a camera switching to power-save mode or that runs out of battery): - switch to single user mode - unmount everything that can be unmounted - remount ro everything that can't be unmounted - reboot (and generally enjoy a kernel panic ;-) ) Not suited for critical production servers, but you won't connect a camera on such a system, would you? BTW, their are already a couple PR around there: http://www.freebsd.org/cgi/query-pr-summary.cgi?text=3Dumount Regards, Romain --=20 Romain Tarti=E8re http://romain.blogreen.org/ pgp: 8DAB A124 0DA4 7024 F82A E748 D8E9 A33F FF56 FF43 (ID: 0xFF56FF43) (plain text =3Dnon-HTML=3D PGP/GPG encrypted/signed e-mail much appreciated) --oyUTqETQ0mS9luUI Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4 (FreeBSD) iD8DBQFHZocZ2OmjP/9W/0MRAgheAJ4g03coUV7d8uFMUqn3qEyGHO8KcACfV1q0 dedKxfRaTPpG2J7SQgKRuBA= =IAOo -----END PGP SIGNATURE----- --oyUTqETQ0mS9luUI-- From owner-freebsd-hackers@FreeBSD.ORG Mon Dec 17 15:11:22 2007 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 819FA16A474 for ; Mon, 17 Dec 2007 15:11:22 +0000 (UTC) (envelope-from jdc@parodius.com) Received: from mx01.sc1.parodius.com (mx01.sc1.parodius.com [72.20.106.3]) by mx1.freebsd.org (Postfix) with ESMTP id 7D3BE13C447 for ; Mon, 17 Dec 2007 15:11:22 +0000 (UTC) (envelope-from jdc@parodius.com) Received: by mx01.sc1.parodius.com (Postfix, from userid 1000) id 6125E1CC07B; Mon, 17 Dec 2007 07:11:22 -0800 (PST) Date: Mon, 17 Dec 2007 07:11:22 -0800 From: Jeremy Chadwick To: "M.Girish Rao" Message-ID: <20071217151122.GA29376@eos.sc1.parodius.com> References: <47667D9A.8070300@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <47667D9A.8070300@gmail.com> User-Agent: Mutt/1.5.16 (2007-06-09) Cc: freebsd-hackers@freebsd.org Subject: Re: boot0 code mystery X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 17 Dec 2007 15:11:22 -0000 On Mon, Dec 17, 2007 at 07:16:02PM +0530, M.Girish Rao wrote: > Whats the memory location of start? I'm going off of memory of my old x86 days, so be kind to me. :-) By the look of it, it's BOOT_BOOT0_ORG, which is 0x600. I'm basing this on the flags passed to cc (actually ld) during linktime. > what's this for incb -0xe(%di) ? No idea. > where are we jumping to in jmp main-LOAD+ORIGIN? main is below the jmp main-LOAD+ORIGIN jump: 91 incb -0xe(%di) # Sector number 92 jmp main-LOAD+ORIGIN # To relocated code 93 94 main: 95 #if defined(SIO) && COMSPEED != 0 LOAD is set to 0x7c00: 27 .set LOAD,0x7c00 # Load address You should be able to get the offset of main by looking at boot0.o once assembled. The start origin doesn't appear to be included (which is why it's added manually). eos# objdump -t boot0.o | grep 'main$' 00000022 l .text 00000000 main Thus I'm left to believe main-LOAD+ORIGIN == 0x8a22. This can be verified by doing: eos# objdump -S -M addr16,data16 boot0.o | grep -m 1 'jmp' 1f: e9 00 8a jmp 8a22 > whats ORIGIN? ORIGIN is an assembler variable set to 0x600: 25 .set ORIGIN,0x600 # Execution address -- | Jeremy Chadwick jdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | From owner-freebsd-hackers@FreeBSD.ORG Mon Dec 17 14:58:26 2007 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D8E0916A421 for ; Mon, 17 Dec 2007 14:58:26 +0000 (UTC) (envelope-from alexander@leidinger.net) Received: from redbull.bpaserver.net (redbullneu.bpaserver.net [213.198.78.217]) by mx1.freebsd.org (Postfix) with ESMTP id 7D56113C4E3 for ; Mon, 17 Dec 2007 14:58:26 +0000 (UTC) (envelope-from alexander@leidinger.net) Received: from outgoing.leidinger.net (p54A56241.dip.t-dialin.net [84.165.98.65]) by redbull.bpaserver.net (Postfix) with ESMTP id 69B6D2E0EF; Mon, 17 Dec 2007 15:58:12 +0100 (CET) Received: from webmail.leidinger.net (webmail.Leidinger.net [192.168.1.102]) by outgoing.leidinger.net (Postfix) with ESMTP id 174A3773C5; Mon, 17 Dec 2007 15:58:09 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=Leidinger.net; s=outgoing-alex; t=1197903489; bh=9RPhNOxwPmchBFcg2HFeiCW2XngmvH2Z1 ibePoCBTdE=; h=Message-ID:X-Priority:Date:From:To:Cc:Subject: References:In-Reply-To:MIME-Version:Content-Type: Content-Disposition:Content-Transfer-Encoding:User-Agent; b=bsGEwQ PELjzmEgHK/O8mliZr290JhJELwDtAAPBxBxF9hy91vyDh3NWTtUdkZWHq40fyu1Opm YApsKgwZKE2bv5md6NMdNZTbhtB3f6HOLeWtCZG+CbxxA1JU/LrAZs20MYV1Uo/OZR9 4H8uP7Jo8FzfSuaXXX9NfvBWJAD4dztMHAhNxc4KAnW4lVwnIUI4nQ6+1tnnQI+kP0K 4tLgHLi4b+lS74ViQuSwSRUQOq4l9g2l8lW9Ey1b9N2HB6SPIi2hcV7C/jb6875Potn ldUIh9GM1b1R6K3L3UUyGGn5sqIPL86Xtm2d9iPTB4ZleDBdN1X5pmxio6K4NiWPI4F w== Received: (from www@localhost) by webmail.leidinger.net (8.14.1/8.13.8/Submit) id lBHEw7we019168; Mon, 17 Dec 2007 15:58:07 +0100 (CET) (envelope-from Alexander@Leidinger.net) Received: from pslux.cec.eu.int (pslux.cec.eu.int [158.169.9.14]) by webmail.leidinger.net (Horde MIME library) with HTTP; Mon, 17 Dec 2007 15:58:07 +0100 Message-ID: <20071217155807.0v26aejw3og808wc@webmail.leidinger.net> X-Priority: 3 (Normal) Date: Mon, 17 Dec 2007 15:58:07 +0100 From: Alexander Leidinger To: "Daniel O'Connor" References: <200712171626.59808.doconnor@gsoft.com.au> <20071217100608.sti502z4skk4g4g8@webmail.leidinger.net> <200712172139.54481.doconnor@gsoft.com.au> In-Reply-To: <200712172139.54481.doconnor@gsoft.com.au> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; DelSp="Yes"; format="flowed" Content-Disposition: inline Content-Transfer-Encoding: 7bit User-Agent: Internet Messaging Program (IMP) H3 (4.1.4) / FreeBSD-7.0 X-BPAnet-MailScanner-Information: Please contact the ISP for more information X-BPAnet-MailScanner: Found to be clean X-BPAnet-MailScanner-SpamCheck: not spam, SpamAssassin (not cached, score=-14.9, required 6, BAYES_00 -15.00, DKIM_SIGNED 0.00, DKIM_VERIFIED -0.00, RDNS_DYNAMIC 0.10) X-BPAnet-MailScanner-From: alexander@leidinger.net X-Spam-Status: No X-Mailman-Approved-At: Mon, 17 Dec 2007 15:12:17 +0000 Cc: freebsd-hackers@freebsd.org, hps@freebsd.org Subject: Re: Linux version of libusb that works with FreeBSD X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 17 Dec 2007 14:58:26 -0000 Quoting Daniel O'Connor (from Mon, 17 Dec 2007 21:39:39 +1030): > On Mon, 17 Dec 2007, Alexander Leidinger wrote: >> AFAIR HPS' USB stack has linux compatibility, maybe you should ask >> him / have a look at it. > > I had a look at the code but I can't see any Linux related code. You better ask him, I never used his USB stack, I just remembered to have read something like this... HPS CCed. Bye, Alexander. -- People need good lies. There are too many bad ones. -- Bokonon, "Cat's Cradle" by Kurt Vonnegut, Jr. http://www.Leidinger.net Alexander @ Leidinger.net: PGP ID = B0063FE7 http://www.FreeBSD.org netchild @ FreeBSD.org : PGP ID = 72077137 From owner-freebsd-hackers@FreeBSD.ORG Mon Dec 17 16:01:56 2007 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id EF4DC16A419 for ; Mon, 17 Dec 2007 16:01:56 +0000 (UTC) (envelope-from romain@blogreen.org) Received: from smtp3-g19.free.fr (smtp3-g19.free.fr [212.27.42.29]) by mx1.freebsd.org (Postfix) with ESMTP id B94E413C448 for ; Mon, 17 Dec 2007 16:01:56 +0000 (UTC) (envelope-from romain@blogreen.org) Received: from smtp3-g19.free.fr (localhost.localdomain [127.0.0.1]) by smtp3-g19.free.fr (Postfix) with ESMTP id CED2C17B560; Mon, 17 Dec 2007 17:01:55 +0100 (CET) Received: from marvin.blogreen.org (marvin.blogreen.org [82.247.213.140]) by smtp3-g19.free.fr (Postfix) with ESMTP id BB22617B5A7; Mon, 17 Dec 2007 17:01:54 +0100 (CET) Received: by marvin.blogreen.org (Postfix, from userid 1001) id 829A15C053; Mon, 17 Dec 2007 17:01:54 +0100 (CET) Date: Mon, 17 Dec 2007 17:01:54 +0100 From: Romain =?iso-8859-1?Q?Tarti=E8re?= To: babkin@users.sf.net Message-ID: <20071217160154.GA19023@marvin.blogreen.org> Mail-Followup-To: babkin@users.sf.net, freebsd-hackers@freebsd.org, Yuri References: <135273.956351197903508116.JavaMail.root@vms070.mailsrvcs.net> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="wRRV7LY7NUeQGEoC" Content-Disposition: inline In-Reply-To: <135273.956351197903508116.JavaMail.root@vms070.mailsrvcs.net> User-Agent: Mutt/1.4.2.3i Cc: freebsd-hackers@freebsd.org, Yuri Subject: Re: Stale mount on disconnected device: how to delete it? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 17 Dec 2007 16:01:57 -0000 --wRRV7LY7NUeQGEoC Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Dec 17, 2007 at 08:58:27AM -0600, Sergey Babkin wrote : > Would not umount -f do the trick? I tried it without particular care one time on a failing device and experienced an instant system reboot (was it caused by the faulty disk or by a limitation in the implementation of the system (FreeBSD 5.x at that time), I can't be sure). Since then, I have never tried to force the unmounting of any device in favor of rebooting the system. In fact, crawling the PR database already reports problems about forcing unmounting of devices [kern/77026, kern/102250, usb/46176, ...]. So I prefer to be sure that everything is safe (not mounted read/write) before trying anything that can lead to data loss. Regards, Romain --=20 Romain Tarti=E8re http://romain.blogreen.org/ pgp: 8DAB A124 0DA4 7024 F82A E748 D8E9 A33F FF56 FF43 (ID: 0xFF56FF43) (plain text =3Dnon-HTML=3D PGP/GPG encrypted/signed e-mail much appreciated) --wRRV7LY7NUeQGEoC Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4 (FreeBSD) iD8DBQFHZp1y2OmjP/9W/0MRAnBWAJ9qAM7t/bfpzkpZR7CuAFQ+Lcg/2wCgmnUq rja84cHJOLN/XlZyQSmSxOc= =J8sa -----END PGP SIGNATURE----- --wRRV7LY7NUeQGEoC-- From owner-freebsd-hackers@FreeBSD.ORG Mon Dec 17 15:58:52 2007 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C24D116A468 for ; Mon, 17 Dec 2007 15:58:52 +0000 (UTC) (envelope-from babkin@verizon.net) Received: from vms173003pub.verizon.net (vms173003pub.verizon.net [206.46.173.3]) by mx1.freebsd.org (Postfix) with ESMTP id AAC8D13C46E for ; Mon, 17 Dec 2007 15:58:52 +0000 (UTC) (envelope-from babkin@verizon.net) Received: from vms070.mailsrvcs.net ([192.168.1.2]) by vms173003.mailsrvcs.net (Sun Java System Messaging Server 6.2-6.01 (built Apr 3 2006)) with ESMTPA id <0JT7002F286N3RB0@vms173003.mailsrvcs.net> for freebsd-hackers@freebsd.org; Mon, 17 Dec 2007 08:56:48 -0600 (CST) Received: from 65.242.108.162 ([65.242.108.162]) by vms070.mailsrvcs.net (Verizon Webmail) with HTTP; Mon, 17 Dec 2007 08:58:27 -0600 (CST) Date: Mon, 17 Dec 2007 08:58:27 -0600 (CST) From: Sergey Babkin X-Originating-IP: [65.242.108.162] To: freebsd-hackers@freebsd.org, =?ISO8859-1?Q?Romain_Tarti=E8re?= Message-id: <135273.956351197903508116.JavaMail.root@vms070.mailsrvcs.net> MIME-version: 1.0 Content-type: text/plain; charset=UTF-8 Content-transfer-encoding: 7bit X-Mailman-Approved-At: Mon, 17 Dec 2007 16:15:11 +0000 Cc: Yuri Subject: Re: Re: Stale mount on disconnected device: how to delete it? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: babkin@users.sf.net List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 17 Dec 2007 15:58:52 -0000 > >On Mon, Dec 17, 2007 at 03:07:02AM -0800, Yuri wrote : >> I had USB camera connected and recognized as umass0 and mounted as /mnt/camera >> on /dev/da0s1. >> >> Camera was disconnected while it was still mounted. > >Personal recipe when this kind of things happens (generally caused by a >camera switching to power-save mode or that runs out of battery): Would not umount -f do the trick? -SB From owner-freebsd-hackers@FreeBSD.ORG Mon Dec 17 16:46:10 2007 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id CEEFF16A469 for ; Mon, 17 Dec 2007 16:46:10 +0000 (UTC) (envelope-from freebsd-hackers@m.gmane.org) Received: from ciao.gmane.org (main.gmane.org [80.91.229.2]) by mx1.freebsd.org (Postfix) with ESMTP id 6456B13C457 for ; Mon, 17 Dec 2007 16:46:10 +0000 (UTC) (envelope-from freebsd-hackers@m.gmane.org) Received: from list by ciao.gmane.org with local (Exim 4.43) id 1J4J55-0006Fw-My for freebsd-hackers@freebsd.org; Mon, 17 Dec 2007 16:44:40 +0000 Received: from www.creo.hu ([217.113.62.14]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Mon, 17 Dec 2007 16:44:39 +0000 Received: from csaba-ml by www.creo.hu with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Mon, 17 Dec 2007 16:44:39 +0000 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-hackers@freebsd.org From: Csaba Henk Date: Mon, 17 Dec 2007 16:41:32 +0000 (UTC) Lines: 68 Message-ID: References: <20071211001828.54e1da6b@deimos.mars.bsd> <20071212134316.3d65f102@deimos.mars.bsd> <20071216232655.5d829d41@deimos.mars.bsd> X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: www.creo.hu User-Agent: slrn/0.9.8.1 (FreeBSD) Sender: news Subject: Re: Disk sync at shutdown and fusefs filesystems X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 17 Dec 2007 16:46:10 -0000 On 2007-12-17, Alejandro Pulver wrote: > > - Some "got hung in unmount" issues are to be sorted out (these > appeared on Linux, and they might or might not appear on FreeBSD). > > > IIRC you are saying that any user could make umount hang. And you said > this is an unintended behavior caused by the implementation, which > appeared on Linux and we don't know if it will happen on FreeBSD. > > Otherwise the daemon would synchronize the fs and let umount return > normally, and this wouldn't happen, right? > > If this always happens then what is the difference between happening on > a root/non-root mount, as it will hang anyways? > > If I missed the point again please correct me, and clarify the following: > Does the hang (point 2)/umount stuck (point 3) issues consist of the > same (I assumed so)? If not, please point out the differences. Oh sorry, I see my wording was still not clear enough... Point 3) and point 2) are completely different issues. Point 2) is about a _bug_ which might make unmount hang (contrary to our intentions). Point 3) is about the access control _policy_ of the "mounting with sync unmount" feature which is DOS capable: it enables some malicious code to make the shutdown sequence hung. [Btw, I used/use the "hang", "block", "make stuck" expressions interchangeably, I'm sorry if it's not correct English or just sounds unnaturally in some cases.] The same statement with more details: Point 2) is about a defect of a naive, straightforward implementation of handling the DESTROY message in the FUSE library. That is, if the daemon is mounted with synch umount, under certain circumstances (if I understood correctly, this amounts to killing the daemon with a SIGTERM [ie., the FUSE session terminates due the sigterm and not because of doing an unmount(2) on the fs]) the umount code of the lib falls into an infinite loop. This is a bug which may or may not affect FreeBSD once DESTROY is implemented for it -- the umount code in the lib is platform specific, anyway. So this is just about a possible bug which really falls into the "we will see it when we get there" category. OTOH, by the essence of the synch umount, mounting an fs daemon w/ synch umount means that the daemon gets the control over the termination of the unmount syscall. So being able to mount w/ synch umount assumes some kind of trusted state -- it enables a malicious daemon to block its unmounting. It's not a real risk if the unmount is done manually -- when the person who unmounts the fs observes that the daemon is blocking the unmount, she can turn to either a forced unmount or killing the daemon. However, during the shutdown sequence, which is automated, noone will be there to forcedly terminate the FUSE session, and shutdown might get stuck this way. So we have to decide how to control the access to mounting with synch umount. This is point 3). Probably I just provide an implementation of it for the kernel module and add a "sync_umount" option to mount_fusefs(8) and let it be as is and we'll see how well it works out, and what to do about access control -wise. Csaba From owner-freebsd-hackers@FreeBSD.ORG Mon Dec 17 17:15:18 2007 Return-Path: Delivered-To: freebsd-hackers@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0FB6C16A419 for ; Mon, 17 Dec 2007 17:15:18 +0000 (UTC) (envelope-from alepulver@FreeBSD.org) Received: from relay03.pair.com (relay03.pair.com [209.68.5.17]) by mx1.freebsd.org (Postfix) with SMTP id CE2CF13C44B for ; Mon, 17 Dec 2007 17:15:17 +0000 (UTC) (envelope-from alepulver@FreeBSD.org) Received: (qmail 50737 invoked by uid 0); 17 Dec 2007 17:15:15 -0000 Received: from unknown (HELO deimos.mars.bsd) (unknown) by unknown with SMTP; 17 Dec 2007 17:15:15 -0000 X-pair-Authenticated: 200.127.63.61 Date: Mon, 17 Dec 2007 14:15:04 -0300 From: Alejandro Pulver To: Csaba Henk Message-ID: <20071217141504.1f3d8932@deimos.mars.bsd> In-Reply-To: References: <20071211001828.54e1da6b@deimos.mars.bsd> <20071212134316.3d65f102@deimos.mars.bsd> <20071216232655.5d829d41@deimos.mars.bsd> X-Mailer: Claws Mail 3.0.2 (GTK+ 2.12.1; i386-portbld-freebsd6.2) Mime-Version: 1.0 Content-Type: multipart/signed; boundary="Sig_/AFYVs7M_8nvkr5DdgWmpidl"; protocol="application/pgp-signature"; micalg=PGP-SHA1 Cc: freebsd-hackers@FreeBSD.org Subject: Re: Disk sync at shutdown and fusefs filesystems X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 17 Dec 2007 17:15:18 -0000 --Sig_/AFYVs7M_8nvkr5DdgWmpidl Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable On Mon, 17 Dec 2007 17:41:16 +0100 Csaba Henk wrote: > [This message has also been posted to gmane.os.freebsd.devel.hackers.] > On 2007-12-17, Alejandro Pulver wrote: > > > > - Some "got hung in unmount" issues are to be sorted out (these > > appeared on Linux, and they might or might not appear on FreeBSD). > > > > > > IIRC you are saying that any user could make umount hang. And you said > > this is an unintended behavior caused by the implementation, which > > appeared on Linux and we don't know if it will happen on FreeBSD. > > > > Otherwise the daemon would synchronize the fs and let umount return > > normally, and this wouldn't happen, right? > > > > If this always happens then what is the difference between happening on > > a root/non-root mount, as it will hang anyways? > > > > If I missed the point again please correct me, and clarify the followin= g: > > Does the hang (point 2)/umount stuck (point 3) issues consist of the > > same (I assumed so)? If not, please point out the differences. >=20 > Oh sorry, I see my wording was still not clear enough... >=20 > Point 3) and point 2) are completely different issues. >=20 > Point 2) is about a _bug_ which might make unmount hang (contrary to our > intentions). Point 3) is about the access control _policy_ of the > "mounting with sync unmount" feature which is DOS capable: it enables > some malicious code to make the shutdown sequence hung. >=20 I understand now (about 3). So a user could write a FUSE daemon which never replies properly (or doesn't reply at all) to the DESTROY code, and the kernel module would be waiting indefinitely. Stalling the shutdown sequence. Maybe this could be solved with a timeout (see below). > [Btw, I used/use the "hang", "block", "make stuck" expressions > interchangeably, I'm sorry if it's not correct English or just sounds > unnaturally in some cases.] >=20 I'm not a native English speaker, so these all seemed the same to me. Thanks for the clarifications. >=20 > The same statement with more details: >=20 > Point 2) is about a defect of a naive, straightforward implementation of > handling the DESTROY message in the FUSE library. That is, if the daemon > is mounted with synch umount, under certain circumstances (if I > understood correctly, this amounts to killing the daemon with a SIGTERM [= ie., > the FUSE session terminates due the sigterm and not because of doing an > unmount(2) on the fs]) the umount code of the lib falls into an infinite > loop. This is a bug which may or may not affect FreeBSD once DESTROY is > implemented for it -- the umount code in the lib is platform specific, > anyway. So this is just about a possible bug which really falls into=20 > the "we will see it when we get there" category. >=20 O.K. > OTOH, by the essence of the synch umount, mounting an fs daemon w/ synch > umount means that the daemon gets the control over the termination > of the unmount syscall. So being able to mount w/ synch umount assumes > some kind of trusted state -- it enables a malicious daemon to block its > unmounting. It's not a real risk if the unmount is done manually -- when > the person who unmounts the fs observes that the daemon is blocking the > unmount, she can turn to either a forced unmount or killing the daemon. > However, during the shutdown sequence, which is automated, noone will be > there to forcedly terminate the FUSE session, and shutdown might get > stuck this way. >=20 > So we have to decide how to control the access to mounting with synch > umount. This is point 3). >=20 I can see 2 approaches to solving this (not sure if both are possible though): Maybe adding a timeout to the FUSE kernel module? I've seen the syncer daemon say "giving up on ..." when I had ATA errors related to configuration/cable problems (it retried for a while, and as disk couldn't sync, it terminated anyways). So maybe something similar could be implemented. Otherwise IMHO only root should be allowed to do such mounts, or having a sysctl disabled by default to allow users do this (like vfs.usermount). >=20 > Probably I just provide an implementation of it for the kernel module > and add a "sync_umount" option to mount_fusefs(8) and let it be as is > and we'll see how well it works out, and what to do about access control > -wise. >=20 > Csaba When the implementation is ready, and if these problems are sorted out, do you think it could be enabled by default (at least for root)? Because that's the behavior most filesystems would prefer I think. Best Regards, Ale --Sig_/AFYVs7M_8nvkr5DdgWmpidl Content-Type: application/pgp-signature; name=signature.asc Content-Disposition: attachment; filename=signature.asc -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (FreeBSD) iD8DBQFHZq6YiV05EpRcP2ERAuFGAKDgn5uOzqDqc81vzBU1SLIMHQrfHACdG7ZY XsA46Qb+XuxQIqnW+vwi/fY= =D6Ce -----END PGP SIGNATURE----- --Sig_/AFYVs7M_8nvkr5DdgWmpidl-- From owner-freebsd-hackers@FreeBSD.ORG Mon Dec 17 18:09:26 2007 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id CEFCA16A420 for ; Mon, 17 Dec 2007 18:09:26 +0000 (UTC) (envelope-from peterjeremy@optushome.com.au) Received: from mail13.syd.optusnet.com.au (mail13.syd.optusnet.com.au [211.29.132.194]) by mx1.freebsd.org (Postfix) with ESMTP id 592CE13C4D3 for ; Mon, 17 Dec 2007 18:09:26 +0000 (UTC) (envelope-from peterjeremy@optushome.com.au) Received: from server.vk2pj.dyndns.org (c220-239-20-82.belrs4.nsw.optusnet.com.au [220.239.20.82]) by mail13.syd.optusnet.com.au (8.13.1/8.13.1) with ESMTP id lBHI9MqO007668 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 18 Dec 2007 05:09:24 +1100 Received: from server.vk2pj.dyndns.org (localhost.vk2pj.dyndns.org [127.0.0.1]) by server.vk2pj.dyndns.org (8.14.1/8.14.1) with ESMTP id lBHI9Mn2067902; Tue, 18 Dec 2007 05:09:22 +1100 (EST) (envelope-from peter@server.vk2pj.dyndns.org) Received: (from peter@localhost) by server.vk2pj.dyndns.org (8.14.1/8.14.1/Submit) id lBHI9LRW067897; Tue, 18 Dec 2007 05:09:21 +1100 (EST) (envelope-from peter) Date: Tue, 18 Dec 2007 05:09:21 +1100 From: Peter Jeremy To: Yuri Message-ID: <20071217180921.GM85797@server.vk2pj.dyndns.org> References: <1197889622.4766585626a92@webmail.rawbw.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="WYTEVAkct0FjGQmd" Content-Disposition: inline In-Reply-To: <1197889622.4766585626a92@webmail.rawbw.com> X-PGP-Key: http://members.optusnet.com.au/peterjeremy/pubkey.asc User-Agent: Mutt/1.5.16 (2007-06-09) Cc: freebsd-hackers@freebsd.org Subject: Re: Stale mount on disconnected device: how to delete it? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 17 Dec 2007 18:09:26 -0000 --WYTEVAkct0FjGQmd Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Dec 17, 2007 at 03:07:02AM -0800, Yuri wrote: >I had USB camera connected and recognized as umass0 and mounted as /mnt/ca= mera >on /dev/da0s1. > >Camera was disconnected while it was still mounted. This triggers known and extremely painful to fix bugs in FreeBSD. Your best work-around is to use ports/emulators/mtools rather than mount_msdosfs to to access removable devices. --=20 Peter Jeremy Please excuse any delays as the result of my ISP's inability to implement an MTA that is either RFC2821-compliant or matches their claimed behaviour. --WYTEVAkct0FjGQmd Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4 (FreeBSD) iD8DBQFHZrtR/opHv/APuIcRAvIkAKCQbxRvqnTh8EAqjnGKdD+sRXj2YwCgi0Hx varIHKAoHyJwiogQtkYkYXU= =lKSE -----END PGP SIGNATURE----- --WYTEVAkct0FjGQmd-- From owner-freebsd-hackers@FreeBSD.ORG Mon Dec 17 18:33:09 2007 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 657BC16A417 for ; Mon, 17 Dec 2007 18:33:09 +0000 (UTC) (envelope-from yuri@rawbw.com) Received: from mail0.rawbw.com (mail0.rawbw.com [198.144.192.41]) by mx1.freebsd.org (Postfix) with ESMTP id 4E7FE13C468 for ; Mon, 17 Dec 2007 18:33:09 +0000 (UTC) (envelope-from yuri@rawbw.com) Received: from mail0.rawbw.com (localhost [127.0.0.1]) by mail0.rawbw.com (8.13.8/8.13.8) with ESMTP id lBHIWoWO031741; Mon, 17 Dec 2007 10:32:50 -0800 (PST) Received: (from www@localhost) by mail0.rawbw.com (8.13.8/8.13.8/Submit) id lBHIWohj031714; Mon, 17 Dec 2007 10:32:50 -0800 (PST) X-Authentication-Warning: mail0.rawbw.com: www set sender to yuri@rawbw.com using -f Received: from ip224.carlyle.sfo.ygnition.net (ip224.carlyle.sfo.ygnition.net [24.219.144.224]) by webmail.rawbw.com (IMP) with HTTP for ; Mon, 17 Dec 2007 10:32:48 -0800 Message-ID: <1197916368.4766c0d0db6a8@webmail.rawbw.com> Date: Mon, 17 Dec 2007 10:32:48 -0800 From: Yuri To: Yuri References: <1197889622.4766585626a92@webmail.rawbw.com> In-Reply-To: <1197889622.4766585626a92@webmail.rawbw.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit User-Agent: Internet Messaging Program (IMP) 3.2.1 X-Originating-IP: 24.219.144.224 X-Mailman-Approved-At: Mon, 17 Dec 2007 18:41:12 +0000 Cc: freebsd-hackers@freebsd.org Subject: Re: Stale mount on disconnected device: how to delete it? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 17 Dec 2007 18:33:09 -0000 > I had USB camera connected and recognized as umass0 and mounted as > /mnt/camera > on /dev/da0s1. > > Camera was disconnected while it was still mounted. I submitted this late at night. Now in the morning another solution came to my mind. I thought I will find it in replies but I didn't. In case of USB device (which device in question in this problem happens to be) usbd can be used to mount it. If attach/detach events trigger mount/unmount commands this problem shouldn't exist. I didn't try though. Otherwise for non-USB devices this situation probably can only happen in case of failing devices. Yuri From owner-freebsd-hackers@FreeBSD.ORG Mon Dec 17 21:22:55 2007 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id F241F16A41A for ; Mon, 17 Dec 2007 21:22:55 +0000 (UTC) (envelope-from james@mansionfamily.plus.com) Received: from fhw-relay07.plus.net (fhw-relay07.plus.net [212.159.14.215]) by mx1.freebsd.org (Postfix) with ESMTP id 9969813C457 for ; Mon, 17 Dec 2007 21:22:55 +0000 (UTC) (envelope-from james@mansionfamily.plus.com) Received: from [80.229.150.39] (helo=mansionfamily.plus.com) by fhw-relay07.plus.net with esmtp (Exim) id 1J4NQL-0000Hh-Ai for freebsd-hackers@freebsd.org; Mon, 17 Dec 2007 21:22:53 +0000 Received: from [192.168.0.87] ([192.168.0.87]:1804) by mansionfamily.plus.com with [XMail 1.22 ESMTP Server] id for from ; Mon, 17 Dec 2007 21:28:15 -0000 Message-ID: <4766E92C.6020703@mansionfamily.plus.com> Date: Mon, 17 Dec 2007 21:25:01 +0000 From: James Mansion Organization: MsgWare User-Agent: Thunderbird 2.0.0.0 (Windows/20070326) MIME-Version: 1.0 To: Kip Macy References: <4763A398.2040109@mansionfamily.plus.com> <47644BFE.3060003@elischer.org> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-hackers@freebsd.org, Julian Elischer Subject: Re: kqueue and libev X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 17 Dec 2007 21:22:56 -0000 Kip Macy wrote: >> he's just plain misinforme > Until we know what he is referring to we can't actually say that. > -Kip > OK he said I could post from our private email so here goes. There were bits in and around relating to the Solaris /dev/poll support (and the mechanism's limitations) which I've elided. I think the most telling thing is probably that drivers need to provide support and that a single mechanism in the driver doesn't support select and poll at the same time - which I guess lines up with the reported failure with USB serial. Does kqueue work with USB for example? How about an AIO request to read from a USB endpoint? It may well just be a case of 'fessing up to system limitations. James ============================================================================ Compile and install rxvt-unicode on freebsd and run it with: urxvt # works, uses select (or maybe poll) LIBEV_FLAGS=8 urxvt # acts weird, uses kqueue (note: only works when urxvt isn't set[gu]id) The typical symptoms are either delayed notificatrions, no notifications at all or _continuous_ notifications and read failing with EAGAIN. Here is a ktrace showing the latter: http://ue.tst.eu/45eb8a3c3e812933cbe3172af2ee4a6c.txt kqueue works well with sockets (or with about anything on netbsd), but fails on more exotic types such as ptys. (I test on Freebsd 6.2 RELEASE, but got reports about problems with earlier and later versions, too, as well as on openbsd (which I didn't verify) and on darwin (which is completely broken)). > You normally don't get useful writeable/readable state for files, No, I only want the same readyness notifications as with select or poll, as is documented in the manpage. (even on platforms where kqueue works this requires some heuristics and workarounds with kqueue due to design limitations (for example problems with close() or fork() that force constant rearming), but thats common in interfaces like kqueue, and by now well understood and handled by libev). > Actually, until recently it was broken on pipes. We've never received > any PRs to that effect so there is no way of knowing. You'll have > better luck asking the author himself. Well, one should better document the types with which it works (which on freebsd apparently includes sockets and nothing else). I also think one should rethink the internal design if every driver needs its own kqueue support, as that will always force kqueue into a second-class citizen not suitable as replacement for select, as it's unreasonable to expect kqueue to just work when its so little used and requires such a high maintainance (linux' epoll for example works fine with everything because it doesn't require drivers to support epoll specifically, so it is unlikely that epoll fails when select would work for example, which is the case on freebsd and darwin). The fact that it works fine on everything I threw at it on netbsd is probably not the result of better design, but more better maintainance, so I wouldn't be surprised if some future version of netbsd failed in similar ways (OTOH, in the past, netbsd consistently was the less buggy platform regardless of topic, wether it was threads, ptys or kqueue, so I might get quite disappointed if that happened :) From owner-freebsd-hackers@FreeBSD.ORG Mon Dec 17 21:54:59 2007 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 37AEF16A419 for ; Mon, 17 Dec 2007 21:54:59 +0000 (UTC) (envelope-from kip.macy@gmail.com) Received: from wa-out-1112.google.com (wa-out-1112.google.com [209.85.146.183]) by mx1.freebsd.org (Postfix) with ESMTP id 0009213C447 for ; Mon, 17 Dec 2007 21:54:58 +0000 (UTC) (envelope-from kip.macy@gmail.com) Received: by wa-out-1112.google.com with SMTP id k17so3745399waf.3 for ; Mon, 17 Dec 2007 13:54:58 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; bh=PiLJrZUG/7Q4r0PQhgaC8pNFOIOv/0ChbjWxmJNTtoI=; b=VG4Vu4xdekNuwx+iHeueXfZRvLoL24F1sr21AX96AFxDJougUO9y/UMQZFYFTEZ84n7Ed9xu3oRDb5aX4KOFEmQYScm0+mlJbyQxkD2ybiPoizsTlRPgyIErNeNbvB0EBZ4rNjkO3Z2/mzrB65ZdKNITiRa8/Lv812rBw4W9TDM= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=jicrl5VhnHLK/zHyy/6/YKXO315tDhn6uul2k6750REpVN/XKUfqgXIc+eG8q1Wu9txLVKW+TKXUtkhcXhetiR93PE0jXZNZY2LEpdDd3KXT4nxUzVhZtexUxo3bQ+T2TBHGxb1T79ydfFXpFNkFQnYxYiT8HvPeOfcJf6Z0Oko= Received: by 10.114.174.2 with SMTP id w2mr3662373wae.17.1197928497138; Mon, 17 Dec 2007 13:54:57 -0800 (PST) Received: by 10.114.255.11 with HTTP; Mon, 17 Dec 2007 13:54:57 -0800 (PST) Message-ID: Date: Mon, 17 Dec 2007 13:54:57 -0800 From: "Kip Macy" To: "James Mansion" In-Reply-To: <4766E92C.6020703@mansionfamily.plus.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <4763A398.2040109@mansionfamily.plus.com> <47644BFE.3060003@elischer.org> <4766E92C.6020703@mansionfamily.plus.com> Cc: freebsd-hackers@freebsd.org, Julian Elischer Subject: Re: kqueue and libev X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 17 Dec 2007 21:54:59 -0000 On Dec 17, 2007 1:25 PM, James Mansion wrote: > Kip Macy wrote: > >> he's just plain misinforme > > Until we know what he is referring to we can't actually say that. > > -Kip > > > > OK he said I could post from our private email so here goes. There were > bits in and around relating to the > Solaris /dev/poll support (and the mechanism's limitations) which I've > elided. > > I think the most telling thing is probably that drivers need to provide > support and that a single mechanism > in the driver doesn't support select and poll at the same time - which I > guess lines up with the reported failure > with USB serial. > > Does kqueue work with USB for example? How about an AIO request to read > from a USB endpoint? > > It may well just be a case of 'fessing up to system limitations. > > James > > ============================================================================ > > Compile and install rxvt-unicode on freebsd and run it with: > > urxvt # works, uses select (or maybe poll) > LIBEV_FLAGS=8 urxvt # acts weird, uses kqueue > > (note: only works when urxvt isn't set[gu]id) > > The typical symptoms are either delayed notificatrions, no notifications at > all or _continuous_ notifications and read failing with EAGAIN. Here is a > ktrace showing the latter: http://ue.tst.eu/45eb8a3c3e812933cbe3172af2ee4a6c.txt > > kqueue works well with sockets (or with about anything on netbsd), but > fails on more exotic types such as ptys. (I test on Freebsd 6.2 RELEASE, > but got reports about problems with earlier and later versions, too, > as well as on openbsd (which I didn't verify) and on darwin (which is > completely broken)). > > > > You normally don't get useful writeable/readable state for files, > > > No, I only want the same readyness notifications as with select or poll, > as is documented in the manpage. (even on platforms where kqueue works > this requires some heuristics and workarounds with kqueue due to design > limitations (for example problems with close() or fork() that force > constant rearming), but thats common in interfaces like kqueue, and by now > well understood and handled by libev). > > > > Actually, until recently it was broken on pipes. We've never received > > any PRs to that effect so there is no way of knowing. You'll have > > better luck asking the author himself. To be more precise, this only manifested itself in erlang. > > Well, one should better document the types with which it works (which on > freebsd apparently includes sockets and nothing else). I also think one > should rethink the internal design if every driver needs its own kqueue > support, as that will always force kqueue into a second-class citizen not > suitable as replacement for select, as it's unreasonable to expect kqueue > to just work when its so little used and requires such a high maintainance > (linux' epoll for example works fine with everything because it doesn't > require drivers to support epoll specifically, so it is unlikely that > epoll fails when select would work for example, which is the case on > freebsd and darwin). > > The fact that it works fine on everything I threw at it on netbsd is > probably not the result of better design, but more better maintainance, so > I wouldn't be surprised if some future version of netbsd failed in similar > ways (OTOH, in the past, netbsd consistently was the less buggy platform > regardless of topic, wether it was threads, ptys or kqueue, so I might get > quite disappointed if that happened :) Interesting, that has been completely counter to my experience. However, I rely on a completely different set of subsystems. Do you have a set of regression tests for libev? It sounds like they would worth having to regression test kqueue. Thanks for your feedback. -Kip From owner-freebsd-hackers@FreeBSD.ORG Mon Dec 17 22:41:05 2007 Return-Path: Delivered-To: freebsd-hackers@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id BEA4B16A4C7 for ; Mon, 17 Dec 2007 22:41:05 +0000 (UTC) (envelope-from jhb@FreeBSD.org) Received: from speedfactory.net (mail6.speedfactory.net [66.23.216.219]) by mx1.freebsd.org (Postfix) with ESMTP id 6C2B513C43E for ; Mon, 17 Dec 2007 22:41:05 +0000 (UTC) (envelope-from jhb@FreeBSD.org) Received: from server.baldwin.cx (unverified [66.23.211.162]) by speedfactory.net (SurgeMail 3.8q) with ESMTP id 224896106-1834499 for multiple; Mon, 17 Dec 2007 17:41:00 -0500 Received: from localhost.corp.yahoo.com (john@localhost [127.0.0.1]) (authenticated bits=0) by server.baldwin.cx (8.13.8/8.13.8) with ESMTP id lBHMeski043178; Mon, 17 Dec 2007 17:40:59 -0500 (EST) (envelope-from jhb@FreeBSD.org) From: John Baldwin To: freebsd-hackers@FreeBSD.org Date: Mon, 17 Dec 2007 15:41:39 -0500 User-Agent: KMail/1.9.6 References: <4D634BCFD1A2144ABECC75FF512D7A9001DF60BE@SKGExch01.marvell.com> <20071207112351.GA6544@eos.sc1.parodius.com> In-Reply-To: <20071207112351.GA6544@eos.sc1.parodius.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200712171541.39959.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH authentication, not delayed by milter-greylist-2.0.2 (server.baldwin.cx [127.0.0.1]); Mon, 17 Dec 2007 17:40:59 -0500 (EST) X-Virus-Scanned: ClamAV 0.91.2/5160/Mon Dec 17 11:46:31 2007 on server.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=-4.4 required=4.2 tests=ALL_TRUSTED,AWL,BAYES_00 autolearn=ham version=3.1.3 X-Spam-Checker-Version: SpamAssassin 3.1.3 (2006-06-01) on server.baldwin.cx Cc: Jeremy Chadwick , Gerald Heinig , Sonja Milicic Subject: Re: Large array in KVM X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 17 Dec 2007 22:41:05 -0000 On Friday 07 December 2007 06:23:51 am Jeremy Chadwick wrote: > On Fri, Dec 07, 2007 at 10:43:00AM +0100, Gerald Heinig wrote: > > Hi Sonja, > > > > > Hi everyone. > > > > > > I'm working on a kernel module that needs to maintain a large > > structure > > > in memory. As this structure could grow too big to be stored in > > memory, > > > it would be good to offload parts of it to the disk. What would be the > > > best way to do this? Could using a memory-mapped file help? > > > > How about implementing your code as a system call, which is called from > > a process that maps a large file into memory, as you suggested above. > > I presume you'd have to handle the question of whether or not your pages > > are in memory yourself, ie. pretty much like any other system call. > > > > Interesting question. > > Somewhat related question: > > What purpose does SYSCALL_MODULE(9) serve? I attempted to use this last > month while writing a kernel module of my own, and was never able to get > it to work for (what understood to be) a couple different reasons: > > 1) There's a maximum # of syscalls permitted (see SYS_MAXSYSCALL in > include/sys/sycall.h), which means a dynamically-allocated syscall via > SYSCALL_MODULE(9) cannot be inserted into the syscalls list. > > 2) The example code in share/examples/kld/syscall/module/syscall.c > specifies the sysent offset as NO_SYSCALL (e.g. -1). You can't pick an > arbitrary number here (from what I could tell), because the kernel > explicitly ensures that the syscall number being called is not larger > than SYS_MAXSYSCALL. This forces you to "steal" a syscall number > between 1 and SYS_MAXSYSCALL, no? -1 tells the kernel to find an unused syscall vector (there are several reserved for this purpose) and assign it for you. You then read the assigned number in userland using modstat(). (You can also get it from your 'offset' variable.. the kernel modifies it in the SYSINIT() invoked by SYSCALL_MODULE() and you could export it via a sysctl, etc.) > 3) I tried using a syscall number (115, deprecated vtrace), using it as > the offset when calling SYSCALL_MODULE, but the userland program calling > syscall(2) returned an error. I didn't research this too thoroughly. syscall_register() will only overwrite a system call whose function pointer is set to lkmnosys() or lkmressys(). -- John Baldwin From owner-freebsd-hackers@FreeBSD.ORG Mon Dec 17 22:50:12 2007 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 11C9416A421 for ; Mon, 17 Dec 2007 22:50:12 +0000 (UTC) (envelope-from james@mansionfamily.plus.com) Received: from ptb-relay03.plus.net (ptb-relay03.plus.net [212.159.14.214]) by mx1.freebsd.org (Postfix) with ESMTP id D4F4E13C465 for ; Mon, 17 Dec 2007 22:50:11 +0000 (UTC) (envelope-from james@mansionfamily.plus.com) Received: from [80.229.150.39] (helo=mansionfamily.plus.com) by ptb-relay03.plus.net with esmtp (Exim) id 1J4Omn-0003OQ-TV for freebsd-hackers@freebsd.org; Mon, 17 Dec 2007 22:50:10 +0000 Received: from [192.168.0.87] ([192.168.0.87]:1990) by mansionfamily.plus.com with [XMail 1.22 ESMTP Server] id for from ; Mon, 17 Dec 2007 22:55:32 -0000 Message-ID: <4766FDA0.9090509@mansionfamily.plus.com> Date: Mon, 17 Dec 2007 22:52:16 +0000 From: James Mansion Organization: MsgWare User-Agent: Thunderbird 2.0.0.0 (Windows/20070326) MIME-Version: 1.0 To: Kip Macy References: <4763A398.2040109@mansionfamily.plus.com> <47644BFE.3060003@elischer.org> <4766E92C.6020703@mansionfamily.plus.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-hackers@freebsd.org, Julian Elischer Subject: Re: kqueue and libev X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 17 Dec 2007 22:50:12 -0000 Kip Macy wrote: > Do you have a set of regression tests for libev? It sounds like they > would worth having to regression test kqueue. > I would have thought that libevent and libev should both the checked against kqueue. Also APR and everything else that has support. I'm not the author of libev though, so I'm the wrong guy to ask. From owner-freebsd-hackers@FreeBSD.ORG Mon Dec 17 23:06:36 2007 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id DDADB16A419 for ; Mon, 17 Dec 2007 23:06:36 +0000 (UTC) (envelope-from fbsd-hackers@mawer.org) Received: from outbound.icp-qv1-irony-out4.iinet.net.au (outbound.icp-qv1-irony-out4.iinet.net.au [203.59.1.150]) by mx1.freebsd.org (Postfix) with ESMTP id 6CCF313C465 for ; Mon, 17 Dec 2007 23:06:36 +0000 (UTC) (envelope-from fbsd-hackers@mawer.org) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AgAAANuIZkfLzq3r/2dsb2JhbAAIqmw X-IronPort-AV: E=Sophos;i="4.24,178,1196607600"; d="scan'208";a="141395154" Received: from unknown (HELO [10.24.1.1]) ([203.206.173.235]) by outbound.icp-qv1-irony-out4.iinet.net.au with ESMTP; 18 Dec 2007 07:37:07 +0900 Message-ID: <4766F9E3.9070304@mawer.org> Date: Tue, 18 Dec 2007 09:36:19 +1100 From: Antony Mawer User-Agent: Thunderbird 2.0.0.9 (Windows/20071031) MIME-Version: 1.0 To: Peter Jeremy References: <1197889622.4766585626a92@webmail.rawbw.com> <20071217180921.GM85797@server.vk2pj.dyndns.org> In-Reply-To: <20071217180921.GM85797@server.vk2pj.dyndns.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Yuri , freebsd-hackers@freebsd.org Subject: Re: Stale mount on disconnected device: how to delete it? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 17 Dec 2007 23:06:36 -0000 On 18/12/2007 5:09 AM, Peter Jeremy wrote: > On Mon, Dec 17, 2007 at 03:07:02AM -0800, Yuri wrote: >> I had USB camera connected and recognized as umass0 and mounted as /mnt/camera >> on /dev/da0s1. >> >> Camera was disconnected while it was still mounted. > > This triggers known and extremely painful to fix bugs in FreeBSD. > Your best work-around is to use ports/emulators/mtools rather than > mount_msdosfs to to access removable devices. Every time this comes up it's branded with the "really hard to fix" message, but I seem to recall the last time this came up Matt Dillon chimed in and said he'd managed to fix it in Dragonfly without too much pain. I had a browse back a while ago at the commits on DF to try and pinpoint the changes that were required to see how practical they were to bring across to FreeBSD; I don't profess to be an expert and have yet to investigate the changes in any detail, but these were the commits I identified: http://freshbsd.org/2007/06/14/03/55/27 http://freshbsd.org/2007/06/17/06/08/52 http://freshbsd.org/2007/06/14/02/09/30 http://freshbsd.org/2007/06/13/21/58/38 http://freshbsd.org/2007/06/13/21/53/39 If someone else is interested in looking at this, it may provide a useful starting point... --Antony From owner-freebsd-hackers@FreeBSD.ORG Tue Dec 18 00:13:57 2007 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id AD9B216A419 for ; Tue, 18 Dec 2007 00:13:57 +0000 (UTC) (envelope-from romain@blogreen.org) Received: from smtp3-g19.free.fr (smtp3-g19.free.fr [212.27.42.29]) by mx1.freebsd.org (Postfix) with ESMTP id 7BEE313C45B for ; Tue, 18 Dec 2007 00:13:57 +0000 (UTC) (envelope-from romain@blogreen.org) Received: from smtp3-g19.free.fr (localhost.localdomain [127.0.0.1]) by smtp3-g19.free.fr (Postfix) with ESMTP id 6C44517B536; Tue, 18 Dec 2007 01:13:56 +0100 (CET) Received: from marvin.blogreen.org (marvin.blogreen.org [82.247.213.140]) by smtp3-g19.free.fr (Postfix) with ESMTP id D015B17B532; Tue, 18 Dec 2007 01:13:55 +0100 (CET) Received: by marvin.blogreen.org (Postfix, from userid 1001) id 6C66D5C053; Tue, 18 Dec 2007 01:13:55 +0100 (CET) Date: Tue, 18 Dec 2007 01:13:55 +0100 From: Romain =?iso-8859-1?Q?Tarti=E8re?= To: Yuri Message-ID: <20071218001355.GA40289@marvin.blogreen.org> Mail-Followup-To: Yuri , freebsd-hackers@freebsd.org References: <1197889622.4766585626a92@webmail.rawbw.com> <1197916368.4766c0d0db6a8@webmail.rawbw.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="Nq2Wo0NMKNjxTN9z" Content-Disposition: inline In-Reply-To: <1197916368.4766c0d0db6a8@webmail.rawbw.com> User-Agent: Mutt/1.4.2.3i Cc: freebsd-hackers@freebsd.org Subject: Re: Stale mount on disconnected device: how to delete it? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 18 Dec 2007 00:13:57 -0000 --Nq2Wo0NMKNjxTN9z Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Dec 17, 2007 at 10:32:48AM -0800, Yuri wrote : > In case of USB device (which device in question in this problem > happens to be) usbd can be used to mount it. >=20 > If attach/detach events trigger mount/unmount commands this problem > shouldn't exist. I didn't try though. The problem is that the detach event can be caught only too late to unmount the device properly. How may it be possible to sync a disk ``as soon as it is detached'' (that is when it is not physically connected to the computer anymore)? Mounting the disk read-only may be a workaround, just as not caching writes (default behaviour of some versions of Windows) and syncing the disk all the time, but this is not as reliable as the mount system provided by Unix and Unix like operating systems. AFAICR, this is the sole weakness of the FreeBSD operating system I know :) And since it is, according to me, an operator error, the best we can do is to use the system as it was designed for ;) Regards, Romain --=20 Romain Tarti=E8re http://romain.blogreen.org/ pgp: 8DAB A124 0DA4 7024 F82A E748 D8E9 A33F FF56 FF43 (ID: 0xFF56FF43) (plain text =3Dnon-HTML=3D PGP/GPG encrypted/signed e-mail much appreciated) --Nq2Wo0NMKNjxTN9z Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4 (FreeBSD) iD8DBQFHZxDD2OmjP/9W/0MRAlwzAJ0Yj6cpBPrY86/bYVcNbwo7HJhI9gCgmdEK /hW7fX2atEgzK6mcsfDqz6M= =f/wW -----END PGP SIGNATURE----- --Nq2Wo0NMKNjxTN9z-- From owner-freebsd-hackers@FreeBSD.ORG Tue Dec 18 00:30:09 2007 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D5E6216A418 for ; Tue, 18 Dec 2007 00:30:09 +0000 (UTC) (envelope-from romain@blogreen.org) Received: from smtp3-g19.free.fr (smtp3-g19.free.fr [212.27.42.29]) by mx1.freebsd.org (Postfix) with ESMTP id 7A20C13C44B for ; Tue, 18 Dec 2007 00:30:09 +0000 (UTC) (envelope-from romain@blogreen.org) Received: from smtp3-g19.free.fr (localhost.localdomain [127.0.0.1]) by smtp3-g19.free.fr (Postfix) with ESMTP id 917A117B53A; Tue, 18 Dec 2007 01:30:08 +0100 (CET) Received: from marvin.blogreen.org (marvin.blogreen.org [82.247.213.140]) by smtp3-g19.free.fr (Postfix) with ESMTP id C776E17B52A; Tue, 18 Dec 2007 01:30:03 +0100 (CET) Received: by marvin.blogreen.org (Postfix, from userid 1001) id 8A63B5C053; Tue, 18 Dec 2007 01:30:03 +0100 (CET) Date: Tue, 18 Dec 2007 01:30:03 +0100 From: Romain =?iso-8859-1?Q?Tarti=E8re?= To: Antony Mawer Message-ID: <20071218003003.GB40289@marvin.blogreen.org> Mail-Followup-To: Antony Mawer , Peter Jeremy , Yuri , freebsd-hackers@freebsd.org References: <1197889622.4766585626a92@webmail.rawbw.com> <20071217180921.GM85797@server.vk2pj.dyndns.org> <4766F9E3.9070304@mawer.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="DKU6Jbt7q3WqK7+M" Content-Disposition: inline In-Reply-To: <4766F9E3.9070304@mawer.org> User-Agent: Mutt/1.4.2.3i Cc: freebsd-hackers@freebsd.org, Yuri Subject: Re: Stale mount on disconnected device: how to delete it? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 18 Dec 2007 00:30:09 -0000 --DKU6Jbt7q3WqK7+M Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hi Antony, On Tue, Dec 18, 2007 at 09:36:19AM +1100, Antony Mawer wrote : > Every time this comes up it's branded with the "really hard to fix" > message, but I seem to recall the last time this came up Matt Dillon > chimed in and said he'd managed to fix it in Dragonfly without too > much pain. >=20 > I had a browse back a while ago at the commits on DF to try and > pinpoint the changes that were required to see how practical they were > to bring across to FreeBSD; I don't profess to be an expert and have > yet to investigate the changes in any detail, but these were the > commits I identified: >=20 > http://freshbsd.org/2007/06/14/03/55/27 > http://freshbsd.org/2007/06/17/06/08/52 > http://freshbsd.org/2007/06/14/02/09/30 > http://freshbsd.org/2007/06/13/21/58/38 > http://freshbsd.org/2007/06/13/21/53/39 >=20 > If someone else is interested in looking at this, it may provide a > useful starting point... First of all, I am not a FreeBSD kernel hacker and thus maybe I am wrong but I think that it is important to recall that DragonflyBSD is ``the logical continuation of the FreeBSD 4.x series'' [1]. As so, it does not provides geom(8) [2], AFAIK. While geom(8) is a really cool piece of code, it also adds many abstraction layers that may have to be adapted to handle such an abnormal situation. This might explain why nobody has already [tried to] fixed this. Maybe somebody from geom@ can give us further details or correct what I wrote? Best regards, Romain References: 1. http://www.dragonflybsd.org/about/history.shtml 2. http://www.freebsd.org/cgi/man.cgi?query=3Dgeom --=20 Romain Tarti=E8re http://romain.blogreen.org/ pgp: 8DAB A124 0DA4 7024 F82A E748 D8E9 A33F FF56 FF43 (ID: 0xFF56FF43) (plain text =3Dnon-HTML=3D PGP/GPG encrypted/signed e-mail much appreciated) --DKU6Jbt7q3WqK7+M Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4 (FreeBSD) iD8DBQFHZxSL2OmjP/9W/0MRAmI1AJ467moDPlcX6cw4I7ReqP/Mig+ZpgCdGwhP IMEvmndimAtonsYQRDsL0EU= =Q2PA -----END PGP SIGNATURE----- --DKU6Jbt7q3WqK7+M-- From owner-freebsd-hackers@FreeBSD.ORG Tue Dec 18 02:16:53 2007 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A520016A41B for ; Tue, 18 Dec 2007 02:16:53 +0000 (UTC) (envelope-from doconnor@gsoft.com.au) Received: from cain.gsoft.com.au (cain.gsoft.com.au [203.31.81.10]) by mx1.freebsd.org (Postfix) with ESMTP id 1556313C45D for ; Tue, 18 Dec 2007 02:16:52 +0000 (UTC) (envelope-from doconnor@gsoft.com.au) Received: from inchoate.gsoft.com.au (inchoate.gsoft.com.au [203.31.81.30]) (authenticated bits=0) by cain.gsoft.com.au (8.13.8/8.13.8) with ESMTP id lBI2Gn8r097100 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 18 Dec 2007 12:46:49 +1030 (CST) (envelope-from doconnor@gsoft.com.au) From: "Daniel O'Connor" To: freebsd-hackers@freebsd.org Date: Tue, 18 Dec 2007 12:46:45 +1030 User-Agent: KMail/1.9.7 References: <200712171626.59808.doconnor@gsoft.com.au> <20071217012757.5210e27c@bhuda.mired.org> In-Reply-To: <20071217012757.5210e27c@bhuda.mired.org> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart5706177.bXzCF7WCmP"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200712181246.46476.doconnor@gsoft.com.au> X-Spam-Score: -3.977 () ALL_TRUSTED,BAYES_00 X-Scanned-By: MIMEDefang 2.58 on 203.31.81.10 Cc: Mike Meyer Subject: Re: Linux version of libusb that works with FreeBSD X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 18 Dec 2007 02:16:53 -0000 --nextPart5706177.bXzCF7WCmP Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Mon, 17 Dec 2007, Mike Meyer wrote: > On Mon, 17 Dec 2007 16:26:58 +1030 "Daniel O'Connor"=20 wrote: > > I am wondering if anyone has tried building such a beast? > > ie a Lunux libusb that will be able to access devices in FreeBSD.. > > Well, the devel/libusb port builds out of the box for me. It's used > by a number of image grabbing tools (gphoto, sane and hplib), and by > tools like nut for talking to UPS systems. I want a *Linux* version of libusb that works on a FreeBSD box under=20 emulation. I have a piece of software for which I can't obtain the source that=20 accesses USB devices with libusb. =2D-=20 Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C --nextPart5706177.bXzCF7WCmP Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4 (FreeBSD) iD8DBQBHZy2O5ZPcIHs/zowRAn1nAKCTKQKVV+4DCx2MTPcoVk7tt3tXswCeL19Y N1bOTI1m+f8kOHPT2oqENaw= =CQUo -----END PGP SIGNATURE----- --nextPart5706177.bXzCF7WCmP-- From owner-freebsd-hackers@FreeBSD.ORG Tue Dec 18 03:44:21 2007 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9D70A16A419 for ; Tue, 18 Dec 2007 03:44:21 +0000 (UTC) (envelope-from binto@triplegate.net.id) Received: from asterix-1.3gate.net (asterix-1.3gate.net [202.127.97.36]) by mx1.freebsd.org (Postfix) with SMTP id C2F3413C442 for ; Tue, 18 Dec 2007 03:44:20 +0000 (UTC) (envelope-from binto@triplegate.net.id) Received: (qmail 39075 invoked by uid 1005); 18 Dec 2007 03:36:12 -0000 Received: from 202.127.97.100 by asterix-1.3gate.net (envelope-from , uid 1003) with qmail-scanner-1.25-st-qms (clamdscan: 0.91.2/4625. perlscan: 1.25-st-qms. Clear:RC:1(202.127.97.100):. Processed in 0.021873 secs); 18 Dec 2007 03:36:12 -0000 X-Antivirus-MY_3GNET-Mail-From: binto@triplegate.net.id via asterix-1.3gate.net X-Antivirus-MY_3GNET: 1.25-st-qms (Clear:RC:1(202.127.97.100):. Processed in 0.021873 secs Process 39069) Received: from smtp.triplegate.net.id (HELO lb1.3gate.net) (202.127.97.100) by asterix-1.3gate.net with SMTP; 18 Dec 2007 03:36:12 -0000 Received: from webmail.triplegate.net.id (unknown [202.127.97.10]) by lb1.3gate.net (Postfix) with ESMTP id E596621105B for ; Tue, 18 Dec 2007 10:40:49 +0700 (WIT) Received: from 202.127.98.144 (SquirrelMail authenticated user binto@triplegate.net.id) by webmail.triplegate.net.id with HTTP; Tue, 18 Dec 2007 10:47:44 +0700 (WIT) Message-ID: <1200.202.127.98.144.1197949664.squirrel@webmail.triplegate.net.id> In-Reply-To: <4766E92C.6020703@mansionfamily.plus.com> References: <4763A398.2040109@mansionfamily.plus.com> <47644BFE.3060003@elischer.org> <4766E92C.6020703@mansionfamily.plus.com> Date: Tue, 18 Dec 2007 10:47:44 +0700 (WIT) From: "binto" To: freebsd-hackers@freebsd.org User-Agent: SquirrelMail/1.4.4 MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-15 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) Importance: Normal Subject: version hwpmc kernel module & pmc library not match X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 18 Dec 2007 03:44:21 -0000 Hi, i run command for kernel profiling purpose: pmcstat -S instructions -O /tmp/sample.out and i get error: pmcstat: ERROR: Initialization of the pmc(3) library failed: No such file or directory I've compile my FreeBSD 6.3-PRERELEASE kernel in i386 machine : device hwpmc options HWPMC_HOOKS myquestion: - any suggestion to fix that error? - how to find what version number of the hwpmc in my machine? - does pmc have version too? Thanks Binto From owner-freebsd-hackers@FreeBSD.ORG Tue Dec 18 03:52:29 2007 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 07A4B16A417 for ; Tue, 18 Dec 2007 03:52:29 +0000 (UTC) (envelope-from kip.macy@gmail.com) Received: from wa-out-1112.google.com (wa-out-1112.google.com [209.85.146.176]) by mx1.freebsd.org (Postfix) with ESMTP id DAF0D13C448 for ; Tue, 18 Dec 2007 03:52:28 +0000 (UTC) (envelope-from kip.macy@gmail.com) Received: by wa-out-1112.google.com with SMTP id k17so3919415waf.3 for ; Mon, 17 Dec 2007 19:52:28 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; bh=vZrTVppk6KGEJptJsYPHHbc0b9Dv1grMTZVYE1KBhkg=; b=ADmdiOzO6qAos4MNqyAzZnUQ6/mP8TJn4/MnGirA6C4MHFP6tjUL/KFrnGwrtET96q7hypUGscdtVFXmC6Wb8D5yI7G10o2wkebXGsZoq4hxYRnW9hWn3JsFSXignAR/qXrqh/v0k5R+HbMKGWyNyTJSUJ1IocIz9ZV2hRK/sIg= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=UnmwUycL4Yuvnr+RPnS0XBobuwUuQUOBviDrUZCMdIH26PNje1e6F5is7wbwAQqqSCG/43nZGH8nCt8ulpgmCc4Kdd3AFhAESOhSV7UpV4hkCovxhXWLFYnnDmQ1nd8f8C6QopP6/wQCNU4cKd+cLDlxvLXxervtTj8kOoMq3ak= Received: by 10.115.54.1 with SMTP id g1mr4455440wak.133.1197949948537; Mon, 17 Dec 2007 19:52:28 -0800 (PST) Received: by 10.114.255.11 with HTTP; Mon, 17 Dec 2007 19:52:28 -0800 (PST) Message-ID: Date: Mon, 17 Dec 2007 19:52:28 -0800 From: "Kip Macy" To: binto In-Reply-To: <1200.202.127.98.144.1197949664.squirrel@webmail.triplegate.net.id> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <4763A398.2040109@mansionfamily.plus.com> <47644BFE.3060003@elischer.org> <4766E92C.6020703@mansionfamily.plus.com> <1200.202.127.98.144.1197949664.squirrel@webmail.triplegate.net.id> Cc: freebsd-hackers@freebsd.org Subject: Re: version hwpmc kernel module & pmc library not match X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 18 Dec 2007 03:52:29 -0000 Check ports 'cpuid' - Vendor ID: "GenuineIntel"; CPUID level 10 Intel-specific functions: Version 000006f6: Type 0 - Original OEM Family 6 - Pentium Pro Model 15 - Extended model 0 Stepping 6 Reserved 0 Odds are you have a post-P4 Intel processor. -Kip On Dec 17, 2007 7:47 PM, binto wrote: > Hi, > > i run command for kernel profiling purpose: > > pmcstat -S instructions -O /tmp/sample.out > > and i get error: > pmcstat: ERROR: Initialization of the pmc(3) library failed: No such file > or directory > > I've compile my FreeBSD 6.3-PRERELEASE kernel in i386 machine : > device hwpmc > options HWPMC_HOOKS > > myquestion: > - any suggestion to fix that error? > - how to find what version number of the hwpmc in my machine? > - does pmc have version too? > > Thanks > Binto > > > > _______________________________________________ > 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 Dec 18 05:04:05 2007 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 599C916A41B for ; Tue, 18 Dec 2007 05:04:05 +0000 (UTC) (envelope-from binto@triplegate.net.id) Received: from outgoing16.3gate.net (outgoing16.3gate.net [202.127.97.16]) by mx1.freebsd.org (Postfix) with SMTP id 92F9613C469 for ; Tue, 18 Dec 2007 05:04:04 +0000 (UTC) (envelope-from binto@triplegate.net.id) Received: (qmail 68109 invoked by uid 1011); 18 Dec 2007 04:56:32 -0000 Received: from 202.127.97.100 by mx2.3gate.net (envelope-from , uid 1009) with qmail-scanner-1.25-st-qms (clamdscan: 0.86.2/1034. spamassassin: 3.0.2. perlscan: 1.25-st-qms. Clear:RC:1(202.127.97.100):. Processed in 0.043695 secs); 18 Dec 2007 04:56:32 -0000 X-Antivirus-3GATE-NET-Mail-From: binto@triplegate.net.id via mx2.3gate.net X-Antivirus-3GATE-NET: 1.25-st-qms (Clear:RC:1(202.127.97.100):. Processed in 0.043695 secs Process 68103) Received: from smtp.triplegate.net.id (HELO lb1.3gate.net) (202.127.97.100) by outgoing16.3gate.net with SMTP; 18 Dec 2007 04:56:32 -0000 Received: from webmail.triplegate.net.id (unknown [202.127.97.10]) by lb1.3gate.net (Postfix) with ESMTP id E06EC21104C; Tue, 18 Dec 2007 12:00:32 +0700 (WIT) Received: from 202.127.98.144 (SquirrelMail authenticated user binto@triplegate.net.id) by webmail.triplegate.net.id with HTTP; Tue, 18 Dec 2007 12:07:27 +0700 (WIT) Message-ID: <1440.202.127.98.144.1197954447.squirrel@webmail.triplegate.net.id> In-Reply-To: References: <4763A398.2040109@mansionfamily.plus.com> <47644BFE.3060003@elischer.org> <4766E92C.6020703@mansionfamily.plus.com> <1200.202.127.98.144.1197949664.squirrel@webmail.triplegate.net.id> Date: Tue, 18 Dec 2007 12:07:27 +0700 (WIT) From: "binto" To: "Kip Macy" User-Agent: SquirrelMail/1.4.4 MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-15 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) Importance: Normal Cc: freebsd-hackers@freebsd.org Subject: Re: version hwpmc kernel module & pmc library not match X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 18 Dec 2007 05:04:05 -0000 check with cpuid: Vendor ID: "GenuineIntel"; CPUID level 10 Intel-specific functions: Version 000006f7: Type 0 - Original OEM Family 6 - Pentium Pro Model 15 - Extended model 0 Stepping 7 Reserved 0 Extended brand string: "Intel(R) Xeon(R) CPU E5335 @ 2.00GHz" CLFLUSH instruction cache line size: 8 Hyper threading siblings: 4 > Check ports 'cpuid' - > > > Vendor ID: "GenuineIntel"; CPUID level 10 > > Intel-specific functions: > Version 000006f6: > Type 0 - Original OEM > Family 6 - Pentium Pro > Model 15 - > Extended model 0 > Stepping 6 > Reserved 0 > > > Odds are you have a post-P4 Intel processor. > > -Kip > > > On Dec 17, 2007 7:47 PM, binto wrote: >> Hi, >> >> i run command for kernel profiling purpose: >> >> pmcstat -S instructions -O /tmp/sample.out >> >> and i get error: >> pmcstat: ERROR: Initialization of the pmc(3) library failed: No such >> file >> or directory >> >> I've compile my FreeBSD 6.3-PRERELEASE kernel in i386 machine : >> device hwpmc >> options HWPMC_HOOKS >> >> myquestion: >> - any suggestion to fix that error? >> - how to find what version number of the hwpmc in my machine? >> - does pmc have version too? >> >> Thanks >> Binto >> >> >> >> _______________________________________________ >> 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" >> > _______________________________________________ > 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 Dec 18 08:34:29 2007 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 32F9D16A420 for ; Tue, 18 Dec 2007 08:34:29 +0000 (UTC) (envelope-from tataz@tataz.chchile.org) Received: from postfix1-g20.free.fr (postfix1-g20.free.fr [212.27.60.42]) by mx1.freebsd.org (Postfix) with ESMTP id D967813C43E for ; Tue, 18 Dec 2007 08:34:28 +0000 (UTC) (envelope-from tataz@tataz.chchile.org) Received: from smtp5-g19.free.fr (smtp5-g19.free.fr [212.27.42.35]) by postfix1-g20.free.fr (Postfix) with ESMTP id 0CD4C2051221 for ; Tue, 18 Dec 2007 09:01:41 +0100 (CET) Received: from smtp5-g19.free.fr (localhost.localdomain [127.0.0.1]) by smtp5-g19.free.fr (Postfix) with ESMTP id A433E3F61BA; Tue, 18 Dec 2007 09:01:39 +0100 (CET) Received: from tatooine.tataz.chchile.org (tataz.chchile.org [82.233.239.98]) by smtp5-g19.free.fr (Postfix) with ESMTP id 84F3A3F61BB; Tue, 18 Dec 2007 09:01:39 +0100 (CET) Received: from obiwan.tataz.chchile.org (unknown [192.168.1.25]) by tatooine.tataz.chchile.org (Postfix) with ESMTP id 483679B497; Tue, 18 Dec 2007 07:59:04 +0000 (UTC) Received: by obiwan.tataz.chchile.org (Postfix, from userid 1000) id 34365405B; Tue, 18 Dec 2007 08:59:04 +0100 (CET) Date: Tue, 18 Dec 2007 08:59:04 +0100 From: Jeremie Le Hen To: "Aryeh M. Friedman" Message-ID: <20071218075904.GC81409@obiwan.tataz.chchile.org> References: <4733E878.2050804@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4733E878.2050804@gmail.com> User-Agent: Mutt/1.5.15 (2007-04-06) Cc: dougb@FreeBSD.org, freebsd-hackers@freebsd.org, freebsd-current@freebsd.org Subject: Re: questions on development(7) X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 18 Dec 2007 08:34:29 -0000 Hi, Sorry for the late reply. On Fri, Nov 09, 2007 at 04:56:24AM +0000, Aryeh M. Friedman wrote: > 4. Mergemaster behaves strange now: everytime I run it does a > buildworld before doing the merge (even if I just did a > installworld)... also it seems to default this to /usr/src2 (which is > most of the time what I want)... is this normal? and if so how do I > turn it off and if I can't how do I set which source tree to use? This is because you're using -m /usr/src2 instead -m /usr/src2/etc. mergemaster(8) isn't well documented for this point. I've written a PR about this and Ruslan Ermilov pointed out he already submitted a better solution to this problem nearly two years ago. Mine: http://www.freebsd.org/cgi/query-pr.cgi?pr=bin/118536 Ruslan's: http://www.freebsd.org/cgi/query-pr.cgi?pr=96528 Regards, -- Jeremie Le Hen < jeremie at le-hen dot org >< ttz at chchile dot org > From owner-freebsd-hackers@FreeBSD.ORG Tue Dec 18 10:38:23 2007 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 918CE16A418 for ; Tue, 18 Dec 2007 10:38:23 +0000 (UTC) (envelope-from ntarmos@ceid.upatras.gr) Received: from poseidon.ceid.upatras.gr (poseidon.ceid.upatras.gr [150.140.141.169]) by mx1.freebsd.org (Postfix) with ESMTP id 005C613C47E for ; Tue, 18 Dec 2007 10:38:22 +0000 (UTC) (envelope-from ntarmos@ceid.upatras.gr) Received: from mail.ceid.upatras.gr (unknown [10.1.0.143]) by poseidon.ceid.upatras.gr (Postfix) with ESMTP id A6352EB464B for ; Tue, 18 Dec 2007 12:38:21 +0200 (EET) Received: from localhost (europa.ceid.upatras.gr [127.0.0.1]) by mail.ceid.upatras.gr (Postfix) with ESMTP id 8F2AC1584F7 for ; Tue, 18 Dec 2007 12:38:21 +0200 (EET) X-Virus-Scanned: amavisd-new at ceid.upatras.gr Received: from mail.ceid.upatras.gr ([127.0.0.1]) by localhost (europa.ceid.upatras.gr [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id r4Q6fJMovhWW for ; Tue, 18 Dec 2007 12:38:21 +0200 (EET) Received: from ace.netcins.ceid.upatras.gr (vfppp079167010077.dsl.hol.gr [79.167.10.77]) by mail.ceid.upatras.gr (Postfix) with ESMTP id 19B1215809E for ; Tue, 18 Dec 2007 12:38:21 +0200 (EET) Received: by ace.netcins.ceid.upatras.gr (Postfix, from userid 1001) id 6E3433F450; Tue, 18 Dec 2007 07:52:01 +0200 (EET) Date: Tue, 18 Dec 2007 07:52:01 +0200 From: Nikos Ntarmos To: freebsd-hackers@freebsd.org Message-ID: <20071218055201.GB51227@ace.netcins.ceid.upatras.gr> Mail-Followup-To: freebsd-hackers@freebsd.org References: <1197889622.4766585626a92@webmail.rawbw.com> <1197916368.4766c0d0db6a8@webmail.rawbw.com> <20071218001355.GA40289@marvin.blogreen.org> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; x-action=pgp-signed Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <20071218001355.GA40289@marvin.blogreen.org> Organization: NetCInS Lab., C.E.I.D., U. of Patras, Greece WWW-Homepage: http://ntarmos.dyndns.org/ X-PGP-Fingerprint: 9680 60A7 DE60 0298 B1F0 9B22 9BA2 7569 CF95 160A Office-Phone: +30-2610-996919 Office-Fax: +30-2610-969011 GPS-Info: 38.31N, 21.82E User-Agent: mutt-ng/devel-r804 (FreeBSD) Subject: Re: Stale mount on disconnected device: how to delete it? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 18 Dec 2007 10:38:23 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Tue, Dec 18, 2007 at 01:13:55AM +0100, Romain Tartière wrote: > On Mon, Dec 17, 2007 at 10:32:48AM -0800, Yuri wrote : > > In case of USB device (which device in question in this problem > > happens to be) usbd can be used to mount it. > > > > If attach/detach events trigger mount/unmount commands this problem > > shouldn't exist. I didn't try though. > > The problem is that the detach event can be caught only too late to > unmount the device properly. How may it be possible to sync a disk > ``as soon as it is detached'' (that is when it is not physically > connected to the computer anymore)? Mounting the disk read-only may > be a workaround, just as not caching writes (default behaviour of some > versions of Windows) and syncing the disk all the time, but this is > not as reliable as the mount system provided by Unix and Unix like > operating systems. > > AFAICR, this is the sole weakness of the FreeBSD operating system I > know :) And since it is, according to me, an operator error, the best > we can do is to use the system as it was designed for ;) Off the top of my head, what is wrong/hard with just logging a device failure, discarding all remaining cached operations, and unmounting the fs when a disk device goes missing? I understand that this is not a viable solution for critical filesystems, but I can see nothing wrong with this approach for removable devices and/or non-critical fs's. Just my $0.02. \n\n -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4 (FreeBSD) Comment: Nikos Ntarmos iD8DBQFHZ2ABm6J1ac+VFgoRAhWtAJ4uomUoe0IDVG0qG2W+t7y9ZSMjugCbBAoz LtIIMhMCk9iZ3NeStO8uwLU= =+o7j -----END PGP SIGNATURE----- From owner-freebsd-hackers@FreeBSD.ORG Tue Dec 18 11:34:06 2007 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 52D3316A418 for ; Tue, 18 Dec 2007 11:34:06 +0000 (UTC) (envelope-from doconnor@gsoft.com.au) Received: from cain.gsoft.com.au (cain.gsoft.com.au [203.31.81.10]) by mx1.freebsd.org (Postfix) with ESMTP id C21BF13C4E9 for ; Tue, 18 Dec 2007 11:34:05 +0000 (UTC) (envelope-from doconnor@gsoft.com.au) Received: from inchoate.gsoft.com.au (ppp121-45-30-69.lns10.adl2.internode.on.net [121.45.30.69]) (authenticated bits=0) by cain.gsoft.com.au (8.13.8/8.13.8) with ESMTP id lBIBXsWZ016256 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 18 Dec 2007 22:03:55 +1030 (CST) (envelope-from doconnor@gsoft.com.au) From: "Daniel O'Connor" To: freebsd-hackers@freebsd.org Date: Tue, 18 Dec 2007 22:03:42 +1030 User-Agent: KMail/1.9.7 References: <1197889622.4766585626a92@webmail.rawbw.com> <20071218001355.GA40289@marvin.blogreen.org> <20071218055201.GB51227@ace.netcins.ceid.upatras.gr> In-Reply-To: <20071218055201.GB51227@ace.netcins.ceid.upatras.gr> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart7090266.mINItEd91n"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200712182203.49414.doconnor@gsoft.com.au> X-Spam-Score: -2.312 () BAYES_00 X-Scanned-By: MIMEDefang 2.58 on 203.31.81.10 Cc: Nikos Ntarmos Subject: Re: Stale mount on disconnected device: how to delete it? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 18 Dec 2007 11:34:06 -0000 --nextPart7090266.mINItEd91n Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Tue, 18 Dec 2007, Nikos Ntarmos wrote: > Off the top of my head, what is wrong/hard with just logging a device > failure, discarding all remaining cached operations, and unmounting > the fs when a disk device goes missing? I understand that this is not > a viable solution for critical filesystems, but I can see nothing > wrong with this approach for removable devices and/or non-critical > fs's. There was a long, long thread which discussed this earlier. It's easy to say what should be done, it's harder to submit patches that=20 clean up the respective failure modes. =2D-=20 Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C --nextPart7090266.mINItEd91n Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4 (FreeBSD) iD8DBQBHZ7Ad5ZPcIHs/zowRArzeAJ4m+0XQGpz9PBei1jYacmjDUyOc/gCfdwS0 DPePtOxwyKrQwIrCU643KEY= =Vg3T -----END PGP SIGNATURE----- --nextPart7090266.mINItEd91n-- From owner-freebsd-hackers@FreeBSD.ORG Tue Dec 18 11:36:28 2007 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 02DBB16A419 for ; Tue, 18 Dec 2007 11:36:28 +0000 (UTC) (envelope-from soralx@cydem.org) Received: from pd2mo3so.prod.shaw.ca (idcmail-mo1so.shaw.ca [24.71.223.10]) by mx1.freebsd.org (Postfix) with ESMTP id C7EBE13C469 for ; Tue, 18 Dec 2007 11:36:27 +0000 (UTC) (envelope-from soralx@cydem.org) Received: from pd3mr1so.prod.shaw.ca (pd3mr1so-qfe3.prod.shaw.ca [10.0.141.177]) by l-daemon (Sun ONE Messaging Server 6.0 HotFix 1.01 (built Mar 15 2004)) with ESMTP id <0JT8007H3TKRK540@l-daemon> for freebsd-hackers@freebsd.org; Tue, 18 Dec 2007 04:36:27 -0700 (MST) Received: from pn2ml2so.prod.shaw.ca ([10.0.121.146]) by pd3mr1so.prod.shaw.ca (Sun Java System Messaging Server 6.2-7.05 (built Sep 5 2006)) with ESMTP id <0JT8004FYTKQNBF0@pd3mr1so.prod.shaw.ca> for freebsd-hackers@freebsd.org; Tue, 18 Dec 2007 04:36:27 -0700 (MST) Received: from soralx ([24.87.3.133]) by l-daemon (Sun Java System Messaging Server 6.2-7.05 (built Sep 5 2006)) with ESMTP id <0JT8000RXTKPJW10@l-daemon> for freebsd-hackers@freebsd.org; Tue, 18 Dec 2007 04:36:26 -0700 (MST) Date: Tue, 18 Dec 2007 03:36:24 -0800 From: soralx@cydem.org In-reply-to: <20071218055201.GB51227@ace.netcins.ceid.upatras.gr> To: freebsd-hackers@freebsd.org Message-id: <20071218033624.2b71bdb5@soralx> MIME-version: 1.0 X-Mailer: Claws Mail 3.0.2 (GTK+ 2.10.14; i386-portbld-freebsd6.2) Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7bit References: <1197889622.4766585626a92@webmail.rawbw.com> <1197916368.4766c0d0db6a8@webmail.rawbw.com> <20071218001355.GA40289@marvin.blogreen.org> <20071218055201.GB51227@ace.netcins.ceid.upatras.gr> Subject: Re: Stale mount on disconnected device: how to delete it? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 18 Dec 2007 11:36:28 -0000 > > The problem is that the detach event can be caught only too late to > > unmount the device properly. How may it be possible to sync a disk > > ``as soon as it is detached'' (that is when it is not physically > > connected to the computer anymore)? Mounting the disk read-only may > > be a workaround, just as not caching writes (default behaviour of > > some versions of Windows) and syncing the disk all the time, but > > this is not as reliable as the mount system provided by Unix and > > Unix like operating systems. > > > > AFAICR, this is the sole weakness of the FreeBSD operating system I > > know :) And since it is, according to me, an operator error, the > > best we can do is to use the system as it was designed for ;) > > Off the top of my head, what is wrong/hard with just logging a device > failure, discarding all remaining cached operations, and unmounting > the fs when a disk device goes missing? I understand that this is not > a viable solution for critical filesystems, but I can see nothing > wrong with this approach for removable devices and/or non-critical > fs's. I was wondering that myself. The possibility of losing data (after some timeout, of course) sure as heck beats recovering from the annoying panicks when something happens with the filesystem's underlying device. And who said those panicks are no problem for production systems? My workstation is a "production system", and it is very hard to recover from reboots in general, and crashes in particular. Unfortunately, they do happen fairly often, usually caused by USB-related stuff (FreeBSD's USB stack is _the_ worst I've seen lately -- I take it that the stack's favorite hobby is panicking the kernel with unrivaled efficiency), sometimes by ATA/ATAPI/SATA (interestingly, SCSI code is quite stable), someimes by something obscure (e.g., just exiting qbittorrent kills the kernel -- NFS woes maybe? just an example). Hot-swapping with some ATA and SCSI drivers is impossible, too (result in panics). I hope you don't mind me, an ol' whiner here, too much, but I really had to say that FreeBSD used to be far more stable. So it seems the trade-off "stability->features" could not be avoided... > Comment: Nikos Ntarmos [SorAlx] ridin' VS1400 From owner-freebsd-hackers@FreeBSD.ORG Tue Dec 18 18:58:58 2007 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1C31016A417 for ; Tue, 18 Dec 2007 18:58:58 +0000 (UTC) (envelope-from dgilbert@daveg.ca) Received: from ox.eicat.ca (ox.eicat.ca [66.96.30.35]) by mx1.freebsd.org (Postfix) with ESMTP id DAB4F13C442 for ; Tue, 18 Dec 2007 18:58:57 +0000 (UTC) (envelope-from dgilbert@daveg.ca) Received: by ox.eicat.ca (Postfix, from userid 66) id 627E6C6B5; Tue, 18 Dec 2007 13:32:01 -0500 (EST) Received: by canoe.dclg.ca (Postfix, from userid 101) id CDC6A61C89; Tue, 18 Dec 2007 13:32:06 -0500 (EST) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <18280.4646.678123.723158@canoe.dclg.ca> Date: Tue, 18 Dec 2007 13:32:06 -0500 To: freebsd-hackers@freebsd.org From: freebsd-list@dclg.ca X-Mailer: VM 7.17 under 21.4 (patch 20) "Double Solitaire" XEmacs Lucid Subject: FreeBSD specific WINE errors X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 18 Dec 2007 18:58:58 -0000 Recently eve-online came out with a new client. Since they now have a "linux" version (which uses TransGaming's Cedega) they are less concerned with wine compatiblity. That said, it seems that some wise people have it working on linux, and I have downloaded, patched and compiled they code they're using. However, the new eve code chucks the following errors on FreeBSD: err:iphlpapi:getRouteTable Received unsupported sockaddr family 0x12 err:iphlpapi:getRouteTable Unexpected address type 0x10 err:iphlpapi:getRouteTable Unexpected address type 0x20 err:ole:CoGetClassObject class {9a5ea990-3034-4d6f-9128-01f3c61022bc} not registered err:ole:CoGetClassObject no class object {9a5ea990-3034-4d6f-9128-01f3c61022bc} could be created for context 0x1 I was hoping some FreeBSD wizards here might recognise what is going wrong here. I'm not sure about the ole object (of if it's important), but the iphlpapi calls --- which I think are the initial http requests that get game news --- are failing and possibly freebsd specific. Dave. -- ============================================================================ |David Gilbert, Independent Contractor. | Two things can be | |Mail: dave@daveg.ca | equal if and only if they | |http://daveg.ca | are precisely opposite. | =========================================================GLO================ From owner-freebsd-hackers@FreeBSD.ORG Tue Dec 18 19:28:52 2007 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7AA3916A419 for ; Tue, 18 Dec 2007 19:28:52 +0000 (UTC) (envelope-from jdc@parodius.com) Received: from mx01.sc1.parodius.com (mx01.sc1.parodius.com [72.20.106.3]) by mx1.freebsd.org (Postfix) with ESMTP id 591A113C4D1 for ; Tue, 18 Dec 2007 19:28:52 +0000 (UTC) (envelope-from jdc@parodius.com) Received: by mx01.sc1.parodius.com (Postfix, from userid 1000) id 5B7AC1CC079; Tue, 18 Dec 2007 11:28:52 -0800 (PST) Date: Tue, 18 Dec 2007 11:28:52 -0800 From: Jeremy Chadwick To: freebsd-list@dclg.ca Message-ID: <20071218192852.GA88889@eos.sc1.parodius.com> References: <18280.4646.678123.723158@canoe.dclg.ca> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <18280.4646.678123.723158@canoe.dclg.ca> User-Agent: Mutt/1.5.16 (2007-06-09) Cc: freebsd-hackers@freebsd.org Subject: Re: FreeBSD specific WINE errors X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 18 Dec 2007 19:28:52 -0000 On Tue, Dec 18, 2007 at 01:32:06PM -0500, freebsd-list@dclg.ca wrote: > Recently eve-online came out with a new client. Since they now have a > "linux" version (which uses TransGaming's Cedega) they are less > concerned with wine compatiblity. That said, it seems that some wise > people have it working on linux, and I have downloaded, patched and > compiled they code they're using. > > However, the new eve code chucks the following errors on FreeBSD: > > err:iphlpapi:getRouteTable Received unsupported sockaddr family 0x12 > err:iphlpapi:getRouteTable Unexpected address type 0x10 > err:iphlpapi:getRouteTable Unexpected address type 0x20 sockaddr family 0x12 (18) is defined in include/sys/socket.h as: #define AF_LINK 18 /* Link layer interface */ I'm completely unfamiliar with Wine (although I am an EVE player! :D ), but my guess is that the Linux EVE client is trying to do something like get a list of IP addresses bound to an interface, or something low-level in the routing table. It's possible that the emulation layer in Wine for FreeBSD lacks this translation. As for the other errors, I'm not sure... -- | Jeremy Chadwick jdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | From owner-freebsd-hackers@FreeBSD.ORG Wed Dec 19 04:41:23 2007 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 95CC916A420 for ; Wed, 19 Dec 2007 04:41:23 +0000 (UTC) (envelope-from atom@smasher.org) Received: from atom.smasher.org (atom.smasher.org [69.55.237.145]) by mx1.freebsd.org (Postfix) with SMTP id 782D113C45B for ; Wed, 19 Dec 2007 04:41:23 +0000 (UTC) (envelope-from atom@smasher.org) Received: (qmail 54239 invoked by uid 1000); 19 Dec 2007 01:32:10 -0000 Message-ID: <20071219013210.54237.qmail@smasher.org> Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Date: Wed, 19 Dec 2007 14:32:08 +1300 (NZDT) From: Atom Smasher In-Reply-To: <20071218033624.2b71bdb5@soralx> MIME-Version: 1.0 OpenPGP: id=0xB88D52E4D9F57808; algo=1 (RSA); size=4096; url=http://atom.smasher.org/pgp.txt References: <1197889622.4766585626a92@webmail.rawbw.com> <1197916368.4766c0d0db6a8@webmail.rawbw.com> <20071218001355.GA40289@marvin.blogreen.org> <20071218055201.GB51227@ace.netcins.ceid.upatras.gr> <20071218033624.2b71bdb5@soralx> To: freebsd-hackers@freebsd.org X-POM: The Moon is Waxing Gibbous (69% of Full) X-Hashcash: 1:20:0712190132:freebsd-hackers@freebsd.org::4dae0hvyStTwlYJd:000000 000000000000000000000000DV29 Subject: Re: Stale mount on disconnected device: how to delete it? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 19 Dec 2007 04:41:23 -0000 On Tue, 18 Dec 2007, soralx@cydem.org wrote: > Unfortunately, they do happen fairly often, usually caused by > USB-related stuff (FreeBSD's USB stack is _the_ worst I've seen lately > -- I take it that the stack's favorite hobby is panicking the kernel > with unrivaled efficiency), sometimes by ATA/ATAPI/SATA (interestingly, > SCSI code is quite stable), someimes by something obscure (e.g., just > exiting qbittorrent kills the kernel -- NFS woes maybe? just an > example). Hot-swapping with some ATA and SCSI drivers is impossible, too > (result in panics). ================== apparently i'm not the only one who had to disable EHCI in order to get ACPI working on a laptop. i'm not a kernel hacker, but how those two are related isn't obvious to me. OHCI works fine, usually ;) -- ...atom ________________________ http://atom.smasher.org/ 762A 3B98 A3C3 96C9 C6B7 582A B88D 52E4 D9F5 7808 ------------------------------------------------- "The law does not allow me to testify on any aspect of the National Security Agency, even to the Senate Intelligence Committee." -- General Allen, Director of the NSA, 1975 From owner-freebsd-hackers@FreeBSD.ORG Wed Dec 19 09:17:19 2007 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3C6E816A418 for ; Wed, 19 Dec 2007 09:17:19 +0000 (UTC) (envelope-from weongyo.jeong@gmail.com) Received: from py-out-1112.google.com (py-out-1112.google.com [64.233.166.182]) by mx1.freebsd.org (Postfix) with ESMTP id 02D1C13C458 for ; Wed, 19 Dec 2007 09:17:17 +0000 (UTC) (envelope-from weongyo.jeong@gmail.com) Received: by py-out-1112.google.com with SMTP id u77so5100349pyb.3 for ; Wed, 19 Dec 2007 01:17:16 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:received:date:to:cc:subject:message-id:mail-followup-to:references:mime-version:content-type:content-disposition:in-reply-to:user-agent:organization:x-operation-sytem:from; bh=xveZhC0tAABx9D1ZakqAjMVHFrgGRerXOewjjO9Ed5s=; b=vsa1b18rN+yPqcRbdy1RPRV5YqIVG3xbMMlXRec4yQ/+H8xkNSb7cjXZ+/7SXmVccfy2YunTuMS4v1mi/KVnGEcNPcy6Tli+Rig/QZ9uv+yRq8lVICFfJTD6v75fMZ0xiet8mXpNgH3FCMlk7/g5thi2dZkw2oIeOQuz87peVRY= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=date:to:cc:subject:message-id:mail-followup-to:references:mime-version:content-type:content-disposition:in-reply-to:user-agent:organization:x-operation-sytem:from; b=po/gd+xtfL7whBj/52DyYQJi1sFLy7dr56dzmG+h3kSONSnp2qMzV8tvHBJ38P1v8kUdsnA1psU7DCNfs++P3kUVATTTOYKO8LjUCoZSmiCk2RpdD8U1Ee4VZNbLpid30cuTjLDkUMh7+L9Nc33Zh7vRWvt6basq8EXuJzKS61A= Received: by 10.35.27.1 with SMTP id e1mr9654809pyj.1.1198054109337; Wed, 19 Dec 2007 00:48:29 -0800 (PST) Received: from freebsd.weongyo.org ( [211.53.35.67]) by mx.google.com with ESMTPS id x72sm20959337pyg.2007.12.19.00.48.25 (version=SSLv3 cipher=OTHER); Wed, 19 Dec 2007 00:48:27 -0800 (PST) Received: by freebsd.weongyo.org (sSMTP sendmail emulation); Wed, 19 Dec 2007 17:48:27 +0900 Date: Wed, 19 Dec 2007 17:48:27 +0900 To: Nils Beyer , jlfreniche Message-ID: <20071219084827.GA84109@freebsd.weongyo.org> Mail-Followup-To: Nils Beyer , jlfreniche , freebsd-hackers@freebsd.org, Andrew Thompson , Sam Leffler , "M. Warner Losh" , Ariff Abdullah References: <000901c7e108$2385d5b0$01081bac@nopwinme> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <000901c7e108$2385d5b0$01081bac@nopwinme> User-Agent: Mutt/1.4.2.3i Organization: CDNetworks. X-Operation-Sytem: FreeBSD From: Weongyo Jeong Cc: freebsd-hackers@freebsd.org, Ariff Abdullah , Andrew Thompson Subject: Re: finished? porting ZyDAS zb1211/zb1211b driver for FreeBSD X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 19 Dec 2007 09:17:19 -0000 On Fri, Aug 17, 2007 at 09:52:26PM +0200, Nils Beyer wrote: > Weongyo Jeong wrote: > >I just finished to port zyd(4) from NetBSD for FreeBSD and it works well > >[...] > >A patch which is for CURRENT is available at [...] > > That's great to read. Is that driver also possible for 6.2-RELEASE and > 6-STABLE? This email is just for your information. Recently, I tried to port zyd(4) driver against RELENG_6 and the result, WIP version, come out here: http://weongyo.org/patches/zyd_RELENG_6-20071219.tar.gz However, this version does not work properly in RELENG_6. When you test this, you will succeed in attaching the device and getting IP address using dhclient(8) but you can see a lot of packet loss. I think that this problem come from the lack of MFCs of ieee80211 framework or USB framework to RELENG_6 because this version works well in CURRENT with small changes. After testing more cases, I will let you know when problems on RELENG_6 are solved. Regards, Weongyo Jeong From owner-freebsd-hackers@FreeBSD.ORG Wed Dec 19 09:43:46 2007 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7F32416A417 for ; Wed, 19 Dec 2007 09:43:46 +0000 (UTC) (envelope-from ntarmos@ceid.upatras.gr) Received: from poseidon.ceid.upatras.gr (poseidon.ceid.upatras.gr [150.140.141.169]) by mx1.freebsd.org (Postfix) with ESMTP id E9C5213C458 for ; Wed, 19 Dec 2007 09:43:45 +0000 (UTC) (envelope-from ntarmos@ceid.upatras.gr) Received: from mail.ceid.upatras.gr (unknown [10.1.0.143]) by poseidon.ceid.upatras.gr (Postfix) with ESMTP id CCD57EB4F92 for ; Wed, 19 Dec 2007 11:43:44 +0200 (EET) Received: from localhost (europa.ceid.upatras.gr [127.0.0.1]) by mail.ceid.upatras.gr (Postfix) with ESMTP id B32B11584E7 for ; Wed, 19 Dec 2007 11:43:44 +0200 (EET) X-Virus-Scanned: amavisd-new at ceid.upatras.gr Received: from mail.ceid.upatras.gr ([127.0.0.1]) by localhost (europa.ceid.upatras.gr [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TasZkHdwTWZ9 for ; Wed, 19 Dec 2007 11:43:44 +0200 (EET) Received: from ace.netcins.ceid.upatras.gr (vfppp079167010077.dsl.hol.gr [79.167.10.77]) by mail.ceid.upatras.gr (Postfix) with ESMTP id 1748F1581C4 for ; Wed, 19 Dec 2007 11:43:44 +0200 (EET) Received: by ace.netcins.ceid.upatras.gr (Postfix, from userid 1001) id 566BB3F454; Wed, 19 Dec 2007 11:37:46 +0200 (EET) Date: Wed, 19 Dec 2007 11:37:46 +0200 From: Nikos Ntarmos To: freebsd-hackers@freebsd.org Message-ID: <20071219093746.GA25058@ace.netcins.ceid.upatras.gr> Mail-Followup-To: freebsd-hackers@freebsd.org References: <1197889622.4766585626a92@webmail.rawbw.com> <20071218001355.GA40289@marvin.blogreen.org> <20071218055201.GB51227@ace.netcins.ceid.upatras.gr> <200712182203.49414.doconnor@gsoft.com.au> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; x-action=pgp-signed Content-Disposition: inline In-Reply-To: <200712182203.49414.doconnor@gsoft.com.au> Organization: NetCInS Lab., C.E.I.D., U. of Patras, Greece WWW-Homepage: http://ntarmos.dyndns.org/ X-PGP-Fingerprint: 9680 60A7 DE60 0298 B1F0 9B22 9BA2 7569 CF95 160A Office-Phone: +30-2610-996919 Office-Fax: +30-2610-969011 GPS-Info: 38.31N, 21.82E User-Agent: mutt-ng/devel-r804 (FreeBSD) Subject: Re: Stale mount on disconnected device: how to delete it? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 19 Dec 2007 09:43:46 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Tue, Dec 18, 2007 at 10:03:42PM +1030, Daniel O'Connor wrote: > On Tue, 18 Dec 2007, Nikos Ntarmos wrote: > > Off the top of my head, what is wrong/hard with just logging a device > > failure, discarding all remaining cached operations, and unmounting > > the fs when a disk device goes missing? I understand that this is not > > a viable solution for critical filesystems, but I can see nothing > > wrong with this approach for removable devices and/or non-critical > > fs's. > > There was a long, long thread which discussed this earlier. > > It's easy to say what should be done, it's harder to submit patches > that clean up the respective failure modes. Point taken. Do you have any pointers to that thread? I did a quick search in hackers@ and current@ but failed to find anything relevant, other than people reporting related crashes and "don't do that, then"-type answers. \n\n -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4 (FreeBSD) Comment: Nikos Ntarmos iD8DBQFHaOZqm6J1ac+VFgoRAs/5AJ9sPZblF1T3MBkDP8K4ycRaFDf9KgCdH3oL u+43/UxmFZnclQvcI4K+Xh8= =E7ue -----END PGP SIGNATURE----- From owner-freebsd-hackers@FreeBSD.ORG Wed Dec 19 23:28:32 2007 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2F25116A417 for ; Wed, 19 Dec 2007 23:28:32 +0000 (UTC) (envelope-from emaste@freebsd.org) Received: from gw.sandvine.com (gw.sandvine.com [199.243.201.138]) by mx1.freebsd.org (Postfix) with ESMTP id E0FF613C447 for ; Wed, 19 Dec 2007 23:28:31 +0000 (UTC) (envelope-from emaste@freebsd.org) Received: from labgw2.phaedrus.sandvine.com ([192.168.3.11]) by gw.sandvine.com with Microsoft SMTPSVC(6.0.3790.3959); Wed, 19 Dec 2007 17:26:22 -0500 Received: by labgw2.phaedrus.sandvine.com (Postfix, from userid 12627) id 1757111711; Wed, 19 Dec 2007 17:26:22 -0500 (EST) Date: Wed, 19 Dec 2007 17:26:21 -0500 From: Ed Maste To: freebsd-hackers@freebsd.org Message-ID: <20071219222621.GA79432@sandvine.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.2.1i X-OriginalArrivalTime: 19 Dec 2007 22:26:22.0353 (UTC) FILETIME=[2F20D810:01C8428E] Subject: config(8) patch for review for src dir handling X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 19 Dec 2007 23:28:32 -0000 I've attached a patch I'd like to commit to config(8) for the way it handles get_srcdir. I'm asking for review since it partially reverts some changes made in revision 1.42 of usr.sbin/config/main.c and I'd like to make sure there are no issues there. Right now config(8) calls realpath("../..", ... to find the src path to write into the kernel Makefile. I want to change this to use $PWD with the last two path components removed, assuming it's the same dir as ../.. . I want to put this in because I often build from an amd(8)-mounted src tree, and realpath produces a path using amd's special temporary mount directory /.amd_mnt/... instead of the intended /host_mounts/... type of path and it times out when accessed that way. Using the logical cwd means that the generated Makefile references /host_mounts/... and amd knows the mount is still in use when building. Comments? -Ed Index: main.c =================================================================== RCS file: /usr/cvs/src/usr.sbin/config/main.c,v retrieving revision 1.76 diff -p -u -r1.76 main.c --- main.c 17 May 2007 04:53:52 -0000 1.76 +++ main.c 18 Dec 2007 21:02:32 -0000 @@ -249,9 +249,30 @@ main(int argc, char **argv) static void get_srcdir(void) { + char *pwd; if (realpath("../..", srcdir) == NULL) errx(2, "Unable to find root of source tree"); + + if ((pwd = getenv("PWD")) != NULL && *pwd == '/' && + (pwd = strdup(pwd))) { + struct stat lg, phy; + int i; + char *p; + + /* remove last two path components */ + for (i = 0; i < 2; i++) { + if ((p = strrchr(pwd, '/')) == NULL) { + free(pwd); + return; + } + *p = '\0'; + } + if (stat(pwd, &lg) != -1 && stat(srcdir, &phy) != -1 && + lg.st_dev == phy.st_dev && lg.st_ino == phy.st_ino) + strlcpy(srcdir, pwd, MAXPATHLEN); + free(pwd); + } } static void From owner-freebsd-hackers@FreeBSD.ORG Thu Dec 20 06:09:22 2007 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9222116A41B for ; Thu, 20 Dec 2007 06:09:22 +0000 (UTC) (envelope-from carl.shapiro@gmail.com) Received: from hs-out-2122.google.com (hs-out-0708.google.com [64.233.178.246]) by mx1.freebsd.org (Postfix) with ESMTP id 4517313C447 for ; Thu, 20 Dec 2007 06:09:22 +0000 (UTC) (envelope-from carl.shapiro@gmail.com) Received: by hs-out-2122.google.com with SMTP id j58so162498hsj.11 for ; Wed, 19 Dec 2007 22:09:21 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; bh=iEa+Va3tg1zQzqwo1mV12iYl7RZ2dJCX6J/xOIllzmM=; b=p7Qfnn8PfHo2uBxiha08DzvF1Jl1fI/4H6dvCoRZgF+zGeH1lHyEF3tIFD2TmJn1kasXNVs/98UovngnKxOEuMXK418Zs73QJesZmMFVgVBnVZ2p7uWApRfH8DI7oPyZFh2Q/vYE/jj8YxELHNmj/fcivJTCLGQ9wa63oSuVnI8= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=Iab1yPEr8HYzdvs958iHXOBznP7f/TTUT2Okek1GpP/3P7KW+I3LZdjmgdYJ3y2xWSwDgL7xRI4dI8RzmtlIJsniFJv464tdB+Cp5nM9sT4aM/efSNUuaJcI4PqlBQZ8/bzsGV/g/SMpXo75WZP+leqVuwV0KtFpg9ggnfp16Ls= Received: by 10.150.196.5 with SMTP id t5mr4002271ybf.109.1198129234640; Wed, 19 Dec 2007 21:40:34 -0800 (PST) Received: by 10.150.200.6 with HTTP; Wed, 19 Dec 2007 21:40:34 -0800 (PST) Message-ID: <4dcb5abd0712192140w29fd39fh53b09fdd4d20e880@mail.gmail.com> Date: Wed, 19 Dec 2007 21:40:34 -0800 From: "Carl Shapiro" To: freebsd-hackers@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline Subject: critical floating point incompatibility X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 20 Dec 2007 06:09:22 -0000 Developers, There is a critical incompatibility between the floating point environment of the 32-bit compatibility environment of AMD64 systems and a genuine i386 system. The default setting of the x87 floating point control word on the i386 port is 0x127F. Among other things, this value sets the precision control to double precision. The default setting of the x87 floating point control word on the AMD64 is 0x37F. This value sets the precision control to double-extended precision. Since the AMD64 port uses SSE2 instructions for single and double precision arithmetic (thereby reserving the x87 for double-extended precision) this is a reasonable setting. Unfortunately, when a 32-bit binary is run under compatibility on an AMD64 system, the floating point control word is 0x37F, not 0x127F. 32-bit binaries do not expect the floating point environment to be in this state. The net effect is that all but the most trivial programs using x87 floating point arithmetic instructions will produce different values when run on a native i386 system than when run under compatibility on a 64-bit system! It seems clear that the right thing to do is to set the floating point environment to the i386 default for i386 binaries. Is the current behavior intended? Carl From owner-freebsd-hackers@FreeBSD.ORG Thu Dec 20 06:25:54 2007 Return-Path: Delivered-To: hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A6C6E16A418 for ; Thu, 20 Dec 2007 06:25:54 +0000 (UTC) (envelope-from imp@bsdimp.com) Received: from harmony.bsdimp.com (bsdimp.com [199.45.160.85]) by mx1.freebsd.org (Postfix) with ESMTP id 6034B13C4CC for ; Thu, 20 Dec 2007 06:25:54 +0000 (UTC) (envelope-from imp@bsdimp.com) Received: from localhost (localhost [127.0.0.1]) by harmony.bsdimp.com (8.14.1/8.14.1) with ESMTP id lBK6MO59007715 for ; Wed, 19 Dec 2007 23:22:24 -0700 (MST) (envelope-from imp@bsdimp.com) Date: Wed, 19 Dec 2007 23:25:11 -0700 (MST) Message-Id: <20071219.232511.-1548301831.imp@bsdimp.com> To: hackers@freebsd.org From: "M. Warner Losh" X-Mailer: Mew version 5.2 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: Subject: Some diffs X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 20 Dec 2007 06:25:54 -0000 Consider the following diffs. The first one does a tiny cleanup of strfile's include style (no real reason other than it bugged me when I added stdint.h). The second one cleans up a minor problem where ${CFLAGS} isn't used where it should be. The next three cleanup the compilation by not assuming sys/types.h is included or by also including And the last, rather long, patch converts the .y in config to a form that more versions of yacc would grok. Comments? Warner ==== //depot/projects/arm/src/games/fortune/strfile/strfile.c#1 - /Users/imp/p4/arm/src/games/fortune/strfile/strfile.c ==== @@ -48,16 +48,17 @@ #include __FBSDID("$FreeBSD: src/games/fortune/strfile/strfile.c,v 1.28 2005/02/17 18:06:37 ru Exp $"); -# include -# include -# include -# include -# include -# include -# include -# include -# include -# include "strfile.h" +#include +#include +#include +#include +#include +#include +#include +#include +#include +#include +#include "strfile.h" /* * This program takes a file composed of strings separated by ==== //depot/projects/arm/src/lib/libmagic/Makefile#2 - /Users/imp/p4/arm/src/lib/libmagic/Makefile ==== @@ -40,8 +40,7 @@ CLEANFILES+= mkmagic build-tools: mkmagic mkmagic: apprentice.c funcs.c magic.c print.c - ${CC} -DHAVE_CONFIG_H -DCOMPILE_ONLY \ - -I${.CURDIR} -I${CONTRDIR} -o ${.TARGET} ${.ALLSRC} + ${CC} -DHAVE_CONFIG_H ${CFLAGS} -o ${.TARGET} ${.ALLSRC} FILEVER!= awk '$$1 == "\#define" && $$2 == "VERSION" { print $$3; exit }' \ ${.CURDIR}/config.h ==== //depot/projects/arm/src/share/mk/bsd.prog.mk#4 - /Users/imp/p4/arm/src/share/mk/bsd.prog.mk ==== @@ -110,17 +110,18 @@ .if defined(PROG) _EXTRADEPEND: -.if defined(LDFLAGS) && !empty(LDFLAGS:M-nostdlib) +.if !defined(FOREIGN_BUILD) .if defined(DPADD) && !empty(DPADD) echo ${PROG}: ${DPADD} >> ${DEPENDFILE} .endif -.else +.if defined(LDFLAGS) && !empty(LDFLAGS:M-nostdlib) echo ${PROG}: ${LIBC} ${DPADD} >> ${DEPENDFILE} .if defined(PROG_CXX) echo ${PROG}: ${LIBSTDCPLUSPLUS} >> ${DEPENDFILE} .endif .endif .endif +.endif .if !target(install) ==== //depot/projects/arm/src/usr.bin/colldef/parse.y#1 - /Users/imp/p4/arm/src/usr.bin/colldef/parse.y ==== @@ -30,6 +30,7 @@ __FBSDID("$FreeBSD: src/usr.bin/colldef/parse.y,v 1.34 2005/05/21 09:55:05 ru Exp $"); #include +#include #include #include #include ==== //depot/projects/arm/src/usr.bin/colldef/scan.l#1 - /Users/imp/p4/arm/src/usr.bin/colldef/scan.l ==== @@ -36,6 +36,7 @@ #include #include #include +#include #include "common.h" #include "y.tab.h" ==== //depot/projects/arm/src/usr.bin/mklocale/ldef.h#1 - /Users/imp/p4/arm/src/usr.bin/mklocale/ldef.h ==== @@ -38,6 +38,7 @@ */ #include +#include /* * This should look a LOT like a _RuneEntry ==== //depot/projects/arm/src/usr.sbin/config/config.y#9 - /Users/imp/p4/arm/src/usr.sbin/config/config.y ==== @@ -95,6 +95,12 @@ void yyerror(const char *s); int yywrap(void); +static void newdev(char *name); +static void newfile(char *name); +static void rmdev_schedule(struct device_head *dh, char *name); +static void newopt(struct opt_head *list, char *name, char *value); +static void rmopt_schedule(struct opt_head *list, char *name); + static char * devopt(char *dev) { @@ -122,14 +128,12 @@ | Config_spec SEMICOLON | - INCLUDE ID SEMICOLON - = { + INCLUDE ID SEMICOLON { if (incignore == 0) include($2, 0); }; | - FILES ID SEMICOLON - = { newfile($2); }; + FILES ID SEMICOLON { newfile($2); }; | SEMICOLON | @@ -137,16 +141,14 @@ ; Config_spec: - ARCH Save_id - = { + ARCH Save_id { if (machinename != NULL && !eq($2, machinename)) errx(1, "%s:%d: only one machine directive is allowed", yyfile, yyline); machinename = $2; machinearch = $2; } | - ARCH Save_id Save_id - = { + ARCH Save_id Save_id { if (machinename != NULL && !(eq($2, machinename) && eq($3, machinearch))) errx(1, "%s:%d: only one machine directive is allowed", @@ -154,15 +156,13 @@ machinename = $2; machinearch = $3; } | - CPU Save_id - = { + CPU Save_id { struct cputype *cp = (struct cputype *)calloc(1, sizeof (struct cputype)); cp->cpu_name = $2; SLIST_INSERT_HEAD(&cputype, cp, cpu_next); } | - NOCPU Save_id - = { + NOCPU Save_id { struct cputype *cp, *cp2; SLIST_FOREACH_SAFE(cp, &cputype, cpu_next, cp2) { if (eq(cp->cpu_name, $2)) { @@ -173,27 +173,20 @@ } | OPTIONS Opt_list | - NOOPTION Save_id - = { rmopt_schedule(&opt, $2); } | + NOOPTION Save_id { rmopt_schedule(&opt, $2); } | MAKEOPTIONS Mkopt_list | - NOMAKEOPTION Save_id - = { rmopt_schedule(&mkopt, $2); } | - IDENT ID - = { ident = $2; } | + NOMAKEOPTION Save_id { rmopt_schedule(&mkopt, $2); } | + IDENT ID { ident = $2; } | System_spec | - MAXUSERS NUMBER - = { maxusers = $2; } | - PROFILE NUMBER - = { profiling = $2; } | - ENV ID - = { + MAXUSERS NUMBER { maxusers = $2; } | + PROFILE NUMBER { profiling = $2; } | + ENV ID { env = $2; envmode = 1; } | - HINTS ID - = { + HINTS ID { struct hint *hint; hint = (struct hint *)calloc(1, sizeof (struct hint)); @@ -203,16 +196,16 @@ } System_spec: - CONFIG System_id System_parameter_list - = { errx(1, "%s:%d: root/dump/swap specifications obsolete", - yyfile, yyline);} + CONFIG System_id System_parameter_list { + errx(1, "%s:%d: root/dump/swap specifications obsolete", + yyfile, yyline); + } | CONFIG System_id ; System_id: - Save_id - = { newopt(&mkopt, ns("KERNEL"), $1); }; + Save_id { newopt(&mkopt, ns("KERNEL"), $1); }; System_parameter_list: System_parameter_list ID @@ -226,23 +219,19 @@ ; Option: - Save_id - = { + Save_id { newopt(&opt, $1, NULL); if (strchr($1, '=') != NULL) errx(1, "%s:%d: The `=' in options should not be " "quoted", yyfile, yyline); } | - Save_id EQUALS Opt_value - = { + Save_id EQUALS Opt_value { newopt(&opt, $1, $3); } ; Opt_value: - ID - = { $$ = $1; } | - NUMBER - = { + ID { $$ = $1; } | + NUMBER { char buf[80]; (void) snprintf(buf, sizeof(buf), "%d", $1); @@ -250,8 +239,7 @@ } ; Save_id: - ID - = { $$ = $1; } + ID { $$ = $1; } ; Mkopt_list: @@ -261,14 +249,11 @@ ; Mkoption: - Save_id - = { newopt(&mkopt, $1, ns("")); } | - Save_id EQUALS Opt_value - = { newopt(&mkopt, $1, $3); } ; + Save_id { newopt(&mkopt, $1, ns("")); } | + Save_id EQUALS Opt_value { newopt(&mkopt, $1, $3); } ; Dev: - ID - = { $$ = $1; } + ID { $$ = $1; } ; Device_spec: @@ -290,16 +275,14 @@ ; Device: - Dev - = { + Dev { newopt(&opt, devopt($1), ns("1")); /* and the device part */ newdev($1); } NoDevice: - Dev - = { + Dev { char *s = devopt($1); rmopt_schedule(&opt, s); From owner-freebsd-hackers@FreeBSD.ORG Thu Dec 20 09:39:53 2007 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0123C16A421 for ; Thu, 20 Dec 2007 09:39:53 +0000 (UTC) (envelope-from peterjeremy@optushome.com.au) Received: from mail13.syd.optusnet.com.au (mail13.syd.optusnet.com.au [211.29.132.194]) by mx1.freebsd.org (Postfix) with ESMTP id 913DD13C4D1 for ; Thu, 20 Dec 2007 09:39:52 +0000 (UTC) (envelope-from peterjeremy@optushome.com.au) Received: from server.vk2pj.dyndns.org (c220-239-20-82.belrs4.nsw.optusnet.com.au [220.239.20.82]) by mail13.syd.optusnet.com.au (8.13.1/8.13.1) with ESMTP id lBK9doOe021068 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 20 Dec 2007 20:39:51 +1100 Received: from server.vk2pj.dyndns.org (localhost.vk2pj.dyndns.org [127.0.0.1]) by server.vk2pj.dyndns.org (8.14.1/8.14.1) with ESMTP id lBK9do1A064871; Thu, 20 Dec 2007 20:39:50 +1100 (EST) (envelope-from peter@server.vk2pj.dyndns.org) Received: (from peter@localhost) by server.vk2pj.dyndns.org (8.14.1/8.14.1/Submit) id lBK9do8X064870; Thu, 20 Dec 2007 20:39:50 +1100 (EST) (envelope-from peter) Date: Thu, 20 Dec 2007 20:39:50 +1100 From: Peter Jeremy To: Carl Shapiro Message-ID: <20071220093950.GA79196@server.vk2pj.dyndns.org> References: <4dcb5abd0712192140w29fd39fh53b09fdd4d20e880@mail.gmail.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="1LKvkjL3sHcu1TtY" Content-Disposition: inline In-Reply-To: <4dcb5abd0712192140w29fd39fh53b09fdd4d20e880@mail.gmail.com> X-PGP-Key: http://members.optusnet.com.au/peterjeremy/pubkey.asc User-Agent: Mutt/1.5.16 (2007-06-09) Cc: freebsd-hackers@freebsd.org Subject: Re: critical floating point incompatibility X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 20 Dec 2007 09:39:53 -0000 --1LKvkjL3sHcu1TtY Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Dec 19, 2007 at 09:40:34PM -0800, Carl Shapiro wrote: >The default setting of the x87 floating point control word on the i386 >port is 0x127F. Among other things, this value sets the precision >control to double precision. The default setting of the x87 floating >point control word on the AMD64 is 0x37F. =2E.. >It seems clear that the right thing to do is to set the floating point >environment to the i386 default for i386 binaries. Is the current >behavior intended? I believe this is an oversight. See the thread beginning http://lists.freebsd.org/pipermail/freebsd-stable/2007-November/037947.html --=20 Peter Jeremy Please excuse any delays as the result of my ISP's inability to implement an MTA that is either RFC2821-compliant or matches their claimed behaviour. --1LKvkjL3sHcu1TtY Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4 (FreeBSD) iD8DBQFHajhm/opHv/APuIcRAjO0AJ94i7/KSBCDcQrzJ+QVhVOC4I/4jACfWTJB Nio6tr4HQ50r6Kc6slvbJ4U= =e1// -----END PGP SIGNATURE----- --1LKvkjL3sHcu1TtY-- From owner-freebsd-hackers@FreeBSD.ORG Thu Dec 20 12:02:36 2007 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 61FEC16A41B for ; Thu, 20 Dec 2007 12:02:36 +0000 (UTC) (envelope-from idiotbg@gmail.com) Received: from v4.rz.uni-leipzig.de (v4.rz.uni-leipzig.de [139.18.1.30]) by mx1.freebsd.org (Postfix) with ESMTP id E277F13C4E5 for ; Thu, 20 Dec 2007 12:02:35 +0000 (UTC) (envelope-from idiotbg@gmail.com) Received: from localhost (localhost [127.0.0.1]) by v4.rz.uni-leipzig.de (Postfix) with ESMTP id C56331C8B72 for ; Thu, 20 Dec 2007 12:32:35 +0100 (CET) X-Virus-Scanned: by amavisd-new at v4-ul Received: from v4.rz.uni-leipzig.de ([127.0.0.1]) by localhost (v4.rz.uni-leipzig.de [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id t8ZxJbsSGSHM for ; Thu, 20 Dec 2007 12:32:35 +0100 (CET) Received: from v1.rz.uni-leipzig.de (v1.rz.uni-leipzig.de [139.18.1.26]) by v4.rz.uni-leipzig.de (Postfix) with ESMTP id AF2B01C8B3A for ; Thu, 20 Dec 2007 12:32:35 +0100 (CET) Received: from localhost (localhost [127.0.0.1]) by v1.rz.uni-leipzig.de (Postfix) with ESMTP id F0CC218F39; Thu, 20 Dec 2007 12:32:33 +0100 (CET) X-Virus-Scanned: by amavisd-new at v1-ul Received: from v1.rz.uni-leipzig.de ([127.0.0.1]) by localhost (v1.rz.uni-leipzig.de [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GW9+VAQ6gnyA; Thu, 20 Dec 2007 12:32:33 +0100 (CET) Received: from server1.rz.uni-leipzig.de (server1.rz.uni-leipzig.de [139.18.1.1]) by v1.rz.uni-leipzig.de (Postfix) with ESMTP id D65F615A22; Thu, 20 Dec 2007 12:32:33 +0100 (CET) Received: from a144026.studnetz.uni-leipzig.de (a144026.studnetz.uni-leipzig.de [139.18.144.26]) by server1.rz.uni-leipzig.de (Postfix) with ESMTP id C3534390B; Thu, 20 Dec 2007 12:32:33 +0100 (CET) From: Momchil Ivanov To: freebsd-hackers@freebsd.org Date: Thu, 20 Dec 2007 12:32:28 +0100 User-Agent: KMail/1.9.7 References: <1197889622.4766585626a92@webmail.rawbw.com> <200712182203.49414.doconnor@gsoft.com.au> <20071219093746.GA25058@ace.netcins.ceid.upatras.gr> In-Reply-To: <20071219093746.GA25058@ace.netcins.ceid.upatras.gr> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart7218858.jXPSmK1Wgj"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200712201232.32511.idiotbg@gmail.com> Cc: Nikos Ntarmos Subject: Re: Stale mount on disconnected device: how to delete it? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 20 Dec 2007 12:02:36 -0000 --nextPart7218858.jXPSmK1Wgj Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline =D0=9D=D0=B0 Wednesday 19 December 2007 10:37:46 Nikos Ntarmos =D0=BD=D0=B0= =D0=BF=D0=B8=D1=81=D0=B0: > Do you have any pointers to that thread? I did a quick search in > hackers@ and current@ but failed to find anything relevant, other than > people reporting related crashes and "don't do that, then"-type answers. I started a thread a while ago, when I`ve experienced the same problem. The= =20 title is 'removing external usb hdd without unmounting causes reboot?' and = it=20 was on -stable. Somebody there pointed out some patches on a russian websit= e,=20 but I`ve never tested them. =2D-=20 This correspondence is strictly confidential. Any screening, filtering and/or production for the purpose of public or otherwise disclosure is forbidden without written permission by the author signed above. If you are not the intended recipient, please immediately notify the sender and permanently delete any copies PGP KeyID: 0x3118168B Keyserver: pgp.mit.edu Key fingerprint BB50 2983 0714 36DC D02E =C2=A0158A E03D 56DA 3118 168B =20 --nextPart7218858.jXPSmK1Wgj Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (FreeBSD) iD8DBQBHalLM4D1W2jEYFosRAkOYAKCBv/hpAPKa+pxARSs82T+M8ZBTAwCgn/Ep wb02CDn2qVCDgD7ZBxjRz3k= =Mn+r -----END PGP SIGNATURE----- --nextPart7218858.jXPSmK1Wgj-- From owner-freebsd-hackers@FreeBSD.ORG Thu Dec 20 13:48:39 2007 Return-Path: Delivered-To: freebsd-hackers@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 60BA916A419 for ; Thu, 20 Dec 2007 13:48:39 +0000 (UTC) (envelope-from tataz@tataz.chchile.org) Received: from smtp5-g19.free.fr (smtp5-g19.free.fr [212.27.42.35]) by mx1.freebsd.org (Postfix) with ESMTP id F38A513C4CC for ; Thu, 20 Dec 2007 13:48:38 +0000 (UTC) (envelope-from tataz@tataz.chchile.org) Received: from smtp5-g19.free.fr (localhost.localdomain [127.0.0.1]) by smtp5-g19.free.fr (Postfix) with ESMTP id 4EFE43F61BF for ; Thu, 20 Dec 2007 14:48:37 +0100 (CET) Received: from tatooine.tataz.chchile.org (tataz.chchile.org [82.233.239.98]) by smtp5-g19.free.fr (Postfix) with ESMTP id 24FFE3F616F for ; Thu, 20 Dec 2007 14:48:37 +0100 (CET) Received: from obiwan.tataz.chchile.org (unknown [192.168.1.25]) by tatooine.tataz.chchile.org (Postfix) with ESMTP id 2EC7D9B497 for ; Thu, 20 Dec 2007 13:45:57 +0000 (UTC) Received: by obiwan.tataz.chchile.org (Postfix, from userid 1000) id 1ADB1405B; Thu, 20 Dec 2007 14:45:57 +0100 (CET) Date: Thu, 20 Dec 2007 14:45:57 +0100 From: Jeremie Le Hen To: freebsd-hackers@FreeBSD.org Message-ID: <20071220134557.GB35586@obiwan.tataz.chchile.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.15 (2007-04-06) Cc: Subject: GCC generated assembly X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 20 Dec 2007 13:48:39 -0000 Hi list, This mail is slightly off-topic because probably not FreeBSD-centric. I've looked at the assembly code generated by GCC, but I am not able to understand the point of every instruction. I've written the following useless program: % #include % % int % main(int ac, char *av[]) % { % char buf[16]; % % if (ac < 2) % return 0; % strcpy(buf, av[1]); % return 1; % } Theorically, the main() function should be something like this: % push %ebp % mov %esp, %ebp % sub $16, %esp % cmp $1, 8(%ebp) % jle .byebye % mov 12(%ebp), %eax % push 4(%eax) % push -16(%ebp) % call strcpy % byebye: % leave % ret So the stack would look like this when calling strcpy() : | av | | ac | | ret | | old ebp| <- ebp [ ] [ ] [ buf ] [ ] | av[1] | | &buf | <- esp On RELENG_6, with GCC 3.4.6, I get the following assembly: % aristote# gcc -S -O vuln.c % aristote# cat vuln.s % .file "vuln.c" % .text % .p2align 2,,3 % .globl main % .type main, @function % main: % pushl %ebp % movl %esp, %ebp % subl $24, %esp % andl $-16, %esp % subl $16, %esp % movl $0, %eax % cmpl $1, 8(%ebp) % jle .L1 % subl $8, %esp % movl 12(%ebp), %eax % pushl 4(%eax) % leal -24(%ebp), %eax % pushl %eax % call strcpy % movl $1, %eax % .L1: % leave % ret % .size main, .-main % .ident "GCC: (GNU) 3.4.6 [FreeBSD] 20060305" While it works, it seems to waste much space on the stack : | av | | ac | | ret | | old ebp| <- ebp { } { } {24 bytes} { (buf1) } { } { } # There could be more space between the two [ ] # buffers because of alignment on 16 bytes. [16 bytes] [ (buf2) ] [ ] { 8 bytes} { (buf3) } | av[1] | | &buf1 | <- esp Is someone able to explain this please? Interestingly, if I change the buffer size from 16 to 32 bytes, buf1 is 40 bytes wide while the two others keep the same size. I've tried with GCC 2.95.3 from ports. Stackwise the differences are: - buf2 doesn't exist - while buf1 is still 24 bytes long, the value passed to strcpy() is buf1 + 8: % leal -16(%ebp),%eax % pushl %eax I will follow up with RELENG_7 GCC 4.2.1 output. Thank you. Regards, -- Jeremie Le Hen < jeremie at le-hen dot org >< ttz at chchile dot org > From owner-freebsd-hackers@FreeBSD.ORG Thu Dec 20 19:38:58 2007 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4B5EB16A418 for ; Thu, 20 Dec 2007 19:38:58 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from speedfactory.net (mail6.speedfactory.net [66.23.216.219]) by mx1.freebsd.org (Postfix) with ESMTP id CC0D013C507 for ; Thu, 20 Dec 2007 19:38:57 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from server.baldwin.cx (unverified [66.23.211.162]) by speedfactory.net (SurgeMail 3.8q) with ESMTP id 225317978-1834499 for multiple; Thu, 20 Dec 2007 14:37:03 -0500 Received: from localhost.corp.yahoo.com (john@localhost [127.0.0.1]) (authenticated bits=0) by server.baldwin.cx (8.13.8/8.13.8) with ESMTP id lBKJcsl7077483; Thu, 20 Dec 2007 14:38:54 -0500 (EST) (envelope-from jhb@freebsd.org) From: John Baldwin To: freebsd-hackers@freebsd.org Date: Thu, 20 Dec 2007 13:46:55 -0500 User-Agent: KMail/1.9.6 References: <20071219.232511.-1548301831.imp@bsdimp.com> In-Reply-To: <20071219.232511.-1548301831.imp@bsdimp.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200712201346.55717.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH authentication, not delayed by milter-greylist-2.0.2 (server.baldwin.cx [127.0.0.1]); Thu, 20 Dec 2007 14:38:54 -0500 (EST) X-Virus-Scanned: ClamAV 0.91.2/5192/Thu Dec 20 12:24:15 2007 on server.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=-4.4 required=4.2 tests=ALL_TRUSTED,AWL,BAYES_00 autolearn=ham version=3.1.3 X-Spam-Checker-Version: SpamAssassin 3.1.3 (2006-06-01) on server.baldwin.cx Cc: hackers@freebsd.org Subject: Re: Some diffs X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 20 Dec 2007 19:38:58 -0000 On Thursday 20 December 2007 01:25:11 am M. Warner Losh wrote: > Consider the following diffs. The first one does a tiny cleanup of > strfile's include style (no real reason other than it bugged me when I > added stdint.h). > > The second one cleans up a minor problem where ${CFLAGS} isn't used > where it should be. > > The next three cleanup the compilation by not assuming sys/types.h is > included or by also including These all seem fine to me. > And the last, rather long, patch converts the .y in config to a form > that more versions of yacc would grok. I have no yacc-clue. > Comments? Was the bsd.prog.mk change accidentally included? > ==== //depot/projects/arm/src/share/mk/bsd.prog.mk#4 - /Users/imp/p4/arm/src/share/mk/bsd.prog.mk ==== > @@ -110,17 +110,18 @@ > > .if defined(PROG) > _EXTRADEPEND: > -.if defined(LDFLAGS) && !empty(LDFLAGS:M-nostdlib) > +.if !defined(FOREIGN_BUILD) > .if defined(DPADD) && !empty(DPADD) > echo ${PROG}: ${DPADD} >> ${DEPENDFILE} > .endif > -.else > +.if defined(LDFLAGS) && !empty(LDFLAGS:M-nostdlib) > echo ${PROG}: ${LIBC} ${DPADD} >> ${DEPENDFILE} > .if defined(PROG_CXX) > echo ${PROG}: ${LIBSTDCPLUSPLUS} >> ${DEPENDFILE} > .endif > .endif > .endif > +.endif > > .if !target(install) -- John Baldwin From owner-freebsd-hackers@FreeBSD.ORG Thu Dec 20 19:55:14 2007 Return-Path: Delivered-To: hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 84BCB16A468 for ; Thu, 20 Dec 2007 19:55:14 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from speedfactory.net (mail6.speedfactory.net [66.23.216.219]) by mx1.freebsd.org (Postfix) with ESMTP id 29C7913C4E8 for ; Thu, 20 Dec 2007 19:55:13 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from server.baldwin.cx (unverified [66.23.211.162]) by speedfactory.net (SurgeMail 3.8q) with ESMTP id 225317978-1834499 for multiple; Thu, 20 Dec 2007 14:37:03 -0500 Received: from localhost.corp.yahoo.com (john@localhost [127.0.0.1]) (authenticated bits=0) by server.baldwin.cx (8.13.8/8.13.8) with ESMTP id lBKJcsl7077483; Thu, 20 Dec 2007 14:38:54 -0500 (EST) (envelope-from jhb@freebsd.org) From: John Baldwin To: freebsd-hackers@freebsd.org Date: Thu, 20 Dec 2007 13:46:55 -0500 User-Agent: KMail/1.9.6 References: <20071219.232511.-1548301831.imp@bsdimp.com> In-Reply-To: <20071219.232511.-1548301831.imp@bsdimp.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200712201346.55717.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH authentication, not delayed by milter-greylist-2.0.2 (server.baldwin.cx [127.0.0.1]); Thu, 20 Dec 2007 14:38:54 -0500 (EST) X-Virus-Scanned: ClamAV 0.91.2/5192/Thu Dec 20 12:24:15 2007 on server.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=-4.4 required=4.2 tests=ALL_TRUSTED,AWL,BAYES_00 autolearn=ham version=3.1.3 X-Spam-Checker-Version: SpamAssassin 3.1.3 (2006-06-01) on server.baldwin.cx Cc: hackers@freebsd.org Subject: Re: Some diffs X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 20 Dec 2007 19:55:14 -0000 On Thursday 20 December 2007 01:25:11 am M. Warner Losh wrote: > Consider the following diffs. The first one does a tiny cleanup of > strfile's include style (no real reason other than it bugged me when I > added stdint.h). > > The second one cleans up a minor problem where ${CFLAGS} isn't used > where it should be. > > The next three cleanup the compilation by not assuming sys/types.h is > included or by also including These all seem fine to me. > And the last, rather long, patch converts the .y in config to a form > that more versions of yacc would grok. I have no yacc-clue. > Comments? Was the bsd.prog.mk change accidentally included? > ==== //depot/projects/arm/src/share/mk/bsd.prog.mk#4 - /Users/imp/p4/arm/src/share/mk/bsd.prog.mk ==== > @@ -110,17 +110,18 @@ > > .if defined(PROG) > _EXTRADEPEND: > -.if defined(LDFLAGS) && !empty(LDFLAGS:M-nostdlib) > +.if !defined(FOREIGN_BUILD) > .if defined(DPADD) && !empty(DPADD) > echo ${PROG}: ${DPADD} >> ${DEPENDFILE} > .endif > -.else > +.if defined(LDFLAGS) && !empty(LDFLAGS:M-nostdlib) > echo ${PROG}: ${LIBC} ${DPADD} >> ${DEPENDFILE} > .if defined(PROG_CXX) > echo ${PROG}: ${LIBSTDCPLUSPLUS} >> ${DEPENDFILE} > .endif > .endif > .endif > +.endif > > .if !target(install) -- John Baldwin From owner-freebsd-hackers@FreeBSD.ORG Thu Dec 20 20:02:00 2007 Return-Path: Delivered-To: hackers@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 180C916A41A; Thu, 20 Dec 2007 20:02:00 +0000 (UTC) (envelope-from imp@bsdimp.com) Received: from harmony.bsdimp.com (bsdimp.com [199.45.160.85]) by mx1.freebsd.org (Postfix) with ESMTP id C71B713C461; Thu, 20 Dec 2007 20:01:59 +0000 (UTC) (envelope-from imp@bsdimp.com) Received: from localhost (localhost [127.0.0.1]) by harmony.bsdimp.com (8.14.1/8.14.1) with ESMTP id lBKJvwBD022222; Thu, 20 Dec 2007 12:57:58 -0700 (MST) (envelope-from imp@bsdimp.com) Date: Thu, 20 Dec 2007 13:00:54 -0700 (MST) Message-Id: <20071220.130054.-660390386.imp@bsdimp.com> To: jhb@FreeBSD.org From: "M. Warner Losh" In-Reply-To: <200712201346.55717.jhb@freebsd.org> References: <20071219.232511.-1548301831.imp@bsdimp.com> <200712201346.55717.jhb@freebsd.org> X-Mailer: Mew version 5.2 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, hackers@FreeBSD.org Subject: Re: Some diffs X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 20 Dec 2007 20:02:00 -0000 In message: <200712201346.55717.jhb@freebsd.org> John Baldwin writes: : Was the bsd.prog.mk change accidentally included? : : > ==== //depot/projects/arm/src/share/mk/bsd.prog.mk#4 - /Users/imp/p4/arm/src/share/mk/bsd.prog.mk ==== : > @@ -110,17 +110,18 @@ : > : > .if defined(PROG) : > _EXTRADEPEND: : > -.if defined(LDFLAGS) && !empty(LDFLAGS:M-nostdlib) : > +.if !defined(FOREIGN_BUILD) : > .if defined(DPADD) && !empty(DPADD) : > echo ${PROG}: ${DPADD} >> ${DEPENDFILE} : > .endif : > -.else : > +.if defined(LDFLAGS) && !empty(LDFLAGS:M-nostdlib) : > echo ${PROG}: ${LIBC} ${DPADD} >> ${DEPENDFILE} : > .if defined(PROG_CXX) : > echo ${PROG}: ${LIBSTDCPLUSPLUS} >> ${DEPENDFILE} : > .endif : > .endif : > .endif : > +.endif : > : > .if !target(install) FreeBSD's build systems assumes bad things. This is one nobody has noticed. Even when compiling purely dynamic, it tries to create a .depend file with libc.a... Or any .a for that matter. OS X doesn't have any .a's to speak of, so this was failing. It is part of another change that tries to hack together enough of an environment to make things build under OS X, but I hit the wall in binutils and need to rethink my approach. Warner From owner-freebsd-hackers@FreeBSD.ORG Thu Dec 20 20:02:00 2007 Return-Path: Delivered-To: freebsd-hackers@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 180C916A41A; Thu, 20 Dec 2007 20:02:00 +0000 (UTC) (envelope-from imp@bsdimp.com) Received: from harmony.bsdimp.com (bsdimp.com [199.45.160.85]) by mx1.freebsd.org (Postfix) with ESMTP id C71B713C461; Thu, 20 Dec 2007 20:01:59 +0000 (UTC) (envelope-from imp@bsdimp.com) Received: from localhost (localhost [127.0.0.1]) by harmony.bsdimp.com (8.14.1/8.14.1) with ESMTP id lBKJvwBD022222; Thu, 20 Dec 2007 12:57:58 -0700 (MST) (envelope-from imp@bsdimp.com) Date: Thu, 20 Dec 2007 13:00:54 -0700 (MST) Message-Id: <20071220.130054.-660390386.imp@bsdimp.com> To: jhb@FreeBSD.org From: "M. Warner Losh" In-Reply-To: <200712201346.55717.jhb@freebsd.org> References: <20071219.232511.-1548301831.imp@bsdimp.com> <200712201346.55717.jhb@freebsd.org> X-Mailer: Mew version 5.2 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, hackers@FreeBSD.org Subject: Re: Some diffs X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 20 Dec 2007 20:02:00 -0000 In message: <200712201346.55717.jhb@freebsd.org> John Baldwin writes: : Was the bsd.prog.mk change accidentally included? : : > ==== //depot/projects/arm/src/share/mk/bsd.prog.mk#4 - /Users/imp/p4/arm/src/share/mk/bsd.prog.mk ==== : > @@ -110,17 +110,18 @@ : > : > .if defined(PROG) : > _EXTRADEPEND: : > -.if defined(LDFLAGS) && !empty(LDFLAGS:M-nostdlib) : > +.if !defined(FOREIGN_BUILD) : > .if defined(DPADD) && !empty(DPADD) : > echo ${PROG}: ${DPADD} >> ${DEPENDFILE} : > .endif : > -.else : > +.if defined(LDFLAGS) && !empty(LDFLAGS:M-nostdlib) : > echo ${PROG}: ${LIBC} ${DPADD} >> ${DEPENDFILE} : > .if defined(PROG_CXX) : > echo ${PROG}: ${LIBSTDCPLUSPLUS} >> ${DEPENDFILE} : > .endif : > .endif : > .endif : > +.endif : > : > .if !target(install) FreeBSD's build systems assumes bad things. This is one nobody has noticed. Even when compiling purely dynamic, it tries to create a .depend file with libc.a... Or any .a for that matter. OS X doesn't have any .a's to speak of, so this was failing. It is part of another change that tries to hack together enough of an environment to make things build under OS X, but I hit the wall in binutils and need to rethink my approach. Warner From owner-freebsd-hackers@FreeBSD.ORG Thu Dec 20 21:41:05 2007 Return-Path: Delivered-To: hackers@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 637B416A418 for ; Thu, 20 Dec 2007 21:41:05 +0000 (UTC) (envelope-from imp@bsdimp.com) Received: from harmony.bsdimp.com (bsdimp.com [199.45.160.85]) by mx1.freebsd.org (Postfix) with ESMTP id 0E17E13C448 for ; Thu, 20 Dec 2007 21:41:04 +0000 (UTC) (envelope-from imp@bsdimp.com) Received: from localhost (localhost [127.0.0.1]) by harmony.bsdimp.com (8.14.1/8.14.1) with ESMTP id lBKLaKJq023403; Thu, 20 Dec 2007 14:36:20 -0700 (MST) (envelope-from imp@bsdimp.com) Date: Thu, 20 Dec 2007 14:39:17 -0700 (MST) Message-Id: <20071220.143917.635806033.imp@bsdimp.com> To: dds@aueb.gr From: "M. Warner Losh" In-Reply-To: <476AE053.5060103@aueb.gr> References: <20071219.232511.-1548301831.imp@bsdimp.com> <476AE053.5060103@aueb.gr> X-Mailer: Mew version 5.2 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: hackers@FreeBSD.ORG Subject: Re: Some diffs X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 20 Dec 2007 21:41:05 -0000 In message: <476AE053.5060103@aueb.gr> Diomidis Spinellis writes: : M. Warner Losh wrote: : > And the last, rather long, patch converts the .y in config to a form : > that more versions of yacc would grok. : > : > Comments? : [...] : > - INCLUDE ID SEMICOLON : > - = { : > + INCLUDE ID SEMICOLON { : [...] : : The = { way for specifying yacc actions is item 5 in yacc's Appendix D : titled "Old Features Supported but not Encouraged" in the Seventh : Edition Unix Programmer's Manual (January, 1979). I believe it's now : time to make the switch. Thanks! We can't switch until the feature has been deprecated for 30 years or more, right? Warner From owner-freebsd-hackers@FreeBSD.ORG Thu Dec 20 21:56:58 2007 Return-Path: Delivered-To: hackers@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 56D7C16A41A for ; Thu, 20 Dec 2007 21:56:58 +0000 (UTC) (envelope-from julian@elischer.org) Received: from outY.internet-mail-service.net (outY.internet-mail-service.net [216.240.47.248]) by mx1.freebsd.org (Postfix) with ESMTP id 3E89213C468 for ; Thu, 20 Dec 2007 21:56:58 +0000 (UTC) (envelope-from julian@elischer.org) Received: from mx0.idiom.com (HELO idiom.com) (216.240.32.160) by out.internet-mail-service.net (qpsmtpd/0.40) with ESMTP; Thu, 20 Dec 2007 13:56:57 -0800 Received: from julian-mac.elischer.org (localhost [127.0.0.1]) by idiom.com (Postfix) with ESMTP id 33425126D46; Thu, 20 Dec 2007 13:56:57 -0800 (PST) Message-ID: <476AE528.2020306@elischer.org> Date: Thu, 20 Dec 2007 13:56:56 -0800 From: Julian Elischer User-Agent: Thunderbird 2.0.0.9 (Macintosh/20071031) MIME-Version: 1.0 To: "M. Warner Losh" References: <20071219.232511.-1548301831.imp@bsdimp.com> <476AE053.5060103@aueb.gr> <20071220.143917.635806033.imp@bsdimp.com> In-Reply-To: <20071220.143917.635806033.imp@bsdimp.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: dds@aueb.gr, hackers@FreeBSD.ORG Subject: Re: Some diffs X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 20 Dec 2007 21:56:58 -0000 M. Warner Losh wrote: > In message: <476AE053.5060103@aueb.gr> > Diomidis Spinellis writes: > : M. Warner Losh wrote: > : > And the last, rather long, patch converts the .y in config to a form > : > that more versions of yacc would grok. > : > > : > Comments? > : [...] > : > - INCLUDE ID SEMICOLON > : > - = { > : > + INCLUDE ID SEMICOLON { > : [...] > : > : The = { way for specifying yacc actions is item 5 in yacc's Appendix D > : titled "Old Features Supported but not Encouraged" in the Seventh > : Edition Unix Programmer's Manual (January, 1979). I believe it's now > : time to make the switch. Thanks! > > We can't switch until the feature has been deprecated for 30 years or > more, right? well that's only 2 years. better start prepping the diff now for comment. > > Warner > _______________________________________________ > 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 Thu Dec 20 22:43:46 2007 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 04DB316A417 for ; Thu, 20 Dec 2007 22:43:46 +0000 (UTC) (envelope-from max@love2party.net) Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.126.177]) by mx1.freebsd.org (Postfix) with ESMTP id 8F9F313C457 for ; Thu, 20 Dec 2007 22:43:44 +0000 (UTC) (envelope-from max@love2party.net) Received: from amd64.laiers.local (dslb-088-066-011-226.pools.arcor-ip.net [88.66.11.226]) by mrelayeu.kundenserver.de (node=mrelayeu8) with ESMTP (Nemesis) id 0ML31I-1J5U7D0vLU-0003gs; Thu, 20 Dec 2007 23:43:43 +0100 From: Max Laier Organization: FreeBSD To: freebsd-hackers@freebsd.org Date: Thu, 20 Dec 2007 23:43:34 +0100 User-Agent: KMail/1.9.7 References: <20071219.232511.-1548301831.imp@bsdimp.com> In-Reply-To: <20071219.232511.-1548301831.imp@bsdimp.com> X-Face: ,,8R(x[kmU]tKN@>gtH1yQE4aslGdu+2]; R]*pL,U>^H?)gW@49@wdJ`H<=?utf-8?q?=25=7D*=5FBD=0A=09U=5For=3D=5CmOZf764=26nYj=3DJYbR1PW0ud?=>|!~,,CPC.1-D$FG@0h3#'5"k{V]a~.<=?utf-8?q?mZ=7D44=23Se=7Em=0A=09Fe=7E=5C=5DX5B=5D=5Fxj?=(ykz9QKMw_l0C2AQ]}Ym8)fU MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart7936845.kka3y6JUg0"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200712202343.41507.max@love2party.net> X-Provags-ID: V01U2FsdGVkX18KXF6BlIp0EWkLJeWJlYcDEy6fjWlXEK0WT4t tfP2hI7ky9zH/UtTS2695pwmfE5ZEWE4Leb3los3ZAlpuxDmch 9KIO2g+vWX9r8Zi8pRL3oCi4Sj2KJmBJVId2JQbdk0= Cc: Subject: Re: Some diffs X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 20 Dec 2007 22:43:46 -0000 --nextPart7936845.kka3y6JUg0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Thursday 20 December 2007, M. Warner Losh wrote: > Consider the following diffs. The first one does a tiny cleanup of > strfile's include style (no real reason other than it bugged me when I > added stdint.h). > > The second one cleans up a minor problem where ${CFLAGS} isn't used > where it should be. > > The next three cleanup the compilation by not assuming sys/types.h is > included or by also including > > And the last, rather long, patch converts the .y in config to a form > that more versions of yacc would grok. > > Comments? sys/types.h (xor param.h) is supposed to be the first include (other than=20 cdefs.h) according to style. The rest seems fine from a quick glance. =2D-=20 /"\ Best regards, | mlaier@freebsd.org \ / Max Laier | ICQ #67774661 X http://pf4freebsd.love2party.net/ | mlaier@EFnet / \ ASCII Ribbon Campaign | Against HTML Mail and News --nextPart7936845.kka3y6JUg0 Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4 (FreeBSD) iD8DBQBHavAdXyyEoT62BG0RAsVeAJ9QSCXgJTpxlZBTI2VxXfUJe8nzGwCfYeY2 Zg+lIL9ba7h1PT0YmvHYjBg= =xZAw -----END PGP SIGNATURE----- --nextPart7936845.kka3y6JUg0-- From owner-freebsd-hackers@FreeBSD.ORG Thu Dec 20 22:29:49 2007 Return-Path: Delivered-To: hackers@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 199F316A417 for ; Thu, 20 Dec 2007 22:29:49 +0000 (UTC) (envelope-from dds@aueb.gr) Received: from mx-out-01.forthnet.gr (mx-out.forthnet.gr [193.92.150.104]) by mx1.freebsd.org (Postfix) with ESMTP id 7896B13C44B for ; Thu, 20 Dec 2007 22:29:48 +0000 (UTC) (envelope-from dds@aueb.gr) Received: from mx-av-04.forthnet.gr (mx-av.forthnet.gr [193.92.150.27]) by mx-out-01.forthnet.gr (8.13.8/8.13.8) with ESMTP id lBKLalcA003158; Thu, 20 Dec 2007 23:36:47 +0200 Received: from MX-IN-01.forthnet.gr (mx-in-01.forthnet.gr [193.92.150.23]) by mx-av-04.forthnet.gr (8.14.1/8.14.1) with ESMTP id lBKLal8p020220; Thu, 20 Dec 2007 23:36:47 +0200 Received: from [192.168.136.22] (ppp116-79.adsl.forthnet.gr [193.92.81.79]) by MX-IN-01.forthnet.gr (8.14.2/8.14.2) with ESMTP id lBKLakmh010560; Thu, 20 Dec 2007 23:36:47 +0200 Authentication-Results: MX-IN-01.forthnet.gr smtp.mail=dds@aueb.gr; spf=neutral Authentication-Results: MX-IN-01.forthnet.gr header.from=dds@aueb.gr; sender-id=neutral Message-ID: <476AE053.5060103@aueb.gr> Date: Thu, 20 Dec 2007 23:36:19 +0200 From: Diomidis Spinellis User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.4) Gecko/20070509 SeaMonkey/1.1.2 MIME-Version: 1.0 To: "M. Warner Losh" References: <20071219.232511.-1548301831.imp@bsdimp.com> In-Reply-To: <20071219.232511.-1548301831.imp@bsdimp.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Mailman-Approved-At: Fri, 21 Dec 2007 01:03:29 +0000 Cc: hackers@FreeBSD.ORG Subject: Re: Some diffs X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 20 Dec 2007 22:29:49 -0000 M. Warner Losh wrote: > And the last, rather long, patch converts the .y in config to a form > that more versions of yacc would grok. > > Comments? [...] > - INCLUDE ID SEMICOLON > - = { > + INCLUDE ID SEMICOLON { [...] The = { way for specifying yacc actions is item 5 in yacc's Appendix D titled "Old Features Supported but not Encouraged" in the Seventh Edition Unix Programmer's Manual (January, 1979). I believe it's now time to make the switch. Thanks! -- Diomidis Spinellis - http://www.spinellis.gr From owner-freebsd-hackers@FreeBSD.ORG Thu Dec 20 22:51:17 2007 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6991C16A417 for ; Thu, 20 Dec 2007 22:51:17 +0000 (UTC) (envelope-from chuckr@chuckr.org) Received: from mail5.sea5.speakeasy.net (mail5.sea5.speakeasy.net [69.17.117.7]) by mx1.freebsd.org (Postfix) with ESMTP id 4C5BC13C461 for ; Thu, 20 Dec 2007 22:51:17 +0000 (UTC) (envelope-from chuckr@chuckr.org) Received: (qmail 6497 invoked from network); 20 Dec 2007 22:51:16 -0000 Received: from april.chuckr.org (chuckr@[66.92.151.30]) (envelope-sender ) by mail5.sea5.speakeasy.net (qmail-ldap-1.03) with AES256-SHA encrypted SMTP for ; 20 Dec 2007 22:51:16 -0000 Message-ID: <476AF132.4080304@chuckr.org> Date: Thu, 20 Dec 2007 17:48:18 -0500 From: Chuck Robey User-Agent: Thunderbird 2.0.0.6 (X11/20071107) MIME-Version: 1.0 To: FreeBSD-Hackers X-Enigmail-Version: 0.95.5 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Mailman-Approved-At: Fri, 21 Dec 2007 01:16:27 +0000 Subject: printing boot probe messages X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 20 Dec 2007 22:51:17 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I've lost the printing of all of th e messages you normally see, when you are booting yoiur machine (you know, mostly probe messages. I used to see them on this box. When I made my first kernel, I had begun (obviously, as we all do) with GENERIC as a base, but changing the first loaders.hints and the kernel, that's the last I saw of booting messages. To illustrate what I *do* see, I watch the first character of that little spiller, but only the very first char, because that's when it stops working, right after sicking the first char. Thbe nest thing I see, maybe 30 seconds later, is a Login: request. Any notion what I could do to get my booting messages back? -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4 (FreeBSD) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFHavEyz62J6PPcoOkRAg7vAJ9zneAz5IuI6kwLOK31ZjeffQdt4gCfZCqF +z0b/+Q+ZHp5MDGcADSy+Go= =AOCE -----END PGP SIGNATURE----- From owner-freebsd-hackers@FreeBSD.ORG Fri Dec 21 07:56:49 2007 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3CE0A16A418 for ; Fri, 21 Dec 2007 07:56:49 +0000 (UTC) (envelope-from ticso@cicely12.cicely.de) Received: from raven.bwct.de (raven.bwct.de [85.159.14.73]) by mx1.freebsd.org (Postfix) with ESMTP id AC5C813C468 for ; Fri, 21 Dec 2007 07:56:48 +0000 (UTC) (envelope-from ticso@cicely12.cicely.de) Received: from cicely5.cicely.de ([10.1.1.7]) by raven.bwct.de (8.13.4/8.13.4) with ESMTP id lBL7k7TO069735; Fri, 21 Dec 2007 08:46:07 +0100 (CET) (envelope-from ticso@cicely12.cicely.de) Received: from cicely12.cicely.de (cicely12.cicely.de [10.1.1.14]) by cicely5.cicely.de (8.13.4/8.13.4) with ESMTP id lBL7jwoe087269 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 21 Dec 2007 08:45:59 +0100 (CET) (envelope-from ticso@cicely12.cicely.de) Received: from cicely12.cicely.de (localhost [127.0.0.1]) by cicely12.cicely.de (8.13.4/8.13.3) with ESMTP id lBL7jw96070002; Fri, 21 Dec 2007 08:45:58 +0100 (CET) (envelope-from ticso@cicely12.cicely.de) Received: (from ticso@localhost) by cicely12.cicely.de (8.13.4/8.13.3/Submit) id lBL7jvax070001; Fri, 21 Dec 2007 08:45:57 +0100 (CET) (envelope-from ticso) Date: Fri, 21 Dec 2007 08:45:57 +0100 From: Bernd Walter To: Chuck Robey Message-ID: <20071221074556.GA69673@cicely12.cicely.de> References: <476AF132.4080304@chuckr.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <476AF132.4080304@chuckr.org> X-Operating-System: FreeBSD cicely12.cicely.de 5.4-STABLE alpha User-Agent: Mutt/1.5.9i X-Spam-Status: No, score=-4.4 required=5.0 tests=ALL_TRUSTED=-1.8, AWL=0.048, BAYES_00=-2.599 autolearn=ham version=3.1.7 X-Spam-Checker-Version: SpamAssassin 3.1.7 (2006-10-05) on cicely12.cicely.de Cc: FreeBSD-Hackers Subject: Re: printing boot probe messages X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: ticso@cicely.de List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 21 Dec 2007 07:56:49 -0000 On Thu, Dec 20, 2007 at 05:48:18PM -0500, Chuck Robey wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > I've lost the printing of all of th e messages you normally see, when you are > booting yoiur machine (you know, mostly probe messages. I used to see them on > this box. When I made my first kernel, I had begun (obviously, as we all do) > with GENERIC as a base, but changing the first loaders.hints and the kernel, > that's the last I saw of booting messages. > > To illustrate what I *do* see, I watch the first character of that little > spiller, but only the very first char, because that's when it stops working, > right after sicking the first char. Thbe nest thing I see, maybe 30 seconds > later, is a Login: request. Sounds like your console is configured to a different device. Maybe it is configured to serial while you are waiting on vga. > Any notion what I could do to get my booting messages back? Switch the console to the device you are looking at. You can easily check the configured console by running conscontrol. Maybe you've lost the device hint for your console device to flag it as beeing a possible console candidate. -- B.Walter http://www.bwct.de http://www.fizon.de bernd@bwct.de info@bwct.de support@fizon.de From owner-freebsd-hackers@FreeBSD.ORG Fri Dec 21 10:56:02 2007 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4D28C16A419 for ; Fri, 21 Dec 2007 10:56:02 +0000 (UTC) (envelope-from danny@cs.huji.ac.il) Received: from cs1.cs.huji.ac.il (cs1.cs.huji.ac.il [132.65.16.10]) by mx1.freebsd.org (Postfix) with ESMTP id 02BD513C447 for ; Fri, 21 Dec 2007 10:56:01 +0000 (UTC) (envelope-from danny@cs.huji.ac.il) Received: from pampa.cs.huji.ac.il ([132.65.80.32]) by cs1.cs.huji.ac.il with esmtp id 1J5fC0-000Jd3-4G for freebsd-hackers@freebsd.org; Fri, 21 Dec 2007 12:33:24 +0200 X-Mailer: exmh version 2.7.2 01/07/2005 with nmh-1.2 To: FreeBSD-Hackers Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 21 Dec 2007 12:33:24 +0200 From: Danny Braniss Message-ID: Subject: diskless and the 21st. century X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 21 Dec 2007 10:56:02 -0000 Hi, Being a great fan of diskless/dataless hosts, I'm always looking for ways to reduce the administration 'overhead'. One issue is the number of different /(root) needed - one for each platform/os-version at least. Another issue is the particular configuration of a host, most of it can be done via rc.conf, but some need to be configured before init(8) gets run - boot/device.hits, boot/loader.conf. Since this are in the disk image, which is shared among many, they are difficult to 'personalize'. One solution, of cource, is to make several copies of the root image, one for each host. Another is to use DHCP, and with a patch to bootp.c(*) makes pxeboot(8) put most of the configurable options in the kernel env. Why all this blaber? well, I need someone with forth knowledge to fix the loader(8), if a variable is already in the kernel environment, don't override. The current problem I'm faced with, is that newer servers have newer/wierd ilo/imap/serial setups, Sun Fire X2200 have the serial console configured to com2, so adding 'hint.sio.1.flags="0x10" made the console available. But as soon as another host - without sio.1 - booted from that image it panicked. So now, I can configure hints. via dhcp. cheers, danny (*): availabel from ftp://ftp.cs.huji.ac.il/users/danny/freebsd/diskless-boot/ From owner-freebsd-hackers@FreeBSD.ORG Fri Dec 21 11:09:34 2007 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8756516A419 for ; Fri, 21 Dec 2007 11:09:34 +0000 (UTC) (envelope-from carl.shapiro@gmail.com) Received: from hs-out-2122.google.com (hs-out-0708.google.com [64.233.178.246]) by mx1.freebsd.org (Postfix) with ESMTP id 238FB13C4E1 for ; Fri, 21 Dec 2007 11:09:33 +0000 (UTC) (envelope-from carl.shapiro@gmail.com) Received: by hs-out-2122.google.com with SMTP id j58so277572hsj.11 for ; Fri, 21 Dec 2007 03:09:33 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; bh=acmpZDzVBG7mPzZjLUu9xJI1wztmMNzi41bv5Ez65nU=; b=dyDnDxdFMbp6+yht2Zg81o9kB/EXpct1ut99sY0cqltvhzVueOzwGqvxwUGC5i48tjdeQG6ZE3IQXX6i4CGwkRGdOohjcWgpJh8B25EgmOqJ4E2qWFFJNCwUp+ITXwgqM9W6ccHWGbKb3HnM7SGov894M+3raVoy4a4iYmn+ZOU= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=E6VR1MJ4xeAxQMyzSP5Wb5mrbeSA+1XgWh+sNsBnXID/lcK96PCex2Bhen+OjGYEYrRGx7hGcTwj/U9av5IX4e1oSY/70kdnZgt3OjORtuNL6FIBkQTJXbbKoLffWzNaq8/83AfEKU5tTCmE9G2urcPqoMmDBvSweKYcCs3YR/o= Received: by 10.150.191.10 with SMTP id o10mr387230ybf.84.1198235373488; Fri, 21 Dec 2007 03:09:33 -0800 (PST) Received: by 10.150.200.6 with HTTP; Fri, 21 Dec 2007 03:09:33 -0800 (PST) Message-ID: <4dcb5abd0712210309kd91b52fla64f64e90dc8213@mail.gmail.com> Date: Fri, 21 Dec 2007 03:09:33 -0800 From: "Carl Shapiro" To: "Peter Jeremy" In-Reply-To: <20071220093950.GA79196@server.vk2pj.dyndns.org> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <4dcb5abd0712192140w29fd39fh53b09fdd4d20e880@mail.gmail.com> <20071220093950.GA79196@server.vk2pj.dyndns.org> Cc: freebsd-hackers@freebsd.org Subject: Re: critical floating point incompatibility X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 21 Dec 2007 11:09:34 -0000 On 12/20/07, Peter Jeremy wrote: > I believe this is an oversight. See the thread beginning > http://lists.freebsd.org/pipermail/freebsd-stable/2007-November/037947.html Thanks for the pointer into the -stable mailing list. The incorrect precision control bits is a serious quality of life issue for those of us who care about consistent numerical computations and the backward compatibility of our FreeBSD object code. Is there an active community of users who care about numerics on FreeBSD? At any rate, I searched the PR database for a bug related to the incorrect control word setting but came up empty handed. If nothing has been filed to date I will go ahead and submit a PR. From owner-freebsd-hackers@FreeBSD.ORG Fri Dec 21 11:57:17 2007 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 573C216A418 for ; Fri, 21 Dec 2007 11:57:17 +0000 (UTC) (envelope-from erikt@midgard.homeip.net) Received: from ch-smtp01.sth.basefarm.net (ch-smtp01.sth.basefarm.net [80.76.149.212]) by mx1.freebsd.org (Postfix) with ESMTP id 05D8113C46A for ; Fri, 21 Dec 2007 11:57:16 +0000 (UTC) (envelope-from erikt@midgard.homeip.net) Received: from c83-253-25-183.bredband.comhem.se ([83.253.25.183]:57779 helo=falcon.midgard.homeip.net) by ch-smtp01.sth.basefarm.net with esmtp (Exim 4.68) (envelope-from ) id 1J5gGE-00012v-3O for freebsd-hackers@freebsd.org; Fri, 21 Dec 2007 12:41:50 +0100 Received: (qmail 60363 invoked from network); 21 Dec 2007 12:41:46 +0100 Received: from owl.midgard.homeip.net (10.1.5.7) by falcon.midgard.homeip.net with ESMTP; 21 Dec 2007 12:41:46 +0100 Received: (qmail 49936 invoked by uid 1001); 21 Dec 2007 12:41:46 +0100 Date: Fri, 21 Dec 2007 12:41:46 +0100 From: Erik Trulsson To: Carl Shapiro Message-ID: <20071221114146.GA49818@owl.midgard.homeip.net> Mail-Followup-To: Carl Shapiro , Peter Jeremy , freebsd-hackers@freebsd.org References: <4dcb5abd0712192140w29fd39fh53b09fdd4d20e880@mail.gmail.com> <20071220093950.GA79196@server.vk2pj.dyndns.org> <4dcb5abd0712210309kd91b52fla64f64e90dc8213@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4dcb5abd0712210309kd91b52fla64f64e90dc8213@mail.gmail.com> User-Agent: Mutt/1.5.16 (2007-06-09) X-Originating-IP: 83.253.25.183 X-Scan-Result: No virus found in message 1J5gGE-00012v-3O. X-Scan-Signature: ch-smtp01.sth.basefarm.net 1J5gGE-00012v-3O 6bf9dc5b7d5c35cc5bd233b584913e11 Cc: freebsd-hackers@freebsd.org Subject: Re: critical floating point incompatibility X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 21 Dec 2007 11:57:17 -0000 On Fri, Dec 21, 2007 at 03:09:33AM -0800, Carl Shapiro wrote: > On 12/20/07, Peter Jeremy wrote: > > I believe this is an oversight. See the thread beginning > > http://lists.freebsd.org/pipermail/freebsd-stable/2007-November/037947.html > > Thanks for the pointer into the -stable mailing list. > > The incorrect precision control bits is a serious quality of life > issue for those of us who care about consistent numerical computations > and the backward compatibility of our FreeBSD object code. Is there > an active community of users who care about numerics on FreeBSD? There are certainly people who care about numerics on FreeBSD. Most of the floating-point related discussions seem to happen on the freebsd-standards@ mailing list. You could check the archives of that list. > > At any rate, I searched the PR database for a bug related to the > incorrect control word setting but came up empty handed. If nothing > has been filed to date I will go ahead and submit a PR. -- Erik Trulsson ertr1013@student.uu.se From owner-freebsd-hackers@FreeBSD.ORG Fri Dec 21 18:38:16 2007 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 05AF716A417 for ; Fri, 21 Dec 2007 18:38:16 +0000 (UTC) (envelope-from bakul@bitblocks.com) Received: from mail.bitblocks.com (mail.bitblocks.com [64.142.15.60]) by mx1.freebsd.org (Postfix) with ESMTP id CB94213C442 for ; Fri, 21 Dec 2007 18:38:15 +0000 (UTC) (envelope-from bakul@bitblocks.com) Received: from bitblocks.com (localhost.bitblocks.com [127.0.0.1]) by mail.bitblocks.com (Postfix) with ESMTP id 0B6F25B42; Fri, 21 Dec 2007 10:11:24 -0800 (PST) To: Peter Jeremy In-reply-to: Your message of "Thu, 20 Dec 2007 20:39:50 +1100." <20071220093950.GA79196@server.vk2pj.dyndns.org> Date: Fri, 21 Dec 2007 10:11:24 -0800 From: Bakul Shah Message-Id: <20071221181125.0B6F25B42@mail.bitblocks.com> Cc: freebsd-hackers@freebsd.org, Carl Shapiro Subject: Re: critical floating point incompatibility X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 21 Dec 2007 18:38:16 -0000 Peter Jeremy wrote: > On Wed, Dec 19, 2007 at 09:40:34PM -0800, Carl Shapiro wrote: > >The default setting of the x87 floating point control word on the i386 > >port is 0x127F. Among other things, this value sets the precision > >control to double precision. The default setting of the x87 floating > >point control word on the AMD64 is 0x37F. > ... > >It seems clear that the right thing to do is to set the floating point > >environment to the i386 default for i386 binaries. Is the current > >behavior intended? > > I believe this is an oversight. See the thread beginning > http://lists.freebsd.org/pipermail/freebsd-stable/2007-November/037947.html >From reading Bruce's last message in that thread, seems to me may be default for 64bit binaries should be the same as on i386. Anyone wanting different behavior can always call fpsetprec() etc. I think the fix is to change __INITIAL_FPUCW__ in /sys/amd64/include/fpu.h to 0x127F like on i386. Also, while at it, comments above this constant in this file and above __INITIAL_NPXCW__ in /sys/i386/include/npx.h needs to reflect what was chosen and why. Filing a PR would help ensure this doesn't get lost. From owner-freebsd-hackers@FreeBSD.ORG Fri Dec 21 19:03:01 2007 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2313E16A4C4 for ; Fri, 21 Dec 2007 19:03:01 +0000 (UTC) (envelope-from julian@elischer.org) Received: from outO.internet-mail-service.net (outO.internet-mail-service.net [216.240.47.238]) by mx1.freebsd.org (Postfix) with ESMTP id E84F013C455 for ; Fri, 21 Dec 2007 19:03:00 +0000 (UTC) (envelope-from julian@elischer.org) Received: from mx0.idiom.com (HELO idiom.com) (216.240.32.160) by out.internet-mail-service.net (qpsmtpd/0.40) with ESMTP; Fri, 21 Dec 2007 11:02:59 -0800 Received: from julian-mac.elischer.org (localhost [127.0.0.1]) by idiom.com (Postfix) with ESMTP id 4C14B126D39; Fri, 21 Dec 2007 11:02:59 -0800 (PST) Message-ID: <476C0DE3.4050806@elischer.org> Date: Fri, 21 Dec 2007 11:02:59 -0800 From: Julian Elischer User-Agent: Thunderbird 2.0.0.9 (Macintosh/20071031) MIME-Version: 1.0 To: Carl Shapiro References: <4dcb5abd0712192140w29fd39fh53b09fdd4d20e880@mail.gmail.com> <20071220093950.GA79196@server.vk2pj.dyndns.org> <4dcb5abd0712210309kd91b52fla64f64e90dc8213@mail.gmail.com> In-Reply-To: <4dcb5abd0712210309kd91b52fla64f64e90dc8213@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Peter Wemm , Bruce Evans , freebsd-hackers@freebsd.org Subject: Re: critical floating point incompatibility X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 21 Dec 2007 19:03:01 -0000 Carl Shapiro wrote: > On 12/20/07, Peter Jeremy wrote: >> I believe this is an oversight. See the thread beginning >> http://lists.freebsd.org/pipermail/freebsd-stable/2007-November/037947.html > > Thanks for the pointer into the -stable mailing list. > > The incorrect precision control bits is a serious quality of life > issue for those of us who care about consistent numerical computations > and the backward compatibility of our FreeBSD object code. Is there > an active community of users who care about numerics on FreeBSD? > > At any rate, I searched the PR database for a bug related to the > incorrect control word setting but came up empty handed. If nothing > has been filed to date I will go ahead and submit a PR. > _______________________________________________ > 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" go ahead and submit the PR I'm guessing a combination of Peter Wemm and Bruce Evans would be able to decide on the right course of action. (CC'd) From owner-freebsd-hackers@FreeBSD.ORG Fri Dec 21 19:11:47 2007 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E8C1F16A421 for ; Fri, 21 Dec 2007 19:11:47 +0000 (UTC) (envelope-from sfourman@gmail.com) Received: from fg-out-1718.google.com (fg-out-1718.google.com [72.14.220.159]) by mx1.freebsd.org (Postfix) with ESMTP id 68F7D13C45B for ; Fri, 21 Dec 2007 19:11:47 +0000 (UTC) (envelope-from sfourman@gmail.com) Received: by fg-out-1718.google.com with SMTP id 16so236868fgg.35 for ; Fri, 21 Dec 2007 11:11:46 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; bh=8NDmOfb799y3xdmW52MOBMwb5A5xjQtCevikxvvSEF0=; b=xFAPc4Ob7TbGX5aqg/MB53PBBMZAnOCrVataHxSvMyU8a94JVBvlgFSEUC+nQt6feR+Kd/9NXqAW7cKvZoIo9KNP9QqtpNT3C99W2KeWULzjPBgPhkje2WDXOdahesXT15b/kuMhv0MmddUYM8EGIztoqx+0WDTQEbf1RQ2Xzso= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=MPou31A+A2zIxf79v+nbTBsrIL/WZHQYFliESl0pnEpiBaOuLEhwnMbM1vuGZ5d+P5dnmisFZgsoNNANK4pDg4wOi5im6ttcsANWv/sFdXCfhaHzE94TyTemjN11m1Nb1oqpx9W16al/KMF8z+6CpS9V3f+pm2BP+VFwq8hPNJk= Received: by 10.86.73.17 with SMTP id v17mr1409554fga.74.1198262859811; Fri, 21 Dec 2007 10:47:39 -0800 (PST) Received: by 10.86.52.6 with HTTP; Fri, 21 Dec 2007 10:47:39 -0800 (PST) Message-ID: <11167f520712211047k17334d5aya976c2d2cfda8f59@mail.gmail.com> Date: Fri, 21 Dec 2007 12:47:39 -0600 From: "Sam Fourman Jr." To: freebsd-hackers@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline Subject: How would I make this work in RELENG_7 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 21 Dec 2007 19:11:48 -0000 I have a PDA smart phone that I would like to use as a wireless modem on my laptop someone from OpenBSD helped me get it committed to OpenBSD 's Tree would someone help me with a similar patch for FreeBSD here is an old post that I made http://www.nabble.com/Alltel-PPC6700-Wireless-Modem-td12491547.html Sam Fourman Jr. From owner-freebsd-hackers@FreeBSD.ORG Fri Dec 21 20:16:44 2007 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id EF33F16A41A for ; Fri, 21 Dec 2007 20:16:44 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from relay02.kiev.sovam.com (relay02.kiev.sovam.com [62.64.120.197]) by mx1.freebsd.org (Postfix) with ESMTP id 8503A13C45D for ; Fri, 21 Dec 2007 20:16:44 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from [212.82.216.226] (helo=deviant.kiev.zoral.com.ua) by relay02.kiev.sovam.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.67) (envelope-from ) id 1J5oIS-000P9W-1z for freebsd-hackers@freebsd.org; Fri, 21 Dec 2007 22:16:43 +0200 Received: from deviant.kiev.zoral.com.ua (kostik@localhost [127.0.0.1]) by deviant.kiev.zoral.com.ua (8.14.2/8.14.2) with ESMTP id lBLKGXOb046201; Fri, 21 Dec 2007 22:16:33 +0200 (EET) (envelope-from kostikbel@gmail.com) Received: (from kostik@localhost) by deviant.kiev.zoral.com.ua (8.14.2/8.14.2/Submit) id lBLKGXd5046200; Fri, 21 Dec 2007 22:16:33 +0200 (EET) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: deviant.kiev.zoral.com.ua: kostik set sender to kostikbel@gmail.com using -f Date: Fri, 21 Dec 2007 22:16:33 +0200 From: Kostik Belousov To: Bakul Shah Message-ID: <20071221201633.GM57756@deviant.kiev.zoral.com.ua> References: <20071220093950.GA79196@server.vk2pj.dyndns.org> <20071221181125.0B6F25B42@mail.bitblocks.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="00sTfE/IIAT5d2r5" Content-Disposition: inline In-Reply-To: <20071221181125.0B6F25B42@mail.bitblocks.com> User-Agent: Mutt/1.4.2.3i X-Scanner-Signature: d3dfc5a0b247ea81d48b6a940fe6235f X-DrWeb-checked: yes X-SpamTest-Envelope-From: kostikbel@gmail.com X-SpamTest-Group-ID: 00000000 X-SpamTest-Info: Profiles 1938 [Dec 21 2007] X-SpamTest-Info: helo_type=3 X-SpamTest-Info: {received from trusted relay: not dialup} X-SpamTest-Method: none X-SpamTest-Method: Local Lists X-SpamTest-Rate: 0 X-SpamTest-Status: Not detected X-SpamTest-Status-Extended: not_detected X-SpamTest-Version: SMTP-Filter Version 3.0.0 [0255], KAS30/Release Cc: Carl Shapiro , freebsd-hackers@freebsd.org Subject: Re: critical floating point incompatibility X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 21 Dec 2007 20:16:45 -0000 --00sTfE/IIAT5d2r5 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Dec 21, 2007 at 10:11:24AM -0800, Bakul Shah wrote: > Peter Jeremy wrote: > > On Wed, Dec 19, 2007 at 09:40:34PM -0800, Carl Shapiro wrote: > > >The default setting of the x87 floating point control word on the i386 > > >port is 0x127F. Among other things, this value sets the precision > > >control to double precision. The default setting of the x87 floating > > >point control word on the AMD64 is 0x37F. > > ... > > >It seems clear that the right thing to do is to set the floating point > > >environment to the i386 default for i386 binaries. Is the current > > >behavior intended? > >=20 > > I believe this is an oversight. See the thread beginning > > http://lists.freebsd.org/pipermail/freebsd-stable/2007-November/037947.= html >=20 > >From reading Bruce's last message in that thread, seems to me > may be default for 64bit binaries should be the same as on > i386. Anyone wanting different behavior can always call > fpsetprec() etc. >=20 > I think the fix is to change __INITIAL_FPUCW__ in > /sys/amd64/include/fpu.h to 0x127F like on i386. I think this shall be done for 32-bit processes only, or we get into another ABI breaking nightmare. >=20 > Also, while at it, comments above this constant in this file > and above __INITIAL_NPXCW__ in /sys/i386/include/npx.h needs > to reflect what was chosen and why. >=20 > Filing a PR would help ensure this doesn't get lost. --00sTfE/IIAT5d2r5 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (FreeBSD) iD8DBQFHbB8gC3+MBN1Mb4gRAvfzAJ4oE92p/C6v34EvgKibtc/rir2LVwCg1ZAX WWaOmJWge/hZDAJ2O5qzEeM= =f5Sx -----END PGP SIGNATURE----- --00sTfE/IIAT5d2r5-- From owner-freebsd-hackers@FreeBSD.ORG Fri Dec 21 22:12:04 2007 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E4B6F16A418 for ; Fri, 21 Dec 2007 22:12:04 +0000 (UTC) (envelope-from gahr@gahr.ch) Received: from cpanel03.rubas-s03.net (cpanel03.rubas-s03.net [195.182.222.73]) by mx1.freebsd.org (Postfix) with ESMTP id 8C21913C45B for ; Fri, 21 Dec 2007 22:12:04 +0000 (UTC) (envelope-from gahr@gahr.ch) Received: from 80-218-191-236.dclient.hispeed.ch ([80.218.191.236] helo=gahrtop.localhost) by cpanel03.rubas-s03.net with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.68) (envelope-from ) id 1J5q67-0005QW-Ii; Fri, 21 Dec 2007 23:12:03 +0100 Message-ID: <476C39CD.7020104@gahr.ch> Date: Fri, 21 Dec 2007 23:10:21 +0100 From: Pietro Cerutti User-Agent: Thunderbird 2.0.0.9 (X11/20071121) MIME-Version: 1.0 To: "Sam Fourman Jr." References: <11167f520712211047k17334d5aya976c2d2cfda8f59@mail.gmail.com> In-Reply-To: <11167f520712211047k17334d5aya976c2d2cfda8f59@mail.gmail.com> X-Enigmail-Version: 0.95.5 OpenPGP: id=9571F78E; url=http://www.gahr.ch/pgp Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="------------enig0E91F10B38DCF504ABC73F9D" X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - cpanel03.rubas-s03.net X-AntiAbuse: Original Domain - freebsd.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - gahr.ch X-Source: X-Source-Args: X-Source-Dir: Cc: freebsd-hackers@freebsd.org Subject: Re: How would I make this work in RELENG_7 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 21 Dec 2007 22:12:05 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig0E91F10B38DCF504ABC73F9D Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Sam Fourman Jr. wrote: > I have a PDA smart phone that I would like to use as a wireless modem > on my laptop >=20 > someone from OpenBSD helped me get it committed to OpenBSD 's Tree >=20 > would someone help me with a similar patch for FreeBSD I don't have any commit bit, but you can try [1] locally and if it works submit a problem report [2]. > Sam Fourman Jr. [1] http://www.gahr.ch/FreeBSD/patches/_htc.diff [2] http://www.freebsd.org/support/bugreports.html Regards, --=20 Pietro Cerutti PGP Public Key: http://gahr.ch/pgp --------------enig0E91F10B38DCF504ABC73F9D Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (FreeBSD) iD8DBQFHbDnSwMJqmJVx944RCjLiAJ9sP1RN2cPkDWh/k/ZVo6wXnxXg8gCeKTpW yc2GmEPXkz1/dQpxRbi/cHs= =g9yX -----END PGP SIGNATURE----- --------------enig0E91F10B38DCF504ABC73F9D-- From owner-freebsd-hackers@FreeBSD.ORG Sat Dec 22 03:37:04 2007 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0F9EC16A417 for ; Sat, 22 Dec 2007 03:37:04 +0000 (UTC) (envelope-from chuckr@chuckr.org) Received: from mail8.sea5.speakeasy.net (mail8.sea5.speakeasy.net [69.17.117.10]) by mx1.freebsd.org (Postfix) with ESMTP id CCB8A13C44B for ; Sat, 22 Dec 2007 03:37:03 +0000 (UTC) (envelope-from chuckr@chuckr.org) Received: (qmail 22919 invoked from network); 22 Dec 2007 03:37:03 -0000 Received: from april.chuckr.org (chuckr@[66.92.151.30]) (envelope-sender ) by mail8.sea5.speakeasy.net (qmail-ldap-1.03) with AES256-SHA encrypted SMTP for ; 22 Dec 2007 03:37:02 -0000 Message-ID: <476C85A0.7050402@chuckr.org> Date: Fri, 21 Dec 2007 22:33:52 -0500 From: Chuck Robey User-Agent: Thunderbird 2.0.0.6 (X11/20071107) MIME-Version: 1.0 To: ticso@cicely.de References: <476AF132.4080304@chuckr.org> <20071221074556.GA69673@cicely12.cicely.de> In-Reply-To: <20071221074556.GA69673@cicely12.cicely.de> X-Enigmail-Version: 0.95.5 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Mailman-Approved-At: Sat, 22 Dec 2007 04:27:53 +0000 Cc: FreeBSD-Hackers Subject: Re: printing boot probe messages X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 22 Dec 2007 03:37:04 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Bernd Walter wrote: > On Thu, Dec 20, 2007 at 05:48:18PM -0500, Chuck Robey wrote: >> -----BEGIN PGP SIGNED MESSAGE----- >> Hash: SHA1 >> >> I've lost the printing of all of th e messages you normally see, when you are >> booting yoiur machine (you know, mostly probe messages. I used to see them on >> this box. When I made my first kernel, I had begun (obviously, as we all do) >> with GENERIC as a base, but changing the first loaders.hints and the kernel, >> that's the last I saw of booting messages. >> >> To illustrate what I *do* see, I watch the first character of that little >> spiller, but only the very first char, because that's when it stops working, >> right after sicking the first char. Thbe nest thing I see, maybe 30 seconds >> later, is a Login: request. > > Sounds like your console is configured to a different device. > Maybe it is configured to serial while you are waiting on vga. > >> Any notion what I could do to get my booting messages back? > > Switch the console to the device you are looking at. > You can easily check the configured console by running conscontrol. > Maybe you've lost the device hint for your console device to flag > it as beeing a possible console candidate. OK, when I run conscontrol, it tells me I am using the dcons console. I looked at the man page for concontrol (and I've been gone from FreeBSD so long, I wasn't even awaare of conscontrol at all) and it informed me I am using the dcons device. I am not aware of any others, I was hoping that if there were such, there would be references to them in either the dcons or conscontrol man pages, but no lock. Is dcons good enough? You understand I would be ecstatic if it wasn't 9and if I could set it to something else, and thereby get my booting messages back.) I checked my kernel config file, it does indeed list the dcons device. Have any other ideas, I'm really listening here. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4 (FreeBSD) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFHbIWgz62J6PPcoOkRAigoAJ99PTNEEeK8LsBEXAtQS8Sc4tan2ACdESgM oBKqPU4TripnypwtKckxt6A= =r7GD -----END PGP SIGNATURE----- From owner-freebsd-hackers@FreeBSD.ORG Sat Dec 22 10:37:39 2007 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9FEB516A419 for ; Sat, 22 Dec 2007 10:37:39 +0000 (UTC) (envelope-from ticso@cicely12.cicely.de) Received: from raven.bwct.de (raven.bwct.de [85.159.14.73]) by mx1.freebsd.org (Postfix) with ESMTP id 532B413C459 for ; Sat, 22 Dec 2007 10:37:38 +0000 (UTC) (envelope-from ticso@cicely12.cicely.de) Received: from cicely5.cicely.de ([10.1.1.7]) by raven.bwct.de (8.13.4/8.13.4) with ESMTP id lBMAbYoU013905; Sat, 22 Dec 2007 11:37:34 +0100 (CET) (envelope-from ticso@cicely12.cicely.de) Received: from cicely12.cicely.de (cicely12.cicely.de [10.1.1.14]) by cicely5.cicely.de (8.13.4/8.13.4) with ESMTP id lBMAbO6b000106 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 22 Dec 2007 11:37:25 +0100 (CET) (envelope-from ticso@cicely12.cicely.de) Received: from cicely12.cicely.de (localhost [127.0.0.1]) by cicely12.cicely.de (8.13.4/8.13.3) with ESMTP id lBMAbOMT016567; Sat, 22 Dec 2007 11:37:24 +0100 (CET) (envelope-from ticso@cicely12.cicely.de) Received: (from ticso@localhost) by cicely12.cicely.de (8.13.4/8.13.3/Submit) id lBMAbNHc016566; Sat, 22 Dec 2007 11:37:23 +0100 (CET) (envelope-from ticso) Date: Sat, 22 Dec 2007 11:37:23 +0100 From: Bernd Walter To: Chuck Robey Message-ID: <20071222103723.GC15935@cicely12.cicely.de> References: <476AF132.4080304@chuckr.org> <20071221074556.GA69673@cicely12.cicely.de> <476C85A0.7050402@chuckr.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <476C85A0.7050402@chuckr.org> X-Operating-System: FreeBSD cicely12.cicely.de 5.4-STABLE alpha User-Agent: Mutt/1.5.9i X-Spam-Status: No, score=-4.4 required=5.0 tests=ALL_TRUSTED=-1.8, BAYES_00=-2.599 autolearn=ham version=3.2.3 X-Spam-Checker-Version: SpamAssassin 3.2.3 (2007-08-08) on cicely12.cicely.de Cc: FreeBSD-Hackers , ticso@cicely.de Subject: Re: printing boot probe messages X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: ticso@cicely.de List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 22 Dec 2007 10:37:39 -0000 On Fri, Dec 21, 2007 at 10:33:52PM -0500, Chuck Robey wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Bernd Walter wrote: > > On Thu, Dec 20, 2007 at 05:48:18PM -0500, Chuck Robey wrote: > >> -----BEGIN PGP SIGNED MESSAGE----- > >> Hash: SHA1 > >> > >> I've lost the printing of all of th e messages you normally see, when you are > >> booting yoiur machine (you know, mostly probe messages. I used to see them on > >> this box. When I made my first kernel, I had begun (obviously, as we all do) > >> with GENERIC as a base, but changing the first loaders.hints and the kernel, > >> that's the last I saw of booting messages. > >> > >> To illustrate what I *do* see, I watch the first character of that little > >> spiller, but only the very first char, because that's when it stops working, > >> right after sicking the first char. Thbe nest thing I see, maybe 30 seconds > >> later, is a Login: request. > > > > Sounds like your console is configured to a different device. > > Maybe it is configured to serial while you are waiting on vga. > > > >> Any notion what I could do to get my booting messages back? > > > > Switch the console to the device you are looking at. > > You can easily check the configured console by running conscontrol. > > Maybe you've lost the device hint for your console device to flag > > it as beeing a possible console candidate. > > OK, when I run conscontrol, it tells me I am using the dcons console. I > looked at the man page for concontrol (and I've been gone from FreeBSD so > long, I wasn't even awaare of conscontrol at all) and it informed me I am > using the dcons device. I am not aware of any others, I was hoping that if > there were such, there would be references to them in either the dcons or > conscontrol man pages, but no lock. Is dcons good enough? You understand I > would be ecstatic if it wasn't 9and if I could set it to something else, and > thereby get my booting messages back.) I checked my kernel config file, it > does indeed list the dcons device. dcons has no output as such, it depends on further support. dcons for example allows console access over firewire. You likely want consolectl as your configured console device. I can just repeat myself: you must have missing some device hints, since the device as such works fine but is not used as console. See if conscontrol lists consolectl as available console devices, if not than you are surely missing a hint if yes then you have explicitly configured you console to be on dcons. > Have any other ideas, I'm really listening here. > > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v2.0.4 (FreeBSD) > Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org > > iD8DBQFHbIWgz62J6PPcoOkRAigoAJ99PTNEEeK8LsBEXAtQS8Sc4tan2ACdESgM > oBKqPU4TripnypwtKckxt6A= > =r7GD > -----END PGP SIGNATURE----- > _______________________________________________ > 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" -- B.Walter http://www.bwct.de http://www.fizon.de bernd@bwct.de info@bwct.de support@fizon.de From owner-freebsd-hackers@FreeBSD.ORG Sat Dec 22 17:52:49 2007 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D3CFA16A417 for ; Sat, 22 Dec 2007 17:52:49 +0000 (UTC) (envelope-from chuckr@chuckr.org) Received: from mail1.sea5.speakeasy.net (mail1.sea5.speakeasy.net [69.17.117.3]) by mx1.freebsd.org (Postfix) with ESMTP id C7CE513C442 for ; Sat, 22 Dec 2007 17:52:49 +0000 (UTC) (envelope-from chuckr@chuckr.org) Received: (qmail 24396 invoked from network); 22 Dec 2007 17:52:48 -0000 Received: from april.chuckr.org (chuckr@[66.92.151.30]) (envelope-sender ) by mail1.sea5.speakeasy.net (qmail-ldap-1.03) with AES256-SHA encrypted SMTP for ; 22 Dec 2007 17:52:48 -0000 Message-ID: <476D4E35.7000808@chuckr.org> Date: Sat, 22 Dec 2007 12:49:41 -0500 From: Chuck Robey User-Agent: Thunderbird 2.0.0.6 (X11/20071107) MIME-Version: 1.0 To: ticso@cicely.de References: <476AF132.4080304@chuckr.org> <20071221074556.GA69673@cicely12.cicely.de> <476C85A0.7050402@chuckr.org> <20071222103723.GC15935@cicely12.cicely.de> In-Reply-To: <20071222103723.GC15935@cicely12.cicely.de> X-Enigmail-Version: 0.95.5 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Mailman-Approved-At: Sat, 22 Dec 2007 18:06:56 +0000 Cc: FreeBSD-Hackers Subject: Re: printing boot probe messages X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 22 Dec 2007 17:52:49 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Bernd Walter wrote: > OK, when I run conscontrol, it tells me I am using the dcons console. I > looked at the man page for concontrol (and I've been gone from FreeBSD so > long, I wasn't even awaare of conscontrol at all) and it informed me I am > using the dcons device. I am not aware of any others, I was hoping that if > there were such, there would be references to them in either the dcons or > conscontrol man pages, but no lock. Is dcons good enough? You understand I > would be ecstatic if it wasn't 9and if I could set it to something else, and > thereby get my booting messages back.) I checked my kernel config file, it > does indeed list the dcons device. > >> dcons has no output as such, it depends on further support. >> dcons for example allows console access over firewire. >> You likely want consolectl as your configured console device. >> I can just repeat myself: you must have missing some device hints, >> since the device as such works fine but is not used as console. >> See if conscontrol lists consolectl as available console devices, >> if not than you are surely missing a hint if yes then you have >> explicitly configured you console to be on dcons. I wish you'd given more examples, because the concontrol man page is extremely unhelpful, but I will see if I can prompt you into it, by providing what comes out of my running conscontrol: TCSH-april:root:/home/chuckr:#105-12:23>conscontrol Configured: dcons Available: dcons,gdb Muting: off If you use the "list" parameter to conscontrol, the same printout results. I *think* you might be saying that I should see something dealing with consolectl, nothing resu;ting even from man -k consolectl. I did find the file /dev/consolectl, but I can't figure out the use of it. Hmmm, I found a hint on an old email, hinting that the command "conscontrol should have been used to add a console. I just tried using the ctl-alt-f1 combo to get onto ttyv0. I did a tty, this proved I was in fact on ttyv0, so i tried to do a "conscontrol add /dev/ttyv0, but what came back was "device not configured". I think I'm close here, so what should my console device be? > > Have any other ideas, I'm really listening here. > _______________________________________________ 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" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4 (FreeBSD) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFHbU41z62J6PPcoOkRAhYiAJ0WMob4kfBZFautZJLbbrOm6HVdzQCgjRJ3 +BYHMNjaRLrYjANPsizWeck= =aUxK -----END PGP SIGNATURE----- From owner-freebsd-hackers@FreeBSD.ORG Sat Dec 22 22:19:31 2007 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2C5BC16A41B for ; Sat, 22 Dec 2007 22:19:31 +0000 (UTC) (envelope-from jdc@parodius.com) Received: from mx01.sc1.parodius.com (mx01.sc1.parodius.com [72.20.106.3]) by mx1.freebsd.org (Postfix) with ESMTP id 233B813C44B for ; Sat, 22 Dec 2007 22:19:31 +0000 (UTC) (envelope-from jdc@parodius.com) Received: by mx01.sc1.parodius.com (Postfix, from userid 1000) id E10111CC038; Sat, 22 Dec 2007 14:19:30 -0800 (PST) Date: Sat, 22 Dec 2007 14:19:30 -0800 From: Jeremy Chadwick To: Chuck Robey Message-ID: <20071222221930.GA33588@eos.sc1.parodius.com> References: <476AF132.4080304@chuckr.org> <20071221074556.GA69673@cicely12.cicely.de> <476C85A0.7050402@chuckr.org> <20071222103723.GC15935@cicely12.cicely.de> <476D4E35.7000808@chuckr.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <476D4E35.7000808@chuckr.org> User-Agent: Mutt/1.5.16 (2007-06-09) Cc: FreeBSD-Hackers , ticso@cicely.de Subject: Re: printing boot probe messages X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 22 Dec 2007 22:19:31 -0000 On Sat, Dec 22, 2007 at 12:49:41PM -0500, Chuck Robey wrote: > TCSH-april:root:/home/chuckr:#105-12:23>conscontrol > Configured: dcons > Available: dcons,gdb > Muting: off > > If you use the "list" parameter to conscontrol, the same printout results. I > *think* you might be saying that I should see something dealing with > consolectl, nothing resu;ting even from man -k consolectl. I did find the > file /dev/consolectl, but I can't figure out the use of it. conscontrol(8) output of configured/available devices simply parses the kern.console sysctl variable. Everything after the "/" is considered an available device for console output, and everything prior is considered a working/used console. So, based on the output of the command you ran, I'd say all of your console messages (the ones you're looking for) are going to dcons. I had absolutely no idea what "dcons" was until I man'd it. It appears to be a basic I/O driver that allows other drivers (or busses) to attach to it. When used as a console device, all kernel messages end up going into that buffer. Therefore, you appear to have some settings in your kernel configuration which are inducing the behaviour you're experiencing. A RELENG_6 box with serial console enabled (/boot.config contains -Dh) and "options GDB" (but no dcons device) enabled in the kernel shows this: eos# conscontrol Configured: ttyd0,consolectl Available: ttyd0,consolectl Muting: off eos# sysctl kern.console kern.console: ttyd0,consolectl,/ttyd0,consolectl, A RELENG_7 box without serial console (just VGA), and "options GDB" in the kernel shows this: icarus# conscontrol Configured: consolectl Available: consolectl,gdb,ttyd0 Muting: off icarus# sysctl kern.console kern.console: consolectl,/consolectl,gdb,ttyd0, > Hmmm, I found a hint on an old email, hinting that the command "conscontrol > should have been used to add a console. conscontrol(8) lets you adjust which devices kernel messages go to. You can't just pick "any device in /dev". It doesn't work that way. > I just tried using the ctl-alt-f1 > combo to get onto ttyv0. I did a tty, this proved I was in fact on ttyv0, so > i tried to do a "conscontrol add /dev/ttyv0, but what came back was "device > not configured". I think I'm close here, so what should my console device be? No, you can't do this. Your available console devices are listed when you do `conscontrol' from the command line. In your case right now, your available consoles are either dcons (which you're already using) or gdb. Based on what I can figure out, your kernel configuration is very likely missing the inclusion of the syscons(4) driver, which is what drives VGA output. Although, the fact that you can switch virtual VGA consoles via Control-Alt-Fx seems to indicate you have a working VGA console somehow. I think it would be benefitial to see your kernel configuration, the contents of /boot/loader.conf, and /boot.config if you have one. -- | Jeremy Chadwick jdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | From owner-freebsd-hackers@FreeBSD.ORG Sat Dec 22 22:21:36 2007 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8BC5716A419 for ; Sat, 22 Dec 2007 22:21:36 +0000 (UTC) (envelope-from jdc@parodius.com) Received: from mx01.sc1.parodius.com (mx01.sc1.parodius.com [72.20.106.3]) by mx1.freebsd.org (Postfix) with ESMTP id 8D8E513C457 for ; Sat, 22 Dec 2007 22:21:36 +0000 (UTC) (envelope-from jdc@parodius.com) Received: by mx01.sc1.parodius.com (Postfix, from userid 1000) id 573CE1CC07B; Sat, 22 Dec 2007 14:21:36 -0800 (PST) Date: Sat, 22 Dec 2007 14:21:36 -0800 From: Jeremy Chadwick To: Chuck Robey Message-ID: <20071222222136.GA34339@eos.sc1.parodius.com> References: <476AF132.4080304@chuckr.org> <20071221074556.GA69673@cicely12.cicely.de> <476C85A0.7050402@chuckr.org> <20071222103723.GC15935@cicely12.cicely.de> <476D4E35.7000808@chuckr.org> <20071222221930.GA33588@eos.sc1.parodius.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20071222221930.GA33588@eos.sc1.parodius.com> User-Agent: Mutt/1.5.16 (2007-06-09) Cc: FreeBSD-Hackers , ticso@cicely.de Subject: Re: printing boot probe messages X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 22 Dec 2007 22:21:36 -0000 On Sat, Dec 22, 2007 at 02:19:30PM -0800, Jeremy Chadwick wrote: > I think it would be benefitial to see your kernel configuration, the > contents of /boot/loader.conf, and /boot.config if you have one. I forgot another one: /boot/device.hints. -- | Jeremy Chadwick jdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB |