headers
Matthias Strubel | 2 Feb 19:51
Picon

Adding hostapn package to grml-iso

Hi,

i'm working on the PirateBox (http://wiki.daviddarts.com/PirateBox)
scripts for debian based system
(http://piratebox.aod-rpg.de/dokuwiki/doku.php) . I love grml very
much and just discovered all needed packages for the basic
Piratebox-Solution a alread installed at the image. Only hostapn is
missing... (yeah, I know, you can install it later)

Is it possible to add the package hostapn to the grml-image on default?
Hostapn is a tool to create an accesspoint with wifi-cards, which
can't switch into "Master"-mode

best regards
Matthias Strubel
Permalink | Reply | 1 comment |
headers
Michael Prokop | 15 Feb 23:27
Favicon

Re: Adding hostapn package to grml-iso

* Matthias Strubel [Thu Feb 02, 2012 at 07:51:05PM +0100]:

> i'm working on the PirateBox (http://wiki.daviddarts.com/PirateBox)
> scripts for debian based system
> (http://piratebox.aod-rpg.de/dokuwiki/doku.php) . I love grml very
> much and just discovered all needed packages for the basic
> Piratebox-Solution a alread installed at the image. Only hostapn is
> missing... (yeah, I know, you can install it later)

> Is it possible to add the package hostapn to the grml-image on default?
> Hostapn is a tool to create an accesspoint with wifi-cards, which
> can't switch into "Master"-mode

Do you mean the hostapd package?

regards,
-mika-
Permalink | Reply | 0 comments |
headers
Matthias Strubel | 16 Feb 15:27
Picon

Re: Adding hostapn package to grml-iso

Hi William,
Hi Mika,

> Do you mean the hostapd package?
yes

> Remastering
At weekends I'm playing around with bootstrap installation via grml in
a virtual machine for testing remastering :)

best regards
Matthias

2012/2/2 William Gardella <gardellawg <at> gmail.com>:
> Matthias,
>
> Piratebox is awesome and so is grml :)
>
> There are two options:
>
> 1. Use grml-live to remaster and make a new image, as described in
> http://wiki.grml.org/doku.php?id=remastering ; or
>
> 2. Use grml's debian live persistence features to add the package and
> any config changes to an additional partition.
>
> Obviously, #1 is easier for redistributing to others, because you get a
> nice shiny new ISO with your changed config/package set, but #2 takes a
> lot less time.
>
(Continue reading)

Permalink | Reply | 1 comment |
headers
Michael Prokop | 16 Feb 15:35
Favicon

Re: Adding hostapn package to grml-iso

* Matthias Strubel [Thu Feb 16, 2012 at 03:27:33PM +0100]:

> > Do you mean the hostapd package?
> yes

We've added it to the GRML_FULL class:

  http://git.io/YQA5MA

so it will be shipped with the upcoming stable release.

regards,
-mika-
Permalink | Reply | 0 comments |
headers
Arbiel Perlacremaz | 18 Feb 00:53
Picon

Booting grml from the iso file itself

Hi

I downloaded grml96_2011.12.iso and I would be glad to boot this file 
without having to burn a CD or to write it down to a USB stick.

I've already done this for Ubuntu distros and for Clonezilla, and I 
found it very helpful.

I've been through the iso file to look for the grub.cfg file and I found 
out that I could write a little grub.cfg file of my own to launch 
grub.cfg which resides in the iso file. I got the menu generated by the 
following lines

