Re: New BLFS Editor
Jeremy Huntwork wrote: Bruce Dubbs wrote: 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. I was a little early on blfs-book I guess. ;) Again, nice to see you with a bit more official status, Richard. -- JH Congrats from me too. -- Shane Shields Registered LFS Compiler: 7582 To drink the WINE of success you must first seek the sayings of source Anyone sending unwanted advertising e-mail to this address will be charged $25 for network traffic and computing time. By extracting my address from this message or its header, you agree to these terms. -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: Upcoming package freeze
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 be P1 (security) bugs. When all the targeted bugs are fixed, I'll generate the -pre1 release. OK, I've gone through Bugzilla again and made a few changes. :) There are now 25 bugs targeted for 6.1. Most are text changes. I left the following packages that need updates. Bug Package 1420 iptables 1183 exim 1350 kerberos 1430 LIBPCAP 1443 Firefox 1444 Thunderbird 1459 Mozilla 1369 Tidy 1475 Ethereal I chose these because of either security issues or because of the popularity of the packages. Also, they are not, for the most part, dependencies of other packages. Note that I also added a 6.2 target to bugzilla and a separate 'Product' for the editors guide. As of this time, I would like to freeze all other package updates until after the 6.1 branch is cut. I am targeting Monday for the -pre1 release, so any help in hammering out the 6.1 bugs will be appreciated. If anyone thinks that I left out something critical or put in too much, please let me know. -- Bruce I'd like to add fcron-2.6.7 (Bug#1482) because I'm updating the text to fix bug#1472, and it has a fix for a nasty mailing bug. I have to text it anyway. Richard. -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: Bugs for 6.1 (1019 Alsa restore)
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 modifications) is not a distro problem. -- Alexander E. Patrakov -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: New BLFS Editor
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 Canales Esparcia Usuario de LFS nº2886: http://www.linuxfromscratch.org LFS en castellano: http://www.escomposlinux.org/lfs-es http://www.lfs-es.com TLDP-ES: http://es.tldp.org -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: Upcoming package freeze
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. Changing to future. -- Bruce -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Speling
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 someone wants to do some more, let me know.
-- Bruce
--
http://linuxfromscratch.org/mailman/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
Re: Speling
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 through the
b's, but if someone wants to do some more, let me know.
ouch!
I'll start on 'h'.
--
David Jensen
--
http://linuxfromscratch.org/mailman/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
Re: Speling
David Jensen wrote: I'll start on 'h'. Done with 'h and i'. Should I commit? snip from Sysstat 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 FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: Upcoming package freeze
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 to commit it now. Richard. -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: Exim
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 increase the fuzz to get it to apply, you really need to look at the code to make sure it will still do the right thing. Sounds as if Bruce did that, but I think it could set a bad example. Ken -- das eine Mal als Tragödie, das andere Mal als Farce -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: Bugs for 6.1 (1019 Alsa restore)
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 example (that we would use otherwise without much modifications) is not a distro problem. Alex, I stand corrected...it's definately a bug. Care to see if below is a permanent fix? No start option in alsa scirpt anymore, just the dev.d helperneed to mention that if more than one sound card is installed that you'll need to adjust the dev.d script and directory. I backgrounded the entire while loop (the user never sees a delay) and set a default timeout of 20 seconds..this can be increased, but I doubt it is necessary. Can you test this on the 486 you had mentioned previously? [EMAIL PROTECTED] ~]# cat /etc/dev.d/snd/controlC0/alsa.dev #!/bin/sh -e x=0 while [ $x -lt 20 ] do sleep 1 if [ -f /usr/sbin/alsactl ]; then /usr/sbin/alsactl restore 0 exit 0 else if [ $x -eq 20 ]; then exit 1 fi fi done [EMAIL PROTECTED] ~]# -- DJ Lucas -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: Temporarily remove Courier from BLFS?
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 reason being is that recent versions have an entirely new build order. Some of Courier has been moved to other packages and things simply don't build the way BLFS says they do. I can only think that it will be a support-nightmare when folks see that we are 7 revs behind and try to use a more current version. I think we should simply eliminate this problem by commenting out Courier from the book for the 6.1 release. Thoughts from others? 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. -- DJ Lucas -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: Temporarily remove Courier from BLFS?
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 current Courier instructions don't work (if any version other than the year-old version in BLFS is used) and there is no hint or other material to assist readers. Courier is the oldest outstanding bug in BLFS for a package update. There obviously is no Editor interest in keeping up this package. It appears to be falling into obligatory update mode instead of all right, a new version, let's get BLFS updated! And from the looks of things, nobody even has enough interest to even do the obligatory updates. :-) -- Randy rmlscsi: [GNU ld version 2.15.94.0.2 20041220] [gcc (GCC) 3.4.3] [GNU C Library stable release version 2.3.4] [Linux 2.6.10 i686] 22:00:01 up 118 days, 21:33, 2 users, load average: 0.31, 0.16, 0.16 -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: Bugs for 6.1 (1019 Alsa restore)
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. -- Alexander E. Patrakov -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: Bugs for 6.1 (1019 Alsa restore)
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 two identical cards
and alsactl store.
Success! Unfortunately, not all the cards were identical, but two of
them were. I have another, but I'd have to drop an important box to get
to it, and it's not necessary anyway. Test case was three SBLive! cards
(EMU10K1 chipset). One is a CT1(I can't read it exactly, haven't
removed it from the machine) and two CT3830s (Identical). I sent
asound.state to my home dir on belgarath, but the test case works as
expected...cold boot to make certain that nothing residual or anything
of that nature.
For recap, here are the contents of the alsa helper:
[EMAIL PROTECTED] ~]# cat /etc/dev.d/snd/alsa.dev
#!/bin/sh -e
DEV_BASENAME=${DEVNAME##*/}
x=0
while [ $x -lt 20 ]
do
sleep 1
if [ -f /usr/sbin/alsactl ]; then
case $DEV_BASENAME in
controlC[0-7])
N=${DEV_BASENAME#controlC}
alsactl restore $N
;;
esac
exit 0
else
if [ $x -eq 20 ]; then
exit 1
fi
fi
done
[EMAIL PROTECTED] ~]#
Next issue with this is the sample soundfont loading. I would think it
could be reasonably assumed that machines requiring soundfonts to be
loaded would have some horsepower and that timing is not an issuebut
assumptions are bad! We can leave well enough alone, or add a second
specific handler for individual devices. Alex, am I correct in my
assumption that the alsa.dev script will run before any device specific
scripts, but the device scripts will run in order? I still don't have
access to my soundfonts...or sfxload for that matter, but it should be
easy enough to find.
-- DJ Lucas
--
http://linuxfromscratch.org/mailman/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
