Mapping linux drive to windows 8.1 PC


Go to solution Solved by Draconian Guppy,

Recommended Posts

Draconian Guppy

Warning, extreme linux noob here

NP.. SAMBA shares are awesome ;) sudo apt-get install samba :p

 

I am in the early process of converting my Win ServR2 box over for Sickbeard.. 

 

 

Use the Samba GUI, and you'll see how easy it is.

 

 

You ever used network shares in Windows (e.g. "\\MyPC\shared videos")? Samba is the Linux port of that, and the two are mostly compatible. I think in Ubuntu, Samba is integrated into Nautilus. You can just right click -> properties on a folder and share it.

 

EDIT: https://www.liberiangeek.net/2011/11/a-quick-way-to-share-folders-in-ubuntu-11-10-oneiric-ocelot/. This is for Oneiric, but presumably it still applies in Trusty.

 

 

You don't have to manually install it like that. Just use your distro's package manager. Either 'sudo apt-get install samba', 'yaourt -S samba', or something similar. If you're adverse to the cli, most distros come with a GUI that does the equivalent.

 

 

So fed up with windows drivers (ati) I decided to give ubuntu 14.04 a go. So I created all the necessary partitions (and managed to keep my existing ntfs info! ) that process was pretty straight forward booting from USB. I use this PC mostly as an internal fileserver over lan.

 

 

I tried right clicking creating a new share, tried via terminal, tried editing the conf. I got 3 different results, none accessible, see below:

 

YWd54Kt.jpg

 

 

 

Here's my smb.conf, which I basically did not modify, just to add another folder at the end.

 

 

 

 
#
# Sample configuration file for the Samba suite for Debian GNU/Linux.
#
#
# This is the main Samba configuration file. You should read the
# smb.conf(5) manual page in order to understand the options listed
# here. Samba has a huge number of configurable options most of which 
# are not shown in this example
#
# Some options that are often worth tuning have been included as
# commented-out examples in this file.
#  - When such options are commented with ";", the proposed setting
#    differs from the default Samba behaviour
#  - When commented with "#", the proposed setting is the default
#    behaviour of Samba but the option is considered important
#    enough to be mentioned here
#
# NOTE: Whenever you modify this file you should run the command
# "testparm" to check that you have not made any basic syntactic 
# errors. 
 
#======================= Global Settings =======================
 
[global]
 
## Browsing/Identification ###
 
# Change this to the workgroup/NT-domain name your Samba server will part of
   workgroup = WORKGROUP
 
# server string is the equivalent of the NT Description field
server string = %h server (Samba, Ubuntu)
 
# Windows Internet Name Serving Support Section:
# WINS Support - Tells the NMBD component of Samba to enable its WINS Server
#   wins support = no
 
# WINS Server - Tells the NMBD components of Samba to be a WINS Client
# Note: Samba can be either a WINS Server, or a WINS Client, but NOT both
;   wins server = w.x.y.z
 
# This will prevent nmbd to search for NetBIOS names through DNS.
   dns proxy = no
 
#### Networking ####
 
# The specific set of interfaces / networks to bind to
# This can be either the interface name or an IP address/netmask;
# interface names are normally preferred
;   interfaces = 127.0.0.0/8 eth0
 
# Only bind to the named interfaces and/or networks; you must use the
# 'interfaces' option above to use this.
# It is recommended that you enable this feature if your Samba machine is
# not protected by a firewall or is a firewall itself.  However, this
# option cannot handle dynamic or non-broadcast interfaces correctly.
;   bind interfaces only = yes
 
 
 
#### Debugging/Accounting ####
 
# This tells Samba to use a separate log file for each machine
# that connects
   log file = /var/log/samba/log.%m
 
# Cap the size of the individual log files (in KiB).
   max log size = 1000
 
# If you want Samba to only log through syslog then set the following
# parameter to 'yes'.
#   syslog only = no
 
# We want Samba to log a minimum amount of information to syslog. Everything
# should go to /var/log/samba/log.{smbd,nmbd} instead. If you want to log
# through syslog you should set the following parameter to something higher.
   syslog = 0
 
# Do something sensible when Samba crashes: mail the admin a backtrace
   panic action = /usr/share/samba/panic-action %d
 
 
####### Authentication #######
 
