Re: Auto mounting USB thumb drives and CD/DVD
On Sat, Apr 10, 2010 at 12:05 PM, Baho Utot baho-u...@columbus.rr.com wrote: What do I need to enable regular users to auto mount DVD/CD and USB drives? I agree with Randy. This is easily found if one searches. Most of your questions do appear to indicate you are just asking questions without looking for the answer first. I have HAL installed. Do I need any other packages? I would like CD/DVD/USB drives when inserted to automount like my slackware 12.2 does. An Icon apperars and it opens a konqueror file manager window. And this one is found in the same place as the first question. A little hint to your first two questions. Look in /etc there is one file that will solve the whole thing. It has to be set up correctly with another one in another directory for a proper boot. The book does touch on the file you need to modify but it does not tell you everything about how to configure it. I have heard that HAL is going away. udev seems to work well in place of HAL. I do not know what the overall Linux community is planning with its planned replacement for HAL. -- If we can but prevent the government from wasting the labours of the people, under the pretence of taking care of them, they must become happy. - Thomas Jefferson -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: Fonts
On Sat, Apr 10, 2010 at 2:55 PM, linux fan linuxscra...@gmail.com wrote: On 4/10/10, William Immendorf will.immend...@gmail.com wrote: On Sat, Apr 10, 2010 at 12:19 PM, linux fan linuxscra...@gmail.com wrote: I unpack bitstream-vera fonts http://ftp.gnome.org/pub/GNOME/sources/ttf-bitstream-vera/1.10/ttf-bitstream-vera-1.10.tar.bz2 [snip] Even better would be the DejaVu fonts, which are basically the Bitstream Vera fonts but they also cover Cyrillic and Greek as well. That is what they say. Maybe my perception is defective, but the Bitstream Vera fonts look better to me. If you apply the Bit stream to one sentence and the DejaVu to another sentence and compare them at the same time you will see they are identical. -- If we can but prevent the government from wasting the labours of the people, under the pretence of taking care of them, they must become happy. - Thomas Jefferson -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: Auto mounting USB thumb drives and CD/DVD
On Sat, Apr 10, 2010 at 12:05 PM, Baho Utot baho-u...@columbus.rr.com wrote: What do I need to enable regular users to auto mount DVD/CD and USB drives? I have HAL installed. Do I need any other packages? I would like CD/DVD/USB drives when inserted to automount like my slackware 12.2 does. An Icon apperars and it opens a konqueror file manager window. In my other post I was referring to /etc/fstab Do you have your CDROM set up similar to this? The key piece is user. /dev/cdrom/mnt/cdrom auto noauto,ro,user0 0 and is your user part of the CDROM group? Instructions on how to do this is found with Google. There are a lot of sites with a lot more information about this. If you want to find a problem start at the beginning and work your way to the end. -- If we can but prevent the government from wasting the labours of the people, under the pretence of taking care of them, they must become happy. - Thomas Jefferson -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: help with-kde442.polkit-kde
On Thu, Apr 8, 2010 at 6:02 PM, Thomas Trepl tho...@equinox.homelinux.org wrote: Hi, the kde4-config should appear in $KDEDIR/bin/ I made a symlink in /usr/bin/ to it for convenience (my $KDEDIR is /opt/kde4). Q1: Must be a very early package Q2: Dont think so. What questions are you talking about? Oh I know, the ones way down in the mess below your reply. Don't top post. The requirements on these lists tells you plainly not to top post. Read the FAQ on the LFS site if you don't know what that means. Greetings, I am having a go at compiling kde-4.4.2 on a blfs (64-bit only). I am now trying to install polkit-kde-1-0.95.1 (http://lists.kde.org/?l=kde-develm=126157604310306w=2). My cmake instruction is as follows:- cmake -G Unix Makefiles $SOURCES/polkit-kde-1-0.95.1 \ -DCMAKE_INSTALL_PREFIX=$KDEDIR -DSYSCONF_INSTALL_DIR=/etc/kde \ -DKDE4_AUTH_POLICY_FILES_INSTALL_DIR:STRING=/usr/share/PolicyKit/policy \ -DENABLE_FAM=ON -DENABLE_EXPAT=ON -DENABLE_INOTIFY=ON \ -DGAIM_LIBS:STRING=/usr/lib -DGAMIN_LIBRARIES:STRING=/usr/lib ## output from running the above ### -- Detecting CXX compiler ABI info - done CMake Error at /usr/local/share/cmake-2.8/Modules/FindKDE4.cmake:58 (MESSAGE): ERROR: Could not find KDE4 kde4-config Call Stack (most recent call first): CMakeLists.txt:5 (find_package) ### I have two questions: QUESTION 1: Which is KDE-program that installs the needed kde4-config ? QUESTION 2: my $KDEDIR is not /usr, is is sensible to change -DKDE4_AUTH_POLICY_FILES_INSTALL_DIR:STRING=/usr/share/PolicyKit/policy \ to -DKDE4_AUTH_POLICY_FILES_INSTALL_DIR:STRING=$KDEDIR/share/PolicyKit/policy \ in the cmake instruction above? suggestions welcomed lux-integ -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page -- If we can but prevent the government from wasting the labours of the people, under the pretence of taking care of them, they must become happy. - Thomas Jefferson -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: libdrm and xorg-server
On Tue, Apr 6, 2010 at 9:30 AM, rhubarb...@poetworld.net wrote: I'm receiving No package 'libdrm' found while compiling X on LFS 6.6 using the development BLFS instructions. However, my .configure includes --disable-glx and --disable-dri. The development instructions refer to LFS 6.5 and I am building on 6.6, which I assume can be done. I'm running matched LFS BLFS 6.3 so I have successfully compiled X, but I'm apparently missing something here. ? It appears that you said you are building LFS 6.6 and BLFS 6.3 on top of it. If that is correct that is your problem. If you are Building LFS 6.6 you should be building BLFS using the svn version. BLFS svn is compatible with LFS 6.6. BLFS 6.3 is not compatible and will give you trouble. -- If we can but prevent the government from wasting the labours of the people, under the pretence of taking care of them, they must become happy. - Thomas Jefferson -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: Qt-3.3.8b
On Thu, Mar 25, 2010 at 8:32 PM, Baho Utot baho-u...@columbus.rr.com wrote: I get the following from configuration What is PCH support? Google is your friend! -- If we can but prevent the government from wasting the labours of the people, under the pretence of taking care of them, they must become happy. - Thomas Jefferson -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: Linuz-PAM-1.1.1
I pointed this out on 12/31/09 http://search.gmane.org/search.php?group=gmane.linux.lfs.beyond.supportquery=Linux-PAM+step+question+BLFS+svn+latest -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: gpm
On Sat, Feb 20, 2010 at 9:37 AM, Carl Thorn thor...@yahoo.com wrote: I compiled gpm-1.20.6 before reading the hint in the svn version of the book. I am using LFS 6.6rc. I was wondering whether the hint still applies to the newer versions as it was last updated in 2006. I can't seem to get the mouse to work. The hint says I should recompile gpm using --without curses and then recompiling ncurses. It also says that gpm won't work with UTF8. This is my second attempt with BLFS. The first time I was using LFS 6.1 supplied with the livecd and BLFS 6.3. The mouse worked as soon as it was compiled in that version. I built gpm-1.20.6 on LFS6.5 without reading any hint. I did not have to mess with curses/ncurses. Did you run the boot script and did you get your /etc/sysconfig/mouse file configured properly? -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: blfs-support Digest, Vol 1970, Issue 1
On Fri, Feb 19, 2010 at 2:49 AM, Dale Stein dstein2...@gmail.com wrote: ok thanks, I will be waiting for the update. No hurry mind you! I just love what you guys are doing and have always read the posts with interest. Stop top posting. Trim and bottom post. Don't send all that garbage from the digest. -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: BLFS libxcb-1.4 configure error cmd terminated
On Wed, Feb 17, 2010 at 5:23 AM, Simon Geard delga...@ihug.co.nz wrote: On Tue, 2010-02-16 at 02:07 -0500, stosss wrote: I looked back through the book and see that libxslt is listed as required in libxcb. I was tired and must have missed it. But I saw it and built it under xmlto. oh well, sorry for the noise. Fair enough... I am going to build LFS/BLFS several more times. Each time I do I learn more. I already built LFS to completion one other time and partially built some of BLFS. This is my sceond time with BLFS and I went farther this time and I have learned more. I am building it as a VM this time instead of using one of my boxes. As you get comfortable with building things manually, consider automating parts, or all of it, as you go. Partly for the time saved on updating a system, but as much for what you learn about scripting (shell or otherwise) to achieve it. I have already been building a lot of it with simple bash scripts. I basically copy all the commands for a package into a pair of script and run them. One for the regular user and one for root. That is what I did with LFS chapter 2 - 9. Right now I am trying to figure out why some of the packages in chapter 23 in BLFS won't build. If I can't figure it out I will post a new thread with details. -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: BLFS-6.4RC1 or any
On Tue, Feb 16, 2010 at 4:46 PM, Chris Staub ch...@beaker67.com wrote: On 02/16/2010 03:18 PM, stosss wrote: I don't like the moving target either, but I have seen that it does not change all that much. Some times there are no changes for several days. Even if there are changes every day they might not be changes in the package version but changes in the text with no changes to packages. Some times the packages that change are ones that you haven't even gotten to yet or have no intention of installing. I switched from the 02-03-2010 to 02-15-2010 and found openssl, CA bundle, and wget had changed which I had already installed. I ran the changes and the system still works, nothing broke. I also saw that unzip had changed, no problem because I was about to install unzip. I installed the new one. Those were the only changes that effected my build with no adverse consequence. The key to the moving target is the change log has to be up-to-date and correct so you can see what changed. I am not saying its not. This is why I would really like to see the book devs go to posting a snapshot only when there has been a change to the book. If the snapshot was only posted when changes happen then you would only need to check the site every night to see if you do need to download the new version. Book devs I am not complaining. I am making a suggestion and this is not an unrealistic suggestion. It would be very useful to everyone and would not have any impact on the book. Generally, the date in the book is updated anytime there is any change at all. Some changes to the book are minor enough that there doesn't need to be a Changelog entry (such as a simple typo fix), but the date is updated anyway because the book has changed. Generally, anything that is significant enough to potentially require rebuilding something *will* be mentioned in the Changelog. There was about 7 to 9 days or so in the first half of this month that the date of the book did not change but there was a nightly snapshot any way. This is what I am talking about. If there are no significant changes like instructions or packages, then there would be no reason to change the book date and no reason to post a snapshot. Again I am not complaining just pointing out that this could be cleaned up to make it easier for everyone. If the book has an updated date and no Changelog entry for that day, just check the svn log to see what was committed. What is the URL for the svn log? -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: BLFS-6.4RC1 or any
On Tue, Feb 16, 2010 at 6:49 PM, Randy McMurchy ra...@linuxfromscratch.org wrote: stosss wrote these words on 02/16/10 14:18 CST: This is why I would really like to see the book devs go to posting a snapshot only when there has been a change to the book. You are making a mountain from a molehill. If you are so worried if there has been changes, just look at the daily rendered HTML development version of BLFS and then look at the ChangeLog. It really isn't that hard. No, but you are putting up a lot of stubborn resistance to my suggestion. When people are stubborn to accepting change then the progress that could come is impeded. Those resisting change say that the LFS/BLFS project has been around for about 10 years as proof that the project is doing something right. That is only proof that the project has been around for a while and maybe the project would be more fine tuned by now if there had not been that stubborn resistance to finding better ways to do things. You complain that you don't have enough help, but when help is offered you ignore it. so I have no petty on you. -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Building LFS/BLFS through ssh session question
Will building LFS/BLFS through an ssh session have adverse effects on the build? I have noticed that vim does not work at all when I am connected to LFS via ssh but works without problem when logged in directly to the LFS computer. -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: Building LFS/BLFS through ssh session question
On Tue, Feb 16, 2010 at 7:42 PM, stosss sto...@gmail.com wrote: Will building LFS/BLFS through an ssh session have adverse effects on the build? I have noticed that vim does not work at all when I am connected to LFS via ssh but works without problem when logged in directly to the LFS computer. I found out that vim will not work across ssh without the correct switches and command string. I learned that vim uses tty. I learned that ssh does not give you a tty session, but there are ways around that. -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: Building LFS/BLFS through ssh session question
On Tue, Feb 16, 2010 at 10:18 PM, ALIP BUDIANTO rabbit8...@gmail.com wrote: On Tue, Feb 16, 2010 at 5:49 PM, stosss sto...@gmail.com wrote: On Tue, Feb 16, 2010 at 7:42 PM, stosss sto...@gmail.com wrote: Will building LFS/BLFS through an ssh session have adverse effects on the build? I have noticed that vim does not work at all when I am connected to LFS via ssh but works without problem when logged in directly to the LFS computer. I found out that vim will not work across ssh without the correct switches and command string. I learned that vim uses tty. I learned that ssh does not give you a tty session, but there are ways around that. -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page Use sed to make it look for a pts of the ssh session? I got around the problem. I have sent info to kde and the distro that is having the problem to see if they can figure out where the problem is. It is happening on kde4.3.4 on my PCLinuxOS but it does not happen in kde3.5.10 on any distro I have tried. The problem is vim will not work across ssh in xterm on kde4 on PCLinuxOS but will in a real terminal. Initially I was wondering if I was messing up my build on (B)LFS doing it over ssh because vim was freaking out. I know what I have to do to make it work so its all good. -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
xorg utilities will not install
Beyond Linux® From Scratch - Version svn-20100215 Chapter 23. X Window System Environment Xorg Utilities I grabbed: http://anduin.linuxfromscratch.org/files/BLFS/svn/xorg/util-7.5-2.md5 http://anduin.linuxfromscratch.org/files/BLFS/svn/xorg/util-7.5-2.wget as user: ran this: mkdir util cd util grep -v '^#' ../util-7.5-2.wget | wget -i- -c \ -B http://xorg.freedesktop.org/releases/individual/util/ md5sum -c ../util-7.5-2.md5 ran tar and entered each directory and ran: ./configure $XORG_CONFIG make then as root: make install makedepend is the only one that installed There were no errors on any of them they all appeared to do what was expected. I ran which and found only makedepend My base is LFS 6.5 -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: Building LFS/BLFS through ssh session question
On Wed, Feb 17, 2010 at 12:08 AM, Bruce Dubbs bruce.du...@gmail.com wrote: stosss wrote: I got around the problem. I have sent info to kde and the distro that is having the problem to see if they can figure out where the problem is. It is happening on kde4.3.4 on my PCLinuxOS but it does not happen in kde3.5.10 on any distro I have tried. The problem is vim will not work across ssh in xterm on kde4 on PCLinuxOS but will in a real terminal. Initially I was wondering if I was messing up my build on (B)LFS doing it over ssh because vim was freaking out. I know what I have to do to make it work so its all good. Please share a little more. I admit that I still don't like kde4 so I don't use it. As you say, there is no problem with kde3 that I've seen. I do know that most distros build X into vim and that can cause a problem if ssh isn't configured to handle that. What was the workaround that solved your problem? Okay, in the xterm it will not work at all (this is on a PCLinuxOS kde4.3.4) but switching from F7 to F1-F6 into the terminal and trying it from there worked like it is supposed to work. Still waiting to see if anyone from PCLOS and kde know why it is not working in kde4 xterm. If some one does not know the command string ssh -t u...@rhost 'vi directory/file' works like a charm. -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: xorg utilities will not install
On Wed, Feb 17, 2010 at 12:25 AM, Bruce Dubbs bruce.du...@gmail.com wrote: stosss wrote: Beyond Linux® From Scratch - Version svn-20100215 Chapter 23. X Window System Environment Xorg Utilities I grabbed: http://anduin.linuxfromscratch.org/files/BLFS/svn/xorg/util-7.5-2.md5 http://anduin.linuxfromscratch.org/files/BLFS/svn/xorg/util-7.5-2.wget as user: ran this: mkdir util cd util grep -v '^#' ../util-7.5-2.wget | wget -i- -c \ -B http://xorg.freedesktop.org/releases/individual/util/ md5sum -c ../util-7.5-2.md5 ran tar and entered each directory and ran: ./configure $XORG_CONFIG make then as root: make install makedepend is the only one that installed There were no errors on any of them they all appeared to do what was expected. I ran which and found only makedepend Did you look at the contents of util-7.5-2.wget? There are only three files installed: /usr/share/aclocal/xorg-macros.m4 /usr/share/man/man1/makedepend.1 /usr/bin/makedepend There used to be more, but xorg utils only has these now. no, sorry! So I still need to go download the others. Man I hate that when I do that! -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: Building LFS/BLFS through ssh session question
On Wed, Feb 17, 2010 at 12:37 AM, Bruce Dubbs bruce.du...@gmail.com wrote: stosss wrote: On Wed, Feb 17, 2010 at 12:08 AM, Bruce Dubbs bruce.du...@gmail.com wrote: What was the workaround that solved your problem? Okay, in the xterm it will not work at all (this is on a PCLinuxOS kde4.3.4) but switching from F7 to F1-F6 into the terminal and trying it from there worked like it is supposed to work. Still waiting to see if anyone from PCLOS and kde know why it is not working in kde4 xterm. If some one does not know the command string ssh -t u...@rhost 'vi directory/file' works like a charm. kde generally uses konsole. Do you really mean xterm? Does PCLinuxOS have any /dev/tty* devices? On the remote system, is it vi or vim? I think you are saying PCLinuxOS is the ssh client, but what is the sshd server? Typically, I just 'ssh host' to get a bash prompt and run vi-vim from there. PCLOS is the client and my lfs 6.5 is the server. Yes ssh host does work in the terminal. PCLOS is a Mandriva fork and they both use all those different drake tools for a lot of the config stuff. I don't think PCLOS follows FHS closely. vim behaves very strangely in PCLOS any way, not like Fedora, Debian and LFS. -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
BLFS libxcb-1.4 configure error cmd terminated
Beyond Linux® From Scratch - Version svn-20100203 Chapter 8. General Libraries libxcb-1.4 checking for xsltproc... no configure: error: XCB requires xsltproc. The command terminated right after that appeared on the screen. I did not see anything in the documentation up to this point about xsltproc. installed Required libXau-1.0.5, libXdmcp-1.0.3, libpthread-stubs-0.1, libxslt-1.1.26, and xcb-proto-1.5 I started this series of package builds from: Beyond Linux® From Scratch - Version svn-20100203 Part VI. X + Window Managers and worked my way through the dependencies installing all of the required and some of the optional. I even looked ahead checking to see what might become required some where else before decided to build or not the optional. I had no problems with any of the packages in the x window system section until this one. I have been following the book and only doing what was in the book and nothing else. My environment for the x windows system builds is set up like this: export XORG_PREFIX=/usr export XORG_CONFIG=--prefix=$XORG_PREFIX --sysconfdir=/etc \ --mandir=$XORG_PREFIX/share/man --localstatedir=/var Placed the above in /etc/profile so they would be available to root and the unprivileged user. /sources/xc /sources/xc/proto /sources/xc/util /sources/xc/libxcb-1.4 -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: BLFS libxcb-1.4 configure error cmd terminated
On Mon, Feb 15, 2010 at 3:09 AM, stosss sto...@gmail.com wrote: Beyond Linux® From Scratch - Version svn-20100203 Chapter 8. General Libraries libxcb-1.4 checking for xsltproc... no configure: error: XCB requires xsltproc. The command terminated right after that appeared on the screen. I did not see anything in the documentation up to this point about xsltproc. installed Required libXau-1.0.5, libXdmcp-1.0.3, libpthread-stubs-0.1, libxslt-1.1.26, and xcb-proto-1.5 I started this series of package builds from: Beyond Linux® From Scratch - Version svn-20100203 Part VI. X + Window Managers and worked my way through the dependencies installing all of the required and some of the optional. I even looked ahead checking to see what might become required some where else before decided to build or not the optional. I had no problems with any of the packages in the x window system section until this one. I have been following the book and only doing what was in the book and nothing else. My environment for the x windows system builds is set up like this: export XORG_PREFIX=/usr export XORG_CONFIG=--prefix=$XORG_PREFIX --sysconfdir=/etc \ --mandir=$XORG_PREFIX/share/man --localstatedir=/var Placed the above in /etc/profile so they would be available to root and the unprivileged user. /sources/xc /sources/xc/proto /sources/xc/util /sources/xc/libxcb-1.4 Okay! Found my problem. I was actually here: Beyond Linux® From Scratch - Version svn-20100203 Chapter 23. X Window System Environment Xorg Libraries And working my way through the required Ed-1.4, Fontconfig-2.7.3, Xorg Protocol Headers, and libXdmcp-1.0.3 And decided to do three of these Optional libxcb-1.4 (a modern Xlib replacement) and xmlto-0.0.23 with one or more of the following: FOP-0.95, Links-2.2, Lynx-2.8.7rel.1, and w3m (to generate additional PDF or text documentation for the libXfont package). If I had jumped over to xmlto-0.0.23 first I would have found the package on that page that gave me what I was missing for libxcb-1.4 Problem solved package built no problems. So maybe a note should be added or the order in the options list changed. So some one else does not get tripped by this. -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Old BSD commands
Beyond Linux® From Scratch - Version svn-20100203 Chapter 42. Extensible Markup Language (XML) DocBook XSL Stylesheets-1.75.2 tar xf ../docbook-xsl-doc-1.75.2.tar.bz2 -C .. -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Google says it Swedish!?
It looks English to me. http://www.linuxfromscratch.org/blfs/downloads/svn/ -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: Google says it Swedish!?
It looks English to me. http://www.linuxfromscratch.org/blfs/downloads/svn/ I attached a png I hope it goes through. attachment: snapshot.png-- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: BLFS libxcb-1.4 configure error cmd terminated
So maybe a note should be added or the order in the options list changed. So some one else does not get tripped by this. In what way is it unclear? The xsltproc command is provided by libxslt, which as you pointed out, is a required dependency in the book. Simon. I looked back through the book and see that libxslt is listed as required in libxcb. I was tired and must have missed it. But I saw it and built it under xmlto. oh well, sorry for the noise. I am going to build LFS/BLFS several more times. Each time I do I learn more. I already built LFS to completion one other time and partially built some of BLFS. This is my sceond time with BLFS and I went farther this time and I have learned more. I am building it as a VM this time instead of using one of my boxes. -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Beyond Linux(R) From Scratch - Version svn-20100203 Chapter 8. General Libraries
libxml2-2.7.6 tar xf ../xmlts20080205.tar.gz if you want to get all the old BSD format out tar -xf ../xmlts20080205.tar.gz or tar -xvf ../xmlts20080205.tar.gz If I had access to the book I would do it for you. -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: Openssh chapter 19
On Sat, Feb 13, 2010 at 3:19 AM, Jan-Christoph Bornschlegel trollf...@googlemail.com wrote: stosss schrieb: [...] I use /usr for everything. During the build process executable binaries should go in /usr/bin. The sentence says copy it there. If it is not there already then where is it? Does it not get put there until make install? Because the same paragraph says it needs to be there before running make test, which is done before make install. Generally make creates executables somewhere under the directory where you call it, and make install copies them to /usr/bin, that's why make install must be done as root and the rest works under any user who can write to the build directory (given you don't have your /usr/bin world writable, of course -- and don't laugh, I knew people who fixed problems like this). So if you compile a package /src/foo-x.y.z.tar.bz2, you'll probably find the package under /src/foo-x.y.z/. If there is a ./build or ./bin or whatever depends on the package. Exceptions, of course, gcc and binutils, which use own build directories -- but you are there when yu call make, aren't you? If I wonder what is new after make, I just run ls -alrtR in the package source directory and compare the timestamp. Or I touch a file _before_ make and then use find -newer :) Or I look at the Makefile. So without knowing the package, I guess from reading here: If you happen to have a scp binary already, no matter where it comes from, save it somewhere and replace it by the newly built one, because the testsuite expects it to reside in /usr/bin. And if it's not there, just make a copy for test make install will overwrite it later anyway. Thanks, I went ahead and unpacked and built the package, copied scp to /usr/bin, ran the test, no errors at all, ran grep it came back clean. Installed the package tried connecting to one of my other OSs no problem. started sshd no problem. After doing it the sentence was easy to understand. Sorry for the noise. -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Openssh chapter 19
svn-20100203 from the 02-10-2010 archive The last sentence in the paragraph between make and make test. _To run the test suite, first copy the scp program to /usr/bin, making sure that you back up any existing copy first._ This is probably enough for some one who has done this before and knows what to look for and where to look and understands the risk of why to back up any existing copy. Not complaining, just pointing out what is probably obvious. :) With a fresh LFS install with only the minimal BLFS stuff done, like reading through chapter 1, 2 and doing chapter 3 and openssl in chapter 4 and the only other things being GPM and WGET installed, there probably isn't any existing copy of scp. Once I have run make, where will the scp program be? Would the make install move it to the replace? Not complaining just suggesting, It would be nice if there was more information then just that sentence. :) Any volunteers willing to help make that sentence a little clearer? -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: Can't control my mutt
Put it on a leash then you can control your mutt. ;) -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: blfs-book-svn-html
On Thu, Feb 11, 2010 at 4:53 AM, Simon Geard delga...@ihug.co.nz wrote: On Wed, 2010-02-10 at 15:35 -0500, stosss wrote: Why is it that you and other developers are so touchy about the book and its condition and people pointing out things that could be done different, better or whatever? Why do you and the others insist on thinking there is nothing wrong with the book and so unwilling to improve it? Because providing technical support, voluntary or not, is pretty bad for one's mental health - constantly responding to the same questions and suggestions again and again and again, frequently without any thanks. Especially so with volunteers, where gratitude is the only reward we can expect. Now, I agree with you, some of us can be a bit sharp - saying You must have done something wrong, go back and read the instructions again is neither helpful, nor friendly. But understand that people aren't intending to be unpleasant - just stressed, or frustrated at being asked the same questions again and again. I agree -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
blfs-book-svn-html
What is different between these two? blfs-book-svn-html-2010-02-04 blfs-book-svn-html-2010-02-09 Both only show changes as of 02/03 and this is also at the top of the page for both of them svn-20100203. I double checked to make sure I had the right one. -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: blfs-book-svn-html
On Wed, Feb 10, 2010 at 6:33 AM, Randy McMurchy ra...@linuxfromscratch.org wrote: stosss wrote these words on 02/10/10 02:35 CST: What is different between these two? blfs-book-svn-html-2010-02-04 blfs-book-svn-html-2010-02-09 Both only show changes as of 02/03 and this is also at the top of the page for both of them svn-20100203. I double checked to make sure I had the right one. Where do you see a blfs-book-svn-html-2010-02-09 book? There is not one that I am aware of. http://www.linuxfromscratch.org/blfs/downloads/svn/ only it is blfs-book-svn-html-2010-02-10 now I got it before it changed. -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: blfs-book-svn-html
On Wed, Feb 10, 2010 at 1:21 PM, Bruce Dubbs bruce.du...@gmail.com wrote: stosss wrote: On Wed, Feb 10, 2010 at 6:33 AM, Randy McMurchy ra...@linuxfromscratch.org wrote: stosss wrote these words on 02/10/10 02:35 CST: What is different between these two? blfs-book-svn-html-2010-02-04 blfs-book-svn-html-2010-02-09 Both only show changes as of 02/03 and this is also at the top of the page for both of them svn-20100203. I double checked to make sure I had the right one. Where do you see a blfs-book-svn-html-2010-02-09 book? There is not one that I am aware of. http://www.linuxfromscratch.org/blfs/downloads/svn/ only it is blfs-book-svn-html-2010-02-10 now I got it before it changed. That the date the tarball was generated, but not the date of the book. There is a script that generates the book daily. If the date is more than one day old, there has been a problem of some kind. The date of the book is set in the source BOOK/general.ent and is on the top of each page in th ebook. Exactly and the 2010-02-09 and 2010-02-10 both have 20100203 at the top of the page. The last entry in the change log is February 3rd, 2010 according to this the book has not changed in seven days. Hence my original question. -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: blfs-book-svn-html
What is different between these two? blfs-book-svn-html-2010-02-04 blfs-book-svn-html-2010-02-09 Both only show changes as of 02/03 and this is also at the top of the page for both of them svn-20100203. I double checked to make sure I had the right one. Where do you see a blfs-book-svn-html-2010-02-09 book? There is not one that I am aware of. http://www.linuxfromscratch.org/blfs/downloads/svn/ only it is blfs-book-svn-html-2010-02-10 now I got it before it changed. That the date the tarball was generated, but not the date of the book. There is a script that generates the book daily. If the date is more than one day old, there has been a problem of some kind. The date of the book is set in the source BOOK/general.ent and is on the top of each page in th ebook. Exactly and the 2010-02-09 and 2010-02-10 both have 20100203 at the top of the page. The last entry in the change log is February 3rd, 2010 according to this the book has not changed in seven days. Hence my original question. Also what is the point of a nightly snapshot if the book has not changed? -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: Thunderbird 3.0.1
I managed to compile Thunderbird 3.0.1 with the attached .mozconfig file (basically a slightly modified Firefox .mozconfig file) using the following command to compile install: make -f client.mk http://client.mk build make -f client.mk http://client.mk install During the compilation and installation process I encountered no problems, but after executing it I have the following problems: * Doesnt load when I execute thunderbird as a regular user (does load when I execute it as root). * When I setup an IMAP account it manages to get the folders list, but then is stalls forever In the status bar I see something like: indexing 1 of 2 messages (0% complete) and it's just stuck like this * I cant open .eml files using File - Open svaed message.. - nothing happens once I choose a file. Anybody has any idea what can cause this ? For the few of you who managed to compile Thunderbird - is it working ok ? Thunderbird works fine for me (I'm using it now) but I built it from the current mercurial sources: https://developer.mozilla.org/en/Simple_Thunderbird_build Looking at your mozconfig, the only options that look a bit iffy to me are: ac_add_options --with-system-nspr ac_add_options --with-system-nss ac_add_options --enable-ldap ac_add_options --enable-safe-browsing What do you know, ac_add_options --enable-safe-browsing was the cause of the problems. I commented it out and now everything is working ok, BUT only for root. When I execute thunderbird as a regular user - nothing happens and I just get a command prompt. Maybe you need to change ownership or permissions on the binary. -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: blfs-book-svn-html
On Wed, Feb 10, 2010 at 1:45 PM, Bruce Dubbs bruce.du...@gmail.com wrote: stosss wrote: Also what is the point of a nightly snapshot if the book has not changed? Because it is set up as a cron job and I didn't go to the effort of trying to figure out if any of the 300 or so pages changed. Most people will look at the document itself, especially the change log, to see what changes have been made. That is exactly what I did. According to the change Log the book has not changed in 7 days. I also put this in one of my earlier posts on this thread. -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: blfs-book-svn-html
On Wed, Feb 10, 2010 at 2:49 PM, Bruce Dubbs bruce.du...@gmail.com wrote: stosss wrote: On Wed, Feb 10, 2010 at 1:45 PM, Bruce Dubbs bruce.du...@gmail.com wrote: stosss wrote: Also what is the point of a nightly snapshot if the book has not changed? Because it is set up as a cron job and I didn't go to the effort of trying to figure out if any of the 300 or so pages changed. Most people will look at the document itself, especially the change log, to see what changes have been made. That is exactly what I did. According to the change Log the book has not changed in 7 days. I also put this in one of my earlier posts on this thread. What's your point? My original point was to find out what was different between the 02/03 and 02/09 snapshots since there did not appear to be any. Then my new point was to question the reason for generating new snapshots if nothing changed. Why is it that you and other developers are so touchy about the book and its condition and people pointing out things that could be done different, better or whatever? Why do you and the others insist on thinking there is nothing wrong with the book and so unwilling to improve it? -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: blfs-book-svn-html
Also what is the point of a nightly snapshot if the book has not changed? Because it is set up as a cron job and I didn't go to the effort of trying to figure out if any of the 300 or so pages changed. Most people will look at the document itself, especially the change log, to see what changes have been made. That is exactly what I did. According to the change Log the book has not changed in 7 days. I also put this in one of my earlier posts on this thread. What's your point? My original point was to find out what was different between the 02/03 and 02/09 snapshots since there did not appear to be any. Then my new point was to question the reason for generating new snapshots if nothing changed. Why is it that you and other developers are so touchy about the book and its condition and people pointing out things that could be done different, better or whatever? Why do you and the others insist on thinking there is nothing wrong with the book and so unwilling to improve it? Because there is only one real rule in linux. YMYR (Your Machine Your Rules) In other words, if you don't like how things are managed by others, talk to them and if they disagree go ahead and pick up your bat and ball and head home. P.S., you were very accusatory with that last post. I'd try not to be too rude to people you're asking support from. I am just pointing out the facts as can be found by searching the archives of any of the LFS mailing lists. I am not trying to be accusatory or rude. Your response is the typical response that can also by found in the same archives to the challenges made by many. Often times it is necessary to find help and solutions from some place other than LFS because of this kind of attitude from people responding as you have. -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: blfs-book-svn-html
On Wed, Feb 10, 2010 at 3:51 PM, Matthew Burgess matt...@linuxfromscratch.org wrote: stosss wrote: Why is it that you and other developers are so touchy about the book and its condition and people pointing out things that could be done different, better or whatever? Why do you and the others insist on thinking there is nothing wrong with the book and so unwilling to improve it? I think that's a little unfair. Please remember that both the LFS and BLFS projects are based on *volunteer* effort and therefore noone should *expect* to have their particular pet-peeve fixed in any particular amount of time (or at all in fact). Whilst we do endeavour to address all suggestions, lack of time or a particular urge to 'scratch an itch' that a particular developer may not be feeling is more than reasonable behaviour in such projects. Why is the fact that we regenerate the book every day such a problem for you? If the date of the book hasn't been incremented then it's fairly safe to say that no changes have been made. I don't think it would take too much to change our nightly jobs to not render a new copy of the book if no changes have been made, but again, nobody apart from you seems to care at the moment. Given the long list of defects in BLFS' Trac system I'd wager that most of the devs would rather spend time tackling them than preventing regeneration of a book on a server that has plenty of capacity to do so. Matthew and Bruce, I am not complaining. I am simply asking. I do realize that this is a volunteer project. I am not expecting you to do things as though you have to. I am willing to jump in and help. I am sorry if you have taken offense. That is not my intention. Yes you get defensive and that is understandable. But it would be a lot better if I and others could figure out how to ask more politely and if those taking offense might also be willing to take a deep breath and assume maybe the person is not trying to be offensive. so, again I apologies. I really would like to help. I like the LFS project. I have been looking at some others that are similar. I don't like them as much but their docs seem to be a little cleaner or better in some ways. There really are some areas that could be improved. The nightly snapshots is not a big deal. I don't have a problem with it. i was not sure about what was going on because the book date was still the same. you guys answered that so okay. -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: blfs-book-svn-html
On Wed, Feb 10, 2010 at 4:39 PM, Bruce Dubbs bruce.du...@gmail.com wrote: stosss wrote: I am not complaining. I am simply asking. Sometimes its hard to interpret words when they are only written. Yes, that is the problem with written communication. My interpretation of your words was a complaint. It may not have been your intent. volunteer project. I am not expecting you to do things as though you have to. I am willing to jump in and help. I am sorry if you have taken offense. There is no offense taken. Perhaps you interpreted some of our written words in a way not intended. again I apologies. OK, but I don't really think that's necessary. There really are some areas that could be improved. That's always true, but what those improvements would be will differ from person to person. It becomes an opinion. True I think that the vast majority of successful LFS builders do just fine with the book the way it is. However we will still try to improve it. Yes, people who are determined to figure things out do go on to build a workable system. I did once I understood the mind set or concept of the way the book was written. If I have a good point of reference and understand the rules/structure/guide or whatever, I can get from the beginning to the end. Its when I can't get that known good point of reference that I get all messed up. -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: Starting BLFS
I went ahead and generated the dependency graph for the required dependencies and another for the full list: http://www.linuxfromscratch.org/~bdubbs/svg/ I don *not* recommend the full list because it's so large you can't see any relationships. Actually, the blfs-all.svg is unusable: $ head blfs-all.svg ?xml version=1.0 encoding=UTF-8 standalone=no? !DOCTYPE svg PUBLIC -//W3C//DTD SVG 1.0//EN http://www.w3.org/TR/2001/REC-SVG-20010904/DTD/svg10.dtd; [ !ATTLIST svg xmlns:xlink CDATA #FIXED http://www.w3.org/1999/xlink; ] !-- Generated by Graphviz version 2.20.3 (Sun Dec 14 19:24:04 UTC 2008) For user: (bdubbs) Bruce Dubbs -- !-- Title: BLFS Pages: 1 -- svg width=38855pt height=5814pt That's about 45 *feet* wide. I'll leave it out there in case anyone wants to try to do something useful with it, but it's not likely. That is huge! -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: blfs-support Digest, Vol 1943, Issue 1
On Fri, Jan 22, 2010 at 4:52 AM, Jay jayfl...@gmail.com wrote: Message4 I managed to compile kernel 2.6.32 with aufs and squashfs. Everything went well. Now i will strip slackware down a little and run the linux live scripts. Don't top post and trim the post. -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
blfs svn book page errors
Beyond Linux® From Scratch - Version svn-20100110 Chapter 16. Basic Networking Programs Rsync-3.0.7 Client Chapter 24 – rsync-3.0.7. should be Chapter 22 – rsync-3.0.7. Beyond Linux® From Scratch - Version svn-20100110 Chapter 16. Basic Networking Programs Samba-3.0.30 Client Chapter 21 – Samba-3.0.30. should be Chapter 19 – Samba-3.0.30. -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: pth-2.0.7 step in book different from...
On Wed, Dec 16, 2009 at 2:03 AM, stosss sto...@gmail.com wrote: blfs-book-svn-html-2009-12-14 chpater 8 pth-2.0.7 At the end of the make command, the last line on screen says: Now please type 'make test' to run a quick test suite. Hope it works. The book says run make check. Beyond Linux® From Scratch - Version svn-20100110 Chapter 8. General Libraries ./configure --prefix=/usr make To test the results, issue: make check. ^^^ this should be make test according to the screen instructions at the end of the make command. -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
iptables-1.4.4 configure question
I have a very basic lfs6.5/blfs svn system. I am taking my time through the security chapter. Been there about 3 weeks now. as I mentioned in another post I was having trouble with iptables-1.3.8 errors during compilation. Chris S gave a link suggesting I should look at iptables-1.4.4. I did, it installed, it appears to be right. My question: setting up a network firewall page has three samples, the first one in the book as copied below, will it work as is until I learn more and decide I might want to change it? My lfs/blfs box is a personal project behind two firewall routers in my personal office at home. I am not using this box for anything other than to learn using the lfs/blfs books. I am pretty sure my box is safe from attack because both of my firewall routers have all the external ports closed and set not to accept anything initiated from the outside. There are no other computers on my network except the one I am using now and the lfs box. I am the only one with physical access to these boxes. I do not go out of my network with the lfs box. I am currently reading this book: LINUX FIREWALLS Attack Detection and Response with iptables, psad, and fwsnort by Michael Rash I will eventually get to all those links about configuring and building firewalls. Personal Firewall A Personal Firewall is designed to let you access all the services offered on the Internet, but keep your box secure and your data private. cat /etc/rc.d/rc.iptables EOF #!/bin/sh # Begin $rc_base/rc.iptables # Insert connection-tracking modules # (not needed if built into the kernel) modprobe ip_tables modprobe iptable_filter modprobe ip_conntrack modprobe ip_conntrack_ftp modprobe ipt_state modprobe ipt_LOG # Enable broadcast echo Protection echo 1 /proc/sys/net/ipv4/icmp_echo_ignore_broadcasts # Disable Source Routed Packets echo 0 /proc/sys/net/ipv4/conf/all/accept_source_route echo 0 /proc/sys/net/ipv4/conf/default/accept_source_route # Enable TCP SYN Cookie Protection echo 1 /proc/sys/net/ipv4/tcp_syncookies # Disable ICMP Redirect Acceptance echo 0 /proc/sys/net/ipv4/conf/all/accept_redirects # Don't send Redirect Messages echo 0 /proc/sys/net/ipv4/conf/all/send_redirects echo 0 /proc/sys/net/ipv4/conf/default/send_redirects # Drop Spoofed Packets coming in on an interface, where responses # would result in the reply going out a different interface. echo 1 /proc/sys/net/ipv4/conf/all/rp_filter echo 1 /proc/sys/net/ipv4/conf/default/rp_filter # Log packets with impossible addresses. echo 1 /proc/sys/net/ipv4/conf/all/log_martians echo 1 /proc/sys/net/ipv4/conf/default/log_martians # be verbose on dynamic ip-addresses (not needed in case of static IP) echo 2 /proc/sys/net/ipv4/ip_dynaddr # disable Explicit Congestion Notification # too many routers are still ignorant echo 0 /proc/sys/net/ipv4/tcp_ecn # Set a known state iptables -P INPUT DROP iptables -P FORWARD DROP iptables -P OUTPUT DROP # These lines are here in case rules are already in place and the # script is ever rerun on the fly. We want to remove all rules and # pre-existing user defined chains before we implement new rules. iptables -F iptables -X iptables -Z iptables -t nat -F # Allow local-only connections iptables -A INPUT -i lo -j ACCEPT # Free output on any interface to any ip for any service # (equal to -P ACCEPT) iptables -A OUTPUT -j ACCEPT # Permit answers on already established connections # and permit new connections related to established ones # (e.g. port mode ftp) iptables -A INPUT -m state --state ESTABLISHED,RELATED -j ACCEPT # Log everything else. What's Windows' latest exploitable vulnerability? iptables -A INPUT -j LOG --log-prefix FIREWALL:INPUT # End $rc_base/rc.iptables EOF chmod 700 /etc/rc.d/rc.iptables -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: iptables-1.3.8 BLFS book svn-20100105 compile error
If the following modprobes are built into the kernel and not modules, should I comment out the modprobes below as in my sample below? cat /etc/rc.d/rc.iptables EOF #!/bin/sh # Begin $rc_base/rc.iptables # Insert connection-tracking modules # (not needed if built into the kernel) # modprobe ip_tables # modprobe iptable_filter # modprobe ip_conntrack # modprobe ip_conntrack_ftp # modprobe ipt_state # modprobe ipt_LOG Is this correct or can it just be left alone like this? cat /etc/rc.d/rc.iptables EOF #!/bin/sh # Begin $rc_base/rc.iptables # Insert connection-tracking modules # (not needed if built into the kernel) modprobe ip_tables modprobe iptable_filter modprobe ip_conntrack modprobe ip_conntrack_ftp modprobe ipt_state modprobe ipt_LOG If you run modprobe on something that is already loaded (as a module or built in) then modprobe does nothing by consume a few cpu cycles. The wall clock time is negligible. You can do it either way. Thank you -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: iptables-1.4.4 configure question
I have a very basic lfs6.5/blfs svn system. I am taking my time through the security chapter. Been there about 3 weeks now. as I mentioned in another post I was having trouble with iptables-1.3.8 errors during compilation. Chris S gave a link suggesting I should look at iptables-1.4.4. I did, it installed, it appears to be right. 1.4.6 is current. And it appears to be the same when it comes to configure, make, make install and operational configuration. I was going to use that but the link was for 1.4.4. My question: setting up a network firewall page has three samples, the first one in the book as copied below, will it work as is until I learn more and decide I might want to change it? My lfs/blfs box is a personal project behind two firewall routers in my personal office at home. I am not using this box for anything other than to learn using the lfs/blfs books. I am pretty sure my box is safe from attack because both of my firewall routers have all the external ports closed and set not to accept anything initiated from the outside. There are no other computers on my network except the one I am using now and the lfs box. I am the only one with physical access to these boxes. I do not go out of my network with the lfs box. I don't use a firewall on my internal computers, but you can if you want. The script you quoted will allow all external connections and no connections from any other box. You can't, for instance, ssh into your system from another local system. That's something you might want to do. I thought about not using a firewall. I haven't used one on my distro boxes in the past and no one has ever made it passed the first router. -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: BLFS svn book Shadow-4.1.4.2 question about a page note
At the bottom of the page for shadow in the BLFS svn book latest and earlier versions. Is this note talking about a step that was done or needs to be done? Note ENV_SUPATH is no longer supported. You must create a valid /root/.bashrc file to provide a modified path for the super-user. I don't think it's in any way unclear, but I'll explain anyway... ENV_SUPATH is an option in /etc/login.defs, specifying the default PATH for the root user. However, the Shadow page in BLFS assumes you are rebuiding Shadow with PAM support, and if you are using PAM, ENV_SUPATH no longer does anything. I got that. Is it telling about a process that was done in the steps above on the shadow page _or_ is it telling about something that still needs (or might need) to be done? -- I think the note means that the variable is defined in the file, but has no effect when using PAM. The note names one possible workaround to modify the super-user path when using shadow with PAM support. ENV_SUPATH exists in /etc/login.defs but does not do or cause any behavior. So the note mentions a step that has not yet been performed nor is described in detail. That is what I thought. If the authors thought it was necessary to make the note, then why not say if the undescribed step is important or what possible problems might be seen by not doing the step? Why not explain how to do the step? If not doing the step won't cause any problem then why mention it at all? -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: BLFS svn book Shadow-4.1.4.2 question about a page note
It looks like you're overthinking things and reading more into what's on the page then what's there. It's referring to exactly what is done on that page - configuring Shadow to use PAM. In particular, it follows up on the previous note about the regular path now being handled by a PAM module and configured in a .conf file - it's just that there apparently isn't any PAM config for the superuser specifically, so the additional note was added about adding to root's .bashrc. Adding _what_ (and how) to root's .bashrc? -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: BLFS svn book Shadow-4.1.4.2 question about a page note
You must create a valid /root/.bashrc file to provide a modified path for the super-user. Therefore, to your question of what to add to root's .bashrc - it's a modified path. You know, since root generally has additional dirs in its PATH (such as /sbin and /usr/sbin). I understand that but you said the note was clear. It is not at all clear. You must(doesn't say why you must. Must is strong. Where is the cause and effect?) create a valid /root/.bashrc file to provide a modified path(what should that modified path look like?) for the super-user. The note has the appearance of something important without giving supporting detail as to why it is important. -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
iptables-1.3.8 BLFS book svn-20100105 compile error
tar -xvf iptables-1.3.8.tar.bz2 cd iptables-1.3.8 sed -i 's/name=$node/name=node/' iptables.xslt make LIBDIR=/lib KERNEL_DIR=/usr 21 | tee ../iptables.log Making dependencies: please wait... Extensions found: IPv4:NFLOG IPv4:connbytes IPv4:dccp IPv4:quota IPv4:recent IPv4:string IPv6:NFLOG IPv6:REJECT IPv6:esp IPv6:hashlimit IPv6:mh IPv6:sctp cc -O2 -Wall -Wunused -I/usr/include -Iinclude/ -DIPTABLES_VERSION=\1.3.8\ -fPIC -o extensions/libipt_ah_sh.o -c extensions/libipt_ah.c cc -shared -o extensions/libipt_ah.so extensions/libipt_ah_sh.o cc -O2 -Wall -Wunused -I/usr/include -Iinclude/ -DIPTABLES_VERSION=\1.3.8\ -fPIC -o extensions/libipt_addrtype_sh.o -c extensions/libipt_addrtype.c cc -shared -o extensions/libipt_addrtype.so extensions/libipt_addrtype_sh.o cc -O2 -Wall -Wunused -I/usr/include -Iinclude/ -DIPTABLES_VERSION=\1.3.8\ -fPIC -o extensions/libipt_comment_sh.o -c extensions/libipt_comment.c cc -shared -o extensions/libipt_comment.so extensions/libipt_comment_sh.o cc -O2 -Wall -Wunused -I/usr/include -Iinclude/ -DIPTABLES_VERSION=\1.3.8\ -fPIC -o extensions/libipt_connmark_sh.o -c extensions/libipt_connmark.c cc -shared -o extensions/libipt_connmark.so extensions/libipt_connmark_sh.o cc -O2 -Wall -Wunused -I/usr/include -Iinclude/ -DIPTABLES_VERSION=\1.3.8\ -fPIC -o extensions/libipt_conntrack_sh.o -c extensions/libipt_conntrack.c cc -shared -o extensions/libipt_conntrack.so extensions/libipt_conntrack_sh.o cc -O2 -Wall -Wunused -I/usr/include -Iinclude/ -DIPTABLES_VERSION=\1.3.8\ -fPIC -o extensions/libipt_dscp_sh.o -c extensions/libipt_dscp.c cc -shared -o extensions/libipt_dscp.so extensions/libipt_dscp_sh.o cc -O2 -Wall -Wunused -I/usr/include -Iinclude/ -DIPTABLES_VERSION=\1.3.8\ -fPIC -o extensions/libipt_ecn_sh.o -c extensions/libipt_ecn.c cc -shared -o extensions/libipt_ecn.so extensions/libipt_ecn_sh.o cc -O2 -Wall -Wunused -I/usr/include -Iinclude/ -DIPTABLES_VERSION=\1.3.8\ -fPIC -o extensions/libipt_esp_sh.o -c extensions/libipt_esp.c cc -shared -o extensions/libipt_esp.so extensions/libipt_esp_sh.o cc -O2 -Wall -Wunused -I/usr/include -Iinclude/ -DIPTABLES_VERSION=\1.3.8\ -fPIC -o extensions/libipt_hashlimit_sh.o -c extensions/libipt_hashlimit.c cc -shared -o extensions/libipt_hashlimit.so extensions/libipt_hashlimit_sh.o cc -O2 -Wall -Wunused -I/usr/include -Iinclude/ -DIPTABLES_VERSION=\1.3.8\ -fPIC -o extensions/libipt_helper_sh.o -c extensions/libipt_helper.c cc -shared -o extensions/libipt_helper.so extensions/libipt_helper_sh.o cc -O2 -Wall -Wunused -I/usr/include -Iinclude/ -DIPTABLES_VERSION=\1.3.8\ -fPIC -o extensions/libipt_icmp_sh.o -c extensions/libipt_icmp.c cc -shared -o extensions/libipt_icmp.so extensions/libipt_icmp_sh.o cc -O2 -Wall -Wunused -I/usr/include -Iinclude/ -DIPTABLES_VERSION=\1.3.8\ -fPIC -o extensions/libipt_iprange_sh.o -c extensions/libipt_iprange.c cc -shared -o extensions/libipt_iprange.so extensions/libipt_iprange_sh.o cc -O2 -Wall -Wunused -I/usr/include -Iinclude/ -DIPTABLES_VERSION=\1.3.8\ -fPIC -o extensions/libipt_length_sh.o -c extensions/libipt_length.c cc -shared -o extensions/libipt_length.so extensions/libipt_length_sh.o cc -O2 -Wall -Wunused -I/usr/include -Iinclude/ -DIPTABLES_VERSION=\1.3.8\ -fPIC -o extensions/libipt_limit_sh.o -c extensions/libipt_limit.c cc -shared -o extensions/libipt_limit.so extensions/libipt_limit_sh.o cc -O2 -Wall -Wunused -I/usr/include -Iinclude/ -DIPTABLES_VERSION=\1.3.8\ -fPIC -o extensions/libipt_mac_sh.o -c extensions/libipt_mac.c extensions/libipt_mac.c: In function 'print': extensions/libipt_mac.c:107: warning: dereferencing type-punned pointer will break strict-aliasing rules extensions/libipt_mac.c:110: warning: dereferencing type-punned pointer will break strict-aliasing rules extensions/libipt_mac.c: In function 'save': extensions/libipt_mac.c:116: warning: dereferencing type-punned pointer will break strict-aliasing rules extensions/libipt_mac.c:120: warning: dereferencing type-punned pointer will break strict-aliasing rules cc -shared -o extensions/libipt_mac.so extensions/libipt_mac_sh.o cc -O2 -Wall -Wunused -I/usr/include -Iinclude/ -DIPTABLES_VERSION=\1.3.8\ -fPIC -o extensions/libipt_mark_sh.o -c extensions/libipt_mark.c cc -shared -o extensions/libipt_mark.so extensions/libipt_mark_sh.o cc -O2 -Wall -Wunused -I/usr/include -Iinclude/ -DIPTABLES_VERSION=\1.3.8\ -fPIC -o extensions/libipt_multiport_sh.o -c extensions/libipt_multiport.c cc -shared -o extensions/libipt_multiport.so extensions/libipt_multiport_sh.o cc -O2 -Wall -Wunused -I/usr/include -Iinclude/ -DIPTABLES_VERSION=\1.3.8\ -fPIC -o extensions/libipt_owner_sh.o -c extensions/libipt_owner.c cc -shared -o extensions/libipt_owner.so extensions/libipt_owner_sh.o cc -O2 -Wall -Wunused -I/usr/include -Iinclude/ -DIPTABLES_VERSION=\1.3.8\ -fPIC -o extensions/libipt_physdev_sh.o -c extensions/libipt_physdev.c cc -shared -o extensions/libipt_physdev.so extensions/libipt_physdev_sh.o cc -O2 -Wall
Re: iptables-1.3.8 BLFS book svn-20100105 compile error
tar -xvf iptables-1.3.8.tar.bz2 etc Have you tried using a more recent version of iptables? No, I will try that. -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: BLFS svn book Shadow-4.1.4.2 question about a page note
On Tue, Jan 5, 2010 at 9:47 PM, Simon Geard delga...@ihug.co.nz wrote: On Tue, 2010-01-05 at 17:21 -0500, Chris Staub wrote: Pasted from the Note in question: You must create a valid /root/.bashrc file to provide a modified path for the super-user. Therefore, to your question of what to add to root's .bashrc - it's a modified path. You know, since root generally has additional dirs in its PATH (such as /sbin and /usr/sbin). Reading that, I think he's actually got a fair point. The intended meaning is that if you were previously using ENV_SUPATH to give root a different PATH from ordinary users, you would now need to do so by modifying root's login scripts. But if you read that note, it starts by assuming the reader actually knows what ENV_SUPATH is, and why it being no longer supported means they have to create a suitable .bashrc file. If they don't know what ENV_SUPATH is, they're merely left with a cryptic instruction to create a .bashrc file with unspecified content. And consider, ENV_SUPATH isn't mentioned in the LFS shadow page, and only mentioned in this page in the context of saying it can't be used. A typical LFS builder is *not* going to know what that message means. A better wording would perhaps be something like: Note: The ENV_SUPATH option used to modify root's default path does not work with PAM. If you are using this option, you'll need to set the path in root's login scripts instead. To me, that explains what it does, and makes it clear that if you don't use it, you don't need to do anything. Thanks Simon for making this clear. It had no useful meaning to me the way it is currently written. -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: BLFS svn book Shadow-4.1.4.2 question about a page note
Reading that, I think he's actually got a fair point. The intended meaning is that if you were previously using ENV_SUPATH to give root a different PATH from ordinary users, you would now need to do so by modifying root's login scripts. But if you read that note, it starts by assuming the reader actually knows what ENV_SUPATH is, and why it being no longer supported means they have to create a suitable .bashrc file. If they don't know what ENV_SUPATH is, they're merely left with a cryptic instruction to create a .bashrc file with unspecified content. And consider, ENV_SUPATH isn't mentioned in the LFS shadow page, and only mentioned in this page in the context of saying it can't be used. A typical LFS builder is *not* going to know what that message means. A better wording would perhaps be something like: Note: The ENV_SUPATH option used to modify root's default path does not work with PAM. If you are using this option, you'll need to set the path in root's login scripts instead. To me, that explains what it does, and makes it clear that if you don't use it, you don't need to do anything. Simon. Yeah, I suppose it's would be reasonable to specify what ENV_SUPATH does. I think I just let myself get carried away with emphasizing the when is it needed part and didn't see that yes, he does have a point about explaining what that var does. Although, If you are using this option would likely not be necessary, as it's part of the default login.defs, so it would pretty much be used by everyone. Otherwise, anyone who is using it would add it themselves, in which case they wouldn't need to be told what it's for. So...yeah, the fact that the user never even creates it themselves would be a valid reason to explain exactly what it's for. Thank you! That is all I was trying to accomplish when I asked my original question. There are parts of the LFS and BLFS book written in a way that leaves less experienced users scratching their head wondering what they just read because it is written on the assumption the reader already knows the subject matter and that is not true 100% of the time. Then when authors or users defend the poorly written parts that just makes it worse. I will bet that is the reason most of the time for the conflict between new comers with less experience and those with more. The LFS project says the books are for learning. If something is written so less experienced users don't understand then change those parts. Don't get defensive and attack the person asking about them. It happens all the time on the LFS list and it happened to me the very first time I posted on this list. -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: BLFS svn book Shadow-4.1.4.2 question about a page note
Note: The ENV_SUPATH option used to modify root's default path does not work with PAM. If you are using this option, you'll need to set the path in root's login scripts instead. This one is clear. Note: The ENV_SUPATH option used to modify root's default path does not work with PAM. You have to set the path in root's login scripts instead. This one is not clear. If you are using this option, Is what makes it clear. If a user does not understand or use ENV_SUPATH they won't be concerned with the note if it has the part in it that you pulled out. If a user is using and understands ENV_SUPATH they will know they need to make adjustments. Why complicate things for the less experienced readers when it is not necessary? This note won't bother me again because I have been educated thanks to Simon. -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: iptables-1.3.8 BLFS book svn-20100105 compile error
The configuration for iptables-1.4.6 is a lot different then iptables-1.3.8
I tried iptables-1.3.8 three times with the same error result each time.
I am going to try iptables-1.4.6 unless someone has a good reason why
I should not just yet.
I am going to do it like this.
./configure --prefix=/usr
make
make install
Can any one see a problem with using this newer one in a LFS6.5/BLFS svn build?
Will this one cause a problem with the current boot scripts?
below is the install file for iptables-1.4.6
Installation instructions for iptables
==
iptables uses the well-known configure(autotools) infrastructure.
$ ./configure
$ make
# make install
Prerequisites
=
* no kernel-source required
* but obviously a compiler, glibc-devel and linux-kernel-headers
(/usr/include/linux)
Configuring and compiling
=
./configure [options]
--prefix=
The prefix to put all installed files under. It defaults to
/usr/local, so the binaries will go into /usr/local/bin, sbin,
manpages into /usr/local/share/man, etc.
--with-xtlibdir=
The path to where Xtables extensions should be installed to. It
defaults to ${prefix}/libexec/xtables.
--enable-devel (or --disable-devel)
This option causes development files to be installed to
${includedir}, which is needed for building additional packages,
such as Xtables-addons or other 3rd-party extensions.
It is enabled by default.
--enable-static
Produce additional binaries, iptables-static/ip6tables-static,
which have all shipped extensions compiled in.
--disable-shared
Produce binaries that have dynamic loading of extensions disabled.
This implies --enable-static.
(See some details below.)
--enable-libipq
This option causes libipq to be installed into ${libdir} and
${includedir}.
--with-ksource=
Xtables does not depend on kernel headers anymore, but you can
optionally specify a search path to include anyway. This is
probably only useful for development.
If you want to enable debugging, use
./configure CFLAGS=-ggdb3 -O0
(-O0 is used to turn off instruction reordering, which makes debugging
much easier.)
Other notes
===
The make process will automatically build multipurpose binaries.
These have the core (iptables), -save, -restore and -xml code
compiled into one binary, but extensions remain as modules.
Static and shared
=
Basically there are three configuration modes defined:
--disable-static --enable-shared (this is the default)
Build a binary that relies upon dynamic loading of extensions.
--enable-static --enable-shared
Build a binary that has the shipped extensions built-in, but
is still capable of loading additional extensions.
--enable-static --disable-shared
Shipped extensions are built-in, and dynamic loading is
deactivated.
--
http://linuxfromscratch.org/mailman/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
Re: iptables-1.3.8 BLFS book svn-20100105 compile error
The configuration for iptables-1.4.6 is a lot different then iptables-1.3.8 I tried iptables-1.3.8 three times with the same error result each time. I am going to try iptables-1.4.6 unless someone has a good reason why I should not just yet. I am going to do it like this. ./configure --prefix=/usr make make install Can any one see a problem with using this newer one in a LFS6.5/BLFS svn build? Will this one cause a problem with the current boot scripts? See suggested instructions for current iptables here - http://wiki.linuxfromscratch.org/blfs/ticket/2714 Thank you -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: iptables-1.3.8 BLFS book svn-20100105 compile error
If the following modprobes are built into the kernel and not modules, should I comment out the modprobes below as in my sample below? cat /etc/rc.d/rc.iptables EOF #!/bin/sh # Begin $rc_base/rc.iptables # Insert connection-tracking modules # (not needed if built into the kernel) # modprobe ip_tables # modprobe iptable_filter # modprobe ip_conntrack # modprobe ip_conntrack_ftp # modprobe ipt_state # modprobe ipt_LOG Is this correct or can it just be left alone like this? cat /etc/rc.d/rc.iptables EOF #!/bin/sh # Begin $rc_base/rc.iptables # Insert connection-tracking modules # (not needed if built into the kernel) modprobe ip_tables modprobe iptable_filter modprobe ip_conntrack modprobe ip_conntrack_ftp modprobe ipt_state modprobe ipt_LOG -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Steps in BSD format and Linux format in BLFS
Bruce pointed out on the LFS list that tar xf is BSD format tar -xf is short Linux format. So is there any special reason for using the BSD format in the BLFS book? I have found in the most recent release and earlier releases, some possible errors blfs-book-svn-html-2009-12-31.tar.bz2 Linux-PAM tar xf Remove the configuration file created earlier by issuing the following command as the root user: rm -rfv /etc/pam.d This removes the pam.d directory and all the contents. If you don't do this step, you will overwrite the test file several steps later and still have all the config files that were created in between. Which way is correct? I did it both ways and both ways seemed to work. I have a lot more config files in pam.d now than I did the first time. Everything looks right now and works but it did not look right before but worked any way. FreeType2 tar xf On the OpenSSH client page one can see this Chapter 21 – OpenSSH-5.1p1 but the link goes to chapter 19 and not 21 which is the database chapter. -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
BLFS svn book Shadow-4.1.4.2 question about a page note
At the bottom of the page for shadow in the BLFS svn book latest and earlier versions. Is this note talking about a step that was done or needs to be done? Note ENV_SUPATH is no longer supported. You must create a valid /root/.bashrc file to provide a modified path for the super-user. -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Linux-PAM step question BLFS svn latest
To test the results, a configuration file must be created. This file will be removed after the tests have completed. Ensure there are no errors produced by the tests before continuing the installation. First create the configuration file by issuing the following commands as the root user: My notes: above it says to create the test config file and after the test the file will be removed. Below you create the file and a directory that will be used later. (or not if you want to go the other way) install -v -m755 -d /etc/pam.d cat /etc/pam.d/other EOF auth required pam_deny.so account required pam_deny.so password required pam_deny.so session required pam_deny.so EOF Now run the tests by issuing make check. Remove the configuration file created earlier by issuing the following command as the root user: rm -rfv /etc/pam.d My notes: The step above removes the directory. My notes: now you get to the configuration after the install and have to put the directory and other file back. Configuring Linux-PAM Config Files /etc/security/* and /etc/pam.d/* or /etc/pam.conf Configuration Information why not just skip the entire rm step above and just overwrite the other file you created earlier. also later in the shadow config steps you over write the other file again. Step from shadow Other Currently, /etc/pam.d/other is configured to allow anyone with an account on the machine to use PAM-aware programs without a configuration file for that program. After testing Linux-PAM for proper configuration, install a more restrictive other file so that program-specific configuration files are required: cat /etc/pam.d/other EOF # Begin /etc/pam.d/other authrequiredpam_deny.so authrequiredpam_warn.so account requiredpam_deny.so account requiredpam_warn.so passwordrequiredpam_deny.so passwordrequiredpam_warn.so session requiredpam_deny.so session requiredpam_warn.so # End /etc/pam.d/other EOF -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: man-db-2.5.5 never installed
Since there is no Note Typogarphy in the book. You could just do this change to the HTML: p bGroff expects the environment variable code class=envarPAGE/code to contain the default paper size./b For users in the United States, bem class=parametercodePAGE=letter/code/em/b is appropriate. Elsewhere, bem class=parametercodePAGE=A4/code/em/b may be more suitable. While the default paper size is configured during compilation, it can be overridden later by echoing either “bspan class=quoteA4/span/b” or “bspan class=quoteletter/span/b” to the code class=filename/etc/papersize/code file. /p -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
man-db-2.5.5 never installed
I found this after trying to access a man page on my still rather fresh LFS 6.5 system after I installed a few packages from the BLFS book. I was using blfs-book-svn-html-2009-12-06 and switched to blfs-book-svn-html-2009-12-14 gpm-1.20.6, bc-1.06, openssl-0.9.8k, libgpg-error-1.7, libgcrypt-1.4.4, gnutls-2.8.4, wget-1.11.4, ntp-4.2.4p7 man-db-2.5.5 showed one error after make and make check during the LFS step on page 6.48 in LFS. I did not realize that error kept it from installing. I went on to finish building LFS 6.5 book with no errors that caused any problem. I have a bootable LFS 6.5. I have attempted twice, on my running LFS 6.5 system, with two different copies of man-db-2.5.5.tar.gz, to unpack, patch, configure, make and make check. I have seen the same error both times. I have complete log files of the entire step process of the unpack, configure, make and make check steps. I can show you as much of the logged process for each step as you want to see. The error is directly related to man.o. I have checked /usr/bin and none of the commands from man-db are there. I am assuming that the problem was because of a step before man-db in the LFS 6.5 book but I don't know where to look in the book or on my system to figure out how to fix the problem. Google didn't help, everything I could find was related to some other problem in distro installs. I have not been able to find anything that tells me what caused the problem or how to fix it. -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: man-db-2.5.5 never installed
On Tue, Dec 15, 2009 at 5:07 AM, Matthew Burgess matt...@linuxfromscratch.org wrote: On Tue, 15 Dec 2009 03:22:00 -0500, stosss sto...@gmail.com wrote: I have complete log files of the entire step process of the unpack, configure, make and make check steps. I can show you as much of the logged process for each step as you want to see. The error is directly related to man.o. I have checked /usr/bin and none of the commands from man-db are there. Please send the logs with about 20 lines of context either side of the man.o failure. We may also need config.log, but for now just the build log should do. some of the lines are really long gcc -std=gnu99 -DHAVE_CONFIG_H -I. -I.. -I../include -I../intl -I../gnulib/lib -I../gnulib/lib -I../lib -I../libdb -DCONFIG_FILE=\/etc/man_db.conf\ -DLOCALEDIR=\/usr/share/locale\ -DAPROPOS=\/usr/bin/apropos\ -DAPROPOS_NAME=\apropos\ -DMAN=\/usr/bin/man\ -DMANCONV=\/usr/lib/man-db/manconv\ -DMANDB=\/usr/bin/mandb\ -DSOELIM=\/usr/bin/zsoelim\ -DWHATIS=\/usr/bin/whatis\ -g -O2 -Wall -W -Wpointer-arith -Wwrite-strings -Wstrict-prototypes -Wshadow -Wformat-security -Wno-missing-field-initializers -MT descriptions.o -MD -MP -MF .deps/descriptions.Tpo -c -o descriptions.o descriptions.c mv -f .deps/descriptions.Tpo .deps/descriptions.Po gcc -std=gnu99 -DHAVE_CONFIG_H -I. -I.. -I../include -I../intl -I../gnulib/lib -I../gnulib/lib -I../lib -I../libdb -DCONFIG_FILE=\/etc/man_db.conf\ -DLOCALEDIR=\/usr/share/locale\ -DAPROPOS=\/usr/bin/apropos\ -DAPROPOS_NAME=\apropos\ -DMAN=\/usr/bin/man\ -DMANCONV=\/usr/lib/man-db/manconv\ -DMANDB=\/usr/bin/mandb\ -DSOELIM=\/usr/bin/zsoelim\ -DWHATIS=\/usr/bin/whatis\ -g -O2 -Wall -W -Wpointer-arith -Wwrite-strings -Wstrict-prototypes -Wshadow -Wformat-security -Wno-missing-field-initializers -MT encodings.o -MD -MP -MF .deps/encodings.Tpo -c -o encodings.o encodings.c mv -f .deps/encodings.Tpo .deps/encodings.Po gcc -std=gnu99 -DHAVE_CONFIG_H -I. -I.. -I../include -I../intl -I../gnulib/lib -I../gnulib/lib -I../lib -I../libdb -DCONFIG_FILE=\/etc/man_db.conf\ -DLOCALEDIR=\/usr/share/locale\ -DAPROPOS=\/usr/bin/apropos\ -DAPROPOS_NAME=\apropos\ -DMAN=\/usr/bin/man\ -DMANCONV=\/usr/lib/man-db/manconv\ -DMANDB=\/usr/bin/mandb\ -DSOELIM=\/usr/bin/zsoelim\ -DWHATIS=\/usr/bin/whatis\ -g -O2 -Wall -W -Wpointer-arith -Wwrite-strings -Wstrict-prototypes -Wshadow -Wformat-security -Wno-missing-field-initializers -MT lexgrog.o -MD -MP -MF .deps/lexgrog.Tpo -c -o lexgrog.o lexgrog.c lexgrog.c:3946: warning: 'input' defined but not used mv -f .deps/lexgrog.Tpo .deps/lexgrog.Po gcc -std=gnu99 -DHAVE_CONFIG_H -I. -I.. -I../include -I../intl -I../gnulib/lib -I../gnulib/lib -I../lib -I../libdb -DCONFIG_FILE=\/etc/man_db.conf\ -DLOCALEDIR=\/usr/share/locale\ -DAPROPOS=\/usr/bin/apropos\ -DAPROPOS_NAME=\apropos\ -DMAN=\/usr/bin/man\ -DMANCONV=\/usr/lib/man-db/manconv\ -DMANDB=\/usr/bin/mandb\ -DSOELIM=\/usr/bin/zsoelim\ -DWHATIS=\/usr/bin/whatis\ -g -O2 -Wall -W -Wpointer-arith -Wwrite-strings -Wstrict-prototypes -Wshadow -Wformat-security -Wno-missing-field-initializers -MT lexgrog_test.o -MD -MP -MF .deps/lexgrog_test.Tpo -c -o lexgrog_test.o lexgrog_test.c mv -f .deps/lexgrog_test.Tpo .deps/lexgrog_test.Po gcc -std=gnu99 -DHAVE_CONFIG_H -I. -I.. -I../include -I../intl -I../gnulib/lib -I../gnulib/lib -I../lib -I../libdb -DCONFIG_FILE=\/etc/man_db.conf\ -DLOCALEDIR=\/usr/share/locale\ -DAPROPOS=\/usr/bin/apropos\ -DAPROPOS_NAME=\apropos\ -DMAN=\/usr/bin/man\ -DMANCONV=\/usr/lib/man-db/manconv\ -DMANDB=\/usr/bin/mandb\ -DSOELIM=\/usr/bin/zsoelim\ -DWHATIS=\/usr/bin/whatis\ -g -O2 -Wall -W -Wpointer-arith -Wwrite-strings -Wstrict-prototypes -Wshadow -Wformat-security -Wno-missing-field-initializers -MT manconv.o -MD -MP -MF .deps/manconv.Tpo -c -o manconv.o manconv.c mv -f .deps/manconv.Tpo .deps/manconv.Po gcc -std=gnu99 -DHAVE_CONFIG_H -I. -I.. -I../include -I../intl -I../gnulib/lib -I../gnulib/lib -I../lib -I../libdb -DCONFIG_FILE=\/etc/man_db.conf\ -DLOCALEDIR=\/usr/share/locale\ -DAPROPOS=\/usr/bin/apropos\ -DAPROPOS_NAME=\apropos\ -DMAN=\/usr/bin/man\ -DMANCONV=\/usr/lib/man-db/manconv\ -DMANDB=\/usr/bin/mandb\ -DSOELIM=\/usr/bin/zsoelim\ -DWHATIS=\/usr/bin/whatis\ -g -O2 -Wall -W -Wpointer-arith -Wwrite-strings -Wstrict-prototypes -Wshadow -Wformat-security -Wno-missing-field-initializers -MT ult_src.o -MD -MP -MF .deps/ult_src.Tpo -c -o ult_src.o ult_src.c mv -f .deps/ult_src.Tpo .deps/ult_src.Po gcc -std=gnu99 -g -O2 -Wall -W -Wpointer-arith -Wwrite-strings -Wstrict-prototypes -Wshadow -Wformat-security -Wno-missing-field-initializers -Wl,--as-needed -o lexgrog compression.o descriptions.o encodings.o fake_security.o lexgrog.o lexgrog_test.o manconv.o ult_src.o util.o ../lib/libman.a ../gnulib/lib/libgnu.a -lz gcc -std=gnu99 -DHAVE_CONFIG_H -I. -I.. -I../include -I../intl -I../gnulib/lib -I../gnulib/lib -I../lib -I../libdb -DCONFIG_FILE=\/etc/man_db.conf\ -DLOCALEDIR=\/usr/share/locale\ -DAPROPOS=\/usr/bin/apropos\ -DAPROPOS_NAME
Re: man-db-2.5.5 never installed
I have complete log files of the entire step process of the unpack, configure, make and make check steps. I can show you as much of the logged process for each step as you want to see. The error is directly related to man.o. I have checked /usr/bin and none of the commands from man-db are there. man.c: In function 'make_roff_command': man.c:1510: error: 'TROFF' undeclared (first use in this function) man.c:1510: error: (Each undeclared identifier is reported only once man.c:1510: error: for each function it appears in.) man.c:1514: error: 'NROFF' undeclared (first use in this function) As everybody here knows, I am not very experienced LFS/BLFS user, but I remind having this same problem and the cause was that Groff package had not been properly installed. The reason: in Groff installation page, the first command is PAGE=paper_size ./configure --prefix=/usr I had not realized, during copy/paste, that the paper_size had to be defined (for me, A4, but for English speaking users, probably it is Letter. After properly recompiling an reistalling Groff, the compilation of Man-DB succeeded. I had the PAGE=letter ./configure --prefix=/usr but ran the steps for groff again and then ran the man-db stuff again and it worked this time. Thanks -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
pth-2.0.7 step in book different from...
blfs-book-svn-html-2009-12-14 chpater 8 pth-2.0.7 At the end of the make command, the last line on screen says: Now please type 'make test' to run a quick test suite. Hope it works. The book says run make check. -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: gpm help
On Thu, Dec 10, 2009 at 8:06 AM, akhiezer lf...@cruziero.com wrote: 20091209233643_MST: stosss stosss at gmail.com wrote: Solved see below On Thu, Dec 10, 2009 at 1:19 AM, stosss stosss at gmail.com wrote: stosss wrote: stosss wrote: Starting with a base LFS 6.5 system, I have compiled and installed GPM I have an IntelliMouse Optical USB and PS2 Compatible mouse . . MDEVICE=/dev/input/mice # I also tried /dev/mouse PROTOCOL=msc # I also tried ms+ GPMOPTS= # I am assuming something has to go in here but I don't know what. . . My current system is just LFS 6.5 with GPM and nothing more. . . checked and /dev/mouse is a link to /dev/input/mice. my mouse is a usb. The book said that usb mice should be /dev/input/mice. I have tried both MDEVICE=/dev/mouse and MDEVICE=/dev/input/mice. I have tried PROTOCOL=msc PROTOCOL=ms+ PROTOCOL=imps2 this one should be for a PS2 mouse but I have the mouse plugged into a usb port. Yes gpm is running. It is the last entry on the screen before the login prompt and when I ps-e I see it in the list. . . I had not apparently tried imps2 with /dev/input/mice it seems to make a difference if it is done with /dev/mouse which I had also tried. i don't understand that either because /dev/mouse is a link to /dev/input/mice. Does anyone know why a ps2 (imps2) mouse setting works with a usb mouse? Just to double-check: is the mouse definitely connected to a usb port on the pc, or does it go via a usb-to-ps2 adapter, into a ps2 port on the pc? I've got what sounds like exactly the same mouse here, on the system used to build lfs-6.5 plus gpm ( wget, links, and lynx) (per LFS-6.5 section '9.3. Rebooting the System'): the mouse has that same IntelliMouse(R) Optical USB and PS/2 Compatible printed on its underside; although, of course, it could be pertinently different hardware 'under the bonnet' to what you've got, given how things can differ across countries or even across versions within a country. The mouse here has a USB connector at the end of its cable, and that connector plugs into the usb port of a little usb-to-ps2 connector, which in turn has its (i.e. the adatper's) ps2 port connecting into a ps2 port on the back of the pc. Worked first-time here with config file: MDEVICE=/dev/mouse PROTOCOL=imps2 GPMOPTS= mine would not work when I had the above config but it works with the one below even though they both mean the same thing. MDEVICE=/dev/input/mice PROTOCOL=imps2 GPMOPTS= And /dev/mouse is a symlink to /dev/input/mice ; and the latter looks ok re perms, ownerships, nodes, c. Just thought it worth a double-check on that connector. I am using the mouse (apparently the same one you have) without the usb/ps2 adaptor. The usb plug is in a usb port. I guess it works with the imps2 protocol because it is a ps2 compatible mouse. -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: gpm help
On Thu, Dec 10, 2009 at 10:57 AM, akhiezer lf...@cruziero.com wrote: 20091210083518_-0500: stosss stosss at gmail.com wrote: On Thu, Dec 10, 2009 at 8:06 AM, akhiezer lf...@cruziero.com wrote: 20091209233643_MST: stosss stosss at gmail.com wrote: Solved see below On Thu, Dec 10, 2009 at 1:19 AM, stosss stosss at gmail.com wrote: stosss wrote: stosss wrote: Starting with a base LFS 6.5 system, I have compiled and installed GPM I have an IntelliMouse Optical USB and PS2 Compatible mouse . . MDEVICE=/dev/input/mice # I also tried /dev/mouse PROTOCOL=msc # I also tried ms+ GPMOPTS= # I am assuming something has to go in here but I don't know what. . . My current system is just LFS 6.5 with GPM and nothing more. . . checked and /dev/mouse is a link to /dev/input/mice. my mouse is a usb. The book said that usb mice should be /dev/input/mice. I have tried both MDEVICE=/dev/mouse and MDEVICE=/dev/input/mice. I have tried PROTOCOL=msc PROTOCOL=ms+ PROTOCOL=imps2 this one should be for a PS2 mouse but I have the mouse plugged into a usb port. Yes gpm is running. It is the last entry on the screen before the login prompt and when I ps-e I see it in the list. . . I had not apparently tried imps2 with /dev/input/mice it seems to make a difference if it is done with /dev/mouse which I had also tried. i don't understand that either because /dev/mouse is a link to /dev/input/mice. Does anyone know why a ps2 (imps2) mouse setting works with a usb mouse? Just to double-check: is the mouse definitely connected to a usb port on the pc, or does it go via a usb-to-ps2 adapter, into a ps2 port on the pc? I've got what sounds like exactly the same mouse here, on the system used to build lfs-6.5 plus gpm ( wget, links, and lynx) (per LFS-6.5 section '9.3. Rebooting the System'): the mouse has that same IntelliMouse(R) Optical USB and PS/2 Compatible printed on its underside; although, of course, it could be pertinently different hardware 'under the bonnet' to what you've got, given how things can differ across countries or even across versions within a country. The mouse here has a USB connector at the end of its cable, and that connector plugs into the usb port of a little usb-to-ps2 connector, which in turn has its (i.e. the adatper's) ps2 port connecting into a ps2 port on the back of the pc. Worked first-time here with config file: MDEVICE=/dev/mouse PROTOCOL=imps2 GPMOPTS= mine would not work when I had the above config but it works with the one below even though they both mean the same thing. MDEVICE=/dev/input/mice PROTOCOL=imps2 GPMOPTS= And /dev/mouse is a symlink to /dev/input/mice ; and the latter looks ok re perms, ownerships, nodes, c. Just thought it worth a double-check on that connector. I am using the mouse (apparently the same one you have) without the usb/ps2 adaptor. The usb plug is in a usb port. I guess it works with the imps2 protocol because it is a ps2 compatible mouse. OK. I don't know enough on the innards of the drivers c: tho' the likes of 'http://www.faqs.org/docs/Linux-mini/XFree86-Second-Mouse.html' (albeit an old ref) indicates that the software supports both sides (ps/2 usb) too. So maybe it's both the hardware and software than can take either role (ps/2 or usb). But why doesn't '/dev/mouse' work? If I use the adapter, then all is ok whether I use '/dev/mouse' or '/dev/input/mice'. And if I don't use the adapter, thus putting the mouse directly into a usb port on back of pc (cold booting in between), then everything still works ok whether I use '/dev/mouse' or '/dev/input/mice'. Protocol was 'imps2' throughout. And things verified by checking e.g.: 'ps auxwww|grep -i gpm' to see what '-m' value it was using; and grep -iE 'mouse|mice|imps|gpm' /var/log/*; and all looks ok each time. What do you get from 'ls -la /dev/mouse'? D'you get (date/time v.likely not same): lrwxrwxrwx 1 root root 10 2009-12-10 15:12 /dev/mouse - input/mice Does it end with *literally* ' - input/mice' (without the quotes)? And for 'ls -la /dev/input/mice'? D'you get (again, of course, date/time v.likely not same): crw-r- 1 root root 13, 63 2009-12-10 15:12 /dev/input/mice Unless something unusual in that output, that's about the end of my in-head knowledge on this; next step would be probly a google on why does /dev/input/mice work but /dev/mouse doesn't or so :| . Btw, the lfs-6.5 kernel here just has all of the mouse/usb/cc stuff built-in: they're not loaded as modules. Mine is set up the same as yours. I tried switching from /dev/input/mice to /dev/mouse and it worked this time. I don't know why it didn't the other time. It doesn't really matter now because it works. -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http
gpm help
Starting with a base LFS 6.5 system, I have compiled and installed GPM I have an IntelliMouse Optical USB and PS2 Compatible mouse I have tried several combinations in the config file and so far nothing appears to be working. I am also not sure If my config file is complete. MDEVICE=/dev/input/mice # I also tried /dev/mouse PROTOCOL=msc # I also tried ms+ GPMOPTS= # I am assuming something has to go in here but I don't know what. I have read the man page, searched with Google and found nothing to help me. Is GPM the best option that can provide mouse operation in a text terminal? My current system is just LFS 6.5 with GPM and nothing more. -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: gpm help
stosss wrote: stosss wrote: Starting with a base LFS 6.5 system, I have compiled and installed GPM I have an IntelliMouse Optical USB and PS2 Compatible mouse I have tried several combinations in the config file and so far nothing appears to be working. I am also not sure If my config file is complete. MDEVICE=/dev/input/mice # I also tried /dev/mouse PROTOCOL=msc # I also tried ms+ GPMOPTS= # I am assuming something has to go in here but I don't know what. I have read the man page, searched with Google and found nothing to help me. Is GPM the best option that can provide mouse operation in a text terminal? My current system is just LFS 6.5 with GPM and nothing more. Two things to check for. First go into the /dev directory and make sure a mouse device actually exists and set MDEVICE accordingly. Secondly, make sure that the gpm daemon is actually running. Also try setting PROTOCOL to imps2. Regards, Wayne. checked and /dev/mouse is a link to /dev/input/mice. my mouse is a usb. The book said that usb mice should be /dev/input/mice. I have tried both MDEVICE=/dev/mouse and MDEVICE=/dev/input/mice. I have tried PROTOCOL=msc PROTOCOL=ms+ PROTOCOL=imps2 this one should be for a PS2 mouse but I have the mouse plugged into a usb port. Yes gpm is running. It is the last entry on the screen before the login prompt and when I ps-e I see it in the list. I'm not sure, but you might want to check the kernel build options and see if there was a usb and or mouse option that needed to be set. Wayne. USB input usb_hid support is built into the kernel I found a test at: http://panuganty.tripod.com/debiantips/mouse.htm Do a cat on the device say '/dev/psaux' or /dev/mouse' or '/dev/input/mice' and then move your mouse. If you see bizarre looking characters on the screen, you got the right device. I tried it and got the weird stuff on the screen. I know MDEVICE=/dev/input/mice is right. I have tried for PROTOCOL= ms, msc, ms3, pnp, ms+, imps2 each time I changed /etc/sysconfig/mouse I reboot. -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: gpm help
Solved see below On Thu, Dec 10, 2009 at 1:19 AM, stosss sto...@gmail.com wrote: stosss wrote: stosss wrote: Starting with a base LFS 6.5 system, I have compiled and installed GPM I have an IntelliMouse Optical USB and PS2 Compatible mouse I have tried several combinations in the config file and so far nothing appears to be working. I am also not sure If my config file is complete. MDEVICE=/dev/input/mice # I also tried /dev/mouse PROTOCOL=msc # I also tried ms+ GPMOPTS= # I am assuming something has to go in here but I don't know what. I have read the man page, searched with Google and found nothing to help me. Is GPM the best option that can provide mouse operation in a text terminal? My current system is just LFS 6.5 with GPM and nothing more. Two things to check for. First go into the /dev directory and make sure a mouse device actually exists and set MDEVICE accordingly. Secondly, make sure that the gpm daemon is actually running. Also try setting PROTOCOL to imps2. Regards, Wayne. checked and /dev/mouse is a link to /dev/input/mice. my mouse is a usb. The book said that usb mice should be /dev/input/mice. I have tried both MDEVICE=/dev/mouse and MDEVICE=/dev/input/mice. I have tried PROTOCOL=msc PROTOCOL=ms+ PROTOCOL=imps2 this one should be for a PS2 mouse but I have the mouse plugged into a usb port. Yes gpm is running. It is the last entry on the screen before the login prompt and when I ps-e I see it in the list. I'm not sure, but you might want to check the kernel build options and see if there was a usb and or mouse option that needed to be set. Wayne. USB input usb_hid support is built into the kernel I found a test at: http://panuganty.tripod.com/debiantips/mouse.htm Do a cat on the device say '/dev/psaux' or /dev/mouse' or '/dev/input/mice' and then move your mouse. If you see bizarre looking characters on the screen, you got the right device. I tried it and got the weird stuff on the screen. I know MDEVICE=/dev/input/mice is right. I have tried for PROTOCOL= ms, msc, ms3, pnp, ms+, imps2 each time I changed /etc/sysconfig/mouse I reboot. I had not apparently tried imps2 with /dev/input/mice it seems to make a difference if it is done with /dev/mouse which I had also tried. i don't understand that either because /dev/mouse is a link to /dev/input/mice. Does anyone know why a ps2 (imps2) mouse setting works with a usb mouse? -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
BLSF chapter 3 bash shell scripts, question about syntax
I am copying the files in the chapter stated in the subject. sometimes I see ] ; and sometimes ]; does it matter if there is a space or not? -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
LFS is at 6.5 BLFS is at 6.3 Why?
Why does LFS stay so far ahead of BLFS? What is the point of building the newest LFS if the BLFS files are older and probably won't work or would be replacing newer versions of apps with older versions? There is a note on the BLFS that says in one or two months a new BLFS will be released. There is no date as to when that was put there or a target date for release. What is the target date for that one or two months? Use SVN if you are using LFS 6.4 what about LFS 6.5? It looks like the smart thing to do to avoid problems would be to build LFS 6.4 and then BLFS SVN/6.4 which is the reason for my orginial question in the subject. -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: LFS is at 6.5 BLFS is at 6.3 Why?
I think one thing is not in the book : the answer to the question why is this package not in the book/why is this version so old/why doesn't the book evolve any faster Come on, guys, what do you think you are dealing with ? This is an entirely free, cooperative work. Nothing advances if noone provides work for it to move on. So the correct answer to those questions should be : move your ass, you bl...y bas...rd !!!. I just got to the point of doing BLFS. I know the project is volunteer. All the books say use whats recommended in the book. Why release something just because it is ready when the next part (the more important part) is not. I was just asking straight forward questions. In response to your sh_ty attitude... FOAD!!! -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: LFS is at 6.5 BLFS is at 6.3 Why?
This just shows that you missed the point of the LFS project : I understand the point of the LFS book And my attitude is not shitty as you say, Yes it is! Hey, guys, your book sucks, if I did it myself, it would be much better, faster... etc.. That was how you took my post that was not my intention. To answer your initial question, if you want a more up to date distribution instruction set, you may want to look at the CBLFS project. Do you mean CLFS? -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
