Re: devd nomatch does not load uslcom anymore

On Tue, May 21, 2024, 1:38 AM Ronald Klop wrote: > Hi, > > May 16th upgraded the kernel of my RPI4. Previous kernel was fom April > 10th. > > From: > FreeBSD 15.0-CURRENT #35 main-5716d902ae1: Wed Apr 10 22:59:37 CEST 2024 > > To: > FreeBSD 15.0-CURRENT #36 main-42b28f81521: Thu May 16 07:54:05 C

Re: Devd / devmatch(8) -- netif race 12-RC1

Warner Losh writes: > coretemp is a CPU device, and so I'm not sure we have the right PNP > information for the CPU bus for it to even load. The coretemp device is not really a device, it's just a couple of MSRs. As such, it is not attached to an enumerable bus, or any bus at all that devd's awar

Re: Devd / devmatch(8) -- netif race 12-RC1

On Wed, Nov 21, 2018, 11:43 PM Dan Partelly wireless lagg initialization is broken in this scenario, all-right. The > init/rc system as it is now can’t cope easily with a modern asynchronous > initialization sequence. Sure you could probably find an order which works, > only to find yourself in tr

Re: Devd / devmatch(8) -- netif race 12-RC1

We're missing a fair bit of information to come to any conclusion yet. Cy, did you used it when loading the wifi drivers automatically with devmatcher ? Cause if you run GENERIC, chances are that you will not see any weird behavior. Most wifi drivers are compiled in kernel in this case.

Re: Devd / devmatch(8) -- netif race 12-RC1

In message <798c848d-5f32-4bf9-87e0-add4f9b74...@rdsor.ro>, Dan Partelly writes : > wireless lagg initialization is broken in this scenario, all-right. The init/ > rc system as it is now can’t cope easily with a modern asynchronous initial > ization sequence. Sure you could probably find an orde

Re: Devd / devmatch(8) -- netif race 12-RC1

wireless lagg initialization is broken in this scenario, all-right. The init/rc system as it is now can’t cope easily with a modern asynchronous initialization sequence. Sure you could probably find an order which works, only to find yourself in trouble next time you want add some modern functi

Re: Devd / devmatch(8) -- netif race 12-RC1

On 20 Nov 2018, at 8:17, dan_parte...@rdsor.ro wrote: No, that's not what's happening. wlan0 isn't racing anything, because it's no longer listed in ifconfig But when is created lagg0 ? Acording rc output on screen , creation of cloned interface lagg0 takes place before wlan0 is created. The

Re: Devd / devmatch(8) -- netif race 12-RC1

No, that's not what's happening. wlan0 isn't racing anything, because it's no longer listed in ifconfig But when is created lagg0 ? Acording rc output on screen , creation of cloned interface lagg0 takes place before wlan0 is created. Then this means SIOCLAGPORT will fail with Invalid argume

Re: Devd / devmatch(8) -- netif race 12-RC1

On Mon, Nov 19, 2018 at 7:48 PM Dan Partelly wrote: > Hello, > > Today I tried a simple wireless failover on a machine running free-bsd. > After reboot the system cannot complete the initialization sequence OK with > devmatcher. > The devd/devmatch(8) combo correctly identified the wireless card

Re: devd on head -r338675 on aarch64 (Pine64+ 2GB example) gets during booting: "sh: /usr/libexec/hyperv/hyperv_vfattach: not found"

On 9/14/18 11:24 AM, Mark Millard via freebsd-arm wrote: > From the boot of the Pine64+ 2GB for -r338675: > > . . . > Starting devd. > sh: /usr/libexec/hyperv/hyperv_vfattach: not found > add host 127.0.0.1: gateway lo0 fib 0: route already in table > . . . I got the same error booting FreeBSD/ri

Re: devd in r329188M don't start

