You are not logged in.
Danielsan wrote:You sure?
Yes. All true UNIX systems provide a unified set of user space tools along with /sbin/init. The BSDs are closer to true UNIX than Linux so they emulate that approach.
I made no comment about commercial influences.
I will now though:
http://www.openbsdfoundation.org/contributors.html ← both Google and Microsoft are regulars in that list.
https://freebsdfoundation.org/our-donors/donors/ ← Facebook as a top level contributor? Really?
Seems like there is nothing that can't be and isn't being coopted. It is the genius of capitalism, and I've seen it over and over again. Anything good and free is bought out sooner or later. Or so it seems. We live in a shit culture.
^ Well it's certainly one of my coping mechanisms, along with trolling. How do you manage?
I manage by immersing myself in actual reality. Not virtual, not augmented, not theoretical, but real, physical reality. I cut my firewood, I take care of my livestock (goats, sheep, and chickens), I grow as much as I can in my garden in season (it's now under half a foot of snow). That sort of thing. I entertain myself by walking in the woods here with my dogs, and playing music alone and with my friends (haven't been in a band for a while), and so forth. Now I am older and also somewhat disabled, so I have learned how to pace myself.
Here in the US, our 'culture' is, quite frankly, psychotic, and our society isn't a society. Things seem grim, and I believe, along with Yeats, that
Turning and turning in the widening gyre
The falcon cannot hear the falconer;
Things fall apart; the centre cannot hold;
Mere anarchy is loosed upon the world...
There is nothing I can do about it - it seems like a Juggernaut bearing down. About the best you can do is try to get out of the way.
Hey! Happy New Year Everybody!!! :-)
Hello:
Anyone seen this?
https://www.theregister.com/2021/12/10/ … foss_fest/
https://www.ventoy.net/en/index.html
Best,
A.
Ventoy is very good - been using it for a while. I have a 32 GB USB stick. If I want to try a new iso, just copy it onto the USB - no 'burning a USB' or anything. I have many things on there. I boot to it, and there's a menu of all the iso's, and you pick one and it boots. It is a marvel - it just works.
Just tried it on my Chimaera box (Arch and Beowulf in parallel installations): Adding that line to /etc/default/grub does not make any difference on efi installations.
rolfie
Works fine on my efi rig running either Daedalus or Ceres. Is it even an issue in Chimaera?
Saying that, i dont care these days, nothing i do on a computer warrants spec-ops type privacy, im actually looking to quit computing altogether. I think it has run its course and is a doomed endeavor and blight on human interactivity.
Ha! I've been coming around to this view myself.
I looked up Hyperbola Linux and their website says:
"Due to the Linux kernel rapidly proceeding down an unstable path, we are planning on implementing a completely new OS derived from several BSD implementations."... and:
"Future versions of Hyperbola will be using HyperbolaBSD which will have the new kernel, userspace and not be ABI compatible with previous versions."What the!
They give reasons. That's somewhat concerning as a Linux user! But is the Linux kernel really heading significantly down that way, or is the Hyperbola site being slightly alarmist??
I think they're just being a bit hyperbolic about it.
So far, from Daedalus-testing (Devuan 5) aka Bookworm-testing (Debian 12) got updates for apps that i daily use.
Nautilus 40.2 Geany 1.37.1 Disks 40.2 ntfs-3g 1:2021.8.22-2 gtk+3.0 3.24.30-3 mediainfo 21.03-1
Awaiting to upgraded very soon 2/5 days.
mpv to 0.33.1-1 alsa-mixer 1.2.5.1-1
Also i hope Debian maintainer pass to sid soon those two-below packages, i had a few concern with them so i can't wait to check it if they've been fixed.
feh 3.7.1 conky 1.12.2
Many other packages have been updated since this topic was opened. That's why i like testing or better sid, but i'll stick on testing for some reasons that requires less attention than sid.
Guys, Do not be confused, this topic is Devuan 5 (testing/sid) aka Daedalus.
See the thread name.
Leave alone Chimaera here.
Daedalus it is one version advance than Chimaera/Ceres.
This thread serve to test (next testing/after chimaera releases).
For people who like to play in advance with testing/sid packagesI open this topic asking about next-testing as there was no repo for Daedalus, and edited it as soon as it was set. Personally, I have taken all the risks and responsibility on my testing jurney.
More here about releases names.
https://www.devuan.org/os/releasesWe know versions and names are a bit confusing at first on the early releases, as some walk faster with repos than with official releases names.
I hope i have somewhat clarified my position and forgive me if i have created a bit confusion if i did.
BR!
"Daedalus it is one version advance than Chimaera/Ceres."
There is no Chimaera/Ceres. Ceres is always unstable. Packages go from Ceres to testing. Although Chimaera has not been officially released as 'stable' yet, Daedalus appears to be the new testing. But it is not one version more advance[d] than Ceres.
I would just stick it in /etc/rc.local. I do a similar thing to defeat the power-saving on my sound card, which makes nasty pops:
#!/bin/bash
echo 0 > /sys/module/snd_hda_intel/parameters/power_save
exit 0
So amprolla always merges according to the 'matching' Debian version, and doesn't really care about stable vs. testing. And ceres will always track sid. I was just curious about the interim period.
Since I started with Devuan back in Jessie days, I've never used stable, testing, etc. in sources.list. That was made very clear from the get-go!
In the interim between Bullseye's release as 'stable' and Chimaera's release, what does amprolla do to generate the chimaera 'virtual' repo? Does it continue merging from bullseye? Or does it start merging from the new Debian testing (bookworm)? What does it do for ceres in this interim? Will it merge from bookworm, or always continue merging from sid?
Capitalism, and indeed Democracy, only "work" with an informed and educated populace. At least here in the US, we have neither. Capitalism in the US has become an abusive mind control system. Democracy has become a joke. Not a funny joke.
Since June 1st, 2021 I've been working on LinuC, a website that gives inexperienced users good instructions on how to install a small Linux on their old computer.
LinuC is now at version 0.5 and it is time to introduce it, especially in the forums of the distributions that are available in LinuC.
You can find Devuan among Further!
Please take a look at the description and check out the rest of the page if you have the time and let me know if you are happy with it. Either by email, or in the LinuC forum, or here. I will stop by every now and then :-)
linuc.mipropia.com
greetings
Patrick
On your website, you describe people that don't want to have anything to do with systemd as paranoid and mentally ill. This is incredibly insulting, not to mention idiotic. Why are you here? Why don't you go away?
I don't know that 'only the very latest machines on the market' have TPM 2.0. My computer has a Core i5 7400, TPM 2.0, and Secure Boot, and it is late-2017. Supposedly, my CPU doesn't qualify for Win11. Woe is me! Like I care :-)
sgage wrote:Not just the 64K of RAM, either. When was the kernel ported to 8-bit 6502 (or 6509 - whatever variant they used)? Never.
No, it wasn't ported, and I'm not really running Beowulf on one, but a unix-like kernel was written in 6502 assembly by the LUnix (Little Unix) project folks between 1993 and 2004. The LUnix home page is still up for anyone wanting to download LUnix and take it for a spin on their favorite Commodore 64 rig: http://lng.sourceforge.net/
Wow, that's pretty cool! I was pretty good at 6502 assembly language back in the late 70's/early 80's - strange days! My first computer was a Commodore PET/CBM. It's amazing what you can do in assembly!
dice wrote:fsmithred wrote:@andyprough:
How do you run linux on a computer with only 64k RAM???
Good question, i was thinking the same. Perhaps the 64 has some mods? I highly doubt a computer from 1982 would be able to run devuan beowulf, but i would be happy to be proven wrong.
Wait 64mb of ram? you say? That seems a bit unlikely, I mean I could understand 32mb... and maybe jwm if its 32 bit and be using something like console-tdm to start it, if you turn off certain services... *cough* dbus *cough*
Even then, 32mb seems like a stretch, but yeah, 64K sounds insanely low to be able to run devuan...
You'd have a better chance of using OpenBSD for something that small...
Just sayin...
I would also love to be proven wrong...
Not just the 64K of RAM, either. When was the kernel ported to 8-bit 6502 (or 6509 - whatever variant they used)? Never.
golinux wrote:zapper wrote:Ah, I didn't know debian EVEN had a release schedule...
Thought it was like, released when we say its ready.
They don't have a fixed schedule. They have a "when it's ready" schedule as does Devuan.
zapper wrote:Good to know, also, I thought chimaera's images were still in alpha...
They are.
zapper wrote:I probably should, but sometimes I am way too lazy for it...
That being said, I assume you just report issues that you see...? Could do that, beyond that, I don't know.
Confirmation that it works or if not what the problem is would be helpful and appreciated.
Hmm, I don't usually use alphas, on my system...
I usually wait till beta to actually consider using it.
Unless I have a virtual machine of it, which isn't a bad idea.
I don't know what I will do, given my current focus, which is more or less Hyperbola, but its a thought to consider.
The installer iso's are alpha, not the distro. Chimaera, based on Debian Bullseye (which is almost ready to be released), is well tested. I've been using it without issues for months now.
mybe mate have need a maintainer
I have been using MATE on Chimaera for months, and have never had such problems. BUT, this is Chimaera updated from Beowulf, for what that's worth. But there seems to be nothing intrinsic to MATE that is broken.
That's really great news and I highly appreciate the efforts and the collaboration that seems to enable running Debian with (at least) sysvinit again - though I have to admit that I didn't try this yet.
Assuming it becomes feasible to use Debian without systemd, I don't think it makes sense to use Devuan just for the mentioned political or "trust" reasons - at least not for me. Actually, by using Devuan you have to trust Debian as well as Devuan is pulling most binary packages from Debian - doesn't it?
If things really turn out for the better in Debian, wouldn't it become more practical to reduce Devuan to "just" a pure Debian-blend with alternative inits preconfigured and systemd-depdendent packages blacklisted?
Please don't get me wrong. I love Devuan and this community. Yet, I wonder if all the effort spent in running and maintaining an own infrastructure could not be better put into the actual work needed for init diversity? With this being said, I have to admit that the wounds from the community split will certainly not heal overnight. But as an end-user who wants to run Debian without systemd, I hope we are getting back on track.
"Yet, I wonder if all the effort spent in running and maintaining an own infrastructure could not be better put into the actual work needed for init diversity? "
That's more than a bit insulting, "actual work'. Just what do you think the Devuan team has been doing for the last years? Playing around 'running and maintaining its own infrastructure'? Do you think you just pop systemd out and pop sysvinit in? You do not seem to understand the full extent to which systemd insinuates itself, and the magnitude of the task of removing it.
If Debian were ever to offer a sysvinit option on installation (which I happen to believe will be never), it will be because of Devuan's work.
Here's the final version (I think). Tested in xfce (thunar) and mate (caja), both in chimaera. I'll rebuild the package later today.
.rubberband, .view .rubberband, view rubberband, rubberband { background-color: alpha (@theme_selected_bg_color, 0.35); border-color: @theme_selected_bg_color; border-style: solid; border-width: 1px; border-radius: 2px; }
This works fine for me using MATE (caja). What I had ended up with, which also works fine w/ caja, was simply this:
.view.rubberband,
.rubberband {
background-color: alpha (@theme_selected_bg_color, 0.35);
border-color: @theme_selected_bg_color;
border-style: solid;
border-width: 1px;
border-radius: 2px;
}
Maybe it wouldn't work w/ thunar, though. In any case, your 'final' version seems to work fine with both. I can't claim that I really understand the css lingo...
Whoops! I spoke too soon. While replacing gtk-widgets.css with the one from Purpy indeed fixes the selection rectangle issue, it creates other problems. Items on the panel have no spacing, the menus don't operate properly (no highlighting as you mouse over items), and perhaps a couple other things. Lots going on in that file! But I poked around and I think I have it solved, and the solution is quite simple.
In the gtk-widgets.css file in the new Clearlooks-Phenix-Deepsea theme, the 'rubberband' code at line begins thusly:
.rubberband,
view rubberband,
rubberband {
I looked at the corresponding code in the css file from the old Purpy (that allowed the selection rectangle to work properly), and it went like so:
.view.rubberband,
.rubberband {
So I deleted the opening ".rubberband" and put a "." in front of the"view rubberband", and the "rubberband" just before the {, and voila! A translucent selection rectangle with everything else continuing to be layed out properly. So there's no need to replace files or such - just fix what seems to be a typo in the existing file.
I will continue to test and see if anything else crops up. But it seems like all is well now...
Incidentally, MATE was forked from Gnome2 years ago, and is now (allegedly) fully transitioned over to GTK+ 3. Or so they announced a while back.
@sgage . . . does the ascii darkpurpy theme work OK on Mate? If yes, try replacing the gtk-widgets.css, applications.css and gtk-widgets-img.css in deepsea with those from darkpurpy. There is one color change towards the end of gtk-widgets.css that you'll want to keep from deepsea but the rest can probably fall back to the earlier gtk version.
[edit] Actually you probably need to use those files from Clearlooks-Phenix-purpy not darkpurpy. You can find them here
Yes! That did it. I used the above-mentioned css files from purpy, from the link you provided. I will try to analyze it tomorrow, but it's bedtime. Thanks for your efforts!!!
The fix is in compliments of ToZ on the Xfce forum. The hilighting is now semi-transparent as it used to be. Either resort to self-help with the patch below or wait for the deepsea theme to get repackaged:
Starting line 158 of gtk-widgets,css, add a ".thunar .rubberband" statement:
.rubberband, .thunar .rubberband, view rubberband, rubberband { background-color: alpha (@theme_selected_bg_color, 0.35); border-color: @theme_selected_bg_color; border-style: solid; border-width: 1px; border-radius: 2px; }
Alas, this does not work for MATE. I added the stanza as is, and also substituting 'caja' for 'thunar', but no joy. I'm sure the fix is hiding in plain sight...
Hi golinux,
I've been using the Chimaera theme for about a week now, and I really like it. But I just noticed a small glitch - on the MATE Desktop, the selection rectangle is an opaque solid white instead of translucent blue, covering up whatever it is one is trying to select. I guess I don't make group selections of things on the desktop very often, because I just noticed this yesterday :-) Anyway, thought you ought to know.
There were no new packages in chimaera for a couple of days, and now there are. I think it's possible that there really were no new packages. Buster is in freeze, so the changes should be slowing down.
I think you're right - I got 10 updates this morning.
Do you get updates if you switch to a specific mirror instead of the deb.devuan.org FQDN?
Even using pkgmaster.devuan.org I get "All packages are up to date".