(OLD) (ARCHIVED) Puppy Linux Discussion Forum Forum Index (OLD) (ARCHIVED) Puppy Linux Discussion Forum
Puppy HOME page : puppylinux.com
"THE" alternative forum : puppylinux.info

This forum can also be accessed as http://oldforum.puppylinux.com
It is now read-only and serves only as archives.

Please register over the NEW forum
https://forum.puppylinux.com
and continue your work there. Thank you.

 
 FAQFAQ   SearchSearch   MemberlistMemberlist   UsergroupsUsergroups    
 ProfileProfile   Log in to check your private messagesLog in to check your private messages   Log inLog in 

The time now is Thu 24 Sep 2020, 08:51
All times are UTC - 4
 Forum index » Advanced Topics » Puppy Projects
DebianDog64 - 64 bit DebianDog-Jessie
Moderators: Flash, JohnMurga
This forum is locked: you cannot post, reply to, or edit topics.   This topic is locked: you cannot edit posts or make replies. View previous topic :: View next topic
Page 18 of 38 [560 Posts]   Goto page: Previous 1, 2, 3, ..., 16, 17, 18, 19, 20, ..., 36, 37, 38 Next
Author Message
dancytron

Joined: 18 Jul 2012
Posts: 1555

PostPosted: Thu 07 Jul 2016, 16:33    Post subject:  

Is anyone (Netflix users?) interested in a remastered Debian Dog 64 with Chrome as the browser?

I have one that I think would just need a few little tiny touch ups I'd be happy to share if anyone is interested.
Back to top
View user's profile Send private message 
mcewanw

Joined: 16 Aug 2007
Posts: 3200

PostPosted: Thu 07 Jul 2016, 19:44    Post subject:  

fredx181 wrote:
Hi All,

DebianDog website launched (includes similar projects, such as this DebianDog64), see more info here:
http://www.murga-linux.com/puppy/viewtopic.php?p=911585#911585

Fred


Nice looking website, Fred. I was just thinking, the other day, that DebianDog family could do with having a website, so happy to see it. I thought you must be busy on something since you went quiet for a wee while. I've been partly the same since working on new app that I first planned out two years ago! Finished the difficult stuff (the C code) now so at least my brain has been having a needed workout. Whether I end up releasing the final product is dubious though since then I'd need to maintain it for self-named passengers like Pelo(!) - who has an attitude I'm not keen to encourage.

Webpage development work may be a better use of time. I'm keen to check out these website development facilities of github - funnily enough, I haven't been using github at all since the days I started writing about using it in old thread posts... my bad. Glad Toni and yourself took off in that direction though.

One thing I would like to see (in addition to the excellent Remastering facilities already provided in DebianDog family) is some automatic way to take a new Debian/Mint/Ubuntu version and forge it into DebianDog 'style' rather than rely on hand building the basics on top of minimum base big distribution installs. I note, for example, that someone is asking if a new MintPup could be built to use Linux Mint 18 - if only that could be scripted DebianDog would last forever... even if we all became too lazy, tired, or otherwise unenthusiastic of continuing with it.

William

_________________
github mcewanw
Back to top
View user's profile Send private message Visit poster's website 
backi

Joined: 27 Feb 2011
Posts: 2007
Location: GERMANY

PostPosted: Fri 08 Jul 2016, 07:12    Post subject:  

Hi mcewanw !

" One thing I would like to see (in addition to the excellent Remastering facilities already provided in Debian-Dog family) is some automatic way to take a new Debian/Mint/Ubuntu version and forge it into Debian-Dog 'style' rather than rely on hand building the basics on top of minimum base big distribution installs.
I note, for example, that someone is asking if a new MintPup could be built to use Linux Mint 18 - if only that could be scripted DebianDog would last forever... even if we all became too lazy, tired, or otherwise unenthusiastic of continuing with it. "

