[Yaird-devel] Bug#337293: yaird vs initramfs

[ingo wagener]

Dear Jonas,

thank you for your comprehensive reply. As I stated I reverted back to the 
more or less original setup. I have now opted for initramfs-tools as yaird 
left my system unbootable.

I understand what you are saying re the design but I would have thought that 
this approach will leave a lot of people who tinker with their partitioning 
thinking that Debian is broken for good :( Also, I had to google quite 
extensively to find the cause of the problem I experienced, i.e. 
documentation is lacking.

I will write a report of my experiences in the Debian forum and would hope 
that you or the person responsible warn of this apparent misbehaviour (after 
all, you don't need me to tell you that this "you should have..." approach is 
not very helpful to someone trying to get their system up again) on the yaird 
website - incl. the error message the system spits out and an easy to follow 
way out of the mess thus created.

Obviously as "normal" end user I would consider this kind of behaviour buggy - 
you as developer would obviously say that it is inherent in the design. 
Difficult one... All I can say that any user will be quite dumbfounded by 
Debian breaking on him like this. After all, anyone might tinker with their 
partitioning at one stage or other. Furthermore, more likely than not that as 
soon as any user has realised what lies at its root s/he will probably change 
to initramfs and shake their head in bewilderment...

I obviously wish that yaird be changed to be more flexible but as for 
suspecting that it can be made so - I have not the slightest idea! I am 
afraid I know nothing about programming, being a translator by trade and as 
such only a "dumb" end user :(

Right now for that report - after all, documentation is a good thing - and 
once again thank you for your detailed reply.

Best wishes

Ingo Wagener

PS.: I wondered why my chrooting from knoppix wouldn't work - thank you for 
your explanation!