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 Wed 12 Dec 2018, 17:32
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 18 of 95 [1417 Posts]   Goto page: Previous 1, 2, 3, ..., 16, 17, 18, 19, 20, ..., 93, 94, 95 Next
Author Message
dancytron

Joined: 18 Jul 2012
Posts: 1162

PostPosted: Mon 14 Aug 2017, 03:03    Post subject:  

zagreb999 wrote:
regards dancytron

stretchdogt is installed with unetbootin
as xenialdog and debiandog.
i do not create any menu.1s

stretchdog can not boot,
xenial and debian boot
perfectly


I don't use unetbootin, but took a quick look at their website.

Unetbootin should have created a file called syslinux.cfg that is the equivalent of the menu.1st file in grub4dos. Your problem is in that file.

Show that file to us and we might be able to fix it.
Back to top
View user's profile Send private message 
zagreb999

Joined: 11 Apr 2014
Posts: 406
Location: Yugoslavija

PostPosted: Mon 14 Aug 2017, 03:18    Post subject:  

dancytron ,
this stretcdog k.4.9 is installed
with debiandog installer.
here is menu.1st
and screenshot
regards.


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

# menu.lst produced by grub4dosconfig-v1.7
color white/blue black/cyan white/black cyan/black
timeout 10
default 0

title Debian-PorteusDog - changes to /live/ sysvinit
uuid BCAD-B3FE
kernel /live/vmlinuz1 from=/ noauto changes=/live/
initrd /live/initrd1.xz

title Debian-PorteusDog - Always Fresh sysvinit
uuid BCAD-B3FE
kernel /live/vmlinuz1 from=/ nomagic base_only norootcopy
initrd /live/initrd1.xz

title Debian-PorteusDog - Copy to RAM sysvinit
uuid BCAD-B3FE
kernel /live/vmlinuz1 noauto from=/ copy2ram
initrd /live/initrd1.xz

title DebianDog - live-boot-3 (default Debian) Persistence Changes sysvinit
uuid BCAD-B3FE
kernel /live/vmlinuz1 boot=live persistence config quickreboot noeject autologin
initrd /live/initrd.img

title DebianDog - live-boot-3 (default Debian) (no persistence) sysvinit
uuid BCAD-B3FE
kernel /live/vmlinuz1 boot=live config quickreboot noeject autologin
initrd /live/initrd.img

title Reboot computer
reboot
screenshot.png
Description 
png

 Download 
Filename  screenshot.png 
Filesize  72.41 KB 
Downloaded  80 Time(s) 
Back to top
View user's profile Send private message 
dancytron

Joined: 18 Jul 2012
Posts: 1162

PostPosted: Mon 14 Aug 2017, 03:33    Post subject:  

I don't see anything obviously wrong.

It is very late here. I will look at it tomorrow if no one else has figured it out by then.

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

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

PostPosted: Mon 14 Aug 2017, 03:49    Post subject: debootstrap fix found for xenialdog 32 bit version...  

anikin wrote:
anikin wrote:
. . .
Regarding debootstrap not working in XenialDog, I think, I know why, but I need to download and install XenialDog and try running debootstrap from it.

In a nutshell, here's why debootstrap fails in XenialDog:

Debian Stretch was supposed to have this new feature: https://wiki.debian.org/UsrMerge
However, at the end of the day, that plan had been scrapped, http://www.phoronix.com/scan.php?page=news_item&px=Debian-Installer-Stretch-RC1 because of a bug discovered in debootstrap version 0.85. Supposedly, that version of debbotstrap had been used to build Ubuntu Xenial. See here for more details:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=843073
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=844221

So, this is an inherited bug. It was present in the early builds of Ubuntu Xenial. To cut it short, if you rebuild Xenial today, it will be debootstrap friendly.


Hi Fred,

SUCCESS! Smile

I was a bit side-tracked by anikin's certainty above so spent too much time trying to debug the error occurrence in xenialdog32 debootstrap scripts themselves to try and understand how the above issues affected anything (since I didn't understand how that could be and turns out they weren't relevant at all).

