JESOS - the Puppy of Light

[1jss]

I've for a long time dreamt of building my own Linux distro. Then I found Puppy Linux.

JESOS is a remaster of BionicPup64 8.0. It's still in it's very early stages, so expect lots of imperfections.



Goals
JESOS wants to be a light, stylish and friendly Linux distro.

• Light: Keep every footprint as small as possible.

• Stylish: The user should never have to frown at their computer. Everything should be beautiful and clear.

• Friendly: Give the user a sane default configuration.

New in this version

• New icon theme (based on elementary and papirus)

• New JWM window buttons (from elementary)

• New default JWM tray layout

• New white GTK theme

• Less preinstalled applications

Download
The ISO (v0.1) can be downloaded from here (click on assets):
https://github.com/1jss/JESOS/releases


Help out
As this is my first remaster I'll certainly need all the help I can get from seasoned remaster masters.
Feel free to give me all your best advice on how to make JESOS better!

[rockedge]

Hello 1jss,

Good work! I will download and set up the remaster and give it a run.

[1jss]

Hi rockedge,

Thanks a lot! As stated this is a very early release, so there is still loads of work to be done!

My current priorities

• Patch the first run greeter

• Make all apps use the same icons in taskbar as in launcher

• Fix progress bar, active button and number carousel in GTK theme

• Find out where the default Pale Moon settings are stored and include them in ISO

• Strip more packages to achieve lower weight

Feel free to suggest any changes and comment any inconveniences.
I will try to address the most urgent changes first.

[rockedge]

default settings for palemoon are in /root/.moonchild productions. Note that it is a hidden directory indicated by the "." before the directory name (this applies to files as well). To see them in the ROX file manager left click the 'eyeball' to "see hidden files"

[1jss]

Oh! Thanks!

(Thanks btw for hosting the forum! Please tell if there is any way to help out!)

[ally]

mirrored here: http://archive.org/details/Puppy_Linux_JESOS

[1jss]

[mention]ally[/mention]
Great! Thanks!

[TerryH]

This is not a comment regarding the puppy, rather a question is for Administrators. As this is clearly identified as a remaster, should it not be moved to the Puppy Derivatives > Re-masters Category. It will at least be the first entered.

[wiak]

This is not a comment regarding the puppy, rather a question is for Administrators. As this is clearly identified as a remaster, should it not be moved to the Puppy Derivatives > Re-masters Category. It will at least be the first entered.

Yes, it is a remaster according to its builder. Looking at the growing list of distros being added to Puppy Derivatives, seems there may be a number of remasters being put in there (e.g. Studio 13.37 3.3 is a remaster is it not - alternatively it could be regarded as Specialized since for a specialized purpose I'd say).

Someone maybe needs to define what a non-remaster Puppy derivative is? I'm not sure myself. I believe EasyOS is a proper Puppy Derivative (and I've read BarryK describing it as that) - EasyOS is not Puppy Linux per se, or a remaster, but it is 'derived' from Puppy LInux. However EasyOS has its own category on the forum, which is better anyway I feel.

There also seem to be some MainLine Pups threads also put into Puppy Derivatives (e.g. is LxPup not mainline?).

So, JESOS is certainly a Remaster (which is a sub-kind of derivative of course).

Would be nice to have non-remaster Puppy Derivative defined for clarity where things should be put.

That Puppy Derivatives forum is already needing a good clean out altogether. It would be good if members who have created threads in there would check it out and let rockedge/admins know what threads should now be deleted/moved. Mainline distros have their own area on the forum and should not also have threads in Puppy Derivatives.

I also wonder about Raspbian Buster; is that Mainline or is it a Puppy Derivative? I thought it was Mainline Puppy using Arm architecture and by 01micko so should be in appropriate location in thread started by 01micko since only the first post author can make alterations to such first posts of threads (which are often required as changes to distro get made).

