search for: _content_

...nc is very persistent in replacing the device node file with just a regular file, which because the file is new, causes it to transfer the content of the original file, filling up the filesystem /dev is on and needing to restore the device node with mknod. So, how can I get rsync to syncronize the _content_ of the device with the _content_ of the source file (or source device)? I don't even have luck trying to syncronize device content to device content (e.g. without --devices, which would just replicate the node and it's major,minor ... it says it is just skipping the non-regular file naming...

On Mon, 2015-06-15 at 21:41 -0500, Robert Nichols wrote: > Non-GPT partitions do not have a UUID. The _content_ (filesystem, > LVM physical volume, non-encrypted swap space, etc.) of such a > partition could have a UUID, but the partition itself does not. ON Centos 5, using GPARTED I created partitions for filing systems ext3 and ext4. 4 primary and unlimited (except by space) extended partitions. Tha...

...rtitions. > LUKS provides a UUID, so being encrypted isn't a barrier to having a UUID. But my point was M$ DOS partitions, not being GPT partitions, can have UUIDs. The original poster appeared to suggest that was not possible. He wrote > > Non-GPT partitions do not have a UUID. The _content_ (filesystem, > > LVM physical volume, non-encrypted swap space, etc.) of such a > > partition could have a UUID, but the partition itself does not. When I think I am mounting a M$ DOS partition, am I mounting a real partition or merely 'the file system' within that partition ?...

...gt; wrote >> > > Those were filesystem UUIDs not partition UUIDs ... LUKS physical volume UUIDs, actually. When you create a LUKS logical volume within that PV, it also has a UUID, and a filesystem within that LUKS LV will have its own UUID. These are all part of the partition's _content_. A GPT partition has its own UUID, independent of the partition's content. An MSDOS partition does not. > LUKS has its own header similar to ext4, lvm, etc headers which has a UUID > in it. > > This UUID being associated with the LUKS header indicates it is not a > partition UU...

On 06/15/2015 07:56 AM, Robert Nichols wrote: > On 06/14/2015 10:08 PM, jd1008 wrote: >> >> >> On 06/14/2015 08:58 PM, John R Pierce wrote: >>> On 6/14/2015 6:55 PM, Timothy Murphy wrote: >>>> Maybe I used dd at some point. >>>> Would this keep the same UUID? >>> >>> DD just does a blind block by block copy between two devices

Reporting a possible inconsistency or bug in handling stringsAsFactors in as.data.frame.table() Here is a simple test > options()$stringsAsFactors [1] TRUE > x<-c("a","b","c","a","b") > d<-as.data.frame(table(x)) > d x Freq 1 a 2 2 b 2 3 c 1 > class(d$x) [1] "factor" >

...these are _not_ complete detailed > instructions): > > _ MBR (aka "msdos" partition) scheme > _ create one partition > _ set the partition as "bootable" (aka "active" flag) > _ dd mbr.bin > _ mount the partition; format it as FAT32 > _ copy the _content_ of the ISO image to the FAT32 partition > _ install SYSLINUX on the FAT32 partition (and replace .c32 modules > with a matching version, if needed) Yes, I recommend this. I've been doing this with Debian live images successfully many times. It was some time ago I created theese, so I was...

On 06/15/2015 11:08 AM, jd1008 wrote: > Thanx for the update > but what about non-gpt and non lvm partitions? > What is used as inp > nut to create a universally unique id? Non-GPT partitions do not have a UUID. The _content_ (filesystem, LVM physical volume, non-encrypted swap space, etc.) of such a partition could have a UUID, but the partition itself does not. -- Bob Nichols "NOSPAM" is really part of my email address. Do NOT delete it.

...s not a partition UUID. A dd of this (or lvm snapshot) to another partition will keep the same UUID. A partition UUID within a GPT table would not be persisted in this manner, and msdos labeled disks have no concept of this to begin with. > > > Non-GPT partitions do not have a UUID. The _content_ (filesystem, > > > LVM physical volume, non-encrypted swap space, etc.) of such a > > > partition could have a UUID, but the partition itself does not. > > When I think I am mounting a M$ DOS partition, am I mounting a real > partition or merely 'the file system'...

HI all, I set up a PXE server by following the following howto ( http://www.tecmint.com/install-pxe-network-boot-server-in-centos-7/ ) is working but I noticed him running I need the CD in one repository http or nfs. because it is necessary to have everything in ISO image? it is possible to boot an ISO by the network as I do with the CD or DVD? Regards.

...t I actually think it is fine as it is: The classifying _factors_ of a crosstable should be factors unless very specifically directed otherwise and that should not depend on the setting of an option that controls the conversion of character data. For as.data.frame.matrix, in contrast, it is the _content_ of the matrix that is being converted, and it seems much more reasonable to follow the same path as for other character data. -pd > On 12 Mar 2019, at 21:39 , Mychaleckyj, Josyf C (jcm6t) <jcm6t at virginia.edu> wrote: > > Reporting a possible inconsistency or bug in handling stri...

Hi all, Some simple questions about codecs: What codec does the Zap channel use by default? Can this default be changed, and to what? (g729 too?) What codec does meetme use? (I think this is ulaw, but asking to be sure) Can you use another codec, or does everything have to be transcoded to ulaw? Finally ... if I have a 3way call going, between 1 g729 caller and two other callers, do I need one

>Paul E Wrote [snip] >Windows 2000 (although it's the same for all of them) doesn't read in >any mime-type to correctly identify a file, it just uses the extension. [snip] What if, at least for Windows, someone wrote a simple application which when associated with .ogg files and an .ogg file was opened simply read enough of the ogg stream to identify the type of content and then

...ioning and formatting the USB device (these are _not_ complete detailed instructions): _ MBR (aka "msdos" partition) scheme _ create one partition _ set the partition as "bootable" (aka "active" flag) _ dd mbr.bin _ mount the partition; format it as FAT32 _ copy the _content_ of the ISO image to the FAT32 partition _ install SYSLINUX on the FAT32 partition (and replace .c32 modules with a matching version, if needed) Beware: I am not describing each step in detail, but some details are very important for the success (or not) of the procedure. Someone else might want...

On 03/18/2017 01:18 AM, Ady Ady via Syslinux wrote: > Some of the things you should / could (re)test / (re)try: > > _ Verify the md5sum of the ISO image. SHA256 verified for downloaded image and for contents of USB flash drive (see below). > _ Is this particular USB device _still_ capable of booting newer > computers? Yes. > What happens if you would try _again_ to boot a