# Server role. Defines in which mode Samba will operate. Possible
# values are "standalone server", "member server", "classic primary
# domain controller", "classic backup domain controller", "active
# directory domain controller". 
#
# Most people will want "standalone sever" or "member server".
# Running as "active directory domain controller" will require first
# running "samba-tool domain provision" to wipe databases and create a
# new domain.
   server role = standalone server
 
# If you are using encrypted passwords, Samba will need to know what
# password database type you are using.  
   passdb backend = tdbsam
 
   obey pam restrictions = yes
 
# This boolean parameter controls whether Samba attempts to sync the Unix
# password with the SMB password when the encrypted SMB password in the
# passdb is changed.
   unix password sync = yes
 
# For Unix password sync to work on a Debian GNU/Linux system, the following
# parameters must be set (thanks to Ian Kahan <<kahan@informatik.tu-muenchen.de> for
# sending the correct chat script for the passwd program in Debian Sarge).
   passwd program = /usr/bin/passwd %u
   passwd chat = *Enter\snew\s*\spassword:* %n\n *Retype\snew\s*\spassword:* %n\n *password\supdated\ssuccessfully* .
 
# This boolean controls whether PAM will be used for password changes
# when requested by an SMB client instead of the program listed in
# 'passwd program'. The default is 'no'.
   pam password change = yes
 
# This option controls how unsuccessful authentication attempts are mapped
# to anonymous connections
   map to guest = bad user
 
########## Domains ###########
 
#
# The following settings only takes effect if 'server role = primary
# classic domain controller', 'server role = backup domain controller'
# or 'domain logons' is set 
#
 
# It specifies the location of the user's
# profile directory from the client point of view) The following
# required a [profiles] share to be setup on the samba server (see
# below)
;   logon path = \\%N\profiles\%U
# Another common choice is storing the profile in the user's home directory
# (this is Samba's default)
#   logon path = \\%N\%U\profile
 
# The following setting only takes effect if 'domain logons' is set
# It specifies the location of a user's home directory (from the client
# point of view)
;   logon drive = H:
#   logon home = \\%N\%U
 
# The following setting only takes effect if 'domain logons' is set
# It specifies the script to run during logon. The script must be stored
# in the [netlogon] share
# NOTE: Must be store in 'DOS' file format convention
;   logon script = logon.cmd
 
# This allows Unix users to be created on the domain controller via the SAMR
# RPC pipe.  The example command creates a user account with a disabled Unix
# password; please adapt to your needs
; add user script = /usr/sbin/adduser --quiet --disabled-password --gecos "" %u
 
# This allows machine accounts to be created on the domain controller via the 
# SAMR RPC pipe.  
# The following assumes a "machines" group exists on the system
; add machine script  = /usr/sbin/useradd -g machines -c "%u machine account" -d /var/lib/samba -s /bin/false %u
 
# This allows Unix groups to be created on the domain controller via the SAMR
# RPC pipe.  
; add group script = /usr/sbin/addgroup --force-badname %g
 
############ Misc ############
 
# Using the following line enables you to customise your configuration
# on a per machine basis. The %m gets replaced with the netbios name
# of the machine that is connecting
;   include = /home/samba/etc/smb.conf.%m
 
# Some defaults for winbind (make sure you're not using the ranges
# for something else.)
;   idmap uid = 10000-20000
;   idmap gid = 10000-20000
;   template shell = /bin/bash
 
# Setup usershare options to enable non-root users to share folders
# with the net usershare command.
 
# Maximum number of usershare. 0 (default) means that usershare is disabled.
;   usershare max shares = 100
 
# Allow users who've been granted usershare privileges to create
# public shares, not just authenticated ones
   usershare allow guests = yes
 
#======================= Share Definitions =======================
 
# Un-comment the following (and tweak the other settings below to suit)
# to enable the default home directory shares. This will share each
# user's home directory as \\server\username
;[homes]
;   comment = Home Directories
;   browseable = no
 
# By default, the home directories are exported read-only. Change the
# next parameter to 'no' if you want to be able to write to them.
;   read only = yes
 
# File creation mask is set to 0700 for security reasons. If you want to
# create files with group=rw permissions, set next parameter to 0775.
;   create mask = 0700
 
# Directory creation mask is set to 0700 for security reasons. If you want to
# create dirs. with group=rw permissions, set next parameter to 0775.
;   directory mask = 0700
 
