It's always bothered me that for some time (perhaps as long as I have
been using LFS?) that I could not get the kernel symbols properly loaded
by sysklogd, producing a message sequence like this:
Nov 15 15:45:38 www kernel: klogd 1.5.1, log source = /proc/kmsg
started.
Nov 15 15:45:38 www
m the line that says iana-etc-20201110.tar.gz - then you get
the pre-built protocols and services file.
Are these files typically DIFFERENT? I've not seen that before.
-Joel
On 2020-11-14 06:58, Pierre Labastie via lfs-dev wrote:
On Sat, 2020-11-14 at 06:18 -0800, Joel Bion via lfs-dev wrote:
The
There's a bit of a mess with protocols/services in the latest builds
from IANA-ETC.
1) They require that Python-3 be installed, because you need to generate
these files in these latest releases by running a script 'update.py',
instead of just being given them in the release.
2) The Python-3
Upgrading Perl was the trigger for me building my own package dependency
tracker utility. With tons of manual configuration, I am able to upgrade any
subset of packages at one time. It tells me what I need to rebuild, in what
order. Some packages trigger no or few rebuilds. Others, like
I must agree with James’ spirit!
I got IPv6 (static addresses) working with LFS and gave my changes back - it’s
easy to do.
And with ARM, the interesting thing about it is that at this point there isn’t
much interesting about it. I haven’t built LFS on ARM, but if I did I would
probably do
As a user of LFS, I appreciate the cleanliness of building the “/tools”
directory in Chapter 5, for this simple reason:
I can pause and log out midway through executing chapter 5, and come back -
without worrying about re-establishing a “context” like a chroot in chapter 5
would require. If I
If the upstream decides to use cmake or meson, things have to change anyway.
But, each are entitled to their opinion, and the editors will decide. :)
Sent from my iPhone
> On Jan 4, 2020, at 7:34 AM, Xi Ruoyao via lfs-dev
> wrote:
>
> On 2020-01-03 09:42 -0800, Joel Bion via l
On 2020-01-03 07:40, Bruce Dubbs via lfs-dev wrote:
On 1/3/20 3:48 AM, Pierre Labastie via lfs-dev wrote:
Le 02/01/2020 à 23:53, Bruce Dubbs via lfs-dev a écrit :
On 1/2/20 3:26 PM, Pierre Labastie via lfs-dev wrote:
Second, use prefix=/usr for Make install, then move the shared
library to
Stick with the x.y.0 is my vote, but my vote is tempered by this uncertainty:
usually, when a team declares a “release” there’s a feature freeze, then
testing with only bug fixes, etc. in other words, a release is different than a
patch. But, is that the case with vim? Or is the “release” just
I agree with what Uwe is saying 100%.
IPv6 use is increasing - right now Google is seeing 24.9% of its
incoming daily traffic is IPv6, of course a lot of that has to do with
mobile devices.
But nobody can really ignore it any more. Ubuntu, Fedora/RedHat, Mint,
etc. - they all support the
So, to summarize:
1) Allow the syntax for if[up,down] to list multiple interfaces (why not?)
2) For each interface:
2a) process all ifconfig. files - such as ifconfig.eth0,
ifconfig.eth0.ipv6 one by one - ignoring both .bak as well as ones ending in ~.
2b) at the end, perform any needed link
ind) most
approximates what a user would want to see if they type "ifdown eth0"
I hope this note better explains why I created ipv46-static.
-Joel
On 2019-12-08 15:11, DJ Lucas via lfs-dev wrote:
On 12/7/2019 9:51 PM, Bruce Dubbs via lfs-dev wrote:
On 12/7/19 9:11 PM, Joel Bion via lfs-
Hint created and sent to hints list
On 2019-12-07 19:51, Bruce Dubbs via lfs-dev wrote:
On 12/7/19 9:11 PM, Joel Bion via lfs-dev wrote:
Hi -
This concerns adding static IPv6 support to Linux From Scratch.
I worked on this a bit a few years ago, but life got in the way, and I
paused all
Hi -
This concerns adding static IPv6 support to Linux From Scratch.
I worked on this a bit a few years ago, but life got in the way, and I
paused all work on this, but over the Thanksgiving break, I finished
things up and and have things working. My LFS machine is now working
fine being a
14 matches
Mail list logo
