From: Mike Frysinger <vapier@gentoo.org>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] RE:Boot floppies
Date: Sat, 26 Jul 2003 14:29:44 -0400 [thread overview]
Message-ID: <200307261429.48944.vapier@gentoo.org> (raw)
In-Reply-To: <1059226798.24874.16.camel@vertigo>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Saturday 26 July 2003 09:39, Chris Gianelloni wrote:
> On Sat, 2003-07-26 at 05:16, C. Brewer wrote:
> > So if this was the case, why a 2.6 kernel? You could do it with a 2.2 or
> > 2.4 oldschool style,
>
> Hardware support. Though I think one could get away easily with a 2.4
> kernel. I see no reason creating an "official" bootdisk with a beta
> kernel.
i was saying that we'd be forcing a kernel on you ... kernel settings are in
the air ... but in the end you'd probably be able to choose kernel/modules
yourself ala slackware style ...
the trouble i'm having (and the reason i sent this mail) is getting
bootloaders working ;) i fixed the zero-ing of ramdisks by using loopback,
but now when i try to grub/lilo a loopback device, it (obviously) complains
it doesnt know anything about a loopback device. anyone ever try this kind
of thing before ? the idea is to produce the final image w/out ever actually
writing/reading to a floppy for (1) speed and (2) no worries of errors.
- -mike
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (GNU/Linux)
iQIVAwUBPyLImEFjO5/oN/WBAQLEMxAAnDkSBSFrklpuCihOLipSTqTmLaLU9mp6
HewrgGvdPYpSCvlpCwJntswNiFnwtIJTdcxfty40SU+Wfk72TYtauEfTWhowkDrq
P5J1mHogwg6tfWWMrwHReW2M7/qduSAmfZ0+A0LKpnhyuKP4AFKJ/aKRtT7dXzNA
CwcaVAy5ycH032sT/o9aCcRCPl7fl62QJ2h/g4BjYunePoxwip5oXUrBGx6KW8ql
NX31zxj/59i3f84C5EgyBOtim5CqPOLOwesQjTbZUHa1yBV5g8T7x9Dl2krE5yJq
GaPfs2Y/hW8srimUnIbMuMzcVSCCXkNneYubhnkLcJo/BkWWpBowGDWR4kbY4trP
5Y5bm0F4jyHHoM1qUywDhxKZaV/O/fnYN05s/TGiJKCp669fEpqFTRDqOvGaGRz7
y4qKT/mlsjBNvr4pZgJVAyXGN05FuZ3+UqPWspri5sorW1ygFvdIXdk5Dk6cEXWy
Dbfqf5GOTt+Xfb1ugF8d+XcVlVzscPoPh9OIZ14BAcSLXhcuzClCopSHcSjMqxcy
g60y4dP5xNcAD7Q0PwPXGT+P/znIlRUOfPGcnOtRzaeJeZB129PGSgX6UiirLU/H
YPc6Bcm1I7leuCKDAhEivgimAtrVAfXRCsvBaZfCpkQyUpOipc0QyKHs0cWeF4qW
GSTpXBPrVr8=
=vB7V
-----END PGP SIGNATURE-----
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2003-07-26 18:29 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-25 18:52 [gentoo-dev] RE:Boot floppies C. Brewer
2003-07-25 19:14 ` Don Seiler
2003-07-25 19:55 ` Chris Gianelloni
2003-07-25 20:27 ` Don Seiler
2003-07-25 22:48 ` Mike Frysinger
2003-07-26 14:02 ` Christian Birchinger
2003-07-28 16:53 ` Michael Andrews
2003-07-28 18:11 ` Chris Gianelloni
2003-07-29 12:43 ` Stuart Herbert
2003-07-29 13:02 ` Chris Gianelloni
2003-07-29 13:26 ` Stuart Herbert
2003-07-29 16:15 ` Chris Gianelloni
2003-07-29 17:52 ` Stuart Herbert
2003-07-29 19:14 ` Chris Gianelloni
2003-08-03 0:17 ` Chris Gianelloni
2003-08-03 0:11 ` [gentoo-dev] Re: [gentoo-core] " Stuart Herbert
2003-08-03 0:31 ` Chris Gianelloni
2003-07-26 18:33 ` Don Seiler
2003-07-25 22:57 ` Mike Frysinger
2003-07-25 22:43 ` Mike Frysinger
2003-07-25 23:09 ` Terje Kvernes
2003-07-26 9:16 ` C. Brewer
2003-07-26 13:39 ` Chris Gianelloni
2003-07-26 18:29 ` Mike Frysinger [this message]
2003-07-26 18:52 ` Chris Gianelloni
2003-07-26 19:55 ` Paul de Vrieze
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=200307261429.48944.vapier@gentoo.org \
--to=vapier@gentoo.org \
--cc=gentoo-dev@gentoo.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