Re: HEADSUP: Change of makedev() semantics.
On Sun, 28 Sep 2003, Poul-Henning Kamp wrote: Basically: 1. Do not call makedev(). 2. If you do cloning, please look at the patches I posted for if_tun/if_tap for how to do it. show an actual document please, explaining how this works from the user's POV.. 3. If you do a normal device driver, cache the result from when you call make_dev(). 4. If you translate foreign dev_t's, ie emulators or compat code, contact me. I'm not sure I understand how this works and should work and we need to talk. 5. If anything else or in doubt, ask me. more docs on how you invisage clonign to work. Can I see some volounteers and/or maintainers please ? ./dev/nmdm/nmdm.c pseudo-cloning. Should do real cloning. If the documentation is easily available and it does what I want I'll convert it.. It may be available but I haven't seen it.. man make_dev(9) doesn't have any 'see also' section that helps.. So, why should I not revoke a vnode that now refers to nothing? ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
HEADSUP: Change of makedev() semantics.
I am in the process of adding ref-counting and locking to dev_t, and would very much prefer if we could get this step completed soon before 5-STABLE gets branched. All this will be transparent to the majority of device drivers, as the refcounting will happen in the make_dev() and destroy_dev() family of calls and normal drivers need not know more about it. But there are a few remaining users of makedev() which get in the way of this effort, and we must get these fixed. Basically: 1. Do not call makedev(). 2. If you do cloning, please look at the patches I posted for if_tun/if_tap for how to do it. 3. If you do a normal device driver, cache the result from when you call make_dev(). 4. If you translate foreign dev_t's, ie emulators or compat code, contact me. I'm not sure I understand how this works and should work and we need to talk. 5. If anything else or in doubt, ask me. Can I see some volounteers and/or maintainers please ? ./alpha/osf1/osf1_misc.c badly named local macro ? ./compat/linux/linux_stats.c ./compat/svr4/svr4_types.h compat code, not sure that this is correct now. Must be supported by new finddev semantics. ./dev/ata/atapi-cd.c cloning related to root mount. gets fixed when phk GEOMify the driver. ./dev/sound/midi/midi.h Not sure. ./dev/nmdm/nmdm.c pseudo-cloning. Should do real cloning. ./dev/syscons/syscons.c Related to console initialization. Maybe tricky. ./dev/sound/pcm/dsp.c ./dev/sound/pcm/mixer.c ./dev/usb/ugen.c ./dev/usb/uscanner.c Failure to cache result of make_dev() ./dev/vinum Failure to cache result of make_dev() ? Thanks in advance! -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 [EMAIL PROTECTED] | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: HEADSUP: Change of makedev() semantics.
On Sunday, 28 September 2003 at 23:22:07 +0200, Poul-Henning Kamp wrote: Basically: 3. If you do a normal device driver, cache the result from when you call make_dev(). ... ./dev/vinum Failure to cache result of make_dev() ? Where should this be cached? Can you point to example code? Greg -- See complete headers for address and phone numbers. NOTE: Due to the currently active Microsoft-based worms, I am limiting all incoming mail to 131,072 bytes. This is enough for normal mail, but not for large attachments. Please send these as URLs. pgp0.pgp Description: PGP signature
Re: HEADSUP: Change of makedev() semantics.
On Sun, Sep 28, 2003 at 11:22:07PM +0200, Poul-Henning Kamp wrote: I am in the process of adding ref-counting and locking to dev_t, and would very much prefer if we could get this step completed soon before 5-STABLE gets branched. All this will be transparent to the majority of device drivers, as the refcounting will happen in the make_dev() and destroy_dev() family of calls and normal drivers need not know more about it. But there are a few remaining users of makedev() which get in the way of this effort, and we must get these fixed. Basically: 1. Do not call makedev(). 2. If you do cloning, please look at the patches I posted for if_tun/if_tap for how to do it. 3. If you do a normal device driver, cache the result from when you call make_dev(). 4. If you translate foreign dev_t's, ie emulators or compat code, contact me. I'm not sure I understand how this works and should work and we need to talk. 5. If anything else or in doubt, ask me. Can I see some volounteers and/or maintainers please ? ./alpha/osf1/osf1_misc.c badly named local macro ? Unused code. umakedev is used within a macro but nowhere defined it seems. makedev is used as a macroname, but ifdef'ed 0. Shouldn't hurt. Maybe someone with knowledge about OSF1 emulation should decide what happens with them in the long run. ./dev/usb/ugen.c ./dev/usb/uscanner.c Failure to cache result of make_dev() I'll take those. -- B.Walter BWCThttp://www.bwct.de [EMAIL PROTECTED] [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: HEADSUP: Change of makedev() semantics.
On Mon, 29 Sep 2003, Greg 'groggy' Lehey wrote: On Sunday, 28 September 2003 at 23:22:07 +0200, Poul-Henning Kamp wrote: Basically: 3. If you do a normal device driver, cache the result from when you call make_dev(). ... ./dev/vinum Failure to cache result of make_dev() ? Where should this be cached? Can you point to example code? Actually, it looks like Vinum is caching the dev_t's, but it's not always using them to get back to the dev_t--sometimes it's invoking makedev() instead. However, this appears to happen only in the vinumrevive.c code, so I'm not sure if that's a property of the cached reference being unavailable -- it looks like it should be available in that context though. I.e., using sd-dev instead of VINUM_SD() -- it looks like there is a valid (struct sd *) reference there to follow, so you can get to the dev_t without doing a makedev(). Robert N M Watson FreeBSD Core Team, TrustedBSD Projects [EMAIL PROTECTED] Network Associates Laboratories ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: HEADSUP: Change of makedev() semantics.
On Sunday, 28 September 2003 at 19:46:20 -0400, Robert Watson wrote: On Mon, 29 Sep 2003, Greg 'groggy' Lehey wrote: On Sunday, 28 September 2003 at 23:22:07 +0200, Poul-Henning Kamp wrote: Basically: 3. If you do a normal device driver, cache the result from when you call make_dev(). ... ./dev/vinum Failure to cache result of make_dev() ? Where should this be cached? Can you point to example code? Actually, it looks like Vinum is caching the dev_t's, Ah, you mean saving the results rather than calling make_dev() every time? Yes, it only calls make_dev() once for any device. but it's not always using them to get back to the dev_t--sometimes it's invoking makedev() instead. However, this appears to happen only in the vinumrevive.c code, so I'm not sure if that's a property of the cached reference being unavailable it looks like it should be available in that context though. No, it should always be available. I was going to say I don't see any references to make_dev() in vinumrevive.c, nor any references to makedev() at all, but I see that VINUM_SD includes both. I.e., using sd-dev instead of VINUM_SD() -- it looks like there is a valid (struct sd *) reference there to follow, so you can get to the dev_t without doing a makedev(). Yes, this is a bug (and an indication of the dangers of using macros :-) I'll fix it. Greg -- See complete headers for address and phone numbers. NOTE: Due to the currently active Microsoft-based worms, I am limiting all incoming mail to 131,072 bytes. This is enough for normal mail, but not for large attachments. Please send these as URLs. pgp0.pgp Description: PGP signature
Re: HEADSUP: Change of makedev() semantics.
In message [EMAIL PROTECTED], Greg 'groggy' Lehey writes: --yRA+Bmk8aPhU85Qt Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Sunday, 28 September 2003 at 23:22:07 +0200, Poul-Henning Kamp wrote: Basically: 3. If you do a normal device driver, cache the result from when you call make_dev(). ... ./dev/vinum Failure to cache result of make_dev() ? Where should this be cached? Can you point to example code? Almost any other device driver. It is usually stored in the softc structure. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 [EMAIL PROTECTED] | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: MAKEDEV(8) manpage
On Mon, Mar 24, 2003 at 09:43:17PM +0200, Giorgos Keramidas wrote: On 2003-03-24 19:14, Christian Brueffer [EMAIL PROTECTED] wrote: I'll write a small manpage this evening which says that MAKEDEV is gone now with a short summary of what devfs does. Does that resolve your worries? If you write a detailed description of devfs please add it to devfs(5) and just replace the existing manpage of MAKEDEV with something like: The MAKEDEV script was deprecated by devfs(5) and geom(4) and removed from FreeBSD after GEOM became mandatory. Please see the devfs(5), devfs(8), geom(4) and mount_devfs(8) manpages for more details. This should be enough IMHO to point the reader to the right place. - Giorgos That was my original intent. I'm still uncertain if it would be better to write a small manpage or just create a MLINK to one of the devfs pages... - Christian -- Christian Brueffer [EMAIL PROTECTED] [EMAIL PROTECTED] GPG Key: http://people.freebsd.org/~brueffer/brueffer.key.asc GPG Fingerprint: A5C8 2099 19FF AACA F41B B29B 6C76 178C A0ED 982D pgp0.pgp Description: PGP signature
Re: MAKEDEV(8) manpage
On Tue, Mar 25, 2003 at 10:11:00AM +0100, Christian Brueffer wrote: On Mon, Mar 24, 2003 at 09:43:17PM +0200, Giorgos Keramidas wrote: On 2003-03-24 19:14, Christian Brueffer [EMAIL PROTECTED] wrote: I'll write a small manpage this evening which says that MAKEDEV is gone now with a short summary of what devfs does. Does that resolve your worries? If you write a detailed description of devfs please add it to devfs(5) and just replace the existing manpage of MAKEDEV with something like: The MAKEDEV script was deprecated by devfs(5) and geom(4) and removed from FreeBSD after GEOM became mandatory. Please see the devfs(5), devfs(8), geom(4) and mount_devfs(8) manpages for more details. This should be enough IMHO to point the reader to the right place. - Giorgos That was my original intent. I'm still uncertain if it would be better to write a small manpage or just create a MLINK to one of the devfs pages... Are you going to write a man page everytime a feature is deprecated? MAKEDEV is dead and gone. At most create the MLINK. -- Steve To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: MAKEDEV(8) manpage
On Tue, 25 Mar 2003, Steve Kargl wrote: SKOn Tue, Mar 25, 2003 at 10:11:00AM +0100, Christian Brueffer wrote: SK On Mon, Mar 24, 2003 at 09:43:17PM +0200, Giorgos Keramidas wrote: SK On 2003-03-24 19:14, Christian Brueffer [EMAIL PROTECTED] wrote: SK I'll write a small manpage this evening which says that MAKEDEV is SK gone now with a short summary of what devfs does. Does that resolve SK your worries? SK SK If you write a detailed description of devfs please add it to devfs(5) SK and just replace the existing manpage of MAKEDEV with something like: SK SK The MAKEDEV script was deprecated by devfs(5) and geom(4) and SK removed from FreeBSD after GEOM became mandatory. Please see SK the devfs(5), devfs(8), geom(4) and mount_devfs(8) manpages for SK more details. SK SK This should be enough IMHO to point the reader to the right place. SK SK - Giorgos SK SK SK That was my original intent. I'm still uncertain if it would be better SK to write a small manpage or just create a MLINK to one of the devfs SK pages... SK SK SKAre you going to write a man page everytime a feature SKis deprecated? MAKEDEV is dead and gone. At most SKcreate the MLINK. MAKEDEV has been in unix since at least version 7. That's about 30 years. If you deprecate a feature, that has been on virtually all unices for 30 years, it makes sense. Each time I type 'man vnconfig' (I don't use mdconfig often enough to remember which is actual and which of it is not there anymore) I'm puzzled that the mdconfig man page pops up. In that case it is easy to understand, that the functionality is almost the same. If I type 'man MAKEDEV' and devfs pops up, I have to think much more to find out, that these are somehow related. harti -- harti brandt, http://www.fokus.fraunhofer.de/research/cc/cats/employees/hartmut.brandt/private [EMAIL PROTECTED], [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: MAKEDEV(8) manpage
On 2003-03-25 07:10, Steve Kargl [EMAIL PROTECTED] wrote: On Tue, Mar 25, 2003 at 10:11:00AM +0100, Christian Brueffer wrote: On Mon, Mar 24, 2003 at 09:43:17PM +0200, Giorgos Keramidas wrote: On 2003-03-24 19:14, Christian Brueffer [EMAIL PROTECTED] wrote: I'll write a small manpage this evening which says that MAKEDEV is gone now with a short summary of what devfs does. Does that resolve your worries? If you write a detailed description of devfs please add it to devfs(5) and just replace the existing manpage of MAKEDEV with something like: The MAKEDEV script was deprecated by devfs(5) and geom(4) and removed from FreeBSD after GEOM became mandatory. Please see the devfs(5), devfs(8), geom(4) and mount_devfs(8) manpages for more details. This should be enough IMHO to point the reader to the right place. That was my original intent. I'm still uncertain if it would be better to write a small manpage or just create a MLINK to one of the devfs pages... Are you going to write a man page everytime a feature is deprecated? MAKEDEV is dead and gone. At most create the MLINK. Only for very important features that are a hardcoded part of most Unix users' brain patterns by now. MAKEDEV is a feature that has been with us for a long time. Actually, it's been in UNIX even before I was born! :-) Besides, I don't like (ab)using MLINKS for implicit redirects, because it feels like cheating or tricking the user to read something that he should instantly recognize and think ah, yes, here it is... this is not always the case though. Imagine the confusion if a Slackware Linux user who has learned that MAKEDEV is the place to look at, who goes into /dev and can't find it. He then goes on to type: % apropos MAKEDEV MAKEDEV: nothing appropriate. That must look annoying. Or even worse (using MLINKS), imagine the confusion when one types: % man MAKEDEV only to find that devfs(5) pops up. I can almost read already the posts to bugs@ or the PRs in the gnats database about manpage error, MAKEDEV loads devfs :-) - Giorgos To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: MAKEDEV(8) manpage
On Mon, Mar 24, 2003 at 09:40:32AM +0200, Jarkko Santala wrote: On Sun, 23 Mar 2003, Poul-Henning Kamp wrote: In message [EMAIL PROTECTED], Christian Brueffer writes: now that MAKEDEV has been gone for a while, the manpages (alpha and i386) can be nuked as well, right? Right. Although it might be considered dragging old baggage around, would it make sense to instead of zapping the man page completely write a new one that would at least give a clue on how things are done these days? Otherwise unclued people might just think there's something wrong with their system because the man page is missing and get even more confused. -jake Well, people are supposed to read UPDATING before updating the system. UPDATING already has an entry about this, so has the handbook, the release notes etc. I think we can't really help people that don't read the recommended documentation. - Christian -- Christian Brueffer [EMAIL PROTECTED] [EMAIL PROTECTED] GPG Key: http://people.freebsd.org/~brueffer/brueffer.key.asc GPG Fingerprint: A5C8 2099 19FF AACA F41B B29B 6C76 178C A0ED 982D pgp0.pgp Description: PGP signature
Re: MAKEDEV(8) manpage
Date: Mon, 24 Mar 2003 14:34:57 +0100 From: Christian Brueffer [EMAIL PROTECTED] Sender: [EMAIL PROTECTED] On Mon, Mar 24, 2003 at 09:40:32AM +0200, Jarkko Santala wrote: On Sun, 23 Mar 2003, Poul-Henning Kamp wrote: In message [EMAIL PROTECTED], Christian Brueffer w= rites: now that MAKEDEV has been gone for a while, the manpages (alpha and i3= 86) can be nuked as well, right? Right. Although it might be considered dragging old baggage around, would it make sense to instead of zapping the man page completely write a new one that would at least give a clue on how things are done these days? Otherwise unclued people might just think there's something wrong with their system because the man page is missing and get even more confused. -jake Well, people are supposed to read UPDATING before updating the system. UPDATING already has an entry about this, so has the handbook, the release notes etc. I think we can't really help people that don't read the recommended documentation. I think POLA should apply to things like this (even across major releases). MAKEDEV has been around for a long time and most folks are used to it being there. It's simply something that most people assume will be there on a Unix-like system. Yes, people should read UPDATING and, better still, the release notes. But taking the added step of having a simple man page with a pointer to the devfs paper and saying that MAKEDEV is no more there will avoid a lot of confusion. The goal of documentation should not be to make it possible for sophisticated users to use the system. It should make it as easy as possible for all levels of users, including those new to Unix and BSD to use the system. R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: [EMAIL PROTECTED] Phone: +1 510 486-8634 To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: MAKEDEV(8) manpage
On Mon, Mar 24, 2003 at 09:12:15AM -0800, Kevin Oberman wrote: Date: Mon, 24 Mar 2003 14:34:57 +0100 From: Christian Brueffer [EMAIL PROTECTED] Sender: [EMAIL PROTECTED] On Mon, Mar 24, 2003 at 09:40:32AM +0200, Jarkko Santala wrote: On Sun, 23 Mar 2003, Poul-Henning Kamp wrote: In message [EMAIL PROTECTED], Christian Brueffer w= rites: now that MAKEDEV has been gone for a while, the manpages (alpha and i3= 86) can be nuked as well, right? Right. Although it might be considered dragging old baggage around, would it make sense to instead of zapping the man page completely write a new one that would at least give a clue on how things are done these days? Otherwise unclued people might just think there's something wrong with their system because the man page is missing and get even more confused. -jake Well, people are supposed to read UPDATING before updating the system. UPDATING already has an entry about this, so has the handbook, the release notes etc. I think we can't really help people that don't read the recommended documentation. I think POLA should apply to things like this (even across major releases). MAKEDEV has been around for a long time and most folks are used to it being there. It's simply something that most people assume will be there on a Unix-like system. Yes, people should read UPDATING and, better still, the release notes. But taking the added step of having a simple man page with a pointer to the devfs paper and saying that MAKEDEV is no more there will avoid a lot of confusion. The goal of documentation should not be to make it possible for sophisticated users to use the system. It should make it as easy as possible for all levels of users, including those new to Unix and BSD to use the system. R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: [EMAIL PROTECTED] Phone: +1 510 486-8634 To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message I'll write a small manpage this evening which says that MAKEDEV is gone now with a short summary of what devfs does. Does that resolve your worries? - Christian -- Christian Brueffer [EMAIL PROTECTED] [EMAIL PROTECTED] GPG Key: http://people.freebsd.org/~brueffer/brueffer.key.asc GPG Fingerprint: A5C8 2099 19FF AACA F41B B29B 6C76 178C A0ED 982D pgp0.pgp Description: PGP signature
Re: MAKEDEV(8) manpage
On Mon, 24 Mar 2003, Christian Brueffer wrote: On Mon, Mar 24, 2003 at 09:12:15AM -0800, Kevin Oberman wrote: Date: Mon, 24 Mar 2003 14:34:57 +0100 From: Christian Brueffer [EMAIL PROTECTED] Sender: [EMAIL PROTECTED] On Mon, Mar 24, 2003 at 09:40:32AM +0200, Jarkko Santala wrote: On Sun, 23 Mar 2003, Poul-Henning Kamp wrote: In message [EMAIL PROTECTED], Christian Brueffer w= rites: now that MAKEDEV has been gone for a while, the manpages (alpha and i3= 86) can be nuked as well, right? Right. Although it might be considered dragging old baggage around, would it make sense to instead of zapping the man page completely write a new one that would at least give a clue on how things are done these days? Otherwise unclued people might just think there's something wrong with their system because the man page is missing and get even more confused. Well, people are supposed to read UPDATING before updating the system. UPDATING already has an entry about this, so has the handbook, the release notes etc. I think we can't really help people that don't read the recommended documentation. I think POLA should apply to things like this (even across major releases). MAKEDEV has been around for a long time and most folks are used to it being there. It's simply something that most people assume will be there on a Unix-like system. Yes, people should read UPDATING and, better still, the release notes. But taking the added step of having a simple man page with a pointer to the devfs paper and saying that MAKEDEV is no more there will avoid a lot of confusion. The goal of documentation should not be to make it possible for sophisticated users to use the system. It should make it as easy as possible for all levels of users, including those new to Unix and BSD to use the system. I'll write a small manpage this evening which says that MAKEDEV is gone now with a short summary of what devfs does. Does that resolve your worries? Exactly what I had in mind, so sounds good to me. ;) You probably want to make it as generic as possible, so that keeping it up-to-date doesn't become a burden in the future. I'd hate to create any extra maintenance work to anyone, no matter how small. Thanks, -jake -- Jarkko Santala [EMAIL PROTECTED]http://www.iki.fi/~jake/ System Administrator2001:670:83:f08::/64 To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: MAKEDEV(8) manpage
On Mon, Mar 24, 2003 at 08:29:59PM +0200, Jarkko Santala wrote: On Mon, 24 Mar 2003, Christian Brueffer wrote: On Mon, Mar 24, 2003 at 09:12:15AM -0800, Kevin Oberman wrote: Date: Mon, 24 Mar 2003 14:34:57 +0100 From: Christian Brueffer [EMAIL PROTECTED] Sender: [EMAIL PROTECTED] On Mon, Mar 24, 2003 at 09:40:32AM +0200, Jarkko Santala wrote: On Sun, 23 Mar 2003, Poul-Henning Kamp wrote: In message [EMAIL PROTECTED], Christian Brueffer w= rites: now that MAKEDEV has been gone for a while, the manpages (alpha and i3= 86) can be nuked as well, right? Right. Although it might be considered dragging old baggage around, would it make sense to instead of zapping the man page completely write a new one that would at least give a clue on how things are done these days? Otherwise unclued people might just think there's something wrong with their system because the man page is missing and get even more confused. Well, people are supposed to read UPDATING before updating the system. UPDATING already has an entry about this, so has the handbook, the release notes etc. I think we can't really help people that don't read the recommended documentation. I think POLA should apply to things like this (even across major releases). MAKEDEV has been around for a long time and most folks are used to it being there. It's simply something that most people assume will be there on a Unix-like system. Yes, people should read UPDATING and, better still, the release notes. But taking the added step of having a simple man page with a pointer to the devfs paper and saying that MAKEDEV is no more there will avoid a lot of confusion. The goal of documentation should not be to make it possible for sophisticated users to use the system. It should make it as easy as possible for all levels of users, including those new to Unix and BSD to use the system. I'll write a small manpage this evening which says that MAKEDEV is gone now with a short summary of what devfs does. Does that resolve your worries? Exactly what I had in mind, so sounds good to me. ;) You probably want to make it as generic as possible, so that keeping it up-to-date doesn't become a burden in the future. I'd hate to create any extra maintenance work to anyone, no matter how small. I'd rather just MLINK mount_devfs(8) to MAKEDEV(8) for the time being, say until 5.2 is out, like is the case for vnconfig(8). Cheers, -- Ruslan Ermilov Sysadmin and DBA, [EMAIL PROTECTED] Sunbay Software AG, [EMAIL PROTECTED] FreeBSD committer, +380.652.512.251Simferopol, Ukraine http://www.FreeBSD.org The Power To Serve http://www.oracle.com Enabling The Information Age pgp0.pgp Description: PGP signature
Re: MAKEDEV(8) manpage
On Mon, Mar 24, 2003 at 11:03:52PM +0200, Ruslan Ermilov wrote: On Mon, Mar 24, 2003 at 08:29:59PM +0200, Jarkko Santala wrote: On Mon, 24 Mar 2003, Christian Brueffer wrote: On Mon, Mar 24, 2003 at 09:12:15AM -0800, Kevin Oberman wrote: Date: Mon, 24 Mar 2003 14:34:57 +0100 From: Christian Brueffer [EMAIL PROTECTED] Sender: [EMAIL PROTECTED] On Mon, Mar 24, 2003 at 09:40:32AM +0200, Jarkko Santala wrote: On Sun, 23 Mar 2003, Poul-Henning Kamp wrote: In message [EMAIL PROTECTED], Christian Brueffer w= rites: now that MAKEDEV has been gone for a while, the manpages (alpha and i3= 86) can be nuked as well, right? Right. Although it might be considered dragging old baggage around, would it make sense to instead of zapping the man page completely write a new one that would at least give a clue on how things are done these days? Otherwise unclued people might just think there's something wrong with their system because the man page is missing and get even more confused. Well, people are supposed to read UPDATING before updating the system. UPDATING already has an entry about this, so has the handbook, the release notes etc. I think we can't really help people that don't read the recommended documentation. I think POLA should apply to things like this (even across major releases). MAKEDEV has been around for a long time and most folks are used to it being there. It's simply something that most people assume will be there on a Unix-like system. Yes, people should read UPDATING and, better still, the release notes. But taking the added step of having a simple man page with a pointer to the devfs paper and saying that MAKEDEV is no more there will avoid a lot of confusion. The goal of documentation should not be to make it possible for sophisticated users to use the system. It should make it as easy as possible for all levels of users, including those new to Unix and BSD to use the system. I'll write a small manpage this evening which says that MAKEDEV is gone now with a short summary of what devfs does. Does that resolve your worries? Exactly what I had in mind, so sounds good to me. ;) You probably want to make it as generic as possible, so that keeping it up-to-date doesn't become a burden in the future. I'd hate to create any extra maintenance work to anyone, no matter how small. I'd rather just MLINK mount_devfs(8) to MAKEDEV(8) for the time being, say until 5.2 is out, like is the case for vnconfig(8). Also good. devfs(5) would be a better choice then, mount_devfs(8) is just an MLINK to mount_std. - Christian -- Christian Brueffer [EMAIL PROTECTED] [EMAIL PROTECTED] GPG Key: http://people.freebsd.org/~brueffer/brueffer.key.asc GPG Fingerprint: A5C8 2099 19FF AACA F41B B29B 6C76 178C A0ED 982D pgp0.pgp Description: PGP signature
Re: MAKEDEV(8) manpage
On 2003-03-24 19:14, Christian Brueffer [EMAIL PROTECTED] wrote: I'll write a small manpage this evening which says that MAKEDEV is gone now with a short summary of what devfs does. Does that resolve your worries? If you write a detailed description of devfs please add it to devfs(5) and just replace the existing manpage of MAKEDEV with something like: The MAKEDEV script was deprecated by devfs(5) and geom(4) and removed from FreeBSD after GEOM became mandatory. Please see the devfs(5), devfs(8), geom(4) and mount_devfs(8) manpages for more details. This should be enough IMHO to point the reader to the right place. - Giorgos PS: I really think that devfs(5) doesn't belong to section 5, since it's not the description of a file format, but this is a very different topic. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
MAKEDEV(8) manpage
Hi, now that MAKEDEV has been gone for a while, the manpages (alpha and i386) can be nuked as well, right? - Christian -- Christian Brueffer [EMAIL PROTECTED] [EMAIL PROTECTED] GPG Key: http://people.freebsd.org/~brueffer/brueffer.key.asc GPG Fingerprint: A5C8 2099 19FF AACA F41B B29B 6C76 178C A0ED 982D pgp0.pgp Description: PGP signature
Re: MAKEDEV(8) manpage
In message [EMAIL PROTECTED], Christian Brueffer writes: --4C6bbPZ6c/S1npyF Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hi, now that MAKEDEV has been gone for a while, the manpages (alpha and i386) can be nuked as well, right? Right. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 [EMAIL PROTECTED] | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: MAKEDEV(8) manpage
On Sun, 23 Mar 2003, Poul-Henning Kamp wrote: In message [EMAIL PROTECTED], Christian Brueffer writes: now that MAKEDEV has been gone for a while, the manpages (alpha and i386) can be nuked as well, right? Right. Although it might be considered dragging old baggage around, would it make sense to instead of zapping the man page completely write a new one that would at least give a clue on how things are done these days? Otherwise unclued people might just think there's something wrong with their system because the man page is missing and get even more confused. -jake -- Jarkko Santala [EMAIL PROTECTED]http://www.iki.fi/~jake/ System Administrator2001:670:83:f08::/64 To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: MAKEDEV lost in 5.0-CURRENT?
On Wed, Mar 12, 2003 at 12:18:08PM -0500, Hiten Pandya wrote: Hartmann, O. (Wed, Mar 12, 2003 at 04:59:52PM +0100) wrote: On Wed, 12 Mar 2003, Sergey A. Osokin wrote: [...] All right, a new 'think another way when going to FreeBSD 5.0 ...'. It also helps when you read src/UPDATING :-) NODEVFS option has been removed and DEVFS thereby made standard. This makes all references to MAKEDEV obsolete, and they should be removed when convenient. On 5.0-RELEASE-p4 I have /usr/src/etc/MAKEDEV and i use it for making the devices in jails. Is there a jail devfs or is the way described in the jail(8) man page still the right(tm) one? Andy To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: MAKEDEV lost in 5.0-CURRENT?
In message [EMAIL PROTECTED], Andy writes: On Wed, Mar 12, 2003 at 12:18:08PM -0500, Hiten Pandya wrote: Hartmann, O. (Wed, Mar 12, 2003 at 04:59:52PM +0100) wrote: On Wed, 12 Mar 2003, Sergey A. Osokin wrote: [...] All right, a new 'think another way when going to FreeBSD 5.0 ...'. It also helps when you read src/UPDATING :-) NODEVFS option has been removed and DEVFS thereby made standard. This makes all references to MAKEDEV obsolete, and they should be removed when convenient. On 5.0-RELEASE-p4 I have /usr/src/etc/MAKEDEV and i use it for making the devices in jails. Is there a jail devfs or is the way described in the jail(8) man page still the right(tm) one? See devfs(8) -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 [EMAIL PROTECTED] | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: MAKEDEV lost in 5.0-CURRENT?
Hello, On 5.0-RELEASE-p4 I have /usr/src/etc/MAKEDEV and i use it for making the devices in jails. Is there a jail devfs or is the way described in the jail(8) man page still the right(tm) one? You can mount devfs into any places. For example a jail. BTW, take extreme care, when doing this, because if you don't set up devfs rules, anybody, who can become root in any jails can do things, which will irreversibly change your day. (reinstall/restore from backup) Hint: cp /dev/null /dev/[what is your root device outside the jail] BTW, it would be good to have an ipf.rules like file to set up those devfs rules. :) --[ Free Software ISOs - http://www.fsn.hu/?f=download ]-- Attila Nagy e-mail: [EMAIL PROTECTED] Free Software Network (FSN.HU)phone @work: +361 210 1415 (194) cell.: +3630 306 6758 To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: MAKEDEV lost in 5.0-CURRENT?
Hello, Hint: cp /dev/null /dev/[what is your root device outside the jail] I meant /dev/zero of course ;) (or /dev/random for the patient one) --[ Free Software ISOs - http://www.fsn.hu/?f=download ]-- Attila Nagy e-mail: [EMAIL PROTECTED] Free Software Network (FSN.HU)phone @work: +361 210 1415 (194) cell.: +3630 306 6758 To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: MAKEDEV lost in 5.0-CURRENT?
On Thu, Mar 13, 2003 at 12:45:24PM +0100, Poul-Henning Kamp wrote: In message [EMAIL PROTECTED], Andy writes: On Wed, Mar 12, 2003 at 12:18:08PM -0500, Hiten Pandya wrote: [...] On 5.0-RELEASE-p4 I have /usr/src/etc/MAKEDEV and i use it for making the devices in jails. Is there a jail devfs or is the way described in the jail(8) man page still the right(tm) one? See devfs(8) After reading it it seems the answer is no there is no special jail devfs, but you can create your own rules for a jail. More informative on this subject was /usr/share/doc/papers/devfs.ascii.gz which i quote here: 8 These behaviours will be controlled with mount options, but these have not yet been implemented because FreeBSD has run out of bitmap flags for mount options, and a new unlimited mount option implementation is still not in place at the time of writing. One mount option ``jaildevfs'', will restrict the contents of the DEVFS mount- point to the ``normal set'' of devices for a jail and automatically hide all future devices and make it impossible for a jailed root to un-hide hidden entries while letting an un-jailed root do so. 8 OK. What a pity. So we have to create our own, based on MAKEDEV jail maybe: 100 path * hide 200 path tty* unhide 300 path random unhide 400 path zero unhide 500 path null unhide 600 path fd/* unhide 700 path mdctl unhide 800 path ptyp* unhide Now the problem is ptyp* and mdctl don't show up, even so they got unhidden. Also symlinking seems to require special actions: $ ln -s null mem $ echo mem* mem mem $ ls -la mem* ls: mem: No such file or directory ls: mem: No such file or directory Obviously some magick happens with hidden devices, so how can you make those links or don't we need them anymore? Andy To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
MAKEDEV lost in 5.0-CURRENT?
Where are the MAKEDEV and MAKEDEV.local scripts in 5.0-CURRENT? I cvsupdate today last time and did a find through /usr/src, but I can not find both script ... -- MfG O. Hartmann [EMAIL PROTECTED] -- Systemadministration des Institutes fuer Physik der Atmosphaere (IPA) -- Johannes Gutenberg Universitaet Mainz Becherweg 21 55099 Mainz Tel: +496131/3924662 (Maschinenraum) Tel: +496131/3924144 (Buero) FAX: +496131/3923532 To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: MAKEDEV lost in 5.0-CURRENT?
On Wed, Mar 12, 2003 at 04:44:25PM +0100, Hartmann, O. wrote: Where are the MAKEDEV and MAKEDEV.local scripts in 5.0-CURRENT? I cvsupdate today last time and did a find through /usr/src, but I can not find both script ... MAKEDEV is dead, baby. MAKEDEV is dead (c) paraphrase from Pulp Fiction Long live devfs(8) :-) Look at http://www.freebsd.org/cgi/query-pr.cgi?pr=docs/48038 Committers still have no time for commit this :-) -- Rgdz,/\ ASCII RIBBON CAMPAIGN Sergey Osokin aka oZZ, \ /AGAINST HTML MAIL http://ozz.pp.ru/ X AND NEWS / \ To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: MAKEDEV lost in 5.0-CURRENT?
On Wed, 12 Mar 2003, Sergey A. Osokin wrote: :On Wed, Mar 12, 2003 at 04:44:25PM +0100, Hartmann, O. wrote: : Where are the MAKEDEV and MAKEDEV.local scripts in 5.0-CURRENT? : I cvsupdate today last time and did a find through /usr/src, : but I can not find both script ... : :MAKEDEV is dead, baby. MAKEDEV is dead (c) paraphrase from Pulp Fiction :Long live devfs(8) :-) :Look at http://www.freebsd.org/cgi/query-pr.cgi?pr=docs/48038 : :Committers still have no time for commit this :-) : :-- : :Rgdz,/\ ASCII RIBBON CAMPAIGN :Sergey Osokin aka oZZ, \ /AGAINST HTML MAIL :http://ozz.pp.ru/ X AND NEWS : / \ : Ouch ;-)) All right, a new 'think another way when going to FreeBSD 5.0 ...'. Thanks. -- MfG O. Hartmann [EMAIL PROTECTED] -- Systemadministration des Institutes fuer Physik der Atmosphaere (IPA) -- Johannes Gutenberg Universitaet Mainz Becherweg 21 55099 Mainz Tel: +496131/3924662 (Maschinenraum) Tel: +496131/3924144 (Buero) FAX: +496131/3923532 To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: MAKEDEV lost in 5.0-CURRENT?
Hartmann, O. (Wed, Mar 12, 2003 at 04:59:52PM +0100) wrote: On Wed, 12 Mar 2003, Sergey A. Osokin wrote: :On Wed, Mar 12, 2003 at 04:44:25PM +0100, Hartmann, O. wrote: : Where are the MAKEDEV and MAKEDEV.local scripts in 5.0-CURRENT? : I cvsupdate today last time and did a find through /usr/src, : but I can not find both script ... : :MAKEDEV is dead, baby. MAKEDEV is dead (c) paraphrase from Pulp Fiction :Long live devfs(8) :-) :Look at http://www.freebsd.org/cgi/query-pr.cgi?pr=docs/48038 : :Committers still have no time for commit this :-) : :-- : :Rgdz,/\ ASCII RIBBON CAMPAIGN :Sergey Osokin aka oZZ, \ /AGAINST HTML MAIL :http://ozz.pp.ru/ X AND NEWS : / \ : Ouch ;-)) All right, a new 'think another way when going to FreeBSD 5.0 ...'. It also helps when you read src/UPDATING :-) NODEVFS option has been removed and DEVFS thereby made standard. This makes all references to MAKEDEV obsolete, and they should be removed when convenient. -- Hiten To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: where is MAKEDEV
Adam Migus wrote: quote who=Toni Schmidbauer On Mon, Jan 27, 2003 at 09:14:36PM +0100, FredBriand wrote: everything seems OK, but my sound card. In the handbook they say I must use the MAKEDEV script (as in Linux) but I can't find it on my disk. freebsd 5.0 is using devfs(5). so device inodes are created automatically. for your soundcard be sure to enable pcm(4) in your kernel. for info on compiling a new kernel see the freebsd handbook: http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/kernelconfig.html It may be easier to just load the module. Try adding it to your /boot/loader.conf. For a list of available sound modules try grep ^snd /boot/defaults/loader.conf. If you don't know what your card is just type kldload snd It got renamed to snd_driver on current (but not on stable). That will load all sound drivers and dmesg will show you which one actually supports your card. Once you know, put that one in Dmesg shows how your card was identified, which is not quite saying which driver supports the card. your /boot/loader.conf. If your driver requires pcm, the loader will load it as a dependancy. -- Daniel C. Sobral (8-DCS) Gerencia de Operacoes Divisao de Comunicacao de Dados Coordenacao de Seguranca TCO Fones: 55-61-313-7654/Cel: 55-61-9618-0904 E-mail: [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] Outros: [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] God isn't dead, he just couldn't find a parking place. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: where is MAKEDEV
quote who=Toni Schmidbauer On Mon, Jan 27, 2003 at 09:14:36PM +0100, FredBriand wrote: everything seems OK, but my sound card. In the handbook they say I must use the MAKEDEV script (as in Linux) but I can't find it on my disk. freebsd 5.0 is using devfs(5). so device inodes are created automatically. for your soundcard be sure to enable pcm(4) in your kernel. for info on compiling a new kernel see the freebsd handbook: http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/kernelconfig.html It may be easier to just load the module. Try adding it to your /boot/loader.conf. For a list of available sound modules try grep ^snd /boot/defaults/loader.conf. If you don't know what your card is just type kldload snd That will load all sound drivers and dmesg will show you which one actually supports your card. Once you know, put that one in your /boot/loader.conf. If your driver requires pcm, the loader will load it as a dependancy. Adam -- Adam Migus - Research Scientist Network Associates Laboratories (http://www.nailabs.com) TrustedBSD (http://www.trustedbsd.org) FreeBSD (http://www.freebsd.org) To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
where is MAKEDEV
Hi, I'm new to FreeBSD and I'm busy installing it on a notebook. Up to now everything seems OK, but my sound card. In the handbook they say I must use the MAKEDEV script (as in Linux) but I can't find it on my disk. I tried to download it with the sysinstall tool but again there seems to be no package available. What can I do? Please help. fred. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: where is MAKEDEV
On Mon, Jan 27, 2003 at 09:14:36PM +0100, FredBriand wrote: everything seems OK, but my sound card. In the handbook they say I must use the MAKEDEV script (as in Linux) but I can't find it on my disk. freebsd 5.0 is using devfs(5). so device inodes are created automatically. for your soundcard be sure to enable pcm(4) in your kernel. for info on compiling a new kernel see the freebsd handbook: http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/kernelconfig.html toni -- Terror ist der Krieg der Armen, | [EMAIL PROTECTED] Krieg ist der Terror der Reichen. | Toni Schmidbauer - Sir Peter Ustinov | msg51023/pgp0.pgp Description: PGP signature
Re: Installing from CD and MAKEDEV
If memory serves me right, Poul-Henning Kamp wrote: In message [EMAIL PROTECTED], Jun Kuriyama writes: At Thu, 24 Oct 2002 12:10:53 + (UTC), kuriyama wrote: I've created install CD with make iso.1 (with sources few hours before). I'm trying to install fresh current box with this CD. But I got MAKEDEV returned non-zero status dialog after extracting dists. It seems cd /dev; sh MAKEDEV all is failed at devfs environment. I found it. Phk changes in 1.297 of src/etc/Makefile not to install MAKEDEV by default. Options may be: This should be fixed now I hope. It works here. I just did a successful i386 install from CDROM. Thanks! Bruce. msg45351/pgp0.pgp Description: PGP signature
Re: Installing from CD and MAKEDEV
At Thu, 24 Oct 2002 12:10:53 + (UTC), kuriyama wrote: I've created install CD with make iso.1 (with sources few hours before). I'm trying to install fresh current box with this CD. But I got MAKEDEV returned non-zero status dialog after extracting dists. It seems cd /dev; sh MAKEDEV all is failed at devfs environment. I found it. Phk changes in 1.297 of src/etc/Makefile not to install MAKEDEV by default. Options may be: (1) Back out 1.297. (2) Set MAKEDEV_INSTALL for install-media environment. (3) Drop non-devfs code from sysinstall (really???). -- Jun Kuriyama [EMAIL PROTECTED] // IMG SRC, Inc. [EMAIL PROTECTED] // FreeBSD Project To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Installing from CD and MAKEDEV
In message [EMAIL PROTECTED], Jun Kuriyama writes: At Thu, 24 Oct 2002 12:10:53 + (UTC), kuriyama wrote: I've created install CD with make iso.1 (with sources few hours before). I'm trying to install fresh current box with this CD. But I got MAKEDEV returned non-zero status dialog after extracting dists. It seems cd /dev; sh MAKEDEV all is failed at devfs environment. I found it. Phk changes in 1.297 of src/etc/Makefile not to install MAKEDEV by default. Options may be: (3) Drop non-devfs code from sysinstall (really???). This is the way we're going. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 [EMAIL PROTECTED] | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Installing from CD and MAKEDEV
In message [EMAIL PROTECTED], Jun Kuriyama writes: At Thu, 24 Oct 2002 12:10:53 + (UTC), kuriyama wrote: I've created install CD with make iso.1 (with sources few hours before). I'm trying to install fresh current box with this CD. But I got MAKEDEV returned non-zero status dialog after extracting dists. It seems cd /dev; sh MAKEDEV all is failed at devfs environment. I found it. Phk changes in 1.297 of src/etc/Makefile not to install MAKEDEV by default. Options may be: This should be fixed now I hope. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 [EMAIL PROTECTED] | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Installing from CD and MAKEDEV
I've created install CD with make iso.1 (with sources few hours before). I'm trying to install fresh current box with this CD. But I got MAKEDEV returned non-zero status dialog after extracting dists. It seems cd /dev; sh MAKEDEV all is failed at devfs environment. Is this my local problem? -- Jun Kuriyama [EMAIL PROTECTED] // IMG SRC, Inc. [EMAIL PROTECTED] // FreeBSD Project To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: MAKEDEV in current
--- Rob [EMAIL PROTECTED] wrote: I've tried to copy MAKEDEV to /dev in current. But get the error- operation not supported. I must be missing some very basic concept. Rob. Rob, FreeBSD-CURRENT makes use of DEVFS by default, so you dont need to create entries unless you have NODEVFS in your kernel configuration file. Also, read the src/UPDATING file more information. Regards. -- Hiten Pandya -- [EMAIL PROTECTED], [EMAIL PROTECTED] __ Do You Yahoo!? LAUNCH - Your Yahoo! Music Experience http://launch.yahoo.com To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: MAKEDEV in current
Rob wrote: I've tried to copy MAKEDEV to /dev in current. But get the error- operation not supported. I must be missing some very basic concept. Rob. It is my understanding that /dev is a dynamic filesystem in -current, and doesn't use or need things like MAKEDEV. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: MAKEDEV in current
On Tue, May 21, 2002 at 10:41:05AM -0700, Rob wrote: I've tried to copy MAKEDEV to /dev in current. But get the error- operation not supported. I must be missing some very basic concept. Rob. Rather basic ;-) : -current uses the devfs filesystem man devfs tells you more about the idea behind this -- | / o / /_ _ [EMAIL PROTECTED] |/|/ / / /( (_) Bulte Arnhem, the Netherlands To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: MAKEDEV in current
On Tue, May 21, 2002 at 10:41:05AM -0700, Rob wrote: I've tried to copy MAKEDEV to /dev in current. But get the error- operation not supported. I must be missing some very basic concept. Rob. You are if you run mount it will tell you /dev is devfs you don't need to run MAKEDEV on -currrent as devices are created as you need them. If you're having a problem with a certain device not existing, then you should post that with all details. -- David W. Chapman Jr. [EMAIL PROTECTED] Raintree Network Services, Inc. www.inethouston.net [EMAIL PROTECTED] FreeBSD Committer www.FreeBSD.org To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: MAKEDEV in current
Rob wrote: I've tried to copy MAKEDEV to /dev in current. But get the error- operation not supported. I must be missing some very basic concept. Rob. Set NO_MAKEDEV_INSTALL=true in /etc/make.conf and make tweaks to /etc/rc.devfs for /dev permissions on -current. Pete... To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
/dev/MAKEDEV not being installed?
Just did a fresh install of -CURRENT and noticed that MAKEDEV isn't being installed. This intentional? -sc -- Sean Chittenden To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: /dev/MAKEDEV not being installed?
Just did a fresh install of -CURRENT and noticed that MAKEDEV isn't being installed. This intentional? -sc MAKEDEV on -current is not needed, since devfs creates device nodes automatically. Alright, sounds good/believable, but how do I extend the number of pty's on current then? I only see 20 tty* entries in /dev and would like the full 256 like I compiled in. -sc -- Sean Chittenden To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: /dev/MAKEDEV not being installed?
In the last episode (Mar 22), Sean Chittenden said: Just did a fresh install of -CURRENT and noticed that MAKEDEV isn't being installed. This intentional? -sc MAKEDEV on -current is not needed, since devfs creates device nodes automatically. -- Dan Nelson [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: /dev/MAKEDEV not being installed?
On Fri, 22 Mar 2002, Sean Chittenden wrote: Just did a fresh install of -CURRENT and noticed that MAKEDEV isn't being installed. This intentional? -sc MAKEDEV on -current is not needed, since devfs creates device nodes automatically. Alright, sounds good/believable, but how do I extend the number of pty's on current then? I only see 20 tty* entries in /dev and would like the full 256 like I compiled in. -sc New entries should clone themselves as needed, up to the precompiled limit. If this is not happening, it's a bug. :-) You can test this by sequentially opening /dev/ptty(n) entries and watch matching ttyp/r/q/s entries appear. Robert N M Watson FreeBSD Core Team, TrustedBSD Project [EMAIL PROTECTED] NAI Labs, Safeport Network Services To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
MAKEDEV - Installation fails - 20020312
Installing on a Sony VAIO PCG-SRX7E/P Boot from 4.5-INSTALL CD (iLINK) set hw.pcic.intr_path=1 set hw.pcic.irq=0 boot Visual configuration, leave only: ata0 atkbd0 psm0 sc0 pcic0 npx0 Partition disk, select Developer and Ports Select 5.0-20020312-CURRENT as release Select -CURRENT FTP installation site DHCP configuration of fxp0 watch all distributions get installed Message MAKEDEV returned non-zero status debug console shows a long series of pid 199 (sh), uid 0: exited on signal 12 (core dumped) Bad system call - core dumped pid 201 (sh), uid 0: exited on signal 12 (core dumped) Bad system call - core dumped pid 203 (sh), uid 0: exited on signal 12 (core dumped) Bad system call - core dumped pid 205 (sh), uid 0: exited on signal 12 (core dumped) Bad system call - core dumped Expect that this is probably due to the incompatibilities between the 4.5-RELEASE /stand/sysinstall and the 5.0 MAKEDEV Plan: try to create a bootable CD with a 5.0 kernel... Nero Burning ROM, select CD-ROM (Boot), boot.flp, Floppy Emulation 2.88MB Load segment of sectors (hex): 07C0 [jmk - their default] Number of loaded sectors: 1 [jmk - their default] set hw.pcic.intr_path=1 set hw.pcic.irq=0 boot ACPI autoload failed - no such file or directory - (crash dump appears) set hw.pcic.intr_path=1 set hw.pcic.irq=0 set hint.acpi.0.disabled=1 boot ACPI autoload failed - no such file or directory - (crash dump appears) # # Any additional suggestions??? # System boots on partial install, however, there is no MAKEDEV in /dev So I'm going to try 'make world kernel' and hope for the best... Thanks! Jeff (4.5-INSTALL) dmesg output follows: Copyright (c) 1992-2002 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 4.5-RELEASE #2: Tue Jan 29 22:44:12 GMT 2002 [EMAIL PROTECTED]:/usr/src/sys/compile/BOOTMFS Timecounter i8254 frequency 1193182 Hz Timecounter TSC frequency 794926962 Hz CPU: Pentium III/Pentium III Xeon/Celeron (794.93-MHz 686-class CPU) Origin = GenuineIntel Id = 0x6b1 Stepping = 1 Features=0x383f9ffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR,SSE real memory = 266862592 (260608K bytes) config intro \^[[m\^[[H\^[[J\^[[3;26H\^[[m\^[[1m\^[[m\^[[6;11H\^[[m\^[[7m\^[[m\^[[7;11H\^[[m\^[[8;11H\^[[m\^[[11;3H\^[[m\^[[12;3H\^[[m\^[[13;3H\^[[m\^[[15;3H\^[[m\^[[16;3H\^[[m\^[[18;3H\^[[m\^[[19;3H\^[[m\^[[21;3H\^[[m\^[[7m\^[[m\^[[22;3H\^[[m\^[[1;1H\^[[6;11H\^[[m\^[[7;11H\^[[m\^[[7m\^[[m\^[[8;11H\^[[m\^[[1;1H\^[[m\^[[H\^[[J\^[[m\^[[H\^[[J\^[[1;1H\^[[m\^[[1;4H\^[[m\^[[1m\^[[m\^[[1m\^[[1;64H\^[[m\^[[1m\^[[m\^[[1m\^[[m\^[[1m\^[[10;1H\^[[m\^[[10;4H\^[[m\^[[1m\^[[m\^[[1m\^[[10;64H\^[[m\^[[1m\^[[18;1H\^[[m\^[[22;1H\^[[m\^[[m\^[[24;1H\^[[m\^[[24;1H\^[[m\^[[1m\^[[m\^[[1m\^[[m\^[[1m\^[[m\^[[1;46H\^[[m\^[[7m\^[[2;1H\^[[m\^[[2;1H\^[[3;1H\^[[m\^[[3;1H\^[[4;1H\^[[m\^[[4;1H\^[[5;1H\^[[m\^[[5;1H\^[[6;1H\^[[m\^[[6;1H\^[[7;1H\^[[m\^[[7;1H\^[[m\^[[8;1H\^[[m\^[[m\^[[9;1H\^[[m\^[[11;1H\^[[m\^[[11;1H\^[[12;1H\^[[m\^[[12;1H\^[[13;1H\^[[m\^[[13;1H\^[[14;1H\^[[m\^[[14;1H\^[[15;1H\^[[m\^[[15;1H\^[[16;1H\^[[m\^[[16;1H\^[[m\^[[17;1H\^[[m\^[[m\^[[19;1H\^[[m\^[[20;1H\^[[m\^[[21;1H\^[[m\^[[2;1H\^[[m\^[[7m\^[[m\^[[2! 3;1H\^[[m\^[[23;1H\^[[m\^[[m\^[[23;1H\^[[m\^[[23;1H\^[[m\^[[1m\^[[m\^[[1m\^[[m\^[[2;1H\^[[1;46H\^[[m\^[[7m\^[[2;1H\^[[m\^[[2;1H\^[[3;1H\^[[m\^[[3;1H\^[[4;1H\^[[m\^[[4;1H\^[[5;1H\^[[m\^[[5;1H\^[[6;1H\^[[m\^[[6;1H\^[[7;1H\^[[m\^[[7;1H\^[[8;1H\^[[m\^[[8;1H\^[[9;1H\^[[m\^[[9;1H\^[[m\^[[19;1H\^[[m\^[[20;1H\^[[m\^[[21;1H\^[[m\^[[2;1H\^[[m\^[[7m\^[[m\^[[23;1H\^[[m\^[[23;1H\^[[m\^[[m\^[[23;1H\^[[m\^[[23;1H\^[[m\^[[1m\^[[m\^[[1m\^[[m\^[[2;1H\^[[2;1H\^[[m\^[[m\^[[23;1H\^[[m\^[[23;1H\^[[m\^[[m\^[[23;1H\^[[m\^[[23;1H\^[[m\^[[1m\^[[m\^[[1m\^[[m\^[[2;1H\^[[m\^[[19;1H\^[[m\^[[20;1H\^[[m\^[[21;1H\^[[m\^[[21;2H\^[[m\^[[3;1H\^[[m\^[[7m\^[[m\^[[23;1H\^[[m\^[[23;1H\^[[m\^[[1m\^[[m\^[[1m\^[[m\^[[3;1H\^[[1;46H\^[[m\^[[7m\^[[2;1H\^[[m\^[[2;1H\^[[3;1H\^[[m\^[[3;1H\^[[4;1H\^[[m\^[[4;1H\^[[5;1H\^[[m\^[[5;1H\^[[6;1H\^[[m\^[[6;1H\^[[7;1H\^[[m\^[[7;1H\^[[8;1H\^[[m\^[[8;1H\^[[9;1H\^[[m\^[[9;1H\^[[11;1H\^[[m\^[[11;1H\^[[12;1H\^[[m\^[[12;1H\^[[13;1H\^[[m\^[[13;1H\^[[14;1H\^[[m\^[[14;1H\^[[15;1H\^[[m\^[[15;! 1H\^[[16;1H\^[[m\^[[16;1H\^[[m\^[[17;1H\^[[m\^[[m\^[[19;1H\^[[m\^[[20;1H\^[[m\^[[21;1H\^[[m\^[[21;2H\^[[m\^[[3;1H\^[[m\^[[7m\^[[m\^[[23;1H\^[[m\^[[23;1H\^[[m\^[[1m\^[[m\^[[1m\^[[m\^[[3;1H\^[[1;46H\^[[m\^[[7m\^[[2;1H\^[[m\^[[2;1H\^[[3;1H\^[[m\^[[3;1H\^[[4;1H\^[[m\^[[4;1H\^[[5;1H\^[[m\^[[5;1H\^[[6;1H\^[[m\^[[6;1H\^[[7;1H\^[[m\^[[7;1H\^[[8;1H\^[[m\^[[8;1H\^[[9;1H\^[[m\^[[9;1H\^[[11;1H\^[[m\^[[11;1H\^[[12;1H\^[[m\^[[12;1H\^[[13;1H\^[[m\^[[13;1H\^[[14;1H\^[[m\^[[14;1H\^[[15;1H\^[[m\^[[15;1H\^[[16;1H\^[[m\^[[16;1H\^[[m\^[[17;1H\^[[m\^[[m\^[[19;1H\^[[m\^[[20;1H\^[[m\^[[21;1H\^[[m\^[[21;2H\^[[m\^[[3;1H\^[[m\^[[7m\^[[m\^[[23;1H\^[[m\^[[23;1H\^[[m\^[[1m\^[[m\^[[1m\^[[m\^[[3;1H\^[[1;46H
Re: MAKEDEV on -current
In message [EMAIL PROTECTED] Raphael Korsoski writes: : After upgrading from -STABLE I no longer have a MAKEDEV script in my /dev : I didn't find anything on this in UPDATING, so I suspect I ought to have : one :) : I think I've missed something, so any pointers would be appreciated. DEVFS doesn't need MAKEDEV. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
MAKEDEV on -current
After upgrading from -STABLE I no longer have a MAKEDEV script in my /dev I didn't find anything on this in UPDATING, so I suspect I ought to have one :) I can't simply cp it from /usr/src/etc/ since cp doesn't seem to like devfs. I think I've missed something, so any pointers would be appreciated. __ |hack mode n.| || | A Zen-like state of total focus on The Problem | | that may be achieved when one is hacking. | -- To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: MAKEDEV on -current
On Sat, 10 Nov 2001, Raphael Korsoski wrote: GAAAK! Ignore this message, I re-read it an realised how stupid it was. Naturally, as I wrote, I'm now using devfs, which explains everything ... I can't simply cp it from /usr/src/etc/ since cp doesn't seem to like devfs. I think I've missed something, so any pointers would be appreciated. Well, yes, I did miss something! __ |hack mode n.| || | A Zen-like state of total focus on The Problem | | that may be achieved when one is hacking. | -- To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
No MAKEDEV?
I just upgraded a fresh install of 4.2 to CURRENT. Everything seemed to go great until I discovered that I have only a small subset of the standard entries in /dev and there is no /dev/MAKEDEV or /dev/MAKEDEV.local. I re-cvsup'd again this morning and repeated the entire makeworld makekernel installkernel installworld mergemaster cycle a second time. It all went great except that I still have no MAKEDEV in /dev and very few entries in /dev, all of which are dated today. I've tried using 'install' to move /usr/src/etc/MAKEDEV into /dev, and tried cp and mv and even did a 'make distribution' from /usr/src/etc and always get an 'operation not supported' error message. I did all these things in single-user mode, BTW. Second question: what is the status of /stand/sysinstall? I see that the new version is in /usr/sbin. Is the old location obsolete? Thanks for any clues! To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: No MAKEDEV?
On Mon, Apr 16, 2001 at 12:36:10PM -0700, walt said: I just upgraded a fresh install of 4.2 to CURRENT. Everything seemed to go great until I discovered that I have only a small subset of the standard entries in /dev and there is no /dev/MAKEDEV or /dev/MAKEDEV.local. I re-cvsup'd again this morning and repeated the entire makeworld makekernel installkernel installworld mergemaster cycle a second time. It all went great except that I still have no MAKEDEV in /dev and very few entries in /dev, all of which are dated today. I've tried using 'install' to move /usr/src/etc/MAKEDEV into /dev, and tried cp and mv and even did a 'make distribution' from /usr/src/etc and always get an 'operation not supported' error message. I did all these things in single-user mode, BTW. I don't run -CURRENT, but check your kernel configuration for "devfs", this basically dynamically creates /dev entries when required, rather than having the entire lot there. Have you actually had any problems with the machine as a result of the tiny amount of /dev entries? If not, I wouldn't worry too much. -- "People who bite the hand that feeds them usually lick the boot that kicks them." -- Unknown. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: No MAKEDEV?
On Mon, Apr 16, 2001 at 12:36:10PM -0700, walt wrote: I just upgraded a fresh install of 4.2 to CURRENT. Everything seemed to go great until I discovered that I have only a small subset of the standard entries in /dev and there is no /dev/MAKEDEV or /dev/MAKEDEV.local. I re-cvsup'd again this morning and repeated the entire makeworld makekernel installkernel installworld mergemaster cycle a second time. It all went great except that I still have no MAKEDEV in /dev and very few entries in /dev, all of which are dated today. devfs(5) I've tried using 'install' to move /usr/src/etc/MAKEDEV into /dev, and tried cp and mv and even did a 'make distribution' from /usr/src/etc and always get an 'operation not supported' error message. I did all these things in single-user mode, BTW. Second question: what is the status of /stand/sysinstall? I see that the new version is in /usr/sbin. Is the old location obsolete? See /usr/src/UPDATING for all the answers :) -- Chris D. Faulhaber - [EMAIL PROTECTED] - [EMAIL PROTECTED] FreeBSD: The Power To Serve - http://www.FreeBSD.org PGP signature
Re: No MAKEDEV?
On Mon, Apr 16, 2001 at 03:51:19PM -0400, Chris Faulhaber wrote: On Mon, Apr 16, 2001 at 12:36:10PM -0700, walt wrote: Second question: what is the status of /stand/sysinstall? I see that the new version is in /usr/sbin. Is the old location obsolete? See /usr/src/UPDATING for all the answers :) Ok, I lied. Yes, /usr/sbin is the new location for sysinstall... -- Chris D. Faulhaber - [EMAIL PROTECTED] - [EMAIL PROTECTED] FreeBSD: The Power To Serve - http://www.FreeBSD.org PGP signature
Re: cp MAKEDEV /dev - on a system with devfs
Brian Somers [EMAIL PROTECTED] wrote: I thought only sysv kept non-startup executables in /etc. There's one real oddity in FreeBSD: [EMAIL PROTECTED]:/etc :; ll rmt lrwxrwxrwx 1 root wheel 13 Jan 28 13:42 rmt - /usr/sbin/rmt* Plus the rc scripts, dhclient-exit-hooks, pccard_ether, and netstart. Tony. -- f.a.n.finch [EMAIL PROTECTED] [EMAIL PROTECTED] "I never wanted to be a weather forecaster -- I wanted to be... a lumberjack! Leaping from tree to tree as they float down the mighty rivers of British Columbia! The giant redwood! The larch! The The mighty scots pine! ..." To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: cp MAKEDEV /dev - on a system with devfs
Brian Somers [EMAIL PROTECTED] wrote: I thought only sysv kept non-startup executables in /etc. There's one real oddity in FreeBSD: [EMAIL PROTECTED]:/etc :; ll rmt lrwxrwxrwx 1 root wheel 13 Jan 28 13:42 rmt - /usr/sbin/rmt* I think that's there for compatibility... programs that want to talk to remote tapes execute ``rsh /etc/rmt ...'' (or is ssh the default these days?). Plus the rc scripts, dhclient-exit-hooks, pccard_ether, and netstart. I guess you could argue that these are more like executable system configuration files, along with others like /etc/start_if.iface. Tony. -- f.a.n.finch [EMAIL PROTECTED] [EMAIL PROTECTED] "I never wanted to be a weather forecaster -- I wanted to be... a lumberjack! Leaping from tree to tree as they float down the mighty rivers of British Columbia! The giant redwood! The larch! The The mighty scots pine! ..." -- Brian [EMAIL PROTECTED]brian@[uk.]FreeBSD.org http://www.Awfulhak.org brian@[uk.]OpenBSD.org Don't _EVER_ lose your sense of humour ! To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: cp MAKEDEV /dev - on a system with devfs
On Tue, 13 Mar 2001 22:38:22 +, Tony Finch [EMAIL PROTECTED] said: There's one real oddity in FreeBSD: lrwxrwxrwx 1 root wheel 13 Jan 28 13:42 rmt - /usr/sbin/rmt* The pathname of the `rmt' program is a fundamental part of the `rmt' ``protocol'' such as it is. We've been over this one many times. -GAWollman To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
cp MAKEDEV /dev - on a system with devfs
Hi, In /usr/src/etc/Makefile: "make distribution" is still trying to copy MAKEDEV to /dev on a system with devfs mounted to /dev. Since devfs is default, is this behaviour correct or my /etc/make.conf is missing something ? regards, -- Jean Louis Ntakpe Texas Instruments - Freising [EMAIL PROTECTED] Wafer Fab Automation Group [EMAIL PROTECTED] Haggerty Str. 1 85350 Freising Telefon +49 (8161) 80-3816 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: cp MAKEDEV /dev - on a system with devfs
In message [EMAIL PROTECTED], Jean Louis Ntakpe writes: Hi, In /usr/src/etc/Makefile: "make distribution" is still trying to copy MAKEDEV to /dev on a system with devfs mounted to /dev. Since devfs is default, is this behaviour correct or my /etc/make.conf is missing something ? I think that MAKEDEV should be moved away from /dev. Ideally it belongs somewhere rather obscure, but /etc/MAKEDEV is ok with me. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 [EMAIL PROTECTED] | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: cp MAKEDEV /dev - on a system with devfs
In message [EMAIL PROTECTED], Jean Louis Ntakpe writes: Hi, In /usr/src/etc/Makefile: "make distribution" is still trying to copy MAKEDEV to /dev on a system with devfs mounted to /dev. Since devfs is default, is this behaviour correct or my /etc/make.conf is missing something ? I think that MAKEDEV should be moved away from /dev. Ideally it belongs somewhere rather obscure, but /etc/MAKEDEV is ok with me. /sbin would be better. I thought only sysv kept non-startup executables in /etc. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 [EMAIL PROTECTED] | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. -- Brian [EMAIL PROTECTED]brian@[uk.]FreeBSD.org http://www.Awfulhak.org brian@[uk.]OpenBSD.org Don't _EVER_ lose your sense of humour ! To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
MAKEDEV broken
Hi
It looks like a function got left out of MAKEDEV.
This seems to fix it:
Index: /usr/src/etc/MAKEDEV
===
RCS file: /home/ncvs/src/etc/MAKEDEV,v
retrieving revision 1.268
diff -u -d -r1.268 MAKEDEV
--- /usr/src/etc/MAKEDEV2000/08/16 16:42:50 1.268
+++ /usr/src/etc/MAKEDEV2000/08/18 06:01:10
@@ -221,6 +221,12 @@
echo $$1 8) 16) | ($1 % 256)))
}
+# Convert a minor number to a unit number.
+minor2unit()
+{
+ echo $$1 16) 8) | ($1 % 256)))
+}
+
# Raw partition for disks
dkrawpart=2
M
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: MAKEDEV broken
Oops, I meant unit2minor for ugen urio :-/
Hi
It looks like a function got left out of MAKEDEV.
This seems to fix it:
Index: /usr/src/etc/MAKEDEV
===
RCS file: /home/ncvs/src/etc/MAKEDEV,v
retrieving revision 1.268
diff -u -d -r1.268 MAKEDEV
--- /usr/src/etc/MAKEDEV 2000/08/16 16:42:50 1.268
+++ /usr/src/etc/MAKEDEV 2000/08/18 06:01:10
@@ -221,6 +221,12 @@
echo $$1 8) 16) | ($1 % 256)))
}
+# Convert a minor number to a unit number.
+minor2unit()
+{
+ echo $$1 16) 8) | ($1 % 256)))
+}
+
# Raw partition for disks
dkrawpart=2
M
--
Brian [EMAIL PROTECTED]brian@[uk.]FreeBSD.org
http://www.Awfulhak.org brian@[uk.]OpenBSD.org
Don't _EVER_ lose your sense of humour !
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: MAKEDEV Warning ???
At 09:18 PM 5/13/2000 +0200, Poul-Henning Kamp wrote: In message [EMAIL PROTECTED], Jeroen Ruigrok van der Werv en writes: -On [2513 21:06], Manfred Antar ([EMAIL PROTECTED]) wrote: I get this in boot mesgs and I don't know how to fix it. Device char-major=13 minor=0 opened in block mode, convert to char mode with /dev/MAKEDEV before 2000-07-01 There is a bug somewhere in the rootmount code. I just lack the expertise to find out where it is. Actually I think this is an indication of really old boot blocks. The old bootblocks passed in a Bmajor number for the root device. Could you try to update your bootblocks with the disklabel program and see if that stops the warning Manfred ? I did a disklabel -B da0 and it still happens Another thing is this is a RAID 1 disk 2 disk mirror on a DPT RAID controller I don't know if that make a difference. Which is the dev I'm supposed to be using : rda0a, da0a, da0s1a ?? Manfred = ||[EMAIL PROTECTED] || ||Ph. (415) 681-6235|| = To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: MAKEDEV Warning ???
In message [EMAIL PROTECTED], Jeroen Ruigrok van der Werv en writes: -On [2513 21:06], Manfred Antar ([EMAIL PROTECTED]) wrote: I get this in boot mesgs and I don't know how to fix it. Device char-major=13 minor=0 opened in block mode, convert to char mode with /dev/MAKEDEV before 2000-07-01 There is a bug somewhere in the rootmount code. I just lack the expertise to find out where it is. Actually I think this is an indication of really old boot blocks. The old bootblocks passed in a Bmajor number for the root device. Could you try to update your bootblocks with the disklabel program and see if that stops the warning Manfred ? -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 [EMAIL PROTECTED] | TCP/IP since RFC 956 FreeBSD coreteam member | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
MAKEDEV Warning ???
I get this in boot mesgs and I don't know how to fix it. Device char-major=13 minor=0 opened in block mode, convert to char mode with /dev/MAKEDEV before 2000-07-01 I've run MAKEDEV all I have a simple fstab: # DeviceMountpoint FStype Options DumpPass# /dev/rda0b noneswapsw 0 0 /dev/da0a / ufs rw 1 1 /dev/rda0e/varufs rw 2 2 /dev/rda0f /usrufs rw 2 2 /dev/rda0g/usr/obj ufs rw 2 2 proc/proc procfs rw 0 0 If i change /dev/da0a to /dev/rda0a it won't mount. If i use this I still get the same message: # DeviceMountpoint FStype Options DumpPass# /dev/da0b noneswapsw 0 0 /dev/da0a / ufs rw 1 1 /dev/da0e/varufs rw 2 2 /dev/da0f /usrufs rw 2 2 /dev/da0g/usr/obj ufs rw 2 2 proc/proc procfs rw 0 0 This also causes the same message: /dev/da0s1b noneswapsw 0 0 /dev/da0s1a / ufs rw 1 1 /dev/da0s1e/varufs rw 2 2 /dev/da0s1f /usrufs rw 2 2 /dev/da0s1g/usr/obj ufs rw 2 2 proc/proc procfs rw 0 0 Which is correct ?? Also I've tried changing the ROOTDEV option in my kernel config to no avail Thanks Manfred = ||[EMAIL PROTECTED] || ||Ph. (415) 681-6235|| = To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: MAKEDEV Warning ???
-On [2513 21:06], Manfred Antar ([EMAIL PROTECTED]) wrote: I get this in boot mesgs and I don't know how to fix it. Device char-major=13 minor=0 opened in block mode, convert to char mode with /dev/MAKEDEV before 2000-07-01 There is a bug somewhere in the rootmount code. I just lack the expertise to find out where it is. -- Jeroen Ruigrok van der Werven Network- and systemadministrator [EMAIL PROTECTED]VIA Net.Works The Netherlands BSD: Technical excellence at its best http://www.via-net-works.nl I believe because it is impossible... To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: MAKEDEV Warning ???
At 09:54 PM 5/13/2000 +0200, Assar Westerlund wrote: Jeroen Ruigrok van der Werven [EMAIL PROTECTED] writes: -On [2513 21:06], Manfred Antar ([EMAIL PROTECTED]) wrote: I get this in boot mesgs and I don't know how to fix it. Device char-major=13 minor=0 opened in block mode, convert to char mode with /dev/MAKEDEV before 2000-07-01 There is a bug somewhere in the rootmount code. The following patch fixed the problem for me. For extra points, rename the function. /assar --- vfs_subr.c~ Sat May 6 00:08:38 2000 +++ vfs_subr.c Sat May 13 21:47:08 2000 @@ -1296,7 +1296,7 @@ return (error); } vp = nvp; - vp-v_type = VBLK; + vp-v_type = VCHR; addalias(vp, dev); *vpp = vp; return (0); That works for me too . Which is the correct dev /dev/da0a , /dev/rda0a , or /dev/da0s1a to use rda0a won't work. da0a works fine and I got rid of all the da0s1a,b,e,f,g ones ? Manfred = ||[EMAIL PROTECTED] || ||Ph. (415) 681-6235|| = To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: MAKEDEV Warning ???
In message [EMAIL PROTECTED], Manfred Antar writes: --- vfs_subr.c~ Sat May 6 00:08:38 2000 +++ vfs_subr.c Sat May 13 21:47:08 2000 @@ -1296,7 +1296,7 @@ return (error); } vp = nvp; - vp-v_type = VBLK; + vp-v_type = VCHR; addalias(vp, dev); *vpp = vp; return (0); That works for me too . Yes, that looks correct. Which is the correct dev /dev/da0a , /dev/rda0a , or /dev/da0s1a to use rda0a won't work. da0a works fine and I got rid of all the da0s1a,b,e,f,g ones ? In all likelyhood /dev/da0s1a is the one you should use. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 [EMAIL PROTECTED] | TCP/IP since RFC 956 FreeBSD coreteam member | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: MAKEDEV Warning ???
At 10:28 PM 5/13/2000 +0200, Jeroen Ruigrok van der Werven wrote: -On [2513 22:08], Manfred Antar ([EMAIL PROTECTED]) wrote: Which is the correct dev /dev/da0a , /dev/rda0a , or /dev/da0s1a to use rda0a won't work. da0a works fine and I got rid of all the da0s1a,b,e,f,g ones ? The /dev/da0s1a would be the correct one to use, example: # DeviceMountpoint FStype Options DumpPass# /dev/da0s1b noneswapsw 0 0 /dev/da0s1a / ufs rw 1 1 /dev/da0s1e /tmpufs rw 2 2 /dev/da0s1g /usrufs rw 2 2 /dev/da0s1f /varufs rw 2 2 /dev/da0s1h /work ufs rw 2 2 /dev/cd0c /cdrom cd9660 ro,noauto 0 0 proc/proc procfs rw 0 0 /dev/fd0/diskette msdos rw,noauto 0 0 -- Jeroen Ruigrok van der Werven Network- and systemadministrator [EMAIL PROTECTED]VIA Net.Works The Netherlands BSD: Technical excellence at its best http://www.via-net-works.nl I walk, I walk alone, into the promised land... OK Thats what I was using before. MAKEDEV doesn't automatically create the s1a devices so I switched thinking that what was causing the error Thanks Manfred = ||[EMAIL PROTECTED] || ||Ph. (415) 681-6235|| = To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: MAKEDEV Warning ???
The following patch fixed the problem for me. For extra points, rename the function. That fixed the problem for the me too. Thanks! Steinar Haug, Nethelp consulting, [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: MAKEDEV Warning ???
Actually I think this is an indication of really old boot blocks. The old bootblocks passed in a Bmajor number for the root device. Could you try to update your bootblocks with the disklabel program and see if that stops the warning Manfred ? I can't speak for this case, but the one I reported is with brand new boot blocks, installed after a -current buildworld today. Steinar Haug, Nethelp consulting, [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: MAKEDEV Warning ???
Jeroen Ruigrok van der Werven [EMAIL PROTECTED] writes: -On [2513 21:06], Manfred Antar ([EMAIL PROTECTED]) wrote: I get this in boot mesgs and I don't know how to fix it. Device char-major=13 minor=0 opened in block mode, convert to char mode with /dev/MAKEDEV before 2000-07-01 There is a bug somewhere in the rootmount code. The following patch fixed the problem for me. For extra points, rename the function. /assar --- vfs_subr.c~ Sat May 6 00:08:38 2000 +++ vfs_subr.c Sat May 13 21:47:08 2000 @@ -1296,7 +1296,7 @@ return (error); } vp = nvp; - vp-v_type = VBLK; + vp-v_type = VCHR; addalias(vp, dev); *vpp = vp; return (0); To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: MAKEDEV Warning ???
-On [2513 22:08], Manfred Antar ([EMAIL PROTECTED]) wrote: Which is the correct dev /dev/da0a , /dev/rda0a , or /dev/da0s1a to use rda0a won't work. da0a works fine and I got rid of all the da0s1a,b,e,f,g ones ? The /dev/da0s1a would be the correct one to use, example: # DeviceMountpoint FStype Options DumpPass# /dev/da0s1b noneswapsw 0 0 /dev/da0s1a / ufs rw 1 1 /dev/da0s1e /tmpufs rw 2 2 /dev/da0s1g /usrufs rw 2 2 /dev/da0s1f /varufs rw 2 2 /dev/da0s1h /work ufs rw 2 2 /dev/cd0c /cdrom cd9660 ro,noauto 0 0 proc/proc procfs rw 0 0 /dev/fd0/diskette msdos rw,noauto 0 0 -- Jeroen Ruigrok van der Werven Network- and systemadministrator [EMAIL PROTECTED]VIA Net.Works The Netherlands BSD: Technical excellence at its best http://www.via-net-works.nl I walk, I walk alone, into the promised land... To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: MAKEDEV Warning ???
I get this in boot mesgs and I don't know how to fix it. Device char-major=13 minor=0 opened in block mode, convert to char mode with /dev/MAKEDEV before 2000-07-01 There is a bug somewhere in the rootmount code. It's the following VFS_MOUNT call at line 215 of vfs_mountroot_try() (/sys/kern/vfs_conf.c): error = VFS_MOUNT(mp, NULL, NULL, NULL, curproc); Steinar Haug, Nethelp consulting, [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: MAKEDEV warning with sysinstall ?
No, I havn't tracked down the last couple of causes of this, but I will try to reproduce it as you describe it with some debugging added. How hard would it be to print the filename (or the device/inode) that triggers the warning? Not at all (warning: cutpasted patch, tabs are screwed up!) A similar message is in /sys/miscfs/specfs/spec_vnops.c now. Anyway, there is still at least one case of devices being opened in block mode in the *kernel*, namely the following VFS_MOUNT call at line 215 of vfs_mountroot_try() (/sys/kern/vfs_conf.c): error = VFS_MOUNT(mp, NULL, NULL, NULL, curproc); Typical message: May 13 20:36:29 bp6 /kernel: Mounting root from ufs:/dev/ad0s1d May 13 20:36:29 bp6 /kernel: Device char-major=116 minor=131075 opened in block mode, convert to char mode with /dev/MAKEDEV before 2000-07-01 (Yes, I have -current root on ad0s1d, and -stable root on ad0s1a.) Steinar Haug, Nethelp consulting, [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Small MAKEDEV bug
On Tue, 09 May 2000 10:26:05 +0200, Sheldon Hearn wrote: I don't agree. I think this is an issue of avoiding changes that unnecessarily astonish existing users. If you can find ways to improve MAKEDEV that don't inconvenience those already familiar with it, great. If your improvements astonish these people, you need to put a bit more thought into what you're actually scoring. I'd like to follow up on myself with a comment that takes a slightly broader view on the problem. As FreeBSD's user base grows, we're going to see two different demands in increasing contention with each other. 1) The demand for an intuitive, consistent interface. 2) The demand for a constant interface. The former represents the need for POLA to be upheld throughout the system at a given moment in time. The latter represents the need for POLA to be upheld from one release to the next, in the arena of "backward compatibility". Both are valid issues that deserve careful thought. In many situations, we can fix inconsistencies "in the moment" without forcing folks to change the way they do things from on release to the next. In those situations where we have to make a decision one way or another, the decision is going to become more and more difficult as the project moves forward. I don't think that the only rule of thumb that can be applied where the two demands are in contention with one another, is that it's worth thinking carefully about what we gain for the change. But we can _certainly_ agree that it's always worth thinking carefully about ways to satisfy _both_ demands wherever possible. Ciao, Sheldon. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: MAKEDEV warning with sysinstall ?
On Mon, 08 May 2000 15:41:55 EST, Erik de Zeeuw wrote: I ran MAKEDEV all, but the message still appear. The messages I found about this on the archives says to do a 'ls -l /dev | grep ^b', and to remake all devices listed, but there's no device listed when I'm doing the 'ls -l /dev | grep ^b'. I'm not sure what that'll score you. Try this: cd /dev for i in `ls`; do if test -b $i; then echo $i; fi; done Ciao, Sheldon. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Small MAKEDEV bug
On Mon, 8 May 2000, Tim Vanderhoek wrote: On Mon, May 08, 2000 at 06:56:03PM -0400, Jeroen C. van Gelderen wrote: I don't buy it :-). This syntax is similar to a special case of the syntax of jot(1). It's better to use jot(1) directly, e.g.: MAKEDEV $(jot -w da 2 0)# make 2 acd devices beginning at acd0 b$ which jot /usr/bin/jot b$ The jot utility doesn't appear to be in /bin. You can just type all the device names or use a shell loop when /usr/bin is not mounted. b$ echo '$(jot -w da 2 0)' | wc 1 5 17 b$ echo $(jot -w da 2 0) | wc 1 2 8 b$ Heh. Yes, it is much faster to type all the device names than to even type the command to generate them when there are a small number of device names. /me mumbles something about the prototypical UNIX hacker... :-) I wouldn't use jot for MAKEDEV'ing disks in practice :-). Part of my point is the new syntax for MAKEDEV is just as hard to remember as the syntax for jot. You would use it once or twice per millenium after install more than about 8 drives at once. Bruce To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: MAKEDEV warning with sysinstall ?
On Tue, 9 May 2000, Sheldon Hearn wrote: On Mon, 08 May 2000 15:41:55 EST, Erik de Zeeuw wrote: I ran MAKEDEV all, but the message still appear. The messages I found about this on the archives says to do a 'ls -l /dev | grep ^b', and to remake all devices listed, but there's no device listed when I'm doing the 'ls -l /dev | grep ^b'. I'm not sure what that'll score you. Try this: cd /dev for i in `ls`; do if test -b $i; then echo $i; fi; done Hmmm... find /dev -type b -print - Chris D. Faulhaber - [EMAIL PROTECTED] - [EMAIL PROTECTED] FreeBSD: The Power To Serve - http://www.FreeBSD.org To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Small MAKEDEV bug
In message [EMAIL PROTECTED], "David O'Brien" writes: On Sun, May 07, 2000 at 03:27:07PM -0400, Jeroen C. van Gelderen wrote: Or just settle for a more intuitive solution: MAKEDEV acd2 creates /dev/acd2 MAKEDEV 2 acd creates /dev/acd[01] which would allow for "MAKEDEV 64 da" and "MAKEDEV 256 pty" I agree with this syntax and after sending my message to you, was sitting there thinking "MAKEDEV num_of_devs dev_name" would make a really nice clear syntax. If you can get BDE's buy-in and other BSD traditionalists I think this would be great. Make it MAKEDEV -num_of_devs dev_name and there will be no ambiguity. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 [EMAIL PROTECTED] | TCP/IP since RFC 956 FreeBSD coreteam member | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Small MAKEDEV bug
David O'Brien wrote: On Sun, May 07, 2000 at 03:27:07PM -0400, Jeroen C. van Gelderen wrote: Or just settle for a more intuitive solution: MAKEDEV acd2 creates /dev/acd2 MAKEDEV 2 acd creates /dev/acd[01] which would allow for "MAKEDEV 64 da" and "MAKEDEV 256 pty" I agree with this syntax and after sending my message to you, was sitting there thinking "MAKEDEV num_of_devs dev_name" would make a really nice clear syntax. If you can get BDE's buy-in and other BSD traditionalists I think this would be great. The good part of this solution is that it's backwards compatible. If the first argument is an integer and the second a device name without a suffix we do the new thing, if not we revert to the traditional behaviour. bde: what do you think? Cheers, Jeroen To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Small MAKEDEV bug
On Mon, 8 May 2000, David O'Brien wrote: On Sun, May 07, 2000 at 03:27:07PM -0400, Jeroen C. van Gelderen wrote: Or just settle for a more intuitive solution: MAKEDEV acd2 creates /dev/acd2 MAKEDEV 2 acd creates /dev/acd[01] which would allow for "MAKEDEV 64 da" and "MAKEDEV 256 pty" I agree with this syntax and after sending my message to you, was sitting there thinking "MAKEDEV num_of_devs dev_name" would make a really nice clear syntax. If you can get BDE's buy-in and other BSD traditionalists I think this would be great. I don't buy it :-). This syntax is similar to a special case of the syntax of jot(1). It's better to use jot(1) directly, e.g.: MAKEDEV $(jot -w da 2 0)# make 2 acd devices beginning at acd0 Bruce To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
MAKEDEV warning with sysinstall ?
I installed FreeBSD 5.0-2506-CURRENT on an AMD K6-2, 64Mb, 4Gb, and when I first launch /stand/sysinstall after the system has start, the following message appears : ... /kernel: WARNING: run /dev/MAKEDEV before 2000-06-01 to get rid of block devices I searched the list archives and find some informations about this, but nothing that helps me understand why I get this message. The only time it happens is when I use sysinstall for the first time after the PC has start. If I'm using sysinstall again without prior reboot, there's no such message. But if I reboot and use sysinstall again, the message shows up again. I ran MAKEDEV all, but the message still appear. The messages I found about this on the archives says to do a 'ls -l /dev | grep ^b', and to remake all devices listed, but there's no device listed when I'm doing the 'ls -l /dev | grep ^b'. Any idea about what could cause this message to come up ? Thanks, Erik de Zeeuw To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: MAKEDEV warning with sysinstall ?
On Mon, May 08, 2000 at 03:41:55PM -0500, Erik de Zeeuw wrote: I installed FreeBSD 5.0-2506-CURRENT on an AMD K6-2, 64Mb, 4Gb, and when I first launch /stand/sysinstall after the system has start, the following message appears : ... /kernel: WARNING: run /dev/MAKEDEV before 2000-06-01 to get rid of block devices I searched the list archives and find some informations about this, but nothing that helps me understand why I get this message. This is because -current no longer has any block devices so /dev/MAKEDEV needs (well, it is cleaner) to remove the old device nodes. -- Wilko Bulte Powered by FreeBSD http://www.freebsd.org http://www.tcja.nl To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: MAKEDEV warning with sysinstall ?
In message [EMAIL PROTECTED], Erik de Zeeuw writes: I installed FreeBSD 5.0-2506-CURRENT on an AMD K6-2, 64Mb, 4Gb, and when I first launch /stand/sysinstall after the system has start, the following message appears : ... /kernel: WARNING: run /dev/MAKEDEV before 2000-06-01 to get rid of block devices I searched the list archives and find some informations about this, but nothing that helps me understand why I get this message. Any idea about what could cause this message to come up ? No, I havn't tracked down the last couple of causes of this, but I will try to reproduce it as you describe it with some debugging added. Thanks for the hint! -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 [EMAIL PROTECTED] | TCP/IP since RFC 956 FreeBSD coreteam member | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: MAKEDEV warning with sysinstall ?
In the last episode (May 08), Poul-Henning Kamp said: In message [EMAIL PROTECTED], Erik de Zeeuw writes: I installed FreeBSD 5.0-2506-CURRENT on an AMD K6-2, 64Mb, 4Gb, and when I first launch /stand/sysinstall after the system has start, the following message appears : ... /kernel: WARNING: run /dev/MAKEDEV before 2000-06-01 to get rid of block devices I searched the list archives and find some informations about this, but nothing that helps me understand why I get this message. Any idea about what could cause this message to come up ? No, I havn't tracked down the last couple of causes of this, but I will try to reproduce it as you describe it with some debugging added. How hard would it be to print the filename (or the device/inode) that triggers the warning? -- Dan Nelson [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: MAKEDEV warning with sysinstall ?
In message [EMAIL PROTECTED], Dan Nelson writes:
In the last episode (May 08), Poul-Henning Kamp said:
In message [EMAIL PROTECTED], Erik de Zeeuw writes:
I installed FreeBSD 5.0-2506-CURRENT on an AMD K6-2, 64Mb, 4Gb, and
when I first launch /stand/sysinstall after the system has start, the
following message appears :
... /kernel: WARNING: run /dev/MAKEDEV before 2000-06-01 to get rid of
block devices
I searched the list archives and find some informations about this, but
nothing that helps me understand why I get this message.
Any idea about what could cause this message to come up ?
No, I havn't tracked down the last couple of causes of this, but I
will try to reproduce it as you describe it with some debugging added.
How hard would it be to print the filename (or the device/inode) that
triggers the warning?
Not at all (warning: cutpasted patch, tabs are screwed up!)
Index: kern_conf.c
===
RCS file: /home/ncvs/src/sys/kern/kern_conf.c,v
retrieving revision 1.75
diff -u -r1.75 kern_conf.c
--- kern_conf.c 2000/03/25 21:10:20 1.75
+++ kern_conf.c 2000/05/06 15:06:33
@@ -270,7 +270,8 @@
if (!whine) {
printf("WARNING: run /dev/MAKEDEV before 2000-06-01 to
get rid of block devices\n");
whine++;
}
+ printf("Whine: %d/%d\n", umajor(x), uminor(x));
return makebdev(umajor(x), uminor(x));
default:
Debugger("udev2dev(...,X)");
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD coreteam member | BSD since 4.3-tahoe
Never attribute to malice what can adequately be explained by incompetence.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: Small MAKEDEV bug
Bruce Evans wrote: On Mon, 8 May 2000, David O'Brien wrote: On Sun, May 07, 2000 at 03:27:07PM -0400, Jeroen C. van Gelderen wrote: Or just settle for a more intuitive solution: MAKEDEV acd2 creates /dev/acd2 MAKEDEV 2 acd creates /dev/acd[01] which would allow for "MAKEDEV 64 da" and "MAKEDEV 256 pty" I agree with this syntax and after sending my message to you, was sitting there thinking "MAKEDEV num_of_devs dev_name" would make a really nice clear syntax. If you can get BDE's buy-in and other BSD traditionalists I think this would be great. I don't buy it :-). This syntax is similar to a special case of the syntax of jot(1). It's better to use jot(1) directly, e.g.: MAKEDEV $(jot -w da 2 0)# make 2 acd devices beginning at acd0 From this it follows that MAKEDEV should be modified to create just it's argument: MAKEDEV dev8 creates just dev8, not dev0-dev7. Otherwise MAKEDEV $(jot -w da 6 4) wouldn't work or violate POLA. Agreed? Now it's a question of "the UNIX way" vs. convenience/userfriendlyness :-) Is it acceptable to have all users juggle with jot(1) or can we build in a convenience syntax that covers 95% of all uses? I'd think the latter, otherwise we might as well force our users to use mknod(8) and chmod(1) directly instead of MAKEDEV; After all, MAKEDEV is just a convenient wrapper around those commands. So I'd still propose: MAKEDEV count device_name_without_suffix MAKEDEV device_name_with_suffix ... As a consolation, added such a special syntax can be added in a few lines at the top of MAKEDEV, after which it recursively calls MAKEDEV with the appropriate jot(1)-expanded device list. So it doesn't clobber the code. Thoughts? Cheers, Jeroen To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Small MAKEDEV bug
On Mon, May 08, 2000 at 06:56:03PM -0400, Jeroen C. van Gelderen wrote: I don't buy it :-). This syntax is similar to a special case of the syntax of jot(1). It's better to use jot(1) directly, e.g.: MAKEDEV $(jot -w da 2 0)# make 2 acd devices beginning at acd0 b$ which jot /usr/bin/jot b$ The jot utility doesn't appear to be in /bin. b$ echo '$(jot -w da 2 0)' | wc 1 5 17 b$ echo $(jot -w da 2 0) | wc 1 2 8 b$ Heh. /me mumbles something about the prototypical UNIX hacker... :-) -- Signature withheld by request of author. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Small MAKEDEV bug
-On [2506 21:55], Bruce Evans ([EMAIL PROTECTED]) wrote: On Sat, 6 May 2000, Maxim Sobolev wrote: I've just noticed that "sh MAKEDEV acd1" doesn't produce node for acd1 due to incorrect comparasion in the "while" loop. This affecting both 4.0-STABLE and 5.0-CURRENT. With this message I'm attaching short patch which should solve this little problem. This is the intended behaviour. "sh MAKEDEV acdN" is supposed to create N acd devices, numbered from 0 to N-1. This broken behaviour was introduced for cd*, mcd* and scd* in rev.1.171. It has since spread to acd*. Other types of disks are handled correctly. Bah, bah, bah. I am really starting to wonder about this sunburn thing. Can we settle this once and for all in a slightly sane manner? I committed the change so that MAKEDEV acd1 creates acd1 and not just acd0. I personally think this is more consistent with the wd/sa/da/ad numbering scheme and would propose to fix the other cd* entries likewise. Because otherwise somebody other than me will make the same (commit) mistake x days/weeks/months/years into the future. Opinions? -- Jeroen Ruigrok van der Werven Network- and systemadministrator [EMAIL PROTECTED]VIA Net.Works The Netherlands BSD: Technical excellence at its best http://www.via-net-works.nl In this short time of promise, you're a memory... To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Small MAKEDEV bug
On Sun, May 07, 2000 at 04:59:46PM +0200, Jeroen Ruigrok van der Werven wrote: Can we settle this once and for all in a slightly sane manner? I committed the change so that MAKEDEV acd1 creates acd1 and not just acd0. This is wrong. ``MAKEDEV acd2'' should either create only /dev/acd2*, or /dev/acd[01]*. It would be nice to fix our inconsistency problem. Looking at the 4.4Lite vendor import to find the BSD way would be a good start. -- -- David([EMAIL PROTECTED]) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Small MAKEDEV bug
[CC culled, -stable removed] David O'Brien wrote: On Sun, May 07, 2000 at 04:59:46PM +0200, Jeroen Ruigrok van der Werven wrote: Can we settle this once and for all in a slightly sane manner? I committed the change so that MAKEDEV acd1 creates acd1 and not just acd0. This is wrong. ``MAKEDEV acd2'' should either create only /dev/acd2*, or /dev/acd[01]*. It would be nice to fix our inconsistency problem. Looking at the 4.4Lite vendor import to find the BSD way would be a good start. Or just settle for a more intuitive solution: MAKEDEV acd2 creates /dev/acd2 MAKEDEV 2 acd creates /dev/acd[01] which would allow for "MAKEDEV 64 da" and "MAKEDEV 256 pty" -- David([EMAIL PROTECTED]) Jeroen To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Small MAKEDEV bug
Hi,
I've just noticed that "sh MAKEDEV acd1" doesn't produce node for acd1 due to
incorrect comparasion in the "while" loop. This affecting both 4.0-STABLE and
5.0-CURRENT. With this message I'm attaching short patch which should solve
this little problem.
-Maxim
--- MAKEDEV 2000/05/06 08:25:52 1.1
+++ MAKEDEV 2000/05/06 08:26:14
@@ -795,7 +795,7 @@
fi
if [ "${units}" -le 31 ]; then
i=0
- while [ $i -lt $units ]; do
+ while [ $i -le $units ]; do
dname=$name$i
rm -rf ${dname}* r${dname}*
mknod ${dname}a c $chr $(($i * 8)) root:operator
Re: Small MAKEDEV bug
On Sat, 6 May 2000, Maxim Sobolev wrote: I've just noticed that "sh MAKEDEV acd1" doesn't produce node for acd1 due to incorrect comparasion in the "while" loop. This affecting both 4.0-STABLE and 5.0-CURRENT. With this message I'm attaching short patch which should solve this little problem. This is the intended behaviour. "sh MAKEDEV acdN" is supposed to create N acd devices, numbered from 0 to N-1. This broken behaviour was introduced for cd*, mcd* and scd* in rev.1.171. It has since spread to acd*. Other types of disks are handled correctly. Bruce To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Small MAKEDEV bug
Bruce Evans wrote: On Sat, 6 May 2000, Maxim Sobolev wrote: I've just noticed that "sh MAKEDEV acd1" doesn't produce node for acd1 due to incorrect comparasion in the "while" loop. This affecting both 4.0-STABLE and 5.0-CURRENT. With this message I'm attaching short patch which should solve this little problem. This is the intended behaviour. "sh MAKEDEV acdN" is supposed to create N acd devices, numbered from 0 to N-1. This broken behaviour was introduced for cd*, mcd* and scd* in rev.1.171. It has since spread to acd*. Other types of disks are handled correctly. How broken behaviour could be "intended"? It is unclear why *cd* devices should be different from all others types of disk devices. Users usually being confused when dealing with special cases like that. I think that there will be no problem if it would create N+1 devices at least until someone will reimplement it correctly. -Maxim To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: MAKEDEV warning
Yep, that's the ticket ! Thanks. Yes, that was an oversight on my part. Please let me know if the fix I committed solves this issue. Poul-Henning In message [EMAIL PROTECTED], Brian Somers writes: I've got an mfs /tmp too :-] Hi, On 0, Ted Sikora [EMAIL PROTECTED] wrote: After building a new kernel yesterday after a cvsup the following appeared. Apr 17 23:07:42 telecast /kernel: WARNING: run /dev/MAKEDEV before 2000-06-01 to get rid of block devices I did a MAKEDEV all and the message still persists. I get this message too whenever I mount a mfs filesystem. The line in /etc/fstab is: /dev/da0s1b /tmp mfs rw,async,-s327680 0 The output of "ls -l /dev/*da0s1b" is: crw-r- 1 root operator 13, 0x00020001 Dec 12 21:09 /dev/da0s1b crw-r- 1 root operator 13, 0x00020001 Dec 12 21:09 /dev/rda0s1b Regards Dirk [.] -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 [EMAIL PROTECTED] | TCP/IP since RFC 956 FreeBSD coreteam member | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. -- Brian [EMAIL PROTECTED]brian@[uk.]FreeBSD.org http://www.Awfulhak.org brian@[uk.]OpenBSD.org Don't _EVER_ lose your sense of humour ! To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: MAKEDEV warning
I've got an mfs /tmp too :-] Hi, On 0, Ted Sikora [EMAIL PROTECTED] wrote: After building a new kernel yesterday after a cvsup the following appeared. Apr 17 23:07:42 telecast /kernel: WARNING: run /dev/MAKEDEV before 2000-06-01 to get rid of block devices I did a MAKEDEV all and the message still persists. I get this message too whenever I mount a mfs filesystem. The line in /etc/fstab is: /dev/da0s1b /tmp mfs rw,async,-s327680 0 The output of "ls -l /dev/*da0s1b" is: crw-r- 1 root operator 13, 0x00020001 Dec 12 21:09 /dev/da0s1b crw-r- 1 root operator 13, 0x00020001 Dec 12 21:09 /dev/rda0s1b Regards Dirk -- Brian [EMAIL PROTECTED]brian@[uk.]FreeBSD.org http://www.Awfulhak.org brian@[uk.]OpenBSD.org Don't _EVER_ lose your sense of humour ! To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: MAKEDEV warning
Yes, that was an oversight on my part. Please let me know if the fix I committed solves this issue. Poul-Henning In message [EMAIL PROTECTED], Brian Somers writes: I've got an mfs /tmp too :-] Hi, On 0, Ted Sikora [EMAIL PROTECTED] wrote: After building a new kernel yesterday after a cvsup the following appeared. Apr 17 23:07:42 telecast /kernel: WARNING: run /dev/MAKEDEV before 2000-06-01 to get rid of block devices I did a MAKEDEV all and the message still persists. I get this message too whenever I mount a mfs filesystem. The line in /etc/fstab is: /dev/da0s1b /tmp mfs rw,async,-s327680 0 The output of "ls -l /dev/*da0s1b" is: crw-r- 1 root operator 13, 0x00020001 Dec 12 21:09 /dev/da0s1b crw-r- 1 root operator 13, 0x00020001 Dec 12 21:09 /dev/rda0s1b Regards Dirk -- Brian [EMAIL PROTECTED]brian@[uk.]FreeBSD.org http://www.Awfulhak.org brian@[uk.]OpenBSD.org Don't _EVER_ lose your sense of humour ! -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 [EMAIL PROTECTED] | TCP/IP since RFC 956 FreeBSD coreteam member | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
