Michael Prokop [Fri, 8 Sep 2023 09:25:08 +0000 (11:25 +0200)]
Release new version 1:
20210208+grml.5
Michael Prokop [Fri, 8 Sep 2023 09:16:35 +0000 (11:16 +0200)]
live-netdev: unify coding style and drop noop $NETDEV assignment
Upstream uses tabs instead of whitespace and if\nthen etc coding style,
while I personally don't like this, let's keep coding style consistent,
to make synching and contributions towards upstream easier.
While at it, the NETDEV="$NETDEV" is a noop, as the variable is assigned
to itself, so drop it.
Michael Prokop [Fri, 8 Sep 2023 09:14:20 +0000 (11:14 +0200)]
Merge remote-tracking branch 'origin/github/pr/16'
Michael Prokop [Fri, 8 Sep 2023 06:51:13 +0000 (08:51 +0200)]
Release new version 1:
20210208+grml.4
Michael Prokop [Fri, 8 Sep 2023 06:36:55 +0000 (08:36 +0200)]
Merge remote-tracking branch 'origin/github/pr/17'
Michael Laß [Thu, 31 Aug 2023 18:03:38 +0000 (20:03 +0200)]
9990-main.sh: activate LVM volumes if needed.
An update to the Debian lvm2 package removed a script in the initrd that
would activate any LVs that are required to access the root volume. Due
to this change, grml failed to find its live media when it was stored on
an LVM volume.
Add an explicit activation of any LVs mentioned in the `live-media` or
`boofrom` kernel arguments, so that the live media can be found again.
Fixes https://github.com/grml/grml/issues/200
ThomasToka [Tue, 4 Jul 2023 10:38:03 +0000 (12:38 +0200)]
Update 9990-select-eth-device.sh
new line deleted
ThomasToka [Tue, 4 Jul 2023 10:27:21 +0000 (12:27 +0200)]
Update 9990-select-eth-device.sh
Update live-netdev to alternatively use a given mac address for the active network device.
it takes the mac, check which device name this mac has and uses the device name then to fire up the network connection
format is "live-netdev=xx:xx:xx:xx:xx:xx"
Michael Prokop [Sat, 24 Apr 2021 20:00:12 +0000 (22:00 +0200)]
Release new version 1:
20210208+grml.3
Michael Prokop [Sat, 24 Apr 2021 19:59:57 +0000 (21:59 +0200)]
Merge remote-tracking branch 'origin/github/pr/15'
Mihai Moldovan [Wed, 7 Apr 2021 13:30:54 +0000 (15:30 +0200)]
9990-misc-helpers.sh: remove mdadm.conf in initramfs if existent.
mkinitramfs is creating the initramfs based on host system parameters.
This is important for RAID support - if the base system (in that case,
the FAI chroot we use to bootstrap grml from) does not contain an
/etc/mdadm/mdadm.conf file (which is the default), it will automatically
generate one for the initramfs from the RAID devices in the currently
running system.
This essentially means that the RAID configuration spills into the
initramfs, even if later grml-live/FAI scripts make sure that they are
not recorded in the squashfs mdadm.conf.
Consequently, the generated image will boot fine on the system that
created the image, but will fail to boot from RAID devices on other
systems, since mdadm --assemble --scan will just refuse to start any
arrays not included in the provided mdadm.conf file as shipped in the
initramfs. Since we build general-purpose images and desperately want to
have auto-detection in such a case, this behavior is unwanted.
The easiest way to fix that is to just delete the initramfs's mdadm.conf
file before calling the RAID auto-detection script. This should restore
correct auto-detection behavior regardless of the system that built the
image without any disadvantage.
Closes: https://github.com/grml/grml/issues/125
Michael Prokop [Fri, 26 Mar 2021 07:59:35 +0000 (08:59 +0100)]
Release new version 1:
20210208+grml.2
Michael Prokop [Fri, 26 Mar 2021 07:56:22 +0000 (08:56 +0100)]
Merge remote-tracking branch 'origin/github/pr/14'
Mihai Moldovan [Thu, 25 Mar 2021 05:15:28 +0000 (06:15 +0100)]
9990-misc-helpers.sh: support lvm/mdadm in fromiso feature.
Previously, it wasn't possible to use fromiso with a Linux software RAID
or LVM device.
The code handling lvm/mdadm devices has been moved around and the
fromiso feature split up, so that lvm/mdadm devices are now started as
necessary even when fromiso has been passed.
The usual caveats apply: if you start from an lvm/mdadm device *without*
using the toram feature, the original volume will be kept mounted, so
it's not safe to mount the volume containing the grml image after
booting it.
With the toram feature, this is not an issue, since all the data is read
into a ramdisk and the original volume unmounted.
Mihai Moldovan [Wed, 24 Mar 2021 11:31:29 +0000 (12:31 +0100)]
9990-misc-helpers.sh: fix RAID detection for findiso.
The local-top mdadm script was replaced with:
1.) systemd integration
2.) a local-block mdadm script for initramfs-tools-based setups
in Debian stretch, so this part was broken ever since.
Use the "new" local-block mdadm script instead.
This one won't allow us to select a specific device to assemble, so just
let it start all of them and hope for the best.
Closes: https://github.com/grml/grml/issues/125
Michael Prokop [Tue, 9 Mar 2021 17:35:34 +0000 (18:35 +0100)]
Release new version 1:
20210208+grml.1
Michael Prokop [Tue, 9 Mar 2021 17:28:27 +0000 (18:28 +0100)]
Merge remote-tracking branch 'upstream/master'
Syncing with Debian's live-boot as of
commit
6cee205c9b6c7eb9c48bf66bfdd75ab04e38308c (tag: debian/1%
20210208, upstream/master)
Michael Prokop [Tue, 9 Mar 2021 17:17:21 +0000 (18:17 +0100)]
Merge remote-tracking branch 'origin/github/pr/13'
Mihai Moldovan [Mon, 8 Mar 2021 05:30:50 +0000 (06:30 +0100)]
9990-misc-helpers.sh: allow fs type override in fromiso feature.
The overriding feature can be turned on/used by prefixing the file
system type to the path, separated from the device node with a colon.
Example (good override): ext4:/dev/vda49/path/to/grml.iso
If the file system specification contains any non-alphanumerical
characters other than '-' or '_', it will be treated as part of the
actual path, since, at least currently, all known file systems match
this rule.
Example (no override): cra$$$yf§:/dev/sr0/another_path/to/grml.iso
In the former example, no file system type override is detected, which
means that the code will eventually search for a device called
'cra$$$yf§:/dev/sr0' (which, granted, doesn't make a lot of sense).
Sometimes it's necessary or at least handy to specify the file system
used for mounting the fromiso backing device directly.
For instance, putting the ISO file on a RAID1-backed device will fail to
mount it through autodetection (which, really, in most cases is a good
thing to not corrupt the array).
This change also mounts the backing device read-only, which should
enable safe usage and mounting even on RAID1 devices. Note, though, that
read-only mounts are not really very much "read-only", since they
actually sometimes still change on-disk file system metadata, like the
last time the device was mounted).
This said, it should be safe enough and users can easily re-sync the
array to ensure consistency later on.
Raphaël Hertzog [Mon, 8 Feb 2021 11:21:40 +0000 (12:21 +0100)]
Update changelog for 1:
20210208 release
Luca Boccassi [Mon, 8 Feb 2021 10:17:48 +0000 (10:17 +0000)]
Merge branch 'revert-
ef866fdb' into 'master'
Revert
ef866fdb
See merge request live-team/live-boot!35
Raphaël Hertzog [Fri, 22 Jan 2021 14:19:07 +0000 (15:19 +0100)]
Update changelog for 1:
20210122 release
Raphaël Hertzog [Fri, 22 Jan 2021 14:16:20 +0000 (15:16 +0100)]
Update my maintainer email
The work I do in the live team is part of my Kali work.
Raphaël Hertzog [Fri, 22 Jan 2021 14:15:28 +0000 (15:15 +0100)]
Update standards version to 4.5.0, no changes needed.
Changes-By: lintian-brush
Fixes: lintian: out-of-date-standards-version
See-also: https://lintian.debian.org/tags/out-of-date-standards-version.html
Raphaël Hertzog [Sat, 12 Dec 2020 16:10:37 +0000 (16:10 +0000)]
Merge branch 'master' into 'master'
9990-select-eth-device.sh: check carrier, pick NIC
See merge request live-team/live-boot!33
Michael Prokop [Fri, 4 Dec 2020 11:50:02 +0000 (12:50 +0100)]
Avoid overlay files of libnss* ending up in initramfs
When the initramfs gets generated on a booted/running live system, then
we end up with unexpected files in the initramfs:
| root@grml ~ # lsinitramfs /boot/initrd.img-5.6.0-2-amd64 | grep squash
| usr/lib/live/mount/overlay/rw/var/tmp/mkinitramfs_pPceGY/usr/lib/live/mount/rootfs/grml64-full.squashfs
| usr/lib/live/mount/overlay/rw/var/tmp/mkinitramfs_pPceGY/usr/lib/live/mount/rootfs/grml64-full.squashfs/lib
| usr/lib/live/mount/overlay/rw/var/tmp/mkinitramfs_pPceGY/usr/lib/live/mount/rootfs/grml64-full.squashfs/lib/x86_64-linux-gnu
| usr/lib/live/mount/overlay/rw/var/tmp/mkinitramfs_pPceGY/usr/lib/live/mount/rootfs/grml64-full.squashfs/lib/x86_64-linux-gnu/libnss_dns-2.30.so
| usr/lib/live/mount/overlay/rw/var/tmp/mkinitramfs_pPceGY/usr/lib/live/mount/rootfs/grml64-full.squashfs/lib/x86_64-linux-gnu/libnss_dns.so.2
| usr/lib/live/mount/overlay/rw/var/tmp/mkinitramfs_pPceGY/usr/lib/live/mount/rootfs/grml64-full.squashfs/lib/x86_64-linux-gnu/libnss_files-2.30.so
| usr/lib/live/mount/overlay/rw/var/tmp/mkinitramfs_pPceGY/usr/lib/live/mount/rootfs/grml64-full.squashfs/lib/x86_64-linux-gnu/libnss_files.so.2
| usr/lib/live/mount/rootfs/grml64-full.squashfs
| usr/lib/live/mount/rootfs/grml64-full.squashfs/lib
| usr/lib/live/mount/rootfs/grml64-full.squashfs/lib/x86_64-linux-gnu
| usr/lib/live/mount/rootfs/grml64-full.squashfs/lib/x86_64-linux-gnu/libnss_dns-2.30.so
| usr/lib/live/mount/rootfs/grml64-full.squashfs/lib/x86_64-linux-gnu/libnss_dns.so.2
| usr/lib/live/mount/rootfs/grml64-full.squashfs/lib/x86_64-linux-gnu/libnss_files-2.30.so
| usr/lib/live/mount/rootfs/grml64-full.squashfs/lib/x86_64-linux-gnu/libnss_files.so.2
| usr/lib/modules/5.6.0-2-amd64/kernel/fs/squashfs
| usr/lib/modules/5.6.0-2-amd64/kernel/fs/squashfs/squashfs.ko
This is caused by the find command, spotting files from
/lib/live/mount/rootfs/grml64-full.squashfs:
| root@grml ~ # find /lib /usr/lib -name 'libnss_dns.so.*' -o -name 'libnss_files.so.*'
| /lib/live/mount/rootfs/grml64-full.squashfs/lib/x86_64-linux-gnu/libnss_dns.so.2
| /lib/live/mount/rootfs/grml64-full.squashfs/lib/x86_64-linux-gnu/libnss_files.so.2
| /lib/x86_64-linux-gnu/libnss_dns.so.2
| /lib/x86_64-linux-gnu/libnss_files.so.2
Avoid this by filtering out files with `/lib/live`.
Raphaël Hertzog [Fri, 23 Oct 2020 14:03:14 +0000 (16:03 +0200)]
Drop Iain R. Learmonth from Uploaders on his request
Closes: #970288
Steven Shiau [Thu, 22 Oct 2020 00:56:19 +0000 (00:56 +0000)]
Update 9990-select-eth-device.sh
Steven Shiau [Thu, 22 Oct 2020 00:49:11 +0000 (00:49 +0000)]
Revert "Merge branch 'master' into 'master'"
This reverts merge request !34
Luca Boccassi [Tue, 4 Aug 2020 10:01:53 +0000 (10:01 +0000)]
Merge branch 'master' into 'master'
Fix leading space in DEVICE setting
See merge request live-team/live-boot!34
Benjamin Drung [Tue, 4 Aug 2020 09:43:06 +0000 (11:43 +0200)]
Fix leading space in DEVICE setting
live-boot will set the `DEVICE` parameter in `/conf/param.conf`. This
parameter specifies the default network interface to use, like eth0. So
only one Ethernet device is allowed here, but live-boot generates a list
with a leading space. For example it will set `DEVICE=' eth0'`. This
causes initramfs script relying on `DEVICE` fail.
Therefore just set the `DEVICE` parameter to the last connected
interface found.
Signed-off-by: Benjamin Drung <benjamin.drung@profitbricks.com>
Michael Prokop [Sat, 18 Jul 2020 15:03:10 +0000 (17:03 +0200)]
Release new version 1:
20200527+grml.5
Michael Prokop [Sat, 18 Jul 2020 15:00:46 +0000 (17:00 +0200)]
Avoid executing memdiskfind under Secure Boot
memdiskfind displays an ugly error message when running under Secure
Boot where access to /dev/mem is restricted:
| cannt open /dev/mem: Operation not permitted
If we can read from /dev/mem then skip the memdiskfind and instead
display a warning message.
Michael Prokop [Sat, 18 Jul 2020 14:24:26 +0000 (16:24 +0200)]
/e/n/i: move sourcing of /etc/network/interfaces.d/ to begin of file
netcardconfig doesn't properly handle this section and it disappears
when configuring network devices then.
Rewriting netcardconfig is on our agenda (see
https://github.com/grml/grml-network/issues/11), until we get there
let's make sure the status quo works as good as possible.
Take over wording based on what ifupdown's postinst script uses.
Michael Prokop [Fri, 17 Jul 2020 21:23:22 +0000 (23:23 +0200)]
Release new version 1:
20200527+grml.4
Michael Prokop [Fri, 17 Jul 2020 21:19:06 +0000 (23:19 +0200)]
Include ethtool binary for debugging network configuration during network boot
This should make it possible to apply specific network speed
settings or disable auto-negotiation.
Related to https://github.com/grml/grml/issues/153
Michael Prokop [Fri, 10 Jul 2020 07:07:21 +0000 (09:07 +0200)]
Release new version 1:
20200527+grml.3
Michael Prokop [Fri, 10 Jul 2020 07:05:19 +0000 (09:05 +0200)]
9990-misc-helpers.sh: ensure to appened to boot.log file
boot.log might exist already, don't overwrite it but instead append output
Michael Prokop [Fri, 10 Jul 2020 06:57:19 +0000 (08:57 +0200)]
0020-read-only: iterate over all devices + improve console message layout
There might be block devices other than /dev/sd* + /dev/vd* (like
/dev/nvme0n*). Instead of hardcoding a static list, let's iterate over
all of them, and then ignore all symlinks (pointing to the actual
devices) and consider only actual block devices.
Also ensure that the device exists (checked via `blockdev --getsz ...`)
before executing `blockdev --setro ...` on it.
Reworked the according console message: using printf with field width
allows us to make this look a bit nicer and better integrate into the
boot sequence look-alike.
JFTR: it would be nice to send output also to `/boot.log` (which ends up
as `/var/log/live/boot.log` on the booted system), but if we do this
then the output is visible twice during startup, as `/boot.live` is sent
to console via `tail -f`. If changing this to only list it via
`/boot.live` it might not be always guaranteed to be visible on screen,
so we didn't change this yet.
This work was funded by Grml-Forensic.
Michael Prokop [Tue, 23 Jun 2020 10:22:29 +0000 (12:22 +0200)]
Release new version 1:
20200527+grml.2
Michael Prokop [Tue, 23 Jun 2020 09:58:20 +0000 (11:58 +0200)]
Add instance for sourcing /etc/network/interfaces.d/ only once
We don't want one instance of `source /etc/network/interfaces.d/*`
per interace, but instead once per file.
Closes: https://github.com/grml/live-boot-grml/issues/11
Michael Prokop [Wed, 27 May 2020 12:14:16 +0000 (14:14 +0200)]
Release new version 1:
20200527+grml.1
JFTR, changelog was generated via:
| % gbp dch --verbose --meta --multimaint-merge --id-length=7 --release --since=
d3f65848c3fd43a5bbb375b1783fa2b9fa6125a6 --debian-branch=master --upstream-branch=master
Michael Prokop [Wed, 27 May 2020 12:15:54 +0000 (14:15 +0200)]
Fix duplicate Homepage header in debian/control
Merge oversight in commit
51f4b9d56200b
Michael Prokop [Wed, 27 May 2020 11:59:06 +0000 (13:59 +0200)]
Merge remote-tracking branch 'upstream/master'
Michael Prokop [Wed, 27 May 2020 11:48:50 +0000 (13:48 +0200)]
9990-grml-networking.sh: support /etc/network/interfaces.d/* in /e/n/i
For example cloud-init writes its network configuration file to
/etc/network/interfaces.d/50-cloud-init, so the file needs
to be sourced.
Related to https://github.com/grml/grml/issues/124
Steven Shiau [Fri, 22 May 2020 12:00:43 +0000 (20:00 +0800)]
9990-select-eth-device.sh: check carrier, pick NIC
Improve the mechanism to check the carrier to pick from
multiple network interfaces. This is based on the patch from
Michal Zatloukal.
Ref: https://sourceforge.net/p/clonezilla/bugs/298/
Raphaël Hertzog [Tue, 21 Apr 2020 08:54:41 +0000 (08:54 +0000)]
Merge branch 'fix-var-tmp-perms' into 'master'
Set sticky bit on /var/tmp as well (matching perms in base-files)
See merge request live-team/live-boot!30
Marcel Partap [Sat, 18 Apr 2020 16:25:08 +0000 (18:25 +0200)]
Set sticky bit on /var/tmp as well (matching perms in base-files)
(Fixes f.e. CUPS PDF driver not producing output files)
Luca Boccassi [Wed, 11 Mar 2020 15:12:45 +0000 (15:12 +0000)]
Merge branch 'debian' into 'master'
amend copyright
See merge request live-team/live-boot!29
Lyndon Brown [Wed, 11 Mar 2020 15:09:47 +0000 (15:09 +0000)]
"Live Systems" -> "Debian Live"
Lyndon Brown [Wed, 11 Mar 2020 13:14:02 +0000 (13:14 +0000)]
amend copyright
Raphaël Hertzog [Mon, 17 Feb 2020 09:53:41 +0000 (09:53 +0000)]
Merge branch 'lintian-fixes' into 'master'
Fix some issues reported by lintian
See merge request live-team/live-boot!27
Raphaël Hertzog [Wed, 22 Jan 2020 14:25:29 +0000 (14:25 +0000)]
Merge branch 'master' into 'master'
Fix flipped logic for handling memdiskfind
See merge request live-team/live-boot!28
Benjamin Drung [Mon, 13 Jan 2020 09:59:40 +0000 (10:59 +0100)]
components/9990-main.sh: Fix shellcheck issue SC2236
shellcheck complains about SC2236: Use -n instead of ! -z.
Signed-off-by: Benjamin Drung <benjamin.drung@profitbricks.com>
Benjamin Drung [Mon, 13 Jan 2020 09:53:19 +0000 (10:53 +0100)]
Fix flipped logic for handling memdiskfind
Commit
07d13d4a81e8e3ea3f7cff63a6528efd5a46b1e7 accidentally flipped
the logic for handling memdiskfind, causing erroneous messages and a
four second boot delay.
Flip the logic again to correct it.
Thanks to Marcel Partap for reporting it.
Signed-off-by: Benjamin Drung <benjamin.drung@profitbricks.com>
Debian Janitor [Wed, 4 Dec 2019 04:46:54 +0000 (04:46 +0000)]
Set debhelper-compat version in Build-Depends.
Fixes lintian: uses-debhelper-compat-file
See https://lintian.debian.org/tags/uses-debhelper-compat-file.html for more details.
Debian Janitor [Wed, 4 Dec 2019 04:46:36 +0000 (04:46 +0000)]
Bump debhelper from old 10 to 12.
+ debian/rules: Move --fail-missing argument to dh_missing.
Fixes lintian: package-uses-old-debhelper-compat-version
See https://lintian.debian.org/tags/package-uses-old-debhelper-compat-version.html for more details.
Debian Janitor [Wed, 4 Dec 2019 04:46:16 +0000 (04:46 +0000)]
Update standards version to 4.4.1, no changes needed.
Fixes lintian: out-of-date-standards-version
See https://lintian.debian.org/tags/out-of-date-standards-version.html for more details.
Raphaël Hertzog [Thu, 17 Oct 2019 09:43:29 +0000 (09:43 +0000)]
Merge branch 'doc-multiple-persistence-overlays' into 'master'
Document the fact that persistence-label now accepts a list
See merge request live-team/live-boot!24
Marcel Partap [Thu, 12 Sep 2019 13:50:08 +0000 (15:50 +0200)]
Document the fact that persistence-label now accepts a list
Raphaël Hertzog [Thu, 12 Sep 2019 13:25:54 +0000 (13:25 +0000)]
Merge branch 'feature-multiple-persistence-overlays' into 'master'
Accept multiple overlay names from persistence-label parameter
See merge request live-team/live-boot!23
Raphaël Hertzog [Thu, 12 Sep 2019 13:25:21 +0000 (13:25 +0000)]
Merge branch 'fix-silence-mount-failures' into 'master'
Fix spurious error msgs from live-boot about failed mounts…
See merge request live-team/live-boot!22
Marcel Partap [Mon, 9 Sep 2019 14:08:40 +0000 (16:08 +0200)]
Fix spurious error msgs from live-boot about failed mounts…
.. and directories already existing
> mount: mounting /dev/sr0 on /run/live/persistence/sr0 failed: No such device
> mount: mounting /dev/vda on /run/live/persistence/vda failed: No such device
> mkdir: can't create directory '/run/live/persistence/vda3/rw': File exists
> mkdir: can't create directory '/run/live/persistence/vda3/work': File exists
Marcel Partap [Mon, 9 Sep 2019 14:10:42 +0000 (16:10 +0200)]
Accept multiple overlay names from persistence-label parameter
.. separated by ',' as in persistence-label=linux-userdata,linux-systemconfig.img
Raphaël Hertzog [Fri, 6 Sep 2019 14:27:19 +0000 (14:27 +0000)]
Merge branch 'master' into 'master'
Fix the issue that fails to boot from removable NTFS device
See merge request live-team/live-boot!20
Closes: #939034
Steven Shiau [Fri, 6 Sep 2019 07:55:36 +0000 (15:55 +0800)]
Use ntfs-3g instead of kernel module ntfs.ko.
Use ntfs-3g instead of kernel module ntfs.ko to mount the file system.
Since Linux kernel 4.19.37-1 from Debian has dropped the support of
ntfs.ko:
https://metadata.ftp-master.debian.org/changelogs//main/l/linux-signed-amd64/linux-signed-amd64_4.19.37+5_changelog
<snipped>
"* ntfs: Disable NTFS_FS due to lack of upstream security support
(CVE-2018-12929, CVE-2018-12930, CVE-2018-12931)"
Raphaël Hertzog [Fri, 6 Sep 2019 06:41:36 +0000 (06:41 +0000)]
Merge branch 'master' into 'master'
Fix DNS search entry in /etc/resolv.conf and copy /etc/hostname and /etc/hosts into target
See merge request live-team/live-boot!19
Benjamin Drung [Wed, 21 Aug 2019 14:55:13 +0000 (16:55 +0200)]
Copy /etc/hostname and /etc/hosts into target
If the target system has an empty /etc/hostname file, copy /etc/hostname
from the initramfs into the target system. If the target system has an
empty or default /etc/hosts file, copy /etc/hosts from the initramfs
into the target system.
Signed-off-by: Benjamin Drung <benjamin.drung@cloud.ionos.com>
Benjamin Drung [Wed, 21 Aug 2019 14:52:54 +0000 (16:52 +0200)]
Create /etc/hostname in initramfs
Persist hostname in /etc/hostname in the initramfs if the hostname is
known.
Signed-off-by: Benjamin Drung <benjamin.drung@cloud.ionos.com>
Benjamin Drung [Wed, 21 Aug 2019 14:48:29 +0000 (16:48 +0200)]
Simplify empty check for /etc/resolv.conf
Shorten regular expression for grep command which matches empty lines
and lines with comments.
Signed-off-by: Benjamin Drung <benjamin.drung@cloud.ionos.com>
Benjamin Drung [Wed, 21 Aug 2019 14:37:46 +0000 (16:37 +0200)]
Fix shellcheck in components/9990-main.sh
Address all issues reported by shellcheck:
```
shellcheck -e SC1091 components/9990-main.sh
```
Signed-off-by: Benjamin Drung <benjamin.drung@cloud.ionos.com>
Benjamin Drung [Wed, 21 Aug 2019 14:15:48 +0000 (16:15 +0200)]
Fix DNS search entry in /etc/resolv.conf
Commit
66d1235abf2dbc4062ed5bb7aef28d99a5a38eb2 added support for
resolving DNS names from initramfs, but only the DNS domain was
configured for the DNS search. The DHCP client also provides the
`DOMAINSEARCH` variable that should be used for searching if available,
because it can contain more than one domain.
Signed-off-by: Benjamin Drung <benjamin.drung@cloud.ionos.com>
Benjamin Drung [Wed, 21 Aug 2019 14:11:13 +0000 (16:11 +0200)]
components/9990-networking.sh: Add shellcheck override
To make `components/9990-networking.sh` shellcheck clean, add an
override for specifying `HWADDR`, which is used by `do_iscsi` from
`9990-mount-iscsi.sh`. Run shellcheck:
```
shellcheck -e SC1090 components/9990-networking.sh
```
Signed-off-by: Benjamin Drung <benjamin.drung@cloud.ionos.com>
Michael Prokop [Thu, 11 Jul 2019 09:51:50 +0000 (11:51 +0200)]
Release new version 1:
20180603+grml.3
Michael Prokop [Thu, 11 Jul 2019 09:47:20 +0000 (11:47 +0200)]
Ensure locating libnss* files doesn't fail on merged-usr systems
Since debootstap v1.0.102 it defaults to --merged-usr, creating
/{bin,sbin,lib}/ symlinks pointing to their counterparts in /usr/
Debian/buster provides debootstrap 1.0.114 and therefore defaults to
--merged-usr as well. If the grml-live build environment
is based on Debian/buster we get this as default.
Inside backend/initramfs-tools/live.hook we have:
| for _SHLIB in $(find /lib -name 'libnss_dns.so.*' -o -name 'libnss_files.so.*')
| do
| copy_exec "${_SHLIB}"
| done
So if /lib is a symlink to /usr/lib (with merged-usr), then the `find
/lib ...` won't find any files (since it doesn't follow the symlink).
This change fixes this behavior.
Development sponsored by Sipwise GmbH.
This is reported as TT#62500 in customer's ticket system.
Steven Shiau [Mon, 17 Jun 2019 15:09:21 +0000 (15:09 +0000)]
A workaround to make sure /dev/mtd0 can be created
A workaround to make sure /dev/mtd0 can be created when memdisk is used.
This is due to sometimes "modprobe phram" can not successfully create /dev/mtd0.
Have to try several times.
Ref: https://gitlab.gnome.org/GNOME/gparted/issues/50#note_523831
http://gparted-forum.surf4.info/viewtopic.php?pid=32784#p32784
Luca Boccassi [Fri, 14 Jun 2019 09:55:47 +0000 (10:55 +0100)]
Update changelog for 1:
20190614 release
Luca Boccassi [Fri, 14 Jun 2019 09:46:10 +0000 (10:46 +0100)]
Set Standards-Version to 4.3.0
Luca Boccassi [Fri, 14 Jun 2019 09:44:56 +0000 (10:44 +0100)]
Set Rules-Requires-Root: no
Benjamin Drung [Wed, 12 Jun 2019 11:03:09 +0000 (13:03 +0200)]
Also search for libnss_*.so files in /usr/lib
The libnss_*.so were moved from /lib to /usr/lib and were not found any
more (breaking resolving the FQDN with "hostname -f").
Therefore also search for libnss_*.so files in /usr/lib.
Closes: #930419
Signed-off-by: Benjamin Drung <benjamin.drung@profitbricks.com>
Roland Clobus [Thu, 9 May 2019 13:12:46 +0000 (13:12 +0000)]
Updated the translation files.
The translators can now update their translations.
Roland Clobus [Thu, 9 May 2019 08:37:21 +0000 (08:37 +0000)]
Use 'true' when referring to boolean environment variables
Roland Clobus [Wed, 8 May 2019 16:48:41 +0000 (18:48 +0200)]
New Build-Depends: po4a for the translation files
Roland Clobus [Wed, 8 May 2019 15:17:41 +0000 (17:17 +0200)]
Rebuild the translations
Roland Clobus [Wed, 8 May 2019 15:10:44 +0000 (17:10 +0200)]
Delete all generated files. They are generated from the po files.
Roland Clobus [Wed, 8 May 2019 15:06:52 +0000 (17:06 +0200)]
Always rebuild po4a.cfg
This is needed to ensure that new languages will automatically be found
Roland Clobus [Wed, 8 May 2019 15:42:12 +0000 (15:42 +0000)]
Automatically create a snapshot of the latest package
Roland Clobus [Wed, 1 May 2019 15:50:04 +0000 (17:50 +0200)]
Fixed Lintian warning: manpage-section-mismatch
Roland Clobus [Wed, 1 May 2019 15:42:09 +0000 (17:42 +0200)]
Fixed a small typo.
Roland Clobus [Wed, 1 May 2019 15:30:56 +0000 (17:30 +0200)]
Updated URL to the homepage and manual.
Roland Clobus [Wed, 1 May 2019 15:24:05 +0000 (17:24 +0200)]
Fixed fetching the version number.
Roland Clobus [Wed, 1 May 2019 15:01:57 +0000 (17:01 +0200)]
Used the same text for po4a as in live-manual.
Roland Clobus [Wed, 1 May 2019 14:56:47 +0000 (16:56 +0200)]
Updated URL to the manual
Roland Clobus [Wed, 1 May 2019 14:53:38 +0000 (16:53 +0200)]
The homepage is https://wiki.debian.org/DebianLive
Roland Clobus [Wed, 1 May 2019 14:47:33 +0000 (16:47 +0200)]
checkbashisms can be found on salsa.debian.org now.
Michael Prokop [Fri, 8 Feb 2019 16:26:15 +0000 (17:26 +0100)]
Release new version 1:
20180603+grml.2
Michael Prokop [Fri, 8 Feb 2019 15:26:21 +0000 (16:26 +0100)]
Do not generate dhcp entry for loopback interface
This fixes a regression that was introduced in commit
52474b4c28303324.
The variable $interface is pointing towards /sys/class/net/lo,
at least until we overwrite the variable by the basename of
its network interface name path. Accordingly fix order for comparison.
Closes: https://github.com/grml/live-boot-grml/issues/9
Thanks: Mykola Malkov for the bug report
Michael Prokop [Thu, 13 Dec 2018 16:29:26 +0000 (17:29 +0100)]
Release new version 1:
20180603+grml.1
Michael Prokop [Fri, 14 Dec 2018 14:27:11 +0000 (15:27 +0100)]
9990-grml-networking.sh: display Grml info, update interfaces comment + operate on all net devices
* By displaying "Preconfiguring Grml networking" it's more
explicit that we're running the 9990-grml-networking.sh code
* It's not the 23networking live-initramfs hook since quite some time,
update the comment for generation of /etc/network/interfaces
* Support also new style network device names by iterating over
/sys/class/net/* and skipping only the loopback interface
Michael Prokop [Thu, 13 Dec 2018 16:26:36 +0000 (17:26 +0100)]
Support debian_networking boot option to use Debian's network behavior
Debian's ip=... support diverges from kernel one and we (Grml) prefer
to use the behavior that's used by the kernel. By default we use our
Grml_Networking implementation from components/9990-grml-networking.sh,
but if the debian_networking boot option is used then we use Debian's
live-boot behavior with Netbase from components/9990-netbase.sh.
(Some minor details also diverge in the network handling, with
vlan support present in Grml, different nameserver handling,...)