Ajitabh Pandey.Info

Last night installed Sabayon 5 amd64 on my laptop. All went fine except when I tried to do an update. I did the following as suggested in the Sabayon wiki:

$ sudo equo update
$ sudo equo update --force
$ sudo equo upgrade --ask

I was shown a long list of around 700+ packages which I started updating. After I was done, I executed the following and rebooted afterwards.

$ sudo equo conf update

Upon logging in to the newly updated system, I was surprised with ‘wicd’ asking me for a root password and then stating that its having a DBus error. So I connected the ethernet cable and a bit of search on the net (using Yahoo search engine) pointed me that I need to add wicd to startup at boot, which I achieved using the following:

$ sudo rc-update add wicd boot

I next rebooted, but still no joy. I was this time getting a message “BAD PASSWORD”. I was pretty sure that my password was correct. Again I spent some time on searching the internet using ethernet cable and finally found that a new version of knetworkmanager was in the entropy, so I decided to switch to it and remove the wicd.

$ sudo equo remove wicd
$ sudo equo install knetworkmanager

This was smooth and all started working well.

This does not mean that there is a problem with wicd. There are lots of people who had problem with knetworkmanager and have switched to wicd. This is the prime reason that sabayon guys have perhaps included wicd into the distribution. But the point which I am not able to understand is that why they changed my functional knetworkmanager during update to wicd?

Anyways, all izz well that ends well. I am writing this post from wire.

Oh!! and I have not rebooted yet. Ok let me reboot after this post and see if all remains well or not. Obviously you will see something either here or on twitter if all is not well.

Share/Save

I recently activated quota on my slicehost slice and it was quite simple and fast to do. The only disadvantage is that I needed to set quota on the only filesystem I had, which is /. If there is a choice then it is advisable to set quota on non-root filesystem such as /home, /var etc. The primary reason for this is that while performing the quota check the filesystem needs to be mounted read-only temporarily by the quotacheck utility. Since the root filesystem can not be mounted read-only while the system is running we need to do a force quota check on the system which might result in in-accurate figures and can cause corruption to the quota files.

Here are the commands which I executed in quick succession to enable the quota:

$ sudo modprobe quota_v2
$ sudo lsmod|grep quota
quota_v2               11392  0
$ sudo mount -o remount,noatime,usrquota,grpquota /

The following command will create the quota files and the -m option is to force the execution as the filesystem can not be mounted read-only.

$ sudo quotacheck -cugm /

Now to calculate the current usage,

$ sudo quotacheck -avugm
quotacheck: Scanning /dev/sda1 [/] done
quotacheck: Checked 8990 directories and 87482 files

Now to set the quota for user testuser we can use setquota. Following command set the quota to 1GB.

$ sudo setquota -u testuser 1000000 1048576 0 0 -a

Share/Save