1

Topic: Milky Way Roadmap

Hi guys, while we are implementing Xenocara for Milky Way v0.3. I've prepared a roadmap with some specific points about all planned versions for Milky Way to let you know how is going our development process:

v0.1:
* Migrate all coadde and my packages in AUR and Parabola to our repos to complete the system -> DONE
* Sync all libre Arch packages -> DONE

v0.2:
* Add OpenRC as the main init system -> DONE
* Remove systemd support -> DONE

v0.3:
* Rebuild all packages in [core] by following the Hyperbola Packaging Guidelines -> DONE
* modules directory in /lib instead of /usr/lib -> DONE
* firmware directory in /lib instead of /usr/lib -> DONE
* initcpio directory in /lib instead of /usr/lib -> DONE
* Add LibreSSL as the default provider of SSL and TLS protocols -> DONE
* Remove OpenSSL support -> DONE
* Add Xenocara as the default provider of display server for the X Window System -> IN PROGRESS
* Remove X.Org support -> IN PROGRESS
* security directory in /lib instead of /usr/lib
* udev directory in /lib instead of /usr/lib
* Remove Node.js support

v0.4:
* Rebuild all packages in [extra] by following the Hyperbola Packaging Guidelines
* Remove remnants of systemd
* Add s6 as an alternative service management
* Add GNU Shepherd as an alternative service management
* Use sndio as our default provider of Sound server
* Remove PulseAudio support
* Use GraphicsMagick as our default provider of Graphics software
* Remove ImageMagick support
* Qt LTS migration
* KDE Plasma LTS migration
* SDL2 migration
* Java removal
* TeX Live restructuring
* Perl 5 restructuring
* Avahi removal
* Remove unsecure protocols
* libdaemon removal
* libatasmart removal
* Rebuild packages with Qt5 WebKit NG

v0.5:
* Rebuild all packages in [community] by following the Hyperbola Packaging Guidelines
* Clean-up [community] by removing unused packages and implementing new ones requested by Hyperbola community

See our Todo lists for further details.

2

Re: Milky Way Roadmap

Emulatorman wrote:

v0.2:
* Add OpenRC as the main init system -> DONE
* Remove systemd support -> DONE

I forgot another major features in v0.2 too:

* Development of UXP applications (Iceweasel-UXP, Icedove-UXP and Iceape-UXP) -> DONE
* rEFInd implementation in live images -> DONE

3

Re: Milky Way Roadmap

Emulatorman wrote:

Hi guys, while we are implementing Xenocara for Milky Way v0.3. I've prepared a roadmap with some specific points about all planned versions for Milky Way to let you know how is going our development process:

v0.1:
* Migrate all coadde and my packages in AUR and Parabola to our repos to complete the system -> DONE
* Sync all libre Arch packages -> DONE

v0.2:
* Add OpenRC as the main init system -> DONE
* Remove systemd support -> DONE

v0.3:
* Rebuild all packages in [core] by following the Hyperbola Packaging Guidelines -> DONE
* modules directory in /lib instead of /usr/lib -> DONE
* firmware directory in /lib instead of /usr/lib -> DONE
* initcpio directory in /lib instead of /usr/lib -> DONE
* Add LibreSSL as the default provider of SSL and TLS protocols -> DONE
* Remove OpenSSL support -> DONE
* Add Xenocara as the default provider of display server for the X Window System -> IN PROGRESS
* Remove X.Org support -> IN PROGRESS
* security directory in /lib instead of /usr/lib
* udev directory in /lib instead of /usr/lib
* Remove Node.js support

v0.4:
* Rebuild all packages in [extra] by following the Hyperbola Packaging Guidelines
* Remove remnants of systemd
* Add s6 as an alternative service management
* Add GNU Shepherd as an alternative service management
* Use sndio as our default provider of Sound server
* Remove PulseAudio support
* Use GraphicsMagick as our default provider of Graphics software
* Remove ImageMagick support
* Qt LTS migration
* KDE Plasma LTS migration
* SDL2 migration
* Java removal
* TeX Live restructuring
* Perl 5 restructuring
* Avahi removal
* Remove unsecure protocols
* libdaemon removal
* libatasmart removal
* Rebuild packages with Qt5 WebKit NG

