- Grml - lists.mur.at

grmlfull-32 2014.11
by David Hare 04 Dez '14

04 Dez '14

Trying out grmlfull-32 2014.11 iso as a virtualbox guest. On two different machines (one wheezy, intel core2, 2GB RAM .. another jessie, intel core2, 1GB RAM) In both cases it hangs at "Waiting for /dev to be fully populated..." I have seen the bug report for udev but thought it was fixed. A few lines above is a suggestion to boot with "noudev". Trying that gives errors "could not open /dev/tty1" repeated for other ttys .. then "could not chown/chmod tty device" ad infinitum. Using "serial console" option boots to a prompt but freezes after X has started (static mouse cursor) Any ideas what is wrong? I have tried also the "-small" and "daily build" versions with the same result. No hardware immediately available to try cd or usb.. Other iso's work fine here in VB.. *except* recent custom builds with jessie+sysvinit+util-linux_25x which also cannot open a tty. David Hare

3 2

Own Rescue-CD based on grml
by Werner P. Schulz 20 Nov '14

20 Nov '14

Last weeks I worked again on remaster grml http://www.wp-schulz.de/rescue-cd-mit-grml.html Perhaps it may be useful for some of us. Greetings Werner

2 3

Grml - new stable release 2014.11 available
by Michael Prokop 17 Nov '14

17 Nov '14

Hi, we just released Grml 2014.11 - Gschistigschasti This Grml release provides fresh software packages from Debian testing (AKA jessie). As usual it also incorporates up2date hardware support and fixes known bugs from the previous Grml release. More information is available in the release notes of Grml 2014.11: http://grml.org/changelogs/README-grml-2014.11/ Grab the latest Grml ISO(s) and spread the word! http://grml.org/download/ PS: Special thanks to Christian Hofstaedtler for helping us in solving a big release stopper caused by udev's net.agent on systems without systemd (AKA http://bugs.debian.org/754987 ) Thanks everyone and happy grml-ing, -mika-

1 0

First Release Candidate of Grml version 2014.10 available
by Michael Prokop 31 Okt '14

31 Okt '14

Hi, so we did it again, the first release candidate of the upcoming Grml version 2014.10, code-named 'Gschistigschasti' was released. This Grml release provides fresh software packages from Debian testing (AKA jessie). As usual it also incorporates up2date hardware support and fixes known bugs from the previous Grml release. For detailed information about the changes between 2014.03 and 2014.10 have a look at the official release announcement: http://grml.org/changelogs/README-grml-2014.10-rc1/ Please test the ISOs and everything you usually use and report back so we can complete the stable release soon. If no major problems come up, the next iteration will be the stable release, which is scheduled for the end of October. Thanks to all contributors! regards, -mika- - for the Grml.org project

1 1

Possible to run grml-debootstrap --vmfile inside docker?
by Patrick Schleizer 18 Okt '14

18 Okt '14

Hi! Was playing a bit with docker... ## On the host. modprobe dm-mod ## Made my own image. sudo apt-get install debootstrap sudo -E /usr/share/docker.io/contrib/mkimage.sh -t $USER/minbase debootstrap --variant=minbase stable ## Run a bash shell within. sudo docker run -i -t $USER/minbase /bin/bash ## Install modprobbe. apt-get install kmod ## Test modprobbe. modprobe dm-mod libkmod: ERROR ../libkmod/libkmod.c:554 kmod_search_moddep: could not open moddep file '/lib/modules/3.16-2-amd64/modules.dep.bin' Which failed, which is what grml-debootstrap would do. And without dm-mod, also kpartx will fail. Cheers, Patrick

1 0

GRML2USB encryption
by Charles Alan Hewson 14 Sep '14

14 Sep '14

Would it be practical to encrypt all of usb stick with grub2 modules? I have concerns about /boot on missing thumb drives. Charles

1 0

grml daily builds
by Carlos Carlos 28 Aug '14

28 Aug '14

Thanks Darshaka and Evgeni. I didn't trust too much in md5 sums as I have seen in other daily build distro and unchanged/unmodified iso that the day it was build for the first time, lets say on 09 January, had x md5 then the automatic build system, rebuilt it again the next day, 10 January, and its md5 was different, who knows it could be the simple different number in the date or a glitch during the automatic build process, iso sizes were exactly the same, the iso was a final version so nothing was modified by the devs because they only add or change things between final versions not a day after a final version is released and their md5 were different. That's why I thought the same thing happens in grml, iso is the same unless you see an increase or decrease in its size, md5 can be different as a matter or different date coded in the build so if you see the same size in 3 consecutive daily builds then you can expect no browser update, no openssl update and the like. I don't know if the autobuild systems are controled by anything/anyone or if they simply keep rebuilding isos on a daily basis and autonomous way no matter if modifications were made or not, something like: It was programmed to do a rebuild every day at 11:00 or so Thanks much for your replies.

1 0

grml daily builds
by Carlos Carlos 28 Aug '14

28 Aug '14

Hi I found the page that generates daily builds of unstable and stable grml, I notice that iso size can be exactly the same for 3 or 4 consecutive days so I suppose nothing was changed or added to the iso in those days, is this correct?. I might be wrong but I don't think there are devs coding new things or modifying old ones every single day. I suppose that the app which generates the daily isos do it automatically and it doesn't matter if something new was added or not, modified or not, it simply keeps doing daily isos non stop, correct?. Thanks in advance for any info.

3 3

Cheatcodes as PDF?
by Tim Landscheidt 23 Mai '14

23 Mai '14

Hi, printing http://git.grml.org/?p=grml-live.git;a=blob_plain;f=templates/GRML/grml-che… isn't easy as there are some long lines especially in the "Configuration settings" section where word-wrap looks aw- ful. Is there a PDF (A4) version available somewhere? Tim

4 4

Some features may be dropped from GNU Screen in the future (including braille support)
by Axel Beckert 04 Apr '14

04 Apr '14

Hi, on the GNU Screen development mailing list, there's currently a thread which discusses how to get some drive in the GNU Screen development again. Amadeusz Sławiński (Cc'ed) has a git repo with some a little bit more disruptive changes at https://github.com/amade/screen/tree/devel/src In the following mail he describes what he changed and removed. (I've shortened the mail. "[…]" show points where I removed parts. Full mail at https://lists.gnu.org/archive/html/screen-devel/2014-04/msg00008.html) One of the GNU Screen feature which are about to be dropped in the future is Screen's braille support. (Which is not enabled in Debian's screen package as far as I can see.) I know that there are quite some visually handicapped Grml users, so I send this mail to the debian-accessibility mailing list and the general Grml mailing list. Reply-To is set to the screen-users mailing list. (I don't read debian-accessibility, but both other lists.) I also allowed myself to Bcc some other heavy screen users I know personally. So if you use Screen's braille features (whatever they are exactly) or any other of the explicitly listed features in the mail below, and want to continue to using them, please speak up now. Upstream is also in need of someone testing (and maybe maintaining) that code. One potentially to be removed screen feature which IIRC is used by Grml by default is the nethack mode with a little bit more cryptic screen messages than by default. Not sure how mission-critical that one is. ;-) ----- Forwarded message from Amadeusz Sławiński <amade(a)asmblr.net> ----- Date: Wed, 2 Apr 2014 19:47:21 +0200 From: Amadeusz Sławiński <amade(a)asmblr.net> To: screen-devel(a)gnu.org Subject: Re: [screen-devel] screen maintainer […] > > * new features (256 colors in hardstatus, hardstatus on top, > > truecolor, ...) […] > > * removal of ancient code (removed most of #ifdef for ancient > > systems) […] > I fear that this may cause a lot of breakage. Linux(*) is by far not > the only platform for Screen out there. > > (*) You wrote earlier that you only tested your code on Linux. Linux > is by far not the only platform, GNU Screen runs on. That's why I warn before hand. Screen is project which accumulated more then 25 years of code according to copyrights. And while it may be interesting to historians, I think it's time source is stripped of those workarounds and retested on machines people use, because it's likely that it just works with far fewer hacks, than it had. > > * removal of features which didn't seem useful or could be replaced […] > Please list which features you removed, so that people at least have a > chance to object. […] That's why I want to talk about it before I do anything drastic, one of reasons I tried to describe my changes at least a bit ;) >From fast comparing between source files: multiuser - seemed more like security risk to me braille - couldn't test :( utmp - seemed broken and there is also utmpx? nethack - funny, but who really needs it? zmodem - according to wiki some ancient file transfer protocol there may be something else... […] I want to make sure that screen stays as usable as it is to people who use it, but also would like to see new stuff happening, that's why I started this talk. Amadeusz ----- End forwarded message ----- Regards, Axel -- ,''`. | Axel Beckert <abe(a)debian.org>, http://people.debian.org/~abe/ : :' : | Debian Developer, ftp.ch.debian.org Admin `. `' | 1024D: F067 EA27 26B9 C3FC 1486 202E C09E 1D89 9593 0EDE `- | 4096R: 2517 B724 C5F6 CA99 5329 6E61 2FF9 CD59 6126 16B5

7 7