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 Fri 24 Nov 2017, 16:39
All times are UTC - 4
 Forum index » Advanced Topics » Puppy Projects
Create Debian 9 (Stretch) minimal ISO similar to DebianDog
Moderators: Flash, JohnMurga
Post new topic   Reply to topic View previous topic :: View next topic
Page 2 of 59 [878 Posts]   Goto page: Previous 1, 2, 3, 4, ..., 57, 58, 59 Next
Author Message
dancytron

Joined: 18 Jul 2012
Posts: 944

PostPosted: Wed 02 Aug 2017, 17:12    Post subject:  

fredx181 wrote:
Thanks guys !

dancytron wrote:
I take it that it uses the list of repositories from the distribution you are using to run it? That's what it seemed to do. edit: no it doesn't

It creates new /etc/apt/sources.list and includes the right (stretch)dog repository depending if it's 32 or 64 bit build.

/snip/

Fred


I think an improvement might be to allow specifying additional repositories as a variable in the script. Of course, I'm thinking of Chrome, but there are lots of other "independent" Debian/Ubuntu repositories out there that people might want to use.
Back to top
View user's profile Send private message 
belham2

Joined: 15 Aug 2016
Posts: 1305

PostPosted: Wed 02 Aug 2017, 17:14    Post subject:  

fredx181 wrote:

A few questions:
- 01-filesystem.squashfs, what's the size (from right-click > How big ?)?
- From what OS you did run it ?
- Enough free space on the partition you build on ?

Fred



1) 133.5MB for the 01-filesystem.squashfs

2) Ran it from Trinity-Stretch 32

3) a 3GB build partition, then moved what I needed over to my big "frugal" partiton with all the various Puppies, DDogs, Trinities and Toni's Mintpup, and BAMMMM---it booted like a champ once I realized the dumba## stunt I was pulling when first trying to get it to boot (plz don't ask, it is embarrassing, lol).


I AM LOVE with this process----oooooh, the moditifcations to the build-script are running through my head, question popups for what DE you want, what borwser, what email, etc, etc......the customization could be incredible.

I am not going to bed NOW (unless the wife come stomping down the stairs and flashes me the "I am going to KILL YOU" look, lol)....I am having too much fun here. Very Happy Laughing Wink
Back to top
View user's profile Send private message 
fredx181


Joined: 11 Dec 2013
Posts: 2604
Location: holland

PostPosted: Wed 02 Aug 2017, 17:22    Post subject:  

Thanks belham Smile

Glad it works now for you, so the "at least 2 GB needed" I wrote should probably changed ? (assuming not enough disk space was the reason it didn't work first few times for you)
Heading to bed now Wink

Fred

_________________
Dog Linux website
Back to top
View user's profile Send private message 
dancytron

Joined: 18 Jul 2012
Posts: 944

PostPosted: Wed 02 Aug 2017, 17:25    Post subject:  

belham2 wrote:
fredx181 wrote:

A few questions:
- 01-filesystem.squashfs, what's the size (from right-click > How big ?)?
- From what OS you did run it ?
- Enough free space on the partition you build on ?

Fred



1) 133.5MB for the 01-filesystem.squashfs

2) Ran it from Trinity-Stretch 32

3) a 3GB build partition, then moved what I needed over to my big "frugal" partiton with all the various Puppies, DDogs, Trinities and Toni's Mintpup, and BAMMMM---it booted like a champ once I realized the dumba## stunt I was pulling when first trying to get it to boot (plz don't ask, it is embarrassing, lol).


I AM LOVE with this process----oooooh, the moditifcations to the build-script are running through my head, question popups for what DE you want, what borwser, what email, etc, etc......the customization could be incredible.

I am not going to bed NOW (unless the wife come stomping down the stairs and flashes me the "I am going to KILL YOU" look, lol)....I am having too much fun here. Very Happy Laughing Wink


Let's be careful not to kill the elegant simplicity of it.

How about just embedding some different "recipes" inside the script but commented out? Want xfce, uncomment the xfce line. Want lxde, then uncomment the lxde line. Want KDE with libre-office, Firefox, Thunderbird, Gimp, KODI and all the other goodies, then uncomment that line.

That could then become an easy way to share configs, by just saying, "This is the recipe that I used, just paste it into the script and go."
Back to top
View user's profile Send private message 
wiak

Joined: 11 Dec 2007
Posts: 372
Location: not Bulgaria