# By default, \\server\username shares can be connected to by anyone
# with access to the samba server.
# Un-comment the following parameter to make sure that only "username"
# can connect to \\server\username
# This might need tweaking when using external authentication schemes
;   valid users = %S
 
# Un-comment the following and create the netlogon directory for Domain Logons
# (you need to configure Samba to act as a domain controller too.)
;[netlogon]
;   comment = Network Logon Service
;   path = /home/samba/netlogon
;   guest ok = yes
;   read only = yes
 
# Un-comment the following and create the profiles directory to store
# users profiles (see the "logon path" option above)
# (you need to configure Samba to act as a domain controller too.)
# The path below should be writable by all users so that their
# profile directory may be created the first time they log on
;[profiles]
;   comment = Users profiles
;   path = /home/samba/profiles
;   guest ok = no
;   browseable = no
;   create mask = 0600
;   directory mask = 0700
 
[printers]
   comment = All Printers
   browseable = no
   path = /var/spool/samba
   printable = yes
   guest ok = no
   read only = yes
   create mask = 0700
 
# Windows clients look for this share name as a source of downloadable
# printer drivers
[print$]
   comment = Printer Drivers
   path = /var/lib/samba/printers
   browseable = yes
   read only = yes
   guest ok = no
# Uncomment to allow remote administration of Windows print drivers.
# You may need to replace 'lpadmin' with the name of the group your
# admin users are members of.
# Please note that you also need to set appropriate Unix permissions
# to the drivers directory for these users to have write rights in it
;   write list = root, @lpadmin
 
[Guppy]
path = /home/guppy/Desktop/guppy
available = yes
valid users = guppy
read only = no
browsable = yes
public = yes
writable = yes
 

 

Link to post
Share on other sites
Haggis

I have a guide i use in the house, i will find it when i get in and pop it to you

  • Like 1
Link to post
Share on other sites
Haggis

here is mine if it helps

#
# Sample configuration file for the Samba suite for Debian GNU/Linux.
#
#
# This is the main Samba configuration file. You should read the
# smb.conf(5) manual page in order to understand the options listed
# here. Samba has a huge number of configurable options most of which 
# are not shown in this example
#
# Some options that are often worth tuning have been included as
# commented-out examples in this file.
#  - When such options are commented with ";", the proposed setting
#    differs from the default Samba behaviour
#  - When commented with "#", the proposed setting is the default
#    behaviour of Samba but the option is considered important
#    enough to be mentioned here
#
# NOTE: Whenever you modify this file you should run the command
# "testparm" to check that you have not made any basic syntactic 
# errors. 
# A well-established practice is to name the original file
# "smb.conf.master" and create the "real" config file with
# testparm -s smb.conf.master >smb.conf
# This minimizes the size of the really used smb.conf file
# which, according to the Samba Team, impacts performance
# However, use this with caution if your smb.conf file contains nested
# "include" statements. See Debian bug #483187 for a case
# where using a master file is not a good idea.
#

#======================= Global Settings =======================

[global]

## Browsing/Identification ###

# Change this to the workgroup/NT-domain name your Samba server will part of
   workgroup = MSHOME

# server string is the equivalent of the NT Description field
   server string = %h server

# Windows Internet Name Serving Support Section:
# WINS Support - Tells the NMBD component of Samba to enable its WINS Server
#   wins support = no

# WINS Server - Tells the NMBD components of Samba to be a WINS Client
# Note: Samba can be either a WINS Server, or a WINS Client, but NOT both
;   wins server = w.x.y.z

# This will prevent nmbd to search for NetBIOS names through DNS.
   dns proxy = no

# What naming service and in what order should we use to resolve host names
# to IP addresses
;   name resolve order = lmhosts host wins bcast

#### Networking ####

# The specific set of interfaces / networks to bind to
# This can be either the interface name or an IP address/netmask;
# interface names are normally preferred
;   interfaces = 127.0.0.0/8 eth0

# Only bind to the named interfaces and/or networks; you must use the
# 'interfaces' option above to use this.
# It is recommended that you enable this feature if your Samba machine is
# not protected by a firewall or is a firewall itself.  However, this
# option cannot handle dynamic or non-broadcast interfaces correctly.
;   bind interfaces only = yes



