On Monday, April 13, 2015 02:28:00 PM Francis Gerund wrote:
When I do:
file
/run/media/default/USBHD005/New_stuff/Archlinux/archlinux-2015.04.01-dual.is
o
I get:
archlinux-2015.04.01-dual.iso: # ISO 9660 CD-ROM filesystem data
'ARCH_201504 ' (bootable)
On
Forgot to say, I tried again, using a different 64-bit computer.
Same exact results!
On Mon, Apr 13, 2015 at 12:55 PM, Francis Gerund ranr...@gmail.com wrote:
Hello.
I downloaded the most recent arch linux dual-boot install iso (from
2015-04-01).
- checked it with md5 and sha1 against
Hello.
I downloaded the most recent arch linux dual-boot install iso (from
2015-04-01).
- checked it with md5 and sha1 against checksums from the website. Also
did gpg verify. All okay.
- burned to cd using Brasero. Verified cd from within Brasero. Okay.
- verified by loop mounting, per
This is gonna sound silly, but try using something other than Brasero,
like cdw or bashburn. I've had Brasero burn corrupt CDs for me in the
past when the commandline tools worked fine, and ever since then I
refuse to use it.
On Mon, Apr 13, 2015, at 14:55, Francis Gerund wrote:
Forgot to say, I
When I do:
file
/run/media/default/USBHD005/New_stuff/Archlinux/archlinux-2015.04.01-dual.iso
I get:
archlinux-2015.04.01-dual.iso: # ISO 9660 CD-ROM filesystem data
'ARCH_201504 ' (bootable)
On Mon, Apr 13, 2015 at 2:04 PM, Damjan Georgievski gdam...@gmail.com
wrote:
Join the club of Brasero haters. That issue existed at least 2-3 years
ago when I used it last. Incredible.
On Mon, Apr 13, 2015, at 16:42, Francis Gerund wrote:
Well, I'll be [darned]!
Burned another cd manually, using wodim, then verified it, as per the
website.
It worked.
So it does
On Mon, Apr 13, 2015, at 17:36, Mauro Santos wrote:
On 13-04-2015 21:55, Jeremy O'Brien wrote:
Join the club of Brasero haters. That issue existed at least 2-3 years
ago when I used it last. Incredible.
On Mon, Apr 13, 2015, at 16:42, Francis Gerund wrote:
Well, I'll be [darned]!
Well, I'll be [darned]!
Burned another cd manually, using wodim, then verified it, as per the
website.
It worked.
So it does seem to be a problem with Brasero, after all.
Thanks guys.
On Mon, Apr 13, 2015 at 2:51 PM, Mark Lee m...@markelee.com wrote:
On Monday, April 13, 2015 02:28:00 PM
On 13-04-2015 21:55, Jeremy O'Brien wrote:
Join the club of Brasero haters. That issue existed at least 2-3 years
ago when I used it last. Incredible.
On Mon, Apr 13, 2015, at 16:42, Francis Gerund wrote:
Well, I'll be [darned]!
Burned another cd manually, using wodim, then verified it, as
Hello.
It seems that the package opal is out of date, and marked such for a
year without it being updated.
The current version in arch is 3.10.3, the newest is 3.14.3, if I
remember correctly.
Any suggestions about what to do in this case? I'm not sure if such
mails belong to this list or
On Monday, April 13, 2015 07:07:35 PM William Hatch wrote:
Hello,
I've been an Arch user for years now because pacman is my favorite package
manager. However, I've been working at a job for almost a year now where I
use a RHEL machine without root access. They let me use whatever software
Hello,
I've been an Arch user for years now because pacman is my favorite package
manager. However, I've been working at a job for almost a year now where I
use a RHEL machine without root access. They let me use whatever software
I want, but I have to build it all from source and install it in
:: Triggering uevents . . .
... blk_update request: I/O error, dev sr0, sector 1226572
... blk_update request: I/O error, dev sr0, sector 1226572
... Buffer I/O error on dev sr0, logical block 153344, async page read
:: Mounting '/dev/disk/by-label/ARCH_201504' ^@ERROR: device did not show
On Mon, Apr 13, 2015 at 11:29 AM, arnaud gaboury
arnaud.gabo...@gmail.com wrote:
gabx@hortensia ➤➤ ~ % R
/usr/lib64/R/bin/exec/R: error while loading shared libraries:
libicuuc.so.54: cannot open shared object file: No such file or
directory
gabx@hortensia ➤➤ ~ % mypac icu
306:icu 55.1-1
On 13.4.2015 11:29, arnaud gaboury wrote:
gabx@hortensia ➤➤ ~ % R
/usr/lib64/R/bin/exec/R: error while loading shared libraries:
libicuuc.so.54: cannot open shared object file: No such file or
directory
gabx@hortensia ➤➤ ~ % mypac icu
306:icu 55.1-1
386:lib32-icu 54.1-1
gabx@hortensia ➤➤ ~ %
Hi,
just released 4.0 kernel to [testing] repository.
- nvidia-304xx
- nvidia-340xx
- r8169
modules do not build.
Please take a look at it.
greetings
tpowa
--
Tobias Powalowski
Archlinux Developer Package Maintainer (tpowa)
http://www.archlinux.org
tp...@archlinux.org
signature.asc
gabx@hortensia ➤➤ ~ % R
/usr/lib64/R/bin/exec/R: error while loading shared libraries:
libicuuc.so.54: cannot open shared object file: No such file or
directory
gabx@hortensia ➤➤ ~ % mypac icu
306:icu 55.1-1
386:lib32-icu 54.1-1
gabx@hortensia ➤➤ ~ % ls -al /usr/lib32/libicuio.so.54
lrwxrwxrwx 1
On 04/13/15 at 11:31am, Armin K. wrote:
On 13.4.2015 11:29, arnaud gaboury wrote:
gabx@hortensia ➤➤ ~ % R
/usr/lib64/R/bin/exec/R: error while loading shared libraries:
libicuuc.so.54: cannot open shared object file: No such file or
directory
gabx@hortensia ➤➤ ~ % mypac icu
306:icu 55.1-1
libicu.so.55 just hit [extra], but I can't see R depending on icu so
maybe it has some plugin which requires icu which you need to rebuild?
If you run the following
$ LD_DEBUG=all ld /usr/lib64/R/bin/exec/R
You should be able to figure out which library that R links with that
needs icu (i.e.
On Mon, Apr 13, 2015 at 11:31 AM, Armin K. kre...@email.com wrote:
On 13.4.2015 11:29, arnaud gaboury wrote:
gabx@hortensia ➤➤ ~ % R
/usr/lib64/R/bin/exec/R: error while loading shared libraries:
libicuuc.so.54: cannot open shared object file: No such file or
directory
gabx@hortensia ➤➤ ~
After a reboot (due to BSOD in the Windows host - faulty RAM) the
interface name changed from eth0 to eno1636:
$ ifconfig eno1636
eno1636: flags=4163UP,BROADCAST,RUNNING,MULTICAST mtu 1500
inet 192.168.101.129 netmask 255.255.255.0 broadcast
192.168.101.255
21 matches
Mail list logo
