OpenMandriva releases beta Topic is solved

Well it is a family: Mandriva Mageia ROSA Unity PCLOS. Brothers and sisters living together in perfect harmony - so it deserved som space of its own.

Moderators: b1o, jkerr82508

User avatar
viking60
Über-Berserk
Posts: 9351
Joined: 14 Mar 2010, 16:34

Re: OpenMandriva releases beta

Postby viking60 » 26 Oct 2013, 23:14

Ok this is getting boring.
Everything works - so this beta is going to make it to the market.
(Well that startup jungle sound is horrible but it does not affect the functionality)

I have helped to squash a few bugs so I wish the OMA guys the best of luck with this one. I will move on now...
Manjaro 64bit on the main box -Intel(R) Core(TM) i7 CPU 920 @ 2.67GHz and nVidia Corporation GT200b [GeForce GTX 275] (rev a1. + Centos on the server - Arch on the laptop.
"There are no stupid questions - Only stupid answers!"

Blackcrack
Posts: 301
Joined: 02 Apr 2013, 08:31

Re: OpenMandriva releases beta

Postby Blackcrack » 27 Oct 2013, 09:34

Hi,

did you test samba, Apache, nfs, + Drakconf Samba configuring, Apache-User-dir (puplic-html/www) configuring and so on ?
works well ?

the problem it is the conversion fully migration to systemd to have managed the jump ..
because, this was the best possible for take this to attack this step with the rebuild the
Mandriva.. ehh openmandriva with the possibles for take all the new goodys in future ..
for fully intecrating the Systemd was the best decision for Bero as Releasmanager and
Arisel as 2nd Hand and Voice in / for the Peoples, but Arisel is an Silence powered up
energy bundle who makes not many words .. and therefore it is Arisel the best man for president ..
because, he knows !! what he does ! how ever.. i think, in the next time.. or next month
i want test openmandriva again .. because i had last month an bug on hardware and have try at all for remove the bug,
but was not works, because it's maybe the Ram or the CPU ..(grrch..) and therefore i mus change the expensive parts :\
(so i become on this steps maybe one/2 cpu's more on my amd and/or bit more rammmmm .. in this way :gimme )
how ever.. that this so far really well works it's really wellll to hear..

best regards
Blacky

User avatar
viking60
Über-Berserk
Posts: 9351
Joined: 14 Mar 2010, 16:34

Re: OpenMandriva releases beta

Postby viking60 » 27 Oct 2013, 10:00

Blackcrack wrote:Hi,

did you test samba, Apache, nfs, + Drakconf Samba configuring, Apache-User-dir (puplic-html/www) configuring and so on ?
works well ?


Blacky

Samba - no I will have a look at it on popular request :-D Apache - yes see the (fixed) drakwizard bug report I set up a fully working LAMP with phpmyadmin. Userdir can be set with the drakwizard - and I set it like ~/public_html. Works.

