Fatdog64 702 Final [7 Feb 2016] [CLOSED]

[step]

Does momanager work in fatdog 702?

When I tried, a po file wasn't created by Geany.
_________________________________________

I don't know if it works, but I know that L18L uploaded an updated version to the Fatdog64 repo in mid April. Update from package manager if you already haven't.

[don570]

Ah Yes.. Here it is. I'll test it out.
http://distro.ibiblio.org/fatdog/packag ... arch-1.txz

__________________________________

[L18L]

Ah Yes.. Here it is. I'll test it out.
http://distro.ibiblio.org/fatdog/packag ... arch-1.txz

__________________________________

Oh No.
After update of gslapt you should find momanager- 20160410-x86_64.

Feedback highly appreciated.

[don570]

Here it is..

http://distro.ibiblio.org/fatdog/contri ... 64-PET.txz
_______________________________

[prehistoric]

I just tried to update Firefox to 46.0 due to some serious vulnerabilities recently revealed. Looks like the update script wasn't smart enough. At the moment I'm running Google Chrome. This naturally allows all of Google's adware to get through. I've been running NoScript on Firefox.

I will try installing gtk-3 separately to see if that fixes the problem.

[Belham]

Prehistoric,

Did you figure out the FF v46 problem? How do we install gtk-3? I mean, the gslapt packge manager doesn't bring anything back when I enter either "gtk-3" or "libgtk-3" or any variation thereof. I was able to update my Tahr64 6.0.5 CE USB sticks by just typing "libgtk-3" in the PPM, and it brought back the gtk-3 stuff needed for install to make FF v46 run smoothly (mainly the gui interface, versus the pre-FFv46 that used python).

I am a bit unsure how to go about getting gtk-3 into fatdogs (either the 702 and/or the 710). Do we have to compile the gtk-3 stuff ourselves, before we can load it?? That sounds like a headache as I wouldn't have the slightest idea where everything goes for gtk-related install.

As you, right now I've defaulted back to Google Chrome (which I hate because of all the adware and tracking), but I keep Chrome only for when I wanted to watch Netflix. I just downloaded Palemoon64 bit, installed it on Fatdog64-710, and went into about:config and closed off everything I could to make more hardened than normal, but it still is not addressing everything that FF v46 is regarding recent security issues found.

If you get gtk-3 installed and FF v46 working, would appreciate any tips and/or advice. I even downloaded the FF v46 tar.bz2 directly, tried to install it that way, but it plain refuses to run without the gtk-3 needed.

Thanks.

[jamesbond]

Sorry, we don't have gtk3 libs for 702. I just built one for 710, but don't have enough energy to do the same for 702.

[01micko]

Sorry, we don't have gtk3 libs for 702. I just built one for 710, but don't have enough energy to do the same for 702.

EDIT

I have packages I compiled in FatDog64-700 a while ago!

They *should* work to get firefox>=46.0 going in FatDog -700,701,702 (works in 700)

http://01micko.com/fatdog64/at-spi2-atk ... 6_64-1.txz
http://01micko.com/fatdog64/at-spi2-cor ... 6_64-1.txz
http://01micko.com/fatdog64/gtk+3-3.8.2-x86_64-2.txz

c83d8a4aed663bcd805f9287828e1a5e at-spi2-atk-2.8.1-x86_64-1.txz
84caaa909deb8cc6cd85a3c8ba0cf121 at-spi2-core-2.8.0-x86_64-1.txz
727b24466c6712d172bbe6c766af6d0a gtk+3-3.8.2-x86_64-2.txz

-------------------------------------------------------

Original stuff below

Slackware64-14.1 gtk3 packages *might* work in 702 - I'll just check the dependencies - I know at-spi is one...

OK, here is the list -

