Re: inittab question
Regards Bill Maidment Maidment Enterprises Pty Ltd -Original message- *From:* Todd And Margo Chester *Sent:* Sunday 19th August 2012 12:25 *To:* Scientific Linux Users *Subject:* inittab question Hi All, Why does this work: #/usr/sbin/faxgetty -D ttyS1 but, placing this in my /etc/inittab does not? m0:2345:respawn:/usr/sbin/faxgetty ttyS1 I have run "init q" several times to no avail. Can anyone see a typo I am missing? # ps ax | grep -i faxget | grep -v grep After invoking from the command line, I get # ps ax | grep -i faxget | grep -v grep 9827 ?Ss 0:00 /usr/sbin/faxgetty -D ttyS1 What am I missing? Many thanks, -T On 08/18/2012 10:33 PM, Bill Maidment wrote:> You need to put it in /etc/init/ nowadays. Read the notes at the top of /etc/inittab Thank you. I missed that. Now to figure out how to use /etc/init. -T Figured it out. Scientific Linux/RHEL 6.x Create a file touch /etc/init/faxgetty.conf For ttyS1, fill it with start on runlevel [2345] stop on runlevel [S016] respawn exec /usr/sbin/faxgetty ttyS1 Then do: initctl start faxgetty
Re: inittab question
Regards Bill Maidment Maidment Enterprises Pty Ltd -Original message- *From:* Todd And Margo Chester *Sent:* Sunday 19th August 2012 12:25 *To:* Scientific Linux Users *Subject:* inittab question Hi All, Why does this work: #/usr/sbin/faxgetty -D ttyS1 but, placing this in my /etc/inittab does not? m0:2345:respawn:/usr/sbin/faxgetty ttyS1 I have run "init q" several times to no avail. Can anyone see a typo I am missing? # ps ax | grep -i faxget | grep -v grep After invoking from the command line, I get # ps ax | grep -i faxget | grep -v grep 9827 ?Ss 0:00 /usr/sbin/faxgetty -D ttyS1 What am I missing? Many thanks, -T On 08/18/2012 10:33 PM, Bill Maidment wrote:> You need to put it in /etc/init/ nowadays. Read the notes at the top of > /etc/inittab > > > Thank you. I missed that. Now to figure out how to use /etc/init. -T
inittab question
Hi All, Why does this work: #/usr/sbin/faxgetty -D ttyS1 but, placing this in my /etc/inittab does not? m0:2345:respawn:/usr/sbin/faxgetty ttyS1 I have run "init q" several times to no avail. Can anyone see a typo I am missing? # ps ax | grep -i faxget | grep -v grep After invoking from the command line, I get # ps ax | grep -i faxget | grep -v grep 9827 ?Ss 0:00 /usr/sbin/faxgetty -D ttyS1 What am I missing? Many thanks, -T
cups and hylafax
Hi All, SL 6.3, x64 Anyone come up with a way to print to Hylafax through CUPS? -T
Re: How to build a custom ISO?
On Thu, Aug 16, 2012 at 5:14 PM, Connie Sieh wrote: > On Thu, 16 Aug 2012, Artifex Maximus wrote: > >> Is there any recommended way to create a custom ISO installer? I have >> no X on my SL just pure console. I've read that revisor is old and not >> supported but pungi is great. I've tried pungi under Fedora 17 for >> "cross build" without success (packages were downloaded but some >> problems with anaconda at building boot image stage). CentOS 6.3 does >> not have pungi. I think SL does not have pungi as well. So revisor is >> the only tool for building such images here in SL land? > > > It is what we use to build SL 6 . Revisor is include in the release along > with the config files used to build the release. Thanks again. Much better now. I would like to ask some questions. How to remove the SELinux warning at boot on the generated ISO file? Why packages folder includes packages for i386 architecture? For example I have wireshark for x86_64 and i386. Why? Is it possible to create ISO for SL 5.x on SL 6.x? Is it possible to create ISO for i386 on x86_64 machine? Is it possible to clean up revisor yum cache folder of older packages and leave only the latest one? Bye, a
Password required in single-user mode?
Hi, I've been running Scientific Linux since the 6.0 days, and single-user mode have basically behaved how I have expected it those few times I needed it. As I usually set up my boxes root accounts with passwords disabled, single-user mode needs to be without root password. Today, after having upgraded from 6.3, I needed to enter single-user mode at boot. And I was asked for a password at boot time. Is this change intentional? # cat /etc/redhat-release Scientific Linux release 6.3 (Carbon) # rpm -qa | grep -i sl_password_for_singleuser | wc -l 0 # grep SINGLE /etc/sysconfig/init SINGLE=/sbin/sushell If this change was intentional, how can I go back to the old behaviour? I double checked the behaviour with an old VM with SL6.1, and that behaves as expected. kind regards, David Sommerseth