The biggest problem with drakconf was this bug:
https://issues.openmandriva.org/show_bug.cgi?id=187
Since that is fixed drakconf is pretty functional. ( I would not want to do a urpme --auto-orphans anytime soon though).
Manjaro 64bit on the main box -Intel(R) Core(TM) i7 CPU 920 @ 2.67GHz and nVidia Corporation GT200b [GeForce GTX 275] (rev a1. + Centos on the server - Arch on the laptop.
"There are no stupid questions - Only stupid answers!"

luca
Posts: 8
Joined: 22 Oct 2013, 20:57

Re: OpenMandriva releases beta

Postby luca » 27 Oct 2013, 10:12

viking60 wrote:(Well that startup jungle sound is horrible but it does not affect the functionality).


hi viking60,
you can disable it

Code: Select all

systemctl disable canberra-system-bootup.service

User avatar
viking60
Über-Berserk
Posts: 9351
Joined: 14 Mar 2010, 16:34

Re: OpenMandriva releases beta -soundbug

Postby viking60 » 27 Oct 2013, 12:14

Thanks luca!
I saw that you were involved in a bug discussion regarding this - here is a demo you can link too to demonstrate what it sounds like
:A

You may have to turn up your volume....
I think I will disable it :-D

@blacky I played around with samba and it sets something up but I never managed to get contact with my other boxes from my VB.

The main problem with samba in this case is the area between the chair and the keyboard.

What does work nicely is ssh and that is way more secure too.
So I have no problem with reaching my mainbox with fish://viking@mainbox-ip in Dolphin
So that is what I use.
Image
Manjaro 64bit on the main box -Intel(R) Core(TM) i7 CPU 920 @ 2.67GHz and nVidia Corporation GT200b [GeForce GTX 275] (rev a1. + Centos on the server - Arch on the laptop.
"There are no stupid questions - Only stupid answers!"

User avatar
viking60
Über-Berserk
Posts: 9351
Joined: 14 Mar 2010, 16:34

Re: OpenMandriva releases beta

Postby viking60 » 27 Oct 2013, 13:21

Hmm It looks like they have introduced a new bug now.
Drakconf prompts for admin password and then simply disappears. It must be something wrong with the prompting because drakconf will start just fine from a terminal as root.
(rpmdrake works just fine though).

Bug reported here
It looks like this:
:A
Manjaro 64bit on the main box -Intel(R) Core(TM) i7 CPU 920 @ 2.67GHz and nVidia Corporation GT200b [GeForce GTX 275] (rev a1. + Centos on the server - Arch on the laptop.
"There are no stupid questions - Only stupid answers!"

Blackcrack
Posts: 301
Joined: 02 Apr 2013, 08:31

Re: OpenMandriva releases beta

Postby Blackcrack » 27 Oct 2013, 17:26

Hi,

@Luca, create an user who you use ever in the other computers and chang it out with you username :)
take a look on the ip's, be normal internal ip's 192.168.0.X-20 ?
Workgroubp it's not really need, you become this server every on adressline from Explorer: \\linuxserver\* with this configuration on allow ip's..
there "hosts allow = 192.168.0.2/19"
from 2-19
linuxuser = windowsuser
linuxpasswords = windowspasswords

the uid from the samba and want be automatic translation via "login" or automatic login by connect

therefor you mus configurate an Linuxuser "blackcrack" for make a test with this smb.conf
for have an User Blackcrack .. or you change the name blackcrack with luca and in the Windows mus exist luca also :)


so take a look and copy this peace of code :)

