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 Mon 22 Jul 2019, 21:03
All times are UTC - 4
 Forum index » Advanced Topics » Puppy Projects
Fatdog64-720 and 721 Final [11 Jan 2018]
Moderators: Flash, JohnMurga
Post new topic   Reply to topic View previous topic :: View next topic
Page 5 of 30 [440 Posts]   Goto page: Previous 1, 2, 3, 4, 5, 6, 7, ..., 28, 29, 30 Next
Author Message
kirk

Joined: 11 Nov 2005
Posts: 1545
Location: florida

PostPosted: Sat 06 Jan 2018, 18:52    Post subject:  

Quote:
How small can a Fatdog64 installation partition be and still function? Either with save folder there or elsewhere?


We don't support "traditional" full installs. A Fatdog64 install is just copying the initrd and vmlinuz to the partition, so if you already have a boot loader installed it's just the size of those two files. What I usually do is make a one or two gigabyte ext3 partition for the intrd and kernel. Then put the savefolder on an ext4 partition. Some bootloaders (grub legacy and gub4dos) are slow loading from ext4.
Back to top
View user's profile Send private message 
rufwoof


Joined: 24 Feb 2014
Posts: 3254

PostPosted: Sat 06 Jan 2018, 19:51    Post subject:  

kirk wrote:
What I usually do is make a one or two gigabyte ext3 partition for the intrd and kernel. Then put the savefolder on an ext4 partition. Some bootloaders (grub legacy and gub4dos) are slow loading from ext4.

I like the flexibility of ext3. Can be mounted as though a ext2 from the likes of BSD, or can be mounted as though a ext4 by Linux. That outweighs the benefit of running native ext4 in my book, so I format (Linux partitions) to ext3 exclusively.
Back to top
View user's profile Send private message 
dr. Dan


Joined: 20 Apr 2015
Posts: 80
Location: Oregon, U.S.A.

PostPosted: Sat 06 Jan 2018, 21:51    Post subject:  

@kirk:
Thanks!

@rufwoof:
Also thanks for the knowledge.

Dan
Back to top
View user's profile Send private message 
snayak

Joined: 14 Sep 2011
Posts: 420

PostPosted: Mon 08 Jan 2018, 09:31    Post subject:  

I got setuptools-38.4.0.zip from https://pypi.python.org/pypi/setuptools. Installed it manually using command
Code:
python setup.py install --record files.txt


Then I tried to install pip using easy_install.
It says
Code:
ImportError: No module named extern


Tried different versions of setuptools, but failed. Tried installing extern 0.2.1 from https://pypi.python.org/pypi/extern/ manually and got the same error. Tried installing importlib 1.0.4 from https://pypi.python.org/pypi/importlib manually, same error.

Am I missing something?
Had not faced any such issue on Fatdog 611.


Sincerely,
Srinivas Nayak

_________________
[Precise 571 on AMD Athlon XP 2000+ with 512MB RAM]
[Fatdog 720 on Intel Pentium B960 with 4GB RAM]

http://srinivas-nayak.blogspot.com/
Back to top
View user's profile Send private message 
chiefengineer

Joined: 25 Mar 2013
Posts: 58

PostPosted: Mon 08 Jan 2018, 18:54    Post subject: Stumped with Dell Laptop I got today
Subject description: 710 boots, 720b gets to spalshscreen, 720 is black
 

Has W10 on hard disk. Just want to leave it there right now. Bios allowed me to boot legacy USB. 710 works great. 720 lights the USB, screen blips a little, then all dark...the beta version got to the splashscreen then went dark forever. Tried in all USB slots with three different USB keys. Turned off TPM in bios no help.

Am I stuck on 710? Used both 710 and 720 to install to key through ISO file. The 720 keys work on other machines fine. What's different here? Have never entered the UEFI world (I just shut it off)...has it become necessary?
Back to top
View user's profile Send private message 
stemsee

Joined: 27 Jun 2013
Posts: 2363
Location: In The Way

PostPosted: Mon 08 Jan 2018, 19:02    Post subject:  

Hi chiefengineer

I had a similar problem! Finally I mounted the 720 iso and manually copied to a fat32 formatted usb drive then ran grub4dos and booted fine. I had problems when I DDed the iso to the drive. I also had problems when trying to boot using refind. James B indicated that my grub64.efi/grub2.efi needed updating. However the 4.14.6 vmlinuz in fd 720 doesnt have ext2/3 compiled in only ext4. I also had to install exfat-fuse and exfat in user space to use with some sd cards for mounting and access. So I recommend the first method on legacy bios systems.

