quot;
> I'm not a big fan of updating my everyday system just because new stuff
> comes out. I need a reason. Before it did update in 2012, my system
> dated back to late 2005.
That said, not being in "LFS development", I build systems to USE
them. "If it ain't
. It does report the drive on
PATA port, but I realize those PATA ports weren't intended to be full
system drives. Something strange in the way chipsets/BIOS' handle
them? I'd expect the Linux kernel to find it. Is there something
unusual (that "Ibex" has),
void initrd!)
Now it all pretty much makes sense. But I guess I'll have to imbed the
most popular supporting PATA controller chips so I've got a decent
chance of coming up with the newer ICH's. Or not. Probably won't be
trying to use these PATA ports that often.
--
Paul Roger
do # make
make[3]: Leaving directory
`/usr/local/src/gcc-build/i686-pc-linux-gnu/libitm'
make[2]: Leaving directory
`/usr/local/src/gcc-build/i686-pc-linux-gnu/libitm'
make[1]: Target `check-target' not remade because of errors.
make[1]: Leaving directory `/usr/local/src/gcc-bu
of time to do it all.
I also like it when there's time for issues to turn up in the
mailing list. I found nothing remotely similar to my problem,
so it's probably me, but I can't find anything suggestive. I HAVE
looked.
Thanks for your attention.
--
Paul Rogers
paulgrog..
gcc tests are complex, I can't find the "smoking gun" even though I've
continued to look. So I guess I can wipe and start over in Ch6, after
another pass through my C&P scripts. Perhaps there was some
contamination... Do you think I need to build the Ch5 Stage1 package
et `check' not remade because of errors.
---8<...
Seems to me the ABI check is rather important. (First time through I
did try installing anyway, but then building e2fsprogs died in a
mysterious way, so I backed-up to rebuilding GCC.) I think I need to
to find a fix for this.
uot;died in a mysterious way" is not a useful error report.
The way it failed made me suspect the compiler. I need a reliable
compiler before wasting time with e2fsprogs.
The question is why the ABI check is failing. I've seen that libgomp
can make abi_check fail, but we don'
from 6.1 about CFLAGS/CXXFLAGS, so those are
specifically unset when building binutils/glibc/gcc. I looked, but 7.2
doesn't have the same admonitions. Are they still an issue? Can they
be contaminating my build now?
--
Paul Rogers
paulgrog...@fastmail.fm
http://www.xprt.net/~pgrogers/
Rogers
uot;Shellshock" bugs (up to patch
53) if anybody's interested.
--
Paul Rogers
paulgrog...@fastmail.fm
http://www.xprt.net/~pgrogers/
Rogers' Second Law: "Everything you do communicates."
(I do not personally endorse any additions after this line. TANSTAAFL :-)
--
htt
27;s and
above. I've still got useful Pentium-3's!
I've learned a whole lot from LFS in the last decade, thanks to you all,
but I've gotten old (70) and I'm not as sharp as I was. I know that.
8'-( It's hard! It comes to us all, but that's no conso
x27;t seen the book, so forgive me if
this is naive, but that sounds like it could be a toolchain adjustment
problem, doesn't it?
--
Paul Rogers
paulgrog...@fastmail.fm
http://www.xprt.net/~pgrogers/
Rogers' Second Law: "Everything you do communicates."
(I do not personal
t the compressors & encrypters
would use the most advanced enhanced instructions they can find, unless
told not to.)
--
Paul Rogers
paulgrog...@fastmail.fm
http://www.xprt.net/~pgrogers/
Rogers' Second Law: "Everything you do communicates."
(I do not personally endorse any add
cal is kind of "free game". All I keep in /usr/src is the
kernel.
> Compare that to many audio/video packages which do go out of their way
> to get the most out of the processor.
Never have been comfortable with Flash--it's one of those Attack
Surfaces!
> For
due to a tangle-up from an earlier-reported
> one from same make-k run: how difficult is it to differentiate between
> such errors and other (separate/standalone) types of error in the same
> output, often depends inter alia on how well you know the code.
Yes, so after the first -k run, w
. There's no real good fix, restoring the
owning package is PROBABLY the answer, but not without checking!)
--
Paul Rogers
paulgrog...@fastmail.fm
http://www.xprt.net/~pgrogers/
Rogers' Second Law: "Everything you do communicates."
(I do not personally endorse any additions after
;s more complex to setup and manage, do I really care? Yes.
--
Paul Rogers
paulgrog...@fastmail.fm
http://www.xprt.net/~pgrogers/
Rogers' Second Law: "Everything you do communicates."
(I do not personally endorse any additions after this line. TANSTAAFL :-)
t is compatible with any
i686. I thought the toolchain would, but that's wrong.
Is there any preferred method for LFS?
--
Paul Rogers
paulgrog...@fastmail.fm
http://www.xprt.net/~pgrogers/
Rogers' Second Law: "Everything you do communicates."
(I do not personally endorse
nks Pierre, I hadn't run into one myself. I'd like one method
that can be consistent, and not create its own confusions. I still
have to get a good make on gcc shortly! ;-)
--
Paul Rogers
paulgrog...@fastmail.fm
http://www.xprt.net/~pgrogers/
Rogers' Second Law: "Everything
> On 11/30/2014 10:14 PM, Dr.-Ing. Edgar Alwers wrote:
> > On Saturday 29 November 2014 21:21:50 Paul Rogers wrote:
> >
> >> > I'm inclined to give up on systemd ( I don't want, like or need
> >> > more complexity)
For the record, nothing of wha
nux-gnu/4.7.1/include-fixed
/usr/include",
what I got is:
/usr/lib/gcc/i686-pc-linux-gnu/4.7.1/include
/usr/local/include
/usr/lib/gcc/i686-pc-linux-gnu/4.7.1/include-fixed
/usr/include
Does this need to be fixed? (Hopefully in some way so it wouldn't
happen again.)
--
Paul Rogers
pa
Yes? Anything else? (It can keep it's "identity" in /etc, for the
most part.)
(I ran through Ch6 last evening with no real problems, now I'm
studying Ch7 before charging in. That's what brought this question
up.)
--
Paul Rogers
paulgrog...@fastmail.fm
Rogers'
r LCD i686.
> And I do not think this is worth scripting, I only do it very
> occasionally
But when one gets to a certain vintage one tends to forget details. 8-(
--
Paul Rogers
paulgrog...@fastmail.fm
Rogers' Second Law: "Everything you do communicates."
(I do not personally
t;rc" scripts, and
used them in 6.1 & 6.6! ;-0 ) Honest, I haven't touched these LFS
bootscripts! When I get the RO failure the system locks up too. It
says press Enter or ^D, but nothing happens--gotta hit the reset button.
Known problem?
--
Paul Rogers
paulgrog...@fastmail.fm
Ro
ited out some of the stuff not needed
for an initial boot kernel, e.g. sound, added some stuff I figured might
be, e.g. USB thumb-drives, I'll be able to verify & snoop this evening.
(TV's doing a "pledge break". ;-) ) But I just got a replacement CPU
for the box that was t
them! One reason
I've never cottoned onto the Debian style systems! What the hell good
are they? I DON'T CARE how long each step takes! Useless space
wasters! One way or another they are going away!
--
Paul Rogers
paulgrog...@fastmail.fm
Rogers' Second Law: "Everything you d
# mv /etc/rc.d/rcS.d /etc/rc.d/rcsysinit.d
No smoke! Boot and shutdown. Oh joy! ;-)
--
Paul Rogers
paulgrog...@fastmail.fm
Rogers' Second Law: "Everything you do communicates."
(I do not personally endorse any additions after this line. TANSTAAFL :-)
--
http://www.f
logies 8'-( , you are correct. I overlooked Chapter 7.7.
--
Paul Rogers
paulgrog...@fastmail.fm
Rogers' Second Law: "Everything you do communicates."
(I do not personally endorse any additions after this line. TANSTAAFL :-)
--
http://www.fastmail.com - mmm... Fastmail.
a recommendable
level of the kernel that I can transparently patch up to, that would
represent a compatible "sweet spot" of some sort?
--
Paul Rogers
paulgrog...@fastmail.fm
Rogers' Second Law: "Everything you do communicates."
(I do not personally endorse any additions
Sorry, Ken, I got a version of the BLFS book that was contemporaneous
with LFS-7.2, "Version 2012-11-02". It always seems to say: "This
package is known to build and work properly using an LFS-7.2 platform."
8-)
--
Paul Rogers
paulgrog...@fastmail.fm
Rogers' Secon
ce".
So you recommend 3.14? That gives me a goal. Thanks for your advice!
--
Paul Rogers
paulgrog...@fastmail.fm
Rogers' Second Law: "Everything you do communicates."
(I do not personally endorse any additions after this line. TANSTAAFL :-)
--
http://www
;t install the book's 1.0.1c, already got "j", but do you have
particular opinions about which is best?
--
Paul Rogers
paulgrog...@fastmail.fm
Rogers' Second Law: "Everything you do communicates."
(I do not personally endorse any additions after this line. TANSTAAFL :-
e maximally-hardened API. But I guess
I'll have to install all three, against future application. This is a
three-link chain, and the weakest one compromises the whole system.
Major bummer!
--
Paul Rogers
paulgrog...@fastmail.fm
Rogers' Second Law: "Everything you do communicat
do with rcS.d. My question is about the rationale for
introducing that possible confusion. Why was that a good thing?
Is init(8) just so out of date it's wrong?
--
Paul Rogers
paulgrog...@fastmail.fm
Rogers' Second Law: "Everything you do communicates."
(I do not perso
es there at
> all and we never update it in BLFS. 'init S' just does the same as
> 'init 1'
Yes, I understand that it works. My question though was _why_ LFS chose
rcS.d, inviting that confusion, when rcsysinit.d always worked just
fine. Is there some future requi
daemon so they can check later whether
there is one to be stopped, or not. When they are called on to stop
a daemon, they can safely assume that they started it. 'Entering
runlevel N, I start the daemon. Leaving runlevel N, I stop it.'"
If you don't think my use of rc1
at the kernel config itself presents in its "Help"? A site
the kernel team keep current for each kernel release, hopefully.
--
Paul Rogers
paulgrog...@fastmail.fm
Rogers' Second Law: "Everything you do communicates."
(I do not personally endorse any
ary, but takes a long time to go through
>everything.
Indeed, and even so, it's not clear what they "mean", what the
implications are. Particularly so for new options. I don't have time
to follow all the kernel lists about things that seem to be irrelevant
to my "
rse, and thank you for what you've given me
this morning. The explorations noted in the previous paragraph may take
me some time. ;-)
--
Paul Rogers
paulgrog...@fastmail.fm
Rogers' Second Law: "Everything you do communicates."
(I do not personally endorse any additions aft
y
installed on new systems here, my goal is something that will boot on
whatever i686 PC gets thrown at it, with customization to come later.
It probably needs ISA support(!) for example. ;-)
It showed me I don't need Control Groups.
--
Paul Rogers
paulgrog...@fastmail.fm
Rogers' Second Law:
know if they're actually hitting the HD. Is this
normal behavior? I haven't seen that before. I'm wondering if this
becomes a "wear and tear" item for the drive, and especially if it's on
USB flash drives?
--
Paul Rogers
paulgrog...@fastmail.fm
Rogers' Second
ave
no evidence that udevd is even looking at the file! Is there something
special we need to do to enable it in udev-188?
--
Paul Rogers
paulgrog...@fastmail.fm
Rogers' Second Law: "Everything you do communicates."
(I do not personally endorse any additions after this line. TAN
I just read the North Korean "Red Star" Linux has world-writable udev
rules AND rcsysinit. Perhaps not quite ready to be world-wide hackers?
--
Paul Rogers
paulgrog...@fastmail.fm
Rogers' Second Law: "Everything you do communicates."
(I do not personally endorse any
somewhere in the 3.10 patch chain, and that's
also quiet. I'm going with that for the time being. I need to get
on with BLFS.
--
Paul Rogers
paulgrog...@fastmail.fm
Rogers' Second Law: "Everything you do communicates."
(I do not personally endorse any additions a
ur system is working better, you could try testing 3.10.0, and
> then using git to eith bisect between 3.9 and 3.10 (linus' tree)
> or between 3.10 and 3.10.62 (stable tree).
Dunno, maybe I'll just finish this and go for LFS-7.6. Probably a year
from now... ;-)
--
Paul Rogers
In network configuration and ifup, what are "INTERFACE_COMPONENTS"? I
can't find that documented in the book, or BLFS.
--
Paul Rogers
paulgrog...@fastmail.fm
Rogers' Second Law: "Everything you do communicates."
(I do not personally endorse any additi
CES="eth0" # Add to IFACE, space separated devices
IP_FORWARD=true
EOF
Thanks.
--
Paul Rogers
paulgrog...@fastmail.fm
Rogers' Second Law: "Everything you do communicates."
(I do not personally endorse any additions after this line. TA
to go serial and just wait for it with gcc, glibc, binutils, a
few of these big things that have to be done right. A clean build is
worth the wait, when there are other things I could do (laundry, fixing
tea, etc.) while it cranks.
--
Paul Rogers
paulgrog...@fastmail.fm
Rogers' Second L
hen ifup would have the actual script's path and
parameters internally. "Ease of use" has opened up many holes. This
looks like one.
--
Paul Rogers
paulgrog...@fastmail.fm
Rogers' Second Law: "Everything you do communicates."
(I do not personally endorse any
accept the
responsibility for changing it if I add a new service.
> > internally. "Ease of use" has opened up many holes. This looks
> > like one.
>
> Your concerns seem to be about situations where a hacker already
> has root.
Not at all. The fact remains, what
s really hard to get people these days to
appreciate these machines.
--
Paul Rogers
paulgrog...@fastmail.fm
Rogers' Second Law: "Everything you do communicates."
(I do not personally endorse any additions after this line. TANSTAAFL :-)
--
http://www.fastmail.com - Does
I want to keep around,
including this 6.6 I'm using now. Their analysis suggests this isn't as
severe as Heartbleed or Shellshock, and exim is the fallguy they
identify. I'll also update exim.
--
Paul Rogers
paulgrog...@fastmail.fm
Rogers' Second Law: "Everything you
en't so old my native language was FORTRAN instead of the more modern
C, I might make more sense of the large block of code that's being
deleted near the end which isn't mentioned in the Qualys analysis, but
I'll take Gentoo's word for it. Seems like it's fixable on my
In both BLFS-7.2 & 7.4 installing GLU is under the Mesa section, with
typical instructions for installation, but it isn't clear where it's to
be extracted to, the Mesa directory or one of it's own? In 7.6 it's got
its own section. Am I to presume that applies to 7.2 &am
x27;t
recall seeing such configuration in the LFS book, and frankly, I find
the udev rules arcane and daunting. Can you point me to something
understandable that will do the job? I have tried Google once or twice,
but didn't find an "Aha!" moment. TIA.
--
Paul Rogers
paulgrog...@fast
e in more detail. I don't want to have to make
a new rule for every stick I plug in, of course--got about a dozen.
Maybe they can be generalized.
I have gtkam for my camera, it manages the mount for root, but doesn't
change permissions for my user account.
One might think this s
set it up without being too precise about different monitors and
video cards/chipsets, but with screen resolutions I can actually use.
Seems like a combination of one or two sections in xorg.conf.d and
pulling the rest automatically ought to work, if'n I could find more
documentation. ;-( Sug
ve to do the
whole config thing! Of course, I just tested it on my "build box"
and need to see it working on a different box/monitor, but it
*should* work! 8-o
--
Paul Rogers
paulgrog...@fastmail.fm
Rogers' Second Law: "Everything you do communicates."
ke this in my .xinitrc
Only ever use one screen. Never thought xrandr got me anything.
> video driver is in use. Of course, that won't help if you really do
> need to sometimes use smaller screen sizes.
Those 1280's are really hard to read!!!
--
Paul Rogers
paulgrog...@fastmail.fm
y P4's, got Conroes, and one i7-940 MoBo/CPU was given to me which
I fleshed out and only use for a major compiling engine. There are
"sweet spots" every other generation or three.
--
Paul Rogers
paulgrog...@fastmail.fm
Rogers' Second Law: "Everything you do communicates.&
ose 3.7.17 should be a problem. My question is, with this 7.2 and
contemporaneous BLFS, will sqlite-3.8.4.2 be a "drop in"? And will I
have to go back and recompile everything already built for 3.7.14? TIA.
--
Paul Rogers
paulgrog...@fastmail.fm
Rogers' Second Law: "Eve
cessary, fixing up the symlink after every install
> while I am still building the system would get me down. But I still
> think that starting from a version of BLFS which is more than 2 years
> old is a waste of your time for desktop systems.
This old system is 6.6 based. It didn't
y'd like to tell me about?
Then because Java is such a huge attack surface, this is where I want
the latest versions of OpenJDK-2.5.4 and Iced-Tea Web-1.5. Again, is
there anything in particular I should know to make the straddle work?
--
Paul Rogers
paulgrog...@fastmail.fm
Rogers' Seco
Right you are. Reposted to the correct list.
--
Paul Rogers
paulgrog...@fastmail.fm
Rogers' Second Law: "Everything you do communicates."
(I do not personally endorse any additions after this line. TANSTAAFL :-)
--
http://www.fastmail.com - Does exactly what it
ays to use vga=769 on the boot line. That does nothing. The LDP
HowTo's are 5 years old and speak of kernel-2.1!
So my question is, where is a good source for me to get up to speed so I
can make the console framebuffer behave the way I want outside of X?
--
Paul Rogers
paulgrog...@fastmail
lping much. This is one of the
reasons I always avoided them.
--
Paul Rogers
paulgrog...@fastmail.fm
Rogers' Second Law: "Everything you do communicates."
(I do not personally endorse any additions after this line. TANSTAAFL :-)
--
http://www.fastmail.com - IMAP accessib
and experience, simpler.
> /etc/sysconfig/console I set FONT=ter-128n. That is a terminus font
> from http://terminus-font.sourceforge.net/. They have a lot of sizes
> available.
Ok, that's another option. So how do all these compare if I'm
occasionally bouncing out of
nd use.
> It's small, light, and fast. Surely, all we require of a bootloader
> is to boot the system. Again, as you say: "simpler is better".
I used it to boot my floppy Linux. I suppose I'll investigate. Does it
handle UEFI?
> grub can be complicated, but we actually
> Sorry for the noise... :) Life was much easier back in the good old
> Netscape v1.0 and v2.0 days :)
Yeah, no spam!
--
Paul Rogers
paulgrog...@fastmail.fm
Rogers' Second Law: "Everything you do communicates."
(I do not personally endorse any additions after
new systems? (All my boxes currently are
older and don't have this problem. But one day...)
--
Paul Rogers
paulgrog...@fastmail.fm
Rogers' Second Law: "Everything you do communicates."
(I do not personally endorse any additions after this line. TANSTAAFL :-)
--
htt
The mrproper target is only in the kernel
makefile, no other packages.
--
Paul Rogers
paulgrog...@fastmail.fm
Rogers' Second Law: "Everything you do communicates."
(I do not personally endorse any additions after this line. TANSTAAFL :-)
--
http://www.fastmail.com - Doe
the delay is neglibile,
a disadvantage of "hiding it", and the LFS bootscripts neglect to run it
in 0 & 6.
BTW, it's a minor untidyness, but the setclock script sources
sysconfig/clock if it's readable. If not, $UTC will be null, a
condition which is not allowed for in th
, though
the order it finds them on that first boot. Note, however, if you need
a particular NIC/plug to have a particular name, eth?, you can just edit
the MAC address.
--
Paul Rogers
paulgrog...@fastmail.fm
Rogers' Second Law: "Everything you do communicates."
(I do not pers
> No, deleting the file just causes the interface initialisation to
> fail. It did not rebuild the 70-persistent-net-rules file.
No? I thought I'd had that work once when I was moving a drive to
a different box. Sorry for the bad advice. Now I'll know not to
next time.
--
Paul
; And I recently found out why.
I don't think I care what they think the reason why is! It's been eth
since the dawn of time. Let's change all the names of the days of the
week too! We don't want days of the week named for the pagan gods and
goddesses! [/sarcasm]
--
Paul Roge
ht (because most people are right
handed and then the ink didn't smudge), top down. Some people read
right to left, top down, some top down, right to left, but NOBODY
reads bottom up! ;-)
--
Paul Rogers
paulgrog...@fastmail.fm
Rogers' Second Law: "Everything you do communicates.&
cular package, replace it, and compare what's there now
with tarballs that were made of each package at the time it was built.
Really, if you're going to spend the time building a system, you have to
have software management--otherwise it's a monolithic blob you can't do
anything wi
meone else defines and is necessary for his
"update" to fit in and work.
> I must admit, I haven't been updating much, just using each system as
> a build host for the next one when a new book comes out, which is
> probably very bad practice security-wise. What do other peopl
to point out that telnet is very useful
on a secure in-house LAN. If one is "staying home" why pay the overhead
of ssh encryption?
I install telnet and ftp client, but none of the r* programs.
--
Paul Rogers
paulgrog...@fastmail.fm
Rogers' Second Law: "Everything you do com
able with well-established
> Unix/Linux traditions, will expect /bin, /sbin and /lib where they
> always have been and are not all that into changing everything for the
> sake of changing everything.
I'm not a LFS Newbie, but Amen, brudder!
--
Paul Rogers
paulgrog...@fastmail.fm
Roger
building BLFS. But how when I'm building LFS? I've
> tried linking host programs with no success.
aplay?
if [ $? -eq 0 ]
then
aplay "happytune.au"
else
aplay "braaak.au"
fi
--
Paul Rogers
paulgrog...@fastmail.fm
Rogers' Second Law: "Everything
>On 09/17/2015 03:22 PM, Paul Rogers wrote:
>>> I've tried snd-pcsp, snd_dummy, and a beep utility without success. I'm
>>> probably missing something simple. How can I sound a beep when building
>>> LFS with alsa enabled?
>>>
>>&g
a recent LFS on a system that old. I
used to do it regularly, but haven't in quite some time--and I use a
lot of old hardware! ;-)
--
Paul Rogers
paulgrog...@fastmail.fm
Rogers' Second Law: "Everything you do communicates."
(I do not personally endorse any additions after
, POD-3.0rc7/-3.1 (on /dev/sda8)" {
insmod ext2
set root=(hd0,8)
linux /boot/vmlinuz root=/dev/sda8 ro
}
menuentry "Reboot" {
reboot
}
menuentry "Help" {
help
pause
}
menuentry "Halt" {
halt
}
--
Paul Rogers
paulgr
other
thing that may cause some difficulty is beginning with a Debian-based
host system, say as compared to a RedHat-derived system. The two have
gone in quite different directions for many years. LFS is perhaps a
little closer to RedHat derivations. Configure is telling you your host
isn't provid
running through the book again,
very quickly. When I'm careful and get it right (fixing oversights is
just part of the process), I can run through my cloning process on some
temporary host system, e.g. Knoppix or LFS Live, shutdown, move drives
if needed, and boot a configured clone that
ed to get the clock adjusted before udev runs? Any ideas? TIA.
--
Paul Rogers
paulgrog...@fastmail.fm
Rogers' Second Law: "Everything you do communicates."
(I do not personally endorse any additions after this line. TANSTAAFL
:-)
--
http://www.fastmail.com - Send your e
t path. I moved the setclock to before checkfs and so far (once)
there was no problem, though I need to go through a couple cycles
bouncing between systems. Just to check, but it's got to be right!
Thanks for listening! 8-)
--
Paul Rogers
paulgrog...@fastmail.fm
Rogers' Second Law
and grub.cfg, or the MBR/grub.cfg itself. That makes
it easier to focus.
--
Paul Rogers
paulgrog...@fastmail.fm
Rogers' Second Law: "Everything you do communicates."
(I do not personally endorse any additions after this line. TANSTAAFL :-)
--
http://www.fastmail.com
describe)
# short or brief produces a one-liner, anything else
# produces a longer description.
describe $2
;;
setup)
setup
;;
build)
build
;;
finish)
on to www.linuxfromscratch.org:80.
HTTP request sent, awaiting response... 404 Not Found
2015-12-12 19:06:38 ERROR 404: Not Found.
--
Paul Rogers
paulgrog...@fastmail.fm
Rogers' Second Law: "Everything you do communicates."
(I do not personally endorse any additions after
TP links there to
the 7.7 wget-list, dated 3-5-15.
--
Paul Rogers
paulgrog...@fastmail.fm
Rogers' Second Law: "Everything you do communicates."
(I do not personally endorse any additions after this line. TANSTAAFL
:-)
--
http://www.fastmail.com - mmm... Fastmail...
--
ht
> It's curious that you got the wget-list from osuosl and not the rest
> of the files that are all available from the same site, same
> directory.
I just ran the wget-list. 8-D That's what it's for, after all. ;-)
I did hammer it for all the BLFS-7.7 files though.
Why is a userid for messagebus, i.e. dbus, being created in the initial
passwd file, when dbus isn't being installed in LFS? Isn't it more
appropriate to create it in BLFS when installing dbus?
I looked through the lfs-dev list threads for all of 2015 and found
no answer.
--
P
BLFS). But I am similarly reluctant
to deviate from the book.
I guess, perhaps the point being less obviously buried in the lists, my
question is where is all this going? Are these to be serious prereqs?
Is LFS abandoning it's minimalist past?
--
Paul Rogers
paulgrog...@fastmail.fm
Rogers
that's where
LFS is going.
Why can't they be installed as part of BLFS? They
used to be.
>
> -- Bruce
--
Paul Rogers
paulgrog...@fastmail.fm
Rogers' Second Law: "Everything you do communicates."
(I do not personally endorse any additions after this line. TANSTAA
Apologies, I fumbled this reply a moment ago. It wasn't ready and
should be removed.
> We've never been completely minimalist.
Neither am I! But my mantra is KISS; above impatience. I really don't
care about boot times. That's never more than a miniscule fraction of
my total wait time.
Sytem
isn't really
> something to do in a 'nix system.
And not even on MFT/MVT/MVS systems. DD statements are "Data
Definitions", indentifying the sources/destinations of data, files for
the most part.
Better would be "copy cons: myprog.exe" ;)
> [2
t
establish the needs of what kind of internal security enhancements of
what scope? How far do *you* take it, and why?
--
Paul Rogers
paulgrog...@fastmail.fm
Rogers' Second Law: "Everything you do communicates."
(I do not personally endorse any additions after this line. TANSTAAFL
eristics of a
system that really needs more than traditional UNIX internal security,
and how much?
--
Paul Rogers
paulgrog...@fastmail.fm
Rogers' Second Law: "Everything you do communicates."
(I do not personally endorse any additions after this line. TANSTAAFL
:-)
--
1 - 100 of 353 matches
Mail list logo
