Re: Wording for configuring perl in ch6

2005-04-01 Thread Joel Miller
Andrew Benton wrote: I agree, but people tell me it's wrong to start sentences with "however" and "but" because they're linking words It's a perfectly legal sentence. In school, we used to call sentences that started like this "spoilers." I don't remember school a lot, but I do remember working

Re: 64-bit LFS

2005-04-01 Thread Ken Moffat
On Thu, 31 Mar 2005, Bruce Dubbs wrote: > I just got a new system for testing LFS builds. It is a Intel 3.2GHz P4 > system with "EM64T" technology. It came with RH Enterprise 3.0 "for > AMD64 and EM64T" preinstalled. 8-D > > I'm not really sure what the EM64T technology does, except Googling >

Re: Managed hotplug events

2005-04-01 Thread Matthew Burgess
Alexander E. Patrakov wrote: When the modified "udev" bootscript sets /sbin/udevsend as a handler, everything is ready. I thought the necessary changes had already got into the bootscripts repository. If not, please submit a bug report to bugzilla, preferably with a patch too. Thanks, Matt. --

Re: Wording for configuring perl in ch6

2005-04-01 Thread Matthew Burgess
Joel Miller wrote: We wouldn't have done exercises with them if it wasn't acceptable to use them. So are you telling me that all those Visual Basic exercises I did means it's actually acceptable to use in the real world? :) -- http://linuxfromscratch.org/mailman/listinfo/lfs-dev FAQ: http://www.l

LFS News Server

2005-04-01 Thread Jeremy Huntwork
Hi all: Posting this to the main lists so that all can see. As you're likely aware, there has been some trouble lately with our news server here. As of Wednesday, we had the server back online and the mail > news gateway was working effectively. However, the news > mail gateway was still not fu

Re: Wording for configuring perl in ch6

2005-04-01 Thread Matthew Burgess
TheOldFellow wrote: However, even in American these are just guidelines. But real English uses rule-breaking quite regularly for emphasis and contrast. LOL, thanks Richard :) I was also taught that conjunctions shouldn't be used at the start of sentences. Often, it seems the most natural way of

Re: Wording for configuring perl in ch6

2005-04-01 Thread Archaic
On Fri, Apr 01, 2005 at 05:13:48PM +0100, Matthew Burgess wrote: > Often, it seems the most natural way of <..> lol Case closed, your honor! -- Archaic Want control, education, and security from your operating system? Hardened Linux From Scratch http://www.linuxfromscratch.org/hlfs -- http:

Re: 6.1 release?

2005-04-01 Thread Jeremy Huntwork
On Wed, Mar 30, 2005 at 03:43:44PM -0700, Archaic wrote: > With the exception of the kernel changing every week, this book seems > rock solid. Add to that the 5 months since lfs-6 was release and it > seems it might be time to cut a testing branch? > > Opinions? > I think it's ready to go as well

Re: 6.1 release?

2005-04-01 Thread Matthew Burgess
On Wed, Mar 30, 2005 at 04:55:18PM -0600, Randy McMurchy wrote: I mentioned this same thing at the beginning of this month. I have several systems running current SVN versions of LFS without any issues I can think of. Sorry for not replying to the OP - it got lost in the recent news-server outage

Re: 6.1 release?

2005-04-01 Thread Randy McMurchy
Jeremy Huntwork wrote these words on 04/01/05 11:12 CST: > I think it's ready to go as well. It would nicely bring it all up-to-date > and fix a few bugs, notably, the strip bug and the 2.6.8.1 cd-writing bug. > I'd like to see a release happen now. Probably best to delay it for a while, as a bra

Re: 6.1 release?

2005-04-01 Thread Matthew Burgess
Randy McMurchy wrote: Probably best to delay it for a while, as a brand new release of the bootscripts was introduced to LFS a couple of days ago. These bootscripts probably should be tested out before releasing a version which includes them. Opinions? That's what the branch is for :) I'm thinking

Re: 6.1 release?

2005-04-01 Thread Jeremy Huntwork
Randy McMurchy wrote: Probably best to delay it for a while, as a brand new release of the bootscripts was introduced to LFS a couple of days ago. These bootscripts probably should be tested out before releasing a version which includes them. Opinions? The changes to the bootscripts seemed minimal,

Banned file: .exe in mail from you

2005-04-01 Thread MAILER DAEMON
BANNED FILENAME ALERT Your message to: [EMAIL PROTECTED] was blocked by our Spam Firewall. The email you sent with the following subject has NOT BEEN DELIVERED: Subject: Re: Its me An attachment in that mail was of a file type that the Spam Firewall is set to block. Reporting-MTA: dns; barra

Iptables/Firewall

2005-04-01 Thread Andrew Benton
In response to a post on BLFS support I looked at the pages in my current version of BLFS (svn-20050331) and I can't see where it says to install the iptables bootscript. Is it just me, or is this a bug in the book? Whilst I'm here on iptables business, in the personal firewall script it sets the

6.1 release branch

2005-04-01 Thread Matthew Burgess
Folks, I've just created the 6.1 release branch. For the incredibly impatient you can pull it from svn.linuxfromscratch.org/LFS/branches/6.1. Until then, you'll have to wait until I render the book and post a link to it :) The idea is that in roughly 2 weeks we'll release 6.1. So, can everyon

Re: 6.1 release branch

2005-04-01 Thread Jeremy Huntwork
Matthew Burgess wrote: Folks, I've just created the 6.1 release branch. For the incredibly impatient you can pull it from svn.linuxfromscratch.org/LFS/branches/6.1. Until then, you'll have to wait until I render the book and post a link to it :) The idea is that in roughly 2 weeks we'll releas

Re: 6.1 release branch

2005-04-01 Thread M.Canales.es
Matthew Burgess escribió en lfs.dev el Viernes, 1 de Abril de 2005 20:22: > > Editors: Please *do not* commit to this branch unless: > > a) It's an obvious typo/spelling mistake > b) It fixes a problem reported against the 6.1 branch either on the > mailing lists or bugzilla > c) The fix has alr

Re: 6.1 release branch

2005-04-01 Thread Matthew Burgess
M.Canales.es wrote: d) Is a PDF look fix ;-) Of course. I will trust anything from anyone (as long as their name is Manuel :)) that touches stuff in the stylesheets/ directory as there is some serious black-magic juju going on in there :) However, rule c) still applies - i.e. if the fix is com

[OT]Re: LFS News Server

2005-04-01 Thread Matthew Burgess
Jeremy Huntwork wrote: If you want to post to a list, you can still do so via email at the corresponding list address. Is there a way to configure Thunderbird to set the recipient automatically for me? I prefer to use the news server, but can accept that keeping it read-only is probably the bes

Re: Wording for configuring perl in ch6

2005-04-01 Thread Joel Miller
Matthew Burgess wrote: Joel Miller wrote: We wouldn't have done exercises with them if it wasn't acceptable to use them. So are you telling me that all those Visual Basic exercises I did means it's actually acceptable to use in the real world? :) toucher -- Registered LFS User 6929 Registered Li

Post-6.1 plans/roadmap

2005-04-01 Thread Matthew Burgess
Folks, Now that the 6.1 cycle has started, here's what's on the cards for future LFS releases. Whether these make it all into the same release, or whether they're staggered over multiple releases depends on how quickly they can stabilise and the amount of development and testing resources avai

Re: 6.1 release branch

2005-04-01 Thread M.Canales.es
Matthew Burgess escribió en lfs.dev el Viernes, 1 de Abril de 2005 20:48: > M.Canales.es wrote: > >> d) Is a PDF look fix ;-) > > Of course. I will trust anything from anyone (as long as their name is > Manuel :)) that touches stuff in the stylesheets/ directory as there is > some serious black

Re: 6.1 release branch

2005-04-01 Thread Justin R. Knierim
Matthew Burgess wrote: I've just created the 6.1 release branch. For the incredibly impatient you can pull it from For testers, I just put together a 6.1-20050401 package tarball. It will be available on the mirrors shortly, as soon as they all sync. -- Justin R. Knierim LFS FTP M

Re: 64-bit LFS

