Page 1 of 1
Porteus as a Server
Posted: 19 Dec 2015, 01:25
by Jack
I have a Server and I want to use Porteus as the software run it as the Server. What packages will I need to add to Porteus to do it or are they all ready there? I would like to remove the desktop if I need to. Any idea to help me to do it?
Re: Porteus as a Server
Posted: 19 Dec 2015, 15:07
by Jack
I want to share files, so I guest file server.
Re: Porteus as a Server
Posted: 19 Dec 2015, 15:28
by Blaze
Jack, ok - no problem. Look at this topic
Установка и настройка Samba - общий доступ к сетевым дискам
I think you understand Russian language
Re: Porteus as a Server
Posted: 20 Dec 2015, 03:30
by Jack
It might help if it was in English. I will look at it better later.
Re: Porteus as a Server
Posted: 21 Dec 2015, 05:37
by Jack
Can you write it in English cause I don't read or understand Russian language.
Re: Porteus as a Server
Posted: 21 Dec 2015, 06:14
by Ed_P
Jack wrote:I don't read or understand Russian language.
Google can.
https://translate.google.com/translate? ... 26t%3D5327
Re: Porteus as a Server
Posted: 21 Dec 2015, 17:24
by Blaze
Jack, it's simple.
1. you are need to download and install modules
Code: Select all
usm -u all
usm -g gnutls
usm -g samba
2. tweak /etc/samba/smb.conf
3. run the commands
Code: Select all
smbpasswd -a root
smbpasswd -e root
chmod +x /etc/rc.d/rc.samba
4. start samba server via command
5. find ip samba server via command
ifconfig and use this ip on another local machine.
Login is
root
Password is
toor
Re: Porteus as a Server
Posted: 21 Dec 2015, 17:41
by Jack
Blaze, Thank you very much. I will try it out and get back if I need help or if it works.
Jack
Re: Porteus as a Server
Posted: 22 Dec 2015, 05:11
by Jack
Blaze or anyone, I'm trying on my 32bit laptop first.
1. you are need to download and install modules
In my Porteus 3.1 Mate I all ready have "gnutls-3.1.16-i486-1 and samba-4.1.0-i486-2" so I didn't need to install them.
2. tweak /etc/samba/smb.conf
And here is mine "/etc/samba/smb.conf" what line would I need to tweak? For what lines need to be tweak just change the color on that line so I would know to fix or change it.
Code: Select all
# 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 (perhaps too
# many!) most of which are not shown in this example
#
# For a step to step guide on installing, configuring and using samba,
# read the Samba-HOWTO-Collection. This may be obtained from:
# http://www.samba.org/samba/docs/Samba-HOWTO-Collection.pdf
#
# Many working examples of smb.conf files can be found in the
# Samba-Guide which is generated daily and can be downloaded from:
# http://www.samba.org/samba/docs/Samba-Guide.pdf
#
# Any line which starts with a ; (semi-colon) or a # (hash)
# is a comment and is ignored. In this example we will use a #
# for commentry and a ; for parts of the config file that you
# may wish to enable
#
# 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]
# workgroup = NT-Domain-Name or Workgroup-Name, eg: LINUX2
workgroup = WORKGROUP
# server string is the equivalent of the NT Description field
server string = Samba Server
# Security mode. Defines in which mode Samba will operate. Possible
# values are share, user, server, domain and ads. Most people will want
# user level security. See the Samba-HOWTO-Collection for details.
security = share
# Added by Brokenman for Porteus
usershare path = /home/guest/Shared
usershare max shares = 5
usershare allow guests = yes
usershare owner only = yes
# This option is important for security. It allows you to restrict
# connections to machines which are on your local network. The
# following example restricts access to two C class networks and
# the "loopback" interface. For more examples of the syntax see
# the smb.conf man page
; hosts allow = 192.168.1. 192.168.2. 127.
# If you want to automatically load your printer list rather
# than setting them up individually then you'll need this
load printers = yes
# you may wish to override the location of the printcap file
; printcap name = /etc/printcap
# on SystemV system setting printcap name to lpstat should allow
# you to automatically obtain a printer list from the SystemV spool
# system
; printcap name = lpstat
# It should not be necessary to specify the print system type unless
# it is non-standard. Currently supported print systems include:
# bsd, cups, sysv, plp, lprng, aix, hpux, qnx
; printing = cups
# Uncomment this if you want a guest account, you must add this to /etc/passwd
# otherwise the user "nobody" is used
; guest account = pcguest
# this tells Samba to use a separate log file for each machine
# that connects
log file = /var/log/samba.%m
# Put a capping on the size of the log files (in Kb).
max log size = 50
# Use password server option only with security = server
# The argument list may include:
# password server = My_PDC_Name [My_BDC_Name] [My_Next_BDC_Name]
# or to auto-locate the domain controller/s
# password server = *
; password server = <NT-Server-Name>
# Use the realm option only with security = ads
# Specifies the Active Directory realm the host is part of
; realm = MY_REALM
# Backend to store user information in. New installations should
# use either tdbsam or ldapsam. smbpasswd is available for backwards
# compatibility. tdbsam requires no further configuration.
; passdb backend = tdbsam
# 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.
# Note: Consider carefully the location in the configuration file of
# this line. The included file is read at that point.
; include = /usr/local/samba/lib/smb.conf.%m
# Configure Samba to use multiple interfaces
# If you have multiple network interfaces then you must list them
# here. See the man page for details.
; interfaces = 192.168.12.2/24 192.168.13.2/24
# Browser Control Options:
# set local master to no if you don't want Samba to become a master
# browser on your network. Otherwise the normal election rules apply
; local master = no
# OS Level determines the precedence of this server in master browser
# elections. The default value should be reasonable
; os level = 33
# Domain Master specifies Samba to be the Domain Master Browser. This
# allows Samba to collate browse lists between subnets. Don't use this
# if you already have a Windows NT domain controller doing this job
; domain master = yes
# Preferred Master causes Samba to force a local browser election on startup
# and gives it a slightly higher chance of winning the election
; preferred master = yes
# Enable this if you want Samba to be a domain logon server for
# Windows95 workstations.
; domain logons = yes
# if you enable domain logons then you may want a per-machine or
# per user logon script
# run a specific logon batch file per workstation (machine)
; logon script = %m.bat
# run a specific logon batch file per username
; logon script = %U.bat
# Where to store roving profiles (only for Win95 and WinNT)
# %L substitutes for this servers netbios name, %U is username
# You must uncomment the [Profiles] share below
; logon path = \\%L\Profiles\%U
# Windows Internet Name Serving Support Section:
# WINS Support - Tells the NMBD component of Samba to enable it's WINS Server
; wins support = yes
# 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
# WINS Proxy - Tells Samba to answer name resolution queries on
# behalf of a non WINS capable client, for this to work there must be
# at least one WINS Server on the network. The default is NO.
; wins proxy = yes
# DNS Proxy - tells Samba whether or not to try to resolve NetBIOS names
# via DNS nslookups. The default is NO.
dns proxy = no
# These scripts are used on a domain controller or stand-alone
# machine to add or delete corresponding unix accounts
; add user script = /usr/sbin/useradd %u
; add group script = /usr/sbin/groupadd %g
; add machine script = /usr/sbin/adduser -n -g machines -c Machine -d /dev/null -s /bin/false %u
; delete user script = /usr/sbin/userdel %u
; delete user from group script = /usr/sbin/deluser %u %g
; delete group script = /usr/sbin/groupdel %g
#============================ Share Definitions ==============================
[homes]
comment = Home Directories
browseable = no
writable = yes
# Un-comment the following and create the netlogon directory for Domain Logons
; [netlogon]
; comment = Network Logon Service
; path = /usr/local/samba/lib/netlogon
; guest ok = yes
; writable = no
; share modes = no
# Un-comment the following to provide a specific roving profile share
# the default is to use the user's home directory
;[Profiles]
; path = /usr/local/samba/profiles
; browseable = no
; guest ok = yes
# NOTE: If you have a BSD-style print system there is no need to
# specifically define each individual printer
[printers]
comment = All Printers
path = /var/spool/samba
browseable = no
# Set public = yes to allow user 'guest account' to print
guest ok = no
writable = no
printable = yes
# This one is useful for people to share files
;[tmp]
; comment = Temporary file space
; path = /tmp
; read only = no
; public = yes
# A publicly accessible directory, but read only, except for people in
# the "staff" group
;[public]
; comment = Public Stuff
; path = /home/samba
; public = yes
; writable = no
; printable = no
; write list = @staff
# Other examples.
#
# A private printer, usable only by fred. Spool data will be placed in fred's
# home directory. Note that fred must have write access to the spool directory,
# wherever it is.
;[fredsprn]
; comment = Fred's Printer
; valid users = fred
; path = /homes/fred
; printer = freds_printer
; public = no
; writable = no
; printable = yes
# A private directory, usable only by fred. Note that fred requires write
# access to the directory.
;[fredsdir]
; comment = Fred's Service
; path = /usr/somewhere/private
; valid users = fred
; public = no
; writable = yes
; printable = no
# a service which has a different directory for each machine that connects
# this allows you to tailor configurations to incoming machines. You could
# also use the %U option to tailor it by user name.
# The %m gets replaced with the machine name that is connecting.
;[pchome]
; comment = PC Directories
; path = /usr/pc/%m
; public = no
; writable = yes
# A publicly accessible directory, read/write to all users. Note that all files
# created in the directory by users will be owned by the default user, so
# any user with access can delete any other user's files. Obviously this
# directory must be writable by the default user. Another user could of course
# be specified, in which case all files would be owned by that user instead.
;[public]
; path = /usr/somewhere/else/public
; public = yes
; only guest = yes
; writable = yes
; printable = no
# The following two entries demonstrate how to share a directory so that two
# users can place files there that will be owned by the specific users. In this
# setup, the directory should be writable by both users and should have the
# sticky bit set on it to prevent abuse. Obviously this could be extended to
# as many users as required.
;[myshare]
; comment = Mary's and Fred's stuff
; path = /usr/somewhere/shared
; valid users = mary fred
; public = no
; writable = yes
; printable = no
; create mask = 0765
3. run the commands
Just type as shown below?
Code: Select all
smbpasswd -a root
smbpasswd -e root
chmod +x /etc/rc.d/rc.samba
4. start samba server via command
Can I just type this "chmod 755 /etc/rc.d/rc.samba" to do it?
5. find ip samba server via command ifconfig and use this ip on another local machine.
What line to look at?
Code: Select all
root@porteus:/home/guest# ifconfig
eth0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
ether 00:1f:16:54:19:88 txqueuelen 1000 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
inet 127.0.0.1 netmask 255.0.0.0
inet6 ::1 prefixlen 128 scopeid 0x10<host>
loop txqueuelen 0 (Local Loopback)
RX packets 48 bytes 2400 (2.3 KiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 48 bytes 2400 (2.3 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
wlan0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.0.4 netmask 255.255.255.0 broadcast 192.168.0.255
inet6 fe80::223:4eff:fe1b:a8bf prefixlen 64 scopeid 0x20<link>
inet6 2607:fcc8:e7c1:9c00:223:4eff:fe1b:a8bf prefixlen 64 scopeid 0x0<global>
ether 00:23:4e:1b:a8:bf txqueuelen 1000 (Ethernet)
RX packets 113128 bytes 130032628 (124.0 MiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 84859 bytes 11612939 (11.0 MiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
root@porteus:/home/guest#
And I guest I need to be sign in as root for it to work?
Login is root
Password is toor
Re: Porteus as a Server
Posted: 22 Dec 2015, 15:58
by Blaze
1. ok
2. about /etc/samba/smb.conf
find
Code: Select all
# workgroup = NT-Domain-Name or Workgroup-Name, eg: LINUX2
workgroup = MYGROUP
replace with
Code: Select all
# workgroup = NT-Domain-Name or Workgroup-Name, eg: LINUX2
workgroup = WORKGROUP
find
Code: Select all
[homes]
comment = Home Directories
browseable = no
writable = yes
replace with
Code: Select all
;[homes]
; comment = Home Directories
; browseable = no
; writable = yes
at the end of the file /etc/samba/smb.conf add these lines
Code: Select all
[porteus]
path = /mnt/sdb1
public = yes
guest ok = yes
writable = yes
printable = no
replace
path on
your path what you want to share.
replace
name of share
[porteus] on your name, for example
[myshare] and save changes.
3. yes. Remeber
Login is root
Password is toor
if it needs, type them.
4. about chmod 755 don't test it. I think - yes.
5. Your ip is
192.168.0.4
Remember this ip must be static, if it doesn't static - you are need to tweak DHP rules in your router.
For example, at my job
And I guest I need to be sign in as root for it to work?
I don't test guest account. I always use root user cheatcode to login.
Probably, you can test guest account. For guest login and password is
guest
Re: Porteus as a Server
Posted: 22 Dec 2015, 20:02
by Jack
Blaze,
2. In the "/etc/samba/smb.conf" I found these lines should I leave them as is?
Code: Select all
# Added by Brokenman for Porteus
usershare path = /home/guest/Shared
usershare max shares = 5
usershare allow guests = yes
usershare owner only = yes
Will I have to change anything in these lines if use the above lines?
Code: Select all
[porteus]
path = /mnt/sdb1
public = yes
guest ok = yes
writable = yes
printable = no
3. Do I need to run every time I restart my computer?
Code: Select all
smbpasswd -a root
smbpasswd -e root
chmod +x /etc/rc.d/rc.samba
4. I will try this "chmod 755 /etc/rc.d/rc.samba".
If I have to restart 3 and 4 after a reboot I will try and make script to do it.
Sorry if I'm a pain but I'm up in age and a little slow.
Jack
Re: Porteus as a Server
Posted: 23 Dec 2015, 07:23
by Blaze
Jack, I think
Code: Select all
# Added by Brokenman for Porteus
usershare path = /home/guest/Shared
usershare max shares = 5
usershare allow guests = yes
usershare owner only = yes
does not need.
about
Code: Select all
[porteus]
path = /mnt/sdb1
public = yes
guest ok = yes
writable = yes
printable = no
Yes. You are need to:
- replace path on your path (for example /mnt/sdb1) what you want to share.
- replace name of share [porteus] on your name, for example [myshare] and save changes.
3 and 4. No. These commands run once and everything will work. Your script does not need.
Re: Porteus as a Server
Posted: 04 Jan 2016, 17:03
by Jack
@ Blaze, I can't try it cause I had to give it back to him. One day I try it on my Laptop Computer.
Re: Porteus as a Server
Posted: 17 Apr 2016, 05:47
by Rava
Question... when you want a fileserver, say, for a local network, e.g. media streaming, so, mp3, video, images sharing, maybe a media center.
All Linux based. Me thinks a LAMP or any Samba is overkill, no?
Would not NFS or whatitcalled, the newer Linux network file sharing thingy again?
Would these not be a more slim solution than using one that supports SM-Windoze when one not needs that?