[gentoo-alpha] Problem installing gentoo linux/genkernel environ on alpha platform

[gentoo-alpha] Problem installing gentoo linux/genkernel environ on alpha platform

[Bill.Glessner]

I have been trying to install gentoo linux on a miata-class alpha platform and,
after following the instructions in the gentoo linux handbook, I still can't
seem to achieve a working system.
I am using a livecd burned from the gentoo-alpha-2004_2-20040730.iso download.
I used a stage1 tarball stage1-alpha-20040730.tbz2 to perform the installation,
and all seemed to go according to the gentoo handbook instructions. I chose the
genkernel option, and its creation/build also seemed to match the gentoo
handbook material.
The kernel version is kernel-2.4.21-alpha-r12. The step where the system disk
is made bootable and a bootloader is configured is where I seem to be failing.
I chose to configure/use the aboot bootloader; however, I can't seem to find
any directions, other than some minimal general material in the aboot, abootconf
and aboot.conf man pages, which describe how to set up abbot and boot the
kernel built during the installation. 
Am I using the most recent, stable gentoo linux installation distribution for
the alpha platform?
Has anyone successfully built a genkernel from the above distribution and
booted it? If so, how did you set up the aboot environment?
The specific problem I am having is:

boot dkc0 -fl "i"

...stuff leading to the aboot scondary bootloader menu...
jumping to bootstrap code
aboot: Linux/Alpha SRM bootloader version 0.9bpre
aboot: switching to OSF/1 PALcode version 1.22
aboot: booting from device 'SCSI 0 1009 0 0 0 0 0'
aboot: valid disklabel found: 3 partitions.
Welcome to aboot 0.9bpre
Commands: 
(the menu)

I give the command (wrapped for readability)

b /boot/kernel-2.4.21-alpha-r12 initrd=/boot/initrd-2.4.21-alpha-r12
 root=/dev/ram0 real_root=/dev/sda2 init=/linuxrc

the boot begins with loading the kernel after a number of device/driver
configurations but hangs at the point

IP protocols: ICMP, UDP, TCP, IGMP
IP: routing cache hash table of 1024 buckets, 8Kbytes
TCP: Hash table configured (established 16384 bind 16384)
NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.
FAT: bogus logical sector size 0
You didn't specify the type of your ufs filesystem

<...a sample mount command...>

>>>WARNING<<< Wrong ufstype may corrupt your filesystem, default is ufstype=old
ufs_read_super: bad magic number
read_super_block: can't find a reiserfs filesystem on (dev 01:00,block 64, size 1024)
read_super_block: can't find a reiserfs filesystem on (dev 01:00,block 8, size 1024)
kernel panic: VFS: Unable to mount root fs on 01:00

The dkc0 disk label has 3 partitions:
a: the swap partition (starting at cylinder 3)
b: the root partition with filesystem type ext2
c: the whole disk partition

I have probably missed/misundertood an installation step or haven't guessed the
correct aboot command so, if someone could provide an example of a working
aboot environment for a working alpha gentoo linux installation, I would
appreciate it.

Thanks for your help
Bill Glessner - System programmer
                Central Washington University

--
gentoo-alpha@gentoo.org mailing list

Re: [gentoo-alpha] Problem installing gentoo linux/genkernel environ on alpha platform

[Fluff]

What are the contents of the /etc/fstab-file? Looks like the boot is looking for
a reiserfs-partition. Have you set the correct filesystems there?

/Fluff

Citerar Bill.Glessner@cwu.EDU:

>
> I have been trying to install gentoo linux on a miata-class alpha platform
> and,
> after following the instructions in the gentoo linux handbook, I still can't
> seem to achieve a working system.
> I am using a livecd burned from the gentoo-alpha-2004_2-20040730.iso
> download.
> I used a stage1 tarball stage1-alpha-20040730.tbz2 to perform the
> installation,
> and all seemed to go according to the gentoo handbook instructions. I chose
> the
> genkernel option, and its creation/build also seemed to match the gentoo
> handbook material.
> The kernel version is kernel-2.4.21-alpha-r12. The step where the system disk
> is made bootable and a bootloader is configured is where I seem to be
> failing.
> I chose to configure/use the aboot bootloader; however, I can't seem to find
> any directions, other than some minimal general material in the aboot,
> abootconf
> and aboot.conf man pages, which describe how to set up abbot and boot the
> kernel built during the installation.
> Am I using the most recent, stable gentoo linux installation distribution for
> the alpha platform?
> Has anyone successfully built a genkernel from the above distribution and
> booted it? If so, how did you set up the aboot environment?
> The specific problem I am having is:
>
> boot dkc0 -fl "i"
>
> ...stuff leading to the aboot scondary bootloader menu...
> jumping to bootstrap code
> aboot: Linux/Alpha SRM bootloader version 0.9bpre
> aboot: switching to OSF/1 PALcode version 1.22
> aboot: booting from device 'SCSI 0 1009 0 0 0 0 0'
> aboot: valid disklabel found: 3 partitions.
> Welcome to aboot 0.9bpre
> Commands:
> (the menu)
>
> I give the command (wrapped for readability)
>
> b /boot/kernel-2.4.21-alpha-r12 initrd=/boot/initrd-2.4.21-alpha-r12
>  root=/dev/ram0 real_root=/dev/sda2 init=/linuxrc
>
> the boot begins with loading the kernel after a number of device/driver
> configurations but hangs at the point
>
> IP protocols: ICMP, UDP, TCP, IGMP
> IP: routing cache hash table of 1024 buckets, 8Kbytes
> TCP: Hash table configured (established 16384 bind 16384)
> NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.
> FAT: bogus logical sector size 0
> You didn't specify the type of your ufs filesystem
>
> <...a sample mount command...>
>
> >>>WARNING<<< Wrong ufstype may corrupt your filesystem, default is
> ufstype=old
> ufs_read_super: bad magic number
> read_super_block: can't find a reiserfs filesystem on (dev 01:00,block 64,
> size 1024)
> read_super_block: can't find a reiserfs filesystem on (dev 01:00,block 8,
> size 1024)
> kernel panic: VFS: Unable to mount root fs on 01:00
>
> The dkc0 disk label has 3 partitions:
> a: the swap partition (starting at cylinder 3)
> b: the root partition with filesystem type ext2
> c: the whole disk partition
>
> I have probably missed/misundertood an installation step or haven't guessed
> the
> correct aboot command so, if someone could provide an example of a working
> aboot environment for a working alpha gentoo linux installation, I would
> appreciate it.
>
> Thanks for your help
> Bill Glessner - System programmer
>                 Central Washington University
>
> --
> gentoo-alpha@gentoo.org mailing list
>
>


--
Fluff Abrahamsson
TIMELESS SOLUTIONS

T: 070 88 88 708
F: 070 88 88 701
E: fluff@fluff.se
#: 4049844

[Proudly presents: hypodea.com and photochallenge.net]


---
IMPORTANT NOTICE!

