Announcement

Collapse
No announcement yet.

couple of questions for a new user please

Collapse
This topic is closed.
X
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    couple of questions for a new user please

    1. I want to launch my vnc server at boot (I'm using x11vnc, and it's working, so that's not important really here). I found a post to help me: http://kubuntuforums.net/forums/index.php?topic=5358.0.

    It asks me to locate the /etc/init.d file. I don't have anything called init.d in /etc. I've seen init.d referred to before on other matters....any ideas where I can locate this ? Am I right in assuming that this is the startup config file ?

    2. In Konq, I really would like to have the default view of 'detailed list view' for file/folder browsing. Elsewhere it says that a session can be saved, but I have failed to understand exactly how this works - every time I relaunch ( I use the default menu bar "Home Folder" to launch Konq ) it always comes up with the icon view. Is there a dummies guide to how to do this: I've had a look, but am not able to come up with anything where I can see where I'm going wrong.

    Thanks for any help out there !!!

    #2
    Re: couple of questions for a new user please

    init.d is a folder in etc and is used on the command line as the service command for stopping/starting/restarting or displaying the status of a service in the folder /etc/init.d/
    example: sudo /etc/init.d/cupsys restart
    cupsys is found in the init.d folder so it can be used


    In Konq setup the window as you like then goto settings...save view profile "Kubuntu File Manager" ... you might like to save the window size settings too then use the checkbox on the dialog window that comes up.
    Kubuntu 18.04 on AMD

    Comment


      #3
      Re: couple of questions for a new user please

      /etc/init.d/ is the general storage place for 'startup scripts'
      There are also directories rc.0 rc.1 .... rc.6 around somewhere in /etc (maybe rc.d, my memory fails me)
      The number at then end of rc. refers to the 'runlevel' , 0 being halt (it is now safe to turn off your computer in win95 terms), 1 being single user (recovery terminal), and *see addendum* 2 being full boot.
      You can create symlinks from real files in /etc/init.d to a runlevel folder, and these scripts will start services fot that runlevel E.G. gdm in rc.2 will start the gnome desktop manager in runlevel 2.
      There is a rc.local file, which is sepecifically for you to write your own commands in. If local is in rc.2 then all my commands in the rc.local file will be run on entering runlevel 2 (in my case start my bzflag and AA server scripts, start rundns for my dyndns hostnames and check for my usb key and mount my encrypted partitions if it is)

      rc.local is fairly limited in what it can do though, sometimes you may have write bash scripts for rc.local to run the comamnd you want, if this becomes the case then writing your own 'init scripts' isn't too hard, pick a simple service ( like gpm or logrotate), see how it works and change it to suit *your* needs, rename it and you have created a new boot service, add it to the rc.x of your choice and away you go.


      **addendum**
      K/Ubuntu is the first distro I have ever seen that has only two 'alive' runlevels (ie not shutdown or reboot)((|Maybe debian did, But I had to do sooo much to make it 'work for me' I didn't notice))
      'Normally' 0 is halt (shutdown), 1 is single user mode (recovery mode), 2 is multi user BUT no network (arghhh I got a virus), 3 is multiuser with network (everything really), 4 is 'custom', 5 is rc.3+xserver and Gnome/KDE/{Insert WM of choice} related services, 6 is reboot. All these are changable though through /etc/inittab and the appropiate rc.x directory. This may seem useless and redundant, but for an example, say you have XGL installed to make your 'I can't get Vista yet' friends a bit green eyed but don't want to run it all the time, setup XGL to run through KDM, and normal X to run through GDM, then set the DM for runlevel 4 to run GDM and 5 to run KDM, when you want to show off XGL, switch from runlevel 4 to 5 (sudo init 5) and away it goes......

      Comment


        #4
        Re: couple of questions for a new user please

        For the Konqueror view profiles....I've saved the view profile, but I don't understand how to launch Konqueror so that it uses that view profile when its launched. I'm guessing that there's something in the GUI, or is this a command line thing ? Thanks for the help.

        Comment


          #5
          Re: couple of questions for a new user please

          Originally posted by jrleighton
          I've saved the view profile, but I don't understand how to launch Konqueror so that it uses that view profile when its launched.
          1. You can add a 'Konqueror Profiles' menu to the Panel or the KMenu

          2. You can launch a profile with command
          Code:
          konqueror --profile <PROFILE>
          (Where <PROFILE> is the name of the profile)

          You can get a list of available profiles with
          Code:
          konqueror --profiles
          You can also create a launcher (shortcut icon) for the profile instead of typing the command, of course

          Comment


            #6
            Re: couple of questions for a new user please

            Thanks treppic for that very informative post about init.d and the rest ... I had no idea yet it was a part of all of that.
            Kubuntu 18.04 on AMD

            Comment


              #7
              Re: couple of questions for a new user please

              Originally posted by Teppic
              **addendum**
              K/Ubuntu is the first distro I have ever seen that has only two 'alive' runlevels (ie not shutdown or reboot)((|Maybe debian did, But I had to do sooo much to make it 'work for me' I didn't notice))
              Kubuntu has 'normal' runlevels from 2 to 5, just that the default runlevel is 2 (like debian).
              However, all the runlevels run the same services by default...you can of course edit the runlevels either manually, with systemservices kcontrol module or with 'sysv-rc-conf'

              Comment

              Working...
              X