Bug#980758: additional info

2021-01-26 Thread Thomas Lange 
The debian installer detects hardware that needs nonfree firmware and
shows the user which package name to install.

On the nonfree version of the Debian live CD the calamares installer
already installs all nonfree firmware packages. Now sure were it gets
the list from.
-- 
regards Thomas

Bug#409271: overlayfs and NFS v4 is working

2019-09-26 Thread Thomas Lange 
There's still no progess in adding NFSv4 to klibc nfsmount for
initramfs-tools.

Here's the info how to use overlayfs and NFSv4 for a read-only
nfsroot but with dracut instead of initramfs-tools:

http://blog.fai-project.org/posts/overlayfs/
http://fai-project.org/fai-guide/#_a_id_nfsv4_a_how_to_use_nfs_v4_with_the_nfsroot

-- 
regards Thomas

Bug#786925: overlay and NFS now works

2016-06-22 Thread Thomas Lange 

Package: src:linux
Fixed: 4.6.2-1

overlayfs and NFS works if you add the option default_permissions to
the mount command as follow:

mount -t nfs -oro,noatime server:/srv/fai/nfsroot /tmp/lower
mount -t overlay overlay 
-olowerdir=/tmp/lower,upperdir=/tmp/upper,workdir=/tmp/work,default_permissions 
/tmp/merged

It works nicely for me with Debian kernel 4.6.2. Without this option,
overwriting an existing file ended with a permissions denied.

This option was added in january 2016 to the kernel. See
http://thread.gmane.org/gmane.linux.file-systems.union/493

IMO we can close this bug now.

-- 
regards Thomas

Bug#686658: (no subject)

2012-11-23 Thread Thomas Lange 
There's some discussion about that 
http://www.spinics.net/lists/linux-nfs/msg32974.html
-- 
regards Thomas


-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/20655.64245.502677.954...@kueppers.informatik.uni-koeln.de

Re: Processed: reassign 669342 to dracut

2012-06-13 Thread Thomas Lange 
 On Wed, 13 Jun 2012 17:19:28 +0200, maximilian attems m...@debian.org 
 said:

 one could easily install in the days yaird and initramfs-tools.
 It invovled a stupid entry in /etc/kernel-img.conf.
yaird was removed in may 2011 from the Debian archive.

 I think it should be very easy to come up with an update-alternatives
 solution, that prioritises the default. (Not Wheezy target but post
 release). If you want to try out an initramfs generator you don't
 know if it will boot, one shouldn't nuke the known working one.
IMO people will use either initramfs-tools or dracut. Therefore
there's no need to make both initramfs generators installed at
once. Fact is also that currently both use the same name for the
initrd, and that's why they should conflict on each other. I can't
understand why you don't like to add the Conflicts: to i-t.
-- 
regards Thomas


-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/20440.47939.512812.954...@kueppers.informatik.uni-koeln.de

Bug#669342: initramfs-tools should conflicts to dracut

2012-04-19 Thread Thomas Lange 

Package: initramfs-tools
Version: 0.101
Severity: minor

Since dracut uses the same file name for the initrd and dracut is a
replacement for initramfs-tools, it should conflict to dracut.

The dracut package already conflicts to initramfs-tools.

-- 
regards Thomas



-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/20367.54389.341847.644...@malzmuehle.informatik.uni-koeln.de

Bug#669345: /etc/kernel/postinst.d/initramfs-tools: update-initramfs: not found

2012-04-19 Thread Thomas Lange 

Package: initramfs-tools
Version: 0.101
Severity: minor
Tags: patch


When I install dracut - which conflicts to initramfs-tools -
initramfs-tools will be removed. But when doing a dpkg-reconfigure the
script /etc/kernel/postinst.d/initramfs-tools is still executed, which
lead to following error:

/etc/kernel/postinst.d/initramfs-tools: 33: 
/etc/kernel/postinst.d/initramfs-tools: update-initramfs: not found


Here's an easy patch for this:

--- /etc/kernel/postinst.d/initramfs-tools  2011-03-30 11:56:12.0 
+0200
+++ initramfs-tools.new 2012-04-19 10:49:28.677972624 +0200
@@ -3,6 +3,8 @@
 version=$1
 bootopt=
 
+[ -x /usr/sbin/update-initramfs ] || exit 0
+
 # passing the kernel version is required
 if [ -z ${version} ]; then