The contents of this email are confidential and are for the exclusive use of the
intended recipient(s). If you are not the intended recipient(s) please note that
any form of distribution, copying or use of this communication or the
information in it is strictly prohibited and may be unlawful. Please note that,
although this email has been virus-checked, neither Timeless Solutions HB nor
the sender accepts any responsibility for viruses and it is your responsibility
to scan the email and attachments (if any). If you believe you have received
this communication in error, please return it (with the title "received in
error") to the sender then delete the email and destroy any copies of it. We
would be grateful if you would also copy the communication to service@fluff.se

----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.


--
gentoo-alpha@gentoo.org mailing list

Re: [gentoo-alpha] Problem installing gentoo linux/genkernel environ on alpha platform

[Bill.Glessner]

The contents of the /etc/fstab are

/dev/sda1       none    swap    sw      0 0
/dev/sda2       /       ext3    noatime 0 1
/dev/sdb1       none    swap    sw      0 0
/dev/cdroms/cdrom0      /mnt/cdrom      auto noauto,user,ro     0 0
none            /proc   proc    defaults        0 0
none            /dev/shm        tmpfs   defaults        0 0

Bill

>Return-path: <fluff@fluff.se>
>Date: Fri, 08 Oct 2004 17:28:11 +0200
>From: Fluff <fluff@fluff.se>
>Subject: Re: [gentoo-alpha] Problem installing gentoo linux/genkernel environ
> on alpha platform
>To: Bill.Glessner@cwu.edu
>Cc: gentoo-alpha@lists.gentoo.org
>
>What are the contents of the /etc/fstab-file? Looks like the boot is looking for
>a reiserfs-partition. Have you set the correct filesystems there?
>
>/Fluff
>









>>Citerar Bill.Glessner@cwu.EDU:
>>
>>
>>I have been trying to install gentoo linux on a miata-class alpha platform and,
>>after following the instructions in the gentoo linux handbook, I still can't 
>>seem to achieve a working system.
>>I am using a livecd burned from the gentoo-alpha-2004_2-20040730.iso
>>download.
>>I used a stage1 tarball stage1-alpha-20040730.tbz2 to perform the > installation,
>>and all seemed to go according to the gentoo handbook instructions. I chose the
>>genkernel option, and its creation/build also seemed to match the gentoo
>>handbook material.
>>The kernel version is kernel-2.4.21-alpha-r12. The step where the system disk
>>is made bootable and a bootloader is configured is where I seem to be failing.
>> I chose to configure/use the aboot bootloader; however, I can't seem to find
>> any directions, other than some minimal general material in the aboot,
>> abootconf
>> and aboot.conf man pages, which describe how to set up abbot and boot the
>> kernel built during the installation.
>> Am I using the most recent, stable gentoo linux installation distribution for
>> the alpha platform?
>> Has anyone successfully built a genkernel from the above distribution and
>> booted it? If so, how did you set up the aboot environment?
>> The specific problem I am having is:
>>
>> boot dkc0 -fl "i"
>>
>> ...stuff leading to the aboot scondary bootloader menu...
>> jumping to bootstrap code
>> aboot: Linux/Alpha SRM bootloader version 0.9bpre
>> aboot: switching to OSF/1 PALcode version 1.22
>> aboot: booting from device 'SCSI 0 1009 0 0 0 0 0'
>> aboot: valid disklabel found: 3 partitions.
>> Welcome to aboot 0.9bpre
>> Commands:
>> (the menu)
>>
>> I give the command (wrapped for readability)
>>
>> b /boot/kernel-2.4.21-alpha-r12 initrd=/boot/initrd-2.4.21-alpha-r12
>>  root=/dev/ram0 real_root=/dev/sda2 init=/linuxrc
>>
>> the boot begins with loading the kernel after a number of device/driver
>> configurations but hangs at the point
>>
>> IP protocols: ICMP, UDP, TCP, IGMP
> IP: routing cache hash table of 1024 buckets, 8Kbytes
> TCP: Hash table configured (established 16384 bind 16384)
> NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.
> FAT: bogus logical sector size 0
> You didn't specify the type of your ufs filesystem
>
> <...a sample mount command...>
>
> >>>WARNING<<< Wrong ufstype may corrupt your filesystem, default is
> ufstype=old
> ufs_read_super: bad magic number
> read_super_block: can't find a reiserfs filesystem on (dev 01:00,block 64,
> size 1024)
> read_super_block: can't find a reiserfs filesystem on (dev 01:00,block 8,
> size 1024)
> kernel panic: VFS: Unable to mount root fs on 01:00
>
> The dkc0 disk label has 3 partitions:
> a: the swap partition (starting at cylinder 3)
> b: the root partition with filesystem type ext2
> c: the whole disk partition
>
> I have probably missed/misundertood an installation step or haven't guessed
> the
> correct aboot command so, if someone could provide an example of a working
> aboot environment for a working alpha gentoo linux installation, I would
> appreciate it.
>
> Thanks for your help
> Bill Glessner - System programmer
>                 Central Washington University
>
> --
> gentoo-alpha@gentoo.org mailing list
>
>


