You are not logged in.
I think unless you want 'intelligent' decision-making on this, best to just let it fail. However, when it fails you should unmount the earlier points (/proc was not unmounted when it failed on /proc/bus/usb in my testing). Its Arch, let the user figure out what to do with it.
Allan-Volunteer on the (topic being discussed) mailn lists. You never get the people who matters attention on the forums.
jasonwryan-Installing Arch is a measure of your literacy. Maintaining Arch is a measure of your diligence. Contributing to Arch is a measure of your competence.
Griemak-Bleeding edge, not bleeding flat. Edge denotes falls will occur from time to time. Bring your own parachute.
Offline
However, when it fails you should unmount the earlier points.
The new daemon has a "umount" command, so the user can do that. I think it's safer than doing it automatically.
My Arch Linux Stuff • Forum Etiquette • Community Ethos - Arch is not for everyone
Offline
ngoonee wrote:However, when it fails you should unmount the earlier points.
The new daemon has a "umount" command, so the user can do that. I think it's safer than doing it automatically.
True, did not see that (haven't actually looked at anything new on it, or on mimeo/pbget). A warning may be nice, but would not have been necessary if I'd just thought a bit anyway. No big issue, as usual its mostly PEBKAC.
Allan-Volunteer on the (topic being discussed) mailn lists. You never get the people who matters attention on the forums.
jasonwryan-Installing Arch is a measure of your literacy. Maintaining Arch is a measure of your diligence. Contributing to Arch is a measure of your competence.
Griemak-Bleeding edge, not bleeding flat. Edge denotes falls will occur from time to time. Bring your own parachute.
Offline
Installed Arch i686 from my running x86_64.
arch32-light came in handy for that job, thanks xyne!
EDIT:
Also for a newcomer to multi-arch environment it's pretty cool to
Get the wanted AUR package's files in /tmp/builds/PACKAGE
[desktop] (ssh) # arch32 su USER -c "cd /tmp/builds/PACKAGE && makepkg -sr"
...
[desktop] (ssh) $ scp PACKAGE.tar.xz laptop:/path/to/mybuilds/
[laptop]~ $ sudo pacman -U PACKAGE.tar.xz
Just needed once for all:
[desktop] (ssh) # pacman32 -S base-devel
[desktop] (ssh) # vim /etc/arch32d.conf #adding /etc/pacman.d/mirrorlist
[desktop] (ssh) # arch32m sync
[desktop] (ssh) # pacman32 -S <PACKAGE dependancies>
Also did the following but looking at the man, looks it comes from old habits rather than being required to attain the goal above.
[desktop] # arch32
[desktop] # mv /etc/pacman.conf /etc/pacman.conf.SAV
[desktop] # ln -s /etc/pacman32.conf /etc/pacman.conf
[desktop] # pacman-key --init && pacman-key --populate && pacman -Syu
Oh, looks as if clean-chroot-manager automatises shared builds management well
Last edited by kozaki (2016-02-05 20:19:47)
Seeded last month: Arch 50 gig, derivatives 1 gig
Desktop @3.3GHz 8 gig RAM, linux-ck
laptop #1 Atom 2 gig RAM, Arch linux stock i686 (6H w/ 6yrs old battery ) #2: ARM Tegra K1, 4 gig RAM, ChrOS
Atom Z520 2 gig RAM, OMV (Debian 7) kernel 3.16 bpo on SDHC | PGP Key: 0xFF0157D9
Offline
When I start windowed applications with this (by sudo arch32 sudo -u username applicationname), I get squares instead of text/font in every application. Looks like this:
http://i.imgur.com/rYc1TER.png
[edit]solved by sudo pacman32 -S ttf-dejavu[/edit]
Last edited by Carl Karl (2016-07-13 17:58:58)
Offline