I am new to all this and was trying to have slackware shutdown the
computer completely. I read that I needed to modify the rc.modules file
in etc/rc.d/ Not realizing that by using KWord when I modified the line
the file became rc.kwd which is not a shell script file.

My question is how do I get the rc.kwd text file converted to a shell
script file? In the KWord open recent files it lists the file as a icon
woth a LOCK. When I click on it, an error saying that it doesn't exist.


I looked in the trash and there are some files there but not the shell
script file rc.modules. I have been using KDE for all of this and
really not that swift with the command prompts.

thanks.. douglas

jgiels@sbcglobal.net wrote:

> My question is how do I get the rc.kwd text file converted to a shell
> script file? In the KWord open recent files it lists the file as a icon
> woth a LOCK. When I click on it, an error saying that it doesn't exist.
>
>
> I looked in the trash and there are some files there but not the shell
> script file rc.modules. I have been using KDE for all of this and
> really not that swift with the command prompts.
>
> thanks.. douglas
>

if it's just a name-thing, then just do " mv rc.kwd rc.modules " and
check if it's still executable.
if the file is damaged ; the file comes with the package "
kernel-modules-2.4.29-i486-1 ".

btw : if you ever damage a file, and want to know in wich package it came,
you can use " grep <filename> /var/log/packages/*

cashmir

On 2005-05-06, jgiels@sbcglobal.net <jgiels@sbcglobal.net> wrote:
> I am new to all this and was trying to have slackware shutdown the
> computer completely. I read that I needed to modify the rc.modules file
> in etc/rc.d/ Not realizing that by using KWord when I modified the line
> the file became rc.kwd which is not a shell script file.
>
> My question is how do I get the rc.kwd text file converted to a shell
> script file? In the KWord open recent files it lists the file as a icon
> woth a LOCK. When I click on it, an error saying that it doesn't exist.
>
>
> I looked in the trash and there are some files there but not the shell
> script file rc.modules. I have been using KDE for all of this and
> really not that swift with the command prompts.
>
> thanks.. douglas
>

Try this: go toa terminal window, xterm...something like that.

at the command prompt %

If you're not root, and you shouldn't be

% su -root
% cd /etc/rc.d
% cp rc.kwd rc.modules
% chmod 755 rc.modules (just in case)

1. never use anything but a text editor to edit config file, something like,
emacs, jed, joe, pico, xemacs...one of these should be on your machine.

This should work for you.

ken

I did this ken and all it did was create a file called rc.modules BUT
its not a script file..

On 2005-05-07, jgiels@sbcglobal.net <jgiels@sbcglobal.net> wrote:
> I did this ken and all it did was create a file called rc.modules BUT
> its not a script file..
>

Assuming that the kword file wasn't empty in the first place:

%less rc.modules

All the characters should be plain, readable text, if not then kword saved
as a binary file...I don't use kword so I can't say...I don't even have it
installed. If it's not plain text open kword and save as a text file, kword
should have this option

Otherwise................

Make sure that the first line is:
#!/bin/sh

then make sure the permissions are correct:

%ls -la rc.* should read.

-rwxr-xr-r .................rc.modules

if not you have to use the chmod command specified earlier or explain why
it's not a script file.

If the file is empty then you have to get a fresh copy from the cd or your
install copy.

ken

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

In alt.os.linux.slackware, No_One dared to utter,
> at the command prompt %
>
> % su -root
> % cd /etc/rc.d
> % cp rc.kwd rc.modules
> % chmod 755 rc.modules (just in case)

Better yet. (Sorry for the long line guys.)

# su -
# ncftpget ftp://ftp.scarlet.be/pub/slackware/s....29-i486-1.tgz
# tar -xzf kernel-modules-2.4.29-i486-1.tgz etc/rc.d/rc.modules.new
# mv etc/rc.d/rc.modules.new /etc/rc.d/rc.modules
# rm -fr etc/rc.d # NOTE! Do _NOT_ do rm -fr /etc/rc.d Note the
# leading slash!
# cd /etc/rc.d/
# rm *.kwd
# chmod 755 rc.modules