--
Fluff Abrahamsson
TIMELESS SOLUTIONS

T: 070 88 88 708
F: 070 88 88 701
E: fluff@fluff.se
#: 4049844

[Proudly presents: hypodea.com and photochallenge.net]


---
IMPORTANT NOTICE!

The contents of this email are confidential and are for the exclusive use of the
intended recipient(s). If you are not the intended recipient(s) please note that
any form of distribution, copying or use of this communication or the
information in it is strictly prohibited and may be unlawful. Please note that,
although this email has been virus-checked, neither Timeless Solutions HB nor
the sender accepts any responsibility for viruses and it is your responsibility
to scan the email and attachments (if any). If you believe you have received
this communication in error, please return it (with the title "received in
error") to the sender then delete the email and destroy any copies of it. We
would be grateful if you would also copy the communication to service@fluff.se

----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.


--
gentoo-alpha@gentoo.org mailing list

[gentoo-alpha] 2.6.8 kernel and SWXCR (Mylex DAC960) controller

[Brian Parkhurst]

After many months of trial and error.  (Actually having the time to really
dig into it more).
I've managed to interpret the DAC960.c source code to determine what the
devfs names might be under the 2.6.8 kernel.
FYI  (my root partition is the 2nd partition on the 1st Logical RAID 5
drive) (2 Logical volumes total)

My /etc/fstab
#Linux 2.6
/dev/rd/host0/target0/part1     none    swap    sw      0 0
/dev/rd/host0/target0/part2     /       ext3    noatime 0 0
/dev/rd/host0/target1/part1     /export ext3    noatime 0 0


#Linux 2.4
#/dev/rd/disc0/part1    none    swap    sw      0 0
#/dev/rd/disc0/part2    /       ext3    noatime 0 0
#/dev/rd/disc1/part1    /export ext3    noatime 0 0

My aboot.conf
0:2/boot/kernel-2.4.21-alpha-r12 root=/dev/rd/disc0/part2 console=ttyS0
console=tty0 initrd=/boot/initrd-2.4.21-alpha-r12 init=/linuxrc
2:2/boot/kernel-2.6.8-gentoo-r6 root=/dev/rd/host0/target0/part2
console=ttyS0 console=tty0 initrd=/boot/initrd-2.6.8-gentoo-r6 init=/linuxrc

The key I found for this to work properly was to make certain the devfs file
system was properly compiled into the kernel and automounted the relevant
portions of my .config.

My .config file:
CONFIG_DEVFS_FS=y
CONFIG_DEVFS_MOUNT=y

Brian Parkhurst
brianp@prodigy.net


--
gentoo-alpha@gentoo.org mailing list

Re: [gentoo-alpha] Problem installing gentoo linux/genkernel environ on alpha platform

[Tony Hammond]

Hi,


>From the output below, it appears that aboot is working fine given that
the kernel has loaded.  This looks like a problem with your ramdisk image
to me.  I agree, check your fstab, but on the ramdisk image.


> >>>WARNING<<< Wrong ufstype may corrupt your filesystem, default is ufstype=old
> ufs_read_super: bad magic number
> read_super_block: can't find a reiserfs filesystem on (dev 01:00,block 64, size 1024)
> read_super_block: can't find a reiserfs filesystem on (dev 01:00,block 8, size 1024)
> kernel panic: VFS: Unable to mount root fs on 01:00


The device file with major:minor number 01:00 is /dev/ram0 or /dev/rd/0
depending on whether you are using devfs.


-Tony

**************************************************************************
Tony Hammond
Computing Cluster Administrator
University of Wisconsin at Madison
Department of Engineering Physics
1500 Engineering Drive
Room 522
Madison, WI 53706-1609
Phone:  608-263-6577
Fax:  608-265-4546
Mobile:  608-239-8744
Email:  hammonda@cae.wisc.edu
URL:  http://www.cae.wisc.edu

On Fri, 8 Oct 2004 Bill.Glessner@cwu.EDU wrote:

>
> I have been trying to install gentoo linux on a miata-class alpha platform and,
> after following the instructions in the gentoo linux handbook, I still can't
> seem to achieve a working system.
> I am using a livecd burned from the gentoo-alpha-2004_2-20040730.iso download.
> I used a stage1 tarball stage1-alpha-20040730.tbz2 to perform the installation,
> and all seemed to go according to the gentoo handbook instructions. I chose the
> genkernel option, and its creation/build also seemed to match the gentoo
> handbook material.
> The kernel version is kernel-2.4.21-alpha-r12. The step where the system disk
> is made bootable and a bootloader is configured is where I seem to be failing.
> I chose to configure/use the aboot bootloader; however, I can't seem to find
> any directions, other than some minimal general material in the aboot, abootconf
> and aboot.conf man pages, which describe how to set up abbot and boot the
> kernel built during the installation.
> Am I using the most recent, stable gentoo linux installation distribution for
> the alpha platform?
> Has anyone successfully built a genkernel from the above distribution and
> booted it? If so, how did you set up the aboot environment?
> The specific problem I am having is:
>
> boot dkc0 -fl "i"
>
> ...stuff leading to the aboot scondary bootloader menu...
> jumping to bootstrap code
> aboot: Linux/Alpha SRM bootloader version 0.9bpre
> aboot: switching to OSF/1 PALcode version 1.22
> aboot: booting from device 'SCSI 0 1009 0 0 0 0 0'
> aboot: valid disklabel found: 3 partitions.
> Welcome to aboot 0.9bpre
> Commands:
> (the menu)
>
> I give the command (wrapped for readability)
>
> b /boot/kernel-2.4.21-alpha-r12 initrd=/boot/initrd-2.4.21-alpha-r12
>  root=/dev/ram0 real_root=/dev/sda2 init=/linuxrc
>
> the boot begins with loading the kernel after a number of device/driver
> configurations but hangs at the point
>
> IP protocols: ICMP, UDP, TCP, IGMP
> IP: routing cache hash table of 1024 buckets, 8Kbytes
> TCP: Hash table configured (established 16384 bind 16384)
> NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.
> FAT: bogus logical sector size 0
> You didn't specify the type of your ufs filesystem
>
> <...a sample mount command...>
>
> >>>WARNING<<< Wrong ufstype may corrupt your filesystem, default is ufstype=old
> ufs_read_super: bad magic number
> read_super_block: can't find a reiserfs filesystem on (dev 01:00,block 64, size 1024)
> read_super_block: can't find a reiserfs filesystem on (dev 01:00,block 8, size 1024)
> kernel panic: VFS: Unable to mount root fs on 01:00
>
> The dkc0 disk label has 3 partitions:
> a: the swap partition (starting at cylinder 3)
> b: the root partition with filesystem type ext2
> c: the whole disk partition
>
> I have probably missed/misundertood an installation step or haven't guessed the
> correct aboot command so, if someone could provide an example of a working
> aboot environment for a working alpha gentoo linux installation, I would
> appreciate it.
>
> Thanks for your help
> Bill Glessner - System programmer
>                 Central Washington University
>
> --
> gentoo-alpha@gentoo.org mailing list
>

--
gentoo-alpha@gentoo.org mailing list

[gentoo-alpha] Portage problem

[Brian Parkhurst]

Hi all,

I had a system crash this weekend, about 12 hours after getting the 2.6.8
kernel working on my alpha.  (unrelated problem).

I've restored the system to a backup from about 10 days ago but it now seems
my portage database is problematic and the typical emerge commands are
failing.

e.g.:

emerge sync seems to work okay
I've successfully run fixpackages.

emerge -uv world
fails after extracting the package with no errors (but doesn't go and
compile it).

I'm guessing that between the time I did the backup and restored it an
upgrade or other emerge had changed the portage tree.
However I am unable to forcefully rebuild the portage set or the gentoolkit.

Any ideas?

Thanks,

Brian Parkhurst
www.pyrobrian.com



--
gentoo-alpha@gentoo.org mailing list

RE: [gentoo-alpha] Portage problem

[Brian Parkhurst]

 
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

E.g.,

alpha-omega export # emerge system
Calculating system dependencies ...done!
>>> emerge (1 of 4) sys-apps/portage-2.0.51_rc9 to /
>>> md5 src_uri ;-) portage-2.0.51_rc9.tar.bz2
>>> Unpacking source...
>>> Unpacking portage-2.0.51_rc9.tar.bz2 to
>>> /var/tmp/portage/portage-2.0.51_rc9/work Source unpacked.
alpha-omega export # 

