Re: Woody installation on IBM 44P-170 - really close
Does anybody know where I may obtain the source code for boot-floppies 3.0.23? PowerPC if it makes a difference. I compiled a boot/root Power3 install image with level 3.0.23 of the boot-floppies. I boot via BOOTP/tftp. However, I still am not able to do an NFS or HTML install. At this point I am not selecting the correct rescue.bin file, but I believe the failure occurs prior to attempting to install the image. It appears to be mounting problems in both cases. I would assume that this has been tested on other platforms, so it is very likely operator error. I have gone through the config file I use during the compile. It is the default power3 config file. It looks ok, but I am no kernel guru. The errors are documented below. I will have to create my own rescue.bin image. What kind of image is this? Do I need to create a true rescue image with bootloader etc, or is this really just the zImage kernel? If it is a true rescue image, I would assume that I use yaboot? I know how to make one; however, does Debian have documentation how they made theirs? My NFS server is version 2. Snippets from config file: # # Block devices # CONFIG_BLK_DEV_FD=y # CONFIG_BLK_DEV_XD is not set # CONFIG_PARIDE is not set # CONFIG_BLK_CPQ_DA is not set # CONFIG_BLK_CPQ_CISS_DA is not set # CONFIG_BLK_DEV_DAC960 is not set CONFIG_BLK_DEV_LOOP=y # CONFIG_BLK_DEV_NBD is not set CONFIG_BLK_DEV_RAM=y CONFIG_BLK_DEV_RAM_SIZE=4096 CONFIG_BLK_DEV_INITRD=y # # Network File Systems # # CONFIG_CODA_FS is not set # CONFIG_INTERMEZZO_FS is not set CONFIG_NFS_FS=y # CONFIG_NFS_V3 is not set # CONFIG_ROOT_NFS is not set CONFIG_NFSD=y # CONFIG_NFSD_V3 is not set CONFIG_SUNRPC=y CONFIG_LOCKD=y # CONFIG_SMB_FS is not set # CONFIG_NCP_FS is not set # CONFIG_NCPFS_PACKET_SIGNING is not set # CONFIG_NCPFS_IOCTL_LOCKING is not set # CONFIG_NCPFS_STRONG is not set # CONFIG_NCPFS_NFS_NS is not set # CONFIG_NCPFS_OS2_NS is not set # CONFIG_NCPFS_SMALLDOS is not set # CONFIG_NCPFS_NLS is not set # CONFIG_NCPFS_EXTRAS is not set # CONFIG_ZISOFS_FS is not set # CONFIG_ZLIB_FS_INFLATE is not set Rolf -- Rolf Brudeseth [EMAIL PROTECTED] pSeries System Engineering Integration, IBM Enterprise Systems Group Austin, TX, Phone: 512-838-6558 -- Forwarded by Rolf Brudeseth/Austin/IBM on 05/22/2002 09:48 AM --- Rolf Brudeseth 05/15/2002 11:53 AM To:Chris Tillman [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED] cc: From: Rolf Brudeseth/Austin/IBM@IBMUS Subject:Re: Woody installation on IBM 44P-170 - really close Importance: Normal On Tue, May 14, 2002 at 01:41:54PM -0500, Rolf Brudeseth wrote: I believe I am really close to getting Debian working on an IBM 44P-170 workstation. I made a combined boot/root image. The kernel is 2.4.18 from kernel.org, while the root image is from Debian. I used the default power3 config file (power3_defconfig). Root image: http://ftp.debian.org/debian/dists/woody/main/disks-powerpc/current/chrp/root.bin No, I actually used: http://ftp.debian.org/debian/dists/woody/main/disks-powerpc/current/chrp/images-1.44/root.bin 02-Apr-2002 I download the boot/root image from Open Firmware via BOOTP. It starts up the installation routine. I am able to successfully partition/format the hard drive. However, if I try to install via NFS I get the following error message: Error mounting NFS filesystem, 'server:/path', please try again. Does it literally say 'server:/path', indicating the variables are not getting initialized? or is the path correct as far as you can see? If you look in vc 3, is there another possibly more detailed error message there? No, I enter the correct server and path name. I know NFS is working, because I am able to mount from other systems. If I try to install via HTTP/FTP it will successfully download rescue.bin and drivers.tgz; however I get the following error messages: Unable to mount the Rescue Floppy. The attempt to extract Rescue Floppy failed. Installation of the file '/tmp/rescue.bin' failed. -- *--v- Installing Debian GNU/Linux 3.0 v--* | http://www.debian.org/releases/woody/installmanual | | debian-imac (potato): http://debian-imac.sourceforge.net | |Chris Tillman[EMAIL PROTECTED] | | May the Source be with you | ** Rolf -- Rolf Brudeseth [EMAIL PROTECTED] pSeries System Engineering Integration, IBM Enterprise Systems Group Austin, TX, Phone: 512-838-6558 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Woody installation on IBM 44P-170 - really close
On Wed, May 22, 2002 at 11:27:15AM -0500, Rolf Brudeseth wrote: Does anybody know where I may obtain the source code for boot-floppies 3.0.23? PowerPC if it makes a difference. The source is the same for all architectures, and can be found in /pool/main/b/boot-floppies/ on any Debian mirror. Note that you do not need this in order to make a new rescue.bin. I will have to create my own rescue.bin image. What kind of image is this? Do I need to create a true rescue image with bootloader etc, or is this really just the zImage kernel? If it is a true rescue image, I would assume that I use yaboot? I know how to make one; however, does Debian have documentation how they made theirs? This chapter in the installation manual: http://www.debian.org/releases/woody/i386/ch-boot-floppy-techinfo.en.html explains how the rescue disk works, specifically how to replace the kernel. -- - mdz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Woody installation on IBM 44P-170 - really close
El mar, 14-05-2002 a las 14:41, Rolf Brudeseth escribió: I believe I am really close to getting Debian working on an IBM 44P-170 workstation. I made a combined boot/root image. The kernel is 2.4.18 from kernel.org, while the root image is from Debian. I used the default power3 config file (power3_defconfig). Root image: http://ftp.debian.org/debian/dists/woody/main/disks-powerpc/current/chrp/root.bin There are not such image. Anyway I'll try with the images on this directory. I have an IBM 44P-170 running Woody over SuSE. -- German Poo Caaman~o mailto:[EMAIL PROTECTED] http://www.ubiobio.cl/~gpoo/chilelindo.html -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Woody installation on IBM 44P-170 - really close
German Poo Caaman~o [EMAIL PROTECTED] writes: El mar, 14-05-2002 a las 14:41, Rolf Brudeseth escribió: I believe I am really close to getting Debian working on an IBM 44P-170 workstation. I made a combined boot/root image. The kernel is 2.4.18 from kernel.org, while the root image is from Debian. I used the default power3 config file (power3_defconfig). Root image: http://ftp.debian.org/debian/dists/woody/main/disks-powerpc/current/chrp/root.bin ^ It's just missing the image-1.44/ ---| There are not such image. Anyway I'll try with the images on this directory. I have an IBM 44P-170 running Woody over SuSE. ttyl, -- Josh Huber | [EMAIL PROTECTED] | -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Woody installation on IBM 44P-170 - really close
German, Sorry, your correct. I have /images-1.44/ missing from the link. I was working way to late. http://ftp.debian.org/debian/dists/woody/main/disks-powerpc/current/chrp/images-1.44/root.bin Rolf -- Rolf Brudeseth pSeries System Engineering Integration, IBM Enterprise Systems Group Austin, TX, Phone: 512-838-6558, T/L: 678-6558 German Poo Caaman~o [EMAIL PROTECTED] on 05/15/2002 10:44:47 AM To:Rolf Brudeseth/Austin/IBM@IBMUS cc:[EMAIL PROTECTED], [EMAIL PROTECTED] Subject:Re: Woody installation on IBM 44P-170 - really close El mar, 14-05-2002 a las 14:41, Rolf Brudeseth escribió: I believe I am really close to getting Debian working on an IBM 44P-170 workstation. I made a combined boot/root image. The kernel is 2.4.18 from kernel.org, while the root image is from Debian. I used the default power3 config file (power3_defconfig). Root image: http://ftp.debian.org/debian/dists/woody/main/disks-powerpc/current/chrp/root.bin There are not such image. Anyway I'll try with the images on this directory. I have an IBM 44P-170 running Woody over SuSE. -- German Poo Caaman~o mailto:[EMAIL PROTECTED] http://www.ubiobio.cl/~gpoo/chilelindo.html -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Woody installation on IBM 44P-170 - really close
On Tue, May 14, 2002 at 01:41:54PM -0500, Rolf Brudeseth wrote:
I believe I am really close to getting Debian working on an IBM 44P-170
workstation.
I made a combined boot/root image. The kernel is 2.4.18 from kernel.org,
while the root image is from Debian. I used the default power3 config
file
(power3_defconfig).
Root image:
http://ftp.debian.org/debian/dists/woody/main/disks-powerpc/current/chrp/root.bin
No, I actually used:
http://ftp.debian.org/debian/dists/woody/main/disks-powerpc/current/chrp/images-1.44/root.bin
02-Apr-2002
I download the boot/root image from Open Firmware via BOOTP. It starts
up
the installation routine. I am able to successfully partition/format the
hard drive.
It'll be great if you can write up the steps required to get here.
Well, I was not planning to get into this yet, but since you brought up the
subject of documentation, here it comes.
I am soon going on vacation. I will be back June 13th. Then I plan to
submit bugs or post to the various Debian news groups where I will document
issues, suggestions, solutions, etc (if still unresolved), such as:
- It appears that powerpc Woody will be released with kernel 2.2 and not
2.4. I suspect that there is limited support for IBM CHRP/PREP systems in
the 2.2 kernel. I will investigate and document this.
- Apparently there is a bug in the version of glibc that Debian is using,
which will prevent Debian from running the 64 bit kernel on the IBM CHRP
systems. I will investigate and document this.
- Document requires patches for IBM CHRP/PREP systems.
- I am uncertain whether Debian has determined how to create bootable CDs
for IBM CHRP/PREP systems. I will investigate and document this.
- I will document how to perform an HTTP/FTP and NFS install on IBM
CHRP/PREP systems (after I figure it out).
- I will write up and submit README files for
'ftp.debian.org/debian/dists/woody/main/disks-powerpc/current/' that will
make things clearer for non-kernel/non-install hackers, like myself (see
below).
- Help out document how to create kernels and combined install/rescue
images for the various IBM CHRP/PREP systems that can be place in the
directory mentioned above.
- I will continuously document the IBM CHRP/PREP systems where I have been
able to successfully install Debian. I have access to pretty much all the
various RS6000/pSeries systems.
However, if I try to install via NFS I get the following error message:
Error mounting NFS filesystem, 'server:/path', please try again.
Does it literally say 'server:/path', indicating the variables are not
getting initialized? or is the path correct as far as you can see?
If you look in vc 3, is there another possibly more detailed error
message there?
No, I enter the correct server and path name. Aha, I assume the 'vc3' is an
error log application? I will try to use it to get better failure
information.
I know NFS is working, because I am able to mount from other systems.
If I try to install via HTTP/FTP it will successfully download
rescue.bin
and drivers.tgz; however I get the following error messages:
Unable to mount the Rescue Floppy.
The attempt to extract Rescue Floppy failed.
Installation of the file '/tmp/rescue.bin' failed.
Why is rescue.bin even required at this point?
boot-floppies never dropped the floppy terminology even when
they added new paths for installation. rescue.bin is the file
that contains the kernel; and the code looks for that file name.
I do not think that 'rescue.bin' contains a kernel. I believe it is only
the rescue root image. The reason I assume this, is because it is the same
size as the 'root.bin' file. When I created the combined install root/boot
image, I renamed 'root.bin' to 'ramdisk.image.gz' and copied it to the '
/usr/src/linux/arch/ppc/boot/images' directory, and then ran a 'make
zImage.initrd'.
I go the clue from the 'powermac' subdirectory. There you will find the
following symbolic link:
ramdisk.image.gz - images-1.44/root.bin
The 'http://ftp.debian.org/debian/dists/woody/main/disks-powerpc/current/'
directories could benefit from having a lot more README files. I will
document this and submit bugs or forward it to the mailing Debian powerpc
mailing list.
Are these known issues?
I just looked through the bug list, and indeed there is an nfs bug
#142267 in the current release. It was fixed by Matt Kraai and is
pending for the next release.
The extract thing sounds familiar to me too, but I can't place it.
The target is not an nfs share too? Thinking the other bug may be
causing this as secondary.
Do I need to submit a bug?
Is there a way I can work around the problem?
You could use wget within the installer to download rescue.bin and
drivers.tgz to your target manually, then point the installer there
for installation of kernel and drivers ('mounted partition').
They need to be arranged as:
powermac/drivers.tgz
powermac/images-1.44/rescue.bin
But maybe the vc3 error messages will give a
Re: Woody installation on IBM 44P-170 - really close
El mié, 15-05-2002 a las 12:53, Rolf Brudeseth escribió: On Tue, May 14, 2002 at 01:41:54PM -0500, Rolf Brudeseth wrote: I believe I am really close to getting Debian working on an IBM 44P-170 workstation. I made a combined boot/root image. The kernel is 2.4.18 from kernel.org, while the root image is from Debian. I used the default power3 config file (power3_defconfig). Root image: http://ftp.debian.org/debian/dists/woody/main/disks-powerpc/current/chrp/root.bin No, I actually used: http://ftp.debian.org/debian/dists/woody/main/disks-powerpc/current/chrp/images-1.44/root.bin 02-Apr-2002 I download the boot/root image from Open Firmware via BOOTP. It starts up the installation routine. I am able to successfully partition/format the hard drive. It'll be great if you can write up the steps required to get here. Well, I was not planning to get into this yet, but since you brought up the subject of documentation, here it comes. I am soon going on vacation. I will be back June 13th. Then I plan to submit bugs or post to the various Debian news groups where I will document issues, suggestions, solutions, etc (if still unresolved), such as: - It appears that powerpc Woody will be released with kernel 2.2 and not 2.4. I suspect that there is limited support for IBM CHRP/PREP systems in the 2.2 kernel. I will investigate and document this. - Apparently there is a bug in the version of glibc that Debian is using, which will prevent Debian from running the 64 bit kernel on the IBM CHRP systems. I will investigate and document this. If your refer to memset's problems, they were solve with glibc 2.1. In my experience, when I installed base files on a new partition on SuSE I downloaded base files from potato, chroot died when it needed libc6. With alien, I changed libc6-*-2.2.4 and nscd from unstable and all worked fine since then. AFAIK, the minimum glibc on Woody will be 2.2.4-4. -- German Poo Caaman~o mailto:[EMAIL PROTECTED] http://www.ubiobio.cl/~gpoo/chilelindo.html -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Woody installation on IBM 44P-170 - really close
It'll be great if you can write up the steps required to get here. Well, I was not planning to get into this yet, but since you brought up the subject of documentation, here it comes. I am soon going on vacation. I will be back June 13th. Then I plan to submit bugs or post to the various Debian news groups where I will document issues, suggestions, solutions, etc (if still unresolved), such as: - It appears that powerpc Woody will be released with kernel 2.2 and not 2.4. I suspect that there is limited support for IBM CHRP/PREP systems in the 2.2 kernel. I will investigate and document this. - Apparently there is a bug in the version of glibc that Debian is using, which will prevent Debian from running the 64 bit kernel on the IBM CHRP systems. I will investigate and document this. - Document requires patches for IBM CHRP/PREP systems. - I am uncertain whether Debian has determined how to create bootable CDs for IBM CHRP/PREP systems. I will investigate and document this. - I will document how to perform an HTTP/FTP and NFS install on IBM CHRP/PREP systems (after I figure it out). - I will write up and submit README files for 'ftp.debian.org/debian/dists/woody/main/disks-powerpc/current/' that will make things clearer for non-kernel/non-install hackers, like myself (see below). - Help out document how to create kernels and combined install/rescue images for the various IBM CHRP/PREP systems that can be place in the directory mentioned above. - I will continuously document the IBM CHRP/PREP systems where I have been able to successfully install Debian. I have access to pretty much all the various RS6000/pSeries systems. This sounds great! I'm happy to convert words into sgml if you'd like. I do not think that 'rescue.bin' contains a kernel. I believe it is only the rescue root image. The reason I assume this, is because it is the same size as the 'root.bin' file. When I created the combined install root/boot image, I renamed 'root.bin' to 'ramdisk.image.gz' and copied it to the ' /usr/src/linux/arch/ppc/boot/images' directory, and then ran a 'make zImage.initrd'. I go the clue from the 'powermac' subdirectory. There you will find the following symbolic link: ramdisk.image.gz - images-1.44/root.bin Yes, that's true, but rescue.bin is different. It's the kernel, gzipped and written to a floppy image. The 'http://ftp.debian.org/debian/dists/woody/main/disks-powerpc/current/' directories could benefit from having a lot more README files. I will document this and submit bugs or forward it to the mailing Debian powerpc mailing list. Cool! -- *--v- Installing Debian GNU/Linux 3.0 v--* | http://www.debian.org/releases/woody/installmanual | | debian-imac (potato): http://debian-imac.sourceforge.net | |Chris Tillman[EMAIL PROTECTED] | | May the Source be with you | ** -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Woody installation on IBM 44P-170 - really close
German, Actually, it is a very good question. It took me a while to figure out. However, you may not have seen the problem I am describing below. I set up an RS/6000 43P-150 running SuSE 7.3 as my BOOTP/tftp server: elas27:~ # cat /etc/bootptab elas23:\ ht=ethernet:\ ha=000629040055:\ bf=zImage.initrd.chrp-rs6k:\ ip=9.3.52.88:\ sm=255.255.255.224:\ bs=auto elas27:~ # ls -l /tftpboot -rwxr-xr-x1 rolfbusers 2689856 May 13 13:29 zImage.initrd.chrp-rs6k So why does this work? Should it not be: bf=/tftpboot/zImage.initrd.chrp-rs6k:\ Well, unlike other BOOTP server that I have used before, this one had /tftpboot hardcoded as root. Therefore, while I was investigating what I thought was an Open Firmware problem, I was really trying to boot from: /tftpboot/tftpboot/zImage.initrd.chrp-rs6k Then all you have to do on the target machine is to issue the following command from Open Firmware (console optional): 0 boot net console=ttyS0 I created the install boot/root image as follows: $ mv root.bin ramdisk.image.gz $ mv ramdisk.image.gz /usr/src/linux/arch/ppc/boot/images $ make zImage.initrd Rolf -- Rolf Brudeseth [EMAIL PROTECTED] pSeries System Engineering Integration, IBM Enterprise Systems Group Austin, TX, Phone: 512-838-6558 German Poo Caaman~o [EMAIL PROTECTED] on 05/15/2002 03:47:54 PM To:Rolf Brudeseth/Austin/IBM@IBMUS cc: Subject:Re: Woody installation on IBM 44P-170 - really close El mié, 15-05-2002 a las 12:53, Rolf Brudeseth escribió: On Tue, May 14, 2002 at 01:41:54PM -0500, Rolf Brudeseth wrote: I believe I am really close to getting Debian working on an IBM 44P-170 workstation. I made a combined boot/root image. The kernel is 2.4.18 from kernel.org, while the root image is from Debian. I used the default power3 config file (power3_defconfig). Root image: http://ftp.debian.org/debian/dists/woody/main/disks-powerpc/current/chrp/root.bin No, I actually used: http://ftp.debian.org/debian/dists/woody/main/disks-powerpc/current/chrp/images-1.44/root.bin 02-Apr-2002 I download the boot/root image from Open Firmware via BOOTP. It starts up the installation routine. I am able to successfully partition/format the hard drive. Excuse me if my question is stupid, but, how did you boot your machine? Thanks in advance, -- German Poo Caaman~o mailto:[EMAIL PROTECTED] http://www.ubiobio.cl/~gpoo/chilelindo.html -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Woody installation on IBM 44P-170 - really close
I believe I am really close to getting Debian working on an IBM 44P-170 workstation. I made a combined boot/root image. The kernel is 2.4.18 from kernel.org, while the root image is from Debian. I used the default power3 config file (power3_defconfig). Root image: http://ftp.debian.org/debian/dists/woody/main/disks-powerpc/current/chrp/root.bin 02-Apr-2002 I download the boot/root image from Open Firmware via BOOTP. It starts up the installation routine. I am able to successfully partition/format the hard drive. However, if I try to install via NFS I get the following error message: Error mounting NFS filesystem, 'server:/path', please try again. I know NFS is working, because I am able to mount from other systems. If I try to install via HTTP/FTP it will successfully download rescue.bin and drivers.tgz; however I get the following error messages: Unable to mount the Rescue Floppy. The attempt to extract Rescue Floppy failed. Installation of the file '/tmp/rescue.bin' failed. Why is rescue.bin even required at this point? Are these known issues? Do I need to submit a bug? Is there a way I can work around the problem? Any help will be appreciated. Rolf -- Rolf Brudeseth [EMAIL PROTECTED] pSeries System Engineering Integration, IBM Enterprise Systems Group Austin, TX, Phone: 512-838-6558 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Woody installation on IBM 44P-170 - really close
On Tue, May 14, 2002 at 01:41:54PM -0500, Rolf Brudeseth wrote:
I believe I am really close to getting Debian working on an IBM 44P-170
workstation.
I made a combined boot/root image. The kernel is 2.4.18 from kernel.org,
while the root image is from Debian. I used the default power3 config file
(power3_defconfig).
Root image:
http://ftp.debian.org/debian/dists/woody/main/disks-powerpc/current/chrp/root.bin
02-Apr-2002
I download the boot/root image from Open Firmware via BOOTP. It starts up
the installation routine. I am able to successfully partition/format the
hard drive.
It'll be great if you can write up the steps required to get here.
However, if I try to install via NFS I get the following error message:
Error mounting NFS filesystem, 'server:/path', please try again.
Does it literally say 'server:/path', indicating the variables are not
getting initialized? or is the path correct as far as you can see?
If you look in vc 3, is there another possibly more detailed error
message there?
I know NFS is working, because I am able to mount from other systems.
If I try to install via HTTP/FTP it will successfully download rescue.bin
and drivers.tgz; however I get the following error messages:
Unable to mount the Rescue Floppy.
The attempt to extract Rescue Floppy failed.
Installation of the file '/tmp/rescue.bin' failed.
Why is rescue.bin even required at this point?
boot-floppies never dropped the floppy terminology even when
they added new paths for installation. rescue.bin is the file
that contains the kernel; and the code looks for that file name.
Are these known issues?
I just looked through the bug list, and indeed there is an nfs bug
#142267 in the current release. It was fixed by Matt Kraai and is
pending for the next release.
The extract thing sounds familiar to me too, but I can't place it.
The target is not an nfs share too? Thinking the other bug may be
causing this as secondary.
Do I need to submit a bug?
Is there a way I can work around the problem?
You could use wget within the installer to download rescue.bin and
drivers.tgz to your target manually, then point the installer there
for installation of kernel and drivers ('mounted partition').
They need to be arranged as:
powermac/drivers.tgz
powermac/images-1.44/rescue.bin
But maybe the vc3 error messages will give a better clue what is
happening.
--
*--v- Installing Debian GNU/Linux 3.0 v--*
| http://www.debian.org/releases/woody/installmanual |
| debian-imac (potato): http://debian-imac.sourceforge.net |
|Chris Tillman[EMAIL PROTECTED] |
| May the Source be with you |
**
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
