DebianDog - Jessie - Continued

[backi]

removed

[rufwoof]

Looks like DebianDog has a script filemnt which is a sym link to /usr/local/bin/mnt-img that is associated to .iso files

i.e. install a copy of that mnt-img file into Debian /usr/local/bin (I've edited the attached to use pcmanfm, was using thunar (one line might need to be uncommented/changed according to which file manager you use). Make it executable. Then on a .iso file right click and select the open with choice and set it up to use that mnt-img script (ticking the relevant box to make that association persistent).

Looks like that might only work for frugal booted i.e. I think I saw some code that used a loop file.

[fredx181]

Looks like DebianDog has a script filemnt which is a sym link to /usr/local/bin/mnt-img that is associated to .iso files

Yes, and also associated with squashfs, sfs, dat, 2fs, 3fs and more.

Fred

[rufwoof]

There is just one thing which is confusing me in your description above ( maybe could confuse some other amateur too) .....how to " empty" this 01-filesystem.squashfs ?

Once all of 01-filesystem.squashfs is extracted to the save area, its in effect redundant i.e. the layering is such that the save area overlays 01-filesystem.squashfs and as they're the same nothing in 01-filesystem.squashfs ever gets used. So you can replace that 01-filesystem.squashfs with another version that contains nothing (and save-on/use-less disk space).

Which can be achieved by renaming or deleting the existing 01-filesystem.squashfs and creating a new one.

cd /live
mkdir t
mksquashfs t 01-filesystem.squashfs
rmdir t

Which normally comes out at around a 4K filesize for that empty 01-filesystem.squashfs.

You could run with no 01-filesystem.squashfs, but I believe Fred encountered problems that way if you want to load other sfs's. Something like if no 01-filesystem.squashfs exists, then no loops are created and without loops you can't allocate a sfs to a loop i.e. the sfs doesn't get loaded. With a empty 01-filesystem.squashfs the loops are created.

Under boot 3 style booting, you can create a filesystem.module file in /live that lists the sfs files to load at startup and they're loaded in the order presented in that filesystem.module file. Under Porteus (boot 1) style, any .squashfs files in /live are loaded in alpha-numeric sorted order (as they are in boot 3 style if no /live/filesystem.module file exists).

[rufwoof]

deleted

[backi]

Regarding mounting Isos with Thunar .Also squashfs and sfs are now mounting well .

Something was corrupted .....did new install ....now works fine .

[belham2]

Regarding mounting Isos with Thunar .Also squashfs and sfs are now mounting well .

Something was corrupted .....did new install ....now works fine .

Backi,

Will you please send me some of your special weed & hefeweizens over on one of tonight's ICE trains? I just spent 3 hours pulling my hair out trying the "Pupjibaro-Jessie" creation. All I can say is: my God, I want to wash Fred's feet as the 2nd Coming after enduring that ordeal.

Glad you got the mounting thing sorted out with a new install.


[edit: spelling errors]

[fredx181]

Hi All,

Just couldn't resist to make a GUI version of the Quick-Remaster tool.
When installed newer quick-remaster package (gui version included), run it from Menu > DebianDog > Quick Remaster Gui.
More options included than in the CLI version, make your choices in the GUI, click OK and remastering is done in less than a minute! (well, if you choose default LZ4 compression).
EDIT: (of course it depends, on a slow USB stick it took for me a little more than 2 minutes, oh well..)
Only for very lazy and impatient persons (including me )

Install from synaptic or from terminal:

Code: Select all

apt-get update
apt-get install quick-remaster # will install latest v1.0.3

.deb package:
http://debiandog.github.io/Jessie/i386/ ... .4_all.deb
EDIT: Bug fix: gz compression option not working in previous version 1.0.3, now fixed in 1.0.4

P.S. as mentioned before, only works when booted with 'porteus-boot' frugally installed.
Thanks again to rufwoof for the concept idea!

Fred

[dancytron]

I just tested the new GUI Remaster tool. Worked great.

I tested the old CLI version with a couple of different configurations a few days ago (on hard drive ext4, save on exit; on usb drive FAT32 Grub for dos, not save on exit with all the different options).

Nothing to report, everything worked as it should.

[backi]

COOL TOOL !

Makes remaster fun .

[fredx181]

Script (testing appreciated ) to upgrade the kernel + initrd + vmlinuz on a frugal install here:
http://murga-linux.com/puppy/viewtopic. ... 740#929740

Fred

[belham2]

Script (testing appreciated ) to upgrade the kernel + initrd + vmlinuz on a frugal install here:
http://murga-linux.com/puppy/viewtopic. ... 740#929740

Fred

Well, that sure was easy Gracias, Fred! (wish I could have done the DD64 this way, I am still not sure if I did it right...this way shows straight away in the terminal with 'uname -a' that it is the correct kernel. In the DD64, for me, it still shows the old one...but I know you explained to me that it probably installed) )

[fredx181]

Hi Belham,

wish I could have done the DD64 this way, I am still not sure if I did it right...this way shows straight away in the terminal with 'uname -a' that it is the correct kernel. In the DD64, for me, it still shows the old one...but I know you explained to me that it probably installed

Well, the package may be installed (showing newer version in synaptic) but that's only half way.
The version output of uname -a MUST correspond with that (after reboot), if it doesn't you booted the older vmlinuz in the 'live' folder. (this way not synced), probably no terrible things will happen, but it's not the way as it should be.

Looking at your screenshot you have version 3.16.7-ckt25-2 installed on DD64.
If that's right (only if) then you could run the upgrade-kernel script to go to latest 3.16.36-1+deb8u2 (with upgraded initrd and vmlinuz).

