The officially official Devuan Forum!

You are not logged in.

#1 Re: Installation » OpenRC and eudev installation in Devuan ceres » 2017-12-03 01:25:34

fog

psp is no better than me just not as widely used. You would have to either clean/remove PSP/ME or better get arm (e.g. ASUS Chromebook C201)
regarding distros: I would think that security dedicated distro even with dbus is better than home brew. This is of course my personal view.

#2 Re: Hardware & System Configuration » Clarity regarding eth0 device name » 2017-12-03 01:11:41

fog
tlathm wrote:

EDIT: Thinking about this more: Why would this require any change to the initrd? Wouldn't simply changing /etc/default/grub and running update-grub be sufficient? Thanks.

Tom

of course, no need to update initrd. My mistake. I am sorry

#3 Re: Installation » OpenRC and eudev installation in Devuan ceres » 2017-12-01 23:25:31

fog

To answer your question:
Since I am using Devuan in VM, I can't use grsec (only exception is VirtualBox for grsec customized by Alpine Linux). I gave up on grsec because of ended updates.

My kernels are small ~3.7MB vmlinuz and I don't use initrd.
If you are asking about compiling deb kernels this is listed in debian handbook. My config file is really for VM. This in fact is the reason why libre kernel is working on the laptop:
libre disables all firmware including my intel wireless, but in VM I set guest with virtual eth0 which is NATed to whatever connection host is making.

I did install eudev without exiting X. This is probably advantage of VM using most common virtual hardware that do not cause problems with installed OS.

If you are looking for good secure VM try Qubes, but to take full advantage of Qubes, you will have to have specific hardware. This is on the other hand quite risky considering latest revelations about bugs in intel me. I have found one way to completely remove ME (BIOS free space will go up from 1MB to 5MB), but I did not try it yet.

#4 Re: Installation » Unsuccessful installation! » 2017-12-01 22:10:39

fog

I don't remember single OS (not only distros) that would not fail on specific hardware. Maybe this is the case? saying "I don't have this problem" just don't fix anything.
Of course maybe this is trolling.

#5 Re: Hardware & System Configuration » Clarity regarding eth0 device name » 2017-12-01 22:01:16

fog
tlathm wrote:
fsmithred wrote:

Explanation: Hand-waving-argument, magic. I don't know. But I think you'll be ok when you move your system to different hardware.

Haha...glad it's not just me. Yes, it appears I'll be OK but it would be nice to understand why. Both are still a mystery to me...that is, how I'm getting eth0 without net.ifnames=0, and why I'm getting no 70-persistent-net.rules (or any other rules) with udev enabled. Don't look a gift horse in the mouth I guess wink.

EDIT: Totally OT: Any idea why wiki.debian.org is apparently blocking the commercial VPN I use? I get 403s...very annoying. I read some things from way back where this was supposedly corrected(?).

Thanks!
Tom

you can set
GRUB_CMDLINE_LINUX="net.ifnames=0 biosdevname=0"
then update grub/initrd

then whatever will happen to init you should always get consistent eth0
remember though to etit interfaces.

regarding VPN and  wiki.debian.org - I don't see this issue (using commercial VPN)

#6 Re: Off-topic » Firefox Quantum » 2017-11-25 00:19:15

fog
fungus wrote:

How often have you opened up a .conf file in linux and there is a comment with a link to search google for examples and information about how to set something up within the .conf file.
I understand that a specific reference may not be there tomorrow so a google search for a phrase "will" be there.  It is like government, it is always there,
I believe that the cleanest, most efficient, and safe version of firefox is that of torproject bundle.  If you wish you can turn scripts on, proxy-off, and use it as any browser, "in an unsafe fashion".  Then you will realize that there are some "features" that don't exist in that firefox.  There is usually a very good reason for turning those off.

Here is a test of uniqueness in fingerprint left by your browser.  https://browserprint.info/captcha
Use NoScript turn all scripts off, then take the test again.  EFF has a similar test called panopticlick or something, which is crappy compared to what this guy measures.  Scary, they can tell your screen size, what fonts you are using, your timezone, keymaps. all with a single visit to a web page.  After some data is collected you become very unique.  Then off you go to another page that incorporates some google-tags and ads and ...

