Kernel Rebuild for DVD burner not good. FreeBSD

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

ASKER

I am feeling a little confused.

KV_BSD# cd /usr/src/sys/i386
KV_BSD# ls
Makefile compile i386 isa svr4
acpica conf ibcs2 linux xbox
bios cpufreq include pci
KV_BSD# cd conf
KV_BSD# ls
.cvsignore GENERIC.hints Makefile RUM_KERN
DEFAULTS KAYVE_KERN NOTES XBOX
GENERIC MAC PAE
KV_BSD# cat GENERIC | grep ndis
KV_BSD# cat GENERIC | grep NDIS
KV_BSD#

ASKER

is NOTES my clue?

# Disable the 4 MByte page PSE CPU feature. The PSE feature allows the
KV_BSD# tail -60 NOTES | head -10

# Enable NDIS binary driver support
options NDISAPI
device ndis

#####################################################################
# VM OPTIONS

# Disable the 4 MByte page PSE CPU feature. The PSE feature allows the
KV_BSD# pwd
/usr/src/sys/i386/conf
KV_BSD#

ASKER

I'm sorry for my stupidity

SOLUTION

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

ASKER

I don't understand how to override don't include ndis as you describe.

SOLUTION

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

ASKER

http://www.iosn.net/Members/kaeru/articles/freebsd/x40

Do I put

ndis_load="NO"
if_ndis_load="NO"

Into /boot/loader.conf?

SOLUTION

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

ASKER

I see no reason why ndis is there and therefore do not understand what you are talking about

KAYVE_KERN: 9 lines, 102 characters.
KV_BSD# pwd
/usr/src/sys/i386/conf
KV_BSD# cate KAYVE_KERN
zsh: command not found: cate
KV_BSD# cat KAYVE_KERN
include GENERIC

ident KAYVEY
nocpu I486_CPU
nocpu I586_CPU

options SMP
device atapicam
nodevice acd
KV_BSD#

I see that it IS there by the make. I have no idea where or why ndis is there I didn't do it so
therefore I have no idea how to take it out.

SOLUTION

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

ASKER

I was going to ask why that should work, but I guess I can classify it under "reboot."

It seems there are no errors now. I don't have any blank disks with me. I will get to that later and
let you know.
makesplat2.log

SOLUTION

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

ASKER CERTIFIED SOLUTION

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

ASKER

Which directory is the "build directory?" I think I have it right. I did "pwd" in "makesplat2.log"

ASKER

_replay.o zfs_rlock.o zfs_vfsops.o zfs_vnops.o zvol.o vdev_geom.o zfs.ko.debug zfs.ko.symbols vnode_if.h vnode_if_newproto.h vnode_if_typedef.h
===> zlib (clean)
rm -f export_syms zlib.ko zlib.kld zlib.o zlib.ko.debug zlib.ko.symbols
===> zyd (clean)
rm -f export_syms if_zyd.ko if_zyd.kld if_zyd.o if_zyd.ko.debug if_zyd.ko.symbols opt_usb.h bus_if.h device_if.h usbdevs.h
KV_BSD# exit

Script done, output file is makesplat2.log
KV_BSD# pwd
/usr/src/sys/i386/compile/KAYVE_KERN
KV_BSD#

ASKER

Okay I am in the process of trying out cubeeg's PATH specific directives

-f .newdep
make -V CFILES -V SYSTEM_CFILES -V GEN_CFILES | MKDEP_CPP="cc -E" CC="cc" xargs mkdep -a -f .newdep -O -pipe -std=c99 -g -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -nostdinc -I. -I/usr/src/sys -I/usr/src/sys/contrib/altq -I/usr/src/sys/contrib/ipfilter -I/usr/src/sys/contrib/pf -I/usr/src/sys/dev/ath -I/usr/src/sys/contrib/ngatm -I/usr/src/sys/dev/twa -I/usr/src/sys/gnu/fs/xfs/FreeBSD -I/usr/src/sys/gnu/fs/xfs/FreeBSD/support -I/usr/src/sys/gnu/fs/xfs -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -m

SOLUTION

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

SOLUTION

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

ASKER

