cel
rather than the current Ok and Cancel.
Hope this was of some help, long live BSD!
(Next time I promise to learn how to use the automated bug reporting
feature).
David Holland
[EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
On 6 Apr 2000, at 12:53, Yoshinobu Inoue wrote:
Is this problem just with current? I am having the same type of
problem with the sshd daemon on 4.0-STABLE
David DeTinne
> > > On 6 Apr 2000, at 12:53, Yoshinobu Inoue wrote:
> > > I applied it and am running with it now, but I
Hello,
My name is David DeTinne and I have been suscribing to FreeBSD
Stable for some time now, before 2.2.2 was released.
Here is my view regarding your posting:
3.1 is probably the most unstable "stable version" ever to be sent out
by Walnut Creek. I have a machine that has 2
On your next ``make world'', you will need to change any "user.group"
specifications in /etc/newsyslog.conf to "user:group".
--
-- David([EMAIL PROTECTED] -or- [EMAIL PROTECTED])
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
nning -CURRENT... well they are
supose to take heed of "HEADS UP" messages.
--
-- David([EMAIL PROTECTED] -or- [EMAIL PROTECTED])
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
types of services.
Interesting idea... I like it. As you said, it removes us from forcing
some policy and just provides the mechanism.
--
-- David([EMAIL PROTECTED] -or- [EMAIL PROTECTED])
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
On Tue, 29 Jun 1999, Alex Zepeda wrote:
> Well, pushing <4s on the power button will turn the computer off (in fact
> it's more of a "hard" power off IIRC).
Depends on the BIOS. It is often settable.
David, who finds most ATX stuff annoying because it hasn't got
? If you have a dump, can you
provide a stack trace? Anything else useful.
David
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
On Sun, 4 Jul 1999, Amancio Hasty wrote:
>
> Curious why are you cvsupping every couple of minutes ?
I think you have a language problem here. I think he meant it normally
takes a couple of minutes, not that he cvsups every couple of minutes.
David
To Unsubscribe: send mail to
did this on 3.2 you must have).
--
-- David([EMAIL PROTECTED] -or- [EMAIL PROTECTED])
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
You'll want to look primarily in the swap_pager code since it messes with
that (at least it used to - I don't recall what Matt's new code does with it).
There should be various calls to vm_object_pip_* that manipulate the
paging_in_progress number.
-DG
David Greenman
Co-fo
gt;
>Anyone have any objections?
Yes, I do - at least with the 512MB figure. That would be half of the 1GB
KVA space and large systems really need that space for things like network
buffers and other map regions.
-DG
David Greenman
Co-founder/Principal Architect, The Free
>: Yes, I do - at least with the 512MB figure. That would be half of the 1GB
>:KVA space and large systems really need that space for things like network
>:buffers and other map regions.
>:
>:-DG
>:
>:David Greenman
>:Co-founder/Principal Architect, The FreeBSD Project
uot;-v" to your CLFAGS in /etc/make.conf show?
--
-- David([EMAIL PROTECTED] -or- [EMAIL PROTECTED])
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
e
then Ports track -STABLE and until recently, Satoshi was only building
packages on -STABLE machines.
--
-- David([EMAIL PROTECTED] -or- [EMAIL PROTECTED])
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
> > Why shouldn't we? Noone uses machines without FPUs anymore.
> What non-ancient
> > CPU doesn't have an FPU? And we're talking about the i386 family here...
> >
>
> Embedded systems, anyone?
True, but how late a version do you really want to run on them? I've left
even my P60's at Fre
> You're correct in that better awareness is almost definitely the key.
> Would you consider posting the -stable and -current port build results
You can find the realtime results from http://bento.freebsd.org/
--
-- David([EMAIL PROTECTED] -or- [EMAIL PROTECTED])
To Unsubs
find any.
David.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
> Does anybody have a plans to fix plip code which is broken a quite
> awhile (several months or so)?
Since I used it just last week on two -CURRENT boxes, I'd say there is
some other problem you are experecing.
--
-- David([EMAIL PROTECTED] -or- [EMAIL PROTECTED])
To
he 450MHz PII ran about 200 times slower than usual!
David.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
[on IDE bus lockups]
I found that my IDE cdrom regularly caused lockups of FreeBSD in the
5-10 second variety. I would suspect that any misbehaving IDE device
can do this.
Dave.
--
|David Gilbert, Velocet
ressed crashdumps?
(Other than no one haveing ever written the the code, of course.) In
other words, if I wrote this would it get committed?
David Scheidt
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
p, even if I have to analyze
it somewhere else.
David Scheidt
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
ion in -CURRENT one
would get this error. But a ``make world'' should have given you a
consistant libc to linke with... Are you sure your /usr/src is clean of
*.o files? Are you using -DNOCLEAN or any other non-standard options in
your ``make world''?
--
-- David([EMAIL
> Noone compiles without -O, so(/and) it's not supported. My take is
> that EGCS says "Hey, I am in optimization level foobar! I can optimize
> for unused code. Hmm... that's unused, so...". Either that or its
> debugging support is really uNFed up.
Actually, more likely at high enough o
s going on with your system, but it's definately unusual
to hit this limit under normal circumstances.
-DG
David Greenman
Co-founder/Principal Architect, The FreeBSD Project - http://www.freebsd.org
Creator of high-performance Internet servers - http://www.terasolutions.com
>On Fri, 23 Ju
not a full make world before commiting. I am *VERY* surprised
it has taken nearly 24hrs for someone to yell Ouch!
This morning and now I have been unable to verify this wasn't a problem
due to local hacks. I am glad to now have independant verification.
--
-- David([EMAIL PROT
> Any prognosis on a fix?
I'll revert when I go to bed if I am not getting anywhere.
--
-- David([EMAIL PROTECTED] -or- [EMAIL PROTECTED])
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
t Netscape is).
Realize when building with -DWANT_AOUT, you are not creating the same
libraries that were on 2.2.x, but rather libs with full 4.0-CURRENT
features and content but in the a.out format.
--
-- David([EMAIL PROTECTED] -or- [EMAIL PROTECTED])
To Unsubscribe: send mail to [EMAIL PR
on vacation,
> it's the "last week" and "six weeks" part I'm not 100% sure.
Six weeks, and no computer more sophisticated than the SCUBA one, are what
I remembered. Someone remind me what a vacation is again?
David
To Unsubscribe: send mail to [EMAIL PROTECT
dlock situation (at least that is my
>take).
I good bit of detective work...excellent job.
-DG
David Greenman
Co-founder/Principal Architect, The FreeBSD Project - http://www.freebsd.org
Creator of high-performance Internet servers - http://www.terasolutions.com
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
.1.2 (the version in our base
src tree). To spend time finding bugs in EGCS-1.1.2 would be a serious
waste of time. You can install the latest ``egcs-devel'' and see if the
bug remains. If so, then a bug report to the GCC people would be
appropriate (but find a small example t
[moved to -chat]
On Tue, 3 Aug 1999, Nik Clayton wrote:
>
> Hmm. "I submitted a PR to FreeBSD, and all I got was this lousy t-shirt."
Wouldn't we rather have "I fixed a PR in FreeBSD..."?
David Scheidt
To Unsubscribe: send mail to [EMAIL PROTECTED]
with &
kernel is
recompiled by a person with a different length username. vers.c
is produced with a string which is a different length which screws
up the offsets.
Maybe newvers.sh should pad usernames to the legal max? Maybe we should
warn people to touch vers.c after editing the Makefile?
takes to build the kernel, and it
> > solves a whole lot of potential problems.
>
> Sounds OK to me. Was this kernel.debug thing merged into -stable?
Nope. I've requested grog to MFC, another person requesting couldn't
hurt. :-)
--
-- David([EMAIL PROTECTED] -or-
problems.
It does cause problems when you keep the kernels for 8 different machines
in one /usr/src. I've never had any problems with -g generating different
code as long as the stuff in vers.c doesn't change length. Being able to
reproduce a kernel with debugging symbols seems like a reas
automatic dependencies loading to work. It isn't that hard. Just use the
"-r" switch to ``mkisofs'' when you burn the image.
> BTW, the dependencies among packages are quite difficult to be guessed
> off-line :-)
The INDEX files tells the dependencies.
--
-- David
> I don´t know, which daemon writes to /var/run/utmp.
>
> Maybe I should notice, that I´m logged in via ssh.
Was this version of ssh built on a 4.0 system, or 2.x? Usernames went
from 8 chars to 16 chars. I was experiencing simular problems when I
upgraded from 2.2.x to 3.0.
--
he same
kernel on all of them), you have a little $$ that you could buy a cheap
4gig drive just for kernel building.
--
-- David([EMAIL PROTECTED] -or- [EMAIL PROTECTED])
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
ave tried. (FreeBSD, Linux, ScumOS, HP/UX, spit NT) I
would buy an external one, as they generate quite a lot of heat.
>
> Is there any support for IDE CD writers or are they not worth bothering with
> on FreeBSD.
There is support, but I don't think they are worth bothering
ng would be helpful.
--
-- David([EMAIL PROTECTED] -or- [EMAIL PROTECTED])
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
> "Linux compatibility"
> "Linux ABI support"
> "Linux binary compatibility"
The suggested "linux mode", has a nice non-technical simple ring to it.
If we called it this, the non-educated might not come away with the wrong
idea. Management(tm) may not understand "ABI" and the exact use of
"binar
others in digital audio extraction (if
that matters to you). Cdrecord and Plextor just work. :-)
Also, Jordan prescribes their CDROM drives.
--
-- David([EMAIL PROTECTED] -or- [EMAIL PROTECTED])
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current"
> 1. Add a "if [ ! -d $bak ] ; then exit fi" to the top
> of the files, or
> 2. Add a "mkdir -p $bak" to the top.
>
> Do others consider this an error, and if so which is the preferred fix?
Both. (2) followed by (1), possible logging
lowed to have application-specific files anywhere except under PREFIX.
--
-- David([EMAIL PROTECTED] -or- [EMAIL PROTECTED])
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
> [ Amancio's reply moved to the *bottom* where replies belong.. ]
He (and some others on this list) should also learn how to NOT QUOTE THE
ENTIRE MESSAGE. Only the relevant parts should be quoted.
--
-- David([EMAIL PROTECTED] -or- [EMAIL PROTECTED])
To Unsubscribe: send
ibreadline.so
ln -s libreadline.so.3 libreadline.so
--
-- David([EMAIL PROTECTED] -or- [EMAIL PROTECTED])
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
ng 4.17 is better than 4.18 for debugging C++? Or are you
saying you didn't know FreeBSD comes with gdb:
$ which gdb
gdb is hashed (/usr/bin/gdb)
$ gdb --version
GNU gdb 4.18
Copyright 1998 Free Software Foundation, Inc.
...
--
-- David([EMAIL PROTECTED] -o
> "Another possibility, if you have the RAM, is to use the team(1)
> program (it's in the ports) to buffer the data as it goes to the burner.
Any reason not to use ``cdrecord -fs=64m'' (or some simular size)
--
-- David([EMAIL PROTECTED] -or- [EMAIL PROTECTE
On Fri, Aug 20, 1999 at 01:04:47PM +0200, Werner Griessl wrote:
Werner, like you we all got 246 line email message. You did not have to
quote the *ENTIRE* thing back to us just to add 3 lines.
If you don't have the time to trim, we don't have the time to read your
reply.
--
> If you have the physical memory sure however if you don't then
> you will start swapping and most likely your cd recording will
> fail.
>
> Hence my recommendation for a small size buffer.
Then there is no advantage in using `team' vs. ``cdrecord -fs=XX'
being committed, that offer is still good.
What do you think Sheldon?
--
-- David([EMAIL PROTECTED] -or- [EMAIL PROTECTED])
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
to? I mean, I never had to go over the default cdrecord uses.
Since the author was already suggesting the use of team(1) he obvisiously
wants a larger buffer. I was mearly asking if there was something about
team(1) better than ``cdrecord -fs=XX''.
--
-- David([EMAIL PROTECTE
certain variables
only when INVARIANTS is defined. The variables seem also to be set
and checked in vm_zone.c.
So I suppose if you use an inline function to initialise something
without INVARIENTS in a module, and then it is checked by the kernel
which did have INVARIENTS defined things go boom...
Of course,
> if it is option 1, I'm keen to know what's wrong with the current driver!
I have survived a number of power loss crashes, with no problems. I tend to
suspect the SCSI driver did something bad.
David Scheidt
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
. Ideas where to look next?
--
-- David([EMAIL PROTECTED] -or- [EMAIL PROTECTED])
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
probably have a new
/usr/bin/cpp that does everything you want it to.
> This behavior breaks the XFree86 3.9.17 build because the procedure
> to build imake depends on /usr/libexec/cpp defining __FreeBSD__
So use ``cc -E'' instead. Simple.
--
-- David([EMAIL PROTECTED])
tion.o ; make' it compiled another source file
> that included PortMgr.h / LevelStat.h just fine, but bombed out elsewhere!
I can't even fathom what you expected to accomplish by this.
Are you a programmer?
--
-- David([EMAIL PROTECTED])
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
the issue
should be raised with Cygnus.
> So there appears to be two solutions to get around this problem:
..snip..
3. Raise this issue with Cygnus.
--
-- David([EMAIL PROTECTED])
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
lot to the object size.
As will whether the language is C or C++.
--
-- David([EMAIL PROTECTED])
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
ouldn't mind to see the output from adding "-v" to CFLAGS in
/etc/make.conf or somewhere closer to the problem.
--
-- David([EMAIL PROTECTED])
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
erested in fixing the
problem and releasing a 3.5-R?
Just like FreeBSD, EGCS has two code branches.
--
-- David([EMAIL PROTECTED])
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
been a better choice as you don't have to remember
to rm the fake .o later.
--
-- David([EMAIL PROTECTED])
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
nt.
The problem most likely needs to be reported for GCC 2.95, *NOT* FreeBSD.
> Okay, lets hope that gcc 2.9.53 comes out before the release of FreeBSD 4.0.
Not unless someone like you gets involved and files a bug report with
Cygnus.
--
-- David([EMAIL PROTECTED])
To Unsubscri
Looks like the leasing stuff in NFS has a little buglet...
(This is with 4.0-CURRENT cvsup'd a few days before Christmas)
Fatal trap 12: page fault while in kernel mode
fault virtual address = 0x12ffa8d4
fault code = supervisor read, page not present
instruction pointer = 0x8
a 2940-LVD controller.
Dave.
--
|David Gilbert, Velocet Communications. | Two things can only be |
|Mail: [EMAIL PROTECTED] | equal if and only if they |
|http://www.velocet.net/~dgilbert
>>>>> "Bill" == Bill Fumerola <[EMAIL PROTECTED]> writes:
Bill> On Thu, 30 Dec 1999, David Gilbert wrote:
>> Related to my last post, the system came up and started to fsck.
>> It appears, with current, that the system will refuse to r/w m
> That sucks severely - NONE of the common units have the PPS output?!
>
> Barf. Oh well.
Many of them do, but it's still not meant for precision timekeeping and the
exact relationship between its PPS pulse edges and UTC's second boundaries
may not be precisely specified. It's not a goo
lock 200 is better than the specifications
indicate. If it really did alternate between 1us early pulses and 1us late
pulses, stability would be measurably impacted. NTP is very good at
smoothing things out anyway, especially since it only probes the clock every
64 seconds or so.
my inbox.
You asked Poul-Henning about *good* timekeeping HW. He told you. $600
isn't that much for computer server related hardware. Warner seconded
the recommendation.
You pay less, you don't get the best. Its up to you to weigh your needs
vs. what you are willing to pay.
And
ct you'll
> have no contributions from me to your little treehouse project in any
> way, shape or form.
Do you promise?? We'll really have *NO* contributions from you?
Including contributing your emails to this list?? Pretty please!!!
Oh please say this is true.
--
-- David([EMAIL
ely
FreeBSD related.
I'm sure the various Linux lists and development groups would greet you
with open arms and would be so very glad to benefit from your
"contributions".
--
-- David([EMAIL PROTECTED])
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
have no basis for making
the accusations that you have against him. I think you owe him an apology.
-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
jump to conclusions without a
lot more to go on than some angry accusations. I would also like to say that
Poul-Henning's behavior in this thread was exceptional and that Karl had no
reason to react the way he did. I think Karl owes a lot of people some
apologies. His behavior was clearly
covering up. Its ashame to
>see leaders do this.
How can you tell that? There is no evidence to support that. *I'm*
certainly not covering anything up and I've seen no reason to believe that
anyone else is, either.
-DG
David Greenman
Co-founder/Principal Architect, The
ete bin trees.
Dave.
--
====
|David Gilbert, Velocet Communications. | Two things can only be |
|Mail: [EMAIL PROTECTED] | equal if and only if they |
|http://www.velocet.net/~dgilbert
in the FreeBSD
distribution, or where. Try looking in /usr/share.
David
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
On Tue, Jan 04, 2000 at 10:28:28PM +0100, Dave J. Boers wrote:
> It's funny how I tend to find things out only just _after_ I asked someone
If you still need the shared libf2c.so.2 for older binaries, install the
latest compat3x distribution.
--
-- David([EMAIL PROTECTED])
To Uns
e COMPAT_LINUX entirely.
I use COMPAT_LINUX because I make kernels more frequently then I make world
or modules. I get fewer panics that way.
David Scheidt
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
DEFAULT_CPP "/usr/bin/cpp"
#endif
#if defined(__sgi) && defined(__ANSI_CPP__)
#define USE_CC_E
David
--
David Dawes Email: [EMAIL PROTECTED]
Co-founder/President, The XFree86 Project, Inc Phone: +1 570 775 9502
http://www.xfree86.org/
On Wed, Jan 05, 2000 at 08:47:07PM -0800, David Dawes wrote:
>I've just been doing a build test of the pre-3.3.6 version of
>XFree86 on a recent FreeBSD 4.0-current, and I've noticed that
>/usr/libexec/cpp doesn't predefine the symbol __FreeBSD__. imake
>uses /usr/libe
On Wed, Jan 05, 2000 at 08:47:07PM -0800, David Dawes wrote:
> I've just been doing a build test of the pre-3.3.6 version of
> XFree86 on a recent FreeBSD 4.0-current, and I've noticed that
> /usr/libexec/cpp doesn't predefine the symbol __FreeBSD__.
Correct. The change
-loaded machine, there are good reasons for it...
Dave.
--
====
|David Gilbert, Velocet Communications. | Two things can only be |
|Mail: [EMAIL PROTECTED] | equal if and only if they |
|http://
works via the watchdog timer.
`xe' is also broken in 4.0-C, awaiting new functions for getting CIS
information.
--
-- David([EMAIL PROTECTED])
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
ply a fact of live in a volunteer project
such as FreeBSD the scheduling that many of us are used to does not work.
Holding up 4.0-R in face if this, just isn't useful.
--
-- David([EMAIL PROTECTED])
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
given -- the
*real* question is how much time the developers will give.
--
-- David([EMAIL PROTECTED])
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
y.
And when will IPv6 fully be in 4-CURRENT?
Besides offering two cents what else can you offer to make this happen?
Time? More money?
People here aren't backing their opinions by tell us *how* their to make
their opinions happen.
--
-- David([EMAIL PROTECTED])
To Unsubscribe: se
On Thu, Jan 06, 2000 at 07:04:16PM -0500, Christian Kuhtz wrote:
> <[EMAIL PROTECTED]> -wk, <[EMAIL PROTECTED]> -hm
^^^
Damnit! I've asked for some features in GCC, GNU grep, and GNU diff. I
want them *NOW* in time for 4.0-RELEASE. So where the fsck are t
i
>
>p.s. pardon the lack of capital letters but my paws can't quite reach
> the shift key and the alphabet keys at the same time
If that is true, then how were you able to push the paren keys?
-DG
David Greenman
Co-founder/Principal Architect, The FreeBSD Project - htt
developers can find the time to put into it
right now. If not, then this whole discussion is a waste of bandwidth and
everyone should just stop gritching over it.
-DG
David Greenman
Co-founder/Principal Architect, The FreeBSD Project - http://www.freebsd.org
Creator of high-performance Internet ser
I tried lint again since David O'Brien committed the new /usr/bin/cpp,
but it turns out that lint is hardwried to use /usr/libexec/cpp.
I changed it to use /usr/bin/cpp, and it works, but gives some
error messages.
Is this still on the list of things to fix, or should I get more details
and
chown-like functionality to mknod(8) and restored
chown & chgrp back to their previous locations. MAKEDEV has been
updated to use the new functionality of mknod(8).
However, do to this moving around of chown & chgrp's install location,
you may easily have stale versions in /sbin and /bin.
ally say.
--
-- David([EMAIL PROTECTED])
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
On Fri, Jan 07, 2000 at 08:32:19AM +, Brian Somers wrote:
> Anyone know what's changed with `calendar' ? I suspect it's the
> recent cpp changes.
Please test this patch.
Index: io.c
===
RCS file: /home/ncvs/src/usr.bin/calend
the linux version of pam, then pam_wheel is broken.
It uses the groups of the person listed in utmp as owning the tty,
instead of the groups of the person running su.
This breaks stuff like su'ing to a sysadmin and then su'ing to root
from a normal users terminal, and means you can't
On Sat, Jan 08, 2000 at 03:48:33PM -0800, Kurt D. Zeilenga wrote:
> Did you try the "use_uid" option?
Looks like you're dead right! I can't test it 'till tomorrow, but I'm
sure it works.
Oh, if only everything came with man pages, then I could RTFM.
D
acflag = AFORK;
> (void) splhigh();
>+ p2->p_flag |= P_INMEM;
> p2->p_stat = SRUN;
> setrunqueue(p2);
> (void) spl0();
It shouldn't be necessary to set the flag inside of splhigh. If you move
it up a line I think you'll have a winn
On Fri, Jan 07, 2000 at 09:28:47AM -0800, David O'Brien wrote:
> On Fri, Jan 07, 2000 at 01:29:27PM +0200, Sheldon Hearn wrote:
> > I think lint(1) might work with this given the following small patch.
>
> I agree that lint might should continue to use /usr/libexec/cpp rat
s (df -k and du -k come to mind
Don't forget our new ``df -h''.
I'm working with mharo to get "-h" added to `du'. I guess we should add
it to `ls' too.
--
-- David([EMAIL PROTECTED])
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
ependencies don't sit there waiting for one
another? (I think we've had to change this several times in the
FreeBSD rc scripts, I guess the reason it might be the other way
around is incase /usr is nfs mounted?)
David.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsub
1 - 100 of 4480 matches
Mail list logo
