Fatdog64-700/701 [April 22 2015] [CLOSED]

[Yoliano]

@watchdog

Thanks for your prompt reply. I have tried your suggestions with results as follows:
1 - Opened Alsamixer and setup my configuration. Closed Alsamixer. In Terminal I entered “alsactl store

[kirk]

can someone point me to the getjava script....I can't run 64 bit on my system.

Attached.

Every time after reboot, I have to operate Network Wizard(net-setup.sh) ->"Activate Settings now" to have it reconnect to my wireless access point.

It does not auto-connect.

Also, while net-setup.sh works, wpa-gui doesn't

I'll let James answer about net-setup.sh, but you said wpa-gui doesn't work. What's not working? Wpa-gui usually works pretty well. That's assuming you're using wireless and dhcp.

2 - Downloaded and unzipped Kirk’s “rc.services.gz

[tlchost]

can someone point me to the getjava script....I can't run 64 bit on my system.

Attached.

I get this error
Downloading Java 8u40 build ...
Cannot find build number, exiting.

[jamesbond]

I get this error
Downloading Java 8u40 build ...
Cannot find build number, exiting.

Change the line that contains "for p in $(seq 20 -1 1); do" to "for p in $(seq 40 -1 1); do". The last time I tried Java was at build 13 so I thought it was safe to start counting down from 20. The current one happens to be build 26.

EDIT:
@L18L - your launch_app_in_another_LANGUAGE from the first-run script earlier in this thread (dated Feb 2015) - does it supersede the one currently in L18L-goodies package (dated Jan 2015)? Or is that just a special version meant for first-run only?
EDIT: Nevermind, the Feb 2015 is now moved to base.

[L18L]

EDIT:
@L18L - your launch_app_in_another_LANGUAGE from the first-run script earlier in this thread (dated Feb 2015) - does it supersede the one currently in L18L-goodies package (dated Jan 2015)? Or is that just a special version meant for first-run only?
EDIT: Nevermind, the Feb 2015 is now moved to base.

Well done, thank you.

The content of $HOME/.fatdog/language is LANG
confused?

launch_app_in_another_LANGUAGE does what its name says.

Note, it is language, not LANG (<language_region>[@variant]).UTF-8.
ex: de is language, de_AT.UTF-8 is LANG.

Fatdog's big advantage is:
all availablel translations are in the one and only nls.sfs;
they can be used
- without the need to add locale (localedef)
- without restart of X server

Thus Fatdog can be run from the beginning in a language of user's choice (if nls is loaded or all the fatdog.mo are in base).

Yes, it can and should and will be used not only at first run.
One can use an alias, ex:

Code: Select all

alias q=launch_app_in_another_LANGUAGE

and use it: run gnumeric in another language

Code: Select all

q gnumeric

[L18L]

Code: Select all

# env | grep TERM
TERM=rxvt-unicode
COLORTERM=rxvt-xpm
# 
# rxvt-unicode
sh: rxvt-unicode: Kommando nicht gefunden.
# 

rxvt-unicode: Command not found.

It is urxvt, I know; but I would like to use $TERM.

[jamesbond]

The content of $HOME/.fatdog/language is LANG

Yeah, I should have renamed that variable to $FATDOG_STATE_DIR/locale instead of /language. I didn't know better, by now it's already entrenched. Next time we can make a big change is for 800 series.

Yes, it can and should and will be used not only at first run.

Thank you. I tested that, and it actually works - cool! Now the only thing left-over in L18L-goodies is the toggleLang rox-app.

It is urxvt, I know; but I would like to use $TERM.

You can't. $TERM does not represent the name of the binary, it represents the type of the terminal that you're connected to. It is just a co-incidence that the terminal type of xterm is TERM=xterm but this is not true in general. Use "defaultterm" instead; in Puppy you will have to find other ways.

@dbabits - I'd recommend you use wpa-gui if you can. net-setup.sh is more for fallback reasons. That being said, take a look at /dev/initrd.err after boot and see if you there is anything there related to wireless. I will also re-test net-setup.sh, I usually use wpa-gui myself.

[kirk]

****WARNING*****

In the repo you'll find some new packages built for qt5, such as vlc-qt5-2.2.1, ffDiaporama-qt5-2.2 and some others. The warning is that if you install ether the new vlc or ffdiaporama, the package manager will also need to install the package ffmpeg2-2.6, which will break anything that is compiled against the old ffmpeg.
In the future there will be a 710 release and right now we're thinking that will have qt5 replacing qt4, so that's why those packages are there. Also those packages have not been tested much.