#### Debugging/Accounting ####

# This tells Samba to use a separate log file for each machine
# that connects
   log file = /var/log/samba/log.%m

# Cap the size of the individual log files (in KiB).
   max log size = 1000

# If you want Samba to only log through syslog then set the following
# parameter to 'yes'.
#   syslog only = no

# We want Samba to log a minimum amount of information to syslog. Everything
# should go to /var/log/samba/log.{smbd,nmbd} instead. If you want to log
# through syslog you should set the following parameter to something higher.
   syslog = 0

# Do something sensible when Samba crashes: mail the admin a backtrace
   panic action = /usr/share/samba/panic-action %d


####### Authentication #######

# "security = user" is always a good idea. This will require a Unix account
# in this server for every user accessing the server. See
# /usr/share/doc/samba-doc/htmldocs/Samba3-HOWTO/ServerType.html
# in the samba-doc package for details.
#   security = user

# You may wish to use password encryption.  See the section on
# 'encrypt passwords' in the smb.conf(5) manpage before enabling.
   encrypt passwords = true

# If you are using encrypted passwords, Samba will need to know what
# password database type you are using.  
   passdb backend = tdbsam

   obey pam restrictions = yes

# This boolean parameter controls whether Samba attempts to sync the Unix
# password with the SMB password when the encrypted SMB password in the
# passdb is changed.
   unix password sync = yes

# For Unix password sync to work on a Debian GNU/Linux system, the following
# parameters must be set (thanks to Ian Kahan <<kahan@informatik.tu-muenchen.de> for
# sending the correct chat script for the passwd program in Debian Sarge).
   passwd program = /usr/bin/passwd %u
   passwd chat = *Enter\snew\s*\spassword:* %n\n *Retype\snew\s*\spassword:* %n\n *password\supdated\ssuccessfully* .

# This boolean controls whether PAM will be used for password changes
# when requested by an SMB client instead of the program listed in
# 'passwd program'. The default is 'no'.
   pam password change = yes

# This option controls how unsuccessful authentication attempts are mapped
# to anonymous connections
   map to guest = bad user

########## Domains ###########

# Is this machine able to authenticate users. Both PDC and BDC
# must have this setting enabled. If you are the BDC you must
# change the 'domain master' setting to no
#
;   domain logons = yes
#
# The following setting only takes effect if 'domain logons' is set
# It specifies the location of the user's profile directory
# from the client point of view)
# The following required a [profiles] share to be setup on the
# samba server (see below)
;   logon path = \\%N\profiles\%U
# Another common choice is storing the profile in the user's home directory
# (this is Samba's default)
#   logon path = \\%N\%U\profile

# The following setting only takes effect if 'domain logons' is set
# It specifies the location of a user's home directory (from the client
# point of view)
;   logon drive = H:
#   logon home = \\%N\%U

# The following setting only takes effect if 'domain logons' is set
# It specifies the script to run during logon. The script must be stored
# in the [netlogon] share
# NOTE: Must be store in 'DOS' file format convention
;   logon script = logon.cmd

# This allows Unix users to be created on the domain controller via the SAMR
# RPC pipe.  The example command creates a user account with a disabled Unix
# password; please adapt to your needs
; add user script = /usr/sbin/adduser --quiet --disabled-password --gecos "" %u

# This allows machine accounts to be created on the domain controller via the 
# SAMR RPC pipe.  
# The following assumes a "machines" group exists on the system
; add machine script  = /usr/sbin/useradd -g machines -c "%u machine account" -d /var/lib/samba -s /bin/false %u

# This allows Unix groups to be created on the domain controller via the SAMR
# RPC pipe.  
; add group script = /usr/sbin/addgroup --force-badname %g

########## Printing ##########

# If you want to automatically load your printer list rather
# than setting them up individually then you'll need this
#   load printers = yes

# lpr(ng) printing. You may wish to override the location of the
# printcap file
;   printing = bsd
;   printcap name = /etc/printcap

# CUPS printing.  See also the cupsaddsmb(8) manpage in the
# cupsys-client package.
;   printing = cups
;   printcap name = cups

############ Misc ############

# Using the following line enables you to customise your configuration
# on a per machine basis. The %m gets replaced with the netbios name
# of the machine that is connecting
;   include = /home/samba/etc/smb.conf.%m

