[SOLVED] (was: Help! dh_build eats my binary.img!)

2008-09-29 Thread tomas
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On Sun, Sep 28, 2008 at 08:37:43PM +0100, Chris Lamb wrote:
 [EMAIL PROTECTED] wrote:
 
   | /usr/bin/lh_binary_usb-hdd: line 114: losetup.orig: command not found

[...]
  - loop-aes-utils (and maybe others) use dpkg-divert to take control

It worked! Installing loop-aes-utils did the trick (of course I could as
well have linked losetup to losetup.orig). Thanks again. I owe you a
$BEVERAGE :-)

BTW: what does the default: autodetected in config/common mean? Would
this have worked in my case? Hm. Maybe this is the effect of running
lh_config over an existing configuration? (I dont't remember putting
this LH_LOSETUP=losetup.orig in there).

Regards
- -- tomás
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFI4HJ/Bcgs9XrR2kYRAqVRAJ0TPH5brgfTrBgJvlqAk6F0VORYRQCeJ5wp
ZQLvzEw93XjstztQAQgRqLU=
=YL2P
-END PGP SIGNATURE-


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Re: [SOLVED] (was: Help! dh_build eats my binary.img!)

2008-09-29 Thread Chris Lamb
[EMAIL PROTECTED] wrote:

 Thus, autodetected means autodetected at lh_config time, right?

Yes. 

You removed whatever was diverting /sbin/losetup since you called
lh_config the first time.


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  [EMAIL PROTECTED]
   `-


signature.asc
Description: PGP signature


ArtistX 0.6 question: rewrite wiki and manual

2008-09-29 Thread Marco Ghirlanda

Hi All,
I'm in the process of building the new ArtistX ( www.artistx.org ) and 
would like to use DL as for the last 5 versions :-) (as always I will 
add a reference to DL in the Distrowatch announcement and on the ArtistX 
website to give DL the maximum credit). Long time ago I made a tutorial 
(which is now in the Wiki under unsupported) and I would like to 
update it as DL has changed a bit over the last two years...:-)


My usual steps

1) lh_config and change config/ files by hand (setting only boot 
parameters to make splashy work and enabling the interactive build)
2) during interactive build add packages and graphic customization 
(basically I create a empty iso with the same Kde/Gnome, save home dir 
and copy to /etc/skel the relevant files + change isolinux splash pic + 
wallpaper in /usr/share/images/desktop-base and splashy background in 
/etc/splashy/themes)


I understand now how to use the include files using 
binary_local-includes/ and chroot_local-includes/ but:


1) how to use external apt sources and make sure they will go into the 
final iso? Need to add only debian-multimedia.org packages.
2) how to add the user artistx to various groups for making effective 
the installation of software like ntfs3g or other packages that require 
that the user is added to groups he is not part of.
3) how to test and include the new live installer (should I put the live 
installer udeb into binary_local-udebs/ ?)
I'm willing to write all your answers in the wiki in the tutorial and 
help to write relevant section of the manual about these topics so 
nobody should ask again to build his custom Debian.


I would strongly recommend to include graphic customizations, groups 
management and the installer as options of Live Magic. In that way it 
would become more like the Reconstructor GUI ( 
http://reconstructor.aperantis.com ) and spread DL also between 
non-technical people. I would be the first tester!


Best regards,

Marco Ghirlanda


Re: ArtistX 0.6 question: rewrite wiki and manual

2008-09-29 Thread tomas
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On Mon, Sep 29, 2008 at 10:41:19AM +0200, Marco Ghirlanda wrote:
 Hi All,
 I'm in the process of building the new ArtistX [...]

 1) how to use external apt sources and make sure they will go into the 
 final iso? Need to add only debian-multimedia.org packages.

As far as I understand, that's what the settings LH_MIRROR_* in
config/bootstrap are for:

  LH_MIRROR_BOOTSTRAP # to bootstrap the build

  LH_MIRROR_CHROOT
  LH_MIRROR_CHROOT_SECURITY # to acutally load the packages during build

  LH_MIRROR_BINARY
  LH_MIRROR_BINARY_SECURITY # what the built system refers to (i.e. its
# sources.list)

Please someone correct me if I'm way off :-)

 2) how to add the user artistx to various groups for making effective the 
 installation of software like ntfs3g or other packages that require that 
 the user is added to groups he is not part of.

The live user gets added at boot time of the live system (*not* at build
time). This surprised me too :-)

So to add it to some groups, you'll have to hook into that. Possibly
you'll have to (programmatically) modify the adduser script in the
target's system initramfs, as in the second recipe in the FAQ:

  
http://wiki.debian.org/DebianLive/FAQ#head-5bb88fb88b407750f2f8ca0c02ca59b18e163bca

Looks a bit scary ;-)

Maybe some hook script would be nice here? Why is the live user
generated so late in the process (i.e. at boot time instead of at build
time)?

Don't know about your third question.

Regards
- -- tomás
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFI4J4xBcgs9XrR2kYRAp3dAJ9aAMDDWUMH+Sy/Y6FzWUKhwT8izgCfYaBy
OK+2mvIhB5ongmaRzUAeJtE=
=eyZf
-END PGP SIGNATURE-


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Re: ArtistX 0.6 question: rewrite wiki and manual

2008-09-29 Thread Marco Ghirlanda

Thanks everybody for the replies.
I didn't understand so much the hook thing. Should I add a script that 
basically repeats usermod commands but where (which dir)? And when will 
be run? (I mean at which point of the iso creation or booting?)
Groups are really important for many application, is there a simple way 
of adding my user to a list of groups? Without this I get lots of 
complains from people about not supporting ntfs and such things.


After I sort this out I will to write relevant infos and possibly upload 
to the documentation or send it to the right person to publish it 
(Daniel?).

Again thanks everybody (especially the developers),

Marco


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]