home
faq
how to
sitemap
contact
 

A short list of linux installation hints
volume 2

 
Fedora xfce  

September 18, 2017

 
   

Listed here, for convenience, are a few linux installation hints. Most of these hints apply to Fedora 24, with Xfce.

  purple seperator  

 

To change the machine's name, edit the file:

              /etc/hostname

  purple seperator  

 

To list the current network settings:

              > ifconfig

  purple seperator  

 

              > yum update

... is now:

              > dnf update

  purple seperator  

 

The screen's resolution may be stuck on 1024x768 or worse 640x480.
The resolution we want is 1920x1080.

The problem is undetected resolutions. Directions for how to fix this were found here:

              Adding undetected resolutions

Start with getting what the video is connected to:

              > xrandr

results can be:

              ...
              VGA-1 connected 1024x768+0+0
              ...

Therefore, the current output is device is: VGA-1

Use the cvt command to get the output of the Modeline.

              > cvt 1920 1080

output:

# 1920x1080 59.96 Hz (CVT 2.07M9) hsync: 67.16 kHz; pclk: 173.00 MHz
Modeline "1920x1080_60.00" 173.00 1920 2048 2248 2576 1080 1083 1088 1120 -hsync +vsync

then create a new xrandr mode:

> xrandr --newmode "1920x1080_60.00" 173.00 1920 2048 2248 2576 1080 1083 1088 1120 -hsync +vsync

             (get some errors from the above)
             (get no errors from the above when issued after a fresh reboot)

There isn't a change in resolution from the above,
to add the new mode to the current video output VGA-1:

> xrandr --addmode 1920x1080_60.00

now to change to the new mode:

> xrandr --output 1920x1080_60.00

Rebooting will remove these settings, so make it permanent:

add an entry into /etc/X11/xorg.conf.d/

...create and edit: /etc/X11/xorg.conf.d/10-monitor.conf

...insert the following:

              Section "Monitor":  
                    Identifier "VGA-1"
                    Modeline "1920x1080_60.00"
                    Option "PreferredMode" "1920x1080_60.00"
              EndSection

save the file, then

              > reboot

  purple seperator  

 

Notes in getting samba to work within fedora 24:

... to install:

             > dnf install samba

An error appears while trying to install and run samba for the first time:

... error while loading shared libraries: libwbclient.so.0

             > [samba]# systemctl start smb.service

             > Job for smb.service failed because the control process exited with error code. See "systemctl status smb.service" and "journalctl -xe" for details.

Check the status of the samba service:

             > [samba]# systemctl status smb.service

output:

      smb.service - Samba SMB Daemon
      Loaded: loaded (/usr/lib/systemd/system/smb.service; enabled; vendor preset: disabled)
      Active: failed (Result: exit-code) since Wed 2017-08-30 03:41:25 CDT; 9s ago
      Process: 3087 ExecStart=/usr/sbin/smbd $SMBDOPTIONS (code=exited, status=127)
      Main PID: 3087 (code=exited, status=127)

      systemd[1]: Starting Samba SMB Daemon...
      smbd[3087]: /usr/sbin/smbd: error while loading shared libraries: libwbclient.so.0:
             cannot open shared object file: No such file or directory
      systemd[1]: smb.service: Main process exited, code=exited, status=127/n/a
      systemd[1]: Failed to start Samba SMB Daemon.
      systemd[1]: smb.service: Unit entered failed state.
      systemd[1]: smb.service: Failed with result 'exit-code'.

this fixes the lost library:

            > update-alternatives --install /usr/lib64/libwbclient.so.0 libwbclient.so.0-64 /usr/lib64/samba/wbclient/libwbclient.so.0 10

now when we run:

            > systemctl start smb.service

it returns with no errors.

            > systemctl start nmb.service

also returns without errors.

--------------

useful commands:

           > systemctl start smb.service
           > systemctl start nmb.service

           > systemctl start smb.service
           > systemctl start nmb.service

           > systemctl restart smb.service
           > systemctl restart nmb.service

           > systemctl status smb -l

to list out the samba users:

           > pdbedit -L -v

Can get error while running pdbedit -L -v:

         tdbsam_open: Failed to open/create TDB passwd [/var/lib/samba/private/passdb.tdb]
           tdbsam_getsampwnam: failed to open /var/lib/samba/private/passdb.tdb!
           User Search failed!

This means we need to be root to issue: pdbedit -L -v

---------------

After spending a few days going in circles, trying to get samba to allow connections between win7 and the linux machine, adding this line to samba's configuration file finally allowed the linux machine to access the win7 directories and files:

          client ntlmv2 auth = no

The problem that kept occurring:

         While trying to access files on a windows 7 machine from a linux machine via samba, nautilus,
         it'll keep asking for login credentials, sometimes even if there are no credentials.

First this was changed on the windows 7 machine:

          Control Panel --> Administrative Tools --> Local Security Policy

          --> Local Policies --> Security Options

          --> Network security: LAN Manager authentication level
          set to: Send LM & NTLM responses

          --> Network security: Minimum session security for NTLM SSP (client & server)
          set: Disable Require 128-bit encryption

To edit the samba configuration file:

           > kate /etc/samba/smb.conf &

Here is the final working smb.conf  file:
-------------------------------------------------------------
# See smb.conf.example for a more detailed config file or
# read the smb.conf manpage.
# Run 'testparm' to verify the config is correct after
# you modified it.

[global]
workgroup = workgroup
server string = Samba Server Version %v
security = user

interfaces = enp3s0 192.168.1.90/24
hosts allow = 127. 192.168.1.

; passdb backend = tdbsam

; printing = cups
printcap name = cups
; load printers = yes
cups options = raw
client use spnego = no
; encrypt passwords = yes
; guest ok = no
; guest account = nobody
map to guest = bad user

name resolve order = bcast hosts lmhosts wins
lanman auth = yes
client lanman auth = no
client ntlmv2 auth = no
client plaintext auth = yes

[homes]
comment = Home Directories
valid users = %S, %D%w%S
browseable = No
read only = No
inherit acls = Yes

[printers]
comment = All Printers
path = /var/tmp
printable = Yes
create mask = 0600
browseable = No

[username]
comment = username files
path = /home/username
write list = root
create mask = 0664
directory mask = 0775
; read only = yes
; browseable = yes
guest ok = yes

# security
security = user
username map = /etc/samba/smbusers
-----------------------------------------------------

Something causes the following line to be commented out:

client ntlmv2 auth = no

something adds a ";" at the beginning of the line. If that happens then the linux box can't connect to windows machines and vice versa. Removing the ";" uncomments the line and linux once again can connect to windows machines, and the windows machines can see the linux's files.

 

  purple seperator  

 

Workaround for setting the background images on the desktop.

The error: while trying to set the background image via:

          right-click >> Desktop Settings >> Background >> folder selection >> "other"

         doesn't allow it to change to a user's folder (the user's folder is greyed out)

         So, we need to be root, then copy the background images we wish to use to this directory:

         /usr/share/backgrounds/images

         Then they appear, and are selectable within the Desktop Settings.

  purple seperator  

 

dark maelstrom icon dark maelstrom
flash games
  t-shirt icon dark maelstrom
t-shirt designs

back

home