From: "Brad House" <brad_mssw@gentoo.org>
To: "Martin Schlemmer" <azarah@gentoo.org>
Cc: gentoo-releng@lists.gentoo.org,
"Gentoo-Base-System" <base-system@gentoo.org>
Subject: Re: [gentoo-releng] x86-livecd - bugs and suggestions
Date: Fri, 23 Jan 2004 16:38:55 -0500 (EST) [thread overview]
Message-ID: <39574.209.251.159.140.1074893935.squirrel@mail.mainstreetsoftworks.com> (raw)
In-Reply-To: <1074892646.7514.25.camel@nosferatu.lan>
>> This is not an issue if you use cdfs/loop type of zisofs or noloop
>> as there is no loop device to be umounted.
>>
>
> Ok, I changed things a bit, so might have expected I guess. I do
> however have an issue with the naming. Some time ago it was decided
> that it should be /mnt/livecd. Now it changed again. Can we decide
> on something now? If so, fix is easy.
>
Well, it's mounting to /mnt/loop right now. I had no idea there was
a current naming convention (I did not have access to the prior 2.4
kernel livecd scripts that did any sort of loop mounting). This would be
an easy change to make to whatever you want it to be, as it's just a
couple of lines in the genkernel linuxrc that need to be changed, just
let me know, as I needed to roll another genkernel that had some
fixes people posted in bugs.gentoo.org (along with some suggested
doc changes), before I totally abandon that project (as previously
discussed).
-Brad
brad_mssw@gentoo.org
--
gentoo-releng@gentoo.org mailing list
next prev parent reply other threads:[~2004-01-23 21:39 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-23 15:04 [gentoo-releng] x86-livecd - bugs and suggestions Benjamin Judas
2004-01-23 17:16 ` Martin Schlemmer
[not found] ` <1074880273.20419.15.camel@antares.hausnetz>
2004-01-23 18:01 ` Martin Schlemmer
[not found] ` <1074883714.20415.29.camel@antares.hausnetz>
2004-01-24 16:38 ` Martin Schlemmer
2004-01-24 16:40 ` Martin Schlemmer
2004-01-24 22:51 ` Benjamin Judas
2004-01-25 6:26 ` Martin Schlemmer
2004-01-25 8:20 ` Brad House
2004-01-25 11:17 ` Martin Schlemmer
2004-01-25 15:52 ` Brad House
2004-01-25 16:11 ` Martin Schlemmer
2004-01-25 16:23 ` Brad House
2004-01-25 16:14 ` Martin Schlemmer
2004-01-25 16:24 ` Brad House
2004-01-25 16:17 ` Martin Schlemmer
2004-01-25 16:29 ` Brad House
2004-01-26 17:50 ` Martin Schlemmer
2004-01-26 18:02 ` Brad House
2004-01-26 18:14 ` Martin Schlemmer
2004-01-26 18:49 ` Brad House
2004-01-27 17:13 ` Martin Schlemmer
[not found] ` <1075311848.9415.1.camel@nosferatu.lan>
2004-01-28 18:09 ` Brad House
2004-01-29 17:19 ` Benjamin Judas
2004-01-29 18:42 ` Martin Schlemmer
2004-02-02 4:36 ` Brad House
2004-02-02 4:48 ` Brad House
2004-01-23 18:43 ` Brad House
2004-01-23 21:17 ` Martin Schlemmer
2004-01-23 21:38 ` Brad House [this message]
2004-01-23 22:26 ` Martin Schlemmer
2004-01-23 23:55 ` Daniel Robbins
2004-01-24 16:40 ` Martin Schlemmer
2004-01-24 21:01 ` Daniel Robbins
-- strict thread matches above, loose matches on Subject: below --
2004-02-02 4:48 Brad House
2004-02-02 19:37 ` Martin Schlemmer
2004-02-02 19:54 ` Brad House
2004-02-02 20:51 ` Martin Schlemmer
[not found] ` <1075755072.6931.82.camel@nosferatu.lan>
2004-02-02 21:17 ` Brad House
2004-02-02 21:46 ` Martin Schlemmer
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=39574.209.251.159.140.1074893935.squirrel@mail.mainstreetsoftworks.com \
--to=brad_mssw@gentoo.org \
--cc=azarah@gentoo.org \
--cc=base-system@gentoo.org \
--cc=gentoo-releng@lists.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