The process is exiting prematurely but I'm not sure for what reason. 

- -----Original Message-----
From: Brian Parkhurst [mailto:brianp@spamcop.net] 
Sent: Monday, October 11, 2004 10:41 AM
To: gentoo-alpha@lists.gentoo.org
Subject: [gentoo-alpha] Portage problem

Hi all,

I had a system crash this weekend, about 12 hours after getting the
2.6.8
kernel working on my alpha.  (unrelated problem).

I've restored the system to a backup from about 10 days ago but it
now seems
my portage database is problematic and the typical emerge commands
are
failing.

e.g.:

emerge sync seems to work okay
I've successfully run fixpackages.

emerge -uv world
fails after extracting the package with no errors (but doesn't go and
compile it).

I'm guessing that between the time I did the backup and restored it
an
upgrade or other emerge had changed the portage tree.
However I am unable to forcefully rebuild the portage set or the
gentoolkit.

Any ideas?

Thanks,

Brian Parkhurst
www.pyrobrian.com



- --
gentoo-alpha@gentoo.org mailing list


-----BEGIN PGP SIGNATURE-----
Version: PGP 8.1

iQA/AwUBQWrXX/Z0qmLutBiIEQLouwCg5fmq/9ewY1+eqLCg6ruH75/7PqYAoNmm
d4jJ97EH4Zz9A9gSj9umc+Yl
=AuJV
-----END PGP SIGNATURE-----


