> When removing the symlinks in / then
> calling dpkg-reconfigure linux-image-amd64
> should create correct symlinks.
Perhabs I'm using an installation from debootstrap.
dpkg-reconfigure -a doesn't work any more and dpks --configure -a does nothing.
Can you add this bug to linux-image maintaine
> This may be the cause of calling dracut manually
You have to call it manually if you change something in config like black
listing modules.
But of the symlink to the wrong image the update won't work.
To: la...@informatik.uni-koeln.de
debian@zengel.org
763...@bugs.debian.org
--
> Jsut for the record. Without giving a peer this works perfectly.
It's not possible to let the peer empty. If I let it empty xen will fill it
with 127.0.255.255.
> Btw, you can also use 24 as netmask
I will try this.
To: la...@informatik.uni-koeln.de
763...@bugs.debian.org
--
To UNSU
> Which filename is wrong here?
initramfs-3.16-2-amd64.img is the wrong filename, because debian uses always
initrd.img-3.16-2-amd64.
To: la...@informatik.uni-koeln.de
debian@zengel.org
763...@bugs.debian.org
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
> Until now it's not an out-of-the-box install of xen diskless jessie posible.
An out-of-the-box install with latest version is working again.
I used initramfs-tools instead of dracut and it is working.
I didn't try nfs4 and was booting from nfs3 share.
To: la...@informatik.uni-koeln.de
deb
> Then, we should reassign the bug to the linux-image package.
If the problem with the wrong filename not exist any longer, we can do this.
To: la...@informatik.uni-koeln.de
debian@zengel.org
763...@bugs.debian.org
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.
> I also updated my jessie machine from 3.14 to 3.16, but my initrd
> has the correct file name.
What is the correct file name? /boot/initrd*?
Normally dracut uses initramfs* and debian uses initrd*. I have seen a posting
about this. I think it was your post from 2012.
I have installed my machi
> I also recognize that this symlink changes from wheezy to jessie. In
> wheezy this is a relative symlink, in jessie it's an absolute symlink.
>
> But I guess it's not dracut, that creates this symlink. I cannot find
> the code in dracut that creates this symlink.
I found some code here:
/var/l
There are some strange things with dracut and jessie:
I updated from kernel 3.14 to 3.16 and get this:
root@somesystem:~# ls -la /boot/
total 124782
drwxr-xr-x 2 root root 10 Oct 1 19:41 .
drwxr-xr-x 21 root root 25 Oct 1 19:41 ..
-rw-r--r-- 1 root root 153354 Aug 9 05:20 config
I didn't make this comand line. The comand line is made by xen config:
vif = [ 'bridge=br_bond0' ]
ip= '192.168.180.120'
netmask = '255.255.255.0'
gateway = '192.168.180.1'
broadcast = '192.168.180.255'
nfs_server = '192.168.180.100'
root= 'nfs:/srv/nfs/xen/asterisk.donner14.p
I didn't call dracut. It was called from aptitude after update of the kernel.
It was made inside the running VM.
Original Message
Subject: Re: Bug#763653: dracut make use of absolute path in soft link
"/initrd.ing" instead of relative (01-Okt-2014 21:09)
From:Thomas Lange
T
11 matches
Mail list logo