Also I wasn't happy to accept that the only solution was a new xenial 32-bit install and so was stubbornly looking for a workaround. However, I suddenly noticed that the issue with debootstrap under XenialDog32 occurred when the script tries to run dpkg via a chroot during the debootstrap second stage installation phase (yes, I know the script pretty well now!) and that sent me down the correct debug road:

Code:
In debootstrap functions:

in_target () {
   in_target_failmsg IN_TARGET_FAIL "Failure trying to run: %s" "$CHROOT_CMD $*" "$@"
}

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

In target 'sid' (which is stretch):

   x_core_install () {
      smallyes '' | in_target dpkg --force-depends --install $(debfor "$@")
   }


That dpkg line above was failing because of busybox chroot being used instead of the also installed chroot from coreutils.


Anyway, to cut a long story short:

In a terminal on XenailDog32 entered:

Code:
which chroot

/bin/chroot

ls -al /bin/chroot


turns out was busybox symlinked version, which debootstrap doesn't like...

Such a simple matter afterall!!!

Because /bin/chroot came earlier in the XenialDog32 executable PATH it was taking precedence over the coreutils chroot, which is in /usr/sbin.

So solution was simply:

Code:
rm /bin/chroot


After that, debootstrap works fine now under XenialDog 32 bit.

Smile

I guess it would be a good idea to check no other busybox util versions are taking PATH precedence over their coreutils counterparts.

wiak


Not sure what all that stuff you were writing, anikin, is about really - but clearly nothing to do with our xenialdog32 debootstrap problem, as it turns out, sorry - but good try anyway. Wink Thank goodness it was such an easy fix in actuality.
Back to top
View user's profile Send private message 
fredx181


Joined: 11 Dec 2013
Posts: 3575
Location: holland

PostPosted: Mon 14 Aug 2017, 04:35    Post subject:  

@wiak

Quote:
SUCCESS! Smile
....
....


Hey! Nice discovery, congrats and thanks!
Btw, it doesn't surprise me that it turned out to be such a simple thing, all the time I had the feeling it could be fixed, but how...., now we know Smile .

@ dancytron
Maybe you did already, but anyway I ask:
- Can you mount the 01-filesystem.squashfs from the build and see if there's the older save2flash inside or not
- Look inside folder dog-boot-stretch from build and also check the save2flash
The "dog-boot" tar.gz from github is for the Jessie Makelive with the netinstall setup.

Fred
Back to top
View user's profile Send private message 
anikin

Joined: 10 May 2012
Posts: 1020

PostPosted: Mon 14 Aug 2017, 04:45    Post subject:  

