[blfs-dev] Two difficulties (one in all versions)
Fernando de Oliveira
famobr at yahoo.com.br
Thu Aug 22 05:44:58 PDT 2013
Em 21-08-2013 19:18, Bruce Dubbs escreveu:
> Fernando de Oliveira wrote:
>> Did not know if sending here, to lfs -dev or to blfs -support.
>> 1. Happened with lfs-7.2,7.3 (both svn) and now with 7.4-rc1.
>> ... as host), after logout and umount, had to reboot the system
>> $ grep tty /etc/group
>> $ grep /dev/pts /etc/fstab
>> devpts /dev/pts devpts gid=4,mode=620 0 0
>> But I was mounting and chrooting with gid 5, as per the book's instructions.
>> Now, I have changed both to gid 5, to conform with the new versions, and
>> the problem disappeared. Of course, had to change tape's gid to 4.
> I'm glad you figured it out. We don't change this type of thing lightly
> and there was a fair amount of discussion back when it was done.
I remember (not details, though), but never thought It would affect me,
>> 2. Happened, perhaps with all versions.
>> Every time I try to create compressdoc with cat command, I obtain a
>> corrupted unusable script. Then, use vim, instead, and copy/paste.
> I don't use compressdoc. I have:
> $ du -sh /opt/OpenJDK-220.127.116.11/man /opt/kde-4.10.3/share/man \
> /opt/xorg /share/man /opt/qt-4.8.4/share/man /usr/share/man
> 1.8M /opt/OpenJDK-18.104.22.168/man
> 228K /opt/kde-4.10.3/share/man
> 17M /opt/xorg/share/man
> 16K /opt/qt-4.8.4/share/man
> 63M /usr/share/man
> That's about 2.1M on a 10G partition or about 0.02% How much space are
Yes, it is not very much. Just followed the "3. After LFS Configuration
Issues", without much thinking, after doing any times. It is a good
point. I will stop using it, at the end, if you do not do it after each
package update, could end with two versions, old compressed, new
> That said, there may be an issue with the size of the copy buffer. When
> I try to select everything, I get a file of 10523 bytes, but when I do
> it in screen size blocks, the file is not corrupted and is 16870 bytes.
> I would do an md5sum on the result, but a user's result may be
> different if a blank line is added or missing from multiple copy/paste
> Note too that when we are doing a copy from a browser, that it needs to
> remove html, so it may be a browser issue.
It was not a big deal, but was worth mentioning. Now, I have better
understanding; before, it was a mystery.
Again, perhaps, a comment or note about the issue? This one, I think I
can do. For example, just slight rephrasing:
"If you would prefer to download the file instead of creating it by
typing or cut-and-pasting ..."
"Using cut-and-pasting, corrupted script creation has been reported. For
this or if you would prefer to download the file, instead, ..."
Anyway, thanks for the explanation.
More information about the blfs-dev