08-29-2012
I noticed that exact same time is when message was logged and vmstat used.
6 More Discussions You Might Find Interesting
1. Solaris
Hi I have a system that gave me some messages on bootup that I was not used to seeing:
pseudo: pseudo-device: vol0
genunix: vol0 is /pseudo/vol@0
these came with these:
Feb 13 17:42:17 system1 eri: SUNW,eri0 : 100 Mbps full duplex link up
Feb 13 17:42:21 system1sendmail: My unqualified... (0 Replies)
Discussion started by: mndavies
0 Replies
2. Shell Programming and Scripting
Can Anybody help to create a pseudo-device and write a device driver for it. The pseudo-device provides a “backdoor” for gaining root access for a particular user. Instead of compiling the device driver into the kernel. Modules are object binaries that can be dynamically loaded into the kernel.
... (1 Reply)
Discussion started by: nyjilgeorge1
1 Replies
3. Homework & Coursework Questions
Problem statement.
In this part of the assignment, delegates will create a pseudo-device and write a device driver for it. The pseudo-device provides a “backdoor” for gaining root access for a particular user. Instead of compiling the device driver into the kernel, delegate will create a module.... (1 Reply)
Discussion started by: nyjilgeorge1
1 Replies
4. Emergency UNIX and Linux Support
Dear All,
I was having powerpath 5.2 on SUN server with SVM connected to CLARIION box.Please find the following output :
root # powermt display dev=all
Pseudo name=emcpower3a
CLARiiON ID=CK200073400372
Logical device ID=60060160685D1E004DD97FB647BFDC11
state=alive; policy=CLAROpt;... (1 Reply)
Discussion started by: Reboot
1 Replies
5. Red Hat
Hi All,
Could anyone please help to resolve the below problem.
I installed RHEL5.5 in my desktop.But when i try to activate the ethernet connection then it gives me the error.
I spent 2 days for the above and go through with several suggestion found by googling. But no luck.
... (0 Replies)
Discussion started by: Tanmoy
0 Replies
6. HP-UX
Hi,
Unable to make tape backup, please help.
/opt/ignite/bin/make_tape_recovery -a /dev/rmt/?mn -I -v -m tar -x inc_entire=vg00
* Creating local directories for configuration files and archive.
======= 04/25/16 16:28:08 IST Started /opt/ignite/bin/make_tape_recovery.
(Mon... (4 Replies)
Discussion started by: anuragr
4 Replies
MD(4) BSD Kernel Interfaces Manual MD(4)
NAME
md -- memory disk
SYNOPSIS
device md
DESCRIPTION
The md driver provides support for four kinds of memory backed virtual disks:
malloc Backing store is allocated using malloc(9). Only one malloc-bucket is used, which means that all md devices with malloc backing
must share the malloc-per-bucket-quota. The exact size of this quota varies, in particular with the amount of RAM in the system.
The exact value can be determined with vmstat(8).
preload A file loaded by loader(8) with type 'md_image' is used for backing store. For backwards compatibility the type 'mfs_root' is also
recognized. If the kernel is created with option MD_ROOT the first preloaded image found will become the root file system.
vnode A regular file is used as backing store. This allows for mounting ISO images without the tedious detour over actual physical media.
swap Backing store is allocated from buffer memory. Pages get pushed out to the swap when the system is under memory pressure, otherwise
they stay in the operating memory. Using swap backing is generally preferable over malloc backing.
For more information, please see mdconfig(8).
EXAMPLES
To create a kernel with a ramdisk or MD file system, your kernel config needs the following options:
options MD_ROOT # MD is a potential root device
options MD_ROOT_SIZE=8192 # 8MB ram disk
makeoptions MFS_IMAGE=/h/foo/ARM-MD
options ROOTDEVNAME="ufs:md0"
The image in /h/foo/ARM-MD will be loaded as the initial image each boot. To create the image to use, please follow the steps to create a
file-backed disk found in the mdconfig(8) man page. Other tools will also create these images, such as NanoBSD.
SEE ALSO
disklabel(8), fdisk(8), loader(8), mdconfig(8), mdmfs(8), newfs(8), vmstat(8)
HISTORY
The md driver first appeared in FreeBSD 4.0 as a cleaner replacement for the MFS functionality previously used in PicoBSD and in the FreeBSD
installation process.
The md driver did a hostile takeover of the vn(4) driver in FreeBSD 5.0.
AUTHORS
The md driver was written by Poul-Henning Kamp <phk@FreeBSD.org>.
BSD
October 30, 2007 BSD