10-23-2013
When I had to use X on a 128MB PIII machine, I used Fluxbox. DOSbox and the like ran fine.
The difference is startling. With 128MB and Gnome I couldn't run GIMP in the remaining memory. With 128MB and Fluxbox, I could compile GIMP in the remaining memory.
Fluxbox does not give you a file browser, however!
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
i need to know how i would go about accessing my floppy disks, cd's and flash drives on my command prompt unix system (1 Reply)
Discussion started by: carlvernon
1 Replies
2. Solaris
Hi.
I got this message in our sun station and it stuck
Setting default IPv4 interface for multicast: add net 224.0/4: gateway pecsun22
but i can still telenet the station...
who could i fix this..
appreciate your help (7 Replies)
Discussion started by: eykyn17
7 Replies
3. AIX
I have an AIX server with a tape Library residing on it. I intend to restore the data backed up to the tape on Red Hat Enterprise Linux 5.
First , i would want to view the contents of the tape on RHEL 5(x86) but seems to be giving an input output error.
I observed that if i backup to tape on... (1 Reply)
Discussion started by: optimum
1 Replies
4. UNIX for Dummies Questions & Answers
I have an AIX server with a tape Library residing on it. I intend to restore the data backed up to the tape on Red Hat Enterprise Linux 5.
First , i would want to view the contents of the tape on RHEL 5(x86) but seems to be giving an input output error.
I observed that if i backup to tape on... (20 Replies)
Discussion started by: optimum
20 Replies
5. AIX
Hello All
I have a system running AIX 61 shared uncapped partition (with 11 physical processors, 24 Virtual 72GB of Memory) .
The output from NMON, vmstat show a high run queue (60+) for continous periods of time intervals, but NO paging, relatively low I/o (6000) , CPU % is 40, Low network.... (9 Replies)
Discussion started by: IL-Malti
9 Replies
6. AIX
Hi
I am running AIX 5.2. My server is running low on memory. It it using about 1307775 file pages on a total of 1511424 (from vmstat -v).
I looked at the memory yesterday morning, and we had plenty of free memory. I did a backup from Windows (ftp mget command) of a large file selection. From... (5 Replies)
Discussion started by: fredrivard
5 Replies
7. Programming
Hi friends,
I hope everyone is fine and doing well. I queried in my previous thread about the low-level qualities of C/C++ languages.I really thank you people for explaining, it was really helpful. One more ambiquity that I have in my mind is regarding the unix system calls like open, creat,... (1 Reply)
Discussion started by: gabam
1 Replies
8. Red Hat
Hi Guys
Required help in Redhat 6.1.
After installation of Redhat 6.1 in VMware system is not going in GUI mode.
please to solve the issue...
Thanks... (5 Replies)
Discussion started by: deviltech
5 Replies
9. Shell Programming and Scripting
Hello i have a working script that sends me an email if system disk space is above 98%.
I would like to add an extra command to the if condition. If disk space is above 98% it would also add an output of cd /var/log && du -sBM * |sort -n 2>&1 |grep -v -e "0M" -e "1M" command to the email.
I'm... (2 Replies)
Discussion started by: taf130
2 Replies
10. UNIX for Advanced & Expert Users
Could I please get some recommendations of a linux live cd for low memory? (1 Reply)
Discussion started by: cokedude
1 Replies
LEARN ABOUT DEBIAN
gfs_jadd
gfs_jadd(8) System Manager's Manual gfs_jadd(8)
NAME
gfs_jadd - Add journals to a GFS filesystem
SYNOPSIS
gfs_jadd [OPTION]... <DEVICE|MOINTPOINT>...
DESCRIPTION
gfs_jadd is used to add journals to a GFS filesystem after the device upon which the filesystem resides has been grown. By running
gfs_jadd on a GFS filesystem, you are filling in space between the current end of the filesystem and the end of the device upon which the
filesystem resides. When this operation is complete, the journal index is updated so that machines mounting the filesystem at a later date
will see the newly created journals in addition to the journals already there. Machines which are already running in the cluster are unaf-
fected.
gfs_jadd will not use space that has been formatted for filesystem data even if that space has never been populated with files.
You may only run gfs_jadd on a mounted filesystem, addition of journals to unmounted filesystems is not supported. You only need to run
gfs_jadd on one node in the cluster. All the other nodes will see the expansion has occurred when required.
You must be superuser to execute gfs_jadd. The gfs_jadd tool tries to prevent you from corrupting your filesystem by checking as many of
the likely problems as it can. When growing a filesystem, only the last step of updating the journal index affects the currently mounted
filesystem and so failure part way through the expansion process should leave your filesystem in its original state.
You can run gfs_jadd with the -Tv flags to get a display of the current state of a mounted GFS filesystem. This can be useful to do after
the journal addition process to see if the changes have been successful.
OPTIONS
-j num The number of new journals to add. This defaults to 1.
-J size
The size of the new journals in megabytes. The defaults to 128MB (the minimum size allowed is 32MB). If you want to add journals of
different sizes to the filesystem, you'll need to run gfs_jadd once for each different size of journal. The size you specify here
will be rounded down so that it is a multiple of the journal segment size which was specified at filesystem creation time.
-h Help. Prints out a short usage message and exits.
-q Quiet. Turns down the verbosity level.
-T Test. Do all calculations, but do not write any data to the disk and do not add journals. This is used to discover what the tool
would have done were it run without this flag. You probably want to turn the verbosity level up in order to gain most information
from this option.
-V Version. Print version information, then exit.
-v Verbose. Turn up verbosity of messages.
SEE ALSO
mkfs.gfs(8) gfs_grow(8)
gfs_jadd(8)