Bruce Dubbs wrote:
> Randy McMurchy wrote:
>
>>DJ Lucas wrote these words on 07/29/05 21:55 CST:
>>
> OK. I'm going to take it out until there is an interest in it. There
> have been only seven messages in blfs-support this year. The interest
> is weak and no one wants to bother with it.
F
Alexander E. Patrakov wrote:
> DJ Lucas wrote:
>
>> I have 4 or 5 SBLive! cards (all identical)...lets see
>> what happens. Never had more than 2 in a single PC before. :-)
>
>
> For me to remove the FIXME, it would be sufficient to post
> /etc/asound.state after setting different volumes on t
Alexander E. Patrakov wrote:
> DJ Lucas wrote:
>
>> I have 4 or 5 SBLive! cards (all identical)...lets see
>> what happens. Never had more than 2 in a single PC before. :-)
>
>
> For me to remove the FIXME, it would be sufficient to post
> /etc/asound.state after setting different volumes on t
DJ Lucas wrote:
I have 4 or 5 SBLive! cards (all identical)...lets see
what happens. Never had more than 2 in a single PC before. :-)
For me to remove the FIXME, it would be sufficient to post
/etc/asound.state after setting different volumes on two identical cards
and "alsactl store".
-
Randy McMurchy wrote:
> DJ Lucas wrote these words on 07/29/05 21:55 CST:
>
>
>>I have no preference. I had seen the 6.2 target and unassigned myself
>>till after release. I'll update it for 6.1 if it's deemed important
>>enough, else comment it out and we'll get it ready for readmission in 6.2
Alexander E. Patrakov wrote:
> DJ Lucas wrote:
>>
>> need to mention that if more than one sound card is
>> installed that you'll need to adjust the dev.d script and directory.
>
>
> No need to adjust the script if you replace "alsactl restore 0" with:
>
> DEV_BASENAME="${DEVNAME##*/}"
> case "
DJ Lucas wrote:
Alexander E. Patrakov wrote:
DJ Lucas wrote:
No..it is not their problem. It is definately a distro problem.
Even if they supply the example dev.d script?
udev-064/etc/dev.d/snd/controlC0/alsa.dev:
#!/bin/sh -e
exec /usr/sbin/alsactl restore 0
IMHO a bug in the upstream examp
DJ Lucas wrote these words on 07/29/05 21:55 CST:
> I have no preference. I had seen the 6.2 target and unassigned myself
> till after release. I'll update it for 6.1 if it's deemed important
> enough, else comment it out and we'll get it ready for readmission in 6.2.
My point is that the curre
Randy McMurchy wrote:
> Hi all,
>
> I am recommending to temporarily remove Courier from the BLFS book
> until after 6.1 is released.
>
> BLFS should not release such an old package (7 revs behind and almost
> a year has gone by since BLFS has updated Courier). This is
> deplorable.
>
> The reas
Hi all,
I am recommending to temporarily remove Courier from the BLFS book
until after 6.1 is released.
BLFS should not release such an old package (7 revs behind and almost
a year has gone by since BLFS has updated Courier). This is
deplorable.
The reason being is that recent versions have an e
Alexander E. Patrakov wrote:
> DJ Lucas wrote:
>
>
>>No..it is not their problem. It is definately a distro problem.
>
>
> Even if they supply the example dev.d script?
>
> udev-064/etc/dev.d/snd/controlC0/alsa.dev:
>
> #!/bin/sh -e
> exec /usr/sbin/alsactl restore 0
>
> IMHO a bug in the u
Ken Moffat wrote:
> On Fri, 29 Jul 2005, Randy McMurchy wrote:
>
>
>>Not to mention that the man page says that increasing the fuzz
>>factor can result in a faulty patch. My feeling is that using the
>>-F flag is encouraging readers to do something which should really
>>be discouraged.
>>
>
> I
On Fri, 29 Jul 2005, Randy McMurchy wrote:
>
> Not to mention that the man page says that increasing the fuzz
> factor can result in a faulty patch. My feeling is that using the
> -F flag is encouraging readers to do something which should really
> be discouraged.
>
Indeed. If you have to increa
Bruce Dubbs wrote these words on 07/29/05 16:57 CST:
> I'm undecided how to handle this. Using the -F option to patch is
> educational and means we don't need to change the patch at all. OTOH, a
> regenerated patch would apply cleanly but would mean more work.
>
> I'm inclined to use the -F opt
I'm looking at the update to exim and the Berkeley patch still seems to
be relevant. The problem is that the locations have changed slightly.
When I do an ordinary patch, I get:
$ patch -Np1 -i ../exim-4.43-db43-1.patch
patching file src/exim_dbmbuild.c
Hunk #1 FAILED at 60.
1 out of 1 hunk FAILE
Guys,
can I propose upgrading midnight commander to the recently-released
4.6.1 before the 6.1 release ? This fixes a number of vulnerabilities
in 4.6.0 (filed with details as bug 1485).
Ken
--
das eine Mal als Tragödie, das andere Mal als Farce
--
http://linuxfromscratch.org/mailman/listin
grrrlgeek wrote:
Hi all,
In Chapter 10 of BLFS svn-20050728, the installation instructions for
ImageMagick say to run make check after make. In the ImageMagick
instructions on advanced-unix-source-installation.html, it says that
the make check should only be issued after make install. It ba
Hi all,
In Chapter 10 of BLFS svn-20050728, the installation
instructions for ImageMagick say to run make check after make. In the
ImageMagick instructions on advanced-unix-source-installation.html, it says that
the make check should only be issued after make install. It barfs
spectacularl
David Jensen wrote:
> David Jensen wrote:
>
>> I'll start on 'h'.
>
>
>
> Done with 'h and i'. Should I commit?
>
Sure.
>
>
> collect and historize performance and activity data.
>
> 'historize' makes me cringe, but it is in the dictionary. Maybe just
> 'record'?
LOL.
historize
\His"
TheOldFellow wrote:
> Richard A Downing wrote:
>
> I'm asking about fcron. I'm ready to commit it now.
OK. Go ahead.
-- Bruce
--
http://linuxfromscratch.org/mailman/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
Richard A Downing wrote:
>
> I'd like to add fcron-2.9.7 (Bug#1482) because I'm updating the text to
> fix bug#1472, and it has a fix for a nasty (fcron) mailing bug.
>
> I have tested it anyway.
>
> Richard.
Bruce,
You didn't rule on this, just on Mozilla. I'm asking about fcron. I'm
ready
David Jensen wrote:
I'll start on 'h'.
Done with 'h and i'. Should I commit?
collect and historize performance and activity data.
'historize' makes me cringe, but it is in the dictionary. Maybe just
'record'?
--
David Jensen
--
http://linuxfromscratch.org/mailman/listinfo/blfs-dev
Bruce Dubbs wrote:
Just for grins, I did:
find -name \*.xml -exec cat {} \; | ispell -H -l|sort|uniq
Do you think we might have a specialized vocabulary? :)
It's not hard to find the problem words. Just do:
grep -r "misspel" *
It's taking a while to fix the spelling errors. I've gone thr
Just for grins, I did:
find -name \*.xml -exec cat {} \; | ispell -H -l|sort|uniq
Do you think we might have a specialized vocabulary? :)
It's not hard to find the problem words. Just do:
grep -r "misspel" *
It's taking a while to fix the spelling errors. I've gone through the
b's, but if s
David Jensen wrote:
> Bruce Dubbs wrote:
>
>> 1459 Mozilla
>>
>>
> See my comments:
>
> http://blfs-bugs.linuxfromscratch.org/show_bug.cgi?id=1459
>
> Mail is buggy here. If it is not a security update, lets ignore it I
> downgraded because it is too annoying.
I missed that comment. Changi
Bruce Dubbs wrote:
1459 Mozilla
See my comments:
http://blfs-bugs.linuxfromscratch.org/show_bug.cgi?id=1459
Mail is buggy here. If it is not a security update, lets ignore it I
downgraded because it is too annoying.
--
David Jensen
--
http://linuxfromscratch.org/mailman/listinfo/blfs
El Jueves, 28 de Julio de 2005 19:02, Bruce Dubbs escribió:
> Please help me in welcoming Richard Downing (aka TheOldFellow) as a new
> BLFS Editor. Richard has been contributing to the lists since 2002 and
> will be a valuable asset to the BLFS Team.
Welcome on-board, Richard :-)
--
Manuel Ca
DJ Lucas wrote:
> No..it is not their problem. It is definately a distro problem.
Even if they supply the example dev.d script?
udev-064/etc/dev.d/snd/controlC0/alsa.dev:
#!/bin/sh -e
exec /usr/sbin/alsactl restore 0
IMHO a bug in the upstream example (that we would use otherwise without much
Bruce Dubbs wrote:
> Bruce Dubbs wrote:
>
>>Just a heads up.
>>
>> I will be going through BZ again tonight and re-examining the
>>outstanding bugs for the 6.1 release. When that is done, I anticipate a
>>package/bug freeze sometime tomorrow. After that, the only non-targeted
>>changes should b
29 matches
Mail list logo
