Linux-Misc Digest #854, Volume #25 Sun, 24 Sep 00 00:13:02 EDT
Contents:
Re: Win98+Linux+FreeBSD all on boot drive? ("Jason Byrne")
wu-ftpd went SLOW after upgrade :( (User Name)
----------------------------------------------------------------------------
From: "Jason Byrne" <[EMAIL PROTECTED]>
Crossposted-To: comp.unix.bsd.freebsd.misc
Subject: Re: Win98+Linux+FreeBSD all on boot drive?
Date: Sat, 23 Sep 2000 20:58:57 -0700
I was considering limiting the reply to one or two groups... but I think
it's all in context for the cross-posting.
"David Efflandt" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]...
> Just wondering if anyone succeeded in putting Win98+Linux+FreeBSD all on
> one very large boot (27GB) drive? Booting to Linux anywhere on the drive
> is no problem using a small /boot partition first, then Win98. My first
> attempt at putting FreeBSD 4.0 after Linux taught me that FreeBSD will not
> boot beyond the 1024 cyl limit.
>
> Ok, so I dropped the FAT32 partition to under 8GB followed by the bsd
> slice with / ending < cyl 1024 and FreeBSD was able to boot. As an
> experiment I then tried creating an extended partition with a FAT32
> logical and it overlapped and wiped out FreeBSD. The Linux+FreeBSD
> mini-HOWTO said Linux install kernels don't usually have UFS support, and
> would probably do the same thing, So I bought another drive for FreeBSD
> and backup. But I still wonder if this would have been possible?
>
> I may still try Win98+Linux+FreeBSD on my laptop, since it would be easy
> to keep / below cyl 1024, even near the end of a 1099 cyl drive.
> Although, fdisk UFS support in RH 6.1 seems unable to read disklabels of
> slices that run beyond the 1024 cyl boundary for some reason.
I would put Win98 on a primary partition large enough to allow for growth of
Win98... and just leave it as the system disk (don't plan on installing
bunches of software - you'll create another FAT32 partition later)
After this... the main issue is getting /boot (primary) partitions set up
for FreeBSD and Linux. Actually
finishing the Linux and FreeBSD installs just takes a bit of patience.
Given a choice on method... I would start the Linux install only to the
point of creating partitions... and create the two primary partions that
will be /boot for FreeBSD and Linux (two separate partitions)
>From a Linux perspective... either fdisk?, cfdisk, or SuSE's more graphical
partitioning tools (and others?) are smart enough to let you create multiple
primary partitions - DiskDruid won't help if you happen to be using RedHat.
(just quit the Linux install after writing the new partition table)
Then I would start the FreeBSD install... and set up one of the primaries
you just created as /boot... and create an extended partition to fill the
rest of the drive... *but* don't actually use the entire drive on logical
partitions. Leave some unpartitioned space that you plan to use for Linux
(and win98?). Create everything you need for FreeBSD and finish the
install...
At this point... you have used up your primary partition limit - 1 for Win98
C: drive, 1 for Linux /boot, 1 for FreeBSD /boot, and the last one as a
container for the extended partition w/logical drives.
Finally... go back to installing Linux and create logical partitions (for
Linux and win98) in the remainder of the free space in the extended
partition... and finish the Linux install.
Last thing would be to boot to Windows and format the logical drive you set
up for FAT32 space.
The basic approach is to put your FreeBSD and Linux boot partitions
somewhere in the middle of your drive... well below the 1024 cylinder limit.
in the short term... I would suggest making boot floppies... and then
committing to a LILO (or FreeBSD boot manager?) later. I like to just make
the Linux /boot partition active and avoid the MBR... but I'm sure you could
work out a number of boot methods.
I think I said all of this correctly ;-) I might verify this later after I
grab a bite to eat...
good luck...
- Jason
>
> --
> David Efflandt [EMAIL PROTECTED] http://www.de-srv.com/
> http://www.autox.chicago.il.us/ http://www.berniesfloral.net/
> http://hammer.prohosting.com/~cgi-wiz/ http://cgi-help.virtualave.net/
>
------------------------------
From: User Name <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.networking
Subject: wu-ftpd went SLOW after upgrade :(
Date: Sun, 24 Sep 2000 03:50:26 GMT
Hi all,
I have RH6.0 running kernel 2.2.14-12. After reading some security
bulletins regarding older versions of wu-ftpd, I decided it would be
best to upgrade. So I downloaded the RPM and upgraded to wu-ftpd
2.6.0-14 (June 23 2000 build).
Now, FTP is unusable. Most of the time, WS_FTP on Windows gives an error
"Blocking call received" and the connection to the linux box fails
altogether. If I do manage to connect, it takes almost a minute for the
connection to happen, then transfers take place at less than 1K/sec. I'm
on a 10/100 LAN and used to get around 1MB/sec with FTP.
Other services are working fine. I can download a file from the linux
box over http and it comes zooming in. So it's not a hardware problem,
it's definitely something with wu-ftpd.
Any solutions?
TIA
------------------------------
** FOR YOUR REFERENCE **
The service address, to which questions about the list itself and requests
to be added to or deleted from it should be directed, is:
Internet: [EMAIL PROTECTED]
You can send mail to the entire list (and comp.os.linux.misc) via:
Internet: [EMAIL PROTECTED]
Linux may be obtained via one of these FTP sites:
ftp.funet.fi pub/Linux
tsx-11.mit.edu pub/linux
sunsite.unc.edu pub/Linux
End of Linux-Misc Digest
******************************
