linuxとかテストとか

some notes about fedora 18

fedora | 20:44

I installed fedora 18 Beta TC4 LXDE spin today. That works fine for me :) So I am running it on my daily used desktop.

However I needed to some search to use it as I did with fedora 17. This is my memo but I hope it'll help someone.

To enable sysrq

I usually enable sysrq feature so I tried to modify /etc/sysctl.conf but there is no such file in /etc. I checked fedora 17 and did "rpm -qf /etc/sysctl.conf" then I got the answer. This file is provided by initscripts package. That seems as if Fedora 17's initscripts package gives it but Fedora 18's is not.

I thought specification has changed. Therefore I check .spec file then I found the answer in its changelog. It says "move default sysctl.conf to /usr/lib/sysctl.d (#760254)" .I checked that directory and found "00-system.conf" that was the file I was looking for. So I could enable sysrq from file.

Running google-chrome

I use Google Chrome as default browser for linux, mac, and windows. Of course I installed it but it didn't work on fedora 18.

When I started chrome from terminal I got following message.

/bin/google-chrome: error while loading shared libraries: libudev.so.0: cannot open shared object file: No such file or directory

That is easy to understand :) I have installed /usr/lib64/libudev.so.1.1.5 instead of libudev.so.0. so I created a symbolic link then chrome works fine.

btw, libudev provides libudev.so.0 file on Fedora 17. However, systemd-libs provides libudev.so.1 on Fedora 18.

ssh

If you run sshd on your Fedora 18 machine, and ssh client gets this error, you may need to check your selinux policy.

Permission denied (publickey,gssapi-keyex,gssapi-with-mic).

If you run desktop, you can see sealert icon on your desktop panel or somewhare in your desktop. Or you can check /var/log/messages.

Anyway, I found this line in /var/log/messages.

Oct 14 13:33:55 saga setroubleshoot: SELinux is preventing /usr/sbin/sshd from search access on the directory .ssh. For complete SELinux messages. run sealert -l 4e85c433-8d6d-4b63-8afe-9d3927b088e9

So I followed this instruction. Actually I had some alerts so that I ran sealert command some times but I was able to solve ssh connection problem :)

# Of course if your .ssh or file permission is wrong, you cannot access to your ssh host.

ツイートする