Hello.
I am working in the field of Particle Physics and setting up the
init sequence of a group of diskless single board computers (Emerson
Network Power MVME3100). I have made an initramfs with a statically
linked busybox and a collection of scripts.
I want to automate the init
Denys Vlasenko a écrit :
On Fri, Mar 19, 2010 at 2:40 PM, Didier Kryn k...@in2p3.fr wrote:
I am working in the field of Particle Physics and setting up the init
sequence of a group of diskless single board computers (Emerson Network
Power MVME3100). I have made an initramfs
Guys,
I apologize for contributing to the noise on this thread, just for
a comment:
To deny access to users, there are several means, including
/bin/false or an exclamation point in /etc/passwd.
/bin/nologin is meant to deny access in a *gentle* way, for example
to inform
Hi Alexander.
If your console is supposed to be a serial port, then you have a
problem with inittab. Your inittab, seems to be meant for virtual
terminal, with tty1 as the console, and ctlr-alt-del setting.
If you use a serial port, you must uncomment the line with ttyS0 in
the
Hi Sameer.
There is a very simple alternative in case you only need to update
a small number of well known files: softlink them to some r/w location,
like /var/run or /lib/init/rw, which you mount on tmpfs. The second of
these locations is created early in newer Debian versions and
Hi Jan.
I think it is just the oposite of what you typed:
adduser daemon mygroup
At least for GNU's adduser. Maybe BB's adduser misses the feature,
otherwise the error message would be weird.
Didier
Le 18/09/2012 09:24, Jan Pohanka a écrit :
Hello,
I can't found
Hi Laurent.
I am using initramfs with static Busybox on VME Single Board
Computers. These are used as servers and can be plugged into various
locations where there is a dedicated NFS server. A USB or sata disk can
also be connected. The kernel boots from onboard flash and the console
Hi Laurent.
I actually have a jffs2 filesystem on another part of the flash
memory, but I decided not to use it for the purpose, for one reason: A
single stupid bug might make the device non-bootable. Because, even if
the jffs2 or squashfs is initially mounted read-only, the main
Hi Stéphane.
I do exactly what you want to do (I boot Debian Wheezy on diskless
PowerPC servers):
Here is my busybox init script (in initramfs)
/bin/busybox mount -t proc none /proc
/bin/busybox mount -t sysfs none /sys
busybox --install
export
Le 17/03/2015 19:56, Harald Becker a écrit :
Hi Didier,
On 17.03.2015 19:00, Didier Kryn wrote:
The common practice of daemons to put themselves in background and
orphan themself is starting to become disaproved by many designers. I
tend to share this opinion. If such a behaviour
Le 16/03/2015 19:18, Harald Becker a écrit :
On 16.03.2015 10:15, Didier Kryn wrote:
4) netlink reader the Unix way
Why let our netlink reader bother about where he sends the event
messages. Just let him do his netlink receiption job and forward the
messages to stdout.
netlink reader
Le 18/03/2015 18:41, Laurent Bercot a écrit :
On 18/03/2015 18:08, Didier Kryn wrote:
No, you must write to the pipe to detect it is broken. And you won't
try to write before you've got an event from the netlink. This event
will be lost.
I skim over that discussion (because I don't agree
Le 18/03/2015 20:01, Harald Becker a écrit :
Do you think it matters losing one more event?
Here we are considering the case when fifosvd is killed (say by
admin's error). I understand lost events can be recovered. However there
is one distinctive advantage in detecting immediately the
Le 18/03/2015 13:34, Harald Becker a écrit :
On 18.03.2015 10:42, Didier Kryn wrote:
Long lived daemons should have both startup methods, selectable by a
parameter, so you make nobodies work more difficult than required.
OK, I think you are right, because it is a little more than a fork
Le 16/03/2015 00:58, Harald Becker a écrit :
We were looking at alternative solutions, so even one more:
3) netlink reader the Unix way
Why let our netlink reader bother about where he sends the event
messages. Just let him do his netlink receiption job and forward the
messages to stdout.
There are interesting technical points in this discussion, but it
turns out to be mostly about philosophy and frustration.
Harald, there are two points in your arguments which make no sense
to me:
Le 12/03/2015 17:31, Harald Becker a écrit :
... because there are people, wo dislike
Le 29/01/2016 17:32, Isaac Dunham a écrit :
for opt in $#; do
case "$opt" in
(*=*) eval "$opt"
;;
esac
done
exec busybox init $@
Isaac,
I understand what that the loop sets environment variables that
init will inherit, but what's the purpose of the $@ at
Le 01/02/2016 23:34, Mike Frysinger a écrit :
On 01 Feb 2016 22:33, Didier Kryn wrote:
Le 01/02/2016 18:10, Mike Frysinger a écrit :
it makes a lot of sense when you fork children that have specific purposes.
rather than just seeing the program's name 4 times, it's more helpful for
them
Le 16/11/2016 18:37, Olivier Brunel a écrit :
On Wed, 16 Nov 2016 16:27:12 +0100
Didier Kryn<k...@in2p3.fr> wrote:
> Hello.
>
> I'm willing to create/delete symlinks in /dev/disk/by-uuid and
>/dev/disk/by-label . For this, I've written a script and added the
>fo
Le 17/11/2016 13:09, Peter Korsgaard a écrit :
On Thu, Nov 17, 2016 at 11:02 AM, Didier Kryn <k...@in2p3.fr> wrote:
I'm assuming you already use environment variables in your script,
e.g. $MDEV, $SEQNUM, etc Maybe you missed $ACTION, sounds like what
you're looking for.
Good t
Hello.
I'm willing to create/delete symlinks in /dev/disk/by-uuid and
/dev/disk/by-label . For this, I've written a script and added the
following lines to /etc/mdev.conf:
sd[a-z][0-9]* root:disk 660 */sbin/mdev-disk
hd[a-z][0-9]* root:disk 660 */sbin/mdev-disk
Note that I
Le 11/10/2017 à 04:43, Jeremy Kerr a écrit :
Hi Laurent,
Thanks for the reply, good to get some conversation going here!
- using a synchronous channel to send the shutdown/reboot message
between the poweroff/reboot helpers, rather than an asynchronous
signal. Say, have init listening on
Le 13/12/2017 à 00:56, Mattias Schlenker a écrit :
Am 13.12.2017 um 00:28 schrieb A.W.C.:
Hi,
yes, I know that Squashfs is read-only filesystem. Tried again, not
sure what need be changed here for this specific configuration and
filesystems available.
# mknod -m 666 /dev/null c 1 3
mknod:
Le 12/02/2020 à 13:16, Eli Schwartz a écrit :
On 2/12/20 6:07 AM, Didier Kryn wrote:
FYI, there has been for decades an adduser in Debian which is higher
level than useradd in the sense that it is a helper for admin. It
enforces local policy and can be used to change it: minimum userid
Le 11/02/2020 à 15:36, Eli Schwartz a écrit :
On 2/11/20 8:13 AM, Donovan Keohane wrote:
In adduser in coreutils, the behavior of --disabled-password sets the
users hash in /etc/shadow to a single asterisk. It looks like busybox
adduser '-D' option is supposed to be analogous to the behavior of
Le 08/06/2020 à 11:12, Denys Vlasenko a écrit :
> Sorry guys, I indeed fell off the radar for too long!
> I'm fine.
> I'm getting on patch review right away!
> SORRY!!!
GREAT news, Denys! So many people, including lurkers like me, were
afraid you were sick.
(~: :~)
Didier
Le 20/07/2020 à 09:22, Laurent Bercot a écrit :
> When writing and using a function that takes pointers, a C programmer
> should always be very aware of the kind of pointer the function expects.
> It is a programming error to pass NULL to a function expecting a pointer
> that cannot be NULL, and
Le 20/09/2023 à 07:51, Roberto A. Foglietta a écrit :
The reason because it exists the ioctl() is well explained here
https://stackoverflow.com/questions/17118705/using-rndaddentropy-to-add-entropy-to-dev-random
which refers to the man page
https://man7.org/linux/man-pages/man4/random.4.html
28 matches
Mail list logo
