Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.user > #227391
| From | anthony gennard <agennae@gmail.com> |
|---|---|
| Newsgroups | linux.debian.user |
| Subject | Re: Returning to /var/log/boot.log and Greg Wooledge`s reply |
| Date | 2020-09-26 13:20 +0200 |
| Message-ID | <ATgpb-4jL-1@gated-at.bofh.it> (permalink) |
| References | <ASSZA-7cp-3@gated-at.bofh.it> <AT8rE-7Tt-5@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
[Multipart message — attachments visible in raw view] - view raw
Thanks. The error with the p instead of q was stupid and just the tiredness I felt at the time, I am 90 after all. I was using q when getting out of the log file. Thanks for the other advice. I am greatly confused about my next attempt. I am trying to install my network printer. an Epson XP 2100, it`s a nightmare. I`ll likely be back asking for help with this. Regards. Anthony John. On Sat, 26 Sep 2020 at 03:48, David Wright <deblis@lionunicorn.co.uk> wrote: > On Fri 25 Sep 2020 at 11:19:40 (+0100), anthony gennard wrote: > > My email has gone haywire and I cannot reply to two of the messages. > > Fortunately, I had made copies of them. > > Greg Wooledge said to me > > >"How are you `looking at ` the file? > > >I would suggest using less. > > > > >You get out of less by pressing p > > No, q, not p. You get out of less with q. > But Ctrl-C can be useful if you do something like search for > a string in a huge file and want to interrupt it because it's > taking too long. > > > Greg, I was using less. > > What I did was:- Open a terminal by ctrl + alt + F1 > > `cd /var/log` then `ls` and I could see boot.log amongst the list of > files > > then I did `sudo less boot.log` and got the list of start ups. > > At this point I was stuck and asked the list for help. > > I was such a fool because I did not look up the man page for less. > > I went through the process and pressed p and low and behold and was back > to > > the `root@??? /var/log`. > > Thank you. > > Now I have to try and print a copy of the first 100 or so lines which > > will give me the last boot up details. > > If you make yourself a member of the adm group, you can read your logs > as a normal user. You'd need to type into any terminal > > $ sudo addgroup myloginname adm > > replacing myloginname as appropriate, but you will need to login again > before the addgroup command will have any effect. > > Cheers, > David. > >
Back to linux.debian.user | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
Returning to /var/log/boot.log and Greg Wooledge`s reply anthony gennard <agennae@gmail.com> - 2020-09-25 12:20 +0200
Re: Returning to /var/log/boot.log and Greg Wooledge`s reply David Wright <deblis@lionunicorn.co.uk> - 2020-09-26 04:50 +0200
Re: Returning to /var/log/boot.log and Greg Wooledge`s reply anthony gennard <agennae@gmail.com> - 2020-09-26 13:20 +0200
Re: Returning to /var/log/boot.log and Greg Wooledge`s reply Richard Hector <richard@walnut.gen.nz> - 2020-09-28 07:30 +0200
Re: Returning to /var/log/boot.log and Greg Wooledge`s reply rhkramer@gmail.com - 2020-09-28 13:50 +0200
Re: Returning to /var/log/boot.log and Greg Wooledge`s reply Richard Hector <richard@walnut.gen.nz> - 2020-09-28 14:50 +0200
Re: Returning to /var/log/boot.log and Greg Wooledge`s reply David Wright <deblis@lionunicorn.co.uk> - 2020-09-28 16:20 +0200
Re: Returning to /var/log/boot.log and Greg Wooledge`s reply rhkramer@gmail.com - 2020-09-28 16:40 +0200
csiph-web