Linux.com

Community Blogs



April fool's post-day report

In the night of the 31 (overlapping over the morning of the 1rst), I was on an assignment about Windows Server 2008. It's a rather though assignment - I'll spare you the details, but we basically go on a hunt on MS' Web site to determine the qualities behind WS2008's architecture. So, I was hunting in the dense forest that is WS2008's Web site and compiling OpenOffice 3.2 in background. When I was trough with the compilation, it was about 12:30, so I decided to go to bed.

I was a bit sad because I didn't have the time to elaborate complex pranks for April fools day. Then, it came to me. Considering the amount of sleep I was going to get, I'd probably be very tired in the morning in the classroom. Some people would then ask me why it is so. And I'd have a plan.

"-You yawn a lot today.

-Yea, got to sleep early this morning, had a lot of stuff to do.

-Really? What where you doing?

-Oh I spent the night scrapping my Gentoo installation to put Windows Vista instead."

Have you ever seen a brain freeze? I did. I saw the hourglass.

"-APRIL FOOLS!

-OH! Er, I thought it didn't make much sense!"

I tried later in the day with my friend in the math class, the reaction was pretty much the same, but he got out of the loop faster. His brain probably ended up telling "false" faster than the first victim.

So, it was a rather satisfying result in the end of the day - despite I only tricked 2 friends. I should probably go to sleep now!

 

Plain Text, Archiving, and Presentation Fidelity

My introduction to computers was as a hobby. My first computer had Microsoft Works for MS-DOS version 1.05 installed on it. Among other things, I decided to use the computer to keep a journal. It was perfect. I could do all my writing on the computer and even edit the text without wasting paper.  

What was even better, I could store my journal on floppy disks, which are more durable than paper.  

Several years later I decided to open and read the journal I wrote on that first computer. I no longer had Microsoft Works, and the word processor I was using by then could not open my journals. I learned my first lesson in proprietary file format lock-in that day.  

I failed to consider the long-term consequences of storing documents in proprietary formats, or even to consider formats at all, really. I sacrificed those concerns in favor of the editing and storage efficiency of computer-based vs. paper-based documents.  

I immediately searched for a format that could work across applications and operating systems (I was using OS/2 by then). I tried various formats with varying degrees of failure. The only format that worked 100% of the time was plain text. It was also clear to me that this format was likely to continue working well into the future, because it had already been in use from well into the past (in computer time).  

It was also the only format that worked with 100% of the programs that offered text editing capabilities. It didn't matter if I used a word processor or a text editor, and it didn't matter if I used a Microsoft operating system or one from some other vendor.  

I recognized even then that the file format of Microsoft's office software chained its customers to its platforms and that entrusting data to proprietary file formats put it at risk. I refused to use word processor formats for anything I wanted to preserve long-term.  

But this created other problems. If I wanted to print a document, I still had to use a word processor, and if I wanted to store that document long-term, I had to keep it in plain text. I was not aware of typesetting systems like LaTeX at the time. So, I saw only two options. I could keep two versions of my document on the computer.  One could be plain text and the other a word processing file format of some kind. Or, I could keep a plain text version on the computer and a paper copy.  

The first option had the advantage of allowing me to store the document entirely on electronic media. But this still had one major drawback. The visual representation of the document could not be preserved long-term.  

The second option had all the disadvantages of paper documents, with the added drawback of separate storage for the plain text computer file from its printed version. But, its visual representation was far more durable.  

The long-term office document storage problem is now being addressed by Open Document Format. In my opinion, it still has not proved itself an equal of plain text in solving that issue, let alone the issue of cross-application fidelity. Until it solves the second issue, long-term preservation of the printed appearance of office documents will remain out of reach.  

Portable Document Format helps address this issue, but it fails to address others. Paper manuscripts often have notes in the margins, stricken text and other, additional information attached to them that PDF documents cannot preserve. Word processor files are better at preserving these details than even plain text files, unless additional formatting is used that preserves the plain text-i-ness of such files while enabling meta-information to exist inside of them. For these and other reasons, plain text has gained a reputation as an inferior format to word processing file formats among many users.  

But, in recent years the Internet has elevated the status of plain text. The promise of the World Wide Web was that collaborative publishing would be open to all. This vision, held by its original creator, was not realized fully until the invention of wikis and blogs. And these do not rely on the features of word processors, but work with formats that are entirely dependent on plain text. Word processors, with their paper-centric interfaces and output medium, are increasingly becoming obsolete as this new publishing paradigm takes hold.  

But, ordinary authors are not necessarily savvy in the use of HTML and other markup systems used on the World Wide Web. For this reason, simplified markup languages were created that remove the requirement to know HTML in order to use wikis and blogs.  

The problem was that different systems used different markup, and one had to learn different markup on each website for which there was a different markup system in place. This was an added source of confusion.  

To address this issue once and for all, even simpler markup languages and utilities were created that would translate its syntax into HTML and other markup systems. One such utility is txt2tags. Its syntax can be translated into HTML, several wiki formats, and LaTeX, which can be translated into PDF. And it allows embedded comments, which addresses the issue of author notes and other information that is not part of the final document.  

Another utility that partly addresses this issue is Markdown. Markdown borrows from conventions used in email messages and adds additional features to format text. It converts its syntax to HTML. This allows users to create valid HTML documents with a syntax familiar to them from reading email.  

There are other markup systems, such as reStructured Text, that go farther than Markdown does to produce multiple output formats. They all have advantages and disadvantages. In my opinion, txt2tags has the advantages of offering multiple output formats in addition to HTML and is aimed at a wider audience than Markdown or other systems. By storing a txt2tags document with its LaTeX and PDF versions in a single archive, document text, notes, and the visual representation may be preserved over a long period of time. It can also produce HTML and various wiki markup from the same source document. It may not be a perfect solution, but it goes a long way toward that solution.  

These utilities preserve plain text without sacrificing presentation.  They let you have your cake and eat it too, instead of forcing you to choose one or the other.  

Ironically, plain text, the archaic format looked down upon during the rise of the word processor and its potential to lock customers into a single vendor's product, is the format best suited to unseat the word processor from its dominant position. Word processors are a relic from a pre-networked world dominated by printed documents. They are ill-suited to today's instantly-published, Internet-connected, platform-neutral world where a document is more likely to appear on a blog or a wiki than to be printed.

 

Windows 7 compatibility

Well after helping develope windows 7. I've not been disappointed.  I can run LINUX VMs and multiboot without any problems. Kubuntu is my current favorite, but I've been looking at a few other flavors to try. I love that I can still make KDE look like mac's GUI. It's hilarious to see my friends think I'm using Mac/OS only to find that it better! It's LINUX!

 

Configure Arch Linux - rc.config


In my installations of Arch Linux, I found that file the most complicated to configure.
So I'm sending mine to serve as the basis for those trying.

#
# /etc/rc.conf - Main Configuration for Arch Linux
#

#
# -----------------------------------------------------------------------
# LOCALIZATION
# -----------------------------------------------------------------------
#
# LOCALE: available languages can be listed with the 'locale -a' command
# HARDWARECLOCK: set to "UTC" or "localtime"
# TIMEZONE: timezones are found in /usr/share/zoneinfo
# KEYMAP: keymaps are found in /usr/share/kbd/keymaps
# CONSOLEFONT: found in /usr/share/kbd/consolefonts (only needed for non-US)
# CONSOLEMAP: found in /usr/share/kbd/consoletrans
# USECOLOR: use ANSI color sequences in startup messages
#
LOCALE="pt_BR.utf8"
HARDWARECLOCK="localtime"
TIMEZONE="America/Sao_Paulo"
KEYMAP="br-abnt2"
CONSOLEFONT=
CONSOLEMAP=
USECOLOR="yes"

#
# -----------------------------------------------------------------------
# HARDWARE
# -----------------------------------------------------------------------
#
# Scan hardware and load required modules at bootup
MOD_AUTOLOAD="yes"
# Module Blacklist - modules in this list will never be loaded by udev
MOD_BLACKLIST=()
#
# Modules to load at boot-up (in this order)
#   - prefix a module with a ! to blacklist it
#
MODULES=()
# Scan for LVM volume groups at startup, required if you use LVM
USELVM="no"