Generally speaking, Puppy Derivatives looks like it is getting into a mess. Easy enough to create more subforums inside it to classify its constituents a bit better (should be discussed under Forum Structure area), but very important not to put Mainline Pups in there I'd say. We do know there can be hundreds of Puppy Derivatives in the form of remasters so expect a long remasters list... Just as well ally archive seems to have unlimited space.

wiak

[mikewalsh]

Aren't we getting in danger of "over-analyzing" here, guys?

(I guess it could of course be argued that Puppy is just a 'victim' of her own success... )


Mike.

[wiak]

Aren't we getting in danger of "over-analyzing" here, guys?

(I guess it could of course be argued that Puppy is just a 'victim' of her own success... )

I guess that is true though I'd say the same could be said for most-all established distros, many of which can be and are remastered by others, but Puppy, more than most any other distro actively encourages remastering/re-creation and that does indeed result in thousands of Pups (there is not a day goes by that I don't hear of yet another one, and I have no idea, in most cases, what the difference actually is - sometimes it is just the change of window manager! - sometimes it is a definite specialised flavour, such as Puppy Studio...).

Personally I'm happy to leave any such decision about Puppy space/organisation to rockedge. Since it is so simple to create subforum categories I do think it is sensible to use them (with care - no further levels below that I'd say).

Without 'some' categorising you end up with a loooooong list of distros, much like the confusing list in Puppy Projects on old forum, which was certainly not good in terms of creating confusion about what is on offer, which are main Puppy release(s) and so on.

Of course, if all forum members said 'we just want one long list of Pups and will work out for ourselves which we want to use' that is up to them, but other problem with that is that the amount of development support (for upgrades and so on) that an individual remaster gets is to a large extent dependent on its maker.

Anyway, best to move such discussions to Forum Structure area and not mess up JESOS thread with general discussion about such issues. I am sure rockedge/admins don't really want to move posts - rather, the author of thread or post would help us all if they check available subforum categories, try and use the most appropriate one available, and ask if unsure or wanting new subforum altogether for some good reason or other. JESOS was described as a remaster, so that is clear enough to me. One thing for sure is that we can have hundreds/thousands of 'remasters' but we can't have hundreds/thousands of subforums!

wiak

[TerryH]

Aren't we getting in danger of "over-analyzing" here, guys?

(I guess it could of course be argued that Puppy is just a 'victim' of her own success... )


Mike.

No not at all. It was clearly stated that it is a remaster in the original post. Rockedge has created a section right at the top of Derivatives specifically for this purpose. Seemed like a good way to start to me. Hopefully others will follow.

[1jss]

This is not a comment regarding the puppy, rather a question is for Administrators. As this is clearly identified as a remaster, should it not be moved to the Puppy Derivatives > Re-masters Category. It will at least be the first entered.

Good point! I'd love this thread to be moved to remasters! Is this something I can do myself or do I need rockedge to help me?

I think it's a good idea to categorize the puppys into subcategories as much as possible and maybe have a separate "new releses tread" where all new releases can be anounced without category or order.

(Edit: Just realized it had already been moved! Thanks!)

[Clarity]

@1jss , have you tried to do a WoofCE build of your PUP?

[perdido]

That Puppy Derivatives forum is already needing a good clean out altogether. It would be good if members who have created threads in there would check it out and let rockedge/admins know what threads should now be deleted/moved. Mainline distros have their own area on the forum and should not also have threads in Puppy Derivatives.

I also wonder about Raspbian Buster; is that Mainline or is it a Puppy Derivative? I thought it was Mainline Puppy using Arm architecture and by 01micko so should be in appropriate location in thread started by 01micko since only the first post author can make alterations to such first posts of threads (which are often required as changes to distro get made).

Generally speaking, Puppy Derivatives looks like it is getting into a mess. Easy enough to create more subforums inside it to classify its constituents a bit better (should be discussed under Forum Structure area), but very important not to put Mainline Pups in there I'd say. We do know there can be hundreds of Puppy Derivatives in the form of remasters so expect a long remasters list... Just as well ally archive seems to have unlimited space.

