Same place where DebianDog comes from, Fred:fredx181 wrote:I wonder where the fdisk included in DebianDog comes from.
http://live.debian.net/cdimage/release/ ... andard.iso
Toni
Same place where DebianDog comes from, Fred:fredx181 wrote:I wonder where the fdisk included in DebianDog comes from.
Ok, but I ment from which package.Toni wrote:Same place where DebianDog comes from, Fred:
http://live.debian.net/cdimage/release/ ... andard.iso
Code: Select all
echo "16384,,L,*" | sfdisk -f -H 16 -uS /dev/sdc
mkfs.ext4 -O ^has_journal /dev/sdc1
Forgot also previously to add the modules, optional and rootcopy folders in /live to the archive.EDIT2:New revision of DebianDog-PorteusDog-new-setup.tar.gz uploaded:
The base_only boot option didn't work previously, now it does.
Thank you, Fred!fredx181 wrote:What you need only in fact is the edited linuxrc so attached here.
Code: Select all
find | cpio -H newc -o | xz --check=crc32 --x86 --lzma2 > ../initrd.xz
Hi, William.mcewanw wrote:Though you say your machine won't boot usb with 8MiB offset Toni (and that may well be the case), I would still be grateful if you could try the above method with 8MiB offset just to be sure gparted isn't the culprit really
I use this:Toni wrote:BTW what is yours compress initrd.xz command?
Code: Select all
find . -print | cpio -o -H newc 2>/dev/null | xz -f --extreme --check=crc32 > ../initrd.xz
I think not. It is up to me now to include the changes and make new iso.sunburnt wrote:# Is there anything left to do for the beta "roll-out".?
I suspect puppy users will prefer to use porteus boot anyway. It is much closer to puppy boot and save method than the debian one. As Fred wrote Porteus boot has fsck code options for partitions and save file is auto-checked every time.Now only problem is the Debian Live boot code "can of worms" that I still can`t figure out.
Yes, I understand how you feel. I kind of feel though that you do need a new thread for each new public release, beta included, so that users can have questions answered for that release and provide test/bug reports (such threads can grow quite large and have a tendency to be distribution specific). In that view there does need to be separate threads for the releases themselves I myself feel anyway. However, perhaps it is also good to continue to have a combined thread (albeit a new one) for development issues (and common bugs raised could have detailed discussion there)? I also think it might be good if Fred and youself could arrange to release new versions at the same time, so that everything remains in sync. What do you think?saintless wrote: One thing makes me worry is opening new thread for DebianDog.
DebianDog is what it is now thanks to the fact we kept one thread for Porteus Wheezy and Light Wheezy. Separating the threads does not seems good idea to me.
Toni
Just an idea:One thing makes me worry is opening new thread for DebianDog.
DebianDog is what it is now thanks to the fact we kept one thread for Porteus Wheezy and Light Wheezy. Separating the threads does not seems good idea to me.
Yes, that sounds better, for now at least; Puppy itself uses up a whole forum (!) so I guess we have to keep an eye on how busy that one thread gets.fredx181 wrote:Hi Toni, All
Just an idea:One thing makes me worry is opening new thread for DebianDog.
DebianDog is what it is now thanks to the fact we kept one thread for Porteus Wheezy and Light Wheezy. Separating the threads does not seems good idea to me.
Two versions of DebianDog in one thread, your version with Icewm, Jwm and my openbox/xfce version but then with the exact same setup (choice for live-boot and porteus-boot)
If you all like the idea I need time to create it but meanwhile you can start new thread already.
I like the idea very much, Fred, but DebianDog has 3 boot methods now. If you don't mind to do the same for Porteus-Wheezy it will be great. Even if you include only 2 boot options I think it will be OK.fredx181 wrote:Just an idea:
Two versions of DebianDog in one thread, your version with Icewm, Jwm and my openbox/xfce version but then with the exact same setup (choice for live-boot and porteus-boot)
I will wait with the thread as much as you need. I still have work on separate kernel modules structure anyway.Toni, can you wait a day for beta release, I've found a bug with copy progress-bar, which is in remasterdog, remastercow and debdog-install.
Anyone experienced that the progress-bar just flashes only (but meanwhile copying continues)?