paradox writes:
> so, I really do not understand why it is so difficult [...]
Easy for you to say, since you're not the one who would have to do the
work and spend the next two years cleaning up the resulting mess.
DES
--
Dag-Erling Smørgrav - d..
the tree with colons in
their name, or files with the same name but different case in the same
directory)
DES
--
Dag-Erling Smørgrav - d...@des.no
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
T
to spin them all up at the same time. I would love
to be able to delay spinning up each disk until it's actually needed
(i.e. /etc/rc.d/zfs start).
DES
--
Dag-Erling Smørgrav - d...@des.no
___
freebsd-current@freebsd.org mailing list
http://lists
atabase is still going to crash.
DES
--
Dag-Erling Smørgrav - d...@des.no
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
tive to the start of the partition.
Unfortunately, you can't easily go from inode to file name; you have to
mount the file system and use something like find -inum.
DES
--
Dag-Erling Smørgrav - d...@des.no
___
freebsd-current@freebsd.org mailing list
block number *39879105* by findblk command?
Uh, 79725167 - 63 = 79725104 and 79725104 - 39845888 = 39879216. How
did you arrive at 39879105?
DES
--
Dag-Erling Smørgrav - d...@des.no
___
freebsd-current@freebsd.org mailing list
http://lists.freeb
Miroslav Lachman <000.f...@quip.cz> writes:
> Dag-Erling Smørgrav writes:
> > Uh, 79725167 - 63 = 79725104 and 79725104 - 39845888 = 39879216. How
> > did you arrive at 39879105?
> I am sorry, it was my confusion.
> My calculation was for *LBA=79725056* reported in
driver to see why the numbers are
different.
And if you're comfortable *writing* kernel code, I would suggest
implementing WORF in geom_mirror :)
DES
--
Dag-Erling Smørgrav - d...@des.no
___
freebsd-current@freebsd.org mailing list
http://lis
Pieter de Goeje writes:
> Dag-Erling Smørgrav writes:
> > And if you're comfortable *writing* kernel code, I would suggest
> > implementing WORF in geom_mirror :)
> I am intrigued, what is this WORF you speak of?
Write On Read Failure. It means that if you can't re
Michael Butler writes:
> This breaks most (if not all) of the QT4-dependent ports for the lack of
> a definition of "off64_t".
They should not use off64_t. More importantly, they should not rely on
zlib to provide it.
DES
--
Dag-Erling Smørgr
t;64" suffix) as if
none of this had ever happened.
And yes, I *will* keep harping on this until people Get It.
DES
--
Dag-Erling Smørgrav - d...@des.no
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Mark Linimon writes:
> Probably 75%+ of the application authors neither know nor care that
> their code is being run on anything other than Linux.
I think you missed the bit where what they're doing is wrong on Linux,
too.
DES
--
Dag-Erling Smørgrav -
Xin LI writes:
> Applications aiming to be portable should not define _LARGEFILE64_SOURCE
> at all, on any *BSD platforms.
nor on Linux.
DES
--
Dag-Erling Smørgrav - d...@des.no
___
freebsd-current@freebsd.org mailing list
http://lists.freeb
all can parse, so sysinstall can just fork-exec sade instead
of duplicating the code.
DES
--
Dag-Erling Smørgrav - d...@des.no
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Rui Paulo writes:
> Dag-Erling Smørgrav writes:
> > Alexander Leidinger writes:
> > > Please consider using SVN instead. A lot more users will be able
> > > to check out from there.
> > We don't grant non-committers access to the Subversion repo.
> Th
is in the past.
One of them was even fully funded by the FreeBSD Foundation. They all
failed.
DES
--
Dag-Erling Smørgrav - d...@des.no
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe,
nfigure a gnop? AFAIK there is no "gnop label", so you can't set up a
persistent gnop; you have to set it up manually at boot time every time,
and there's a risk that the fs (or other layers higher up) will taste
the underlying device instead of the gnop.
DES
--
recorded on-disk)
DES
--
Dag-Erling Smørgrav - d...@des.no
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Alexander Leidinger writes:
> Dag-Erling Smørgrav writes:
> > There have been at least three or four attempts to do this in the
> > past. One of them was even fully funded by the FreeBSD Foundation.
> > They all failed.
> I was told a lot of people tried to make t
John Baldwin writes:
> Dag-Erling Smørgrav writes:
> > My suggestion is to add a "sysinstall mode" to sade where it
> > operates under certain (minor) constraints and reports what it did
> > in a format that sysinstall can parse, so sysinstall can just
> >
won't be visible if we forcibly and unconditionally
use 4k sectors.
DES
--
Dag-Erling Smørgrav - d...@des.no
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail t
Alexey Tarasov writes:
> Advanced Format disks reports 512, but there is another command in ATA
> standard which can tell us if it uses 4k sector.
Send me one and I'll look into it :)
DES
--
Dag-Erling Smørgrav - d...@des.no
___
free
presentation layer is actually 80% of the work. What
you call the business logic already exists (libgeom).
DES
--
Dag-Erling Smørgrav - d...@des.no
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To
Garrett Cooper writes:
> If the user shoots him or herself in the foot, that's their own
> problem.
That kind of attitude is why people choose Linux over FreeBSD...
DES
--
Dag-Erling Smørgrav - d...@des.no
___
freebsd-current@freebsd.org m
Garrett Cooper writes:
> Dag-Erling Smørgrav writes:
> > Garrett Cooper writes:
> > > Dag-Erling Smørgrav writes:
> > > > [restored relevant context which was removed earlier in the thread]
> > > > ...which is exactly what I said - but in the sysinst
differ from
> typing a wrong command in?
Please, please, go have a cup of coffee, then come back and *read what I
wrote* instead of just making stuff up.
DES
--
Dag-Erling Smørgrav - d...@des.no
___
freebsd-current@freebsd.org mailing list
http://li
Andriy Gapon writes:
> P.S. DES's name looks strange in headers :-)
Get a better MUA. MIME quoted-printable has been around for what, 15
years?
DES
--
Dag-Erling Smørgrav - d...@des.no
___
freebsd-current@freebsd.org mailing l
`we're here' sade needs to be populating
> $DESTDIR/etc/fstab, not sysinstall ?
At that time (when sysinstall invokes sade) there is no $DESTDIR/etc -
sysinstall hasn't yet started extracting the base distribution.
DES
--
Dag-Erling Smørgrav - d...@des.no
_
o-raid "hardware" out there. ataraid(4) has served it's
> purpose, tiding us over until GEOM RAID facilities were in place. Now it's
> time for it to be retired.
gstripe can't create a bootable striped set; ataraid can.
DES
--
Dag-Erling Smørgrav - d...@des.no
_
Well, this won't be a problem if we have GEOM classes that can
> understand metadata created by the ATA RAID BIOS(es).
Most pseudo-raid kit has nifty features like checksum offloading,
composite writes etc. which can improve performance considerably. You
can't access those from GEOM.
Alexander Motin writes:
> Dag-Erling Smørgrav writes:
> > Most pseudo-raid kit has nifty features like checksum offloading,
> > composite writes etc. which can improve performance considerably. You
> > can't access those from GEOM.
> Have you ever seen them document
ug which sos@ worked around in the driver, I forget which)
> Any URLs?
Google "Promise FastTrak SATA RAID"
I have two or three of those, including one with on-board SDRAM (but no
battery backup)
DES
--
Dag-Erling Smørgrav - d...@des.no
___
Lev Serebryakov writes:
> "Dag-Erling Smørgrav" writes:
> > Most pseudo-raid kit has nifty features like checksum offloading,
> > composite writes etc.
> Why are they called ``PSEUDO-raids'' then?
Several reasons - they don't present the array to t
"Sean C. Farley" writes:
> This should trim some time off BSD grep.
Did you actually test your patch? It makes absolutely no measurable
difference.
DES
--
Dag-Erling Smørgrav - d...@des.no
___
freebsd-current@freebsd.org mail
e, try to mmap(2) it first, and if
that fails, fall back to the plain buffered read(2) method.
DES
--
Dag-Erling Smørgrav - d...@des.no
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe,
lone
language, but as an embeddable scripting engine. We could easily create
our own scripting language based on lua with FreeBSD-specific functions,
and there would be no fear of interfering with third-party software,
because it wouldn't be called lua.
DES
--
Dag-Erl
"Sean C. Farley" writes:
> Dag-Erling Smørgrav writes:
> > Did you actually test your patch? It makes absolutely no measurable
> > difference.
> Yes, I saw a reduction,
I didn't...
DES
--
Dag-Erling Smørgrav - d...@des.no
__
ng using for the build32 stage on
> amd64, where ${CC} has a bunch of flags (including -isystem, -L and -B)
> appended.
No, what is used is a variant of method 1 *on top of* method 2 for a
very specific case. You need "a special version of clang" (method 2)
an
Dimitry Andric writes:
> Dag-Erling Smørgrav writes:
> > No, what is used is a variant of method 1 *on top of* method 2 for a
> > very specific case. You need "a special version of clang" (method 2)
> > anyway to support cross-building.
> Eventually, clang s
defined as uint64_t on sparc64 and sun4v,
and in sys/boot as unsigned long int, which is the correct size on both
32-bit and 64-bit machines (assuming I32LP64).
DES
--
Dag-Erling Smørgrav - d...@des.no
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
by the user (the "TiVo clause"), although the bits that
are most commonly used in embedded devices (Linux itself and busybox)
are still under GPLv2.
DES
--
Dag-Erling Smørgrav - d...@des.no
___
freebsd-current@freebsd.org mailing list
http://
cense for us.
Does that really matter? We're not going to start building releases
with icc, are we?
DES
--
Dag-Erling Smørgrav - d...@des.no
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To
ult in people actually running the
> profiling tools which pointed to the buffering as the number one thing
> to fix.
There is a lesson here: people who are unsatisfied with the performance
of ${TOOL} should profile it before they start a flamefest on -current.
DES
--
Dag-E
this particular case I think
> it's pretty obvious that I'm either alone, or in a very non-vocal
> group; so c'est la vie.
"This is madness!"
"Madness? This... is... CURRENT!"
DES
--
Dag-Erling Smørgrav - d...@des.no
__
grep - expecting correctness and speed.
Based on my 12 years of experience in this project, you are very, very
wrong.
DES
--
Dag-Erling Smørgrav - d...@des.no
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/
"V. T. Mueller, Continum" writes:
> Dag-Erling Smørgrav writes:
> > Based on my 12 years of experience in this project, you are very,
> > very wrong.
> An 'argumentation' like the above is simply a killer phrase that ends
> every discussion.
An 'ar
0.000 100.00% regexec [38]
The culprit seems to be the first memchr() in grep_fgetln(). For some
reason, even with -O2, it is not inlined:
% echo "disassemble grep_fgetln" | gdb -q -batch -x /dev/stdin
/usr/obj/usr/src/usr.bin/grep/grep | grep memchr
0x0000000000402
and moreover FreeBSD HPC,
Not "FreeBSD clusters", but "*the* FreeBSD cluster", i.e. the .f.o
machines hosted by Y!.
DES
--
Dag-Erling Smørgrav - d...@des.no
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailma
his is not about "what we expect people to do" but about "what I expect
*you*, an experienced FreeBSD committer, to do" :)
DES
--
Dag-Erling Smørgrav - d...@des.no
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/
x27;%x' expects type 'unsigned
int', but argument 4 has type 'vm_offset_t'
/src/sys/powerpc/fpu/fpu_emu.c:778: warning: format '%x' expects type 'unsigned
int', but argument 3 has type 'register_t'
*** Error code 1
Stop in /obj/powerpc.powerpc64/src/
Adrian Chadd writes:
> I've just looked at grep_fgetln(). Surely memchr() isn't required there.
Of course it is, how else are you going to locate the '\n'? OTOH, I'm
not sure grep_fgetln() is needed at all.
DES
--
Dag-E
rr.
DES
--
Dag-Erling Smørgrav - d...@des.no
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
is no way to fix this with the current tinderbox code.
MHO is that the entire powerpc64 thing is very poorly thought out.
DES
--
Dag-Erling Smørgrav - d...@des.no
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listi
ught
> the system time for gnugrep and bsdgrep would be almost the same.
Two reasons:
1) BSD grep does tons of unnecessary memory-to-memory copy operations in
grep_fgetln().
2) GNU grep has its own highly optimized regex code.
DES
--
Dag-Erling Sm
bles other languages they already know, than Lisp, which doesn't.
DES
--
Dag-Erling Smørgrav - d...@des.no
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mai
Gabor PALI writes:
> Sorry for chiming in, just a quick idea. If you find the "get a
> high-level language that compiled to C" idea good,
I don't think it's a good idea, and I don't understand why this thread
seems stuck in that rut.
DES
--
Da
"b. f." writes:
> At r211506, 'grep -wq' does not seem to work properly (in the very
> least, it is not the same as with GNU grep),
"Does not seem to work properly" is not a very useful statement. The
least you could do is provide an example.
DES
-
erbox). What *would* help would be an easy way to determine,
*before* trying to build it, whether a specific kernel config is
appropriate for a specific target. Can you think of an easier way to do
this than to scan the config for the "machine&q
Gabor PALI writes:
> Dag-Erling Smørgrav writes:
> > Gabor PALI writes:
> > > Sorry for chiming in, just a quick idea. If you find the "get a
> > > high-level language that compiled to C" idea good,
> > I don't think it's a good idea
>
t an absolute. I think what we are doing
> isn't a problem for 99.999% of use cases.
On the rare occasions where I use sysinstall, I usually find that prompt
annoying... but I almost broke a CD drive once by ejecting the tray
with the enclosure's dust cover half clo
orrect line is "device md", but mdconfig(8) will automatically load
the module, so you don't need it.
DES
--
Dag-Erling Smørgrav - d...@des.no
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-
urrent bottleneck in BSD grep is the memchr() that looks for
'\n' in the input buffer.
DES
--
Dag-Erling Smørgrav - d...@des.no
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsu
Nathan Whitehorn writes:
> Dag-Erling Smørgrav writes:
> > I'm not sure I understand what you mean (or rather, how it would
> > help the tinderbox). What *would* help would be an easy way to
> > determine, *before* trying to build it, whether a specific kernel
>
scripting language, not a general-purpose one.
BTW, most of the Perl scripts we had were rewritten in C, not sed / awk.
DES
--
Dag-Erling Smørgrav - d...@des.no
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebs
e specific matches, since the index lists
only files, not exact positions. For anything other than fixed strings,
it reverts to agrep, but I assume (I haven't looked at the code) that if
the regexp has one or more fixed components, it uses those to narrow the
search space before running agrep.
D
classes, and you rewrite them to exclude
\n: /[^bar]/ becomes /[^bar\n]/, /./ becomes /[^\n]/, etc., and the
FSA will stop if it hits EOL before it reaches an accepting state.
DES
--
Dag-Erling Smørgrav - d...@des.no
___
freebsd-current
"Sean C. Farley" writes:
> Dag-Erling Smørgrav writes:
> > Aho-Corasick is not really a search algorithm, but an algorithm for
> > constructing a table-driven finite state machine that will match
> > either of the search strings you fed it. I believe it is less
Mike Haertel writes:
> Dag-Erling Smørgrav writes:
> > You don't really need to "isolate the containing line" unless you have
> > an actual match, do you?
> Theoretically no. However, suppose the pattern was /foo.*blah/.
> The Boyer-Moore search will be
"b. f." writes:
> Dag-Erling Smørgrav writes:
> > "Does not seem to work properly" is not a very useful statement. The
> > least you could do is provide an example.
> I did provide an example, later in the same sentence that you quoted.
I forgot to an
Dag-Erling Smørgrav writes:
> No idea what causes it, but a quick grep (hah!) for qflag turns up the
> following horror:
>
> /* Find out the correct return value according to the
>results and the command line option. */
> exit(c ? (notfound ? (
dfreeslot':
/usr/src/usr.bin/xargs/xargs.c:676: warning: old-style function definition
*** Error code 1
Stop in /usr/src/usr.bin/xargs.
DES
--
Dag-Erling Smørgrav - d...@des.no
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailma
s are wearing a bit thin. Is there a problem with the
> tinderbox build machine perhaps?
No, the failures are too systematic for that.
DES
--
Dag-Erling Smørgrav - [EMAIL PROTECTED]
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/l
t
happens to be triggered by make(1) because it is a big (if not the
biggest) vfork(2) consumer.
DES
--
Dag-Erling Smørgrav - [EMAIL PROTECTED]
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe,
I use it daily and have never had any trouble (except for the broken
Xalan in 1.4.1).
DES
--
Dag-Erling Smørgrav - [EMAIL PROTECTED]
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
directories
around.
DES
--
Dag-Erling Smørgrav - [EMAIL PROTECTED]
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Scott Long <[EMAIL PROTECTED]> writes:
> Anyone know what is up with this? I'm not getting it on my LINT builds.
revision 1.41
date: 2003/08/01 17:00:49; author: obrien; state: Exp; lines: +1 -1
Fix kernel build -- 'c' was the unused var, not 'lines'.
DE
Tinderbox <[EMAIL PROTECTED]> writes:
> TB --- mkdir /home/des/tinderbox/CURRENT
Disk failure on the tinderbox machine.
DES
--
Dag-Erling Smørgrav - [EMAIL PROTECTED]
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinf
.
The correct construct is tr '[:lower:]' '[:upper:]'
DES
--
Dag-Erling Smørgrav - [EMAIL PROTECTED]
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
sight.
It can be done, but not without cheating. You have to have the PAM
support code do chauthtok as part of the authentication sequence.
I've been meaning to do it for a while but haven't gotten around to it
yet.
DES
--
Dag-Erling Smørgrav - [EMAIL PROTECTED]
__
yanked away in the middle of
the run.
DES
--
Dag-Erling Smørgrav - [EMAIL PROTECTED]
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
nderbox to use.
DES
--
Dag-Erling Smørgrav - [EMAIL PROTECTED]
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
;t be bothered to make it work correctly
with all combinations of make install / make reinstall and
pre-existing /boot/kernel directory or symlink.
DES
--
Dag-Erling Smørgrav - [EMAIL PROTECTED]
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd
ould see what command is executed before the
script hangs.
DES
--
Dag-Erling Smørgrav - [EMAIL PROTECTED]
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
[EMAIL PROTECTED] /home/des# ps -opid,vsize,tsiz,command -p$$
PID VSZ TSIZ COMMAND
4712 23804 zsh
How can the text size for zsh be only 4 kB?
DES
--
Dag-Erling Smørgrav - [EMAIL PROTECTED]
___
[EMAIL PROTECTED] mailing list
http
04)
That shouldn't have any impact on my problem though, should it?
DES
--
Dag-Erling Smørgrav - [EMAIL PROTECTED]
Console: serial port
BIOS drive A: is disk0
BIOS drive C: is disk1
BIOS 640kB/523200kB available memory
FreeBSD/i386 bootstrap loader, Revision 1.1
([EMAIL PROTECTED], Mon Sep 1
Tomi Vainio - Sun Finland <[EMAIL PROTECTED]> writes:
> First maxusers was 0 then when changed it to 8.
That's a regression. Keep it at 0.
DES
--
Dag-Erling Smørgrav - [EMAIL PROTECTED]
___
[EMAIL PROTECTED] mailing list
http://lis
Tomi Vainio - Sun Finland <[EMAIL PROTECTED]> writes:
> Dag-Erling Smørgrav writes:
> > Tomi Vainio - Sun Finland <[EMAIL PROTECTED]> writes:
> > > First maxusers was 0 then when changed it to 8.
> > That's a regression. Keep it at 0.
> I understo
be really useful to know where the fault lies. We might even
(God forbid!) figure out a way to fix it. You can easily force the
system to boot with less than the full amount of memory by setting
hw.physmem to e.g. "64m" in /boot/loader.conf or at the loader prompt.
DES
--
Dag
Tomi Vainio - Sun Finland <[EMAIL PROTECTED]> writes:
> If you could just give instructions what you wanna get when system
> panics I might be able to persuade the other that we should crash our
> system once more.
I already have.
DES
--
Dag-Erling Smørgrav - [
Bryan Liesner <[EMAIL PROTECTED]> writes:
> The last change to ata-lowlevel (rev 1.11) causes a 10-15 second delay
> probing for a drive that's not there: [...]
Same symptoms here...
DES
--
Dag-Erling Smørgrav - [EMAIL PROTECTED]
___
ic problem with OpenSSH 3.5 which requires an update
to 3.6.1? Or do you just want me to update it to make the numbers
look pretty on your screen?
DES
--
Dag-Erling Smørgrav - [EMAIL PROTECTED]
___
[EMAIL PROTECTED] mailing list
http://lists.freeb
same bug, and 3.7 isn't out yet.
DES
--
Dag-Erling Smørgrav - [EMAIL PROTECTED]
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
David Rhodus <[EMAIL PROTECTED]> writes:
> On Tuesday, September 16, 2003, at 11:54 AM, Dag-Erling Smørgrav wrote:
> > Is there a specific problem with OpenSSH 3.5 which requires an update
> > to 3.6.1? Or do you just want me to update it to make the numbers
> > look p
ble,
like SCSI_DELAY?
DES
--
Dag-Erling Smørgrav - [EMAIL PROTECTED]
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Jeremy Messenger <[EMAIL PROTECTED]> writes:
> On Wed, 17 Sep 2003 10:57:58 +0200, Dag-Erling Smørgrav <[EMAIL PROTECTED]> wrote:
> > No. 3.6.1 has the same bug, and 3.7 isn't out yet.
> http://www.mindrot.org/pipermail/openssh-unix-announce/2003-September/64.
o on the RTP cluster.
John, is something wrong with cvsup on the RTP cluster?
DES
--
Dag-Erling Smørgrav - [EMAIL PROTECTED]
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
size
> *** Error code 1
Please ignore. It seems the RTP cluster's CVS repo is no longer being
updated; I've disabled the tinderbox until this is resolved.
DES
--
Dag-Erling Smørgrav - [EMAIL PROTECTED]
___
[EMAIL PROTECTED] mailing list
http:
ugger
An NMI almost certainly indicates a hardware failure.
DES
--
Dag-Erling Smørgrav - [EMAIL PROTECTED]
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Kris Kennaway <[EMAIL PROTECTED]> writes:
> Yes, since you have run installworld you have now installed a 5.x
> /bin/sh binary, which cannot run on the 4.x kernel you are running.
He *hasn't* run installworld; installworld would have installed the
new loader.
DES
--
Dag-Erling
Tinderbox <[EMAIL PROTECTED]> writes:
> [nothing]
argh!
/me fix
DES
--
Dag-Erling Smørgrav - [EMAIL PROTECTED]
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail t
1 - 100 of 430 matches
Mail list logo
