LinuxQuestions.org
Visit Jeremy's Blog.
Home Forums Tutorials Articles Register
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices


Reply
  Search this Thread
Old 12-12-2008, 11:37 AM   #1
TSquaredF
Member
 
Registered: Dec 2005
Location: "The South Coast of Texas"
Distribution: Slackware64-current
Posts: 564

Rep: Reputation: Disabled
Minor problems using extra/wicd in 12.2


Last night I upgraded my desktop to 12.2 & decided to use wicd to manage networking. I followed the README & moved /etc/rc.d/rc.inet1.conf.new to /etc/rc.d/rc.inet1.conf & didn't add anything to it. Did the same for rc.wireless, though this box has no wireless & it looks like I can't upgrade my laptop because of the madwifi drivers. The problem is that I have a cifs share in my fstab that is not getting mounted at boot time. I think the share is supposed to get mounted at line 101 in rc.M with the command
Code:
mount -a -v 2> /dev/null | grep -v "already mounted"
This is right after the commands that start rc.inet1 & rc.inet2. wicd is not started until line 170 in rc.M. I'm wondering if it makes any difference if I move the lines that start wicd up above the mount line, or should I move the mount line below the wicd code?
After the system is booted it just takes a
Code:
mount /mnt/mountpoint
to mount the share, so it mounts fine, just not automagically, when it should.
[Edit] It makes no difference whatsoever how the line are moved around in rc.M, the share does not get mounted because of an "unavailable network". I am now calling a script to mount the share from my rc.local & that works OK, but I would like to know how to do this from /etc/fstab.[/Edit]
Regards,
Bill

Last edited by TSquaredF; 12-12-2008 at 02:43 PM.
 
Old 12-13-2008, 09:07 PM   #2
niels.horn
Senior Member
 
Registered: Mar 2007
Location: Rio de Janeiro - Brazil
Distribution: Slackware64-current
Posts: 1,004

Rep: Reputation: 91
Are there any messages in /var/log/messages about the failed mount?

How is the mount defined in your /etc/fstab?
 
Old 12-13-2008, 09:53 PM   #3
slackass
Member
 
Registered: Apr 2006
Location: SE Texas
Distribution: Slack64-15.0
Posts: 910

Rep: Reputation: 90
I'm no expert on this stuff but all I did to get my wireless working is installed wicd with slackpkg and it detected my wireless and wired and set it up for me.
However:
You do have to set up encryption afterwards.

EDIT:
On one of my boxes I installed wicd from extra and it did not work right.
I then reinstalled it with slackpkg (with my wireless running unsecured) and then it detected it..

Last edited by slackass; 12-13-2008 at 10:01 PM.
 
Old 12-14-2008, 02:34 AM   #4
rworkman
Slackware Contributor
 
Registered: Oct 2004
Location: Tuscaloosa, Alabama (USA)
Distribution: Slackware
Posts: 2,559

Rep: Reputation: 1351Reputation: 1351Reputation: 1351Reputation: 1351Reputation: 1351Reputation: 1351Reputation: 1351Reputation: 1351Reputation: 1351Reputation: 1351
Here's the deal:
1. Wicd requires dbus.
2. Dbus requires the /usr filesystem.
3. /usr might require networking.
See the problem?

Long story short, we can't start wicd until after dbus.
We can't start dbus until after we *know* /usr is mounted.

Probably the best way to handle this is to stick a "mount -a" in rc.local.
 
Old 12-14-2008, 03:01 PM   #5
TSquaredF
Member
 
Registered: Dec 2005
Location: "The South Coast of Texas"
Distribution: Slackware64-current
Posts: 564

Original Poster
Rep: Reputation: Disabled
Thanks for the replies. Since I posted this, I have had a few nits caused by upgrading a 12.1 installation that had GSlacky installed to 12.2. Yesterday I backed everything up & did a fresh install of 12.2. I did not set up networking during the install & after I installed wicd, I went into /etc/rc.d/rc.inet2 & commented out the lines to mount nfs, cifs & smbfs shares, just to keep errors from popping up at boot time. I copied the lines concerning cifs shares into /etc/rc.d/rc.local. However, I still got "error 101: network not found". Since the mount command worked OK after the desktop was up, I thought that wicd just needed a bit more time, so moved it to the end of rc.local & inserted a "sleep 10" command. That got my share mounted. I shaved seconds off the sleep command & when I got to 4, the share would no longer mount. Now I am at "sleep 5" & all is well. As I add other things to rc.local, I will put them before the mount command & can probably shave more seconds off the sleep; when I had upgraded, I didn't need it at all. I personally prefer wicd to the traditional Slackware networking tools, not that I can't use them, but wicd just seems more intuitive, particularly for wireless.
Regards,
Bill
 
Old 12-14-2008, 05:01 PM   #6
mRgOBLIN
Slackware Contributor
 
Registered: Jun 2002
Location: New Zealand
Distribution: Slackware
Posts: 999

Rep: Reputation: 231Reputation: 231Reputation: 231
Put something like this in rc.local and you won't need to wait for a fixed time.
(replace the IP address with your gateway/router/NFS server address)

Code:
for dot in $(seq 10); do
        echo -n "."
        ping -c1 192.168.1.254 &>/dev/null
        exstat=$?
        if [ ${exstat} -eq 0 ]; then
                break
        fi
done

if [ ${exstat} -eq 0 ]; then
        echo " Network is up!"
        mount -a -v 2> /dev/null | grep -v "already mounted"
else
        echo " Network failed to connect!"
fi
 
Old 12-14-2008, 06:08 PM   #7
TSquaredF
Member
 
Registered: Dec 2005
Location: "The South Coast of Texas"
Distribution: Slackware64-current
Posts: 564

Original Poster
Rep: Reputation: Disabled
mRgOBLIN: Thanks for the script. I have one which tests whether the cifs share is mounted & warns me if not. I wasn't sure how to check the existence of the network, so just tested whether the share was in mtab. This will integrate into that script nicely & do both jobs. Thanks again.
Regards,
Bill
 
  


Reply



Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
WICD and WPA2 Supplicant Problems on Ubuntu 8.10 SaraiKhan Linux - Wireless Networking 2 12-07-2008 06:12 PM
Problems with WICD in XUbuntu Neej Suab Linux - Newbie 0 11-20-2007 08:41 PM
minor problems ahmed_alzahrani Linux From Scratch 2 09-05-2004 03:21 PM
A Few minor problems... fuelinjection Linux - General 1 06-10-2004 05:44 AM
Minor problems Gai-jin Linux - Newbie 4 01-07-2003 09:11 PM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware

All times are GMT -5. The time now is 07:54 PM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration