Project:VisualEditor testing/Test

Hello, and welcome to the VisualEditor demonstration page. Do not expect edits here to stay for long; this page is like the sandbox.

'''Feedback here will likely be ignored. Please use VisualEditor/Feedback instead. Read VisualEditor/Welcome for the answers to many of your questions.'''

Note: The "VisualEditor" button only works with the Vector or MonoBook skins; see notes.

There are also specific test pages for templates, for references, and for formulæ.

= Heading 1a - Testing =

How to enable writing to NTFS hard drives for free in OS X Mavericks
Windows uses the NTFS file system for its hard drives. Mac OS X can read files on NTFS hard drives, but it can't write files to them, which is a glaring omission. Attempting to drag a file into an NTFS drive in Mac OS X will only result in your mouse cursor turning into an error sign. Since many Hackintoshes dual-boot Windows and Mac OS X, being unable to share files between hard drives can lead to a lot of problems with file management. Fortunately, you can enable NTFS writing on OS X Mavericks with relatively little trouble-- all it takes is a few drivers and 10 minutes of your time.

This mini-guide merely repeats what we said in our last article about enabling NTFS write capabilities in Mac OS X, from back in 2012. Of course, a bit has changed since then. Nowadays, you can actually just skip third-party drivers altogether by enabling Apple's native NTFS drivers through Terminal instead. Despite these developments, however, we still recommend that you follow this guide and install third-party drivers anyways. It's simpler, and you don't need to use Terminal. (Here at MacBreaker, we have a policy of avoiding the use of Terminal whenever possible.)

UPDATE (September 12, 2014): Niresh has combined the 3 separate drivers listed in this guide into a single all-in-one NTFS driver package, which is quicker and easier to install. However, the download process on Niresh's website is a bit convoluted, so it's up to you whether you want to try his new driver package, or just stick to the current method detailed in this guide (either way, the results are the same).

1. Install FUSE for OS X Download and install OSXFUSE on your computer. While it won't enable NTFS write in Mac OS X by itself, FUSE is a necessary "building block" for pretty much any Mac driver that deals with third-party file systems (including the NTFS file system).

DOWNLOAD: FUSE for OS X

While installing FUSE for OS X, be sure to check the "MacFUSE Compatibility Layer" option in the installer. You'll need it for the next step, in which we install the NTFS-3G driver-- that driver hasn't been updated in a while, so it needs this extra compatibility layer to work properly.

2. Install NTFS-3G Next, download and install NTFS-3G. This is the driver that will actually enable NTFS write capabilities on your computer.

DOWNLOAD: NTFS-3G

During the installation process, you'll be given an option to install the NTFS-3G driver with either "No caching" or "UBLIO caching". While it probably won't actually matter, you may want to choose "No caching" to be safe. Either way, can always change this setting afterwards. Then, once the installation is finished, reboot your computer.

Back in the days of Mac OS X Snow Leopard, you could simply install this driver by itself (along with MacFUSE, the predecessor to OSXFUSE), and then Mac OS X would have NTFS writing capabilities automatically. Unfortunately, development of NTFS-3G has since stopped, which is why we need to do a bit of extra work to make everything run right.

3. Install fuse-wait The first time you boot into Mac OS X after installing NTFS-3G, you'll probably be bombarded with error messages about your hard drives. Technically, this means that NTFS-3G is working correctly; you should now be able to write files onto your NTFS drives in Mac OS X. However, you'll probably want to get rid of these annoying error messages. To do that, download and install the fuse_wait patch for NTFS-3G.

DOWNLOAD: fuse_wait

Once fuse_wait is installed, that's all there is to it! You should now be able to write files onto NTFS hard drives in Mac OS X, seamlessly and without any errors. Congratulations!

This is some text. This text has a bold and an italic word in it.

Heading 1b
= Solaris 10 boot process : sparc = The boot process for SPARC platform involves 5 phases as shown in the diagram below. There is a slight difference in booting process of a SPARC based and x86/x64 based solaris operating system.

