Author: quidame Date: To: The Tails public development discussion list Subject: [Tails-dev] Fwd: Re: Help needed with branch
bugfix/writable_boot_media
Oops again,
I had selected the 'Reply' button... sorry for the noise
quidame
-------- Original Message --------
Subject: Re: [Tails-dev] Help needed with branch bugfix/writable_boot_media
Date: Mon, 10 Jun 2013 21:02:05 +0200
From: quidame <quidame@???>
To: intrigeri <intrigeri@???>
Oops...
On 10/06/2013 18:25, intrigeri wrote: > [...]
> I'll give it a try ASAP, and will get back to you if I need help.
> Thanks for the offer :)
the "first draft on the fly" effectively was a draft. Don't rely on it.
The filesystem labeled 'TailsData' is on a dm device; so the rule about
this device has no chance to be applied where I have placed it. For your
first test, I suggest instead to keep 99-hide-TailsData.rules as is, and
just add another rules file (i.e. the first draft without the TailsData
specific rule). You can give it any name between 62*.rules and 99*.rules.
>> Another possibility could be to kill bilibop-udev and replace it by
>> bilibop-live, with live-specific additional stuff (but this is not done).
>
> This sounds useful, but I suggest we start with the solution described
> above; then if we're happy with it, we can consider generalizing it,
> and making it available to all Debian Live users. But well, if you
> feel confident enough to work on a bilibop-live package on the short
> term, I certainly don't meant to discourage you.
Not on the short term. The next thing I plan to modify in bilibop is to
add debconf support to bilibop-rules. It will be enough...