--
gentoo-alpha@gentoo.org mailing list

RE: [gentoo-alpha] Portage problem

[Brian Parkhurst]

 
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Additional info from emerge -duv portage

Script started on Mon Oct 11 12:02:17 2004
alpha-omega portage # 
emerge -duv portage
Calculating dependencies  
Parent:    None
Depstring: sys-apps/portage
Candidates: ['sys-apps/portage']
ebuild: sys-apps/portage-2.0.51_rc9
binpkg: None
Parent:    ebuild / sys-apps/portage-2.0.51_rc9 merge
Depstring: !bootstrap? ( sys-devel/patch ) !build? (
>=sys-apps/sed-4.0.5 dev-python/python-fchksum
>=dev-lang/python-2.2.1 sys-apps/debianutils >=app-shells/bash-2.05a
) selinux? ( >=dev-python/python-selinux-2.15 )
Candidates: ['dev-python/python-fchksum', 'sys-devel/patch',
'>=dev-lang/python-2.2.1', '>=sys-apps/sed-4.0.5',
'>=app-shells/bash-2.05a', 'sys-apps/debianutils']
ebuild: dev-python/python-fchksum-1.7.1
binpkg: None
ebuild: sys-devel/patch-2.5.9
binpkg: None
ebuild: dev-lang/python-2.3.4
binpkg: None
ebuild: sys-apps/sed-4.1.2
binpkg: None
ebuild: app-shells/bash-3.0-r6
binpkg: None
ebuild: sys-apps/debianutils-1.16.7-r4
binpkg: None
Exiting... ebuild / sys-apps/portage-2.0.51_rc9 merge
Exiting... None
 ...done!
