dickohead

apparently, you have to pay for Ryzom.... and continue paying a subscription fee... how is that open-source?

Total Anihilation works well with wine - and is one of the greatest RTs games ever produced! You can even add units/maps to make the game more interesting, more difficult or whatever!

check your pm phunni, solution to your ATI problem... i hope... if it's not too late.

i too have a linksys router and have been experiencing issues with it just not working some times, no matter what operating system i am in, and it is also a connection problem between either: my modem and router my modem and my ISP i am always able to access the router, and the only thing so far i have found that fixes my problem is unplugging the router and modem from mains and plugging them back in. Works every time.

Hey guys, How do i create a samba user that can login to restricted samba shares from windows XP? I have public access working fine for heaps of folders... but that's my problem, everyone can see everyone elses home folders..... not a good idea! So how do i restrict them so when users try to access folders, they are asked to login? Here is the section of my smb.conf file: [DYLAN_HOMEPAGE] path = /home/dylan/public_html comment = Dylan's Homepage writeable = yes valid users = @dylan user = dylan i have run: smbpasswd -a dylan password: retype password: and that was all good, but is there a command to add the user as an smbuser? smbuseradd made sense, but isn't a command in mandrake 10......... how do i allow users login access to samba from windows xp? Everytime i try and login from an XP machine, it fails and tells me that: is not accessible. You might not have permissions, blah blah Multiple connections to a server or shared resource by the same user, using more than one username, are not allowed. Disconnect all previous connections to the server or shared resource and try again but i have no other connections to the samba folder... i am logged into ssh, but not as 'dylan '.....

set all ip addresses to static, or have the linux box static, and set up DHCP so it assigns addresses to the windows machine. Or - see if you can ping from windows to linux when your network neighbourhood doesn't work, then you'll know it's more likely to be a samba issue.

*bashes self in head* thanks gowator, that's exactly what i forgot, been dealing with Samba and Apache a whole lot, and i was doing all that at the command line, but when using MDK to access NFS it was all graphical, and i wasn't logged in as root.... so it will work as root, which makes sense, but not as my user, which i shall fix when i get home! Thanks for reminding me!

a very good source of CSS/XHTML help is http://alistapart.com they have some great methods of doing things! When viewing your site in IE, i notice that the content is shifted to the right a fair bit.... looks horrid! If you want to use multiple style sheets, your best option would be to to use PHP to set either variables, or cookies, and then have a script that selects a style sheet based on the contents of the cookie... want to know how to do that? so do i :unsure: !!!

so the only way to fix that would be to some how let apache know all the addresses it is known as, and redirect it to one global one.... that way it will only log in once, to the redirected one..... i think....

httpd2: Could not determine the server's fully qualified domain name, using 127.0.0.1 for ServerName So i changed that in my httpd.conf file, there was also a favicon.ico error about 300 times, so i just put a tux icon in :P, but now when i log in to: dickinson.homelinux.net/tim it promtps me for a username and password twice, but it redirects me to dickinson.homelinux.net/tim/ which is great!!! But why do i have to log in twice now :unsure:

when i enter the username and password correctly i get sent to either: /tim/ - which gives me my index.php file or /tim - which gives me nothing. All i want to be able to do is have it so that when /tim is added to the domain name, it changes it to /tim/ that way the login works and the page comes up. I will check the error files now, see if it mentions anything. Thanks anon, i'll post what i find.

http://dickinson.homelinux.net i am using PHP currently, for multiple things, PHP is fine, and htaccess is fine: http://dickinson.homelinux.net/tim/ as you can see :D: But - it just won't forward /tim to /tim/

