with a priority, propagate that priority down to the device
drivers and act accordingly in the disksort disk-scheduling code.
That would allow us to address not only the bgfsck but also things
like silly-seek-syndrome and other sub-optimal issues in our current
I/O system.
--
Poul-Henning Kamp | UNIX
In message [EMAIL PROTECTED], Frode Nordahl writ
es:
The nasty part:
- fdisk showed all partitions as type 165 (FreeBSD), I took a chance and
continued anyway. Now my two non-FreeBSD partitions are lost :)
Fixed.
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED
machine and the same devices. So why do they probe
wrong?
I have no idea either, but the answer must be somewhere in the da driver...
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
Never
In message [EMAIL PROTECTED], Poul-Henning Kamp
writes:
phk 2002/11/01 07:32:12 PST
Modified files:
sys/fs/specfsspec_vnops.c
Log:
Put a KASSERT in specfs::strategy() to check that the incoming buffer
has a valid b_iocmd. Valid is any one of BIO_{READ,WRITE,DELETE
.)
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
Never attribute to malice what can adequately be explained by incompetence.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe
etc)
This will show you what the libdisk library thinks about your disks.
I'd like to see the output, along with the output from:
sysctl -n kern.geom.conftxt
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD
: initialization from incompatible point
er type
*** Error code 1
Stop in /usr/obj/usr/src/sys/GENERIC.
*** Error code 1
Stop in /usr/src.
*** Error code 1
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3
=
Hi Craig,
Can you please email me:
boot -v console output (use serial console if you can)
sysctl -n kern.geom.confxml
Thanks in advance!
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD committer
In message [EMAIL PROTECTED], Craig Rodrigues writes:
--qDbXVdCdHGoSgWSk
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
On Thu, Oct 31, 2002 at 04:56:49PM +0100, Poul-Henning Kamp wrote:
Can you please email me:
boot -v console output (use serial console if you
Makefile.inc1 par-cleandir
=== kerberos5
=== lib/libpam
=== lib/libssh
cd: can't cd to /usr/src/lib/libssh
=== secure/usr.bin/ssh
*** Error code 2
=== kerberos5/doc
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD committer | BSD since
/share/man/man3
install -o root -g wheel -m 444 com_err.3.cat.gz
/R/stage/trees/base/usr/share/man/man/cat3/com_e
rr.3.gz
install: /R/stage/trees/base/usr/share/man/man/cat3/com_err.3.gz: No such file or
directory
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED
.
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
Never attribute to malice what can adequately be explained by incompetence.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe
/obj/usr/src/secure/usr.sbin/sshd/../../../kerbe
ros5/lib/libroken -lroken -lopie -lmd -lssh -lcrypt -lcrypto -lutil -lz -lwrap -
lpam
auth1.o: In function `do_authloop':
auth1.o(.text+0x220): undefined reference to `mm_auth_krb5'
*** Error code 1
1 error
*** Error code 2
--
Poul-Henning Kamp
In message [EMAIL PROTECTED], Dag-Erling Smorgrav writes:
Poul-Henning Kamp [EMAIL PROTECTED] writes:
auth1.o: In function `do_authloop':
auth1.o(.text+0x220): undefined reference to `mm_auth_krb5'
*** Error code 1
1 error
*** Error code 2
You must have cvsupped at a bad time - looks like
In message [EMAIL PROTECTED], Dag-Erling Smorgrav writes:
Poul-Henning Kamp [EMAIL PROTECTED] writes:
In message [EMAIL PROTECTED], Dag-Erling Smorgrav writes:
You must have cvsupped at a bad time - looks like you missed the three
Makefile deltas in src/secure.
I just started over, and cvsup
In message [EMAIL PROTECTED], Dag-Erling Smorgrav writes:
Poul-Henning Kamp [EMAIL PROTECTED] writes:
Inside the chroot.
'make release' checks out src in the sandbox, then chroots to it and
does a plain 'make world' right? There's no chance the sources in the
sandbox were stale
In message [EMAIL PROTECTED], Maksim Yevmenkin writes:
the question is: are options GEOM and NODEVS compatible?
No, they are not.
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
Never
if=/dev/ad0 bs=1k count=64 | uuencode ache.ad0
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
Never attribute to malice what can adequately be explained by incompetence.
To Unsubscribe
stat(c0f26340,cc34ad10,c039bed6,409,2) at stat+0x52
syscall(2f,2f,2f,8057e86,805b52f) at syscall+0x28e
Xint0x80_syscall() at Xint0x80_syscall+0x1d
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3
extracting dists.
It seems cd /dev; sh MAKEDEV all is failed at devfs environment.
I found it.
Phk changes in 1.297 of src/etc/Makefile not to install MAKEDEV by
default. Options may be:
(3) Drop non-devfs code from sysinstall (really???).
This is the way we're going.
--
Poul-Henning Kamp
extracting dists.
It seems cd /dev; sh MAKEDEV all is failed at devfs environment.
I found it.
Phk changes in 1.297 of src/etc/Makefile not to install MAKEDEV by
default. Options may be:
This should be fixed now I hope.
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL
. This gives us a scatter gather ability in
the entire disk I/O path.
This opens up a host of possibilities for things like clustering,
background writes (using copy-on-write pages) etc etc etc.
Needless to say, it will also drastically change the working
environment for struct buf.
--
Poul-Henning
in your way just disconnect libdisk from the build.
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
Never attribute to malice what can adequately be explained by incompetence.
To Unsubscribe
promise to fix all the issues which come up, but I will do my
very best...
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
Never attribute to malice what can adequately be explained by incompetence
=
=mKIc
-END PGP SIGNATURE-
--LQksG6bCIzRHxTLp--
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD committer | BSD
In message [EMAIL PROTECTED], Ruslan Ermilov writes:
--gr/z0/N6AeWAPJVB
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
On Tue, Oct 22, 2002 at 08:41:38AM +0200, Poul-Henning Kamp wrote:
=20
Thankyou!
=20
This is most valuable
In message [EMAIL PROTECTED], Seigo Tanimur
a writes:
The patch at:
http://people.FreeBSD.org/~tanimura/patches/dynamicbuf.diff.gz
Comments and flames are welcome. Thanks a lot.
This looks very very interesting!
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED
In message [EMAIL PROTECTED], Vitaly Markitantov writes:
Where i can found performance comparison of -CURRENT over -STABLE systems?
Very little has been done yet, -CURRENT is not expected to perform
particularly well until more of the kernel is out from under the
Giant lock.
--
Poul-Henning
/resolv.conf, stopping the install dead in
its tracks.
This bugs were fixed about 20 hours ago.
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
Never attribute to malice what can adequately
In message [EMAIL PROTECTED], [EMAIL PROTECTED]
.de writes:
Is sysinstall still supposed to copy the contents of the mfsroot-
image to /stand ? This at least results in two copies of sysinstall,
one in /stand and the other one in /usr/sbin.
That is intentional
--
Poul-Henning Kamp | UNIX
In message [EMAIL PROTECTED], [EMAIL PROTECTED]
.de writes:
On Tue, Oct 22, 2002 at 10:39:32PM +0200, Poul-Henning Kamp wrote:
That is intentional
Is it ok then that the sysinstall in /stand of the 0917-JPSNAP
immediately dumps core with signal 10 when run on a 1017 -current ?
Current
===
Somehow your rijndael-api-fst.c is not up to date, you should have
rev 1.4.
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
Never attribute to malice what can adequately be explained
in advance,
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
Never attribute to malice what can adequately be explained by incompetence.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe
In message [EMAIL PROTECTED], Kris Kennaway writes:
--4SFOXa2GPu3tIq4H
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
On Mon, Oct 21, 2002 at 07:49:13PM +0200, Poul-Henning Kamp wrote:
=20
A number of us go into release
it for write and closing again.
Something as simple as
sh -c true 4/dev/da2
may do the trick.
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
Never attribute to malice what can adequately
);
struct mtx mymutex;
bzero(mymutex, sizeof mymutex);
mtx_init(mymutex, g_up, MTX_DEF, 0);
mtx_lock(mymutex);
It looks like mtx_init() cannot be called without holding Giant
which is clearly a bug.
--
Poul-Henning Kamp
if you have open partitions under that
device, I have patches underway for that.
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
Never attribute to malice what can adequately be explained
, but not substituting another value.
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
Never attribute to malice what can adequately be explained by incompetence.
To Unsubscribe: send mail to [EMAIL PROTECTED
, this would be OK with me, I would
probably say ENOENT instead. EINVAL generally means you gave a
wrong parameter to a syscall, ENOENT is more of a Looked, found
nothing kind of error.
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD
, both with and without GEOM
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
Never attribute to malice what can adequately be explained by incompetence.
To Unsubscribe: send mail to [EMAIL
causes panic at wdsleep() via
wdopen(). Please fix this problem or back out your change.
Can you provide some details on this panic ?
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
Never
)
*/
error = g_getattr(MBR::type, cp, i);
- if (!error i != 165 flags == G_TF_NORMAL)
+ if (!error i != 165 i != 169 flags == G_TF_NORMAL)
break;
/* Get sector size, we need it to read data. */
--
Poul-Henning Kamp
,
NOCRED, td);
--
Peter Edwards
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3
In message [EMAIL PROTECTED], Jens Schweikhardt writes:
On Sun, Oct 13, 2002 at 05:20:11PM +0200, Poul-Henning Kamp wrote:
In file included from /src/current/sys/geom/geom_bsd.c:62:
/src/current/sys/sys/disklabel.h:174: size of array `__assert174' is negative
*** Error code 1
because
There are quite a number of these gadgets on eBay right now, they would
probably make a cheap entry-level platform for powerpc work:
http://cgi.ebay.com/ws/eBayISAPI.dll?ViewItemitem=2059912083
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC
In message [EMAIL PROTECTED], Bruce Evans writes:
On Wed, 9 Oct 2002, Poul-Henning Kamp wrote:
In message [EMAIL PROTECTED], Seth Hieronymus writes:
I think your recent commits have fixed my hang on boot with an empty
ZIP-drive. Thank you.
Cool.
It still can't even mount root for my
to
get the slice number passed in a way that is recognized by all
kernels of interest (or change ROOTDEVNAMES back and forth)
Yes, you might in fact risk being dragged (kicking and screaming
I'm sure) into the middle nineties.
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL
-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
Never attribute to malice what can adequately be explained by incompetence.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current
a patch sitting in my tree which I couldn't get to work,
probably because the blocksize issue obscured it, I'll get to it
one of these days.
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
In message [EMAIL PROTECTED], Seth Hieronymus writes:
I think your recent commits have fixed my hang on boot with an empty
ZIP-drive. Thank you.
Cool.
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD committer | BSD since
/where
diff -ur /some/where /
manual review.
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
Never attribute to malice what can adequately be explained by incompetence
This patch may also fix problems on PC98 which as far as I know
have 1k sector disks, so if some of the PC98 people could
try it a GEOM kernel out now I would be grateful.
Poul-Henning
In message [EMAIL PROTECTED], Poul-Henning Kamp
writes:
phk 2002/10/07 00:15:37 PDT
Modified
is
what the problem is. Some where in /sys/dev/ata is an EBUSY that should
be ENXIO.
If you can instrument at least atapi-all.c and atapi-fd.c and help track
this down it would be most helpful.
I talked with sos@ about this today, and I'll be working on something
tonight.
--
Poul-Henning Kamp
be valid.
No, GEOM is a strictly stacking system, so in that case the disklabel
would be on ad0c and ad2c
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
Never attribute to malice what can
, counter-intuitive and prone to mistakes.
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
Never attribute to malice what can adequately be explained by incompetence.
To Unsubscribe: send mail
works then...
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
Never attribute to malice what can adequately be explained by incompetence.
To Unsubscribe: send mail to [EMAIL PROTECTED
not sure where it is documented, but you can
access each track separately with some /dev/acd0t%d kind of syntax
or something.
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
Never attribute
In message [EMAIL PROTECTED], Alexander Leiding
er writes:
On Sat, 05 Oct 2002 22:39:03 +0200
Poul-Henning Kamp [EMAIL PROTECTED] wrote:
One hand for your own code, and one hand for the infrastructure.
We have several areas of the kernel which is in disrepair, the
worst is buf/VM
it on the page, correspond with volounteers,
poll them to see if they gave up etc etc etc.
Otherwise there is no point in even starting it.
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
Never
DTRT, but it will also accept
un-offset ondisk disklabels, which I hope we can migrate to now.
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
Never attribute to malice what can adequately
places
in vfs_mount.c and cd9660_vfsops.c where you see it using EINVAL
and try to find out which particular one it is ?
printf(EINVAL HERE %s %d\n, __FILE__, __LINE__):
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD
;
printf(%.3f\n, (a / N) * 1e9 );
exit (0);
}
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
Never attribute to malice what can adequately be explained by incompetence
if that solves the problem ?
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
Never attribute to malice what can adequately be explained by incompetence.
To Unsubscribe: send mail to [EMAIL PROTECTED
In message [EMAIL PROTECTED], Seth Hieronymus writes:
You were right. After trying both a CD, and a zip-disk in the computer
(both together, and separately), having a zip-disk in the drive seems to
allow the boot to continue normally.
ATA(PI) or SCSI interface ZIP ?
--
Poul-Henning Kamp
no media rather
than ENXIO as it should.
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
Never attribute to malice what can adequately be explained by incompetence.
To Unsubscribe: send mail
In message [EMAIL PROTECTED], Bruce Evans writes:
On Sat, 5 Oct 2002, Peter Wemm wrote:
Bruce Evans wrote:
On Fri, 4 Oct 2002, Poul-Henning Kamp wrote:
Worst case you will have the option to use:
options NOGEOM
options vinum
A NOGEOM option would be as acceptable
-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
Never attribute to malice what can adequately be explained by incompetence.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current
experience will have to judge if I delivered on the promises I made
along the way.
Thanks for listening,
Poul-Henning
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
Never attribute to malice what can
/cd0 and not try to append 'c',
there are not, and have probably never been BSD disklabels
on enough disks to warrant this hack.
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
Never attribute
a disklabel.
Same errors with ad2.
Same diagnosis.
Typically you will find that devices with disklabels are named
ad%ds%d
All the partitions do mount and seem to work OK, so I'm not sure how
much of this is expected behavior.
All of it :-)
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
).
(Still not connected to the build)
Revision ChangesPath
1.2 +22 -12src/lib/libexpat/Makefile
1.1 +59 -0 src/lib/libexpat/libbsdxml.3 (new)
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD
/geom/geom_disk.c ?
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
Never attribute to malice what can adequately be explained by incompetence.
To Unsubscribe: send mail to [EMAIL PROTECTED
In message [EMAIL PROTECTED], n0go013 writes
:
On 04.10-15:40, fergus wrote:
On 04.10-14:20, Poul-Henning Kamp wrote:
[...]
I suspect vinum uses this sysctl to get an inventory of disks in
the system, so can I get you to try again making sure you have
rev. 1.20 of src/sys/geom/geom_disk.c
In message [EMAIL PROTECTED], n0go013 writes
:
On 04.10-18:27, Poul-Henning Kamp wrote:
In message n0go013 writes :
On 04.10-15:40, fergus wrote:
On 04.10-14:20, Poul-Henning Kamp wrote:
[...]
I suspect vinum uses this sysctl to get an inventory of disks in
the system, so can I
In message [EMAIL PROTECTED], Lars Eggert writes:
This is a cryptographically signed message in MIME format.
--ms040706010906030302070807
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Poul-Henning Kamp wrote:
I would need to look
In message [EMAIL PROTECTED], Ju
lian Elischer writes:
No, it is established principal tha the importer of new features has the
responsibility to make older subsystems work.
I'm _so_ glad to hear _you_ say that:
When will you have made KSE work on sparc64 and ia64 ?
--
Poul-Henning Kamp
lost more data on vinum RAID5
volumes than on striped ccd parititions, and not becaue of hardware
failures.
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
Never attribute to malice what can
.
If it is useful in any capacity, even as hint of what/how to do such
a thing, I think we should leave it. If it is just old junk we
should boot it.
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
In message [EMAIL PROTECTED], Daniel E
ischen writes:
On Fri, 4 Oct 2002, Poul-Henning Kamp wrote:
In message [EMAIL PROTECTED], Ju
lian Elischer writes:
No, it is established principal tha the importer of new features has the
responsibility to make older subsystems work.
I'm _so_ glad
was a nice way of paying homage, and if we decide to reverse
the naming decision later it would save us trouble.
That's why I didn't ask for a repo-move/copy.
If the concensus is that the directory should be renamed, I have
no objections to that, I'll just go with the flow.
--
Poul-Henning Kamp
since it was mostly a proof-of-concept
thing for data transformations in GEOM.
On its way to -current is an industry-strength disk-encryption, but
it is not commit ready yet.
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD committer
In message [EMAIL PROTECTED], Eric Hodel writes:
--wRRV7LY7NUeQGEoC
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
Poul-Henning Kamp ([EMAIL PROTECTED]) wrote:
In message [EMAIL PROTECTED], Eric Hodel writes:
=20
the bit
: vinum opens devices directly at the cdevsw
level, bypassing in the process the vnodes and specfs.
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
Never attribute to malice what can
sectorsize
fwsectors
fwheads
The last two are only to be used to read/write firmware/bootstrap
compatible magic data on the disks.
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3
not prevent us from taking the other route
later on, whereas putting an official-looking expat in the tree
and yanking that later would be a mess.
Any famous last words before the fat lady sings ?
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since
see how
ports could be affected.
At least not until somebody starts deliberately looking for that name.
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
Never attribute to malice what can
at 12:17:53PM +0200, Poul-Henning Kamp wrote:
This is just to note that I have updated the JKH page with a lot of new
stuff, so if your coding-pencil itches:
http://people.freebsd.org/~phk/TODO/
|Make -j improvement
|
|make(1) with -j option uses a select loop to wait for events
in
a similar fashion.
noted.
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
Never attribute to malice what can adequately be explained by incompetence.
To Unsubscribe: send mail to [EMAIL
the permissions
of whatever they point at is used.
I don't think DEVFS is the source of your problem here, I can't think
how it would be. I wonder more if this is an oversight of the
new mount code.
mux@ any input there ?
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL
the issue could be made moot by some /etc support for devfs(1).
In fact, as the loudest supporter of MAKEDEV, you might be the best
person to drive its transcription into /etc/defaults/devfs.conf. :-)
And with devfs(8), you can enact your personal policy just the way
you like :-)
--
Poul-Henning
for us.
In the meantime, DEVFS is the best I could come up with which makes
life simpler for users, developers and administrators, and still
retains as many of the flaws as we want to keep.
Like it or not, unless you have a better alternative you'll be stuck
with it.
--
Poul-Henning Kamp
?, it should be obvious from context :-)
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
Never attribute to malice what can adequately be explained by incompetence.
To Unsubscribe: send mail
a few
working weeks of development time so far.
I don't think you are anywhere near the mean, or the median for
that matter, of FreeBSD users.
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
In message [EMAIL PROTECTED], Andrew Gallatin w
rites:
Poul-Henning Kamp writes:
Provided nothing terminal pops up in the next 5 days, GEOM will
become default in -current on Saturday 5th of october.
Please test it now on _your_ configuration and tell me if it
fails to work
In message [EMAIL PROTECTED], Takahashi Yoshihiro
writes:
In article [EMAIL PROTECTED]
Takahashi Yoshihiro [EMAIL PROTECTED] writes:
In article [EMAIL PROTECTED]
Poul-Henning Kamp [EMAIL PROTECTED] writes:
Provided nothing terminal pops up in the next 5 days, GEOM will
become default
In message [EMAIL PROTECTED], Sheldon Hearn writes:
On (2002/09/30 21:09), Poul-Henning Kamp wrote:
Maybe you'd get more testers if you wait until the latest serious
problems are resolved before going ahead.
Maybe you wouldn't, though. So I wouldn't be annoyed if you responded
with Worth
In message [EMAIL PROTECTED], Bruce Evans writes:
On Mon, 30 Sep 2002, Poul-Henning Kamp wrote:
Provided nothing terminal pops up in the next 5 days, GEOM will
become default in -current on Saturday 5th of october.
Please test it now on _your_ configuration and tell me if it
fails to work
In message [EMAIL PROTECTED], Bruce Evans writes:
On Mon, 30 Sep 2002, Poul-Henning Kamp wrote:
In message [EMAIL PROTECTED], David O'Brien writes:
On Mon, Sep 30, 2002 at 09:09:46PM +0200, Poul-Henning Kamp wrote:
Provided nothing terminal pops up in the next 5 days, GEOM will
become
In message [EMAIL PROTECTED], Bruce Evans writes:
On Tue, 1 Oct 2002, Poul-Henning Kamp wrote:
In message [EMAIL PROTECTED], Bruce Evans writes:
On Mon, 30 Sep 2002, Poul-Henning Kamp wrote:
Provided nothing terminal pops up in the next 5 days, GEOM will
become default in -current
In message [EMAIL PROTECTED], Takahashi Yoshihiro
writes:
In article [EMAIL PROTECTED]
Poul-Henning Kamp [EMAIL PROTECTED] writes:
Provided nothing terminal pops up in the next 5 days, GEOM will
become default in -current on Saturday 5th of october.
Please test it now on _your_
601 - 700 of 1643 matches
Mail list logo
