Re: Authentication & PAM
> Anybody knows how to change authentication _ONLY_ to PAM? PAM support in STABLE is very incomplete. M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: Roasting Newbies
Thought for the day: From little Newbies do mighty Gurus grow. Some positive stuff on the list for a change; about time. What I cannot understand is why anyone is suprised that stable recieves _inappropriate_ mail. If you track stable you are _REQUIRED_ to subscribe to _THIS_ mailing list. (Yes I am shouting, sorry). My understanding of human nature says this is where any questions are going to get posted. Perhaps something (less dry) in the subscription acknowledgement might help. Justin Wolf is right on track. Ask yourself, why is Linux getting such a lot of press? It's reached critical mass in terms of number of users, thats why. FreeBSD can be the best O/S ever, but if people (aka. Newbies) don't use it, it may not survive. If you/we are going to provide basic help for newbies (myself included), it needs to be friendlier than man. HTML or even info would be better (IMHO). It might also be worth aliasing "help". Before you all run away screaming, I'm suggesting that a level of indirection is useful. This week help might mean man newbie. Next week it could mean info newbie, or whatever. Keeping the user inferface the same is _a_good_thing_. A Friday night Saturday morning ian j hart. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: Roasting Newbies
I think all of these are very good ideas. Set out plenty of pointers to self-help and it makes dealing with people that want to learn much easier. I love to say 'man it' or goto freebsd.org and follow the links to 'newbie' or something similar. It also makes sense to keep a few of the lists closed, then the newbie flames are just averted right away. While many people in the FreeBSD community may have an anti-newbie attitude I find it slightly annoying. It was like this when linux was very young in '93, many folks flamed newbies that asked dumb questions, while they rarely replied to any questions that were actually technical at all nor consistently pointed them to self-help, that has changed and I think linux is far better to start people off with, but we should still be reasonable about treating folks curiosities with some respect. My $.02, -chris To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: cannot compile ipfw... Did I miss something?
Found my own problem. My tree was slightly corrupt. -Dave To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: [Patches avail?] Re: MMAP() in STABLE/CURRENT ...
:>ECC doesn't protect against certain types of motherboard address line :> errors (since although the ECC is correct, the selected address is wrong, so :> thus the data is wrong). There's parity protection on parts of the CPU :> address bus, but I don't believe there is any protection between the memory :> controller and the DIMMs for this type of problem. A handful of metal :> filings is also known to cause problems when it is dispersed properly. :-) : :Your suppose to remove the motherboard before drilling holes in your :chassis!!! :-). And be careful when you strip them there screws out, :that little bit of metal filings is enough to through one for some : :Rod Grimes - KD7CAX - (RWG25)[EMAIL PROTECTED] Forget the drilling! Blood conducts electricity... simply *installing* a motherboard in those fraggin sharp-edged sheet metal chassis is enough! -Matt Matthew Dillon <[EMAIL PROTECTED]> To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: [Patches avail?] Re: MMAP() in STABLE/CURRENT ...
> >On Thu, Oct 07, 1999 at 10:09:23AM -0700, Matthew Dillon wrote: > > > >> Intel's ECC implementation is not perfect (1), but it's good enough to > >> catch these sorts of problems. > > > >Just as an interesting side note, we had a motherboard which > >supported ECC ram and had ECC ram in it and which was crashing. > >Eventually we discovered that every 8th byte in page aligned 4KB > >chunks was becomming corrupted. > > > >We replaced the ram and saw no improvement, and then got a replacement > >motherboard. As far as I could see the only significant difference > >between the new and old motherboard was the addition of a heat sink > >to the memory controler chip. The machine is now perfectly happy. > > > >So it seems that ECC isn't enough if your memory controler is too > >hot! > >ECC doesn't protect against certain types of motherboard address line > errors (since although the ECC is correct, the selected address is wrong, so > thus the data is wrong). There's parity protection on parts of the CPU > address bus, but I don't believe there is any protection between the memory > controller and the DIMMs for this type of problem. A handful of metal > filings is also known to cause problems when it is dispersed properly. :-) Your suppose to remove the motherboard before drilling holes in your chassis!!! :-). And be careful when you strip them there screws out, that little bit of metal filings is enough to through one for some real loops. A good blast of 60psi dry air does wonders for ``fixing'' some of these really strange problems :-) Now if I could just find something that would get sheet rock sanding dust out of tape drive mechanisms, a dunk in the freon tank often works, but that also cleans out all the lubrication :-). -- Rod Grimes - KD7CAX - (RWG25)[EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: disk partitions
Tom Embt wrote: > > At 06:50 PM 10/8/99 +0900, you wrote: > >Tom Embt wrote: > >> > >> If ever there was such a requirement, it is no longer applicable. Some > >> (all?) off the various incantations of Windows need to boot < 1024 cyl > >> boundary (usually 8 GB), but they are happy in any slice. IIRC, they do > >> have problems booting to anything other than primary master for IDE. > > > >There *is* a limitation. Windows will only boot from a primary > >partition. > > I never said otherwise[1], but you are correct. ..something that I've > stopped thinking of as a limitation bur rather a M$ fact of life :( > > I've noticed the BSL documentation claims to be able to boot from extended > partitions if the OS supports it. Does anyone know if this means Windows > can indeed be tricked into doing this? If not, I must wonder what OS's > _do_ support such a thing. I don't have the $$ to get a full version of it > to play with. Linux, os/2, and windows NT will boot off extended partitions, for what it's worth. Eric Hedstrom [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: disk partitions
At 06:50 PM 10/8/99 +0900, you wrote:
>Tom Embt wrote:
>>
>> If ever there was such a requirement, it is no longer applicable. Some
>> (all?) off the various incantations of Windows need to boot < 1024 cyl
>> boundary (usually 8 GB), but they are happy in any slice. IIRC, they do
>> have problems booting to anything other than primary master for IDE.
>
>There *is* a limitation. Windows will only boot from a primary
>partition.
I never said otherwise[1], but you are correct. ..something that I've
stopped thinking of as a limitation bur rather a M$ fact of life :(
I've noticed the BSL documentation claims to be able to boot from extended
partitions if the OS supports it. Does anyone know if this means Windows
can indeed be tricked into doing this? If not, I must wonder what OS's
_do_ support such a thing. I don't have the $$ to get a full version of it
to play with.
note 1: Actually I guess it depends on one's exact interpretation of my
words. A more correct statement might have been: "The windows boot
partition can be any of the four slices, and that slice may be in any
location on the disk excepting BIOS limitations (8 GB limit)." My thinking
is that booting from an extended partition (which Windows can't do anyway)
does not constitute booting from a slice, but instead from a small subset
("logical drive") of a slice, and therefore that slice cannot be defined as
_the_ Windows boot slice. However you look at it, it's just nitpicking as
it seems clear that both you and I know what we're talking about.
Oh bother, I've written too much. And it seems this isn't really
applicable to -stable anyway. Darn.
Tom Embt
[EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-stable" in the body of the message
Re: Seeing log messages associated with CVSup updates
[ On Friday, October 8, Daniel C. Sobral wrote: ]
>
> This script is really cool, but it is still a little bit lacking. If
> we could have a link to the diff between the version you have and
> the latest version, that would be much better. It seems feasible,
> isn't it?
>
Yes, most of the above seems feasible. There would be a little guesswork and
heuristics on the "linking to the diff" part, but the rest is pretty much done
by the following. The idea for this script, of course, was gleaned from the
original awk script posted by John Polstra yesterday.
Use at will, modify to suit your needs :)
#!/usr/bin/perl
#
# Copyright (c) 1999 John C. Reynolds
# All rights reserved.
#
# Redistribution and use in source and binary forms, with or without
# modification, are permitted provided that the following conditions
# are met:
# 1. Redistributions of source code must retain the above copyright
# notice, this list of conditions, and the following disclaimer,
# without modification, immediately at the beginning of the file.
# 2. The name of the author may not be used to endorse or promote products
# derived from this software without specific prior written permission.
#
# THIS SOFTWARE IS PROVIDED BY THE AUTHOR AND CONTRIBUTORS ``AS IS'' AND
# ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
# IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
# ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE FOR
# ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
# DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
# OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
# HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
# LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
# OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
# SUCH DAMAGE.
#
#
# Quickie script to reformat CVSup (16) log files into HTML. Links
# references to files, deltas, and committers to the CVS web CGI program
# and the FreeBSD web site.
#
# The idea for this program originated from an 'awk' script created by
# <[EMAIL PROTECTED]>, with other ideas and patches submitted
# by Marcel Moolenaar <[EMAIL PROTECTED]>.
#
require 'ctime.pl';
$url = 'http://www.freebsd.org/cgi/cvsweb.cgi';
if ($ARGV[0] eq '') {
print "Usage: $0 cvsup-log-file > cvsup-log-file.html\n";
exit 1;
}
# Grab date from file if not coming in from stdin
#
$date = '';
unless ($ARGV[0] eq '-') {
($dev, $ino, $mode, $nlink, $uid, $gid,
$rdev, $size, $atime, $mtime, @junk) = stat ($ARGV[0]);
$date = ctime ($mtime);
chomp ($date);
$date = '(' . $date . ')';
}
if (! open (IN, $ARGV[0])) {
print (STDERR "Could not open '$ARGV[0]' for reading - $!\n");
exit 2;
}
while () {
if (/Parsing\s+supfile\s+"(.*?)"/) {
$file = $1;
s#$file#$file#;
}
if (/(Edit|Checkout)\s+(\S+)/) {
$file = $2;
($realfile = $file) =~ s/,v$//;
s#$file#$file#;
}
if (/Add\s+delta\s+(\S+).*?(\S+)\s*$/) {
$rev = $1;
$committer = $2;
s#$rev#$rev#;
s#$committer#mailto:$committer\@freebsd.org">$committer#;
}
if (/Updating\s+collection\s+(\S+)/) {
$collection = $1;
}
push (@lines, $_);
}
close (IN);
print "\n\n";
print "CVSup log for '$collection' ${date}\n\n";
print "\n\n\n";
foreach (@lines) {
print;
}
print "\n\n\n\n";
--
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
| John Reynolds CEG, CCE, Next Generation Flows, HLA |
| Intel Corporation MS: CH6-210 Phone: 480-554-9092 pgr: 868-6512 |
| [EMAIL PROTECTED] http://www-aec.ch.intel.com/~jreynold/ |
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-stable" in the body of the message
Re: Roasting Newbies
On Fri, Oct 08, 1999 at 05:37:29AM -0500, Mike Pritchard wrote: > On Thu, Oct 07, 1999 at 05:20:45PM -0400, Michael Lucas wrote: > > IMHO, tensions on the FreeBSD lists are running at their greatest > > level since... oh, I'd say mid-96, when I first subscribed to > > -questions. > > > > If a "FreeBSD newbies info page" will help, then I'm all for it. I > > don't see what sort of "ramifications" it could have, other than to > > (perhaps) reduce some of the stress all around. > > If we add a "newusers" web document, then how about 1 or 2 "newusers" > on-line manual pages as well. I'm thinking something along the lines > of newusers.7 (misc documentation), and newusers.8 (sys admin docs). > We can setup the default install /etc/motd to mention these documents > in the hope that they will be read. And maybe mention them elsewhere > in some of the install documentation, and other places. > > If someone gives me the text, I'll be sure that it gets converted > to our current man page style somehow (either by me, or someone > I con...err, convince to do it :-). I'm sure given quality text, > we can find someone to convert it to docbook format, and I can > probably do that, too, if no one else steps up to do that. see what sue blake <[EMAIL PROTECTED]> has produced and posts regularly, every saterday from memory in, for and the education of how beginners, and where they can find help. it is posted to freebsd-newbies, which sue does a good job moderating. regards jonathan -- === Jonathan Michaels PO Box 144, Rosebery, NSW 1445 Australia ===<[EMAIL PROTECTED]> To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: Authentication & PAM
On Fri, Oct 08, 1999 at 04:21:56PM +0300, Ruslan Ermilov wrote: > Where did you get this pam_ldap? It is not in neither -current nor -stable. > It is possible, that it is buggy. Please try replacing pam_ldap by pam_skey > and check whether it will still let you to log in. I compiled it myself. But - aaah - with pam_skey.so I can't log in. Thanks! :) bye -- Sebastian Soenksen ; http://www.planlos.hanse.de/ ; pgpkey available To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: [Patches avail?] Re: MMAP() in STABLE/CURRENT ...
>On Thu, Oct 07, 1999 at 10:09:23AM -0700, Matthew Dillon wrote: > >> Intel's ECC implementation is not perfect (1), but it's good enough to >> catch these sorts of problems. > >Just as an interesting side note, we had a motherboard which >supported ECC ram and had ECC ram in it and which was crashing. >Eventually we discovered that every 8th byte in page aligned 4KB >chunks was becomming corrupted. > >We replaced the ram and saw no improvement, and then got a replacement >motherboard. As far as I could see the only significant difference >between the new and old motherboard was the addition of a heat sink >to the memory controler chip. The machine is now perfectly happy. > >So it seems that ECC isn't enough if your memory controler is too >hot! ECC doesn't protect against certain types of motherboard address line errors (since although the ECC is correct, the selected address is wrong, so thus the data is wrong). There's parity protection on parts of the CPU address bus, but I don't believe there is any protection between the memory controller and the DIMMs for this type of problem. A handful of metal filings is also known to cause problems when it is dispersed properly. :-) -DG David Greenman Co-founder/Principal Architect, The FreeBSD Project - http://www.freebsd.org Creator of high-performance Internet servers - http://www.terasolutions.com Pave the road of life with opportunities. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: [Patches avail?] Re: MMAP() in STABLE/CURRENT ...
On Thu, Oct 07, 1999 at 10:09:23AM -0700, Matthew Dillon wrote: > Intel's ECC implementation is not perfect (1), but it's good enough to > catch these sorts of problems. Just as an interesting side note, we had a motherboard which supported ECC ram and had ECC ram in it and which was crashing. Eventually we discovered that every 8th byte in page aligned 4KB chunks was becomming corrupted. We replaced the ram and saw no improvement, and then got a replacement motherboard. As far as I could see the only significant difference between the new and old motherboard was the addition of a heat sink to the memory controler chip. The machine is now perfectly happy. So it seems that ECC isn't enough if your memory controler is too hot! David. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
