Re: Xircom RealPort 10/100 LAN modem?
In muc.lists.freebsd.questions, you wrote: > > Does anyone know of support for this PCMCIA card in FreeBSD? I have looked > everywhere and can't seem to find it anywhere...not good. I also have a > Linksys LANmodem 33.6 10Bast-T PCMCIA NIC. Anyone know if that one is > supported? For those interested, I just got my Xircom CE3 10/100 running on today's 5.0-current snapshot. It doesn't work on 4.x yet. -Arun To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Wrong permissions on /dev ?
I upgraded my 4.0-release laptop to 5.0-current today and my xe0 was recognized by the driver and everything was great. There is a minor nit about the permissions on /dev. It was not readable by others. So ps wouldn't work, because it could not open /dev/null. -Arun To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Anyone else seeing jumpy mice?
"Jordan K. Hubbard" wrote: > > No, I don't mean rodents who've nibbled on chocolate-covered expresso > beans, I mean PS/2 mice which fall victim to this new problem: > > May 19 00:50:45 zippy /kernel: psmintr: out of sync (00c0 != ). > > I've seen it for the last few weeks and can only think that something > must be stomping on the psm driver now (or the driver is missing > interrupts for reasons of its own). Anyone else seeing this? FWIW, with -current from 5/8, I don't have any of those in /var/log/messages, going back to 5/1. I have a logitech PS/2 mouse, and I don't use moused, since I couldn't get it to work with my wheel. HTH, Doug -- "Live free or die" - State motto of my ancestral homeland, New Hampshire Do YOU Yahoo!? To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Anyone else seeing jumpy mice?
On 22-May-00 Kazutaka YOKOTA wrote: > > Please, if you can avoid it, don't unplug and replug the mouse while > the power is on. The PS/2 mouse interface is generally not capable > of hot plugging/unplugging. > > As for sleep/wake-up problem on the laptop computers, you may > be able to resolve the problem by adding the following kernel options. > > options PSM_HOOKRESUME > options PSM_RESETAFTERSUSPEND Is it possible to do a reset after seeing the "psmintr: out of sync (00c0 != )"? Jonathan Hanna <[EMAIL PROTECTED]> To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Anyone else seeing jumpy mice?
Kazutaka YOKOTA wrote: > > >> FWIW, those are all the symptoms of this problem too. The mouse > >> doesn't just jump, it goes nuts with simulated button events. :) > > > >This can really suck with certain email clients, too. > > > >My hardware: Sony VAIO PCG-F160 w/integrated trackpad: > > > > psm0: irq 12 on atkbdc0 > > psm0: model GlidePoint, device ID 0 > > Don't the following kernel options work for this machine? > > options PSM_HOOKRESUME > options PSM_RESETAFTERSUSPEND They compile and boot fine. I'll let you know in a day or two if this stops the crazy mouse syndrome. For what it's worth, I've seen this both before and after a suspend/resume. -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC [EMAIL PROTECTED] http://softweyr.com/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Anyone else seeing jumpy mice?
>> FWIW, those are all the symptoms of this problem too. The mouse >> doesn't just jump, it goes nuts with simulated button events. :) > >This can really suck with certain email clients, too. > >My hardware: Sony VAIO PCG-F160 w/integrated trackpad: > > psm0: irq 12 on atkbdc0 > psm0: model GlidePoint, device ID 0 Don't the following kernel options work for this machine? options PSM_HOOKRESUME options PSM_RESETAFTERSUSPEND Kazu To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Anyone else seeing jumpy mice?
>> > Um, if you don't see the above message but see erratic mouse >> > behavior, then there may be a configuration problem (for moused or >> > X), or a hardware problem. > >Well, the mouse is fairly new (less than 6 months) and otherwise works like >a charm. I never saw this before 4.0, but that was also about the time >I added the KVM. Oh, I see. You also use a KVM. The psm driver in FreeBSD versions before 4.0 is also screwed when a less-than-compatible KVM is used. Kazu To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Anyone else seeing jumpy mice?
"Jordan K. Hubbard" wrote: > > > I haven't seen this message, but I _have_ been seeing an off-and-on problem > > where my PS/2 (Logitech Firstmouse) mouse will go insane. Just moving it > > causes clicks, wild pointer motion, all sorts of stuff. I usually have to > > FWIW, those are all the symptoms of this problem too. The mouse > doesn't just jump, it goes nuts with simulated button events. :) This can really suck with certain email clients, too. My hardware: Sony VAIO PCG-F160 w/integrated trackpad: psm0: irq 12 on atkbdc0 psm0: model GlidePoint, device ID 0 -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC [EMAIL PROTECTED] http://softweyr.com/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: One more question (different now)
Warner Losh wrote: > > In message <[EMAIL PROTECTED]> "David O'Brien" writes: > : On Thu, May 11, 2000 at 12:48:40PM -0600, Warner Losh wrote: > : > In the US, how do I get the same thing for C++? > : > : http://web.ansi.org/public/std_info.html > : > : Search for "C++": > : > : ISO/IEC 14882:1998 Programming languages - C++ $ 305 > : ISO/IEC 14882-1998 Information Technology - Programming Languages - C++ $18 > > That's cool. I can get the electronic version for only $18. What > format is it in? PDF, according to http://webstore.ansi.org/default.asp which is the page you end up at once you create a profile and login. -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC [EMAIL PROTECTED] http://softweyr.com/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Anyone else seeing jumpy mice?
Mike Smith wrote: > > >I haven't seen this message, but I _have_ been seeing an off-and-on problem > > >where my PS/2 (Logitech Firstmouse) mouse will go insane. Just moving it > > >causes clicks, wild pointer motion, all sorts of stuff. I usually have to > > >log in from another box and kill and restart moused; that fixes things. > > > > Um, if you don't see the above message but see erratic mouse > > behavior, then there may be a configuration problem (for moused or > > X), or a hardware problem. Well, the mouse is fairly new (less than 6 months) and otherwise works like a charm. I never saw this before 4.0, but that was also about the time I added the KVM. > You can also get this if you have moused running but have configured X to > point to the physical mouse device rather than /dev/sysmouse. Nope. -- Frank Mayhar [EMAIL PROTECTED] http://www.exit.com/ Exit Consulting http://store.exit.com/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Anyone else seeing jumpy mice?
In message <[EMAIL PROTECTED]> Kazutaka YOKOTA writes: : But, there now are so many dumb KVMs which screw us, and we may have : to accept that... Yes. I've been cursed to use some of the dumb KVMs at work. It got so bad that I've connected my mouse directly to the main machine and not run X on the other machines. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Anyone else seeing jumpy mice?
> >I haven't seen this message, but I _have_ been seeing an off-and-on problem > >where my PS/2 (Logitech Firstmouse) mouse will go insane. Just moving it > >causes clicks, wild pointer motion, all sorts of stuff. I usually have to > >log in from another box and kill and restart moused; that fixes things. > > Um, if you don't see the above message but see erratic mouse > behavior, then there may be a configuration problem (for moused or > X), or a hardware problem. You can also get this if you have moused running but have configured X to point to the physical mouse device rather than /dev/sysmouse. -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ [EMAIL PROTECTED] \\ and he'll hate you for a lifetime. \\ [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Anyone else seeing jumpy mice?
>> I've seen it for the last few weeks and can only think that something >> must be stomping on the psm driver now (or the driver is missing >> interrupts for reasons of its own). Anyone else seeing this? > >Yes, recently on 4.0-stable, though provoked by unplugging and >replugging in the mouse. It did not recover. This I thought >sounded like a PR on the mouse being dead after a wakeup >from sleep mode. Please, if you can avoid it, don't unplug and replug the mouse while the power is on. The PS/2 mouse interface is generally not capable of hot plugging/unplugging. As for sleep/wake-up problem on the laptop computers, you may be able to resolve the problem by adding the following kernel options. options PSM_HOOKRESUME options PSM_RESETAFTERSUSPEND Kazu To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Anyone else seeing jumpy mice?
>> May 19 00:50:45 zippy /kernel: psmintr: out of sync (00c0 != ). >> >> I've seen it for the last few weeks and can only think that something >> must be stomping on the psm driver now (or the driver is missing >> interrupts for reasons of its own). Anyone else seeing this? > >I haven't seen this message, but I _have_ been seeing an off-and-on problem >where my PS/2 (Logitech Firstmouse) mouse will go insane. Just moving it >causes clicks, wild pointer motion, all sorts of stuff. I usually have to >log in from another box and kill and restart moused; that fixes things. Um, if you don't see the above message but see erratic mouse behavior, then there may be a configuration problem (for moused or X), or a hardware problem. Kazu To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Anyone else seeing jumpy mice?
>: May 19 00:50:45 zippy /kernel: psmintr: out of sync (00c0 != ). >: >: I've seen it for the last few weeks and can only think that something >: must be stomping on the psm driver now (or the driver is missing >: interrupts for reasons of its own). Anyone else seeing this? > >I see this from time to time on whacked out mice that come into my >posession. Sadly, I see it most on my laptop. It seems to happen >less offten when I have > PSM_HOOKRESUME > PSM_RESETAFTERSUSPEND >defined in my kernel config file. > >I've also seen this when I've tried to hot plug mice. This includes >when power is lost to my KVM switch. When that happens, I gotta >reboot all the machines that are attached to it since something is >whacko at that point, I get those messages, or worse no mice and no >message at all. When power to the mouse is, either accidentally or intentionally, cut, the internal setting of the mouse is naturally lost, and the mouse may behave in a different way than the way the psm driver assumes... >Hmmm, time for a good ioctl interface to newbus :-) Or, an ioctl to reset the mouse... I have long rejected this idea because it will only encourage people to detach and attach the PS/2 mouse, which is generally not capable of hot plug/unplug. But, there now are so many dumb KVMs which screw us, and we may have to accept that... Kazu To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Anyone else seeing jumpy mice?
>May 19 00:50:45 zippy /kernel: psmintr: out of sync (00c0 != ). > >I've seen it for the last few weeks and can only think that something >must be stomping on the psm driver now (or the driver is missing >interrupts for reasons of its own). Anyone else seeing this? Do you, by any chance, use a KVM? Kazu To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Anyone else seeing jumpy mice?
Jonathan Hanna drunkenly mumbled... > > > I've seen it for the last few weeks and can only think that something > > must be stomping on the psm driver now (or the driver is missing > > interrupts for reasons of its own). Anyone else seeing this? > > Yes, recently on 4.0-stable, though provoked by unplugging and > replugging in the mouse. It did not recover. This I thought > sounded like a PR on the mouse being dead after a wakeup > from sleep mode. sometimes the people who clean our office move my computer to vacuum the floor and somehow they always manage to knock the mouse plug out. i try everything i can think of, but the only way to make the mouse start working again is to reboot. this is 4.0-stable, and it used to happen with 3.4-stable before i upgraded as well so i don't think this is version specific, it is something in the psm driver than hasn't changed in a while. -brian To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Anyone else seeing jumpy mice?
Jonathan Hanna wrote: > Yes, recently on 4.0-stable, though provoked by unplugging and > replugging in the mouse. It did not recover. This I thought > sounded like a PR on the mouse being dead after a wakeup > from sleep mode. Come to think of it, I do use a KVM switch, but this usually happens after I've been hacking away a while, having not touched the switch in hours or days. Still, it could be related, I guess. -- Frank Mayhar [EMAIL PROTECTED] http://www.exit.com/ Exit Consulting http://store.exit.com/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
RE: Anyone else seeing jumpy mice?
On 22-May-00 Jordan K. Hubbard wrote: > No, I don't mean rodents who've nibbled on chocolate-covered expresso > beans, I mean PS/2 mice which fall victim to this new problem: > > May 19 00:50:45 zippy /kernel: psmintr: out of sync (00c0 != ). > > I've seen it for the last few weeks and can only think that something > must be stomping on the psm driver now (or the driver is missing > interrupts for reasons of its own). Anyone else seeing this? > Yes, recently on 4.0-stable, though provoked by unplugging and replugging in the mouse. It did not recover. This I thought sounded like a PR on the mouse being dead after a wakeup from sleep mode. Jonathan Hanna <[EMAIL PROTECTED]> To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Anyone else seeing jumpy mice?
In message <3970.958963729@localhost> "Jordan K. Hubbard" writes: : No, I don't mean rodents who've nibbled on chocolate-covered expresso : beans, I mean PS/2 mice which fall victim to this new problem: : : May 19 00:50:45 zippy /kernel: psmintr: out of sync (00c0 != ). : : I've seen it for the last few weeks and can only think that something : must be stomping on the psm driver now (or the driver is missing : interrupts for reasons of its own). Anyone else seeing this? I see this from time to time on whacked out mice that come into my posession. Sadly, I see it most on my laptop. It seems to happen less offten when I have PSM_HOOKRESUME PSM_RESETAFTERSUSPEND defined in my kernel config file. I've also seen this when I've tried to hot plug mice. This includes when power is lost to my KVM switch. When that happens, I gotta reboot all the machines that are attached to it since something is whacko at that point, I get those messages, or worse no mice and no message at all. I know one isn't supposed to hot plug mice, but there are times when one is using a KVM switch when it sure would be nice to reset the driver. Hmmm, there's a psmdetach. Is there anyway to force a device to be detached? I know unloading the driver will do it, but one can't unload the driver compiled into the kernel, can one? And even if you could, I'd run the risk of loading a driver that doesn't match my kernel. Hmmm, time for a good ioctl interface to newbus :-) Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Anyone else seeing jumpy mice?
> I haven't seen this message, but I _have_ been seeing an off-and-on problem > where my PS/2 (Logitech Firstmouse) mouse will go insane. Just moving it > causes clicks, wild pointer motion, all sorts of stuff. I usually have to FWIW, those are all the symptoms of this problem too. The mouse doesn't just jump, it goes nuts with simulated button events. :) - Jordan To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Anyone else seeing jumpy mice?
Jordan K. Hubbard wrote: > No, I don't mean rodents who've nibbled on chocolate-covered expresso > beans, I mean PS/2 mice which fall victim to this new problem: > > May 19 00:50:45 zippy /kernel: psmintr: out of sync (00c0 != ). > > I've seen it for the last few weeks and can only think that something > must be stomping on the psm driver now (or the driver is missing > interrupts for reasons of its own). Anyone else seeing this? I haven't seen this message, but I _have_ been seeing an off-and-on problem where my PS/2 (Logitech Firstmouse) mouse will go insane. Just moving it causes clicks, wild pointer motion, all sorts of stuff. I usually have to log in from another box and kill and restart moused; that fixes things. -- Frank Mayhar [EMAIL PROTECTED] http://www.exit.com/ Exit Consulting http://store.exit.com/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Anyone else seeing jumpy mice?
No, I don't mean rodents who've nibbled on chocolate-covered expresso beans, I mean PS/2 mice which fall victim to this new problem: May 19 00:50:45 zippy /kernel: psmintr: out of sync (00c0 != ). I've seen it for the last few weeks and can only think that something must be stomping on the psm driver now (or the driver is missing interrupts for reasons of its own). Anyone else seeing this? - Jordan To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Major device numbers and mem device redesign
In message <[EMAIL PROTECTED]>, Mark Murray writes:
>> > I ask, as my RNG is a kld, and I want it to be as separate as possible
>> > without getting ridiculous.
>>
>> Yes. You could just cut/paste the existing mem.c driver, and remove
>> everything but the random hooks. In your init code register minors 3 and
>> 4, and that's all you have to worry about.
>
>Cool! So it means I can also remove the
>
>switch (minor(dev)) {
>
> 3:
> /* Stuff */
> break;
> default:
> return FOO;
>}
>
>and reduce that to
>
>/* Stuff */
>
>On the grounds that my routine will never see the other crap?
>If so, way cool!
yes, enjoy :-)
--
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: Major device numbers and mem device redesign
In message <[EMAIL PROTECTED]>, Mark Murray writes:
>> > > I want to commit a new /dev/random RSN, so I'll be needing a major
>> > > device; what is the procedure for getting one? I know how to steal one,
>> > > but ISTR that this is not how it is done.
>> >
>> > Just edit sys/conf/majors and claim the next available number.
>>
>> You don't need one. You can use the same major/minor numbers. You can
>> register multiple cdevsw's per major number with make_dev(); (do NOT
>> use cdevsw_add() for this).
>
>How does this work for all the routines? When you register the
>"new" minor number, can you be specifying new read/write/poll/ioctl/etc
>routines?
>
>I ask, as my RNG is a kld, and I want it to be as separate as possible
>without getting ridiculous.
make_dev() takes a pointer to your struct cdevsw{} for this particular
minor.
--
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
pcm static
I was just wondering what the status on the static in the pcm driver on the SoundBlaster ViBRA16X is... Just in case anyone forgot what I'm talking about, almost half the time when I start playing an mp3 or an mpg movie I get static out of the soundcard instead of music. If I keep restarting the song or movie, eventually I get music instead of static, but then every time I switch songs I get static about half the time again when the new song starts. Also, short wav files aren't playing all the way through again. = | Kenneth Culver | FreeBSD: The best OS around.| | Unix Systems Administrator | ICQ #: 24767726 | | and student at The | AIM: muythaibxr | | The University of Maryland, | Website: (Under Construction) | | College Park. | http://www.wam.umd.edu/~culverk/| = To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Major device numbers and mem device redesign
> Yes. Each instance of make_dev() takes a cdevsw argument for the minor numbe
r
> in question. So, you could have /dev/mem read/write/ioctl etc routines
> for major 2, minor 0 and 1, while have minors 3 and 4 being installed with
> their own open/close/read/write/etc routines.
>
> Devices are looked up as a hash of major+minor, and the devsw entries from
> that point on.
OK - how do the
switch (minor(dev)) {
/* stuff */'
default:
return ENXIO;
}
cases get handled? By the hashing routine?
Can these be hunted down and killed?
M
--
Mark Murray
Join the anti-SPAM movement: http://www.cauce.org
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: Major device numbers and mem device redesign
> > I ask, as my RNG is a kld, and I want it to be as separate as possible > > without getting ridiculous. > > Have a look at http://jeroen.vangelderen.org/FreeBSD/misc_device . Thanks! You have some good ideas in there; I may just borg some of them. :-) M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Major device numbers and mem device redesign
Mark Murray wrote: > > > > > I want to commit a new /dev/random RSN, so I'll be needing a major > > > > device; what is the procedure for getting one? I know how to steal one, > > > > but ISTR that this is not how it is done. > > > > > > Just edit sys/conf/majors and claim the next available number. > > > > You don't need one. You can use the same major/minor numbers. You can > > register multiple cdevsw's per major number with make_dev(); (do NOT > > use cdevsw_add() for this). > > How does this work for all the routines? When you register the > "new" minor number, can you be specifying new read/write/poll/ioctl/etc > routines? > > I ask, as my RNG is a kld, and I want it to be as separate as possible > without getting ridiculous. Have a look at http://jeroen.vangelderen.org/FreeBSD/misc_device . Cheers, Jeroen To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Major device numbers and mem device redesign
> On Sun, May 21, 2000 at 09:53:18AM +0200, Mark Murray wrote:
> > I want to commit a new /dev/random RSN,
>
> Forgot to mention, please keep in mind this needs to be MI.
> sys/kern_random.c (which was sys/i386/isa/random_machdep.c) still is
> *very* ugly from a MI point of view. Any changes to kern_random.c would
> be greatly appreciated -- expecially removing the hardcoding of "16", as
> the reasons it was done don't apply to the Alpha, and I'm sure the IA-64
> and sparc.
That's why I'm doing it :-) I'm trying very hard to forget that I'm
on ${ARCH}, and just coding in C for what I can see. ;-)
M
--
Mark Murray
Join the anti-SPAM movement: http://www.cauce.org
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: Major device numbers and mem device redesign
On Sun, May 21, 2000 at 09:53:18AM +0200, Mark Murray wrote: > I want to commit a new /dev/random RSN, Forgot to mention, please keep in mind this needs to be MI. sys/kern_random.c (which was sys/i386/isa/random_machdep.c) still is *very* ugly from a MI point of view. Any changes to kern_random.c would be greatly appreciated -- expecially removing the hardcoding of "16", as the reasons it was done don't apply to the Alpha, and I'm sure the IA-64 and sparc. -- -- David ([EMAIL PROTECTED]) Disclaimer: Not speaking for FreeBSD, just expressing my own opinion. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Major device numbers and mem device redesign
On Sun, May 21, 2000 at 09:53:18AM +0200, Mark Murray wrote: > I want to commit a new /dev/random RSN, so I'll be needing a major > device; Why can't you just rip out the existing random stuff and put in your new stuff -- keeping the major and minor numbers the same? -- -- David ([EMAIL PROTECTED]) Disclaimer: Not speaking for FreeBSD, just expressing my own opinion. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Major device numbers and mem device redesign
> > I ask, as my RNG is a kld, and I want it to be as separate as possible
> > without getting ridiculous.
>
> Yes. You could just cut/paste the existing mem.c driver, and remove
> everything but the random hooks. In your init code register minors 3 and
> 4, and that's all you have to worry about.
Cool! So it means I can also remove the
switch (minor(dev)) {
3:
/* Stuff */
break;
default:
return FOO;
}
and reduce that to
/* Stuff */
On the grounds that my routine will never see the other crap?
If so, way cool!
M
--
Mark Murray
Join the anti-SPAM movement: http://www.cauce.org
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: Major device numbers and mem device redesign
Mark Murray wrote: > > > > I want to commit a new /dev/random RSN, so I'll be needing a major > > > > device; what is the procedure for getting one? I know how to steal one, > > > > but ISTR that this is not how it is done. > > > > > > Just edit sys/conf/majors and claim the next available number. > > > > You don't need one. You can use the same major/minor numbers. You can > > register multiple cdevsw's per major number with make_dev(); (do NOT > > use cdevsw_add() for this). > > How does this work for all the routines? When you register the > "new" minor number, can you be specifying new read/write/poll/ioctl/etc > routines? Yes. Each instance of make_dev() takes a cdevsw argument for the minor number in question. So, you could have /dev/mem read/write/ioctl etc routines for major 2, minor 0 and 1, while have minors 3 and 4 being installed with their own open/close/read/write/etc routines. Devices are looked up as a hash of major+minor, and the devsw entries from that point on. Presently: make_dev(&mem_cdevsw, 0, UID_ROOT, GID_KMEM, 0640, "mem"); make_dev(&mem_cdevsw, 1, UID_ROOT, GID_KMEM, 0640, "kmem"); make_dev(&mem_cdevsw, 2, UID_ROOT, GID_WHEEL, 0666, "null"); make_dev(&mem_cdevsw, 3, UID_ROOT, GID_WHEEL, 0644, "random"); make_dev(&mem_cdevsw, 4, UID_ROOT, GID_WHEEL, 0644, "urandom"); make_dev(&mem_cdevsw, 12, UID_ROOT, GID_WHEEL, 0666, "zero"); make_dev(&mem_cdevsw, 14, UID_ROOT, GID_WHEEL, 0600, "io"); There is no reason at all to stop each of those minor devices having their own cdevsw and handler functions. > I ask, as my RNG is a kld, and I want it to be as separate as possible > without getting ridiculous. Yes. You could just cut/paste the existing mem.c driver, and remove everything but the random hooks. In your init code register minors 3 and 4, and that's all you have to worry about. Cheers, -Peter To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Major device numbers and mem device redesign
> > > I want to commit a new /dev/random RSN, so I'll be needing a major > > > device; what is the procedure for getting one? I know how to steal one, > > > but ISTR that this is not how it is done. > > > > Just edit sys/conf/majors and claim the next available number. > > You don't need one. You can use the same major/minor numbers. You can > register multiple cdevsw's per major number with make_dev(); (do NOT > use cdevsw_add() for this). How does this work for all the routines? When you register the "new" minor number, can you be specifying new read/write/poll/ioctl/etc routines? I ask, as my RNG is a kld, and I want it to be as separate as possible without getting ridiculous. M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Major device numbers and mem device redesign
Doug Rabson wrote: > On Sun, 21 May 2000, Mark Murray wrote: > > > Hi > > > > I want to commit a new /dev/random RSN, so I'll be needing a major > > device; what is the procedure for getting one? I know how to steal one, > > but ISTR that this is not how it is done. > > Just edit sys/conf/majors and claim the next available number. You don't need one. You can use the same major/minor numbers. You can register multiple cdevsw's per major number with make_dev(); (do NOT use cdevsw_add() for this). > > > > Also - Peter said something about the "mem" device needing > > to only contain the /dev/mem and /mem/kmem devices, and > > /dev/(random|urandom|null|zero) needing to move to MI areas. I have done > > this, as KLD's. Who wants to review? > > I'll take a look. > > -- > Doug Rabson Mail: [EMAIL PROTECTED] > Nonlinear Systems Ltd.Phone: +44 20 8442 9037 > > > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-current" in the body of the message > > Cheers, -Peter -- Peter Wemm - [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED] "All of this is for nothing if we don't go to the stars" - JMS/B5 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Major device numbers and mem device redesign
On Sun, 21 May 2000, Mark Murray wrote: > Hi > > I want to commit a new /dev/random RSN, so I'll be needing a major > device; what is the procedure for getting one? I know how to steal one, > but ISTR that this is not how it is done. Just edit sys/conf/majors and claim the next available number. > > Also - Peter said something about the "mem" device needing > to only contain the /dev/mem and /mem/kmem devices, and > /dev/(random|urandom|null|zero) needing to move to MI areas. I have done > this, as KLD's. Who wants to review? I'll take a look. -- Doug Rabson Mail: [EMAIL PROTECTED] Nonlinear Systems Ltd. Phone: +44 20 8442 9037 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: PAM & OpenSSH 2.1 & X11 -> signal 11
On 21 May, Hajimu UMEMOTO wrote:
[kris CCed, I think hi knows how to handle this]
> Alexander> after a new build{world,kernel} after the import of OpenSSH 2.1 to
> Alexander> internat (cvsupped 2517, around 14:00 CEST), xdm gets a signal
> Alexander> 11 if I use pam_ssh.so (after entering the password).
> Alexander> After removing the lines with pam_ssh.so for xdm I'm able to login.
>
> Alexander> Is someone else able to reproduce this?
>
> I also met this with wdm here.
> To avoid this problem, I replaced pam_ssh.c with
> ports/security/opessh/pam_ssh.c with changing PATH_SSH_AGENT to
> /usr/bin/ssh-agent. It seems working.
I haven't tried it (yet), but a diff between both (src/crypto/... and
ports/...) show many differences:
---snip---
(5) netchild@ttyp2% diff -duH /usr/src/crypto/openssh/pam_ssh/pam_ssh.c
/usr/ports/security/openssh/files/pam_ssh.c |wc
174 6715212
---snip---
Some of them are ok (__PREFIX__), but the other differences are changes
to support DSA-keys (if I read this correctly).
Kris, may I assume they get merged into the tree soon?
> --
^ It seems you have forgotten to add a space after the dashes.
> Hajimu UMEMOTO @ Internet Mutual Aid Society Yokohama, Japan
> [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED]
> http://www.imasy.org/~ume/
Bye,
Alexander.
--
I believe the technical term is "Oops!"
http://www.Leidinger.net Alexander+Home @ Leidinger.net
GPG fingerprint = 7423 F3E6 3A7E B334 A9CC B10A 1F5F 130A A638 6E7E
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Major device numbers and mem device redesign
Hi I want to commit a new /dev/random RSN, so I'll be needing a major device; what is the procedure for getting one? I know how to steal one, but ISTR that this is not how it is done. Also - Peter said something about the "mem" device needing to only contain the /dev/mem and /mem/kmem devices, and /dev/(random|urandom|null|zero) needing to move to MI areas. I have done this, as KLD's. Who wants to review? M To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
