On Tue, 21 Sep 1999, David Krinsky wrote:
On Mon, Sep 20, 1999 at 12:05:38AM +, Gary Hampton ([EMAIL PROTECTED])
wrote:
On Mon, 20 Sep 1999, Adam Strohl wrote:
Remake your acd device, I think you may need a patch to do it. I had the
same problem, until I rm-ed the device and
I've just been bitten by the following, so I figured I might as
well warn others. From a quick glance it doesn't seem to have been
mentioned, or not clearly enough, in this list.
Too late drat ! But xdm saves the day !
[.]
--
Pierre Beyssac[EMAIL PROTECTED]
--
On Mon, Sep 20, 1999 at 09:55:19PM +, Adam Strohl wrote:
Well, is there a work around, telneting out does the same thing, using
the -l user option used to allow me to log into remote hosts, not
The workaround I found was to boot single then "su - mylogin".
--
Pierre Beyssac
On Tue, Sep 21, 1999 at 08:29:26AM +0200, Mark Murray wrote:
- /usr/bin/login and friends are now linked against libscrypt
instead of libcrypt.
This is a link bug. The Makefile says "-lcrypt". JDP?
Then there's the problem that libcrypto.so.3 won't magically be a
link to a
The "md" driver I committed today is mostly a proof-of-concept thing
which came out of a chat with Peter Wemm.
It acts like a disk in all aspects, although it will be hard to boot
from it :-)
It will do very simple compression, in that a sector (512bytes)
which is filled with the same
This is a request for a review. This patch fixes a bug in specfs
relating to dealing with the EOF condition of a block device.
If the EOF occurs in the middle of a block, specfs was not
properly calculating the truncation for the I/O.
This problem was first found by Tor.
Mark Murray wrote:
- /usr/bin/login and friends are now linked against libscrypt
instead of libcrypt.
This is a link bug. The Makefile says "-lcrypt". JDP?
Umm...
Previously there was:
.if ${OBJFORMAT} == elf
SONAME= ${LCRYPTBASE}.so.${SHLIB_MAJOR}
.endif
This appears to have
:The "md" driver I committed today is mostly a proof-of-concept thing
:which came out of a chat with Peter Wemm.
:
:It acts like a disk in all aspects, although it will be hard to boot
:from it :-)
:
:It will do very simple compression, in that a sector (512bytes)
:which is filled with the same
Thanks for all the suggestions,
Here are some followup comments to some suggestions
* '...get a copy of mount...' I was not able to mount
anything so I could not copy from the floppy.
* '... why not start with 3.3 ...' I just got the hang
of cvsup so I wanted to try upgrade and make world
*
It looks like top and w are broken (whereas ps works) with a -current
from this night.
top displays weird stuff:
PID USERNAME PRI NICE SIZERES STATETIME WCPUCPU COMMAND
-1067947544 375545 185 50663 3078M 0K ? 64??? 134561792.00% 657040
0 root -22 49209
This appears to have been lost.
Hmm. I might be the culprit. Fixing now...
M
--
Mark Murray
Join the anti-SPAM movement: http://www.cauce.org
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
On Tue, Sep 21, 1999 at 07:51:18PM +0200, Mark Murray wrote:
This appears to have been lost.
Hmm. I might be the culprit. Fixing now...
Uh, this seems to have been fixed by Peter a moment ago.
Now the only thing that I'd like to know is: where do I get the
current CVS sources for
Now the only thing that I'd like to know is: where do I get the
current CVS sources for libdescrypt, so that this doesn't prevent
me from logging-in next time?
Usual places? It is in Internat as well.
M
--
Mark Murray
Join the anti-SPAM movement: http://www.cauce.org
To Unsubscribe: send
On Tue, Sep 21, 1999 at 08:09:02PM +0200, Mark Murray wrote:
Usual places? It is in Internat as well.
Yes, my question was more or less _where_ are the usual places :-)
because internat.freebsd.org is apparently down at the moment.
I finally got it from:
On Tue, Sep 21, 1999, Pierre Beyssac wrote:
I have reinstalled libkvm and a kernel in sync with the rest of
the system... Have I missed something?
You haven't given a lot of information. Was this the result
of a full buildworld, installworld and then new kernel?
Or did you just update
On Tue, Sep 21, 1999 at 01:30:02PM -0500, Chris Costello wrote:
You haven't given a lot of information. Was this the result
of a full buildworld, installworld and then new kernel?
Sorry I was unclear, yes: a full buildworld+installworld+new kernel
(the same installworld that broke login
On Tue, Sep 21, 1999 at 08:59:42PM +0200, John Hay wrote:
Can you explain a bit more what "apparently down" mean please?
I didn't manage to connect on it by ftp when I sent the previous
message. Apparently I haven't waited long enough: connectivity
between France and this machine is just
Ten'th update to the new ATA/ATAPI driver:
It been awhile since the last major update, as a benefit there
are some cool things in this one (and new bugs probably :) )...
The ATA driver has grown "real" timeout support for all devices.
This means that it should be possible to get in contact
Anybody who control CVS tree please copy
/usr/src/contrib/groff/troff/hyphen.us-ru
to
/usr/src/contrib/groff/tmac/locale/hyphen.us-ru
and
/usr/src/usr.sbin/lpr/filters.ru/koi2alt.c
to
/usr/src/usr.sbin/lpr/filters.ru/koi2alt/koi2alt.c
Thanx in advance.
--
Andrey A. Chernov
On Tue, Sep 21, 1999 at 08:40:07PM +0200, Pierre Beyssac wrote:
Sorry I was unclear, yes: a full buildworld+installworld+new kernel
(the same installworld that broke login and friends for me). This
includes kernel modules of course.
Something more (probably unrelated): when I exit top with
If you have a PIIX4 based SMP system and run current, could you
please try out this patch:
http://phk.freebsd.dk/piix/
I'm very interested in hearing if there are any measurable difference
apart from clock granularity being 3 times better.
--
Poul-Henning Kamp
Rebuilt world and kernel about 20 minutes ago, now XDM cores, along with
login, I've had to fall back to single user mode, whoever is workin' on this
let me know if you commit some fixes, I'll be awake for a few hours and I'd
love to test them (read as "love to have my box working again" ;'D).
On Tue, 21 Sep 1999, Luoqi Chen wrote:
This reminds me about the usage of TSC counter on SMP. First even though
we don't use TSC for time keeping on SMP, the TSC frequency from calibration
is still valid (at least for BSP), and we can show it in the cpu identification
message. Second, the
One question comes to mind: is there a way that the TSCs could become
desynchronized somehow? Even though all CPUs run at the same frequency,
isn't there a strong possibility for slight frequency deviation since
we use crystal oscillation instead of a more accurate atomic breakdown
for
24 matches
Mail list logo