On Sat, Feb 17, 2018 at 8:06 AM, Hans Petter Selasky wrote: > On 02/17/18 15:58, Warner Losh wrote: > >> USB WAS ABSOLUTELY TESTED. I rebooted my machine several times, unloaded >> drivers, etc. It all just worked for me. >> >> Please don't make snide comments like this, along with drive by commi

Re: devd in r329188M don't start

On 02/17/18 15:58, Warner Losh wrote: USB WAS ABSOLUTELY TESTED. I rebooted my machine several times, unloaded drivers, etc. It all just worked for me. Please don't make snide comments like this, along with drive by commits to devmatch without even discussing the problems with me. It's really pi

Re: devd in r329188M don't start

On Sat, Feb 17, 2018 at 6:31 AM, Hans Petter Selasky wrote: > On 02/17/18 11:38, Alex V. Petrov wrote: > >> 12.0-CURRENT #12 r329446M: Sat Feb 17 17:11:05 +07 2018: >> on boot multilines: >> >> devmatch: Malformed NOMATCH string: ''?'' >> >> > Can you try these two patches: > > https://svnweb.fre

Re: devd in r329188M don't start

On 02/17/18 15:22, Alex V. Petrov wrote: Sorry, prev msg this only afrer one patch. Now is all OK. There is one more, but not so important: https://svnweb.freebsd.org/changeset/base/329458 Thank for your testing! --HPS ___ freebsd-current@freebsd.

Re: devd in r329188M don't start

Sorry, prev msg this only afrer one patch. Now is all OK. 17.02.2018 21:18, Hans Petter Selasky пишет: > On 02/17/18 14:51, Alex V. Petrov wrote: >> devmatch: Malformed NOMATCH string: ''?'' persists >> >> > > Did you reinstall /etc ? > > --HPS > > -- - Alex.

Re: devd in r329188M don't start

On 02/17/18 14:51, Alex V. Petrov wrote: devmatch: Malformed NOMATCH string: ''?'' persists Did you reinstall /etc ? --HPS ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send

Re: devd in r329188M don't start

devmatch: Malformed NOMATCH string: ''?'' persists 17.02.2018 20:31, Hans Petter Selasky пишет: > On 02/17/18 11:38, Alex V. Petrov wrote: >> 12.0-CURRENT #12 r329446M: Sat Feb 17 17:11:05 +07 2018: >> on boot multilines: >> >> devmatch: Malformed NOMATCH string: ''?'' >> > > Can you try these t

Re: devd in r329188M don't start

On 02/17/18 11:38, Alex V. Petrov wrote: 12.0-CURRENT #12 r329446M: Sat Feb 17 17:11:05 +07 2018: on boot multilines: devmatch: Malformed NOMATCH string: ''?'' Can you try these two patches: https://svnweb.freebsd.org/changeset/base/329455 https://svnweb.freebsd.org/changeset/base/329456 Ob

Re: devd in r329188M don't start

12.0-CURRENT #12 r329446M: Sat Feb 17 17:11:05 +07 2018: on boot multilines: devmatch: Malformed NOMATCH string: ''?'' mouse don't start 13.02.2018 19:50, Hans Petter Selasky пишет: > On 02/13/18 10:47, Jakob Alvermark wrote: >> +1 >> >> My USB mouse was working fine before the switch to devmat

Re: devd in r329188M don't start

Am 16.02.2018 um 07:17 schrieb Warner Losh: On Thu, Feb 15, 2018 at 11:12 PM, Rainer Hurling > wrote: Am 13.02.2018 um 13:50 schrieb Hans Petter Selasky: On 02/13/18 10:47, Jakob Alvermark wrote: +1 My USB mouse was working fine b

Re: devd in r329188M don't start

On Thu, Feb 15, 2018 at 11:12 PM, Rainer Hurling wrote: > Am 13.02.2018 um 13:50 schrieb Hans Petter Selasky: > >> On 02/13/18 10:47, Jakob Alvermark wrote: >> >>> +1 >>> >>> My USB mouse was working fine before the switch to devmatch. Now I have >>> to 'kldload ums' manually. >>> >>> Same for US

