> -----Original Message----- > From: Francesco Valla <valla.francesco@xxxxxxxxx> > On Wednesday, 30 October 2024 at 09:22:09 Bird, Tim <Tim.Bird@xxxxxxxx> wrote: > > I have a few tools that I plan to publish over the next little while. > > > > Some of these might make their way into the kernel 'scripts' directory, but some > > others of these might not be appropriate to add there. > > > > So I'm thinking of putting together a repository of boot-time related tools > > for people to play with. Here's a sample of one tool that I find handy: > > ---- > > #!/bin/sh > > # sort-initcalls.sh - sort the initcalls by duration > > > > if [ -z "$1" -o "$1" = "-h" ] ; then > > echo "Usage: sort-initcalls.sh <dmesg file>" > > exit 1 > > fi > > > > grep "initcall.*after" $1 | sed "s/\(.*\)after\(.*\)/\2 \1/g" | sed "s/\r//" | sort -n > > ---- > > See https://elinux.org/Initcall_Debug for details. > > > > For tools on their way upstream, this would serve as a development repository > > where different ideas and techniques can get hashed out. > > > > So, does anyone have alternative ideas for hosting such tools, or comments on > > this approach? > > Sounds fine, at least from the perspective of a developer not so much expert > on the whole mainline development flow (like me). > > Were you thinking of using the Github PR method to accept contributions? Yes, as well as patches on the mailing list in a format suitable for a kernel submission, even though it wouldn't be going into a kernel tree, but rather a github repository with user-space tools (and maybe a yocto layer definition). I hope to initialize the repository this week. -- Tim
