Syntax:

dd [—help] [—version] [if=file] [of=file] [ibs=bytes] [obs=bytes] [bs=bytes]
[cbs=bytes] [skip=blocks] [seek=blocks] [count=blocks] [conv={ascii,
ebcdic, ibm, block, unblock, lcase, ucase, swab, noerror, notrunc, sync}]

DESCRIPTION:

The GNU version of dd copies a file (from the standard input to the standard output, by default) with a user-selectable blocksize, while optionally performing conversions on it.

OPTIONS:

Numbers can be followed by a multiplier:
b=512, c=1, k=1024, w=2, xm=number m

These options are available:
—help Print a usage message on standard output and exit successfully.
—version Print version information on standard output then exit successfully.
if=file Read from file instead of the standard input.
of=file Write to file instead of the standard output. Unless conv=notrunc is given, truncate
file to the size specified by seek= (0 bytes if seek= is not given).
ibs=bytes Read bytes bytes at a time.
obs=bytes Write bytes bytes at a time.
bs=bytes Read and write bytes bytes at a time. Override ibs and obs.

cbs=bytes Convert bytes bytes at a time.
skip=blocks Skip blocks ibs-sized blocks at start of input.
seek=blocks Skip blocks obs-sized blocks at start of output.
count=blocks Copy only blocks ibs-sized input blocks.
conv=conversion[,conversion...] Convert the file as specified by the conversion arguments.

Conversions:

ascii Convert EBCDIC to ASCII.
ebcdic Convert ASCII to EBCDIC.
ibm Convert ASCII to alternate EBCDIC.
block Pad newline-terminated records to size of cbs, replacing newline with trailing spaces.
unblock Replace trailing spaces in cbs-sized block with newline.
lcase Change uppercase characters to lowercase.
ucase Change lowercase characters to uppercase.
swab Swap every pair of input bytes. Unlike the UNIX dd, this works when an odd
number of bytes are read. If the input file contains an odd number of bytes, the last
byte is simply copied (since there is nothing to swap it with).
noerror Continue after read errors.
notrunc Do not truncate the output file.
sync Pad every input block to size of ibs with trailing NULLs.

In the  image there is a RCS -Tree which have  following parts:

One Branch : 1.3.1.1  and this branch is originated from 1.3

Two releases : 1.x.x.x and 2.x

##########- STEPS FOR BRANCHING IN THE RCS TREE -#############

–>>    In already existing rcs tree, check the revisions by
using ‘rlog filename.c,v‘ .

–>>    Chose a revision to branch , and check-out its editable
             version.
i.e,
co -l1.3 filename.c,v

–>>    Now make changes into the file and check it in the tree
with  the particular branch Number,
i.e,
ci -r1.3.1 filename.c

–>>    Hence it will create first revision of branch 1.3.1
i.e,
version- 1.3.1.1    (1st Rev. of branch 1.3.1)

–>>    You also can create New Release for your Project, simply
by using Release No.
i.e,
ci -r2 filename.c

–>>    Hence it will create Second revision of RCS-Tree
i.e,
version- 2.1    (1st Rev. of Release 2)

–>>    You should refer to the above image while reading this for better
           understanding.

######################################################

Then follow these steps:

• first you have to install “livecd-tools” package.
• now plug in the pen drive & search the node using dmesg command in terminal,then unmount the partition created by it e.g.:umount /dev/sdb1
• now use this command to make it bootable:

livecd-iso-to-disk –format –reset-mbr /home/folder/fedora15_32bit.iso /dev/sdb1

where /home/folder/fedora15_32bit.iso  is path,where iso image is present & /dev/sdb1 is path for usb pen drive.

After the terminal shows 100% complete,your usb drive becomes bootable..& this pen drive will no longer show files on windows..

thank you..

The kernel file, in Ubuntu, is stored in your /boot folder and is called vmlinuz-version. The name vmlinuz comes from the unix world where they used to call their kernels simply “unix” back in the 60?s so Linux started calling their kernel “linux” when it was first developed in the 90?s.

When virtual memory was developed for easier multitasking abilities, “vm” was put at the front of the file to show that the kernel supports virtual memory. For a while the Linux kernel was called vmlinux, but the kernel grew too large to fit in the available boot memory so the kernel image was compressed and the ending x was changed to a z to show it was compressed with zlib compression. This same compression isn’t always used, often replaced with LZMA or BZIP2, and some kernels are simply called zImage.

The version numbering will be in the format A.B.C.D where A.B will probably be 2.6, C will be your version, and D indicates your patches or fixes.

In the /boot folder there will also be other very important files called initrd.img-version, system.map-version, and config-version. The initrd file is used as a small RAM disk that extracts and executes the actual kernel file. The system.map file is used for memory management before the kernel fully loads, and the config file tells the kernel what options and modules to load into the kernel image when the it is being compiled.

int main( int argc ,char*argv[])

{

}

[root@emblogic ~]# setenforce 0

[root@emblogic ~]# sestatus
SELinux status: enabled
SELinuxfs mount: /sys/fs/selinux
Current mode: permissive
Mode from config file: enforcing
Policy version: 28
Policy from config file: targeted

and now try to put or get file from server .

what to do ?

i am using Fedora 17

kernel 3.4.2-4

i boot my system using one kernel and installed drivers of wireless usb stick(usb wifi-dongule) on that kernel using ndiswrapper..

its working properly..

but when i boot the system using second kernel its not working..

do we have to install the drivers on every kernel separately..??

i got following error message.

Insufficient server config – no servers found. Aborting.

what to do ?

what it does mean ?

what it means about…..    ?

What it means ?

but here the area is same, so the server may also same.

in this case do i able to share the files