Re: PXE boot in F17 has changed considerably?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Here is the "default" I use.  Askmothod is ignored.
I installed 3312 apps on the last pxeboot install.

On 04/28/2012 09:49 PM, Tom H wrote:
On Sat, Apr 28, 2012 at 5:03 PM, Mark Zhitomirski<markj@xxxxxxx>  wrote:
I've got used to installing Fedora 15/16 via PXE by simply putting/modifying a couple of lines in pxelinux.cfg/default like these:

LABEL Fedora16
    MENU LABEL Install Fedora 16 x86-64
    KERNEL fedora16x64/vmlinuz
    initrd fedora16x64/initrd.img

vmlinuz and initrd.img were taken from
linux/releases/16/Fedora/x86_64/os/images/pxeboot/
in case of F16

However when i do the same with files from
linux/releases/test/17-Beta/Fedora/x86_64/os/images/pxeboot/
or
linux/development/17/x86_64/os/images/pxeboot/
i get the following errors (both on a real and on a virtual machine):
====
dracut: anaconda using disk root at /dev/sr0
dracut Warning: Couldn't mount /dev/sr0
dracut Warning: no suitable images
dracut Warning: /dev/root does not exists

Dropping to debug shell
===

Is this the expected behavior and was it discussed / documented somewhere?
http://lists.fedoraproject.org/pipermail/test/2012-February/105658.html

http://lists.fedoraproject.org/pipermail/test/2012-February/105514.html

--
Chuck Forsberg WA7KGX N2469R     caf@xxxxxxxx   www.omen.com
Developer of Industrial ZMODEM(Tm) for Embedded Applications
  Omen Technology Inc      "The High Reliability Software"
10255 NW Old Cornelius Pass Portland OR 97231   503-614-0430

prompt 1
default linux
timeout 100

label linux
kernel vmlinuz
append initrd=initrd.img ramdisk_size=9216 askmethod root=live:http://192.168.1.13/squashfs.img repo=http://192.168.1.13/fc17/os
-- 
test mailing list
test@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test

[Index of Archives]     [Fedora Desktop]     [Fedora SELinux]     [Photo Sharing]     [Yosemite Forum]     [KDE Users]

  Powered by Linux