v0.5:
* Rebuild all packages in [community] by following the Hyperbola Packaging Guidelines
* Clean-up [community] by removing unused packages and implementing new ones requested by Hyperbola community

See our Todo lists for further details.

I look forward to sndio migration. ps, is the new libressl package still in testing? no new updates on it is why I ask.

;o

HyperbolaBSD: The Future of Secure Libre Lightweight Operating Systems!

4

Re: Milky Way Roadmap

zapper wrote:

I look forward to sndio migration. ps, is the new libressl package still in testing? no new updates on it is why I ask.

;o

Yes, because Hyperbola isn't a rolling release distro, LibreSSL will be available for v0.3 in stable.

5

Re: Milky Way Roadmap

Emulatorman wrote:
zapper wrote:

I look forward to sndio migration. ps, is the new libressl package still in testing? no new updates on it is why I ask.

;o

Yes, because Hyperbola isn't a rolling release distro, LibreSSL will be available for v0.3 in stable.

I gathered that, hmm... I wonder when 0.3 stable is coming out then.

HyperbolaBSD: The Future of Secure Libre Lightweight Operating Systems!

6 (edited by aether 2019-06-07 18:46:37)

Re: Milky Way Roadmap

Hi Emulatorman,
Will the v0.3 features the packages from debian buster ?
By the way, will the move to Xenocara require specific configuration ?
Thanks for your work ! (and others involved)

7

Re: Milky Way Roadmap

aether wrote:

Hi Emulatorman,
Will the v0.3 features the packages from debian buster ?

Hi aether,

Milky Way is based on Arch snapshot of May 8th 2017 + Debian patches from Stretch, see our article about releases for further details.

aether wrote:

By the way, will the move to Xenocara require specific configuration ?

I don't think so, since Xenocara X server is a customised X.Org X server that utilises a dedicated _x11 user by default to drop privileges and perform privilege separation in accordance to OpenBSD's least privilege policy. Anyway, if there is some specific configuration, i'll let you know through a new wiki article or HOWTO.

aether wrote:

Thanks for your work ! (and others involved)

You're welcome smile

8

Re: Milky Way Roadmap

zapper wrote:

I gathered that, hmm... I wonder when 0.3 stable is coming out then.

I think it will be ready around 2 or 3 months.

9

Re: Milky Way Roadmap

Emulatorman wrote:

Milky Way is based on Arch snapshot of May 8th 2017 + Debian patches from Stretch, see our article about releases for further details.

Sorry, got confused. I was wondering about the arch snapshot "update" since the last one is from 2017.. I read "approx. 2020 (stable)" for new release on the page you linked. Well, I guess as long it follows Debian security updates, it is good then.

Emulatorman wrote:

I don't think so, since Xenocara X server is a customised X.Org X server that utilises a dedicated _x11 user by default to drop privileges and perform privilege separation in accordance to OpenBSD's least privilege policy. Anyway, if there is some specific configuration, i'll let you know through a new wiki article or HOWTO.

Ok smile Good then.

10

Re: Milky Way Roadmap

Emulatorman wrote:
zapper wrote:

I gathered that, hmm... I wonder when 0.3 stable is coming out then.

I think it will be ready around 2 or 3 months.

Makes sense, I wondered something btw, is it possible to make a sndio version of apulse? Aka, instead of making programs that require pulse work with alsa, they would work with sndio?

It would be nice if you could do that when we finally switch to sndio. smile

But yeah, do you know how long after buster is released you will make a version of Hyperbola based off of it?

and not an understatement, but you are doing a very hard and tough job... Thank you.  You deserve a lot of credit and also credits too. wink

HyperbolaBSD: The Future of Secure Libre Lightweight Operating Systems!

11

Re: Milky Way Roadmap

aether wrote:

Hi Emulatorman,
Will the v0.3 features the packages from debian buster ?
By the way, will the move to Xenocara require specific configuration ?
Thanks for your work ! (and others involved)

1.0 will be what the one based on Buster will be called... I hope in a year Emulatorman will make his own version at the most, of it. smile

and yes, we owe him and others alot of thanks and more!

HyperbolaBSD: The Future of Secure Libre Lightweight Operating Systems!

