You are not logged in.
Pages: 1
I'm trying to install Adobe Acrobat Reader on my 64-bit system, but have run into a problem. I've installed a 32-bit chroot system, since the program is 32-bit only, and have downloaded the installer. When I use schroot -p AdbeRdr9.1.2-1_i486linux_enu.bin, it returns this error:
E: boost::filesystem::create_directory: No such file or directory: "/var/lib/schroot/mount/Arch32-78c64bc2-1bcd-4c7a-9359-dd8661dfaef4/opt/arch32/proc"
E: Arch32-78c64bc2-1bcd-4c7a-9359-dd8661dfaef4: Chroot setup failed: stage=setup-start
As far as I'm aware, my mount points in /etc/schroot/mount-arch32 are correct:
# mount.defaults: static file system information for chroots.
# Note that the mount point will be prefixed by the chroot path
# (CHROOT_PATH)
#
# <file system> <mount point> <type> <options> <dump> <pass>
proc /opt/arch32/proc proc defaults 0 0
/dev /opt/arch32/dev none rw,bind 0 0
#/dev/pts /dev/pts none rw,bind 0 0
tmpfs /opt/arch32/dev/shm tmpfs defaults 0 0
/sys /opt/arch32/sys none rw,bind 0 0
/tmp /opt/arch32/tmp none rw,bind 0 0
/home /opt/arch32/home none rw,bind 0 0
/var/lib/dbus /opt/arch32/var/lib/dbus none rw,bind 0 0
It seems like the installer is trying to create a directory for its files in the chroot system's /proc directory, but can't find or mount it?
Could anyone please shed some light into this? No amount of Google Fu was effective in destroying this error.
Last edited by samjh (2009-08-25 07:11:22)
Offline
When you use a chroot, you should just use pacman within the chroot to install. Its easiest that way.
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
Unfortunately, Acrobat reader is not in the Arch repositories, so I can't install it using pacman.
Offline
Why on earth would you want to use a pig of an application like Adobe Reader?
Ok...acroread is in community.
But I recommend using a better pdf reader like evince or epdfview.
Last edited by sand_man (2009-08-25 10:18:58)
Offline
+1 on epdfview or xpdf
I use both, epdfview seems to be a little faster at rendering which is nice if you want to just look at the text, but sometimes some images are not so good, thats when I turn to xpdf and all is well.
I can understand why someone wants to use acroread, it does a lot of things but it really is a pig of an application.
R00KIE
Tm90aGluZyB0byBzZWUgaGVyZSwgbW92ZSBhbG9uZy4K
Offline
Not to forget apvlv.
I even defined an alias for it:
alias PD='apvlv'
alias PDF='acroread'
Where acroread is a fallback only when the pdf structure appears to be too complicated. (Unfortunately there are cases which only acroread can handle. )
Last edited by bernarcher (2009-08-25 12:45:40)
To know or not to know ...
... the questions remain forever.
Offline
Sigh... I need a pdf reader that can print multiple pages per sheet, which neither evince or okular can do properly. My printer completely screws up N-up printing (both Windows and Linux), so any pdf reader which relies on the printer driver for n-up is no good for me.
If there are alternative applications that is as capable of n-up printing without dependence on the printer driver's n-up features, I'd be happy to try them. That excludes xpdf and okular, since both are dependent on n-up support from the driver. I think that also excludes epdfview.
Right now, I'm using Win7RC on VirtualBox to do n-up pdf printing, but it would be nicer to have a native Linux solution.
Last edited by samjh (2009-08-25 13:00:31)
Offline
Basically, go get the acroread PKGBUILD and build it in your chroot. I've been using that, works fine. Check out the wiki on 32-bit chroot, should have instructions for you.
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
Hi, any news on this topic? Today I followed same wiki page, I have mount-arch32 same as samjh above. The case is, I can chroot and already have installed what I needed inside and can run from chroot - anyway even even simple
schroot -p ls
also gives
E: boost::filesystem::create_directory: No such file or directory: "/var/lib/schroot/mount/Arch32-[id]/opt/arch32/proc"
E: Arch32-[id]: Chroot setup failed: stage=setup-start
I guess something isn't right with that mount-arch32? Wiki don't say it, but how should it look like? Or maybe problem is somewhere else?
My GPG fingerprint: 7170 26A9 D477 9FC5 3940 7266 40F5 57B7 3149 6106
Offline
Strange. i followed the wiki and have a working chroot for wine, google earth, skype, and acroread. Here's my mount-arch32
# <file system> <mount point> <type> <options> <dump> <pass>
/proc /proc proc defaults 0 0
/proc/bus/usb /proc/bus/usb none rw,bind 0 0
/dev /dev none rw,bind 0 0
/dev/pts /dev/pts none rw,bind 0 0
/dev/shm /dev/shm none rw,bind 0 0
/sys /sys none rw,bind 0 0
/tmp /tmp none rw,bind 0 0
/var/lib/dbus /var/lib/dbus none rw,bind 0 0
/var/abs/local /var/abs/local none rw,bind 0 0
/home /home none rw,bind 0 0
/home/data /home/data none rw,bind 0 0
The /dev/shm, /var/lib/dbus are for my pulseaudio. /var/abs/local is where I store my custom packages. /home/data is a separate partition mounted (for sharing with windows).
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
# mount.defaults: static file system information for chroots. # Note that the mount point will be prefixed by the chroot path # (CHROOT_PATH) # # <file system> <mount point> <type> <options> <dump> <pass> proc /opt/arch32/proc proc defaults 0 0 /dev /opt/arch32/dev none rw,bind 0 0 #/dev/pts /dev/pts none rw,bind 0 0 tmpfs /opt/arch32/dev/shm tmpfs defaults 0 0 /sys /opt/arch32/sys none rw,bind 0 0 /tmp /opt/arch32/tmp none rw,bind 0 0 /home /opt/arch32/home none rw,bind 0 0 /var/lib/dbus /opt/arch32/var/lib/dbus none rw,bind 0 0
Hey, just registered because I recently had the same headache and was able to solve it, and I figured I'd better help you out too Unfortunately, this is NOT correct, it looks correct and I made the same exact error but the "file system" and "mount points" must be switched. File system is the actual part of your HD that is being mounted and mount point is "where" it's mounted for schroot. Here's a fixed version:
# mount.defaults: static file system information for chroots.
# Note that the mount point will be prefixed by the chroot path
# (CHROOT_PATH)
#
# <file system> <mount point> <type> <options> <dump> <pass>
/opt/arch32/proc /proc proc defaults 0 0
/opt/arch32/dev /dev none rw,bind 0 0
#/dev/pts /dev/pts none rw,bind 0 0
/opt/arch32/dev/shm /tmpf tmpfs defaults 0 0
/opt/arch32/sys /sys none rw,bind 0 0
/opt/arch32/tmp /tmp none rw,bind 0 0
/opt/arch32/home /home none rw,bind 0 0
/opt/arch32/var/lib/dbus /var/lib/dbus none rw,bind 0 0
Hopefully this should fix your issue!(it worked for me in any case)
17:23 < ConSiGno> yeah baby I release the source code with your mom every night
17:24 < ConSiGno> you could call them nightly builds if you know what I mean
Offline
Hello!
I agree with bernarcher. Apvlv is very good for VIM fans.
Offline
Hey, just registered because I recently had the same headache and was able to solve it, and I figured I'd better help you out too Unfortunately, this is NOT correct, it looks correct and I made the same exact error but the "file system" and "mount points" must be switched. File system is the actual part of your HD that is being mounted and mount point is "where" it's mounted for schroot.
indeed, that was the reason - now it works like a charm, thank you!
My GPG fingerprint: 7170 26A9 D477 9FC5 3940 7266 40F5 57B7 3149 6106
Offline
Pages: 1