oops

sr/src/sys/modules/if_ndis/../../dev/if_ndis/if_ndis.c:3469: error: (Each undeclared identifier is reported only once
/usr/src/sys/modules/if_ndis/../../dev/if_ndis/if_ndis.c:3469: error: for each function it appears in.)
*** Error code 1

Stop in /usr/src/sys/modules/if_ndis.
*** Error code 1

Stop in /usr/src/sys/modules.
*** Error code 1

Stop in /usr/obj/usr/src/sys/KAYVE_KERN.
*** Error code 1

Stop in /usr/src.
*** Error code 1

Stop in /usr/src.
KV_BSD# exit

Script done, output file is makesplat.log
KV_BSD#

Script done, output file is makesplat.log
KV_BSD# pwd
/usr/src
KV_BSD#

makesplat.log

ASKER

Oh this?

/usr/src
KV_BSD# man config
CONFIG(8) FreeBSD System Manager's Manual CONFIG(8)

NAME
config -- build system configuration files

SYNOPSIS
config [-CVgp] [-d destdir] SYSTEM_NAME
config [-x kernel]

DESCRIPTION
The config utility builds a set of system configuration files from the
file SYSTEM_NAME which describes the system to configure. A second file
tells config what files are needed to generate a system and can be aug-
mented by configuration specific set of files that give alternate files
for a specific machine (see the FILES section below).

Available options and operands:

-V Print the config version number.

-C If the INCLUDE_CONFIG_FILE is present in a configuration
file, kernel image will contain full configuration files
included literally (preserving comments). This flag is kept
for backward compatibility.

-d destdir Use destdir as the output directory, instead of the default
one. Note that config does not append SYSTEM_NAME to the
directory given.

-g Configure a system for debugging.

-x kernel Print kernel configuration file embedded into a kernel file.
This option makes sense only if options INCLUDE_CONFIG_FILE
entry was present in your configuration file.

-p Configure a system for profiling; for example, kgmon(8) and
gprof(1). If two or more -p options are supplied, config
configures a system for high resolution profiling.

SYSTEM_NAME Specify the name of the system configuration file containing
device specifications, configuration options and other sys-
tem parameters for one system configuration.

The config utility should be run from the conf subdirectory of the system
source (usually /sys/ARCH/conf), where ARCH represents one of the archi-
tectures supported by FreeBSD. The config utility creates the directory
../compile/SYSTEM_NAME or the one given with the -d option as necessary
and places all output files there. The output of config consists of a
number of files; for the i386, they are: Makefile, used by make(1) in
building the system; header files, definitions of the number of various
devices that will be compiled into the system.

After running config, it is necessary to run ``make depend'' in the
directory where the new makefile was created. The config utility prints
a reminder of this when it completes.

If any other error messages are produced by config, the problems in the
configuration file should be corrected and config should be run again.
Attempts to compile a system that had configuration errors are likely to
fail.

DEBUG KERNELS
Traditional BSD kernels are compiled without symbols due to the heavy
load on the system when compiling a ``debug'' kernel. A debug kernel
contains complete symbols for all the source files, and enables an expe-
rienced kernel programmer to analyse the cause of a problem. The debug-
gers available prior to 4.4BSD-Lite were able to find some information
from a normal kernel; gdb(1) provides very little support for normal ker-
nels, and a debug kernel is needed for any meaningful analysis.

For reasons of history, time and space, building a debug kernel is not
the default with FreeBSD: a debug kernel takes up to 30% longer to build
and requires about 30 MB of disk storage in the build directory, compared
to about 6 MB for a non-debug kernel. A debug kernel is about 11 MB in
size, compared to about 2 MB for a non-debug kernel. This space is used
both in the root file system and at run time in memory. Use the -g
option to build a debug kernel. With this option, config causes two ker-
nel files to be built in the kernel build directory:

o kernel.debug is the complete debug kernel.

o kernel is a copy of the kernel with the debug symbols stripped off.
This is equivalent to the normal non-debug kernel.

There is currently little sense in installing and booting from a debug
kernel, since the only tools available which use the symbols do not run
on-line. There are therefore two options for installing a debug kernel:

o ``make install'' installs kernel in the root file system.

o ``make install.debug'' installs kernel.debug in the root file system.

FILES
/sys/conf/files list of common files system is built from
/sys/conf/Makefile.ARCH generic makefile for the ARCH
/sys/conf/files.ARCH list of ARCH specific files
/sys/ARCH/compile/SYSTEM_NAME default kernel build directory for system
SYSTEM_NAME on ARCH.

SEE ALSO
config(5)

The SYNOPSIS portion of each device in section 4.

Building 4.3 BSD UNIX System with Config.

HISTORY
The config utility appeared in 4.1BSD.

Before support for -x was introduced, options INCLUDE_CONFIG_FILE
included entire configuration file that used to be embedded in the new
kernel. This meant that strings(1) could be used to extract it from a
kernel: to extract the configuration information, you had to use the com-
mand:

strings -n 3 kernel | sed -n 's/^___//p'

BUGS
The line numbers reported in error messages are usually off by one.

FreeBSD 7.0 May 8, 2007 FreeBSD 7.0
KV_BSD#

ASKER

Howcome it says BSD 4.3? I thought it was BSD 4.4

ASKER

So you told me wrong?

729 COMMON ITEMS:
730
731 General Notes
732 -------------
733 Avoid using make -j when upgrading. From time to time in the
734 past there have been problems using -j with buildworld and/or
735 installworld. This is especially true when upgrading between
736 "distant" versions (eg one that cross a major release boundary
737 or several minor releases, or when several months have passed
738 on the -current branch).
739
740 Sometimes, obscure build problems are the result of environment
741 poisoning. This can happen because the make utility reads its
742 environment when searching for values for global variables.
743 To run your build attempts in an "environmental clean room",
744 prefix all make commands with 'env -i '. See the env(1) manual
745 page for more details.
746
747 When upgrading from one major version to another it is generally
748 best to upgrade to the latest code in the currently installed branch
749 first, then do an upgrade to the new branch. This is the best-tested
750 upgrade path, and has the highest probability of being successful.
751 Please try this approach before reporting problems with a major
752 version upgrade.
753
754 To build a kernel
755 -----------------
756 If you are updating from a prior version of FreeBSD (even one just
757 a few days old), you should follow this procedure. It is the most
758 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
759
760 make kernel-toolchain
761 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
762 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
763
764 To test a kernel once
765 ---------------------
766 If you just want to boot a kernel once (because you are not sure
767 if it works, or if you want to boot a known bad kernel to provide
768 debugging information) run
769 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
770 nextboot -k testkernel
772 To just build a kernel when you know that it won't mess you up
773 --------------------------------------------------------------
774 This assumes you are already running a 5.X system. Replace
775 ${arch} with the architecture of your machine (e.g. "i386",
776 "alpha", "amd64", "ia64", "pc98", "sparc64", etc).
777
778 cd src/sys/${arch}/conf
779 config KERNEL_NAME_HERE
780 cd ../compile/KERNEL_NAME_HERE
781 make depend
782 make
783 make install
784
785 If this fails, go to the "To build a kernel" section.
786

ASKER

ACPI FAILURE AGAIN!!!

n.o acpi_isab.o acpi_package.o acpi_pci.o acpi_pcib.o acpi_pcib_acpi.o acpi_pcib_pci.o acpi_powerres.o acpi_quirk.o acpi_resource.o acpi_timer.o acpi_pci_link.o acpi_thermal.o acpi_acad.o acpi_battery.o acpi_cmbat.o acpi_cpu.o acpi_ec.o acpi_hpet.o acpi_lid.o acpi_perf.o acpi_smbat.o acpi_throttle.o OsdDebug.o OsdHardware.o OsdInterrupt.o OsdMemory.o OsdSchedule.o OsdStream.o OsdSynch.o OsdTable.o OsdEnvironment.o acpi_machdep.o acpi_wakeup.o madt.o assym.o
assym.o: file not recognized: File format not recognized
*** Error code 1

Stop in /usr/src/sys/modules/acpi/acpi.
*** Error code 1