12

Re: Milky Way Roadmap

Guys, Xenocara migration has done now, so it's our current development state of Milky Way v0.3:

* Rebuild all packages in [core] by following the Hyperbola Packaging Guidelines -> DONE
* modules directory in /lib instead of /usr/lib -> DONE
* firmware directory in /lib instead of /usr/lib -> DONE
* initcpio directory in /lib instead of /usr/lib -> DONE
* Add LibreSSL as the default provider of SSL and TLS protocols -> DONE
* Remove OpenSSL support -> DONE
* Add Xenocara as the default provider of display server for the X Window System -> DONE
* Remove X.Org support -> DONE
* security directory in /lib instead of /usr/lib -> IN PROGRESS
* udev directory in /lib instead of /usr/lib -> IN PROGRESS
* Remove Node.js support

13

Re: Milky Way Roadmap

Cool, so just these left:

* security directory in /lib instead of /usr/lib -> IN PROGRESS
* udev directory in /lib instead of /usr/lib -> IN PROGRESS
* Remove Node.js support

I wonder what 0.3 will look like. smile

HyperbolaBSD: The Future of Secure Libre Lightweight Operating Systems!

14

Re: Milky Way Roadmap

udev directory migration has done now, so just security directory migration and Node.js removal left:

* Rebuild all packages in [core] by following the Hyperbola Packaging Guidelines -> DONE
* modules directory in /lib instead of /usr/lib -> DONE
* firmware directory in /lib instead of /usr/lib -> DONE
* initcpio directory in /lib instead of /usr/lib -> DONE
* Add LibreSSL as the default provider of SSL and TLS protocols -> DONE
* Remove OpenSSL support -> DONE
* Add Xenocara as the default provider of display server for the X Window System -> DONE
* Remove X.Org support -> DONE
* security directory in /lib instead of /usr/lib -> IN PROGRESS
* udev directory in /lib instead of /usr/lib -> DONE
* Remove Node.js support -> IN PROGRESS

15

Re: Milky Way Roadmap

security directory migration has done now, so the Node.js removal is the next one:

* Rebuild all packages in [core] by following the Hyperbola Packaging Guidelines -> DONE
* modules directory in /lib instead of /usr/lib -> DONE
* firmware directory in /lib instead of /usr/lib -> DONE
* initcpio directory in /lib instead of /usr/lib -> DONE
* Add LibreSSL as the default provider of SSL and TLS protocols -> DONE
* Remove OpenSSL support -> DONE
* Add Xenocara as the default provider of display server for the X Window System -> DONE
* Remove X.Org support -> DONE
* security directory in /lib instead of /usr/lib -> DONE
* udev directory in /lib instead of /usr/lib -> DONE
* Remove Node.js support -> IN PROGRESS

16

Re: Milky Way Roadmap

Guys, the Milky Way v0.3 migration article is available now. It is only for beta-test users who would make testing (eg. debug broken packages, test LibreSSL and Xenocara stability, etc) to stabilize for next release cycle.

If you found some broken package or instability, or some troubleshooting to be added in the migration article, please report to HyperTask.

17

Re: Milky Way Roadmap

I'll wait the 0.3 installer but I have some questions to update my
installer file [pacman -S - < pacman-list.txt]:

1- Migration to xenocara

xorg-server -> xenocara-server
xf86-video-intel -> xorg-video-intel
xorg-xinit -> xenocara-xinit
xorg-apps -> xenocara-apps

It's correct?

2- openssh

openssh -> openssh

not change?

3- /boot

chmod 700 /boot

Is it correct like in the 0.2?

4- startx

/etc/X11/Xwrapper.config
- - - - - - - - - - - - - - - - - - - - - - - 
# Xorg.wrap configuation file
needs_root_rights = yes
- - - - - - - - - - - - - - - - - - - - - - -

Is it necessary until?

18 (edited by zapper 2019-07-14 21:56:31)

Re: Milky Way Roadmap

Emulatorman wrote:

Guys, the Milky Way v0.3 migration article is available now. It is only for beta-test users who would make testing (eg. debug broken packages, test LibreSSL and Xenocara stability, etc) to stabilize for next release cycle.

