Filename Used Quotes

Hastily created a decade ago and limited by primitive PC electronics, DOS did many frustrating things. Naming files was one of them. DOS restricted file names to a maximum of eleven characters, which had to appear like this:   xxmiller.tom   Because of this, people couldn’t give memorable names to their DOS files. It was preferable to call a file about a jazz trumpeter Miles or perhaps MilesDavis but DOS wouldn’t allow that. A file name must have no more than eight characters, then a period, then three characters. The nearest a DOS name could come to Miles Davis was MilesDav.isx. That wasn’t exactly easy to remember. With more powerful PCs and more planning, it was easy to create a program that allowed so-called long file names. OS/2 created files such as TomMiller or Holiday.On.Ice or any combination of 255 characters. But when someone using a DOS application, with its short names, tried to find a file bearing a long OS/2 name either in his own PC or from another PC, reached via a network, it wasn’t possible. The OS/2 files, if they had long names, were not visible through DOS (or Windows, for that matter, which then relied on the same file-naming technique). As a result, few OS/2 customers bothered to switch to long names. The short, inconvenient DOS names persisted. The

The function literal _.endsWith(_), used in the filesEnding method, means the same thing as: (fileName: String, query: String) => fileName.endsWith(query)

you could just write (fileName, query) => fileName.endsWith(query). Since the parameters are each used only once in the body of the function (i.e., the first parameter, fileName, is used first in the body, and the second parameter, query, is used second), you can use the placeholder syntax: _.endsWith(_). The first underscore is a placeholder for the first parameter, the file name, and the second underscore a placeholder for the second parameter, the query string.

1.1M    ./scripts 58M     ./cloud9 74M     . You can also use tee to write the output to several files at the same time, as shown in this example: root@beaglebone:/opt# du ‐d1 ‐h | tee /tmp/1.txt /tmp/2.txt /tmp/3.txt Filter Commands (from sort to xargs) There are filtering commands, each of which provides a useful function: sort: This command has several options, including (‐r) sorts in reverse; (‐f) ignores case; (‐d) uses dictionary sorting, ignoring punctuation; (‐n) numeric sort; (‐b) ignores blank space; (‐i) ignores control characters; (‐u) displays duplicate lines only once; and (‐m) merges multiple inputs into a single output. wc (word count): This can be used to calculate the number of words, lines, or characters in a stream. For example: root@beaglebone:/tmp# wc < animals.txt  4  4 18 This has returned that there are 4 lines, 4 words, and 18 characters. You can select the values independently by using (‐l) for line count; (‐w) for word count; (‐m) for character count; and (‐c) for the byte count (which would also be 18 in this case). head: Displays the first lines of the input. This is useful if you have a very long file or stream of information and you want to examine only the first few lines. By default it will display the first 10 lines. You can specify the number of lines using the ‐n option. For example, to get the first five lines of output of the dmesg command (display message or driver message), which displays the message buffer of the kernel, you can use the following: root@beaglebone:/tmp# dmesg | head ‐n5   [    0.000000] Booting Linux on physical CPU 0x0   [    0.000000] Initializing cgroup subsys cpuset   [    0.000000] Initializing cgroup subsys cpu   [    0.000000] Initializing cgroup subsys cpuacct   [    0.000000] Linux version 3.13.4-bone5(root@imx6q-sabrelite-1gb-0) tail: This is just like head except that it displays the last lines of a file or stream. Using it in combination with dmesg provides useful output, as shown here: root@beaglebone:/tmp# dmesg | tail ‐n2   [   36.123251] libphy: 4a101000.mdio:00 - Link is Up - 100/Full   [   36.123421] IPv6:ADDRCONF(NETDEV_CHANGE): eth0:link becomes ready grep: A very powerful filter command that can parse lines using text and regular expressions. You can use this command to filter output with options, including (‐i) ignore case; (‐m 5) stop after five matches; (‐q) silent, will exit with return status 0 if any matches are found; (‐e) specify a pattern; (‐c) print a count of matches; (‐o) print only the matching text; and (‐l) list the filename of the file containing the match. For example, the following examines the dmesg output for the first three occurrences of the string “usb,” using ‐i to ignore case: root@beaglebone:/tmp# dmesg |grep ‐i ‐m3 usb   [    1.948582] usbcore: registered new interface driver usbfs   [    1.948637] usbcore: registered new interface driver hub   [    1.948795] usbcore: registered new device driver usb You can combine pipes together. For example, you get the exact same output by using head and displaying only the first three lines of the grep output: root@beaglebone:/tmp# dmesg |grep ‐i usb |head ‐n3   [    1.948582] usbcore: registered new interface driver usbfs   [    1.948637] usbcore: registered new interface driver hub   [    1.948795] usbcore: registered new device driver usb xargs: This is a very powerful filter command that enables you to construct an argument list that you use to call another command or tool. In the following example, a text file args.txt that contains three strings is used to create three new files. The output of cat is piped to xargs, where it passes the three strings as arguments to the touch command, creating three new files a.txt, b.txt,

- ASM file can be copied to remote asm instance(diskgroup) using asmcmd command. SYNTAX - asmcmd> cp - -port asm_port file_name remote_asm_user/remote_asm_pwd@remote_host:Instancce_name:TARGET _ASM_PATH ASMCMD> cp --port 1521 s_srv_new21.dbf sys/oracle@172.20.17.69.+ASM1:+ARCL/s_srv_new21.dbf

What it is: You can mix phrases, unique IDs, and Folgezettel to come up with your own file-naming conventions – and/or add whatever other data you think is useful to your filenames. For example, you might start each filename with a Folgezettel code, add a useful phrase, and use a keyword or a unique character to help with other properties. For example, the note about Narcissus could be named “1a1a - Narcissus stared at his reflection - Example.” You’d have the Folgezettel code you created, a useful phrase, and the “Example” keyword could help you find various categories of notes. You could have in your filenames other categories such as Quotes, Facts, and Stories, which would help you find the right category of information to fill in the gaps as you write. Pros: The best part of mixing your own file-naming convention from a variety of techniques is you can customize it to your workflow. Cons: The worst part of mixing your own file-naming convention from a variety of techniques is there’s no end to how much time and energy you could waste tweaking it.