>>> emerge (1 of 1) sys-apps/portage-2.0.51_rc9 to /
+ dyn_clean
+ rm -rf /var/tmp/portage/portage-2.0.51_rc9/image
+ hasq keeptemp autoaddcvs buildpkg ccache distcc distlocks notitles
sandbox userpriv usersandbox
+ local x
+ local me=keeptemp
+ shift
+ for x in '"$@"'
+ '[' autoaddcvs == keeptemp ']'
+ for x in '"$@"'
+ '[' buildpkg == keeptemp ']'
+ for x in '"$@"'
+ '[' ccache == keeptemp ']'
+ for x in '"$@"'
+ '[' distcc == keeptemp ']'
+ for x in '"$@"'
+ '[' distlocks == keeptemp ']'
+ for x in '"$@"'
+ '[' notitles == keeptemp ']'
+ for x in '"$@"'
+ '[' sandbox == keeptemp ']'
+ for x in '"$@"'
+ '[' userpriv == keeptemp ']'
+ for x in '"$@"'
+ '[' usersandbox == keeptemp ']'
+ return 1
+ rm -rf /var/tmp/portage/portage-2.0.51_rc9/temp/eclass-debug.log
+ hasq keepwork autoaddcvs buildpkg ccache distcc distlocks notitles
sandbox userpriv usersandbox
+ local x
+ local me=keepwork
+ shift
+ for x in '"$@"'
+ '[' autoaddcvs == keepwork ']'
+ for x in '"$@"'
+ '[' buildpkg == keepwork ']'
+ for x in '"$@"'
+ '[' ccache == keepwork ']'
+ for x in '"$@"'
+ '[' distcc == keepwork ']'
+ for x in '"$@"'
+ '[' distlocks == keepwork ']'
+ for x in '"$@"'
+ '[' notitles == keepwork ']'
+ for x in '"$@"'
+ '[' sandbox == keepwork ']'
+ for x in '"$@"'
+ '[' userpriv == keepwork ']'
+ for x in '"$@"'
+ '[' usersandbox == keepwork ']'
+ return 1
+ rm -rf /var/tmp/portage/portage-2.0.51_rc9/.compiled
+ rm -rf /var/tmp/portage/portage-2.0.51_rc9/.unpacked
+ rm -rf /var/tmp/portage/portage-2.0.51_rc9/.installed
+ rm -rf /var/tmp/portage/portage-2.0.51_rc9/build-info
+ rm -rf /var/tmp/portage/portage-2.0.51_rc9/work
+ '[' -f /var/tmp/portage/portage-2.0.51_rc9/.unpacked ']'
+ true
+ set +x
>>> md5 src_uri ;-) portage-2.0.51_rc9.tar.bz2
+ dyn_setup
+ '[' GNU == Linux ']'
+ pkg_setup
+ return
+ set +x
+ dyn_unpack
+ trap abort_unpack SIGINT SIGQUIT
+ local newstuff=no
+ '[' -e /var/tmp/portage/portage-2.0.51_rc9/work ']'
+ '[' -e /var/tmp/portage/portage-2.0.51_rc9/work ']'
+ install -m0700 -d /var/tmp/portage/portage-2.0.51_rc9/work
+ '[' -d /var/tmp/portage/portage-2.0.51_rc9/work ']'
+ cd /var/tmp/portage/portage-2.0.51_rc9/work
+ echo '>>> Unpacking source...'
>>> Unpacking source...
+ src_unpack
+ unpack portage-2.0.51_rc9.tar.bz2
+ local x
+ local y
+ local myfail
+ local tarvars
+ '[' GNU == BSD ']'
+ tarvars=--no-same-owner
+ for x in '"$@"'
+ myfail='failure unpacking portage-2.0.51_rc9.tar.bz2'
++ pwd
+ echo '>>> Unpacking portage-2.0.51_rc9.tar.bz2 to
/var/tmp/portage/portage-2.0.51_rc9/work'
>>> Unpacking portage-2.0.51_rc9.tar.bz2 to
>>> /var/tmp/portage/portage-2.0.51_rc9/work 
+ y=portage-2.0.51_rc9.tar
+ y=tar
+ case "${x##*.}" in
+ '[' tar == tar ']'
+ bzip2 -dc /usr/portage/distfiles/portage-2.0.51_rc9.tar.bz2
+ tar xf - --no-same-owner
+ cd /var/tmp/portage/portage-2.0.51_rc9/work/portage-2.0.51_rc9
+ touch /var/tmp/portage/portage-2.0.51_rc9/.unpacked
+ echo '>>> Source unpacked.'
>>> Source unpacked.
+ cd /var/tmp/portage/portage-2.0.51_rc9
+ trap SIGINT SIGQUIT
+ set +x
alpha-omega portage:

