From mboxrd@z Thu Jan 1 00:00:00 1970 X-Received: by 10.182.65.164 with SMTP id y4mr16590405obs.26.1434093272970; Fri, 12 Jun 2015 00:14:32 -0700 (PDT) X-BeenThere: voidlinux@googlegroups.com Received: by 10.140.106.35 with SMTP id d32ls2162060qgf.64.gmail; Fri, 12 Jun 2015 00:14:32 -0700 (PDT) X-Received: by 10.140.39.165 with SMTP id v34mr200923qgv.25.1434093272770; Fri, 12 Jun 2015 00:14:32 -0700 (PDT) Date: Fri, 12 Jun 2015 00:14:32 -0700 (PDT) From: Pierre Bourgin To: voidlinux@googlegroups.com Message-Id: <91f403ae-3ffa-472e-860a-796f709b003f@googlegroups.com> Subject: Live image not usable from network boot : dracut lack of support of NFS/tftp ? MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----=_Part_117_81806357.1434093272286" ------=_Part_117_81806357.1434093272286 Content-Type: multipart/alternative; boundary="----=_Part_118_549391224.1434093272286" ------=_Part_118_549391224.1434093272286 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Hello, I would like a networked boot (PXE) of the VoidLinux live image. So I try to reuse content of ISO file (unsquash Live FS, etc) I've tried the following PXE/tftpboot configuration, but none of them are working: LABEL VL32bit.nfs MENU LABEL VoidLinux Live Mate i686 (2015-04) - NFS KERNEL kernels/voidlinux/i686/cdrom/boot/vmlinuz APPEND initrd=kernels/voidlinux/i686/cdrom/boot/initrd root=live:nfs:192.168 .50.1:/share/tftpboot/kernels/voidlinux/i686/rootfs.liveOS/root [other parameters] LABEL VL32bit.tftp MENU LABEL VoidLinux Live Mate i686 (2015-04) - tftp KERNEL kernels/voidlinux/i686/cdrom/boot/vmlinuz APPEND initrd=kernels/voidlinux/i686/cdrom/boot/initrd root=live:tftp://192.168.50.1/kernels/voidlinux/i686/rootfs.liveOS/LiveOS/ext3fs.img [other parameters] Loading of kernel and initrd files are fine, but dracut (launched from initrd) fails to work with the "root" parameter in both cases. I suspect that dracut has been built without tftp or NFS support in the voidlinux image ? Someone succeeded to have a VoidLinux Live image from network or did I missed something ? Do you plan to add support of tftp/NFS in initrd/dracut in order to have it ? This is really convinient to test a distribution without having to burn a CD and so on ... Thanks - Pierre ------=_Part_118_549391224.1434093272286 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable
Hello,

I would like a networked boot (PXE) of the V= oidLinux live image.
So I try to reuse content of ISO file (unsquash Liv= e FS, etc)

I've tried the following PXE/tftpboot configuration, but = none of them are working:

LABEL VL32bit.nfs
MENU LABEL VoidLinux Live = Mate i686 = (2015-04) -  NFS
KERNEL kernels/voidlinux/i686/= cdrom/boot/vmlinuz
APPEND initrd=3Dkernels/voidlinux/i686/cdrom/boot= /initrd root<= span style=3D"color: #660;" class=3D"styled-by-prettify">=3Dlive:nfs:192.168.50.1:/share/<= /span>tftpboot/kernels/voidlinux/i686/rootfs.liveOS/= root [other parameters<= span style=3D"color: #660;" class=3D"styled-by-prettify">]

LABEL VL32bit.tftp
MENU LABEL VoidLinux= Live Mate i686 (2015-= 04)= -  tftp
KERNEL kernels/voidlinux/i686/cdrom/boot/vmli= nuz
APPEND initrd=3Dkernels= /voidlinux= /i686/cdrom/boot/initrd root=3Dlive= :tftp://192.168.50.1/kernels/v= oidlinux/i686/rootfs.liveOS/LiveOS/ext3fs.img [other parameters]



Loading of kernel and initrd files are fine, but dracu= t (launched from initrd) fails to work with the "root" parameter in both cases.
I suspec= t that dracut has been built without tftp or NFS support in the voidlinux i= mage ?

Someone succeeded to have a VoidLinux Live image from network= or did I missed something ?

Do you plan to add support of tftp/NFS = in initrd/dracut in order to have it ?
This is really convinient to test= a distribution without having to burn a CD and so on ...

Thanks - P= ierre
------=_Part_118_549391224.1434093272286-- ------=_Part_117_81806357.1434093272286--