[KLUG Members] New SuSE installation
Mike Williams
members@kalamazoolinux.org
Wed, 17 Jul 2002 17:08:12 -0400
On Wed, 17 Jul 2002 12:00:01 -0400,
members-request@kalamazoolinux.org wrote:
>> I have an old (sortof) installation of SuSE 7.1 that I use a house
server.
>>I would like to update everything, which YAST2 (the config / update
>>tool) won't do except as individual packages. I have downloaded an
ISO
>>of the boot disk for SuSE 8.0, which will supposedly boot then get
the
>>remaining files from an FTP server, but this doesn't work.
Networking
>>starts, but it can't connect to the FTP server even though TCP/IP
>>settings are correct.
>
>Can't help much there without more specifics. Can you capture
traffic
>from another box with something like ethereal and see if it is even
>trying, etc....
------------begin tcpdump----------------
Here's a complete tcpdump from one of the failed attempts. Looks to
me like it's making some kind of attempt, but I can't decipher much
more than that.
16:05:37.301854 10.0.0.14.1026 > ftp.suse.com.ftp: S [ECN-Echo,CWR]
4245204564:4
16:05:40.301358 10.0.0.14.1026 > ftp.suse.com.ftp: S [ECN-Echo,CWR]
4245204564:4
16:05:42.301382 arp who-has router.local tell 10.0.0.14
16:05:42.304541 arp reply router.local is-at 0:a0:c5:e0:45:d
(0:a0:c9:8d:4a:1e)
16:05:46.301549 10.0.0.14.1026 > ftp.suse.com.ftp: S [ECN-Echo,CWR]
4245204564:4
16:05:58.301964 10.0.0.14.1026 > ftp.suse.com.ftp: S [ECN-Echo,CWR]
4245204564:4
16:06:22.302763 10.0.0.14.1026 > ftp.suse.com.ftp: S [ECN-Echo,CWR]
4245204564:4
16:07:10.304395 10.0.0.14.1026 > ftp.suse.com.ftp: S [ECN-Echo,CWR]
4245204564:4
16:07:15.304523 arp who-has router.local tell 10.0.0.14
16:07:15.307204 arp reply router.local is-at 0:a0:c5:e0:45:d
(0:a0:c9:8d:4a:1e)
-------------end tcpdump-------- sorry about the ugly formatting
>>I've also considered converting to Redhat since it seems to do a
better job
>> of updating an existing installation.
---------snip-----------
>>I have 3 CD's of Redhat 7.3,
>>but seem to be running into partition table problems. (This is on
a
>>different machine so I don't kill a production box.) On most
attempts
>>it takes 10 minutes or so for each partitioning operation (even
>>opening the FDISK screen), and at the end it gives a critical
failure
>
>Can you post the exact message?
Well, while trying to collect error messages I got it to work.
Default install failed with the helpful message "Could not allocate
partitions", but Disk Druid seems to be managing. Looks like the
gremlins ran when they saw I was taking notes.
--
Mike Williams, knightperson@zuzax.com on 07/17/2002