echo 2 W: initramfs-tools: ${DPKG_MAINTSCRIPT_PACKAGE:-kernel 
package} did not pass a version number


Log of the problem:


wheezy[~]# aptitude install dracut
The following NEW packages will be installed:
  dracut{b} 
0 packages upgraded, 1 newly installed, 0 to remove and 1 not upgraded.
Need to get 0 B/133 kB of archives. After unpacking 442 kB will be used.
The following packages have unmet dependencies:
 dracut : Conflicts: initramfs-tools but 0.101 is installed.
The following actions will resolve these dependencies:

 Remove the following packages:
1) initramfs-tools 



Accept this solution? [Y/n/q/?] 
The following NEW packages will be installed:
  dracut 
The following packages will be REMOVED:
  initramfs-tools{a} 
0 packages upgraded, 1 newly installed, 1 to remove and 1 not upgraded.
Need to get 0 B/133 kB of archives. After unpacking 115 kB will be used.
Do you want to continue? [Y/n/?] 
dpkg: initramfs-tools: dependency problems, but removing anyway as you 
requested:
 linux-image-3.2.0-2-amd64 depends on initramfs-tools (= 0.99~) | 
linux-initramfs-tool; however:
  Package initramfs-tools is to be removed.
  Package linux-initramfs-tool is not installed.
  Package dracut which provides linux-initramfs-tool is not installed.
  Package initramfs-tools which provides linux-initramfs-tool is to be removed.
 linux-image-3.2.0-2-amd64 depends on initramfs-tools (= 0.99~) | 
linux-initramfs-tool; however:
  Package initramfs-tools is to be removed.
  Package linux-initramfs-tool is not installed.
  Package dracut which provides linux-initramfs-tool is not installed.
  Package initramfs-tools which provides linux-initramfs-tool is to be removed.
(Reading database ... 178235 files and directories currently installed.)
Removing initramfs-tools ...
Processing triggers for man-db ...
Processing triggers for doc-base ...
Processing 1 removed doc-base file...
Registering documents with dhelp...
Selecting previously unselected package dracut.
(Reading database ... 178182 files and directories currently installed.)
Unpacking dracut (from .../archives/dracut_018-2_all.deb) ...
Processing triggers for man-db ...
Setting up dracut (018-2) ...
dracut: Generating /boot/initrd.img-3.2.0-2-amd64
 
wheezy[~]# dpkg-reconfigure linux-image-3.2.0-2-amd64   
Running depmod.
Examining /etc/kernel/postinst.d.
run-parts: executing /etc/kernel/postinst.d/dracut 3.2.0-2-amd64 
/boot/vmlinuz-3.2.0-2-amd64
run-parts: executing /etc/kernel/postinst.d/initramfs-tools 3.2.0-2-amd64 
/boot/vmlinuz-3.2.0-2-amd64
/etc/kernel/postinst.d/initramfs-tools: 33: 
/etc/kernel/postinst.d/initramfs-tools: update-initramfs: not found
run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 127
Failed to process /etc/kernel/postinst.d at 
/var/lib/dpkg/info/linux-image-3.2.0-2-amd64.postinst line 696, STDIN line 2.






-- Package-specific info:
-- initramfs sizes
-- /proc/cmdline
BOOT_IMAGE=/boot/vmlinuz-3.2.0-2-amd64 
root=UUID=a1abfdce-78e6-4c16-a5d6-3eef6f04f9ee ro quiet

-- resume
RESUME=UUID=34690ec1-2b81-4b16-8105-ac3f759f309c
-- /proc/filesystems
ext4


-- /etc/initramfs-tools/update-initramfs.conf
update_initramfs=yes
backup_initramfs=no


-- System Information:
Debian Release: wheezy/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 3.2.0-2-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages initramfs-tools depends on:
ii  cpio   2.11-7
ii  klibc-utils2.0~rc3-1
ii  module-init-tools  none
ii  udev   175-3.1

Versions of packages initramfs-tools recommends:
ii  busybox  1:1.19.3-5

Versions of packages initramfs-tools suggests:
pn  bash-completion  none


-- 
regards Thomas



-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/20367.54280.649032.516...@malzmuehle.informatik.uni-koeln.de

Re: postinst of linux-image complains if initrd has different file name