+at-spi2-atk,+at-spi2-core,+atk,+bzip2,+cairo,+cxxlibs,+gcc-g++,+dbus,+expat,+fontconfig,+freetype,+gcc,+gdk-pixbuf2,+glib2,+harfbuzz,+icu4c,+libICE,+libSM,+libX11,+libXau,+libXcomposite,+libXcursor,+libXdamage,+libXdmcp,+libXext,+libXfixes,+libXi,+libXinerama,+libXrandr,+libXrender,+libffi,+libpng,+libxcb,+openssl-solibs,+openssl,+pango,+pixman,+util-linux,+zlib

Probably only need +at-spi2-atk,+at-spi2-core, and of course gtk+3-3.8.2-x86_64-2.txz as I believe others are in FatDog64.

YMMV, and I might get back to this later with a real test.

[prehistoric]

01Micko's suggestions worked. I am now running Firefox 46.0, though my experience with major updates suggests this will not be stable until about 46.0.2.

The longer-term problem of being able to do anything safely on the Internet without becoming a wholly-owned subsidiary of some monster corporation remains.

Just how bad Internet security problems are is highlighted in some recent publications which show the U.S. Secret Service, EU CCC and UK CERT have suffered data breaches. At the other end of the spectrum there are still banks with unattended ATMs running Windows XP and connected to telephone lines.

One might also point out that the average web page now has more code and complexity than the early computer game appropriately titled DOOM. No telling what this will mean for the coming Internet of Things That Go Graunch in the Night.

As always, I forecast strange lights in the skies, earthquakes, tidal waves, monstrous births, and the collapse of civilization as we know it.

[Belham]

I got FF v46 working in both Fatdog64-710 (thanks to jamesbond's gtk-3 upload today) and also saw Micko's post for 702, and it works great.

As far as being "safe" on the Internet anymore, given how the Internet was originally designed (to be open, non-encrypted, etc,etc), something is going to have to change over the next few decades. It is spooky at how good coders/blackhats are becoming at standing in the middle of everything, without ever having to infect either end of, say for example, a bank transaction. He!!, the only thing I feel safe with nowadays is using U2F for email (and soon for banking), where I at least get a sense that I am not only relying on a twisted, contorted login name and even more, twisted, contorted password I've conjured up (and have to change religiously every month or so just for peace of mind). Login pictures and/or your own personal logo (as are logins & passwords) are a joke compared to U2F. As much as I hate Google, they are at least correct in pushing this (U2F) and a decent few Gmailers are finally adopting it. Google/Gmail just needs to drop the whole cellphone verification thing for Gmail to become 100% secure in terms of a user accessing it and their email. Now, them protecting your account safely is another matter entirely, lol. Besides, regarding the safety and the Internet, everyone knows a gut-wrenching attack (in terms of not millions, but hundreds of millions if not a billion or two disappearing from a large online bank's users collective accounts) is coming. It is just a matter of when, not if. And it will be another 2009-stock-market-mortgage-debacle event that will set the U.S. economy, Fed Reserve and fin'l markets back on their collective heels and will scare the beejeezus out of everyone. Only then we will see encrypted digital currencies truly take off.

[jamesbond]

@01micko - my sincerest thanks for rescuing 702 users

First post updated with link to Mick's post.

[quirkian2new]

@01micko, thanks
successfully run Firefox 47 on my Fatdog701 after install your 3 files.

[Atle]

Just since i found a copy of Civilization VI in my drawer like a few days ago, I wanted to try it out under Fatdog/Wine...

At first glance it seemed to work, but after installation it all stopped.

Now of course playing windows games in Puppy is not a right nor a real support issue, but its a bit fun since i intend to bring it live using Wlanmaker in order to make a gameserver out of it(among other things and projects)

So I wonder... Are there others out there that plays either Civ 4, 5 or 6?

Just so we could hook up and maybe get it to work?

Never used Wine before and never played Civ neither, but its a intriguing idea to sort of find good games that can run as server and then combine it with Wlanmaker that works great under Fatdog.

If Linux is going to be the worlds favorite desktop in the next 25 years we better start kicking some MS-ass