for config in /boot/grub/*_default.cfg ; do source "$config" ; done
for config in /boot/grub/*_options.cfg ; do source "$config" ; done
source /boot/grub/addons.cfg

and I choose the first entry, grml32. The boot process than proceded 
until I got an error message stating that

BOOT failed
grml32 2011.12 Release Codename Knecht Rootrecht [2011-12-23]

And the explanation was

Unable to find a medium containing a live file system.

I suppose this message results from the fact that I've not been able to 
correctly set the iso_path and the kernelopts variables which are used 
as parameters of the linux command of the menuentry command.
(Continue reading)

Permalink | Reply | 2 comments |
headers
Ulrich Dangel | 18 Feb 01:06
Favicon

Re: Booting grml from the iso file itself

* Arbiel Perlacremaz wrote [18.02.12 00:53]:

> I downloaded grml96_2011.12.iso and I would be glad to boot this
> file without having to burn a CD or to write it down to a USB stick.

> function iso_virtuel {
> search --file --set=root --no-floppy /${2}
> loopback iso ${1}${2}
> }
> 
> menuentry 'grmliso' {
> iso_virtuel / "grml96_2011.12.iso"
> set root=(iso)
> set iso_path=(iso)
> configfile /boot/grub/grub.cfg
> }

The problem is probably that you have to export the iso path otherwise
the exported values won't be availabe in the other grub configs. This
means you have to add export iso_path to your menu entry.

There are other small issues you should also be aware of:

1) You should use loopback.cfg instead of grub.cfg as loopback.cfg is a
more standardized way e.g. ubuntu also supports loobpack.cfg
2) The released grml96 iso image has a wrong grub config (i think you
only can boot either grml64 or grml32). You should generate your own
grub config with the current grml2usb itself.

Ulrich
(Continue reading)

Permalink | Reply | 1 comment |
headers
Michael Prokop | 18 Feb 07:55
Favicon

Re: Booting grml from the iso file itself

* Ulrich Dangel [Sat Feb 18, 2012 at 01:06:52AM +0100]:

> 2) The released grml96 iso image has a wrong grub config (i think you
> only can boot either grml64 or grml32). You should generate your own
> grub config with the current grml2usb itself.

Yeah, it's http://bts.grml.org/grml/issue1134
and already fixed in the daily ISOs and for the upcoming stable
release.

JFYI

regards,
-mika-
Permalink | Reply | 0 comments |
headers
Matthias Strubel | 20 Feb 05:46
Picon

Re: Adding hostapn package to grml-iso

Am 17.02.2012, 12:00 Uhr, schrieb <grml-request <at> ml.grml.org>:

> We've added it to the GRML_FULL class:
>
>   http://git.io/YQA5MA
>
> so it will be shipped with the upcoming stable release.
>
> regards,
> -mika-

Geat!
Thank you.

best regards
Matthias
Permalink | Reply | 0 comments |
headers
Stefan Weiss | 27 Feb 15:24
Picon
Favicon

Updating USB stick with persistency option?

Hello.

I'm trying out to the persistency feature for the first time. I had a
4GB USB stick lying around, so I'm following the example in the wiki
more or less verbatim.

What I'm wondering is, can this USB stick be updated when the next Grml
version is released? Up until now, there was never any user data on the
stick (or CD), but now there could be something worth preserving in
$HOME. I'm not sure how exactly the persistency snapshots work, but I
guess simply running grml2usb with the new ISO won't be enough.

It's no big deal if an update isn't possible. I'll expect there will
only be a couple of shell scripts and .debs in my $HOME, and I can
easily transfer them to a different partition before updating. If that's
the case, should I wipe the home-rw, live-rw, and GRMLCFG partitions
when I install the new ISO?

Thanks,
stefan
Permalink | Reply | 2 comments |
headers
Stefan Weiss | 27 Feb 16:32
Picon
Favicon

Re: Updating USB stick with persistency option?

On 2012-02-27 15:35, William Gardella wrote:
> Stefan,
> 
> In my experience and understanding, Debian Live persistence does present
> some issues with upgrading the underlying live system.  The files found
> in snapshots/persistence partitions always pre-empt their equivalents on
> the image, which Debian Live seems to always assume to be older than the
> snapshot.  So if you have been apt-get upgrading and installing lots of
> software to live-rw, for example, that will prevent any newer package
> versions on the ISO from being seen.  With home-rw, there shouldn't be
> as big of a headache, but of course if you have altered the
> grml-installed configuration files, those versions will remain and
> preempt the ISO (you will have to copy over new grml user configuration
> manually if you want it).  I don't know about GRMLCFG because I don't
> use it, but my guess would be that it will continue to replace the
> relevant bits of /etc/ exactly as it did on your previous ISO version.
> 
> So I guess it will probably save some headaches to wipe live-rw, but
> home-rw should be okay.
> 
> Best,
> Will

Thanks, that makes sense.
I think I'll just play it safe and wipe all the snapshot partitions
before I upgrade. It's unlikely that I'll make major adjustments to the
system anyway, apart from installing a few packages and storing shell
scripts in $HOME.

- stefan
(Continue reading)

Permalink | Reply | 0 comments |

Gmane