From: Mario Lang <mlang@teleweb.at>
To: blinux-list@redhat.com
Subject: Re: woody root.bin
Date: Fri, 05 Jul 2002 21:00:22 +0200 [thread overview]
Message-ID: <874rfegfuh.fsf@lexx.delysid.org> (raw)
In-Reply-To: <Pine.LNX.4.44.0207050112130.507-100000@maranatha.chartermi.net> (Cheryl Homiak's message of "Fri, 5 Jul 2002 09:25:03 -0500 (CDT)")
Cheryl Homiak <chomiak@chartermi.net> writes:
> 3. I did my tar command for the brlttydisk as follows:
> tar cvpf brlttydisk.tar *
> I think using the "f" and the filename is actually the proper way to use tar
> rather than using a 'greater than" sign, though I imagine that works too.
redirection works the same as the f argument works, its really just a
matter of taste.
well, maybe if you use eshell, or some other strangely implemented
shell variant, but ash shouldn't present a performance problem I think.
> 8. Per the comment that was made re: the new installer system coming down the
> pike where hacking bootdisks may not be of help, those of us involved in debian
> might want to get some fingers in that pie so that brltty users don't get
> locked
> out of being able to install debian with brltty in the future. It's too easy to
> get left in the position of complaining after the fact about something that
> might have been forseen and dealt with before the fact.
I successfully built the debian-installer floppies already.
They are far from usable for installation right now, but I'm
slowly progressing... As soon as I have something useable/testable in
this direction, I'll tell.
--
CYa,
Mario
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
Boris DAIX
` Mario Lang
` Boris DAIX
` Andor Demarteau
` Boris DAIX
` Mario Lang
` Mario Lang
` Boris DAIX
` Cheryl Homiak
` Boris DAIX
` Cheryl Homiak
` woody root.bin: update on installation attempt Cheryl Homiak
` Mario Lang [this message]
` woody root.bin Nath
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=874rfegfuh.fsf@lexx.delysid.org \
--to=mlang@teleweb.at \
--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).