This is a very constructive idea to keep the evolution of the Dog type family going into direction of a kind of "Super-breed"....if not " inmortal"... but as a real force in the world of Linux Distros one have to reckon with .
A type of concept which i`ve been waiting longer for.

This concept is much more flexible than " Old School "
Hard-disk installs ....and a lot more advanced
(please don`t get me wrong ) than just a "simple - normal " Puppy .
Getting access to the repos of major Distros and simultaneously using all those goodies from Puppies ,means a Quantum Leap forward from (please don`t get me wrong again ) ....
...from a niche Distro ( a fine niche ...i have to admit ) like Puppies...getting access to the "Silk-Road "...the " Super-Highway" or the " Panama Canal " to the most important Mainstream Distros. .........

This is a major " Break Through" ,not only for Puppies, ..but for Linux world en general.
I am not a Linux Nerd or specialist...but so i feel .
Let me tell you ...

I am totally impressed ...this D-D and friends project is a real "Killer".....a real Champion .

I do promote it when ever and where ever i can .

Cheers !
Back to top
View user's profile Send private message 
fredx181


Joined: 11 Dec 2013
Posts: 4481
Location: holland

PostPosted: Fri 08 Jul 2016, 15:47    Post subject:  

Hi William, backi,

William wrote:
One thing I would like to see (in addition to the excellent Remastering facilities already provided in DebianDog family) is some automatic way to take a new Debian/Mint/Ubuntu version and forge it into DebianDog 'style' rather than rely on hand building the basics on top of minimum base big distribution installs. I note, for example, that someone is asking if a new MintPup could be built to use Linux Mint 18 - if only that could be scripted DebianDog would last forever... even if we all became too lazy, tired, or otherwise unenthusiastic of continuing with it.


Not sure if I understand well, you mean for example when Stretch becomes stable to transform the official Debian Stetch live cd into DebianDog 'style' ?
Something like that would be great, I will think about it, although I'm not very optimistic that it can be scripted.
To make it work with several distros it will probably be a hit and miss thing.
What we did with Jessie was just upgrading Wheezy by replacing 'wheezy' with 'jessie' in /etc/apt/sources.list and "apt-get dist-upgrade". That went pretty well (except for systemd transformation if I remember well)
I tried similar with Jessie>Stretch and there were lots of complications, e.g aufs module not included in newer Debian kernel (they use different layering method now instead of aufs, can't remember the name for it right now).
Toni used an existing live distribution and stripped it. I did different with XenialDog and DD64 by making a minimal full install first, added applications and used remasterdog (which worked fine BTW).

It's complicated, there's also the initrd for porteus-boot that needs modified etc...

Good luck with your program, don't get distracted by some "passenger" Wink

@backi
Quote:
...from a niche Distro ( a fine niche ...i have to admit ) like Puppies...getting access to the "Silk-Road "...the " Super-Highway" or the " Panama Canal " to the most important Mainstream Distros. .........
......
I do promote it when ever and where ever i can .


Maybe I'll add a new section on the dog website and you write some more poetry about DD there... Smile
Probably I will extend it more anyway, howto's etc..

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

Joined: 16 Aug 2007
Posts: 3200

PostPosted: Fri 08 Jul 2016, 18:01    Post subject:  

fredx181 wrote:

Not sure if I understand well, you mean for example when Stretch becomes stable to transform the official Debian Stetch live cd into DebianDog 'style' ?


Yes, that is that I meant Fred.

I realise that it may be difficult to automate such a process reliably from distribution to distribution since their own contents and internal mechanisms are a bit of a moving target.

William

_________________
github mcewanw
Back to top
View user's profile Send private message Visit poster's website 
Belham

Joined: 07 Jan 2016
Posts: 133

PostPosted: Sun 10 Jul 2016, 12:27    Post subject: firewall  

Hi Fred and/or anyone that uses DD,

I've sort of a stupid question: in all this time I've used DD64 (I automatically always install ufw/gufw) I've never paid attention if there is already a firewall included in Debian Dogs? Is there?? I looked everywhere through the menu and start up services, couldn't find anything, so I assume there isn't one unless we install it. Correct?


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


Joined: 24 Feb 2014
Posts: 3725

PostPosted: Sun 10 Jul 2016, 12:41    Post subject: Re: firewall  

Belham wrote:
Hi Fred and/or anyone that uses DD,

I've sort of a stupid question: in all this time I've used DD64 (I automatically always install ufw/gufw) I've never paid attention if there is already a firewall included in Debian Dogs? Is there?? I looked everywhere through the menu and start up services, couldn't find anything, so I assume there isn't one unless we install it. Correct? Thanks.

I don't think there is a firewall by default, you have to install it as you say (??? not 100% sure). Personally I don't bother as I sit behind a Virgin Media cable modem that has a firewall and behind that I'm hard wired into a router (Netgear) that also has a firewall and where wireless on that router is disabled (hard wired connections only). So a firewall would only be protecting against other family members ... easier for them to just walk across the room and turn the PC on to 'break-in'. If we connected direct to the main cable modem that also has wireless activated then I'd be more inclined to install a firewall on the PC's.
Back to top
View user's profile Send private message 
mcewanw

Joined: 16 Aug 2007
Posts: 3200

PostPosted: Mon 11 Jul 2016, 00:05    Post subject:  

fredx181 wrote:

Good luck with your program, don't get distracted by some "passenger" :wink:


Nearing completion actually. I "think" I have finished the hard stuff (required C code backend). Now working on gui, which is coming along fine, but boring work compared to mind-twisting C... Were it not for the kids suddenly being on school holiday here (for the next 2 weeks) I'd probably be able to make first release today or tomorrow. Certainly looks like it 'should' be finished within a week though (or I am guilty of extreme laziness, or something diabolical crops up unexpectedly in the code, which seems unlikely now...).

Of course, me posting anything on murga forum at the moment is just me lazily distracting myself from what I should be doing. Bye!

William

_________________
github mcewanw
Back to top
View user's profile Send private message Visit poster's website 
learnhow2code

Joined: 12 Jun 2016
Posts: 1015

PostPosted: Mon 11 Jul 2016, 01:08    Post subject:  

fredx181 wrote:
you mean for example when Stretch becomes stable to transform the official Debian Stetch live cd into DebianDog 'style' ?
Something like that would be great, I will think about it, although I'm not very optimistic that it can be scripted.
To make it work with several distros it will probably be a hit and miss thing.


i think its quite a viable idea, which can be done one of the following ways:

* the script is automated, but the output will need some coaxing
* the script is automated, but the input will need some coaxing
* the script is automated, but the script will need some tweaking/configuration/updating
* one or more of the above

in each case, the script saves lots of work. the better the script is, the more work it saves. the script still requires a person to run it and see what comes out, and possibly do more.

_________________
users | devs
fig os 1.3 md5
Back to top
View user's profile Send private message 
Belham

Joined: 07 Jan 2016
Posts: 133

PostPosted: Mon 11 Jul 2016, 08:48    Post subject: DebianDog installer  

Hi all,

Have a question about using DebianDog installer, wanting to install DD64 from its current running USB onto another bigger USB SATA HD enclosure partition. I am so used to running stuff off USB and/or SD cards, or either actually using a download ISO to install to a partition, that I've gone braindead just wanting to install DD64 here (booted the USB it is on as "Always Fresh, and there's no savefile and/or change folders/files to worry about).

On the DD installer that popped up, I selected my partition (it already been set up with Gpart, and formatted to Ext4...there are 5 other puppies on different partitions there Very Happy ), so when I am looking at this DD installer, and I don't want to re-download the DD64 ISO to install it that way, exactly what do i choose under the "OR SELECT DIRECTORY" and the "DebianDog FOLDER" underneath oit?? The partition it will be on is currently under the control of Grub4Dos for this external SATA USB HD enclosure.

Sorry for going braindead today Rolling Eyes


(EDIT: Is it maybe the /live/image/live/ folder's contents to the partition? In other words, the empty base folder, the empty modules folder, the empty optional folder, the empty "rootcopy" folder, and then the meat & potatoes of the 01-filesystem.squashfs., the initd.img, the initrd1.xz, the jessie-x86_64.sgn and finally the vmlinuz1?

And then use which ones for entry into Grub4dos? vmlinuz1 and initrd.img only??)


EDIT2...am giving up and re-downloading the ISO. I tried copying th empty base, modules, optional and rootcopy folders straight to the partition, then also copied the jessie-x86_64.sgn, the 01-filesystem.squashfs, the initrd.img, the initrd1.xz, the vmlinuz1. I then entered in Grub4dos (for the partition that these are now on):

title DebianDog64 (sda4/boot)
UUID ######-######-######-#.....(I put the actual UUID)
kernel /boot/vmlinuz1 root=/dev/sda4 ro
initrd /boot/initrd1.xz

got nothing...then tried..

title DebianDog64 (sda4/boot)
UUID ######-######-######-#.....(I put the actual UUID)
kernel /vmlinuz1 root=/dev/sda4 ro
initrd /initrd1.xz

..got more nothing except again, Error 22, saying no directory or files there Lastly, in desperation, tried to point to the squashfs (renamed it to .sfs ending)

title DebianDog64 (sda4/boot)
UUID ######-######-######-#.....(I put the actual UUID in)
kernel /boot/vmlinuz1 root=/dev/sda4 ro basesfs=local:/boot/01-filesystem.sfs
initrd /boot/initrd1.xz

...and again got more nothing except same error. I know I am screwing something up all around here, lol, but as I said, am too braindead to figure it out.

Oh well, soon as I get time this evening am going to re-get the ISO gownload so I can point the DebianDog installer to it and let it do it correctly
Back to top
View user's profile Send private message 
Belham

Joined: 07 Jan 2016
Posts: 133

PostPosted: Mon 11 Jul 2016, 11:23    Post subject:  

Ok, something is not making sense:

On a separate, good functioning USB that has DebianDog64 DD on it working great (where it boots up fine in any mode you choose), I then booted it up to "Always Fresh" and used the included DebianDog64 installer to install a freshly downloaded ISO to a partition of another external USB that I have (a 160GB Sate drive) which has many other puppies and other Linux OSes on it.

This 160GB sata drive already has Fatdog64, Tahr64, Quirky 8.0, Slacko64, among other OSes, each on their own 10GB partitions, each booting greatly with grub4dos. The DebianDob64 install went to partition 4, everything went great, even decided to let reinstall Grub4dos and have that partition take over the Grub4dos work. I copied all my old grub4dos entries, put them in the new menu.lst on partition 4, and then booted up.

All of the different OSes bootup great, but when i try to boot any one of the debiandog64 entries, this is what I get after it spins up:

ERROR 13: INVALID OR UNSUPPORTED EXECUTABLE FORMAT

Here's an example of the exact message when trying to bootup, picking one at random, Debian-PorteusDog:

"Booting Debian-PorteusDog - Always Fresh sysvinit
setting root to (hd0,3)
Filesystem type is ext2fs, partition type 0x83
[Linux-bzImage, setup=0x4200, size=0x2f3b40]
initrd /live/initrd1.xz

Error 13: Invalid or unsupported executable format

PRess any key to continue..."
(which takes you back to the Grub4Dos boot screen, where all other Linux OSes will boot, but none of the Debain ones)


Below are a sampling of some of the grub4dos entries, all of them function except for the ones the DebianDog Installer actually installed. Not one of those will boot up and instead throws the error 13 mentioned above:

(plz note: all UUIDs are removed, there's no reason to post those)

title Fatdog64 (sda1/boot)
uuid
kernel /boot/vmlinuz rootfstype=ramfs basesfs=local:/boot/fd64.sfs
initrd /boot/initrd

title Quirky Xerus64 8.0 (sda5/xerus)
uuid
kernel /xerus/vmlinuz install_specs=UUID=:ext4:xerus
initrd /xerus/initrd.q

title Tahr64 6.0.5 CE (sda6/boot)
uuid
kernel /vmlinuz root=/dev/sda6 ro
initrd /initrd.gz

title Manjaro 16.06.1 XFCE (sda17/boot)
uuid
kernel /boot/vmlinuz-4.4-x86_64 root=/dev/sda17 rw
initrd /boot/initramfs-4.4-x86_64.img

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

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

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

title DebianDog - live-boot-3 Persistence Changes sysvinit
uuid
kernel /live/vmlinuz1 boot=live persistence config quickreboot noeject autologin
initrd /live/initrd.img

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

title DebianDog - live-boot-3 Copy to RAM sysvinit
uuid
kernel /live/vmlinuz1 boot=live toram=01-filesystem.squashfs
initrd /live/initrd.img


Can anyone provide any help?? Why would grub4dos, installed by the DebianDog64 installer itself, not make the correct grubdos entries to allow a person to boot any of the DD64 choices on its partition? And I know DD64's grub4dos install is acting correctly, because every other installed OS on this external USB Sata HD boots up fine using the grub4dos installed by DebianDog64. Yet, somehow, the entries it made for DebianDog64 itself, the grub4dos DD64 installed cannot boot them up, and instead throws that "Error 13" mentioned above. Crazy......!!!

Fred, what am I doing wrong???????[/u]
Back to top
View user's profile Send private message 
Belham

Joined: 07 Jan 2016
Posts: 133

PostPosted: Mon 11 Jul 2016, 13:49    Post subject:  

Just wanted to give an update to this nightmare DD64 install to a partition (on an 160GB Sata enclosure USB) from a fully functioning DD64 USB stick, using the DD64 Install program:

I managed to get a bit passed the grub4dos problem (I don't know if this makes a difference or not, but the Grub4Dos that DD64 Installer tries to install is Version 1.7. I have Version 1.9.2.

Well, I have removed DD64's older grub4dos installer, and used Fatdog64 Grub4dos installer to put grub4dos back on the 160GB Sata USB drive to control all the partitions. As mentioned earlier, all the DD64 Installer's original entries for grub4dos do not work. They continually thrwo up Error 13 no matter what.

I then started playing around, I copied over from the original working DD64 USB all the files that were originally alongside the LIVE folder. Then, I got this entry (something the DD64 Grub4Dos installer doesn't even come up with) to go the farthest in trying to boot anything up from the parititon DD64 is instaled to:

Debian
UUID (the UUID number goes here)
kernel /ubnkern
initrd /ubninit

This entry will begin the boot process, many lines of boot screen pass, pages pass in fact, then it stops at the:
[143.840497] random: nonblocking pool is initialized. From there, it just sits forever........ If I hit enter repeatedly here, I can get a "(initramfs)" prompt, but am unsure what to do with it.

I know this 160GB is good, that there is nothing wrong with it, because I have ran checks on it before ever putting any of the other puppies and other Linux OSes on it.

Whatever is going on is because of some mixup in DebianDog64 Installer installing to a partition. This doesn't matter if you install from a live, fresh USB and/or a live freshly burned CD. DebianDog64 just refuses, on all my systems, to be put on a partition & have the user control whether it boots or not via Grub4dos.

If DebianDog64 is installed to its own USB and/or CD, then it works. But something is screwing up when you want to run it on a partition, and the same hard drive has other partitions that are loaded with other puppies and other Linux OSes (and they all work great with the grub4dos on it).

Guess I'll have to wait for Fred to see what the issue is here, and/or workaround. Until then....am removing DD64 completely off both the USB it is on, and also reformating the partition it was installed on this new external USB drive. And for since I have downloaded DebianDog64 twice now, I know another download is not going to make a difference. So, will throw in the trash one of the Live Cds it is on, and keep the other one and await a response from Fred (or anyone) who can tell me what I am doing wrong by simply trying to install DebianDog64 from a Live CD/USB to a partition on another drive, with gurb4dos as the governor, and why every other Linux OS boots up and works, but DebianDob won't even bootup from that Ext4 formatted partition.
Back to top
View user's profile Send private message 
fredx181


Joined: 11 Dec 2013
Posts: 4481
Location: holland

PostPosted: Mon 11 Jul 2016, 14:38    Post subject:  

Hi Belham,

It seems to me that you did nothing wrong the last time, so I don't have an answer right now.
I'll try to reproduce (install to hdd, the same as you did) today or tomorrow, so I'll get back later.

What is the bootloader on your working DD64 USB install?

Edit: Oops, re-reading your post I see now that you used an external USB HD, I'm not sure I can find one at the moment, so it's gonna take more time for me to reproduce exactly the same.

Fred

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

Joined: 07 Jan 2016
Posts: 133

PostPosted: Mon 11 Jul 2016, 15:28    Post subject:  

fredx181 wrote:
Hi Belham,

It seems to me that you did nothing wrong the last time, so I don't have an answer right now.
I'll try to reproduce (install to hdd, the same as you did) today or tomorrow, so I'll get back later.

What is the bootloader on your working DD64 USB install?

Fred



Hi Fred!

I wiped/formatted the working USB to Ext4 on another Ubuntu 14.04.3 machine, then DD to copy DebianDog64 over to it, and everything works great. So i assume since I used Ubuntu 14.04.3, it would have grub2 on it. Yes?

Hey, seriously, you probably just got home from work. Don't worry about this until you actually have some real, free time, and not where you have to press for it. I actually am pretty angry at myself that I cannot figure this out....I mean, I'm no genius, but I know I must have messed something up. let me retrace my steps, using the freschly downloaded CD of DebianDog64, and see if i can't figure out what I am doing wrong.

The 160GB external Sata USB I am installing it to has the following on it:

-Fatdog64
-Quirky 8.0
-Takr64
-Slacko64
(and the fifth quick running OS I want is your DebianDog64).

the other Linux OSes I have on this drive are:
--antiX-16
--Peppermint 7
--Manjaro XFCE 16.0.6.1
--MX-15 KDE
--LinuxLite 3.0

And they all bootup great with the Grub4dos v1.9.2 that Fatdog64 installed for me when it was the first OS of any type to be put on this drive. So it's not like I don't know grub4dos a bit. There's just something I know I am doing wrong. I can get this DebianDog64 in the menu.lst grub4dos entry (listed afterwards) to almost go all the way in booting up but it stops on :

"....Begin: Running /scripts/local-bottom....done
Begin: Running /scripts/init-bottom....mount: mounting /dev/on /root/dev failed : No such file or Directory
done.
No init found. Try passing init= bootarg.
modprobe: module echi-orion not found in modules.dep
[12.414017] uhci_hcd: USB Universal Host Controller Interface Driver

BusyBox v1.22.1 (Debian 1:11.22.0-9+deb8u1) built-in shell (ash)
Enter "help" for a list of built-in commands

/bin/sh: can't access tty; job control turned off
(initramfs).........................................................
"


Here's the two grub4dos entry variations that produced the above and at least allowed me to get that far (the entries that the DebianDog64 installer originally made for Grub4dos would NOT even get past anything and they would immediately throw up Error 13 before any bootup attempting got underways):

(plz note that the following, this isn't the normal entries DD64 Installer installs to Grub4dos. I had to create playing around with these. At least the following two grub4dos entries I almost made it all the way through bootup)


title DebianDog64 (sda4/boot)
UUID ###--(left this out, no reason to post it)
kernel /ubnkern
initrd /ubninit


(used this one after copying eveyhting over from the /mnt/sda working DD64 USB drive)

title DebianDog64 (sda4/boot)
UUID ###--(left this out, no reason to post it)
kernel /ubnkern rootfstype=ramfs basesfs=local:/live/01-filesystem.sfs root=/dev/sda4
initrd /ubninit


(on this one I renamed the 01-filesystem-squashfs to 01-filesystem.sfs in the "LIVE" folder of the newly installed DD64 to the partition).


Doggone DD64 runs perfect off the working sole USB I've been using for a long time, and it also runs great from a Live CD. Bbut getting it to play nice with other Linux & Puppy OSes on a bigger USB external Sata drive when installed to a partition, well, it is driving me crazy. I think my machines are rising up and revolting!! Laughing [/b]
Back to top
View user's profile Send private message 
fredx181


Joined: 11 Dec 2013
Posts: 4481
Location: holland

PostPosted: Mon 11 Jul 2016, 18:18    Post subject:  

Hey Belham,

Quote:
Hey, seriously, you probably just got home from work. Don't worry about this until you actually have some real, free time, and not where you have to press for it.


No worries, I like to know if there's some bug in the installer, never tried on external HD, only on internal or USB flash.
Posting now from DD64 frugal install on external HD, so *unfortunately* couldn't reproduce the error you got.
But at first it didn't work for me because I had a few menu.lst files on other/different partitions so found the wrong one (on sdb1).
Then deleted these, rebooted and it found the right one on sdb3, where I installed DD64, and booted fine.
Something you could check if this possibly is the case for you also and also check if the UUID is correct. by doing in terminal for 4th partition e.g.:
Code:
blkid /dev/sdb4


Quote:
title DebianDog64 (sda4/boot)
UUID ###--(left this out, no reason to post it)
kernel /ubnkern
initrd /ubninit


That looks like unetbootin install, maybe you previously used it?
Don't know much about it. Probably best to give up on trying to make it work that way.

In one of your previous posts you wrote some ways to try booting DD64 e.g:

Quote:
title DebianDog64 (sda4/boot)
UUID ######-######-######-#.....(I put the actual UUID)
kernel /boot/vmlinuz1 root=/dev/sda4 ro
initrd /boot/initrd1.xz


That won't work because the files (and folders, e,g. base) need to be in folder named "live"
And also it won't work if you rename 01-filesystem.squashfs to 01-filesystem.sfs, just leave the.squashfs as it is.

These should work in menu.lst:
- If "live" folder is on root of partition: (make sure there's no other partition with "live" on the root)
Code:
title Debian-PorteusDog  -  changes to /live/ sysvinit
 uuid <UUID>     ### (check if it corresponds with the actual UUID of the partition)
 kernel /live/vmlinuz1 from=/ noauto changes=/live/
 initrd /live/initrd1.xz

- If "live" folder is inside "boot" folder (when "boot' is on root of partition):
Code:
title Debian-PorteusDog  -  changes to /boot/live/ sysvinit
 uuid <UUID>
 kernel /boot/live/vmlinuz1 from=/boot noauto changes=/boot/live/
 initrd /boot/live/initrd1.xz


Please also read here for "porteus-boot" options:
https://github.com/DebianDog/Jessie/wiki/Porteus-boot

Hope you can make it work .

EDIT: Did a google search on "ERROR 13: INVALID OR UNSUPPORTED EXECUTABLE FORMAT" and most result are about Windows loading through grub.

I guess it's in your case about loading vmlinuz
From grub's web site:

Quote:
13 : Invalid or unsupported executable format
This error is returned if the kernel image being loaded is not recognized as Multiboot or one of the supported native formats (Linux zImage or bzImage, FreeBSD, or NetBSD).



Fred

_________________
Dog Linux website
Tinylinux blog by wiak

Last edited by fredx181 on Mon 11 Jul 2016, 19:24; edited 1 time in total
Back to top
View user's profile Send private message 
Display posts from previous:   Sort by:   
Page 18 of 38 [560 Posts]   Goto page: Previous 1, 2, 3, ..., 16, 17, 18, 19, 20, ..., 36, 37, 38 Next
This forum is locked: you cannot post, reply to, or edit topics.   This topic is locked: you cannot edit posts or make replies. 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.0909s ][ Queries: 12 (0.0132s) ][ GZIP on ]