Alright, way beyond frustrated with this problem at the moment, i have read more documentation that you can poke a stick at, and have tried so many possible combinations of RewriteRule and RewriteBase in as many .htaccess files as i have folders to fix. Restarted the apache server so many times it thinks it's running on windows. Now.... I am running mandrake 10.0, with Apache 2, and no matter how many apparent solutions there are on the internet - not one of them work. I have multiple folders accessible from the root directory of my website, one of them is: tim/ and the other is ~tim/ one is the home page directory, the other for file uploads..... now - when i go to: domainname.com/tim - it won't redirect me to domainname.com/tim/ nor will it work with ~tim Where and what do i have put in place so that anyone who makes a request on the address: domainname.com/tim or /~tim will be redirected so that the index.php file loads up? I have read the URL redirecting guide at Apache.org, and tried to put the following: RewriteEngine on RewriteBase /~tim/ RewriteRule ^tim$ tim/ [R] into the .htaccess file inside the /tim and /~tim folders - but it refuses to work, i have also tried to put: RewriteEngine on RewriteBase /~tim/ RewriteCond %{REQUEST_FILENAME} -d RewriteRule ^(.+[^/])$ $1/ [R] into the root directory of my apache server - /var/www/html/.htaccess and in the folders /tim and /~tim.... And yes the modules are loading in my httpd.conf file, and yes UseCanonicalName on is present.... Surely the code i am using is wrong, because nothing i do seems to work... and i am very close to giving in, which really hurts!!!

Hey guys, I can authenticate as a local user and gain access to my server fien, but am unable to login as anonymous..... /etc/proftpd.conf # This is a basic ProFTPD configuration file (rename it to # 'proftpd.conf' for actual use. It establishes a single server # and a single anonymous login. It assumes that you have a user/group # "nobody" and "ftp" for normal operation and anon. ServerName "Linux Box FTP Access" ServerType standalone DefaultServer on # Allow FTP resuming. # Remember to set to off if you have an incoming ftp for upload. AllowStoreRestart on # Port 21 is the standard FTP port. Port 21 # Umask 022 is a good standard umask to prevent new dirs and files # from being group and world writable. Umask 022 # To prevent DoS attacks, set the maximum number of child processes # to 30. If you need to allow more than 30 concurrent connections # at once, simply increase this value. Note that this ONLY works # in standalone mode, in inetd mode you should use an inetd server # that allows you to limit maximum number of processes per service # (such as xinetd). MaxInstances 30 # Set the user and group under which the server will run. User nobody Group nogroup # To cause every FTP user to be "jailed" (chrooted) into their home # directory, uncomment this line. DefaultRoot ~ # Normally, we want files to be overwriteable. <Directory /> AllowOverwrite on </Directory> # Needed for NIS. PersistentPasswd off # Default root can be used to put users in a chroot environment. # As an example if you have a user foo and you want to put foo in /home/foo # chroot environment you would do this: # # DefaultRoot /home/foo foo #Set root directory for Anonymous user <Anonymous /var/ftp> AnonRequirePassword off #set the user and group for "anonymous" access User ftp Group ftp RequireValidShell off #alias "anonymous" login to "ftp" UserAlias anonymous ftp #restrict "Anonymous" from writing to anything <Directory *> <Limit WRITE> DenyAll </Limit> </Directory> </Anonymous> Now that all seemd fine and dandy.... but whren i try and connect: [root@localhost root]# ftp 192.168.1.111 Connected to 192.168.1.111. 220 ProFTPD 1.2.9 Server (Linux Box FTP Access) [linuxbox] 500 AUTH not understood 500 AUTH not understood KERBEROS_V4 rejected as an authentication type I am confused?! i have seen a few problems on the internet with access and KERBEROS_V4 authentication, but i know nothing about it, and cannot find anything useful about it.... has anyone had this issue and know of a solution? Many thanks in advance!! :woops: Dickohead.

yeh exportsfs has been run, and the shares are picked up by the client, but i am unable to write to them.... it's odd, because the samba shares are working perfectly, read and write :confused:

Hey guys, I have set up some NFS shares, and i have access to them, but i am unable to write to them at all..... Here is the contents of /etc/exports on the server: /home/tim/Music *(rw,all_squash,sync) /home/tim/Storage *(rw,all_squash,sync) /var/www/html/tim *(rw,all_suqash,sync) and here is the contents of /etc/fstab on the client: 192.168.1.111:/home/tim/Music /mnt/Music nfs soft,rsize=8192,wsize=8192,nosuid 0 0 192.168.1.111:/home/tim/Storage /mnt/Storage nfs soft,rsize=8192,wsize=8192,nosuid 0 0 192.168.1.111:/var/www/html/tim /mnt/tim nfs soft,rsize=8192,wsize=8192,nosuid 0 0 According to what i have read, this should be correct.... but for some reason... it won't allow me full access, i have resytarted both sets of NFS (NMB) services on the client and the server, but access is still denied..... both the client and server are running mandrake 10. Hope someone can see what i have done wrong!! :unsure:

FRICKIN YEH!!!!! I added the attribute of: guest only = ok to my shares and i now have read access to them.... but i do not have write access from the windows machines.... here is my new smb.conf file: # 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] workgroup = MSHOME server string = Server printcap name = cups load printers = yes printing = cups printer admin = @adm log file = /var/log/samba/log.%m max log size = 50 guest account = smbuser map to guest = bad user security = user encrypt passwords = yes smb passwd file = /etc/samba/smbpasswd socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192 dns proxy = no #============================ Share Definitions ============================== [printers] comment = All Printers path = /var/spool/samba browseable = no guest ok = yes writable = no printable = yes create mode = 0700 use client driver = yes [print$] path = /var/lib/samba/printers browseable = yes write list = @adm root guest ok = yes inherit permissions = yes [pdf-gen] path = /var/tmp guest ok = No printable = Yes comment = PDF Generator (only valid users) printing = bsd printcap name = cups #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 [TIM_MUSIC] path = /home/tim/Music comment = /home/tim/Music public = yes only guest = yes guest ok = yes writable = yes [TIM_STORAGE] path = /home/tim/Storage comment = /home/tim/Storage public = yes only guest = yes guest ok = yes writable = yes wide links = no I added smbuser to the group of users and the group tim and now it works!!! now how do i add solved to the thread...?

that's just an alert to let you know have put a cd in the drive that conmtains music and data (a mixed cd)...... somewhere in gnome config (i'm a kde user) there will be an option to turn that off surely..... try the gnome help files.

and if it fails again at start up, open a console and get root access (su) then type: ifup eth0 this will bring up the eth0 interface, hopefully connecting you to the network, after that, try running your lan config again and set a static ip if need be, or use dynamic then in a console type (as root): ifconfig and make sure you have obtained an IP address (if set dynamically) or try pinging your router if you set it as static: ping 192.168.1.X where x is the routers address if you can do this it has worked, reboot and hope it starts at boot time. if not... you may have to keep typing "ifup eth0" each time untill a proper fix is found. (i had the same issue - the above worked for me!)

you could try asking at a linksys forum perhaps? or maybe run the network config tool, or the hardware config tool?

not too knowledgeable on fstab entries myself... especially in regards to external drives, but i was using 10.1 and it refused to mount local NTFS drives at all - so perhaps you're having the same problem as me...? The kernel does not like them at all! Try recompiling your kernel to a newer version and make sure NTFS support is enabled.... just a suggestion

alrighty, i added the smb.conf file, it's frickin huge, but i wasn't sure what to cut out and what to leave in... so being a samba noob i left it all in.... hope it's not too hard to look at!!! :unsure:

