You are not logged in.
Alas, gksu has been deprecated in Debian.
In Beowulf try su -
@sadegh . . . we cannot see any images on you computer. Please post online somewhere.
Best way to do secure banking is to visit the bank in person perhaps?
This. ^^^ No online banking for me . . .
Maybe give sgfxi a try.
Read more here.
💁 ... someone just made this forum full utf8... enjoy
https://unicode.org/emoji/charts/full-emoji-list.html
Just great. Something else to block. Anyway to disable it?
Screenshot?
I did not change the mirror, I just selected the br mirror.
My question is: is there any security risk?
No. The mirrors are just rsync copies of pkgmaster.devuan.org
. . . a specific mirror from the list can be accessed using the corresponding BaseURL
This from the mirror list:
FQDN: devuan.c3sl.ufpr.br
BaseURL: devuan.c3sl.ufpr.br
Bandwidth: 20Gb/s
Rate: 1h
Country: Brazil
CountryCode: BR
Protocols: HTTP | RSYNC
Active: Yes
DNSRR: yes
I think this BaseURL needs to be in sources.list not the country code (which devuan is not set up to understand): devuan.c3sl.ufpr.br
Country codes are not available in Devuan. This from the website:
Devuan has a network of package repository mirrors in place. The mirror network is accessible using the FQDN “deb.devuan.org” via http NOT https. Country Codes (CC) are currently unavailable but a specific mirror from the list can be accessed using the corresponding BaseURL.
I know this is just going to derail the thread (I'll stop after this post, so make of it what you will), but I was more or less referring to how in the heck they are "popular", when I barely know any GNU/Linux user who has that OS as their daily driver, newbie or experienced. I could understand some exceptions, but the "number one on DistroWatch" thing just seems like a meme.
Also, isn't Systemd now included to some extent (source)?
Nonetheless, I appreciate the efforts of people like Steven Pusser who port and maintain packages not currently supported by Debian upstream.
systemd has always been available in MX:
All things are impermanent. It is a fool's task to cling to anything much less ephemeral data. The knowledge collected here quickly becomes outdated and moves to the bottom of the list. Seems like this thread is much ado about . . . well, nothing really . . . If we ever get a workable wiki, that is an entirely different medium with more lasting power.
Doesn't look like it's ever been in the repos. You can get it here.
Oooooo such big words and proclamations. Please get over yourself.
(golinux yawns . . .)
golinux wrote:Vernon wrote:Why undisclosed?
Because that's the only way to insure that the outcome will be completely random and not engineered by someone with an axe to grind.
Everyone has an axe to grind. My axe is called Freedom and Openness. Based on your advocacy of post editing time limits and keeping those limits secret, your axe is apparently called something quite different.
You are so busy blustering and demanding, you really didn't think that through, did you. A time limit would only be a "secret" until it was triggered, then it wouldn't be a secret anymore would it. LOL! And if it's never triggered, what does it matter? You just want to latch on to anything to argue and demand. That energy coming from someone who has been here only about 2 months is quite out of sync with this peaceful, collaborative project and disrespectful of the hours of love we have poured into Devuan since the fork.
(golinux wishes this forum had an ignore feature)
golinux wrote:The reaction to the current option sends a message that should be heeded. My suggestion would be to experiment with the edit timeout window starting at X number of months/days (to be collectively decided and undisclosed).
Why undisclosed?
Because that's the only way to insure that the outcome will be completely random and not engineered by someone with an axe to grind.
golinux wrote:Then wait and see if anyone notices.
So, sort of like when you complain to a Debian package manager about only supporting systemd and they reply lets see if anyone notices?
Nothing like that if you read the above. That's just how I would do it to make the community response completely unbiased. Not saying it will be done that way.
One excellent point that you made is to figure out what happens when an initial post is Deleted rather than just Edited. Does this only Delete the initial post or all the other follow-up posts as well?
Deletion of an initial post should only be allowed if there are no responses, IMO. That's the way the Debian forum does it. I posted a link about that a few posts up.
Suggestion . . . maybe close your eyes and let the mind and breath settle for a few minutes . . . the world appears quite different when the churning stops . . . ![]()
We're a pretty mellow and collaborative bunch so I don't see that happening. In fact HoaS, you seem to have mellowed considerably since you've been hanging around here. The reaction to the current option sends a message that should be heeded. My suggestion would be to experiment with the edit timeout window starting at X number of months/days (to be collectively decided and undisclosed). Then wait and see if anyone notices.
This forum is less than a side-dish on Ralph's menu. There would be no Devuan without Ralph. Period. This issue will be discussed internally in a few days. In the meantime, please be patient and constructive in your comments. And remember to breathe . . .
FYI documentation of Debian packages touched by Devuan in Beowulf.
There are 453 of which 218 deal with task-[localization] and 29 probably duplicate packages in beowulf-proposed-updates.
I wasn't aware that the number was this high.
There are backups but no revision software. A forum is by nature ephemeral so there's not really a need for it IMO. It is always possible to dig in the Internet Archive.
@doa379 . . . please gain some knowledge about devuan before you speak. Or perhaps you like embarrassing yourself . . .
https://pkgmaster.devuan.org/bannedpackages.txt
https://dev1galaxy.org/viewtopic.php?id=1925
https://pkginfo.devuan.org/
This forum, like debian's, is a hybrid of problem solving, wiki-like documentation and social interactions. It's been working quite well and I see no reason to throw out the baby with the bathwater. As I said before, we need to find the sweet spot between users having the option to improve/correct posts at the point where technical errors were made (not 10 posts later) while not having the ability to delete an entire thread which I assume deleting the first post would do. Also . . . as mentioned by Vernon, posters must have the ability to mark their issue as [SOLVED].
Disabling the login combined with a marker below the username that this user no longer is active and/or turning the username unclickable could be enough.
Yes. Scrambling info in an account is a solution that is quite effective.
Reasons to allow unlimited time for editing.
Posted issues take an indeterminate time to solve. By setting an edit time limit, you don't allow posters to change a topic subject to [solved]
I am a very poor typist and make many typos and grammatical errors which I may not notice until days later when reviewing my posts. And yes, I do like to go back and review my posts and admire them
I may discover additional issues that I should have discussed originally in a HOWTO days later or weeks later. Edit timeouts could prevent me for updating the HOWTO
Excellent points. +1