stemsee
Back to top
View user's profile Send private message MSN Messenger 
chiefengineer

Joined: 25 Mar 2013
Posts: 58

PostPosted: Mon 08 Jan 2018, 23:05    Post subject: Bummer  

Thanks for that stemsee.
I'll try your methods one by one and report back.
I noticed in subsequent boots of 710 I never got
the splashscreen displayed...it would sit awhile and go directly
to the default boot on the menu. Makes me think
video incompatibility.

Edit:
Success with the FAT32 solution!
Thanks!

720 even works nicely with clickpad which 710 did not.

Second edit:
I spoke too soon. Boot only works every other time, if that. Also, Kali Linux, which boots the world fails half the time with the same symptoms: splash screen, blank dark nothing, and a flashing USB. For kicks I burned a 720 CDR and it does exactly the same thing. Thus, Dell (and MS) have either sold me a flaky machine or they have changed the way the legacy bios seems to handle brightness, or I am way off. It is an Inspiron 15 to save anyone else the trouble of returning like I am about to do.

Last edited by chiefengineer on Wed 10 Jan 2018, 01:40; edited 1 time in total
Back to top
View user's profile Send private message 
vanchutr

Joined: 05 Aug 2006
Posts: 439

PostPosted: Tue 09 Jan 2018, 01:12    Post subject: about FatDog64-720 Final' installation  