If you found some broken package or instability, or some troubleshooting to be added in the migration article, please report to HyperTask.

I am thinking of trying what you mentioned in a virtual machine again. Aka Hyperbola test images.

HyperbolaBSD: The Future of Secure Libre Lightweight Operating Systems!

19

Re: Milky Way Roadmap

gnu wrote:

1- Migration to xenocara

xorg-server -> xenocara-server
xf86-video-intel -> xorg-video-intel
xorg-xinit -> xenocara-xinit
xorg-apps -> xenocara-apps

It's correct?

Yes, it's correct

gnu wrote:

2- openssh

openssh -> openssh

not change?

There aren't changes in relation to the package name, however our latest OpenSSH package is adapted only for LibreSSL and integrated with libbsd.

gnu wrote:

3- /boot

chmod 700 /boot

Is it correct like in the 0.2?

Yes, it's correct

gnu wrote:

4- startx

/etc/X11/Xwrapper.config
- - - - - - - - - - - - - - - - - - - - - - - 
# Xorg.wrap configuation file
needs_root_rights = yes
- - - - - - - - - - - - - - - - - - - - - - -

Is it necessary until?

The Xorg.wrap is useless now because was disabled the systemd-logind integration and restored the setuid bit to the Xenocara executable, allowing Xenocara Server to work without having the systemd PAM module installed and set up.

20

Re: Milky Way Roadmap

zapper wrote:

I am thinking of trying what you mentioned in a virtual machine again. Aka Hyperbola test images.

Yes, that is the way to make testing under a secure way.

21

Re: Milky Way Roadmap

Thanks!

22

Re: Milky Way Roadmap

Good luck @Emulatorman (and others) for the 0.3 release. Hopefully, it shouldn't be long now smile

23

Re: Milky Way Roadmap

Node.js removal has done now, so if there aren't more issues reported by our beta-users, we will release v0.3 in the next 10 days.

Meanwhile, we are waiting for the new UXP applications which is being developed by g4jc to release in conjunction with v0.3.

Milky Way v0.3 Roadmap Status:

* Rebuild all packages in [core] by following the Hyperbola Packaging Guidelines -> DONE
* modules directory in /lib instead of /usr/lib -> DONE
* firmware directory in /lib instead of /usr/lib -> DONE
* initcpio directory in /lib instead of /usr/lib -> DONE
* Add LibreSSL as the default provider of SSL and TLS protocols -> DONE
* Remove OpenSSL support -> DONE
* Add Xenocara as the default provider of display server for the X Window System -> DONE
* Remove X.Org support -> DONE
* security directory in /lib instead of /usr/lib -> DONE
* udev directory in /lib instead of /usr/lib -> DONE
* Remove Node.js support -> DONE

24 (edited by zapper 2019-09-10 10:42:02)

Re: Milky Way Roadmap

Emulatorman wrote:

Node.js removal has done now, so if there aren't more issues reported by our beta-users, we will release v0.3 in the next 10 days.

Meanwhile, we are waiting for the new UXP applications which is being developed by g4jc to release in conjunction with v0.3.

Milky Way v0.3 Roadmap Status:

* Rebuild all packages in [core] by following the Hyperbola Packaging Guidelines -> DONE
* modules directory in /lib instead of /usr/lib -> DONE
* firmware directory in /lib instead of /usr/lib -> DONE
* initcpio directory in /lib instead of /usr/lib -> DONE
* Add LibreSSL as the default provider of SSL and TLS protocols -> DONE
* Remove OpenSSL support -> DONE
* Add Xenocara as the default provider of display server for the X Window System -> DONE
* Remove X.Org support -> DONE
* security directory in /lib instead of /usr/lib -> DONE
* udev directory in /lib instead of /usr/lib -> DONE
* Remove Node.js support -> DONE


All is well with my system.  I have the new your-freedom package and no problems here. smile

EDIT: Iceape-uxp-noscript is not working in iceape-uxp.

probably needs to be patched asap.

HyperbolaBSD: The Future of Secure Libre Lightweight Operating Systems!

25

Re: Milky Way Roadmap

So are we far away from 0.3 release ?
Because using a 3 months old outdated browser is not comforting to say the least. I see the iceweasel is receiving updates but it is only for testing.