Re: trends in fedora

Bill Davidsen wrote:
Rex Dieter wrote:
Bill Davidsen wrote:


Given that the network isn't brought up until the user logs in

Checking the "activate device when computer starts" option in
system-config-network works nicely for me.

I had the feeling that I needed NM to get wsa working, but I'll try anything at this point. I'll let you know if that helps.

It appears that the current working solution is to start the interface by hand after the system is up, define it in network and keep NM out. It may be that NM simply came in with an upgrade at the same time as the breakage, but I'm not going back.

The proximate cause seems to be that DHCP tried to set up the NIC before it associates, because the supplicant is either not starting early enough or just taking too long to get connected. I about 85% sure of that sequence, most o the time I get associated but no IP, and my little script doesn't start dhclient until the AP is connected.

I just wish upgrade would mean "works better" rather than "works differently if at all." This system was dead reliable before the "security update" came along.

The timing of this startup may well have been right on the edge before the upgrade, and making something faster might be the one thing which made it too fast.

Thanks to all who offered ideas, given the ability to generate a script and no issues about running it being too inconvenient, I'm regarding this as ugly but working.

--
Bill Davidsen <davidsen@xxxxxxx>
"We have more to fear from the bungling of the incompetent than from
the machinations of the wicked." - from Slashdot

--
fedora-list mailing list
fedora-list@xxxxxxxxxx
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines

Relevant Pages

  • automate dcpromo during nt4 pdc upgrade to W2k3 DC
    ... I am attempting to script the upgrade of a NT4 PDC to a W2K3 domain ... I have set the UnAttendMode to ... FullUnattended and the upgrade works perfectly up to the point where the ... @rem SetupMgrTag ...
    (microsoft.public.windows.server.migration)
  • Re: samba-common = 3.0.23d-4 but 3.0.24-2 is installed
    ... wants to upgrade to is 3.0.23d-4 which is lower. ... The problem is that the pre-removal script ... Reading package lists... ... warning - old pre-removal script returned error exit status 102 ...
    (Debian-User)
  • Re: FC2 upgrade-X problem
    ... Immideately after upgrade completed I ran 'yum update' ... > getting the X server to launch. ... I made up a test script that runs all the ... > longer able to run startx. ...
    (Fedora)
  • Re: Can someone help me write a "yes-man" program
    ... not work with the Ubuntu system upgrade script, ... which upgrade script you mean. ... from optparse import OptionParser ...
    (comp.lang.tcl)
  • Re: Some thoughts about Fedora Core 1 packages upgrade
    ... > upgrade hundreds of clients through Internet(big burden on Internet ... > building options, we have to download source RPMs as well, so there ... i'd recommend the apt-mirror script to be run once a day, ...
    (Fedora)