Re: [blfs-support] Troubles Building NSS-3.15.3 [Corrected Major Error]
Le 05/12/2013 19:21, Dan McGhee a écrit : On 12/05/2013 11:20 AM, Dan McGhee wrote: This build has failed three times for me. Here is the applicable portion of the build log: [What I originally included was an excerpt from my error log. I apologize for the mistake. [...] 1420 Fatal error: can't create Linux3.8_x86_64_glibc_PTH_64_OPT.OBJ/pk11cert.o: No such file or directory [...] This means the directory Linux3.8_x86_64_glibc_PTH_64_OPT.OBJ does not exist. 1445 make[2]: *** [Linux3.8_x86_64_glibc_PTH_64_OPT.OBJ/pk11cert.o] Error 2 1446 make[2]: *** Waiting for unfinished jobs 1447 pk11load.c: In function 'SECMOD_UnloadModule': [...] You are using job parallelization, aren't you? Delete the build directory and start anew without the -j flag. ISTR job parallelization is broken for NSS. And the first error really looks like some directory, which should have been created before the long statement, had not... The first time it failed, it failed because it couldn't make the directory. Now it's an object file--as was the second failure. Now I am in need of help, because I don't know how to translate the long statements. Regards Pierre -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-support] problem using BS or DEL key
On Fri, Dec 6, 2013 at 1:04 AM, Ken Moffat zarniwh...@ntlworld.com wrote: Forgot to attach it the first time, and when I did it bounced (too big, whoops!). So here's the third attempt, using xz to compress it from 177K to 7K. sigh/ Thanks and sorry for confusion! I had no Unicode initially, but added it after initial comments. However adding Unicode font didn't help. I'll try your suggestions tomorrow. Anyway I've already found troubling news re. my Intel Atom GPU: Intel D2550 Cedarview (GMA3600) has PowerVR 545 graphics core. And its problem is described here: https://gist.github.com/Aissen/2925633 Now I understand why I can't get grub and kernel to get a higher resolution... At least it explains a difference in behaviour between 2 different Atom motherboards (old one has D510). That's very old news and I think you're getting side-tracked. As I've already mentioned I have a Cedar Trail motherboard and it's now working OK for me; the crappy graphics chip shouldn't be an issue on the console. Richard -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-support] du on / produces errors from /proc
Le 05/12/2013 18:18, Richard Melville a ?crit : Does anybody know what causes the following:- du: cannot access '/proc/602/task/602/fd/4': No such file or directory du: cannot access '/proc/602/task/602/fdinfo/4': No such file or directory du: cannot access '/proc/602/fd/4': No such file or directory du: cannot access '/proc/602/fdinfo/4': No such file or directory What were you doing? Building some package? What is the command which generated that output? Regards Pierre I was just checking disk space with du -sh / as root. That was the only output apart from the requested disk space. Richard -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-support] du on / produces errors from /proc
Le 06/12/2013 10:56, Richard Melville a écrit : Le 05/12/2013 18:18, Richard Melville a ?crit : Does anybody know what causes the following:- du: cannot access '/proc/602/task/602/fd/4': No such file or directory du: cannot access '/proc/602/task/602/fdinfo/4': No such file or directory du: cannot access '/proc/602/fd/4': No such file or directory du: cannot access '/proc/602/fdinfo/4': No such file or directory What were you doing? Building some package? What is the command which generated that output? Regards Pierre I was just checking disk space with du -sh / as root. That was the only output apart from the requested disk space. Richard /proc/602 is a system directory associated to the process number 602. I guess du first finds 602 inside proc when listing the directory /proc, then tries to open it. If 602 is a transcient process (that is it runs for a short time), it may happen that it has disappeared before the second time it is accessed. You may add --exclude=/proc to the command linen but I think it is harmless. Regards Pierre -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-support] du on / produces errors from /proc
Date: Fri, 06 Dec 2013 11:35:35 +0100 From: Pierre Labastie pierre.labas...@neuf.fr To: BLFS Support List blfs-support@linuxfromscratch.org Subject: Re: [blfs-support] du on / produces errors from /proc Le 06/12/2013 10:56, Richard Melville a écrit : Le 05/12/2013 18:18, Richard Melville a ?crit : Does anybody know what causes the following:- du: cannot access '/proc/602/task/602/fd/4': No such file or directory du: cannot access '/proc/602/task/602/fdinfo/4': No such file or directory du: cannot access '/proc/602/fd/4': No such file or directory du: cannot access '/proc/602/fdinfo/4': No such file or directory What were you doing? Building some package? What is the command which generated that output? Regards Pierre I was just checking disk space with du -sh / as root. That was the only output apart from the requested disk space. Richard /proc/602 is a system directory associated to the process number 602. I guess du first finds 602 inside proc when listing the directory /proc, then tries to open it. If 602 is a transcient process (that is it runs for a short time), it may happen that it has disappeared before the second time it is accessed. You may add --exclude=/proc to the command linen but I think it is harmless. - and/or use the '-x' flag if it's really just the '/' partition that you want info for. If you're wanting info on the full filesys tree, then perhaps something like 'df [-a] -hP --total'; as for 'du', there are various command-line options to adjust the format to suit what you want. akh -- -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-support] problem using BS or DEL key
On Thu, Dec 5, 2013 at 11:01 PM, Ken Moffat zarniwh...@ntlworld.com wrote: I still think my suggestion of checking every key will identify if any of the keys are being garbled in the kernel, and therefore if this is a kernel _input_ problem. But here is an alternative train of thought : When you trigger the garbage, is it really there, or only in the screen output ? Start a command with '#' so that it is treated as a comment, type, do whatever you need to so that the spurious garbage appears, then press enter. And make a written note of exactly what you typed, and a guide to what appeared and where it was on the line, so that you can repeat the test. 1. Typed: # k kk 2. Then deleted 2 speces between kkk-s with BS 3. white blocks appeared on the same line till the end of the screen Then key enter again : does the garbage scroll up, so that the current line is empty apart from the prompt ? It does scroll up Then key the up-arrow once to see the last line of history - is the garbage there in the history ? No, it's not there (not in bash history) If the garbage is only on the screen then I guess it _is_ a kernel problem, but in the _video_ driver (i915 I suppose, but maybe you compiled in vga). I will rebuild kernel Your LatArCyrHeb font has two, possibly three, characters which match a white square. If you manage to prove that it is a kernel video problem, can you please loadkeys LatGrkCyr-8x16 and repeat the test. I'm guessing you will get a capital T with a comma below it (either U+021A or, in that font, U+0162), or a capital U with an acute accent (U+00DA), or else a capital U with a breve (U+016C). Knowing what appears might be useful if this is a bug in a video driver. I'll attach the text listing of that font - I'm guessing it is one of character positions 210, 212, or 216. Do you mean setfont instead of loadkeys? Screen font changed, but white block is still the same while using LatGrkCyr-8x16. If I select viscii10-8x16 I can see blinking white letter U with diacritics on a grey background. It is a last letter in showconsolefont. If Iset lat1-16 I see y (U+00FF) If it is a video-driver problem, please attach the relevant part of your kernel config I will recompile with: Graphics support --- * Intel GMA5/600 KMS Framebuffer [*] Intel GMA3600/3650 support (Experimental) And, which kernel is this ? I'm going to build a latest stable from kernel.org 3.10.22 /alexey -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-support] problem using BS or DEL key
On Fri, Dec 06, 2013 at 02:26:24PM +0100, Alexey Orishko wrote: On Thu, Dec 5, 2013 at 11:01 PM, Ken Moffat zarniwh...@ntlworld.com wrote: I still think my suggestion of checking every key will identify if any of the keys are being garbled in the kernel, and therefore if this is a kernel _input_ problem. But here is an alternative train of thought : When you trigger the garbage, is it really there, or only in the screen output ? Start a command with '#' so that it is treated as a comment, type, do whatever you need to so that the spurious garbage appears, then press enter. And make a written note of exactly what you typed, and a guide to what appeared and where it was on the line, so that you can repeat the test. 1. Typed: # k kk 2. Then deleted 2 speces between kkk-s with BS 3. white blocks appeared on the same line till the end of the screen Then key enter again : does the garbage scroll up, so that the current line is empty apart from the prompt ? It does scroll up Then key the up-arrow once to see the last line of history - is the garbage there in the history ? No, it's not there (not in bash history) If the garbage is only on the screen then I guess it _is_ a kernel problem, but in the _video_ driver (i915 I suppose, but maybe you compiled in vga). I will rebuild kernel Yes, based on what you said about gma500 then I guess that should fix it. Your LatArCyrHeb font has two, possibly three, characters which match a white square. If you manage to prove that it is a kernel video problem, can you please loadkeys LatGrkCyr-8x16 and repeat the test. I'm guessing you will get a capital T with a comma below it (either U+021A or, in that font, U+0162), or a capital U with an acute accent (U+00DA), or else a capital U with a breve (U+016C). Knowing what appears might be useful if this is a bug in a video driver. I'll attach the text listing of that font - I'm guessing it is one of character positions 210, 212, or 216. Do you mean setfont instead of loadkeys? Screen font changed, but white block is still the same while using LatGrkCyr-8x16. If I select viscii10-8x16 I can see blinking white letter U with diacritics on a grey background. It is a last letter in showconsolefont. If Iset lat1-16 I see y (U+00FF) Yes, I did mean setfont - sorry. If you change to the gma500 driver, I hope it will fix this. If it is a video-driver problem, please attach the relevant part of your kernel config I will recompile with: Graphics support --- * Intel GMA5/600 KMS Framebuffer [*] Intel GMA3600/3650 support (Experimental) And, which kernel is this ? I'm going to build a latest stable from kernel.org 3.10.22 /alexey Good luck - I guess that compiling a kernel on an atom will be slow. ĸen -- das eine Mal als Tragödie, dieses Mal als Farce -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-support] Troubles Building NSS-3.15.3 [Corrected Major Error]
On 12/06/2013 02:51 AM, Pierre Labastie wrote: Le 05/12/2013 19:21, Dan McGhee a écrit : On 12/05/2013 11:20 AM, Dan McGhee wrote: This build has failed three times for me. Here is the applicable portion of the build log: [What I originally included was an excerpt from my error log. I apologize for the mistake. [...] 1420 Fatal error: can't create Linux3.8_x86_64_glibc_PTH_64_OPT.OBJ/pk11cert.o: No such file or directory [...] This means the directory Linux3.8_x86_64_glibc_PTH_64_OPT.OBJ does not exist. 1445 make[2]: *** [Linux3.8_x86_64_glibc_PTH_64_OPT.OBJ/pk11cert.o] Error 2 1446 make[2]: *** Waiting for unfinished jobs 1447 pk11load.c: In function 'SECMOD_UnloadModule': [...] You are using job parallelization, aren't you? Delete the build directory and start anew without the -j flag. ISTR job parallelization is broken for NSS. And the first error really looks like some directory, which should have been created before the long statement, had not... The first time it failed, it failed because it couldn't make the directory. Now it's an object file--as was the second failure. Now I am in need of help, because I don't know how to translate the long statements. Regards Pierre For some reason I was compiling NSS in my Ubuntu host system using the chroot environment. Pierre's reference to a parallel build, and since I wasn't trying to do one, got me looking. So there's one thing. But I could not get NSS to build in my new LFS system whether in a terminal environment or graphics environment. The build kept nagging me with: /bin/mkdir: can't create Linux3.10_x86_64_glibc_PTH_64_OPT.OBJ/some name.o: No such file or directory Since I use the Package Users' system, I've learned that this statement is usually a permissions situation and 99% of the time the referenced directory or file already exists. But this situation had me hornswoggled because all the files and directories in the build environment belonged to Mr. nss-3.15.3. The only thing I could come up with was that the build was trying to read a file somewhere that gave read access to only one user. There is only one user, outside of my home directory, for which that is true on my system and that is 'root.' So, I built NSS as root, which I really don't like to do, and it compiled perfectly. To keep my system together and before I ran the 'install' commands, I did chown -R for the build tree. All is well now, except that I just can't figure out what stopped me from building it as an unprivileged user. Dan -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-support] Troubles Building NSS-3.15.3 [Corrected Major Error]
Le 06/12/2013 18:12, Dan McGhee a écrit : On 12/06/2013 02:51 AM, Pierre Labastie wrote: Le 05/12/2013 19:21, Dan McGhee a écrit : On 12/05/2013 11:20 AM, Dan McGhee wrote: This build has failed three times for me. Here is the applicable portion of the build log: [What I originally included was an excerpt from my error log. I apologize for the mistake. [...] 1420 Fatal error: can't create Linux3.8_x86_64_glibc_PTH_64_OPT.OBJ/pk11cert.o: No such file or directory [...] This means the directory Linux3.8_x86_64_glibc_PTH_64_OPT.OBJ does not exist. 1445 make[2]: *** [Linux3.8_x86_64_glibc_PTH_64_OPT.OBJ/pk11cert.o] Error 2 1446 make[2]: *** Waiting for unfinished jobs 1447 pk11load.c: In function 'SECMOD_UnloadModule': [...] You are using job parallelization, aren't you? Delete the build directory and start anew without the -j flag. ISTR job parallelization is broken for NSS. And the first error really looks like some directory, which should have been created before the long statement, had not... The first time it failed, it failed because it couldn't make the directory. Now it's an object file--as was the second failure. Now I am in need of help, because I don't know how to translate the long statements. Regards Pierre For some reason I was compiling NSS in my Ubuntu host system using the chroot environment. Pierre's reference to a parallel build, and since I wasn't trying to do one, got me looking. Sorry if I was wrong: I read [Linux3.8_x86_64_glibc_PTH_64_OPT.OBJ/pk11cert.o] Error 2 1446 make[2]: *** Waiting for unfinished jobs And I thought that make wouldn't have to wait for unfinished jobs if not doing a parallel build. Anyway, glad you found how to compile it. Regards, Pierre -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-support] Troubles Building NSS-3.15.3 [Corrected Major Error]
On 12/06/2013 11:14 AM, Pierre Labastie wrote:
Le 06/12/2013 18:12, Dan McGhee a écrit :
For some reason I was compiling NSS in my Ubuntu host system using the
chroot environment. Pierre's reference to a parallel build, and since
I wasn't trying to do one, got me looking.
Sorry if I was wrong: I read
[Linux3.8_x86_64_glibc_PTH_64_OPT.OBJ/pk11cert.o] Error 2
1446 make[2]: *** Waiting for unfinished jobs
And I thought that make wouldn't have to wait for unfinished jobs if not
doing a parallel build. Anyway, glad you found how to
compile it.
Pierre, you weren't wrong. What you read is correct. But what I
learned is that with the uname options used, when I tried to compile
using 'chroot' in Ubuntu, NSS picked up on the 3.8.xxx kernel Ubuntu
uses. When I tried to compile in {,B}LFS the error changed to
Linux3.10_x86_64 etc. but remained the same. Make would still exit
with waiting for unfinished jobs. And the first culprit was always
can't make the file. That lead me to the permissions angle. That's
why this whole thing was confusing.
Maybe someday, I'll have the time and energy to slog through the build
process and try to find out why this happened. Although I'm happy with
the outcome, I don't like to build as root.
Dan
--
http://linuxfromscratch.org/mailman/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
Re: [blfs-support] problem using BS or DEL key
On Dec 6, 2013, at 10:51 AM, Ken Moffat wrote: Good luck - I guess that compiling a kernel on an atom will be slow. ĸen All hail the power of cross compilers with faster machines! Hopefully it does get fixed so this thread will help someone. Lots of information here. Sincerely, William Harrington -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-support] Troubles Building NSS-3.15.3 [Corrected Major Error]
Dan McGhee wrote: Maybe someday, I'll have the time and energy to slog through the build process and try to find out why this happened. Although I'm happy with the outcome, I don't like to build as root. You shouldn't need to build as root, but you do need to install as root. There is something wrong with the scripts you are using. The following (nss-3.15.1) works fine for me as a normal user: patch -Np1 -i $DIR/$PROGRAM-standalone-2.patch cd nss make BUILD_OPT=1 \ NSPR_INCLUDE_DIR=/usr/include/nspr \ USE_SYSTEM_ZLIB=1 \ ZLIB_LIBS=-lz \ USE_64=1 \ NSS_USE_SYSTEM_SQLITE=1 where DIR and PROGRAM are defined earlier. -- Bruce -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-support] Troubles Building NSS-3.15.3 [Corrected Major Error]
On 12/06/2013 01:19 PM, Bruce Dubbs wrote: Dan McGhee wrote: Maybe someday, I'll have the time and energy to slog through the build process and try to find out why this happened. Although I'm happy with the outcome, I don't like to build as root. You shouldn't need to build as root, but you do need to install as root. There is something wrong with the scripts you are using. The following (nss-3.15.1) works fine for me as a normal user: patch -Np1 -i $DIR/$PROGRAM-standalone-2.patch cd nss make BUILD_OPT=1 \ NSPR_INCLUDE_DIR=/usr/include/nspr \ USE_SYSTEM_ZLIB=1 \ ZLIB_LIBS=-lz \ USE_64=1 \ NSS_USE_SYSTEM_SQLITE=1 where DIR and PROGRAM are defined earlier. -- Bruce I use the Package Users system and this is the first and only time that this situation has developed. You're right about something being amiss in the scripts, but more precisely maybe the path of a package user. It's set-up to find wrappers for make. In this system, permissions is the biggy. What I want to learn is, What in the build tree's permissions causes the wraper scripts to fail when working in only the build tree? One test I didn't run because I wanted to get to the Xulrunner build is I didn't build as me. My path is different than a package user's. The only thing I've ever had trouble with in this system is deciding which things need to be SUID. Then there's xorg that also needs to be owned by root *and* run SUID. Dan -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-support] Troubles Building NSS-3.15.3 [Corrected Major Error]
Dan McGhee wrote: The only thing I've ever had trouble with in this system is deciding which things need to be SUID. Then there's xorg that also needs to be owned by root *and* run SUID. This is what I have: $ find `echo $PATH|tr : ' '` -type f -perm -u=s -ls -rwsrwxr-x 1 root root73967 Oct 24 08:02 /bin/ping -rwsr-xr-x 1 root root36153 Oct 24 08:02 /bin/umount -rwsr-xr-x 1 root root47774 Oct 24 08:02 /bin/mount -rwsrwxr-x 1 root root67902 Oct 24 08:02 /bin/ping6 -rwsr-xr-x 1 root root71065 Oct 24 08:02 /bin/passwd -rwsr-xr-x 1 root root63386 Oct 24 08:02 /bin/su -rwsr-xr-x 1 root root37425 Oct 24 08:03 /usr/bin/expiry -rwsr-xr-x 1 root root 150805 Oct 24 08:03 /usr/bin/sudo -r-sr-s--- 1 root wireshark 328098 Nov 8 12:54 /usr/bin/dumpcap -rwsr-xr-x 1 root root54180 Oct 24 08:03 /usr/bin/chsh -rwsr-sr-x 1 atd atd 55989 Oct 24 08:03 /usr/bin/at -rwsr-xr-x 1 root root26485 Oct 24 08:03 /usr/bin/pkexec -rwsr-xr-x 1 root root 981824 Oct 24 08:03 /usr/bin/vmware-mount -rwsrwxr-x 1 root root63194 Oct 24 08:03 /usr/bin/rlogin -rwsrwxr-x 1 root root66959 Oct 24 08:03 /usr/bin/rcp -rwsrwxr-x 1 root root57372 Oct 24 08:03 /usr/bin/rsh -rwsr-xr-x 1 root root55806 Oct 24 08:03 /usr/bin/chfn -r-sr-s--- 1 root wireshark 1356907 Nov 8 12:54 /usr/bin/tshark -rwsr-xr-x 1 root root80722 Oct 24 08:03 /usr/bin/gpasswd -rwsr-xr-x 1 root root42083 Oct 24 08:03 /usr/bin/newgrp -rwsr-xr-x 1 root root 383100 Oct 24 08:03 /usr/bin/screen-4.0.3 -rwsr-xr-x 1 root root63931 Oct 24 08:03 /usr/bin/chage -rwsr-xr-x 1 root root22629 Oct 24 16:28 /opt/kde/bin/kwrited -rwsr-xr-x 1 root root 12629202 Sep 13 12:32 /opt/xorg/bin/Xorg -r-s--x--x 1 root root 118827 Oct 24 08:02 /sbin/mount.nfs -rwsr-xr-x 1 root root 1075712 Sep 29 14:19 /usr/sbin/vmware-authd find `echo $PATH|tr : ' '` -type f -perm -g=s -ls -r-sr-s--- 1 root wireshark 328098 Nov 8 12:54 /usr/bin/dumpcap -rwxr-sr-x 1 root tty 30709 Oct 24 08:03 /usr/bin/wall -rwsr-sr-x 1 atd atd 55989 Oct 24 08:03 /usr/bin/at -r-sr-s--- 1 root wireshark 1356907 Nov 8 12:54 /usr/bin/tshark -rwxr-sr-x 1 root postdrop 876569 Sep 9 16:23 /usr/sbin/postqueue -rwxr-sr-x 1 root postdrop 823343 Sep 9 16:23 /usr/sbin/postdrop -- Bruce -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-support] problem using BS or DEL key
On Fri, Dec 6, 2013 at 7:02 PM, William Harrington kb0...@berzerkula.org wrote: Good luck - I guess that compiling a kernel on an atom will be slow. ĸen All hail the power of cross compilers with faster machines! I'll give it a try. Hopefully it does get fixed so this thread will help someone. Lots of information here. Finally, folks! I've recompiled and installed a new kernel with Graphics support --- * Intel GMA5/600 KMS Framebuffer [*] Intel GMA3600/3650 support (Experimental) and even got nice penguins during kernel boot :-) Screen resolution is also increased from vga. I don't see any garbage on the screen while deleting symbols with BS/DEL. Next time I would know to check hw thoroughly instead of trusting Intel with gpus :-) Thanks everyone for pointing me in the right direction cheers, alexey -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
[blfs-support] Ways to convert a .doc to something more civil.
Hi all! Is there a way to convert .doc documents to something else (preferably PDF) WITHOUT using *Office? The thing is that I have moved to new harware, rebuilt most of (B)LFS, but would want to read these bunch of documents without first having to spend the entire weekend hacking OpenOffice. It has been 3 or 4 years since I last built it and I remember it not being a breeze. BTW, this e-mail is not signed because of a mixup with keys when I migrated to the new machine. I'll get them when I get back home for Christmas. I also forgot my SSL certificate files so now I can't really SSL around the net - at least untill I rebuild them. I *really* hope I remembered to bring the PGP keys for various packages I spent years collecting. Have to check that in the morning. -- You don't need an AI for a robot uprising. Humans will do just fine. -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-support] Ways to convert a .doc to something more civil.
On 12/06/2013 10:30 PM, Aleksandar Kuktin wrote: Hi all! Is there a way to convert .doc documents to something else (preferably PDF) WITHOUT using *Office? The thing is that I have moved to new harware, rebuilt most of (B)LFS, but would want to read these bunch of documents without first having to spend the entire weekend hacking OpenOffice. It has been 3 or 4 years since I last built it and I remember it not being a breeze. BTW, this e-mail is not signed because of a mixup with keys when I migrated to the new machine. I'll get them when I get back home for Christmas. I also forgot my SSL certificate files so now I can't really SSL around the net - at least untill I rebuild them. I *really* hope I remembered to bring the PGP keys for various packages I spent years collecting. Have to check that in the morning. You could use AbiWord if you don't want to build entire Libreoffce. But it seems that wv package (available in BLFS) could help you do what you want. See http://wvware.sourceforge.net/ wv Utilities. They recommend using abiword executable though. -- Note: My last name is not Krejzi. -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-support] Ways to convert a .doc to something more civil.
On Fri, 06 Dec 2013 22:37:57 +0100 Armin K. kre...@email.com wrote: You could use AbiWord if you don't want to build entire Libreoffce. But it seems that wv package (available in BLFS) could help you do what you want. See http://wvware.sourceforge.net/ wv Utilities. They recommend using abiword executable though. Okay, I got it. I love the font AbiWord is using by default. A couple of things needed a couple of patches. I'll push them to the list tomorrow, it's late now. -- You don't need an AI for a robot uprising. Humans will do just fine. -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
[blfs-support] Samba Daemons smbd nmbd winbind Don't Start
Howdy experts, On the road to installing XFCE, I'm trying to install libsoup-2.44.2. The BLFS book has an option for Samba-4.12 (ntlm_auth is required to run the test suite). to run the tests. I've successfully installed Samba (as well as the other suggested options) and installed the blfs-bootscripts-20131023 install scripts to start the daemons. After installing the above stuff I rebooted and watched the progress of linux booting up. Each of the daemons smbd, nmbd and winding failed to install. Any clues as to what's going wrong? Alan -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-support] Samba Daemons smbd nmbd winbind Don't Start
Alan Feuerbacher wrote: Howdy experts, On the road to installing XFCE, I'm trying to install libsoup-2.44.2. The BLFS book has an option for Samba-4.12 (ntlm_auth is required to run the test suite). to run the tests. I've successfully installed Samba (as well as the other suggested options) and installed the blfs-bootscripts-20131023 install scripts to start the daemons. After installing the above stuff I rebooted and watched the progress of linux booting up. Each of the daemons smbd, nmbd and winding failed to install. Any clues as to what's going wrong? failed to install is a little short on information we can use to help. -- Bruce -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