smb.conf:

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
#
# 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]
   
    # 1. Server Naming Options:
    # workgroup = NT-Domain-Name or Workgroup-Name
    workgroup = Arbeitsgruppe
   
    # netbios name is the name you will see in "Network Neighbourhood",
    # but defaults to your hostname
    #  netbios name = <name_of_this_server>
   
    # server string is the equivalent of the NT Description field
    server string = Linuxserever smb %h %v
   
    # Message command is run by samba when a "popup" message is sent to it.
    # The example below is for use with LinPopUp:
    ; message command = /usr/bin/linpopup "%f" "%m" %s; rm %s
   
    # 2. Printing Options:
    # Required to load all CUPS printers
    printcap name = cups
    load printers = yes
   
    # printcap cache time, so samba will automatically load new cups printers
    printcap cache time = 60
   
    # It should not be necessary to spell out the print system type unless
    # yours is non-standard. Currently supported print systems include:
    # bsd, sysv, plp, lprng, aix, hpux, qnx, cups
    printing = cups
   
    # Samba 2.2 supports the Windows NT-style point-and-print feature. To
    # use this, you need to be able to upload print drivers to the samba
    # server. The printer admins (or root) may install drivers onto samba.
    # Note that this feature uses the print$ share, so you will need to
    # enable it below.
    # Printer admins are now defined by granting the SePrintOperatorPrivilege, ie:
    # run: net rpc rights grant 'DOMAIN\Printer Operators' SePrintOperatorPrivilege
   
    # 3. Logging Options:
    # this tells Samba to use a separate log file for each machine
    # that connects
    log file = /var/log/samba/%m.log
   
    # Put a capping on the size of the log files (in Kb).
    max log size = 50
   
    # Set the log (verbosity) level (0 <= log level <= 10)
    # log level = 3
   
    # 4. Security and Domain Membership Options:
    # 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. Do not enable this if (tcp/ip) name resolution does
    # not work for all the hosts in your network.
    #   hosts allow = 192.168.1. 192.168.2. 127.
   
    # Uncomment this if you want a guest account, you must add this to /etc/passwd
    # otherwise the user "nobody" is used
    #  guest account = pcguest
    # Allow users to map to guest:
    map to guest = bad user
   
    # Security mode. Most people will want user level security. See
    # security_level.txt for details.
    security = user
    # Use password server option only with security = server or security = domain
    # When using security = domain, you should use password server = *
    #   password server = <NT-Server-Name>
    #   password server = *
   
    # Password Level allows matching of _n_ characters of the password for
    # all combinations of upper and lower case.
    #  password level = 8
    #  username level = 8
   
    # You may wish to use password encryption. Please read
    # ENCRYPTION.txt, Win95.txt and WinNT.txt in the Samba documentation.
    # Do not enable this option unless you have read those documents
    # Encrypted passwords are required for any use of samba in a Windows NT domain
    # The smbpasswd file is only required by a server doing authentication, thus
    # members of a domain do not need one.
    encrypt passwords = yes
    smb passwd file = /etc/samba/smbpasswd
   
    # The following are needed to allow password changing from Windows to
    # also update the Linux system password.
    # NOTE: Use these with 'encrypt passwords' and 'smb passwd file' above.
    # NOTE2: You do NOT need these to allow workstations to change only
    #        the encrypted SMB passwords. They allow the Unix password
    #        to be kept in sync with the SMB password.
    ;  unix password sync = Yes
    # You either need to setup a passwd program and passwd chat, or
    # enable pam password change
    ;  pam password change = yes
    #  passwd program = /usr/bin/passwd '%u'
    ;  passwd chat = *New*UNIX*password* %n\n *Re*ype*new*UNIX*password* %n\n \
    ;*passwd:*all*authentication*tokens*updated*successfully*
   
    # Unix users can map to different SMB User names
    ;  username map = /etc/samba/smbusers
   
    # 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 = /etc/samba/smb.conf.%m
   
    # Options for using winbind. Winbind allows you to do all account and
    # authentication from a Windows or samba domain controller, creating
    # accounts on the fly, and maintaining a mapping of Windows RIDs to unix uid's
    # and gid's. winbind uid and winbind gid are the only required parameters.
    #
    # winbind uid is the range of uid's winbind can use when mapping RIDs to uid's
    #  idmap uid = 10000-20000
    #
    # winbind gid is the range of uid's winbind can use when mapping RIDs to gid's
    #  idmap gid = 10000-20000
    #
    # winbind separator is the character a user must use between their domain
    # name and username, defaults to "\"
    #  winbind separator = +
    #
    # winbind use default domain allows you to have winbind return usernames
    # in the form user instead of DOMAIN+user for the domain listed in the
    # workgroup parameter.
    #  winbind use default domain = yes
    #
    # template homedir determines the home directory for winbind users, with
    # %D expanding to their domain name and %U expanding to their username:
    #  template homedir = /home/%D/%U
   
    # When using winbind, you may want to have samba create home directories
    # on the fly for authenticated users. Ensure that /etc/pam.d/samba is
    # using 'service=system-auth-winbind' in pam_stack modules, and then
    # enable obedience of pam restrictions below:
    #  obey pam restrictions = yes
   
    #
    # template shell determines the shell users authenticated by winbind get
    #  template shell = /bin/bash
   
    # 5. Browser Control and Networking Options:
    # 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
   
    # Configure remote browse list synchronisation here
    #  request announcement to, or browse list sync from:
    #       a specific host or from / to a whole subnet (see below)
    #   remote browse sync = 192.168.3.25 192.168.5.255
    # Cause this host to announce itself to local subnets here
    #   remote announce = 192.168.1.255 192.168.2.44
   
    # 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
   
    # 6. Domain Control Options:
    # Enable this if you want Samba to be a domain logon server for
    # Windows95 workstations or Primary Domain Controller for WinNT and Win2k
    #   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 roaming profiles for WinNT and Win2k
    #        %L substitutes for this servers netbios name, %u is username
    #        You must uncomment the [Profiles] share below
    #   logon path = \\%L\Profiles\%u
   
    # Where to store roaming profiles for Win9x. Be careful with this as it also
    # impacts where Win2k finds it's /HOME share
    # logon home = \\%L\%u\.profile
   
   
    # The add user script is used by a domain member to add local user accounts
    # that have been authenticated by the domain controller, or when adding
    # users via the Windows NT Tools (ie User Manager for Domains).
   
    # Scripts for file (passwd, smbpasswd) backend:
    # add user script = /usr/sbin/useradd -s /bin/false '%u'
    # delete user script = /usr/sbin/userdel '%s'
    # add user to group script = /usr/bin/gpasswd -a '%u' '%g'
    # delete user from group script = /usr/bin/gpasswd -d '%u' '%g'
    # set primary group script = /usr/sbin/usermod -g '%g' '%u'
    # add group script = /usr/sbin/groupadd %g && getent group '%g'|awk -F: '{print $3}'
    # delete group script = /usr/sbin/groupdel '%g'
   
    # Scripts for LDAP backend (assumes nss_ldap is in use on the domain controller,
    # and needs configuration in smbldap_conf.pm
    # add user script = /usr/sbin/smbldap-useradd -m '%u'
    # delete user script = /usr/sbin/smbldap-userdel '%u'
    # add user to group script = /usr/sbin/smbldap-groupmod -m '%u' '%g'
    # delete user from group script = /usr/sbin/smbldap-groupmod -x '%u' '%g'
    # set primary group script = /usr/sbin/smbldap-usermod -g '%g' '%u'
    # add group script = /usr/sbin/smbldap-groupadd '%g' && /usr/sbin/smbldap-groupshow %g|awk '/^gidNumber:/ {print $2}'
    # delete group script = /usr/sbin/smbldap-groupdel '%g'
   
   
    # The add machine script is use by a samba server configured as a domain
    # controller to add local machine accounts when adding machines to the domain.
    # The script must work from the command line when replacing the macros,
    # or the operation will fail. Check that groups exist if forcing a group.
    # Script for domain controller for adding machines:
    # add machine script = /usr/sbin/useradd -d /dev/null -g machines -c 'Machine Account' -s /bin/false -M '%u'
    # Script for domain controller with LDAP backend for adding machines (please
    # configure in /etc/samba/smbldap_conf.pm first):
    # add machine script = /usr/sbin/smbldap-useradd -w -d /dev/null -c 'Machine Account' -s /bin/false '%u'
   
    # Domain groups:
    # Domain groups are now configured by using the 'net groupmap' tool
   
    # Enable priveleges, ie allowing members of Domain Admins to join machines
    # to the domain
    # enable privileges = yes
   
    # Samba Password Database configuration:
    # Samba now has runtime-configurable password database backends. Multiple
    # passdb backends may be used, but users will only be added to the first one
    # Default:
    # passdb backend = tdbsam
    # TDB backen with fallback to smbpasswd and guest
    # passdb backend = tdbsam smbpasswd guest
    # LDAP with fallback to smbpasswd guest
    # Enable SSL by using an ldaps url, or enable tls with 'ldap ssl' below.
    # passdb backend = ldapsam:ldaps://ldap.mydomain.com smbpasswd guest
    # Use the samba2 LDAP schema:
    # passdb backend = ldapsam_compat:ldaps://ldap.mydomain.com smbpasswd guest
   
    # Idmap settings (set idmap uid and idmap gid above):
    # Idmap backend to use:
    # idmap backend = ldap:ldap://ldap.mydomain.com
   
    # LDAP configuration for Domain Controlling:
    # The account (dn) that samba uses to access the LDAP server
    # This account needs to have write access to the LDAP tree
    # You will need to give samba the password for this dn, by
    # running 'smbpasswd -w mypassword'
    # ldap admin dn = cn=root,dc=mydomain,dc=com
    # ldap ssl = start_tls
    # start_tls should run on 389, but samba defaults incorrectly to 636
    # ldap port = 389
    # ldap suffix = dc=mydomain,dc=com
    # Seperate suffixes are available for machines, users, groups, and idmap, if
    # ldap suffix appears first, it is appended to the specific suffix.
    # Example for a unix-ish directory layout:
    # ldap machine suffix = ou=Hosts
    # ldap user suffix = ou=People
    # ldap group suffix = ou=Group
    # ldap idmap suffix = ou=Idmap
    # Example for AD-ish layout:
    # ldap machine suffix = cn=Computers
    # ldap user suffix = cn=Users
    # ldap group suffix = cn=Groups
    # ldap idmap suffix = cn=Idmap
   
   
    # 7. Name Resolution Options:
    # All NetBIOS names must be resolved to IP Addresses
    # 'Name Resolve Order' allows the named resolution mechanism to be specified
    # the default order is "host lmhosts wins bcast". "host" means use the unix
    # system gethostbyname() function call that will use either /etc/hosts OR
    # DNS or NIS depending on the settings of /etc/host.config, /etc/nsswitch.conf
    # and the /etc/resolv.conf file. "host" therefore is system configuration
    # dependant. This parameter is most often of use to prevent DNS lookups
    # in order to resolve NetBIOS names to IP Addresses. Use with care!
    # The example below excludes use of name resolution for machines that are NOT
    # on the local network segment
    # - OR - are not deliberately to be known via lmhosts or via WINS.
    # name resolve order = wins lmhosts bcast
   
    # 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 built-in default for versions 1.9.17 is yes,
    # this has been changed in version 1.9.18 to no.
    dns proxy = no
    netbios name = Linuxserver
    hosts allow = 192.168.0.2/19
