You are not logged in.
Nice to see you jheaton5! Several DUFers have found their way here already. Speaking of DUF . . . isn't the yearly hosting fee due around this time of the year? Haven't seen a mention of it over there.
There will be. I have the same 32 bit problem. ![]()
parazyd is walking the talk! This just posted on the dng list:
heads 0.0 is out!
It finally happened and it's not vaporware!
heads 0.0 is a preview live CD of what heads is going to be about. This release is not intended to be used from a security point of view, but as a showcase and testing point of view.
I am not even completely sure everything is torified, but hey, that's what testing is for, no?
So please, download the ISO from the downloads link in the above navbar and abuse the hell out of it
Throughout a certain period, bugs will be fixed within the build system, and patched releases will be released without announcement. So check regularly for 0.0.x releases on the downloads page...
But first, read some notes on it all:
Booting the ISO can be done with some virtualization like qemu or VirtualBox, or it can be dd-ed to a USB flash drive and booted on a laptop. It can be burned to optical media as well.
The MATE desktop environment is not yet included in this release, only AwesomeWM is installed. You can install other environments easily by yourself.
When booted, you will be presented with instructions on how to login, and start a graphical environment. Keep in mind the root password is shown only once and you will have to reboot if you lose access to it.
FWIW on my Devuan Jessie Xfce, I have both udisks2 and libsystemd0 installed but not libpam-systemd. Drives do not automount but do with a click on a right button menu option of the icon that pops up on my desktop.
Is anything like this on the ML or in git?
Not that I've seen. If only . . .
When is the best time for IRC questions??? (EST)
Anytime. The is often a burst of activity when Europe is awakening (and we in the US are sleeping). But there is no clear pattern. Post and you can check the botbot logs for a response anytime.
The definitive answer is in the documentation that is buried at https://files.devuan.org/. That info should be in the https://files.devuan.org/README.txt file and on the index page of the website. Currently it is very hard to find.
OK, jaromil has added that info to https://files.devuan.org/README.txt Will be easier to find now.
What is the issue with ascii and ceres?
Amprolla, that is responsible for the Devuan repos, sometimes lags a bit behind the Debian repos. There are also more packages that need attention as systemd expands its reach. Focus now is on Jessie. Feel free to join in the effort.
Introduction
The purpose of this walkthrough is to give the very basics of converting Debian packages to Devuan. This means making sure that there is no hard dependency on systemd in packages. The good news is that it's much easier to package for Devuan right now than it is to learn packaging from scratch, so this is the best time to jump in if you want to maintain packages for Devuan.
It's important to point out that this is not a manual, there is no intention to document everything about Debian packaging in this one page. Rather this guide just shows you how to remove systemd from a package and make sure it is usable for Devuan. You really do not need to be amongst Debian's elite to help out with Devuan packaging, and everything here will be explained as clearly as possible.
@millpond: I posted your question on irc and here's the response. Centurion_Dan is doing most of the packaging for Devuan:
<Centurion_Dan> golinux: it's not scripts, rather changes usually in the debian/rules to disable the reliance on systemd api's
You might also find dev1fanboy's Maintainer walkthrough useful.
IIRC amprolla2 will tag Debian packages that rely on systemd and quarantine them until they can be repackaged sans systemd.
rrq has put a new and effective spam deterrent in place so signatures have been re-enabled.
@pedropt . . . Could you please use quote instead of code tags when appropriate as in above post. Thanks.
@bobemoe @iamwhatiam . . . The best thing I can think of would be to call @CenturionDan in a response to that issue. I doubt he has time to trawl through git to find issues and that would bring it to his attention. I have just done that for both those issues. As to tags/labels . . . you need permissions to create them and actually, I haven't found them that effective.
@katzenmuzak . . . Thanks for compiling that list. Those issues would have to be posted in git.devuan.org to get any attention. The best place I can think of is here but you might be able to dig out more targeted projects also. In addition I would post the list to dng where it might catch someone's attention (but will get 'lost' rather quickly).
The spam situation has been resolved. Spammers are being filtered at the door. But we can't get a break. Now our host's reverse DNS is down so some registration confirmation emails are not being delivered and we're having to manually enable them.
Which is more helpful for Devuan for me to run, Ascii or Jessie? There are a lot of rough edges and thus potentially a lot of bug reports to file. So where do the developers want us to focus attention?
You might want to check what's in jessie-proposed. Those packages may get into RC1 if the feedback is positive and bug-free. Beware that the xfce4-settings package there was broken - I had to downgrade to stable version. Don't know if it's been fixed yet. After RC1 the focus will be more on ascii.
EDIT: This just posted on irc:
<Centurion_Dan> Attention should be on jessie - particularly installation testing and desktop useability issues.
Have you thought about using captcha - http://captcha.net/
Chanku says it requires JS and wants to avoid that..
@Pick2 . . . bots are much more sophisticated now than they were back in '04. I have not noticed any 'groups of spammers'. It's a steady flow. Some domains are more prominent than others but I see no pattern that would ever allow 'account activation' to be disabled. Even if we could get a script to nuke them based on the SFS db, some would still get through. It would however, simplify the process of activating legitimate accounts. The only solution I can see that would be 100% effective is to 'jail' the bots at the door with account activation.
Maybe https://www.stopforumspam.com could be of some use?
We've been using SFS since we went online. The spam domains are well-known to us and we can delete them with confidence. But it is CONSTANT manual labor and some are getting through before we can get to them. This approach is not sustainable. We have not yet found a way to automate deleting those registrations against the SFS database.
The question asked here is whether forum members have any thoughts about or objections to requiring activation of new accounts via admin intervention.
UPDATE: The mod requiring answers to questions worked for a while but now the bots are finding us again.
The best solution I can think of to deal with the bots is to require account activation. A new group with no posting privileges would contain all new registrations. An admin could then delete the bot accounts and move 'legitimate' accounts to the members group. This is distasteful because it is a type of censorship. But it's something I can live with and as the primary 'unverified' bot hunter, would be grateful for.
Chanku and I would appreciate feedback from all of you before we consider implementing this change. So please share your thoughts why you think this is or is not a good solution. Perhaps some of you can come up with some better ideas.
golinux
I can't remember if the root terminal icons weren't in sync between the menu and the panel when I set up my desktop but they are now. I might have changed it in the panel preferences, certainly never via command in the terminal. I change icons all the time in the panel by clicking on properties > edit > icon (just browse to the one you want to use). Done.
I just posted a quick how-to on the sleep button fix over in the Documentation section. If you get a chance to look at it, please et me know if you think it needs anything...
Very nice! Thanks for taking the time to write it up.
I will write it up soon and post in Documentation. If nothing else, you can have endless fun making the 'special buttons' do whatever you want...
Well, I won't be doing that but there are others who might want to. ![]()
Yes, I'd be interested in learning something about all that systemd junk...
Here are the first few nibbles. Probably more to come as I pinged jaromil, nextime and Centurion_Dan . . .
<KatolaZ> golinux: those should be systemd-related scripts installed by other packages
<muep> it is usually harmless for a package to ship a config file for something that is not installed
<golinux> muep: If a package is not installed, why would related config files be sucked in for a non-existent purpose?
<muep> golinux: because packages include those files for the cases where they are installed alongside the thing that does not happen to be present
<muep> and because devuan is using debian packages as-is where they are suitable
<KatolaZ> golinux: and because we should not make the same mistake that all the distros have done
<KatolaZ> i.e., making it impossible to use anything else
<KatolaZ> if a package has scripts for runit or openrc or systemd, why should we remove them?
<KatolaZ> those script will never be executed if runit, openrc, or systemd is not installed
The conversation continues here on botbot.
I was able to whip up a simple acpi event catcher and script to have the sleep button work.
Perhaps you could share your fix in Documentation?
I did notice, in my poking around, that there is a lot of systemd stuff in /etc/systemd/system, /lib/systemd, and /var/lib/systemd. What's that all about? Or did it get sucked in by something I installed maybe?
I also have these components installed and found it 'disturbing'. That question has been asked before - maybe by me - but I can't remember the answer. LOL! I'll throw it up on #devuan and see who bites . . .
Do you have upower installed? That used to be the solution but may not be going forward. There is history in the botbot logs.