Void Linux discussion
 help / color / mirror / Atom feed
From: Pierre Bourgin <pbou...@gmail.com>
To: voidlinux@googlegroups.com
Subject: Live image not usable from network boot : dracut lack of support of NFS/tftp ?
Date: Fri, 12 Jun 2015 00:14:32 -0700 (PDT)	[thread overview]
Message-ID: <91f403ae-3ffa-472e-860a-796f709b003f@googlegroups.com> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 1332 bytes --]

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

[-- Attachment #1.2: Type: text/html, Size: 8470 bytes --]

             reply	other threads:[~2015-06-12  7:14 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-12  7:14 Pierre Bourgin [this message]
2015-06-12  7:39 ` Juan RP
2015-06-12  7:47   ` Duncaen
2015-06-12  8:21     ` Pierre Bourgin

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=91f403ae-3ffa-472e-860a-796f709b003f@googlegroups.com \
    --to="pbou..."@gmail.com \
    --cc=voidlinux@googlegroups.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).