Alexander E. Patrakov wrote:
Richard A Downing wrote:
Should we ask the LFS guys to take that out of their rules, so that we
can deal with it in BLFS? This kind of relates to my comment that the
explanation for some of this is buried in the LFS book (well the alsa
modules stuff anyway).
Thi
Alexander E. Patrakov wrote:
> Forgot to say a trivial thing: IMHO it is easier to explain
> mknod+chown+chmod than kernel+modprobe+udev.
A master of understatement!
-- Bruce
--
http://linuxfromscratch.org/mailman/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscr
Magnus Larsson wrote:
Hello DJ Lucas,
Thank you for your build instruction. It works for me, besides some problems
related to Impress and templates. Impress will crash when selecting a
template.
Test:
1) Start simpress. The presentation wizard starts.
2) Select "From template".
3) OpenOffi
I wrote:
Richard A Downing wrote:
What EXACTLY was wrong with MAKEDEV? So it created a few extra nodes
and didn't create /dev/agpgart and /dev/hda9. Missing devices were the
only valid complaint AFAIK. Udev's ability to handle hot-plugged devices
was considered a not-very-needed feature.
Richard A Downing wrote:
I'm sorry I started this again now. I have to say I am more confused
than ever. Do the guys (I use the term loosly, as 'imbeciles' seems
more appropriate right now) upstream have any idea of the difficulties
they are creating by this almost undocumented mess?
No, the
Richard A Downing wrote:
Should we ask the LFS guys to take that out of their rules, so that we
can deal with it in BLFS? This kind of relates to my comment that the
explanation for some of this is buried in the LFS book (well the alsa
modules stuff anyway).
This is buried in the LFS book for
On Tue, Oct 25, 2005 at 09:56:35PM -0500, Randy McMurchy wrote:
>
> 29 is fine, except in February. That's why I just knocked it down
> to 25.
Okay. Will keep that in mind.
> I suppose the hint is now obsolete, and should be moved to wherever
> obsolete hints are moved to.
Will take care of tha
Archaic wrote these words on 10/25/05 21:30 CST:
> Referencing both Randy's hint and the book, I see that the warning for
> "Number of daily files to keep" in the hint is 29. In the book it is 25.
>
> Just wondering if the difference is intentional or not.
29 is fine, except in February. That's w
Referencing both Randy's hint and the book, I see that the warning for
"Number of daily files to keep" in the hint is 29. In the book it is 25.
Just wondering if the difference is intentional or not.
--
Archaic
Want control, education, and security from your operating system?
Hardened Linux Fro
Dan Nicholson wrote:
If anything is
written, I'd be glad to peruse it and give an opinion as someone who
still has only the loosest grasp of how the hardware is set up.
Well, I've written some notes up on this, though they're not entirely
accurate.
http://www.linuxfromscratch.org/pipermail/lf
On 10/25/05, Matthew Burgess <[EMAIL PROTECTED]> wrote:
> What I do think could do with improving, and it will do with a revamped
> udev setup in LFS, is the explanation of how udev works and a general
> explanation of how to set up rules and a pointer to examples as provided
> by BLFS for common t
Randy McMurchy wrote:
This now appears to be a continuation of the previous threads on
LFS-Dev about should or should not LFS define rules.
And I'll ask again, aside from plain ol' `cat' (which isn't useful for
anything than raw PCM files, IIRC), what tools in LFS can utilise the
sound devic
Randy McMurchy wrote:
> Richard A Downing wrote these words on 10/25/05 12:16 CST:
>
>
>>Should we ask the LFS guys to take that out of their rules, so that we
>>can deal with it in BLFS?
>
>
> I am against that idea because the device nodes are going to be
> created regardless if there is a r
Richard A Downing wrote:
> Alexander E. Patrakov wrote:
>
>>Richard A Downing wrote:
>>
>>
>>>Guys,
>>>
>>>The method documented in the svn book doesn't work for me. The script
>>>that the 15-alsa.rules file associates with udev's discovery of a
>>>control interface is never apparently called (Ud
Jeremy Huntwork wrote:
> Richard A Downing wrote:
>
>> Now I have it working, and all I did was to to mv the rules file
>> elsewhere and back again. This has me completely baffled :-)
>
>
> Gremlins.
>
> --
> JH
Heck, do you think so? I saw that movie. Maybe I should burn the
computer, or
Randy McMurchy wrote:
Bruce Dubbs wrote these words on 10/25/05 11:16 CST:
I also don't really understand why udev is necessary for sound. Sound
cards are not something one normally plugs into the computer while power
is applied.
That would depend on how one defines "sound card". When I pl
Randy McMurchy wrote:
> Bruce Dubbs wrote these words on 10/25/05 11:16 CST:
>
>
>>I also don't really understand why udev is necessary for sound. Sound
>>cards are not something one normally plugs into the computer while power
>>is applied.
>
>
> That would depend on how one defines "sound ca
Bruce Dubbs wrote these words on 10/25/05 11:16 CST:
> I also don't really understand why udev is necessary for sound. Sound
> cards are not something one normally plugs into the computer while power
> is applied.
That would depend on how one defines "sound card". When I plug in
my Plantronics U
Randy McMurchy wrote:
> Richard A Downing wrote these words on 10/25/05 10:51 CST:
>
>
>>and that doesn't change anything. It still never calls the script.
>>
>>Now I'm out of ideas.
>
>
> You could always go back to the way it was by having it restore
> the volumes at boot (from /etc/rc.d/ini
Richard A Downing wrote:
Now I have it working, and all I did was to to mv the rules file
elsewhere and back again. This has me completely baffled :-)
Gremlins.
--
JH
--
http://linuxfromscratch.org/mailman/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See t
Randy McMurchy wrote:
> Richard A Downing wrote these words on 10/25/05 10:51 CST:
>
>
>>and that doesn't change anything. It still never calls the script.
>>
>>Now I'm out of ideas.
>
>
> You could always go back to the way it was by having it restore
> the volumes at boot (from /etc/rc.d/ini
Alexander E. Patrakov wrote:
> Richard A Downing wrote:
>
>> Guys,
>>
>> The method documented in the svn book doesn't work for me. The script
>> that the 15-alsa.rules file associates with udev's discovery of a
>> control interface is never apparently called (Udev-063).
Now I have it working,
Richard A Downing wrote these words on 10/25/05 10:51 CST:
> and that doesn't change anything. It still never calls the script.
>
> Now I'm out of ideas.
You could always go back to the way it was by having it restore
the volumes at boot (from /etc/rc.d/init.d/alsa):
start)
Richard A Downing wrote:
> Alexander E. Patrakov wrote:
>
>>Richard A Downing wrote:
I'll try 070 (a la SVN LFS) and report back.
and that doesn't change anything. It still never calls the script.
Now I'm out of ideas.
R.
--
http://linuxfromscratch.org/mailman/listinfo/blfs-dev
FAQ: http://
Richard A Downing wrote:
Guys,
The method documented in the svn book doesn't work for me. The script
that the 15-alsa.rules file associates with udev's discovery of a
control interface is never apparently called (Udev-063).
could you please try replacing this line:
KERNEL=="controlC[0-9]*",
Bruce Dubbs wrote:
> Richard A Downing wrote:
>
>
>>I also don't seem to be able to get the snd_pcm_oss module loaded, which
>>is required for realplayer.
>
>
> Can it be loaded with modprobe?
> -- Bruce
Yes, and of course, I can load it at boot time. My concern is that the
book gives no gu
Richard A Downing wrote:
> I also don't seem to be able to get the snd_pcm_oss module loaded, which
> is required for realplayer.
Can it be loaded with modprobe?
-- Bruce
--
http://linuxfromscratch.org/mailman/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: Se
27 matches
Mail list logo