Dev1galaxy doesn't seem to have any of this, and the forum works just fine with scripts off.  Try reading an article in NYT or Guardian, and see how many sites are on to you.

I have FF57 installed, only nine add-ons
https://browserprint.info/captcha
1st run: Your fingerprint's UUID is dad8284d-bfef-4977-9b5c-069c820cf70b;
2nd run: Your fingerprint's UUID is 4a99f9f7-9578-4248-89bd-ddcc86d1c6ad;

I did give a chance and enabled javascript. I also disabled firejail ( I use overlay to kill anything downloaded)

No chance that this site would discover anything.

I think that FF57 is o.k. Way better than Chrome/google in terms of privacy. I do check Palemoon once in a while but it still suffers from some compatibility issues.

#7 Re: Other Issues » [Solved] Virtualbox guest additions - not working (Ascii) » 2017-11-04 15:34:45

fog
makh wrote:

Hello

But the version is not compatible to virtualbox 5.2. Any ways ...

Thankyou all for your kind help.

Well ASCII comes with the VB version that you installed (see above) that is 5.1.30.
If you want to try VB 5.2 then get it from Oracle. While VB depends on kernel in terms of compatibility, I would think that VB 5.2 is compatible with kernel 4.9 that comes with ASCII.

If 5.2 is not compatible with linux 4.9 either build your own kernel and problem solved

.. or upgrade ASCII to CERES:

apt search virtualbox
Sorting... Done
Full Text Search... Done
boinc-virtualbox/unstable 7.8.3+dfsg-2 amd64
  metapackage for virtualbox-savvy projects

virtualbox/unstable,now 5.2.0-dfsg-2 amd64 [installed]
  x86 virtualization solution - base binaries

virtualbox-dkms/unstable,now 5.2.0-dfsg-2 all [installed,automatic]
  x86 virtualization solution - kernel module sources for dkms

virtualbox-ext-pack/unstable 5.2.0-2 all
  extra capabilities for VirtualBox, downloader.

virtualbox-guest-additions-iso/unstable 5.2.1-118452-1 all
  guest additions iso image for VirtualBox

virtualbox-guest-dkms/unstable,now 5.2.0-dfsg-2 all [installed]
  x86 virtualization solution - guest addition module source for dkms

virtualbox-guest-source/unstable 5.2.0-dfsg-2 all
  x86 virtualization solution - guest addition module source

virtualbox-guest-utils/unstable,now 5.2.0-dfsg-2 amd64 [installed,automatic]
  x86 virtualization solution - non-X11 guest utilities

virtualbox-guest-x11/unstable,now 5.2.0-dfsg-2 amd64 [installed]
  x86 virtualization solution - X11 guest utilities

virtualbox-qt/unstable,now 5.2.0-dfsg-2 amd64 [installed,automatic]
  x86 virtualization solution - Qt based user interface

virtualbox-source/unstable 5.2.0-dfsg-2 all
  x86 virtualization solution - kernel module source

I am running both ASCII and CERES in VM and both are really stable. I have installed latest custom 4.13.11 kernels in both ASCII and CERES though.
Another option would be to temporary enable CERES sources in ASCII to install Devuan's VB 5.2 again with possible kernel upgrade.

#8 Re: Other Issues » [Solved] Virtualbox guest additions - not working (Ascii) » 2017-11-04 05:03:50

fog
golinux wrote:

Try ascii backports.  It is in Debian stretch backports so should be in ascii's.

yes:

apt search virtualbox
Sorting... Done
Full Text Search... Done
virtualbox/ascii-backports,now 5.1.30-dfsg-1~bpo9+1 amd64 [installed]
  x86 virtualization solution - base binaries

virtualbox-dkms/ascii-backports,now 5.1.30-dfsg-1~bpo9+1 all [installed,automatic]
  x86 virtualization solution - kernel module sources for dkms

virtualbox-guest-dkms/ascii-backports,now 5.1.30-dfsg-1~bpo9+1 all [installed]
  x86 virtualization solution - guest addition module source for dkms