# You can enable VFS recycle bin and on-access virus-scanning on a per
# share basis:
# Uncomment the next 2 lines (make sure you create a .recycle folder in
# the base of the share and ensure all users will have write access to it.
# For virus scanning, install samba-vscan-clamav and ensure the clamd service
# is running
#   vfs objects = vscan-clamav recycle
#   vscan-clamav: config-file = /etc/samba/vscan-clamav.conf

# Un-comment the following and create the netlogon directory for Domain Logons
# [netlogon]
#   comment = Network Logon Service
#   path = /var/lib/samba/netlogon
#   guest ok = yes
#   writable = no

#Uncomment the following 2 lines if you would like your login scripts to
#be created dynamically by ntlogon (check that you have it in the correct
#location (the default of the ntlogon rpm available in contribs)
#root preexec = /usr/bin/ntlogon -u '%u' -g '%g' -o %a -d /var/lib/samba/netlogon/
#root postexec = rm -f '/var/lib/samba/netlogon/%u.bat'

# Un-comment the following to provide a specific roving profile share
# the default is to use the user's home directory
#[Profiles]
#    path = /var/lib/samba/profiles
#    browseable = no
#    guest ok = yes
#    writable = yes
# This script can be enabled to create profile directories on the fly
# You may want to turn off guest acces if you enable this, as it
# hasn't been thoroughly tested.
#root preexec = PROFILE='/var/lib/samba/profiles/%u'; if [ ! -e $PROFILE ]; \
#                then mkdir -pm700 $PROFILE; chown '%u':'%g' $PROFILE;fi
# If you want read-only profiles, fake permissions so windows clients think
# they have written to the files
# vfs objects = fake_perms

