Hallo dear list,
for years I have a small helper in /etc/profile.d to search for an
existing ssh-agent instance for my user and set the SSH_* environment
variables accordingly if it finds one. If none is running it does the
usual eval $(ssh-agent) thing.
In the last days I built LFS 10.1
Hallo,
om some older LFS versions I could flip back 2 or 3 pages of screen
content, and this feature seems to have gone with 10.0. Is this some
option I missed to turn on which is optional now? I thought this was
very convenient.
Stay healthy,
Thomas
--
Do you wanna be a legend or a passing
Hallo dear list,
> It was in the development book, but was deleted when updating to
> OpenSSH-8.5p1. I'll file an errata for it at my next commit, but here's
> what you need to do:
looks like I could have simply updated to 8.5 but I wasn't aware that 8.4
wasn't the latest release anymore.
The
Hallo Douglas,
> if [ "$(uname -m)" != "x86_64" ]; then
> l1="#ifdef __NR_pselect6_timeyr"
> l2="SC_ALLOW(__NR_pselect6_time64),"
> l3="#endif"
> sed -e "/^ifdef __NR_read$/ i $l1\n$l2\n$\l3" -i sandbox-seccomp-filter.c
> fi
apart from the minor typos your suggestion is gold!
thanks so
Hallo dear list,
I have successfully compiled LFS 10.1 on my legacy P4 (32 bit) with jhalfs-4212
(svn) on an existing LFS 10.0.
Compilation went fine overnight, after installing a kernel it boots fine.
Next step was compiling openssh 8.4 to make it headless again (I had exchanged
some cables on
Hallo,
> I'll note though that you are the only one giving feedback and the
> scripts have only had minor changes since at least 2011.
if you remember we had a discussion some time ago about the sequence of
bootscripts for shutdown when unmounting network drives. The old method
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 from, not where
I'm going to. If I use "grub-install" I know the grub.cfg from
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 that.
I can understand the rationale and the bigger picture for the
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 partition that ran the last
grub-install command (e.g. /dev/sda1).
But: if I
Hallo,
> which in my SlackBuild scripts, I am using the /tmp directory to untar
> What would be the correct way of untarring in /tmp ?
create a subdirectory below /tmp, this will work.
Stay healthy,
Thomas
--
Do you wanna be a legend or a passing footprint on the sands of time?
--
Hallo,
>> For some reason my /tmp directory keeps resetting to 0755
a typical reason for this problem is unpacking an archive file in /tmp
which contains the "." current directory. tar will happily reset the
permissions and destroy the 1777 setting.
For exactly this reason I try to avoid
Hallo,
> fstrim is now a part of LFS package util-linux.
> For sysvinit I'm not sure how to do this.
thanks for pointing this out. I searched for "fstrim" in the books' ToC
only and missed it.
For SysV you would use a cron job, imho a weekly one would suffice. My
work machine is a RHEL and
Hallo Ken,
>> 9.1 build on SSD:
>> The SBU unit value is equal to 117 seconds.
>> Total time required to build the system: 79.6 SBU
> The SBU in LFS is related to the _host_ system
I build LFS on its older version. If it works I build with that LFS to
the 2nd partition (I'm using a
Hallo,
I did some comparing of build times.
Building was done on an older i5-6500 with 16 GB RAM, SATA harddisk and SSD.
9.1 build on SSD:
The SBU unit value is equal to 117 seconds.
Total time required to build the system:79.6 SBU
8.3 build on HD:
The SBU unit value is equal
Hallo,
>> It fails at intl-stage2, calling configure, and the config.log in the
>> build-directory tells me that ld cannot find crt1.o.
> make a small change of jhalfs to account for that. What is your jhalfs
> revision?
> It should work Ok with revision 4134.
It does now, currently building
Hallo Pierre,
>> It fails at intl-stage2, calling configure, and the config.log in the
>> build-directory tells me that ld cannot find crt1.o.
> Now, it may be something else. Do you mean it fails during gcc-pass1? If it
> fails at some "intl" target, I'd check whether the --disable-nls has been
Hallo,
>> Would a 32-bit kernel work if I compile it on a 64-bit machine with the
>> 32-bit config taken from the current compile system?
> I think you need at least a multilib gcc.
I had success! After a bit of experimenting I found the following to work:
take the .config from the 32-bit
Hallo,
> make i386_defconfig
> make menu config (to customize the kernel)
would it be sufficient to use the exact .config file from the previous
compile on a 32-bit system?
Tschau...Thomas
--
Do you wanna be a legend or a passing footprint on the sands of time?
--
Hallo,
I have some servers running with 32-bit LFS (intentionally). Longterm I
plan to switch to 64 bit, but not right now. I'm contemplating switching
the kernel compile from a 32-bit machine to one of my 64-bit systems to
win some time. The 32-bit P4 compile machine takes ~100 minutes for a
Hallo,
I started LFS 9.0 on a fresh partition and it stopped at step 158 (of my
jhalfs numbering) where it compiles the kernel ... it nearly finishes
but then complains about cpio missing.
CC kernel/rseq.o
AR kernel/built-in.a
GZIPkernel/config_data.gz
CC [M]
Hallo,
> I've been trying off and on to get a Qualcom Atheros to work. lspci
> shows it as AR9227. It's a plain PCI card. I've come to the
> conclusion that there must be a firmware blob for this card.
can you boot some other distribution and check dmesg for messages about
which files are
Hallo,
> For those attempting to install GRUB from the tarball, (I suspect
> very few)
isn't this the main point of "linux from scratch"?
I've *always* built grub from the tarball when building a new LFS system.
Tschau...Thomas
--
"Do you wanna be a legend or a passing footprint on the sands
Hallo,
> CC=$LFS_TGT-gcc
> I mean really on their own line, w/o the trailing '\' on each line.
you could solve that by exporting the variables. only exported variables are
visible in sub shells, or variables listed on the same command line in front of
the command invoked.
"CC=... make" would
Hallo,
I assume those first and last were for packages that aren't in BLFS ?
there were also packages from LFS and BLFS which showed that.
Imho it's not directly stemming from changes in glibc but in stricter
gcc checking, more warnings enabled and less assuming what the
programmer wanted
Hallo,
I think we need to add some role='nodump' tags to some entries in openssh.
that's a great idea. The BLFS book contains lots of "if you want x then
you do y" and jhalfs more or less verbatim copies all the optional stuff
as given.
May I suggest you mark the "documentation" part of
Hallo,
In fact, when using jhalfs with BLFS, there is no way out of some scriptlet
editing. Rewriting the book+jhalfs so that everything can be automated would
be a big task...
that's ok for me. I've been through the generated scripts more than one
time to fit them to my current needs,
Hallo,
For the "rm" instructions, I'd suggest not adding -f, because usually,
where is that happening?
I have no actual example for rm where -f would be necessary, this was
just something coming to my mind when I wrote about forcing interactive
mode with cp or mv and remove -i switches
Hallo and a happy new year,
On all occasions the makefile stopped after 146-revisedchroot with the sudo
the bug. Can you send me the "configuration" file you have used?
I'll try to recreate. I started fresh yesterday, and now the Makefile
contains CHROOT2. I hope I can remember which
Hallo,
I've been entertaining myself by building LFS 8.3 over the weekend.
Originally I wanted to measure the difference between an old Samsung
SATA drive and a more recent SSD on an i5-6500 with 8 GB RAM but it
turned out to be more of an jhalfs adventure ;)
I'm using jhalfs from svn, not
Hallo,
>>> Just to let know to the list, I have a 8.3 liveCD and PXE build
> I generated an ISO, which should be usefull in
> case you need to fix your LFS.
I would like to learn how to build a LiveCD. I tried with squashfs
myself but I could never get it running. Could you elaborate please?
Hallo,
Am 23/08/18, 19:09 schrieb Paul Rogers:
> License Restictions:
> "... or (v) publish or provide any Software benchmark or comparison test
> results."
>
Intel has changed the license restrictions according to the Register
Hallo,
Am 23/08/18, 19:09 schrieb Paul Rogers:
> License Restrictions:
> "... or (v) publish or provide any Software benchmark or comparison test
> results."
since Intel publishes benchmarks by themselves about patch influence I
guess this is a leftover from an NDA of a closed beta test.
Hallo,
>> 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
Hallo,
I have a question regarding setting the video mode.
During boot the kernel switches to a mode suitable to the monitor
capabilities (for my monitor with 1920x1200 this would be 75 rows x 240
cols) if the monitor supports this.
Now here's where my problem starts: I use a 4-port KVM switch
Hallo,
> Wrong - the patch _was_ the fix for 32-bit. 4.17.8 is out now.
good news.
4.17.8 in fact works on my 32 bit machine.
I tried out gzip kernel compression instead of xz but that didn't help.
Tschau...Thomas
--
"Do you wanna be a legend or a passing footprint on the sands of time?"
Hallo,
I am compiling the current linux kernels for my 32 and 64 bit machines.
The latest 4.17.7 does not work for me on 32 bit (intel core2 duo) while
it boots fine on the i5 64 bit.
I used the same config as for 4.17.6 which compiles and boots fine on
the 32 bit CPU.
LFS 8.2, gcc 7.3.
Anyone
Hallo,
>> carelessness. I wonder if it's host-related. I notice that the first
>> complainer was using Mint (an Ubuntu derivative) and the second was
>> using Ubuntu itself. I don't know about the third one. But I seem to
>> remember from some years back that Ubuntu was not then considered a
>>
Hallo,
are you really using gcc 7.0.0 in the upcoming LFS release? I thought
we're heading for gcc 7.3 with retpoline support.
Tschau...Thomas
--
"Do you wanna be a legend or a passing footprint on the sands of time?"
signature.asc
Description: OpenPGP digital signature
--
Hallo,
> Thomas, I'm not quite sure what you are asking me to do. I save all
> my config files for reference. I've got a 4.14.1 kernel building now,
> made with oldconfig using the 4.13.16 config file and defaults for
> all new options. What exactly do you want me to do with it when it's
>
Hallo,
>> I wonder if that explains the problems I am having with recent
>> kernels. I am running on an old machine without PCID (I just
>> checked) and I cannot boot anything later than the end of series
>> 4.13. The panic occurs in the acpi driver
I have some old machines which I reuse as DNS,
Hallo,
> su: must be run from a terminal
what are the defaults in your sudo.conf?
Have you switched on requiretty?
You could selectively (or globally) switch it off.
Defaults:timtas !requiretty
Tschau...Thomas
--
"Do you wanna be a legend or a passing footprint on the sands of time?"
Hallo,
> I built a whole LFS and my normal desktop with 7.3, based on LFS
> r11352 (14th January) and BLFS r19700 (25th January). For that it
> dropped in and the new version gave me no trouble.
for me gcc 7.3 does not seem like a simple drop-in. There were so many
changes standard-wise (C and
Hallo,
I could not compile lynx 2.8.8.rel2 with ncurses 6.1 on LFS svn.
Reason: in /usr/include/term.h the lib-internal variable cur_term is
shielded from visibility by an #ifdef.
I'm not completely sure if term.h is really installed by ncurses because
I couldn't find this file in the ncurses
Hallo
On 02/03/2018 04:42 PM, Bruce Dubbs wrote:
configure needs the following switch on 32 bit systems:
--enable-64-bit-bfd
>>>
>>> Thomas, Have you tested you built grub?
jhalfs logfile tells me that grub was built, and after grub-install I
could boot the machine from the svn LFS
Hallo,
I rebuilt LFS from SVN with kernel 4.15 gcc 7.3 on i686.
# head -n7 /proc/cpuinfo
processor : 0
vendor_id : GenuineIntel
cpu family : 15
model : 4
model name : Intel(R) Pentium(R) 4 CPU 3.20GHz
stepping: 9
microcode : 0x3
> PTI offers
Hallo,
Am 31/01/18, 17:59 schrieb Pierre Labastie:
>>> lib/i386/relocator64.S: Assembler messages:
>>> lib/i386/relocator64.S:66: Error: unknown pseudo-op: `.code64'
> Hmmm, after reading the documentation, it looks like the following flags
> should be added to binutils' configure on a 32-bit
Hallo,
I have a suspicion that grub 2.02 cannot be compiled with gcc 7.3.
grub is step 127 in the jhalfs Makefile so I assume gcc is working in
general, I'm well into ch. 6 of the LFS-svn book.
gcc -DHAVE_CONFIG_H -I. -I.. -Wall -W -DGRUB_MACHINE_PCBIOS=1
-DGRUB_MACHINE=I386_PC -m32 -nostdinc
Hallo,
I saw a report a little while ago claiming that machines as far
back as SandyBridge were also affected, but my SB didn't get
newer firmware.
intel pulled the 201801 microcode from the download site and is offering
now the 201711 archive again.
news are that all CPUs with
Hallo,
Am 17/01/18, 17:03 schrieb Bruce Dubbs:
> shopt -s checkwinsize
this will set bash's internal knowledge about the screen size, but
actually I wanted to know if it's possible to repeat setting the screen
to the maximum size like the kernel did during startup.
I tried commands like setfont
Hallo,
am I right in understanding that for compiling a new kernel with
retpoline resiliency I need a patched gcc until this is covered in an
official gcc release?
Would it be possible to build a concurrent intermediate gcc which does
not affect the mainline one by choosing some different env
Hallo,
I'm using a KVM switch at home to connect 4 PCs to one keyboard, mouse
and screen. This KVM switch simulates 1024x768 resolution for the
machines that are currently not active.
Under unclear situations (to me) the LFS machine looses the settings for
size and resolution hardware-wise, but
Hallo,
> Not all the microcode is to fix Spectre!
>
> My experience is that intel microcode for older processors does not
> get changed, but they copy it into the latest tarball. When I
I dowloaded the 2018 microcode package and to my big surprise I found
files for old CPUs where there was no
Hallo,
during winter vacation I had some fun building LFS again; I wanted to
dive into UEFI systems.
I installed Fedora 27 on a machine with an old-ish i5-3350, 16 GB RAM
and 256 GB SSD.
Fedora 27 comes with gcc 7.2, and this combination cannot build LFS 8.0
without changes. This information
Hallo,
>>> Could i build lfs system on usb disk?If can what i must write?
> I don't see why not. But by default, these drives always have vfat
> filesystems on them. You'll have to reformat it in ext4. Once it's
> mounted on $LFS, it should behave like any other partition.
I was thinking about
Hallo,
> Just to confirm, would downloading the free ISO from the website,
> burning it to a cd, and running it on my host machine get the job done
> (I have never run memtest86 before)?
to the best of my knowledge all linux distro CDs contain an option to
boot into memtest86. It is a very small
Hallo,
> file so that it referred to it instead of the 4.9 kernel. The grub menu
> came up, and then the boot process froze with "Booting GNU/Linux, Linux
> 4.11..." on the screen.
usually the gcc compile process is a very good RAM test in itself but
just to be sure can you boot into memtest86
Hallo,
> I started wondering about the purpose of this line:
> sed -i '233,237 s/max)/max \\/' lib/intprops.h
it seems that the surrounding #define is 0 in your case so you don't
encounter the bad macro definition. The sed introduces a syntax error,
too, so it seems noone ever evaluated
Hallo,
the automated build finished a moment after midnight and the reported
filename is off by one day ...
"The report file 8.0-SBU_DU-2017-04-11.report has been created"
-rw-r--r-- 1 root root 55047 Apr 12 00:08 8.0-SBU_DU-2017-04-12.report
Apart from that the build went fine (minus my
Hallo,
I fixed the timezone setting and restarted make.
To my relief it only restarted at 076 and not from the beginning.
It is one sort of dumb error I tend to make, and usually it occurs when
the penalty is high, in this case when the make step takes a veeery long
time ;)
> That could be
Hallo,
I've tried jhalfs in the latest 2.4 version and it works quite nicely
for me (used it some years ago to build 6.something).
However it failed for me during 076-glibc today because I made a dumb
mistake. I entered a bad timezone name which I only later realized would
not work because
Hallo,
I have built an LFS 7.10 system (without systemd) and I'm quite happy
with it so far, everything works great. Now I wanted to transfer some
files so I connected a memory stick but there's no device to mount.
I'm unsure about whether I should expect an USB stick to work with base
LFS or
Hallo,
one step of LFS preparation is the copying of linux header files to
system include directories.
Should this process be repeated after a kernel update?
Or only after a major update (e.g. 4.7->4.8->4.9)?
Or not at all because it should keep matching the installed gcc?
Tschau...Thomas
--
62 matches
Mail list logo
