Mitchell Laks | 1 Mar 01:31 2012
Picon

Re: not in X. man command does not respect set bell-style visible

On 19:01 Wed 29 Feb     , Sven Joachim wrote:
> 
> This is because .inputrc is only honored by programs that use readline,
> and the standard pager does not use that.
> 
> > how to get rid of this?
> 
> Make sure that less (the standard pager) is invoked with the "-q"
> option.  E.g. set PAGER="/usr/bin/less -q" in the environment.
> 
Thank you that explains the problem to me.

I see now that unless less is invoked with the -q option i will get the sound.

I see references on google to the fact that the pager is set via the PAGER variable
but when I do echo $PAGER I get nothing. 

1) I see that there is a pager
and that
2) man pager 
gives me
 man less
and that

3) which pager 
is
/usr/bin/pager
which is a symlink to
/etc/alternatives/pager
which is a link to
(Continue reading)

Brian | 1 Mar 01:43 2012
Picon

Re: xserver-xorg vs. xserver-xorg-video-nouveau

On Wed 29 Feb 2012 at 23:48:22 +0300, Stayvoid wrote:

> This guide wasn't helpful. "modprobe nouveau" outputs nothing and

It wouldn't output anything if the module was already in place.

> there is no nouveau module in the output of "lsmod." But nouveau

That is extremely surprising considering you have shown a dmesg output
elsewhere which displays it being brought into use and being used for
the framebuffer on the console.

> appears in the output of "lspci -vv."

I don't suppose it said 'Kernel driver in use: nouveau?

> Let's try to fix it in gNewSense. (My version is based on Squeeze.)

gNewSense is nearly three years old and, I think, based on Ubuntu. The
suggested mismatch is most likely the cause of X not running. In Debian
at that time nouveau packages were possibly classed as experimental.

4352191442 | 1 Mar 03:04 2012
Picon
Picon

RE: .s

Hi

--
==================================================================
This mobile text message is brought to you by AT&T

Jason Heeris | 1 Mar 04:45 2012
Picon

Print a message to all terminals at boot

I have a Debian Squeeze system that exposes a terminal on the serial
line (ttyS0) and the usual tty ones. I would like to print a message
at the very end of the boot sequence, but before any user logs in (the
message is a diagnostic that may affect whether the user logs in at
all).

If I put, say, echo "Message" in /etc/rc.local, it only shows up on
the serial console. How can I print a message to all consoles?

Cheers,
Jason

Tom H | 1 Mar 06:39 2012
Picon

Re: not in X. man command does not respect set bell-style visible

On Wed, Feb 29, 2012 at 7:31 PM, Mitchell Laks <mlaks <at> post.harvard.edu> wrote:
> On 19:01 Wed 29 Feb     , Sven Joachim wrote:

>> This is because .inputrc is only honored by programs that use readline,
>> and the standard pager does not use that.
>>
>> > how to get rid of this?
>>
>> Make sure that less (the standard pager) is invoked with the "-q"
>> option.  E.g. set PAGER="/usr/bin/less -q" in the environment.
>
> I see references on google to the fact that the pager is set via the PAGER variable
> but when I do echo $PAGER I get nothing.

Because PAGER isn't set by default.

You can set it in "/etc/environment" or "~/.bashrc" or "~/.profile".

> 1) I see that there is a pager
> and that
> 2) man pager
> gives me
>  man less
> and that
> 3) which pager
> is
> /usr/bin/pager
> which is a symlink to
> /etc/alternatives/pager
> which is a link to
(Continue reading)

Tom H | 1 Mar 07:03 2012
Picon

Re: Print a message to all terminals at boot

On Wed, Feb 29, 2012 at 10:45 PM, Jason Heeris <jason.heeris <at> gmail.com> wrote:
>
> I have a Debian Squeeze system that exposes a terminal on the serial
> line (ttyS0) and the usual tty ones. I would like to print a message
> at the very end of the boot sequence, but before any user logs in (the
> message is a diagnostic that may affect whether the user logs in at
> all).
>
> If I put, say, echo "Message" in /etc/rc.local, it only shows up on
> the serial console. How can I print a message to all consoles?

"rc.local" will only display an "echo..." on the console.

If you want a message displayed pre-login:

If it's static, you can add it to "/etc/issue".

If it's dynamic (e.g. "ifconfig lo"), you can add it to
"/etc/rc.local" but use "ifconfig lo > ttyX" but the message won't
display before ssh sessions.

If you want a message displayed post-login:

You can append it to "/var/run/motd" in "/etc/init.d/bootlogs" or
"/etc/rc.local".

Bob Proulx | 1 Mar 07:22 2012

Re: Print a message to all terminals at boot

Tom H wrote:
> Jason Heeris wrote:
> > line (ttyS0) and the usual tty ones. I would like to print a message
> > at the very end of the boot sequence, but before any user logs in (the
> > message is a diagnostic that may affect whether the user logs in at all).
>
> If it's static, you can add it to "/etc/issue".

Or if the process can update /etc/issue before getty can display it.
The /etc/issue file could be updated many times and that should be
okay.  The contents are displayed when getting displays the login
prompt.  Meaning that when getting is started it will catch the
current contents of /etc/issue at that moment.  So updates need to be
early in the boot cycle or getty needs to be held off until later in
the boot cycle.

I believe that if someone hits enter on the serial console that getty
will print the current /etc/issue again.  Meaning that a user could
get the current value by hitting enter intentionally.  But I can't
recall if it does it before every login or only when it respawns after
a timeout or several failed logins.

Bob
Bob Proulx | 1 Mar 07:25 2012

Re: Print a message to all terminals at boot

Bob Proulx wrote:
> okay.  The contents are displayed when getting displays the login
> prompt.  Meaning that when getting is started it will catch the

Grr...

  s/getting/getty/g

My typos are getting worse.  Sorry for the noise.

Bob
Jason Heeris | 1 Mar 07:26 2012
Picon

Re: Print a message to all terminals at boot

On 1 March 2012 14:22, Bob Proulx <bob <at> proulx.com> wrote:
>> If it's static, you can add it to "/etc/issue".
>
> Or if the process can update /etc/issue before getty can display it.

rc.local appears to run before the contents of /etc/issue is
displayed... is that guaranteed (in squeeze), or just coincidental on
my system? Because that would be the simplest way to achieve this, I
think.

Incidentally, it contains escape sequences ( \n \l ) at the end. Are
they for use with "echo -e" or something else entirely?

Cheers,
Jason

Jason Heeris | 1 Mar 07:34 2012
Picon

Re: Print a message to all terminals at boot

On 1 March 2012 14:26, Jason Heeris <jason.heeris <at> gmail.com> wrote:
> Incidentally, it contains escape sequences ( \n \l ) at the end. Are
> they for use with "echo -e" or something else entirely?

Ah, just found the answer to this in "man issue" — they're escape
sequences for getty (or whatever substitute).

— Jason


Gmane