Sponsored Content
Full Discussion: netbsd
Operating Systems BSD netbsd Post 302147887 by porter on Thursday 29th of November 2007 12:46:12 AM
Old 11-29-2007
Standard is to put

xdm=YES

in /etc/rc.conf
 

8 More Discussions You Might Find Interesting

1. UNIX Desktop Questions & Answers

NetBSD Troubles

HI, I just installed NetBSD i386 v. latest. I am having a few problems: For some reason X just won't start!? Another is I can't access My CDROM or Floppy. Thanks in advance! (3 Replies)
Discussion started by: vertigo
3 Replies

2. UNIX Desktop Questions & Answers

Starting X in NetBSD

Hi I have NetBSD and i am having a trouble Starting X. It keeps asking me for the config file and I run the text confing file but it messes up. I really want to be able to run the Graphical Setup. I read about the Graphical setup from a book but they didn't tell how to start it. help please!? (9 Replies)
Discussion started by: vertigo
9 Replies

3. UNIX for Dummies Questions & Answers

bash in netbsd

i recently downloaded and installed bash on my netbsd box (1.5.2) and set my shell and my root shell using user mod to change the shell, command executed under root. bash is installed from my user home directory (home/joe) and i moved the bash executable to /bin/ and everything is fine, except i... (6 Replies)
Discussion started by: norsk hedensk
6 Replies

4. BSD

NetBSD Ports

They put NetBSD on a Dreamcast. Thats just awesome. What can't they put it on!? (1 Reply)
Discussion started by: Phobos
1 Replies

5. BSD

Anyone using NetBSD pkgsrc on FreeBSD?

I confess, I'm getting a hair frustrated with the FreeBSD ports system. Is there a reasonably headache-free way of migrating all my installed apps to pkgsrc? Is it advisable or not? Or should I just change my systems over to NetBSD? Or stop worrying an learn to love FBSD ports? (0 Replies)
Discussion started by: criglerj
0 Replies

6. UNIX for Dummies Questions & Answers

netbsd

which better freebsd and netbsd for server unix (0 Replies)
Discussion started by: salehudinayubi
0 Replies

7. Virtualization and Cloud Computing

NetBSD on VirtualBox

Hello, guys! I use Ubuntu 9.04 as desktop operating system and I want to make some tests on NetBSD. I tried to install as a virtual sistem on VirtualBox but it doesn't want to install. You can see the error in the attached file. Do you guys have any clue about what the problem could be? (3 Replies)
Discussion started by: Sergiu-IT
3 Replies

8. BSD

NetBSD on OLD laptop

I want to install NetBSD on the Compaq LTE 5000. ("Of course it runs NetBSD!!") But the laptop does NOT have a CD-ROM drive. How can I solve?? Thanks for any reply! :) PS: I hope i'm posting in the right item... (2 Replies)
Discussion started by: mghis
2 Replies
SAVECORE(8)						    BSD System Manager's Manual 					       SAVECORE(8)

NAME
savecore -- save a core dump of the operating system SYNOPSIS
savecore [-fvz] [-N system] [-Z level] [directory] savecore -c [-v] [-N system] savecore -n [-v] [-N system] DESCRIPTION
When the NetBSD kernel encounters a fatal error, the panic(9) routine arranges for a snapshot of the contents of physical memory to be writ- ten into a dump area, typically in the swap partition. Upon a subsequent reboot, savecore is typically run out of rc(8), before swapping is enabled, to copy the kernel and the saved memory image into directory, and enters a reboot message and information about the core dump into the system log. If a directory is not specified, then /var/crash is used. The kernel and core file can then be analyzed using various tools, including crash(8), dmesg(8), fstat(1), gdb(1), iostat(8), netstat(1), ps(1), and pstat(8), to attempt to deduce the cause of the crash. Crashes are usually the result of hardware faults or kernel bugs. If a kernel bug is suspected, a full bug report should be filed at http://www.netbsd.org/, or using send-pr(1), containing as much information as possible about the circumstances of the crash. Since crash dumps are typically very large and may contain whatever (potentially confidential) information was in memory at the time of the crash, do NOT include a copy of the crash dump file in the bug report; instead, save it somewhere in the event that a NetBSD developer wants to examine it. The options are as follows: -c Only clears the dump without saving it, so that future invocations of savecore will ignore it. -f Forces a dump to be taken even if the dump doesn't appear correct or there is insufficient disk space. -n Check whether a dump is present without taking further action. The command exits with zero status if a dump is present, or with non-zero status otherwise. -N Use system as the kernel instead of the default (returned by getbootfile(3)). Note that getbootfile(3) uses secure_path(3) to check that kernel file is ``secure'' and will default to /netbsd if the check fails. -v Prints out some additional debugging information. -z Compresses the core dump and kernel (see gzip(1)). -Z level Set the compression level for -z to level. Defaults to 1 (the fastest compression mode). Refer to gzip(1) for more information regarding the compression level. savecore checks the core dump in various ways to make sure that it is current and that it corresponds to the currently running system. If it passes these checks, it saves the core image in directory/netbsd.#.core and the system in directory/netbsd.# (or in directory/netbsd.#.core.gz and directory/netbsd.#.gz, respectively, if the -z option is used). The ``#'' is the number from the first line of the file directory/bounds, and it is incremented and stored back into the file each time savecore successfully runs. savecore also checks the available disk space before attempting to make the copies. If there is insufficient disk space in the file system containing directory, or if the file directory/minfree exists and the number of free kilobytes (for non-superusers) in the file system after the copies were made would be less than the number in the first line of this file, the copies are not attempted. If savecore successfully copies the kernel and the core dump, the core dump is cleared so that future invocations of savecore will ignore it. SEE ALSO
fstat(1), gdb(1), gzip(1), netstat(1), ps(1), send-pr(1), crash(8), dmesg(8), iostat(8), pstat(8), rc(8), syslogd(8), panic(9) HISTORY
The savecore command appeared in 4.1BSD. BUGS
The minfree code does not consider the effect of compression. BSD
September 13, 2011 BSD
All times are GMT -4. The time now is 09:28 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy