Slackware This 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.
Are you new to LinuxQuestions.org? Visit the following links:
Site Howto |
Site FAQ |
Sitemap |
Register Now
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.
|
 |
01-13-2004, 04:55 PM
|
#1
|
LQ Newbie
Registered: Dec 2003
Location: Cobourg, ON
Distribution: Slackware 10/Suse 9.2
Posts: 19
Rep:
|
Program on boot-up won't stop running in a continuous loop...
First of all, I think this has to do with my addition of "/seti/setiathome &" to the rc.d script.
Upon rebooting my system for the first time, it would ask me for a new user name or to create a new account. I can't even identify if it is seti or not because all it does is this.
Now, to the point: How can I boot up Linux and delete this line out of rc.d? It really is the only change that I can think back to that might do this. Everything else seems to work fine at boot-up except for this program that keeps running until my computer restarts. It doesn't even get to the login prompt.
Or do you think it might be something else? I just want to be able to log in so I can sort this mess out...
Thanks!
|
|
|
01-13-2004, 05:13 PM
|
#2
|
Member
Registered: Jan 2004
Posts: 33
Rep:
|
I am not sure if I understood you correctly, but is the problem a program that starts itself upon bootup and then restarts the machine? Or...? Do you at all get to a login prompt in text or X mode?
In any case, boot up in single mode. From your lilo or grub prompt choose a kernel to boot and add "single" to it so that you can boot up into single mode. You will need your root password and from there you can do some damage.
Alternatively, use a rescue CD or floppy and modify your /etc/rc.d
However, I find it really suspicious that you cannot login because some piece of software is running...
G.
|
|
|
01-13-2004, 06:12 PM
|
#3
|
LQ Newbie
Registered: Dec 2003
Location: Cobourg, ON
Distribution: Slackware 10/Suse 9.2
Posts: 19
Original Poster
Rep:
|
I'm sorry if my description sucked, but that was the best I could do...
-I suspect that this is a program that I set to run at bootup in rc.d
-I don't know if it is supposed to restart the machine, but the only way to get out of it is with ctrl+alt+del, and then all of a sudden it stops and restarts the machine.
-No, I don't get as far as the login prompt.
-This particular machine is a server and I did not install X on it at all.
About booting in single mode...
Would I just type, for example, 'bare.i -single'?
|
|
|
01-13-2004, 06:19 PM
|
#4
|
Member
Registered: Jan 2004
Posts: 33
Rep:
|
get into the (lilo) prompt and type "<image name> single" without the quotes. See if that works. I am not sure I remember if booting into single mode runs through rcX.d or not, I think not, that's why I say give it a shot.
G.
|
|
|
01-13-2004, 06:19 PM
|
#5
|
Member
Registered: Jan 2004
Posts: 33
Rep:
|
To make it clearer:
if your image is: linux-2.6.1, you would do (in the prompt):
linux-2.6.1 single
G.
|
|
|
01-13-2004, 09:00 PM
|
#6
|
Member
Registered: Dec 2002
Location: Winnipeg, Manitoba, Canada
Distribution: Slackware
Posts: 371
Rep:
|
If that doesnt work here is another method put in your installation cd such as slackware 9.0 (for me) then once it boots up and then once you login in as root type
mount /dev/rootpartition /mnt
then that should mount your root partition so you can go into /etc/rc.d and edit whatever u wanna edit using pico or whatever program you use this was the easyest way i could think of to do what i belive ur trying to do GOOD LUCK!
Matt3333
|
|
|
01-14-2004, 01:06 AM
|
#7
|
LQ Newbie
Registered: Dec 2003
Location: Cobourg, ON
Distribution: Slackware 10/Suse 9.2
Posts: 19
Original Poster
Rep:
|
Thanks for the help, G.
Booting into 'single' mode did the trick. Seti@home isn't acting up anymore...
|
|
|
All times are GMT -5. The time now is 09:31 PM.
|
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
|
Latest Threads
LQ News
|
|