You are not logged in.
You know systemd, a USB was put in? Waiting for some stupid shit (1 min 30 seconds/infinite). I frequently connect to NFS, sometimes server gets broken. Then I click reboot, but it won't reboot because of systemd, and this happens on my debian system. Does it also happen with devuan? I am so sick of this...
recklessswing wrote:I FUCKING DID IT!!! I GOT INTO THE BIOS AND CHANGED BOOT ORDER HECK YESS!! But didn't install to 1GB disk, it's probably die in a year anyway. NAND FLASH what could I expect? So I installed devuan into an SSD in another pc, then put it inside.
Congrats, friend :-)
Sadly couldn't make it under 1 GB. Alpine linux is too alien to me. I'll just use an SSD.
I FUCKING DID IT!!! I GOT INTO THE BIOS AND CHANGED BOOT ORDER HECK YESS!! But didn't install to 1GB disk, it's probably die in a year anyway. NAND FLASH what could I expect? So I installed devuan into an SSD in another pc, then put it inside.
I am talking about netinstall. I got a very spesific device, it has a 1GB builtin USB disk. It's an hassle to remove. What if I just install netinstall, no GUI, nothing? How much space will it take?
Why in the hell netinstall doesn't enable this? This is so primitive. Why not just enable hot plug automatically in netinstall, are we living in 90's? Please tell me.. Just because I unplugged the ethernet cable now I just need to restart it to make networking work again.. Sigh.
The default desktop theme is installed with desktop-base but all the old themes from grub to the desktop are available in the repos. You can also get all the pieces at:
https://git.devuan.org/devuan/documenta … t/graphics
If you need help finding where to put them just holler . . .
That git link is broken. Can't download anything from there. Btw, wasn't there a dark mode for these themes? And what about pc's that don't currently use devuan? I run debian on one of my laptops and I want this theme pls.
I think that's the clearlooks-phenix-cinnabar-theme package. EDIT: and cinnabar-icon-theme.
I found it but after a lot of googling. Wow. This shouldn't be this hard man.
What about icon themes and window options? Where to find those too?
I liked devuan 3's reddish colors more than this devuan 4. How could I bring those themes and icons back?
You can nano /etc/apt/preferences.d/systemd
Package: systemd
Pin: release *
Pin-Priority: -1Package: *systemd*
Pin: release *
Pin-Priority: -1Package: systemd:i386
Pin: release *
Pin-Priority: -1and than use as many compatible repos as you like. It should be ok. For example I have LMDE chimaera edition))
But if some package from another repo requires systemd as dependency than you are out of luck with this package.
I tried similiar stuff but in the end they failed. Good try though.
I've looked at porting OMV to Devuan a couple times, but the author of OMV has tied the majority of his code directly to systemd behavior.
It will require a fork and a lot of unwinding of hardcoded systemd stuff to get it going.
I think it won't work then. Thanks for info.
At first I had to enter name and password blind, then the screen was switched to the corresponding output. Then I enabled in slim.conf the sessionstart_cmd with the name of an executable script file, where the same xrandr commands are called. Worked fine on my old Thinkpad.
This would probably work, but can't try. Changed to lightdm already. Works already.
For example this was on chroot:
root@pardus:/# apt-get full-upgrade
...
Downloading packages etc.
....
....
Removing: systemd-sysv (247.3-7+deb11u1) ...
dpkg: systemd: some dependency problems blah blah
plymouth depends on this: systemd (>= 232-8~).
libpam-systemd:amd64 depends to this: systemd (= 247.3-7+deb11u1).
libnss-systemd:amd64 depends to this: systemd (= 247.3-7+deb11u1).
Removing: systemd (247.3-7+deb11u1) ...
systemd is the active init system, please switch to another before removing systemd.
dpkg: systemd paketi işlenirken sorun yaşandı (--remove):
systemd paketi pre-removal betiği kuruldu alt süreci 1 hatalı çıkış kodu ile sona erdi
#means systemd pre removal script is installed but sub process returned error code 1
dpkg: çok fazla hata oldu, işlem durduruluyor
#dpkg: too many errors, stopping the process
İşleme sırasında hatalarla karşılaşıldı:
systemd
Çok fazla hatayla karşılaşıldığı için işlem yarıda kesildi.
#Because of too many errors the process is halted.
E: Sub-process /usr/bin/dpkg returned an error code (1)
There are the commands in the links I posted. It used to work but not anymore. Can't remove systemd. Thus it fails. Even though I try to remove it from a chroot.
This is an UNOFFICIAL method, that used to work. But not anymore.
EDIT 1: I also tried direct migrate from debian to devuan, that now also doesn't work because of similiar errors? Which is this:https://www.devuan.org/os/documentation/install-guides/chimaera/bullseye-to-chimaera
The point is, it's debian but on systemd related packages, it uses devuan repos instead. Rest is debian. But it doesn't work anymore. It says systemd is the init system bla bla, and can't remove it. No matter how you try. Is there a way to override this? Here was a topic I used: https://forum.pardus.org.tr/t/pardusu-nosystemd-hale-getirmek/20676
Don't mind the Turkish, you get the idea I hope. Pardus is another debian based system btw, %100 the same. I tried this with debian before also and it worked. But not anymore it doesn't. At 4. phase it uses live usb and we chroot inside it, and we try to remove systemd. But doesn't work.
Why I do this? Sometimes devuan repos go down for a long time. With this way we use devuan repos only for systemd related packages thus less usage.
Probably calling xrandr in your .xsession or .xinitrc may help.
Here my example on an older Thinkpad T410S:
xrandr --output VGA-1 --primary xrandr --output LVDS-1 --off
But before simply call xrandr without any parameters, to figure out what the names for your outputs is. In above example VGA-1 is the external monitor and LVDS-1 the laptops own screen.
Sadly this didn't work. I want this to work on slim login screen. I assume this .xinitrc is run when login is complete, so it's useless.
If you go into the display setting, you should be able to set the external monitor to be the primary.
Bro you don't get it. I am talking about login screen... Not the display screen after the login screen.
I use a zebra printer on a debian machine, and I used devuan machine to connect and print from it. I did nothing in devuan machine at all. Just setting up printer on debian, then when I open printer-options, there is that printer(given that they are connected to the same network). Then I printed, it worked the first time. I am happy. Although, for few first tries, it shown printing pages too big for it's size. For example I use something like 50*30mm, but libreoffice writer page there is 500*300mm at least. But after a few restarts now it works. Great, we don't depend on systemd for this then
I have a laptop, it's own screen has lightning problems. So I use another monitor. But when logging with slim, it shows the login text on the laptop screen, I can barely see that screen. I want that thing shown on the monitor I plugged.
Haven't tried it but their colllectd .deb has a sysvinit script as well as a systemd unit file so it looks promising.
Why don't you experiment in a disposable VM and report back?
Didn't work. It gave this output:
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:
The following packages have unmet dependencies:
openmediavault : Depends: netplan.io but it is not installable
Depends: systemd but it is not installable
Depends: systemd-sysv but it is not installable
E: Unable to correct problems, you have held broken packages.
bash: omv-confdbadm: command not found
root@somepc:/home/user# rm /etc/apt/sources.list.d/openmediavault.list
Is it possible? It's quite possible to install omv on top of freshly installed debian. Can I do it with devuan?
Pop 22.04 has a weird problem, no mouse at all works. Only touchpad. But on devuan 5.18 kernel, everything works. The backports one I mean. I am back with devuan. Does anyone has the same problems with ubuntu 22.04 and derivatives?
Why don't we fork systemd instead? Let's just remove unneccessary parts. Can't we do that? Wouldn't it be better? Or worse?
Will it be something we hate as much as systemd? Just curious. Sorry if this was asked before. Is it as bad as systemd or worse? By the way, why don't we fork systemd instead? Let's just remove unneccessary parts. Can't we do that?
Hello:
deepforest wrote:thanks for help!
You're welcome.
deepforest wrote:... is it worth trying to install nvidia-legacy-340xx ...
The 340XX drivers are propiertary/closed source and Debian cannot supply a 340XX package because Nvidia will not update them for newer kernels.
True to their A1-asshole mentality, they will not release the code for the hardware to be used in newer kernels.
What about old amd cards? How do they work then? Like for example, hd 6850. I still use it with 5.10 kernel. I don't think amd still release something for them. Just curious. I also got some x1950, a prehistoric card.
Which results in things like, I for one set up a password with ö, although I selected Turkish keymap at start and pressed ö in my keyboard, it still uses English keymap which that, password doesn't wont really have ö in it, instead it has "," which is in place of ö. That is just an example. Probably happens with all non English languages. I think Swedish has ö, Germans have ü. I can pass this because I know English keyboard aswell, so a lucky guess fixed this problem for me.