# Most people will find that this option gives better performance.
# See smb.conf(5) and /usr/share/doc/samba-doc/htmldocs/Samba3-HOWTO/speed.html
# for details
# You may want to add the following on a Linux system:
#         SO_RCVBUF=8192 SO_SNDBUF=8192
#   socket options = TCP_NODELAY

# The following parameter is useful only if you have the linpopup package
# installed. The samba maintainer and the linpopup maintainer are
# working to ease installation and configuration of linpopup and samba.
;   message command = /bin/sh -c '/usr/bin/linpopup "%f" "%m" %s; rm %s' &

# Domain Master specifies Samba to be the Domain Master Browser. If this
# machine will be configured as a BDC (a secondary logon server), you
# must set this to 'no'; otherwise, the default behavior is recommended.
#   domain master = auto

# Some defaults for winbind (make sure you're not using the ranges
# for something else.)
;   idmap uid = 10000-20000
;   idmap gid = 10000-20000
;   template shell = /bin/bash

# The following was the default behaviour in sarge,
# but samba upstream reverted the default because it might induce
# performance issues in large organizations.
# See Debian bug #368251 for some of the consequences of *not*
# having this setting and smb.conf(5) for details.
;   winbind enum groups = yes
;   winbind enum users = yes

# Setup usershare options to enable non-root users to share folders
# with the net usershare command.

# Maximum number of usershare. 0 (default) means that usershare is disabled.
;   usershare max shares = 100

# Allow users who've been granted usershare privileges to create
# public shares, not just authenticated ones
   usershare allow guests = yes

#======================= Share Definitions =======================

[homes]
   comment = Home Directories
   browseable = no

# By default, the home directories are exported read-only. Change the
# next parameter to 'no' if you want to be able to write to them.
   read only = no

# File creation mask is set to 0700 for security reasons. If you want to
# create files with group=rw permissions, set next parameter to 0775.
   create mask = 0775

# Directory creation mask is set to 0700 for security reasons. If you want to
# create dirs. with group=rw permissions, set next parameter to 0775.
   directory mask = 0775

# By default, \\server\username shares can be connected to by anyone
# with access to the samba server.
# The following parameter makes sure that only "username" can connect
# to \\server\username
# This might need tweaking when using external authentication schemes
   valid users = %S

# Un-comment the following and create the netlogon directory for Domain Logons
# (you need to configure Samba to act as a domain controller too.)
;[netlogon]
;   comment = Network Logon Service
;   path = /home/samba/netlogon
;   guest ok = yes
;   read only = yes

# Un-comment the following and create the profiles directory to store
# users profiles (see the "logon path" option above)
# (you need to configure Samba to act as a domain controller too.)
# The path below should be writable by all users so that their
# profile directory may be created the first time they log on
;[profiles]
;   comment = Users profiles
;   path = /home/samba/profiles
;   guest ok = no
;   browseable = no
;   create mask = 0600
;   directory mask = 0700

[printers]
   comment = All Printers
   browseable = no
   path = /var/spool/samba
   printable = yes
   guest ok = no
   read only = yes
   create mask = 0700

# Windows clients look for this share name as a source of downloadable
# printer drivers
[print$]
   comment = Printer Drivers
   path = /var/lib/samba/printers
   browseable = yes
   read only = yes
   guest ok = no
# Uncomment to allow remote administration of Windows print drivers.
# You may need to replace 'lpadmin' with the name of the group your
# admin users are members of.
# Please note that you also need to set appropriate Unix permissions
# to the drivers directory for these users to have write rights in it
;   write list = root, @lpadmin

# A sample share for sharing your CD-ROM with others.
;[cdrom]
;   comment = Samba server's CD-ROM
;   read only = yes
;   locking = no
;   path = /cdrom
;   guest ok = yes

[TV-Shows]
   comment = Some useful files
   read only = no
   locking = no
   path = /home/tv-shows
   guest ok = no

[Movies]
   comment = Some useful files
   read only = no
   locking = no
   path = /home/media
   guest ok = no