EDIT: Re-uploaded the script, see EDIT here:
http://murga-linux.com/puppy/viewtopic. ... 740#929740
The change gives better chance it will succeed, even if before you manually installed latest kernel with a (downloaded) .deb.

Fred

[greengeek]

P.S. I truly wonder if Puppy enthusiasts realize that the 'keeping your OS up-to-date with critical security flaws is a brain-dead easy with the DebianDogs? I mean, you install "unattended-upgrades" via the terminal, and you never have to worry about it again. It has changed how I view puppies overall, and imho, gives other pups & pup-related OSes something to shoot for. Slacko repos are great and all, but Debian repos seem to get stuff out faster, with less problems.

Puppy has a different philosophy. If you want to trust someone else to give you the "latest and greatest" then puppy is probably not the solution.

I left Windows because of the need to trust their infernal updates and I feel that trusting other people to constantly "cure" security flaws is a neverending roundabout just like the old windows nonsense.

I guess it might seem naiive but many of the Puppy enthusiasts you mention actually abhor auto updates. I guess it's like riding a motorcycle with no helmet - sometimes you just want to do it and let "common sense" go to hell. A bit like running as root really.

[le_sabre]

Hi all
I am new here. Just tried DD (32bits) on an old computer with 1 GB ram.
I did a frugal install to a 2GB pendrive. Quite happy with it I have a strange problem though.

When I change the resolution to 1920x1200 (my screen default), the screen turns to black and says, no signal

I can reach this resolution if I change it progressively, first 800x600, then 1024xsomething and so on. Then I can change to 1920x1200 and stays there, no problem.

If I save changes, next time I reboot I see the desktop for a moment (with low resolution) and then, of course, when it loads the changes, the screen goes to black and I can't do anything.

Any suggestion?
Thanks in advance

[mjaksen]

Hi Fred,

This looks amazing. I can't believe the whole thing runs in 75MB idle. I'm a new convert for XFCE. And the whisker menu should be required on all puppies everywhere. So far everything seems to work like a dream. The SFSdrop is SUPER convenient when making adrive.sfs's, saved me SO many mounts and umounts.

Do you have any idea how to get a Broadcom BCM43142 driver for this without internet?

Marc

[dancytron]

Hi Fred,

This looks amazing. I can't believe the whole thing runs in 75MB idle. I'm a new convert for XFCE. And the whisker menu should be required on all puppies everywhere. So far everything seems to work like a dream. The SFSdrop is SUPER convenient when making adrive.sfs's, saved me SO many mounts and umounts.

Do you have any idea how to get a Broadcom BCM43142 driver for this without internet?

Marc

You mean you have to download it manually and then install it on a different computer?

Download from here https://packages.debian.org/jessie/broadcom-sta-dkms The download link is at the bottom of the page labelled "all".

Some instructions here.

https://wiki.debian.org/wl

[fredx181]

Upgrade-Kernel made into a package now, install with Synaptic, or from terminal:

Code: Select all

apt-get update
apt-get install upgrade-kernel

See here for the improvements made, suggestions by 'The Flying Cat'
http://murga-linux.com/puppy/viewtopic. ... 244#930244

Also see here:
http://murga-linux.com/puppy/viewtopic. ... 740#929740

Upgrading to the latest kernel will fix the Dirty COW bug, see also rufwoof's topic about it here:
http://murga-linux.com/puppy/viewtopic.php?t=108674

Fred

[rufwoof]

Installed via apt-get and ran the kernel update ... all worked great.

Fantastic job Fred.

(Running the latest DD Jessie version as my 'admin' secondary boot choice).

[belham2]

Hi Fred,

Just wanted to post some unusual behavior (well, I don't know if it is unusual...but I've not seen this before) in this new Debian Dog Jessie.

I always do frugal installs, and almost always to either SD cards and/or straight USB sticks. So, I last night I take this new DebianDog Jessie that I am growing fonder of by the day, and plug it into another machine.

On bootup, I am faced with disappeared taskbars, icons missing, etc, etc. Yet, other changes (I made on the original machine) are there. I then take the SD/USB & plug it back into the original machine, and everything re-appears like nothing is wrong.

I then try the same thing on a 3rd machine, and---again---all sorts of weirdness, and it is not exactly the same as the 2nd machine weirdness either. This time, whole programs are missing out of the menu, ##.desktop files are missing, the background is gone, and a few other things.

I start thinking to myself "...this is super strange..", because I have never seen this before in any frugal install of other pups and/or pup-related distros. I then grab my frugally-installed DD64 SD/USB stick, and, totally confusing me, boots across all machines with not one issue and/or problem.

Thinking I have 'Halloween Demons' in my system, I try one last item for this new DebianDog Jessie: a netbook laptop. Again, the weirdness. Debian Dog Jessie displays all sorts of strange behavior---and what bugs me again is that this behavior is different from the above 3 machines. How is that possible???


Can you give me any ideas and/or hints what might be going on? Did I mess something up installing it originally?? Should I do the whole thing over again? Or did possibly the "kernel-update' do something that I am not aware of??? What throws me off, is if you plug the SD/USB into the original machine it was frugally installed on, it acts like nothing is wrong and everything runs perfect. Yet if you plug it into another machine, any of the machines, it goes haywire (please note: all machines are AMDs. and not one of them have any HDs attached ---they are solely setup for dedicated pup & pup-related use).

Thanks for any hints and/or tips in trying to figure this out. I just can't figure out why DD64 would act normal across all machines, and yet this new DebianDog Jessie i686 is doing some sort of "gremlin" dance depending on what machine it is plugged into.