1
Show Posts
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
4
Update Notices / Re: /lib becomes a symlink
« on: July 15, 2012, 10:44:09 AM »
No problem, Repeat commands.
Note: http://archtr.org/forum/viewtopic.php?f=5&t=397#p3402
Code: [Select]
sudo pacman -Syu --ignore glibcCode: [Select]
sudo pacman -SuRebootNote: http://archtr.org/forum/viewtopic.php?f=5&t=397#p3402
8
Introductions / Re: Thanks so much you guys!
« on: June 09, 2012, 11:21:28 AM »
Welcome to the Bridge linux 
9
KDE / Re: Upgrade to kde 4.8.4 failed due two conflicting files.
« on: June 08, 2012, 12:20:08 PM »
Please, thanks.
10
KDE / Re: Upgrade to kde 4.8.4 failed due two conflicting files.
« on: June 08, 2012, 05:20:24 AM »11
Update Notices / Filesystem upgrade - manual intervention required
« on: June 07, 2012, 03:29:33 PM »
As of filesystem-2012.6-2 the folders /var/run and /var/lock will be replaced by symlinks to /run and /run/lock, respectively.
On most systems this is already the case, as initscripts create the symlinks on boot. However, these symlinks are not owned by any package, which is what we are fixing with this upgrade.
If the symlinks are already in place on your system (which should be the case for most people), then you can simply perform
Otherwise, if /var/run or /var/lock are directories (e.g. if you are using systemd and never booted with initscripts) you need to delete the directories before performing the update. As these directories are used at runtime, it is recommended to shutdown any background tasks before performing
Note: In general, it is strongly advised to avoid the --force switch as it is not safe. However, in this particular case it is safe, and suggested to avoid having to manually delete the /var/run or /var/lock symlinks.
Lastly, on upgrading filesystem users of kernels prior to linux-3.4 will get a warning about permissions on /sys. This is nothing to worry about, as of linux-3.4 the permissions will be 555, and this upgrade reflects this in the filesystem package.
http://www.archlinux.org/news/filesystem-upgrade-manual-intervention-required-1/
On most systems this is already the case, as initscripts create the symlinks on boot. However, these symlinks are not owned by any package, which is what we are fixing with this upgrade.
If the symlinks are already in place on your system (which should be the case for most people), then you can simply perform
Code: [Select]
# pacman -Syu --ignore filesystem && pacman -S filesystem --forceOtherwise, if /var/run or /var/lock are directories (e.g. if you are using systemd and never booted with initscripts) you need to delete the directories before performing the update. As these directories are used at runtime, it is recommended to shutdown any background tasks before performing
Code: [Select]
# rm -rf /var/run /var/lock && pacman -Syu && rebootNote: In general, it is strongly advised to avoid the --force switch as it is not safe. However, in this particular case it is safe, and suggested to avoid having to manually delete the /var/run or /var/lock symlinks.
Lastly, on upgrading filesystem users of kernels prior to linux-3.4 will get a warning about permissions on /sys. This is nothing to worry about, as of linux-3.4 the permissions will be 555, and this upgrade reflects this in the filesystem package.
http://www.archlinux.org/news/filesystem-upgrade-manual-intervention-required-1/
12
Installation / Re: login / password
« on: May 29, 2012, 05:34:06 AM »
May be useful in http://archtr.org/forum/viewtopic.php?f=62&t=3
13
General Discussion / How to Aur package installation?
« on: May 28, 2012, 10:56:45 AM »
Turn on the terminal:
edit pacman.conf
32
64
F3 the save F2 exit
update
after install yaourt
To install a package on Aur
Code: [Select]
pacman -S base-develedit pacman.conf
Code: [Select]
nano /etc/pacman.confAdd the bottom row32
Code: [Select]
[archlinuxfr]
Server = http://repo.archlinux.fr/i68664
Code: [Select]
64
[archlinuxfr]
Server = http://repo.archlinux.fr/x86_64F3 the save F2 exit
update
Code: [Select]
pacman -SyyCode: [Select]
pacman -Syuafter install yaourt
Code: [Select]
pacman -S yaourtTo install a package on Aur
Code: [Select]
yaouurt -S package name15
Announcements / Re: Announcing Bridge Linux 2012.5
« on: May 26, 2012, 03:03:42 AM »
Thanks @Ninja-1
announcement : http://archtr.org/forum/viewtopic.php?f=5&t=282
Gnome: http://sourceforge.net/projects/bridgelinux/files/GNOME/2012.5/
Kde : http://sourceforge.net/projects/bridgelinux/files/KDE/2012.5/
Light : http://sourceforge.net/projects/bridgelinux/files/Light/2012.5/
Xfce : http://sourceforge.net/projects/bridgelinux/files/Xfce/2012.5/
announcement : http://archtr.org/forum/viewtopic.php?f=5&t=282
Gnome: http://sourceforge.net/projects/bridgelinux/files/GNOME/2012.5/
Kde : http://sourceforge.net/projects/bridgelinux/files/KDE/2012.5/
Light : http://sourceforge.net/projects/bridgelinux/files/Light/2012.5/
Xfce : http://sourceforge.net/projects/bridgelinux/files/Xfce/2012.5/