On Monday, February 8, 2021 2:59:47 AM CST Pierre Labastie wrote:
> On Sun, 2021-02-07 at 21:49 -0600, paul rogers wrote:
> > On Sunday, February 7, 2021 2:54:42 PM CST Paul rogers wrote:
> > > On Sunday, February 7, 2021 2:33:02 PM CST Pierre Labastie wrote:
> > > &g
On Sunday, February 7, 2021 2:54:42 PM CST Paul rogers wrote:
> On Sunday, February 7, 2021 2:33:02 PM CST Pierre Labastie wrote:
> > On Sun, 2021-02-07 at 13:20 -0600, paul rogers wrote:
> > > On Sunday, February 7, 2021 12:11:09 PM CST Pierre Labastie wrote:
> > > &g
On Sunday, February 7, 2021 2:33:02 PM CST Pierre Labastie wrote:
> On Sun, 2021-02-07 at 13:20 -0600, paul rogers wrote:
> > On Sunday, February 7, 2021 12:11:09 PM CST Pierre Labastie wrote:
> > > On Sun, 2021-02-07 at 11:26 -0600, paul rogers wrote:
> > > > On Su
On Sunday, February 7, 2021 12:11:09 PM CST Pierre Labastie wrote:
> On Sun, 2021-02-07 at 11:26 -0600, paul rogers wrote:
> > On Sunday, February 7, 2021 6:26:29 AM CST Pierre Labastie wrote:
> > > On Sun, 2021-02-07 at 01:18 -0600, p...@kemascraft.com wrote:
> > > &g
On Sunday, February 7, 2021 6:26:29 AM CST Pierre Labastie wrote:
> On Sun, 2021-02-07 at 01:18 -0600, p...@kemascraft.com wrote:
> > I'm working through the LFS 10.0 book. I got the error: " fatal
> > error: bits/c+
> > +config.h: No such file or directory". The file exist. I'm at
> > 8.6.1. Insta
> On 10/24/19 4:54 PM, Paul Rogers wrote:
> >> Is there any reason LFS does not include WGET?
> > I think so. wget is just the tip of an iceberg. I do/would not let ANY
> > (B)LFS system have any network connection until it was suitably prepared,
> > "armo
with everything I need. Everything is stand-alone
until I have about 20 packages installed. Generally far beyond.
--
Paul Rogers
paulgrog...@fastmail.fm
Rogers' Second Law: "Everything you do communicates."
(I do not personally endorse any additions after this line. TANSTAAFL :-)
It's easier for me, because virtually all O run is my own LFS, but knowing
which partition controls GRUB is never a problem. I append "(I own GRUB)" to
the title of that partition's stanza in grub.cfg.
--
Paul Rogers
paulgrog...@fastmail.fm
Rogers' Second Law: "
e it. It's up to you to get yourself to the
top. I've helped quite enough.
BTW, you've seen my Second Law in my tagline. My Third Law is: There is no
such thing as teaching--there is only learning.
--
Paul Rogers
paulgrog...@fastmail.fm
Rogers' Second Law: "Everyt
tir like mad, cooking each dish in just a minute or so.
When I have to go back and startover, which STILL can happen, it's *WAY* faster
than cut and paste, and provides perfect documentation how the system was
built--both great advantages!
If you "like" Mint for building LFS,
20 years between the system you want to build and what it is built on. Many,
many things have changed. I don't see the benefit of trying. The experiences
might not be as parallel as you think. The amount of work certainly doubles.
p.s. Can you be more parsimonious about what you quote a
are explicit
and implicit dependencies. Interchangable parts is not a part of Linux
systems, except in limited circumstances. Branching out on your own is called
"Dependency Hell" for good reason. FBBG! You've been told this several times.
--
Paul Rogers
paulgrog...
per 1024 bytes..
>
> I hope that this is about what You would be OK with for checking out
> the Hard Drive..
Maybe. You used "mke2fs -c ..."? A "normal" mke2fs doesn't do a surface scan,
and since that drive may be bad, you need every sector checked.
&
T format it with ext4!, just ext2.
You're making a 20 year-old system!!! Forget EVERYTHING that has happened
since then. You're going to be using a 2.6 kernel, for crying out loud!
--
Paul Rogers
paulgrog...@fastmail.fm
Rogers' Second Law: "Everything you do communicates.&qu
Download an image of Knoppix-5.0.2 and burn it to a CD, then boot that to a
shell on that K6. Then you'll have a shell to can test that drive with under
Linux.
--
Paul Rogers
paulgrog...@fastmail.fm
Rogers' Second Law: "Everything you do communicates."
(I do not pe
to a
contemporaneous CDR.
> ...
> P.S., I was partially wrong in what I said, Mint first loads itself
> into Memory, probably a small version of the whole thing..
How much does it load into memory? Does it let you have a shell?
>
> Is there any way to Load up a later Mint and u
as telling me what is going on at
the time it fails, e.g. runing some particular program, what made you decide it
was "stuck". "Stuck" isn't an operative word.
--
Paul Rogers
paulgrog...@fastmail.fm
Rogers' Second Law: "Everything you do communicates."
(I do not
you fixed it! If you don't, it's not going to disappear, and
sooner or later it'll come back and bite you in the butt at the worst time!
--
Paul Rogers
paulgrog...@fastmail.fm
Rogers' Second Law: "Everything you do communicates."
(I do not personally endorse any
ld Ptolemy, "There is no royal road to
geometry." Learn by doing.
--
Paul Rogers
paulgrog...@fastmail.fm
Rogers' Second Law: "Everything you do communicates."
(I do not personally endorse any additions after this line. TANSTAAFL :-)
--
http://lists.linuxfromscratch.or
nd you're really better off making sure the
BIOS sees what it knows how to handle, i.e. with a CD drive in it.
--
Paul Rogers
paulgrog...@fastmail.fm
Rogers' Second Law: "Everything you do communicates."
(I do not personally endorse any additions after this line. TANSTAAFL :-)
#x27;d examine all the large caps and look for bulging tops.
What's the CPU and chipset?
--
Paul Rogers
paulgrog...@fastmail.fm
Rogers' Second Law: "Everything you do communicates."
(I do not personally endorse any additions after this line. TANSTAAFL :-)
--
http://lists.linu
6) Fire-up the 586 and keep a keyboard key pressed during post. If it's an AMI
BIOS, there'll be an id string in the lower left corner.
--
Paul Rogers
paulgrog...@fastmail.fm
Rogers' Second Law: "Everything you do communicates."
(I do not personally endorse any
rt over.
3) FBBG! Build the packages in the book. Don't get creative.
4) What identifications are in the board's silkscreen? It may be good to know
what it really is, especially if it's an off-brand. I may be able to come up
with an id.
p.s. I still have my IMSAI!
--
Pa
ad
> the Book OR do I need to copy it to a USB Stick and copy and Paste that
> to the 586 ??
How? Does your 586 support USB? Which version, if any? Do you have a USB
version 1 stick?
I think you should be spending your time reading about the history of the 586
era! Doesn
been found in the kernel and other FOSS
since, e.g. ShellShock, HeartBleed, and Ghost.) You'll be making a 20 year-old
system on 20 year-old hardware, about equivalent to driving a horse and buggy
on an Interstate Highway in a war zone! But don't let that stop you.
--
Paul Rogers
b! Firefox, 10hrs more
or less, will have to be v2.0.0.16 at best, and it won't be able to handle
modern websites, but you knew that. But when you're done it will run.
--
Paul Rogers
paulgrog...@fastmail.fm
Rogers' Second Law: "Everything you do communi
;ve tried them a few times, all
on my desktops, and missed CTL-SHIFT-+ much more than any supposed advantage,
so now just use VESA drivers.
> I just turned 50 and have learned what I know by hacking and poking at
> things - but I’ve clearly missed some fundamental material. I would
>
t; breaking and fixing things is my definition of "fun".
NOOoo! You don't break and fix things until you've got it working.
> important question is: when I get this version booting and running, do I
> get to be Counted a second time? :-)
Also NO.
--
Paul Rogers
boot on anything and everything". Chances are
that would be a lot more difficult on the day you might need it, than it is now!
--
Paul Rogers
paulgrog...@fastmail.fm
Rogers' Second Law: "Everything you do communicates."
(I do not personally endorse any additions
I was at the right time to have
recapitulated essentially the whole history of computing from 1st generation on
up, either professionally or personally.
--
Paul Rogers
paulgrog...@fastmail.fm
Rogers' Second Law: "Everything you do communicates."
(I do not personally
ke subshell and the exit
$PIPESTATUS sets the return code if any part of the pipe produces a return
code, not just the last, i.e. the make, which is what we want.
--
Paul Rogers
paulgrog...@fastmail.fm
Rogers' Second Law: "Everything you do communicates."
(I do not p
something does error out, the script will stop and you'll have a file of
the console log to dissect. PIPESTATUS isn't very well known but works a charm
in this application. I've been doing this for 15 years. ;-)
--
Paul Rogers
paulgrog...@fastmail.fm
Rogers' Second L
K because I don't much care for non-VESA,
but it does depend on frame buffers, boot parameters, which can include kernel
mode setting and vga= or video=, and just which driver is in control. IME it
takes a bit of fiddling to get it, and after you've seen it once or twice, who
cares?
--
ven. I
weasel-word that because I _ALWAYS_ "tee" a log file off of every CMMI and
that's not in the book (yet).
I consider going back to the beginning, wiping it all away, and starting over
from scratch, once, to be expected. Twice, just an annoyance. And my first
build
ing your package management of choice. And
that includes a script "startover". ;-)
They give you an excellent point of departure for your next version.
--
Paul Rogers
paulgrog...@fastmail.fm
Rogers' Second Law: "Everything you do communicates."
(I do not personally endorse
package I question, or compare the original binaries to what's there now. When
I clone an as-built system I have the option of not loading all that stuff, but
with the size of drives in the last several years I haven't needed to except
for testing to make sure that optio
-solution. Break away from beating your head against the wall here--it's
an impediment to the solution. Do something nice for a while, until you can
come back to this with a fresher perspective. It's rarely a waste of time.
"Sleep on it" if possible.
--
Paul Rogers
paulgrog...@
Re: the entropy issue - It's always a good idea to "dd" the host's random
number seed to a new system to start off with. Storage locations may vary.
--
Paul Rogers
paulgrog...@fastmail.fm
Rogers' Second Law: "Everything you do communicates."
(I do not per
f."
(Mickey Mantle)
And watch for side effects of all meds!
--
Paul Rogers
paulgrog...@fastmail.fm
Rogers' Second Law: "Everything you do communicates."
(I do not personally endorse any additions after this line. TANSTAAFL :-)
--
http://lists.linuxfromscratch.org/listinfo
quot; now. Got an idea I'm using the wrong host
system for the set of --TARGETs I'm using & used in the past. Yes, I do have
an old 586 system on this i7! I think I should fix the targets. Thanks!
Sometimes it helps to have someone to talk one out of confusion. TTYL.
--
> but those are both "antique" and who knows if any of it is still
> relevant (apart, obviously, from setting -march).
I have -CTARGET set in all the configures already.
> ĸen
Thanks, again. I suppose I'll wait a couple days for the meds to certainly
have worn off.
at the end of Ch5 this time.
Any idea what I could've done wrong, or whether it IS safe to proceed?
--
Paul Rogers
paulgrog...@fastmail.fm
Rogers' Second Law: "Everything you do communicates."
(I do not personally endorse any additions after this line. TANSTAAFL :-)
--
h
License Restictions:
"... or (v) publish or provide any Software benchmark or comparison test
results."
--
Paul Rogers
paulgrog...@fastmail.fm
Rogers' Second Law: "Everything you do communicates."
(I do not personally endorse any additions after this lin
find.
--
Paul Rogers
paulgrog...@fastmail.fm
Rogers' Second Law: "Everything you do communicates."
(I do not personally endorse any additions after this line. TANSTAAFL :-)
--
http://lists.linuxfromscratch.org/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
U
ne that, as have we all, but it's a waste of time. You'll be
miles ahead by blowing it all away, restoring just the /tools backup, if you
got it all and at the right place, and starting Ch6 from scratch. This time
you might consider putting all the book's instructions for each package in
> Is it possible to force-set the video mode after boot? Is this a
> separate package with some CLI or is this not possible at all?
Depending on the driver you're using, it may be trivial. You can set it by a
kernel boot parameter in the GRUB stanza, e.g. video=1024x768 or whatever
ouble with getting a newer i3 is the infrastructure incompatibility.
There's no failure short of a direct lightning strike that would take me down
for more than a few minutes.
Thanks, Ken. I'll start prowling kernel versions again.
--
Paul Rogers
paulgrog...@fastmail.fm
Rogers'
I've been hoping for KPTI mitigation
for 32-bit kernels, but mostly have lost hope.
So to be clear, are we talking here about running 4.17 in 32-bit mode, or just
on a Core-2 Duo, which LFS would build in 64-bit mode "unless steps were taken"
(gmp, et al)?
--
Paul Rogers
pa
modules need to be available to the system at all times,
and 3) rebuilding the kernel isn't fearsome for us, I've never seen ANY need
for an initramfs and build what's necessary as a monolithic kernel.
If that's true, even with systemd, why is there any need to build an initram
that calls init-net-rules. The
book doesn't say so, but from a cursory look at the code it seems as if ".
/lib/udev/init-net-rules INTERFACE_NAME=eth0" (or the inverse) might work. Is
that right? (It says it's an LFS script, so someobdy here should know.)
--
Paul Roger
working on a processor that runs at less than 10W, and
the mini-ITX infrastructure makes a nice small system. It was a bit of a
"heavy lift" for the processor, so I typically go back to 7.2.
--
Paul Rogers
paulgrog...@fastmail.fm
Rogers' Second Law: "Everything you do communic
ht there next to it.
http://www.linuxfromscratch.org/hints/downloads/files/pio-files/
--
Paul Rogers
paulgrog...@fastmail.fm
Rogers' Second Law: "Everything you do communicates."
(I do not personally endorse any additions after this line. TANSTAAFL :-)
--
http://lists.linuxfromscrat
linuxfromscratch.org/hints/downloads/files/pio-hint.txt
--
Paul Rogers
paulgrog...@fastmail.fm
Rogers' Second Law: "Everything you do communicates."
(I do not personally endorse any additions after this line. TANSTAAFL :-)
--
http://lists.linuxfromscratch.org/listinfo/lfs-support
F
I See the Hints page about using "pio", "Package Installation Observer"
(formerly known as "git", but that name got usurped). I've been using it with
(B)LFS installs for almost 15 years now, and find it fits in very well, YMMV.
--
Paul Rogers
paulgro
-2 Duo.
>
> List, I didn't realise that the same problem was already discussed on
> this mailing list.
Yes, thing can get rather "buried". The book/site doesn't seem to use the
errata much.
--
Paul Rogers
paulgrog...@fastmail.fm
Rogers' Second Law:
>>
> >> Just my 2c's worth
> >> da kiwi
> >
> > When I last looked at Pale moon (last year), I was under the
> > impression that it needed a much older version of gcc than we were
> > then using ?
I looked at it within the last couple months bu
se those old systems
> when I've managed to trash the current one and need to recover from
> backups. So I have successfully updated both 8.2 and 8.1 systems.
>
> ĸen
My approach is to keep a couple bootable versions on each box, but I suspect my
versions are a bit more stable than
;ve got it all thought out, if you know what I mean. Sometimes
it can be a good thing when one can't just "brute force it" and has to do it
with some finesse.
I'll do building on an old 12GB i7-940, so's I can use -j8.
--
Paul Rogers
paulgrog...@fastmail.fm
Rogers&#
e right. I was trying to address the more general proposition of adding
optimizations when building. IMO, it's generally not a good idea.
--
Paul Rogers
paulgrog...@fastmail.fm
Rogers' Second Law: "Everything you do communicates."
(I do not personally endorse any add
ed how and where
is not worth the generally minor speed benefits. I never add optimization
options when building LFS unless the instructions say to. If the programmer
knows it's OK and adds it to the makefile parameters, fine. I don't presume to
know better, that it would work when (s)h
y error, but still with -mtune in CFLAGS, and it
ran without a hitch. Fine, I'll take it. I don't know where that odd line
came from, but I don't even know if I can reproduce it. I'll go on from here,
see what happens, if anything.
Apologies for interrupting your weeken
to try compiling without -mtune, the one known
difference, and later recompile xz on something like a P4 or Conroe?)
--
Paul Rogers
paulgrog...@fastmail.fm
Rogers' Second Law: "Everything you do communicates."
(I do not personally endorse any additions after this line. TANSTAAFL
environment at each
snapshot you may or may not have been. That's not the job any of us are
volunteering for.
I'm sorry to have to tell you this, but none of us are going to analyze what
you're telling us you did, and showing us in bits and pieces, and tell you
w
parted from the
book's path--and that's why I used the word "forensic" above. No deviations
are allowed. And yes, from time to time I've had problems there myself.
- I start all my build scripts "#!/bin/bash -e" so they "drop out" on errors.
Of
LFS-7.7 as host.
Let me take a look at the archives, I haven't been following this thread until
this caught my eye.
--
Paul Rogers
paulgrog...@fastmail.fm
Rogers' Second Law: "Everything you do communicates."
(I do not personally endorse any additions after this
Some first-gen Core CPUs also get
the axe, including the Intel Core i7-970, 980, 980X, and 990X."
--
Paul Rogers
paulgrog...@fastmail.fm
Rogers' Second Law: "Everything you do communicates."
(I do not personally endorse any additions after this line. TANSTAAFL :-)
--
http://
gt; Oh well, I'll probably reboot to bare metal, or just start living inside
> VirtualBox, but nailing this issue would be educational.
I agree not to let it go. But if you're virtualized you should have kept
"squeaky-clean" initial install systems, and have an easy time of
And although I do recognize
there may come a time to break backward compatibility, I still wish they'd
provide a P2->P3 translator.
--
Paul Rogers
paulgrog...@fastmail.fm
Rogers' Second Law: "Everything you do communicates."
(I do not personally endorse any additio
m I protecting it from? I use root. One must be just as
careful when using sudo anyway. Have I screwed up? Once or twice since I
built my first LFS in 2004, but that's what backups are for.
--
Paul Rogers
paulgrog...@fastmail.fm
Rogers' Second Law: "Everything you do commun
.4.115 & 4.9.81.
I searched the Changelogs for "kpti" and "32.b" but found nothing to suggest
they have mitigations for 32-bit kernels. Nor 64-bit for that matter.
--
Paul Rogers
paulgrog...@fastmail.fm
Rogers' Second Law: "Everything you do communic
On Fri, Feb 2, 2018, at 10:00 AM, Paul Rogers wrote:
...
> installed this system with the original kernel on a 1 MHz low-power
> (~10W) VIA C7 "Esther" (P3 equivalent) system, but while compatible the
> CPU can be painfully slow. Not today, Esther. I worked on my
> &
't
made its way into 4.4 i686 kernels yet.
No use building Spectre mitigation if Meltdown is wide open, so I bailed out at
that point. I'm still hoping for Meltdown patches!
--
Paul Rogers
paulgrog...@fastmail.fm
Rogers' Second Law: "Everything you do communicates.&quo
ations yet that the 4.4 & 4.9 kernel
patches install PTI on i686 builds.
Also, perhaps you can clarify: The latest kernel patches for 4.4 & 4.9 use
retpoline. Clearly we *want* both, but I'm confused about whether each offers
any mitigation on its own?
--
Paul Rogers
paulgrog..
end of the
matter"):
https://lkml.org/lkml/2018/1/22/598
This is an older (1/4) thread about IBRS/IBPB microcode patches that has a
rather extensive chain:
https://lkml.org/lkml/2018/1/4/615
Responses to that "garbage":
https://lkml.org/lkml/2018/1/21/194
Newer (1/20) long-
n the list an
> extremely helpful and informative supplement to the LFS-build process.
Indeed, the more of us looking for the best advice to share, the better for us
all.
--
Paul Rogers
paulgrog...@fastmail.fm
Rogers' Second Law: "Everything you do communicates."
On Tue, Jan 23, 2018, at 10:38 AM, Bruce Dubbs wrote:
> Paul Rogers wrote:
> > "SUSE's Richard Biener is making preparations for officially releasing GCC
> > 7.3.0 on Thursday, 25 January.
> >
> > GCC 7.3 is the point release to GCC 7 that's quick
y
Anybody know of fixes backported to gcc-6?
--
Paul Rogers
paulgrog...@fastmail.fm
Rogers' Second Law: "Everything you do communicates."
(I do not personally endorse any additions after this line. TANSTAAFL :-)
--
http://lists.linuxfromscratch.org/listinfo/lfs-support
FAQ: http:/
o affected, but my SB didn't get newer
> firmware.
>
> ĸen
The initial reports suggest even my Conroes and Nehalem-Bloomfield/Lynnfield
are!
--
Paul Rogers
paulgrog...@fastmail.fm
Rogers' Second Law: "Everything you do communicates."
(I do not personally endorse any
"Windows patches are fixed, but microcode updates are causing even more
trouble."
https://arstechnica.com/gadgets/2018/01/good-newsbad-news-in-quest-to-get-meltdown-and-spectre-patched/
--
Paul Rogers
paulgrog...@fastmail.fm
Rogers' Second Law: "Everything you do comm
> Paul Rogers wrote:
> >> Well, except if the kernel breaks something, just remove the file and
> >> grub entry and then reboot. If a BIOS/UEFI update causes an issue, you
> >> get the pleasure of finding out whether there is a supported downgrade
> >> path.
> Well, except if the kernel breaks something, just remove the file and
> grub entry and then reboot. If a BIOS/UEFI update causes an issue, you
> get the pleasure of finding out whether there is a supported downgrade
> path. :-)
IF your system hasn't been "bricked"
On Sat, Jan 13, 2018, at 4:09 PM, Bruce Dubbs wrote:
> Paul Rogers wrote:
>
> > Updating microcode can be a dangerous thing. I've never found a need
> > to live on the bleeding edge of technology.
>
> I agree about bleeding edge issues, but leading edge is OK. M
tes *do* mitigate Spectre.
Intel has withdrawn some of the updates because they caused new problems.
Updating microcode can be a dangerous thing. I've never found a need to live
on the bleeding edge of technology.
--
Paul Rogers
paulgrog...@fastmail.fm
Rogers' Second Law: "E
https://newsroom.intel.com/news/intel-security-issue-update-addressing-reboot-issues/
--
Paul Rogers
paulgrog...@fastmail.fm
Rogers' Second Law: "Everything you do communicates."
(I do not personally endorse any additions after this line. TANSTAAFL :-)
--
http://lists.linux
in is expected to soon build a customized
kernel, eliminating a lot of HD drivers, adding NIC, ALSA, AGP/FB/DRI--none of
which are *necessary* to boot.
--
Paul Rogers
paulgrog...@fastmail.fm
Rogers' Second Law: "Everything you do communicates."
(I do not personally endorse any
#x27;t know what to make of all this. Making sense of Intel's
file names as relates to particular hardware is also obscure to me.
--
Paul Rogers
paulgrog...@fastmail.fm
Rogers' Second Law: "Everything you do communicates."
(I do not personally endorse any additions aft
ax is only 2GB, IIRC. IMO, running a 64-bit OS is a plus
only if it has more than 4GB to play with.
--
Paul Rogers
paulgrog...@fastmail.fm
Rogers' Second Law: "Everything you do communicates."
(I do not personally endorse any additions after this line. TANSTAAFL :-)
--
http://
ly fashion is very
much more so. What kind of important jobs? How about all the infrastructure
we all depend upon? Like having potable water coming out of the tap?
> said he *thought* the problem started with the Westmere generation.
So the guys who found it and said it affected everyt
> On Mon, Jan 08, 2018 at 04:14:50PM -0800, Paul Rogers wrote:
> > I've just patched one of my older Core2 "Conroe", LFS-7.7, up to 4.4.110.
> > It's an i686 system.
> >
> > Any ideas? TIA.
> >
>
> Looking at my lkml mailbox, patch
NC_RAID6_RECOV=y
CONFIG_CRYPTO=y
#
# Crypto core or helper
#
> > The ext3 filesystem is still available in 4.14.
>
> I read it wasn't:
> "KernelNewbies: 4.3
Apparently that source was wrong.
--
Paul Rogers
paulgrog...@fastmail.fm
Rogers' Second Law: &qu
http://www.kroah.com/log/blog/2018/01/06/meltdown-status/
--
Paul Rogers
paulgrog...@fastmail.fm
Rogers' Second Law: "Everything you do communicates."
(I do not personally endorse any additions after this line. TANSTAAFL :-)
--
http://lists.linuxfromscratch.org/listinfo/lfs-su
esystem and leaves Ext4, which can
also mount Ext3 filesystems, as the main Ext filesystem; "
--
Paul Rogers
paulgrog...@fastmail.fm
Rogers' Second Law: "Everything you do communicates."
(I do not personally endorse any additions after this line. TANSTAAFL :-)
--
http://lists.linuxfr
ility issues also. Had that once with inode sizes, and didn't need the
delay!
--
Paul Rogers
paulgrog...@fastmail.fm
Rogers' Second Law: "Everything you do communicates."
(I do not personally endorse any additions after this line. TANSTAAFL :-)
--
http://lists.linuxfromscrat
or patches to solidify. There are significant
infrastructure issues all around. Not to mention (Windows & Linux) "kernel"
support for all the systems in commercial service in hospitals, grocery stores,
and offices that will never be updated.
--
Paul Rogers
paulgrog...@fastmail.fm
Rogers&#
ght I was being clear when I said "it's not worth doing" that I
was expressing a personal value judgement.
>
> ĸen
>
> 1. I think it was tglx (a kernel maintainer) who first used that
> phrase, I like it.
New to me. But I fear google is more than a numb
cific kernel will be built for
that box in its intended purpose configuration. I don't think I've ever
deleted those first two kernels on any cloned box--fallbacks. WFM.
--
Paul Rogers
paulgrog...@fastmail.fm
Rogers' Second Law: "Everything you do communicates."
(I do n
LFS system just fine.
--
Paul Rogers
paulgrog...@fastmail.fm
Rogers' Second Law: "Everything you do communicates."
(I do not personally endorse any additions after this line. TANSTAAFL
:-)
--
http://lists.linuxfromscratch.org/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/blfs/
's irrelevant,
from Ch5 is appropriate. Don't tell someone, "Don't do what I'm going
to tell you all through this chapter," and proceed to tell them how to
do what they're not supposed to do, and be surprixed when they continue
to do it.
--
oremost among the stumbling blocks, especially where gcc is involved,
but there are others, e.g. I'm not sure how to tell Clang to
cross-compile, audio-video drivers, MPEG decoders, etc.
--
Paul Rogers
paulgrog...@fastmail.fm
Rogers' Second Law: "Everything you do communica
> >
> > Maybe change the video mode on the kernel command line if using KMS.
> > Append something like video=1024x768-24@60m, for instance, to the
> > grub.conf. The first four values and separators should be obvious, the m
> > adds margins. See Documentation/fb/modedb.txt for complete document
1 - 100 of 353 matches
Mail list logo