wiak

I have noticed that all "Official versions as listed on puppylinux.com have an .iso file hosted on ibiblio.com

"Mainline Puppy Distros" has the description ""Offical" versions on puppylinux.com "

The "official" versions as listed on puppylinux.com are
-----------------------------------------------------------------------
Raspbian Buster armhf 32-bit Raspup 8.2.1
Ubuntu Bionic x86 32-bit BionicPup32 8.0
Ubuntu Bionic 64 x86_64 64-bit BionicPup64 8.0
Ubuntu Xenial x86 32-bit XenialPup 7.5
Ubuntu Xenial 64 x86_64 64-bit XenialPup64 7.5
Slackware 14.1 x86 32-bit Slacko Puppy 6.3.2
Slackware64 14.1 x86_64 64-bit Slacko64 Puppy 6.3.2
Ubuntu Tahr x86 32-bit Tahrpup 6.0.5
Ubuntu Tahr 64 x86_64 64-bit Tahrpup64 6.0.5

"Mainline" is missing the Raspbian Buster 8.2.1 , That release is currently located in the derivatives forum
"Mainline" also includes additional "unofficial" releases beyond what is included in "Official distributions" puppylinux.com

I have noticed that all the "official releases" per puppylinux.com have the .iso files located on the ibiblio server
Some "unofficial releases" have .html pages on ibiblio point to other download sites.

FWIW

[rockedge]

@perdido
viewforum.php?f=141

[1jss]

@1jss , have you tried to do a WoofCE build of your PUP?

Not yet, but I'd love to try! Now that the murga-linux forum is accessible again I guess there is more documentation available.

Next version
I'm currently working on a 0.2 remaster with new tray configuration (but same layout), new battery and storage icons, less preinstalled apps and patched pMount and first run screen.

Slim ISO and fast boot
I would like to slim down the ISO and make it boot really fast, but we'll see how it ends up. If you know good ways to optimize, feel free to share!

Package management
I'm also searching for a good solution for packaging and package management. I feel like installing from the Ubuntu repos isn't always stable. I would like to include a slim graphical app store (think icons, description and install button) of some kind, but haven't found any turn-key solution yet. If you have any hints here, please share!

[1jss]

My root folder (/) on my development installation got corrupted so that the files created there were undeletable. I tried deleting them both in UI and terminal, which seemed to work, but after a reboot they persisted. Any ideas?

