HelloSystem enabling upgrade

Hi
Recently, I have downloaded and installed (for testing purpose) the HelloSystem which is based upon FreeBSD. Maybe you can advise me to ask on their forum, but here I am in "off-topic" section :)
I don't care if any of my action break the HelloSystem. My question here is related to 'pkg'. When on HelloSytem, I issue the command (pkg upgrade), it gives following message:
Code:
pkg upgrade is not yet supported in hellosystem
It is said on their github page that: presently 'pkg upgrade' breaks the HelloSystem. But I don't care and looking forward to upgrade it (for testing) in any way.
So, my question here is that how they (HelloSystem team) have disabled 'pkg update' and 'pkg upgrade'? From some config file? And How can I enable it?
Thanks
 
I am using FreeBSD on one my of main systems (along with other OSes like Linux, Windows).
HelloSystem is based upon FreeBSD. After playing with it for an hour, I think "it is FreeBSD" with custom theming, packages and configuration. That's why I am interested in testing this system.
The message was given by 'pkg', so I think there may be a way to do the same on FreeBSD.
 
Maybe it doesn't even install a correct database of all the packages installed, who knows? Most likely, the people building it.
I guess they didn't disable pkg upgrades "just because"…
 
To use pkg as you would on FreeBSD, instead use pkg.real - I think this aught to work looking at the links above.
Looking at that script and at the issue referenced there, it seems pkg was intended to work on hellosystem and was disabled because of that issue as a "workaround".

So yes, this could work, but it could also completely b0rk your "hellosystem". You've been warned ;)
 
pkg.real worked. And after reboot, the system continues to work. The only difference is minor look and feel.
I am a long term Linux user, however, after it has messed up few years ago, I think that FreeBSD has no choice but to get successful and take its place.
 
2 ways I know.

1. You go to /usr/src and you type:
Code:
make -C release cdrom
This will make a .iso of freebsd

2. Freebsd memory disk tool,

Hellosystem seems to use this tool. I don't see what is the advantage of a memory disk.
PS :Just let us know the icon colors you will use.
 
2 ways I know.

1. You go to /usr/src and you type:
Code:
make -C release cdrom
This will make a .iso of freebsd

2. Freebsd memory disk tool,

Hellosystem seems to use this tool. I don't see what is the advantage of a memory disk.
PS :Just let us know the icon colors you will use.
Does it mean that when people want to create a derivative, they install FreeBSD base system, their preferred utilities, desktop, etc and then issue the command (make -C release cdrom)?
You seem curious about icon colors 😄
 
My personal opinion is that when you create a derivative you must have something specific in mind.
For openbsd security was an important thing. And look thanks to openbsd we have openntpd and sndiod.
So it is not a bad thing.
Dragonlfy said I can do better than UFS2. Let me create my own filesystem.
Netbsd said I have some hardware I want to run onto.
What happened to pcbsd ? They had a tool to configure zpools.
Hellosystem is a derivative of furybsd ?
 
My personal opinion is that when you create a derivative you must have something specific in mind.
For openbsd security was an important thing.
Maybe you should clearly separate "distribution", "derivative" and "fork". OpenBSD clearly is a fork (of NetBSD).
  • distribution: just some form of re-packaging original software, maybe add some config tools and other "nice" stuff
  • derivative: a project changing existing software, but following upstream (I think HardenedBSD might be an example of a FreeBSD derivative)
  • fork: take existing software, but only at one point in time, from then on, develop it yourself
Sure, not every project exactly matches one of these categories, but it helps ;)
 
My personal opinion is that when you create a derivative you must have something specific in mind.
For openbsd security was an important thing. And look thanks to openbsd we have openntpd and sndiod.
So it is not a bad thing.
Dragonlfy said I can do better than UFS2. Let me create my own filesystem.
Netbsd said I have some hardware I want to run onto.
What happened to pcbsd ? They had a tool to configure zpools.
Hellosystem is a derivative of furybsd ?
I am not in the field of computers (programming, networking, administration etc.), so I cannot say that by creating a derivative I can introduce "something new" or solve some "stonage" problem.
However, I like to learn about stuff (especially Unix and Linux). So, testing distros/derivatives or trying to learn that how they are created is part of my learning process.
 
… I like to learn about stuff (especially Unix and Linux). So, testing distros/derivatives or trying to learn that how they are created is part of my learning process.

See for example:


Special thanks: Mjölnir and Samuel Venable.

… To use pkg as you would on FreeBSD, instead use pkg.real

