linux-hotplug.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ken Ryan <newsryan42@leesburg-geeks.org>
To: linux-hotplug@vger.kernel.org
Subject: Re: SuSE 10.0 udev stuck with bogus name / rule entry
Date: Fri, 09 Jun 2006 03:36:11 +0000	[thread overview]
Message-ID: <4488ECAB.9000608@leesburg-geeks.org> (raw)
In-Reply-To: <44886E78.3000801@leesburg-geeks.org>

Greg KH wrote:

>On Thu, Jun 08, 2006 at 02:37:44PM -0400, Ken Ryan wrote:
>  
>
>>Hello.
>>
>>I'm trying to recover from a failed attempt at creating a udev rule.
>>
>>I'm running SuSE 10.0, pretty well up to date via YOU.
>>    
>>
>
>Any chance of trying out 10.1 now?  This list isn't for distro specific
>support, sorry, try one of the opensuse mailing lists (but they will
>probably just recommend upgrading to 10.1...)
>
>good luck,
>
>greg k-h
>  
>
I am planning on upgrading to 10.1 whenever I get my shipment from 
Novell (I took
Novell up on their free shipping offer, now the box has been on 
backorder for a couple
weeks.  My net connection is only a measly 128kb so the idea of 
downloading iso
images doesn't appeal to me).  I have to admit I've become a bit leery 
about upgrading
because of all the folks griping on the suse lists about how buggy 10.1 is.

I know the list isn't for distro-specific stuff; I was hoping a 
udev/hotplug guru would be
able to help me understand what the heck happened, and where ttyS0 is 
getting remembered.
As I continue to dig into this I'm getting the impression that udev and 
hotplug are necessarily
very distro-specific so I can understand if you can't really help.  I 
did post to a couple suse
lists, I just thought I might get lucky.

I did find that if I put lines at the end of the start case in boot.udev 
which mimic the
force-reload activity plus a small delay the system then comes up fine.  
I'm now trying
to figure out how to get the corrected entries remembered by suse's boot 
process.  With
the hack in place I boot almost normally, I get xdm and everything since 
/dev is properly
populated.  If I take the hack back out it reverts to the broken state.  
Since I can't figure out
what got ttyS0 stuck in there I don't know how to overwrite it.

Now that I am able to boot after a fashion, though, I'm going to pull 
out my last backup and
see if I can find the bogus rule...perhaps you or someone else on the 
list can give me a clue
as to what my erroneous rule might have done.

I miss my Slackware installation.  All this idiot-resistant gui stuff is 
great until something
breaks, then it seems to be impossible to figure out.

       ken




_______________________________________________
Linux-hotplug-devel mailing list  http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel

  parent reply	other threads:[~2006-06-09  3:36 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-08 18:37 SuSE 10.0 udev stuck with bogus name / rule entry Ken Ryan
2006-06-09  2:30 ` Greg KH
2006-06-09  3:36 ` Ken Ryan [this message]
2006-06-09 11:18 ` Kay Sievers
2006-06-10  1:40 ` Ken Ryan
2006-06-10 10:41 ` Kay Sievers

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4488ECAB.9000608@leesburg-geeks.org \
    --to=newsryan42@leesburg-geeks.org \
    --cc=linux-hotplug@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).