I also had troubles remixing as I had removed former built in packages that were called on at first boot (I don't know where) which makes the first boot experience a mess of error messages. I guess I should have chosen a smaller base distro.

This means that there will be no JESOS 0.2 for now.

I might start over with a minimal Fossapup64, but for now I will isolate some parts of JESOS so that others can take advantage of them in their systems.

[1jss]

Files
Files is a minimal file browser.

Features:
- Minimal UI
- Path bar
- Recognizes mimes
- Plenty of keyboard shortcuts
- Right click option to open folder in terminal
- Right click option to open file as text

Dependencies:
- gtk3
- python3
- Currently hard coded to look for app icon in "/opt/Files/icon.svg"
- Currently hard coded to open urxvt on "open with terminal"
- Currently hard coded to open geany on "open file as text"

Run:
- Rename files.txt to files
- Make it executable (eg. in rox)
- Click on it or run ./files in terminal.

Screenshot of the app.

files.png (54.99 KiB) Viewed 1174 times

I wasn't able to upload the svg icon, so I'll just include it as text here:

Code: Select all

<svg xmlns="http://www.w3.org/2000/svg" width="48" height="48" version="1">
  <path d="M44 41V19s0-2-2-2H6c-2 0-2 2-2 2v22c0 1.108.892 2 2 2h36c1.108 0 2-.892 2-2z" opacity=".2"/>
  <path d="M4 36V8c0-1.108 1-2 2-2h13c2 0 2 1.602 2 4h21s2 0 2 2v24c0 1.108-.892 2-2 2H6c-1.108 0-2-.892-2-2z" fill="#b75"/>
  <path d="M44 39V17c0-1.108-.899-2.122-2-2H6c-2 0-2 1.917-2 1.917V39c0 1.108.892 2 2 2h36c1.108 0 2-.892 2-2z" opacity=".2"/>
  <rect width="36" height="16" x="6" y="13" rx="2" ry="2" fill="#fff"/>
  <path d="M44 40V18s0-2-2-2H6c-2 0-2 2-2 2v22c0 1.108.892 2 2 2h36c1.108 0 2-.892 2-2z" fill="#ea6"/>
  <path d="M6 6c-1 0-2 .892-2 2v1c0-1.108 1-2 2-2h13c2 0 2 1.602 2 4h21.103S44 11 44 13v-1c0-2-1.897-2-1.897-2H21c0-2.398 0-4-2-4z" opacity=".1" fill="#fff"/>
</svg>

[1jss]

Online
Online is a minimal web browser.

Features:
- Minimal UI
- Unified url and search bar (searches if there is a space in the input)
- Plenty of keyboard shortcuts
- Hidden progress bar

Dependencies:
- gtk3
- python3
- webkit2
- Currently hard coded to look for app icon in "/opt/Online/icon.svg"

Run:
- Rename online.txt to online
- Make it executable (eg. in rox)
- Click on it or run ./online in terminal.

Screenshot of Online web browser.

online.png (95.4 KiB) Viewed 1173 times

I wasn't able to upload the svg icon, so I'll just include it as text here:

Code: Select all

<svg xmlns="http://www.w3.org/2000/svg" width="64" height="64" version="1">
  <circle cx="32" cy="32" r="28" fill="#83e"/>
  <circle cx="34.5" cy="29.5" r="20.5" opacity=".2"/>
  <circle cx="32" cy="32" r="14" fill="#fff"/>
</svg>

[1jss]

Minimal battery icon
A minimal battery icon script for the status bar.

Dependencies:
- Python 2
- Uses acpi for battery status

Code: Select all

#!/usr/bin/env python2
# -*- coding: utf-8 -*-

import gtk
import gobject
import subprocess
import re

ACPI_CMD = 'acpi'
TIMEOUT = 10

class MainApp:
	def __init__(self):
		self.icon = gtk.StatusIcon()
		self.update_icon()
		gobject.timeout_add_seconds(TIMEOUT,self.update_icon)
	
	def get_battery_info(self):
		text = subprocess.check_output(ACPI_CMD).strip('\n')
		if(re.match("[^:]+:[^,]+,.+",text)):
			data = text.split(',')
			return {'state':data[0].split(':')[1].strip(' '),
					'percentage':int(data[1].strip(' %')),
					'tooltip': text.split(':',1)[1][1:]
					}
	
	def get_icon_name(self, state, percentage):
		if state == 'Discharging':
			if percentage < 5:
				return 'battery-empty-symbolic'
			elif percentage < 40:
				return 'battery-caution-symbolic'
			elif percentage < 60:
				return 'battery-low-symbolic'
			elif percentage < 80:
				return 'battery-good-symbolic'
			else:
				return 'battery-full-symbolic'
		else:
			if percentage < 5:
				return 'battery-empty-charging-symbolic'
			elif percentage < 40:
				return 'battery-caution-charging-symbolic'
			elif percentage < 60:
				return 'battery-low-charging-symbolic'
			elif percentage < 80:
				return 'battery-good-charging-symbolic'
			else:
				return 'battery-full-charged-symbolic'
	
	def update_icon(self):
		info = self.get_battery_info()
		icon_name = self.get_icon_name(info['state'],info['percentage'])
		self.icon.set_from_icon_name(icon_name)
		self.icon.set_tooltip_text(info['tooltip'])
		return True
	
if __name__ == "__main__":
	try:
		MainApp()
		gtk.main()
	except KeyboardInterrupt:
		pass