Re: cant configure s390 installation
On Wed, Sep 22, 2004 at 10:18:15PM +0200, Shimon Lebowitz wrote:
> Hi,
> I ran the base install of Debian using
> NFS. The CD image was mounted on my PC
> (on a virtual CDROM generated by Daemon-tools).
What is Daemon-tools and is this machine running Windows or some kind of
unix?
> After the install, and a reboot, I was told to run
> /usr/sbin/base-config
> First I remounted the CD image, with:
> mount -t nfs -o ro 10.1.20.40:/cdpc /mnt/PC-cd
>
> and then ran the base-config command.
>
> Here is some console output, with comments (starting ***) by me.
> I apologize for the length of the posting.
>
>
> linux01:/# mount -t nfs -o ro 10.1.20.40:/cdpc /mnt/PC-cd
> linux01:/# mount
> /dev/dasd/0193/part1 on / type ext3 (rw,errors=remount-ro)
> proc on /proc type proc (rw)
> 10.1.20.40:/cdpc on /mnt/PC-cd type nfs (ro,addr=10.1.20.40)
> linux01:/# /usr/sbin/base-config
>
> *** the base-config program displayed the following questions
> *** and below each is my answer, marked with ">>"
>
> Pick the geographic area in which you live.
> >> Asia
> Select a city or time zone:
> >> Jerusalem
> Shall I enable md5 passwords?
> >> Yes
> Shall I enable shadow passwords?
> >> Yes
> *** At this point an error message was displayed, in the background
> *** line-mode screen, which disappeared when the next panel was
> *** painted. I have no idea if this was important.
>
> Apt Configuration
> Apt can access the Debian archive in a variety of ways. Choose the
> access method apt should use. For example if you have a Debian cd,
> select "cdrom", while if you plan to install via a Debian mirror,
> choose "ftp" or "http".
>
> Choose the method apt should use to access the Debian archive:
> >> filesystem
>
> Use non-free software?
> >> No
>
> Enter mirror directory:
> >> /mnt/PC-cd
>
> Apt Configuration
> Failed to access the Debian archive
>
> When I tried to access the debian archive using the information you
> provided, apt gave the following error. I will run through the
> questions again, try to correct the error.
>
> Failed to fetch file:/mnt/PC-cd/dists/stable/main/binary-
> s390/Packages
> File not found W: Couldn't stat source package list file: stable/main
> Packages
> (/var/lib/apt/lists/_mnt_PC-cd_dists_stable_main_binary-
> s390_Packages)
> - stat (2 No such file or directory) W: You may want to run apt-get
> update to correct these problems E: Some index files failed to
> download, they have been ignored, or old ones used instead.
>
> *** It then went back to the "choose the method" panel.
>
> *** I wanted to see why it has trouble fetching that file,
> *** so I went to look for it:
>
> linux01:/# cd /mnt/PC-cd/dists/stable/main/binary-s390
> bash: cd: /mnt/PC-cd/dists/stable/main/binary-s390: Not a directory
> linux01:/# cd /mnt/PC-cd/dists/stable/main
> bash: cd: /mnt/PC-cd/dists/stable/main: Not a directory
> linux01:/# cd /mnt/PC-cd/dists/stable
> bash: cd: /mnt/PC-cd/dists/stable: Not a directory
> linux01:/# cd /mnt/PC-cd/dists
> linux01:/mnt/PC-cd/dists#
>
> *** hmmm.. lots of missing directories here!
>
> linux01:/mnt/PC-cd/dists# ls -al
> total 10
> dr-xr-xr-x 1 root root 8192 Sep 22 2004 .
> drwxrwxrwx 1 root root 8192 Sep 22 2004 ..
> -r-xr-xr-x 1 root root 266 Dec 2 2003 TRANS.TBL
> -r-xr-xr-x 1 root root 0 Dec 2 2003 frozen
> -r-xr-xr-x 1 root root 0 Dec 2 2003 stable
> -r-xr-xr-x 1 root root 0 Dec 2 2003 testing
> -r-xr-xr-x 1 root root 0 Dec 2 2003 unstable
> dr-xr-xr-x 1 root root 8192 Dec 2 2003 woody
>
> *** Aha! there IS a "stable", but it's a file, not a directory.
> *** and there is also a "woody" directory.....
> *** Let's see what is in /woody
Ah, I guess you must be running a defective OS (probably windows) that
doesn't understand the concept of symlinks, which is what stable,
testing, frozen and usntable are. You must have working symlinks on the
nfs share for the installer to work.
> linux01:/mnt/PC-cd/dists# cd woody
> linux01:/mnt/PC-cd/dists/woody# ls -al
> total 906
> dr-xr-xr-x 1 root root 8192 Dec 2 2003 .
> dr-xr-xr-x 1 root root 8192 Sep 22 2004 ..
> -r-xr-xr-x 1 root root 3652610 Nov 20 2003 Contents-s390.gz
> -r-xr-xr-x 1 root root 644 Dec 2 2003 Release
> -r-xr-xr-x 1 root root 250 Dec 2 2003 TRANS.TBL
> dr-xr-xr-x 1 root root 8192 Dec 2 2003 contrib
> dr-xr-xr-x 1 root root 8192 Dec 2 2003 main
> dr-xr-xr-x 1 root root 8192 Dec 2 2003 non-US
>
> *** Oh! /woody has a "main" in it!
>
> linux01:/mnt/PC-cd/dists/woody# cd main
> linux01:/mnt/PC-cd/dists/woody/main# ls -al
> total 13
> dr-xr-xr-x 1 root root 8192 Dec 2 2003 .
> dr-xr-xr-x 1 root root 8192 Dec 2 2003 ..
> -r-xr-xr-x 1 root root 153 Dec 2 2003 TRANS.TBL
> dr-xr-xr-x 1 root root 8192 Dec 2 2003 binary-s390
> dr-xr-xr-x 1 root root 8192 Dec 2 2003 disks-s390
> dr-xr-xr-x 1 root root 8192 Dec 2 2003 source
> linux01:/mnt/PC-cd/dists/woody/main# cd binary-s390
> linux01:/mnt/PC-cd/dists/woody/main/binary-s390# ls -al
> total 280
> dr-xr-xr-x 1 root root 8192 Dec 2 2003 .
> dr-xr-xr-x 1 root root 8192 Dec 2 2003 ..
> -r-xr-xr-x 1 root root 878588 Dec 2 2003 Packages
> -r-xr-xr-x 1 root root 239849 Dec 2 2003 Packages.gz
> -r-xr-xr-x 1 root root 95 Dec 2 2003 Release
> -r-xr-xr-x 1 root root 152 Dec 2 2003 TRANS.TBL
>
> *************
> It turns out that the hierarchy the config program wanted,
> "/mnt/PC-cd/dists/stable/main/binary-s390", really exists as:
> "/mnt/PC-cd/dists/woody/main/binary-s390".
>
> So, what do I do now, to configure my s390 Debian system???
Use a real OS (a unix one) to host the CD for NFS since you need a valid
unix filesystem for the installer to access over NFS. What a Windows PC is
likely to simulate will not be good enough.
Len Sorensen
Reply to: