Re: [blfs-support] Is it worth jumping in for me? / Can LFS be even more simple?
Am Mittwoch, dem 06.01.2021 um 22:24 -0600 schrieb Paul via blfs- support: > I am interested in the idea of LFS to better understand Unix/Linux. I > have been using Linux (Ubuntu/Debian/Arch) as my desktop for several > years and it bothers me that I still don't understand A LOT about how it > works. I like the idea of being able to simplify to the point where I > understand the whole thing. However, looking through some of the LFS > book (I haven't actually done it) I am concerned that the final system > may still not be simplified to the point where I will have time to > understand it all. > > Question 1: If I thoughtfully work through LFS, will I understand what > every file on my system is for and what every process in userspace is doing? Definitly not every single file/process. There are still (even LFS is quite lightweight) thousands of them, at least files - so i don't think there's someone who knows them all by name. But for sure you'll get a better understanding of how they are organized on disk and probably a better understanding of where to look when searching for something. > > Question 2: Is it possible to run a system using only the kernel, grub > (or other bootloader), maybe a compiler/libc if I need it, and a single > executible loaded by the kernel that I would write in C? Kind of like a > "hello world" exercise that would turn my computer into a single > text-based game, a super super super simple shell, or literally printing > "hello world" on the monitor? Sure, that is the 'init' program (/sbin/init) which needs to be replaced. Than you can strip down your system to be a two-files-OS (1. kernel, 2. your init). Doubt whether it is really fun ;-) > > Thanks! -Paul > -- Thomas -- http://lists.linuxfromscratch.org/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-support] Network issue with VirtualBox
Am Samstag, den 10.10.2020, 11:39 +1100 schrieb Fosca via blfs- support: > > Hello Everyone, > > Nice to meet you all. > > Well I have just managed to do LFS-10.0 in VirtualBox. > > The way I set it up was to install ArchLinux with the Anarchy-Installer > since Arch is quite uptodate with packaages; the one exception being > that 'sudo pacman -S make' needs to be done. > > Using VB allowed me to Snapshot progressively and so saved me from long > spells on the keyboard and having to re-do when something went haywire. > > Now the issue I'm having is that 'ping -c 5 www.google.com' does not > work in the new LFS-10.0 (which I have on sda3). > > My '/etc/sysconfig/ifconfig.enp0s3' reads as follows: > > ONBOOT=yes > IFACE=enp0s3 > SERVICE=ipv4-static > IP=192.168.1.222 > GATEWAY=192.168.1.154 > PREFIX=24 > BROADCAST=192.168.1.255 > > And it's not working in VB. > > Now if I look at Arch in VB on sda2, it says that it has an > IP - 10.0.2.15 > Broadcast - 10.0.2.255 > if that should mean anything in this case. > > My modem-router is a Billion BiPAC 8700AX(L)-1600 > > I would much appreciate some pointers on how solve this little problem. > > Kind regards > > Fosca > I've setup all my LFS stuff in VBox and it works pretty nice. I configured the network for the VMs as "Netzwerkbrücke" - don't know what the exact english translation is, i think something like "Bridged network". Use the device with which the VBox host is connected to the LAN. Within the VMs, the network is set up just as the VMs would be physical parts of the network. Choose an IP form the network range and set the GATEWAY to what is configured as such on the VBox host. Than you should be able to reach the internet from the VM as well as reach your VM from the LAN. -- Thomas -- http://lists.linuxfromscratch.org/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-support] Beyond Linux® From Scratch (System V Edition) - Version 9.1: LSB-Tools-0.6
Hi Scott, Am Freitag, den 14.08.2020, 07:24 -0400 schrieb Scott Andrews via blfs-support: > On Fri, 14 Aug 2020 08:18:09 +0200 > Christopher Gregory via blfs-support > wrote: > > > Hello, > > > > As a general rule we do not give assistance to people who are doing > > things outside the scope of the written book instructions. We do not > > use either the debian packaging system nor that of Redhat or whatever > > they like to call themselves these days. > > > > I know from personal experience that you have to have an expert grasp > > on the various package managers to be able to successfully create a > > working package, and that is on a system that natively uses such a > > system, which lfs/blfs does not. > > > > Christopher. > > My point is that the utility that you have has errors with it. That > doesn't have anything to do with a package manager. The rngd > package does come from debian but the init script is yours, ie it is > from the LFS template. Shouldn't the utility you have install and remove > the init symlinks correctly? Or should if fail? Should the utility > that you offer work after installation? After installation what does the > method used to install it have? If it is broke, it is broke. Also you > claim LSB support/conformity but LFS does not fully conform to LSB > specs. You have to have rpm installed to do so, Also LFS does not > conform to the LSB spec on langauges, particularly Python. i think that went a bit the wrong direction. I'm pretty sure that Chris didn't meant that you have to give up if there is a hickup when using (B)LFS. Using (B)LFS is definitly in scope of the group here - especially in this channel. I assume that came from partly really annoying support cases (mostly on the IRC) where ppl sometimes come up with really strange setups, huge deviations from the book and finally the expectation that we could fix their system right in the next minute by having a look in the crystal ball. > Again I see that I am abandoned by the LFS group and I am on my own. > Should I fix this myself? And if I do should I keep the fixes to > myself? Why should I fix and post the fixes to the package if I am > always abandoned by the LFS editors/group? As far as i can see, this issue has been tracked down to a typo in the LSB package (which already is fixed by a sed in the current instructions), so your report was definitly ok - while initially it was not that clear. Whenever you have found a bug, fixes in form of patches or of sed (if the fix is not that complex) are always welcome! So, keep calm and happy LFSing ;-) -- Thomas Btw, to which chapter in LSB are you referring in terms of RPM & Python? -- http://lists.linuxfromscratch.org/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-support] LiveCD
Am Montag, den 01.06.2020, 11:53 +0300 schrieb Greekforce1821 via blfs-support: > Good morning gentlemen, I have a question for you. Is it possible, when I > finish my BLFS build, to create an iso image just like an ordinary livecd in > order to share my fully customised BLFS distro? Generally spoken: yes. But you cannot simply copy the partition over to an ISO. There is some more stuff to do. You need a CD boot loader (syslinux), you have to find the CD while booting, deal with the fact that a CD is read- only, setup ramdisks, mount filesystems etc. etc. You need to strip down the installation and use squashfs, at least a 700MB CD is probably not large enough... -- Thomas -- http://lists.linuxfromscratch.org/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-support] Older GCC install
Am Samstag, den 16.05.2020, 13:39 +0200 schrieb Cliff McDiarmid via blfs-support: > > Sent: Saturday, May 16, 2020 at 12:11 AM > > From: "Don Cross via blfs-support" > > To: "BLFS Support List" > > Cc: "Don Cross" > > Subject: Re: [blfs-support] Older GCC install > > On Fri, May 15, 2020 at 6:00 PM Cliff McDiarmid via blfs-support > > mailto:blfs-support@lists.linuxfromscratch.org]> > > wrote: > > I need to install an older GCC to compile a particular piece of software. > > At present I'm using GCC 9.2(recent LFS). > > I've managed to compile 8.4 and it works, but I need 8.1. > > > As a long-time C programmer, I'm curious why you need an older C compiler. > > Okay thanks Don. I'm trying to compile Gnucash 3.10 which has not been a > problem in the past. The dependencies at present stress the use of GCC 8.0 > > > If I knew what problem gcc 8.4 is causing, maybe I could help get it > > working, so you don't need to compile 8.1. I'm willing to give it a shot if > > I had more details. > > I've compiled Gnucash 3.10 with GCC 8.1 abeit on another LFS(older). > > On my newer LFS it fails with GCC 9.2 AND 8.4 which as I mentioned I got > working on the same system. I hope you're still with me. > > Anyway.. the errors that the compilers are producing, with Gnucash, look like > compiler errors. Not missing libraries or fuctions etc. They are > substantial and I could mail them if you can help. What are those errors? Usually, if an old package cannot be compiled with a recent compiler, its hardly an error of the compiler but weak programming of the package. Older compilers may accept those weakness, newers don't. Maybe its possible to patch gnucash a bit to get it compiled... -- Thomas -- http://lists.linuxfromscratch.org/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-support] Falkon browser 3.1 not working, QtWebEngine problem?
Am Sonntag, den 05.04.2020, 11:07 + schrieb Mark Broeders via blfs-support: > Hello! > > I've succesfully completed a (B)LFS (development version) install and > everything works great so far, but I can't seem to get Falkon browser > working. I suppose the problem must be with QtWebEngine, but so far I haven't > been able to figure out what I've done wrong. I completely followed the book > and everything installs fine, but when I open Falkon it just shows a blank > page (with everything else showing fine, such as the menu bar etc.). It > doesn't load any URL's and the only message I'm getting is: > > QWebEngineUrlScheme::registerScheme: Too late to register scheme "falkon" > QWebengineUrlScheme::registerScheme: Too late to register scheme "extension" > Please register the custom scheme 'falkon' via > QWebEngineUrlScheme::registerScheme() before installing the custom scheme > Please register the custom scheme 'extension' via > QWebEngineUrlScheme::registerScheme() before installing the custom scheme > Use of deprecated not thread-safe setter, use setUrlRequestInterceptor instead > > I've also installed Otterbrowser succesfully (just to investigate if > QtWebEngine might be the culprit), but that just gives me a flickering > screen. It seems to load the opening page (duckduck.go), but I cannot type > anthing. If i type in a different URL it just crashes without any error > messages (except for the "Use of deprecated not thread-safe setter, use > setUrlRequestInterceptor instead" message i believe). > > Some additonal info: I tried with both 9.1 and the development version of the > book. Tried with both Qt 5.14.1 and 5.14.2, with QtWebEngine as part of Qt > and QtWebengine seperately. My xorg settings are good, rendering and such are > working fine. And i have absolutely no idea what to do next (I've already > done a complete reinstall). > > Could anyone help me with this? Or give me a pointer what to do next? Thanks > in advance! I saw that once before but unfortunatly, i cannot remember how i fixed it. Which qt/qtwebengine version do you use? Did you something recompile after falkon has been installed? What happens if you start "falkon -e" ? Btw, I see the messages too but falkon works pretty fine. -- Thomas -- http://lists.linuxfromscratch.org/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
[blfs-support] OT: folding@home / corona
Hi all, for those who have some spare CPUs and might want to donate them to the FAH project, I hacked a little setup script with which you get the FAH client running on you LFS box. FAH provides data packages on which some calculations has to be performed. Actually, the project provides data to analyze protein structures which might be helpful to fight the currently well-known (or sadly not known) corona virus. Providing the data to many computers the sum is more powerful as being a super computer. Everyone to decide for your own whether this is helpful or not - but i think if there is chance, we should take it... FAH client is provided as a binary only but its statically linked so nearly everything the client needs is on board. Installing the client is not really invasive - just two binaries in /usr/bin and some stuff in /usr/share. The attached script sets the client up ready to run. You might want to have a look into the script first as there are three parameters to set for your environment. Happy folding ;-) -- Thomas (running two VMs with 4 CPUs each for FAH) setup-fah.sh Description: application/shellscript -- http://lists.linuxfromscratch.org/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-support] New package: chkconfig
Am Freitag, den 03.04.2020, 12:38 -0400 schrieb Scott Andrews:
> On 4/3/20 12:21 PM, Thomas Trepl wrote:
> > Am Freitag, den 03.04.2020, 10:42 -0400 schrieb Scott Andrews via
> > blfs-support:
> > > Any interest in adding chkconfig to the system V book?
> > >
> > > I have successfully added it to my systems.
> > >
> > > I also have a script that starts and stop daemon and will tell you all
> > > the daemons present on the system and the status running or stopped.
> > > Any interest in that?
> > I think for the SysV guys it might be of interest.
> > Is there a link to the package/script?
> >
> > --
> > Thomas
> >
>
> https://github.com/fedora-sysv/chkconfig
>
> I use this package chkconfig-1.11.tar.gz.
>
> I use rpm and I can attach the spec file for this
>
>
> This is the service script
>
> cat > /usr/sbin/service << EOF
> #! /bin/sh
> VERSION="$(basename $0) ver. 0.92"
> USAGE="Usage: $(basename $0) < option > | --status-all | [ service_name
> [ command | --full-restart ] ]"
> SERVICE=
> SERVICEDIR="/etc/rc.d/init.d"
> OPTIONS=
> if [ $# -eq 0 ]; then
> echo "${USAGE}" >&2
> exit 1
> fi
> cd /
> while [ $# -gt 0 ]; do
> case "${1}" in
> --help | -h | --h* )
> echo "${USAGE}" >&2
> exit 0
> ;;
> --version | -V )
> echo "${VERSION}" >&2
> exit 0
> ;;
> *)
> if [ -z "${SERVICE}" -a $# -eq 1 -a "${1}" = "--status-all"
> ]; then
> cd ${SERVICEDIR}
> for SERVICE in * ; do
> case "${SERVICE}" in
> checkfs ) ;;
> localnet) ;;
> mountvirtfs) ;;
> rc) ;;
> sendsignals) ;;
> swap) ;;
> udev_retry) ;;
> cleanfs) ;;
> modules) ;;
> network) ;;
> reboot) ;;
> setclock) ;;
> template) ;;
> console) ;;
> halt) ;;
> mountfs) ;;
> sysctl) ;;
> udev) ;;
> *)
> if [ -x "${SERVICEDIR}/${SERVICE}" ]; then
> env -i PATH="$PATH" TERM="$TERM"
> "${SERVICEDIR}/${SERVICE}" status
> fi
> ;;
> esac
> done
> exit 0
> elif [ $# -eq 2 -a "${2}" = "--full-restart" ]; then
> SERVICE="${1}"
> if [ -x "${SERVICEDIR}/${SERVICE}" ]; then
> env -i PATH="$PATH" TERM="$TERM"
> "${SERVICEDIR}/${SERVICE}" stop
> env -i PATH="$PATH" TERM="$TERM"
> "${SERVICEDIR}/${SERVICE}" start
> exit $?
> fi
> elif [ -z "${SERVICE}" ]; then
> SERVICE="${1}"
> else
> OPTIONS="${OPTIONS} ${1}"
> fi
> shift
> ;;
> esac
> done
> if [ -f "${SERVICEDIR}/${SERVICE}" ]; then
> env -i PATH="$PATH" TERM="$TERM" "${SERVICEDIR}/${SERVICE}" ${OPTIONS}
> else
> echo $"${SERVICE}: unrecognized service" >&2
> exit 1
> fi
> EOF
>
> chmod +x /usr/sbin/service
Thanks!
Well, strange version numbering ... but more difficult is that they refer to
SElinux stuff which is AFAIK not available on a LFS system. So to use it on a
LFS system, SElinux must be patched out or add a lot more to the book (SElinux)
than just this package.
--
Thomas
--
http://lists.linuxfromscratch.org/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
Re: [blfs-support] New package: chkconfig
Am Freitag, den 03.04.2020, 10:42 -0400 schrieb Scott Andrews via blfs-support: > Any interest in adding chkconfig to the system V book? > > I have successfully added it to my systems. > > I also have a script that starts and stop daemon and will tell you all > the daemons present on the system and the status running or stopped. > Any interest in that? I think for the SysV guys it might be of interest. Is there a link to the package/script? -- Thomas -- http://lists.linuxfromscratch.org/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-support] Base system What are Yall using?
Am Sonntag, den 23.02.2020, 12:28 -0500 schrieb Scott Andrews via blfs-support: > What packages do most here add to the LFS build to create your "BASE" system? > > I add the following: > > raspberrypi - raspberry pi firmware, kernel add additional boot scripts > > rpm - package manager > > yum - package manager tools > > python2 - needed for yum > > sqlite - needed for yum > > rngd - hardware random generator > > sudo > > make-ca > > logrotate > > ntp > > which > > wget > > dosfstools > > wireless-tools > > wpa_supplicant > > I then add additional packages to the above to create a DNS server, SMTP > server, IMAP server > > When I finish the servers [ 1 master and 1 backup ] I will the build a > desktop machine hopefully using Lumina as a desktop. KDE is too heavy and > GNOME I don't care for. The lightweight desktop won't cut the muster either. > Lumina is QT based with dbus and company. It strongly depends on what the newly built system is meant for. It could be another version of a LFS build server, an infrastructure server (like DHCP, DNS, and friends), a desktop machine... But my machines will all have more or less PKG_BASE=( which pcre popt gpm ed db libtirpc rpcsvc-proto libnsl pam shadow sudo openssh libidn lib32-libidn libunistring lib32-libunistring libidn2 lib32-libidn2 libpsl zip unzip wget ca-certs libtasn1 lib32-libtasn1 nettle lib32-nettle p11-kit lib32-p11-kit gnutls lib32-gnutls dhcpcd rpcbind nfs-utils nfs-client libcap net-ssleay io-socket-ssl mozilla-ca ntp lynx netfs initd-tools sqlite ply bind-client pciutils libusb usbutils traceroute nano run-parts fcron mariadb-client postgresql-client postfix ) and PKG_DEVEL=( icu lib32-icu scons libxml2 libgpg-error libgcrypt libxslt cyrus-sasl libldap lib32-cyrus-sasl lib32-libldap apr apr-util serf subversion sgml-common docbook-xml docbook-xsl docbook-dsssl libarchive libuv curl lib32-curl cmake gcc rsync yasm libpsl gdb gdb-static fpc xmlto llvm ) installed (the lib32-xxx stuff is because i've a multilib environment here). > > This will be all done on the ARM Raspberry Pi platform using 2, 3 and 4 > models. > > After I complete this project I may create a "LFS" and "BLFS" books for the > ARM platform. You might have a look to https://intestinate.com/pilfs/ for LFS on PI. -- Thomas -- http://lists.linuxfromscratch.org/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-support] [lfs-support] Bug in xsltproc [XSL Stylesheet issue (PDF)]
Am Donnerstag, den 21.11.2019, 19:17 +0100 schrieb Thomas Trepl: > Hi again, > > just as a follow-up: > > I asked the Apache/FOP guys about that issue: > > http://mail-archives.apache.org/mod_mbox/xmlgraphics-fop-users/201911.mbox/ajax/%3C4d044e44a7a07fcf688ffda8e8de2724d81a5c4f.camel%40linuxfromscratch.org%3E > > and subsequent answers. > > Looks like it is a bug somewhere in (newer) versions of xsltproc. That > might explain why it still works on higgs. Using saxon6 to create the > .fo file works pretty fine even its way much slower than xsltproc, but > thats not really an issue (at least to me). > > I'll go to file a bug to the xsltproc project (after trying to figure > out with which version of xsltproc the bug came in; hopefully that > testing won't required too much time... > > Btw, added BLFS-Support list since it is not really LFS- but more > BLFS-related. I initially put the thread here as i thought the admins > did some woodoo on higgs in the XSL-stack. > "Kommando zurück!" I just did some test compiler runs on libxslt and it shows following picture: WORKS: 1.1.28 WORKS: 1.1.29 FAIL : 1.1.30 FAIL : 1.1.31 FAIL : 1.1.32 FAIL : 1.1.33 and finally WORKS: 1.1.34 So, there were four releases which did not render correctly. During the test builds I saw that my machine had still 1.1.33 (same on Arch). Looks like that the bug has been fixed in 1.1.34 which is already in the BLFS-book. Sorry for the noise! -- Thomas -- http://lists.linuxfromscratch.org/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
[blfs-support] Bug in xsltproc [XSL Stylesheet issue (PDF)]
Hi again, just as a follow-up: I asked the Apache/FOP guys about that issue: http://mail-archives.apache.org/mod_mbox/xmlgraphics-fop-users/201911.mbox/ajax/%3C4d044e44a7a07fcf688ffda8e8de2724d81a5c4f.camel%40linuxfromscratch.org%3E and subsequent answers. Looks like it is a bug somewhere in (newer) versions of xsltproc. That might explain why it still works on higgs. Using saxon6 to create the .fo file works pretty fine even its way much slower than xsltproc, but thats not really an issue (at least to me). I'll go to file a bug to the xsltproc project (after trying to figure out with which version of xsltproc the bug came in; hopefully that testing won't required too much time... Btw, added BLFS-Support list since it is not really LFS- but more BLFS-related. I initially put the thread here as i thought the admins did some woodoo on higgs in the XSL-stack. -- Thomas -- http://lists.linuxfromscratch.org/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-support] openjdk8 + ant
Am Sonntag, den 27.10.2019, 02:59 + schrieb DJ Lucas via blfs- support: > > On 10/26/2019 5:26 PM, Thomas Trepl via blfs-support wrote: > > Hi all, > > > > i have for some reason to use openjdk8 for which i used the > > instructions just like if would be jdk-12. Java (jdk8) works pretty > > fine so far. > > > > Now i wanted to build ant (as a prerequisite to Tomcat) but failed at > > the > > $ bootstrap/bin/ant -Ddest=optional -f fetch.xml > > command. It reports an error which has something to do with SSL: > > > > ... > > $ bootstrap/bin/ant -Ddest=optional -f fetch.xml > > Buildfile: /home/lfs/apache-ant-1.10.7/fetch.xml > > > > pick-dest: > > [echo] Downloading to /home/lfs/apache-ant-1.10.7/lib/optional > > > > probe-m2: > > > > download-m2: > > [echo] Downloading to /home/lfs/apache-ant-1.10.7/lib/optional > >[get] Getting: > > https://archive.apache.org/dist/maven/ant-tasks/2.1.3/binaries/maven-ant-tasks-2.1.3.jar > >[get] To: /home/lfs/apache-ant-1.10.7/lib/optional/maven-ant- > > tasks-2.1.3.jar > >[get] Error getting > > https://archive.apache.org/dist/maven/ant-tasks/2.1.3/binaries/maven-ant-tasks-2.1.3.jar > > to /home/lfs/apache-ant-1.10.7/lib/optional/maven-ant-tasks-2.1.3.jar > > > > BUILD FAILED > > /home/lfs/apache-ant-1.10.7/get-m2.xml:85: javax.net.ssl.SSLException: > > java.lang.RuntimeException: Unexpected error: > > java.security.InvalidAlgorithmParameterException: the trustAnchors > > parameter must be non-empty > > at sun.security.ssl.Alerts.getSSLException(Alerts.java:208) > > ... > > > > Unfortunatly, i'm a real expert in SSL and certificate stuff so i've > > no clue what to do and where to look, got stuck here. > > Would you mind to point me in a direction to have look? > > > > Btw, its a LFS-9.0 build, make-ca-1.5. > > > > Any ideas on how that could be fixed? Thank you! > > > It's using the wrong invocation of java (might be able to fix it in the > build, but I really don't remember how). It might be as simple as > symlinking /etc/pki/tls/java/cacerts to /opt/jdk/jre/lib/cacerts or > /opt/jdk/lib/cacerts. The first one was it (with using /opt/jdk/jre/lib/*security*/cacerts as target) Thank you DJ! That was easy, oh damn, i'm so lost in ssl/cert space... I once again reviewed my instructions i executed and checked again what happend. Looks like i missed to handle some errors: When doing the binary install, book says to continue with setup and in the "Setting up the Certificate Authority Certificates for Java" section it talks about /etc/ssl/java/cacerts but that file does not exists and make-ca-1.5 seems not creating it. And there is a instruction "ln -sfv /etc/pki/tls/java/cacerts /opt/jdk/lib/security/cacerts" while /opt/jdk/lib/security does not exist. The security directory only exists in jre. Next, "keytool -list -cacerts" results in error "Illegal option: -cacerts" -cacerts seems to not a valid option (at least not in jdk8). > Optionally, you can look at the get-m2.xml file > (or loop through it) and manually download the files and just drop them > into lib/optional/ so that the build script doesn't try to do it for > you. Honestly, the best option is probably to drop back to an earlier > ant version to build Tomcat with JDK-8 . Then export the JDK8 and old > ant environment only in the Tomcat environment (just source the > environment files (not in profile.d) directly from the startup script) - > that way you can use newer java and ant for the rest of the system. Yeah, I'll have a look on that in order to move on to jdk12 later. I have already created a "select-java [8|12]" script which sets the environment per session proper to the selected jdk. -- Thomas -- http://lists.linuxfromscratch.org/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
[blfs-support] openjdk8 + ant
Hi all, i have for some reason to use openjdk8 for which i used the instructions just like if would be jdk-12. Java (jdk8) works pretty fine so far. Now i wanted to build ant (as a prerequisite to Tomcat) but failed at the $ bootstrap/bin/ant -Ddest=optional -f fetch.xml command. It reports an error which has something to do with SSL: ... $ bootstrap/bin/ant -Ddest=optional -f fetch.xml Buildfile: /home/lfs/apache-ant-1.10.7/fetch.xml pick-dest: [echo] Downloading to /home/lfs/apache-ant-1.10.7/lib/optional probe-m2: download-m2: [echo] Downloading to /home/lfs/apache-ant-1.10.7/lib/optional [get] Getting: https://archive.apache.org/dist/maven/ant-tasks/2.1.3/binaries/maven-ant-tasks-2.1.3.jar [get] To: /home/lfs/apache-ant-1.10.7/lib/optional/maven-ant- tasks-2.1.3.jar [get] Error getting https://archive.apache.org/dist/maven/ant-tasks/2.1.3/binaries/maven-ant-tasks-2.1.3.jar to /home/lfs/apache-ant-1.10.7/lib/optional/maven-ant-tasks-2.1.3.jar BUILD FAILED /home/lfs/apache-ant-1.10.7/get-m2.xml:85: javax.net.ssl.SSLException: java.lang.RuntimeException: Unexpected error: java.security.InvalidAlgorithmParameterException: the trustAnchors parameter must be non-empty at sun.security.ssl.Alerts.getSSLException(Alerts.java:208) at sun.security.ssl.SSLSocketImpl.fatal(SSLSocketImpl.java:1959) at sun.security.ssl.SSLSocketImpl.fatal(SSLSocketImpl.java:1916) at sun.security.ssl.SSLSocketImpl.handleException(SSLSocketImpl.java:1899 ) at sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1420) at sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1397) at sun.net. www.protocol.https.HttpsClient.afterConnect(HttpsClient.java:559) at sun.net. www.protocol.https.AbstractDelegateHttpsURLConnection.connect(AbstractDelegateHttpsURLConnection.java:185) at sun.net. www.protocol.https.HttpsURLConnectionImpl.connect(HttpsURLConnectionImpl.java:153) at org.apache.tools.ant.taskdefs.Get$GetThread.openConnection(Get.java:76 6) at org.apache.tools.ant.taskdefs.Get$GetThread.get(Get.java:676) at org.apache.tools.ant.taskdefs.Get$GetThread.run(Get.java:666) ... Unfortunatly, i'm a real expert in SSL and certificate stuff so i've no clue what to do and where to look, got stuck here. Would you mind to point me in a direction to have look? Btw, its a LFS-9.0 build, make-ca-1.5. Any ideas on how that could be fixed? Thank you! -- Thomas -- http://lists.linuxfromscratch.org/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-support] LFS 8.4 rc
Am Samstag, den 16.02.2019, 15:18 +0100 schrieb Gerhard Gedigk via blfs-support: > Hello, > > please correct the example for the German console fonts. (7.6.5) > > KEYMAP="de-latin1" # is correct > > FONT="lat0 ... needs to be changed to lat1 as well. > This is needed to display the special characters for the German language > correctly. > > Thank you > Gerhard I have - # Begin /etc/sysconfig/console UNICODE="1" KEYMAP="de-latin1" KEYMAP_CORRECTIONS="euro2" #FONT="lat0-16 -m 8859-15" FONT="Lat2-Terminus16 -m 8859-15" # End /etc/sysconfig/console - in my /etc/sysconfig/console. Note the UNICODE="1". With this, lat0-16 works fine, while my favorite font is the Terminus. Would you try it with UNICODE=1 again and tell the result? Btw, thats something for LFS-support, not BLFS-support. Lets continue talking there. -- Thomas -- http://lists.linuxfromscratch.org/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-support] twm menu not working
Am Freitag, den 08.02.2019, 16:37 +0100 schrieb Cliff McDiarmid via blfs-support: > lHi > > I'm building a new LFS. I've got to the Xorg testing and I'm booting into > the three windows and clock. I haven't got a left click twm menu though. > So i can't move the windwos etc. > > Have googled this problem with no luck. Any ideas? > > thanks > Cliff Try to unset any environment vars like LANG and LC_xxx etc. Than export LANG=C Maybe there is an issue with charset, it helped me a time ago. -- Thomas -- http://lists.linuxfromscratch.org/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-support] twm and xinit?
Am Montag, den 03.12.2018, 04:40 + schrieb Hans Malissa via blfs- support: > Hi, > > I'm in section "Xorg-7 Testing and Configuration" in BLFS 8.3-systemd. Xorg > seems to work, and when I issue startx I get the Xorg desktop with 3 xterm > windows and 1 xclock window. However, the windows have no frames, and cannot > be moved or resized. I remember twm differently, and I'm wondering if it's > supposed to be like this, or if something is wrong with twm? Is this the > default behavior, just windows that have no frames, and cannot be moved or > resized? > Thanks a lot, > > Hans Wasn't there something with character sets? Try playing with locales. -- Thomas -- http://lists.linuxfromscratch.org/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-support] php-7.2.9, strange directories after make install
Am Montag, den 10.09.2018, 19:12 +0200 schrieb Thomas Trepl via blfs- support: > Am Montag, den 10.09.2018, 09:41 -0400 schrieb Jean-Marc Pigeon via > blfs-support: > > Hello, > > > > http://www.linuxfromscratch.org/blfs/view/svn/general/php.html > > Version 2018-09-08 > > Here is a list of directories which I think are > > unexpected after a "make install". > > > > /.channels/.alias/pear.txt > > /.channels/.alias/pecl.txt > > /.channels/.alias/phpdocs.txt > > /.channels/__uri.reg > > /.channels/doc.php.net.reg > > /.channels/pear.php.net.reg > > /.channels/pecl.php.net.reg > > /.depdb > > /.depdblock > > /.filemap > > /.lock > > /usr/lib/php/.channels/.alias/pear.txt > > /usr/lib/php/.channels/.alias/pecl.txt > > /usr/lib/php/.channels/.alias/phpdocs.txt > > /usr/lib/php/.channels/__uri.reg > > /usr/lib/php/.channels/doc.php.net.reg > > /usr/lib/php/.channels/pear.php.net.reg > > /usr/lib/php/.channels/pecl.php.net.reg > > /usr/lib/php/.filemap > > /usr/lib/php/.lock > > /usr/lib/php/.registry/archive_tar.reg > > /usr/lib/php/.registry/console_getopt.reg > > /usr/lib/php/.registry/pear.reg > > /usr/lib/php/.registry/structures_graph.reg > > /usr/lib/php/.registry/xml_util.reg > > > > > > Installing something at root level '/' is rather strange. > > > > It is the first time I compiled PHP within LFS (LFS-8.3) so > > I can not say if LFS-8.2+PHP have those file too. > > > > Could other BLFS users confirm have those php directories/files? > > Can we delete those files without problem? (my guess: yes). > > Do we need to adjust the configure options list in book? > > Indeed, strange thing - the files and the fact that I've not seen > them > while updating. > > Let's have a look where those files come from and if we can configure > them away. Looks like adding "--without-pear" does the trick but what else does that switch imply? -- Thomas -- http://lists.linuxfromscratch.org/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-support] php-7.2.9, strange directories after make install
Am Montag, den 10.09.2018, 09:41 -0400 schrieb Jean-Marc Pigeon via blfs-support: > Hello, > > http://www.linuxfromscratch.org/blfs/view/svn/general/php.html > Version 2018-09-08 > Here is a list of directories which I think are > unexpected after a "make install". > > /.channels/.alias/pear.txt > /.channels/.alias/pecl.txt > /.channels/.alias/phpdocs.txt > /.channels/__uri.reg > /.channels/doc.php.net.reg > /.channels/pear.php.net.reg > /.channels/pecl.php.net.reg > /.depdb > /.depdblock > /.filemap > /.lock > /usr/lib/php/.channels/.alias/pear.txt > /usr/lib/php/.channels/.alias/pecl.txt > /usr/lib/php/.channels/.alias/phpdocs.txt > /usr/lib/php/.channels/__uri.reg > /usr/lib/php/.channels/doc.php.net.reg > /usr/lib/php/.channels/pear.php.net.reg > /usr/lib/php/.channels/pecl.php.net.reg > /usr/lib/php/.filemap > /usr/lib/php/.lock > /usr/lib/php/.registry/archive_tar.reg > /usr/lib/php/.registry/console_getopt.reg > /usr/lib/php/.registry/pear.reg > /usr/lib/php/.registry/structures_graph.reg > /usr/lib/php/.registry/xml_util.reg > > > Installing something at root level '/' is rather strange. > > It is the first time I compiled PHP within LFS (LFS-8.3) so > I can not say if LFS-8.2+PHP have those file too. > > Could other BLFS users confirm have those php directories/files? > Can we delete those files without problem? (my guess: yes). > Do we need to adjust the configure options list in book? Indeed, strange thing - the files and the fact that I've not seen them while updating. Let's have a look where those files come from and if we can configure them away. -- Thomas -- http://lists.linuxfromscratch.org/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-support] Common post install commands
Am Samstag, den 01.09.2018, 00:34 +0100 schrieb Ken Moffat via blfs- support: > On Fri, Aug 31, 2018 at 11:52:42PM +0200, Thomas Trepl via blfs- > support wrote: > > > > More generally spoken, the DESTDIR-method is pretty fine as long as > > you > > take in account that sometimes the sequence of the instructions > > needs > > to be changed. I assume you do DESTDIR to provide binary packages > > for > > other machines than the building machine - which is IMHO the only > > reason DESTDIR makes sense. > > Not at all: it lets you see exactly what is going to be installed. > e.g. When building a new package, or new version: > > Does a package really need --disable-static, or are no static libs > installed ? > > How much space does the install take ? > Totally agree from an editor's point of view. My scripts do report those data automatically - its exactly this method where they get the data from. > Of course, not all packages support DESTDIR, some Python modules and > Qt packages need a different magic word. Also one or two others, > and sometmes you still need to be root to run it. > > Some editors document these things in the xml, which is only handy > when you come to make the edit : by that point I (hope to) know what > I'm going to put in the book. When I remember, I usually put these > things in the wiki. For Python modules using setup.py, --root > /some/dir usually works. It would be great if the book could show a little marker, a little green button or so, at the wiki-link if there is really a page existing. I think this could help to get the wiki more in mind but it would mean to access tracs database while rendering the book. Don't know if xsltproc supports calling external functions. -- Thomas -- http://lists.linuxfromscratch.org/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-support] Common post install commands
Am Freitag, den 31.08.2018, 23:06 +0300 schrieb Waleed Hamra via blfs- support: > Greetings guys; > > What are some common post install commands I should know about? > For instance, I know that if a package installs a .desktop file, I > should run "update-desktop-database" to update the cache. For some > programs there's gtk-update-icon-cache, though I don't really know > when > I need to run that, I just run after every gtk package. > > I had some problems with akonadi earlier, and after some debugging, > I > noticed it outputting something about some mail mime types being > invalid, so I ran update-mime-database, and that solved it. > > Anything else I should be aware about? I ask since everything is > installed using a DESTDIR method, so if make install is expected to > fix > some of this stuff, it's not. > > Thanks a lot for any pointers. > > Waleed Hamra You allready found the two most used tools to run. After installing fonts, you may think about "fc-cache". 'info -d ' maybe another one. Ken mentioned ldconfig for each package which does something with libraries. More generally spoken, the DESTDIR-method is pretty fine as long as you take in account that sometimes the sequence of the instructions needs to be changed. I assume you do DESTDIR to provide binary packages for other machines than the building machine - which is IMHO the only reason DESTDIR makes sense. For instance, when building a daemon, the first instructions are to create some user/groups (e.g. apache for httpd or postfix/postdrop for postfix, etc). The users are most of the time not required for build time (one exception is fcron), it is required when you do the install of the DESTDIR-binary. So in this case, build postgres on machine A, tar it up, unpack it on B and create the user/group on B (plus doing some chown+chmod) and run the initdb stuff (what if a database is allready there?). For user/groups its obvious, failures to create them are reported mostly very quick. It becomes a bit more tricky when it comes to special file-/directory-permissions. All that stuff needs to be done on the target machine (B) - so at a very different time. And watch out for configuration files which might exist on B allready. Don't overwrite them, work changes into them. -- Thomas -- http://lists.linuxfromscratch.org/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-support] logrotate sed missing -i
Am Sonntag, den 19.08.2018, 03:29 +0300 schrieb Waleed Hamra: > Greetings guys; > > On this page: > http://www.linuxfromscratch.org/blfs/view/systemd/general/logrotate.html > > , the second sed is missing the -i parameter. > Good catch - will fix that. -- Thomas -- http://lists.linuxfromscratch.org/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-support] [blfs-dev] BLFS-Basic
Am Freitag, den 13.07.2018, 11:17 -0500 schrieb Bruce Dubbs: > On 07/13/2018 04:08 AM, thomas wrote: > > Am 2018-07-09 22:08, schrieb Bruce Dubbs: > > > ... > > > In addition, upstream changes are released often. The average is > > > about 3.5 packages every day, seven days a week. > > > ... > > > To address this, I am proposing to split BLFS into two (or > > > possibly > > > more) books. My tentative names are BLFS-Basic and BLFS- > > > Advanced. > > > BLFS-Basic is primarily command line tools and programs plus the > > > basic > > > Xorg section of BLFS. This would be updated regularly and a > > > 'stable' > > > version released every six months with the LFS book. > > > > Just a thought: > > > > What if we would use only *stable* versions of packages in the > > BLFS-*Stable* book? > > All of BLFS tries to use only stable releases now. There are some > exceptions when a package uses a development library release, but > it's rare. > > > Ok, the book would than be not so bleeding-edge (but rock-solid i > > assume). This would reduce the amount of updates we would have to > > make > > in order to keep it on the very recent status. For example, bind > > (DNS-server) had two tickets to upgrade to 9.13.1 and a few days > > later > > to 9.13.2. Two tickets which may simply drop out if stable-book > > stick on > > stable version 9.12.2. > > Why do you think bind-9.13 is a development release? If it is and > I've > missed it, I need to update the currency scripts to reflect that. Go to https://www.isc.org/downloads/ and open the dropdown-box for "bind". The list will state 9.13.2 as unstable/development in red letters, 9.12.2 as current-stable in green. > > The problem here is that different packages use different methods to > designate development releases. Some use even/odd minor > versions. Some > use -RCx or -dev, some use minor or point version numbers >= 80 or > 90. > This list is not exhaustive. > > Add to that that some developers do not bother to do development > releases. Sometimes we see three 'stable' releases in a week. Yeah, all that happens, too :-) -- Thomas -- http://lists.linuxfromscratch.org/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-support] [blfs-dev] BLFS-Basic
Am Montag, den 09.07.2018, 15:08 -0500 schrieb Bruce Dubbs: > As most of you know, BLFS is huge. If it is printed on paper, it > would > take over 2000 pages. There are over a thousand individual packages > in > the book. Wow, never seen that in this way... > In addition, upstream changes are released often. The average is > about > 3.5 packages every day, seven days a week. > > Since LFS/BLFS contributions are done completely by volunteers, the > upstream change rate is overwhelming our ability to keep up to date. > The problem is not LFS. That is doable. The problem is the size > and > change rate of BLFS. Yes, its a huge amount of work which is to be done to keep all those packages up-to-date. Moreover, not only keeping them up-to-date in terms of using the most current version, it's the review of the instructions all the time, checking for new config options, the check of interoperability with other packets and so on - not just dropping in a new version number and updating the md5 chksum. > To address this, I am proposing to split BLFS into two (or possibly > more) books. Yes, divide into two (or more) "physically" different books. They could be maintained and tagged independently. The maintenance than could be organized in svn-branches on those books. ---> [BLFS-8.2] ---> stable Basic BLFS-8.2 ---> [BLFS-8.3] ---> |^ ^ || | | Security patches / Bugfixes | for rls merge |^ | dev-8.3 to HEAD || | +-> Devel for next rls (dev-8.3) ---+ The devel-branch could be merged more than just one time if required to the HEAD, just creating a BLFS-Basic-8.2.x release. Just a thought... > My tentative names are BLFS-Basic and BLFS-Advanced. > BLFS-Basic is primarily command line tools and programs plus the > basic > Xorg section of BLFS. This would be updated regularly and a > 'stable' > version released every six months with the LFS book. The BLFS- > Advanced > book will be a 'rolling release'. We did this with BLFS between LFS > versions 6.3 and 7.4 (August 2008 until September 2014). A pretty cool idea. One question i have is: Would BLFS-Basic have impact on the release of a new LFS-version. When releasing a new LFS, the BLFS-Basic should be available in time also. > With a rolling release, there is less consistency and a > comprehensive > check against the current stable LFS is not done. Packages would be > frequently out of date. ... which is IMHO no problem at all if accepted that this may not address security issues in a proper way and such. xLFS is primarily for teaching how stuff works by showing instructions with which something can be built without using esotheric stuff like packetmanagers (while everyone of us has built his/her own one, isn't it?). xLFS never had the aim to be a full-featured distro. I see issues with linking from one book to the other, but with clever xml-entities we should come over it, right? The impact on jhALFS is unknown to me as i use my own pkgmngr - so no idea about this. > For BLFS-Basic I am attaching a straw man for the contents. I > anticipate that an experienced LFS builder could complete all the > packages in BLFS-Basic in a day or two. > > I am now looking for feedback. Are there other solutions? Is my > list > for BLFS-Basic too large? Is there something missing? Maybe check the list for packages like "at" or "(f)cron" which are called to be a requirement for LSB compliance. Add the minimum toolset to be able to rebuild the LFS/BLFS-Basic book. To much WMs. Just FluxBox (or one of the others) would be enough. All in all, it would be an interesting project in the xLFS hemisphere! -- Thomas -- http://lists.linuxfromscratch.org/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-support] qt5 without openssl really is a bad idea. Was Re: Make problems with Qt-5 on BLFS-8.1
Am Sonntag, den 03.12.2017, 23:40 + schrieb Ken Moffat: > On Mon, Nov 27, 2017 at 10:49:31PM +, Ken Moffat wrote: > > > > The idea of disabling (old) openssl in qt has attractions, I might > > give it a try - but the only qt progs I usually build are qupzilla > > (uses qtwebengine) and vlc. > > > > But qupzilla fails to build - > error: invalid use of incomplete type 'const class QSslCertificate' > which seems pretty conclusive, so I'm adding openssl-1.0.2 and > rebuilding qt5. > > Another case of "don't try this at home" ;-p > I did - with qt-5.10.0. Seems to work. qt5-5.10 does not compile with openssl-1.0 but fine with 1.1. QupZilla also does. -- Thomas -- http://lists.linuxfromscratch.org/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-support] raid array is read-only
Ken, you are my hero! See comments below: Am Freitag, den 24.11.2017, 01:35 + schrieb Ken Moffat: > On Thu, Nov 23, 2017 at 09:53:57PM +0100, Thomas Trepl wrote: > > Hi all, > > > > there is a problem as my raid device is read-only so > > /etc/rc.d/init.d/checkfs fails. > > > > The machine is built on the C236 chipset and I have enabled raid5. > > There are 3 1TB disks combined to an raid-5 array. > > The partiton type is gpt, grub+EFI installed on /boot. the > > partition > > layout is > > > > /dev/md126p1 /boot > > /dev/md126p2 swap > > /dev/md126p3 / (ArchLinux) > > /dev/md126p4 / (LFS-1) > > /dev/md126p5 / (LFS-2) > > /dev/md126p6 /home > > /dev/md126p7 /srv > > /dev/md126p8 /data > > > > I have no experience of RAID5, nor of making partitions within RAID > devices, and I was initially surprised to see such as high-numbered > device (126), but I suspect that is an Arch thing. From what I've > no written below, maybe DM Raid ? Thats a raid thing, Arch as well as LFS uses this device names. > But the usual question to ask when something stops working is: what > has changed since it was last working ? I'm assuming you've had > this working in both Arch and LFS, but I start to think this might > be a new setup ? It's a brand new machine, there was nothing before on it. I've installed Arch to "bootstrap". > > Arch is booting quite well. I've taken Arch's kernel config, built > > the > > kernel for LFS with this config, created an initramfs using BLFS's > > mkinitramfs script. > > If you are able to get into LFS, e.g. from chroot, I would try > rebuilding the kernel using 'Y' for any DM options, and for the > required MD options. I've only used RAID1 on LFS, and not for the > /boot or / devices, so no idea if that setup works in current LFS. Well, yes, that will be an option. The question i try to find an answer to is: Whats the difference between Arch and LFS as both using same kernel config, both booting using a initramfs. There must be something in the LFS setup which makes the device RO which is not the case in Arch. > > > I found that the mkinitramfs script misses "readlink" and > > "basename" > > which are called somewhere within udev. A patch for that see below. > > The > > patch eliminates some error mesages in early boot stage, but > > changed > > nothing of the ro-issue. > > > > I found systemd stuff in the udev rules dealing with mdraid. > > Unfortunatly, I'm not used enough to udev rules to say whether this > > may > > be something to think about. ArchLinux does use systemd, I'm > > building > > stricktly non-systemd systems. Those udev rules are > > > > ./lib/udev/rules.d/63-md-raid-arrays.rules and > > ./lib/udev/rules.d/64-md-raid-assembly.rules > > > > Any ideas what could be the reason why devices are read-only? > > > > From an Arch forum at https://bbs.archlinux.org/viewtopic.php?id=1370 > 58 > (summarised) > > > mdadm --readwrite /dev/md126 reports no errors, but md126 remain > > read only > > > > However, after: > > mdadm --stop /dev/md126 > > sudo mdadm --assemble --scan > > It worked, and mountable for write > > > > But after reboot it became r/o again > > The only things I really got from that are: > > · you might be using DM raid ? > > · the initcpio needed /sbin/mdmon added to it This seems to be the answer to the question above. In the BLFS mkinitramfs script, only mdadm and udevd are copied. I added mdmon to that list, rebooted and - tadadada - the device is mounted RW :-) I'm pretty sure to have seen that archforum-thread also, but somehow the mdmon thing didn't manage to get into my brain. Your explicit question about mdmon did the trick ;-) > > But maybe the things in that conversation will mean more to you than > to me. Beyond that, do you have the same /etc/mdadm.conf in Arch > and LFS, and can you get any useful output from mdadm or mdmon (or > dmesg) ? Unfortunatly there is nothing. I tweaked checkfs in the way that it will not halt the system to be able to have look to dmesg, but there is nothing valuable in it for this case. > ĸen > -- > Truth, in front of her huge walk-in wardrobe, selected black leather > boots with stiletto heels for such a barefaced truth. > - Unseen Academicals Thanks Ken, its often the small things which makes bigger things work. I'll prepare a little patch for mkinitramfs and put it here again (or better in a ticket) for further discussion before i update the book. -- Thomas -- http://lists.linuxfromscratch.org/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
[blfs-support] raid array is read-only
Hi all,
there is a problem as my raid device is read-only so
/etc/rc.d/init.d/checkfs fails.
The machine is built on the C236 chipset and I have enabled raid5.
There are 3 1TB disks combined to an raid-5 array.
The partiton type is gpt, grub+EFI installed on /boot. the partition
layout is
/dev/md126p1 /boot
/dev/md126p2 swap
/dev/md126p3 / (ArchLinux)
/dev/md126p4 / (LFS-1)
/dev/md126p5 / (LFS-2)
/dev/md126p6 /home
/dev/md126p7 /srv
/dev/md126p8 /data
Arch is booting quite well. I've taken Arch's kernel config, built the
kernel for LFS with this config, created an initramfs using BLFS's
mkinitramfs script.
I found that the mkinitramfs script misses "readlink" and "basename"
which are called somewhere within udev. A patch for that see below. The
patch eliminates some error mesages in early boot stage, but changed
nothing of the ro-issue.
I found systemd stuff in the udev rules dealing with mdraid.
Unfortunatly, I'm not used enough to udev rules to say whether this may
be something to think about. ArchLinux does use systemd, I'm building
stricktly non-systemd systems. Those udev rules are
./lib/udev/rules.d/63-md-raid-arrays.rules and
./lib/udev/rules.d/64-md-raid-assembly.rules
Any ideas what could be the reason why devices are read-only?
--
Thomas
Index: trunk/autolfs/files/mkinitramfs
===
--- trunk/autolfs/files/mkinitramfs (Revision 665)
+++ trunk/autolfs/files/mkinitramfs (Arbeitskopie)
@@ -38,6 +38,8 @@
binfiles="sh cat cp dd killall ls mkdir mknod mount "
binfiles="$binfiles umount sed sleep ln rm uname"
+ubinfiles="readlink basename dirname"
+
sbinfiles="udevadm modprobe blkid switch_root"
#Optional files and locations
@@ -55,6 +57,7 @@
# Create base directory structure
mkdir -p $WDIR/{bin,dev,lib/firmware,run,sbin,sys,proc}
+mkdir -p $WDIR/usr/bin
mkdir -p $WDIR/etc/{modprobe.d,udev/rules.d}
touch $WDIR/etc/modprobe.d/modprobe.conf
ln -s lib $WDIR/lib64
@@ -104,6 +107,11 @@
copy $f sbin
done
+for f in $ubinfiles ; do
+ ldd /usr/bin/$f | sed "s/\t//" | cut -d " " -f1 >> $unsorted
+ copy /usr/bin/$f usr/bin
+done
+
# Add udevd libraries if not in /sbin
if [ -x /lib/udev/udevd ] ; then
ldd /lib/udev/udevd | sed "s/\t//" | cut -d " " -f1 >> $unsorted
--
http://lists.linuxfromscratch.org/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
Re: [blfs-support] Error in xorg-fonts
Am Dienstag, den 20.09.2016, 15:24 +1000 schrieb Samuel Tyler:
>
>
> On Tuesday, 20 September 2016, Thomas Trepl <thomas@linuxfromscratch.
> org> wrote:
> > Hi all,
> >
> > I got following message while installing the Xorg fonts:
> >
> > ...
> > checking for memory.h... yes
> > checking for strings.h... yes
> > checking for inttypes.h... yes
> > checking for stdint.h... yes
> > checking for unistd.h... yes
> > checking for pkg-config... /usr/bin/pkg-config
> > checking pkg-config is at least version 0.9.0... yes
> > checking build system type... x86_64-unknown-linux-gnu
> > checking host system type... x86_64-unknown-linux-gnu
> > checking for a sed that does not truncate output... /bin/sed
> > checking for root directory for font files... Package fontutil was
> > not
> > found in
> > the pkg-config search path.
> > Perhaps you should add the directory containing `fontutil.pc'
> > to the PKG_CONFIG_PATH environment variable
> > No package 'fontutil' found
> > ${datarootdir}/fonts/X11
> > checking for directory for 100dpi files... ${FONTROOTDIR}/100dpi
> > checking for fc-cache... /usr/bin/fc-cache
> > checking for mkfontdir... /usr/X11/bin/mkfontdir
> > checking for bdftopcf... /usr/X11/bin/bdftopcf
> > checking font compression method... gzip
> > checking for gzip... /bin/gzip
> > checking for ucs2any... no
> > configure: error: ucs2any is required to build font-adobe-100dpi.
> >
> > Any ideas what happened here? Neither ucs2any nor fontutil are in
> > the
> > book, so i wonder why this hard dependency comes up here.
> >
> > --
> > Thomas
> > --
> > http://lists.linuxfromscratch.org/listinfo/blfs-support
> > FAQ: http://www.linuxfromscratch.org/blfs/faq.html
> > Unsubscribe: See the above information page
> >
>
> I assume you are using BLFS 7.10? Are fontutil or ucs2any related?
>
Yes, it's based on LFS-7.10, BLFS is the development branch (which is
not far ahead of BLFS-7.10).
--
http://lists.linuxfromscratch.org/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
[blfs-support] Error in xorg-fonts
Hi all,
I got following message while installing the Xorg fonts:
...
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking for pkg-config... /usr/bin/pkg-config
checking pkg-config is at least version 0.9.0... yes
checking build system type... x86_64-unknown-linux-gnu
checking host system type... x86_64-unknown-linux-gnu
checking for a sed that does not truncate output... /bin/sed
checking for root directory for font files... Package fontutil was not
found in
the pkg-config search path.
Perhaps you should add the directory containing `fontutil.pc'
to the PKG_CONFIG_PATH environment variable
No package 'fontutil' found
${datarootdir}/fonts/X11
checking for directory for 100dpi files... ${FONTROOTDIR}/100dpi
checking for fc-cache... /usr/bin/fc-cache
checking for mkfontdir... /usr/X11/bin/mkfontdir
checking for bdftopcf... /usr/X11/bin/bdftopcf
checking font compression method... gzip
checking for gzip... /bin/gzip
checking for ucs2any... no
configure: error: ucs2any is required to build font-adobe-100dpi.
Any ideas what happened here? Neither ucs2any nor fontutil are in the
book, so i wonder why this hard dependency comes up here.
--
Thomas
--
http://lists.linuxfromscratch.org/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