# NOTE: If you have a CUPS print system there is no need to
# specifically define each individual printer.
# You must configure the samba printers with the appropriate Windows
# drivers on your Windows clients or upload the printer driver to the
# server from Windows (NT/2000/XP). On the Samba server no filtering is
# done. If you wish that the server provides the driver and the clients
# send PostScript ("Generic PostScript Printer" under Windows), you have
# to use 'printcap name = cups' or swap the 'print command' line below
# with the commented one. Note that print commands only work if not using
# 'printing=cups'
[printers]
    comment = All Printers
    path = /var/spool/samba
    browseable = no
    # to allow user 'guest account' to print.
    guest ok = yes
    writable = no
    printable = yes
    create mode = 0700
    # =====================================
    # print command: see above for details.
    # =====================================
    print command = lpr-cups -P %p -o raw %s -r # using client side printer drivers.
    #   print command = lpr-cups -P %p %s # using cups own drivers (use generic PostScript on clients).
    # If you install drivers on the server, you will want to uncomment this so
    # clients request the driver
    use client driver = yes

# This share is used for Windows NT-style point-and-print support.
# To be able to install drivers, you need to be either root, or listed
# in the printer admin parameter above. Note that you also need write access
# to the directory and share definition to be able to upload the drivers.
# For more information on this, please see the Printing Support Section of
# /usr/share/doc/samba-<version>/docs/Samba-HOWTO-Collection.pdf
#
# A special case is using the CUPS Windows Postscript driver, which allows
# all features available via CUPS on the client, by publishing the ppd file
# and the cups driver by using the 'cupsaddsmb' tool. This requires the
# installation of the CUPS driver (http://www.cups.org/windows.php)
# on the server, but doesn't require you to use Windows at all :-).
[print$]
    path = /var/lib/samba/printers
    browseable = yes
    write list = @adm root
    guest ok = yes
    inherit permissions = yes
