On Fri, Feb 28, 2025 at 6:44 PM Kenneth Gober <kgober@gmail.com> wrote:
>
> On Thu, Feb 27, 2025 at 2:57 PM Mihai Popescu <mihscu@gmail.com> wrote:
>>
>> So, my idea is to preface all remaining sections with echo -n
>> "Starting to do X ...." then ending with "Done." Pretty much like
>> printf debugging.
>> Still I don;t know yet to build my final .img file to test with it.
>> I guess i will stop here for the moment, till someone will hit that issue too.
>
>
> You don't need to build an entire image to test changes to the installer.
>
> When you reach the "(I)nstall, (U)pgrade, (A)utoinstall or (S)hell?" prompt
> choose (S)hell. Then you can edit install.sub and/or install.md directly if
> you know how to use ed(1) or sed(1), or you can copy pre-edited files from
> somewhere else (a mounted file system, a thumb drive containing a tar
> image, ftp/http or nfs if you manually bring up the network, etc.)
>
> Once you're done, exit from the shell and the installer will restart, now with
> your changes.
>
> -ken
Thank you, i checked that and I can find the files. About ed(1) or
sed(1) thank you but not thank you. Please do not send me back to
punched cards computers era. It was fun to draw on them as a kid, but
I don;t want to go there anymore :)
I tried many methods, but always i got stuck. I don;t even understand
why the bootblock phase was not signaled with an echo and fdisk
message is out to null, still there is the congratulations message
out.
I tried a snapshot from ftp.hostserver.de, the
archive/2025-02-01-0105/ section, it works.
I will continue with bisect method, between that archive section and
the date when my install broke. It will take a while since I have only
one computer to download, write the usb stick and test.
Thank you.
No comments:
Post a Comment