10 More Discussions You Might Find Interesting
1. SuSE
Hi. Not sure if this should go in the beginners section, so forgivness please if it's not correctly placed.
I just installed Linux Fedora Core 6 on my home computer (and am very very new to this) so I can learn more about it. However, I am looking for the FC6 equivalent to the System Device... (2 Replies)
Discussion started by: Carl1976
2 Replies
2. Linux
Hi ,
I am facing a strange with BIND in Fedora Core 6. Here is the config for more info.
#cat /etc/named.caching-nameserver.conf
options {
listen-on port 53 { any; };
directory "/var/named";
// dump-file "/var/named/data/cache_dump.db";
... (3 Replies)
Discussion started by: narasimhulu
3 Replies
3. Linux
hi i dont know much about linux but my boss gave me a job to backup all the mysql database and tables from fedora core4 running as web/database server. i can enter in fedora using remote desktop from my laptop but after that i am unable to do anything. if any one can help me in finding mysql and... (3 Replies)
Discussion started by: obstinate
3 Replies
4. Linux
hi all
i am currently using fedora core 3 . i downloaded the iso image of fedora core 6 but after installing the fedora core 6 . while starting linux it gives a error saying init is been killed .
wht is happened?
thank u (3 Replies)
Discussion started by: nageshrk
3 Replies
5. UNIX for Dummies Questions & Answers
Hello I'm trying to install fedora core 5 and I'm currently at this screen here:
http://fedora.redhat.com/docs/fedora-install-guide-en/fc5/figs/installingpackages.png
However, the bottom bar is completely gray and there's nothing telling me the "status" of the install. I also told it to format... (2 Replies)
Discussion started by: obeseogre
2 Replies
6. UNIX for Dummies Questions & Answers
Hello,
I am about to install Fedora on a partition on my hard drive. I got the CD from a magazine and it isnt a LiveCD so the magazine says "fedora core installer isn't a LiveCD, so it will merrily destroy your primary partition when you install on your machine", now I'm guessing the primary... (1 Reply)
Discussion started by: ArkNia
1 Replies
7. Linux
in fedora core 2 with enforcing mode in selinux , why even as a root OS doesnt give permission to create any directory or file in /home ? (1 Reply)
Discussion started by: the.last.soul
1 Replies
8. Linux
I've been using FC2, but my sound card doesn't work
I'm new with linux systems..
but there says that needs to recompile kernel
how can i do it with a kernel 2.6.5 i386 ?
by the way,. my sound card chipset is an ESS 1869F, with a compaq deskpro Smal Form Factor. but i have not found a... (4 Replies)
Discussion started by: Quake
4 Replies
9. Linux
I have done some research on the Fedora Project and trying to find clear cut answer on how to migrate from current OS - RH 8.0 Pro to Fedora Core 2. Can anybody help me with this and does Fedora Core 2 include OpenOffice and Ximian Evolution like with my RH 8.0 Pro. (3 Replies)
Discussion started by: Mark McWilliams
3 Replies
10. Linux
These are not my desktop (I am still using FC1), they are from Internet forum.
http://gator.dt.uh.edu/~yangm001/snapshot1.jpg
http://gator.dt.uh.edu/~yangm001/snapshot2.jpg (0 Replies)
Discussion started by: HOUSCOUS
0 Replies
MDADM.CONF(5) File Formats Manual MDADM.CONF(5)
NAME
mdadm.conf - configuration for management of Software Raid with mdadm
SYNOPSIS
/etc/mdadm.conf
DESCRIPTION
mdadm is a tool for creating, managing, and monitoring RAID devices using the md driver in Linux.
Some common tasks, such as assembling all arrays, can be simplified by describing the devices and arrays in this configuration file.
SYNTAX
The file should be seen as a collection of words separated by white space (space, tab, or newline). Any word that beings with a hash sign
(#) starts a comment and that word together with the remainder of the line is ignored.
Any line that starts with white space (space or tab) is treated as though it were a continuation of the previous line.
Empty lines are ignored, but otherwise each (non continuation) line must start with a keyword as listed below. The keywords are case
insensitive and can be abbreviated to 3 characters.
The keywords are:
DEVICE A device line lists the devices (whole devices or partitions) that might contain a component of an MD array. When looking for the
components of an array, mdadm will scan these devices (or any devices listed on the command line).
The device line may contain a number of different devices (separated by spaces) and each device name can contain wild cards as
defined by glob(7).
Also, there may be several device lines present in the file.
For example:
DEVICE /dev/hda* /dev/hdc*
DEV /dev/sd*
DEVICE /dev/discs/disc*/disc
ARRAY The ARRAY lines identify actual arrays. The second word on the line should be the name of the device where the array is normally
assembled, such as /dev/md1. Subsequent words identify the array, or identify the array as a member of a group. If multiple identi-
ties are given, then a component device must match ALL identities to be considered a match. Each identity word has a tag, and
equals sign, and some value. The tags are:
uuid= The value should be a 128 bit uuid in hexadecimal, with punctuation interspersed if desired. This must match the uuid stored in
the superblock.
super-minor=
The value is an integer which indicates the minor number that was stored in the superblock when the array was created. When an
array is created as /dev/mdX, then the minor number X is stored.
devices=
The value is a comma separated list of device names. Precisely these devices will be used to assemble the array. Note that the
devices listed there must also be listed on a DEVICE line.
level= The value is a raid level. This is not normally used to identify an array, but is supported so that the output of
mdadm --examine --scan
can be use directly in the configuration file.
num-devices=
The value is the number of devices in a complete active array. As with level= this is mainly for compatibility with the output
of
mdadm --examine --scan.
spare-group=
The value is a textual name for a group of arrays. All arrays with the same spare-group name are considered to be part of the
same group. The significance of a group of arrays is that mdadm will, when monitoring the arrays, move a spare drive from one
array in a group to another array in that group if the first array had a failed or missing drive but no spare.
MAILADDR
The mailaddr line gives an E-mail address that alerts should be sent to when is running in --monitor mode (and was given the --scan
option). There should only be one MAILADDR line and it should have only one address.
PROGRAM
The program line gives the name of a program to be run when mdadm --monitor detects potentially interesting events on any of the
arrays that it is monitoring. This program gets run with two or three arguments, they being the Event, the md device, and possibly
the related component device.
There should only be one program line and it should be give only one program.
EXAMPLE
DEVICE /dev/sd[bcdjkl]1
DEVICE /dev/hda1 /dev/hdb1
# /dev/md0 is known by it's UID.
ARRAY /dev/md0 UUID=3aaa0122:29827cfa:5331ad66:ca767371
# /dev/md1 contains all devices with a minor number of
# 1 in the superblock.
ARRAY /dev/md1 superminor=1
# /dev/md2 is made from precisey these two devices
ARRAY /dev/md2 devices=/dev/hda1,/dev/hda2
# /dev/md4 and /dev/md5 are a spare-group and spares
# can be moved between them
ARRAY /dev/md4 uuid=b23f3c6d:aec43a9f:fd65db85:369432df
spare-group=group1
ARRAY /dev/md5 uuid=19464854:03f71b1b:e0df2edd:246cc977
spare-group=group1
MAILADDR root@mydomain.tld
PROGRAM /usr/sbin/handle-mdadm-events
SEE ALSO
mdadm(8), md(4).
MDADM.CONF(5)