Script done on Mon Oct 11 12:02:46 2004

- -----Original Message-----
From: Brian Parkhurst [mailto:brianp@spamcop.net] 
Sent: Monday, October 11, 2004 11:57 AM
To: 'Brian Parkhurst'; gentoo-alpha@lists.gentoo.org
Subject: RE: [gentoo-alpha] Portage problem

 
*** PGP SIGNATURE VERIFICATION ***
*** Status:   Good Signature
*** Signer:   Brian C. Parkhurst <brianp@u.washington.edu>
(0xEEB41888)
*** Signed:   10/11/2004 11:56:31 AM
*** Verified: 10/11/2004 12:03:43 PM
*** BEGIN PGP VERIFIED MESSAGE ***

E.g.,

alpha-omega export # emerge system
Calculating system dependencies ...done!
>>> emerge (1 of 4) sys-apps/portage-2.0.51_rc9 to /
>>> md5 src_uri ;-) portage-2.0.51_rc9.tar.bz2
>>> Unpacking source...
>>> Unpacking portage-2.0.51_rc9.tar.bz2 to
>>> /var/tmp/portage/portage-2.0.51_rc9/work Source unpacked.
alpha-omega export # 

The process is exiting prematurely but I'm not sure for what reason. 

- -----Original Message-----
From: Brian Parkhurst [mailto:brianp@spamcop.net] 
Sent: Monday, October 11, 2004 10:41 AM
To: gentoo-alpha@lists.gentoo.org
Subject: [gentoo-alpha] Portage problem

Hi all,

I had a system crash this weekend, about 12 hours after getting the
2.6.8
kernel working on my alpha.  (unrelated problem).

I've restored the system to a backup from about 10 days ago but it
now seems
my portage database is problematic and the typical emerge commands
are
failing.

e.g.:

emerge sync seems to work okay
I've successfully run fixpackages.

emerge -uv world
fails after extracting the package with no errors (but doesn't go and
compile it).

I'm guessing that between the time I did the backup and restored it
an
upgrade or other emerge had changed the portage tree.
However I am unable to forcefully rebuild the portage set or the
gentoolkit.

Any ideas?

Thanks,

Brian Parkhurst
www.pyrobrian.com



- --
gentoo-alpha@gentoo.org mailing list



*** END PGP VERIFIED MESSAGE ***


-----BEGIN PGP SIGNATURE-----
Version: PGP 8.1

iQA/AwUBQWrZ1PZ0qmLutBiIEQIUeQCgxgY0dIUfqrKMZRwIEhiLK+qlE6gAoIry
4UYNuHAPhe+yxR1qTJpZAr9b
=61Fh
-----END PGP SIGNATURE-----


--
gentoo-alpha@gentoo.org mailing list

Re: [gentoo-alpha] Portage problem

[Brian Parkhurst]

As I've not had any success in restoring emerge functionality to the system.
I'm wiping it and doing a full restore of the system from my backup tape
from 3 weeks ago.

Hopefully this will resolve the emerge failures.  Otherwise its back to
Gentoo 2004.2 and build out from my backup world file.  The re-compile time
should be about 5 days with all that I've emerged over the past year.  What
a way to upgrade...

Brian Parkhurst
www.pyrobrian.com  (offline at the moment)



--
gentoo-alpha@gentoo.org mailing list