Re: [SLE] How to deactivate SuSEPlugger and SuSEWatcher on GNOME startup

From: Joe Morris (NTM) (Joe_Morris_at_ntm.org)
Date: 06/02/05

  • Next message: CorvusE: "Re: [SLE] nss_db" 
    Date: Thu, 02 Jun 2005 14:49:10 -0500
To: SLE <suse-linux-e@suse.com>

    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@ntm.org
Registered Linux user 231871
-- 
Check the headers for your unsubscription address
For additional commands send e-mail to suse-linux-e-help@suse.com
Also check the archives at http://lists.suse.com
Please read the FAQs: suse-linux-e-faq@suse.com
  • Next message: CorvusE: "Re: [SLE] nss_db"

    Relevant Pages

    • Re: AD Restore disaster please help.........
      ... Usually the problem that occurs on dissimilar hardware is regarding the HAL ... Our AD environment consists of a Win2k3 R2 Forest, with Root domain ... the root and two in the child. ... For the last two days I've been trying to do a restore of the system ...
      (microsoft.public.windows.server.active_directory)
    • Re: Trying to reconfigure F9 to new computer hardware... firstboot?
      ... I am not sure that copying the root partition from one machine to another ... Was there some special reason not to use one of the normal install methods ... usability and now that you know everything works, you want to migrate your working setup to real hardware. ... filesystem or broken hard disk as a backup/restore method. ...
      (Fedora)
    • Re: Fedora Core 3 & Core 4 Password questions
      ... >>Is there any length of complex password that can be assigned to the ROOT ... > Then don't install it on the users hardware, ... the disk directly accessed and software ... Someone who has enough patience can work their way through the locks. ...
      (alt.computer.security)
    • Re: VM Rootkits: The Next Big Threat? (PC Magazine)
      ... Such close relationships with hardware allow the OS to be ... they were trojan backdoored unix binary executables offering ... remote root access to the attacker that installed them. ... actual hardware and the so-called "rootkit" act as the platform for it. ...
      (alt.comp.anti-virus)
    • Re: [SLE] How to deactivate SuSEPlugger and SuSEWatcher on GNOME startup
      ... > user has turned off suseplugger, and there is new hardware that has not been ... > installed, since there is only one hardware installation cache, ... The root user had never logged in, as root, I think. ... And yast says nothing about new hardware, ...
      (SuSE)