Re: devd in r329188M don't start

Am 13.02.2018 um 13:50 schrieb Hans Petter Selasky: On 02/13/18 10:47, Jakob Alvermark wrote: +1 My USB mouse was working fine before the switch to devmatch. Now I have to 'kldload ums' manually. Same for USB audio, snd_uaudio.ko was loaded by devd before. Hi, This is a known issue. Can

Re: devd in r329188M don't start

On 13/02/2018 23:50, Hans Petter Selasky wrote: > On 02/13/18 10:47, Jakob Alvermark wrote: >> +1 >> >> My USB mouse was working fine before the switch to devmatch. Now I >> have to 'kldload ums' manually. >> >> Same for USB audio, snd_uaudio.ko was loaded by devd before. >> > > Hi, > > This is a

Re: devd in r329188M don't start

Yes, it seems to be working. Thanks! Jakob On 02/13/18 13:50, Hans Petter Selasky wrote: On 02/13/18 10:47, Jakob Alvermark wrote: +1 My USB mouse was working fine before the switch to devmatch. Now I have to 'kldload ums' manually. Same for USB audio, snd_uaudio.ko was loaded by devd be

Re: devd in r329188M don't start

Yes, for me it works. Thank you. 13.02.2018 19:50, Hans Petter Selasky пишет: > On 02/13/18 10:47, Jakob Alvermark wrote: >> +1 >> >> My USB mouse was working fine before the switch to devmatch. Now I >> have to 'kldload ums' manually. >> >> Same for USB audio, snd_uaudio.ko was loaded by devd bef

Re: devd in r329188M don't start

On 02/13/18 10:47, Jakob Alvermark wrote: +1 My USB mouse was working fine before the switch to devmatch. Now I have to 'kldload ums' manually. Same for USB audio, snd_uaudio.ko was loaded by devd before. Hi, This is a known issue. Can you try the attached patch? Rebuild devmatch(8) and

Re: devd in r329188M don't start

+1 My USB mouse was working fine before the switch to devmatch. Now I have to 'kldload ums' manually. Same for USB audio, snd_uaudio.ko was loaded by devd before. Jakob On 02/13/18 10:34, Alex V. Petrov wrote: Why is not the driver loaded when the mouse is connected? 13.02.2018 16:19, Ha

Re: devd in r329188M don't start

Why is not the driver loaded when the mouse is connected? 13.02.2018 16:19, Hans Petter Selasky пишет: > On 02/13/18 10:20, Alex V. Petrov wrote: >> usb.conf is not found anywhere in the system. This is normal? > > devmatch is supposed to replace usb.conf . The contents of usb.conf is > now part

Re: devd in r329188M don't start

On 02/13/18 10:20, Alex V. Petrov wrote: usb.conf is not found anywhere in the system. This is normal? devmatch is supposed to replace usb.conf . The contents of usb.conf is now part of the linker hints, /boot/kernel/linker.hints . --HPS ___ freebs

Re: devd in r329188M don't start

Mouse start work only after handly: kldload ums usb.conf is not found anywhere in the system. This is normal? 13.02.2018 15:08, Hans Petter Selasky пишет: > On 02/13/18 09:02, Alex V. Petrov wrote: >> after update, devd don't starting with: >> devd: Cannot parse /etc/devd/devmatch.conf at line 1

Re: devd in r329188M don't start

In /var/log/messages: devd: line 13: }: syntax error File /etc/devd/devmatch.conf (11-13 lines): nomatch 100 { action "service devmatch start" }; 13.02.2018 15:08, Hans Petter Selasky пишет: > On 02/13/18 09:02, Alex V. Petrov wrote: >> after update, devd don't starting with: >> devd: Can

Re: devd in r329188M don't start

