Processed: block 749109 with 748679

2014-08-19 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> block 749109 with 748679
Bug #749109 [live-config] add broadcom-sta autodetection
749109 was not blocked by any bugs.
749109 was not blocking any bugs.
Added blocking bug(s) of 749109: 748679
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
749109: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=749109
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems


--
To UNSUBSCRIBE, email to debian-live-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
https://lists.debian.org/handler.s.c.14084438679919.transcr...@bugs.debian.org



Bug#749109: Bug#748679: Add autoconfiguration script for live-config

2014-08-19 Thread intrigeri
Hi Gaudenz,

meta:

 * I'm replying on #749109, as this part of the discussion is about
   code that's being added to live-config, not to broadcom-sta.
 * Daniel: sorry for the useless ping sent earlier this month on
   #748679, I was confused by the remaining tags left there
   after cloning.
 * I've tried to clarify the status of these two bug reports in the
   BTS, and the relationship between them, which seemed very confusing
   to me initially; sorry if I messed something up.

Gaudenz Steinlin wrote (12 Jun 2014 19:07:10 GMT) :
> - In some parts it looks like it should be a general wlan driver
>   selection mechanism. Which would be great, but then overrides are
>   stored in /usr/share/live/config/broadcom-sta/ and the script is
>   called 1190-broadcom-sta. 

I've seen broadcom-sta support requested quite often on the Tails user
support channels, while I don't remember anything similar for other
drivers, so I say let's get the ad-hoc support for broadcom-sta in
first, hopefully in time for Jessie, and then we'll see if/how it can
be generalized. Fair enough?

> - It uses 14e44 as a first filter in the script. While it's true that
>   the ID of all currently supported devices starts with this string, the
>   broadcom vendor ID is only 14e4. The last 4 is part of the device ID. 
> - The blacklisting logic is the wrong way around. If broadcom-sta is
>   selected as a driver, all entries in
>   /etc/modprobe.d/broadcom-sta-dkms.conf should be blacklisted. If it's
>   not selected, they should NOT be blacklisted. Additionally the wl
>   kernel module should be blacklisted in this case.
> - checking for a state file makes this script basically useless with
>   persistency on removable media. When moving to live media (ie USB
>   stick) from one system to another you want to rerun this script each
>   time. State files are nice for user preferences, but I don't see a use
>   case for them for hardware configuration.

Care to provide a patch that fixes these problems?

Cheers,
--
intrigeri


-- 
To UNSUBSCRIBE, email to debian-live-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/85zjf0933u@boum.org



Just a thank you

2014-08-19 Thread Zed
I wanted to thank the Debian-Live community for the assistance in 
building my first installable live-cd. I have learned a lot and am now 
building ISOs with the customized Debian-based distro I have wanted to 
build for a long time.


Now that I am starting to understand the ins and outs, I am looking 
forward to paying it back and helping the cause.


I plan on updating my github to reflect my changes in case anyone is 
interested today\tonight.  https://github.com/mrzed/

I will have two new repos:
lily-live-mate_64
lily-live-xfce4_64

These will be getting updated as I progress, but will work as-is once 
posted.


I found looking at others work to see how it was working assisted in 
deciphering many of my questions.


Special thanks to Anthony McInerney for sharing his git with me and 
getting me started.


Thank you again,

Zed (Devin)


--
To UNSUBSCRIBE, email to debian-live-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/53f3c5eb.9020...@lilypadmudlib.com



Re: Common bootloaders configuration thoughts

2014-08-19 Thread chals
On Sun, Aug 17, 2014 at 7:26 PM, adrian15  wrote:
> El 17/08/14 15:06, Daniel Baumann escribió:
>
>> On 08/17/2014 03:37 AM, adrian15 wrote:
>>>
>>> In one hand I want to be able to rename Debian Live distro into
>>> Something distro by just changing one variable. And at the same time I
>>> want that multi-live usb tools detect the iso as a Debian live so that
>>> they don't have to implement their code for each and everyone of the
>>> Debian derivatives.
>>
>>
>> lb is moving, albeit slowly, to that eventually, yes.
>
>
> I am mostly interested in renaming distro name, specially, at the bootloader
> stage.
>
> If I can help on any of these please tell me how would you go on how to
> implement it. I know how would I do it but I don't know every detail about
> live-build and, well,...
>



Hi Adrian,

On the one hand let me tell you that as far as I can tell, live-build
has been constantly evolving ever since its early inception. What is
more, it has to be constantly tweaked to work with every new release,
which after all, means constant evolution. This is to say, it is a
moving target (or at least that is my experience since I'm following
the project's development).

One of the aspects that live-build is more conscious of is about
derivative projects. live-build is a more and more derivative-friendly
tool which takes very seriously the need to debrand certain things as
much as possible. (For example, the new lb init tool includes the
--project option to cater for supported derivative projects).

> if Live-build has to be rewritten into python (Has this even started?) so...
> not sure if my contribution would be worth.
>

Yes, some scripts (mainly the bootstrap related ones) have already
been re-written into python by Daniel. My perception of it is that
this is an ongoing process, which will take a certain amount of time
and some really hard work but it will eventually be worth it.

On a personal note: I know you are a grub expert. This makes you the
right person for the job. I'm very happy you finally decided to
implement grub support for such an awesome project as debian live is.

And last but not least, the most important thing is that your
contribution is really worth the time and effort you put in.

Have a nice summer holiday!


-- 
chals
www.chalsattack.com
ch...@chalsattack.com


--
To UNSUBSCRIBE, email to debian-live-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
https://lists.debian.org/cajrhvajezqmzfa+umg+5k1mzjzfzbfp-5roomv0gh0sva...@mail.gmail.com