I have two questions related to the syncer process that replaces the old
update process:
(1) The syncer process is waken up once a second (it sleeps on lbolt). If
I have more than 30 mounted filesystems, then each filesystem's dirty data
will stay more than 30 seconds. If I only have a couple
On Wed, 19 Apr 2000, Matthew Dillon wrote:
:
:I have two questions related to the syncer process that replaces the old
:update process:
:
:(1) The syncer process is waken up once a second (it sleeps on lbolt). If
:I have more than 30 mounted filesystems, then each filesystem's dirty data
On Sat, 15 Apr 2000, Zhihui Zhang wrote:
I have two unrelated questions I can not figure out myself:
(1) Does FreeBSD NFS implementation support "noac" to disable attribute
cache? I know this is not good for performance.
It seems to me that FreeBSD does not have the mount op
I have two unrelated questions I can not figure out myself:
(1) Does FreeBSD NFS implementation support "noac" to disable attribute
cache? I know this is not good for performance.
(2) I am trying to display kernel profiling sysctl variables with sysctl
-a or sysctl -A without success. They
I searched the mailing list archive. I am not sure whether Vinum has
solved the problem of atomic writes in a stripe to both the data fragment
and parity fragment (RAID 5). In the case of a crash, you have no idea of
where the writes have finished (even worse, a fragment may contain
several
On Fri, 24 Mar 2000, Mike Smith wrote:
I searched the mailing list archive. I am not sure whether Vinum has
solved the problem of atomic writes in a stripe to both the data fragment
and parity fragment (RAID 5). In the case of a crash, you have no idea of
where the writes have
On Mon, 6 Mar 2000, Chris Costello wrote:
On Monday, March 06, 2000, Zhihui Zhang wrote:
Can anyone tell me where is the code for pci_intr_establish() and
_thread_sys_read()? I could not find them under /usr/src.
I can tell you offhand that _thread_sys_anything is the _real_
syscall
Can anyone tell me where is the code for pci_intr_establish() and
_thread_sys_read()? I could not find them under /usr/src.
Thanks,
-Zhihui
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
I have created several kernel threads that can die after being idle for a
while. I did this by copying the kthread_create() funtion from CURRENT
over to FreeBSD 3.3-Release. Is there a way to remove the zombie threads
after they die or prevent them from creating? Any potential problems in
trying
On Fri, 3 Mar 2000, Michael Bacarella wrote:
Upon reading of Microsoft's fabulous innovations in the filesystem arena,
I started playing with some ideas of my own (not to be confused with
ORIGINAL ideas)
Can someone tell me why copy-on-write filesystems would be bad?
Imagine: cp
My professor plans to use FreeBSD for teaching purpose. We will allow
students to build their kernel but do not want to give them root password.
So it's better to find a way to let students build kernel under their own
account, save the kernel on a floppy and then boot from the floppy.
I am
On Sat, 26 Feb 2000, Alex Povolotsky wrote:
Hello!
I've just read (well, partially) a whitepaper named "Embedded Inodes and
Explicit Grouping: Exploiting Disk Bandwidth for Small Files" (don't have
URL at hand).
Ideas presented there are QUIT interesting. Did anyone tried to implement
I have spent some time understanding the NQNFS code and have two questions
to ask:
(1) People say we can not do write-behind on the NFS server side. Does
this mean all vnode I/O must be performed with IO_SYNC (or other similar)
flag set on the server side when the I/O is done on behalf of a NFS
On 7 Feb 2000, Johan Danielsson wrote:
Zhihui Zhang [EMAIL PROTECTED] writes:
If the daemon can somehow reside entirely inside the kernel, like
NFS daemon, we can save those crossings.
Yes, but the whole point of having the daemon in userspace is that
it's *so* much easier
After reading part of the Arla daemon code available at
http://www.stacken.kth.se/projekt/arla/, I feel it is a real good design.
The daemon code is a multi-threaded user process that does most of the job
and the kernel is an interface to VFS. They communicate with each other
via a character
I have searched the archive for a while and still have some confusions
about this subjects:
(1) Some people say "For I/O bound activity, kernel threads are a really
bad idea". But I read the following passage from else where:
Kernel threads perform better in I/O-intensive applications
The message comes when you create a new filesystem with newfs. According
to page 263 of the "The complete FreeBSD", this is not a problem because
the space will be used anyway (how?).
I searched the archive, somebody mentioned an option to newfs to use the
unallocated space. My understanding
On Wed, 19 Jan 2000, Arun Sharma wrote:
In muc.lists.freebsd.hackers, you wrote:
When the kernel wants to access any user data, it either copies them into
the kernel or maps them into kernel address space. Can anyone tell me the
reasons why this is done? When a process enters the
When the kernel wants to access any user data, it either copies them into
the kernel or maps them into kernel address space. Can anyone tell me the
reasons why this is done? When a process enters the kernel mode, the
page tables are not changed.
I have taken this for granted for a long time
I use the following statements to time the system time used by a routine:
struct rusage ru_start, ru_end;
struct timeval stime;
getrusage(RUSAGE_SELF, ru_start);
call the routine
getrusage(RUSAGE_SELF, ru_end);
timersub(ru_end.ru_stime, ru_start.ru_stime, stime);
Sometimes I find that the
I have looked at the KLD examples and found out that they boils down to a
DECLARE_MODULE() macro with the subsystem given as SI_SUB_DRIVERS. Is
there any reason for using this particular SI_SUB_DRIVERS? I see another
example at http://www.freebsd.org/~abial/ that uses SI_SUB_EXEC.
Is this
On Fri, 17 Dec 1999, Andrzej Bialecki wrote:
On Fri, 17 Dec 1999, Arun Sharma wrote:
I have also figured out how to dynamically register sysctl nodes.
The trick is to basically malloc a sysctl_oid and fill in the right
fields and calling sysctl_register_oid. The code is in a kernel
:(3) Or maybe we can add a parameter to the filesytem, telling it to try to
:preallocate some contiguous disk space for all directory files. I guess
:that the cost per bit on disk is less than the cost per bit in memory.
I believe the filesystem already does this.
The FFS tries to
The big benefits to locality of meta file data are to allow
drive/driver caching to do sequential (or close to) reads in as large
blocks as possible. There was a recent SigOS paper on a modified Unix
filesystem that was designed to take advantage of modern disk systems,
Do you still
I have modified FFS filesystem code to put the disk inode at the beginning
of a file, i.e, the logical block #0 of each file begins with 128 bytes of
its disk inode and the rest of it are file data.
Everything seems to be working. But I am stuck with an ELF executable
file stored in this
On Mon, 6 Dec 1999, Ronald G. Minnich wrote:
On Mon, 6 Dec 1999, Zhihui Zhang wrote:
I have modified FFS filesystem code to put the disk inode at the beginning
of a file, i.e, the logical block #0 of each file begins with 128 bytes of
its disk inode and the rest of it are file data
On Mon, 6 Dec 1999, Julian Elischer wrote:
how do you find the inode?
There is an inode address map to look up. Each entry is four bytes.
-Zhihui
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
On Mon, 6 Dec 1999, Ronald G. Minnich wrote:
On Mon, 6 Dec 1999, Zhihui Zhang wrote:
I am doing some research on filesystem. I guess it may be faster to put
the disk inode with its file data together so that both can be read into
memory in one I/O.
I still don't get it. To get
I used to know that memory to memory copy is done by the DMA controller in
the I/O bridge (Actually, this knowledge confues me because DMA controller
normally does not store the data that pass through it. Now the source and
destination are both memory, how can it achieve this at the same time
Please take a look at the following piece of code that creates a large
hole in a file named hole.dat. It tries to write 0x30-0x39 both at the
front and the tail of that file, the hole is therefore in the middle.
main()
{
char c;
FILE * fp;
fp = fopen("hole.dat", "w");
I have set up a remote debugging environment. But I think default 9600
bps is slow. I can use "set remotebaud 19200" on the debugging machine
side. How can I set the baud rate on the target machine that is running
the debugged kernel? (I press CTRL+ESC+ALT to drop to DDB mode and find
no
On Mon, 15 Nov 1999, Greg Lehey wrote:
On Monday, 15 November 1999 at 15:13:53 -0700, Kenneth D. Merry wrote:
Zhihui Zhang wrote...
I have set up a remote debugging environment. But I think default 9600
bps is slow. I can use "set remotebaud 19200" on the debugging mach
I have set up an environment of remote serial debugging on FreeBSD
3.3-Release. I have a program that whenever it runs the kernel panics.
Is there any way I can use remote serial debugging to trace this panic
process instead of examining a dead kernel (i.e., coredump)?
Or, is there any way I
On Tue, 9 Nov 1999, Greg Lehey wrote:
On Tuesday, 9 November 1999 at 8:52:58 -0500, Zhihui Zhang wrote:
I have set up an environment of remote serial debugging on FreeBSD
3.3-Release. I have a program that whenever it runs the kernel panics.
Is there any way I can use remote serial
On Tue, 9 Nov 1999, Greg Lehey wrote:
On Tuesday, 9 November 1999 at 8:52:58 -0500, Zhihui Zhang wrote:
I have set up an environment of remote serial debugging on FreeBSD
3.3-Release. I have a program that whenever it runs the kernel panics.
Is there any way I can use remote serial
On Tue, 9 Nov 1999, Greg Lehey wrote:
On Tuesday, 9 November 1999 at 13:36:56 -0800, Archie Cobbs wrote:
Zhihui Zhang writes:
Thanks for your reply. What confuses me is that when I use commands "gdb"
(enter remote protocol mode) and "step" on the target mach
Thanks! I will certainly look into them. In the same time, I add a
sysctl variable and let my program calls Debugger("some string") if that
sysctl variable is true.
I don't understand what that's useful for.
If the kernel routine is going to be called from my code, I set the sysctl
I did a little remote debugging with serial cable on 4.0-current a while
ago. But now I can not make it work on 3.3-RELEASE.
I have used kermit to make sure that the cable connection is good. I also
have added necessary kernel options into the configuration file. My
questions are:
(1) What
On Tue, 2 Nov 1999, Greg Lehey wrote:
On Tuesday, 2 November 1999 at 17:10:41 -0500, Zhihui Zhang wrote:
It is said that the granularity of disk I/O is a sector. I read a little
bit of the source code isa/wd.c, which I think is the driver of IDE disks.
I find out that the disk can
From the system's point of view, there is no difference in reliability
between doing a single sector transfer and a multi-sector transfer
except for the size of the retry. Since retries do not occur very often
nobody really cares how big the retry is. Since there is a huge
It is said that the granularity of disk I/O is a sector. I read a little
bit of the source code isa/wd.c, which I think is the driver of IDE disks.
I find out that the disk can perform multi-block I/O sometimes. Does this
mean the granularity of disk I/O can be multi-sector? If the disk can
I have put all distribution files on a machine and installed three PCs via
FTP from that machine. The installation process should access the same
files, the buffer cache can be used to improve effieciency on the
filesystem side. I am wondering whether some sort of optimization is done
on the
The iozone performs 10 operations: read, write, re-read, re-write, read
backwards, read strided, fread, fwrite, random read, pread. Can anyone
explain to me a little more than what their names imply or give me some
references?
Any help is appreciated.
-Zhihui
To Unsubscribe: send mail to
Can anyone tell me the reason why we want to update the name of a
filesystem with the mount(8) command? From the source code, the new name
must be on the same vnode or device as the old name.
Any help is appreciated.
-Zhihui
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe
I am trying to change the mount point of a mounted filesystem (from
/testme to /test) with the update option (-u):
# mount /dev/wd0s2e /testme
# mount -u /dev/wd0s2e /test
mount: /dev/wd0s2e on /test: specified device does not match mounted
device
Why it does not work (I know I can umount
On Fri, 15 Oct 1999, Zhihui Zhang wrote:
Is the UMAPFS working? I add "options UMAPFS" to the configuration file
of FreeBSD 3.3-Release and rebuilt the kernel. I got the following
errors:
loading kernel
umap_vnops.o: In function `umap_lock':
umap_vnops.o(.text+0x568):
Is the UMAPFS working? I add "options UMAPFS" to the configuration file
of FreeBSD 3.3-Release and rebuilt the kernel. I got the following
errors:
loading kernel
umap_vnops.o: In function `umap_lock':
umap_vnops.o(.text+0x568): undefined reference to `null_bypass'
umap_vnops.o: In function
The comments say that the flag LK_INTERLOCK means "unlock passed simple
lock after getting lk_interlock". Under what circumstances are we going to
need two simple locks (release the first one after getting the second
one)? I can not understand this easily from the source code.
Any help is
Can anyone suggest me a way of searching symbols in the entire /usr/src
tree? I normally use grep */*. But grep does not work recursively, right?
Something like a small shell script may do this. Thanks a lot.
-Zhihui
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe
On Mon, 11 Oct 1999, Gustavo V G C Rios wrote:
May anyone here point me where in the source tree i can see file system
API implemented, like open, write, close, etc.
Check files /sys/src/sys/kern/vfs_syscalls.c and
/sys/src/sys/kern/sys_generic.c
-Zhihui
To Unsubscribe: send mail to
On Mon, 11 Oct 1999, Ruslan Ermilov wrote:
On Sun, Oct 10, 1999 at 03:16:43PM -0400, Zhihui Zhang wrote:
I modify the day time client program from the Stevens' book and run it on
both a Sun workstation and a FreeBSD machine. In the program, I use
signal() and alarm() to set a 5
I modify the day time client program from the Stevens' book and run it on
both a Sun workstation and a FreeBSD machine. In the program, I use
signal() and alarm() to set a 5 seconds timeout. The program works as
expected on Sun (after I comment out the daytime line in the file
/etc/inetd.conf)
is appreicated.
--
Zhihui Zhang. Please visit http://www.freebsd.org
--
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
The following is copied from the comments of FFS code:
"Block devices associated with filesystems may have new I/O requests
posted for them even if the vnode is *locked*, so no amount of trying will
get them clean. Thus we give block devices a good effort, then just give up.
For all other file
file types, go around and try again until it is clean."
Can anyone explain to me when this situation will occur and, preferrably,
point to the place of the related source code?
Any help is appreciated.
------
Zhihui Zhang. Please
I have been able to register a RPC service with the inetd deamon by
modifying the /etc/inetd.conf and /etc/rpc files. The RPC code is
generated with the -I option, i.e., by using rpcgen -I myfile.x.
(For those who have read my previous post, I made a mistake there. The
program number is a hex
I have been able to register a RPC service with the inetd deamon by
modifying the /etc/inetd.conf and /etc/rpc files. The RPC code is
generated with the -I option, i.e., by using rpcgen -I myfile.x.
(For those who have read my previous post, I made a mistake there. The
program number is a
modify the file /etc/defaults/rc.conf to set inetd_flags to be "-d"
(debug). This makes sure that inetd does register rls during bootup. After
bootup, the "rpcinfo -p localhost" on server also shows rls is there.
Can anyone tell me what I am missing? Thanks a lot.
---
On Mon, 27 Sep 1999, Alfred Perlstein wrote:
On Mon, 27 Sep 1999, Zhihui Zhang wrote:
I have typed in the source code of rls (remote directory list) from the book
"Power programming with RPC" and run it under FreeBSD successfully.
But I can not get the rls server
On Mon, 27 Sep 1999, Alfred Perlstein wrote:
On Mon, 27 Sep 1999, Zhihui Zhang wrote:
I have typed in the source code of rls (remote directory list) from the book
"Power programming with RPC" and run it under FreeBSD successfully.
But I can not get the rls server
headers
from the mbufs before it pass the mbufs up to the socket layer.
Any help is appreciated.
--
Zhihui Zhang. Please visit http://www.freebsd.org
--
To Unsubscribe: send mail to [EMAIL PROTECTED
command:
# mount -o port=xxx host:directory directory
and the -o port=xxx part will be passed onto the mount_nfs. Is this
right?
Thanks for any help.
--
Zhihui Zhang. Please visit http://www.freebsd.org
On Tue, 21 Sep 1999, Zhihui Zhang wrote:
The mount_nfs manual says I can use -o port=port_number to specify
a port number for NFS requests. Which port number should I use: the port
number of the portmapper (111), the port number of the mountd daemon, or
the port number of the nfsd daemon
.
--
Zhihui Zhang. Please visit http://www.freebsd.org
--
To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-hackers in the body of the message
Can anyone tell me how to let a daemon process print a message to the
console? Adding printf() does not work (I wonder if a daemon process
has been cut of relationship with stdout). Thanks for any help.
--
Zhihui Zhang. Please visit http
On Mon, 13 Sep 1999, Brian Mitchell (ISSATL) wrote:
syslog() with the proper facility is probably the best way to do this.
Another possibility is opening /dev/console, but I think that will aquire
a controlling terminal.
On Mon, 13 Sep 1999, Zhihui Zhang wrote:
Can anyone tell me
I am wondering where the NFS authentication is done in FreeBSD. Is it done
by the NFS daemon mountd (or other daemon) or within the kernel? Can
anyone give me a pointer? Thanks a lot.
--
Zhihui Zhang. Please visit http://www.freebsd.org
.
--
Zhihui Zhang. Please visit http://www.freebsd.org
--
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
On Wed, 8 Sep 1999, Luoqi Chen wrote:
The flag MNT_RELOAD is not documented in mount manpages. From the source
code, I find that it is always used along with MNT_UPDATE which can be
speficied by user (-u option). Can anyone explain the usage of MNT_RELOAD
for me? It seems not to be
ce of test2.c if I step that routine. Why it does not
work with fork()? Am I missing something?
Thanks for any help.
------
Zhihui Zhang. Please visit http://www.freebsd.org
--
To Unsubscribe: send m
until I can attach to it.
That will not be as easy.
-Zhihui
On Wed, 8 Sep 1999, Zhihui Zhang wrote:
I am using gdb 4.18 on FreeBSD-current. The program being debugged
consists of two small files: test1.c and test2.c. The main() in test1.c
has a call to fork
.
--
Zhihui Zhang. Please visit http://www.freebsd.org
--
To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-hackers in the body of the message
On Wed, 8 Sep 1999, Luoqi Chen wrote:
The flag MNT_RELOAD is not documented in mount manpages. From the source
code, I find that it is always used along with MNT_UPDATE which can be
speficied by user (-u option). Can anyone explain the usage of MNT_RELOAD
for me? It seems not to be
with fork()? Am I missing something?
Thanks for any help.
--
Zhihui Zhang. Please visit http://www.freebsd.org
--
To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-hackers
until I can attach to it.
That will not be as easy.
-Zhihui
On Wed, 8 Sep 1999, Zhihui Zhang wrote:
I am using gdb 4.18 on FreeBSD-current. The program being debugged
consists of two small files: test1.c and test2.c. The main() in test1.c
has a call to fork
On Mon, 6 Sep 1999, Alex Povolotsky wrote:
Hello!
The following program
#include stdio.h
#include fcntl.h
main() {
int control;
if ((control = open("STATUS",O_WRONLY|O_NONBLOCK))0) {
perror("Could not open STATUS ");
exit(1);
}
On Mon, 6 Sep 1999, Alex Povolotsky wrote:
Hello!
The following program
#include stdio.h
#include fcntl.h
main() {
int control;
if ((control = open(STATUS,O_WRONLY|O_NONBLOCK))0) {
perror(Could not open STATUS );
exit(1);
}
s is done by FreeBSD 4.0
automatically and the file debug.kernel is the one with symbols.
Any help is appreciated.
----------
Zhihui Zhang. Please visit http://www.freebsd.org
--
To Unsubscribe: send mail
On Mon, 30 Aug 1999, Zhihui Zhang wrote:
After reading the handbook and some postings in the mailing list archive.
I still can not make remote debugging work. I basically did the following
on FreeBSD-current 4.0 (A is debugging machine, B is the target):
(1) Build a debug kernel
On Mon, 30 Aug 1999, Zhihui Zhang wrote:
(3) On machine A, go to the compile directory:
#gdb -g kernel.debug
-g?
This is a typo. It should be "gdb -k kernel.debug". I have just posted
another message pointing out my mistakes. Thanks for your response
automatically and the file debug.kernel is the one with symbols.
Any help is appreciated.
--
Zhihui Zhang. Please visit http://www.freebsd.org
--
To Unsubscribe: send mail to majord...@freebsd.org
On Mon, 30 Aug 1999, Zhihui Zhang wrote:
After reading the handbook and some postings in the mailing list archive.
I still can not make remote debugging work. I basically did the following
on FreeBSD-current 4.0 (A is debugging machine, B is the target):
(1) Build a debug kernel
On Mon, 30 Aug 1999, Zhihui Zhang wrote:
(3) On machine A, go to the compile directory:
#gdb -g kernel.debug
-g?
This is a typo. It should be gdb -k kernel.debug. I have just posted
another message pointing out my mistakes. Thanks for your response.
-Zhihui
To Unsubscribe
is appreciated.
--
Zhihui Zhang. Please visit http://www.freebsd.org
--
To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-hackers in the body of the message
In file uipc_usrreq.c, there are many routines beginning with unp_. For
example, unp_connect(), unp_bind(), etc. What does unp stand for?
Thanks.
--
Zhihui Zhang. Please visit http://www.freebsd.org
In file uipc_usrreq.c, there are many routines beginning with unp_. For
example, unp_connect(), unp_bind(), etc. What does unp stand for?
Thanks.
--
Zhihui Zhang. Please visit http://www.freebsd.org
1,
then we can only use /dev/vn0x. The x stands for one of those eight
partitions [a-h] in one slice.
(2) For /dev/vn0[a-h], which one from a-h should I use for which purpose?
Any help is appreciated.
------
Zhihui Zhang. Please visit http://www.f
only use /dev/vn0x. The x stands for one of those eight
partitions [a-h] in one slice.
(2) For /dev/vn0[a-h], which one from a-h should I use for which purpose?
Any help is appreciated.
--
Zhihui Zhang. Please visit http://www.freebsd.org
Hi, Rich:
Can you find a serial cable for me? I need to connect two PCs together
via RS232 ports.
Thanks.
--
Zhihui Zhang. Please visit http://www.freebsd.org
--
To Unsubscribe: send mail
Hi, Rich:
Can you find a serial cable for me? I need to connect two PCs together
via RS232 ports.
Thanks.
--
Zhihui Zhang. Please visit http://www.freebsd.org
--
To Unsubscribe: send mail
ger exists.
You can't do that without a process to debug.
Is there something wrong? I did the same thing with the postmortem
coredump files and got similar messages. Maybe I am using gdb in a wrong
way.
Any help is appreciated.
------
Zhihui Zhan
On Fri, 20 Aug 1999, Greg Lehey wrote:
You can't control the execution of the kernel, you can just look at
the way things are. With the core dump, you at least have the
advantage that things won't change while you look at them; you can't
even do that with /dev/mem. The other alternative
.
You can't do that without a process to debug.
Is there something wrong? I did the same thing with the postmortem
coredump files and got similar messages. Maybe I am using gdb in a wrong
way.
Any help is appreciated.
--
Zhihui Zhang. Please visit
On Fri, 20 Aug 1999, Greg Lehey wrote:
You can't control the execution of the kernel, you can just look at
the way things are. With the core dump, you at least have the
advantage that things won't change while you look at them; you can't
even do that with /dev/mem. The other alternative is
und.
(kgdb) where
No stack.
Thanks for any help.
------
Zhihui Zhang. Please visit http://www.freebsd.org
--
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
No stack.
Thanks for any help.
--
Zhihui Zhang. Please visit http://www.freebsd.org
--
To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-hackers in the body of the message
- Release.
Any help is appreciated.
--
Zhihui Zhang. Please visit http://www.freebsd.org
--
To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-hackers in the body
the dumpon command. Thanks.
--
Zhihui Zhang. Please visit http://www.freebsd.org
--
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
On Fri, 13 Aug 1999, Andrzej Bialecki wrote:
On Fri, 13 Aug 1999, Zhihui Zhang wrote:
Can anyone tell me how to modify the config file to build a kernel that
creates dump image whenever it panics. Currently I have to use dumpon
command after system bootup. But this command does
the dumpon command. Thanks.
--
Zhihui Zhang. Please visit http://www.freebsd.org
--
To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-hackers in the body of the message
101 - 200 of 250 matches
Mail list logo