2005-04-01 Thread Andy Neebel
On Mar 31, 2005 10:25 PM, Bruce Dubbs <[EMAIL PROTECTED]> wrote: > I just got a new system for testing LFS builds. It is a Intel 3.2GHz P4 > system with "EM64T" technology. It came with RH Enterprise 3.0 "for > AMD64 and EM64T" preinstalled. > > I'm not really sure what the EM64T technology does

Re: 6.1 release branch

2005-04-01 Thread Matthew Burgess
Matthew Burgess wrote: Until then, you'll have to wait until I render the book and post a link to it :) OK, it's now rendered and available at http://www.linuxfromscratch.org/lfs/view/testing/. Regards, Matt. -- http://linuxfromscratch.org/mailman/listinfo/lfs-dev FAQ: http://www.linuxfromscratch

Re: Wording for configuring perl in ch6

2005-04-01 Thread Bruce Dubbs
Matthew Burgess wrote: I was also taught that conjunctions shouldn't be used at the start of sentences. But you can. :) -- Bruce -- http://linuxfromscratch.org/mailman/listinfo/lfs-dev FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page

Re: 6.1 release branch

2005-04-01 Thread Bryan Kadzban
Matthew Burgess wrote: The idea is that in roughly 2 weeks we'll release 6.1. So, can everyone please hammer this one to death and report all problems to this list and preferably also to bugzilla so we can keep track of them. Two issues I've seen so far: 1) The URL for less may not be right. Less

Re: Post-6.1 plans/roadmap

2005-04-01 Thread Greg Schafer
Matthew Burgess wrote: > * GCC-4.0 - 4.0.0 is currently scheduled for April 15th. There's some > interesting changes for us (like they went and removed our beloved spec > file!) as well as compile and execution time speedups and the usual > bunch of bug fixes. There's also currently issues wi

Re: 6.1 release branch

2005-04-01 Thread Jeremy Huntwork
Bryan Kadzban wrote: Matthew Burgess wrote: The idea is that in roughly 2 weeks we'll release 6.1. So, can everyone please hammer this one to death and report all problems to this list and preferably also to bugzilla so we can keep track of them. Two issues I've seen so far: 1) The URL for less m

Re: 6.1 release branch

2005-04-01 Thread Archaic
On Fri, Apr 01, 2005 at 09:04:21PM -0500, Jeremy Huntwork wrote: > > http://www.greenwoodsoftware.com/less/less-382.tar.gz The book doesn't use explicit links to packages. GNU should be used, IMO. -- Archaic Want control, education, and security from your operating system? Hardened Linux From

This is LFS

2005-04-01 Thread [EMAIL PROTECTED]
> diy-linux.org/pipermail/ > > Regards > Greg > -- Excuse me, but this is the Linux From Scratch project development list. sash -- http://linuxfromscratch.org/mailman/listinfo/lfs-dev FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page

Re: Post-6.1 plans/roadmap

2005-04-01 Thread Robert Connolly
gcc4 segfaults fairly easily still. I don't see how they're going to stabilize it in the next two weeks. Using -O3/-finline-functions on glibc causes a segfault from gcc4, its fixed in the rhl branch weeks ago but the 4.0 branch has yet to include the fix. Passing -funroll-loops to vim63 causes

Re: Managed hotplug events

2005-04-01 Thread Alexander E. Patrakov
(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 changes had already got into the bootscr

Re: Managed hotplug events

2005-04-01 Thread Matthew Burgess
Alexander E. Patrakov wrote: What remains is reported at: http://bugs.linuxfromscratch.org/show_bug.cgi?id=1068 Many thanks Alexander. Those don't seem too risky to get into 6.1, or are they? They certainly seem much closer to bug fixes than introducing new functionality. Cheers, Matt. -- http

Re: Post-6.1 plans/roadmap

2005-04-01 Thread Matthew Burgess
Greg Schafer wrote: In case anyone is interested, I have a GCC4 based build working really well. Did they get the fixincludes in there to allow building from a host with a stock glibc-2.3.4 install on it - i.e. they fix the invalid C in pthread.h? If not, then we'll have to wait until at least a