2012-04-11 Thread Thomas Lange 
 On Wed, 11 Apr 2012 02:44:44 +0100, Ben Hutchings b...@decadent.org.uk 
 said:

 If dracut would use the same name for the initrd as initramfs-tools,
 then there are two programs in /etc/kernel/postinst.d which would
 write to the same file. So, IMO dracut must use another file name
 for its initrd and the postinst of linux-image should support initrd
 file names like initramfs.. What's your oppinion?

 I think dracut and initramfs-tools should each conflict with
 linux-initramfs-tool.
Mmm, I think that's not possible.  The linux-image package depends on
initramfs-tools or linux-initramfs-tool (see below). If dracut
conflicts with linux-initramfs-tool it can't be installed since the
linux-image package does not (yet) list dracut in its dependency
list. Additionally initramfs-tools currently provides
linux-initramfs-tool, so why should it now conflict with it?


Package: linux-image-3.2.0-2-amd64
Depends: kmod | module-init-tools, linux-base (= 3~), initramfs-tools (= 
0.99~) | linux-initramfs-tool

-- 
regards Thomas


-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/20357.17193.435028.446...@malzmuehle.informatik.uni-koeln.de

postinst of linux-image complains if initrd has different file name

2012-04-10 Thread Thomas Lange 
Hi,

when using dracut (017-1) instead of initramfs-tools on a wheezy
machine /var/lib/dpkg/info/linux-image-3.2.0-2-amd64.postinst creates
and complains about a dangling symlink /initrd.img. This is because
dracut creates a initrd file called initramfs-3.2.0-2-amd64.img. This
is properly detected by update-grub but not by the postinst script of
the linux-image package.

Is there a policy that the initrd must be called initrd.img-`uname
-r`?  Since grub handles different initrd file names (in
/etc/grub.d/10_linux), I assume the postinst of the linux-image
package should also handle a initrd called initramfs*.img.

If dracut would use the same name for the initrd as initramfs-tools,
then there are two programs in /etc/kernel/postinst.d which would
write to the same file. So, IMO dracut must use another file name
for its initrd and the postinst of linux-image should support initrd
file names like initramfs.. What's your oppinion?





Here's the log of a test on my wheezy machine without initramfs-tools
installed, but using dracut 017-1. I've set debug=1 in the postinst script.

This is what I did:

rm /vmli* /initr*
ls -l /vmlinu* /initr* /boot/vmlinu* /boot/initr*
/var/lib/dpkg/info/linux-image-3.2.0-2-amd64.postinst configure
ls -l /vmlinu* /initr* /boot/vmlinu* /boot/initr*
/var/lib/dpkg/info/linux-image-3.2.0-2-amd64.postinst configure
ls -l /vmlinu* /initr* /boot/vmlinu* /boot/initr*


Script started on Tue 10 Apr 2012 06:12:36 PM CEST
wheezy[~]# rm /vmli* /initr*
wheezy[~]# ls -l /vmlinu* /initr* /boot/vmlinu* /boot/initr*
-rw-r--r-- 1 root root 14130694 Apr 10 18:11 /boot/initramfs-3.2.0-2-amd64.img
-rw-r--r-- 1 root root  2804816 Mar 20 20:35 /boot/vmlinuz-3.2.0-2-amd64

wheezy[~]# /var/lib/dpkg/info/linux-image-3.2.0-2-amd64.postinst configure
Running depmod.
image_magic: kimage=vmlinuz, image_dest=/
 image_name=vmlinuz-3.2.0-2-amd64, src_dir=/boot/ at 
/var/lib/dpkg/info/linux-image-3.2.0-2-amd64.postinst line 449, STDIN line 2.
handle_missing_link: kimage=vmlinuz, image_dest=/
 image_name=vmlinuz-3.2.0-2-amd64, src_dir=/boot/ at 
/var/lib/dpkg/info/linux-image-3.2.0-2-amd64.postinst line 336, STDIN line 2.
Test relative: testing /boot/ - / at 
/var/lib/dpkg/info/linux-image-3.2.0-2-amd64.postinst line 130, STDIN line 2.
image_magic: kimage=initrd.img, image_dest=/
 image_name=initrd.img-3.2.0-2-amd64, src_dir=/boot/ at 
/var/lib/dpkg/info/linux-image-3.2.0-2-amd64.postinst line 449, STDIN line 2.
handle_missing_link: kimage=initrd.img, image_dest=/
 image_name=initrd.img-3.2.0-2-amd64, src_dir=/boot/ at 