Stop in /usr/src/sys/modules/acpi.
*** Error code 1

Stop in /usr/src/sys/modules.
*** Error code 1

Stop in /usr/src/sys/i386/compile/KAYVE_KERN.
KV_BSD#

kernelsplat.log

ASKER

WHAT's WRONG WITH DMESG????
Script done, output file is kernelsplat.log
KV_BSD# pwd
/home/kayve
KV_BSD# dmesg | grep acpi
KV_BSD# dmesg | grep ACPI
KV_BSD# dmesg
KV_BSD#

Script done, output file is kernelsplat.log
KV_BSD# pwd
/home/kayve
KV_BSD# dmesg | grep acpi
KV_BSD# dmesg | grep ACPI
KV_BSD# dmesg
KV_BSD# cd /var
KV_BSD# ls
.snap            cache            games            lost+found      run
account            crash            gdm            mail            rwho
at            cron            heimdal            msgs            spool
audit            db            lib            named            tmp
backups            empty            log            preserve      yp
KV_BSD# ls spool
clientmqueue      lock            mqueue            output
cups            lpd            opielocks
KV_BSD# ls audit
KV_BSD# ls msgs
bounds
KV_BSD# ls msgs/bounds
msgs/bounds
KV_BSD# ls -l msgs
total 2
-rw-r--r-- 1 root wheel 4 Mar 16 03:01 bounds
KV_BSD# ls -l cache
total 4
drwxr-xr-x 3 root cups 512 Oct 25 19:22 cups
drwxr-xr-x 2 haldaemon haldaemon 512 Nov 8 07:34 hald
KV_BSD# ls -l crash
total 562686
-rw-r--r-- 1 root wheel 2 Nov 25 17:58 bounds
-rw------- 1 root wheel 436 Nov 15 15:44 info.0
-rw------- 1 root wheel 434 Nov 15 16:11 info.1
-rw------- 1 root wheel 434 Nov 15 16:43 info.2
-rw------- 1 root wheel 436 Nov 25 14:37 info.3
-rw------- 1 root wheel 436 Nov 25 17:58 info.4
-rw-r--r-- 1 root wheel 5 Feb 24 2008 minfree
-rw------- 1 root wheel 147120128 Nov 15 15:44 vmcore.0
-rw------- 1 root wheel 93601792 Nov 15 16:11 vmcore.1
-rw------- 1 root wheel 96358400 Nov 15 16:43 vmcore.2
-rw------- 1 root wheel 131399680 Nov 25 14:37 vmcore.3
-rw------- 1 root wheel 125730816 Nov 25 17:58 vmcore.4
KV_BSD#

