Op 25-4-2013 19:44, Adam Williamson schreef:
On Wed, 2013-04-24 at 18:48 +0200, A.J. Werkman wrote:
This is the link about the SYSLINUX feature: https://fedoraproject.org/wiki/Features/SyslinuxOption
It talks about a anaconda hidden option and a kickstart option:
- How do I prepare my system to test this feature? What packages need
to be installed, config files edited, etc.?
Enable syslinux in kickstart with whatever option is decided upon, or via the similar Anaconda hidden option.
I can't find how this option is called.
I remember reading the feature too, but I haven't heard of it being added to anaconda yet. Let me check the git logs...
...yeah, nothing in there either. It looks like this just hasn't been added to anaconda at all yet. You might ask in #anaconda and see what their knowledge of this feature is.
Is/will the SYSLINUX feature be implemented in the upcomming F19?
Koos.
...yeah, nothing in there either. It looks like this just hasn't been added to anaconda at all yet. You might ask in #anaconda and see what their knowledge of this feature is.
Is/will the SYSLINUX feature be implemented in the upcomming F19?
Read Adam's last sentence again :-) It's best to ask at the source (anaconda team, which means #anaconda or @anaconda-devel).
Isn't that anaconda-devel-list@redhat.com?
Koos.
Op 26-4-2013 14:26, Kamil Paral schreef:
...yeah, nothing in there either. It looks like this just hasn't been added to anaconda at all yet. You might ask in #anaconda and see what their knowledge of this feature is.
Is/will the SYSLINUX feature be implemented in the upcomming F19?
Read Adam's last sentence again :-) It's best to ask at the source (anaconda team, which means #anaconda or @anaconda-devel).
Anaconda-devel-list mailing list Anaconda-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/anaconda-devel-list
On Fri, Apr 26, 2013 at 11:17:55AM -0400, Chris Lumens wrote:
Is/will the SYSLINUX feature be implemented in the upcomming F19?
We're all really quite busy and it's not on anyone's todo list, so the only way it's going to get implemented is if someone who cares submits some patches for us to review.
It is on my todo list. Patches coming in one minute. :)
On Fri, Apr 26, 2013 at 04:16:57PM -0400, Matthew Miller wrote:
On Fri, Apr 26, 2013 at 11:17:55AM -0400, Chris Lumens wrote:
Is/will the SYSLINUX feature be implemented in the upcomming F19?
We're all really quite busy and it's not on anyone's todo list, so the only way it's going to get implemented is if someone who cares submits some patches for us to review.
It is on my todo list. Patches coming in one minute. :)
I'm also keeping
https://fedoraproject.org/wiki/Features/SyslinuxOption#Current_status
up-to-date, by the way.
On 26.04.2013 22:22, Matthew Miller wrote:
[…]
I'm also keeping
https://fedoraproject.org/wiki/Features/SyslinuxOption#Current_status
Documentation …
Obviously the Arch people don't use grubby[1]. ;)
poma
[1] https://git.fedorahosted.org/cgit/grubby.git/tree/grubby.c#n457 "grubby fatal error: unable to find a suitable template" i.e. "DBG: Image entry failed: no line found"
On Tue, Apr 30, 2013 at 03:36:39PM +0200, poma wrote:
I'm also keeping https://fedoraproject.org/wiki/Features/SyslinuxOption#Current_status
Obviously the Arch people don't use grubby[1]. ;)
grubby is rather picky about the formatting of the file. Patches are definitely welcome to improve that.
On Tue, Apr 30, 2013 at 01:12:23PM -0400, Matthew Miller wrote:
I'm also keeping https://fedoraproject.org/wiki/Features/SyslinuxOption#Current_status
Obviously the Arch people don't use grubby[1]. ;)
grubby is rather picky about the formatting of the file. Patches are
^ config
On 30.04.2013 19:42, Matthew Miller wrote:
On Tue, Apr 30, 2013 at 01:12:23PM -0400, Matthew Miller wrote:
I'm also keeping https://fedoraproject.org/wiki/Features/SyslinuxOption#Current_status
Obviously the Arch people don't use grubby[1]. ;)
grubby is rather picky about the formatting of the file. Patches are
^ config
I actually thought it would be good to put a warning on[1] the use of the "kernel" entry in the "extlinux.conf" - i.e. the difference between the respective use of the Fedora's grubby and what is stated on the Arch links[1].
poma
[1] https://fedoraproject.org/wiki/Features/SyslinuxOption#Documentation
On 26.04.2013 22:22, Matthew Miller wrote:
On Fri, Apr 26, 2013 at 04:16:57PM -0400, Matthew Miller wrote:
On Fri, Apr 26, 2013 at 11:17:55AM -0400, Chris Lumens wrote:
Is/will the SYSLINUX feature be implemented in the upcomming F19?
We're all really quite busy and it's not on anyone's todo list, so the only way it's going to get implemented is if someone who cares submits some patches for us to review.
It is on my todo list. Patches coming in one minute. :)
I'm also keeping
https://fedoraproject.org/wiki/Features/SyslinuxOption#Current_status
up-to-date, by the way.
Fedora-19-Beta-TC2-i386-netinst.iso
https://fedoraproject.org/wiki/Features/SyslinuxOption#Current_status … updates=http://mattdm.fedorapeople.org/updates-f19-extlinux.img extlinux …
Could not find kernel image: menu.c32 boot: Could not find kernel image: menu.c32 boot: […]
file /etc/extlinux.conf /etc/extlinux.conf: broken symbolic link to `../boot/extlinux/extlinux.conf'
For a successful boot[1][2].
poma
[1] mv/cp /boot/extlinux.conf /boot/extlinux/extlinux.conf
[2] --- /boot/extlinux.conf 2013-05-03 01:45:35.000000000 -0400 +++ /boot/extlinux/extlinux.conf 2013-05-03 01:39:17.000000000 -0400 @@ -10,10 +10,10 @@ #totaltimeout 9000
label Fedora (0-rescue-e567d261136e65c44daec4be883d00f5) - kernel /boot/vmlinuz-0-rescue-e567d261136e65c44daec4be883d00f5 + kernel /vmlinuz-0-rescue-e567d261136e65c44daec4be883d00f5 append rd.lvm.lv=fedora/swap rd.md=0 rd.dm=0 root=/dev/mapper/fedora-root vconsole.keymap=us rd.lvm.lv=fedora/root initrd=/initramfs-0-rescue-e567d261136e65c44daec4be883d00f5.img rd.luks=0 rhgb quiet
label Fedora-3.9.0-301.fc19.i686.PAE (3.9.0-301.fc19.i686.PAE) - kernel /boot/vmlinuz-3.9.0-301.fc19.i686.PAE + kernel /vmlinuz-3.9.0-301.fc19.i686.PAE append rd.lvm.lv=fedora/swap rd.md=0 rd.dm=0 initrd=/initramfs-3.9.0-301.fc19.i686.PAE.img rd.luks=0 vconsole.keymap=us rd.lvm.lv=fedora/root root=/dev/mapper/fedora-root rhgb quiet
run/install/updates/pyanaconda/bootloader.py class EXTLINUX(BootLoader) need some love :)
On Fri, May 03, 2013 at 08:10:19AM +0200, poma wrote:
file /etc/extlinux.conf /etc/extlinux.conf: broken symbolic link to `../boot/extlinux/extlinux.conf' For a successful boot[1][2].
There's apparently a problem with a separate /boot partition. Working on figuring that out.
On Fri, May 03, 2013 at 08:10:19AM +0200, poma wrote:
updates=http://mattdm.fedorapeople.org/updates-f19-extlinux.img extlinux Could not find kernel image: menu.c32 boot: Could not find kernel image: menu.c32
This is fixed now in a newer (but same URL) updates.img.
On 06.05.2013 23:48, Matthew Miller wrote:
On Fri, May 03, 2013 at 08:10:19AM +0200, poma wrote:
updates=http://mattdm.fedorapeople.org/updates-f19-extlinux.img extlinux Could not find kernel image: menu.c32 boot: Could not find kernel image: menu.c32
This is fixed now in a newer (but same URL) updates.img.
Appreciate. :)
To conclude. After successful installation extlinux's default kernel is the 'rescue' one, unlike the grub's.[5] However, both boot's schemes do work: kernel [/boot]/vmlinuz* initrd=[/boot]/initramfs* Anyhow a standalone initrd entry is more legible than an appended one, to me. There is some timeout at the end of the installation, just before rebooting, unlike with the grub.[4][3] After all, grub is good reference, right. :) There is a picturesque display how to take up installation accompanied by the extlinux, if it isn't so obvious.[2][1] :) At the very end, I've mentioned before anaconda showing: "Pane is dead" which is repeated even with your 'updates-f19-extlinux.img' - extracted and then assembled via: anaconda/scripts/upd-updates update-extlnx.img run/install/updates/pyanaconda/bootloader.py run/install/updates/pyanaconda/flags.py usr/sbin/anaconda How do you manage to do it, may I ask?
poma
[5][4][3][2][1] http://goo.gl/G5ShD
…
At the very end, I've mentioned before anaconda showing: "Pane is dead" which is repeated even with your 'updates-f19-extlinux.img' - extracted and then assembled via: anaconda/scripts/upd-updates update-extlnx.img run/install/updates/pyanaconda/bootloader.py run/install/updates/pyanaconda/flags.py usr/sbin/anaconda How do you manage to do it, may I ask?
The issue was dirs permissions. I should've checked via 'lsinitrd' before installing, may I say. :) Sorry.
poma
…
Anyhow a standalone initrd entry is more legible than an appended one, to me.
…
This[1] patch is based on your 'bootloader.py' from 'updates-f19-extlinux.img'[2] with an increment from me - standalone initrd entry(extlinux.conf). Patched against anaconda's git commit 0578bafb968da06a4ae9b627ffd5de1d9871eb4d Can be tested[4] with the updates image - 'updates-extlnx.img'[3].
poma
[1] bootloader.py-extlnx.diff(attach) [2] http://mattdm.fedorapeople.org/updates-f19-extlinux.img [3] ftp://ftp.leeds.ac.uk/incoming/extlinux/updates-extlnx.img [4] "… 7 days" :)
On Thu, May 09, 2013 at 06:53:55PM +0200, poma wrote:
Anyhow a standalone initrd entry is more legible than an appended one, to me.
Yeah, I'm in favor.
HOWEVER: have you tested that this works with grubby? Because I get an error about unable to find a suitable template unless initrd is on the append line.
Since grubby just works with the other configuration and it's really just cosmetic, I figured I wouldn't bother for F19. If you'd like to fix the problem in grubby, though, that'd be cool.
(Also, while there, it'd be nice for it to support 'linux' in addition to 'kernel'.)
On 09.05.2013 19:44, Matthew Miller wrote:
On Thu, May 09, 2013 at 06:53:55PM +0200, poma wrote:
Anyhow a standalone initrd entry is more legible than an appended one, to me.
Yeah, I'm in favor.
HOWEVER: have you tested that this works with grubby? Because I get an error about unable to find a suitable template unless initrd is on the append line.
Since grubby just works with the other configuration and it's really just cosmetic, I figured I wouldn't bother for F19. If you'd like to fix the problem in grubby, though, that'd be cool.
(Also, while there, it'd be nice for it to support 'linux' in addition to 'kernel'.)
It's your call, so you decide. ;) However, here Extlinux has no problemos with the 'grubby', at all[1]. For some time I use Extlinux on Fedora 18, also without problemos. I haven't even mentioned the Rawhide. So. And if I think about it twice, "kernel" is pretty good global keyword for the kernel's entries, and thus to linux kernel. But everything is prone to change. =)
poma
[1] 'f19-extlinux-initrd-OK.txt'(attach)
… In addition: # grep extlinux /var/log/anaconda/syslog 06:02:28,961 NOTICE kernel:[ 0.000000] Kernel command line: initrd=initrd.img inst.stage2=hd:LABEL=Fedora\x2019-Beta-TC3\x20i386 updates=ftp://ftp.leeds.ac.uk/incoming/extlinux/updates-extlnx.img extlinux BOOT_IMAGE=vmlinuz # # grep -A1 extlinux /var/log/anaconda/anaconda.program.log 06:14:33,087 INFO program: Running... extlinux --install /boot/extlinux 06:14:33,367 INFO program: /boot/extlinux is device /dev/vda1 06:14:33,369 DEBUG program: Return code: 0
poma
On Thu, May 09, 2013 at 10:35:14PM +0200, poma wrote:
However, here Extlinux has no problemos with the 'grubby', at all[1]. For some time I use Extlinux on Fedora 18, also without problemos.
That is very strange. I used this exact file, removed the 3.9.1 kernel, and then reinstalled the kernel, and again got the grubby can't-find-template error. The only significant difference is that my system is x86_64 (so I did make that alteration). I'll try a fresh i686 install and see if I can reproduce.
On May 10, 2013, at 9:19 AM, Matthew Miller mattdm@fedoraproject.org wrote:
On Thu, May 09, 2013 at 10:35:14PM +0200, poma wrote:
However, here Extlinux has no problemos with the 'grubby', at all[1]. For some time I use Extlinux on Fedora 18, also without problemos.
That is very strange. I used this exact file, removed the 3.9.1 kernel, and then reinstalled the kernel, and again got the grubby can't-find-template error. The only significant difference is that my system is x86_64 (so I did make that alteration). I'll try a fresh i686 install and see if I can reproduce.
Is /boot on Btrfs? https://bugzilla.redhat.com/show_bug.cgi?id=864198
Chris Murphy
On 05/11/2013 11:22 AM, Chris Murphy wrote:
On May 10, 2013, at 9:19 AM, Matthew Miller mattdm@fedoraproject.org wrote:
On Thu, May 09, 2013 at 10:35:14PM +0200, poma wrote:
However, here Extlinux has no problemos with the 'grubby', at all[1]. For some time I use Extlinux on Fedora 18, also without problemos.
That is very strange. I used this exact file, removed the 3.9.1 kernel, and then reinstalled the kernel, and again got the grubby can't-find-template error. The only significant difference is that my system is x86_64 (so I did make that alteration). I'll try a fresh i686 install and see if I can reproduce.
Is /boot on Btrfs? https://bugzilla.redhat.com/show_bug.cgi?id=864198
Currently the name of the game is Ext[234]linux[1][2]. Somehow I doubt that this is a file system problem. ;)
poma
[1] https://lists.fedorahosted.org/pipermail/anaconda-patches/2013-May/004084.ht... [2] https://git.fedorahosted.org/cgit/anaconda.git/tree/pyanaconda/bootloader.py...
anaconda-devel@lists.fedoraproject.org
-
A.J. Werkman -
Chris Lumens -
Chris Murphy -
Kamil Paral -
Matthew Miller -
poma