- Grml-devel - lists.mur.at

Re: [Grml-devel] [Grml] ifenslave bonding issue Re: First Release Candidate of Grml version 2020.06 available
by Michael Prokop 25 Jun '20

25 Jun '20

Hi! * Csillag Tamas [Wed Jun 24, 2020 at 02:10:31PM +0200]: > On Sat, Jun 06, 2020 at 06:24:51PM +0200, Michael Prokop wrote: > > Please test the ISOs and everything you usually use and rely on, 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 June (2020 *cough* :)). > It seems that I got hit by this bug: > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=959236 Thanks for bringing this to our attention. It was quite sad timing for us that this didn't make it into Debian/testing yet and we were just in the middle of our release process. :-/ We are re-doing the build process with the ifenslave bugfix right now. > There are multiple "source /etc/network/interfaces.d/*" lines in > /e/n/interfaces which I do not know if is a real issue of just cosmetic. Thanks for reporting this one, I noticed this one as well and reported it as https://github.com/grml/live-boot-grml/issues/11 and fixed this today already, so the stable release will include the fix. :) regards -mika-

2 1

Grml - new stable release 2020.06 available
by Michael Prokop 24 Jun '20

24 Jun '20

Hi, we said we'll release by the end of June, and here we are! The stable release of Grml version 2020.06 with codename 'Ausgehfuahangl' is available and is hitting our mirrors. More information about this release is available in the release notes of Grml 2020.06: https://grml.org/changelogs/README-grml-2020.06/ Grab the latest Grml ISO(s) and spread the word: https://grml.org/download/ If you should notice any bugs please let us know: https://grml.org/bugs/ We welcome constructive feedback, suggestions for improvement and your contributions, please just reach out to us: https://grml.org/contact/ Thanks to everyone contributing to Grml and this release! Take care and happy Grml-ing! -mika- - for the Grml project

1 0

grml-rescueboot
by Ryan Finnie 17 Jun '20

17 Jun '20

Hi all, I'm the maintainer of Finnix, which recently released a new version after 5 years[0]. A user asked if I was planning on updating grub-finnix, a functional equivalent of grml-rescueboot. I'm going to cut out most of a conversation I had with Paul Wise since it was a bunch of embarrassing half-remembered history[1], but in a nutshell, grml-rescueboot is actually perfectly capable of setting up ISOs in grub via the loopback.cfg standard, which means that many distros (Debian, Ubuntu, Grml, Finnix, etc) can utilize it, but it's not immediately apparent, and it calls the generated menu entries Grml, but are otherwise functional. What I'd like to propose is to genericize grml-rescueboot as grub-loopback-iso. This package could be aware of distros (e.g. continue to say "Grml Rescue System" for grml-*.iso). I also have a few additional wanted updates, namely fixing the grub dependencies so it can be used on arm64 UEFI (which it also would otherwise work fine on). The grml-rescueboot package could remain and depend on grub-loopback-iso, as it has the update-grml-rescueboot script which *is* Grml-specific. If this is something we agree can be pursued, I'm willing to do the work (conceptually, https://github.com/finnix/grub-loopback-iso-pkg is about 80% of the work done already, but would need more work to be a proper transitional from grml-rescueboot). I just wanted to make sure this is something Grml is not opposed to. Thanks, Ryan Finnie [0] https://blog.finnix.org/2020/05/14/finnix-120-released/ [1] In 2014 I had apparently forked grml-rescueboot as grub-loopback-iso, but never got it into Debian. And at some point it was added as a grml-rescueboot git branch? (http://git.grml.org/?p=grml-rescueboot.git;a=shortlog;h=refs/heads/grub-loo…) So it was known about and maybe was discussed at some point, but I honestly don't remember. I had updated my grub-loopback-iso and was looking for sponsors when Paul reminded me of grml-rescueboot again.

2 2

First Release Candidate of Grml version 2020.06 available
by Michael Prokop 15 Jun '20

15 Jun '20

Hi, long time no see, but here we are! The first release candidate of the upcoming Grml version 2020.06, code-named 'Ausgehfuahangl' is available. This Grml release provides fresh software packages from Debian testing (AKA bullseye). As usual it also incorporates current hardware support and fixes known bugs from the previous Grml release. For detailed information about the changes between 2018.12 and 2020.06-rc1 have a look at the official release announcement: https://grml.org/changelogs/README-grml-2020.06-rc1/ You can download Grml 2020.06-rc1 from: https://grml.org/download/prerelease/ Please test the ISOs and everything you usually use and rely on, 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 June (2020 *cough* :)). Thanks to all our contributors! regards, -mika- - for the Grml.org project

3 3

Re: [Grml-devel] [Grml] iPXE for networkbooting
by Geert Stappers 14 Apr '20

14 Apr '20

On 06-04-2020 23:24, Michael Prokop wrote: > Hi! > > * Geert Stappers [Mon Apr 06, 2020 at 06:11:45PM +0200]: > >> At http://grml.org/terminalserver/ is a reference to an abandoned >> networkbootproject. > >> Networkbootproject iPXE is alive and kicking, it's URL is https://ipxe.org > > Thanks for reporting this, Geert. > >> How to get the GRML website updated with that information? > > Our website is managed with Git, a pull request against > https://github.com/grml/grml.org/ is more than welcome (or drop us a > patch via mail to grml-devel (at) ml.grml.org or my personl mail > address if PRs on github don't work for you, also a mirror of the > repository is available at > https://git.grml.org/?p=grml.org.git;a=summary). Find it attached. Cheers Geert Stappers

2 1

[grml-debootstrap] Should /etc/network/interfaces be copied from the host by default?
by Darshaka Pathirana 02 Mär '19

02 Mär '19

Hi, before creating an issue on GitHub I would like to hear your opinion on this subject. This is a follow up of this: [1] https://github.com/grml/grml-debootstrap/issues/126 `grml-debootstrap` by default copies `/etc/network/interfaces` from the host to the target system. Debian/stretch+ uses Predictable Network Interface Names by default whereas the current Grml release (currently 2018.12) still uses the traditional/legacy interface name (eth0). When deploying a Debian/stretch system out of the latest Grml release (currently 2018.12) we have the situation that the `/etc/network/interfaces` file from the host is copied to the target system which then will boot with no network connection because no Predictable Network Interface Names are configured in it. We should discuss if deploying the host `/etc/network/interfaces` file by default is (still) the best approach. I would vote for a new option like `--hostinterfaces` which does that and go for `--defaultinterfaces` as the new default option. What do you think? Regards, - Darsha

1 0

Grml/Debian Bug Squashing Party in Salzburg, 2019
by Michael Prokop 11 Jan '19

11 Jan '19