UPDATE... If someone, for educational purposes would like to give it a try, but aint got Civ, I got it and can lend it out for this educational project. That needs a PM...

[prehistoric]

Now running Firefox 46.0.1 on Fatdog 702 with 01micko's gtk3 packages. Still expect another update this month.

Firefox 47 is slated to go mainstream on June 7.

Not sure there is such a thing as a stable browser release anymore.

[quirkian2new]

@Atle,

I loaded the following two sfs files and then can run my win32 programs successfully.

32bit-slacko6.sfs
wine-1.7.39-v2.1.sfs

[ktrls]

Hi,

I don't know if anybody solved this issue.

I'm trying Fatdog64 702 with the goal to install on an old Asus A6000KMSeries notebook.

I'm not able to boot the distro with a USB drive because I receive a kernel panic message.
So I tried to use the same iso with virtualbox on an other PC but I receive the same message.

I attach a screenshot of the last test.

quirkian2new have suggeste to use a small initrd on boot, but I don't know how it works.

Can anybody help me?

Thanks in advance
Salvo

[Belham]

Hi,

I don't know if anybody solved this issue.

I'm trying Fatdog64 702 with the goal to install on an old Asus A6000KMSeries notebook.

I'm not able to boot the distro with a USB drive because I receive a kernel panic message.
So I tried to use the same iso with virtualbox on an other PC but I receive the same message.

I attach a screenshot of the last test.

quirkian2new have suggeste to use a small initrd on boot, but I don't know how it works.

Can anybody help me?

Thanks in advance
Salvo

Salvo [nice name ],

I'm not the foremost expert here but I'll try to help you out here since I've remastered my Fatdogs (702 and now the 710 versions) to get a "small initrd" so it would boot quickly on my machines (instead of the 7-8 minute bootup times I was getting---and there would be an occassional "kernel-panic" too on my HP Netbook). Remastering to a "small initrd" removed all those problems and made Fatdog great fun to use & learn.

Ok, here goes (this is really easy, trust me):

1. Forget about installing to your hard drive for a minute. We'll come back to that, since you're having problems now

