07-17-2001
Hmm I'll be using the Red Hat 7.1 with I believe the 2.4 Kernel? Would I still need to do all of that?
8 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
Is there an easy (and safe) way to upgrade RedHat versions remotely? I know the difference between 7.2 and 7.3 is just a bunch of newer .rpm file versions. Or is there more? Do I have to boot the CD and choose upgrade? What if I'm 100 miles from the server and would like to avoid traveling there?... (1 Reply)
Discussion started by: ArkiMage
1 Replies
2. SuSE
Hello,
Anyone out there deal with updating OS on linux servers remotely? We use Suse but like to hear what someone else does with any linux version. We have network connectivity to our remote locations but it's just a DSL connection, so some will be fast and some will be slow.
Thanks for... (1 Reply)
Discussion started by: benefactr
1 Replies
3. News, Links, Events and Announcements
two articles related to live upgrades that i found useful and noteworthy.
Solaris 10 5/08 Live Upgrade Gotcha :: Col’s Tech Stuff
Solaris Live Upgrade and Patches :: Col’s Tech Stuff (0 Replies)
Discussion started by: pupp
0 Replies
4. AIX
Hey!!!
Has anyone done HMC patch installation remotely? I would love to know if that would be possible. I have been doing through CD/DVD but hate to do the additional work of finding someone in the DC and sending him the CD's.
I have seen the option to supply remote site. can that be helpful?... (5 Replies)
Discussion started by: balaji_prk
5 Replies
5. AIX
Lets says I have 2 HMC's A and B, connected to a p570 managed system.
Right now the firmware level of the p570 is EM320_076 and that needs to be upgraded to EM340_095.
Now the HMC's are at V7R3.3 and as per the code matrix the HMC's needs to be upgraded to V7R3.4 Servicepack 2.
Now my... (5 Replies)
Discussion started by: balaji_prk
5 Replies
6. AIX
Hi everyone,
My current AIX OS level is "7100-01-06-1241"
and I am planning to upgrade it to " 7100-02-03 ".
Can i directly upgrade it to "7100-02-03" from 7100-01-06" ?
or first i need to upgrade the "7100-01-06" LPAR to TL 02 and then reboot and
then upgrade it to TL 02 SP03 ?
... (4 Replies)
Discussion started by: System Admin 77
4 Replies
7. What is on Your Mind?
This post is about the "Desktop" view, not "Mobile' ...
First of all, I want to thank everyone for all the great comments, error checking and feature suggestions as we modernize the site, step-by-step.
Also, thank you for your patience with me when as we make the site better.
So far, we... (1 Reply)
Discussion started by: Neo
1 Replies
8. What is on Your Mind?
Dear All,
I have made significant progress coding new discussion thread tagging features.
As always, we want all users to tag thread and moderators to tag threads with relevant keywords.
Moving forward, in addition to the #1 important "human tagging", we will also auto tag threads with one... (4 Replies)
Discussion started by: Neo
4 Replies
RAM(4) Kernel Interfaces Manual RAM(4)
NAME
ram - ram disk driver
SYNOPSIS
/sys/conf/SYSTEM:
NRAM ram_size # RAM disk size (512-byte blocks)
major device number(s):
block: 3
minor device encoding:
must be zero (0)
DESCRIPTION
The ram pseudo-device provides a very fast extended memory store. It's use is intended for file systems like /tmp and applications which
need to access a reasonably large amount of data quickly.
The amount of memory dedicated to the ram device is controlled by the NRAM definition in units of 512-byte blocks. This is also patchable
in the system binary through the variable ram_size (though a patched system would have to be rebooted before any change took effect; see
adb(1)). This makes it easy to test the effects of different ram disk sizes on system performance. It's important to note that any space
given to the ram device is permanently allocated at system boot time. Dedicating too much memory can adversely affect system performance
by forcing the system to swap heavily as in a memory poor environment.
The block file accesses the ram disk via the system's buffering mechanism through a buffer sharing arrangement with the buffer cache. It
may be read and written without regard to physical disk records. There is no `raw' interface since no speed advantage is gained by such an
interface with the ram disk.
DISK SUPPORT
The ram driver does not support pseudo-disks (partitions). The special files refer to the entire `drive' as a single sequentially
addressed file.
A typical use for the ram disk would be to mount /tmp on it. Note that if this arrangement is recorded in /etc/fstab then /etc/rc will
have to be modified slightly to do a mkfs(8) on the ram disk before the standard file system checks are done.
FILES
/dev/ram block file
/dev/MAKEDEV script to create special files
/dev/MAKEDEV.local script to localize special files
SEE ALSO
hk(4), ra(4), rl(4), rk(4), rp(4), rx(4), si(4), xp(4) dtab(5), autoconfig(8)
DIAGNOSTICS
ram: no space. There is not enough memory to allocate the space needed by the ram disk. The ram disk is disabled. Any attempts to access
it will return an error.
ram: not allocated. No memory was allocated to the ram disk and an attempt was made to open it. Either not enough memory was available at
boot time or the kernel variable ram_size was set to zero.
BUGS
The ram driver is only available under 2.11BSD.
3rd Berkeley Distribution Januray 27, 1996 RAM(4)