d MD(4) devices
(and vn(4) devices before that).
One way or another: It is _not_ a GBDE problem.
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
ing vnode backed md(4) devices is sort of incestuous, and that may
be what happens here: For certain operations it is necessary to lock
all the way to the top of the filesystem, and this may be what results
in a deadlock for you now.
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PRO
will not get paged in. I often see the getty's for
the vty's and similar junk on my swap space.
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD committer | BSD sin
ice is init'ed and attached but the
master key and lock sector is never written to the device. This
is the mode you want to use for paging devices.
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD committer | BSD since 4
date
sysctl kern.malloc
sysctl vm.zone
swapinfo
ps -axlw
and look out for anything which just gobbles up more and more
memory.
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD committer | BSD sinc
bp2->bio_cmd = bp->bio_cmd;
bp2->bio_length = bp->bio_length;
@@ -304,6 +325,7 @@
bzero(&mymutex, sizeof mymutex);
mtx_init(&mymutex, "g_xdown", MTX_DEF, 0);
+ mtx_init(&gbiomutex, "gbio", MTX_DEF, 0);
for(;;)
In message <[EMAIL PROTECTED]>, Poul-Henning Kamp writes:
>
>[I'm CC'ing current because this seems to have a significant negative
>impact on -current kernel stability, and we can use some more data,
>in particular on non-i386 SMP machines]
I just committed a workar
In message <[EMAIL PROTECTED]>, Poul-Henning Kamp writes:
>
>[I'm CC'ing current because this seems to have a significant negative
>impact on -current kernel stability, and we can use some more data,
>in particular on non-i386 SMP machines]
OK, thanks to a very qu
the disk has been labeled by previous
>versions and upgraded from source.
That sounds interesting. Can you send me the outout of:
diskinfo /dev/ad0*
sysctl -b kern.geom.confxml
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RF
lem for you, the above is the workaround.
--
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
ion it appears in.)
>/vol/vol0/users/des/tinderbox/CURRENT/sparc64/sparc64/src/sys/kern/kern_ktr.c:270:
>warning: unused variable `c'
>*** Error code 1
What gives ?
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD commit
temadministrator Tel.: (+43 1) 4277-14073
>Vienna University Computer Center Fax.: (+43 1) 4277-9140
>University of Vienna http://mailbox.univie.ac.at/~le/
>
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TC
syscall+0x273
Xint0x80_syscall() at 0xc032e23d = Xint0x80_syscall+0x1d
--- syscall (6), eip = 0x80b2edb, esp = 0xbfbff69c, ebp = 0xbfbff6a8 ---
Debugger("witness_lock")
Stopped at 0xc032cab4 = Debugger+0x54: xchgl %ebx,0xc0432164 = in_Debugger.0
db> cont
--
Poul-Henni
;frame=0x0) at /usr/src/sys/kern/kern_fork.c:794
> td = (struct thread *) 0x0
> p = (struct proc *) 0xc6139d3c
>(kgdb) quit
>[EMAIL PROTECTED] crash]# exit
>
>Script done on Mon Aug 4 23:58:35 2003
>
>--
>Lukas Ertl eMail: [EMAIL PROTECTED]
PICKUP_GIANT();
+ /* PICKUP_GIANT(); */
} else
DEV_STRATEGY(bp);
--
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 mali
as being more beneficial to the project.
>Could you please give details (privately if you want, but I think this
>could be of interest to other people too).
See sys/fs/specfs/specfs_vnops.c, that is probably faster.
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED]
ght have been
renamed or have multiple names.
--
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 e
In message <[EMAIL PROTECTED]>, Poul-Henning Kamp
writes:
>phk 2003/08/06 08:05:28 PDT
>
> FreeBSD src repository
>
> Modified files:
>sys/i386/i386tsc.c
>sys/i386/include clock.h
>sys/i386/isa clock.c
> Log:
> Don
h Matt Jacob maintains.
--
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.
__
bp2->bio_offset = (off_t)bp->bio_blkno << DEV_BSHIFT;
>402 KASSERT(bp2->bio_offset >= 0,
>403 ("Negative bio_offset (%jd) on bio %p",
>404 (intmax_t)bp2->bio_offset, bp));
>405 bp2->bio_length = (off_t)bp->bio
lproc -- (already displayed)
Spin locks:
Locks which were never acquired:
rip
pseudofs_fileno
msq
semid
cd9660_ihash
msdosfs dehash
bpf interface lock
ACPI global lock
taskqueue
strategy
bounce pages lock
jumbo mutex
securelevel mutex lock
UUID generator mutex lock
umtx
phys_pager list
vm map sleep
off
up to 2 interrupts per second.
--
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 message <[EMAIL PROTECTED]>, Lukas Ertl writes:
>On Wed, 6 Aug 2003, Poul-Henning Kamp wrote:
>
>> In message <[EMAIL PROTECTED]>, [EMAIL PROTECTED] writes:
>> >Hello Poul,
>> >
>> >Can you please look into problems reported on current@ li
y wrong thing to
do, and it seems that vinum does not respect the D_NOGIANT
flag which GEOM recently started setting.
--
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
There is no way my work could cause reboots from the bootmgr or loader.
--
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 adequate
In message <[EMAIL PROTECTED]>, Poul-Henning Kamp
writes:
>phk 2003/08/13 00:21:54 PDT
>
> FreeBSD src repository
>
> Added files:
>tools/tools/ministat Makefile README chameleon iguana
> ministat.c
I just added this small tool
the disklabel, and you should be happy again.
We actually have a swapoff(8) 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
Never attribute to malice what can adequately be ex
ather than take the detour over vnodes and specfs.
This will not happen in the first couple of weeks I suspect.
--
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 wha
I plan to remove the pca driver in about a week.
Protest only from actual users respected.
If you don't know what pca is or what it does, do not even send email.
Thank you!
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
Fr
ics.
> I changed the /etc/rc.conf
>start_vinum="YES" to NO and can start ok now.
What was the actual panic message ?
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
Never a
/etc.
*** FATAL ERROR: Cannot 'cd' to /usr/src/etc and install files to
the temproot environment
critter#
--
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 m
Can you try to print out the bp->b_dev structure
if you still have the dump ?
--
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 adeq
In message <[EMAIL PROTECTED]>, Eivind Olsen writes:
>--On 12. august 2003 21:26 +0200 Poul-Henning Kamp <[EMAIL PROTECTED]>
>wrote:
>> In message <[EMAIL PROTECTED]>, Eivind Olsen writes:
>>> Hello. Some of you might have seen my previous mailings regardi
oking at
>it now and will probably be committing a fix.
Already committed.
--
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 ex
In message <[EMAIL PROTECTED]>, MATOBA Hirozumi wri
tes:
>On condition of hw.acpi.cpu.performance_speed as 8,
>the clock works
You should not be using the TSC for timekeeping if you change the
frequency of it.
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMA
h Disk Drive 2.05
+* Serial Number ST92163-2000
+*/
+ {T_DIRECT, SIP_MEDIA_REMOVABLE, "General Flash Disk Drive",
+"*", "*"},
+ /*quirks*/ DA_Q_NO_SYNC_CACHE
+ }
#endif /* DA_OLD_QUIRKS */
};
x27;t this effectively doom any attempt at getting rid af Giant
from below ?
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
Never attri
t;TSC" frequency 1595302164 Hz
>| $ sysctl -w kern.timecounter.hardware=i8254
>| Fixes the problem for me. I suspect you should set this in
>| /etc/sysctl.conf to enable it permanently.
>
>Thank you for your advice.
I've given timecounters "qualities" which sho
fter it has been closed. I am not sure
how this is possible, the mountpoint should be long gone etc.
--
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 ade
In message <[EMAIL PROTECTED]>, Robe
rt Watson writes:
>
>On Sat, 16 Aug 2003, Poul-Henning Kamp wrote:
>
>> >> The problem seems to be due to select() being called on the /dev/null
>> >> device, and it is holding the filedesc lock when it reaches
>>
0
#define SIS_RXDMA_256BYTES 0x0070
-#define SIS_RXCFG256 \
- (SIS_RXCFG_DRAIN(64)|SIS_RXDMA_256BYTES)
+#define SIS_RXCFG128 \
+ (SIS_RXCFG_DRAIN(128)|SIS_RXDMA_128BYTES)
#define SIS_RXCFG64 \
(SIS_RXCFG_DRAIN(64)|SIS_RXDMA_64BYTES)
--
Poul-Henning Kamp
In message <[EMAIL PROTECTED]>, David Malone writes:
>On Sat, Aug 16, 2003 at 10:18:43PM +0200, Poul-Henning Kamp wrote:
>> At one point we have to say "Well, the locks we have above are solid,
>> but we need to drop Giant below here" but if Witness sees a
>>
>+.It Pa /dev/acd0
> .El
> .Sh AUTHORS
> .An Jean-Marc Zucconi
>
>
>
>
>--
>Craig Rodrigues
>http://crodrigues.org
>[EMAIL PROTECTED]
>___
>[EMAIL PROTECTED] mailing list
>http://lists.freebsd.org/m
tempted allocated which can contain
more entries.
You can adjust both the regular and the overflow table sizes with
compile time constants NDEVFSINO and NDEVFSOVERFLOW.
When more of the kernel has been de-Giantized, this code can be
revisited and these constants can probably be eliminated.
--
Po
the sleep interruptible
would break all sorts of standards)
--
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 ade
In message <[EMAIL PROTECTED]>, Jens Rehsack writes:
>I have 2 machines with P4P800-Deluxe with the 3C940. If phk@ could fix
>the swap-issue, so that I can reboot easily, I would test your patches,
>too.
"swap-issue" ?
--
Poul-Henning Kamp | UNIX since Zilog Z
rmine what values are optimal.
Any input you have in that respect are most welcome (send it to sam@ and phk@)
--
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 ad
to calculate
the parity, it cannot just DMA the data out into hardware like a
scsi controller can do.
--
Poul-Henning Kamp FreeBSD coreteam member
[EMAIL PROTECTED] "Real hackers run -current on their laptop."
FreeBSD -- It will take a long time before progress
+++ sys/isa/fd.c 2000/03/24 20:20:53
>@@ -2228,6 +2228,7 @@
> BUF_LOCKINIT(bp);
> BUF_LOCK(bp, LK_EXCLUSIVE);
> bp->b_flags = B_PHYS | B_FORMAT;
>+ bp->b_iocmd = BIO_WRITE;
>
> /*
>* calculate a fake blkno, so fdstr
t I can't find malloc.conf anywhere in /usr/src. How does it get
>created during the build ?
>
> -Arun
>
>
>To Unsubscribe: send mail to [EMAIL PROTECTED]
>with "unsubscribe freebsd-current" in the body of the message
>
--
Poul-Henning Kamp FreeBSD
In message <[EMAIL PROTECTED]>, Arun Sharma writes:
>On Sat, Mar 25, 2000 at 08:55:16PM +0100, Poul-Henning Kamp wrote:
>>
>> Please read the malloc(3) manual page.
>>
>
>I did and created malloc.conf as documented there. And things were
>fine after that
In message <[EMAIL PROTECTED]>, Arun Sharma writes:
>On Sat, Mar 25, 2000 at 09:05:18PM +0100, Poul-Henning Kamp wrote:
>> In message <[EMAIL PROTECTED]>, Arun Sharma writes:
>> >On Sat, Mar 25, 2000 at 08:55:16PM +0100, Poul-Henning Kamp wrote:
>> >>
&
ith Matt's SMP stuff
>and came across a problem where it seems that 5.0 doesn't get any
>IO down to my vinum striped disks.
>
>I'll get panics,
You should know better than expect help providing only this little
information...
--
Poul-Henning Kamp FreeBSD
ire message?
If you had at least told me what panic you were getting I might
have looked :-)
Alfred, belive me, I'm doing my best here, but simply saying "I'll
get panics" is so far from a respectable bug report that I will
ignore it nomatter who sends it.
-
ddress space.
>
>It would be cheaper just to lock the bloody thing, although you can't
>pack all the significance of a timeval into 16 bits anyway (in a fashion
>that's going to make many people happy).
Or do the "stable-storage" thing with it, and just grab
>Only the i8254 timecounter hardware currently needs interrupt-disabling,
>but it is hopefully never used on SMP machines.
Worse. It is used by default on SMP machines which don't sport the
PIIX timecounter.
--
Poul-Henning Kamp FreeBSD coreteam member
[EMAIL PROTECTED]
e had a paper in the works about timecounters for over a year
now, I should really sit down and finish it.
--
Poul-Henning Kamp FreeBSD coreteam member
[EMAIL PROTECTED] "Real hackers run -current on their laptop."
FreeBSD -- It will take a long time befo
In message <[EMAIL PROTECTED]>, Jesper Skriver writes:
>On the box below, a relative new dual PIII box, with a Intel
>motherboard, does it use the i8254 or the PIIX timecounter ?
>
>[...]
>Timecounter "PIIX" frequency 3579545 Hz
You're using the PIIX.
--
P
as a goal something at least as comparable as what IBM did
>with one of their mainframes. Oh, say, lets shoot for being able to
>run 4000 copies or so of linux under VMWare on FreeBSD :-)
>
>Once we fix the deadlocks, that is.
We don't need VMWare really, we
el code.. I only have one machine here.)
>
>
>On Fri, 31 Mar 2000, Poul-Henning Kamp wrote:
>> >run 4000 copies or so of linux under VMWare on FreeBSD :-)
>
>Unfortunatly you can only run one vmware at a time under BSD.
>
>> >
>> >Once we fix the d
at's just the way it is, and as far as I know it is the way
it will continue to be.
Get used to it.
--
Poul-Henning Kamp FreeBSD coreteam member
[EMAIL PROTECTED] "Real hackers run -current on their laptop."
FreeBSD -- It will take a long time before progres
http://phk.freebsd.dk/misc
I belive the patch is now fundamentally ready for commit, I'm running
it here myself, and the delta in kernel warnings have been analyzed
and deemed mostly harmless.
Some componenents are still not converted and use a cast from bio to
buf, prominently vinum an
In message <[EMAIL PROTECTED]>, Hellmuth Michaelis writes
:
>>From the keyboard of Poul-Henning Kamp:
>
>> We need to be frugal about the kernel stack, for a lot of reasons,
>> that's just the way it is, and as far as I know it is the way
>> it will cont
um/bio problem is atrocious timing.
Actually, it is the other way around, Greg finally started to look for
the bug in vinum in the middle of my commits.
How dare he do that ?
:-)
--
Poul-Henning Kamp FreeBSD coreteam member
[EMAIL PROTECTED] "Real hackers run -
right sensible to me, and I suggest you do
that.
--
Poul-Henning Kamp FreeBSD coreteam member
[EMAIL PROTECTED] "Real hackers run -current on their laptop."
FreeBSD -- It will take a long time before progress goes too far!
To Unsubscribe: send mail to [EMAIL
t least FreeBSDcon and indications seems to be that
it is actually a malloc/free gottcha in vinum.
I have nothing to do with that, apart from being releived that
we don't seem to have a random stack-smasher bug in the system.
Poul-Henning
--
Poul-Henning Kamp FreeBSD coreteam mem
correct. The problem you're talking about I blamed
>elsewhere, not specifically CAM. To quote from
>http://www.lemis.com/vinum/bugs.html:
OK, sorry, I havn't heard about it since FreeBSDcon and back then
CAM was in the spotlight.
--
Poul-Henning Kamp | UNIX since Zilog Ze
ther as a general tool or as a kernel targeted tool
under src/tools. And the faster the better :-)
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD coreteam member | BSD since 4.3-tahoe
Never attribute to malice what can adequately
I have a machine which isn't doing much right now, so I have decided
to set it up as an automatic "FreeBSD Build checker".
Once per day the machine cvsups, checks out a virgin source tree,
tries to build GENERIC, GENERIC98, LINT and world. If any of these
builds fail it will send a report like
e they would shrink to
zero if we annoyed people enough with them.
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD coreteam member | BSD since 4.3-tahoe
Never attribute to malice what can adequately be explained by incompetence.
To Unsu
In message <[EMAIL PROTECTED]>, Warner Losh writes:
>In message <[EMAIL PROTECTED]> Poul-Henning Kamp writes:
>: awi.o(.text+0x3b4): undefined reference to `memcmp'
>: awi.o(.text+0x3cf): undefined reference to `memset'
>
>What I want to know is why I d
..
It is to be left there to catch people who use functions which are
not in the kernel, but which gcc implements as built-ins :-)
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD coreteam member | BSD since 4.3-tahoe
Never attribu
;t build.
If it reports, it includes the errors which from the non-building
components and "New warnings in *" delta lists relative to the
previous report.
I've sorted the report so that the most interesting things are
at the top.
Other ideas welcome.
--
Poul-Henning Kamp
, and by sending it to -current
maybe a new junior hacker or two could be ferret out :-)
>Think a bit bigger-picture also; theoretically, we should have these
>reports for -current and the RELENG_3 and RELENG_4 branches. The
>machine-resources are available for it, we just haven't organiz
In message <[EMAIL PROTECTED]>, Nar
vi writes:
>The summary of summaries would roughly look like this:
>
> Subject: -current build report
>
> Success: world, generic
> Fail: lint
The First part of the email is a summary just like that.
--
Poul-H
n, we are talking about an email which is shorter than the
list of open PRs, and if people actually *DO* something about it
it will get shorter fast
The only reason it is a long report right now is that people are sloppy!
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED]
agreement here, and that was also what the core decision said:
only visible to processed run under the linuxolator.
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD coreteam member | BSD since 4.3-tahoe
Never attribute to malice what
ot be set by default.
>
>I saw the same kind of patches and my laptop has this w/o any problems
>for long time.
>I'd like to commit submitted patch 2 or 3 days later if no objections.
It would be nice to have some kind of understanding why the tsc is
better than the i8254 before
In message <[EMAIL PROTECTED]>, Alan Clegg writes:
>Out of the ether, Poul-Henning Kamp spewed forth the following bitstream:
>
>> >> I'd like to recommend the following patches. Adding the option
>> >> "CLK_USE_TSC_ANYWAY" allows my laptop to
nd{AOL mode}
Hmm, that sounds weird...
At what time does the message come relative to the mounting of the
root filesystem ? Before or after ?
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD coreteam member | BSD since 4.3-tahoe
In message <[EMAIL PROTECTED]>, Warner Losh writes:
>In message <[EMAIL PROTECTED]> Poul-Henning Kamp writes:
>: At what time does the message come relative to the mounting of the
>: root filesystem ? Before or after ?
>
>I get mine when nfs starts up.
Any chance yo
In message <[EMAIL PROTECTED]>, Warner Losh writes:
>In message <[EMAIL PROTECTED]> Poul-Henning Kamp writes:
>: In message <[EMAIL PROTECTED]>, Warner Losh writes:
>: >In message <[EMAIL PROTECTED]> Poul-Henning Kamp writes:
>: >: At what time does th
was in the
>stream --nope. pulled a 'glimpse' of 'current' list but
>found no reference.
This file is generated on the fly in the compile directory
I belive.
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
Fr
===> bin/csh/nls
cd /usr/src/bin/csh/nls ; make afterdistribute DESTDIR=/R/stage/trees/bin
===> bin/csh/nls/finnish
make: don't know how to make distribute. Stop
*** Error code 2
Stop in /usr/src/bin/csh/nls.
*** Error code 1
--
Poul-Henning Kamp | UNIX since Zilog Zeus
lease/../usr/share/nls/fi_FI.ISO_8859-1/tcsh.cat: No such file or
directory
*** Error code 71
Stop in /syv/src/bin/csh/nls/finnish.
*** Error code 1
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD coreteam member | BSD since 4.3
AHsAOLO0GwMG7gAAAeUAAAOMrBACAbyrx8nrVwMFvKvHyerb
>Ddi8q8fJ61cDBbyryAnpCUiuiUkBOT32DQBaWgDgsFVWAwBgl6o62wgARRAATOnG
>AABAETSnrBACAawQAgIAewB7ADhA+hwCBuwAAAAC8X9/AQG8q8fiS0k4WLyryAnpCUiu
>vKvICeoOMES8q8gJ6iDujbpJATntswsASgAAAEoA4LBVVgMAYJeqOtsIAEUQADzpx0AA
>QAa65awQAgHM
:
>> crw-r- 1 root operator 13, 0x00020001 Dec 12 21:09 /dev/da0s1b
>> crw-r- 1 root operator 13, 0x00020001 Dec 12 21:09 /dev/rda0s1b
>>
>> Regards
>> Dirk
>
>--
>Brian <[EMAIL PROTECTED]>
> <http://www.Aw
an towards a sysctl which prevents bdevs
from being opened starting 2000-06-01.
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD coreteam member | BSD since 4.3-tahoe
Never attribute to malice what can adequately be explained by incomp
t enough to justify an immediate
MFC.
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD coreteam member | BSD since 4.3-tahoe
Never attribute to malice what can adequately be explained by incompetence.
To Unsubscribe: send mail to
st the way it is Matt. Get used to it.
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD coreteam member | BSD since 4.3-tahoe
Never attribute to malice what can adequately be explained by incompetence.
To Unsubscribe: send mail
qualify for immediate MFC status unless
the security officer says so.
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD coreteam member | BSD since 4.3-tahoe
Never attribute to malice what can adequately be explained by incompe
an immediate MFC in this patch. Please
allow the normal waiting period to elapse before you MFC.
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD coreteam member | BSD since 4.3-tahoe
Never attribute to malice what can adequatel
Matt,
I will say it this last time:
Your patch does not qualify for immediate MFC.
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD coreteam member | BSD since 4.3-tahoe
Never attribute to malice what can adequately
you are talking about for 4.x/5.x.
4.x-stable is a -stable tree and shall be treated as such.
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD coreteam member | BSD since 4.3-tahoe
Never attribute to malice what can adequately
===
SUMMARY
===
World
compiled
637 Warnings
45 Errors
Kernel LINT
compiled
149 Warnings
0 Errors
Kernel GENERIC
compiled
59 Warnings
0 Errors
Kernel GENERIC98
In message <[EMAIL PROTECTED]>, Andrzej Bialecki
writes:
>On Tue, 25 Apr 2000, Poul-Henning Kamp wrote:
>
>>
>> ===
>> SUMMARY
>> ===
>
>[27kB long list of errors deleted..]
>
>I th
iled
>> 149 Warnings
>> 0 Errors
>> Kernel GENERIC
>> compiled
>> 59 Warnings
>> 0 Errors
>> Kernel GENERIC98
>> ***didn't compile***
>> 54 Warnings
>> 0 Errors
>
>This doesn't lo
New patch at: http://phk.freebsd.dk/misc/sys_kernel_h.patch
This patch removes 67 unneeded instances of #include
Comments, tests and reviews please.
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD coreteam member | BSD since
In message <[EMAIL PROTECTED]>, Greg Lehey writes:
>On Wednesday, 26 April 2000 at 11:50:11 +0200, Poul-Henning Kamp wrote:
>>
>> New patch at: http://phk.freebsd.dk/misc/sys_kernel_h.patch
>>
>> This patch removes 67 unneeded instances of #include
>>
Removes 43 unneeded #include includes.
Comments, tests and reviews please
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD coreteam member | BSD since 4.3-tahoe
Never attribute to malice what can adequately be explained by
1001 - 1100 of 1468 matches
Mail list logo
