Re: NNTP Server
Richard A Downing wrote: Is there any realistic expectation that the facility to write to the lists via the NNTP service will be fixed? There is also a suggestion that it might be withdrawn. I came up with a plan that may well have fixed NNTP, but have been too busy to get around to it. As it necessesitates bringing down both NNTP and mailman for a while, then it also needs to be planned accordingly. I've also recently realised that if one CC's a list, only the 'To:' recipient gets a copy in their respective news group! I'm not sure whether it's always been like that or not, but it certainly seems broken to me! Matt. -- http://linuxfromscratch.org/mailman/listinfo/lfs-dev FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
Re: Shadow Group Support
Greg Schafer wrote:
Hi
Seeking feedback from anyone who is knowledgable about Shadow Group Support.
Oh, Greg, did you really have to bring this up? :)
The reason I ask - the latest shadow-4.0.11.1 has revamped the autoconfigury
to allow `--{dis,en}able-shadowgrp'.
That's also why I haven't upgraded shadow in a while. I saw your
battles with various broken versions from the DIY-Linux mailing list, so
decided to steer clear until it looked as if things had settled down.
FWIW, if upstream believe it shouldn't be on by default, then we should
follow their recommendation and drop the optional 'grpconv' command from
the book. I have no idea how common shadowed groups are out in the wild
though.
Cheers,
Matt.
--
http://linuxfromscratch.org/mailman/listinfo/lfs-dev
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page
Re: New BLFS Editor
Thank you all for your good wishes. I shall endeavour to limit the damage I cause by, for instance, my tipografikal inexaktytudes. Richard. -- http://linuxfromscratch.org/mailman/listinfo/lfs-dev FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
NNTP Server
Is there any realistic expectation that the facility to write to the lists via the NNTP service will be fixed? There is also a suggestion that it might be withdrawn. I ask, since I'm updating the text in the BLFS book, and I want to accurately reflect the true situation. My current draft reads: "All the mailing lists hosted at linuxfromscratch.org are also accessible via the NNTP server. All messages posted to a mailing list will be copied to its correspondent newsgroup. Note, however, that as this is written, it is not possible to write to the mailing lists via the NNTP service." R. -- http://linuxfromscratch.org/mailman/listinfo/lfs-dev FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
Re: Upcoming package freeze
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 -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: r6572 - in branches/cross-lfs/BOOK:
Randy McMurchy wrote: > [snip highly technical and best as I can figure, well-reasoned analysis] > > Thanks, Greg. I am interested in hearing from the pro-remove-headers > folks in response to your message. > > Hopefully, there will be continued discussion. This type of discussion > is, after all, what this list is all about. This thread provides some more evidence for keeping the "Glibc headers" step: http://gcc.gnu.org/ml/gcc/2005-07/msg01206.html I think it should be reasonably clear by now that building without the Glibc headers is not kosher. I hope that Jim fixes the Cross docs upon his return. Regards Greg -- http://www.diy-linux.org/ -- http://linuxfromscratch.org/mailman/listinfo/lfs-dev FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
Re: Bugs for 6.1 (1019 Alsa restore)
Alexander E. Patrakov wrote: > non-module, /usr is not a separate partition => works > module, /usr is not a separate partition => works > non-module, /usr is a separate partition => broken (upstream problem) It's not really an upstream problem. It's a local implementaion problem...if you need it at boot, you should have put it on the root partiton, or found a nice way to wait for the alsactl util to become availible. If you've done neither, then it's your own fault, or in this case, your distro's fault for not warning you. :-) > module, /usr is a separate partition => works > > This brokenness has been reported to linux-hotplug-devel, they suggest > moving alsactl to /sbin and its libraries to /lib. Of course they cannot > be serious. > Actually, yes they can be. That or the 'sit and spin' are the correct ways to handle it, which is why I'm looking at a bootscript only solution to handle it well after /usr is mounted. What I feel that saves BLFS a bit of headache in dealing with the wait time, is that the script will not likely be installed if a soundcard does not exist. The USB devices bring up an interesting twist, but a searching message could lead the user into finding their error before the timeout. However, having both is definately not badstarting the existing alsa script a second time results in a pretty green OK, but I don't know about sfxload. I need to find the default soundfont banks to test that, but I don't have the CD...will have a look around tomorrow. > Unfortunately, I cannot find my own post there. Should I repost? > No..it is not their problem. It is definately a distro problem. > > Bad, some people prefer pure-ALSA systems, therefore no /dev/dsp. > Whoops. Slip of the tounge (or fingers?). I had made that exact mistake once before on this list too. Yes definately '[ ! -d /dev/snd ]' should work much better if a sitNspin is needed. -- DJ Lucas -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Shadow Group Support
Hi
Seeking feedback from anyone who is knowledgable about Shadow Group Support.
Is it actually used much in the wild?
How useful really is it?
Should the shadow pkg have it switched on by default?
The reason I ask - the latest shadow-4.0.11.1 has revamped the autoconfigury
to allow `--{dis,en}able-shadowgrp'. Unfortunately, while the `--help'
output says it defaults to "yes" it actually defaults to "no". So if you
want Shadow Group support enabled, you must pass `--enable-shadowgrp' to
configure.
Earlier versions just had it enabled by default with no way to change it.
The upshot - if you build shadow-4.0.11.1 using current instructions then
`grpconv' will not work. LFS instructs the reader to optionally run this
program so.. something clearly needs to be done. For now, I'm just passing
`--enable-shadowgrp' to preserve the old behavior.
Here is the blurb from the shadow docs about the feature. The 3rd para would
appear to be outdated:
Shadow Group Files -
This option utilizes an alternate, non-readable file to
contain encrypted group passwords and group administrator
information.
This feature allows one or more users to be defined as
the administrators of a group for the purpose of adding
or deleting members and changing the group password.
Select this option by defining the SHADOWGRP macro. You
must also create an emptry /etc/gshadow file. You must
select the SHADOWPWD option if you select SHADOWGRP.
Thanks for any insights.
Regards
Greg
--
http://www.diy-linux.org/
--
http://linuxfromscratch.org/mailman/listinfo/lfs-dev
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page
Re: LFS Roadmap
Alexander E. Patrakov wrote: > Some of the users for which 8-bit encodings work might still prefer > UTF-8 for compatibility with RedHat (at the cost of incompatibility with > the rest of the world). Also UTF-8 support is a requirement for LSB > certification. Ubuntu 5.04 also uses pt_BR.UTF-8 on a default "Br. Portuguese" installation, although it's broken on the text console (things like "ls --help" show strange characters intead of e.g. accents). OTOH, GNOME works fine with UTF-8 (including gnome-terminal). -- Anderson Lizardo [EMAIL PROTECTED] http://www.linuxfromscratch.org/ signature.asc Description: OpenPGP digital signature -- http://linuxfromscratch.org/mailman/listinfo/lfs-dev FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
Re: Dependency on libiconv in J2SDK-1.4.2 ?
Matthew Burgess wrote: Tushar Teredesai wrote: Perhaps we should have a note in the glibc instructions that libiconv should not be installed since it is incompatible with glibc. CCing lfs-dev for their consideration. Well, I'm still sitting firmly on the fence with this one :) Do we know roughly how many packages might cause one to think that libiconv is required? Here's how I currently see it: I believe AbiWord has it in the README. Gnome used to have it on their pre-requisites page, it may still be there. 1. All affected packages are outside LFS Yes, probably should be in BLFS. It's not a FAQ but there was a thread last month (fontconfig) and again now this month. If a person installs in /usr the iconv.h header is a goner. Probably it could be pulled from he glibc tarball, I haven't looked. -- David Jensen -- http://linuxfromscratch.org/mailman/listinfo/lfs-dev FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
Re: Dependency on libiconv in J2SDK-1.4.2 ?
On 7/28/05, Matthew Burgess <[EMAIL PROTECTED]> wrote: > Tushar Teredesai wrote: > > > Perhaps we should have a note in the glibc instructions that libiconv > > should not be installed since it is incompatible with glibc. CCing > > lfs-dev for their consideration. > > Well, I'm still sitting firmly on the fence with this one :) I will try to nudge you a little bit :) > Do we know > roughly how many packages might cause one to think that libiconv is > required? No idea. I do remember this issue cropping up during GNOME-1 days since the GNOME docs used to mention libiconv as a dependency. Have not seen it recently till this e-mail. Lot of GNU packages (including ones installed in LFS) check for libiconv since it is needed for non-glibc based systems. > Here's how I currently see it: > > Arguments for warning in LFS: > > 1. Glibc is installed in LFS > > Arguments against warning in LFS: > > 1. All affected packages are outside LFS There is no good place to warn in BLFS (there is no section "Packages Not to Install", maybe there should be!). Hence, IMO the best option is the package with which it clashes. > 2. The warning in LFS may have been forgotten about by the time someone > comes to install an affected package. We can always point back to the note in LFS and say "See, now you have borked your glibc installation, go and redo LFS" :-) -- Tushar Teredesai mailto:[EMAIL PROTECTED] http://www.linuxfromscratch.org/~tushar/ -- http://linuxfromscratch.org/mailman/listinfo/lfs-dev FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
Re: [Proposal] Add verbose switch to commands that accept it
Since I just came across one of these again, here is an example, again BLFS and not LFS... this time in ghostscript: chown -v -R root:root /usr/local/share/ghostscript/fonts J.O. -- http://linuxfromscratch.org/mailman/listinfo/lfs-dev FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
Re: Dependency on libiconv in J2SDK-1.4.2 ?
Tushar Teredesai wrote: Perhaps we should have a note in the glibc instructions that libiconv should not be installed since it is incompatible with glibc. CCing lfs-dev for their consideration. Well, I'm still sitting firmly on the fence with this one :) Do we know roughly how many packages might cause one to think that libiconv is required? Here's how I currently see it: Arguments for warning in LFS: 1. Glibc is installed in LFS Arguments against warning in LFS: 1. All affected packages are outside LFS 2. The warning in LFS may have been forgotten about by the time someone comes to install an affected package. Cheers, Matt. -- http://linuxfromscratch.org/mailman/listinfo/lfs-dev FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
Re: [Proposal] Add verbose switch to commands that accept it
Matthew Burgess wrote: Err, *hundreds* of lines? What commands did you add '-v' on to make it output that much. In the vast majority of cases it should just be one line per command, I would imagine. Ahemm... May have been an exaggeration, but nevertheless, there was a lot of "scrolling away useful stuff" involved. It was probably something from the BLFS-book, since that's where I've been installing stuff from, lately. But I cannot remember exactly what package. Now I have aliased my xterm to 'xterm -sl 5000', problem solved. But -v is a great help when there are just a few commands, definitely. J.O. -- http://linuxfromscratch.org/mailman/listinfo/lfs-dev FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
Re: New BLFS Editor
On 7/28/05, Bruce Dubbs <[EMAIL PROTECTED]> 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. Welcome abroad Richard. -- Tushar Teredesai mailto:[EMAIL PROTECTED] http://www.linuxfromscratch.org/~tushar/ -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [Proposal] Add verbose switch to commands that accept it
On 7/28/05, Randy McMurchy <[EMAIL PROTECTED]> wrote: > Matthew Burgess wrote these words on 07/28/05 12:16 CST: > > > Err, *hundreds* of lines? What commands did you add '-v' on to make it > > output that much. In the vast majority of cases it should just be one > > line per command, I would imagine. > > I took the OP to mean the BLFS additions of -v. Over on BLFS, > -v was added to cp -R commands where perhaps as many as hundreds > of files may be logged in instances where documentation is copied > manually. How about leaving the option to the users? At the begining of LFS, there can be a note stating that they could alias the commands if they want verbose output. alias cp "cp -v", ... -- Tushar Teredesai mailto:[EMAIL PROTECTED] http://www.linuxfromscratch.org/~tushar/ -- http://linuxfromscratch.org/mailman/listinfo/lfs-dev FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
Re: New BLFS Editor
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. -- Bruce Sure, welcome aboard Richard! Remember to keep a sense of humor, KDE-3.4.2 is out, Bruce committed 3.4.1 yesterday! :-) -- David Jensen -- http://linuxfromscratch.org/mailman/listinfo/lfs-dev FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
Re: [Proposal] Add verbose switch to commands that accept it
Matthew Burgess wrote these words on 07/28/05 12:16 CST: > Err, *hundreds* of lines? What commands did you add '-v' on to make it > output that much. In the vast majority of cases it should just be one > line per command, I would imagine. I took the OP to mean the BLFS additions of -v. Over on BLFS, -v was added to cp -R commands where perhaps as many as hundreds of files may be logged in instances where documentation is copied manually. -- 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] 12:24:00 up 117 days, 11:57, 2 users, load average: 0.03, 0.43, 0.57 -- http://linuxfromscratch.org/mailman/listinfo/lfs-dev FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
Re: File-4.14
David Jensen wrote: While downloading File-4.14 I saw there is an official patch in. ftp://ftp.gw.com/mirrors/pub/unix/file/ It appears to fix 2 minor nits in the mime types.. Yeah, I saw that too, but wasn't sure it was really worth bothering with. I can't get to the site at the moment, but from memory one of the file types was 'scream', I forget what the other one was. If there's a huge outcry for us to fix this, I'll add the patch, but I'd rather just pick up such a fix when 4.15 comes out. Cheers, Matt. -- http://linuxfromscratch.org/mailman/listinfo/lfs-dev FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
Re: New BLFS Editor
Bruce Dubbs wrote: Please help me in welcoming Richard Downing (aka TheOldFellow) as a new BLFS Editor. Indeed. Welcome Richard! I'm sure you'll prove to be a very valuable asset to the team. Matt. -- http://linuxfromscratch.org/mailman/listinfo/lfs-dev FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
Re: [Proposal] Add verbose switch to commands that accept it
Jens Olav Nygaard wrote: Since everybody seems to be so positive... I found it extremely annoying when I realized this change, as hundreds of lines scrolled by, and all the useful information from previous commands just scrolled into oblivion. Err, *hundreds* of lines? What commands did you add '-v' on to make it output that much. In the vast majority of cases it should just be one line per command, I would imagine. Cheers, Matt. -- http://linuxfromscratch.org/mailman/listinfo/lfs-dev FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
New LiveCD Team Member
Hi All, I'd like to publicly welcome Thomas Pegg who has joined the LFS LiveCD team. He specifically volunteered to help create a x86_64 LiveCD - I think that there are many of you out there that would welcome such a CD. For some time Thomas has been efficiently maintaining the nALFS profiles on the ALFS project, so I'm looking forward to tapping into that for the LiveCD project as well. Welcome aboard, Thomas. -- JH -- http://linuxfromscratch.org/mailman/listinfo/lfs-dev FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
Re: New BLFS Editor
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 -- http://linuxfromscratch.org/mailman/listinfo/lfs-dev FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
New BLFS Editor
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. -- Bruce -- http://linuxfromscratch.org/mailman/listinfo/lfs-dev FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
File-4.14
While downloading File-4.14 I saw there is an official patch in. ftp://ftp.gw.com/mirrors/pub/unix/file/ It appears to fix 2 minor nits in the mime types.. I can re-diff it to LFS standards and commit it to Patches. I can't add it to the BOOK(s) though. fwiw -- David Jensen -- http://linuxfromscratch.org/mailman/listinfo/lfs-dev FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
Re: [Proposal] Add verbose switch to commands that accept it
Matthew Burgess wrote: policy. Does anyone have any strong opinions either way? Since everybody seems to be so positive... I found it extremely annoying when I realized this change, as hundreds of lines scrolled by, and all the useful information from previous commands just scrolled into oblivion. But when just a few files/links/directories are made, I like it. (So I wouldn't actually dear to suggest adding a '|tail -10' to all commands, although I might do it myself to a few... J.O. -- http://linuxfromscratch.org/mailman/listinfo/lfs-dev FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
