On Fri, 25 Sep 2020 at 10:40, anthony gennard <agen...@gmail.com> wrote:
> > > > On Thu, 24 Sep 2020 at 10:11, anthony gennard <agen...@gmail.com> wrote: > >> Thanks very much; it will take me some time to understand your advice. I >> will revert as soon as I can. >> >> On Thu, 24 Sep 2020 at 15:03, Hans <hans.ullr...@loop.de> wrote: >> >>> Am Donnerstag, 24. September 2020, 15:45:47 CEST schrieb Greg Wooledge: >>> I believe, the op wants to look it as easy as possible. So I suggest >>> kwrite >>> (if he has plasma5 aka KDE installed). >>> >>> You must got the correct rights. Either you start plasma as root, then >>> you can >>> just start kwrite and open the log file. or, ifr you start plasma as >>> normal >>> user, do this: >>> >>> >>> Start a konsole (like xterm, konsole, uxterm) >>> >>> then type in "su -p" (without quotes) and enter the password of root. >>> >>> and last start "kwrite" in this konsole >>> >>> Now you can open your logfile. >>> >>> If you are using another window-manager like GNOME, LXDE, Enligtenment >>> whatever, it might got another graphical editor. >>> >>> Note: Every graphical application can be started with higher rights from >>> the >>> konsole (or terminal, how others may call it), by getting higher rights >>> with >>> su -p. (the -p stands for "preserve actual environment). >>> >>> Good luck >>> >>> Hans >>> >>> >>> >>> > On Thu, Sep 24, 2020 at 09:59:57AM +0100, anthony gennard wrote: >>> > > I am looking at the contents of my boot log file; when trying to get >>> out >>> > > of >>> > > the very long file I thought Ctrl + c should do it - it does not and >>> I >>> > > cannot >>> > > find any way. I wanted to try tail and head so see how they do. Can >>> anyone >>> > > please help me. >>> > >>> > How are you "looking at" the file? I would suggest using less. >>> > >>> > You get out of less by pressing q. >>> >>> >>> >>> >>>
