From: Wakko Warner <wakko@animx.eu.org>
To: Alex Davis <alex14641@yahoo.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Let's get rid of ide-scsi
Date: Fri, 10 Feb 2006 07:08:02 -0500 [thread overview]
Message-ID: <20060210120801.GB27814@animx.eu.org> (raw)
In-Reply-To: <20060210060333.8628.qmail@web50212.mail.yahoo.com>
Alex Davis wrote:
> --- Wakko Warner <wakko@animx.eu.org> wrote:
> > I personally do not agree with this. I worked on at boot disk(floppy) which
> > contained the kernel and modules to find a cdrom (or usb disk) and use it as
> > my 2nd stage. If I had to use ide-cd, I would not beable to do my first
> > stage loader on a single floppy (I support ide and scsi cdroms via sr-mod).
> >
> > ide-cd.ko is > than sr-mod.ko + ide-scsi.ko
> >
> > I am aware that scsi_mod.ko is larger than those 3 combined and I still need
> > it regardless for usb.
> >
> > My personal vote would be to drop the entire ide subsystem which would thus
> > drop ide-scsi. The SCSI layer has been a general block device layer for
> > more than true scsi devices. USB, Firewire, and SATA use the scsi layer.
> > And as I understand it, libata is starting to handle PATA devices. Once it
> > can handle PATA fine, the ide code would pretty much be useless.
> >
> > I am also against the seperate USB block layer, I personally saw no use in
> > it.
> >
> > --
> > Lab tests show that use of micro$oft causes cancer in lab animals
> > Got Gas???
> >
>
> Wakko:
>
> Modules can be compressed: On a 2.6.15 kernel doing a 'gzip -9 idecd.ko' reduced its size
> from 43616 bytes to 19234 bytes. The only additional step is modifying 'modules.dep' and
> changing idecd.ko to idecd.ko.gz. You now have a fully functional ide cdrom driver.
This I did not know. I'm not sure if it will really matter or not. The
initramfs is already gzip -9'd. I have a list of modules that are required
for stage 1 which pulls in the dependancies for those modules. It does
currently fit on a single floppy. I'm using a upx compressed kernel, a gzip
-9'd initramfs, kernel is compiled with -Os and I'm using a -Os compiled
busybox statically compiled with uclibc. When it's all said and done, I
have less than 10kb available on a floppy. I thought it was quite an
acomplishment getting all that one 1 floppy.
--
Lab tests show that use of micro$oft causes cancer in lab animals
Got Gas???
next prev parent reply other threads:[~2006-02-10 12:04 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-10 0:21 Alex Davis
2006-02-10 0:36 ` Wakko Warner
2006-02-10 5:24 ` Greg KH
2006-02-10 5:35 ` Joshua Kwan
2006-02-10 12:11 ` Wakko Warner
2006-02-10 16:31 ` Greg KH
2006-02-10 17:31 ` Wakko Warner
2006-02-10 18:12 ` Alan Cox
2006-02-10 6:03 ` Alex Davis
2006-02-10 12:08 ` Wakko Warner [this message]
2006-02-10 16:09 ` Alan Cox
2006-02-10 21:30 ` Bill Davidsen
[not found] <mailman.1139533140.4060.linux-kernel2news@redhat.com>
2006-02-10 19:23 ` Pete Zaitcev
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20060210120801.GB27814@animx.eu.org \
--to=wakko@animx.eu.org \
--cc=alex14641@yahoo.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®