Re: Sound files on bootup; IMessenger for SuSE

From: Dan Say (danielsay_at_NOSPAMyahoo.com)
Date: 04/02/04


Date: Thu, 01 Apr 2004 22:19:24 GMT

In article <20040329001248.516113f3@allevil.local>, Kevin Nathan <knathan@project54.com> wrote:
>On Mon, 29 Mar 2004 02:12:55 GMT
>DanielSay@NOSPAMyahoo.com (Dan Say) wrote:
>
>> Thousands of programs and no obvious index.
>
>Yes, one the more frustrating aspects of learning Linux is finding the
>program names for what you want to do! One method is to cruise through
>the various /bin/ dirs and see what's there. Don't run anything without
>first reading the man page, though -- unless you are *really*
>adventurous, and don't mind fixing a self-inflicted wound! :-)
          Found a good chapter in Koffler's book
          Linux: Installation, Configuration, Use.
          Pity that there is no further English editions than the 2nd.
          His web site shows that the book substantially increased
          with the fourth German-language edition.
>
>Another method is to use 'apropos' with a word or term for which you'd
>like to see if there is any reference. For example, with your sound'
>query, try:
> apropos wav or apropos sound
>('man -k' performs a similar function.)
>
>To answer your other question, you will need to go thru the boot
>sequence for Linux, and especially SUSE's version. If you have the
>boxed set, their Admin Guide usually covers it and then there are good
>Linux-generic docs on:
>
> http://www.tldp.org/
>
>Basically, the startup scripts are in:
>
> /etc/init.d/

           Yes, found similar initrd leads in the little essay
           "What is unique about SuSE" somewhere in
           the manuals and on the SuSEgreeter page
           program function. It is a start to try and
           do something from a user and from root, or
           for each user. I'll have to print and cogitate.
>
>with the different runlevels having links to the scripts to run on
>entering and leaving a runlevel in dirs under that one, like:
>
> /etc/init.d/rc3.d/
>
>and so on. Generally, you don't want to mess around in system scripts,
>since SUSE may trash your changes on the next upgrade (or not change
>the script on an update because you modified it), but rather create your
>own scripts and add them to the boot sequence.



Relevant Pages

  • Re: Why does /etc/rc.d/rc work the way it does?
    ... ]>> from the current level and then start scripts from the new level. ... it runs both the kill scripts and start scripts from the new level. ... For example level 3 has networking and level 2 does not. ... in all runlevels. ...
    (comp.os.linux.setup)
  • Re: /etc/rc.boot
    ... > Please don't make me write init.d scripts for every single line ... and add it into the boot sequence using ... then you need multiple scripts, but nothing is stopping you from ... "Theoretical politics is interesting. ...
    (Debian-User)
  • Re: boot.local
    ... items run AFTER all other init scripts have been executed. ... Where in SuSE 10 can items be added to run AFTER all other init ... place in the boot sequence? ...
    (alt.os.linux.suse)
  • Re: Files in the /rtc/rc.d/rc*.d directory
    ... > scripts that are called when the system boots in each of the possible ... And when the systems shuts down are the scripts in this ... > about the digital code after the letter S or K, ...
    (comp.os.linux.misc)