El Domingo, 9 de Abril de 2006 02:44, Randy McMurchy escribió:
Is there any way we can change and move to a versioned directory
target, so folks a year from now will know which version of stylesheets
they'll need?
Facts:
-The xsl-stylesheets-current symlink is used only to copy the
El Domingo, 9 de Abril de 2006 18:40, Bruce Dubbs escribió:
In BLFS, we created an image/ directory and have the images in SVN.
That seems like a better way to me. That way the entire book is in SVN
and is not dependent on any external sources. If it matters, the files
are 136K.
I have
El Domingo, 9 de Abril de 2006 22:36, Jeremy Huntwork escribió:
All in all, I don't think it's going to be much of a problem. I merged
udev_update into my working copy, rendered and created a diff. I would
appreciate it if a few eyes could take a look and let me know if I've
missed anything,
El Domingo, 9 de Abril de 2006 22:54, M.Canales.es escribió:
First things noticed. In general.ent generic-version and
lfs-bootscripts-version need to be fixed.
Whit the lfs-bootscripts-version fix, the changelog entry for March 22, 2006
should be updated.
Remember to svn add chapter05
El Sábado, 8 de Abril de 2006 18:24, Jeremy Huntwork escribió:
My reasoning is that 1) /etc/mtab isn't really anything to do with the
other kernfs mounts, 2) we already create /etc in 6.5 Creating
Directories and that fits there - there's no real need to create /etc
any earlier 3) by section
El Sábado, 8 de Abril de 2006 18:54, Jeremy Huntwork escribió:
Well, if we're changing that page from just Essential Symlinks to
Essential Symlinks and Files, then we might as well merge that page with
6.7 because, in my mind, 6.7 as it is really could be renamed to
'Creating Essential
El Viernes, 7 de Abril de 2006 17:38, Chris Staub escribió:
I've started working on a page describing the reasoning behind the
package build order for LFS. Take a look at it here -
http://linuxfromscratch.org/~chris/lfs-book/chapter05/buildorder.html.
Any comments - page layout, location,
El Jueves, 6 de Abril de 2006 22:37, Archaic escribió:
On Thu, Apr 06, 2006 at 10:27:23PM +0200, M.Canales.es wrote:
The build will take some hours on my system, then the commit will be made
tomorrow if there is no build issues.
Sounds good, Manuel. Thanks for all the help! :)
Build
El Viernes, 7 de Abril de 2006 19:26, Dan Nicholson escribió:
Out of curiosity, what kind of hardware do you have? I've been
getting three error here using an Athlon-XP for a while now. I like
to think these are processor specific, but I haven't really
investigated.
An Intel(R) Pentium(R)
El Viernes, 7 de Abril de 2006 19:51, Dan Nicholson escribió:
Unfortunately, there's not a lot of info there. Do you still have the
source directory? How about, now that the base system is installed,
try to rebuild e2fsprogs and see if the tests still fail.
I have yet all the kernel
El Viernes, 7 de Abril de 2006 20:06, Dan Nicholson escribió:
On 4/7/06, M.Canales.es [EMAIL PROTECTED] wrote:
I have yet all the kernel filesystems mounted. I will do now a new
E2fsprogs build ith mount -bind. After that i will to umount /dev and
mount it again like is done in trunk to do
El Viernes, 7 de Abril de 2006 20:20, M.Canales.es escribió:
I have keeped both build trees, if you need some info from them.
Diffing the build trees all dfferences are in the build/test/* files.
All files on that drectory for the mount -bind build have ths additional
line
El Viernes, 7 de Abril de 2006 21:05, Bryan Kadzban escribió:
The rest of the function is a bit hairy though. Probably the best way
to figure out what exactly it's complaining about is to set the DEBUG
preprocessor define to something other than zero; this should be doable
if you cd into
El Miércoles, 5 de Abril de 2006 14:57, William Zhou escribió:
BTW, in the section Important, the last sentence got a word misspelled.
It is to aid not to aide.
Fixed, thanks.
--
Manuel Canales Esparcia
Usuario de LFS nº2886: http://www.linuxfromscratch.org
LFS en castellano:
El Viernes, 7 de Abril de 2006 21:43, Archaic escribió:
However, for size recording, my script does one thing in chroot to make
/ appear in /etc/mtab:
mount -f -t $fs_type /dev/$partition /
Maybe that's why it works for me?
Bingo!
When I made the umount of /dev and remount all kernel
El Viernes, 7 de Abril de 2006 22:07, Dan Nicholson escribió:
I just built e2fsprogs in chroot using mount --bind and no other
modifications except that it's building on top of a full system. No
test failures:
Do you have an $LFS/etc/mtab file?
--
Manuel Canales Esparcia
Usuario de LFS
El Viernes, 7 de Abril de 2006 22:08, M.Canales.es escribió:
After the removal of /etc/mtab, the test failures are here againg.
More news:
A plain touch $LFS/etc/mtab allow to pass successfully all e2fsprogs test.
--
Manuel Canales Esparcia
Usuario de LFS nº2886: http
El Viernes, 7 de Abril de 2006 22:27, Dan Nicholson escribió:
Yes, I get the failures without /etc/mtab. That's the issue.
Due that in udev_update no mounts are done inside the chroot, /etc/mtab isn't
created.
I think that we should to add the touch /etc/mtab in chapter06/e2fsprogs.xml
just
El Jueves, 6 de Abril de 2006 19:28, Jeremy Huntwork escribió:
I'm merging alpha as we speak. Archaic and I have planned to do
udev_update next week, if no objections are made.
No objections in my end ;-)
--
Manuel Canales Esparcia
Usuario de LFS nº2886: http://www.linuxfromscratch.org
El Domingo, 2 de Abril de 2006 10:40, M.Canales.es escribió:
I would prefer to have both, the real home site links (not the current
ones) and the full packages download links.
I will start making the required changes on my local copy waiting
agreements (or lack of complaints) before to do
El Jueves, 6 de Abril de 2006 19:42, Jeremy Huntwork escribió:
I'm sure Archaic wouldn't mind if you started on seeing what would need
to happen to merge udev in now (perhaps even create a diff?) I think its
wise to leave space of a week for testing between merges, though.
Generating the diff
El Jueves, 6 de Abril de 2006 19:47, Archaic escribió:
On Thu, Apr 06, 2006 at 07:38:53PM +0200, M.Canales.es wrote:
Due that there is no comments against that, I will do the commit now.
Please wait, or merge the change to udev_update to avoid another set
of conflicts when that branch merges
El Jueves, 6 de Abril de 2006 19:46, M.Canales.es escribió:
El Jueves, 6 de Abril de 2006 19:42, Jeremy Huntwork escribió:
I'm sure Archaic wouldn't mind if you started on seeing what would need
to happen to merge udev in now (perhaps even create a diff?) I think its
wise to leave space
El Jueves, 6 de Abril de 2006 20:19, Jeremy Huntwork escribió:
Well, any chance you can attach a diff here first? I'm just curious
about what gets changed...
Attached.
--
Manuel Canales Esparcia
Usuario de LFS nº2886: http://www.linuxfromscratch.org
LFS en castellano:
El Jueves, 6 de Abril de 2006 20:31, Jeremy Huntwork escribió:
Oh. I thought you were doing it the other way. Since alpha is in trunk
now, I you were going to merge all the changes to the udev_branch since
it split from trunk back to trunk. This agrees with the method in the
subversion docs:
El Jueves, 6 de Abril de 2006 21:00, Jeremy Huntwork escribió:
Yes, I see what you were thinking. I misunderstood your intentions
before. Well, if it makes it easier to merge udev_update back to trunk,
then I'd say go for it.
OK. I will do the commit in a hour if there is no objections from
El Jueves, 6 de Abril de 2006 22:16, Archaic escribió:
You sure are in a hurry today Manuel. :) Have you actually built a
system according to the proposed changes? I would suggest a run of
jhalfs on your local copy before committing.
I'm downloading now the last updated packages.
The build
El Sábado, 1 de Abril de 2006 00:50, Ag Hatzim escribió:
By the way.
There was a discussion about 2 months ago [1],with the conclusion that we
can link directly to the package tarballs.
I would prefer to have both, the real home site links (not the current ones)
and the full packages
El Sábado, 25 de Marzo de 2006 22:41, Jeremy Huntwork escribió:
To me, it just seems easier to work with dependencies all in one file
rather than separately in each chapter06 file. Especially as we're
looking at including another page (IIRC) that describes more of the
rationale for
El Miércoles, 22 de Marzo de 2006 14:43, Alexander E. Patrakov escribió:
The attached patch does the following:
Applied the changes for chapter06/udev.xml
I left the others ones to Matthew.
--
Manuel Canales Esparcia
Usuario de LFS nº2886: http://www.linuxfromscratch.org
LFS en
El Sábado, 25 de Marzo de 2006 20:52, Jeremy Huntwork escribió:
Manuel, I wanted to start adding this stuff into the book. I was
wondering if it would make sense to have this as some sort of
dynamically available data. I'm not sure if an entity makes sense (e.g.,
autoconf-deps) but that's all
El Martes, 21 de Marzo de 2006 23:31, Matthew Burgess escribió:
The actual devices (/dev/hdc on my box) are created correctly, but the
symlinks are incorrect if one has multiple CD/DVD drives. Therefore,
the bug is rightly an LFS one. Now, with the observation that the
underlying devices
El Viernes, 17 de Marzo de 2006 18:23, Bruce Dubbs escribió:
It appears that we have a problem with the tidy program to make the html
pretty. I'll make sure the latest version is being used.
Actually is an issue with the obfuscate.sh script.
Is was created for when all links was rendered in
El Miércoles, 8 de Marzo de 2006 20:36, Bruce Dubbs escribió:
It is time to start considering a new LFS release.
I see that we are behind on gcc and glibc as gcc-4.1 and glibc-2.4 have
been released.
The kernel is about to release 2.6.16 (they have been on 2.6.16-rc5 for
about two weeks
El Miércoles, 8 de Marzo de 2006 20:58, Archaic escribió:
Testsuite depends on: additional dependencies to run the testsuites
Of course. That is what 'additional' means ;-)
--
Manuel Canales Esparcia
Usuario de LFS nº2886: http://www.linuxfromscratch.org
LFS en castellano:
El Lunes, 27 de Febrero de 2006 02:02, Bruce Dubbs escribió:
I would like to announce that Dan Nicholson has been appointed as the
newest BLFS Editor. Please help me in welcoming him to the project.
Wow, fresh meat in the team ;-)
Welcome on board, Dan.
--
Manuel Canales Esparcia
Usuario de
El Miércoles, 8 de Febrero de 2006 15:18, Jeremy Huntwork escribió:
Manuel, I wonder if it's best to leave the date alone when making
strictly XML changes. Either that, or start adding Changelog entries for
them. Just so its not confusing to those comparing the Changelog with
the date.
Well,
El Viernes, 20 de Enero de 2006 17:34, Jim Gifford escribió:
Talking to community members in cross-lfs, most of them don't want to be
forced to use utf-8, because they don't need it. Others want to be able
to test it, and if they don't like it do a build without it.
No one is forcing to use
El Jueves, 19 de Enero de 2006 12:41, Jeremy Huntwork escribió:
In my experience only ViewCVS does it this way. Every other different
piece of software I've used shows the file right off. Anyway, I wonder
if there's a way to control this, and I can look into it...
Actually I see more logical
El Martes, 17 de Enero de 2006 10:14, Filip Bartmann escribió:
How can I make TeX output from LFS book XML sources? I find, that under
directory stylesheet is file lfs-tex.xsl-how can I use this file for
converting from xml to TeX?
That stylesheet depend on db2latex
El Martes, 17 de Enero de 2006 12:36, Alexander E. Patrakov escribió:
Filip Bartmann wrote:
Why is in Makefiles for LFS books parameters -nonet? If I don't remove
this parameters I can't build this books, because I have errors failed
to load external entity. Have I something wrong?
Yes, old
Hi!
Starting the Spanish translation update I noticed that the i18n patches
referenced in the book are yet hosted on the Alexander's home dir.
For consintency, and to allow patcheslist.xsl and jhalfs do well their job,
that patches must be placed into the Patches Project repository, and
El Lunes, 28 de Noviembre de 2005 16:33, Bruce Dubbs escribió:
These are the main alternative packages/options that I can remember off
the top of my head. I'd have to go through the book to get a
comprehensive list, but we are just talking concepts right now.
Well, all that seems good
El Martes, 22 de Noviembre de 2005 20:32, Gerard Beekmans escribió:
If what you said can easily be done--a shared file across all
repositories--then that's how we should go about it.
svn:externals have several limitations, see the last two paras in this page:
El Lunes, 21 de Noviembre de 2005 22:22, Matthew Burgess escribió:
3) Change the Makefile to do the following test instead:
if [ $(prefix) = / -o $(prefix) = ];
Try this:
if [ x$(prefix) = x/ ]
That is recommended way to test varaibles when you aren't sure that it allways
have an asigned
El Domingo, 20 de Noviembre de 2005 15:01, Matt Darcy escribió:
should be
tar jxvf ../module-init-tools-testsuite-3.1.tar.bz2 --strip-path=1
The strip option is also questionable on certain versions of tar on
platforms.
Not. When issuing that command the tar binary used must be the one
in
El Viernes, 18 de Noviembre de 2005 10:11, [EMAIL PROTECTED] escribió:
In this scenario, jhalfs breaks because:
* Variables JHALFSDIR,LOGDIR,MKFILE are set in jhalfs.conf
related to BUILDDIR, but not reset when BUILDDIR is overwritten
in the command-line.
* The sed in
El Viernes, 18 de Noviembre de 2005 04:49, Jeremy Huntwork escribió:
As far as 1 goes, it's nice to see various people commenting on a much
more visible list. It helps round out the discussion and determine
whether or not this is an important issue to many people.
Thinking on that, and after
Hi !
I would to start indenting the LFS-SVN sources this weekend. I hope that it
will take only a few days (more of the indented blocks, like the Contents
of ... sections, can be ported from CLFS, the big work will be to indent the
Spanish translation sources :-/ )
But that meant that no
El Viernes, 11 de Noviembre de 2005 19:41, Randy McMurchy escribió:
M.Canales.es wrote these words on 11/11/05 12:30 CST:
I don't remember any discussion about the alphabetical merge. Is
this something that is deemed so trivial that it isn't worthy of
community discussion before
El Sábado, 29 de Octubre de 2005 17:38, Jeremy Huntwork escribió:
Howdy.
Manuel, you have it buildable via jhalfs, right?
Yes.
Have you seen good results with that?
Running now a new full build with current jhalfs version to be sure that all
is fine. I'm using this command line:
#
El Martes, 25 de Octubre de 2005 16:03, Jeremy Huntwork escribió:
The idea of keeping the code cleaner by using a function is nice,
however I disagree that this is more readable.
At least to me the version using case is more hard to read and isn't as
flexible as the _IS_ function. The _IS_
El Lunes, 17 de Octubre de 2005 21:53, Jeremy Huntwork escribió:
Seth W. Klein wrote:
case $i in *groff)
Manuel, do you mind if we switch over to this method of string
comparisons in jhalfs? David's method is nice, but the syntax Seth
suggests is easier to read and doesn't result in
El Lunes, 17 de Octubre de 2005 15:06, Dan Nicholson escribió:
I'm sure you knew this, but remember that set -e does not break for
simple errors in while loops. Haven't looked at jhalfs to know if this
is the case or not. Just wanted to give a heads up.
Yeah, I read the bash man page before
El Lunes, 17 de Octubre de 2005 21:53, Jeremy Huntwork escribió:
Seth W. Klein wrote:
case $i in *groff)
Manuel, do you mind if we switch over to this method of string
comparisons in jhalfs? David's method is nice, but the syntax Seth
suggests is easier to read and doesn't result in
El Viernes, 14 de Octubre de 2005 22:56, Matthew Burgess escribió:
Yeah, I hit the missing patches.ent file today too. As it's a fairly
safe change to do (`make validate' and the rendering process that copies
the patches will catch any inadvertent errors) feel free to backport
patches.ent
El Sábado, 15 de Octubre de 2005 04:54, Alexander E. Patrakov escribió:
1. For the UTF-8 book, it is also needed to download
glibc-libidn-2.3.5.tar.bz2 from lfs-matrix. Please handle this similarly
to glibc-linuxthreads and bash-doc tarballs.
This and the groff-patchlevel issue should both be
El Viernes, 14 de Octubre de 2005 15:36, David Fix escribió:
Sorry, a bit of a typo, but this is more correct:
if [ ${i: -5} = groff ] ; then {do something} ; fi
That sounds good and is more portable for when supporting Cross-LFS.
I will test it soon, many thanks :-)
--
Manuel Canales
El Viernes, 14 de Octubre de 2005 16:19, Alexander E. Patrakov escribió:
Jeremy Huntwork wrote:
BTW, has anyone else tried this?
The showstopper is in /home/lfs/.bash_profile: the su command starts a
shell that, as a result, waits for user input. I deleted that file.
El Viernes, 14 de Octubre de 2005 17:08, Bruce Dubbs escribió:
I havn't tried jhalfs yet, but as a suggestion, /etc/shadow could have a
null root password:
echo root /etc/shadow
Yes, but that will implies another deviation from the book's commands, and not
to corfim that Shadow is
El Viernes, 14 de Octubre de 2005 17:08, Bruce Dubbs escribió:
/etc/fstab is a different matter. If jhalfs could pick up a custom file
from the host system written before running, it might avoid a
post-script edit.
Added a switch to can submit a real /etc/fstab file, and a note on the final
Hi!
I'm very happy to announce that jhalfs is now able to build a full LFS SVN
system (or any other LFS XML sources based in current LFS SVN) in a very
simple way and using the actual commands found in the XML sources.
The sources can be downloaded via
svn co
El Miércoles, 12 de Octubre de 2005 14:06, Alan Lord escribió:
Is this an alternative to alfs or something more different [sorry about
the English there - yeuckkk!] than that?
Is something very different to nALFS. nALFS have many features and uses beyond
the build of a base LFS system.
Is
El Lunes, 3 de Octubre de 2005 23:44, Dan Nicholson escribió:
Don't know if this works with make, but I saw a nice solution to this
problem in Greg Shafer's build system that uses Bash scripts. In
order to continue to run as root user in the chroot, he uses:
exec su -c ${CHROOT_CMD}
where
Hi!
jhalfs is a tool to build an LFS system using the real commands found in the
LFS SVN book. It's intended as a standar framework for developers and
testers.
http://svn.linuxfromscratch.org/viewcvs.cgi/jhalfs/trunk/?root=ALFS
It can dowload the needed packages and patches (from
El Domingo, 2 de Octubre de 2005 13:15, M.Canales.es escribió:
Do by hand all steps up to the end of chapter03, create the $LFS/jhalfs
directory and place into it a fresh svn working-copy of your sources naming
the directory lfs-development.
Actually i'm planning to add a switch to can use
El Domingo, 2 de Octubre de 2005 17:35, Jeremy Huntwork escribió:
Wow, you've really taken my idea and run with it. ;) It looks nice, just
where I would have (probably) gone myself. I'll have to get some time to
sit down and really look it over.
Thanks, and very happy to read to you :-)
The
El Domingo, 2 de Octubre de 2005 18:45, Joshua Murphy escribió:
hmm ... would it work to make a Stage 2 script that's simply called
as the command to execute through chroot? ... i'm not much of a
developer, but i've looked at building my own scripts before, and i've
considered a lot of little
El Martes, 20 de Septiembre de 2005 21:19, Jeremy Huntwork escribió:
Thanks again - I've enjoyed it immensely.
Thanks to you for all the work done :-)
I will try to keep alive your other child: jhalfs.
--
Manuel Canales Esparcia
Usuario de LFS nº2886: http://www.linuxfromscratch.org
El Jueves, 15 de Septiembre de 2005 23:43, Jim Gifford escribió:
If we do this, we could remove chroot from the Cross-LFS, since it's
only there for same arch to same arch capability.
Exactly ;-)
--
Manuel Canales Esparcia
Usuario de LFS nº2886: http://www.linuxfromscratch.org
LFS en
El Jueves, 15 de Septiembre de 2005 19:06, Jim Gifford escribió:
After some discussion with Gerard, he has requested I prepare a proposal
to the LFS community concerning the Cross-LFS book.
Up to this point work on Cross-LFS has been done with the idea that,
eventually, its features would be
El Jueves, 15 de Septiembre de 2005 22:56, Jim Gifford escribió:
One of things I've been mulling over is maybe have cross-lfs just build
the toolchains, but the rest of the stuff, currently the temp-system and
final-system of Cross-LFS, could be the future LFS book that supports
multiple
El Martes, 13 de Septiembre de 2005 20:50, Matthew Burgess escribió:
With that in mind, we'd appreciate feedback on the attached config file
especially if you've tested it in the field and found that we broke
something! Errors and omissions expected :)
The network devices removal includes
El Jueves, 8 de Septiembre de 2005 21:32, Matthew Burgess escribió:
Manuel, is this likely to cause problems
for your intended docbook-xsl-1.69.1 related patches you've got planned
for the weekend?
Don't worry about that.
The merge will implies only that I don't will need to verify the
Hi!
I'm planning to update all [B,H]LFS books (trunk and active branches) to use
the new DocBook-XSL-1.69.1 version the next Saturday 2005-09-10 at 12h UTC.
Please, update your machines to can render the books using that new XSL
version.
Thanks.
--
Manuel Canales Esparcia
Usuario de LFS
El Domingo, 4 de Septiembre de 2005 10:49, Chris Staub escribió:
I don't think that's a problem with the fact that you stopped and
restarted - if libstdc++ does not exist in /usr/lib then you forgot to
install the c++ compiler in chap. 6. Does /usr/bin/gcc exist?
I think that do you meant
El Lunes, 29 de Agosto de 2005 00:31, Jeremy Huntwork escribió:
One of the packages is unpacked from '/sources' while the other one is
unpacked from '../' - Presumably they're located in the same directory.
Which location should we be using?
IMHO, ../
Both for consistency with how the
El Lunes, 29 de Agosto de 2005 19:25, Matthew Burgess escribió:
I'll try to get around to getting the two changes in some time this
week, then we'll merge the branch into trunk probably a week after that
(just to give folks a chance to ensure there's no more problems, and
that the 'ftp' and
El Martes, 23 de Agosto de 2005 20:09, Jim Gifford escribió:
Matt,
Which direction do we want to go in.
IMHO, for LFS we need only ping for FHS compliance. It's possible to build
(and use) just Inetutil's ping on all archs?
About ftp, actually isn't a requisite for LFS. We could point the
El Martes, 23 de Agosto de 2005 20:56, Jim Gifford escribió:
M.Canales.es wrote:
IMHO, for LFS we need only ping for FHS compliance. It's possible to
build (and use) just Inetutil's ping on all archs?
Doesn't work on Sparc
Debian have an inetutils ping for Sparc:
http://packages.debian.org
El Viernes, 12 de Agosto de 2005 20:18, Matthew Burgess escribió:
Hi folks,
Please join me in welcoming Ken Moffat to the LFS development team. Ken
has been a long time contributor to both the development and support
communities, and his knowledge and dedication to the project are certain
El Lunes, 8 de Agosto de 2005 08:42, Archaic escribió:
Hrmm. Well if it is deemed to be more accurate using screen tags as
opposed to just para tags, that is easily fixed, but since we aren't
actually typing in the command as seen, but rather inserting it into
another command, I don't know if
El Lunes, 1 de Agosto de 2005 20:01, Randy McMurchy escribió:
Manuel, could you start looking into the differences between the
1.68.1 and recent version so we can think about updating BLFS.
1.69.0 is a beta version. Actually, all dot cero versions are beta, not
intended to production use,
El Sábado, 30 de Julio de 2005 20:54, Matthew Burgess escribió:
Well, bashref.html is linked to from
http://www.linuxfromscratch.org/~matthew/LFS-references.html, which is
itself linked to from chapter01/resources.html in the book. We could
add a link to the full bash-doc tarball to the
El Martes, 26 de Julio de 2005 04:16, Gerard Beekmans escribió:
Clutter will be a concern. The TOC has to be clean and easy to navigate.
Like I said above, a chapter re-organization may be required to maintain
a logically flowing TOC where you don't get lost.
Actually at this momment we are
Hi!
A new Xinclude approach is now available for review. It can be found into the
installation sections of the kernel pages, boot in bootable and reboot
chapters.
I will wait comments and complaints before to propagate it to the rest of the
book.
That work as follow:
.- Each text block that
El Martes, 12 de Julio de 2005 12:19, Claudio Cattazzo escribió:
Hi all,
if you want to add the Italian localization in lfs-l10n.xml, here it is!
Many thanks. It will be added soon to the official stylesheets.
--
Manuel Canales Esparcia
Usuario de LFS nº2886:
El Martes, 5 de Julio de 2005 08:39, Alexander E. Patrakov escribió:
I think that the biggest trouble is that xpointer expressions include
some meaningless offset numbers like para[2] instead of assigning a
meaningful name to the exact text to be copied to another page.
The more simplest way
El Lunes, 4 de Julio de 2005 19:43, Jeremy Huntwork escribió:
I'm not trying to be a stick in the mud here, and Manuel, I do
appreciate all your good work and efforts to make things more fluid, but
after trying to edit the new cross-lfs book several times and *still*
getting lost and turned
El Lunes, 4 de Julio de 2005 22:05, Jim Gifford escribió:
I wouln't say it failed, I think we should just keep it architecure
specific.
It failed on their current form. The xpointer expesions used aren't useful for
moving targets. That is the big issue: if there is a change on the nodes
El Lunes, 27 de Junio de 2005 19:53, Matthew Burgess escribió:
Hi folks,
After a very long delay [1] it looks as if we really are nearly there.
There are two bugs remaining to be fixed (1582 and 1586) which are
simply textual changes. I'll be doing a 6.1 pre-release tomorrow night
El Sábado, 25 de Junio de 2005 18:01, Randy McMurchy escribió:
Hi all,
However, my question is this:
All that is a know issue that should be adderssed ASAP:
http://linuxfromscratch.org/pipermail/lfs-dev/2005-June/051727.html
--
Manuel Canales Esparcia
Usuario de LFS nº2886:
El Jueves, 23 de Junio de 2005 13:09, Archaic escribió:
In the inputrc page I noticed an application tag. In HTML it was
converted to span class=application. However, I do not see any
difference in the output of this text. So I looked at the stylesheets
and sure enough, that class isn't
El Jueves, 23 de Junio de 2005 08:24, Archaic escribió:
I made some changes in my WC and created a diff to see if something like
this might be usable and worthwhile. Basically it just keeps us from
having to update the test results link in abouttestsuites.xml.
Look a good idea to me.
--
El Martes, 21 de Junio de 2005 01:56, Archaic escribió:
A hybrid of something like BLFS does might be nice. However, I don't
like the idea of having package-specific entities spread across multiple
files. Here's an idea for a packages.ent (or even left in general.ent)
file:
To place
El Martes, 21 de Junio de 2005 22:49, Archaic escribió:
On Tue, Jun 21, 2005 at 08:21:27PM +0200, M.Canales.es wrote:
To place entities on the files headers isn't a good idea for LFS, IMHO.
Please explain what is not good about having all package-specific
entities in one place.
To place
El Jueves, 16 de Junio de 2005 18:59, Archaic escribi:
On Thu, Jun 16, 2005 at 11:28:40AM -0500, Randy McMurchy wrote:
Okay, we really need this sorted.
Randy: SBU changes will throw everything off
Bruce: SBU changes are minor
I was only holding off due to Randy's concern for the timings,
El Jueves, 16 de Junio de 2005 23:05, Jeremy Huntwork escribi:
One drawback is that we'd be cross-compiling every package (which we
don't currently do) and some would need to be hacked a bit to get that
to work. However, it can be done, and it has been done.
Another big drawback (at least to
El Jueves, 16 de Junio de 2005 23:05, Jeremy Huntwork escribi:
1) If you chose to build on the host system because of its speed, you
get to use that speed for the entire build.
That will meant that the user will want to cross-compile also a lot of
packages from BLFS, most notably an X Window
El Martes, 14 de Junio de 2005 21:52, Jay D. McHugh escribió:
There are typos are the URL's for the bzip and texinfo packages. bzip
has two 2s and texinfo says textinfo rather than texinfo.
Fixed, thanks :-)
--
Manuel Canales Esparcia
Usuario de LFS nº2886:
201 - 300 of 321 matches
Mail list logo
