Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.user > #227328 > unrolled thread

Returning to /var/log/boot.log and Greg Wooledge`s reply

Back to article view | Back to linux.debian.user

Contents

  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

#227328 — Returning to /var/log/boot.log and Greg Wooledge`s reply

[Multipart message — attachments visible in raw view] — view raw

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

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.

[toc] | [next] | [standalone]

#227379

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.

[toc] | [prev] | [next] | [standalone]

#227391

[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.
>
>

[toc] | [prev] | [next] | [standalone]

#227440

On 26/09/20 2:47 pm, David Wright wrote:
> 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.

I think you mean adduser rather than addgroup there:

$ sudo adduser myloginname adm

You're adding the user to the group, rather than the group to the user :-)

Richard

[toc] | [prev] | [next] | [standalone]

#227444

On Monday, September 28, 2020 01:28:01 AM Richard Hector wrote:
> On 26/09/20 2:47 pm, David Wright wrote:
> > 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.
> 
> I think you mean adduser rather than addgroup there:
> 
> $ sudo adduser myloginname adm
> 
> You're adding the user to the group, rather than the group to the user :-)

I think either will work:

from man adduser <one of five ways to invoke adduser>:

   Add an existing user to an existing group
       If  called  with  two non-option arguments, adduser will add an 
existing user to an existing group.


from man addgroup <one of five ways to invoke addgroup>:

   Add an existing user to an existing group
       If  called  with  two non-option arguments, adduser will add an 
existing user to an existing group.







> 
> Richard

[toc] | [prev] | [next] | [standalone]

#227450

On 29/09/20 12:40 am, rhkramer@gmail.com wrote:
> On Monday, September 28, 2020 01:28:01 AM Richard Hector wrote:
>> On 26/09/20 2:47 pm, David Wright wrote:
>> > 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.
>> 
>> I think you mean adduser rather than addgroup there:
>> 
>> $ sudo adduser myloginname adm
>> 
>> You're adding the user to the group, rather than the group to the user :-)
> 
> I think either will work:
> 
> from man adduser <one of five ways to invoke adduser>:
> 
>    Add an existing user to an existing group
>        If  called  with  two non-option arguments, adduser will add an 
> existing user to an existing group.
> 
> 
> from man addgroup <one of five ways to invoke addgroup>:
> 
>    Add an existing user to an existing group
>        If  called  with  two non-option arguments, adduser will add an 
> existing user to an existing group.

Those are both the same manpage (adduser(8)), which describes both
commands. Both instances of that quote refer to adduser :-)

addgroup is just a symlink to adduser, but behaves differently when
called with that name.

Richard

[toc] | [prev] | [next] | [standalone]

#227456

On Tue 29 Sep 2020 at 01:42:03 (+1300), Richard Hector wrote:
> On 29/09/20 12:40 am, rhkramer@gmail.com wrote:
> > On Monday, September 28, 2020 01:28:01 AM Richard Hector wrote:
> >> On 26/09/20 2:47 pm, David Wright wrote:
> >> > 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.
> >> 
> >> I think you mean adduser rather than addgroup there:
> >> 
> >> $ sudo adduser myloginname adm
> >> 
> >> You're adding the user to the group, rather than the group to the user :-)
> > 
> > I think either will work:
> > 
> > from man adduser <one of five ways to invoke adduser>:
> > 
> >    Add an existing user to an existing group
> >        If  called  with  two non-option arguments, adduser will add an 
> > existing user to an existing group.
> > 
> > 
> > from man addgroup <one of five ways to invoke addgroup>:
> > 
> >    Add an existing user to an existing group
> >        If  called  with  two non-option arguments, adduser will add an 
> > existing user to an existing group.
> 
> Those are both the same manpage (adduser(8)), which describes both
> commands. Both instances of that quote refer to adduser :-)
> 
> addgroup is just a symlink to adduser, but behaves differently when
> called with that name.

I just gave the OP a command that works. I hadn't expected it to
kick off a discussion, nor to have to justify it. But:

axis!david 08:55:22 ~ $ grep -e '^adm' -e '^unlock' /etc/group
adm:x:4:david
unlock:x:1010:
axis!david 08:55:47 ~ $ grep -e '^adm' -e '^unlock' /etc/group
adm:x:4:david,unlock
unlock:x:1010:
axis!david 08:56:40 ~ $ 

axis 08:51:11 ~#  addgroup unlock adm
Adding user `unlock' to group `adm' ...
Adding user unlock to group adm
Done.
axis 08:56:28 ~# 

Or, if you prefer it in a time sequence:

axis!david 08:55:22 ~ $ grep -e '^adm' -e '^unlock' /etc/group
adm:x:4:david
unlock:x:1010:
axis!david 08:55:47 ~ $ grep -e '^adm' -e '^unlock' /etc/group

axis 08:51:11 ~#  addgroup unlock adm
Adding user `unlock' to group `adm' ...
Adding user unlock to group adm
Done.
axis 08:56:28 ~# 

axis!david 08:55:47 ~ $ grep -e '^adm' -e '^unlock' /etc/group
adm:x:4:david,unlock
unlock:x:1010:
axis!david 08:56:40 ~ $ 

Buried in there is "addgroup unlock adm", where adm is the well-known
group, and unlock is the user whose sole function is to lock and
unlock /home partitions on my systems.

Cheers,
David.

[toc] | [prev] | [next] | [standalone]

#227457

On Monday, September 28, 2020 08:42:03 AM Richard Hector wrote:
> On 29/09/20 12:40 am, rhkramer@gmail.com wrote:
> > On Monday, September 28, 2020 01:28:01 AM Richard Hector wrote:
> >> On 26/09/20 2:47 pm, David Wright wrote:
> >> > 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.
> >> 
> >> I think you mean adduser rather than addgroup there:
> >> 
> >> $ sudo adduser myloginname adm
> >> 
> >> You're adding the user to the group, rather than the group to the user
> >> :-)
> > 
> > I think either will work:
> > 
> > from man adduser <one of five ways to invoke adduser>:
> >    Add an existing user to an existing group
> >    
> >        If  called  with  two non-option arguments, adduser will add an
> > 
> > existing user to an existing group.
> > 
> > from man addgroup <one of five ways to invoke addgroup>:
> >    Add an existing user to an existing group
> >    
> >        If  called  with  two non-option arguments, adduser will add an
> > 
> > existing user to an existing group.
> 
> Those are both the same manpage (adduser(8)), which describes both
> commands. Both instances of that quote refer to adduser :-)
> 
> addgroup is just a symlink to adduser, but behaves differently when
> called with that name.

Ahh, yes, you are right, and David (Wright) was right, also.  (I didn't read 
carefully enough :-(

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.user

csiph-web