[SFR]

sven

I noticed this problem before, but now know how to reproduce it:
1. Use volume or brighness +/- keys - XOSD displays info on the screen.
2. Use something that doesn't use XOSD (Alt+F2, Win+e, etc.)
3. Use vol/brightness again - XOSD doesn't work anymore, until sven is restarted.

What's interesting, if "Enable Frame" in XOSD options is checked, it doesn't happen, probably because the frame gets displayed always (as a small and empty rectangle in case if given shortcut doesn't use XOSD).

Anyway, having the above info and not knowing C I somehow managed to work around this issue.
I've added the following else statement in gtkosd.c:

Code: Select all

# diff -u old/gtkosd.c new/gtkosd.c 
--- old/gtkosd.c	2006-09-29 00:04:58.000000000 +0200
+++ new/gtkosd.c	2015-03-25 14:53:55.296414365 +0100
@@ -177,6 +177,8 @@
 
 	if(osd->debug_frame)
 		gdk_draw_rectangle (bitmap,fg_gc,False,0, 0,osd->width - 1,osd->height - 1);
+	else
+	    gdk_draw_rectangle (bitmap,fg_gc,False,0, 0, 1 - 1, 1 - 1);
 
 
 	gdk_window_set_back_pixmap (osd->darea->window, pixmap, FALSE);
# 

so the rectangle gets drawn every time, but if "Enable Frame" is unchecked, it's invisible.
Thanks to this XOSD keeps working.

Of course this is not a real solution, but the best I can came up with...

Greetings!

[jamesbond]

I know of this problem but I could not reproduced it reliably, thus I can't pinpoint the problem. Thanks for pointing and *fixing* this out. Patch applied, package rebuild, repo updated.

[Yoliano]

@kirk

Thanks for your response. Answering your question: No, the Master Volume does not return to my setting, but falls to about -12 dB. (Just checked again).

[L18L]

Now the only thing left-over in L18L-goodies is the toggleLang rox-app.

Feel free to move it into base ( or nls ? ).

As I am knowing now how to use sit
I would like to change it, sitting in the panel only, no desktop icon.

Should be activated, and makes sense, if one non-English locale is defined.

(Once upon a time I was looking in that "W" OS installed by a German language only user;
there was a language switcher [ not being used, but working , toggle by one click ] )

[jrb]

I see that there is an older version of conky in the fatdog64 repo

In fact, it was me who compiled and upload this particular version, because in newer versions transparency on ROX desktop doesn't work, unless we use some tricks like feh...
Anyway, it's always nicer to have such a functionality OOTB and on the panel...

I have recently been setting up a jwm-rox desktop in Porteus. I installed http://distro.ibiblio.org/puppylinux/pe ... 0-i486.pet but got no transparency, just black background. I solved it by inserting:

Code: Select all

<Background type="image">/usr/share/backgrounds/default.jpg</Background>

in my .jwmrc file as well as:

Code: Select all

<backdrop style="Stretched">/usr/share/backgrounds/default.jpg</backdrop>

in my rox pin file.

Sorry to comment so late, just followed a link here saying 0micko was back. Welcome back Mick!

[01micko]

Hi jrb

@jamesbond and kirk. A couple of pages back I reported failure of guvcview. It is a documented kernel issue that forced the maintainer to do a substantial rewrite for the 2.0x series, which unfortunately is still only gtk+3. It does work fine (2.0.3 version) if gtk+3 and supporting libs are compiled and guvcview built against that. I used PV's SlackBuild for 14.1.

Anyway, vlc can record webcam with audio, just takes a bit of fumbling around. I came up with a cute way to take stills using mplayer, but that is the topic of another thread when I release the script.

I found that you have cellwriter which is a nice solution for keyboard on the iconia w500 touchscreen. The Accelerometer is quite well supported too and I have automatic screen rotation working coutesy of a guy on the arch forum named Padfoot, who wrote a python script. I am in the process of porting that to C so that it can be used without the devx loaded. It's a shame that Xrandr is so clunky when rotating a screen though, but that's what we have, not much can be done about it.

The other problem though is input rotation. Theoretically, evdev supports long touch right click but this is broken. I'm going to gather more evidence and submit a bug report to the evdev devs. I even built the latest git version and the bug is still there. Xerrs.log repoprts that the right click option is loaded (when I have no files sourced from /etc/X11/xorg.conf.d/) but if I put in a 99-calibaration.conf with the correct cal and the relevant lines there Xorg.log reports that it unloads evdev! Padfoots script only works on rotating the input when evdev is only loaded. If wacom is loaded, right click with extra finger does work but PF's script won't rotate the input.

My solution to this is to call and external script (from my C code, similar to how zarfy does) to either cater for evdev or wacom, assuming evdev can get fixed.

It's fun.

[James C]

Dug an old box off the shelf so running Fatdog 700 live as a hardware check.

As expected audio,video and internet are all working on initial boot.

Code: Select all

-Computer-
Processor		: AMD Athlon(tm) 64 Processor 3400+
Memory		: 952MB (330MB used)
Machine Type		: Physical machine
Operating System		: Fatdog64 [700]
User Name		: root (root)
Date/Time		: Wed Mar 25 23:20:18 2015
-Display-
Resolution		: 1024x768 pixels
OpenGL Renderer		: Gallium 0.4 on ATI RS480
X11 Vendor		: The X.Org Foundation
-Audio Devices-
Audio Adapter		: ATIIXP - ATI IXP

Code: Select all

Multimedia audio controller		: Advanced Micro Devices, Inc. [AMD/ATI] IXP SB400 AC'97 Audio Controller (rev 02)
VGA compatible controller		: Advanced Micro Devices, Inc. [AMD/ATI] RS480 [Radeon Xpress 200 Series] (prog-if 00 [VGA controller])
Display controller		: Advanced Micro Devices, Inc. [AMD/ATI] RS480 [Radeon Xpress 200 Series] (Secondary)
Ethernet controller		: Broadcom Corporation NetXtreme BCM5751 Gigabit Ethernet PCI Express (rev 20)

Code: Select all

# free
             total       used       free     shared    buffers     cached
Mem:        952036     802680     149356      19072      67860     473144
-/+ buffers/cache:     261676     690360
Swap:            0          0          0
# 

[Billtoo]

Hi Mick,

Guvcview is working okay on my Fatdog-700 desktop and laptop
installations, I needed to change the Camera Output setting to BGR3.

[jamesbond]

@Billtoo: thanks for the confirmation.

@Mick - A couple of pages back I reported failure of guvcview.
Yes I read about that but forgot to respond. Like Billtoo, it works here too by setting rgb3/bgr3 as the output format. The last time I looked at it, the "new stuff" was about supporting webcam with x264 output. So if it does not work on yours, probably because your webcam only does x264 and nothing else. I tried to port newer gucview back to gtk2 but I quickly gave up when the diff between 1.7.1 and the recent ones became too great (which means I have to re-do the port from scratch).

@Mick - Anyway, vlc can record webcam with audio, just takes a bit of fumbling around.

Yes. Perhaps we can drop guvcview when it really stops working. I have looked at ucview too in the past, but at that time found that it was not easy to build (can't recall the reason).

@Mick - autoscreen rotation.

Glad you make it work. Basically the idea is to get the output from the accelerometer, determine the orientation and then drive xrandr and wacom/evdev orientation. If you can get the accelerometer output in shell then you don't need python for that.

I had similar script for my tablet (the previous meaning of tablet - which is "Tablet PC" - not the modern meaning of that) that used xrandr and xsetwacom. It was clunky too, but it worked. That was long ago, still in early 600 days I think. I think I also have a screen rotation script for XO-4, which was worked between me and Mavrothal. xrandr to set the screen, and OLPC-specific commands to change the orientation of the touchscreen.

@Mick - Theoretically, evdev supports long touch right click but this is broken

What a shame. xf86-input-evdev used to support this, I have this long-touch emulation as right-click working in XO-4 with older evdev. The Xorg team decided that this is too easy and went something else more complicated instead. So it no longer works for touchscreen (it still works for touchpad and mouse - try it. Annoying isn't it - they remove the feature where it is most needed but leave it for when it is not).

Since xsetwacom can set orientation too, perhaps you can convince padfoot to call xsetwacom instead of evdev?

@James C: I recently fired out my dual-core Atom N450 netbook with 1GB RAM to test with 700 too. Got similar results like yours. And if I extract out the fd64.sfs from the initrd, it uses less than 100MB RAM for the desktop, leaving the other 900MB for applications. Nice (50MB out of that 100MB is actually kernel modules, if you take that out too, you have the desktop running with only 50MB. I think that's not too bad for a frugal setup).

@L18L: I await your next development with "sit" ...

EDIT: Oh and since Barry is experimenting with UEFI, I am inspired to write my own story too, here: http://lightofdawn.org/wiki/wiki.cgi/SonyLinuxUefiBoot.

[jamesbond]

A new fatdog-update-700-noarch-1.txz package has magically appeared on the repo. This contains the latest Fatdog base scripts, suitable for installing via gslapt. Once installed, however, it cannot be uninstalled (if you try Fatdog will definitely stops working), but you can always update it continuously to get the latest update.

fatdog-update-700 will continue to be updated as long as updates are still compatible with the 700 base. It will end when we move to 710 (which is still in the far future) and then we will have fatdog-update-710.

This package only contains the updated scripts. It is *NOT* a service pack that contains all sort of updates. It does not add new binary packages or browser updates or kernel modules etc - it just provides update scripts, things like rc.services fixes, the new findnrun script, etc. It will not overwrite your preferences, wallpaper setting, openbox theme, etc - but if you have customised some of fatdog scripts, they will get overwritten.

You still need to update openssl, flash-plugin, etc to get updates for those critical components.

With this update, 701 may not happen unless there is a lot of demand for it.

[Pavan]

Seeing as you seem to be doing your best to make this as hard as possible for first time users , newbies and non linux users then could you at least add the relevant information with links in the first post on how a user goes about getting the latest up to date fixed version of fatdog , instead of scattering stuff around the thread in a half arsed way and expecting people to read every post let alone understand it ??

Considering in the thread you didn't understand which version of L18L launch_app to use you would have thought you would have understood what it is like for the non-experts with all these fixes.

Someone needs to say something even if it gets peoples backs up as blowing smoke up peoples asses doesn't achieve anything.

[L18L]

Seeing as you seem to be doing your best to make this as hard as possible for first time users , newbies and non linux users then could you at least add the relevant information with links in the first post on how a user goes about getting the latest up to date fixed version of fatdog , instead of scattering stuff around the thread in a half arsed way and expecting people to read every post let alone understand it ??

Considering in the thread you didn't understand which version of L18L launch_app to use you would have thought you would have understood what it is like for the non-experts with all these fixes.

Someone needs to say something even if it gets peoples backs up as blowing smoke up peoples asses doesn't achieve anything.

Keep cool, in

Fatdog64 64-bit GNU/Linux Operating System

Fatdog64 is an all 64-bit version of GNU/Linux built from source packages for Intel/AMD systems. Despite its 'fat' name (and a 'fat' dog icon), Fatdog64 is a small, fast, yet versatile operating system targeted for the desktop home users.

Run it in LiveCD mode, LiveUSB mode, install it 'frugally' to your harddisk or SSD, or run from and save changes to a multi-session DVD. Use it in 'throwaway mode' (no persistent data is kept - all things are wiped out after you reboot), or persist your personal settings and configurations across reboots using savefile or save directory.

Fatdog64 installation requires no dedicated partition. Fatdog64 will happily use existing partitions of other operations systems to store its system files and savefiles - it can even use existing NTFS partitions.

What's the obsession with 'Fat'? Why the name 'Fat' dog? Fatdog64 was originally derived from Puppy Linux, yet another fast, small and versatile Linux operating system for 32-bit Intel/AMD systems. Fatdog Linux (the precursor to Fatdog64) started as an "extended" or "fatter" derivative of Puppy Linux, including extras such as the complete Xorg, inclusion of large packages such as Firefox, Pidgin, Gimp, Kino, etc that made it larger (in terms of size) than Puppy Linux. Over the time, Fatdog migrated to support 64-bit platform (hence Fatdog64 name) and grew became an independent distribution of its own - while striving to keep the original spirit of Puppy Linux of being small, fast, and versatile. For a fuller history click here.

Fatdog64 700 series - the latest iteration of Fatdog64 - is hand-built based on recipes from Linux From Scratch, version 7.5 (the latest when the Fatdog64 700 alpha1, the first public release of Fatdog64 700, was released).

There isn't anything about first time users , newbies and non linux users
Hope that helps