Peter wrote:
> So this should be added to the NOTE to clarify that is is intentional
> and point to the bash reference ???
I have tried to put something that makes sense into the NOTE. See r7798.
signature.asc
Description: OpenPGP digital signature
--
http://linuxfromscratch.org/mailman/listin
On Thu, Sep 21, 2006 at 08:15:42PM +0100, Matthew Burgess wrote:
> Ken Moffat wrote:
> >
> > I totally fail to understand that last statement.
>
> Sorry, as you and Manuel rightly pointed out I screwed that last
> statement up. Maybe I shouldn't bother with any LFS stuff tonight? :-)
>
Referri
Matthew Burgess linuxfromscratch.org> writes:
> The quotes are simply wrong in the case of the udev rules as it will
> cause the \(newline) sequence to appear in the rules file as-is, which
> won't do the right thing, AIUI.
So this should be added to the NOTE to clarify that
is is intentional
Ken Moffat wrote:
On Thu, Sep 21, 2006 at 07:33:16PM +0100, Matthew Burgess wrote:
Sorry about that complete and utter lie above. It's the other way
around, of course. If EOF is unquoted, shell expansion occurs within
the here-document. Additionally, as bash(1) states, newline handling
diff
El Jueves, 21 de Septiembre de 2006 20:33, Matthew Burgess escribió:
> Sorry about that complete and utter lie above. It's the other way
> around, of course. If EOF is unquoted, shell expansion occurs within
> the here-document.
Yes.
> Additionally, as bash(1) states, newline handling
> diff
On Thu, Sep 21, 2006 at 07:33:16PM +0100, Matthew Burgess wrote:
>
> Sorry about that complete and utter lie above. It's the other way
> around, of course. If EOF is unquoted, shell expansion occurs within
> the here-document. Additionally, as bash(1) states, newline handling
> differs betwe
Matthew Burgess linuxfromscratch.org> writes:
> Sorry about that complete and utter lie above. It's the other way
> around, of course. If EOF is unquoted, shell expansion occurs within
> the here-document. Additionally, as bash(1) states, newline handling
> differs between the quoted and un
Matthew Burgess wrote:
Peter wrote:
ISTR also some failure that was reported on
support due to EOF not being quoted.
The only failure you'll get by not quoting EOF is if the contents of the
here-document contain shell variables that you want to have expanded.
I'd agree that consistency woul
On Thu, Sep 21, 2006 at 06:00:19PM +, Peter wrote:
>
> All other examples througout the book
> are shown using the quotes,
> so consistency is the main reason.
> Note also that some of the typos are:
> cat >/
> but throughout the book it is:
> cat > /
>
This sounds like another of the "all
Peter wrote:
ISTR also some failure that was reported on
support due to EOF not being quoted.
The only failure you'll get by not quoting EOF is if the contents of the
here-document contain shell variables that you want to have expanded.
I'd agree that consistency would be nice to have, and t
El Jueves, 21 de Septiembre de 2006 19:32, Peter Ennis escribió:
>
> cat >/etc/udev/rules.d/82-cdrom.rules << EOF
> sbould be:
> cat > /etc/udev/rules.d/82-cdrom.rules << "EOF"
Not.
That EOF must not be quoted to can have each udev rule spited in the book, due
layout issues, but dumped on an u
Ken Moffat linuxfromscratch.org> writes:
>
> Peter, why do you think EOF needs to be quoted on the 'cat' line ?
>
> Ken
All other examples througout the book
are shown using the quotes,
so consistency is the main reason.
Note also that some of the typos are:
cat >/
but throughout the book it
On Thu, Sep 21, 2006 at 10:32:21AM -0700, Peter Ennis wrote:
>
> LFS 6.2 Stable
>
> 7.12.1. CD-ROM symlinks
>
> cat >/etc/udev/rules.d/82-cdrom.rules << EOF
> sbould be:
> cat > /etc/udev/rules.d/82-cdrom.rules << "EOF"
>
[ snip more of the same ]
Peter, why do you think EOF needs to be quot
LFS 6.2 Stable
7.12.1. CD-ROM symlinks
cat >/etc/udev/rules.d/82-cdrom.rules << EOF
sbould be:
cat > /etc/udev/rules.d/82-cdrom.rules << "EOF"
The second approach yields:
cat >/etc/udev/rules.d/82-cdrom.rules << EOF
should be:
The second approach yields:
cat > /etc/udev/rules.d/82-cdrom.rule
Bruce Dubbs wrote:
Peter Ennis wrote:
Does it automatically get sent to the dev list when entered
via Trac
Yes.
More accurately, Peter, Trac notifications go to the lfs-book list, as
do Subversion commits. Practically speaking, there is no difference as
editors are subscribed to both lf
Peter Ennis wrote:
> Does it automatically get sent to the dev list when entered
> via Trac
Yes.
or should I do that also?
No.
-- Bruce
--
http://linuxfromscratch.org/mailman/listinfo/lfs-dev
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page
Dan Nicholson gmail.com> writes:
> Maybe
> Alexander knows better. Here's one way to do it.
>
> $ ls -l /sys/class/net/*/device
> lrwxrwxrwx 1 root root 0 2006-08-29 06:50 /sys/class/net/eth0/device
> -> ../../../devices/pci:00/:00:0f.0
>
> $ udevinfo -a -p /class/net/eth0
...>
> loo
Matthew Burgess linuxfromscratch.org> writes:
>
> Peter,
>
> Would you mind putting this issue in Trac [0] please? > [0]
http://wiki.linuxfromscratch.org/lfs/newticket
>
OK. I will go through the posts and add them as "Enhancement",
or whatever seems appropriate, to Trac.
Does it automati
On 8/29/06, Peter Ennis <[EMAIL PROTECTED]> wrote:
LFS 6.2
Capitalization Issue:
=
7.13.1. Creating stable names for network interfaces
^ ^ ^ ^
Thanks.
Udev Stuff:
===
Reading section 7.13.1 it mentions
"If you are going to
Peter Ennis wrote:
LFS 6.2
Capitalization Issue:
=
7.13.1. Creating stable names for network interfaces
^ ^ ^ ^
Udev Stuff:
===
Reading section 7.13.1 it mentions
"If you are going to use the bus position as a key, create Udev r
LFS 6.2
Capitalization Issue:
=
7.13.1. Creating stable names for network interfaces
^ ^ ^ ^
Udev Stuff:
===
Reading section 7.13.1 it mentions
"If you are going to use the bus position as a key, create Udev rules
similar to the
Peter Ennis wrote:
>
1. Case discrepancy:
>
2. Case discrepancies:
Thanks Peter. Fixed in r7778.
--
http://linuxfromscratch.org/mailman/listinfo/lfs-dev
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page
LFS 6.2
1. Case discrepancy:
7.5. Configuring the setclock Script
7.7. Configuring the sysklogd script
^^
7.10. Configuring the localnet Script
7.13. Configuring the network Script
2. Case discrepancies:
7. Setting Up System Bootscripts
7.3. How Do T
Beyond Linux From Scratch - Version svn-20060809
Part II. Post LFS Configuration and Extra Software
http://www.linuxfromscratch.org/blfs/view/svn/postlfs/config.html#postlfs-config-bootdisk
Creating a Bootable CD-ROM
A hint that describes the instructions for creating this ISO imate
24 matches
Mail list logo