I have searched this forum and many more but have yet been able to find an resolved issue similar to mine..... I am running a mandrake 10 server with two samba shares, one for Music and one just for other file Storage. The problem is that windows XP cannot open them up, i have created a samba user called: smbuser and gave them no password using: smbpasswd and i also set the default user in smb.conf to be smbuser..... my config file is attached, but i am still unable to figure out what is wrong :unsure: I know it will be something simple i have overlooked, it always is! But on a side note... i've never had samba working with MDK 10, but it worked fine in MDK 9.X Any help would be greatly appreciated guys!!! # 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 = MSHOME # 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 = Server %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: # CHANGES TO ENABLE PRINTING ON ALL CUPS PRINTERS IN THE NETWORK # (as cups is now used in linux-mandrake 7.2 by default) # if you want to automatically load your printer list rather # than setting them up individually then you'll need this printcap name = cups load printers = yes # 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 admin = @<group> <user> printer admin = @adm # This should work well for winbind: ; printer admin = @"Domain Admins" # 3. Logging Options: # this tells Samba to use a separate log file for each machine # that connects log file = /var/log/samba/log.%m # 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 = smbuser # 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 ; winbind uid = 10000-20000 # # winbind gid is the range of uid's winbind can use when mapping RIDs to gid's ; winbind 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: # Most people will find that this option gives better performance. # See speed.txt and the manual pages for details socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192 # 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/share/samba/scripts/smbldap-useradd.pl '%u' ; delete user script = /usr/share/samba/scripts/smbldap-userdel.pl '%u' ; add user to group script = /usr/share/samba/scripts/smbldap-groupmod.pl -m '%u' '%g' ; delete user from group script = /usr/share/samba/scripts/smbldap-groupmod.pl -x '%u' '%g' ; set primary group script = /usr/share/samba/scripts/smbldap-usermod.pl -g '%g' '%u' ; add group script = /usr/share/samba/scripts/smbldap-groupadd.pl '%g' && /usr/share/samba/scripts/smbldap-groupshow.pl %g|awk '/^gidNumber:/ {print $2}' ; delete group script = /usr/share/samba/scripts/smbldap-userdel.pl '%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/share/samba/scripts/smbldap-useradd.pl -w -d /dev/null -g machines -c 'Machine Account' -s /bin/false %u # Domain groups: # Domain groups are now configured by using the 'net groupmap' tool # 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 = smbpasswd guest # 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: # Idmap backend to use: ; idmap backend = ldap:ldap://ldap.mydomain.com # This is a range of unix user-id's that samba will map non-unix RIDs to, # such as when using Winbind ; idmap uid = 10000-20000 ; idmap gid = 10000-20000 # 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 # 8. File Naming Options: # Case Preservation can be handy - system default is _no_ # NOTE: These can be set on a per share basis ; preserve case = no ; short preserve case = no # Default case is normally upper case for all DOS files ; default case = lower # Be very careful with case sensitivity - it can break things! ; case sensitive = no # Enabling internationalization: # you can match a Windows code page with a UNIX character set. # Windows: 437 (US), 737 (GREEK), 850 (Latin1 - Western European), # 852 (Eastern Eu.), 861 (Icelandic), 932 (Cyrillic - Russian), # 936 (Japanese - Shift-JIS), 936 (Simpl. Chinese), 949 (Korean Hangul), # 950 (Trad. Chin.). # UNIX: ISO8859-1 (Western European), ISO8859-2 (Eastern Eu.), # ISO8859-5 (Russian Cyrillic), KOI8-R (Alt-Russ. Cyril.) # This is an example for french users: ; dos charset = 850 ; unix charset = ISO8859-1 #============================ Share Definitions ============================== [homes] comment = Home Directories browseable = yes writable = yes # You can enable VFS recycle bin 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. See # examples/VFS/recycle/REAME in samba-doc for details ; vfs object = /usr/lib/samba/vfs/recycle.so # 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 # 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 # 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). # 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-generator] path = /var/tmp guest ok = No printable = Yes comment = PDF Generator (only valid users) #print command = /usr/share/samba/scripts/print-pdf file path win_path recipient IP & print command = /usr/share/samba/scripts/print-pdf %s ~%u //%L/%u %m %I "%J" & # 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 ; public = yes ; writable = no ; write list = @staff # Audited directory through experimental VFS audit.so module: # Uncomment next line. ; vfs object = /usr/lib/samba/vfs/audit.so # 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 [MUSIC] path = /home/Tim/Music comment = /home/Tim/Music public = yes guest ok = yes writable = yes [STORAGE] path = /home/Tim/Storage comment = /home/Tim/Storage public = yes guest ok = yes writable = yes wide links = no

alrighty! Many thanks to pmpatrick and chris z, i am now successfully in mandrake 10.1 on my second hard drive, the problem all along was this: As you stated pmpatrick, my initrd was incorrect, and devfs was set to mount rather than nomount, but it runs out my partitions are not labled /hdb1,2,3 they are /hdb,1,5,6 ..... it seems my first hard drive is done in very much the same fashion, not to worry! it all works now.... except for an odd error when trying to run almost anything.... "KLauncher could not be reached via DCOP" If you have any ideas on that....... glad to hear them! If not i shall search google tomorrow some time. Many thanks guys, you have been amazing help!!! :D

glad to see i have errors!!! That makes things a lot cleare, and i am using standard IDE hard drives. So i need to copy my vmlinuz and initrd files from /hdb1/boot to /hda3/boot and then lilo will boot the correct kernel and thus load linux from /hdb? so there is no need to copy modules or anything over aswell? Because i only made /boot 50MB, and my modules are a lot bigger than that.... i shall alter lilo and place vmlinuz and initrd into my /boot partition on /hda Wish me luck!! many thanks pmpatrick!