Michael Grant <[EMAIL PROTECTED]> wrote:
> # mdconfig -l -u md0
> md0 vnode 23503425 KBytes
-current has support for showing the file name:
# mdconfig -lu0
md0 vnode 3.0M /home/dima/test
I don't know when this will be MFC'd.
> Furthermore, could we have that info when we run
t get installed. Is
> this intentional?
> I only looked in /usr/bin and /usr/sbin, is it someplace else? No
> manpage for it either.
It's in /usr/libexec (well, at least it is on -current, and this is an MFC..).
--
Dima Dorfman <[EMAIL PROTECTED]>
Finger [EMAIL PROTECTED] for
tarted), I'd say you are quite incapable
of piping flames (which this message is not) to /dev/null. No
pun/offense/whatever intended. I'm just expressing my opinion.
Regards
Dima Dorfman
mentions that the -q option is accepted by usernext and groupnext
(not related to this problem; just thought I'd stick it there
while I'm doing this).
If you would, please try it out (at least the core dump remedy) and
see if it solves the problem.
Thanks
some point.
I've submitted a PR (25537) to get something like that added to
sysinstall's help system (pressing "F1"), but noone's looked at it yet
:-/. It answers this question and possibly many others that have come
up in the last few weeks.
x27;t help. Also, I can't reproduce this problem. Does it happen
every time? On all filesystems? On all (most?) hosts? How big are
the filesystems? Anything else you could tell me to help me reproduce
this? I'll gladly help in fixing it if I can recreate it.
Thanks
uld you please
try the patch in PR bin/26507 and let me know if it helps? I've also
attached it for your convenience.
Thanks,
Dima Dorfman
[EMAIL PRO
Rob Simmons <[EMAIL PROTECTED]> writes:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: RIPEMD160
>
> I noticed this message on all of the ide based FreeBSD boxen after the
> first time I did a make world etc:
>
> no devsw (majdev=0 bootdev=0xa020)
>
> - From what I've been reading in the arch
Jordan Hubbard <[EMAIL PROTECTED]> writes:
> 10 days ago, Andrey broke the handbook builds in -stable [...]
The *Handbook* build? Or did you mean the release notes?
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-stable" in the body of the message
Paul <[EMAIL PROTECTED]> writes:
> Is anyone else experiencing this problem? On two separate machines now,
> cvsup'd to -STABLE, I get the following error when trying to compile.
> Doesn't matter if it's GENERIC, or my customer kernel... i get the same
> thing either way:
Have you done a bui
Steve Price <[EMAIL PROTECTED]> writes:
> Anyone have any suggestions for what the most probable causes of
> the following panic are?
>
> panic: NMI indicates hardware failure
It's obvious that something is generating an NMI when it shouldn't.
There's a sysctl, machdep.panic_on_nmi, that control
Robert <[EMAIL PROTECTED]> writes:
> What is up with "cron" not working?
>
> I cvsup'd last night and its still br0ke.
It works fine unless you don't specify a username in /etc/crontab.
It's a bug that it crashes instead of civilly reporting the error, but
it has never and will never do what y
CSI disks. Also, while this shouldn't touch the actual data
on your disk, I strongly recommend you have a backup; just in case.
Hope this helps
--
Dima Dorfman <[EMAIL PROTECTED]>
Finger [EMAIL PROTECTED] for my public PGP key.
If only God would give me some clear sign! Like making
13 matches
Mail list logo
