gcmartin wrote:Again, the primary change, this time, was to NOT install all of the PETs required for this version to replace my older FATDOG520
What were the pets you installed that caused the startup to fail?
Atle wrote:I have set the login graphical and as root with a new password,
I still get the same message. Can only install as root...
That, even if I do log in as root.
Don't do it from the browser. In Fatdog the browser runs as unprivileged user "spot" and doesn't have the rights to install pets.
Download it, use Rox to open the folder that contains it, then (double-)click it.
liboicl wrote:To elaborate on my mouse issues, which for some reason have now transferred to 6.0.1. I am unsure if this is even related to fatdog anymore. Anyway, when the OS boots my mouse and keyboard lights go off.
For whatever it is worth, I had specific problems with a particular mouse and a particular laptop. Fatdog+that laptop+that mouse = not working. "dmesg" would show messages as if the mouse as constantly plugged and unplugged. Change any of the combination - works (ie, Fatdog+mouse = works on another laptop, or Fatdog+laptop = works with another mouse, or Windows+laptop+mouse = works)... Go figure
kirk wrote:
Ted, I think James has that, but he's out of town for a while.
Thanks kirk.
Yes, sorry I forgot. The source is here:
ftp://ftp.berlios.de/pub/cdrecord/alpha ... 13.tar.bz2 and I have uploaded it to /source/c too just now.
prehistoric wrote:There are two separate questions here: 1) desired behavior, in terms of searching subdirectories;
I remember we discussed this before but google refused to help me
anyway, Fatdog by default only searches the root directory of every drive. If you want it to search sub-directories as well, add the "search=n" parameter (root directory is "level 1", so to search one directory depth, you use search=2). Remember that searching is slow and that's the main reason why Fatdog only searches at the root directory. When you install Fatdog you're to know where the savefile is, and it is best to tell Fatdog about it. And if you don't know how to create the obscure boot parameter - as rcrsn51 point out, there is a useful tool in the control panel.
2) consistency between separate user interactions. Having a GUI for creating a save file doesn't help much if you need to write obscure bootloader code to use it. Shouldn't the default action be to look in the directory where the kernel or initrd resides? If the user explicitly chooses to place the savefile elsewhere couldn't a flag be passed to indicate this?
No, because there isn't any logical place to keep this information. In fact, as far as I know, there is no way for a running kernel to know the original location of its own "vmlinuz" binary ... (other than by hacks and by searching *all* disks - but then it can still fail to find it ...)
If a flag file already exists next to the kernel and initrd, the new location could be added to a list for the user to choose from at boot time. There would be no searching for locations not used by some savefile.
It actually involves searching as well, that is, searching for that flag file. In addition to be unreliable - searching is, as discussed above, slow.
This would be particularly useful for testing multiple versions, as with the experimentation going on now with proprietary drivers.
With grub, grub4dos or syslinux, one can always specify the default boot parameters and edit it / modify it at every boot.
Yes it is probably more troublesome than if the handholding is done by Fatdog itself (by a menu etc), but I would prefer to focus on fast everyday performance rather than ease of experimentation - after all (for me at least) I use Fatdog as my *primary* operating system.
Flash wrote:First off, I discovered that I can't choose any of the boot options - it doesn't yet respond to my USB keyboard at that stage of the boot process...
Flash, what's the brand of your keyboard? Fatdog has a few drivers for generic HID devices built-in, but they keep inventing new ones...
Also, I can no longer copy by highlighting text in Geany, then paste the highlighted text into a console window (either rxvt or xterm) by simultaneously clicking the left and right mouse buttons.
There is a way. You need to install xinput, available from x_misc_tools from the package manager. Basically you can use xinput to enable the 3button-emulation on the fly. I can guide you with the rest of the steps later on if you're interested.
is there anything that can give you the correct way how to use the aboriginal cross compiler or uclibc buildroot. because I've tried them but always failed.
This should be discussed in the Programming forum, but anyway ... the aboriginal cross compiler is here:
http://www.landley.net/aboriginal/downloads/binaries/ and how to use them is explained here:
http://www.landley.net/aboriginal/downl ... ies/README. How to use Buildroot is explained here:
http://buildroot.busybox.net/downloads/ ... anual.html. The binaries were built with unpatched original sources.
cheers!