Re: live cd from mexico
On Mon, Apr 13, 2009 at 12:50 PM, s <email@example.com> wrote:
> hello list
> This is my first post from Mexico,
> I want to do my own live CD to live performance with supercollider and more
> but I'm a little confused with the installation of packages. I followed the
> thread "custom live cd" and I have some questions:
> Do I need to create a folder in /tmp to make a live cd?
No just make a folder say supercollider:
then move in to supercollider:
>> sudo lh_config -a -d lenny i386 - categories main contrib non-free-p gnome
>> - gnome-orca packages audacity brltty Rhythmbox - packages-lists / home /
>> daniel / stuff / packages.list
As an exercise in understanding try just running from the folder supercollider:
Then have a look at the files created under config folder. For
packages see config/chroot and look for LH_PACKAGES=""
> <first, if you pass more than one argument to a parameter, it needs to be
> quoted, e.g. - foo 'bar baz'.
> wich are the parameters in sudo lh_config -a -d lenny i386 -
> what is "quoted"?
> Wich are the arguments that I have to quote?
> second, packages-lists do not work like this. put
> / home / daniel / stuff / packages.list into config /
> and set - packages-lists packages.list
> Are the first and second steps applied to the line at the same time? or
> after applying the first step and executing the line then I apply the second
> I thought that I had to do lh_config in order to have the
> chroot_local-packageslists folder.
> How do I put / home / xxxx / stuff / packages.list into config /
> chroot_local-packageslists ?
Not sure I understand but I think you can look at
/usr/share/live-helper/lists/ for examples. But you can just add the
packages you want as listed above.
>> cd ~
>> cp file1 file2 file3 ... / tmp / livecd / config / includes / home / user
> What are file1 file2 file3?,
> Are they packages?
> Sorry if these questions are too basic, I am learning.
No worries, I hope this information helps. If not post again.
Also if you have not read the manual it might offer more details on
> _[s] -- linux #434565