From: Cal Sullivan <california.l.sullivan@intel.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] sysvinit-inittab: fix getty device removal
Date: Tue, 29 Nov 2016 13:05:56 -0800 [thread overview]
Message-ID: <effe6688-33a7-7bda-8dea-471e58149824@intel.com> (raw)
In-Reply-To: <2a1fd093-8b07-1e04-4167-f52c0698446e@linux.intel.com>
[-- Attachment #1: Type: text/plain, Size: 2965 bytes --]
On 11/29/2016 12:52 PM, Leonardo Sandoval wrote:
>
>
>
> On 11/29/2016 02:15 PM, Christopher Larson wrote:
>>
>> On Tue, Nov 29, 2016 at 11:29 AM,
>> <leonardo.sandoval.gonzalez@linux.intel.com
>> <mailto:leonardo.sandoval.gonzalez@linux.intel.com>> wrote:
>>
>> From: Leonardo Sandoval
>> <leonardo.sandoval.gonzalez@linux.intel.com
>> <mailto:leonardo.sandoval.gonzalez@linux.intel.com>>
>>
>> getty devices were not being removed in some cases because device
>> name
>> was not at the end of the line, for example a ttyS1 device:
>>
>> S1:12345:respawn:/bin/start_getty 115200 ttyS1 vt102
>>
>> Removing this limitation allows sed to remove any line containing
>> the device.
>>
>> Signed-off-by: Leonardo Sandoval
>> <leonardo.sandoval.gonzalez@linux.intel.com
>> <mailto:leonardo.sandoval.gonzalez@linux.intel.com>>
>> ---
>> meta/recipes-core/sysvinit/sysvinit-inittab_2.88dsf.bb
>> <http://sysvinit-inittab_2.88dsf.bb> | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git
>> a/meta/recipes-core/sysvinit/sysvinit-inittab_2.88dsf.bb
>> <http://sysvinit-inittab_2.88dsf.bb>
>> b/meta/recipes-core/sysvinit/sysvinit-inittab_2.88dsf.bb
>> <http://sysvinit-inittab_2.88dsf.bb>
>> index c219cbf..dd30f43 100644
>> --- a/meta/recipes-core/sysvinit/sysvinit-inittab_2.88dsf.bb
>> <http://sysvinit-inittab_2.88dsf.bb>
>> +++ b/meta/recipes-core/sysvinit/sysvinit-inittab_2.88dsf.bb
>> <http://sysvinit-inittab_2.88dsf.bb>
>> @@ -62,7 +62,7 @@ if [ "x$D" = "x" ] && [ -e /proc/consoles ]; then
>> k=`echo ${i} | sed s/^.*\://g`
>> if [ -z "`grep ${j} /proc/consoles`" ]; then
>> if [ -z "${k}" ] || [ -z "`grep ${k}
>> /proc/consoles`" ] || [ ! -e /dev/${j} ]; then
>> - sed -i /^.*${j}$/d /etc/inittab
>> + sed -i /^.*${j}/d /etc/inittab
>>
>>
>> This doesn’t check for the end of a word, so it’d match a partial as
>> well. Would that be a problem? i.e. ttyS1 vs ttyS10.
>
> That is the intention, that line removal is not tied to finding the
> device at the end of the line. With proposed patch, it removes the
> device, no matter where is located.
>
Right, but look at this hypothetical example:
S1:12345:respawn:/bin/start_getty 115200 ttyS1 vt102
S10:12345:respawn:/bin/start_getty 115200 ttyS10
Both would match, when you only want the top to match. This is untested
but likely more what we want:
sed -i /^.*${j}[\ $]/d /etc/inittab
That way we either match up to a space (end of word) or end of line.
---
Cal
>
>> --
>> Christopher Larson
>> clarson at kergoth dot com
>> Founder - BitBake, OpenEmbedded, OpenZaurus
>> Maintainer - Tslib
>> Senior Software Engineer, Mentor Graphics
>
>
>
[-- Attachment #2: Type: text/html, Size: 6320 bytes --]
next prev parent reply other threads:[~2016-11-29 21:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-29 18:29 [PATCH] sysvinit-inittab: fix getty device removal leonardo.sandoval.gonzalez
2016-11-29 20:15 ` Christopher Larson
2016-11-29 20:52 ` Leonardo Sandoval
2016-11-29 21:05 ` Cal Sullivan [this message]
2016-11-29 21:08 ` Cal Sullivan
2016-11-29 21:53 ` Leonardo Sandoval
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=effe6688-33a7-7bda-8dea-471e58149824@intel.com \
--to=california.l.sullivan@intel.com \
--cc=openembedded-core@lists.openembedded.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox