Tested here, Ubuntu 20.04:
$ printf 'a\nb\n' | busybox sed -n -e '/a/w xxx' -e '/b/w xxx' ;cat xxx
a
$ uname -a
Linux desktop 5.4.0-39-generic #43-Ubuntu SMP Fri Jun 19 10:28:31 UTC
2020 x86_64 x86_64 x86_64 GNU/Linux
Em 01/01/2022 22:38, Paul Eggert escreveu:
This bug in BusyBox 'sed'
Why would you want to completely disable root login?
If it is a security feature, how can it be used? It can be interesting
to avoid escalating priviledges, but then how to to administrative
tasks? (assuming ssh root login is disabled too)
Thanks,
Alain
On 01-10-2015 14:39, Denys Vlasenko
Em 09-09-2012 00:52, Mike Frysinger escreveu:
On Sat, Sep 8, 2012 at 5:35 PM, Rich Felker wrote:
The legal rights to kernel code of course belong to the kernel
developers, who are actively working to undermine enforcement.
some developers don't want to enforce, some do, and many don't care
What I usualy do is to have a command line parameter when it is invoked
by another script or cron. This is easy to test as $1
Then if the script is called from the user there is no parameter (or
different ones)
I hope that this is possible in your case
Alain
Em 27-07-2012 05:20, Harald
Em 12-07-2012 02:36, Tito escreveu:
HI,
maybe Copyright (C) 1998-2012 by the Busybox project developers
and then adding a full list to the source package and to the website
could be a solution.
This is not good. In case of a court dispute, all copyright owners have
to be present. So if you
Em 12-07-2012 16:29, Bradley M. Kuhn escreveu:
Alain Mouette wrote:
This is not good. In case of a court dispute, all copyright owners
have to be present. So if you want the copyright do be good for
something, it has to be nominal!
Alain, I'm not sure I understand your point. Any given
This should work:
21 /dev/null
First you redirect error(2) do console(1)...
Alain
Em 10-01-2011 13:23, David Henderson escreveu:
Is there a way to prevent modprobe from displaying information related
to a driver being loaded? I'm stumped and have tried the following:
modprobe -q e1000e
Could anyone *please* explain what was the violation exactly and what
should they have done to comply with BusyBox's licence.
Thanks for any information, this is important for me...
Alain
PS: sorry Walter Harms for the message to your address, no harm intended :)
Em 06-08-2010 10:43, walter
Em 15-04-2010 04:11, Denys Vlasenko escreveu:
2. Linux kernel will attempt to update RTC at 500ms mark and
not at a second mark. Do they known something better?
Hmm, I didn't know that.
Perhaps they thought this minimizes average error in setting
RTC time.
This makes sense. One problem in
Hi Tom,
Could you put toghether some king of tutorial, or at least the basic
steps to make BusyBox work on Android? This can be much usefull to
anyone retracing your steps... (like me :) I plan to get an Android
Phone soon)
Thanks,
Alain
Tom Spear escreveu:
On Wed, Jan 13, 2010 at 12:15
10 matches
Mail list logo