Most hardware will need a BIOS update at some time and it's relatively easy to do. When you use Linux, however, you face an additional hurdle since occasionally upgrading the BIOS requires an installer that only works using Windows. Of course, no one wants to install a full Microsoft Windows OS just to spend less than 30 seconds to update the BIOS, then turn around and re-install Linux.
What if we could boot into Windows using a CD-ROM and run the win32 BIOS update program using that? Check out FalconFour's Ultimate Boot CD. The best source for it is his Facebook page or his Wordpress page. Those pages provide a link to download it via torrent or a direct link. The current version is v4.61.
Simply boot into the WindowsXP environment and run the BIOS installation program. It's that easy.
In my case, I was updating the BIOS of an HP 1120NR notebook.
Slashdot ran a story about getting Quake2 running in a browser windows. That is very cool.
There were installation instruction at quake2-gwt-port except the instructions were not for "Linux" but only for Linux distros that provide apt-get (probably Ubuntu). That is not cool at all.
While it would have been possible for them to write their HOWTO instructions in a generic way (provide a list of all dependencies, provide links to source code for needed apps not included in every Linux distro, etc.), they just assumed that everybody uses Ubuntu. Bad. Bad. Bad.
Here's what I needed to do to get it compiled and installed on my Mageia5 system. Read those Ubuntu-ed instructions first for the details. You should be using sudo to run commands that need root privileges. (All the following commands are written on one line even if they appear to be on multiple lines.) $ sudo urpmi mercurial ant gcj-tools javacc lame vorbis-tools $ hg clone https://quake2-gwt-port.googlecode.com/hg/ quake2-gwt-port $ cd ~/quake2-gwt-port $ sudo ant run This will install the original Quake II demo resources, build the client and server code, then run the server. Play Quake2 in your browser with:http://localhost:8080/GwtQuake.html It seems to run just fine in Firefox (as well as PaleMoon, QupZilla, very slow in Arora, not at all in Dillo) window. It doesn't run in very old versions of Firefox or possibly other browsers because of the opengl requirement.
Back in the early days of Linux, the changes to the Operating System were so
dramatic that even when updating withing the same distro, in-place point
release updates were problematic enough and it was always
recommended that a major version release be done from scratch. There
were just too many major changes to the underlying subsystems and
package naming conventions. Doing an in-place update was just asking for
Modern distros have matured quite a bit,
although there are occasionally some major subsystem changes being made.
Yet it's never been easier to do an in-place major version upgrade.
I just did the upgrade on several Mageia4 systems and the results were consistent and satisfactory, not to mention simple.
Always backup critical information. Have a Mageia4 recovery disc on hand.
You can always download an ISO image to do the upgrade rather than do an in-place installation if your Internet connection is slow. DO NOT attempt an upgrade from the Live ISO image as it will overwrite your existing system.
Reboot. You'll be using a new kernel, new glibc and so on.
$ sudo shutdown -r now
Run the package update command from Step 4 again. It should return with no packages needing updating.
Done. But . . . .
Do Some Checking.
$ cat /etc/redhat-release
$ cat /etc/issue
Those commands should return the information that you are running Mageia5. I did have an issue on one machine and $ sudo urpmi mageia-release-commonfixed it. You can also manually edit those version files in /etc to change the version number.
There are several Dynamic DNS clients available for Linux. I have never had them work satisfactorily with my DNS provider ZoneEdit.
It is possible to use wget to send the current IP address to ZoneEdit (all on one line, of course). $/usr/bin/wget -O - --http-user=USER_NAME --http-passwd=PASSWORD 'http://dynamic.zoneedit.com/auth/dynamic.html?host=DOMAIN_NAME.COM'
This can be run as any user.
I have found it useful to use cron to run it. Instead of a specific time, I just use the macro @daily in my crontab.
NOTE: ZoneEdit is migrating to a user key rather than a password and, while they are maintaining backwards compatibility for now, you should migrate as soon as practical.
It appears that "the cloud" is the popular buzzword now. All cloud computing is is a remote file server where you can store, access, share and manipulate your files. While several commercial services are available, it's possible to create your own cloud service using the ownCloud software. As with any powerful server software, it's not out-of-the-box easy, but with some preparation and understanding, it's not that difficult. Most of this HOWTO is Mageia-specific; a lot of the configuration details are enumerated at the ownCloud website documents.
We're installing ownCloud on a minimal Mageia4 virtual machine using VirtualBox just to go through the process. There is no X-server, so it's all done on the command line.
Mageia5 documentation, installation discs and Errata can be found here.
Part One -- Installing the Apache Webserver
We must begin by installing the Apache webserver. It's certainly possible to use alternative webservers, but Apache is most common. Getting a working Apache webserver is pretty straightforward.
1. Install Apache and some other related modules we'll need. Eventually, you'll want to configure ownCloud to use SSL, so install that module now.
$ sudo urpmi apache apache-mod_ssl
Note that we don't install apache-mod_dav since ownCloud supplies its own DAV module.
2. Use drakconf on the command line and choose the selection that allows you to configure the firewall to allow the web server (and the ssh server for system administration via ssh).
3. Set inint to run the webserver on startup.
$ sudo chkconfig httpd on
4. Start the webserver.
$ sudo service httpd start
5. Check to see that the webserver is working by pointing you browser to the server IP. I used the text-based lynx browser since there is no X-server on this machine.
$ lynx localhost
And it works!
Part Two - Install Useful Dependencies
Use urpmi to install the following apps. The ownCloud documentation explains why they are useful. You might as well do it now.
By default, the Mageia package installs ownCloud in /use/share. There's nothing wrong with that although some people prefer it to be someplace else and, with some care, you can move it wherever you like. What's important is that the user apache own all the files and directories associated with ownCloud. We do that by using:
$ sudo chown -R apache:apache /usr/share/owncloud
NOTE: When upgrading using URPMI, the file ownerships are changed but can be easily fixed as shown above.
It's also necessary to provide an initial configuration file. The easiest way to do that is to copy the example they provide. That leaves us with a pristine example file to examine if we need.
When we run ownCloud the first time, it will strip out all the comments and fill in some of the values during its initial setup.
Part Four - Setup ownCloud
Before you access the admin part of ownCloud, you must be logging in from an authorized fully qualified domain name (FQDN). This is allowed by editing config.php to add your FQDN. If you are assigned a dynamic IP address, you must use a dynamic DNS service to get access; it's a security feature.
Once that is out of the way, access the admin pages by pointing your web browser to http://your.server.address/owncloud.
The complete configuration is actually a little more complicated that this and I'll be adding links to documents that provide details, but essentially this is what you need to to do to get ownCloud running on Mageia4. It's just not as simple as "urpmi owncloud".
NOTE: In an older installation of ownCloud, I had some difficulty getting ownCloud 6.x to run reliably, but Mageia5 now offers version 8.X. If you need a version newer than Mageia provides, you can simply download the latest tar.bz2 package from the ownCloud site and replace the contents of /usr/share/owncloud, making sure to change the ownership to apache:apache as noted above.
Ubuntu has just announced that you can use Ubuntu to watch Netflix. They make it seem like Ubuntu is something unique and Ubuntu is the only way you can watch Netflix on Linux.
I use the Mageia distro of Linux, so that Ubuntu-specific mojo won't work for me.
Thankfully, it's not Ubuntu, but the beta version of the Chrome browser that has implemented DRM extensions for HTML5 video (along with a recent version of the NSS library, which Mageia has). All one need do is spoof the User Agent in Chrome to make Netflix think it's serving the video on a Windows platform and you are watching Netflix!
1. Download and install Google Chrome beta from here.
2. Install the User-Agent Switcher from here.
3, Configure the User-Agent Switcher to spoof the user-agent as Mozilla/5.0 (Windows NT 6.3; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/37.0.2049.0 Safari/537.36 by adding it to the Chrome profilelike this:
4. Log in to your Netflix account and enjoy the show.
5. No Ubuntu needed, just thank Nathan VanCamp.