Smdev

0 views

Skip to first unread message

Casimiro Lurten

unread,

Aug 5, 2024, 12:57:16 PM8/5/24

to kingbackbreakouv

Smdevis simple device manager. It's alternative to udev, eudev and mdev. I maintain smdev ebuilds on my overlay[1]. I have working keyboard, mouse, touchpad, trackpoint, sound, graphics, wifi, hotplug and module autoloading with the default config and initscript that comes with the ebuild.

It is recommended to make LiveCD or LiveUSB before rebooting first time with smdev. It is possible that your system goes into unbootable state if something goes wrong. If you wish to remove eudev you should do it after you have made sure everything is working with smdev.

But we are stuck with a big IBM chunk, we are not out of the hole yet, we love what IBM does for us (like junkies love the pusher) from the second we hit enter on the bootloader screen. udev hooks running and rerunning and eternally running till everything is shutdown and gone to sleep.

Then comes this other solution, an intermediary, which can utilize any mdev provider, simulate the ability to be triggered by a change in hw, run the mdev (of choice!), and provide new definitions for hw adder/removed. This project was called nldev, a middle man.

Then skarnet begins work, not yet finished, to provide a true and complete udev alternative, still less than 1/3 of the code of (udev/eudev/libeudev), and it does work if you study the subject in depth and can configure it right. A nice template of a .conf file to uncomment all its abilities that are utilized, would have been nice, but skarnet wants you to do your own research and make your own choices, just like s6 s6-rc, etc. No ground food and chewed ready for swallowing from skarnet, they like to see you in tears before you make their sw work. Their server has been running for a ?decade? with it, with reboots only taking place in leap years, and if there is no pandemic.

Because they want us fenced in and dependent to control us. It is our single mission in life to bring those fences down, because on our land we can build autonomy, on their land we will always be slaves. We will not make this mistake again, to allow our land to be purchased for individual use. Am I losing it? No, anticapitalista knows what I am talking about.

Talking with someone who has done extensive work to make this run says that his setup is such that at least the small problems I have witnessed are not there, in a very similar system. Also, there are several modules/parts of smdev that provide it with additional functionality, oen is a uuid module which helps it populate the dev/disk directory.

I just felt that a few people in antiX may be interested to know that such alternatives exist, therefore the post.

The more people become aware of the possibilities the faster they will grow and provide better functionality.

How can runit not be dead but consolekit2 is? When will the mainstream linux dev community brand runit as dead? And when they do, what is antiX and void, and artix, and many others expected to do, return to sysvinit because runit is DEAD!!!

d-feet [written in python] is a D-Bus debugger that allow you to:

* View names on the session and system bus

* View exported objects, interfaces, methods and signals

* View the full command line of services on the bus

* Show values of properties

* Execute methods with parameters on the bus and see their return values

Then make sure, that an update will not reinstal the dbus daemons

# apt-mark hold dbus dbus-daemon dbus-x11

All dependencies to dbus are still fulfilled, but no dbus is running.

A few programs will not work properly anymore and have to be replaced by others.

If an application does not start anymore, maybe the exec line in the starter has to be modified.

The system will be fully funtional, if you can do without certain desktop notifications.