X-systemd.automount and sshfs

I've been using sshfs to access files on my pi for serveral months now. Today i tried to enable automatic mounting with x-systemd.automount, but although a manual mount is still possible, the automatic mount fails constantly with a "no such device" error since i added the additional option in /etc/fstab. Journalctl -f on the pi reveals that the "Connection is closed [preauth]", so I would guess that something is wrong with my client authenticating. But I don't understand how is this possible because I can in fact mount the partition manually. Even if I use the exact command used by systemd (found via ps -fe) with root it prompts me for the password of my key and then it mounts correctly. Shouldn't automount then prompt for my password, when my X starts? Any ideas?
line in /etc/fstab:
herrzinter-pi.local:/media/mediacrypt /home/herrzinter/Multimedia fuse.sshfs users,noauto,_netdev,reconnect,x-systemd.automount 0 0
Last edited by MrTea (2013-07-01 15:34:13)

WonderWoofy is right, until now I always used the automatically generated nautilus entry to mount the remote folder. In this case mount command is executed as <user> and so I don't need to put the additional information in the /etc/fstab. btw i didn't exactly look this up, but I've used this setup for quiet some time now, and I guess, that I forgot the herrzinter@ part once and noted that it worked anyway
I now added this and the "IdentityFile=/..." option pointing to a dummy ssh key without passphrase and it then it's working, but I am not to happy with this, as an empty passphare key is not really nice, and also nautilus is showing me duplicated entries... but in genreal I have to look at the setup again I am not sure anymore if the x-systemd.automount option is really such a good idea in my case, as the network setup of my laptop is changing quite often... perhaps a bash script at login, or a custom systemd unit is better suited for my purpose
Thank you all anyway

Similar Messages

[SOLVED] Systemd and Sshfs Automount

Hi,
I'm trying to set up automount on an sshfs drive. From other posts I already concluded this line for my /etc/fstab:
[email protected]:/users/schnitzl /home/ben/data/mnt/uni/ fuse.sshfs noauto,x-systemd.automount,users,idmap=user,IdentityFile=/home/ben/.ssh/id_rsa,allow_other,reconnect 0 0
But yet it does not work. Whilst logging into the remote Host from command line is no problem:
ssh [email protected],
automounting fails:
-- cd uni/
bash: cd: uni/: No such device.
journalctl -b | grep uni tells me:
Nov 15 16:31:31 mario systemd[1]: Mounting /home/ben/data/mnt/uni...
Nov 15 16:31:31 mario systemd[1]: Mounted /home/ben/data/mnt/uni.
Nov 15 16:31:31 mario systemd[1]: home-ben-data-mnt-uni.mount mount process exited, code=exited status=1
Nov 15 16:31:31 mario systemd[1]: Unit home-ben-data-mnt-uni.mount entered failed state.
Any Ideas?
Benjamin
Edit: Which services do I have to restart, in order to let systemd reload the /etc/fstab configuartion?
Last edited by Lord Bo (2012-11-15 17:06:55)

Thank you very much! That was the right option! I already had it there, but as it did not work yet, I altered the line and forgot to add this option... . However: one last thing: Which services do I have to restart, after having altered /etc/fstab in order to take changes into effect? It is a bit annoying always having to restart the whole system.
Edit:
teekay wrote:EDIT: sorry, I oversaw the noauto. So you want on-demand, right? https://bbs.archlinux.org/viewtopic.php?id=146674
Well it is now mounted on demand (as soon, as I try to access the directory).
And the link you provided: I already found that during my researches, but the crucial point was, as you mentioned, the missing _netdev option. However: Thanks again .
Last edited by Lord Bo (2012-11-15 16:54:52)

X-systemd.automount nfs drive

Hi,
I can't seem to get systemd.automount to behave. I have an nfs share available on machine 'kombi' and am trying to access it from machine 'forrest':
[root@forrest ~]# showmount -e kombi
Export list for kombi:
/mnt/nfs4/georgia 192.168.1.202
/mnt/nfs4 192.168.1.202
It is set up to automount in /etc/fstab:
kombi:/georgia /mnt/georgia nfs4 rw,suid,dev,exec,noauto,nouser,async,clientaddr=192.168.1.202,_netdev,x-systemd.automount,x-systemd.device-timeout=8 0 0
Logging output from journalctl indicates it timed out but then mounted:
Dec 14 17:45:11 forrest systemd[1]: mnt-georgia.mount mounting timed out. Stopping.
Dec 14 17:45:11 forrest systemd[1]: Mounted /mnt/georgia.
Dec 14 17:45:11 forrest systemd[1]: Mounted /mnt/georgia.
However it is not mounted. Any process trying to access /mnt/georgia hangs.
Any ideas where I have gone wrong? I don't care if it automounts at boot or at first access. What I'd like is for it to gracefully handle mounting when 'kombi' is up, and unmounting when 'kombi' is down.

Thanks, I guess I have misread other advice on the forums. Even systemd.mount man page states:
If x-systemd.device-timeout= is specified it may be used to configure how long systemd should wait for a device to show up before giving up on an entry from /etc/fstab.
From this statement I would expect the remote filesystem to not be mounted if the other machine is down, but not to cause a local process to hang trying to access the unmounted directory.
It looks like autofs may be the way to go - from the NFS wiki:
Using autofs is useful when multiple machines want to connect via NFS; they could both be clients as well as servers. The reason this method is preferable over the earlier one is that if the server is switched off, the client will not throw errors about being unable to find NFS shares.

Can systemd automounter unmount inactive fileystems?

Hi,
tl;dr: Can systemd automounter unmount fileystems after a period of inactivity, like autofs does?
I've just started discovering the wonderful new world of systemd, and to my great joy I found that it contains an automounter, so I thought that I would be able to use that instead of using autofs.
The single thing that I like to automount is my home NAS on my laptop (via NFSv4) that I every day take from home to work and then back home.
To do this with autofs is kind of like killing mosquitoes with a flamethrower. I would much rather just have my automounted NAS defined in my fstab than having to force the slightly mysterious autofs.xxx-files to mount the drive with the options I want it to use.
So, I got systemd to automount my NAS and all was joy! Until I realized that it wasnt unmounting it after a time of non-use. I have googled quite a bit, searched the forums, but have found no mention that systemd either has or doesnt have this kind of functionality.
So my purpose with this post is to get a definitive answer, does systemd do this? And if it doesn't, maybe others searching for the same information will end up here, and find the answer...
/DonO

I've been having this problem for as long as I can remember. I have finally decided to sit down and work something out instead of my laptop hanging all the time when it can't find the nfs server. The systemd.automount feature is nice, but it really sucks that it does not auto unmount when the share is not found.
Also, having systemd.automount means that every time I open vim, or a manpage, and there is no network connection, systemd tries to mount the shares. I'm not sure why because I am not directly accessing them. Everything loads slowly when systemd automount is active for my shares and there is no network connection.
Using soft instead of hard is a workaround, but then when the network connection is lost, corruption can occur.
It seems like the only way to really solve this problem is to have some kind of script run when the network comes up to mount the shares, and to unmount when it goes down. This would require custom systemd units or something. Diving into the systemd manuals is something I have been putting off because they are so hefty.
For anyone that is interested, here is my fstab:
lithium:/mnt/data /mnt/data nfs noauto,noatime,rsize=32768,wsize=32768,soft,retry=0,timeo=3,x-systemd.automount,x-systemd.device-timeout=1ms 0 0
lithium:/var/cache/pacman /var/cache/pacman nfs noauto,noatime,rsize=32768,wsize=32768,soft,retry=0,timeo=3,x-systemd.automount,x-systemd.device-timeout=1ms 0 0
Last edited by demizer (2013-07-14 09:00:23)

[solved] systemd-journal and shadow.pacnew updates

After a recent install and update I have come across the same issue described here where the user was recommended to ignore and erase some .pacnew files. My update generated the following:
/etc/dhcpcd.conf.pacnew
/etc/group.pacnew
/etc/passwd.pacnew
/etc/shadow.pacnew
/etc/gshadow.pacnew
The first, dhcpcd, seemed sensible enough and I incorporated the changes. The latter four all share the following characteristics:
1. Removed mentions of systemd-journal-remote and systemd-journal-upload. I'm not sure why so I left those records in place.
2. Changed a few permissions here or there, which i incorporated into /etc/group and /etc/password.
3. Changed the default shell for a few users; these changes I incorporated.
I was unable to open /etc/shadow or /etc/gshadow in write mode so I've left these files. Perhaps that's fine because the thread mentioned above says so. However, there's no explanation of why or where this information was obtained (or ordained!)
Is it fine to leave these two files? Why have syssystemd-journal-remote and systemd-journal-upload been omitted?
Last edited by Deau (2014-08-29 06:54:18)

