You are not logged in.
After these last days upgrade of ufw, my rules disappeared on my 3 computers with Archlinux.
Pacman log says it saved them as /lib/ufw/user.rules.pacsave. I recovered them by doing a:
mv /lib/ufw/user.rules.pacsave /usr/lib/ufw/user.rules
ufw reload
I don't understand why the maintainer chose to save configuration without moving this file to its new destination. I hope there is no problem to do as I did.
Last edited by jdn06 (2012-03-11 13:08:39)
Offline
Try to understand how pacman works.
If the package doesn't ship that file anymore and the file is in the 'backup' array, this is what is going to happen.
The configs have been moved to /usr/lib/ufw/user.rules:
http://projects.archlinux.org/svntogit/ … 9213d95504
Offline
Maybe it's part of the new Arch politic of moving /bin, /lib, /sbin under /usr...
Offline
Maybe it's part of the new Arch politic of moving /bin, /lib, /sbin under /usr...
Yup, but the .pacsave files work like this no matter the reason for the change see e.g. https://bbs.archlinux.org/viewtopic.php … 0#p1044870
Offline
Try to understand how pacman works.
If the package doesn't ship that file anymore and the file is in the 'backup' array, this is what is going to happen.
I don't agree with you. The message from the maintainer in pacman could be at least more precise by indicating where to put the new config file and by warning about unloading of all rules. On a distant server, this situation could be quite critical - I know, you don't use ufw on a distant server
Last edited by jdn06 (2012-03-11 13:09:33)
Offline
The thread I linked to suggested the need for a better maintainer - users communication too: https://bbs.archlinux.org/viewtopic.php?id=134045
Offline
Yup, but the .pacsave files work like this no matter the reason for the change see e.g. https://bbs.archlinux.org/viewtopic.php … 0#p1044870
Still, there are also *.install script which can help to workaround such a behaviour in cases like these. I guess majority wants to keep their rules.
P.S. I was quite surprised today when I could not ssh to by home box...
--
Milan Knizek
http://knizek.net
Offline
With my latest upgrade, the new libgl 'replaced' mach64-dri which gave me a blank screen and a non-responsive keyboard. Ufw also upgraded and I couldn't login with ssh. Took me some hours to get stuff working again.
We have a front page, please use it to warn your userbase about changes like this.
Offline