From: Horst von Brand <vonbrand@sleipnir.valparaiso.cl>
To: Riley Williams <rhw@MemAlpha.CX>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: 2.2.X patch query
Date: Mon, 30 Oct 2000 23:29:12 -0300 [thread overview]
Message-ID: <200010310229.e9V2TCF29473@sleipnir.valparaiso.cl> (raw)
In-Reply-To: Message from Riley Williams <rhw@MemAlpha.CX> of "Mon, 30 Oct 2000 20:01:32 -0000." <Pine.LNX.4.10.10010301935480.10495-100000@infradead.org>
Riley Williams <rhw@MemAlpha.CX> said:
[...]
> Before I go any further with this, I would like to ask a few questions
> relating to it:
>
> 1. Is there any likelihood of this making it into the official
> kernel, or am I just wasting my time?
Depends, I'd say... perhaps after a long shakeout and much use.
> 2. Would I be right in thinking it's too late for either the
> 2.2 or 2.4 kernels ???
No way.
> Assuming it'd be of interest to Linus and yourself...
[...]
> 5. I was wondering about providing some means of selecting
> whether to dump to /dev/fd0 or /dev/fd1 (or others if
> present). What would be your opinion on this?
Keep it as simple as possible. I'd leave the option open if not hard, but
not implement it at all at first.
> 6. A while back, I developed a high-level floppy formatter
> that produces a non-standard DOS-compatible format that
> allows 1436k of data on a 1440k floppy, and produced a
> bash script that would produce disks formatted in this
> format.
>
> My current plans are for SYSRQ-D to raw write direct to
> /dev/fd0 and effectively reformat the disks in this
> format, dropping the log file thereon in the process. I
> don't plan on doing the low-level format, just the
> high-level one.
KISS, again. What use is a non-standard 1436Kb DOS format when writing at
most 1Mb? I'd just dump it raw to /dev/fd0, whoever wants to read it later
will have all kinds of tools at hand.
Remember:
- Bloat
- This will have to work even in a thoroughly hosed system to be of any use
--
Horst von Brand vonbrand@sleipnir.valparaiso.cl
Casilla 9G, Vin~a del Mar, Chile +56 32 672616
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2000-10-31 2:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-10-30 20:01 2.2.X patch query Riley Williams
2000-10-30 21:08 ` Andreas Dilger
2000-10-31 2:29 ` Horst von Brand [this message]
2000-10-31 13:38 ` 2.2.X patch query (with initial PATCH against 2.2.17) Riley Williams
2000-10-31 14:20 ` Dominik Kubla
2000-10-31 19:38 ` Horst von Brand
2000-10-31 20:22 ` Andreas Dilger
2000-11-03 17:23 ` Riley Williams
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=200010310229.e9V2TCF29473@sleipnir.valparaiso.cl \
--to=vonbrand@sleipnir.valparaiso.cl \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=rhw@MemAlpha.CX \
/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