Boot PROM phase
1. The boot PROM runs the power on self test (POST) to test the hardware. 2. The boot PROM displays the banner with below information - Model type - processor type - Memory - Ethernet address and host ID 3. Boot PROM reads the PROM variable boot-device to determine the boot device. 4. Boot PROM reads the primary boot program ( bootblk ) [sector 1 to 15] and executes it.

Boot program phase
1.  bootblk  loads the secondary boot program  ufsboot  into memory. 2. ufsboot reads and loads the kernel. The kernel is composed of 2 parts : 3. ufsboot combines these 2 kernel into one complete kernel and loads into memory.
 * unix (platform specific kernel)
 * genunix (platform independent kernel)

Kernel initialization phase
1. The kernel reads the configuration file /etc/system. 2. Kernel initializes itself and loads the kernel modules. The modules usually reside in /kernel and /usr/kernel directories. (Platform specific drivers in /platform/‘uname -i‘/kernel and /platform/‘uname -m‘/kernel directories)

Init phase
1. Kernel starts the /etc/init daemon (with PID 1). 2. The /etc/init daemon starts the svc.startd process which is responsible for starting and stopping the services. 3. The /etc/init daemon uses a file called /etc/inittab to boot up the system to the appropriate run level mentioned in this file.

Legacy Run Levels Run level specifies the state in which specific services and resources are available to users. 0  - system running PROM monitor (ok> prompt) s or S   - single user mode with critical file-systems mounted.(single user can access the OS) 1  - single user administrative mode with access to all file-systems.(single user can access the OS) 2  - multi-user mode. Multiple users can access the system. NFS and some other network related daemons does not run 3  - multi-user-server mode. Multi user mode with NFS and all other network resources available. 4  - not implemented. 5  - transitional run level. Os is shutdown and system is powered off. 6  - transitional run level. Os is shutdown and system is rebooted to the default run level. svc.startd phase 1. After kernel starts the svc.startd daemon. svc.startd daemon executes the rc scripts in the /sbin directory based upon the run level.

rc scripts Now with each run level has an associated script in the /sbin directory -rwxr--r--  3 root     sys   1678 Sep 20  2012 /sbin/rc0 -rwxr--r--  1 root     sys         2031 Sep 20  2012 /sbin/rc1 -rwxr--r--  1 root     sys         2046 Sep 20  2012 /sbin/rc2 -rwxr--r--  1 root     sys         1969 Sep 20  2012 /sbin/rc3 -rwxr--r--  3 root     sys         1678 Sep 20  2012 /sbin/rc5 -rwxr--r--  3 root     sys         1678 Sep 20  2012 /sbin/rc6 -rwxr--r--  1 root     sys         4069 Sep 20  2012 /sbin/rcS Each rc script runs the corresponding /etc/rc?.d/K* and /etc/rc?.d/S* scripts. For example for a run level 3, below scripts will be executed by /sbin/rc3 : /etc/rc3.d/K* /etc/rc3.d/S* The syntax of start and stop run scripts is S##name_of_script - Start run control scripts K##name_of_scrips - Stop run control scripts Note the S and K in caps. Scripts starting with small s and k will be ignored. This can be used to disable a script for that particular run level.
 * 1) ls -l /sbin/rc?

= Heading 2a - Testing =

Heading 3abc
= Heading 1b =

Heading 2bc
= Heading 3c = List item:
 * Foo

List item with formatted content:
 * Fooo

List item with a paragraph in it:
 * Baaaaar
 * Baz
 * sdk
 * skldv
 * klsdsv
 * sjdkvn
 * sjnvd
 * skjvn
 * sjvn
 * 1) sdvjksdv
 * 2) sdkjvn
 * 3) skvdjnsvk
 * 4) skjvn
 * 5) svdjnjk
 * 6) Qsjvks
 * 7) svkjsnvd
 * 8) ksvjd
 * 9) skdvslv

= How to Enable NTFS Write Support in Mac OS X = Oct 2, 2013 - 34 Comments

OS X has always been able to read NTFS drives, but tucked away in Mac OS X is a hidden option to enable write support to drives formatted as NTFS (NTFS stands for New Technology File System and is a proprietary file system format for Microsoft Windows). Enabling NTFS write support on the Mac is fairly technical and it’s not officially supported by Apple, making it an experimental feature that is best left in the hands of advanced users who understand the process and the potential repercussions.

