next time you go through an airport, make a joke to the officers that you are carrying a bomb - see how your free speech works out for you and remember you haven't escalated to physical violence.
trolls threatening rape and death are not subjective, would you tolerate someone directly threatening your family? You can call someone all the names you like in freedom of speech (except some examples like being anti-Semitic) but threatening someone's life in not "freedom of speech" in a civilised society
its not about "some punk ass talking shit", its about anonymous rape and death threats against a person and/or their family. I couldn't give a shit about trolls talking shit because i don't know and therefore i don;t care about their opinion, but physically threatening my family is a different thing altogether
well well, now we've got UKIP supporters/Daily Mail (Hilter Supporting UK newspaper) readers who have shown no intelligence whatsoever infiltrating slashdot posts
its not for that childish slashdot troll, its for the trolls that threaten death and rape etc, a bit like not being allowed to shout "Fire!" or "Bomb!" in a theatre as a joke as there is no way of knowing if its true. Jail time might be a little much for a first offence but front page exposure of the exposed troll might be a start
if i recall Daniel Stones presentation, he said they removed "network transparency" from X and its now "network capable", they don;t appear to be the same thing
Journald in conjunction with syslog
Compatibility with a classic syslog implementation can be provided by letting systemd forward all messages via the socket/run/systemd/journal/syslog. To make the syslog daemon work with the journal, it has to bind to this socket instead of/dev/log (official announcement). The syslog-ng package in the repositories automatically provides the necessary configuration.
As of systemd 216 the default journald.conf for forwarding to the socket is no. This means you will need to set the option ForwardToSyslog=yes in/etc/systemd/journald.conf to actually use syslog-ng with journald. See Syslog-ng#Overview for details.
If you use rsyslog instead, it is not necessary to change the option because rsyslog pulls the messages from the journal by itself.
" One reason X has a lot of stuff is that it supported a lot of different obscure operating systems. I guess that is why it had an ELF loader (if this is even true). " - you should really watch the whole of Daniel Lyons video, it explains a lot of things why Wayland came about and lists a lot of issues with X
why is it an issue, its just another tool to use. Do you complain about just how many editors are there? is more than one editor needed? you can create yourself a little alias or script (bash, bourne, zsh, etc etc) that extracts the text files and continue as normal or you can just configure it to suit your needs. heres a link on how to set up systemd to log as text https://fitzcarraldoblog.wordp...
I know, i've used the horrible things in the long distant past. I also remember the days that anyone using a GUI was trashed. A GUI is only optional if you don't need to use GUI programs. X is an outdated mess that has a lot of the same "complaints" that the anti-systemd posters moan about (do one thing etc etc) but X gets defended instead of trashed.
Its a distro's choice of whatever it wants to include in its distribution, no-one is forcing you to use it so its not sabotaging anyone elses stuff. systemd can be uninstalled and any init system used, its just a choice you have to make.
This explanation is from Eric Griffiths who wrote The Wayland Situation: Facts About X vs. Wayland
II) “X is Network Transparent.” Wrong. Its not. Core X and DRI-1 were network transparent. No one uses either one. Shared-Memory, DRI-2 and DRI-3000 are NOT network transparent, they do NOT work over the network. Modern day X comes down to synchronous, poorly done VNC. If it was poorly done, async, VNC then maybe we could make it work. But its not. Xlib is synchronous (and the movement to XCB is a slow one) which makes networking a NIGHTMARE.
Slashdot Mirror
next time you go through an airport, make a joke to the officers that you are carrying a bomb - see how your free speech works out for you and remember you haven't escalated to physical violence.
trolls threatening rape and death are not subjective, would you tolerate someone directly threatening your family? You can call someone all the names you like in freedom of speech (except some examples like being anti-Semitic) but threatening someone's life in not "freedom of speech" in a civilised society
its more to do with trolling like this http://nakedsecurity.sophos.co...
no-one will spend any jail time for slashdot type trolling but they should for this type http://nakedsecurity.sophos.co...
as a 12 year old, you'll probably get detention
its not about "some punk ass talking shit", its about anonymous rape and death threats against a person and/or their family. I couldn't give a shit about trolls talking shit because i don't know and therefore i don;t care about their opinion, but physically threatening my family is a different thing altogether
don't propagate such nonsense, you sound like a UKIP supporter and we know that UKIP supporters have no grasp of the facts
well well, now we've got UKIP supporters/Daily Mail (Hilter Supporting UK newspaper) readers who have shown no intelligence whatsoever infiltrating slashdot posts
shhhh... don't use facts to destroy his small minded views or lack of understanding
its not for that childish slashdot troll, its for the trolls that threaten death and rape etc, a bit like not being allowed to shout "Fire!" or "Bomb!" in a theatre as a joke as there is no way of knowing if its true. Jail time might be a little much for a first offence but front page exposure of the exposed troll might be a start
step away from that mirror before it breaks
if i recall Daniel Stones presentation, he said they removed "network transparency" from X and its now "network capable", they don;t appear to be the same thing
i think the argument is over "network transparent" and "network capable", they don;t appear to be the same thing
i doubt there are any broken feelings, just despair as to why there are so many twats like you in forums
have a read of this section from this article for Arch for a possible solution https://wiki.archlinux.org/ind...
/run/systemd/journal/syslog. To make the syslog daemon work with the journal, it has to bind to this socket instead of /dev/log (official announcement). The syslog-ng package in the repositories automatically provides the necessary configuration. /etc/systemd/journald.conf to actually use syslog-ng with journald. See Syslog-ng#Overview for details.
Journald in conjunction with syslog
Compatibility with a classic syslog implementation can be provided by letting systemd forward all messages via the socket
As of systemd 216 the default journald.conf for forwarding to the socket is no. This means you will need to set the option ForwardToSyslog=yes in
If you use rsyslog instead, it is not necessary to change the option because rsyslog pulls the messages from the journal by itself.
f*ck i mean Daniel Stone
" One reason X has a lot of stuff is that it supported a lot of different obscure operating systems. I guess that is why it had an ELF loader (if this is even true). " - you should really watch the whole of Daniel Lyons video, it explains a lot of things why Wayland came about and lists a lot of issues with X
well, don't configure it for binary logging then https://fitzcarraldoblog.wordp...
here's how to do it https://fitzcarraldoblog.wordp...
why is it an issue, its just another tool to use. Do you complain about just how many editors are there? is more than one editor needed? you can create yourself a little alias or script (bash, bourne, zsh, etc etc) that extracts the text files and continue as normal or you can just configure it to suit your needs. heres a link on how to set up systemd to log as text https://fitzcarraldoblog.wordp...
I know, i've used the horrible things in the long distant past. I also remember the days that anyone using a GUI was trashed. A GUI is only optional if you don't need to use GUI programs. X is an outdated mess that has a lot of the same "complaints" that the anti-systemd posters moan about (do one thing etc etc) but X gets defended instead of trashed.
Its a distro's choice of whatever it wants to include in its distribution, no-one is forcing you to use it so its not sabotaging anyone elses stuff. systemd can be uninstalled and any init system used, its just a choice you have to make.
can the system encrypt the log files are they are written or is it done afterwards?
if those complaints are "old" but still relevant they might as well be commented on and mentioned
This explanation is from Eric Griffiths who wrote The Wayland Situation: Facts About X vs. Wayland
II) “X is Network Transparent.” Wrong. Its not. Core X and DRI-1 were network transparent. No one uses either one. Shared-Memory, DRI-2 and DRI-3000 are NOT network transparent, they do NOT work over the network. Modern day X comes down to synchronous, poorly done VNC. If it was poorly done, async, VNC then maybe we could make it work. But its not. Xlib is synchronous (and the movement to XCB is a slow one) which makes networking a NIGHTMARE.
Have you read this at phoronix? http://www.phoronix.com/scan.p...
would this help? its a 4 page article on it http://www.phoronix.com/scan.p...