2. Make sure your computer/laptop can boot off either a CD/DVD (and/or a USB---but we'll focus here on CD/DVD_. Go into your BIOS, Google how to do that, it is also very easy, most all BIOS for the past 10 years let you also bootup from not only an internal HD, but also the CD/DVD (and/or USB).

3. Next, download the Fatdog64 ISO to your windows machine.

4. Use the Windows CD/DVD burning software (either Windows own program and/or a program you've installed) and burn the ISO image to the CD/DVD. Pay attention, you are NOT making a "data disk". You are choosing the program's option to "burn the ISO image".

5. After burning the ISO, remove the CD/DVD, and shutdown Windows completely.

6. Start the computer again, and immediately hit either F12 (or F5 or F7 or F10 on some BIOS systems) to enter the choice of what you want to boot first. You can learn which F button you need to hit by finding it out in yur BIOS and/or Googling your BIOS and reading about it.

7. Before choosing to boot from the 'CD/DVD rom drive", open your CD rom and put in your burned ISO CD/DVD.

8. Click the boot option "CD/DVD drive" and let your computer start up.

9. You'll be in Fatdog64 after a few minutes. This is a Live-CD (or DVD) session, and we are going to make the remastered ISO from it and save it to a USB thumbdrive (or another CD/DVD).

10. After Fatdog64 has booted, click on "Menu", then "Setup", then "Fatdog Control Panel", then the tab "Utilities". Notice right there on the first line in this tab is the "FATDOG REMASTERED LIVE-CD shortcut.

Click it, and from there just follow the directions as it will ask you as you go through what you want to do. One of the clickable option boxes that comes up asks you whether you want to keep the normal "humungous" initrd or if you want the "small" initrd option.

As a hint, pay attention doing this remastering like when it first opens, it is going to ask you to point to the "vmlinuz" option (hint---it is right there in your CD, just click--staying inside the remastering program & using its search abiliites---until you find it (it is easy to find). Highlight it so the remastering program knows to use it.

Then go all the way through the remastering program, clicking the "small initrd" choice---and here's another big hint. The remastering program will popup a box near the end (before it begins starting) that says if you want to modify anything before continuing, I am opening a window for you to do so. You need to click into the "Boot" folder, and then open the "syslinux.cfg" file. You are going to add something to line 23:

It says this: append rootfstype=ramfs

You need to add this to that line:

basesfs=local:/boot/fd64.sfs

So line 23 when finished should look like this:

append rootfstype=ramfs basesfs=local:/boot/fd64.sfs

If you do not do this now, your CD/DVD may not boot (it has something specifically to do with remastering a Fatdog64 and choosing "small initrd" option; it doesn't apply to other remastering when you use the normal "humungous" iniitrd option (which may, or may not, be causing your kernel panics).


Once the remastered ISO is finished (the program will tell you and popup boxes saying such, you are then--staying in the current Fatdog & using its pBurn program---going to burn this Remastered ISO to another CD/DVD. The remastering popup program will actually ask if you want to do this, which you do.

After that is finished, you know what to do. Take this new remastered ISO CD/DVD out, and I recommend grabbing an USB thumbdrive and saving your new remastered ISO to it (no need to reformat it or anything, just save the remastered ISO to it).



Everything else is a cakewalk from there. Put the new remastered CD/DVD in your computer, see if it will boot up. If it does, then go into the same process as above (into the "Fatdog Control Panel", and this time you are going to choose "Fatdog64 Installer" (it's right beside the Fatdog64 Remaster Live-CD" you just used above).

Then install Fatdog64 to your partition on your hard drive, and from there everything is easily solved (this is where Google is your friend if you are confused on this---there are tons of writeups for this, and they should all apply since you'll have a working remastered ISO of Fatdog64 (knock-on-wood )


Please know that there are many ways to skin the cat on installing Fatdog64, i.e we could install through USB or, if we wanted, we could just copy files from a working directory of Fatdog and transfer them to the partition on your HD. The way I write above is the long way, but the key thing here is to ensure that a remastered ISO actually does bootup on your system (and doesn't suffer another kernel-panic, like you are getting now which a small initrd might solve, or it might not solve). If a remastered ISO with a small initrd doesn't boot up, then I honestly do not how to help you any further.

Good luck!

P.S. Forgive any spelling and/or grammar errors, am banging this out on the keyboard past lunchtime when I shouldn't be ;-0

[csshin]

I have to access our university wifi which used an wpa2-enterprise-peap encryption. I searched and got to the conclusion that I need something like the following in the wpa_suplicant.conf
:

network={
ssid="XXXpeap"
scan_ssid=1
key_mgmt=WPA-EAP
eap=peap
anonymous_identity="my identity"
identity="my Identity"
password="my Password"
phase2-auth=mschapv2
ca_cert="no cert"
priority=2
}

The wpa_gui of Fatdog cannot generate this automatically. I tried to mannually edited the wpa_supplicant.conf to add a new entry for network description. However, once edited, the wpa_gui can no longer work and just said cannot get the status of wpa_suplicant.

Could anybody help to point me in how to add the necessary netwark description without breaking the networking capability?

[don570]

If you read my experiences with fatdog arm and a home wifi network
http://murga-linux.com/puppy/viewtopic. ... =786366711

I didn't have to have a wpa_supplicant.conf
I just used network-setup.sh

I filled in three boxes ---> SSID,security,password

...but then I needed to know the address of the server , the Share and its password (if any is needed).
I used mount-FULL -t cifs

How a university runs wifi is beyond my understanding
______________________________________

[quirkian2new]

For those who want a slim copy of Firefox46, here is another choice :

https://sourceforge.net/projects/lightfirefox/files/46/

I have unpacked the 64bit rpm and run successfully on Fatdog702. Feel very satisfied with its speed. Worth giving it a try.