1ramdiskadm(1M) System Administration Commands ramdiskadm(1M)
2
3
4
6 ramdiskadm - administer ramdisk pseudo device
7
9 /usr/sbin/ramdiskadm -a name size [g | m | k | b]
10
11
12 /usr/sbin/ramdiskadm -d name
13
14
15 /usr/sbin/ramdiskadm
16
17
19 The ramdiskadm command administers ramdisk(7D), the ramdisk driver. Use
20 ramdiskadm to create a new named ramdisk device, delete an existing
21 named ramdisk, or list information about existing ramdisks.
22
23
24 Ramdisks created using ramdiskadm are not persistent across reboots.
25
27 The following options are supported:
28
29 -a name size Create a ramdisk named name of size size and its corre‐
30 sponding block and character device nodes.
31
32 name must be composed only of the characters a-z, A-Z,
33 0-9, _ (underbar), and - (hyphen), but it must not
34 begin with a hyphen. It must be no more than 32 charac‐
35 ters long. Ramdisk names must be unique.
36
37 The size can be a decimal number, or, when prefixed
38 with 0x, a hexadecimal number, and can specify the size
39 in bytes (no suffix), 512-byte blocks (suffix b), kilo‐
40 bytes (suffix k), megabytes (suffix m) or gigabytes
41 (suffix g). The size of the ramdisk actually created
42 might be larger than that specified, depending on the
43 hardware implementation.
44
45 If the named ramdisk is successfully created, its block
46 device path is printed on standard out.
47
48
49 -d name Delete an existing ramdisk of the name name. This com‐
50 mand succeeds only when the named ramdisk is not open.
51 The associated memory is freed and the device nodes are
52 removed.
53
54 You can delete only ramdisks created using ramdiskadm.
55 It is not possible to delete a ramdisk that was created
56 during the boot process.
57
58
59
60 Without options, ramdiskadm lists any existing ramdisks, their sizes
61 (in decimal), and whether they can be removed by ramdiskadm (see the
62 description of the -d option, above).
63
65 Example 1 Creating a 2MB Ramdisk Named mydisk
66
67 # ramdiskadm -a mydisk 2m
68 /dev/ramdisk/mydisk
69
70
71
72 Example 2 Listing All Ramdisks
73
74 # ramdiskadm
75 Block Device Size Removable
76 /dev/ramdisk/miniroot 134217728 No
77 /dev/ramdisk/certfs 1048576 No
78 /dev/ramdisk/mydisk 2097152 Yes
79
80
81
83 ramdiskadm returns the following exit values:
84
85 0 Successful completion.
86
87
88 >0 An error occurred.
89
90
92 See attributes(5) for descriptions of the following attributes:
93
94
95
96
97 ┌─────────────────────────────┬─────────────────────────────┐
98 │ ATTRIBUTE TYPE │ ATTRIBUTE VALUE │
99 ├─────────────────────────────┼─────────────────────────────┤
100 │Availability │SUNWcsr │
101 ├─────────────────────────────┼─────────────────────────────┤
102 │Interface Stability │Evolving │
103 └─────────────────────────────┴─────────────────────────────┘
104
106 attributes(5), ramdisk(7D)
107
109 The abilities of ramdiskadm and the privilege level of the person who
110 uses the utility are controlled by the permissions of /dev/ramdiskctl.
111 Read access allows query operations, for example, listing device infor‐
112 mation. Write access is required to do any state-changing operations,
113 for example, creating or deleting ramdisks.
114
115
116 As shipped, /dev/ramdiskctl is owned by root, in group sys, and mode
117 0644, so all users can do query operations but only root can perform
118 state-changing operations. An administrator can give write access to
119 non-privileged users, allowing them to add or delete ramdisks. However,
120 granting such ability entails considerable risk; such privileges should
121 be given only to a trusted group.
122
123
124
125SunOS 5.11 25 Mar 2003 ramdiskadm(1M)