Here’s what I did to fix auto-mounting, trash and authorization problems:
Install gvfs-afc (which added: gvfs, libsoup-gnome, libsoup, libproxy, gconf, orbit2, libcdio, libcddb, gnome-disk-utility, libunique, libgnome-keyring).
exec ck-launch-session dbus-launch openbox-session
dbus needs to be after consolekit to fix the authorization problems.
I installed Gnome-globalmenu. This litte gem acts like the top panel in OS X. So the menubar of the window that is active is showed in the top panel. But when you have a light colored panel, the white tekst is difficult to read.
Change the text color in Gnome-globalmenu:
GlobalMenu’s text is determined by your desktop theme. If you want to change it do the following:
- add this code to ~/.gtk-2.0
(note: ”~” is your home directory, and to be able to see .gtk-2.0 there you’ll need to press ctrl-h or select View -> Show Hidden Files)
fg[NORMAL] = "#000000"
widget_class "**" style "menu_item"
fg[NORMAL] = "#FFFFFF"
widget_class "**" style "menubar"
#FFFFFF is white, and is the colour that will be used for ”File Edit View…”
#000000 is black, and is what will be used in the drop down menus, eg. ”New Open Close Save…”
Change the colours to whatever you want. Just use 6 characters, where each character is one of ”0123456789ABCDEF”
The first pair of characters is for red, the second for green, and the third for blue.
Note: this will also change the menu clour in Firefox (which is not compatible with GlobalMenu) so you may want to change your firefox theme to suit (Tools -> Addons -> Themes in Firefox)
Thanks to Ayoli http://ubuntuforums.org/member.php?u=122327
for showing me how to do this
If anyone finds this helpful please thank him, not me.
I did a fresh install of Arch. Then installed several windowmanagers / DE’s. But it didnt’ matter which I choose, everytime I tried to mount a external storage device i.e. USB drive, hardrive, MMC card that horrible error popped up: Error mounting the device: Not authorized….
After hours digging in the forums I found the solution:
First, remove your “dbus-launch” and “ck-launch-session” calls in your .xinitrc. Then, in /etc/slim.conf, change “login_cmd” to this:
“login_cmd exec ck-launch-session /bin/bash -login ~/.xinitrc %session”
This circumvents the need for dbus-launch, and also makes sure that everything in .xinitrc is automatically in a ConsoleKit session. This is documented here. (https://wiki.archlinux.org/index.php/Slim#PolicyKit)
Install udisk and udiskie:
#yaourt -S udisk
#yaourt -S udiskie
A lot off times reading the forums, it get’s mentioned…. add [xxxx] to your daemons. Huh… daemons, what’s that?
Daemons are programs that are started and run in the background after you (re)boot your machine.
Where do i find daemons?
Edit the file “rc.conf” located in /etc :
# sudo nano /etc/rc.conf
I’ve got an old Dell laptop, which runs Arch, an Imac 20 inch and a LG DP1W mediaplayer and streamer. Now would it not be great if I could share file across all three machines? I’m gonna start with SAMBA and see how well this works. NFS will come later…
Ok, here we go.
Step 1. First thing to do is install the Samba client and server software on Arch.
# sudo pacman -S smbclient samba gamin
Gamin is a file and directory monitoring system defined to be a subset of the FAM (File Alteration Monitor) system. It is a service provided by a library which allows for the detection of modification to a file or directory. Gamin re-implements the FAM specification with inotify. It is newer and more actively maintained than FAM, maintains compatibility with FAM and can replace it in almost every case. It is a GNOME project, but does not have GNOME dependencies.
Step 2. Configure samba. As root, copy the default Samba configuration file to /etc/samba/smb.conf:
# cp /etc/samba/smb.conf.default /etc/samba/smb.conf
Then configure this file to your needs. By default the HOME user directories are shared.
Step 3. Add a user. To log into a Samba share you’ll need to add a user:
# smbpasswd -a <user>
Note that the user you add should be an existing user on the server side of Samba.
Step 4. Make Samba load at boot. Add the following to /etc/rc.conf to access the shares at boot:
# sudo nano /etc/rc.conf
Find the section that looks like and add smbnetfs and samba:
DAEMONS=(... smbnetfs samba )
That’s it! You should now be able to access your home folder from a another machine.
One of the things that annoyed me was having to enter my login and password at every boot. I use SLIM. Fortunately SLIM is very easy to setup to autologin a specific user.
Here’s how… :
To make SLiM automatically login as a specified user (without having to type a password) the following lines in /etc/slim.conf should be changed.
# default_user simone
Uncomment this line, and change “simone” to the user to be logged into automatically.
# auto_login no
Uncomment this line and change the ‘no’ to ‘yes’. This enables the auto login feature.
Source: Arch Wiki pages
I thought it would be nice if I could connect to Arch Linux through my Imac. Well OpenSSH is the way to do this fairy easy.
Here’s what I did to make the magic happen:
1. Install OpenSSH
sudo pacman -S openssh
2. To let other people ssh to your machine you need to adjust /etc/hosts.allow, add the following:
# let everyone connect to you (this is what I use, it maybe a security risk when one is a lot on a public internet connection)
# OR you can restrict it to a certain ip
# sshd: 192.168.0.1
# OR restrict for an IP range
# sshd: 10.0.0.0/255.255.255.0
# OR restrict for an IP match
# sshd: 192.168.1.
3. Optional, add sshd to the “DAEMONS” section of your /etc/rc.conf:
DAEMONS=(... ... sshd ... ...) 4.Dont forget to restart the daemon (as root):
# /etc/rc.d/sshd restart
That’s it! Now you should be possible to SSH into your Arch box through a client with the following commond (On OS X that is…)
ssh -l [username] [ip-adress]
Source: Arch Linux ArchWiki pages: https://wiki.archlinux.org/index.php/SSH
Well, be gentile here with me please…This is my first post ever on a blog
I recently started out using Arch Linux. Coming from Ubuntu I have some experience with the CLS but not that much. Reasons for using Arch for me are speed, flexibility, VERY well documented, good forums, and it runs very smooth on my old Dell C640 laptop.
I’ll be sharing my experiences here, as I hope to make some progress during my time using Arch.
Specs of the machinery are…:
Pentium IV 2.0 Mhz (wooohooo!)
512 MB RAM DDRI
1024 * 768 screen
1 USB I port