On 5/11/19 5:28 PM, Niels Terp wrote:
On 5/10/19 5:25 PM, Niels Terp wrote:
Hey, I’m kind of new here. I build LFS several times a few years
ago, but then got busy with other things.
Now I’m back, I’m following current stable lfs, and here is my
first problem:
I have a
On 3/1/20 4:54 PM, Rob wrote:
Ken Moffat wrote:
Do you have links to whatever speed or other efficiency this package
provides ? As a user of the sysvinit books I've never found DBus to
be an obvious cause of pain or "ooh, this is so slow!" thoughts.
All I have is word on the street. I'm no
On 3/2/20 3:42 AM, DJ Lucas wrote:
On 3/1/2020 4:50 PM, Scott Andrews wrote:
I may not need dbus if I am successful building lumina.
Hey, something I might actually be able to help with. From about a
year ago (or so
On 1/22/20 3:03 PM, Bruce Dubbs wrote:
On 1/22/20 12:15 PM, Douglas R. Reno wrote:
On 1/22/20 11:40 AM, Scott Andrews wrote:
I am trying to build the lfs editor manual after downloading the
source with svn
executing make nochunks returns the following error
$ make nochunks
xsltproc
On 1/22/20 9:49 PM, Bruce Dubbs wrote:
On 1/22/20 8:29 PM, Douglas R. Reno wrote:
This link does not exist any more
http://docbook.sourceforge.net/release/xsl/1.69.1/xhtml/profile-docbook.xsl
I can confirm this, it seems that the oldest version that they have
available on Sourceforge
On 1/23/20 9:01 AM, Pierre Labastie wrote:
Le 23/01/2020 à 13:25, Scott Andrews a écrit :
On 1/22/20 9:49 PM, Bruce Dubbs wrote:
On 1/22/20 8:29 PM, Douglas R. Reno wrote:
This link does not exist any more
http://docbook.sourceforge.net/release/xsl/1.69.1/xhtml/profile-docbook.xsl
I can
On 1/23/20 4:04 PM, pierre.labas...@neuf.fr wrote:
De : "Bruce Dubbs"
A : "Pierre Labastie"
Envoyé: jeudi 23 janvier 2020 17:21
Objet : Re: [lfs-support] Building editor-manual
On 1/23/20 8:01 AM, Pierre Labastie wrote:
> Le 23/01/2020 à 13:25, Scott Andrews a écrit :
&
On 1/22/20 1:15 PM, Douglas R. Reno wrote:
Also How would you build the LFS-9.0 from the BOOK source?
If you're looking to render the book, do this (from within the
trunk/BOOK folder of an SVN checkout):
make REV=sysv BASEDIR=~/wherever_you_want_your_files_output_to
make REV=sysv
I am trying to build the lfs editor manual after downloading the source
with svn
executing make nochunks returns the following error
$ make nochunks
xsltproc --xinclude --nonet -stringparam profile.condition html \
--output ~/lfs-editors-guide/LFS-EDITORS-GUIDE.html \
On 1/22/20 3:03 PM, Bruce Dubbs wrote:
On 1/22/20 12:15 PM, Douglas R. Reno wrote:
On 1/22/20 11:40 AM, Scott Andrews wrote:
I am trying to build the lfs editor manual after downloading the
source with svn
executing make nochunks returns the following error
$ make nochunks
xsltproc
My foray into building LFS on the raspberry pi platform has went
extremely well. I am thinking about taking the LFS book that is
currently available and modifying it for the ARM platform. The required
changes are not many. This may turn out to be a long range project, as
I am going to look
On 1/20/20 4:58 PM, Tom Armistead wrote:
I also build LFS for my ARM and powerpc machines. For the last few
LFS releases I have put my LFS ARM/PPC book patch and general notes on
the how to do it at http://www.github.com/tarmiste/lfs-non-ia
It is a bit rough in spots but may be
On 1/20/20 4:37 PM, Don Cross wrote:
On Mon, Jan 20, 2020 at 4:13 PM Bruce Dubbs <mailto:bruce.du...@gmail.com>> wrote:
On 1/20/20 2:49 PM, Scott Andrews wrote:
> My foray into building LFS on the raspberry pi platform has went
> extremely well. I am thinking about
Anyone have this error?
ar cr libgrep.a glthread/lock.o glthread/threadlib.o kwset.o m-fgrep.o
m-regex.o mbrlen.o regex.o
ranlib libgrep.a
make[3]: Leaving directory
'/mnt/lfs/source/gettext-0.20.1/gettext-tools/libgrep'
Making all in src
here=`pwd`; \
cd ../../libtextstyle/lib && \
On 1/4/20 7:38 PM, Bruce Dubbs wrote:
On 1/4/20 4:11 PM, Scott Andrews wrote:
On 1/4/20 1:45 PM, Flareon Zulu wrote:
On January 4, 2020, at 09:47, Scott Andrews
wrote:
>Anyone have this error?
>ar cr libgrep.a glthread/lock.o glthread/threadlib.o kwset.o m-fgrep.o
>m-regex.o
On 1/4/20 1:45 PM, Flareon Zulu wrote:
On January 4, 2020, at 09:47, Scott Andrews
wrote:
>Anyone have this error?
>ar cr libgrep.a glthread/lock.o glthread/threadlib.o kwset.o m-fgrep.o
>m-regex.o mbrlen.o regex.o
>ranlib libgrep.a
>make[3]: Leaving directory
>'/mnt/
On 1/4/20 1:38 PM, Flareon Zulu wrote:
On January 4, 2020, at 09:47, Scott Andrews
wrote:
>Anyone have this error?
>ar cr libgrep.a glthread/lock.o glthread/threadlib.o kwset.o m-fgrep.o
>m-regex.o mbrlen.o regex.o
>ranlib libgrep.a
>make[3]: Leaving directory
>'/mnt/
On 1/5/20 12:10 PM, Bruce Dubbs wrote:
On 1/5/20 8:01 AM, Scott Andrews wrote:
This is what I used in the build:
./configure --disable-shared
make -j1
The result:
[snip]
make[2]: Entering directory
'/mnt/lfs/source/gettext-0.20.1/gettext-tools/src'
here=`pwd`; \
cd ../../libtextstyle
On 1/5/20 12:25 PM, Flareon Zulu wrote:
On January 5, 2020, at 09:51, Scott Andrews
wrote:
>
>On 1/5/20 3:35 AM, Pierre Labastie wrote:
>> Le 05/01/2020 à 05:37, Bruce Dubbs a écrit :
>>> On 1/4/20 7:45 PM, Ken Moffat wrote:
>>>> On Sat, Jan 04, 2020 a
On 1/5/20 4:34 PM, Bruce Dubbs wrote:
On 1/5/20 1:34 PM, Scott Andrews wrote:
Looking to see if there is any interest for LFS running on Raspberry
pi hardware here?
I am currently working to get a build of LFS working on some
raspberry pi 4 hardware. I have LFS version 8.4 running on Rpi 2
On 1/5/20 5:07 PM, Ken Moffat wrote:
On Sun, Jan 05, 2020 at 02:34:41PM -0500, Scott Andrews wrote:
Looking to see if there is any interest for LFS running on Raspberry pi
hardware here?
I am currently working to get a build of LFS working on some raspberry pi 4
hardware. I have LFS version
Looking to see if there is any interest for LFS running on Raspberry pi
hardware here?
I am currently working to get a build of LFS working on some raspberry
pi 4 hardware. I have LFS version 8.4 running on Rpi 2 and Rpi3 which I
currently use them for IMAP server and a validating DNS server.
On 1/5/20 3:35 AM, Pierre Labastie wrote:
Le 05/01/2020 à 05:37, Bruce Dubbs a écrit :
On 1/4/20 7:45 PM, Ken Moffat wrote:
On Sat, Jan 04, 2020 at 05:11:18PM -0500, Scott Andrews wrote:
On 1/4/20 1:45 PM, Flareon Zulu wrote:
On January 4, 2020, at 09:47, Scott Andrews
wrote:
Anyone have
On 1/6/20 11:28 AM, Ken Moffat wrote:
On Sun, Jan 05, 2020 at 10:10:00PM -0500, Scott Andrews wrote:
On 1/5/20 5:07 PM, Ken Moffat wrote:
On Sun, Jan 05, 2020 at 02:34:41PM -0500, Scott Andrews wrote:
I guess you've answered Bruce's post about your gettext problem. To
repeat for everyone who
Sent from my iPhone
> On Apr 15, 2020, at 1:50 PM, Flareon wrote:>--
> I think he's saying it's an example, and not something to take literally.
> Please stop griping; I have enough school to deal with around here without
> people throwing fits about examples. Please?
>
> Flareon Zulu
>
Sent from my iPhone
> On Apr 15, 2020, at 2:51 PM, Flareon wrote:
>
>
> On April 15, 2020, at 12:19, Scott Andrews
> wrote:
>
> >
> >
> >Sent from my iPhone
> >
> >On Apr 15, 2020, at 1:50 PM, Flareon wrote:>--
> >
> >
The local.conf file is incorrect and will not allow remote logins
add this to the local.conf file to correct
disable_plaintext_auth = no
cat > /etc/dovecot/local.conf <<- EOF
protocols = imap
disable_plaintext_auth = no
ssl = no
# The next line is only needed if you have no
On 4/15/20 12:38 PM, Pierre Labastie wrote:
On Wed, 2020-04-15 at 11:44 -0400, Scott Andrews wrote:
The local.conf file is incorrect and will not allow remote logins
add this to the local.conf file to correct
disable_plaintext_auth = no
cat > /etc/dovecot/local.conf <<- EOF
On 4/15/20 1:04 PM, Pierre Labastie wrote:
On Wed, 2020-04-15 at 12:47 -0400, Scott Andrews wrote:
On 4/15/20 12:38 PM, Pierre Labastie wrote:
On Wed, 2020-04-15 at 11:44 -0400, Scott Andrews wrote:
The local.conf file is incorrect and will not allow remote logins
add this to the local.conf
does any one actually use the #lfs and #lfs-support on freenote?
Trying to set this up but it looks like is is not working.
--
http://lists.linuxfromscratch.org/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
Do not top post on
On Tue, 26 May 2020 13:36:20 +0300
Greekforce1821 wrote:
> Hello again! , I am experiencing some kind of errors in my bootable
> kernel. As you can see in the photo, when I reached the end of the
> guide and shutdown -r now the system, the kernel loaded but there
> were some kind of errors
On Wed, 17 Jun 2020 15:19:14 +0100
Ken Moffat wrote:
> I've now completed, and booted, a build of the new-style LFS. I'm
> loggied in (and using ssh to write this post). Both my normal
> users (ken, lfs), as well as root can login - so the passwords are
> correct.
>
> But only root can su, so
On Wed, 17 Jun 2020 18:45:44 +0100
Ken Moffat wrote:
> On Wed, Jun 17, 2020 at 12:19:25PM -0400, Scott Andrews wrote:
> > On Wed, 17 Jun 2020 15:19:14 +0100
> > Ken Moffat wrote:
> >
> > > I've now completed, and booted, a build of the new-style LFS. I'm
&
On Wed, 17 Jun 2020 19:07:02 +0100
Ken Moffat wrote:
> On Wed, Jun 17, 2020 at 01:51:49PM -0400, Scott Andrews wrote:
> > On Wed, 17 Jun 2020 18:45:44 +0100
> > Ken Moffat wrote:
> >
> > > On Wed, Jun 17, 2020 at 12:19:25PM -0400, Scott Andrews wrote:
> &
On Sun, 28 Jun 2020 18:19:56 -0600
Flareon Zulu wrote:
>
> And now I'm going to roll around dying of laughter...
>
> Flareon Zulu
>
Coming from you well just more ignorance
--
http://lists.linuxfromscratch.org/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
On Sun, 28 Jun 2020 13:42:10 +0200
Frans de Boer wrote:
> LS,
>
> Currently, the previous chapter 5 has been split into 3 separate
> chapters. It is obvious why the new chapter 7 exists.
> However, chapter 5 and 6 are a bit puzzling. There are no extra
> actions between chapter 6 and 5, in
On Sun, 28 Jun 2020 19:41:20 +0200
Frans de Boer wrote:
> On 28-06-2020 14:07, Scott Andrews wrote:
> > On Sun, 28 Jun 2020 13:42:10 +0200
> > Frans de Boer wrote:
> >
> >> LS,
> >>
> >> Currently, the previous chapter 5 has been split into 3 s
On Mon, 8 Jun 2020 16:11:22 -0600
Flareon Zulu wrote:
> In building util-linux in ch 5 of the dev book, it wanted me to supply
> --build, --target, and --host. I used $LFS_TGT to make it happy on all
> three, but has anyone else had this come up?
>
> Flareon Zulu
That was the incorrect thing
On Mon, 23 Nov 2020 04:07:48 +
Ken Moffat wrote:
> On Sun, Nov 22, 2020 at 01:14:17AM +, Ken Moffat wrote:
> > On Sat, Nov 21, 2020 at 06:09:52PM -0600, Brian Hagen wrote:
> >
> > My general recommndation for LFS is that you use a *recent* distro.
> > But the availability of 32-bit x86
On 1/31/21 2:15 PM, Bruce Dubbs wrote:
On 1/31/21 12:44 PM, Scott Andrews wrote:
I have been going through the boot scripts and cleaning them up and I
came across this jewel...
BTW it would be helpful to use some kind of standard in all the boot
scripts, blfs included
mountfs ${failed
I have been going through the boot scripts and cleaning them up and I
came across this jewel...
BTW it would be helpful to use some kind of standard in all the boot
scripts, blfs included
mountfs ${failed} is undefined/not defined
case "${1}" in
start) log_info_msg "Remounting root
On 2/4/21 8:11 PM, Xi Ruoyao wrote:
On 2021-02-04 15:19 -0600, Bruce Dubbs wrote:
I am OK with the changes to omit seccomp, but when building on an LFS
10.0 system, there were no problems before.
Hi Bruce,
On LFS/BLFS if libseccomp.so is installed, /usr/include/seccomp.h would be also
On 2/4/21 5:54 PM, Pierre Labastie wrote:
On Thu, 2021-02-04 at 17:11 -0500, Scott Andrews wrote:
On 2/4/21 4:46 PM, Pierre Labastie wrote:
On Thu, 2021-02-04 at 21:50 +0100, Frans de Boer wrote:
On 04/02/2021 21:21, Pierre Labastie wrote:
On Thu, 2021-02-04 at 20:03 +0100, Frans de Boer
On 2/4/21 4:46 PM, Pierre Labastie wrote:
On Thu, 2021-02-04 at 21:50 +0100, Frans de Boer wrote:
On 04/02/2021 21:21, Pierre Labastie wrote:
On Thu, 2021-02-04 at 20:03 +0100, Frans de Boer wrote:
On 04/02/2021 16:22, Scott Andrews wrote:
On 2/4/21 9:14 AM, Frans de Boer wrote:
The new
On 2/4/21 3:50 PM, Frans de Boer wrote:
On 04/02/2021 21:21, Pierre Labastie wrote:
On Thu, 2021-02-04 at 20:03 +0100, Frans de Boer wrote:
On 04/02/2021 16:22, Scott Andrews wrote:
On 2/4/21 9:14 AM, Frans de Boer wrote:
The new instructions for compiling file-5.39 in the first phase
On 2/4/21 9:14 AM, Frans de Boer wrote:
The new instructions for compiling file-5.39 in the first phase, are
incomplete. As it turns out, you can only compile file when the
configure command is augmented with '--disable-libseccomp'. The file
$LFS/usr/include/libseccomp/seccomp.h does not
On 2/9/21 9:29 PM, Ken Moffat wrote:
On Tue, Feb 09, 2021 at 03:24:53PM -0500, Baho Utot wrote:
A note should be placed in the book about --with-ensurepip=yes.
It will not build pip, setuptools and wheel if they are already installed on
the system.
Rebuilding python3 will not rebuild pip,
Moved to list.
On 3/22/21 1:41 PM, Bruce Dubbs wrote:
On 3/22/21 11:54 AM, Scott Andrews wrote:
On 3/22/21 12:25 PM, Bruce Dubbs wrote:
On 3/22/21 10:44 AM, Scott Andrews wrote:
Syntax errors found in /etc/init.d/rc...
Not errors, but someone's preferences. For instance all
On 3/24/21 7:55 AM, Patrick Frisch wrote:
Hi there,
I'm a big fan of the LFS project and build a system from time to
time. My last build was a bit outdated so I decided to begin from
scratch. I realized, that there are major changes in the build
procedure for the toolchain lately. The
On Wed, 24 Mar 2021 17:07:57 +0100
Patrick Frisch wrote:
> Am 24.03.21 um 13:12 schrieb Scott Andrews:
> >
> > echo $LFS
> >
> > Looks like it wasn't set
> >
> >
> >
>
> No, $LFS is set almost always to /mnt/lfs, as it was in this case,
>
On Wed, 24 Mar 2021 17:05:23 -0400
Scott Andrews wrote:
> On Wed, 24 Mar 2021 18:11:46 +0100
> Pierre Labastie wrote:
>
> > On Wed, 2021-03-24 at 17:07 +0100, Patrick Frisch wrote:
> > >
> > > Am 24.03.21 um 13:12 schrieb Scott Andrews:
> > > &
On Wed, 24 Mar 2021 18:11:46 +0100
Pierre Labastie wrote:
> On Wed, 2021-03-24 at 17:07 +0100, Patrick Frisch wrote:
> >
> > Am 24.03.21 um 13:12 schrieb Scott Andrews:
> > >
> > > echo $LFS
> > >
> > > Looks like it wasn't set
> >
The existing function does not return a correct result for all signal types.
# check_sig_type() #
# Usage: check_signal [ -{signal} | {signal}
] #
# #
# Purpose: Check if signal
On 3/30/21 12:34 AM, Bruce Dubbs wrote:
On 3/29/21 7:30 PM, Scott Andrews wrote:
The existing function does not return a correct result for all signal
types.
# check_sig_type() #
Original less empty lines
check_sig_type()
{
local valsig
# The list of termination signals
Doesn't write to ${BOOTLOG} what was actually skipped
I have added an "_" to the beginning of the corrected function name so I
can test the results.
Remove it to replace log_skip_msg() in init_functions
log_skip_msg()
{
/bin/echo -n -e "${BMPREFIX}${@}"
/bin/echo -e
This code is from killproc:
If killproc is called ( for example: /etc/init.d/sysklogd: killproc
/sbin/klogd )
and the pid file exists and the process in not running:
then the case statement receives a 1 exit status from from
pidlist=`pidofproc "${1}"` ,pidlist contains "" and pidfile is
case statement changes to
case "${retval}" in
0) ;; # Program is running correctly
1) # Program is not running, but an invalid pid file exists
# Remove the pid file.
# If a PID file exists with that name, assume that is it.
[ -z
in init-functions start_daemon pidfile is not validated before removing...
code as follows
start_daemon()
{
local force=""
local nice="0"
local pidfile=""
local pidlist=""
local retval=""
# Process arguments
while true
do
case "${1}" in
On 4/1/21 11:06 PM, Bruce Dubbs wrote:
On 4/1/21 7:15 PM, Scott Andrews wrote:
in init-functions start_daemon pidfile is not validated before
removing...
code as follows
[snip]
# Execute
if [ -z "${force}" ]; then
if [ -z
On 4/2/21 8:58 AM, Bruce Dubbs wrote:
On 4/2/21 6:29 AM, Scott Andrews wrote:
On 4/1/21 11:06 PM, Bruce Dubbs wrote:
On 4/1/21 7:15 PM, Scott Andrews wrote:
in init-functions start_daemon pidfile is not validated before
removing...
code as follows
[snip]
# Execute
On Tue, 16 Mar 2021 20:07:45 +0100
Pierre Labastie wrote:
[ putlin ]
>
> Well, I guess I've never tried /etc/init.d/network restart, since
> usually, after boot, I only want to stop/start individual
> interfaces (I use "ifdown " then "ifup ").
>
If I change the ifconfig. script like in
On Thu, 18 Mar 2021 11:51:09 -0500
Bruce Dubbs wrote:
> On 3/18/21 11:21 AM, Scott Andrews wrote:
> >
> > I am presently looking at and working on the LFS boot scripts.
> > They are in my opinion very rough state.
> >
> > I am going to clean them up and
I am presently looking at and working on the LFS boot scripts.
They are in my opinion very rough state.
I am going to clean them up and use the following format for all of
the individual scripts that will be used on my systems as follows:
Shebang line: #!/bin/bash
Comment Title block:
On Thu, 18 Mar 2021 11:51:09 -0500
Bruce Dubbs wrote:
> On 3/18/21 11:21 AM, Scott Andrews wrote:
> >
> > I am presently looking at and working on the LFS boot scripts.
> > They are in my opinion very rough state.
> >
> > I am going to clean them up and
On Thu, 18 Mar 2021 15:11:27 -0500
Bruce Dubbs wrote:
> On 3/18/21 1:32 PM, Scott Andrews wrote:
>
> Although the init-functions and rc scripts currently run properly,
> what you propose below is a bit cleaner.
>
> I'll note that the scripts were initially written to be
On Thu, 18 Mar 2021 19:06:40 +0100
Tim Tassonis wrote:
> On 3/18/21 6:21 PM, Scott Andrews wrote:
> > On Thu, 18 Mar 2021 11:51:09 -0500
> > Bruce Dubbs wrote:
> >
> >> On 3/18/21 11:21 AM, Scott Andrews wrote:
> >>>
> >>> I am pr
On Thu, 18 Mar 2021 22:17:07 +0100
Pierre Labastie wrote:
> On Thu, 2021-03-18 at 14:32 -0400, Scott Andrews wrote:
> > On Thu, 18 Mar 2021 11:51:09 -0500
> > Bruce Dubbs wrote:
> >
> > > On 3/18/21 11:21 AM, Scott Andrews wrote:
> > > >
>
Found something interesting
Per the gnu bash reference manual..
-f file
True if file exists and is a regular file.
-h file
True if file exists and is a symbolic link.
-x file
True if file exists and is executable.
Function as built from rc
check_script_status()
{
# $i is set
Syntax errors found in /etc/init.d/rc...
Found by shellcheck
In rc line 15:
. /lib/lsb/init-functions
^-- SC1091: Not following: /lib/lsb/init-functions was not specified as
input (see shellcheck -x).
In rc line 21:
MSG="FAILURE:\n\nYou should not be reading this error message.\n\n"
On 3/22/21 12:25 PM, Bruce Dubbs wrote:
On 3/22/21 10:44 AM, Scott Andrews wrote:
Syntax errors found in /etc/init.d/rc...
Not errors, but someone's preferences. For instance all the
'Prefer explicit escaping: "\\n"' issues are wrong. The page
https://github.com/koalaman/shell
On Fri, 19 Mar 2021 07:09:06 +0100
Pierre Labastie wrote:
>
> Using brackets depends on "something". If something is a predicate,
> you need brackets. If something is a (compound) command, no
> brackets. I've not looked in details at the "if" in the boot
> scripts, but they must be correct in
On Fri, 19 Mar 2021 23:26:01 +0100
Pierre Labastie wrote:
> On Fri, 2021-03-19 at 07:24 -0400, Scott Andrews wrote:
> > On Fri, 19 Mar 2021 07:09:06 +0100
> > Pierre Labastie wrote:
> >
> > >
> > > Using brackets depends on "something". If
On Fri, 19 Mar 2021 23:26:01 +0100
Pierre Labastie wrote:
> On Fri, 2021-03-19 at 07:24 -0400, Scott Andrews wrote:
> > On Fri, 19 Mar 2021 07:09:06 +0100
> > Pierre Labastie wrote:
> >
> > >
> > > Using brackets depends on "something". If
On 3/20/21 4:38 PM, Bruce Dubbs wrote:
On 3/20/21 10:44 AM, Pierre Labastie wrote:
Anyway, I hope you are now convinced that the right command for
testing script
status is:
if ! check_script_status; then continue; fi
I agree with the syntax, but have a problem with the name. What are
we
#! /bin/sh
VERSION="$(basename ${0}) verison: 2021-03-15"
USAGE="Usage: $(basename ${0}) < option > | --status | [ service_name [ command
| --restart ] ]"
SERVICEDIR="/etc/init.d"
SERVICE=''
OPTIONS=''
if [ ${#} -eq 0 ]; then echo "${USAGE}" >&2; exit 1; fi
while [ ${#} -gt 0 ]; do
case
On Mon, 15 Mar 2021 18:20:31 +0100
Tim Tassonis wrote:
> On 3/15/21 4:53 PM, Scott Andrews wrote:
> > #! /bin/sh
> > VERSION="$(basename ${0}) verison: 2021-03-15"
> > USAGE="Usage: $(basename ${0}) < option > | --status |
> > [ service_name [
I am in the process of adding ipv6 to the the network scripts
Yes, I have read IPv6-in-LFS.txt and that isn't the proper way to add
ipv6 to the bootscripts in my opinion. Good information wrong
implementation. I am looking to create ipv6-static and maybe
ipv6-static-route files.
May have to add
# Function: pidofproc [-p pidfile] pathname
# The pidofproc function shall return one or more process
# identifiers for a particular daemon using the algorithm
# given above. Only process identifiers of running
# processes should be returned. Multiple process
# identifiers shall be
# Function: statusproc
# Purpose: This function prints status of a particular daemon to stdout
# Usage: statusproc [-p pidfile] pathname
# Inputs: -p pidfile, use the specified pidfile instead of pidof
# must be fully qualififed
# Outputs: Status printed
function statusproc {
On Fri, 16 Apr 2021 20:12:16 -0500
DJ Lucas wrote:
> On 4/9/2021 5:16 AM, Scott Andrews wrote:
> > This script is not intended to run with ash, the she bang line is
> > as follows
> >
> > #!/bin/bash --posix
>
>
> My apologies for the duplicate
On 4/9/21 2:10 AM, Tim Tassonis wrote:
Hi Scott
On 4/9/21 2:40 AM, Scott Andrews wrote:
# Function: pidofproc [-p pidfile] pathname
# The pidofproc function shall return one or more process
# identifiers for a particular daemon using the algorithm
# given above. Only process
On Wed, 17 Feb 2021 22:04:06 +0100
Thomas Seeling wrote:
> Hallo,
>
>
> is it possible to query the "breadcrumb" of a grub boot process?
>
> Say I have multiple partitions, e.g. /dev/sda1, /dev/sda5, /dev/sda6,
> with different LFS versions.
>
> When booting grub chooses grub.cfg from the
On Sun, 21 Feb 2021 13:23:51 +0100
Thomas Seeling wrote:
> Hallo,
>
> > Do I understand correctly that the main question is "which
> > grub.cfg will be used by grub at next reboot after running
> > grub-install"? Or is there more?
>
> basically yes, but no ;). I want to know where I came
On Fri, 19 Feb 2021 16:02:30 +0100
Thomas Seeling wrote:
> Hallo,
>
> >> is it possible to query the "breadcrumb" of a grub boot process?
> >> Is there a query function that I can use to find out how my
> >> system got bootstrapped?
>
> > Use a single boot partition and install grub to use
On Mon, 22 Feb 2021 15:12:22 +0100
Armin Tüting wrote:
> Hello,
>
> the following output from binutils 2.36.1:-
>
> [...]
> required isl version is 0.15 or later
> *** This configuration is not supported in the following
> subdirectories:
> zlib
> (Any other directories should still
85 matches
Mail list logo
