Net :: How to modify Samba extension

Hmmmmmmmmmmmmmmmmm...............

There is something weird going on with the Unionfs system. Looing at the output I posted above the /ramdisk directories should be the top level ones & therfore show all the files linked in the union under that directory (I'm assuming the directory listing is in order of priority). On first booting DSL & opening emelfm (or just using 'ls' in a console) there are no files visible in e.g. /ramdisk/bin. If a file is opened in /bin using e.g. Beaver & then closed it will appear in the file list under /ramdisk/bin (files referenced by symlinks in /bin don't appear in /ramdisk/bin when they are selected).

I'm assuming that the script for unionfs sets /ramdisk/<dir> as the top priority directory. It appears that files only appear in the /ramdisk/<dir> directory listings when an operation is carried out that may require them to be writable. This is not how I thought unionfs was supposed to work. I thought all the files were visible from the top priority directory, but only physically copied to the medium holding the top priority directory if they were needed to be writable?

Quote

I'm uncertain how unionfs decides which of the files it decides to use when /etc/samba/smb.conf if accessed, but it always seems to pick up the one I want (i.e. the edited one in /ramdisk/etc) & that is the one that is stored & reloaded by the backup system when selected in filetool.lst.

using the listu command shows the search order with the topmost level preceding down.

All files are visible from /etc. You really shouldn't being specifying lower level branches, e.g., /ramdisk/etc as only files that have been written are copied there.

Quote

There is something weird going on with the Unionfs system

- Ah, it's somehow good to see that I'm not the only one who has "strange things happen" when not using the legacy boot.

I compiled the full version of samba yesterday, but it looks like smbmount is no longer supported and the kernel in DSL appears not to support the replacement mount.cifs...(or maybe I didn't use the correct syntax).

Confusingly, there is so much stuff available via Google on samba that makes it more difficult to figure out than if there were nothing at all

RobertS,

I agree with what you say, but try this.

Load Samba.unc. Try to edit smb.conf. It doesn't appear in either /etc/samba or ramdisk/etc/samba.

Trying to edit /opt/samba/etc/samba/smb.conf produces a ro file warning & the file can't be altered (surely this is where unionfs should kick in & make a copy to /ramdisk/etc/samba?).

Using emelfm as root, copy smb.conf from /opt/samba/etc/samba to /etc/samba. The copy goes with no error, but no file appears in /etc/samba. Looking in /ramdisk/etc/samba - the file is now there & can be edited. In a terminal cd to /etc/samba & try 'ls', no files are found. Still in /etc/samba try 'vi smb.conf - the file from /ramdisk/etc/samba is opened in vi !!

Quote

Using emelfm as root, copy smb.conf from /opt/samba/etc/samba to /etc/samba...

This is perhaps because of the following symlink chain which exists prior to loading the samba extension:

/etc/samba/smb.conf -> /KNOPPIX/etc/samba/smb.conf -> /opt/samba/smb.conf

I've noticed you cannot overwrite a symlink like /etc/samba/smb.conf - you have to delete it and then copy the replacement file (or it seems that way to me at least).

Next Page...
original here.