On 17/04/17 05:05 AM, Felix Miata wrote:
https://bugzilla.opensuse.org/show_bug.cgi?id=447981 Closed worksforme 9 years ago. should I reopen it? Clone it? File from scratch? Simotek on IRC said file a bug, but I wonder if there is some other editor on installation media that I just don't know how to find.
I booted the 42.2 rescue system to try to see what's what. The only editors I could get to open were Edit, Joe and Vim. All have the same non-interface that's unfriendly to non-veteran users of the vi/ed interface paradigm.
Also, the rescue shell's help command suggests 'info bash' and 'man -k' to get more help. Both commands produce "command not found".
Before I file any bug, I wonder whether the rescue system is complete when launched from a Grub boot (here, normally used for HTTP installations instead of creating media from isos) that specifies only linux and initrd? Help works. Mount works. Gdisk and fdisk work. Same results tried with TW instead of 42.2.
I would not expect a RESCUE system to be a complete, fully functional system. It is a debug & repair environment. It is not an everyday system, except possibly for those at the 'repair bench' of a support organization. I would expect it to be a) for use only by people who know what they are doing, 'cos this is ROOT power and to repair the system b) the rest of the system is out there ... if you can make it work The times I've needed to use the rescue system my boot or kernel is the thing that's been borked. Or possible the RootFS - which was common in the early days of BtrFS. I can, thank you the developers of LVM and thanks to my obsession with multiple file systems as well as /home, mount other file systems such as /usr/share. I've discussed in other threads why I choose to have all these separate file systems, here's another reason. I can mount an intact /usr and /usr/share and so have access to, for example, the man pages that you mention. I usually end up repairing the old RootFS, mounting that (with a few other bits of setup that I'll pass over here) and then doing a CHROOT. So now I'm in my old running system and can do proper things like 'mkinitrd' and Hence the system is rescued. Wasn't that the point? A RESCUE system is for doing serious level repairs. That's not for noobs. It for people who know what they are doing .... 'Under the hood". I don't expect this to be user-friendly, have eye candy or training wheels. When I do this my MAN PAGES are the handwritten notes and in my book of notes, the one that includes all the notes I took when doing setups, when doing this kind of thing in the past. The kind of information I expect to need when I don't have a running system or an off-lined system. "Dead trees" have their uses.
From my DatbaseOfDotSigQuotes: "The master worries about the work, and the apprentice worries about the tools" -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org