SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
i just finished upgrading to FRG Gnome 2.12 and during installation i said "No" to installing (don't know if that's the correct word) rc scripts. how do i go about letting it do those rc scripts. any help would be appreciated.
Distribution: Slackware64 14.2 and current, SlackwareARM current
Posts: 1,645
Rep:
I don't know if there is a routine for doing this, since I have gware installed. But you can search which packages would have installed a script in /etc/rc.d, I guess.
What do you get If you do a
You could then take a deeper look in the appropriate files in /var/log/packages to see if there really would have been installed a file in that directory (look at the FILE LIST section) and reinstall these packages.
Last edited by titopoquito; 11-29-2005 at 03:51 AM.
Originally posted by titopoquito I don't know if there is a routine for doing this, since I have gware installed. But you can search which packages would have installed a script in /etc/rc.d, I guess.
What do you get If you do a
You could then take a deeper look in the appropriate files in /var/log/packages to see if there really would have been installed a file in that directory (look at the FILE LIST section) and reinstall these packages.
Now I get the idea. (see my previous posting)
titopoquito's script did not do anything for me (i am running KDE now, but have FRG installed.
Code:
# cd /var/log/packages
# ls *frg
# find . -name "*frg" -exec grep -l "etc\/rc.d" \{\} \;
does the trick.
there are 4 rc-files issued by freerock.
this is appearently my new rc.local after having installed freerock:
Code:
#!/bin/sh
#
# /etc/rc.d/rc.local: Local system initialization script.
#
# Put any local setup commands in here:
#
## some private settings remained, but are removed here.
## the following lines were inserted here at freerock install time
# To disable howl, chmod rc.howl to 644
if [ -x /etc/rc.d/rc.howl ]; then
echo "Starting Howl mDNS daemons"
. /etc/rc.d/rc.howl start
fi
# To disable dbus, chmod rc.messagebus to 644
if [ -x /etc/rc.d/rc.messagebus ]; then
echo "Starting D-BUS Messaging Subsystem"
. /etc/rc.d/rc.messagebus start
fi
# To disable hal, chmod rc.hal to 644
if [ -x /etc/rc.d/rc.hal ]; then
echo "Starting HAL"
# wait a few seconds to let udev complete its
# initialization. Otherwise hald will not recognize CD/DVD
# drives and will not start polling them
( sleep 5; /etc/rc.d/rc.hal start ) &
fi
These rc.owl, rc.dbus and rc.hal scripts exist indeed in /etc/rc.d.
they are NOT executable.
My problem is that I have no idea what purpose these scripts are for, what their use is, what they do?
I am not going to try them before I know what they do.
Could anyone explain, where I can find this.
freerock gnome runs fine as i am concerned.
My guess is that it matters which kernel you have, and how you configured it.
not sure exactly what rc.howl does, except rc.howl has something to do with dns and i think HAL makes easy for devices like cd-rom's, media cards and digital camera to mount on your machine.
i upgraded to slack 10.2 (kernel 2.6.10) now and installed Frg gnome 2.12.1, but the only problem with this is, everything seems to be crashing. everytime i try to change the desktop background, that crashes, theme manager crashes. bmpx crashes.
what i did notice is if i create another user and try to use Xnest to login everything works fine but if i login via gdm using any user profile everything's crashing. i'm not sure if anyone's having the same issue but if someone can point out what's going on i would really appreciate it. my gnome desktop is useless for now and i'm using XFCE until i figure out why gnome's kaputz.
Distribution: Slackware64 14.2 and current, SlackwareARM current
Posts: 1,645
Rep:
Quote:
Originally posted by Douwe Now I get the idea. (see my previous posting)
titopoquito's script did not do anything for me (i am running KDE now, but have FRG installed.
Code:
# cd /var/log/packages
# ls *frg
# find . -name "*frg" -exec grep -l "etc\/rc.d" \{\} \;
Distribution: Slackware64 14.2 and current, SlackwareARM current
Posts: 1,645
Rep:
Quote:
Originally posted by Douwe My guess is that it matters which kernel you have, and how you configured it.
From the Gware website, I think this should be correct for Freerock Gnome as well:
Quote:
The GWARE GNOME package set is a complete GNOME build that takes advantage of the powerful features of D-BUS and HAL, which rely on the hotplug system of the 2.6 kernel. Thus, a 2.6 kernel is highly recommended for use with GWARE.
About these rc.howl, rc.dbus and rc.hal scripts:
I looked at the GWARE site (better info there then at freerock!) and googled around.
These seem to me highly experimental stuff for developers.
I will not use them now.
Unclear in any case is which common programs are using (one of) them.
If you are not a developer, you will not miss them.
I will enable them if it turns out that common programs need them.
Me personal don't like the freerock people put them in rc.local, which IMHO is for the user, not the distro-maker.
however I must admit: my personal stuff in rc.local was untouched.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.