Summary: | [PATCH] According to changes in Genkernel integrated with Dracut | ||
---|---|---|---|
Product: | Gentoo Hosted Projects | Reporter: | Amadeusz Żołnowski (RETIRED) <aidecoe> |
Component: | Catalyst | Assignee: | Gentoo Catalyst Developers <catalyst> |
Status: | RESOLVED WONTFIX | ||
Severity: | normal | CC: | kanelxake, nikoli |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: | 0001-fixes-for-Dracut.patch |
Description
Amadeusz Żołnowski (RETIRED)
![]() Created attachment 242127 [details, diff]
0001-fixes-for-Dracut.patch
Why do you need the old genkernel generator for netboot? Does this mean that for netboot you need the ramdisk genkernel genkernel today, and there is no way dracut can generate that kind of ramdisk? (In reply to comment #2) > Why do you need the old genkernel generator for netboot? > Does this mean that for netboot you need the ramdisk genkernel genkernel today, Yes. > and there is no way dracut can generate that kind of ramdisk? There is. Everything is possible. :-) I have talked a bit with armin76 some time ago about it and I think I will know how to handle Catalyst problems. When I will have more time, I will take different approach for integration Dracut with Genkernel. |