That should get you up and no matter what (provided you have ncftp
installed of course).

> 1. never use anything but a text editor to edit config file, something like,
> emacs, jed, joe, pico, xemacs...one of these should be on your machine.

What?! No vi?! Thou shalt bow at the altar of Slack and say three
Hail Bobs everyday for a week! Thou must also pay $99.95 to atone.

- --
It is better to hear the rebuke of the wise,
Than for a man to hear the song of fools.
Ecclesiastes 7:5
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQFCfCDovgVcFKpJf4gRAggkAKCpO5BnT6vDvOEadFqHXE jRL5poAACeJqT4
tYe3IxsXZd39xQqzMe4loFA=
=ZSK1
-----END PGP SIGNATURE-----

On 2005-05-07, +Alan Hicks+ <alan@lizella.netWORK> wrote:
>
> # su -
> # ncftpget ftp://ftp.scarlet.be/pub/slackware/s....29-i486-1.tgz
> # tar -xzf kernel-modules-2.4.29-i486-1.tgz etc/rc.d/rc.modules.new
> # mv etc/rc.d/rc.modules.new /etc/rc.d/rc.modules
> # rm -fr etc/rc.d # NOTE! Do _NOT_ do rm -fr /etc/rc.d Note the
> # leading slash!
> # cd /etc/rc.d/
> # rm *.kwd
> # chmod 755 rc.modules

Better solution
>
>> 1. never use anything but a text editor to edit config file, something like,
>> emacs, jed, joe, pico, xemacs...one of these should be on your machine.
>
> What?! No vi?! Thou shalt bow at the altar of Slack and say three
> Hail Bobs everyday for a week! Thou must also pay $99.95 to atone.

Vi? Vi???. Oh, you mean that ancient program some diehards pretend is a
text editor.

ken

"No_One" typed:
> On 2005-05-07, +Alan Hicks+ <alan@lizella.netWORK> wrote:
>> What?! No vi?! Thou shalt bow at the altar of Slack and say three
>> Hail Bobs everyday for a week! Thou must also pay $99.95 to atone.
>
> Vi? Vi???. Oh, you mean that ancient program some diehards pretend
> is a text editor.

Hmm! Doesn't look ancient to me--

ayaz[4][~]$ vi --version
GNU Emacs 21.3.2
Copyright (C) 2002 Free Software Foundation, Inc.
GNU Emacs comes with ABSOLUTELY NO WARRANTY.
You may redistribute copies of Emacs
under the terms of the GNU General Public License.
For more information about these matters, see the file named COPYING.

--
Ayaz Ahmed Khan http://fast-ce.org/ayaz/

I was going through some code from 2002, frustrated at
the lack of comments, cursing the moron who
put this spaghetti together, only to realize later that
I was the moron who had written it.

-- CowboyRobot wrote on /.

jgiels@sbcglobal.net wrote:

> I am new to all this and was trying to have slackware shutdown the
> computer completely. I read that I needed to modify the rc.modules
> file in etc/rc.d/...

mc > enter > F3 > up to /.. > enter up to /etc > enter > down to /rc.d >
enter > down to *rc.modules > F4 > down to #### APM Support ### fourth
line #/sbin/modprobe apm delete the #at the front of that line and
reboot.

The usual caveats about being root apply.

--
Two Ravens
"...hit the squirrel..."

* Ayaz Ahmed Khan <resilient@myrealbox.com> writes:

> "No_One" typed:
>> Vi? Vi???. Oh, you mean that ancient program some diehards pretend
>> is a text editor.

> Hmm! Doesn't look ancient to me--

> ayaz[4][~]$ vi --version
> GNU Emacs 21.3.2

Beautiful! Of course it'd be better if it said "XEmacs" or
"SXEmacs". :-)


--
|---<Steve Youngs>---------------<GnuPG KeyID: A94B3003>---|
| Genius - Is the ability to reduce |
| the complicated to the simple |
|----------------------------------<steve@youngs.au.com>---|