Should I use a CoW filesystem on my PC if I only wanted snapshot capabilities ? Post: 303044634

9 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Unix Capabilities?

We are looking into buying a new software, billing software that is, and want to know if you can run that on the same UNIX server as another major software? Is there a limit to the different types of software Unix can run, or is it like windows where you can install as many as you like? ...

2. UNIX for Advanced & Expert Users

p570 Capabilities

Hi there. I've been tasked with making a new design for our Unix systems :eek: Now the question I have is; How many LPARs can a p570 hold WITHOUT using a VIO Server. Many Thanks Kees

3. Red Hat

Adding capabilities to an RPM

Hi. I downloaded a package that could only be installed on RHEL5, and not 4 or 3, so I got the source in order to compile it on RHEL 3 so hopefully it will work on all versions. So I have the source for a working package, but when I build it in RHEL 3 and then try to install it in RHEL 5, it...

4. Filesystems, Disks and Memory

Wanted: Geographically distributed filesystem solution

I'm looking for a means to ensure that servers in the two or three datacenters, connected in a ring via IP through two ISPs, can distribute load and/or replicate data among at least two SAN-class disk devices. I want to evaluate several solutions, and I'm open to solutions ranging from free,...

5. Solaris

Cannot use filesystem while sending a snapshot

I've got a Solaris 11 Express installed on my machine. I have created a raidz2 zpool named shares and a simple one-disc zpool named backup. I have made a script that would send a daily snapshot of shares to backup. I use these commands zfs snapshot shares@DDMMRRRRHHMM zfs send -i shares@.......

6. UNIX for Advanced & Expert Users

Use of Capabilities

I wonder if anyone could assist with some problems I'm having with Linux Capabilities and their use when using the commands "nice" and "schedtool". I run a couple of PCs, one is an elderly AMD Sempron 2800+ (32-bit, 2GHz clock and 3GB memory) that is used as a family multimedia system running...

7. Linux

Broadcom under Fedora 18 (Spherical Cow)

So I'm having a problem getting a Broadcom BCM4312 wireless controller to work under the broadcom-wl module $uname Linux 3.8.11-200.fc18.x86_64 #1 SMP Wed May 1 19:44:27 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux lspci -v 05:00.0 Network controller: Broadcom Corporation BCM4312 802.11b/g...

8. UNIX for Advanced & Expert Users

Linux capabilities discussion

Hi I'm trying to compile my linux kernel with CONFIG_SECURITY_CAPABILITIES=y. any idea what this thing does ?? Also another question , If I compile the kernel that I'm currently using , what'll happen ? ~cheers

9. What is on Your Mind?

Anybody want to talk about Dirty Cow?

Hi All, How worried is everyone about the Dirty Cow Linux exploit? Has anybody experienced attacks yet? From the research I've done it seems that the exploit is "reliable" (that is it works nearly every time on vulverable systems) which is not good news. We all believe that Unix/Linux...

LEARN ABOUT FREEBSD

uefi

UEFI(8) 						    BSD System Manager's Manual 						   UEFI(8)

NAME

     UEFI -- Unified Extensible Firmware Interface bootstrapping procedures

DESCRIPTION

     The UEFI Unified Extensible Firmware Interface provides boot- and run-time services to operating systems.	UEFI is a replacement for the
     legacy BIOS on the i386 and amd64 CPU architectures, and is also used on arm64 and ia64.

     The UEFI boot process loads system bootstrap code located in an EFI System Partition (ESP).  The ESP is a GPT or MBR partition with a spe-
     cific identifier that contains an msdosfs(5) FAT file system with a specified file hierarchy.

	   Partition Scheme    ESP Identifier
	   GPT		       C12A7328-F81F-11D2-BA4B-00A0C93EC93B
	   MBR		       0xEF

     The UEFI boot process proceeds as follows:
	   1.	UEFI firmware runs at power up and searches for an OS loader in the EFI system partition.  The path to the loader may be set by an
		EFI environment variable.  If not set, the default is /EFI/BOOT/BOOTX64.EFI.  The default UEFI boot configuration for FreeBSD
		installs boot1.efi as /EFI/BOOT/BOOTX64.EFI.
	   2.	boot1.efi locates the first partition with the type freebsd-ufs, and from it loads loader.efi.
	   3.	loader.efi loads and boots the kernel, as described in loader(8).

     The vt(4) system console is automatically selected when booting via UEFI.

FILES

     /boot/boot1.efi
		   First stage UEFI bootstrap
     /boot/boot1.efifat
		   msdosfs(5) FAT file system image containing boot1.efi for use by bsdinstall(8) and the bootcode argument to gpart(8).
     /boot/loader.efi
		   Final stage bootstrap
     /boot/kernel/kernel
		   default kernel
     /boot/kernel.old/kernel
		   typical non-default kernel (optional)

SEE ALSO

     vt(4), msdosfs(5), boot(8), gpart(8)

HISTORY

     UEFI boot support first appeared in FreeBSD 10.1.

AUTHORS

     UEFI boot support was developed by Benno Rice <benno@FreeBSD.org>, Ed Maste <emaste@FreeBSD.org>, and Nathan Whitehorn
     <nwhitehorn@FreeBSD.org>.	The FreeBSD Foundation sponsored portions of the work.

CAVEATS

     EFI environment variables are not supported by loader(8) or the kernel.

     boot1.efi loads loader.efi from the first FreeBSD-UFS file system it locates, even if it is on a different disk.

     boot1.efi cannot load loader.efi from a ZFS(8) file system.  As a result, UEFI does not support a typical root file system on ZFS configura-
     tion.

BSD
								 October 17, 2014							       BSD