slackware speakup and pcmcia

[Joseph C. Lininger]

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

For the most part, unchecking something in the list of things to start 
actually does result in the service being disabled. At least that has 
been my experience when I've installed Slackware. I'm willing to bet 
that either you accidentally didn't uncheck that when you thought you 
had, or that there was just a small oversite on the part of the author 
of the slackware setup script. Probably a simple typo or something. The 
only real way to know for sure is if someone else has had the problem of 
having pcmcia installed, but not selected to have it run at boot up. If 
the script didn't have the exec bit switched off on their system, then 
we know it's the setup script. If it turns out that it is the setup 
script, I'd be willing to check it out and submit a patch.

- -- 
It's not one damn thing after another, it's the same damn thing over and
over. (History repeats itself)
Joseph C. Lininger
jbahm at pcdesk.net
Verification: 5eab38a77ac40416e075be8f50607ff7

And so it came to pass that on Mon, 5 Sep 2005, Jude DaShiell said

> Okay, thanks much that fix with using chmod to turn off the executeable bit 
> on the /etc/rc.d/rc.pcmcia script worked.  What should probably worry lots of 
> slackware installers is that if a decision to disable pcmcia on the install 
> really didn't disable pcmcia what else was left running they wanted to have 
> turned off.
>
>
>
> _______________________________________________
> Speakup mailing list
> Speakup at braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
>
>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)

iD8DBQFDHZwKJ6dqn0mqPbARAo2AAJ9MbaZYOl8ebfgR+66TedukTwl/QgCg5g2X
EAyrLn2TdJjX7ALSu9bgrvA=
=8j6T
-----END PGP SIGNATURE-----