Re: signatures (was: Re: Mailing list for...)

Re: signatures (was: Re: Mailing list for...)

[Jim Stevenson]

Anyone on a list of power users should save the fucking welcome message.
Save those of us who archive the trouble of trimming the unsubscribe footer!

Re: signatures (was: Re: Mailing list for...)

[Luke Davis]

OK, Jim: we don't need the language...
You might want to lose the "power user" line: if you were a "power user",
after all, you would use sed or awk to remove those signature
blocks--they have been formated to facilitate that.


On Sun, 7 Feb 1999, Jim Stevenson wrote:

> Anyone on a list of power users should save the fucking welcome message.
> Save those of us who archive the trouble of trimming the unsubscribe footer!

Re: signatures (was: Re: Mailing list for...)

[Ann K. Parsons]

Hi all,

Just an update and a comment.  I have Linux installed, but it's not
complete yet.  My friend didn't have time to complete the job, but at least
we're on the road.

RE welcome messages et signatures.  Jim, if you think people save welcome
messages, even "power users", you are sadly mistaken.  It would be nice if
people were organized, but they aren't.  Having the info right in the
message saves us from the longers message that says:

"Hello, can you please tell me how to unsubscribe.  Thank you in advance."

or:  "Unsubscribe me"  Or:  "quit quit quit quit signoff".

I'm serious, guys, it happens.  Consider yourselves lucky that the message
prevents this kind of idiocy.  <sigh>  "The grass is always greener".

RE long signatures.  It's good netiquette to limit your sigs to four lines.
 The content of the sig is a person's choice and shouldn't be questioned.
You gonna yell at your neighbor because he insists on wearing a baseball
cap backwards, or an old yellow jacket that has a rip in the back.  C'mon,
guys, let's talk about Linux.  I want to know if it's possible to put some
kind of beep at the end of the boot process so that I will know when to
type my login.  Any thoughts?  Thanks.


Ann P.
At 06:07 PM 2/7/99 -0800, Jim Stevenson wrote:
>Anyone on a list of power users should save the fucking welcome message.
>Save those of us who archive the trouble of trimming the unsubscribe footer!
>
>---
>Send your message for blinux-list to blinux-list@redhat.com
>Blinux software archive at ftp://leb.net/pub/blinux
>Blinux web page at http://leb.net/blinux
>To unsubscribe send mail to blinux-list-request@redhat.com
>with subject line: unsubscribe
>
>
>

beeping login

[Jim Danley]

Ann,

The file /etc/issue is displayed immediately before the login prompt.
If you edit the /etc/issue file and append a control-g to the end, then
you will hear a beep from the computer's speaker when it's time to login.

There is a possible gotcha, however.  Not all Linux systems are created
equal.  Some recreate the /etc/issue file each time you reboot.  If the
"beeping login" disappears the next time that you reboot, then you will
need to track down the start-up script responsible for creating your
/etc/issue file and modify it to automatically append the control-g
each time.

On Mon, Feb 08, 1999 at 07:15:14AM -0500, Ann K. Parsons wrote:
> guys, let's talk about Linux.  I want to know if it's possible to put some
> kind of beep at the end of the boot process so that I will know when to
> type my login.  Any thoughts?  Thanks.

Re: beeping login

[Dave Mielke]

On Mon, 8 Feb 1999, Jim Danley wrote:
>There is a possible gotcha, however.  Not all Linux systems are created
>equal.  Some recreate the /etc/issue file each time you reboot.  If the
>"beeping login" disappears the next time that you reboot, then you will
>need to track down the start-up script responsible for creating your
>/etc/issue file and modify it to automatically append the control-g
>each time.

On RedHat systems, which, by default, do rewrite /etc/issue on each boot, this
script is /etc/rc.d/rc.local. That's actually all that this script does, so
another approach is to remove all but its first line, and then /etc/issue will
persist.

-- 
Dave Mielke           | 856 Grenon Avenue | I believe that the Bible is the
Phone: 1-613-726-0014 | Ottawa, Ontario   | Word of God. Please contact me
EMail: dave@mielke.cc | Canada  K2B 6G3   | if you're concerned about Hell.

Re: beeping login

[Ann K. Parsons]

Hi all,

Jim D., thanks.  That's exactly my problem.  Red Hat makes a practice of
rewriting the file.  <grrrrr>  So what is the original called, where is it?
 Thanks.

Ann P.

Re: beeping login

[Ann K. Parsons]

Hi all,

Dave, thanks.  Now, I can stop growling!  I mean, we must have tried to
edit the thing six times yesterday, and every time we'd be back to square
one.  sheesh!

Ann P.
At 12:17 PM 2/8/99 -0500, Dave Mielke wrote:
>On Mon, 8 Feb 1999, Jim Danley wrote:
>>There is a possible gotcha, however.  Not all Linux systems are created
>>equal.  Some recreate the /etc/issue file each time you reboot.  If the
>>"beeping login" disappears the next time that you reboot, then you will
>>need to track down the start-up script responsible for creating your
>>/etc/issue file and modify it to automatically append the control-g
>>each time.
>
>On RedHat systems, which, by default, do rewrite /etc/issue on each boot,
this
>script is /etc/rc.d/rc.local. That's actually all that this script does, so
>another approach is to remove all but its first line, and then /etc/issue
will
>persist.
>
>-- 
>Dave Mielke           | 856 Grenon Avenue | I believe that the Bible is the
>Phone: 1-613-726-0014 | Ottawa, Ontario   | Word of God. Please contact me
>EMail: dave@mielke.cc | Canada  K2B 6G3   | if you're concerned about Hell.
>
>---
>Send your message for blinux-list to blinux-list@redhat.com
>Blinux software archive at ftp://leb.net/pub/blinux
>Blinux web page at http://leb.net/blinux
>To unsubscribe send mail to blinux-list-request@redhat.com
>with subject line: unsubscribe
>
>
>

Speech Synth project

[Corbin]

Hello all.
Previously I've asked you for help in finding a senior project.  I've kind
of decided on doing things with speech synth.  

I'm looking for a couple of interested blinuxers with whom to correspond.
Right now I'm struggling over whether to start something from scratch,
or to just improve an existing product, and could use some guidance.  I am
rather unfamiliar with current synth products and their use and function. 
Please just email me directly (not the list).
Thank you,
Aaron Corbin.

Re: beeping login

[Hans Zoebelein]

Redhat Issue file is rewritten through /etc/rc.d/rc.local script file
at every reboot .

Edit /etc/rc.d/rc.local and change the line 

echo "" > /etc/issue
into 
echo "your_content_goes_here" > /etc/issue 
Now "your_content..." will shine up from after the next reboot. 

Enjoy!
Hans  


On Mon, 8 Feb 1999, Ann K. Parsons wrote:

> Hi all,
> 
> Jim D., thanks.  That's exactly my problem.  Red Hat makes a practice of
> rewriting the file.  <grrrrr>  So what is the original called, where is it?
>  Thanks.
> 
> Ann P.
> 
> ---
> Send your message for blinux-list to blinux-list@redhat.com
> Blinux software archive at ftp://leb.net/pub/blinux
> Blinux web page at http://leb.net/blinux
> To unsubscribe send mail to blinux-list-request@redhat.com
> with subject line: unsubscribe
>