On 02/13/18 09:02, Alex V. Petrov wrote: after update, devd don't starting with: devd: Cannot parse /etc/devd/devmatch.conf at line 13 (file default!) If I disable it, don't work mouse in xorg. https://svnweb.freebsd.org/changeset/base/329194 --HPS __

Re: devd in r329188M don't start

On 02/13/18 09:02, Alex V. Petrov wrote: after update, devd don't starting with: devd: Cannot parse /etc/devd/devmatch.conf at line 13 (file default!) If I disable it, don't work mouse in xorg. I think there is a missing ";" at the end of line 13. Try adding one. --HPS _

Re: devd limitations -- was [CFT] packaging the base system with pkg(8)

> Ideally, when the automounter daemon starts, it should > connect to devd via an IPC channel and request notification of the specific > events that it wants I was under the impression that devd.seqpacket.pipe accomplishes this. Am I right in assuming that the issue is that devd forwards ALL even

Re: devd problem after recent upgrade

On Wed, 26 Mar 2014, Mateusz Guzik wrote: On Wed, Mar 26, 2014 at 02:53:25AM +0100, Mateusz Guzik wrote: On Tue, Mar 25, 2014 at 09:31:57PM -0400, AN wrote: I just upgraded to svn r263756 and have a major problem, the system has no mouse. When I reboot I see the following message on the con

Re: devd problem after recent upgrade

On Wed, Mar 26, 2014 at 02:53:25AM +0100, Mateusz Guzik wrote: > On Tue, Mar 25, 2014 at 09:31:57PM -0400, AN wrote: > > I just upgraded to svn r263756 and have a major problem, the system > > has no mouse. When I reboot I see the following message on the > > console: > > devd:devctl sysctl missin

Re: devd problem after recent upgrade

On Tue, Mar 25, 2014 at 09:31:57PM -0400, AN wrote: > I just upgraded to svn r263756 and have a major problem, the system > has no mouse. When I reboot I see the following message on the > console: > devd:devctl sysctl missing from kernel > > then > > /etc/rc.d failed to start devd, and also I h

Re: devd or dhclient or ifconfig behavior seems broken

On Thu, Jul 04, 2013 at 08:50:21AM -0500, Mark Felder wrote: > Check the man page for dhclient.conf. You can use the supercede > functionality to always force the settings you prefer. Thanks for the suggestion. I was trying to use resolvconf.conf to put specific nameservers into resolv.conf, but

Re: devd or dhclient or ifconfig behavior seems broken

Check the man page for dhclient.conf. You can use the supercede functionality to always force the settings you prefer. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to

Re: devd based AUTOMOUNTER

Hi, I have created a PORT at last, its in the 'port' directory in the usual place: https://github.com/vermaden/automount/ Its my first PORT so feel free to bash me about my mistakes ;) After latest 'commits' I think that its ready for day-to-day use. To make 'full advantage' of *automount* in

Re: devd based AUTOMOUNTER

Hi, I removed the state_lock and stat_unlock mechanisms as they appeared to be not needed, I have shufled with 3 drives all the time and the 'integrity' has not been lost, at it was a lot faster, because the lock always had to wait for the 'slowest' drive (in term of initializing the device, like

Re: devd based AUTOMOUNTER

written by ${ME} ... > First BUG: (not fixed yet, but workaround already is working) > > TEST/BUG/CASE: > Plug in FAT32 and NTFS drives at the same time, when FAT32 device > will be detected first, it will get mounted and the NTFS drive will be > mounted TWICE, so I added > __check_already_mounte

Re: devd based AUTOMOUNTER

written by Andriy Gapon ... > Hey, this seems like a quite nice tool. > Can you create a web-page and/or port for it? > It would be more convenient to follow its development that way. > Thank you! Sure, its now available here, I will try to create port later: https://github.com/vermaden/automoun

Re: devd based AUTOMOUNTER

Hi, new version with new features (and BUGs ;p) Added check if ntfsfix from sysutils/ntfsprogs is available, if Yes then try to fix the NTFS filesystem before mouting it. Added GPL3 License ... just joking ;) ... added FreeBSD License to the file. Added 'noatime' as a default mount option when