KV_BSD# ls -l crash
total 562686
-rw-r--r-- 1 root wheel 2 Nov 25 17:58 bounds
-rw------- 1 root wheel 436 Nov 15 15:44 info.0
-rw------- 1 root wheel 434 Nov 15 16:11 info.1
-rw------- 1 root wheel 434 Nov 15 16:43 info.2
-rw------- 1 root wheel 436 Nov 25 14:37 info.3
-rw------- 1 root wheel 436 Nov 25 17:58 info.4
-rw-r--r-- 1 root wheel 5 Feb 24 2008 minfree
-rw------- 1 root wheel 147120128 Nov 15 15:44 vmcore.0
-rw------- 1 root wheel 93601792 Nov 15 16:11 vmcore.1
-rw------- 1 root wheel 96358400 Nov 15 16:43 vmcore.2
-rw------- 1 root wheel 131399680 Nov 25 14:37 vmcore.3
-rw------- 1 root wheel 125730816 Nov 25 17:58 vmcore.4
KV_BSD# cat /var/crash/info.4
Dump header from device /dev/ad0s2b
Architecture: i386
Architecture Version: 2
Dump Length: 125730816B (119 MB)
Blocksize: 512
Dumptime: Tue Nov 25 15:04:59 2008
Hostname: KV_BSD
Magic: FreeBSD Kernel Dump
Version String: FreeBSD 7.0-RELEASE #0: Sun Feb 24 19:59:52 UTC 2008
root@logan.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC
Panic String: page fault
Dump Parity: 2871993455
Bounds: 4
Dump Status: good
KV_BSD# cat /var/crash/info.0
Dump header from device /dev/ad0s2b
Architecture: i386
Architecture Version: 2
Dump Length: 147120128B (140 MB)
Blocksize: 512
Dumptime: Sat Nov 15 15:43:14 2008
Hostname: KV_BSD
Magic: FreeBSD Kernel Dump
Version String: FreeBSD 7.0-RELEASE #0: Sun Feb 24 19:59:52 UTC 2008
root@logan.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC
Panic String: page fault
Dump Parity: 2727718240
Bounds: 0
Dump Status: good
KV_BSD# cat /var/crash/info.1
Dump header from device /dev/ad0s2b
Architecture: i386
Architecture Version: 2
Dump Length: 93601792B (89 MB)
Blocksize: 512
Dumptime: Sat Nov 15 16:09:21 2008
Hostname: KV_BSD
Magic: FreeBSD Kernel Dump
Version String: FreeBSD 7.0-RELEASE #0: Sun Feb 24 19:59:52 UTC 2008
root@logan.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC
Panic String: page fault
Dump Parity: 2165308781
Bounds: 1
Dump Status: good
KV_BSD# cat /var/crash/info.2
Dump header from device /dev/ad0s2b
Architecture: i386
Architecture Version: 2
Dump Length: 96358400B (91 MB)
Blocksize: 512
Dumptime: Sat Nov 15 16:41:50 2008
Hostname: KV_BSD
Magic: FreeBSD Kernel Dump
Version String: FreeBSD 7.0-RELEASE #0: Sun Feb 24 19:59:52 UTC 2008
root@logan.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC
Panic String: page fault
Dump Parity: 2115491693
Bounds: 2
Dump Status: good
KV_BSD# cat /var/crash/info.3
Dump header from device /dev/ad0s2b
Architecture: i386
Architecture Version: 2
Dump Length: 131399680B (125 MB)
Blocksize: 512
Dumptime: Tue Nov 25 14:17:08 2008
Hostname: KV_BSD
Magic: FreeBSD Kernel Dump
Version String: FreeBSD 7.0-RELEASE #0: Sun Feb 24 19:59:52 UTC 2008
root@logan.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC
Panic String: page fault
Dump Parity: 1414696815
Bounds: 3
Dump Status: good
KV_BSD#

SOLUTION

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

SOLUTION

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

ASKER

This is a different disk. I have three disks. Why do you have to be such an ambiguous abusive *@#&, gheist? You give arcane instructions and get angry when I don't understand them.

Right now I have a little disaster. I was only able to complete one of cubeeg's clearly stated, perfect
syntax commands that doesn't assume I can read your mind or have some minutia knowledge that one
allegedly gains from reading the handbook three times. I have 2 books on FreeBSD administration,
I read the one completely and have had time to get half through the other. You get mad at me because
I try to follow instructions that you give that are incomplete, and I don't have time to spend hours trying
to google things that I don't even know what to google.