I'd installed succesfully FatDog64-720 Final on USB Hardisk
0. Boot any puppy derivative (I 'd used Slacko_5.7)
1. Make an ext2 partition on My HardDisk
2. Make an directory (e.g FatDog720)
3. Open Fatdog64-720.iso
4. Copy all files in Fatdog64-720.iso to directory (included:
boot.catalog
efiboot.img
fatdog.png
fatdog.xpm
fix-usb.sh
grub.cfg
initrd
initrd-nano.xz
isolinux.bin
isolinux.cfg
vesamenu.c32
vmlinuz

help:
basesfs.msg
blank.png
boot.msg
help.msg
savefile.msg
startnet.msg

lick:
LICK-1.2.0-win32.exe
README-fatdog.html
README.md

5. Use "Grub4Dos config to install (frugal)
We wiil get this config file:
title Fatdog64 (sdb1/fatdog720)
uuid f737daea-5272-4175-9c6e-3ebbd50065e0
kernel /fatdog720/vmlinuz pdrv=f737daea-5272-4175-9c6e-3ebbd50065e0 psubdir=fatdog720 pmedia=atahd pfix=fsck
initrd /fatdog720/initrd

6. Reboot and test your installation
Back to top
View user's profile Send private message 
snayak

Joined: 14 Sep 2011
Posts: 420

PostPosted: Tue 09 Jan 2018, 03:47    Post subject:  

Dear All,

From my Fatdog 720 I see this.

Code:
~# ls -l /usr/bin/ | grep multiarch_wrapper
lrwxrwxrwx   1 root root       17 Dec 29  2015 aoss -> multiarch_wrapper
lrwxrwxrwx   1 root root       17 Jan  9  2016 apr-1-config -> multiarch_wrapper
lrwxrwxrwx   1 root root       17 Jan  9  2016 apu-1-config -> multiarch_wrapper
lrwxrwxrwx   1 root root       17 May  7  2017 bacon -> multiarch_wrapper
lrwxrwxrwx   1 root root       17 May  7  2017 bacongui -> multiarch_wrapper
lrwxrwxrwx   1 root root       17 Jan  8  2016 ccache-swig -> multiarch_wrapper
lrwxrwxrwx   1 root root       17 Jan  5  2016 croco-0.6-config -> multiarch_wrapper
lrwxrwxrwx   1 root root       17 Aug 27 11:57 cups-config -> multiarch_wrapper
lrwxrwxrwx   1 root root       17 Mar  7  2016 curl-config -> multiarch_wrapper
lrwxrwxrwx   1 root root       17 Jan 10  2016 cygdb -> multiarch_wrapper
lrwxrwxrwx   1 root root       17 Jan 10  2016 cython -> multiarch_wrapper
lrwxrwxrwx   1 root root       17 May  2  2016 dbus-binding-tool -> multiarch_wrapper
lrwxrwxrwx   1 root root       17 Oct  9  2016 ffmpeg -> multiarch_wrapper
lrwxrwxrwx   1 root root       17 Dec  1  2016 flash-player-properties -> multiarch_wrapper
lrwxrwxrwx   1 root root       17 Sep 28  2015 freetype-config -> multiarch_wrapper
lrwxrwxrwx   1 root root       17 Nov 20  2016 gdk-pixbuf-csource -> multiarch_wrapper
lrwxrwxrwx   1 root root       17 Nov 20  2016 gdk-pixbuf-query-loaders -> multiarch_wrapper
lrwxrwxrwx   1 root root       17 Oct  6 20:57 gimptool-2.0 -> multiarch_wrapper
lrwxrwxrwx   1 root root       17 Apr 29  2016 g-ir-compiler -> multiarch_wrapper
lrwxrwxrwx   1 root root       17 Apr 29  2016 g-ir-generate -> multiarch_wrapper
lrwxrwxrwx   1 root root       17 Apr 29  2016 g-ir-scanner -> multiarch_wrapper
lrwxrwxrwx   1 root root       17 Jan  9  2016 gpg-error-config -> multiarch_wrapper
lrwxrwxrwx   1 root root       17 Dec 29  2015 gpgme-config -> multiarch_wrapper
lrwxrwxrwx   1 root root       26 Apr 30  2016 gsl-config -> /usr/bin/multiarch_wrapper
lrwxrwxrwx   1 root root       17 Jan  9  2016 gst-inspect-32 -> multiarch_wrapper
lrwxrwxrwx   1 root root       17 Jan  9  2016 gst-launch-32 -> multiarch_wrapper
lrwxrwxrwx   1 root root       17 Jan  9  2016 gst-typefind-32 -> multiarch_wrapper
lrwxrwxrwx   1 root root       17 Sep 10  2016 gtk-query-immodules-2.0 -> multiarch_wrapper
lrwxrwxrwx   1 root root       17 Jan  8  2016 ijs-config -> multiarch_wrapper
lrwxrwxrwx   1 root root       17 Jan  6  2016 imlib2-config -> multiarch_wrapper
lrwxrwxrwx   1 root root       17 Dec 29  2015 ksba-config -> multiarch_wrapper
lrwxrwxrwx   1 root root       17 Jan 11  2016 libart2-config -> multiarch_wrapper
lrwxrwxrwx   1 root root       17 Dec 29  2015 libassuan-config -> multiarch_wrapper
lrwxrwxrwx   1 root root       17 Oct 26  2016 libgcrypt-config -> multiarch_wrapper
lrwxrwxrwx   1 root root       17 Jan 11  2016 libmikmod-config -> multiarch_wrapper
lrwxrwxrwx   1 root root       17 Mar  3  2017 libnet-config -> multiarch_wrapper
lrwxrwxrwx   1 root root       17 Sep 28  2015 libpng16-config -> multiarch_wrapper
lrwxrwxrwx   1 root root       17 Sep 28  2015 libpng-config -> multiarch_wrapper
lrwxrwxrwx   1 root root       17 Nov 19  2016 libtool -> multiarch_wrapper
lrwxrwxrwx   1 root root       17 Dec 29  2015 libusb-config -> multiarch_wrapper
lrwxrwxrwx   1 root root       17 Dec 29  2015 libusb-config-32 -> multiarch_wrapper
lrwxrwxrwx   1 root root       17 Oct  3 10:38 llvm-config -> multiarch_wrapper
-rwxr-xr-x   1 root root     5120 Mar  5  2015 multiarch_wrapper
lrwxrwxrwx   1 root root       17 Mar  7  2015 ncursesw5-config -> multiarch_wrapper
lrwxrwxrwx   1 root root       17 Jan  9  2016 neon-config -> multiarch_wrapper
lrwxrwxrwx   1 root root       17 Jan  8  2016 orcc -> multiarch_wrapper
lrwxrwxrwx   1 root root       17 Jan 11  2016 pcap-config -> multiarch_wrapper
lrwxrwxrwx   1 root root       17 Jan  9  2016 pcre-config -> multiarch_wrapper
lrwxrwxrwx   1 root root       17 Mar 14  2015 perl -> multiarch_wrapper
lrwxrwxrwx   1 root root       17 Mar 14  2015 perl5.20.0 -> multiarch_wrapper
lrwxrwxrwx   1 root root       17 Jan  8  2016 pspell-config -> multiarch_wrapper
lrwxrwxrwx   1 root root       17 Dec 29  2015 pth-config -> multiarch_wrapper
lrwxrwxrwx   1 root root       17 Mar  8  2016 python -> multiarch_wrapper
lrwxrwxrwx   1 root root       17 Mar  8  2016 python2 -> multiarch_wrapper
lrwxrwxrwx   1 root root       17 Mar  8  2016 python2.7 -> multiarch_wrapper
lrwxrwxrwx   1 root root       17 Jan 23  2016 rlwrap -> multiarch_wrapper
lrwxrwxrwx   1 root root       17 Jan 11  2016 sane-config -> multiarch_wrapper
lrwxrwxrwx   1 root root       17 May  2  2016 sdl2-config -> multiarch_wrapper
lrwxrwxrwx   1 root root       17 May  2  2016 sdl-config -> multiarch_wrapper
lrwxrwxrwx   1 root root       17 Dec 22  2016 smpeg-config -> multiarch_wrapper
lrwxrwxrwx   1 root root       17 Jan  8  2016 swig -> multiarch_wrapper
lrwxrwxrwx   1 root root       17 Jan  9  2016 taglib-config -> multiarch_wrapper
lrwxrwxrwx   1 root root       17 Jan  9  2016 tclsh -> multiarch_wrapper
lrwxrwxrwx   1 root root       17 Jan  9  2016 tclsh8.6 -> multiarch_wrapper
lrwxrwxrwx   1 root root       17 Jan  9  2016 wish -> multiarch_wrapper
lrwxrwxrwx   1 root root       17 Jan  9  2016 wish8.6 -> multiarch_wrapper
lrwxrwxrwx   1 root root       17 Apr 26  2016 xml2-config -> multiarch_wrapper
lrwxrwxrwx   1 root root       17 Sep 28  2015 xslt-config -> multiarch_wrapper


~# /usr/bin/multiarch_wrapper
/usr/bin/multiarch_wrapper-64: No such file or directory
~#


What is multiarch_wrapper ? python is symlink to this. Surprisingly executing multiarch_wrapper yeilds nothing!

Any idea?

Sincerely,
Srinivas Nayak

_________________
[Precise 571 on AMD Athlon XP 2000+ with 512MB RAM]
[Fatdog 720 on Intel Pentium B960 with 4GB RAM]

http://srinivas-nayak.blogspot.com/
Back to top
View user's profile Send private message 
step

Joined: 04 May 2012
Posts: 1188

PostPosted: Tue 09 Jan 2018, 06:34    Post subject:  

Fatdog64-720 can run binaries for 32 and 64 bit architectures. multiarch_wrapper is used to wrap certain architecture-dependent binaries so that hardcoded paths to libraries work correctly. multiarch_wrapper executes a different program based on the USE_ARCH environment variable. Source code for the wrapper is here.
_________________
Fatdog64-802|+Packages|Kodi|Findnrun|+forum|gtkmenuplus
Back to top
View user's profile Send private message 
jamesbond

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

PostPosted: Tue 09 Jan 2018, 06:39    Post subject:  

@fandog: https://ubuntuforums.org/archive/index.php/t-1245536.html
This would be too dangerous to be automated. The risk of things going wrong and make the situation worse is just too high. If you do this thing, you'd better be aware of the risk involved.

@stemsee:
Quote:
I also discovered that the init scripts and boot process has changed significantly (system-init) > (busybox-init (binary)).
Not really. That way of booting has always been the case since Fatdog 600.

Quote:
. . making it difficult to boot the main.sfs with any other initrd/init script.

Of course. You can't just replace Fatdog's initrd with any random init/initrd script and expect things to work. They both work together. If you want to replace it, the replacement init/initrd need to be compatible. It's not too difficult. In fact, with some loss of functionality, the basesfs can be booted with no initrd at all. See here.

Quote:
Also there are significant changes in the use of permissions or ACLs on root directories, it seems.
Main permission change is on /root, as noted in the release notes. Anything else (ACL, etc) are probably just showing because in 720 the utilities are built with support for ACL and extended attributes; but they aren't being used.

Quote:
Previous 710 would break with the latest upgrades using gslapt.
Unfortunately yes, because we can't afford the effort to maintain two separate repositories for 710 and 720. Anyway, we always state that we can only support the latest version of Fatdog. As soon as a new release is announced, support for the previous versions cease (it's up to the community to maintain those older versions, if they wish).

Quote:
720 is working great now, and I wonder if all the technical changes are listed somewhere?
Release Notes.

@dr. Dan:
Quote:
How small can a Fatdog64 installation partition be and still function? Either with save folder there or elsewhere?
What is ideal as a minimum?

Kirk alreay answered that. But I will elaborate a little bit.
"Installation partition" is a very vague word in Fatdog.

If you use the default install, you need a minimum space of vmlinuz + initrd (plus any savefile/savefolder you need), as Kirk said.
But with Fatdog you've got options to suit your needs.

You can have vmlinuz in one partition, and initrd in another.
You can extract basesfs (fd64.sfs) from initrd and put it elsewhere, while the "shrunk" initrd + vmlinuz is in one partition.
You can extract basesfs, kernel-modules.sfs, and put these in separate or same partition; and have "nano-ed" initrd + vmlinuz in one partition.
None of the "advanced" installation is automated/scripted/GUI-ed, you need to do it yourself, depending on what you're doing.

Of course, to all the above, you need to add the size of the bootloader if you don't have one already. It's about 3MB for grub4dos, and 10MB for UEFI.

@vanchutr: Thanks for testing.
For the record, "pdrv=f737daea-5272-4175-9c6e-3ebbd50065e0 psubdir=fatdog720 pmedia=atahd pfix=fsck" are all not supported by Fatdog, so you're running it as if you don't pass in any extra parameter at all.
The first 3 parameters are replaced by "savefile" and "basesfs" parameter; and the last one is replaced by "dofsck".

@snayak: There is already setuptools and pip in the repo. It's a bit old, version 12, but do you need the latest version?
If you really need to use the latest version, look at our build recipes below to see how we built the earlier versions:
http://distro.ibiblio.org/fatdog/source/710/recipes/python-setuptools-12.0.4-noarch-1.tar.gz
and
http://distro.ibiblio.org/fatdog/source/710/recipes/python-pip-7.0.3-noarch-1.tar.gz

As for multiarch_wrapper, it's meant so that some programs who aren't multi-lib aware, can run in a multi-lib environment. In other words, it allows 32-bit python and 64-bit python to co-exist, for example. You can read the details here: http://www.clfs.org/view/CLFS-3.0.0-SYSVINIT/x86_64/final-system/multiarch_wrapper.html.

EDIT: I saw step's reply when I was typing this. Thanks step Smile

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

Joined: 14 Sep 2011
Posts: 420

PostPosted: Wed 10 Jan 2018, 02:14    Post subject:  

Dear jamesbond/step,

Many thanks for your time and valuable input. I will have a look at setuptools and pip.

Sincerely,
Srinivas Nayak

_________________
[Precise 571 on AMD Athlon XP 2000+ with 512MB RAM]
[Fatdog 720 on Intel Pentium B960 with 4GB RAM]

http://srinivas-nayak.blogspot.com/

Last edited by snayak on Wed 10 Jan 2018, 02:36; edited 1 time in total
Back to top
View user's profile Send private message 
snayak

Joined: 14 Sep 2011
Posts: 420

PostPosted: Wed 10 Jan 2018, 02:21    Post subject:  

deleted my post from here
_________________
[Precise 571 on AMD Athlon XP 2000+ with 512MB RAM]
[Fatdog 720 on Intel Pentium B960 with 4GB RAM]

http://srinivas-nayak.blogspot.com/

Last edited by snayak on Wed 31 Jan 2018, 05:27; edited 1 time in total
Back to top
View user's profile Send private message 
snayak

Joined: 14 Sep 2011
Posts: 420

PostPosted: Wed 10 Jan 2018, 03:33    Post subject:  

Package description of pip says:

Code:
python-pip 7.0.3 (Python Package Installer)

pip is package manager for python. You only need to use this if the python package you need is not available in gslapt repository. This package is only needed for python < 2.7.9 (pyton 2.7.9 onwards includes pip as standard).


But I see

Code:
~# pip
bash: /usr/bin/pip: No such file or directory
~#


python version on Fatdog 720 is:

Code:
Python 2.7.11 (default, Mar  8 2016, 14:58:29)
[GCC 4.8.3] on linux2


Am I mistaken?


Srinivas Nayak

_________________
[Precise 571 on AMD Athlon XP 2000+ with 512MB RAM]
[Fatdog 720 on Intel Pentium B960 with 4GB RAM]

http://srinivas-nayak.blogspot.com/
Back to top
View user's profile Send private message 
borzeh

Joined: 12 Jan 2014
Posts: 21

PostPosted: Wed 10 Jan 2018, 05:29    Post subject: savefile/folder Auto selection?  

@step @kirk @jamesbond

Hi!
sry mention You all!
When booting , If we have more than one save file , it will prompt which one to use , 1 , 2 etc..
Is it possible after some seconds/minutes it will autoselect first one?

<!-- I need all of them! but use first one most of the time! -->

Thank! Smile
Back to top
View user's profile Send private message 
Display posts from previous:   Sort by:   
Page 5 of 30 [440 Posts]   Goto page: Previous 1, 2, 3, 4, 5, 6, 7, ..., 28, 29, 30 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.0868s ][ Queries: 12 (0.0154s) ][ GZIP on ]