Code: Select all
BASESFS_COMPRESSION="-comp xz" fatdog-split-initrd.sh ...OK, that works, thanks.jamesbond wrote: If small size is really what you're after, you can always run the splitter like this:Code: Select all
BASESFS_COMPRESSION="-comp xz" fatdog-split-initrd.sh ...
That's the spirit!dr. Dan wrote:@jamesbond: Thanks for looking, and I am only intending to be helpful to someone.
Well for the first thing, I don't have BAT0, I have BAT1. I don't have "charge_now", but I do have energy_now. My laptop is a Vaio.Just for curiosity, since I really do not know that much about system stuff, what files are in your laptop's path "/sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0A:00/power_supply/BAT0/" (AKA the location of "$POWER_PATH/*/charge_now" on my systems? I had success on a Dell and a HP. I could try an Acer and an Asus, just to learn something.
I don't think it has anything to do with the versions. Just that different battery drivers (or ACPI) expose the same information in different way.I might be able to try running 702 and then 710 as a test, but it would be fairly inconvenient just now, so I'll ask for low expectations.
When you have installed it, the installer will create a file that you can run to automate the process; but it is highly recommended that you read the file before doing anything. There are several modes of Win7 installation, but I remember if you follow the common cases, you should be able to find that file in your C: drive when you boot to Windows. Did you see this file? What exactly did the problem you encounter?By the way, I installed FD710 on this HP using the Windows bootloader option, but it required a fair amount of research to learn how to configure the Windows 7 boot system to work. It was far from automatic!
Much welcome.Thanks as always.
This was in regard to your suggestion that I compare idle state between the two for battery consumption.jamesbond wrote:dr. Dan wrote:I might be able to try running 702 and then 710 as a test, but it would be fairly inconvenient just now, so I'll ask for low expectations.
Thanks, it is working fine. I read the instructions repeatedly, ran the .exe file, but it did not accomplish the install successfully, so I modified the necessary files myself. I don't have enough understanding to help with diagnostics.When you have installed it, the installer will create a file that you can run to automate the process; but it is highly recommended that you read the file before doing anything. There are several modes of Win7 installation, but I remember if you follow the common cases, you should be able to find that file in your C: drive when you boot to Windows. Did you see this file? What exactly did the problem you encounter?By the way, I installed FD710 on this HP using the Windows bootloader option, but it required a fair amount of research to learn how to configure the Windows 7 boot system to work. It was far from automatic!
Much welcome.Thanks as always.
Oh, right. Well if the difference is not too big and you're not much affected then perhaps it's just the variation I said earlier.dr. Dan wrote:This was in regard to your suggestion that I compare idle state between the two for battery consumption.
No worries. Feel free to contact me if you have any problems with that in the future. In writing OS installer for dual-boot systems, "safety is number one priority" - I would rather the installation fail, rather that it messes the original OS the point that it won't boot. I tested the installer against pristine Win7, things may have changed with SP1 release and whatnot.Thanks, it is working fine. I read the instructions repeatedly, ran the .exe file, but it did not accomplish the install successfully, so I modified the necessary files myself. I don't have enough understanding to help with diagnostics.
): Next release of Fatdog will no longer have /root/spot. It will be relocated to /home/spot. Compatibility symlink will be provided.Final thoughts
Fatdog64 710 is a good choice for a someone looking for a distribution to put on a flash drive to use on multiple computers. The distribution's savefile persistence feature is really easy to set up and use. Even if not using a savefile to keep changes between sessions, Fatdog64 ships with enough software to be able to do most general computing tasks. Document editing, browsing the web, e-mail, even playing a few games can be accomplished using this super small distribution. While I personally would have opted for a few different packages here and there, Fatdog64 has a good collection of software and should prove useful for many users.
Fatdog doesn't package Java anymore in the repo, because Java is often updated and you usually want to use the latest version.steff99 wrote:my next step was to install java jre 8. I had big problems with this as the package in the repo was only version 1.7
jre 1.7 is very outdated now and has 100's of holes in it.
time for an update perhaps?
my
The text-based network manager is meant for "more advanced" things like using static IP, etc.I noticed that fatdogs internet connection was done via a text base window.
Frisbee is faster, or the text-based manager is faster?this worked but it was quite different to using frisbee, and being able to connect much faster.
Suggestion noted, thanks.I would offer a suggestion to integrate frisbee into the pup for ease of use.
We tested XFCE a few years ago. At that time it was noticeably bigger, and slower, than openbox/rox combination. We may try again later on.I also love thunar file manager and the xfce desktop. I tired multiple times to get that working but it was impossible. perhaps a derivitive would go well?
drunkjedi's suggestion is right. However the built-in getjava.sh has stopped working for the latest version of JDK 8 now; (no) thanks to Oracle changing their download URL, grrrr. Download the attached package (remove the ".gz" extension), install it, and you'll get updated getjava.sh that works.drunkjedi wrote:Open terminal. Run "getjava.sh" (I suggest using this method as in terminal you can see if some error occurs and report it back here.)steff99 wrote:my next step was to install java jre 8.
Nice review!jamesbond wrote:Thanks for the info James C. That's very nice review
One of the "issue" is inability to install into UEFI systems. True while we have plenty of documentation on how to do, there is no automated GUI tool. Perhaps we should write one.
Sorry, I am not able to create duplicate entries.stemsee wrote:how to remove duplicate or any entry from fatdog-quick-locale-switcher?
Delete the corresponding directory in /usr/lib64/locale. (worked for me, zh_CN.utf8 deleted)stemsee wrote:how to remove duplicate or any entry from fatdog-quick-locale-switcher?
Code: Select all
# locale -a
C
de_AT.utf8
de_DE.utf8
en_AU
en_AU.utf8
en_US
en_US.utf8
fr_FR.utf8
POSIX
ru_UA.utf8
# Our friend Gobbi has posted an sfs file for xfce desktop in our contributed software thread.steff99 wrote:I also love thunar file manager and the xfce desktop. I tired multiple times to get that working but it was impossible. perhaps a derivitive would go well?