wiak, nice discovery, however, the root cause still remains. ***The bug was introduced by debootstrap version 0.85***. If you debootstrap/rebuild Xenial with a different version of debootstrap (which I've tested), you will have a clean build without this bug. It's that simple.
Back to top
View user's profile Send private message 
rufwoof

Joined: 24 Feb 2014
Posts: 2711

PostPosted: Mon 14 Aug 2017, 04:58    Post subject:  

anikin wrote:
rufwoof wrote:
. . . That said for Stretch I have installed gtk2 adwaita and qt4/qt5 adwaita also, to go along with the default inbuilt adwaita gtk3
This one? https://packages.debian.org/stretch/gnome-themes-standard

Yes ... and adwaita-qt4 and adwaita-qt (for qt5, for instance more recent versions of vlc)

_________________
( ͡° ͜ʖ ͡°) :wq
Back to top
View user's profile Send private message 
saintless


Joined: 11 Jun 2011
Posts: 3882
Location: Bulgaria

PostPosted: Mon 14 Aug 2017, 05:03    Post subject:  

wiak wrote:
Code:
which chroot

/bin/chroot

ls -al /bin/chroot


turns out was busybox symlinked version, which debootstrap doesn't like...

Such a simple matter afterall!!!

Because /bin/chroot came earlier in the XenialDog32 executable PATH it was taking precedence over the coreutils chroot, which is in /usr/sbin.

So solution was simply:

Code:
rm /bin/chroot


The /bin/chroot symlink to busybox was a fix to make porteus-boot work in DebianDog. It is a bug in initrd1.xz linuxrc script which should call /usr/sbin/chroot (the official distro version) fixed a long time ago here:
https://github.com/MintPup/DebianDog-Wheezy/commit/7beca5e0c26ecb7064ecf68f4c23d5d1fd45b302
Maybe Fred has this fix in XenialDog32 initrd1.xz but I'm not sure.
In short in any Dog based distro /bin/chroot should be removed and also /bin/awk (if it is still present in DebianDog forks).

Edit: BTW I have a lot of troubles lately experimenting with different busybox versions inside initrd image. One version fixes one problem and breaks well working functions from previous version. Maybe compiling issues and diferences. It is always better to use official distro binary instead symlink to busybox. Like symlinking /bin/chroot to /usr/sbin/chroot instead to busybox.

Toni

_________________
Farewell, Nooby, you will be missed...
Back to top
View user's profile Send private message MSN Messenger 
fredx181


Joined: 11 Dec 2013
Posts: 3575
Location: holland

PostPosted: Mon 14 Aug 2017, 07:00    Post subject:  

wiak wrote:
So solution was simply:

Code:
rm /bin/chroot

After that, debootstrap works fine now under XenialDog 32 bit.


The downside is that if you reboot (with saving changes) after removing /bin/chroot Xenialdog32 won't boot anymore, message at boot:
Code:
bin/chroot: Not found

So indeed as saintles said, better instead of removing, create symlink to /usr/sbin/chroot:
Code:
ln -sf /usr/sbin/chroot /bin/chroot


Fred
Back to top
View user's profile Send private message 
anikin

Joined: 10 May 2012
Posts: 1020

PostPosted: Mon 14 Aug 2017, 12:42    Post subject:  

wiak's discovery was good, but Toni's isn't any worse either Smile That being said, if I were in charge, I'd simply stick to the official Debian boot procedures and discard all these DD boot methods - 2, 3 and Porteus-boot.
Back to top
View user's profile Send private message 
peebee


Joined: 21 Sep 2008
Posts: 3568
Location: Worcestershire, UK

PostPosted: Mon 14 Aug 2017, 13:37    Post subject:  

If I add gnome-mplayer (available at https://fredx181.github.io/StretchDog/i386/Packages/Included/gnome-mplayer-1.0.7_1.0.6.2_i386.deb ??) to the build I get the following error:
Code:
Package gnome-mplayer is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source
However the following packages replace it:
  gnome-mplayer-1.0.7

E: Package 'gnome-mplayer' has no installation candidate

_________________
LxPup = Puppy + LXDE
Back to top
View user's profile Send private message Visit poster's website 
jd7654

Joined: 06 Apr 2015
Posts: 257

PostPosted: Mon 14 Aug 2017, 14:05    Post subject:  

peebee wrote:
If I add gnome-mplayer (available at https://fredx181.github.io/StretchDog/i386/Packages/Included/gnome-mplayer-1.0.7_1.0.6.2_i386.deb ??) to the build I get the following error:
Code:
Package gnome-mplayer is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source
However the following packages replace it:
  gnome-mplayer-1.0.7

E: Package 'gnome-mplayer' has no installation candidate


Yeah, I ran into that too. I had to explicitly state gnome-mplayer-1.0.6 and then it worked.

Strange as though all the other packages installed by the base name: (Mate build)
Code:
live-boot wget net-tools ifupdown wireless-tools sysvinit-core xserver-xorg-core xserver-xorg psmisc fuse x11-utils x11-xserver-utils dbus-x11 busybox sudo mawk xinit xterm pciutils usbutils file rsync dosfstools exfat-fuse exfat-utils ntfs-3g

mate-core menu pluma gparted parted pv synaptic volumeicon-alsa alsa-utils viewnior pm-utils xdotool wmctrl desktop-file-utils mime-support cryptsetup-bin squashfs-tools conky fakeroot xserver-xorg-input-evdev xserver-xorg-input-synaptics pfind chromium gnome-mplayer-1.0.6

yad gtkdialog obshutdown pup-volume-monitor peasywifi remaster-scripts quick-remaster apt2sfs sfsload fixdepinstall greybird-theme-dd-stretch makedebpackage flashplayerchoice

firmware-linux-free firmware-linux-nonfree


Still, much easier than woof!
Back to top
View user's profile Send private message 
rcrsn51


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

PostPosted: Mon 14 Aug 2017, 14:21    Post subject:  

jd7654 wrote:
I had to explicitly state gnome-mplayer-1.0.6 and then it worked.

Did you mean "gnome-mplayer-1.0.7"? Because that is correct package name in Fred's repo.
Back to top
View user's profile Send private message 
jd7654

Joined: 06 Apr 2015
Posts: 257

PostPosted: Mon 14 Aug 2017, 14:27    Post subject:  

rcrsn51 wrote:
jd7654 wrote:
I had to explicitly state gnome-mplayer-1.0.6 and then it worked.

Did you mean "gnome-mplayer-1.0.7"? Because that is correct package name in Fred's repo.


It worked as 1.0.6. Not sure how I got that. I think I apt-get installed in the live distro, and that is what it pulled from deb. So I just put that in builder. I could be mistaken, but saw the same error and 1.0.6 in above recipe worked.

EDIT: confirmed. I had some other DebLive amd64 ISOs lying around, tried boot fresh again. That gnome-mplayer-1.0.6 is what gets pulled: (abbreviated log)

Code:
root@live:~# apt-get update
Get:1 http://security.debian.org/debian-security stretch/updates InRelease [62.9 kB]
...         
Reading package lists... Done

root@live:~# apt-get install gnome-mplayer
Reading package lists... Done
...
Package gnome-mplayer is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source
However the following packages replace it:
  gnome-mplayer-1.0.6
E: Package 'gnome-mplayer' has no installation candidate

root@live:~# apt-get install gnome-mplayer-1.0.6
Reading package lists... Done
...
0 upgraded, 43 newly installed, 0 to remove and 4 not upgraded.
Need to get 9488 kB of archives.
After this operation, 17.9 MB of additional disk space will be used.
Do you want to continue? [Y/n]
Get:1 http://ftp.de.debian.org/debian stretch/main amd64 libcdparanoia0 amd64 3.10.2+debian-11 [56.6 kB]
...
Get:43 https://fredx181.github.io/StretchDog/amd64/Packages ./ gnome-mplayer-1.0.6 1.0.6-2 [3321 kB]
Fetched 9488 kB in 8s (1174 kB/s)   
...                                             
Setting up gnome-mplayer-1.0.6 (1.0.6-2) ...
Processing triggers for libc-bin (2.24-11+deb9u1) ...
Processing triggers for menu (2.1.47+b1) ...
root@live:~#
Back to top
View user's profile Send private message 
wiak

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

PostPosted: Mon 14 Aug 2017, 16:16    Post subject:  

saintless wrote:

The /bin/chroot symlink to busybox was a fix to make porteus-boot work in DebianDog. It is a bug in initrd1.xz linuxrc script which should call /usr/sbin/chroot (the official distro version) fixed a long time ago here:
https://github.com/MintPup/DebianDog-Wheezy/commit/7beca5e0c26ecb7064ecf68f4c23d5d1fd45b302
Maybe Fred has this fix in XenialDog32 initrd1.xz but I'm not sure.
In short in any Dog based distro /bin/chroot should be removed and also /bin/awk (if it is still present in DebianDog forks).


Yes, I hadn't rebooted at that point and my fix to use coreutils chroot was the only 'discovery' I was making concerning debootstrap and happy xenialdog32 not needing rebuilt as earlier 'forecast'. I was using a pristine XenialDog32 at that point of course so no changes/DebianDog_xdinitrd.xz issue involved at that point! Wink

wiak
Back to top
View user's profile Send private message 
Display posts from previous:   Sort by:   
Page 18 of 95 [1417 Posts]   Goto page: Previous 1, 2, 3, ..., 16, 17, 18, 19, 20, ..., 93, 94, 95 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.1031s ][ Queries: 12 (0.0254s) ][ GZIP on ]