virtualbox-guest-source/ascii-backports 5.1.30-dfsg-1~bpo9+1 all
  x86 virtualization solution - guest addition module source

virtualbox-guest-utils/ascii-backports,now 5.1.30-dfsg-1~bpo9+1 amd64 [installed,automatic]
  x86 virtualization solution - non-X11 guest utilities

virtualbox-guest-x11/ascii-backports,now 5.1.30-dfsg-1~bpo9+1 amd64 [installed]
  x86 virtualization solution - X11 guest utilities

virtualbox-qt/ascii-backports,now 5.1.30-dfsg-1~bpo9+1 amd64 [installed,automatic]
  x86 virtualization solution - Qt based user interface

virtualbox-source/ascii-backports 5.1.30-dfsg-1~bpo9+1 all
  x86 virtualization solution - kernel module source

hope this will help

#9 Re: Other Issues » [Solved] Virtualbox guest additions - not working (Ascii) » 2017-11-03 18:57:12

fog
makh wrote:

Hi

I actually cloned the jessie, then upgraded to ascii. Then installed the guest cd after the upgrade.

I dont see any issue except that the guest addons arent working...

My folder creation was same as for jessie, no difference.

My host OS is Arch.

Edit 1: I reinstalled the guest additions:

# sh VBoxLinuxAdditions.run 
Verifying archive integrity... All good.
Uncompressing VirtualBox 5.1.30 Guest Additions for Linux...........
VirtualBox Guest Additions installer
Removing installed version 5.1.30 of VirtualBox Guest Additions...
vboxadd.sh: Stopping VirtualBox Additions.
Copying additional installer modules ...
Installing additional modules ...
vboxadd.sh: Starting the VirtualBox Guest Additions.
Failed to set up service vboxadd, please check the log file
/var/log/VBoxGuestAdditions.log for details.

# cat /var/log/VBoxGuestAdditions.log

vboxadd.sh: failed: modprobe vboxguest failed.

Edit: Installing the dkms and the kernel header solved the issue.

Thankyou

your screenshot indicates that you have installed VB from Oracle. You can also try Devuan's version of VB with all needed components. This way you may avoid problems related to the future upgrades.

#10 Re: Other Issues » [Solved] Virtualbox guest additions - not working (Ascii) » 2017-11-03 03:18:14

fog
makh wrote:

Hi

I have installed the guest cd components, but they are not working in ascii: like shared folder.

I am having devuan ascii installed inside virtualbox 5.1.30

also I get for:

cat /etc/debian_version
9.2
cat /etc/devuan_version
jessie

Thankyou

I have ASCII (VB 5.1.30) and CERES (VB 5.2.0) installed in virtual box. All components work including shared folders.
How are you creating shared folders?
I hope that you set shared folders while VM guest is turned off?
What is your VM host?

#11 Re: Hardware & System Configuration » working method for module blacklisting? » 2017-10-26 16:24:42

fog

because:

cynwulf wrote:

I used Linux since around 2002 and used Slackware and Debian for years .

I said

fog wrote:

I started using computers probably long before you were born and before phrase "personal cumputers" was used for the first time, that is in mid 70'. In high school we had obligatory (then called informatics)  programming held at the university (that was really advanced high school). I went through VAX, early Sun, NetWare, bunch of BSDs, linuxes, Be, Apple products, DOS and Windows systems plus some other stuff I don't even remember.

otherwise, I don't care.

cynwulf wrote:

I generally don't get into dick waving,.

so yes, you do. See above

now

cynwulf wrote:

According to the Linux man page bootparam(7) lp=0 is correct. lp=none would only disable the first parallel port, not the driver. (yes, in 99% of cases, you may have only one port, but lp=0 seems correct - may avoid the need to blacklist modules as well - worth trying anyway).

passing lp=0 does not work as I explained above. As an expert you should know this reading one of my posts. If you correct someone, do it properly. To make it plain:
You should say
lp=0 does this but it will not work in this case because of this done (I bet you knew it already)



cynwulf wrote:

Anyway as my continued presence is clearly a barrier to the "solutions" flooding in, I'll bow out at this point...

