but also with the hosts's version. We expect
GRUB to boot not only LFS, but also a host distro. If a host distro
uses a new ext3 filesystem, we have a big problem.
--
Alexander E. Patrakov
--
http://linuxfromscratch.org/mailman/listinfo/lfs-dev
FAQ: http://www.linuxfromscratch.org/faq/
Unsu
2008/3/19, Bruce Dubbs <[EMAIL PROTECTED]>:
> What distros use the new version of e2fsprogs? What boot loader do
> those distro's use?
Debian Lenny. It offers a choice among a patched version of Grub
Legacy, LILO, and GRUB2.
--
Alexander E. Patrakov
--
http://linuxfromsc
ur
own instructions for bin86 and LILO.
--
Alexander E. Patrakov
--
http://linuxfromscratch.org/mailman/listinfo/lfs-dev
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page
latest distros.
--
Alexander E. Patrakov
--
http://linuxfromscratch.org/mailman/listinfo/lfs-dev
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page
this "discouraging" attitude, package management will never become part of
the LFS book.
--
Alexander E. Patrakov
--
http://linuxfromscratch.org/mailman/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
Knoppix (but the latest
version is available only as a huge DVD) and Zenwalk (Slackware-based,
and thus too buggy, especially when it comes to non-English language
support). Any other alternatives?
--
Alexander E. Patrakov
--
http://linuxfromscratch.org/mailman/listinfo/lfs-dev
FAQ:
good work, e.g., by
building dependencies of the MOC player (or any other useful package), see
http://moc.daper.net/links .
--
Alexander E. Patrakov
--
http://linuxfromscratch.org/mailman/listinfo/lfs-dev
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page
d be quite
appropriate.
+1.
--
Alexander E. Patrakov
--- perl-5.8.8.orig/lib/ExtUtils/MM_Unix.pm
+++ perl-5.8.8/lib/ExtUtils/MM_Unix.pm
@@ -20,7 +20,7 @@
use ExtUtils::MakeMaker qw($Verbose neatvalue);
-$VERSION = '1.50';
+$VERSION = '1.50_01';
require ExtUtils::MM_An
just a
> guide to building a linux system?
This, by itself, looks right. Let's see if the book and our resources can bear
this.
--
Alexander E. Patrakov
--
http://linuxfromscratch.org/mailman/listinfo/lfs-dev
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page
Libblkid is easier to build.
--
Alexander E. Patrakov
--
http://linuxfromscratch.org/mailman/listinfo/lfs-dev
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page
ling a boot loader is not one of such steps. Even
more: various non_ext2-fsprogs don't actually belong there.
--
Alexander E. Patrakov
--
http://linuxfromscratch.org/mailman/listinfo/lfs-dev
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page
Dan Nicholson wrote:
> You really need gawk, not mawk.
Then please add gawk and bison in Chapter 5 before binutils, to accomodate
Debian-based LiveCDs and PCLinuxOS, respectively.
--
Alexander E. Patrakov
--
http://linuxfromscratch.org/mailman/listinfo/lfs-dev
FAQ: h
Dan Nicholson wrote:
> On Thu, Apr 3, 2008 at 8:15 PM, Alexander E. Patrakov
> <[EMAIL PROTECTED]> wrote:
>> Dan Nicholson wrote:
>> > You really need gawk, not mawk.
>>
>> Then please add gawk and bison in Chapter 5 before binutils, to accomodate
Dan Nicholson wrote:
> On Fri, Apr 4, 2008 at 7:28 AM, Alexander E. Patrakov
>> For a regular distro, I would agree. For a third-party LiveCD, I disagree.
>
> I still don't think instructions should be special for this situation.
> If you chose a host that doesn&
LFS and subsequent packages to a different machine.
--
Alexander E. Patrakov
--
http://linuxfromscratch.org/mailman/listinfo/lfs-dev
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page
hild into water and say "he learns swimming" (bad joke:
I can't swim). No, learning must be gradual, the reader must see a trouble-free
book first and _then_ experiment.
--
Alexander E. Patrakov
--
http://linuxfromscratch.org/mailman/listinfo/lfs-dev
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page
s for official LiveCD releases.
--
Alexander E. Patrakov
--
http://linuxfromscratch.org/mailman/listinfo/lfs-dev
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page
Bruce Dubbs wrote:
> Alexander E. Patrakov wrote:
>> Hello,
>>
>> Some newbies get caught by our advertisement (which might be true for older
>> versions of LFS, but is untested as of LFS-6.3):
>>
>>> It is not difficult to build an LFS system of
ist and 0 SVN commits
since January, 1st). So it would be better to say something like "a scripted
build" (meaning user-written scripts) instead of "ALFS", and proide some
concrete specs of a "reasonably fast system".
--
Alexander E. Patrakov
--
http://linuxfromscr
I wrote:
> Bruce Dubbs wrote:
>> Alexander E. Patrakov wrote:
>>> Hello,
>>>
>>> Some newbies get caught by our advertisement (which might be true for
>>> older versions of LFS, but is untested as of LFS-6.3):
>>>
>>>> It is not
rdware and Time Requirements"
(and possibly rename "Host System Requirements" to "Host System Software
Requirements"). My variant of renaming also allows to mention the "x86-only"
limitation of LFS in any of the two sections.
--
Alexander E. Patrakov
--
ple that I would like to avoid.
As for your proposal to put RPM into BLFS, I think this has to be discussed in
LFS, too. Reason: package management belongs in the next-generation LFS, and it
is an option to have it there, as opposed to BLFS.
--
Alexander E. Patrakov
--
http://linuxfromscratch
Randy McMurchy wrote:
> Cc: to BLFS-Dev
>
> Alexander E. Patrakov wrote these words on 03/31/08 10:44 CST:
>> Bruce Dubbs wrote:
>>> The implication of going to DESTDIR for LFS would imply doing the same
>>> for BLFS. Some of the BLFS packages are not DESTDIR
the visits--e.g.,
this way it may be possible to trick the future scripts into generating a
multilib 32-bit book by first visiting "x86_64 multilib" and then "x86".
--
Alexander E. Patrakov
--
http://linuxfromscratch.org/mailman/listinfo/lfs-dev
FAQ: http://www.linuxfromscrat
w.linuxfromscratch.org. So
far, I have found no obvious way to compromise the scripts in the current PHP
configuration.
--
Alexander E. Patrakov
--
http://linuxfromscratch.org/mailman/listinfo/lfs-dev
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page
libraries
without the .so symlinks, new openssl dynamic libraries with the .so symlinks,
new headers. You can't have all three at the same time without splitting the
package (assuming that the package manager knows about file conflicts).
--
Alexander E. Patrakov
--
http://linuxfromscratch.org/
Jeremy Huntwork wrote:
> Alexander E. Patrakov wrote:
>> Glibc is not the best example for discussion. I requested such sample page
>> for
>> bash, not for glibc, for a reason: bash needs a specific patch in the RPM
>> case,
>> and I don't see the way to
t a
new incompatible version of the library becomes a completely different and
(from
the viewpoint of dpkg) unrelated package.
--
Alexander E. Patrakov
--
http://linuxfromscratch.org/mailman/listinfo/lfs-dev
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page
Dan Nicholson wrote:
> Fedora is getting along fine without putting libraries in separate
> subpackages.
The -devel split is not really about putting headers somewhere else to save
space, it's really about libraries.
--
Alexander E. Patrakov
--
http://linuxfromscratch.org/mailm
Marc McLaughlin (LUSYN) wrote:
> Out of interest, which bootloaders mentioned by Jeremy for LFS 7.0 will
> work with x86-64? I only managed to get my x86-64 LFS build booting
> with EXTLINUX.
LILO, Grub2.
--
Alexander E. Patrakov
--
http://linuxfromscratch.org/mailman/listinfo/lf
ot;invalid XML").
About the editor: it does show line numbers for errors, but it doesn't number
lines. Inconvenient for large pages.
--
Alexander E. Patrakov
--
http://linuxfromscratch.org/mailman/listinfo/lfs-dev
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page
al purposes, Debian rules are
incoherent
between various Debian packages.
--
Alexander E. Patrakov
--
http://linuxfromscratch.org/mailman/listinfo/lfs-dev
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page
e rest of the tasks can be done with a simpler
Wiki-like syntax once one writes additional parsers.
--
Alexander E. Patrakov
--
http://linuxfromscratch.org/mailman/listinfo/lfs-dev
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page
he explicit build
instructions, but is suitable only for simple CMMI-like packages), and there
are
other options.
--
Alexander E. Patrakov
--
http://linuxfromscratch.org/mailman/listinfo/lfs-dev
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page
t say somewhere on the PM page that we don't use the %configure and
similar macros in our spec files (and call ./configure directly instead)
because
we want 100% correspondence between commands in no-PM and RPM versions of LFS?
--
Alexander E. Patrakov
--
http://linuxfromscratch.org
ndling configuration files when upgrading a package.
So: given that we still can't agree on the set of features to implement, I
propose LFS to never have any sort of PM, and those who disagree with this "no
PM" policy should start a fork right now.
--
Alexander E. Patrakov
--
http://linuxfr
come was (roughly) that LFS needs to provide at
least a no-PM and PM versions, with a well-known PM. And a requirement has been
formulated that the commands must match between these two versions (thus ruling
out %configure for RPM). Now Bruce wonders if we create a source RPM for each
ook assumes that you have only one network card and configures only
eth0, see the hint if you need something beyond this simple case;
3) always write udev rules by hand--the idea is simple!
4) your own variant.
--
Alexander E. Patrakov
--
http://linuxfromscratch.org/mailman/listinfo/lfs-dev
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page
compatibility
when upgrading kernels.
--
Alexander E. Patrakov
--
http://linuxfromscratch.org/mailman/listinfo/lfs-dev
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page
.linuxfromscratch.org/lfs/view/development/chapter04/addinguser.html:
useradd -s /bin/bash -g lfs -m -k /dev/null lfs
See "bash" here? On the next page, /bin/bash is also explicitly called
in ~/.bash_profile.
So: the bug report is invalid.
--
Alexander E. Patrakov
--
http://linuxfrom
ooks (preferably separate for stable & development
versions), artwork, stuff in public_html, and PDFs, just to compare?
--
Alexander E. Patrakov
--
http://linuxfromscratch.org/mailman/listinfo/lfs-dev
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page
are, obviously, available from /proc/net/dev. So,
is our "by default, use iproute2 only" choice justified enough?
--
Alexander E. Patrakov
--
http://linuxfromscratch.org/mailman/listinfo/lfs-dev
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page
ted manual pages from all packages in LFS and BLFS
and/or patch Man not to look for them at all. This is the only "right" thing
to do now, because such support is based on either obsolete standards
(ISO-8859-1) or, even worse, hacks. This will also serve better for the
readers,
Randy McMurchy wrote:
> Hi all,
>
> I noticed that the Ncurses author creates patches against
> the 5.6 version. I can't remember if this has been
> discussed before, and if it has then my apologies for
> not remembering.
This is how he publishes development versions.
--
ru_RU.KOI8-R there.
I think I am not alone with this bibtex problem.
--
Alexander E. Patrakov
--
http://linuxfromscratch.org/mailman/listinfo/lfs-dev
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page
error message or manpage) is infinitely better than an unreadable one.
--
Alexander E. Patrakov
--
http://linuxfromscratch.org/mailman/listinfo/lfs-dev
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page
sing a dictionary containing the translation of, say, "NAME" for all
languages). I.e., the old version was likely to give wrong answers anyway,
that's why this feature was removed. Could you please test both old and
new "file" on manual pages installed by Man-1.6f?
--
g all packages that provide
translated manual pages.
Currently, no actions related to manual pages are needed. Only
edit /etc/sysconfig/console and /etc/profile, and convert stuff in your home
directory.
--
Alexander E. Patrakov
--
http://linuxfromscratch.org/mailman/listinfo/lfs-dev
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page
default,
too. Obviously, complete removal of support for translated manual pages by
this patch makes groff-utf8 unneeded. "+lang none" is still needed.
--
Alexander E. Patrakov
diff -ur man-1.6f.orig/configure man-1.6f/configure
--- man-1.6f.orig/configure 2007-08-21 10:15:21.0 +060
DJ Lucas wrote:
> Alexander E. Patrakov wrote:
> > DJ Lucas wrote:
> >> Roll back to file-4.21. The newer versions of file do not display the
> >> character set if type is text/troff
> >
> > Testcase please. IMHO they are right, as it is impossible to relia
onfiguration needed in order
> to read man-pages in the encoding of my preference,
> legacy or utf8.
Very interesting, however, on my system, no packages installed Greek manual
pages. Where you got them from, except the "man" package (that doesn't install
them if one passes
DJ Lucas wrote:
> Actually, the individual locales are not needed any longer.
However, some locales improve the coverage of the testsuites, and I
think it is instructive to show how to create individual locales with
localedef.
--
Alexander E. Patrakov
--
http://linuxfromscratch.org/mail
ity is agreed as to
> the direction we take.
Please look at
http://linuxfromscratch.org/pipermail/lfs-dev/2006-January/055425.html -
basically, if you are going to remove the patch, rerun the tests and, if
they fail, forget about LSB certification.
--
Alexander E. Patrak
hat can be of use? I am
> especially interested in the coreutils tests that had previously
> failed. Looks like they were still broken in 6.9.
There are no bookmarks, I googled for the subject combined with my surname.
--
Alexander E. Patrakov
--
http://linuxfromscratch.org/mailman/lis
gt; we use recent groff with man-db ?" and for that I have no idea, I
>> haven't even got close to looking at how it's all set up in current
>> debian and ubuntu.
>>
> No..only groff CVS.
No, not even groff CVS, because it expects different command line
options than those hard-coded in Man-DB.
--
Alexander E. Patrakov
--
http://linuxfromscratch.org/mailman/listinfo/lfs-dev
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page
this particular task.
> Likewise, if one is making changes to partition tables, why would the
> program that is making those changes not inform Linux about those
> changes?
dd, see example above, It just doesn't know that it modifies the
partition table :)
--
Alexander E. Patrakov
--
http://linuxfromscratch.org/mailman/listinfo/lfs-dev
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page
ed, it does contain /usr/bin/m4.
--
Alexander E. Patrakov
--
http://linuxfromscratch.org/mailman/listinfo/lfs-dev
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page
stribution. Here
are some examples: ..., ..., old LFS LiveCD", not "if you don't want to
install a distribution, try LFS LiveCD".
--
Alexander E. Patrakov
--
http://linuxfromscratch.org/mailman/listinfo/lfs-dev
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page
when
Knoppix exists and can be made to work as a host?", and I think that
defining this balance (and thus establishing the criteria of the future
LFS LiveCD usefulness) is the real question to discuss.
--
Alexander E. Patrakov
--
http://linuxfromscratch.org/mailman/listinfo/lfs-dev
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page
"English
> tutorial" is an acceptable fallback, and is what the book did at that
> time. It *looks* like vimtutor -- or at least the way LFS installs it
> now -- has simply gotten better. If that's correct: Yay! ;-)
Yes, that's correct, and that's old
#x27;s why
I am against it.
--
Alexander E. Patrakov
--
http://linuxfromscratch.org/mailman/listinfo/lfs-dev
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page
I'd like to see comparison of both
approaches. E.g., if the manual pages are installed with a Makefile, it
is often easier to convert manual pages before installation than to
patch the Makefile.
> For example, to install Spanish manual pages
Let's drop this buggy package and explain both techniques with French
manual pages.
--
Alexander E. Patrakov
--
http://linuxfromscratch.org/mailman/listinfo/lfs-dev
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page
t scripts exist in the package, but
that for the sake of demonstration, out "convert-mans" script is used.
--
Alexander E. Patrakov
--
http://linuxfromscratch.org/mailman/listinfo/lfs-dev
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page
ded to complete each of the ways, you will perhaps be able
to come up with a better phrase.
> Following LFS's previous policy, if upstream distributes the manual
Not sure if the reference to our previous setup (not policy, as we
couldn't change it!) is a good thing.
The rest is OK.
--
Alexander E. Patrakov
--
http://linuxfromscratch.org/mailman/listinfo/lfs-dev
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page
n't pass '+lang none' to Man's build?
It is a problem for all distributions that don't pass '+lang none'. No
distribution known to me passes '+lang none'. Fedora converts error
messages so that they look right in UTF-8 locales, but this makes them
incorrec
n, Man-DB checks
> the table, and performs the necessary conversion. E.g., because of
> "UTF-8" extension in the directory name...
It always performs the necessary conversion (e.g., in ru_RU.KOI8-R
locale, it can use manual pages from /usr/share/man/ru.UTF-8), so let's
drop or m
Bruce Dubbs wrote:
> Alexander E. Patrakov wrote:
>
>> So, please choose another word below.
>>
>>> When man encounters an unexpected encoding, it will display the contents
>>> as configured, resulting in completely illegible text.
>
> How about '
I wrote:
> Bruce Dubbs wrote:
>> Alexander E. Patrakov wrote:
>>
>>> So, please choose another word below.
>>>
>>>> When man encounters an unexpected encoding, it will display the
>>>> contents as configured, resulting in completely ille
Robert Connolly wrote:
> Is there a reason Binutils pass2 has --disable-nls?
Yes, the same as before: if someone wishes to use HJL binutils, this
avoids the "gettext" host requirement.
--
Alexander E. Patrakov
--
http://linuxfromscratch.org/mailman/listinfo/lfs-
ot; group and its special gid.
--
Alexander E. Patrakov
--
http://linuxfromscratch.org/mailman/listinfo/lfs-dev
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page
e.g. fltk fails to build), the fix is:
http://sourceware.org/cgi-bin/cvsweb.cgi/libc/nptl/sysdeps/pthread/pthread.h.diff?r1=1.24&r2=1.25&cvsroot=glibc
Also, do we really want to provide a kernel with known broken CD writing
without any warning?
--
Alexander E. Patrakov
--
http://lin
Bruce Dubbs wrote:
> The only change is either one package version or some minor instruction
> changes.
Or even better, no version changes, only minimal patches to fix known
problems.
--
Alexander E. Patrakov
--
http://linuxfromscratch.org/mailman/listinfo/lfs-dev
FAQ
(sorry, something is wrong again with the news server, thus the private CC:)
Matthew Burgess wrote:
> Alexander E. Patrakov wrote:
>> When the modified "udev" bootscript sets /sbin/udevsend as a
>> handler, everything is ready.
>
> I thought the necessary c
Nathan Coulson to create an
official configuration file for that palette :)
Q: is it all that has to be done in order to get working UTF-8 in LFS?
A: no, one has to adjust instructions for ncurses and man (both can be made
harmless for non-UTF-8 users) and to add optional --disable-nls type
flags to some other packages. Also one has to mark some broken packages
in BLFS.
--
Alexander E. Patrakov
console
Description: application/shellscript
--
http://linuxfromscratch.org/mailman/listinfo/lfs-dev
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page
8859-1". Also some people say it's
better to remove LC_ALL (i.e. set only LANG) and I tend to agree with them
now.
Please do that before LFS 6.1 comes out.
--
Alexander E. Patrakov
--
http://linuxfromscratch.org/mailman/listinfo/lfs-dev
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page
Matthew Burgess wrote:
> Alexander E. Patrakov wrote:
>
>> So it's better to change the book to say "ISO-8859-1".
>
> Easy enough to do, added to my (ever growing) TODO for 6.1.
>
>> Also some people say it's better to remove LC_ALL (i.e. set on
just too many patches so one can't
seriously consider the "grep" package trouble-free.
At least one patch has to be added (maybe post-6.1) for eliminating important
UTF-8 bug:
http://www.gentoo.org/cgi-bin/viewcvs.cgi/*checkout*/sys-apps/grep/files/2.5.1-utf8-case.
Matthew Burgess wrote:
> Alexander E. Patrakov wrote:
>> So it's better to change the book to say "ISO-8859-1".
>
> Hmm, but as Ken pointed out, 'locale -a' (which we point out on that
> same page) lists 'en_GB.iso88591', so I've a feel
Alexander E. Patrakov wrote:
> Matthew Burgess wrote:
>
>> Alexander E. Patrakov wrote:
>>> So it's better to change the book to say "ISO-8859-1".
>>
>> Hmm, but as Ken pointed out, 'locale -a' (which we point out on that
>> same
the expected backspace/delete
characters.
> I have not changed /etc/inputrc.
This only controls applications linked with readline. Vim isn't.
> KEYMAP_CORRECTION="/etc/kbd/bs-sends-del"
Typo, someone should fix it.
--
Alexander E. Patrakov
--
http://linuxfromscratch.org/mailman/listinfo/lfs-dev
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page
mand is not needed.
Or should we keep that just in case so that the proposal can be easily
reconsidered? That would depend on people willing to provide translations
and on bootscript coders to make their bootscripts translation-friendly.
--
Alexander E. Patrakov
--
http://linuxfromscratch.org/mailman/listinfo/lfs-dev
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page
sole file? Or did you leave it alone?
> Guess I'm wondering if you have a keymap that needs fixing as is
> mentioned here:
>
> http://www.linuxfromscratch.org/view/stable/chapter07/console.html
No, the problem is in fact the opposite (i.e. Bruce does the opposite of the
fix mentioned the
ng hotplug. Can we change that
> to an 'echo > /var/log/hotplug/events'?
Question: why do we need to create this file at all? I prefer NOT having my
hotplug events logged.
--
Alexander E. Patrakov
--
http://linuxfromscratch.org/mailman/listinfo/lfs-dev
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page
gettext 0.14.4 requires creation of one more locale on glibc page
checking for a traditional french locale... fr_FR
checking for a french Unicode locale... fr_FR.UTF-8
--
Alexander E. Patrakov
--
http://linuxfromscratch.org/mailman/listinfo/lfs-dev
FAQ: http://www.linuxfromscratch.org/faq
Matthew Burgess wrote:
> Alexander E. Patrakov wrote:
>> gettext 0.14.4 requires creation of one more locale on glibc page
>
> I took a quick look at the configure script and couldn't determin what
> effects having those 2 locales has, i.e. what features of gettext rely
&
more
translated messages, but would also require recompilation of kbd-1.12 in
order to move keymaps and screen fonts to /lib/kbd.
2) Translate BLFS bootscripts also. Will do that after discussion of
translated LFS bootscripts.
--
Alexander E. Patrakov
--
http://linuxfromscratch.org/mailman/listinf
ng at all. It cannot deal with kernel messages and
unexpected program output anyway.
2) Handle "\n" correctly in boot_mesg when constructing lines and counting
characters.
3) Never pass "\n" to boot_mesg.
My vote goes for (1).
--
Alexander E. Patrakov
<>--
http:/
.
For counting characters in $STRING, the ${#STRING} construction can be
used. It won't work with non-bash in UTF-8 locales correctly, but the
only (AFAIK) shell that supports UTF-8 is bash. So it's safe to assume
that non-bash just won't be used in UTF-8 locales.
--
Alexander E. P
Nathan Coulson wrote:
BTW, does the # work under ash? [the Counting Characters part, not
the international part. (Internationalzation for someone who wants to
use ash, is probably not a major concern)]
Then ${#STRING} construction works properly in ash in all 8-bit locales.
--
Alexander E
a /dev entry and udev has
absolutely no relation to /proc contents.
--
Alexander E. Patrakov
--
http://linuxfromscratch.org/mailman/listinfo/lfs-dev
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page
already implemented in cross-LFS, but the explanation "it
is not needed" is not perfect.
--
Alexander E. Patrakov
--
http://linuxfromscratch.org/mailman/listinfo/lfs-dev
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page
this context, it
should be replaced with a plain "=".
--
Alexander E. Patrakov
--
http://linuxfromscratch.org/mailman/listinfo/lfs-dev
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page
correctly
(also please specify your locale). Suboptimal but not strictly incorrect
guesses should be explained (i.e. what exactly is suboptimal).
Test results should go to the lfs-support list.
--
Alexander E. Patrakov
#!/bin/sh
#
t from the patch.
--
Alexander E. Patrakov
--
http://linuxfromscratch.org/mailman/listinfo/lfs-dev
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page
s these two bugs and some others.
The -1b patch attempts to fix those two bugs, but I cannot call the fix
100% correct for xterm (it relies upon the undocumented fact that xterm
ignores the "\033(K" sequence). The -1a patch is IMHO a safer solution.
Please choose which of the so
uot;\033(K" sequence). The -1a patch is IMHO a safer solution.
Please choose which of the solutions should go into LFS-6.1.
--
Alexander E. Patrakov
Submitted by: Alexander E. Patrakov
Date: 2005-06-05
Initial Package Version: 21.6
Upstream Status: Not Submitted - Hack
Origin: Alexander E. P
, it may have the same problem in Chapter 5. Cannot test this
with Knoppix right now because of bandwidth issues.
Maybe someone should add this to the list of known Chapter 5 glibc
testsuite failures.
--
Alexander E. Patrakov
--
http://linuxfromscratch.org/mailman/listinfo/lfs-dev
FAQ: http:
> Maybe someone should add this to the list of known Chapter 5 glibc
> testsuite failures.
No need to do so, because the only known bad host so far is our -pre3 Live CD.
--
Alexander E. Patrakov
--
http://linuxfromscratch.org/mailman/listinfo/lfs-dev
FAQ: http://www.linuxfromscratch.org/f
Jeremy Huntwork wrote:
Alexander E. Patrakov wrote:
a) drop 8139cp (in preference to 8139too), eepro100 (in preference to
e100), dmfe (in preference to tulip), xircom_tulip_cb (in preference
to xircom_cb, and it doesn't load anyway because of missing symbols).
If you disagree because
a problem with the patch.
The remaining are cpio failures, off-topic on this list. Will post them
to blfs-dev separately after further investigation.
--
Alexander E. Patrakov
--
http://linuxfromscratch.org/mailman/listinfo/lfs-dev
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page
501 - 600 of 855 matches
Mail list logo