The puter took forever to boot up (it is old HW, the same laptop frame but I have the newest HD
that is not a dual boot I think. Right now my guess is that I better do the second step suggested by
cubeeg, namely make installkernel..

preempting gheist's abusive prejudiced nonsense, I think my FreeBSD 7.0 has been working pretty
well. I haven't bothered figuring out how to get sound working again, I can't run flash, but I can run
browsers and terminals and that it fine for my purposes. gcc also works fine and easy and I have
a nice command line that is familiar to me that I have been using such similar commandlines since 1985.
Right now the situation is that gnome is coming up very slow but I cannot multitask. It came up with
desktop icons at first, and I clicked "start terminal" and "start screenshot" and "start epiphany" many times but right now I have a terminal I have su-ed so I will do make installkernel and reboot and see
what happens. The desktop icons have disappeared, but I can see the green grass background and
the toolbar thing at the bottom. Instead of having a destop menu system "applications.. etc" it has been
replaced with the terminal menus "file..etc"

ASKER

I have uploaded a number of my "abusive activities" on this free photoserver that predates the dot
com crash run by a friend from my "crashing class at Berzerkeley" days when I put computer science
aside and went for molecular biology

http://www.monkeyview.net/id/965/fsck/index.vhtml

You can see my laptop model numbers

http://www.monkeyview.net/id/965/fsck/dmesg/index.vhtml

Here is the best closeup

http://www.monkeyview.net/id/965/fsck/dmesg/PB12001901.vhtml

Here I am buying one new hard drive:

http://www.monkeyview.net/id/965/fsck/newhd/index.vhtml

More RAM I think

http://www.monkeyview.net/id/965/fsck/inst_world/p5240179.0.jpg

a hub
http://www.monkeyview.net/id/965/fsck/hub/index.vhtml

The older enclusure working

one of the hardrives label:

http://www.monkeyview.net/id/965/fsck/jumpers/PC170027.vhtml

I have one HD that has 60GB I think.. that is the one that makes clunky sounds but
still runs. It has a dead MS Vista partition and is running FreeBSD 6.2 I think. I have
another that has 120GB and a third that has 160GB I think it is.

Here is a picture of two of my hard drives:

http://www.monkeyview.net/id/965/fsck/torrent/p5120213.vhtml

Each time I got a new hard drive, I got a new "enclosure" Here is my second enclosure's box:

http://www.monkeyview.net/id/965/fsck/torrent/p5120215.vhtml

This set of pictures was when I bought the second hard drive I think

http://www.monkeyview.net/id/965/fsck/torrent/index.vhtml

http://www.monkeyview.net/id/965/fsck/hub/p1230121.vhtml

ASKER

For better or for worse, I have got a terminal, and have run the commmand in /usr/src :

make installkernel KERNCONF=KAYVE_KERN

Now the terminal window went away, replaced by a screenshot. I must roll my rollychair over
there away from this windoze machine and kill that. Maybe I should make a new screenshot.

ASKER

okay. now I am running the clunky hard drive
clunky.png
crazy.png
crazy2.png

ASKER

too bad I couldn't capture all the crazy things.

ASKER

I forgot to post my 37 photos of me swapping my hard drives just nowto show you what is happening

http://www.monkeyview.net/id/965/fsck/swap/index.vhtml

monkeyview.net is a free photo server.

ASKER

Now I can access files I made during "the crazyness" of the green grass that I am not running now. Now
I am running old clunky hard drive

# ls /mnt/nexstar/src/sys
ls: /mnt/nexstar/src/sys: Device not configured
# ls /mnt/usr
# uname -a
FreeBSD 6.2-RELEASE FreeBSD 6.2-RELEASE #0: Fri Jan 12 11:05:30 UTC 2007 root@dessler.cse.buffalo.edu:/usr/obj/usr/src/sys/SMP i386
#

makeinstallkernel.log

ASKER

# df
Filesystem 1K-blocks Used Avail Capacity Mounted on
/dev/ad0s2a 297326 76288 197252 28% /
devfs 1 1 0 100% /dev
/dev/ad0s2e 396526 13610 351194 4% /tmp
/dev/ad0s2f 13570958 11503562 981720 92% /usr
/dev/ad0s2d 396526 30056 334748 8% /var
/dev/da1s2f 34401278 22354482 9294694 71% /mnt/nexstar
#

# df -g
Filesystem 1G-blocks Used Avail Capacity Mounted on
/dev/ad0s2a 0 0 0 28% /
devfs 0 0 0 100% /dev
/dev/ad0s2e 0 0 0 4% /tmp
/dev/ad0s2f 12 10 0 92% /usr
/dev/ad0s2d 0 0 0 8% /var
/dev/da1s2f 32 21 8 71% /mnt/nexstar
# df- m
df-: not found
# df -m
Filesystem 1M-blocks Used Avail Capacity Mounted on
/dev/ad0s2a 290 74 192 28% /
devfs 0 0 0 100% /dev
/dev/ad0s2e 387 13 342 4% /tmp
/dev/ad0s2f 13252 11233 958 92% /usr
/dev/ad0s2d 387 29 326 8% /var
/dev/da1s2f 33594 21830 9076 71% /mnt/nexstar
#

SOLUTION

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.