From owner-freebsd-current@FreeBSD.ORG Tue Jul 5 10:03:53 2005 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3B22416A41C for ; Tue, 5 Jul 2005 10:03:53 +0000 (GMT) (envelope-from akm@theinternet.com.au) Received: from mail14.syd.optusnet.com.au (mail14.syd.optusnet.com.au [211.29.132.195]) by mx1.FreeBSD.org (Postfix) with ESMTP id C237D43D48 for ; Tue, 5 Jul 2005 10:03:50 +0000 (GMT) (envelope-from akm@theinternet.com.au) Received: from camelot.theinternet.com.au (c211-30-103-113.carlnfd1.nsw.optusnet.com.au [211.30.103.113]) by mail14.syd.optusnet.com.au (8.12.11/8.12.11) with ESMTP id j65A3kGx014219; Tue, 5 Jul 2005 20:03:46 +1000 Received: by camelot.theinternet.com.au (Postfix, from userid 1000) id 7C49C60E4; Tue, 5 Jul 2005 20:03:46 +1000 (EST) Date: Tue, 5 Jul 2005 20:03:46 +1000 From: Andrew Milton To: Marcin Jessa Message-ID: <20050705100346.GM56644@camelot.theinternet.com.au> References: <20050705115234.44adc0ed.lists@yazzy.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050705115234.44adc0ed.lists@yazzy.org> User-Agent: Mutt/1.5.9i Cc: FreeBSD-Current Subject: Re: getty replacement X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 05 Jul 2005 10:03:53 -0000 +-------[ Marcin Jessa ]---------------------- | Hi guys. | | Is there any way to replace "/usr/libexec/getty Pc" with a custom application and what would be requirements for such an app? It's definitely do-able with compiled code. | Running | ttyv0 "/some/app/shell_code.sh Pc" cons23 on secure | gives me: | init: getty repeating too quickly on port /dev/ttyv0, sleeping 30 secs | and my code is not executed. This won't work, because shell scripts aren't directly executable. The shell handles parsing the #!/bin/sh header and executing them for you. -- Andrew Milton akm@theinternet.com.au