# Settings suitable for Winbind:
# write list = @"Domain Admins" root
# force group = +@"Domain Admins"

# A useful application of samba is to make a PDF-generation service
# To streamline this, install windows postscript drivers (preferably colour)
# on the samba server, so that clients can automatically install them.
# Note that this only works if 'printing' is *not* set to 'cups'

[pdf-gen]
    path = /var/tmp
    guest ok = No
    printable = Yes
    comment = PDF Generator (only valid users)
    printing = bsd
    #print command = /usr/share/samba/scripts/print-pdf file path win_path recipient IP &
    print command = /usr/share/samba/scripts/print-pdf "%s" "%H" "//%L/%u" "%m" "%I" "%J" &
    lpq command = /bin/true
[Linux]
    path = /exports/store01
    comment = Linux Soft
    browseable = yes
    public = no
    writable = yes
    read list = blackcrack
    write list = blackcrack
    admin users = blackcrack
    valid users = blackcrack
    inherit permissions = yes
    hide dot files = no
    preserve case = yes
[windows]
    path = /exports/store03
    comment = winsoft
    browseable = yes
    public = no
    writable = yes
    read list = blackcrack
    write list = blackcrack
    admin users = blackcrack
    valid users = blackcrack
    inherit permissions = yes
    hide dot files = no
    preserve case = yes
[homes]
    path =
    comment = /home/%U on %D
    browseable = no
    writable = yes
[Server]
    path = /exports/store02
    comment = Server- on %D
    browseable = yes
    public = no
    writable = yes
    read list = blackcrack
    write list = blackcrack
    admin users = blackcrack
    valid users = blackcrack
    inherit permissions = yes
    hide dot files = no
    preserve case = yes
[Grafik]
    path = /exports/store05
    comment = Artwork on %D
    browseable = yes
    public = no
    writable = yes
    read list = blackcrack
    write list = blackcrack
    admin users = blackcrack
    valid users = blackcrack
    inherit permissions = yes
    hide dot files = no
    preserve case = yes
[games]
    path = /exports/store06
    comment = Games on %D
    browseable = yes
    public = no
    writable = yes
    read list = blackcrack
    write list = blackcrack
    admin users = blackcrack
    valid users = blackcrack
    hide dot files = no
    preserve case = yes
[Media]
    path = /exports/store04
    comment = Autdio&Video
    browseable = yes
    public = no
    writable = yes
    read list = blackcrack
    write list = blackcrack
    admin users = blackcrack
    valid users = blackcrack
    hide dot files = no
    preserve case = yes
[Users]
    path = /exports/store07
    comment = User-Folders on %D
    browseable = yes
    public = no
    writable = yes
    read list = blackcrack
    write list = blackcrack
    admin users = blackcrack
    valid users = blackcrack
    inherit permissions = yes
    hide dot files = no
    preserve case = yes
[FTP]
    path = /exports/store08
    comment = FTP-Folder on %D
    browseable = yes
    writable = yes
    read list = blackcrack
    write list = blackcrack
    admin users = blackcrack
    valid users = blackcrack
    inherit permissions = yes
    hide dot files = no
    preserve case = yes
[phpfileexplorer]
    path = /exports/store10
    comment = php-fs
    browseable = yes
    public = no
    writable = yes
    read list = blackcrack
    write list = blackcrack
    admin users = blackcrack
    valid users = blackcrack
    inherit permissions = yes
    hide dot files = yes
    preserve case = yes



copy this conf in you /etc/samba/smb.conf