Re: devd based AUTOMOUNTER

В Mon, 20 Feb 2012 09:43:59 +0100 vermaden пишет: > Hi, > > new version with new features (and BUGs ;p) > > Added check if ntfsfix from sysutils/ntfsprogs is available, if Yes > then try to fix the NTFS filesystem before mouting it. > > Added GPL3 License ... just joking ;) ... added FreeBSD L

Re: devd based AUTOMOUNTER

[cc list trimmed] Hey, this seems like a quite nice tool. Can you create a web-page and/or port for it? It would be more convenient to follow its development that way. Thank you! on 20/02/2012 10:43 vermaden said the following: > Hi, > > new version with new features (and BUGs ;p) > > Added c

Re: devd based AUTOMOUNTER

Hi, sorry for late response, but I currently have quite a lot 'weekend activities' that are definitely not near a computer ;) written by Gleb Kurtsou ... >> __state_lock() { >> while [ -f ${STATE}.lock ]; do sleep 0.5; done >> :> ${STATE}.lock >> } > > Why not keep it stateless, unmounting

Re: devd based AUTOMOUNTER

On (18/02/2012 10:48), vermaden wrote: > Added a check if ntfs-3g is available, if not then mount_ntfs is used instead. > Added deleting of empty directories at ${MNTPREFIX}. > Added ${MNTPREFIX} to be set to /mnt or /media according to preference > > #! /bin/sh > > PATH=/bin:/sbin:/usr/bin:/usr/

Re: devd based AUTOMOUNTER

On Saturday 18 February 2012 10:48:11 vermaden wrote: > Added a check if ntfs-3g is available, if not then mount_ntfs is used > instead. Added deleting of empty directories at ${MNTPREFIX}. > Added ${MNTPREFIX} to be set to /mnt or /media according to preference > > #! /bin/sh > > PATH=/bin:/sbin

Re: devd based AUTOMOUNTER

Added a check if ntfs-3g is available, if not then mount_ntfs is used instead. Added deleting of empty directories at ${MNTPREFIX}. Added ${MNTPREFIX} to be set to /mnt or /media according to preference #! /bin/sh PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin MNTPREFIX="/media

Re: devd based AUTOMOUNTER

Latest version with additional checks for NTFS and FAT32, to be precise, for NTFS filesystem with label "FAT" and for FAT filesystem with label "NTFS" ;) #! /bin/sh PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin LOG="/var/log/automount.log" STATE="/var/run/automount.state" DATE

Re: devd based AUTOMOUNTER

... even newer version, seems to have all 'problems' fixed now ;) #! /bin/sh PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin LOG="/var/log/automount.log" STATE="/var/run/automount.state" DATEFMT="%Y-%m-%d %H:%M:%S" __create_mount_point() { # /* 1=DEV */ MNT="/mnt/$( basename

Re: devd based AUTOMOUNTER

I already made some changes for the 'better' ... Here is the latest version: #! /bin/sh PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin LOG="/var/log/automount.log" STATE="/var/run/automount.state" DATEFMT="%Y-%m-%d %H:%M:%S" __create_mount_point() { # /* 1=DEV */ MNT="/mnt/

Re: devd based AUTOMOUNTER

On 02/17/12 09:49, vermaden wrote: > Hi, > > I have finally made some effort on writing flexible yet very simple > automounter for FreeBSD desktop. > > Feel free to submit me BUG reports ;) > > It currently supports these file formats: > -- NTFS(rw) requires [port]sysutils/fusefs-ntfs[/port] > --

Re: devd and/or ACPI not reporting a heat problem

In message: <4c187778.9060...@freebsd.org> Doug Barton writes: : Howdy, : : I thought my heat problems were over with this laptop thanks to all : the great suggestions I've received about powerd, no stepping, etc. (I : also propped up both the back and the front to make a nice big air

