Message Area
Casually read the BBS message area using an easy to use interface. Messages are categorized exactly like they are on the BBS. You may post new messages or reply to existing messages!

You are not logged in. Login here for full access privileges.

Previous Message | Next Message | Back to Linux operating system (OS), a U...  <--  <--- Return to Home Page
   Networked Database  Linux operating system (OS), a U...   [656 / 900] RSS
 From   To   Subject   Date/Time 
Message   unruh    Carlos E.R.   Re: It's bad enough that Usenet is mostly insults, now our softw   December 5, 2018
 11:52 PM *  

On 2018-12-05, Carlos E.R. <robin_listas@es.invalid> wrote:
> On 05/12/2018 15.55, William Unruh wrote:
>> On 2018-12-05, Carlos E.R. <robin_listas@es.invalid> wrote:
>>> On 03/12/2018 15.21, William Unruh wrote:
>>>> On 2018-12-03, Carlos E.R. <robin_listas@es.invalid> wrote:
>>>>> On 03/12/2018 13.45, Kenny McCormack wrote:
>>>>>> In article <ep1edf-f59.ln1@Telcontar.valinor>,
>>>>>> Carlos E.R. <robin_listas@es.invalid> wrote:
>>>>>> ...
>>>>>>> Sure, I have seen that in openSUSE. And if I typed the wrong password
or
>>>>>>> tried to use the wrong command it would *insult* me. This is a
>>>>>>> configuration which I disabled fast:
>>>>>>>
>>>>>>> /etc/sudoers:
>>>>>>>
>>>>>>> ## Do not insult users when they enter an incorrect password.
>>>>>>> Defaults !insults
>>>>>>>
>>>>>>>
>>>>>>> And openSUSE years ago changed the default configuration file to not
>>>>>>> insult, but the software default was to insult.
>>>>>>
>>>>>> Just out of curiosity, what was the insult?  What does it say?
>>>>>
>>>>> I don't remember. That we would be reported to the administrator.
>>>>
>>>> HOw is that an insult? It is (presumably/hopefully) a statement of fact.
>>>
>>> Nononono. The gist of what it said was that, but the wording was with
>>> insults. And no, I don't remember them, I disabled them long ago - after
>>
>> Ah, OK. I agree that there is no need for that kind of behaviour.
>>
>>
>>> all I'm the administrator and what I do as user I want to give myself
>>> permission to do. I don't need to be insulted by software in my own
>>> computer.
>>>
>>> Example:
>>>
>>> sudo apk-get update
>>> [sudo] password for saket:
>>> Are you on drugs?
>> I assume that that is an example you made up rather than an actual
>> quote.
>> but yes, there is no need for that.
>
> An actual quote, hand typed by me from a photo in one of the links I
> posted. I omitted the shell prompts for brevity.
>
>
>
>> Note that I have never seen this behaviour and the word "insult" does
>> not occur in my /etc/sudoers file (and I do not have a sudo.conf file)
>> so I seem to have been spared (Mageia 6)
>> .
>
> Maybe your distro maintainer disabled it in the source.
>
Another good reason to use Mageia.

>

--- SoupGate-Win32 v1.05
 * Origin: SpaceSST BBS Usenet <mccarragher.org> Fidonet Gateway (255:255/999)
  Show ANSI Codes | Hide BBCodes | Show Color Codes | Hide Encoding | Hide HTML Tags | Show Routing
Previous Message | Next Message | Back to Linux operating system (OS), a U...  <--  <--- Return to Home Page

VADV-PHP
Execution Time: 0.0966 seconds

If you experience any problems with this website or need help, contact the webmaster.
VADV-PHP Copyright © 2002-2024 Steve Winn, Aspect Technologies. All Rights Reserved.
Virtual Advanced Copyright © 1995-1997 Roland De Graaf.
v2.0.140505

Warning: Unknown: open(c:\Sessions\sess_lnh0kf2f8efcd522vtsiigmd72, O_RDWR) failed: No such file or directory (2) in Unknown on line 0 Warning: Unknown: Failed to write session data (files). Please verify that the current setting of session.save_path is correct (c:\Sessions) in Unknown on line 0 PHP Warning: session_start(): open(c:\Sessions\sess_lnh0kf2f8efcd522vtsiigmd72, O_RDWR) failed: No such file or directory (2) in D:\wc5\http\public\VADV\include\common.inc.php on line 45 PHP Warning: Unknown: open(c:\Sessions\sess_lnh0kf2f8efcd522vtsiigmd72, O_RDWR) failed: No such file or directory (2) in Unknown on line 0 PHP Warning: Unknown: Failed to write session data (files). Please verify that the current setting of session.save_path is correct (c:\Sessions) in Unknown on line 0