From: "Marc Groeneveld" <mgroeneveld@svb.nl>
To: <blinux-list@redhat.com>
Subject: Re: Thanks, and I still need help!
Date: Fri, 3 Jul 1998 10:13:43 +0200 [thread overview]
Message-ID: <08124680300095@svb.nl> (raw)
Hi,
Making an ext2 filesystem on a zip disk is no problem.
No side effects.
Marc.
----------
> Van: Luke Davis <ldavis@voicenet.com>
> Aan: blinux-list@redhat.com; General Linux Discussion List
<LINUX-L@mana.landofhaze.com>
> Onderwerp: Thanks, and I still need help!
> Datum: vrijdag 3 juli 1998 7:17
>
> Houdy!
>
> First of all: thanks to all of those who gave me advice on my ZIP drive
> problems of a couple weeks ago...
>
> Eventhough kernels will not successfully build on this system,
> remaking/insting the modules apparently did the trick.
>
> mount -tmsdos /dev/hdb1 # or hdb4
>
> Is what now works.
>
> Q: Has anyone ever tried creating a linux-compatable filesystem on an
> existing zipdisk partition (over top of a dos format)?
> Q: If so: were there any bad effects?
>
> Now:
>
> Weather before or after boot is complete, I still need a method for
> redirecting the console to something other than the console: weather it
be
> a local /dev device, or some network device.
>
> I plan to be using systems in which noone will have access to the
console,
> and therefore I have to have quick access to what ever is comming on the
> console (I can probably count on syslog-ish processes to give me most of
> it, but...).
>
> Does anyone have any idea on this?
>
> Luke
>
> ---
> Send your message for blinux-list to blinux-list@redhat.com
> Blinux software archive at ftp://leb.net/pub/blinux
> Blinux web page at http://leb.net/blinux
> To unsubscribe send mail to blinux-list-request@redhat.com
> with subject line: unsubscribe
next reply other threads:[~ UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
Marc Groeneveld [this message]
-- strict thread matches above, loose matches on Subject: below --
Luke Davis
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=08124680300095@svb.nl \
--to=mgroeneveld@svb.nl \
--cc=blinux-list@redhat.com \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).