Re: devd and/or ACPI not reporting a heat problem

On 6/16/2010 5:05 AM, John Baldwin wrote: > You can reduce the polling interval by changing > hw.acpi.thermal.polling_rate (it is in seconds it seems) to a lower value. Thanks, I'll give that a try, although with the cleaning I gave it yesterday I'm hoping to avoid heat problems for a while. :)

Re: devd and/or ACPI not reporting a heat problem

On Wednesday 16 June 2010 3:04:24 am Doug Barton wrote: > Howdy, > > I thought my heat problems were over with this laptop thanks to all the > great suggestions I've received about powerd, no stepping, etc. (I also > propped up both the back and the front to make a nice big air pocket.) > I've

Re: devd

In message: <[EMAIL PROTECTED]> Andrew Thompson <[EMAIL PROTECTED]> writes: : I am wondering what the state of devd is, should I be using it instead : of pccardd? At the moment I have neither running, but want to 'up' my : wi card on insert. Working. devd_enable=YES in /etc/rc.con

Re: devd/devctl

On Friday, September 12, 2003, at 06:26 pm, Suleiman Souhlal wrote: I was wondering if it would be a good idea to modify devd and devctl for them to handle other events than attaching and detaching devices.. For example, they could be used to mark a network interface as down, when the network

Re: devd/devctl

In message: <[EMAIL PROTECTED]> "Brandon S. Allbery KF8NH" <[EMAIL PROTECTED]> writes: : On Sat, 2003-09-13 at 18:49, M. Warner Losh wrote: : > and you cannot tell dhclient that interfaces have arrived. : : dhclient(8) seems to think otherwise, although it doesn't explain quite : how (

Re: devd/devctl

On Sat, Sep 13, 2003 at 06:59:21PM -0400, Brandon S. Allbery KF8NH wrote: > On Sat, 2003-09-13 at 18:49, M. Warner Losh wrote: > > and you cannot tell dhclient that interfaces have arrived. One way for it to tell that this has happened automatically is to get it to listen on a PF_ROUTE socket and

Re: devd/devctl

On Sat, 2003-09-13 at 18:49, M. Warner Losh wrote: > and you cannot tell dhclient that interfaces have arrived. dhclient(8) seems to think otherwise, although it doesn't explain quite how (I assume it wants you to pause and resume via OMAPI/omshell(8) since it doesn't appear to support "interface"

Re: devd/devctl

In message: <[EMAIL PROTECTED]> Doug Barton <[EMAIL PROTECTED]> writes: : On Sat, 13 Sep 2003, M. Warner Losh wrote: : : > In message: <[EMAIL PROTECTED]> : > Doug Barton <[EMAIL PROTECTED]> writes: : > : That functionality is being ported back to the vendor, if it hasn't b

Re: devd/devctl

On Sat, 13 Sep 2003, M. Warner Losh wrote: > In message: <[EMAIL PROTECTED]> > Doug Barton <[EMAIL PROTECTED]> writes: > : That functionality is being ported back to the vendor, if it hasn't been > : already. If we want really cool whizbang features that are more specific > : to us, we

Re: devd/devctl

In message: <[EMAIL PROTECTED]> Doug Barton <[EMAIL PROTECTED]> writes: : That functionality is being ported back to the vendor, if it hasn't been : already. If we want really cool whizbang features that are more specific : to us, we _should_ be looking at stuff like devd. The trick is

Re: devd/devctl

On Sat, 13 Sep 2003, M. Warner Losh wrote: > Yes. that has been the plan for some time now. However, dhclient is > really lame in a lot of ways. Martin Blapp has made it a lot better > of lates. In geral, I tend to believe that I shouldn't fix bugs in > dhclient with devd things. However, a m

Re: devd/devctl

