I wrote:
BTW, I have no 64-bit PC.
This is no longer true. Now I have a system with Intel BLKDG965SSCK
motherboard, Intel Core 2 Duo E6420 CPU, and 2 GB or RAM. My first task
is to fix the LiveCD so that it works well on this computer (this means
updating the kernel).
--
Alexander E.
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
Jeremy Huntwork wrote:
As far as a native x86_64 build is concerned, I think that would be a
good candidate for 7.0.
Agreed. Personally, I'd like to see multilib support (since there is
only a 32-bit zsnes, and I do use the Flash plugin from
Jeremy Huntwork wrote:
Hmmm... Looking at the livecd repo, I'm seeing that Alexander has
included a 64-bit gcc and binutils. So a step in that direction has
already been taken.
They are cross-tools, and are installed in /tools (and thus, they don't
appear on the real CD). Also, gcc is just
On 7/14/07, Randy McMurchy [EMAIL PROTECTED] wrote:
Dan Nicholson wrote these words on 07/14/07 12:52 CST:
It's their stable branch which contains many backported bug fixes and
they're not producing any more releases. Is it better to use a known
buggy glibc-2.5? If glibc-2.5.1 was
Dan Nicholson wrote:
I think most of the issues brought up in this thread have been
addressed. I'd like to see if glibc-2.5.1 will happen, but we can
certainly just use the latest branch_update patch. The LiveCD is still
kind of up in the air, but I think most of the big concerns have been
On 6/8/07, Dan Nicholson [EMAIL PROTECTED] wrote:
So, I think it's about time we start pushing out a 6.3 release. What
do you guys think? Here are the outstanding issues I can think of.
Matthew, ping? Any thoughts on this?
I think most of the issues brought up in this thread have been
Dan Nicholson wrote these words on 07/14/07 10:34 CST:
I think most of the issues brought up in this thread have been
addressed. I'd like to see if glibc-2.5.1 will happen, but we can
certainly just use the latest branch_update patch.
Just out of curiosity, why are we continually updating the
Dan Nicholson wrote these words on 07/14/07 12:52 CST:
It's their stable branch which contains many backported bug fixes and
they're not producing any more releases. Is it better to use a known
buggy glibc-2.5? If glibc-2.5.1 was imminent, I'd say wait, but recent
history would suggest it's
Dan Nicholson wrote:
So, what are the major bugs?
1) Unclear status of wireless network support. The CD doesn't contain
wpa-supplicant and doesn't have firmware for most wireless network cards
(even though we qualify as ISV and thus can redistribute ipw firmware).
However, I can't test
I wrote:
1) Unclear status of wireless network support. The CD doesn't contain
wpa-supplicant and doesn't have firmware for most wireless network cards
(even though we qualify as ISV and thus can redistribute ipw firmware).
However, I can't test this because I don't have a wireless
I want to just say out front what my opinion of the LiveCD is before I
respond to individual points. The most important task of the livecd is
to provide a host with a known working kernel and toolchain to allow
people to build *LFS. Next, it should provide tools that allow the
*LFS support
Dan Nicholson wrote:
If you're using the toram option, you must remount the CD to use the
package tarballs in /lfs-sources.
I don't know if that's all that's correct. I didn't investigate when I
was using toram yesterday.
Now we have an additional variable: the -nosrc CD, which doesn't
On 6/11/07, Alexander E. Patrakov [EMAIL PROTECTED] wrote:
Dan Nicholson wrote:
If you're using the toram option, you must remount the CD to use the
package tarballs in /lfs-sources.
I don't know if that's all that's correct. I didn't investigate when I
was using toram yesterday.
Now
On 6/8/07, Alexander E. Patrakov [EMAIL PROTECTED] wrote:
Dan Nicholson wrote:
Anything else?
LiveCD. I simply have no possibility to fix all known bugs, so LFS 6.3 has
to be released without the CD and should not mention it at all.
OK. I think this should be top priority because we need to
Alexander E. Patrakov wrote:
Dan Nicholson wrote:
Anything else?
LiveCD. I simply have no possibility to fix all known bugs, so LFS 6.3 has
to be released without the CD and should not mention it at all.
My own issue with the livecd on the inspiron is actually the hardware,
not your
El Viernes, 8 de Junio de 2007 23:23, Dan Nicholson escribió:
So, I think it's about time we start pushing out a 6.3 release. What
do you guys think?
IMHO, just update to the packages listed now on Trac (except, of course, the
toolchain ones), and do package freezing to release 6.3 very soon.
Alexander E. Patrakov wrote:
LiveCD. I simply have no possibility to fix all known bugs, so LFS 6.3 has
to be released without the CD and should not mention it at all.
I would see nothing wrong with using a LiveCD with is running an older
version of LFS, but simply has the latest 6.3
So, I think it's about time we start pushing out a 6.3 release. What
do you guys think? Here are the outstanding issues I can think of.
* Linux-2.6.21: Yesterday I read this blog post from the Fedora kernel
maintainer,
Dave Jones:
http://kernelslacker.livejournal.com/79957.html
Doesn't
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
Dan Nicholson wrote:
* Udev rules: Alexander has posted in a couple other places that we
have broken rules for DVB and floppy device setup. Alexander/Bryan,
could you guys look at our ruleset and make sure they do everything
we want them to?
Dan Nicholson wrote:
Anything else?
LiveCD. I simply have no possibility to fix all known bugs, so LFS 6.3 has
to be released without the CD and should not mention it at all.
--
Alexander E. Patrakov
--
http://linuxfromscratch.org/mailman/listinfo/lfs-dev
FAQ:
20 matches
Mail list logo
