Puppy Linux Discussion Forum Forum Index Puppy Linux Discussion Forum
Puppy HOME page : puppylinux.com
"THE" alternative forum : puppylinux.info
 
 FAQFAQ   SearchSearch   MemberlistMemberlist   UsergroupsUsergroups   RegisterRegister 
 ProfileProfile   Log in to check your private messagesLog in to check your private messages   Log inLog in 

The time now is Sat 25 Nov 2017, 02:14
All times are UTC - 4
 Forum index » Advanced Topics » Puppy Projects
Fatdog64-630 & 631 Final (May 12 2014)
Moderators: Flash, JohnMurga
Post new topic   Reply to topic View previous topic :: View next topic
Page 39 of 42 [627 Posts]   Goto page: Previous 1, 2, 3, ..., 37, 38, 39, 40, 41, 42 Next
Author Message
Bindee

Joined: 19 Jun 2014
Posts: 365

PostPosted: Sun 27 Jul 2014, 18:19    Post subject:  

Kirk , James

Have you modified or customised VLC and Firefox in any way that users should avoid updating them to the latest version ?

I vaguely seem to remember James saying Firefox has been modified and thats why it says nightly build.

Just wanted to check if it will break anything.

Thanks
Back to top
View user's profile Send private message 
Pavan

Joined: 01 Jun 2014
Posts: 30

PostPosted: Tue 29 Jul 2014, 05:17    Post subject:  

Anyone used or using a steelseries kana v2 mouse with fatdog ?

I wondered if all the buttons and wheel work ok.
Back to top
View user's profile Send private message 
jamesbond

Joined: 26 Feb 2007
Posts: 3080
Location: The Blue Marble

PostPosted: Wed 30 Jul 2014, 11:51    Post subject:  

@LateAdopter - that's an interesting experiments, yes. Never cross my mind to use kexec on x86_64 because the bootloaders are capable ones. But yes, I'm glad that it works; I assume you compile your own minimal kernel since Fatdog's one isn't compiled with kexec.