# The next two parameters show how to auto-mount a CD-ROM when the
#	cdrom share is accesed. For this to work /etc/fstab must contain
#	an entry like this:
#
#       /dev/scd0   /cdrom  iso9660 defaults,noauto,ro,user   0 0
#
# The CD-ROM gets unmounted automatically after the connection to the
#
# If you don't want to use auto-mounting/unmounting make sure the CD
#	is mounted on /cdrom
#
;   preexec = /bin/mount /cdrom
;   postexec = /bin/umount /cdrom

  • Like 1
Link to post
Share on other sites
Draconian Guppy

thanks, Ill check as soon as  I get home.

Link to post
Share on other sites
Draconian Guppy

fixed using this:

 

If you?re unable to access the shares, go back to your Ubuntu machine and run the commands below:

sudo smbpasswd -a USERNAME

quick_share_oneiric_6_thumb.png

Replace USERNAME with your account name.

 

Now try again to access the shares from your Windows machine

 

To find your computer name in Ubuntu run the command below:

hostname

 

Enjoy!

 

 

Can't add tech points to myself eh?

Link to post
Share on other sites
Draconian Guppy

Cool thanks! 

  • Like 1
Link to post
Share on other sites
This topic is now closed to further replies.
  • Recently Browsing   0 members

    No registered users viewing this page.

  • Similar Content

    • By anmol112
      Windows 11 may get support for third-party widgets after all
      by Anmol Mehrotra



      Earlier this week, a Windows 11 build leaked online giving us the first look at the upcoming OS update. While, the new update comes with a visual overhaul, it also brings back a long lost feature. Tucked between the File Explorer and Task View sits the widgets option. If you have used Windows 7 in the past then you must be familiar with the widgets option. Unfortunately, the widgets option in the leaked Windows 11 build is just News and Interests which was launched for Windows 10 earlier this year.

      However, reliable Microsoft insider, Walking Cat claims that Microsoft is planning to add support for third-party widgets that will allow users to customize the widgets menu as per their liking. However, initially, Windows 11 will support only first-party widgets, with third-party support rolling out later.

      This is further confirmed by Rafael Rivera who did not find APIs related to third-party widgets in the leaked build indicating that the initial Windows 11 update will not ship with support for the third-party widgets.

      Microsoft is expected to announce Windows 11 at an event next week. However, thanks to the recent leak, we were able to take a look at Windows 11 this week. You can check out our first impressions as well as hands-on articles for more information on Windows 11. In essence, the new update merges Windows 10 and Windows 10x while also bringing performance improvements as well as features such as the new window snapping assist.

    • By zikalify
      Canonical announces end of life date for Ubuntu 20.10 Groovy Gorilla
      by Paul Hill



      Canonical has announced that Ubuntu 20.10 Groovy Gorilla is set to lose support on July 22, 2021. As the release was one of those between the Long-Term Support (LTS) releases, it only has nine months of life. Those running this particular version of Ubuntu are urged to upgrade their systems to Ubuntu 21.04 Hirsute Hippo which has been available since April.

      To assist you in upgrading your computer, Canonical has published a guide that runs through everything you need to know and do to get to the latest version. If you’re not sure which version of Ubuntu you have, open Settings, scroll down the left-hand pane until you reach About, and then look under OS Name and you should be able to see which version you are on. Most people checking should find that they’re on Ubuntu 20.04.2 LTS, which is supported until 2025.

      After July 22, systems with Ubuntu 20.10 can still be used but they won’t receive important security updates. Quickly, you’ll notice your web browser become outdated which will only increase your risk. If you have a particular use for Ubuntu 20.10 which is preventing you from upgrading, disconnecting your computer from the internet and keeping it offline is another option you have for staying safe

      For most people, the Long-Term Support versions of Ubuntu are best because upgrades are only needed every couple of years. The interim releases, while stable, act more like a testing ground for new features between LTS releases.

    • By zikalify
      Linux Mint 20.2 beta ISOs are now ready for download
      by Paul Hill



      Earlier this week, Neowin reported that the Linux Mint 20.2 beta ISOs were undergoing final testing before being made available. Today, you can now download Linux Mint 20.2 beta from a choice of the Cinnamon, MATE, or Xfce editions.

      One of the main updates in Linux Mint 20.2 is to the Update Manager and the way it handles and alerts users to updates. On Linux Mint systems, all of the installed software, including apps, are updated centrally in the Update Manager. To bring more centralisation to the system, Cinnamon spices (add-ons in Cinnamon) are now visible in the Update Manager whenever there’s an update for them.

      Another issue with the Update Manager is that, by default, the user needs to apply updates manually but not everybody does. To remedy this, infrequent notifications will be displayed to users to let them know that there are available updates. The people that see these notifications will likely not be the type of people who keep their system up to date so they are offered the option to enable automatic updates so they’re never bothered by them again. Doing things this way gives users a choice over whether updates should be forced on users.

      There are a few new app additions in this update. The first is a new XApp called Buiky which allows you to bulk rename files on your system. Bulky is not included in the Xfce edition because the Thunar file manager already has this feature baked in. The other new app is Sticky Notes which replaces GNote as the default app for taking notes. Sticky Notes is built using GTK3, supports HiDPI, and integrates well with the desktop environment so it should be nice to use.

      Included in the release notes is also a mention of an unofficial Warpinator app for Android. Warpinator is a tool that Linux Mint developed a little while ago that allows you to send files between Linux Mint machines on your local network. With the Warpinator Android app, you’ll be able to easily send files to and from your mobile devices.

      Finally, the Cinnamon edition ships with Cinnamon 5.0 which includes a new content search feature. It also comes with fixes for several memory leaks which should improve its performance. A slightly unusual change coming with Cinnamon 5.0 is the ability to limit the total amount of RAM Cinnamon can use. If the limit is reached, Cinnamon will restart itself but you won’t lose your session or windows. When the limit is reached, Cinnamon becomes unresponsive for a second while performing an internal reboot.

      In the Linux Mint world, beta testing usually runs for a couple of weeks before the stable release is made available. Upgrading from Linux Mint 20 and 21 will be made available a little bit after the stable release is made available. The upgrade should be available via the Update Manager and should be painless.

    • By Abhay V
      Microsoft's second event for June 24 is aimed at Windows developers
      by Abhay Venkatesh



      Microsoft is slated to hold a “What’s next for Windows” event at 11 AM ET on June 24 to unveil Windows 11, a name that has recently been confirmed thanks to the leaked build that made it to the web. However, it turns out that the Windows 11 event might not be the only one to be taking place next Thursday, as the Redmond firm is holding an event for 3 PM ET, which it announced via Twitter today.

      As is the case with these event invites, not much in the way of information is being provided. However, the company is rumored to be working on a brand new Microsoft Store with new policies that expand the types of apps that can be distributed through the store. It is possible that that announcement, along with more information on the specifics for developers, will be provided during the event.

      During the firm’s Build conference last month, CEO Satya Nadella said that the company will “create more opportunities for every Windows developer” and that it will “welcome every creator who is looking for the most innovative, new, open platform to build[,] distribute[,] and monetize applications”. It is possible that the developer-focused event dives into new app development and monetization capabilities brought by the revamped Microsoft Store policies. It is anybody’s guess if there are any surprise announcements.

      The developer event is scheduled for 3 PM ET on June 24, four hours after the live stream for the Windows 11 event begins. The firm will stream the developer event on YouTube here.

    • By hellowalkman
      Intel's Speed Select Technology ironically hurting performance, but a fix is coming
      by Sayan Sen

      Intel's Speed Select Technology (SST) is a power management solution from the company that allows users to manage core prioritization and frequency regulation depending on the workloads in order to improve performance and efficiency.

      However, as an Intel engineer has observed, there is performance regression by more than 10% in benchmarks with the mode enabled. And while it isn't stated, the impact in a real workload might be lower but it's still a cause for concern.

      The engineer further explains that the standard Linux PCI interface which is used here is causing the delay as it searches through hundreds of PCI devices, during mapping, that are attached to the system. For those wondering why the need to mention hundreds of devices here, that's because Intel SST is a complex solution and is only available in Xeons and not in the mainstream Core lineup.

      Since the root cause of the problem has been identified, the good news is that a patch that promises to fix this should be available soon via a future firmware if it isn't already out. The fix is a fairly simple one and will use the cached data that will speed up the search process.

      Here's what the full LKML message says:

      Intel launched SST back in 2019 inside Cascade Lake Xeon CPUs. The technology is quite versatile as it enables several options like setting core prioritization, base clock tweaking, and more. As stated above, SST is implemented in the firmware and carried out by the processor's Power Control Unit (PCU). For more information on SST, visit Intel's official site here.