empty promises?

#12 Re: Hardware & System Configuration » working method for module blacklisting? » 2017-10-26 13:09:37

fog
ralph.ronnquist wrote:

Since I (and you?) don't have cups, disabling it for cups is not a solution.

I managed to get the (standard) ASCII 4.9.0-4-amd64 kernel to avoid loading parport and friends by having boot parameter

lp=none

together with blacklisting:

# echo blacklist parport > /etc/modprobe.d/blacklist-parport.conf
# echo blacklist parport_pc >> /etc/modprobe.d/blacklist-parport.conf
# update-initramfs -u

It needs both kernel parameter and blacklisting. Possibly lp=0 would work as well, but I couldn't bother testing it.

Thank you, this is how I understand help.
Unfortunately it did not help.
If you look at the boot process [Info] loading lp, [Info] loading parport and [Info] loading parport_pc appear before kernel variables. Someone just went overboard to make sure that lp is loaded. At this point this is just funny.
I give up. No point to bother Devuan devs. This is too small thing to be concerned about.

@cynwulf
Man you are incorrigible.
I started using computers probably long before you were born and before phrase "personal cumputers" was used for the first time, that is in mid 70'. In high school we had obligatory (then called informatics)  programming held at the university (that was really advanced high school). I went through VAX, early Sun, NetWare, bunch of BSDs, linuxes, Be, Apple products, DOS and Windows systems plus some other stuff I don't even remember.

Personally, when I help then I keep my opinions to myself, so should you. That is for the best and this is what you should learn still. Your sarcasm is misplaced and coming (probably) from hurt pride (I assume because I did not appreciate your knowledge you graciously pour on me) but:
1) I don't care
2) sarcasm in this situation would make sense if you would provide working solution. You did not.
3) at this point your comments are just annoying irrelevant of how long you've been using computers
4) lesson for me: don't ask for help


I think that this topic should be closed because no solution can be found and too much misplaced ambitions hijack the topic of this thread.

Is there "topic closed" button somewhere?

#13 Re: Hardware & System Configuration » working method for module blacklisting? » 2017-10-25 22:43:27

fog

yes,
and all started with simple question about module blacklisting.
I really appreciate your help. I don't know what to say. I am not trying to be rude. I appreciate experience. Sorry?

Still I have no solution. Let's drop it. If Devuan can't leave without parport, then I will leave it be. This is not such a big deal.

#14 Re: Hardware & System Configuration » working method for module blacklisting? » 2017-10-25 19:20:24

fog

