Mailinglist Archive: opensuse (2441 mails)

["Joe Morris (NTM)" <Joe_Morris@xxxxxxx>]

Carlos E. R. wrote:
> The root user had never logged in, as root, I think.
To kde I'll assume.  Same here, except by accident from console 1.
> In any case, when I 
> did log in as root a few days ago, I was told that "new hardware was 
> found", namely, the ethernet card that has been working for years, and 
> continues to be installed and working. So I told it to go away. 
>
>  
Thus the problem.  It is working, but it does not mean it is in the Yast 
hardware database.  Once it is there, it will not prompt unless 
something changes (and it won't even if something changes if suseplugger 
can't run, i.e. since you renamed them).
> I just want it to shut up for ever: if I want to mantain hardware, I'm 
> clever enough to fire up yast. And yast says nothing about new hardware, 
> it is happy and content.
>
>  
What does it show for the NIC in Yast>Hardware>Hardware Information?  
Just running it seems to create new unique keys, so that might solve 
your problem.  Hope so. :-)
> What do you sugest, that I start as root again, say ok to new hardaware 
> found, "a la windows", allow it to proceed and perhaps break something 
> that is already working?
Not necessarily, just that the fact the module loads and the card works 
doesn't mean it is "found" hardware as far as Yast is concerned (though 
since that is what Yast was supposed to do it should have).
> Can't just I say, good doggy, now be good and 
> shut up?
I'm sure you can.  I was just pointing out that suseplugger is quiet for 
all users once it has "found" all present hardware.  It will only prompt 
a "new" user about new hardware if there is new hardware.  If you made 
sure it was all "found", that puppy WOULD be quiet.  My point was there 
was another way to shut it up, which was IIUC the designed way.
--
Joe Morris
New Tribes Mission
Email Address: Joe_Morris@xxxxxxx
Registered Linux user 231871