Exactly.

sudo mv /usr/sbin/pkg.real /usr/sbin/pkg

However, proceed with caution.

pkg.real worked. And after reboot, the system continues to work.

There's fragility if, for example, you prefer latest packages.

"it is FreeBSD" with custom theming, packages and configuration.

Plus (amongst other things) custom applications, which can break as a result of pkg upgrade:
  • some breakables, such as the custom Falkon, resemble the ports to FreeBSD
  • others breakables are unique to helloSystem and may be more difficult to fix.
From an experiment yesterday with recently-released 0.5.0 (0E223):
1624008034514.png

Partial fixes, none of which are officially supported by helloSystem, include:

pkg install -qy py38-qt5 py38-pytz py38-dateutil py38-psutil

– unfortunately, it seems that one of those installations breaks the previously working (essential) Keyboard Layout application a.k.a. Keyboard preferences:

1624008768996.png

– I imagine that installing another package from the FreeBSD repository can fix custom applications such as these, but I have not yet tested.

The good news is that it's still almost entirely FreeBSD, so (after overwriting the crippled custom pkg binary with FreeBSD's binary) you can install whatever you like.

sysutils/lxqt-config plugs some gaps but cannot fix the Apple Mac-oriented helloSystem keyboard layout so if you prefer a non-swapped layout etc.:

‼️ use helloSystem Keyboard preferences before upgrading packages and use the File menu to save preferences (there's no hint to save when closing the application).

… featherpad…

<https://github.com/tsujan/FeatherPad/issues/423> was thought-provoking. There's probably no hope of the developer changing the default shortcut, so instead:


… What happened to pcbsd ? …

It's Official But Sad: TrueOS Is Over As Once The Best Desktop BSD OS - Phoronix

<https://web.archive.org/web/20200424111117/https://www.truenas.com/trueos-discontinuation/>

… Hellosystem is a derivative of furybsd ? …

Partly. <https://hellosystem.github.io/docs/search.html?q=FuryBSD&check_keywords=yes&area=default>
 
automount and automount

For the benefit of readers who may be new to these things, we have (amongst other things):
  1. automount(8) integral to FreeBSD i.e. <https://www.freebsd.org/cgi/man.cgi?query=automount&sektion=8&manpath=FreeBSD+13.0-RELEASE>
  2. non-integral sysutils/automount.
FreeBSD Desktop – Part 17 – Configuration – Automount Removable Media | 𝚟𝚎𝚛𝚖𝚊𝚍𝚎𝚗 (vermaden, 2018-10-11) is probably the best introduction to such things.

… automount. Never used it. Always done explicitly. It's annoying when you want to raw write and it seems already mounted.

helloSystem aside: I once produced a USB flash drive that causes FreeBSD to panic (crash), if I recall correctly the production involved an untimely automated mount.

For reference only:

Code:
root@mowa219-gjp4-8570p:/var/crash # cat info.7
Dump header from device: /dev/ada0p3
Architecture: amd64
Architecture Version: 2
Dump Length: 3197423616
Blocksize: 512
Compression: none
Dumptime: 2021-01-05 05:36:34 +0000
Hostname: mowa219-gjp4-8570p
Magic: FreeBSD Kernel Dump
Version String: FreeBSD 13.0-CURRENT #75 main-c572-g82397d791: Sun Jan  3 20:00:09 GMT 2021
    root@mowa219-gjp4-8570p:/usr/obj/usr/src/amd64.amd64/sys/GENERIC-NODEBUG
Panic String: ufs_dirbad: /media/da1p1: bad dir ino 2 at offset 0: mangled entry
Dump Parity: 3353580913
Bounds: 7
Dump Status: good
root@mowa219-gjp4-8570p:/var/crash # cat info.8
Dump header from device: /dev/ada0p3
Architecture: amd64
Architecture Version: 2
Dump Length: 965197824
Blocksize: 512
Compression: none
Dumptime: 2021-01-05 05:43:56 +0000
Hostname: mowa219-gjp4-8570p
Magic: FreeBSD Kernel Dump
Version String: FreeBSD 13.0-CURRENT #75 main-c572-g82397d791: Sun Jan  3 20:00:09 GMT 2021
    root@mowa219-gjp4-8570p:/usr/obj/usr/src/amd64.amd64/sys/GENERIC-NODEBUG
Panic String: ufs_dirbad: /media/da1p1: bad dir ino 2 at offset 0: mangled entry
Dump Parity: 3118830961
Bounds: 8
Dump Status: good
root@mowa219-gjp4-8570p:/var/crash # cat info.9
Dump header from device: /dev/ada0p3
Architecture: amd64
Architecture Version: 2
Dump Length: 920911872
Blocksize: 512
Compression: none
Dumptime: 2021-01-06 05:26:31 +0000
Hostname: mowa219-gjp4-8570p
Magic: FreeBSD Kernel Dump
Version String: FreeBSD 13.0-CURRENT #75 main-c572-g82397d791: Sun Jan  3 20:00:09 GMT 2021
    root@mowa219-gjp4-8570p:/usr/obj/usr/src/amd64.amd64/sys/GENERIC-NODEBUG
Panic String: ufs_dirbad: /media/da1p1: bad dir ino 2 at offset 0: mangled entry
Dump Parity: 575902577
Bounds: 9
Dump Status: good
root@mowa219-gjp4-8570p:/var/crash # cat info.0
Dump header from device: /dev/ada0p3
Architecture: amd64
Architecture Version: 2
Dump Length: 1056231424
Blocksize: 512
Compression: none
Dumptime: 2021-01-06 05:41:55 +0000
Hostname: mowa219-gjp4-8570p
Magic: FreeBSD Kernel Dump
Version String: FreeBSD 13.0-CURRENT #75 main-c572-g82397d791: Sun Jan  3 20:00:09 GMT 2021
    root@mowa219-gjp4-8570p:/usr/obj/usr/src/amd64.amd64/sys/GENERIC-NODEBUG
Panic String: ufs_dirbad: /media/da1p1: bad dir ino 2 at offset 0: mangled entry
Dump Parity: 2253689713
Bounds: 0
Dump Status: good
root@mowa219-gjp4-8570p:/var/crash # cat info.1
Dump header from device: /dev/ada0p3
Architecture: amd64
Architecture Version: 2
Dump Length: 998150144
Blocksize: 512
Compression: none
Dumptime: 2021-01-06 05:54:58 +0000
Hostname: mowa219-gjp4-8570p
Magic: FreeBSD Kernel Dump
Version String: FreeBSD 13.0-CURRENT #75 main-c572-g82397d791: Sun Jan  3 20:00:09 GMT 2021
    root@mowa219-gjp4-8570p:/usr/obj/usr/src/amd64.amd64/sys/GENERIC-NODEBUG
Panic String: ufs_dirbad: /media/da0p1: bad dir ino 2 at offset 0: mangled entry
Dump Parity: 2538181233
Bounds: 1
Dump Status: good
root@mowa219-gjp4-8570p:/var/crash # cat info.2
Dump header from device: /dev/ada0p3
Architecture: amd64
Architecture Version: 2
Dump Length: 1024663552
Blocksize: 512
Compression: none
Dumptime: 2021-01-06 22:55:28 +0000
Hostname: mowa219-gjp4-8570p
Magic: FreeBSD Kernel Dump
Version String: FreeBSD 13.0-CURRENT #75 main-c572-g82397d791: Sun Jan  3 20:00:09 GMT 2021
    root@mowa219-gjp4-8570p:/usr/obj/usr/src/amd64.amd64/sys/GENERIC-NODEBUG
Panic String: ufs_dirbad: /media/da0p1: bad dir ino 2 at offset 0: mangled entry
Dump Parity: 3307639153
Bounds: 2
Dump Status: good
root@mowa219-gjp4-8570p:/var/crash # cat info.3
Dump header from device: /dev/ada0p3
Architecture: amd64
Architecture Version: 2
Dump Length: 3206725632
Blocksize: 512
Compression: none
Dumptime: 2021-03-09 07:52:16 +0000
Hostname: mowa219-gjp4-8570p
Magic: FreeBSD Kernel Dump
Version String: FreeBSD 14.0-CURRENT #88 main-n245277-0d3b3beeb25: Fri Mar  5 06:52:45 GMT 2021
    root@mowa219-gjp4-8570p:/usr/obj/usr/src/amd64.amd64/sys/GENERIC-NODEBUG
Panic String: ufs_dirbad: /media/Kingston_DataTraveler_3.0_60A44C413D03E310C7299800_p4: bad dir ino 715970 at offset 0: mangled entry
Dump Parity: 738202137
Bounds: 3
Dump Status: good
root@mowa219-gjp4-8570p:/var/crash #

Note: in this case, the mangled entry in relation to UFS is not symptomatic of a problem with UFS. The underlying mangle occurred before the file system could be properly written to its partition.
 
Back
Top