In message: <[EMAIL PROTECTED]> Suleiman Souhlal <[EMAIL PROTECTED]> writes: : I was wondering if it would be a good idea to modify devd and : devctl for them to handle other events than attaching and detaching : devices.. For example, they could be used to mark a network : interface as

Re: devd *NOT* called on wi0 insert?

In message: <[EMAIL PROTECTED]> David Gilbert <[EMAIL PROTECTED]> writes: : > "M" == M Warner Losh <[EMAIL PROTECTED]> writes: : : M> In message: <[EMAIL PROTECTED]> Larry : M> Rosenman <[EMAIL PROTECTED]> writes: : I have a (within the week) : M> -CURRENT system. If I boot with m

Re: devd *NOT* called on wi0 insert?

> "M" == M Warner Losh <[EMAIL PROTECTED]> writes: M> In message: <[EMAIL PROTECTED]> Larry M> Rosenman <[EMAIL PROTECTED]> writes: : I have a (within the week) M> -CURRENT system. If I boot with my Linksys : WPC11 V.3 card M> inserted : I get the dhcp actions and all is fine. If I remove th

Re: devd *NOT* called on wi0 insert?

In message: <[EMAIL PROTECTED]> Larry Rosenman <[EMAIL PROTECTED]> writes: : However, I still am not impressed with the devd.conf(5) man page. It could : be lots more helpful. agreed 100% Warner ___ [EMAIL PROTECTED] mailing list http://lis

Re: devd *NOT* called on wi0 insert?

--On Friday, September 05, 2003 15:41:22 -0500 Larry Rosenman <[EMAIL PROTECTED]> wrote: > Although I'd like to tell it NOT to config the onboard rl0 interface. : > : > Will ifconfig_rl0="NO" do that? : In answer to my own question, the answer is NO. : : So, we still need a way to do that. You

Re: devd *NOT* called on wi0 insert?

--On Friday, September 05, 2003 14:37:04 -0600 "M. Warner Losh" <[EMAIL PROTECTED]> wrote: In message: <[EMAIL PROTECTED]> Larry Rosenman <[EMAIL PROTECTED]> writes: : : : --On Friday, September 05, 2003 14:37:39 -0500 Larry Rosenman : <[EMAIL PROTECTED]> wrote: : : > : > : > --On F

Re: devd *NOT* called on wi0 insert?

In message: <[EMAIL PROTECTED]> Larry Rosenman <[EMAIL PROTECTED]> writes: : : : --On Friday, September 05, 2003 14:37:39 -0500 Larry Rosenman : <[EMAIL PROTECTED]> wrote: : : > : > : > --On Friday, September 05, 2003 13:30:03 -0600 "M. Warner Losh" : > <[EMAIL PROTECTED]> wrote: :

Re: devd *NOT* called on wi0 insert?

--On Friday, September 05, 2003 14:37:39 -0500 Larry Rosenman <[EMAIL PROTECTED]> wrote: --On Friday, September 05, 2003 13:30:03 -0600 "M. Warner Losh" <[EMAIL PROTECTED]> wrote: I do have pccard_ifconfig=DHCP in my rc.conf. Aha! I added this, and it now works(tm). Although I'd like to te

Re: devd *NOT* called on wi0 insert?

--On Friday, September 05, 2003 13:30:03 -0600 "M. Warner Losh" <[EMAIL PROTECTED]> wrote: In message: <[EMAIL PROTECTED]> Larry Rosenman <[EMAIL PROTECTED]> writes: : I have a (within the week) -CURRENT system. If I boot with my Linksys : WPC11 V.3 card inserted : I get the dhcp a

Re: devd *NOT* called on wi0 insert?

In message: <[EMAIL PROTECTED]> Larry Rosenman <[EMAIL PROTECTED]> writes: : I have a (within the week) -CURRENT system. If I boot with my Linksys : WPC11 V.3 card inserted : I get the dhcp actions and all is fine. If I remove the card, we don't : kill off dhclient. : : If I boot w