PostPosted: Wed 02 Aug 2017, 19:44    Post subject:  

The script is really quite simple at the moment so would be a good time to think about modularising it in such a way that it could easily be amending for particular purposes/additions/distributions without changing the resulting core script. I played with mcewanw's wex recently and it has some kind of facility for addon functions without needing to change original script at all, but I'm pretty much a novice myself when it comes to scripting.

wiak
Back to top
View user's profile Send private message 
rcrsn51


Joined: 05 Sep 2006
Posts: 11729
Location: Stratford, Ontario

PostPosted: Wed 02 Aug 2017, 20:11    Post subject:  

saintless wrote:
fredx181 wrote:
t...his line should be removed (or commented out:
Code:
 rm -rf tmpa/etc/rc.d

Now that peasywifi is in the dog repositories, I guess I'll have to update all remaster script packages that have similar as this line (not sure yet, maybe easier to consult rcrsn51 about a small change in peasywifi) sigh...

Removing /etc/rc.d, /etc/DISTRO_SPECS, and /initrd in remasterdog and remastercow scripts is sometning I insisted to include to prepare DebianDog for puppy-boot option (using initrd.gz from puppy with debian kernel).
Better remove the lines above from the scripts to make easier puppy developers to keep the same structure for packages like peasywifi (inside /etc/rc.d for puppy and dog based system). Porteus-boot and live boot will not create /initrd or /etc.rc.d (both are puppy specific for important configuration files).

Toni


I am sending you PWF v4.5 which moves rc.network into /etc/pwf. This should solve your problem.

The service script in /etc/init.d just needs to point to the new location.

Last edited by rcrsn51 on Wed 02 Aug 2017, 20:40; edited 1 time in total
Back to top
View user's profile Send private message 
wiak

Joined: 11 Dec 2007
Posts: 372
Location: not Bulgaria

PostPosted: Wed 02 Aug 2017, 20:15    Post subject:  

I note fred that you say this script can be run from any Debian-based OS. I can't help but wonder, if it is 'possible' it could be made to run from a Puppy (?) - in particular, does 'debootstrap' program need a debian-based system or can a different Linux be used for that chroot installed debian environment (followed by rest of script?).

https://wiki.debian.org/Debootstrap

Quote:
debootstrap is a tool which will install a Debian base system into a subdirectory of another, already installed system. It doesn't require an installation CD, just access to a Debian repository. It can also be installed and run from another operating system, so, for instance, you can use debootstrap to install Debian onto an unused partition from a running Gentoo system.


Just thought it would be great if a Puppy user could use this to immediately build a DebianDog to a usb stick or something (or maybe a mod of this script could do that?).

wiak

EDIT:

Seems that one advantage of debootstrap over multistrap is that debootstrap doesn't itself need dpkg/apt. Seems to me that once the new debootstrap debian system is built in a chroot then that could be used to complete the build(?) - i.e. maybe arranged thus could then indeed use even a non-debian-type Puppy system (or any Linux system) for the build?

multistrap:

https://wiki.debian.org/Multistrap

Quote:
Its main limitation compared to debootstrap is that it uses apt and dpkg directly so can only work on a debian system - debootstrap depends on nothing but shell, wget, binutils and thus can run pretty-much anywhere.

The main advantage with multistrap is the flexibility to mix packages from different repositories and different suites and manage customised variants with configuration files.

Last edited by wiak on Wed 02 Aug 2017, 21:00; edited 1 time in total
Back to top
View user's profile Send private message 
rcrsn51


Joined: 05 Sep 2006
Posts: 11729
Location: Stratford, Ontario

PostPosted: Wed 02 Aug 2017, 20:58    Post subject:  

wiak wrote:
Just thought it would be great if a Puppy user could use this to immediately build a DebianDog to a usb stick or something (or maybe a mod of this script could do that?).wiak


Quote:
Run from a Debian based system 32-bit or 64-bit (will create i686 (32-bit) or x86_64 (64-bit) live system accordingly to the architecture of the OS you are running from)


The script needs apt-get.
Back to top
View user's profile Send private message 
wiak

Joined: 11 Dec 2007
Posts: 372
Location: not Bulgaria

PostPosted: Wed 02 Aug 2017, 21:03    Post subject:  

Yes, I know the current mklive build script needs apt-get, but I have pointed out that debootstrap itself doesn't. I wondered if the debootstrap-created debian system (in a chroot) could as a secondary stage then be used to complete the build process (since that could use apt-get whereas the underlying system could be say a Puppy which itself couldn't use apt-get)? If you see what I mean.

Main thing I was thinking was that the script 'debootstrap' could itself be run under Puppy linux (or other Linux if desired) - creating a Debian system in a chroot (jail/container), and the rest of the mklive script run from that chroot (jail/container) thereafter...

wiak
Back to top
View user's profile Send private message 
mikeslr


Joined: 16 Jun 2008
Posts: 2020
Location: 500 seconds from Sol

PostPosted: Wed 02 Aug 2017, 22:18    Post subject:  

Hi wiak,

Eight months ago I posed the challenge of adding adrive builder, apt or synaptic to Puppies (in general), mentioning those which already included apt and synaptic. http://murga-linux.com/puppy/viewtopic.php?t=109436.

To date, only Pelo has suggested this apt/synaptic solution. http://murga-linux.com/puppy/viewtopic.php?p=961960#961960. Neither Pelo nor I claim to have any expertise in programming. And I haven't had the time to explore the validity of his response.

You're welcome to 'give it a go.'

mikeslr
Back to top
View user's profile Send private message 
wiak

Joined: 11 Dec 2007
Posts: 372
Location: not Bulgaria

PostPosted: Wed 02 Aug 2017, 23:48    Post subject:  

mikeslr wrote:

Eight months ago I posed the challenge of adding adrive builder, apt or synaptic to Puppies (in general), mentioning those which already included apt and synaptic. http://murga-linux.com/puppy/viewtopic.php?t=109436.


That's not what I'm suggesting or have in mind mikeslr. Rather, I'm suggesting it should be reasonably easily possible to modify the fred-provided mklive-stretch build system in the first thread of this post such that it can be run from a standard Puppy (or other Linux system) - the result will still be a debian-live debiandog type system rather than an otherwise standard Puppy with apt/dpkg capability.

