i'd guess a mirror issue, no updates on arch in a week? never.
i'd pick a new mirror and go -Syyu.
luckily i've got IRC in the next terminal...
19:44 !mirrorcheck
19:44 see the status of mirrors:
http://users.archlinux.de/~gerbra/mirrorcheck.html <>
http://www.archlinux.de/?page=MirrorStatus
Hi David,
>
> I have several boxes running arch. In the past week or so, I haven't
> had any updates. Is it my system not updating or have there been relatively
> few updates?
>
I noticed the same thing. Quite a few of the mirrors were out of date
for some reason. I changed to a mirror t
Listmates,
I have several boxes running arch. In the past week or so, I haven't
had any updates. Is it my system not updating or have there been relatively few
updates?
--
David C. Rankin, J.D.,P.E.
Rankin Law Firm, PLLC
510 Ochiltree Street
Nacogdoches, Texas 75961
Telephone: (936) 71
--- El mié 22-jul-09, Daenyth Blank escribió:
> On Tue, Jul 21, 2009 at 23:01, Gerardo Exequiel Pozzi wrote:
> >
> > Hello,
> >
> > This is a list [#1] of possible packages that can be
> arch=('any') in a future.
>
> Would you mind posting the script you used to find that?
> :)
>
Hi
Is base
On Wed, Jul 22, 2009 at 4:03 PM, Baho Utot wrote:
> _DO NOT_ change the type in /etc/fstab that should be set to the
> filesystem on the raid array.
>
> You want to change the partition table.
Sorry, I wasn't clear. I fixed the partition tables, and I haven't
touched fstab.
--
Samuel 'Shardz' B
On Wed, 2009-07-22 at 15:55 -0400, Samuel Baldwin wrote:
> On Wed, Jul 22, 2009 at 3:49 PM, Baho Utot wrote:
> > That's the filesystem on the raid array.
> >
> > The partition type should be fd... you set that using fdisk
> > The fd tells a system that the partition is part of a raid array.
> > You
On Wed, Jul 22, 2009 at 3:49 PM, Baho Utot wrote:
> That's the filesystem on the raid array.
>
> The partition type should be fd... you set that using fdisk
> The fd tells a system that the partition is part of a raid array.
> You should set it on all the partitions that makeup md0 and md1
Ahh, I
On Wed, 2009-07-22 at 15:36 -0400, Samuel Baldwin wrote:
> On Wed, Jul 22, 2009 at 6:37 AM, Gerhard Brauer wrote:
> > Not sure if i understand: You don't boot from the raid arrays, correct?
> > These are only data or whatever arrays which you mount to /mnt/mdX?
>
> Correct.
>
> > Have you put you
On Wed, Jul 22, 2009 at 6:37 AM, Gerhard Brauer wrote:
> Not sure if i understand: You don't boot from the raid arrays, correct?
> These are only data or whatever arrays which you mount to /mnt/mdX?
Correct.
> Have you put your raid module (raid1) in /etc/rc.conf->MODULES and have
> you put your
At Wed, 22 Jul 2009 12:33:37 +0200,
Jan de Groot wrote:
>
> On Wed, 2009-07-22 at 14:28 +0400, Sergej Pupykin wrote:
> > Hi,
> >
> > I need help to build parrot for x86_64.
> >
> > /usr/bin/ld: /usr/lib/libreadline.a(readline.o): relocation R_X86_64_32
> > against `rl_get_previous_history' can
Am Dienstag, den 21.07.2009, 21:45 -0400 schrieb Samuel Baldwin:
> My drives RAID drives are set up as so: sdc1 and sdd1 are mirrored to
> make md0, sde1 and sdf1 are mirrored to make md1. These are mounted at
> /mnt/md0 and /mnt/md1, respectively, and formatted to ext4.
Not sure if i understand:
On Wed, 2009-07-22 at 14:28 +0400, Sergej Pupykin wrote:
> Hi,
>
> I need help to build parrot for x86_64.
>
> /usr/bin/ld: /usr/lib/libreadline.a(readline.o): relocation R_X86_64_32
> against `rl_get_previous_history' can not be used when making a shared
> object; recompile with -fPIC
> /usr/l
Hi,
I need help to build parrot for x86_64.
/usr/bin/ld: /usr/lib/libreadline.a(readline.o): relocation R_X86_64_32 against
`rl_get_previous_history' can not be used when making a shared object;
recompile with -fPIC
/usr/lib/libreadline.a: could not read symbols: Bad value
Does it ask to reco
13 matches
Mail list logo