#
# -----------------------------------------------------------------------
# NETWORKING
# -----------------------------------------------------------------------
#
HOSTNAME="Arch"
#
# Use 'ifconfig -a' or 'ls /sys/class/net/' to see all available
# interfaces.
#
# Interfaces to start at boot-up (in this order)
# Declare each interface then list in INTERFACES
#   - prefix an entry in INTERFACES with a ! to disable it
#   - no hyphens in your interface names - Bash doesn't like it
#
# Note: to use DHCP, set your interface to be "dhcp" (eth0="dhcp")
#
eth0="dhcp"
INTERFACES=(lo eth0)
#
# Routes to start at boot-up (in this order)
# Declare each route then list in ROUTES
#   - prefix an entry in ROUTES with a ! to disable it
#
gateway="default gw 192.168.0.1"
ROUTES=(!gateway)
#
# Enable these network profiles at boot-up.  These are only useful
# if you happen to need multiple network configurations (ie, laptop users)
#   - set to 'menu' to present a menu during boot-up (dialog package required)
#   - prefix an entry with a ! to disable it
#
# Network profiles are found in /etc/network-profiles
#
#NET_PROFILES=(main)

#
# -----------------------------------------------------------------------
# DAEMONS
# -----------------------------------------------------------------------
#
# Daemons to start at boot-up (in this order)
#   - prefix a daemon with a ! to disable it
#   - prefix a daemon with a @ to start it up in the background
#
DAEMONS=(syslog-ng dbus hal network netfs crond alsa gdm fam vboxdrv)


# End of file

 

 

 

movie player part 2.... making it permanent with Brasero Disk Burner

When I showed my husband the film clip, he liked it and said that we should make a copy... so I decided to give Brasero disk burner a try. I have used it to make copies of photos, but not movies. So, I put a blank dvd disk in, and then followed the directions given when starting the application. No different, or difficult than with photos. I now have a permanent copy. We should make copies of anything important... just in case... something happens, like the OS crashing.. (I know, those things only happen with other OS's :?  ) well, to have just in case you upgrade and want to keep extra copies, or if your PC  breaks down, or whatever.

At any rate Brasero Disk Burner is good for photos, data, and movies.... as well as audio. Sound, and image is good.  It is fast too.

 

Movie player... ( personal)

During the Christmas holidays, I had taken some film shots with my digital camera. It was the first time I had tried this and wasn't sure whether it would work. I opened it with Movie player and was able to see the shots, however short.  This was important, since they are of my father in law who is now 98 years old. They may be the last such shots of him singing.  Thank you Linux/ Ubuntu for making it easy for me to do this.

 

Web Design Job And A Story Of Diabetic Boy.

I am currently work for Malaysia web design firm and we also done some web marketing services such as backlink building, press release distribution and writing, etc. I love what I doing right now because it's giving me more free time hanging out with my family. We usually works online but they do have office in Malaysia called Global Empire Enterprise. Beside working for the company, I also doing my own research and writing articles about diabetes warning signs. I began to built the diabetes site because of an inspirational video posted by a young diabetic who have been diagnosed for Juvenile Diabetes since he was 1 years old. The video was very touching that I drop my tear every time I remember about it. The young boy explained his life by capturing pictures of him and his families. It still fresh in my mind. The boy keep on going strong even though there's losing day or night for him. I am not a diabetic but after watching the video, it makes me wonder how fortunate I am. However, I found out that a lot of peoples being ignorant about this topic. It is believe that diabetes is included into Top 10 Killer Disease. Millions of peoples are dying from this disease and it's rising every year. Why are we being so ignorant about this disease? I hope you people out there can be more alert about this disease.

Regards,

Debra.

 

Urgent: Help Shawn Powers & Family

Today is a day of grief for Linux Journal. This afternoon, Associate Editor Shawn Power's home burned down...

Read more... Comment (0)
 

Read Me First

First of all, hello.

Well, that wasn't so bad. Some say that the first step is the harder. For me, it's my third attempt at a blog. So it is my third first step. My first one was a disaster. I dare you to find out my old blog. My second one was absorbed into the abyss of the recent economical crisis, never to be found again. Hopefully, this one will be able to fly a little better.

Read more... Comment (0)
 

no comment

Just out of curiosity, I tried to download Windows Media Player 11 with Wine. I watched anxiously as the files unzipped, hoping, wishing... that it would work. Just when it got to where it was ready to download to my computer a message appeared asking for authorization code.  It is the first time I have seen this in a program. I can understand in updates, but this is just a media player. Maybe MS is  trying to make it harder for those who have copies of an OS, instead of the original. In any case one more reason to switch to Linux.
 

In the Beginning

Hello and welcome to my first blog, please feel free to feedback any information that might help me improve my next blog entry.

Read more... Comment (0)
 
Page 5 of 14

Who we are ?

The Linux Foundation is a non-profit consortium dedicated to the growth of Linux.

More About the foundation...

Frequent Questions

Join / Linux Training / Board