OK, well apologies for the slight tangent I sent us off on, but again it comes back to this "DEVNAME" thing.
Before, or after, when you call fdisk..
can you add some debug to the log file?
It seems that's not doing what you think it should be. Again, as previously suggested, you should fully qualify the commands (/usr/bin/grep, etc.) - shouldn't make any assumptions about the environment udev is using when it does stuff.
If you change all of the ">> $LOG_FILE" to "&>> $LOG_FILE", you'll also log all the errors, if there are any.
installed fedora core 5 on a pc with USB and some usual things. in boot up it is stopped at "Starting udev:". Its harddisk light is busy. is it reconfiguring the kernel?. what do to solve this problem?. (0 Replies)
Hello all
I have to run manually make commands in our system the make compilations task's takes very long
And I like to be able to run another make task right after one is finished.
What is the best way to automate it ? (2 Replies)
Hi,
I worte a script which runs perfect when i execute it manually. But when i scheduled into cron the grep command alone is not working.
the sample script,
/usr/bin/grep FTP $subfile > /tmp/tfsrec.dat
tfs=`echo $?`
if
then
echo "FTP FOUND"
else
echo "FTP NOT FOUND"
Where... (5 Replies)
I'm curious about the behavior where any udev labeled device causes that corresponding listing to disappear from fdisk, sfdisk, or in the case of RDAC, lsvdev.
I have seen this on both EMC clariion and Sun Storagetek/Engenio 6540 arrays.
We use RHEL5.1 and udev to create persistent labels for... (2 Replies)
Hello!
I'm sorry if this is the false Forum, didn't really knew where to put it...
My question:
I have serveral USB-Sticks and wrote several Udev-Rules for theme, each Sticks needs to do something else, but all are using the same script (they have common tasks to do) and only some parts are... (2 Replies)
hi
i want to automate fdisk command .
i spawned a process containing fdisk command from a process
and tried to send the options to fdisk promt from that process.
but that spawed process is notstarting itself
help me out
trying for two days
:wall:
my code:
#!/bin/bash
echo... (5 Replies)
Hello,
MBR partition table made by linux fdisk looks certainly not correct when printed by openbsd fdisk:
Partition table created on linux (centos 6.3):
# fdisk -l /dev/sdc
Disk /dev/sdc: 10.7 GB, 10737418240 bytes
255 heads, 63 sectors/track, 1305 cylinders
Units = cylinders of 16065 *... (2 Replies)
I have made a program that reads a text file and checks for palindromic words and then outputs them. They each appear on a new line with a count of the number of occurences beside each of the words.
Requirements for being classed as palindrome are that the word must have at least 3 letters and... (7 Replies)
Discussion started by: greenhouse91
7 Replies
LEARN ABOUT MINIX
fdisk
FDISK(8) System Manager's Manual FDISK(8)NAME
fdisk - partition a hard disk [IBM]
SYNOPSIS
fdisk [-hm] [-sn] [file]
OPTIONS -h Number of disk heads is m
-s Number of sectors per track is n
EXAMPLES
fdisk /dev/hd0 # Examine disk partitions
fdisk -h9 /dev/hd0 # Examine disk with 9 heads
DESCRIPTION
When fdisk starts up, it reads in the partition table and displays it. It then presents a menu to allow the user to modify partitions,
store the partition table on a file, or load it from a file. Partitions can be marked as MINIX, DOS or other, as well as active or not.
Using fdisk is self-explanatory. However, be aware that repartitioning a disk will cause information on it to be lost. Rebooting the sys-
tem immediately is mandatory after changing partition sizes and parameters. MINIX, XENIX, PC-IX, and MS-DOS all have different partition
numbering schemes. Thus when using multiple systems on the same disk, be careful.
Note that MINIX, unlike MS-DOS , cannot access the last sector in a partition with an odd number of sectors. The reason that odd partition
sizes do not cause a problem with MS-DOS is that MS-DOS allocates disk space in units of 512-byte sectors, whereas MINIX uses 1K blocks.
Fdisk has a variety of other features that can be seen by typing h.
Fdisk normally knows the geometry of the device by asking the driver. You can use the -h and -s options to override the numbers found.
SEE ALSO part(8).
FDISK(8)