The steps you took look quite sane to me.
These groups are not in the defaults provided by filesystem (e.g. I don't have them). see the edit
Apparently systemd creates system groups and users on it's own, see 'man systemd-sysusers'. Do you know / can figure out why these groups are created in the first place ? not important in this case, see the edit as well
FYI e.g.: https://bugs.archlinux.org/task/41717
The filesystem package provides those files as defaults (group, passwd, shadow, gshadow amongst otheres). However there are some packages that actually add additional groups they need (like ntp e.g.). The filesystem package cannot know about these. Therefor it's likely to have more groups in your local installation than in the .pacnew files you get.
The same applies for manually created users and groups of course.
If needed see the man pages for explanations of the respective files (e.g. 'man group').
Edit: Ok, I see that after an update I have them as well, so these are apparently new systemd groups and users. I think the rest I said above is still valid, so leaving those in place was the right thing to do.
Last edited by rebootl (2014-08-28 20:46:43)

Automounter and volume manager based on DevKit

Hi there,
I've written a simple automounter and volume manager based on DeviceKit:
http://www.ashrentum.net/jmcejuela/prog … 0.2.tar.gz
Some may find it interesting.
Currently it only manages media drives. I hasn't support yet for CDs/DVDs.

jmcejuela wrote:
Hi there,
I've written a simple automounter and volume manager based on DeviceKit:
http://www.ashrentum.net/jmcejuela/prog … 0.2.tar.gz
Some may find it interesting.
Currently it only manages media drives. I hasn't support yet for CDs/DVDs.
Hello, good job!
I was thinking of writing a patch for skvm to use DeviceKit. How does DeviceKit compare to HAL? any obvious deficiencies or whatnot? I've not looked into this at all yet. I'll look into the code to see if I can get any ideas

Automount and Rebooting

Hi
I heard now desktop based automounts doesnt work. I installed gvfs to mount my drives with xfce. I recently updated my system .
Now it gives "Not authorized to perform operation." error.
I also can't reboot and shutdown with xfce it just logs out to slim with these buttons .
How can I make automounting and the powermanager work again ?

1. Read the wiki
2. Stop crossposting

Systemd automount luks partition in background

A bit of a technical story for systemd experts.
Systemd causes a few seconds delay on boot when it automounts all fstab entries and one of those entries is an encrypted volume. The problem is when I mount a data partition which is really not important, i.e. it can wait until the system is completely booted. I can fix this by using noauto in crypttab and fstab or I can use a rc.local script to mount the partition manually. But how can I tell systemd this partition is not important and mounting this partition should never delay booting? Is it even possible with systemd?
/etc/crypttab:
data /dev/... /root/data.key
/etc/fstab
/dev/mapper/data /mnt/data ext4 rw,relatime 0 0

Thanks aesiris, I've tried this but it's the same. When I don't mount the encrypted data partition on boot the system goes from text mode to X within 2 seconds. If I do mount the data partition the console goes from text mode to framebuffer (not sure how to call it but when you got a higher resolution text console) and then to X. Guess what I want is not possible with systemd.

Systemd automount of /home results in locate ignoring /home

Hi,
Per the suggestion on the systemd wiki page, I have instructed systemd (via /etc/fstab) to automount /home. This is supposed to allow me to boot faster on those occasions when my /home needs to be fsck'ed. (Please correct me if I've misunderstood this point.) This results in "mount" reporting that my /home filesystem type is "autofs".
This again results in locate ignoring my entire /home when indexing my harddisk, since the default /etc/updatedb.conf has PRUNEFS="(...) autofs (...)", i.e. it ignores all autofs filesystems. Now, I don't want to remove autofs from this list, since other filesystems that should be ignored (e.g. /proc/sys/fs/binfmt_misc) are of autofs type. I also would prefer to keep the automount trick from the wiki.
Any suggestions as to how this can be accomplished? I have RTFM for updatedb.conf, and it does not have a "whitelist" of any sort. That would be the optimal solution, IMO, but requires an update from the mlocate maintainer upstream. Can I tell systemd to fake the filesystem type of home, or to pass on the actual filesystem type (ext4)?

Here is another discussion of this issue: https://bbs.archlinux.org/viewtopic.php?id=154539
Apparently the time savings provided by automounting /home may not be not significant enough to make it worthwhile. You can test this yourself, or continue with the other workarounds you are already aware of.

[SOLVED] systemd, autofs and lxdm

OK, after recently migrating rc.conf to the more 'systemd' structure, but still using init I figured I'd give systemd another shot, and herein lies my problem.
According to the wiki there should already be units available for various DMs, though i only have xdm available. I've copied and modified the copied version for lxdm (well, not strictly correctly, I've modified it to start xfce the same way that my "old" style does, with ck-launch) but I just get dumped to a root desktop (which I can't log out of). What I want is the lxdm login. I'm pretty sure there's a bunch of stuff I've forgotten since I set this up, so how do I get systemd to launch lxdm to a login screen.
Second. I'm getting autofs errors at boot, and automounting isn't available.
Google has helped me not one jot (either lousy googling or lousy forum thread titles, not sure which) and I need to fix this too.
Not looking for a verbatim answer. Rather looking for links where I can get the why's and wherefore's. The Arch systemd wiki doesn't cover this (it assumed units present which are not).
I've installed the arch units already. Any pointers would be appreciated.
Last edited by Roken (2012-07-28 22:25:06)

lxdm package from Community contains usr/lib/systemd/system/lxdm.service
please check with
pacman -Ql lxdm
But if you can't
systemctl enable lxdm.service
you can try manually symlink it
ln -s '/usr/lib/systemd/system/lxdm.service' '/etc/systemd/system/display-manager.service'
btw. in AUR pkgbuilds there are no lxdm.service at the moment, so you neet to copy it from community source files (best way)
Last edited by nbvcxz (2012-07-26 11:28:11)

No automount and no wpa wireless after migrating to openbox

I've just tried openbox after I removed kde.(everything was fine there)
now both pcmanfm and thunar are not able to see the removable devices and the devices are not even mounted in the /media. so I think maybe the problem is with systemd-logind
I also cannot use wpa/wpa2 encryptions for accessing wireless, using nm-applet
the networkmanager, wpa_supplicant services are all enabled and active however the udisks service is not.
I saw in the wiki the output of the command " loginctl show-session $XDG_SESSION_ID " must have "Active=yes" in it but I haven't such an output.
I'm completely confused by all these Consolekit/logind things and I don't know what exactly should I ask here and what information is relevant so if you think that I have to add something to the question please let me know.
Last edited by amiragha (2012-11-20 19:18:56)

hi, openbox doesn't manage automounts that is a feature for a lightweight desktop, not a bug. However you can use udiskie (pacman -S udiskie) to manage automount, just install it and put udiskie & at the end of your $HOME/.config/openbox/autostart
Consolekit is not needed any more

GNOME 3.4 changing remembered automount and display settings

Here's an interesting observation.
My setup is the following: notebook computer + external display.
2 user accounts A and B and I'm using GNOME 3.4 in fall-back mode.
I think it's important to know, account A was created before I bought external display and started using it as a main one. Account B was created when I already used external display.
So, I use only external display at 1920x1200 resolution:
xrandr
Screen 0: minimum 320 x 200, current 1920 x 1200, maximum 8192 x 8192
VGA-0 connected 1920x1200+0+0 (normal left inverted right x axis y axis) 518mm x 324mm
1920x1200 60.0*+
1920x1080 60.0
1600x1200 60.0
1680x1050 60.0
1280x1024 60.0
1280x960 60.0
1024x768 60.0
800x600 60.3
640x480 60.0
720x400 70.1
LVDS connected (normal left inverted right x axis y axis)
1280x800 60.0 +
1280x720 59.9
1152x768 59.8
1024x768 59.9
800x600 59.9
848x480 59.7
720x480 59.7
640x480 59.4
I also have a bunch of external USB drives connected to this notebook computer and they get automounted with the help of udisks2 helper:
mount |grep udis
/dev/sdb1 on /run/media/A/9d244934-d9fa-4a8e-8dd7-5c595f5518cf type ext2 (rw,nosuid,nodev,relatime,uhelper=udisks2)
So, I boot my Arch Linux, external display is connected and notebook is configured (by clicking Fn+Display key to choose to output video signal to external display only), I see GDM. So far so good, only external display is used, choosing automatically correct native resolution of 1920x1200.
I enter user account password in GDM, GNOME starts loading.
What happens for user A is that:
- notebook's display gets lit up, showing video output in its native resolution of 1280x800
- external display duplicates the video output apparently in this 1280x800 resolution (because the image is kind of zoomed and unscaled, blurred: because it's not a native resolution)
- I have to click Fn+Display key to switch available modes and choose one when only external display is used. When it's done, native resolution of 1920x1200 is chosen for external display and all is good.
However, when I resume from sleep notebook when logged in as user A, even though the external display is used in native resolution, just as it's supposed to be, I can see that notebook's screen is glowing, but not showing any video output. I need then to turn off power for it pushing Fn+Sun (an icon depicting sun with one half filled, and the other empty signifying on/off modes) .
The USB disks. When GNOME is loaded for user A I can see in Places my drives, but I have to manually click them to get them mounted. When resuming from sleep, I have to do it again. They're automatically detected, but aren't mounted.
All of that shouldn't be normally happening. Why?
Because for user B none of that is true.
External display works as expected on GNOME's start, when resuming from sleep under user B notebook's screen never isn't glowing. USB disks are automounted when user session is loaded, or OS is resumed from sleep.
Obviously, I want the same for user A. But there aren't really any settings to tweak, at least none that I know of or could find myself.
It would seem that something like session settings are different for these two user accounts, but I know really little about session management in GNOME. Might be something else.
I would appreciate it if you shared your insights or ideas as to how to make user A GNOME session to behave much like user B's in respect to displays and mounting of external USB drives.
Last edited by xCrucialDudex (2012-10-13 07:56:41)

I have the same problem as you. I can't access the system settings nor the online accounts thing. I guess we will have to wait till the next patch or something. Here is the bug report.

Systemd: Suspend and Hibernate not working

Hi,
When I try to hibernate my Notebook using systemd with 'systemctl hibernate', it sometimes (from time to time it even works) fails with the error message "a dependency job for hibernate.target failed". In the journal I see the following:
The system clock has been changed to REALTIME microseconds after January 1st, 1970.
Jun 04 23:52:57 localhost systemd[1]: systemd-hibernate.service: main process exited, code=exited, status=1/FAILURE
Jun 04 23:52:57 localhost systemd[1]: Failed to start Hibernate.
-- Subject: Unit systemd-hibernate.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/li … temd-devel
-- Unit systemd-hibernate.service has failed.
-- The result is failed.
Jun 04 23:52:57 localhost systemd[1]: Dependency failed for Hibernate.
-- Subject: Unit hibernate.target has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/li … temd-devel
-- Unit hibernate.target has failed.
-- The result is dependency.
Jun 04 23:52:57 localhost systemd[1]: Service sleep.target is not needed anymore. Stopping.
Jun 04 23:52:57 localhost systemd[1]: Unit systemd-hibernate.service entered failed state.
Jun 04 23:52:57 localhost systemd[1]: Stopping Sleep.
-- Subject: Unit sleep.target has begun shutting down
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/li … temd-devel
-- Unit sleep.target has begun shutting down.
Jun 04 23:52:57 localhost systemd[1]: Stopped target Sleep.
-- Subject: Unit sleep.target has finished shutting down
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/li … temd-devel
-- Unit sleep.target has finished shutting down.
:x
Any ideas? Furthermore, during hibernate (when it works) my screen first gets black, the system comes back and only then it really hibernates.
Others suggest switching to linux-lts. Does that really make sense? Isn't this a systemd issue?
suspend sometimes fails to work either (screen gets blank, but system weaks up after a few seconds again):
Jun 05 06:59:14 localhost systemd[1]: Stopping Sleep.
-- Subject: Unit sleep.target has begun shutting down
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/li … temd-devel
-- Unit sleep.target has begun shutting down.
Jun 05 06:59:14 localhost systemd[1]: Stopped target Sleep.
-- Subject: Unit sleep.target has finished shutting down
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/li … temd-devel
-- Unit sleep.target has finished shutting down.
Jun 05 06:59:14 localhost systemd[1]: Reached target Suspend.
-- Subject: Unit suspend.target has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/li … temd-devel
-- Unit suspend.target has finished starting up.
-- The start-up result is done.
Thanks,
Michael

Thanks, but I do not call systemd-sleep manually, I just do the ordinary "systemctl hibernate".
Unfortunately, the error "A dependency job for hibernate.target failed. See 'journalctl -xn' for details" just happened again. Alas, I'm not able to debug it according to the manual (https://wiki.archlinux.org/index.php/sy … emd_errors). When I try to get the log messages for the PID that causes hibernate.service to fail, I don't see anything suspicious in the logs:
$ sudo systemctl status systemd-hibernate.service
systemd-hibernate.service - Hibernate
Loaded: loaded (/usr/lib/systemd/system/systemd-hibernate.service; static)
Active: failed (Result: exit-code) since Fri 2014-06-13 14:32:52 CEST; 12min ago
Docs: man:systemd-suspend.service(8)
Process: 26712 ExecStart=/usr/lib/systemd/systemd-sleep hibernate (code=exited, status=1/FAILURE)
Main PID: 26712 (code=exited, status=1/FAILURE)
Jun 13 14:32:37 localhost systemd[1]: Starting Hibernate...
Jun 13 14:32:37 localhost systemd-sleep[26712]: Suspending system...
Jun 13 14:32:52 localhost systemd[1]: systemd-hibernate.service: main process exited, code=exited, status=1/FAILURE
Jun 13 14:32:52 localhost systemd[1]: Failed to start Hibernate.
Jun 13 14:32:52 localhost systemd[1]: Unit systemd-hibernate.service entered failed state.
$ sudo journalctl -b _PID=XXXX
-- Logs begin at Thu 2013-09-26 16:12:25 CEST, end at Fri 2014-06-13 14:43:40 CEST. --
Jun 13 14:32:37 localhost systemd-sleep[26712]: Suspending system...
Any ideas?

How does systemd, wpa_supplicant, and dhcpcd work together? rtl8188su

I'm running arch with alarm (done a pacman -Syu to get latest everything) on an original Raspberry Pi model B.
I'm using a Belkin USB adapter which is really a Realtek rtl8188su chip, which is recognized with the r8712u module. I want to do it all from the command line (not running a GUI, as this Pi won't be having a display attached.)
The system recognizes the built-in Ethernet, and dhcpcd assigns it an IP address, so I can SSH into it and try to bring up the wlan0 interface.
I'm an old-school Linux/UNIX hacker, but I haven't had a lot of experience with systemd, nor with wpa_supplicant or even much of udev, so I'm a bit lost in trying to make this work.
I made sure wpa_supplicant and wpa_cli were installed. Then I edited /etc/wpa_supplicant/wpa_supplicant.conf to add my ssid/passphrase, and saved it as /etc/wpa_supplicant/wpa_supplicant.wlan0.conf. I also did "systemctl enable wpa_supplicant," and I've rebooted.
The status of the system is that it does not enable the wlan0 interface. Further, the wpa_cli tool does not work. If I run just "wpa_cli" or with a command like "wpa_cli list" then I get the error:
could not connect to wpa_supplicant - wpa_ctrl_open: No such file or directory
This is weird, because wpa_supplicant is running in dbus listen mode:
[root@alarmpi ~]# ps alx | grep [w]pa
0 0 94 1 20 0 5636 1416 poll_s Ss ? 0:00 /usr/sbin//wpa_supplicant -u
Each time I boot, I get this message in /dev/log/messages.log:
Nov 10 01:40:06 alarmpi kernel: [ 648.082619] ADDRCONF(NETDEV_UP): wlan0: link is not ready
Now, if I insted does "systemctp stop wpa_supplicant" and start it manually, it does bring up the interface:
[root@alarmpi ~]# wpa_supplicant -i wlan0 -D wext -c /etc/wpa_supplicant/wpa_supplicant.wlan0.conf
wlan0: Trying to associate with a0:21:b7:63:a1:98 (SSID='jwatte' freq=2462 MHz)
wlan0: Associated with a0:21:b7:63:a1:98
wlan0: WPA: Key negotiation completed with a0:21:b7:63:a1:98 [PTK=CCMP GTK=CCMP]
wlan0: CTRL-EVENT-CONNECTED - Connection to a0:21:b7:63:a1:98 completed (auth) [id=0 id_str=]
[root@alarmpi ~]# ifconfig wlan0
wlan0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet6 fe80::a86:3bff:feb4:c21a prefixlen 64 scopeid 0x20<link>
ether 08:86:3b:b4:c2:1a txqueuelen 1000 (Ethernet)
RX packets 30 bytes 3813 (3.7 KiB)
RX errors 0 dropped 1 overruns 0 frame 0
TX packets 5 bytes 610 (610.0 B)
TX errors 0 dropped 1 overruns 0 carrier 0 collisions 0
[root@alarmpi ~]#
However, dhcpcd is not auto-launched to provide an IP address to the interface.
So, how is this supposed to work? How am I supposed to configure the system so that all the pieces click together? It should start wpa_supplicant with the right config data, and/or configure it over dbus correctly, and it should make sure dhcpcd is then invoked to obtain an IP address. I have *no idea* how to actually configure this to do the right thing, because all the tutorials and documentation I can find on the web is either very abstract ("services live in /usr/lib/systemd/...") or just claim that things "will magically work" if I have the correct configuration.
Help! Don't know what to do next!

Your manual wpa_supplicant invocation result looks good, so the major hurdle you have taken already.
For wireless you need a management method that acts as interface to wpa_supplicant and dhcp and watches the connection. Before you browse off to archlinuxarm, also read the non-abstract introduction here: https://wiki.archlinux.org/index.php/Wi … management

Gnome automount and media.repo under Oracle Linux 6.3

Hello,
I experiencing a strange behavior testing the following under Oracle Linux 6.3 (x86-64-bit) UEK2 with all latest updates. I selected the Gnome desktop packages using the "customize now" ratio button when installing the OS
* Log in to a graphical shell such as GNOME
* Insert addition media disk into the computer
* Observe the media is mounted by the session
* Wait a couple of seconds
* Observe the /etc/yum.repos.d/packagekit-media.repo now exists
The above is explained in more details at http://people.redhat.com/rhughes/media-repo.txt
I don't know what the "addition media disk" is, but inserted the Oracle Linux 6.3 x86_64 binary distribution DVD, which also has media.repo file in the root directory. And btw, I'm using VirtualBox and the DVD is an .iso disk image.
I'm experiencing the following:
Gnome automount works and automatically opens the DVD when inserted.
It does not create the /etc/yum.repos.d/packagekit-media.repo file.
It actually does create the named repo file, but only after one waits about 15 minutes. Perhaps this has anything to do with gpk-update-icon, but when run manually it hangs.
With the packagekit-media.repo file finally created. The gpk-application however complains: "The group list was invalid".
I know how to create a yum configuration file pointing to a local repository, which is also coverd in the Oracle Linux 6.3 distribution readme. I just wonder about the problem. Th automatic business with the media.repo file seems broken and useless. I did one more test using the original RHEL kernel which, as expected, did not make a difference.
Does anyone know more about it?
Thanks!

I cannot create an SR, but I did some more tests creating my own DVD, playing with the info in the media.repo file. It seems matching the mediaid and .discinfo information alone doesn't fix it.
Actually some of the stuff is explained in the link I already used: http://people.redhat.com/rhughes/media-repo.txt. The problem seems that it doesn't work as advertised.
It takes exactly 15 min. before the system (gnome) automatically copies the media.repo file from DVD to /etc/packagekit-media.repo. If the file already exists it gets overwritten.
I think it might be a good idea to make an entry in the media.repo file on the DVD, such as:
baseurl=file:///media/<disklabel>
skip_if_unavailable=True
Then when inserting the DVD under gnome it would not be necessary to create a yum repository configuration file to use the DVD. The 15 min. delay will have to be fixed, which is only supposed to take a couple of seconds.
Edited by: Dude on Aug 27, 2012 5:51 PM

X-systemd.automount and sshfs

Similar Messages

Maybe you are looking for