I do have a technical background but it is in project management and not myself programming per se. As a project manager I look for general purpose methodologies rather than a specific implementation (such as, in this case, a mklive-stretch build system that needs to be run from a Debian apt/dpkg capable system - via chroot second stage, I doubt that limitation is necessary, and via modularisation I do not see that 'stretch' needs to be a specified limitation either, so if modularised appropriately I believe it shouldn't be later necessary to rewrite an almost identical mklive build script to build non-stretch system). Making a good project great is often about implementing a specific idea in a more general purpose manner (indeed traditional Unix philosophy works in that direction).

EDIT: If you go too far down the path on a design that is very specific it becomes much harder later to universalise/generalise the method - hence the importance to modularise and generalise as close as possible to the germination of the project idea. To put it another way, at the beginning, things are reasonably simple; that's the best time to invest in looking for most general purpose/flexible solutions.

wiak

EDIT2: I have total faith, by the way, that Fred himself is perfectly capable of relatively easily making this script work the way I suggest. All changes require some extra work (and tests of course) but now would be the time... But of course he might not like the suggested approach or want to implement it, which is fine.
Back to top
View user's profile Send private message 
fredx181


Joined: 11 Dec 2013
Posts: 2604
Location: holland

PostPosted: Thu 03 Aug 2017, 04:04    Post subject:  

Hi wiak,

I think I see what you mean, something like: once the chroot is created by debootstrap, Debian management will 'take over' so it could maybe work from a non-Debian OS, right?
Well, I had a quick look at the dependencies for debootstrap in DEBIAN/control file, only mentioned is "wget", so that looks good.
But further I looked inside the debootstrap script and noticed some "dpkg" command lines, so the host OS probably needs dpkg installed to make debootsrap work. Question
On line 109 of the mklive-stretch script (first stage, still outside chroot):
Code:
apt-get install debootstrap wget xorriso isolinux xz-utils squashfs-tools -y --force-yes

debootstrap is no more than a script and the other dependencies can be installed on a Puppy I guess (xorriso and isolinux are just to create ISO, but can be done in other ways also, using genisoimage, and squashfs-tools (for mksquashfs) is included in any puppy)
Then line 115 runs debootstrap
Code:
debootstrap --arch=$ARCH --variant=minbase stretch chroot http://ftp.us.debian.org/debian/


I attached the debootstrap script, to test in puppy, just extract it somewhere in PATH, e.g. /usr/bin/
So maybe, just maybe, if a Puppy has dpkg, things might work.

To be honest, at this point of time, I don't feel like trying to make this work in puppy, prefer to focus now on other things.
But if you or anyone want to go the road to make it work on Puppy, I can help in some way maybe.
I think the best is to try first if debootsrap works OK, by for example for 32-bit:
Code:
mkdir -p stretch/chroot && cd stretch
debootstrap --arch=i386 --variant=minbase stretch chroot http://ftp.us.debian.org/debian/



Fred
debootstrap.tar.gz
Description  debootstrap (script only)
gz

 Download 
Filename  debootstrap.tar.gz 
Filesize  5.46 KB 
Downloaded  29 Time(s) 

Last edited by fredx181 on Thu 03 Aug 2017, 04:30; edited 2 times in total
Back to top
View user's profile Send private message 
fredx181


Joined: 11 Dec 2013
Posts: 2604
Location: holland

PostPosted: Thu 03 Aug 2017, 04:14    Post subject:  

rcrsn51 wrote:
I am sending you PWF v4.5 which moves rc.network into /etc/pwf. This should solve your problem.


Probably the best is to modify the remaster scripts and others (so that it doesn't remove /etc/rc.d) and build new packages because there are more programs that include /etc/rc.d, e.g. your peasy firewall monitor (and maybe more I can't think of now)
But thanks anyway !

Fred

_________________
Dog Linux website
Back to top
View user's profile Send private message 
wiak

Joined: 11 Dec 2007
Posts: 372
Location: not Bulgaria

PostPosted: Thu 03 Aug 2017, 04:32    Post subject:  

fredx181 wrote:

But further I looked inside the debootstrap script and noticed some "dpkg" command lines, so the host OS probably needs dpkg installed to make debootsrap work. Question


Thanks Fred,

I quickly looked inside debootstrap, and it seems to me that you just need to give the arch and for such case dpkg being installed isn't a requirement. Here are the lines from debootstrap usage I noticed (particularly note the last line):

Code:
usage()
{
   echo "Usage: ${0##*/} [OPTION]... <suite> <target> [<mirror> [<script>]]"
   echo "Bootstrap a Debian base system into a target directory."
   echo
   cat <<EOF
      --help                 display this help and exit
      --version              display version information and exit
      --verbose              don't turn off the output of wget

      --download-only        download packages, but don't perform installation
      --print-debs           print the packages to be installed, and exit

      --arch=A               set the architecture to install (use if no dpkg)
                               [ --arch=powerpc ]


Probably needs someone more skilled in progamming than me though, and not essential anyway I realise! The idea can be kept in mind maybe though as things get developed.

EDIT: Having said that, I maybe will do my best to try and check debootstrap working in a Puppy since I think I understand maybe enough for that testing stage. First I have to install a Puppy though since I don't have one on here just now! Smile I'll try on a Slacko, just for proof of concept...

wiak

Last edited by wiak on Thu 03 Aug 2017, 04:54; edited 1 time in total
Back to top
View user's profile Send private message 
fredx181


Joined: 11 Dec 2013
Posts: 2604
Location: holland

PostPosted: Thu 03 Aug 2017, 04:45    Post subject:  

wiak wrote:
I quickly looked inside debootstrap, and it seems to me that you just need to give the arch and for such case dpkg being installed isn't a requirement. Here are the lines from debootstrap usage I noticed (particularly note the last line):

Ok, just a matter of trying it out then, if the debootstrap process works properly, then simply do (chroot binary required):
Code:
chroot chroot # if chroot is the name of directory already created

And then see if "apt-get install <somepackage>" works.

EDIT: sorry there's more required to test that, see here:
https://github.com/DebianDog/MakeLive/blob/gh-pages/README-Stretch.md#mount-bind-proc-dev-and-sys-in-chroot

@dancytron
Quote:
I think an improvement might be to allow specifying additional repositories as a variable in the script. Of course, I'm thinking of Chrome, but there are lots of other "independent" Debian/Ubuntu repositories out there that people might want to use.


Yes, good idea, probably that's rather easy to implement.
You think of also your special setup for running chrome as normal user ?
Btw, as it is now there's only root account, no multiuser support I tested yet.

Fred
Back to top
View user's profile Send private message 
Display posts from previous:   Sort by:   
Page 2 of 59 [878 Posts]   Goto page: Previous 1, 2, 3, 4, ..., 57, 58, 59 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.0773s ][ Queries: 14 (0.0087s) ][ GZIP on ]