You are not logged in.
Generated a pkg having the correct config file but vmlinuz26 is the ID for the kernel tie-in which is the same as that provided in /root/boot.
I desire to boot from the above boot data( map also provided) and do not know how to establish correct lilo boot statement.
Do I move the pkg to /root/boot and call pkg?
The last iteration of a kernel-custom resulted in a custom vmlinuz ID but the config was incorrect.
This time the reverse is true...correct config...suspected trouble with vmlinuz26 since it is the same as the original kernel26 vmlinuz26.
Can I reidentify the vmlinuz in the subject file, transfer it to /root/boot and solve this problem?
Prediction...This year will be a very odd year!
Hard work does not kill people but why risk it: Charlie Mccarthy
A man is not complete until he is married..then..he is finished.
When ALL is lost, what can be found? Even bytes get lonely for a little bit! X-ray confirms Iam spineless!
Offline
Yes, reidentify vmlinuz26 as vmlinuz26a and copy into /root/boot solved the problem.
Prediction...This year will be a very odd year!
Hard work does not kill people but why risk it: Charlie Mccarthy
A man is not complete until he is married..then..he is finished.
When ALL is lost, what can be found? Even bytes get lonely for a little bit! X-ray confirms Iam spineless!
Offline