this is what is wrong with your help (I don't mean to offend)
in the first post I clearly stated that I do use custom kernel.

fog wrote:

the only thing that works is compiling kernel without listed above modules, but then I am getting FATAL errors at boot complaining about missing modules.

If you red it carefully I assume you would not bother with help:

cynwulf wrote:

If you're going to build your own kernel, the problems that you come across are your problems and any input from other users, using their time to assist you is a bonus.

Aside from personal point of view regarding custom kernels (which are unnecessary), comparing system behaviour under default Devuan kernel or custom let me eliminate kernel as a possible culprit (I always keep original kernel as a backup). If fact if you would read my first post carefully (assuming help) you would know that I did eliminate any standard files that may have anything to do with modules loading.

I was asking then what nonstandard file is hidden in devuan that may force loading of specific modules because as I pointed before:

fog wrote:

There are other modules that I can efficiently blacklist in devuan.

From your posts I did not learn anything valuable (again no offense).

OBSD history is available at wikipedia, while I unnecessary mentioned OBSD, I did not make any errors that should be corrected by citing internet source. However, this is my mistake.

I understand that you wanted to help but whole purpose of my thread  got almost certainly lost now.

Recently I had some issues with solaris. After submitting questions at solaris forum, I got plenty of help.. as yours. That is not much real info. Eventually one of solaris maintainers got involved at in short post pointed me to the solution.

so thank you again, I appreciate what you trying to do but this goes nowhere. Let's wait and hope that someone knows the answer. If no solution is suggested, I can live with parport module as it is.

#15 Re: Hardware & System Configuration » working method for module blacklisting? » 2017-10-25 14:45:29

fog
cynwulf wrote:

If the laptop is without a parallel port then some builtin is loading those lkms.

The difference is in the configuration (or the version) apart from that it's very much the same thing.  You could compare the configs of the kernels in question to see how they differ with regard to IEEE1284/parallel.  It may be a built in driver for a specific controller which is causing those modules to load.

Drivers/hardware is all handled by the kernel, it's how the kernel image has been configured and compiled.  Not knowing precisely how you've configured your custom kernel, it's not easy to say.  However...

If it's still relevant - it may not be, but worth a try - check the file "/etc/modules" or "/etc/modules.conf" to see if any lkms related to the ones in question are being specifically loaded.

(OpenBSD's first release was in 96.  Both OpenBSD and NetBSD hardly made use of lkms anyway (nothing like what Linux does) - I'm not sure if NetBSD still does, in a limited fashion or not at all.  They are - and always will be a security hole - hence why OpenBSD removed the module loader and associated code - being security focused.)

ok,
I apologize for bringing up joke about OBSD and modules. This is really irrelevant to the topic.

I have no clue what Debian/Devuan maintainers did to keep parallel port so persistent. There are other modules that I can efficiently blacklist in devuan. 
Obviously you also have not a clue about this specific issue, so lets leave this at this and leave space for someone who can give me succinct  but working solution.

thank you

#16 Re: Hardware & System Configuration » working method for module blacklisting? » 2017-10-25 13:12:10

fog

thank you,
this is laptop without parallel port.

while kernel sources are the same, there are really differences how distro handles custom kernel.

Devuan references to parport must be outside kernel. As I mentioned, devuan starts without compiled modules for parport but complains about missing parts, similar kernel in CRUX, Slackware, Funtoo does not.

By the way, I was just kidding about OBSD modules listing (in 90' it actually did list modules as far as I remember but memory not the same anymore)

#17 Re: Hardware & System Configuration » working method for module blacklisting? » 2017-10-24 21:48:11

fog

Thank you  for helping.
In contrast to OBSD, linux can list modules:
lsmod and then show dependency:
lsmod | grep lp
modinfo -F depends lp

based on this I want disable parport and dependent modules: parport_pc, ppdev, lp

I build my own kernel, but of course checked this. All are modules.
Kernel without these works of course, however during boot it complains about missing modules. I want to get rid of modules and make system happy .

What is interesting is that other distros just let go of whatever I remove from kernel (aside vital parts of course). Devuan seems really attached to parallel port

#18 Hardware & System Configuration » working method for module blacklisting? » 2017-10-24 18:29:41

fog
Replies: 19

Hello,
I am trying to blacklist few modules: parport_pc, parport, ppdev,lp (important: I am not using initrd in the case if someone asks about updating initramfs)
Unfortunately none of the methods listed work:
/etc/modprobe.d/blacklist.conf
where blacklist.conf is
blacklist parport

or
/etc/modprobe.d/parport.conf
blacklist parport

or adding
modprobe.blacklist=parport
kernel parameter to grub

or setting
skip=
parameter in
/etc/discover-modprobe.conf

the only thing that works is compiling kernel without listed above modules, but then I am getting FATAL errors at boot complaining about missing modules.

I am surprised that parport is so difficult to remove from devuan nowadays when parallel  port is really a dinosaur.

I would appreciate any suggestion.
thank you

#19 Re: Off-topic » Adventures of the systemd clownface » 2017-10-23 18:55:40

fog
JoshuaFlynn wrote:
fog wrote:

this is your vm setup/vid card fault.

Despite the fact that I've hosted 10 different Linux OSes in VM on this machine perfectly fine.

(All the working ones have one thing in common: they either minimise or don't have systemd on them on default install.)

Lubuntu is also of course L, for 'Lightweight', which means graphics shouldn't be an issue, and any graphics failure should drop down into text based, not this weird-ass clown face.

Connectorivity wrote:

I do believe that is 17.04. Joshua was using 14.04.

I was using 16.04, but you're still correct, his version doesn't align.

cynwulf wrote:

Setting aside what I might think of systemd, this kind of thread only fuels the argument that many systemd opponents are just ill-informed fanboi types.

It's a bit hard to make rational arguments against systemd if you get banned for it (after administrators turn pseudo-trolls to bait adversarial responses).

Curiously, this shallow thread prompted nothing, but a thread of substance and research prompts a ban? Go figure.

cynwulf wrote:

I'm not sure what Linux KMS/DRM video driver stack and X.org server have got to do with systemd.

Even putting aside the blatant blame-shifting game (what bug hunting or diagnosis did you use to reach the conclusion on what's occurring on my machine?), it's a valid question - but directed at the wrong person, and should be directed at the systemd developers themselves; one wonders why desktop environments (such as say, LXDE, KDE and XFCE) are being integrated into systemd.

Along with, of course, everything else.

And don't bother with the 'init'/'umbrella project' switcheroo, someone already tried it and from what I saw they didn't come back (unless it was under a sock account).

ok.
I don't really care what version of lubuntu do you want to run. All are the same (here 16.04 or whatever you want to "challenge");
lubuntu_16_06_in_VM.png

think a bit about the logic: if 17.07 runs fine (with systemd) and 14.04 runs fine (also with systemd). so just in the case, if something would go wrong, then it would be lubuntu devs fault. Not systemd. If you would have a little of good will to understand OS you are running, you would know what specific piece of software can or can't do.

The weakness of your arguments lays in the fact that anyone who is pro systemd will laugh at your anti systemd misinformed propaganda. Learn about init learn about your "enemies" by first hand experience. Then this might be serious discussion.

As of now this is nothing more than zealotry. Your arguments in this particular form are not rational. You seem like obnoxious child who just heard something but it is not even able to properly laid valid arguments.

I am not defending systemd but I believe that you are not doing any service to "anti-systemd" point of view

#20 Re: Off-topic » Adventures of the systemd clownface » 2017-10-23 13:08:12

fog
Connectorivity wrote:
fog wrote:

this is your vm setup/vid card fault. Nothing to do with systemd:
https://thumb.ibb.co/fYmKqm/lubuntu_in_VM.png

I heard that last solar eclipse was caused by excessive use of systemd....


I do believe that is 17.04. Joshua was using 14.04. 17.04 works perfectly fine in a VM, hence Joshua's point that the addition of systemd makes it act differently in a VM. The eclipse was quite great... always remember to use glasses!

This is just wild speculation, broken vid card has nothing to do with systemd. I don't know what VM he is using, but take look at hardware configuration of VM host.
When I have time I can try to load 14.04. ....and in the case of problems ask at vbox forums?

here you go 14.04 running just fine as VM guest..
lubuntu_14_04_in_VM.png

now for clarification: latest SystemRescueCd (Gentoo/OpenRC based) vid is broken too (previous versions worked), Whonix (Debian/systemd) generates cpu errors (VM version).
as you can see none of this has anything to do with systemd.
I think that zealotry is bad for anything. Also you clearly do not bother to solve problems just blame on something. That is just laziness.

#21 Re: Off-topic » Adventures of the systemd clownface » 2017-10-20 18:21:13

fog

this is your vm setup/vid card fault. Nothing to do with systemd:
lubuntu_in_VM.png

I heard that last solar eclipse was caused by excessive use of systemd....

#22 Re: Off-topic » When you can't tell the difference between Windows and systemd » 2017-10-19 13:08:11

fog
JoshuaFlynn wrote:
FOSSuser wrote:

You are forgetting BSD, it is what was used prior to Linux development, is still available freely, & is totally free of the systemd bug. smile

Do you mean like OpenBSD and FreeBSD? Me and a friend were digging into various OSes to see which ones don't have systemd.

I eyeballed Alpine whilst my friend eyeballed OpenBSD and Gentoo. Surprisingly enough, all had traces of systemd. Alpine doesn't have systemd initially (great if you like 1980s text command interface with no real functionality, I guess?), but the moment you install XFCE (seemingly the only desktop environment you can get working on there), udev dependencies come flying in along with systemd references. In the case of OpenBSD I was told by my friend that folders (/lib/systemd etc) were found on there, and in the case of Gentoo systemd was a running process(!).

In both Alpine and Gentoo's case they make a point of stating they're systemd-free, so it's quite surprising. OpenBSD not so much, but I regularly hear how BSD is systemd free.

I probably should download an ISO of FreeBSD and take a look. Perhaps people's ideas of 'systemd-free' is different to mine; I mean in the sense of absolutely no dependencies, files or folders referencing such a thing (even if such a thing isn't installed per se), what I'd call 'certifiably systemd-free'. If there's still a file poking it's head up, for all I know it might be creating yet another system vulnerability that just hasn't been discovered yet.


(Call me paranoid if you will, but paranoia kept me from moving onto a systemd based OS, and the DNS remote code execution and admin root privilege 'it's a feature not a bug' along with... other questionable practices means paranoia gets more screen time when it comes to OS decision making.)

If you are into systemd free OSes (well mostly linux distros) the this may help:
http://without-systemd.org/wiki/index.php/Main_Page
https://www.reddit.com/r/linux/comments … or_can_be/
https://systemd-free.org/

I keep my laptop systemd free and currently running Slackware, Funtoo, Devuan, FreeBSD, HardenedBSD, OpenIndiana.
Was using OpenBSD, NuTyX, Obarun, Artix, CRUX, Gobo linux, Sabayon and Alpine (I dropped Arch in 2005 long before systemd arrived).
BSDs are using BSD style init
OpenIndiana is using SMF

more here
https://wiki.gentoo.org/wiki/Comparison_of_init_systems

From my perspective, unless something really stands out I would not bother. While I can understand Debian Devuan split, I find it bizarre that there is so many Ubuntu children which differ only in WM/DM. 
Same goes with a lot of derivatives of Arch, Slackware, Debian.
Sometimes it is difficult to find real (technical) reasoning behind new distro. Except free choice.

Connectorivity wrote:
cynwulf wrote:
FOSSuser wrote:

That surprises me about OpenBSD, it's Canadian based, & when I use it, it is with Fluxbox & Firefox, it must be the programs that are added bringing it in. sad

There is no systemd in OpenBSD (or any of the other *BSD derived projects).  You might find some cruft in the way of redundant directories or configs in certain ports (some ports may even spit out redundant dot files), but none of it is functional or of any use.

What would happen if I were to remove these dot files?

pretty simple:
check out what will happen with your ~/ after deleting all .* files. Just loosing some config settings. Mostly though these are cleaned anyway.

#23 Installation » OpenRC and eudev installation in Devuan ceres » 2017-10-18 20:26:06

fog
Replies: 5

I intentionally selected the subject similar to this one:
https://dev1galaxy.org/viewtopic.php?id=1128
that is I did exactly the same as described in the topic above.
in detail:
1) updated Devuan Jesse
https://talk.devuan.org/t/upgrading-dev … -ascii/363
2) installed openrc
https://dev1galaxy.org/viewtopic.php?id=1128
and removed services I don't need
3) installed eudev
https://dev1galaxy.org/viewtopic.php?id=1543
4) installed libre linux kernel from sources
http://linux-libre.fsfla.org/pub/linux-libre/releases/
compiled deb kernel streamlined for my hardware/virtualbox

Devuan_ceres_Opeb_RC_eudev_4_13_7_libre_f.png

with LXDE system takes 216MB with fluxbox or openbox this will take much less of course.

When I was trying ceres a month ago system was freezing often. Now, after few hours ceres still behaves. To me this means that developers are working hard to get new Devuan ready.

#24 Re: Hardware & System Configuration » linux-libre kernel 4.1.43 upgrade » 2017-10-14 22:01:09

fog
garyz.dev1 wrote:

a little looking on his website came up with this link   https://jxself.org/git/linux-libre.git

thank you, I did not notice it.

#25 Re: Hardware & System Configuration » linux-libre kernel 4.1.43 upgrade » 2017-10-12 17:49:15

fog

hello,
are there linux-libre sources available or only compiled kernel. From the look at jxself.org/linux-libre does not seem as sources are available?

Board footer

Forum Software