Ask Your Question

jadesword's profile - activity

2017-11-05 06:07:51 -0600 received badge  Famous Question (source)
2017-11-05 06:07:51 -0600 received badge  Notable Question (source)
2017-11-05 06:07:51 -0600 received badge  Popular Question (source)
2016-04-22 06:58:26 -0600 received badge  Nice Answer (source)
2016-04-22 06:58:25 -0600 received badge  Nice Question (source)
2016-03-21 09:03:00 -0600 received badge  Self-Learner (source)
2016-03-21 09:03:00 -0600 received badge  Teacher (source)
2016-03-21 09:02:50 -0600 received badge  Student (source)
2016-02-28 08:28:32 -0600 commented answer Fedora20 su login authentication failure

You are correct about the permissions. Without the correct password, no permission change would have worked. I was just poking around when I ran across the actual solution that worked and I do not need the default root password that was entered by the original programmer. I am learning.

2016-02-28 08:15:30 -0600 answered a question Fedora20 su login authentication failure

Found the answer at {http://askubuntu.com/questions/168101/why-cant-i-access-super-user-mode-with-su} and it worked.

$ sudo passwd -S root
root PS 1969-12-30 0 99999 7 -1 (Password set, SHA512 crypt.)
$ sudo passwd root
Changing password for user root.
New password:
Retype new password:
passwd: all authentication tokens updated successfully.
$ sudo passwd -S root
root PS 2016-02-27 0 99999 7 -1 (Password set, SHA512 crypt.)
$ su --login
Password:
Last failed login: Sun Feb 28 05:58:49 MST 2016 on pts/1
There were 5 failed login attempts since the last successful login.
#

The date of the original password is interesting as it seems that the su default password was set by the original programmer.

2016-02-28 07:34:11 -0600 commented answer Fedora20 su login authentication failure

What is the "root" password?

2016-02-28 07:09:13 -0600 commented answer Fedora20 su login authentication failure

As stated, I tried several passwords, the account password should have worked, but failed. Every other guess failed as well. Further research says that I should change the permissions using chmod, but I am not sure of the exact coding as there are no examples of the format in the documentation. One suggestion is [sudo chmod -v 7777 /bin/su", but I have yet to try it.

2016-02-28 06:19:30 -0600 asked a question Fedora20 su login authentication failure

No matter what password I use, the result is the same.

$ su --login
Password:
su: Authentication failure
$

Is there a default password or is there a command that is required to enable and set a password for su?

2016-02-28 05:54:09 -0600 commented question root password does not work when using "su" in the shell or installing software as a normal user

Makes sense if the user is already logged in as root, but to log in as root, you will be using the user's keyboard layout.

Das macht Sinn, wenn der Benutzer bereits als root angemeldet, aber als root anmelden, werden Sie die Benutzer-Tastaturlayout werden.

2016-02-28 05:35:12 -0600 commented answer Having a problem setting environment variables in Fedora23

I have a related problem in modifying the environmental variables in Fedora20. This makes the decision to upgrade less likely as it seems to be much more difficult to modify environmental variables in Fedora23. There should be a simple way to configure environmental variables. For example, a simple LC_TIME modification to allow the format Sun 2016-02-28 04:35:15 -07 seems to be almost impossible unless the user is a master system programmer. It should be something simple. For example, the way you would program the date and time format in LibreOffice.

2016-02-27 20:58:49 -0600 commented answer ISO8601 date and time format seems to be unavailable.

How can I find it so I can modify it?

2016-02-27 13:15:33 -0600 commented answer What password size do you recommend for user and root in Fedora?

What is the minimum and maximum number of characters allowed by Fedora for a password and what is allowed or disallowed? I presume abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ0123456789!@#$%^&*()_+-={}[]:;"'<>?/., as the keyboard characters should be allowed. What about special characters not usually found on a keyboard? Or foreign characters?

2016-02-27 12:58:15 -0600 commented answer ISO8601 date and time format seems to be unavailable.

Looks like I am going to create the missing en_US.utf-8, except the listing shows en_US.utf8.

$ localectl list-locales | grep en_US
en_US
en_US.iso88591
en_US.iso885915
en_US.utf8
$

The file I modified is /usr/share/i18n/locales/en_US and is the only en_US found using a global search that had LC_TIME in it.

I will try your suggestion later as I am really busy now and will be in a world of hurt if something goes wrong and I am unable to use the computer. I really appreciate your efforts on my behalf. I am learning more about computers now.

2016-02-26 19:36:12 -0600 commented answer ISO8601 date and time format seems to be unavailable.

Modified en_US, but was unable to select en_US using sudo localectl set-locale LC_TIME=en_US.
Was unable to find en_US.utf8, so was unable to modify en_US.utf8.
Was unable to find en_DK.utf8, so was unable to modify en_DK.utf8.
Reboot was performed before checking for differences.

2016-02-26 04:11:38 -0600 commented answer ISO8601 date and time format seems to be unavailable.

I even tried:
$ sudo localectl set-locale LC_TIME=en_US
[sudo] password for User:
$
locale
LANG=en_US.utf8
LC_CTYPE="en_US.utf8"
LC_NUMERIC=en_US.utf8
LC_TIME=en_US.utf8
LC_COLLATE="en_US.utf8"
LC_MONETARY=en_US.utf8
LC_MESSAGES="en_US.utf8"
LC_PAPER=en_US.utf8
LC_NAME="en_US.utf8"
.LC_ADDRESS="en_US.utf8"
LC_TELEPHONE="en_US.utf8"
LC_MEASUREMENT=en_US.utf8
LC_IDENTIFICATION="en_US.utf8"
LC_ALL=
$

2016-02-26 03:56:48 -0600 commented answer ISO8601 date and time format seems to be unavailable.

Tried and failed to use en_US as locale.

2016-02-26 03:54:40 -0600 received badge  Commentator
2016-02-26 03:54:40 -0600 commented question ISO8601 date and time format seems to be unavailable.

Must I continue to deal with unfamiliar date formats? Nothing I tried so far has worked.

2016-02-26 02:36:00 -0600 commented answer ISO8601 date and time format seems to be unavailable.

This is getting complex. I do not wish to implement a different locale. I want to modify the one that is being used now to control date and time formats. I need to find the file so the date format may be modified. I found en_US, but the modifications made did not change anything. Perhaps, if I used your code, but with en_US? I will try it.

Did not work. I detected no change anywhere.

2016-02-24 16:01:48 -0600 commented answer ISO8601 date and time format seems to be unavailable.

I tried Settings > Region & Language > Formats and previewed DK and found too many unacceptable differences. I was unable to find en_DK.utf8 or even en_US.utf8, but I did find en_US that has options for changing the time format. Unfortunately, it seems the calls for the format are not directed there. I need to find the script for the calls and change en_US.utf8 and change it to en_US so the calls are directed to where the formats reside.

I noticed that en_US uses ISO8601, so very little modification was required. I even entered comments that translate unicode into human readable format.

2016-02-23 22:22:22 -0600 commented answer ISO8601 date and time format seems to be unavailable.

$ localectl list-locales | grep en_DK
en_DK
en_DK.iso88591
en_DK.utf8
$

Did a search for the files {en_dk}:
/usr/share/hyphen/hyph_en_DK.dic
/usr/share/i18n/locales/en_DK

2016-02-23 14:59:37 -0600 commented answer ISO8601 date and time format seems to be unavailable.

en_DK.UTF-8 does not exist.

2016-02-22 05:14:07 -0600 commented question ISO8601 date and time format seems to be unavailable.

I am new to fedora. I want to implement the change everywhere date and time are displayed.

The following was found in All Settings/Details/Overview. Perhaps this will answer some of your questions. Looks like it needs a fixed width font to display properly.

         OS   Fedora 20
Device name   localhost.localdomain
     Memory   34.4 GiB
  Processor   AMD FX(tm)-8350 Eight-Core Processor x 8
    OS Type   64-bit
   Graphics   Gallium 0.4 on AMD PITCAIRN
      Gnome   Version 3.10.2
       Disk   2.0 TB

2016-02-22 04:38:23 -0600 commented answer ISO8601 date and time format seems to be unavailable.

Interesting command, but the problem is formatting the display of date and time everywhere. So far, the only place I can change the format is in the terminal and it is a one time modification of format that is not permanent and does not change the display anywhere else. This does not change the display format in terminal, as shown above. My preference is Sun 2016-02-21 17:33:29 -07, but unless I know what file(s) to modify, I will be unable to implement a permanent change of format anywhere.

2016-02-21 20:53:45 -0600 commented answer ISO8601 date and time format seems to be unavailable.

Using "man date", found something that seems to work in terminal, but nowhere else. I even tried to re-boot to see if it would change anything, but I saw no difference.

$ date +%a %F %T %:::z
Sun 2016-02-21 17:33:29 -07
$ date
Sun Feb 21 17:33:44 MST 2016
$

Would seem that I need to enter the format in a file somewhere.

Do I need to enter it in multiple files for every program that invokes date and time?

2016-02-21 12:20:22 -0600 commented question ISO8601 date and time format seems to be unavailable.

Would like all dates and times to be formatted ddd YYYY-MM-DD hh:mm:ss ±hh:mm Three character day of the week, four digit year, two digit month, two digit day, two digit hour (0-23), two digit minute, two digit second. The last time I entered this data, I included the reason, which may be why the comment was deleted.

2016-02-21 08:46:03 -0600 commented answer ISO8601 date and time format seems to be unavailable.

Seems that all of my answers were deleted. Need to know what file and where the file should be located to effect a change. Knowing what to enter does not help if there is no data as to where it is to be entered. I hope that this comment is not deleted so I may get a useful answer.

2016-02-20 16:15:13 -0600 received badge  Organizer (source)
2016-02-20 15:54:11 -0600 asked a question ISO8601 date and time format seems to be unavailable.

Is there a way to use the ISO8601 date and time format?

[+%a %F %T %:::z] {Sun 2016-02-21 17:33:29 -07} is my preferred format, but I have no idea where or how to make the required modifications so that this format will be universally and permanently displayed.