@Bindee, both VLC and Firefox are self-compiled and not the official binaries from the website. For example firefox is "nightly" (because we aren't allowed to use firefox brand). Thus both will not auto-update.

If you need an updated firefox, you can always delete the built-in one and download and install firefox from official binaries, it should work. VLC - I haven't tested, as VLC has a lot more dependencies.

@Pavan - not me. I use Logitech standard wheel mouse.

_________________
Fatdog64, Slacko and Puppeee user. Puppy user since 2.13.
Contributed Fatdog64 packages thread.
Back to top
View user's profile Send private message 
LateAdopter

Joined: 27 May 2011
Posts: 275
Location: Reading UK

PostPosted: Wed 30 Jul 2014, 14:35    Post subject:  

Hello jamesbond

jamesbond wrote:
@LateAdopter - I assume you compile your own minimal kernel since Fatdog's one isn't compiled with kexec.



That's what Kexec-Loader provides. It's a kernel: 740kB and an initrd: 128kB, plus a collection of optional filesystem drivers and device drivers.

It only has FAT and Joliet filesystems built-in but you can add any of the others needed.

It means that you can boot from any device and filesystem supported by linux. You are not limited to what the BIOS and bootloader support.
Back to top
View user's profile Send private message 
gcmartin

Joined: 14 Oct 2005
Posts: 6730
Location: Earth

PostPosted: Wed 30 Jul 2014, 20:26    Post subject: A potential universal Boot-Manager
Subject description: Could get around the proprietary boot loaders if applied effectively
 

Hello @LateAdopter. What you share is of great interest. And Thanks to both you and @JamesBond.

You share a bootloader approach which has cross-platform ability and cross-peripherals for boot identification and selection. This brings Linux universality to the bootmanager/bootloader arena. Idea

_________________
Get ACTIVE Create Circles; Do those good things which benefit people's needs!
We are all related ... Its time to show that we know this!
3 Different Puppy Search Engines or use DogPile
Back to top
View user's profile Send private message 
Bindee

Joined: 19 Jun 2014
Posts: 365

PostPosted: Thu 31 Jul 2014, 01:49    Post subject:  

jamesbond wrote:
@Bindee, both VLC and Firefox are self-compiled and not the official binaries from the website. For example firefox is "nightly" (because we aren't allowed to use firefox brand). Thus both will not auto-update.

If you need an updated firefox, you can always delete the built-in one and download and install firefox from official binaries, it should work. VLC - I haven't tested, as VLC has a lot more dependencies.


I think it might be best if i just left them alone then. Mr. Green

Seeing as FireFox has regular security fixes and VLC has codec bug fixes couldn't you assign someone with good Linux knowledge to the fatdog team to keep these packages updated while still keeping it self-compiled how you want them?

Question
Back to top
View user's profile Send private message 
jamesbond

Joined: 26 Feb 2007
Posts: 3080
Location: The Blue Marble

PostPosted: Thu 31 Jul 2014, 11:38    Post subject:  

Bindee wrote:
I think it might be best if i just left them alone then. Mr. Green

Firefox isn't too difficult to update. Just delete /usr/lib64/firefox and /usr/lib64/firefox-27, get the tarball for 64-bit Linux from firefox website, expand it, and copy the resulting "firefox" directory to /usr/lib64.

Quote:
Seeing as FireFox has regular security fixes and VLC has codec bug fixes couldn't you assign someone with good Linux knowledge to the fatdog team to keep these packages updated while still keeping it self-compiled how you want them?


I wish I could *assign* someone Laughing

But you do have a point. I'm sure some of Fatdog users will continue to stay with the 600 series (I've seen some sticking to 500 series) so it would be good if the community can form a support group around these older series, and I would encourage anyone with interest to do so.

In addition, Fatdog64 600 series has a public repository, accessible using Fossil SCM, here: http://www.ibiblio.org/fatdogscm/cgi-bin/fatdog64.cgi/index With this, you can rebuild Fatdog64, identical with the released versions. Anybody who is interested to maintain the 600 series can use that as the base and continue to release "unofficial" updates to Fatdog64 631 (it's "unofficial" because as far as the officer is concerned, the 600 series ends with 631).

Fatdog users tend to be the quiet types, though, so I don't really know how many of you are out there.

Now the most exciting news of all: Fatdog64 700 alpha1 is released today. Announcement here.

_________________
Fatdog64, Slacko and Puppeee user. Puppy user since 2.13.
Contributed Fatdog64 packages thread.

Last edited by jamesbond on Thu 31 Jul 2014, 12:31; edited 1 time in total
Back to top
View user's profile Send private message 
Ted Dog


Joined: 13 Sep 2005
Posts: 4013
Location: Heart of Texas

PostPosted: Thu 31 Jul 2014, 12:14    Post subject:  

I wouldn't mind helping keep 600 series alive. But I will see what happens with the new direction taken by 700. COMING SOON... Surprised
Back to top
View user's profile Send private message 
Bindee

Joined: 19 Jun 2014
Posts: 365

PostPosted: Fri 01 Aug 2014, 00:45    Post subject:  

Thanks James , I'll checkout 700
Back to top
View user's profile Send private message 
JustGreg

Joined: 24 May 2005
Posts: 785
Location: Connecticut USA

PostPosted: Fri 01 Aug 2014, 09:13    Post subject:
Subject description: Help with creating a Pet
 

First, this not a bug. I need some help creating a pet for Fatdog 64

My employer has started using a new web page/java script for time keeping. I noticed that the page was not rendering correctly with Firefox Nightly 29.0 version of Fatdog64. However, on my work Computer with Firefox 31.0, the page renders correctly. I decide to try to make a pet of the official Mozilla Firefox 31.0 package.

I downloaded the 64 bit package for other Linux, Firefox-31.0.tar.bz2 file. The bz2 fiel was copied to a working test diectory. I used pupzip to expand the archive to the directory Firefox-31.0 under the test directory. Using the dir2tgz command, Firefox-31.0.tgz archive was created. I created a pet file using tgz2pet command.

Using the pet installer, the pet was installed. Here is where I found I missed a step or two. After the pet installer successfully finished, first I noticed it reported no menu entry for applications menu. What do I need to add to create a menu entry? Secondly, the installer placed the needed files back in the original test directory and not in the system files. How do I correct this?

The good news is the official Mozzila package worked correctly when I started it. However, the time sheet web page still did not render correctly. I do want to use the official released version and create a proper pet. Thank you in advance for any help.

_________________
Enjoy life, Just Greg
Live Well, Laugh Often, Love Much

Last edited by JustGreg on Sat 02 Aug 2014, 12:45; edited 1 time in total
Back to top
View user's profile Send private message 
jamesbond

Joined: 26 Feb 2007
Posts: 3080
Location: The Blue Marble

PostPosted: Fri 01 Aug 2014, 12:39    Post subject:  

JustGreg, download the official binaries and then do this work in terminal (assuming your /tmp is plenty of space, if not, do it elsewhere):

Code:
cd /tmp
mkdir -p firefox-31-631/usr/lib64 # for example (change whatever name you'd like.
tar -xf /path/to/downloaded/firefox-tarball.tar.gz -C /tmp/firefox-31-631/usr/lib64
pushd /tmp/firefox-31-631/usr/lib64
mv firefox firefox-31
ln -sf firefox-31 firefox
popd
dir2pet firefox-31-631


I haven't tested this step by step but I remember this is how we actually package the firefox that goes into the basesfs. The point is that the pet must have firefox in /usr/lib64 and the original /usr/lib64/firefox symlink must be changed to point to the new one. All existing menu items etc will automatically point to the new one.

_________________
Fatdog64, Slacko and Puppeee user. Puppy user since 2.13.
Contributed Fatdog64 packages thread.
Back to top
View user's profile Send private message 
JustGreg

Joined: 24 May 2005
Posts: 785
Location: Connecticut USA

PostPosted: Sat 02 Aug 2014, 12:03    Post subject:
Subject description: FireFox 31.0 Pet
 

Thanks for the code. It does seem to work. I have run into a problem. When I tried to use the menu entry the older Nightly version 29 came up. I looked the defaultbrowser code and saw it ran firefox under run-as-spot. I tried to run the new version with the following code in urxvt:
Code:
exec /usr/bin/run-as-spot /usr/lib64/firefox-31.0/firefox "$@"
, the older Nightly version 29 of firefox is executed. But, if I use
Code:
exec  /usr/lib64/firefox-31.0/firefox
or the symlink to the 31 version then the newer 31 version is started. I must be doing something wrong.

Thanks for showing me the popd and pushd commands. Nice to learn something new.

Disregard the above. I found the problem. I had to edit the file
/spot/.local/share/applications/usr-app-Nightly-1MCEAX.desktop to the following:
Code:
[Desktop Entry]
Encoding=UTF-8
Version=1.0
Type=Application
NoDisplay=true
#Exec=/usr/lib64/firefox-29.0/firefox %u
Exec=/usr/lib64/firefox-31.0/firefox %u
Name=Nightly
Comment=Custom definition for Nightly

I have read Fatdog-64 Alpha post and the future change ending the use of the Pets for the more common Slackware package management. So, I think this problem is ended. I will be waiting for the beta 700 version to try it out. Thanks again for the help.

_________________
Enjoy life, Just Greg
Live Well, Laugh Often, Love Much
Back to top
View user's profile Send private message 
eowens2

Joined: 27 Aug 2008
Posts: 172

PostPosted: Mon 04 Aug 2014, 21:14    Post subject:  

I would like to report that I have openvpn up and running on Fatdog64_630, and have uploaded the necessary files.

Smokey01 is kindly hosting openvpn-2.3.4-x86_64.pet and gadmin-openvpn-client-0.1.9-x86_64.pet, both with a date stamp of 4-Aug-2014.

Gadmin-openvpn-client is a GUI-facilitator for openvpn; while it works hand-in-glove with gadmin-openvpn-server, it also allows import of configuration files from commercial openvpn service providers and to connect to them (which is how I use it). The GUI has a handy switch, “Start at Boot”, so that anytime you use your browser, an encrypted tunnel is being used.

The files can be found at www.smokey01.com/software/Fatdog64-600/.
Back to top
View user's profile Send private message 
eowens2

Joined: 27 Aug 2008
Posts: 172

PostPosted: Wed 06 Aug 2014, 18:39    Post subject:  

Dumb question. How do I find the kernel header files for kernel 3.12.18? Are they part of the source?
Back to top
View user's profile Send private message 
jamesbond

Joined: 26 Feb 2007
Posts: 3080
Location: The Blue Marble

PostPosted: Thu 07 Aug 2014, 08:53    Post subject:  

eowens2 wrote:
Dumb question. How do I find the kernel header files for kernel 3.12.18? Are they part of the source?

Part of the kernel source, yes.

_________________
Fatdog64, Slacko and Puppeee user. Puppy user since 2.13.
Contributed Fatdog64 packages thread.
Back to top
View user's profile Send private message 
Display posts from previous:   Sort by:   
Page 39 of 42 [627 Posts]   Goto page: Previous 1, 2, 3, ..., 37, 38, 39, 40, 41, 42 Next
Post new topic   Reply to topic View previous topic :: View next topic
 Forum index » Advanced Topics » Puppy Projects
Jump to:  

You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
You cannot attach files in this forum
You can download files in this forum


Powered by phpBB © 2001, 2005 phpBB Group
[ Time: 0.0716s ][ Queries: 13 (0.0169s) ][ GZIP on ]