Hi! The Debian project hosts a Bug Squashing Party in Salzburg/Austria, taking place from April 5th to April 7th 2019. A Bug Squashing Party is a come-together of developers, contributors and enthusiasts who try to fix as many bugs as possible. We've been invited to join the Bug Squashing Party and since Grml is an official derivative of Debian weâ€™re more than happy to take this opportunity. This is the perfect time and place to meet with fellow Grml and Debian developers, contributors and friends, to make the next Debian- and Grml-Release the best ever! :) The key facts: * Location: conova communications GmbH, Karolingerstr. 36A, 5020 Salzburg, Austria * Date: 2019-04-05 (Friday) until 2019-04-07 (Sunday) If you want to join us please visit https://wiki.debian.org/BSP/2019/04/Salzburg for further information. If you've any questions feel free to reach out to us (https://grml.org/contact/). PS: For the ones of you who can't join us in Salzburg, feel free to join us during the Bug Squashing Party on IRC (#grml on irc.freenode.org)! regards, -mika-

1 0

Grml - new stable release 2018.12 available
by Michael Prokop 31 Dez '18

31 Dez '18

Hi, we said we'll release by the end of December, and here we are! The stable release of Grml version 2018.12 with codename 'Gnackwatschn' is available and already hit our mirrors. More information about this release is available in the release notes of Grml 2018.12: https://grml.org/changelogs/README-grml-2018.12/ Grab the latest Grml ISO(s) and spread the word: https://grml.org/download/ If you should notice any bugs please let us know: https://grml.org/bugs/ We welcome constructive feedback, suggestions for improvement and your contributions, please just reach out to us: https://grml.org/contact/ Thanks to everyone contributing to Grml and this release! Happy new year and happy Grml-ing! -mika-

1 0

First Release Candidate of Grml version 2018.12 available
by Michael Prokop 21 Dez '18

21 Dez '18

Hi, just in time we have a present for you! The first release candidate of the upcoming Grml version 2018.12, code-named 'Gnackwatschn' is available. This Grml release provides fresh software packages from Debian testing (AKA buster). As usual it also incorporates current hardware support and fixes known bugs from the previous Grml release. For detailed information about the changes between 2017.05 and 2018.12 have a look at the official release announcement: https://grml.org/changelogs/README-grml-2018.12-rc1/ You can download Grml 2018.12-rc1 from: https://grml.org/download/prerelease/ Please test the ISOs and everything you usually use and rely on, 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 December (2018 *cough* :)). Thanks to all our wonderful contributors! regards, -mika- - for the Grml.org project

2 1

about grml in Grub
by Gregory Amaudruz 05 Dez '18

05 Dez '18

HI I put the iso file in a direcotoy of my usb stick and installed grub to boot it from in the Grub file I put: submenu "GRML 2014.11 ---> " { menuentry "Grml Rescue System 64bit" { iso_path="/boot/iso/grml64-full_2014.11.iso" export iso_path loopback loop (hd0,1)$iso_path set root=(loop) kernelopts=" ssh=foobarbaz toram " export kernelopts configfile /boot/grub/loopback.cfg } for that verson But that BIG problem with that once I am on the linux and I open a terminal and type: fdisk -l The entire drive is looped. So, I have multiple partitions of the USB Stick and I want to make it so that it loops only the first partition NOT the entrie drive. So, that I can mount septrate partions that are on the drive and have access to reading file and puting files on it. What to I need to put in the grub file as the description like what is above, So that it loops only the first partion on the drive and NOT the entire drive???????? Alos, if you can give me the GRUB descrption for the NEW GRML you have on your website, rather then the 2014 one. having the new Full version of the 64-bit, would be great. I have tried it and I do know it is a root access only, since it is system recovery This is what I did to install grub on the USB stick http://community.linuxmint.com/tutorial/view/1846 1) Prepare the usb drive: A new usb drive should be ready to permit the installation of Grub. However, if a drive has been used to boot an iso file previously, you may get an error concerning "iso9660 filesystem", depending on how the iso boot was created. The "iso9660 filesystem" means that at some point the USB held an isohybrid image. Since that filesystem is in the first 64 sectors of the disk, you can't delete it by deleting partitions. You can delete all of your partitions, and it will still be there. You can fix that with the dd command. First, make sure you know the linux drive letter for your USB drive. You don't want to accidentally erase your hard drive. Run the following commands just to be sure you have the right drive designation. inxi - pou or sudo fdisk -l Since I have two internal hard drives, my USB is sdc. Yours might be sdb or sdd Now you can erase the boot area and everything on the drive with this command sudo dd if=/dev/zero of=/dev/sdX bs=4096 - where X is your USB drive It takes a long time to dd a drive, so be patient. My 8 GB drive took almost 20 minutes. 2) Configure the usb drive: If you don't have GParted, install it > sudo apt-get install gparted Open GParted and locate the USB drive using the drop-down menu at the top right. Unmount the USB drive - right click > Unmount Create a new partition table (so that you can format to ext2) - Device > Create Partition Table > msdos Create a new ext2 partition - right click on the unallocated space > New > Format: ext2, Label: Grub2isoUSB - (it can be ext2, ext3, or ext4. I use ext2 on flash drives because the lack of journaling means less wear and tear on the drive.) Set the boot Flag - right click > Manage Flags > boot Close GParted. Now you have a clean USB drive ready for your .iso files. 3) Install grub2 to the USB: - (my USB is sdc) Mount the USB partition: udisks --mount /dev/sdc1 Make a /boot directory: sudo mkdir /media/Grub2isoUSB/boot Install Grub: sudo grub-install --boot-directory=/media/Grub2isoUSB/boot /dev/sdc Take ownership of the mount point and all directories on the USB so that you can edit grub.cfg and add and remove .iso files freely: sudo chown -R $USER:$USER /media/Grub2isoUSB OR: sudo chown -R yourusername:yourusername /media/Grub2isoUSB - edit the command for your actual user name and the correct mount point.

2 1