/var/lib/dpkg/info/linux-image-3.2.0-2-amd64.postinst line 336, STDIN line 2.
Test relative: testing /boot/ - / at 
/var/lib/dpkg/info/linux-image-3.2.0-2-amd64.postinst line 130, STDIN line 2.
Examining /etc/kernel/postinst.d.
run-parts: executing /etc/kernel/postinst.d/dracut 3.2.0-2-amd64 
/boot/vmlinuz-3.2.0-2-amd64
run-parts: executing /etc/kernel/postinst.d/pm-utils 3.2.0-2-amd64 
/boot/vmlinuz-3.2.0-2-amd64
run-parts: executing /etc/kernel/postinst.d/zz-update-grub 3.2.0-2-amd64 
/boot/vmlinuz-3.2.0-2-amd64
Generating grub.cfg ...
Found linux image: /boot/vmlinuz-3.2.0-2-amd64
Found initrd image: /boot/initramfs-3.2.0-2-amd64.img
Found memtest86+ image: /boot/memtest86+.bin
Found memtest86+ multiboot image: /boot/memtest86+_multiboot.bin
done


wheezy[~]# ls -l /vmlinu* /initr* /boot/vmlinu* /boot/initr*
-rw-r--r-- 1 root root 14130547 Apr 10 18:13 /boot/initramfs-3.2.0-2-amd64.img
-rw-r--r-- 1 root root  2804816 Mar 20 20:35 /boot/vmlinuz-3.2.0-2-amd64
lrwxrwxrwx 1 root root   30 Apr 10 18:12 /initrd.img - 
/boot/initrd.img-3.2.0-2-amd64
lrwxrwxrwx 1 root root   26 Apr 10 18:12 /vmlinuz - 
boot/vmlinuz-3.2.0-2-amd64


wheezy[~]# /var/lib/dpkg/info/linux-image-3.2.0-2-amd64.postinst configure
Running depmod.
image_magic: kimage=vmlinuz, image_dest=/
 image_name=vmlinuz-3.2.0-2-amd64, src_dir=/boot/ at 
/var/lib/dpkg/info/linux-image-3.2.0-2-amd64.postinst line 449, STDIN line 2.
DEBUG: There is a symlink for vmlinuz
Move?: kimage=vmlinuz, image_dest=/, 
image_name=vmlinuz-3.2.0-2-amd64, src_dir=/boot/ at 
/var/lib/dpkg/info/linux-image-3.2.0-2-amd64.postinst line 185, STDIN line 2.
DEBUG: OK. We found symlink, and we should have a symlink here.
DEBUG: The link vmlinuz points to (boot/vmlinuz-3.2.0-2-amd64)
DEBUG: (boot/vmlinuz-3.2.0-2-amd64) is really (/boot/vmlinuz-3.2.0-2-amd64)
vmlinuz(/boot/vmlinuz-3.2.0-2-amd64
) points to /boot/vmlinuz-3.2.0-2-amd64
 (/boot/vmlinuz-3.2.0-2-amd64) -- doing nothing at 
/var/lib/dpkg/info/linux-image-3.2.0-2-amd64.postinst line 268, STDIN line 2.
image_magic: kimage=initrd.img, image_dest=/
 image_name=initrd.img-3.2.0-2-amd64, src_dir=/boot/ at 
/var/lib/dpkg/info/linux-image-3.2.0-2-amd64.postinst line 449, STDIN line 2.
DEBUG: There is a symlink for initrd.img
Move?: kimage=initrd.img, image_dest=/, 
image_name=initrd.img-3.2.0-2-amd64, src_dir=/boot/ at

Bug#409271: dracut can do NFS v4

2012-01-17 Thread Thomas Lange 
Just for the record.

The dracut package has NFS v4 support. Maybe it's easier to use dracut
instead of waiting for klibc supporting it.
-- 
regards Thomas



-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/20245.35419.296341.428...@malzmuehle.informatik.uni-koeln.de

Bug#453294: ignores boot=live, order of parameters is important

2007-11-28 Thread Thomas Lange 
Package: initramfs-tools
Version: 0.85h

I'm using initramfs-tools and live-initramfs to boot my FAI
environment. Therefore I have to append boot=live and root=/dev/nfs to
get the live-initramfs scripts executed.

If I use this order

boot=live root=/dev/nfs

it does not work, since the script /usr/share/initramfs-tools/init
defines boot=nfs when parsing root=/dev/nfs. So my definition of
boot=live get overwritten.

Using the order root=/dev/nfs boot=live 
work without any hassle.

-- 
regards Thomas



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]