Because this feature is officially unsupported by Apple, NTFS should not be considered a reliable cross-platform file system for moving files between a Mac and a Windows PC, users will still want to format drives for the FAT file system for optimal Mac to/from PC drive compatibility with full read and write support (perhaps a better solution for many users would be to use samba networking and share files directly through a local network between the PC and Mac in question). Additionally, the lack of official support suggests there could be the potential for something to go wrong, either in the form of kernel panics or even theoretical data loss on the NTFS drive. Accordingly, such a feature may be best as a last resort and should not be used with important data on the Windows drive without having adequate backups of those files.

Comfortable with all of that? Great, we’ll cover two different ways to enable NTFS write support in OS X, this must be used on a per-drive basis and it requires the usage of the command line.

Enable OS X NTFS Write Support Using Drive UUID
Though it’s slightly more complicated than the drive-name based approach mentioned below, this is really the best method for precision.

Connect the NTFS drive to the Mac, then retrieve the NTFS drives UUID with the following command string:

With the resulting UUID, use the following command to append the UUID with NTFS read and write support to /etc/fstab:

The NTFS drive will likely not appear on the desktop by default, but you can get access to it in the /Volumes/ directory by opening that folder in the Finder with the following command:

If you do want to see the drive on the desktop (assuming you have the desktop shown, of course), you can make an Finder alias with a symbolic link:

You can also use the experimental NTFS write mounting with a drive name rather than UUID, which we’ll go over next.

Enable NTFS Write Support with the Drive Name
For precision I prefer to use the UUID method, but you can also add NTFS write support by using the Windows drives name by using the following command:

Because this uses the sudo command you will need to enter an admin password to be able to execute the entire command properly. This command string is appending the drive name to the end of the /etc/fstab file, because /etc/ is a system directory you need to have superuser access to write to files in that directory, thus the requisite sudo prefix.

For example, adding read/write support to an NTFS drive named “WINDOWS8″ would look like the following:

If the drive has as complex name, use the UUID method mentioned above, or rename the NTFS drive in Windows before attempting to mount it with write support.

Again, you’ll want to look in /Volumes/ to find the newly mounted Windows NTFS drive with full read and write support. As mentioned already, it can also be helpful to create a symbolic link on the OS X Desktop to easily access the mounted NTFS drive:

There are a variety of easier but older tools to automatically complete the processes mentioned above, but the aforementioned NTFS Mounter utility seems to have stopped working post-Snow Leopard, and thus modern versions of OS X from Mountain Lion to Mavericks will want to use the command line approach instead. There are also third party paid apps available to provide NTFS support to OS X, which may be better options for enterprise environments where an experimental feature is not considered reliable enough to deploy

List item with multiple paragraphs in it:
 * First


 * Second


 * Third

List item with an internal link:
 * Baz

List item with an internal renamed, formatted link:
 * hhjhjk
 * kjlkjl


 * A Link Named Quux

List item with an external named link:
 * xkcd

List item with an external auto-numbered link:
 * 

Sequential list items and an empty list item with a paragraph following: Foo Bar Baz!
 * Last list item
 * No really, this is the last one
 * No, I really mean it this time.

Numbered list item:
 * 1) Foo

Sequential numbered list items:
 * 1) Foo
 * 2) Bar
 * 3) Baz

Nested ordered and numbered list items:
 * 1) Foo
 * 2) * FooFoo
 * 3) * FooBar
 * 4) Bar
 * 5) BarFoo
 * 6) BarBar
 * 7) BarBarFoo
 * 8) BarBarBar
 * 9) Baz
 * 10) BazFooFoo
 * 11) BazFooBar
 * 12) BazFooBaz
 * 13) BazBar
 * 14) BazBarFoo
 * 15) * BazBarBar
 * 16) * BazBarBaz
 * 17) * BazBarBazFoo
 * 18) * BazBarBazBar
 * 19) * BazBarBazBaz