and open it with drakconf and check it out ;)
i hope it helps ..
naturally can you set all shares to puplic, i have here made
it via static ip's and user's so be it a bit more save as only public access ..

i hope it helps :greetings

best regards
Blacky
Last edited by Blackcrack on 28 Oct 2013, 07:16, edited 2 times in total.

User avatar
dedanna1029
Sound-Berserk
Posts: 8784
Joined: 14 Mar 2010, 20:29
Contact:

Re: OpenMandriva releases beta

Postby dedanna1029 » 27 Oct 2013, 19:59

For those on this beta, you might want to add to the very top of urpmi.cfg:

Code: Select all

{
post-clean: 0
}


This way, when you update, if the update doesn't work, you can roll back easily. It keeps the downloaded rpms in /var/cache/urpmi/rpms. What I used to do in order to keep from filling up / (root), was move them to their own folder that I'd created in /home. Once I was completely sure all was working well from the update (a couple days of running), then I'd delete them.

This is also handy for those proggies that you love that are going away. It gives you an rpm to install to future versions of the distro (example is grip, was glad to see it still in Mageia, or an older kernel that works just right for you).

This is only a suggestion, but I can almost guarantee that if you don't, you will wish you had at some point.

Sorry to butt in here, just thought that tip prudent.
I'd rather be a free person who fears terrorists, than be a "safe" person who fears the government.
No gods, no masters.
"A druid is by nature anarchistic, that is, submits to no one."
http://uk.druidcollege.org/faqs.html

Blackcrack
Posts: 301
Joined: 02 Apr 2013, 08:31

Re: OpenMandriva releases beta

Postby Blackcrack » 28 Oct 2013, 07:15

hi Dedanna,

this tip is prudent !
and how it is the way for setting back in which date back ?
plz don't post the half .. if you what told, tell it like it is possible to make this ..
humm, this forum should have an dokuwiki or something :)

best regards
Blacky

User avatar
viking60
Über-Berserk
Posts: 9351
Joined: 14 Mar 2010, 16:34

Re: OpenMandriva releases beta

Postby viking60 » 28 Oct 2013, 09:48

Blackcrack wrote:hi Dedanna,

humm, this forum should have an dokuwiki or something :)

best regards
Blacky



I'll see what I can do about it - I guess a structuring of the tips would be in order.

But we do have the tips and tricks section that only contains tips - it is not allowed to start any topic there that starts with a question. It will only contain solutions.

So if dedanna wants to give a complete and working tip - that would be the place to do it.

It does not have to be rocket science - any working tip will do however simple.
Manjaro 64bit on the main box -Intel(R) Core(TM) i7 CPU 920 @ 2.67GHz and nVidia Corporation GT200b [GeForce GTX 275] (rev a1. + Centos on the server - Arch on the laptop.
"There are no stupid questions - Only stupid answers!"

User avatar
viking60
Über-Berserk
Posts: 9351
Joined: 14 Mar 2010, 16:34

Re: OpenMandriva releases beta

Postby viking60 » 28 Oct 2013, 11:23

I guess the last bug I reported was kind of spitting in the soup since it most likely comes from a fix. Now the fix has become a new bug, probably security policy related.

They don't like it because they have not fixed it in 24 h and they have not confirmed it either - but the video is rather obvious - so there is no point in denying it either.

I have provided data and they are probably looking for something superduper specials on my setup that makes me the "sinner". Which also would be fine (all the specials I have done is to upgrade with apper to workarround that showstoper bug).

I am afraid that this is a global reproducible bug though... Has anyone else noticed it?
Manjaro 64bit on the main box -Intel(R) Core(TM) i7 CPU 920 @ 2.67GHz and nVidia Corporation GT200b [GeForce GTX 275] (rev a1. + Centos on the server - Arch on the laptop.
"There are no stupid questions - Only stupid answers!"

luca
Posts: 8
Joined: 22 Oct 2013, 20:57

Re: OpenMandriva releases beta

Postby luca » 28 Oct 2013, 16:49

Hi viking60,
i'm sorry, but i've tried on several vm and i cannot reproduce it.

Is there nothing useful in .xsession-errors?
and in journalctl?


Return to “The Mandriva family”