|
Who's Online
We have 3 guests online
Tags
This will be shown to users with no Flash or Javascript.
|
|
Written by Jason Kendall
|
|
Monday, 20 July 2009 21:45 |
I went to pick up a USB->Ethernet net adapter for $9, but I wasn't sure it would work - Unfortunately, they didn't have any - So i'm delayed at this point.
My end goal is:
Have a LiveCD type boot from the SD Card so that No partitioning is required - problem with this is that the configuration would need to be saved - at this point, it appears as tho, the only config I would need to keep is the database connection details stored in /etc/mythtv/mysql.txt and /etc/mythtv/config.xml (which may not be correct).
So - Using the Homebrew Channel, you'll be able to load up the .elf file, which boots a LiveCD, the LiveCD will mount and check for a config on the SD Card which will then create the required config files. All this, while looking pretty.
Another thing I need todo is strip out all the things we won't be using from the Linux Distro I'm basing this off of - thus making it as small as possible.
A quick reminder, that you will need a USB Network adapter, because, at this point the linux kernel does not support the internal wifi adapter. Secondly, it should be noted that the Wii will only run in USB 1.1 mode - Thus, limitting to 12MB/s.
|
|
Written by Jason Kendall
|
|
Saturday, 18 July 2009 23:34 |
Ok - So, I've been waiting around for someone else to build a working mythtv front end for the wii, using home brew.
To say the least, I have up waiting and did it myself ;)
I took a basic Linux stack for the wii, found OOC deb packages and manually installed them into my SD card, tracked down and install all the required libs and well - to say the least - WIIIIIIII I have a mythtv front end, almost.
Unfortunatly, all the USB ethernet addaptors I have don't seem to work on the wii with linux - so I'll need to go pick up one of those to confirm that this is working. Once I get to confirm it's working, I'll preatty and clean it up build some tgz's of it and provide some details on how to install it.
Keep checking back here to see my progress!
|
|
Written by Jason Kendall
|
|
Sunday, 22 March 2009 19:33 |
|
And thanks for all the fish? No, wait.. wrong book ;)
Yeah, it's been a while since I updated. Mostly due to other projects - and nothing in those projects to really write about. I do have a few news projects that some readers may be interested in;
Silent-Chaos - This website is being built to share information relating to security issues. Notifications, and other cool tools will be made available as I have time to build them.
If you happen to be on twitter, You can also follow silentchaos for important security alerts - mostly FOSS projects I either use or know people that use. But someday i'll have a team to post all kinds of alerts.
|
|
Written by Jason Kendall
|
|
Wednesday, 07 January 2009 21:51 |
I've been working on a special project.. one that requires the building of multiple virtual machines on the fly. My VM of choice (as seen in previous entries) is Xen.
Part of my requirements is the ability to have a base image of a root drive, then have each of the dynamic VMs have their own dynamic image based on the original. One, if they wanted to, and had the space - could just copy the drive image multiple times. And this would work.
Fortunately, there is a better way. Copy-on-write disks are disks that write changes from a base image to a separate file. Thus, reducing the overall usage. This is what I want.
Xen wiki has multiple solutions to doing this, however, I wanted something simple, and supported at the xen level. This left me with qcow files.
In order to save some people some time. I wanted to describe how I went about getting the images to work -- pain for me, means less pain for you in the long run.
To make a long story short:
- Created a image with dd (see previous posts)
- Made my changes to the image
- used "qemu-img convert -O qcow2 (base-img) (qcow-img)" to convert the image to a base qcow format
- built the actual qcow files with "create-qcow (image-size) (container-qcow) (qcow-img)"
Some notes:
- When building your base image with dd - it CAN NOT be a spare file (meaning using the seek) it must be a full img
- img2qcow does not work! (or at least it didn't for me)
Some errors you might see
- Failed to write new L1 table (Usually after: Converting image to big endian L1 table)
- Your using qcow files, not qcow2 - probably because you used img2qcow or -O qcow with qemu-img
- QCOW Open failed
- You may have used qcow-create, but referenced a raw image - not a qcow image.
- XENBUS: Waiting for devices to initialise
- One of your devices didn't init in dom0 - look at /var/log/syslog to find the error in your ways
|
|
Written by Jason Kendall
|
|
Monday, 29 December 2008 00:26 |
A little back ground: I like Xen - works (almost) great on my hardware. However there is a few bugs that still exist in the Ubuntu kernels, that newer kernels don't have. I've been told (via IRC) that SUSE (Open in my case) has some of the best support for Xen in it's kernels. So I'm documenting my Jurny in updating my Ubuntu Xen machine's Kernel to a newer OpenSuse Kernel:
First off, You need to download the new RPM from the website. The following link will give you a list of Xen Kernels for the [Almost] latest version of OpenSuse: http://software.opensuse.org/search?baseproject=openSUSE%3A11.0&p=1&q=Kernel-xen Look for the one with the highest number - At this time it is: kernel-xen-2.6.25.20-13.1.i586.rpm
Download and extract the RPM into a temp directory: (Need to figure this one out - I use Midnight Commander, and I was able to enter the RPM, then enter the CPIO file, extracting tha data from there)
Once you have the extracted Directories (/boot, /etc, /lib, /usr) copy them to the root drive. There shouldn't be any duplicate files.
Ubuntu provides two scrtipts you need to run next;
- Create a initrd.img file for the kernel by running: update-initramfs -k [kernel name] -c
- Look for the installed System.map file to find the name, in this case it is 2.6.25.20-13-xen
- Update your grub by running: update-grub
[At this point, I did things in the wrong order so I Crashed, I'll update this after I test again.]
Update 1:
- I just rebooted the server after re-running the update-grub command. This time, I got a full boot, but Xend didn't seem work. I'll need to work on this issue next. |
|
|
|
<< Start < Prev 1 2 3 4 5 6 7 8 9 10 Next > End >>
|
|
Page 3 of 14 |
|
