* alarm for halt script @ Count Zero ` Michael P. Gorse ` Luke Davis 0 siblings, 2 replies; 4+ messages in thread From: Count Zero @ UTC (permalink / raw) To: blinux-list greetings all, I am in the initial stages of installing suse linux 6.0. By initial stages, I mean that at this point I have the system up and running but am still trying to get a serial terminal working so I have speech and so forth. One problem that I can foresee is knowing when the shutdown command is completed. This seems to take a slightly different amount of time each time. I have discussed this problem with another user on this list, and he suggested the idea of having the halt script do a distinctive beep or something to indicate that it is complete. I am interested in how the rest of you solve this particular problem. I would also be interested in corresponding with anyone with experience with the suse distribution. regards, Tom ^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: alarm for halt script alarm for halt script Count Zero @ ` Michael P. Gorse ` Massimiliano Perantoni ` Luke Davis 1 sibling, 1 reply; 4+ messages in thread From: Michael P. Gorse @ UTC (permalink / raw) To: blinux-list The serial-console code in the kernel might help (take a look at /usr/src/linux/Documentation/serial-console.txt) On Sun, 6 Jun 1999, Count Zero wrote: > greetings all, > > I am in the initial stages of installing suse linux 6.0. By initial > stages, I mean that at this point I have the system up and running but am > still trying to get a serial terminal working so I have speech and so > forth. One problem that I can foresee is knowing when the shutdown > command is completed. This seems to take a slightly different amount of > time each time. I have discussed this problem with another user on this > list, and he suggested the idea of having the halt script do a distinctive > beep or something to indicate that it is complete. I am interested in how > the rest of you solve this particular problem. I would also be interested > in corresponding with anyone with experience with the suse distribution. > regards, > Tom > > --- > 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 > > ^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: alarm for halt script ` Michael P. Gorse @ ` Massimiliano Perantoni 0 siblings, 0 replies; 4+ messages in thread From: Massimiliano Perantoni @ UTC (permalink / raw) To: blinux-list Il giorno Mon, 07 Jun 1999, Michael P. Gorse ha scritto: > The serial-console code in the kernel might help (take a look at > /usr/src/linux/Documentation/serial-console.txt) The solution Is easier for me: I have a mini server (a 486 DX4) that doesnì't have a monitor, so I need the same a beep at the end of the system halt. I solved modifiyng the script my RedHat (sorry no experience with Suse, but I think it's similar) executes when it halts the system. If you insert a line like this echo -e "\7" before the message of successful halting, the system will beep. The steps you should follow are: 1) search that script in your Suse, in redhat it's in /etc/rc.d/init.d and is named, with great fantasy, halt 2)ask to a friend of yours what does Suse print out when has halted the system before the kernels system halted. 3)Find the raw in the script where there is such a message, for this you should be able of a little of shell programming. 4)Insert the row I indicated above. I hope it works for you as it did for me. Massimiliano Perantoni > > On Sun, 6 Jun 1999, Count Zero wrote: > > > greetings all, > > > > I am in the initial stages of installing suse linux 6.0. By initial > > stages, I mean that at this point I have the system up and running but am > > still trying to get a serial terminal working so I have speech and so > > forth. One problem that I can foresee is knowing when the shutdown > > command is completed. This seems to take a slightly different amount of > > time each time. I have discussed this problem with another user on this > > list, and he suggested the idea of having the halt script do a distinctive > > beep or something to indicate that it is complete. I am interested in how > > the rest of you solve this particular problem. I would also be interested > > in corresponding with anyone with experience with the suse distribution. > > regards, > > Tom > > > > --- > > 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 > > > > > > --- > 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 -- "If automobiles had followed the same development cycle as the computer, a Rolls-Royce would today cost $100, get a million miles per gallon, and explode once a year, killing everyone inside." --Robert Cringley ^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: alarm for halt script alarm for halt script Count Zero ` Michael P. Gorse @ ` Luke Davis 1 sibling, 0 replies; 4+ messages in thread From: Luke Davis @ UTC (permalink / raw) To: blinux-list Use reboot instead of halt. Wait for the sound of your FD drive's initialization, then deactivate the system. ^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~ UTC | newest] Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed) -- links below jump to the message on this page -- alarm for halt script Count Zero ` Michael P. Gorse ` Massimiliano Perantoni ` Luke Davis
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).