ניחשתם נכון:

More stuff can be found at this picasa web album:

Wallpapers

How I got to it? For some reason, when running Fedora’s KDE software management tool, this was the only suggested software in response to the search “LDAP” (which wasn’t a library, plugin or command line tool).

I gave it a chance and actually, its really useful syntax.

Entries are separated by one or more empty lines, and each start with an entry ID number followed by the fully qualified DN of the entry. To edit an entry, just change the following lines in any way you see fit – updating, adding or removing properties is as easy as writing in VI. If you want to add a new entry, create a new batch of lines but start with a line that has the word add (instead of an entry id) followed by the DN you want to add.

A note to remember: the passwords are shown and editable (at least if you log in as a user with full administrative permissions) – as the hash result, exactly as its stored in the directory server itself. You can manipulate them just like any other LDAP attribute, but to set up a new password you’d have to first generate the hash for the new password, and save that. One option is to use the OpenLDAP slappasswd, for example:

slappasswd -h {SHA} -s somepassword


The -h parameter specifies the hashing algorithm to use, and you have to put that text in the attribute value before the hash result. This OpenLDAP FAQ entry has more on the subject of password hashes, including some useful scripts.

When you “save” the buffer, ldapvi will prompt you for a confirmation, which may looks like this:


add: 3, rename: 0, modify: 0, delete: 0
Action? [yYqQvVebB*rsf+?] ?


At which point you are supposed to hit “y” to update the server, though as you can see there are quite a few alternative choices (and in the spirit of VI, presented in a very concise way). And basically that’s it.

So if you’re looking for a good tool to manage your LDAP directory, and your’re a die-hard fan of VI, this just may be the thing for you. Me? Its a useful tool and I’ll be happy to keep it on my belt to fall on to if I’m fresh out of options (which is actually currently the case), but I’ll keep looking for something more… how shall I put it… graphical? less looking like an 80s reject? no, I know – something I can happily let MSCEs use .

Related articles

• LDAP authentication on Fedora 16 (and why it sucks) (geek.co.il)
• LDAP – Lightweight Directory Access Protocol (acordocoletivo.org)
• Using Browsers with OpenLDAP cn=config Tree (administratosphere.wordpress.com)

Recently I had the fortune to work on a Lenovo T420 laptop that has this setup, and it works very well on MS-Windows with the Nvidia Optimus driver – you get battry life around 10 hours with the 9 cell battery.

Unfortunately I spend most of my day in Linux and because Nvidia does not support Optimus on Linux, you have the poor choice of either running everything on the Nvidia chip – decreasing battery life to around 4 hours if you’re careful, or disabling the Nvidia chip completely.

The solution comes from the Bumblebee project – a software suite to handle the switching between the Nvidia discrete graphics and the embedded Intel chip.

The setup is pretty simple to understand (though I suspect under the hood there are many problems to be solved): A service runs and waits for users to ask for 3D accelerated graphics. When a user starts a program using the special command optirun, the service loads the Nvidia driver, starts an X server using the discrete graphics (with the display disconnected from the actual screen) and runs the specified program on that “background” X server. Then it copies the visuals from the program that is rendered using the discrete graphics to a window on the main X server. When the program terminates, the service closes the secondary X server, removes the driver and powers down the graphics card – putting us back into the ~10 hours battery life.

The Bumblebee software had some problems in the past, but the current version – 3.0 – looks very good. There are a few seconds of delay when you launch the application (setting up the driver and X takes some time), but performance is about what you’d expect when running directly on the hardware. All this without any configuration – that is if you are running on the stable Ubuntu version.

As I can’t leave well enough alone, and whenever someone says “alpha”, I say – “I wants”, I’m running the current Ubuntu 12.04 alpha (which is not so bad – due to be released in a couple of months, it works very well). And of course Bumblebee doesn’t work properly here.

So this is what I had to do to get it running:

These instructions assume you are doing everything in a command line. If you are not comfortable with the command line, this guide is not for you – go away.

1. We will start by installing Bumblbee itself and its dependencies. We will need to add their PPA to the Ubuntu software sources list:
sudo add-apt-repository ppa:bumblebee/stable
Unfortunately the project has a repository for Ubuntu 12.04, but at this point in time it does not include all the needed packages. I had to edit the source list file and add the 11.10 repositories as well before installation could complete – open the file /etc/apt/sources.list.d/bumblebee-stable-precise.list for editing as root, for example:
sudo gedit /etc/apt/sources.list.d/bumblebee-stable-precise.list
and duplicate the two lines found there, changing the word precise to oneiric in the duplicates. Save and exit the editor, then run these:
sudo apt-get update
sudo apt-get install bbswitch-dkms bumblebee bumblebee-nvidia virtualgl-libs:i386 libgl1-mesa-glx:i386 libc6:i386
sudo usermod -a -G bumblebee $USER

   The last line adds the current user (the one you are logged in as) to the “bumblbee” user group – only users who are part of this group may use the Bumblebee service. If you have more users that you want to be able to play 3D games, then you need to add them as well.
2. The Bumblebee Project recommends Ubuntu users to install the “X-Swat” x-updates PPA, but this isn’t available for 12.04 users, and we are already running the latest X anyway, right? After bumblebee didn’t work for me, I went to the next best thing – the xorg-edgers repository. A word of warning – this is a set of highly experimental software – if it works for you, count yourself lucky and if it doesn’t – don’t complain. To install it, type:
sudo apt-add-repository ppa:xorg-edgers/ppa
sudo apt-get update
sudo apt-get dist-upgrade -y
At this point most likely your kernel and other important software packages have been upgraded, so its a good idea to reboot.
3. After you come back from the reboot, the standard Nvidia driver will not work, because of an incompatible ABI version. Not to worry, its time to recompile a new Nvidia driver. Start by removing your old one with:
sudo apt-get purge nvidia-current
Now to get the most up to date Nvidia driver package to rebuild a driver that works with your latest Xorg and kernel, create a new directory to hold the Nvidia package sources and change into it, and type:
sudo apt-get install build-essential checkinstall -y
sudo apt-get build-dep nvidia-current-updates -y
apt-get source nvidia-current-updates
Now with the source downloaded and all dependencies installed, we can build a new driver and install it:
cd nvidia-graphics-drivers*
dpkg-buildpackage -us -uc -nc
cd ..
sudo dpkg -i nvidia-current-updates_*.deb
If all went well, you have your new Nvidia driver instaled. Lets see if it loads Ok:
sudo modprobe nvidia_current_updates
If you get no error, then we can go to the next step.
4. The Bumblebee configuration must be modified to work with all this cutting edge stuff, so lets start by turning off the Bumblbee service:
sudo stop bumblebeed

   Now you need to edit the Bumblebee configuration file. Use your favorite text editor to open /etc/bumblebee/bumblebee.conf as root, for example:
sudo gedit /etc/bumblebee/bumblebee.conf
. This is a standard INI filewith a lot of comments to help you figure out what is going on in here, and we will need to do some changes to (a) disable auto-detection and force Nvidia mode and (b) help Bumblebee locate the drivers for the Nvidia graphics. Make these changes:
   • In the [bumblebeed] section, set Driver=nvidia
   • In the [driver-nvidia] section, set KernelDriver=nvidia_current_updates and in both LibraryPath and XorgModulePath change nvidia-current to nvidia-current-updates.

   Save the file after all the changes have been complete, and start the service again:
sudo start bumblbeed


5. At this point, Bumblebee should be ready to do some damage. The recommended way to test it is to run
optirun glxspheres
Give it a few seconds to launch the window (the screen may black out for a bit, don’t worry about it). When the window appears, it should show a graphical demo and a frame per seconds counter at the bottom left corner. On my system it shows a respectable 86 frames per seconds (vs 2 frames per seconds on the embedded Intel chip). If the glxspehere window doesn’t come up, and you get errors from the optirun command, look in the system log file /var/log/syslog for lines from bumblebeed. Also if you haven’t rebooted your computer since you built the Nvidia drivers, it might be a good idea to try that as well.

Running games with optirun is pretty straight forward – either invoke them manually or edit their .desktop files to add the optirun command. I’ve also used this in MS-Windows games running under wine (I recommend using PlayOnLinux – its a beautiful piece of work), and they work perfectly well.

Best of luck, and let me know if it works or if it doesn’t.

Related articles

• Installing Nvidia drivers on Fedora 16 – the wrong way (geek.co.il)
• Ubuntu 12.04 LTS, Codename Precise Pangolin Releases Its First Alpha (techie-buzz.com)
• How to manually install latest nvidia drivers on Ubuntu Oneiric 11.10 (neelmohile.wordpress.com)

So if you still want to authentication your Fedora installation against the company’s Active Directory – and can’t/won’t rely on Winbind’s notably flaky behaviour, you can always install NSS/PAM ldap authentication manually. Unfortunately its not as easy as it sounds, and as I learned the hard way – one must pay careful attention to SELinux. So here’s the recipe:

1. Install pam_ldap and nss_ldap: yum install -y nss_ldap (this will also install the PAM support).
2. Configure LDAP access. In Fedora the NSS and PAM configuration were broken into 2 different files. Fortunately the syntax and required configuration is identical so you can just create both files as a copy of each other or even use a link. My configuration looks like this:

   
# the Active Directory domain - this the LDAPized FQDN of your Active Directory tree
base dc=some,dc=domain,dc=com
# the CN of an unpriviliged user that is allowed to log in and search in the domain.
# we created this dummy user that is not part of the normal domain user and it is needed
# for many integration scenarios
binddn CN=authuser,CN=Users,dc=some,dc=domain,dc=com
bindpw 123456
scope sub
timelimit 120
bind_timelimit 120
bind_polict soft
idle_timelimit 3600
# this is the default set up for SBS directory installation
nss_base_passwd ou=SBSUsers,ou=Users,ou=MyBusiness,dc=some,dc=domain,dc=com
nss_base_shadow ou=SBSUsers,ou=Users,ou=MyBusiness,dc=some,dc=domain,dc=com
nss_base_group ou=Security Groups,ou=MyBusiness,dc=some,dc=domain,dc=com?sub
nss_initgroups_ignoreusers root,ldap,named,avahi,haldaemon,dbus,radvd,tomcat,radiusd,news,mailman,nscd,gdm
# this configuration is based on SFU 3.5 schema that must be installed on the ActiveDirectory server
nss_map_objectclass posixAccount user
nss_map_objectclass shadowAccount user
nss_map_attribute uid sAMAccountName
nss_map_attribute homeDirectory unixHomeDirectory
nss_map_attribute shadowLastChange pwdLastSet
nss_map_objectclass posixGroup group
nss_map_attribute uniqueMember member
pam_login_attribute sAMAccountName
pam_filter objectclass=User
pam_password md5
# configuration for the LDAP server connection
ssl no
uri ldap://LDAP.SERVER.NAME/
tls_cacertdir /etc/openldap/cacerts


   The pam_ldap and nss_ldap come with a default configuration file – just overwrite both of these with the content above (after adapting it to your needs – change the LDAP server name, the LDAP base DN, login user and search paths).

   This is as good a time as any to make sure that your computer can indeed access the LDAP server. I recommend installing openldap-clients and running a test query using ldapsearch. For example, the following query will list all the users eligible for log in using the configuration above:

   
ldapsearch -h LDAP.SERVER.NAME -D "CN=authuser,CN=Users,dc=some,dc=domain,dc=com" -w 123456 -b "ou=SBSUsers,ou=Users,ou=MyBusiness,dc=some,dc=domain,dc=com" dn


3. Now you need to configure the authentication stack to use your new LDAP configuration. Unfortunately, the Fedora configuration tool will not allow you to select LDAP without SSL or TLS and without Krebros, so we’d need to edit the configuration files by hand. But lets start with a clean setup – run authconfig-tui --enablemkhomedir and make sure only “Cache Information”, “Use Shadow Passwords” and “Local authorization is sufficient” are selected, and click “Next”.

   Now lets go edit the configuration files directory. There are two configuration files that need to be edited – /etc/pam.d/system-auth and /etc/pam.d/password-auth. The changes needed to both are identical so just go ahead and edit one of them with your favorite text editor and then copy it over the other one:

   • In the auth section, before the line for pam_deny add:

     
auth sufficient pam_ldap.so use_first_pass


   • In the account section, before the line for pam_permit add:

     
account [default=bad success=ok user_unknown=ignore] pam_ldap.so


   • In the password section, before the line for pam_deny add:

     
password sufficient pam_ldap.so use_authtok


   • In the session section, after the last line, add:

     
session optional pam_ldap.so


   Alternatively, you can download this patch file, and execute it using cd /etc/pam.d; patch < fix-auth.txt.

   Additionally you need to configure NSS separately by adding the ldap module to the configuration in /etc/nsswitch.conf: edit the file and add it in the lines for passwd, shadow and groups, like so:

   
passwd: files ldap
shadow: files ldap
group: files ldap


4. We also need to get SELinux to allow NSS and PAM to contact the LDAP server as part of the login process (before the user gets their own security context where such things are allowed). To do that, run this command: setsebool authlogin_nsswitch_use_ldap 1

Your system should now be ready to log in using LDAP. Have fun.

Required Ingridients:

• A computer with The GIMP installed
• Your handy smart phone with a 5MP or better camera
• A good pen and paper.

So anyway, here’s the process from top to bottom, with pictures:

1. Sit down at a proper table, and using a good black heavy-line pen on a white clean high-density paper, write what you need to write – slowly and deliberately but without pauses. Try not to smear the ink so you get clean continuous lines, otherwise the quality suffers a lot.
   
2. Now take your phone and start the camera app. Make sure that flash is on (not auto – always on), and if your camera supports it, set the “auto focus” mode to “Macro”. Position the camera close to the paper so that it sees your whole text and hold the shutter button (don’t release it yet) to let the camera focus. If you don’t get a clean focus then don’t take the shot, move the camera a bit away and try again until you get a clean focus.
3. After the picture is taken, load it into the computer. This part is usually the most complicated part of the whole process. On my phone I have “Google Docs” app installed, so I “Share” to “Docs” and I then use the browser to go to Google Docs and download the image file.
   
4. Now its time to start GIMP, load the picture and do the magic:
   
5. The first tool to use is the “Crop” tool from the toolbox – we need the image contain only the actual hand written note we want to convert, and specifically we need to get rid of the edges of the picture where the flash didn’t highlight the paper well (because the camera was so close to the paper
   
   The “Auto Shrink” feature is normally very useful for these kinds of jobs, but because of the inherently “noisy’ background of the paper, it wouldn’t work at all – just do your best manually and leave a bit of margin around the text. When you’re done setting up the box around the text, then click the center of the selection to make the crop.
6. Next we need to clear the image of most of the background noise of the paper before the real work can begin – to do this we will use the popular “Unsharp Mask” filter
   
   When the “Unsharp Mask” dialog comes up, push both the “Radius” and “Amount” sliders all the way to the end, while leaving the “Threshold” value at its default small value (I usually set it to 5, but any small number will work fine)
   
   After you apply the filter, the image would look drastically different, as you can see in the example below, but we’re not done yet
   
   If you look closely you’ll see that there are still some color artifacts present. In this example the photograph source is of rather high quality, but with less high quality input you may still see here some blobs and spots which should get taken care of by the next step.
7. To completely separate the hand written text from the background, we will use the “Threshold” command from the “Colors” menu – this will highlight in black only the ink from the photograph and will clear everything else to white. When the “Threshold” dialog opens, click the “Auto” button to automatically select the correct threshold value.
   
   At this point we are basically done with the major part of the work. We need only prepare the image for embedding and possibly due a bit more clean up if the original wasn’t of a good enough quality and we still got some black blotches where there shouldn’t be any.
8. The next step is to remove the white background from the image so it can be later embed the image into another document without having a white box around the text, that hides whatever we were supposedly “writing over”. From the “Colors” menu select the “Color to Alpha” command and apply its default setting (which should be to have the color White converted to transparency)
   
9. If we still got some inky looking blotches, left from the previous stage that we want to remove, you can clean them up manually by adding a layer mask
   
   And set it up to start completely white (opaque – which is the default)
   
   Once that is done – and you can see the layer mask as a white box to the right of the layer preview in the layers tab, take a paintbrush from the toolbox, and touch it to where you have noise that you want removed, careful not to touch actual lines
   
   Finally apply the layer mask by right clicking the layer in the layers tab and selecting “Apply Mask”
10. The last step is to save the result as a PNG file – so that we keep the transparency of the background.

The new image is now ready for import into your PDF editing software of choise, or into any other document where you need to fake ink on paper. You can also, obviously, keep the digital file and use it many times without bothering your hardware (pen, paper and camera) again.

Good luck.

מרכיבים:

• 400 גרם אפונה יבשה צהובה. אפשר להחליף בעדשים חומות או עדשים כתומות (אם כי הן קטנות יותר ונוטות להפוך לעיסה במרק). לא הייתי ממליץ לשים אפונה יבשה ירוקה או עדשים ירוקות כי המרק לא יקבל את הצבע הצהוב הרצוי שלו.
• בצל גדול
• תפוח אדמה בינוני או גדול. ניסיתי להחליף לקולורבי – תחליך התפ”א הסטנדרטי שלי וזה עובד, אבל לא מדהים.
• שני גזרים בינוניים שטופים. אני בד”כ לא מקלף אותם למרות שאני יודע שיש כאלה שאוהבים את זה, ואני אומר – כל הויטמינים בקליפה!
• 2-3 פטריות – להסמיך את המרק. אפשר גם להחליף בקישוא אבל זה נותן למרק צבע יותר ירוק.

הכנה:

להעמיד קלחת קטנה עם מים רותחים על חום בינוני-גבוה ולשפוך פנימה את האפונה היבשה או העדשים. לתת לזה לרחוש ולהוסיף מדי פעם מים אם המים לא מכסים את האפונה. נניח לאפונה להתבשל ולהתרכך בזמן שאנחנו מכינים את שאר הרכיבים.

לשים בסיר כף שמן ולקצוץ פנימה את הבצל. בגדול את הבצל אמורים לגרור כמו שנעשה את שאר הירקות, אבל בצל ופומפיה יסתיים בדמעות, אז אני פשוט קוצץ אותו לחתיכות קטנות. לשים על חום בינוני ולתת לבצל להתאדות עד שהוא שקוף. כשהבצל מוכן ומתחיל קצת להשחים, נשתמש בפומפיה בשביל לגרור לתוך הסיר את התפ”א (כדאי לקלף קודם, אבל אני מניח שלא חייבים) ואת הגזרים. אם החלטנו להשתמש בקישוא במקום בפטריה (או בנוסף – אני גמיש) אז גם הוא נכנס עכשיו. לכסות את הסיר ולתת לתערובת להתבשל לבד כ-20 דקות. כדאי לפתוח ולערבב מדי פעם.

כשהירקות מוכנים, להוריד את האפונה ולשטוף אותה במים נקיים – כדי לנקות את כל העמילנים ושאר השטויות שיוצאות בזמן הבישול ועושות קצף – אני שופך בזהירות את כל המים מהקלחת בלי לאבד את האפונה, ואז ממלא במים נקיים ושופך שוב פעם או פעמיים. לבסוף להוסיף את האפונה – בלי מים – לסיר. אם אנחנו רוצים לשים פטריות בפנים (מומלץ – זה גם מוסיף מאוד לטעם), אז עכשיו זה הזמן להוסיף אותן לסיר, שוב ע”י לגרור אותן בפומפיה.

למלא את הסיר במים רותחים, ולהביא לרתיחה. לערבב מדי פעם עד שהמרק רותח ואז להוריד לאש קטנה. לבשל כ-20 דקות, וכדאי לערבב מדי פעם.

אחרי 20 דקות, הגיע הזמן להוסיף תבלינים: אני שם כפית כורכום, שתי כפיות כמון, חצי כפית מלח, פלפל פפריקה מתוקה וג’ינגר כל אחד. לחילופין אבקת קארי המבוססת על כמון כורכום וכוסברה תחליף את רוב התבלינים האלה.

לבשל עוד 10 דקות על אש קטנה ולקרוא למרק “מוכן”.

בתיאבון.

Related articles

• Longer, Hotter And More Water! (lukeford.net)
• Yesterday’s Turkey Is Today’s Soup (thespectacledbean.wordpress.com)
• Pea Soup is good for the soul (balanceandblueberries.wordpress.com)

The main advantage of either of these methods is security: both have easy transport security (SSH by default, Apache if you set it to server over SSL) and are easy to setup authentication for (SSH authenticate against the system’s accounts using PAM and Apache authenticate against basically anything with a simple setup).

The main disadvantage of these methods are that they are slow (SSH is apparently somewhat faster then HTTP) and when supporting multiple large projects of many developers I started running into all kinds of weird connection errors when you try to manipulate many files on many projects at the same time.

Subversion itself offers another alternative using their own network service called svnserve – this is a standard unix daemon that listens on a specific port and uses a native protocol to communicate with Subversion clients (using the svn:// schema in Subversion URLs). It offers very good performance, but no transport security (encryption) by default. Another major problem with using svnserve as a network service is that while CentOS ships the binary itself (it is required as part of the way that the svn+ssh:// protocol is implemented) it doesn’t ship any support files to run it as a standalone service nor to help with its configuration. Also by default svnserve can only authenticate users using its own Apache-style password database file – which makes it unsuitable to integrate in large organizations.

In this article I’ll document how I setup snvserve as a network service to support a large development environment. The requirements do not include transport security because the server is on a private network and can only be accessed by trusted computers (either local or through a VPN), but we do need to have Subversion users authenticate against a central authentication server that is used by all local services. In my setup the authentication services is Mirosoft ActiveDirectory, but the local server is setup to authenticate to the ActiveDirectory using PAM, so we will setup svnserve to use PAM and gloss over the ActiveDirectory specifics.

The process is as follows:

1. Set up your server: Install CentOS 6 and configure PAM to authenticate to your central authentication. Verify that users can SSH into the server using their login credentials.
2. Set up your Subversion repository: Install subversion and use svnadmin to create your repository. In the below examples I’ve created the repository under /var/svn
3. Set up svnserve to require authentication and do the authentication using the Cyrus SASL libraries: copy the file svnserve.conf from your repository’s configuration directory (for example /var/svn/svnserve.conf) to /etc/svnserve.conf. Edit it and add in the [general] section the following lines:
anon-access = none
auth-access = write
realm = The Name of Your Repository
make sure that all other settings in that section are commented out. Now add, at the bottom of the file, a new section like this:
[sasl]
use-sasl = true

4. Setup the Cyrus SASL library to work with the saslauthd authentication service: create the file /etc/sasl2/svn.conf with the following content:
pwcheck_method: saslauthd
mech_list: plain login

5. Start the saslauthd service and make sure it always run when the system start, by executing the following commands:
# service saslauthd start
# chkconfig saslauthd on

6. Set up saslauthd to allow svnserve to authenticate using the main system’s PAM configuration, by executing the following command:
# cd /etc/pam.d
# ln -s system-auth svn

7. Create the SysV initialization script for svnserve – this will allow you to start and stop svnserve using the service command and have it run when the system start. This is the major part that I expected CentOS to ship but is missing. Creating a good SysV script is not trivial – you can do it yourself but I suggest using the script presented here. I’ve used the script from this blog post which is not bad but its implementation of status didn’t report the status of a dead process, so I modified it and you can download my modified version here. The file is compressed because of WordPress, just download it, run it through gunzip and copy the resulting file to /etc/init.d/svnserve and then give it “execute permissions” using:
# chmod 755 /etc/init.d/svnserve

8. Create a configuration file for the service by creating and editing the file /etc/sysconfig/subversion.conf with this content:
OPTIONS="--config-file=/etc/svnserve.conf -r /var/svn"

   We use the -r option to limit svnserve access to only our repository, so have the value there point to your actual repository if its not /var/svn
9. Set up svnserve to run when the system start, and then start the service itself:
# chkconfig svnserve on
# service svnserve start


And that’s it – you should have svnserve listening on port 3690 and ready to serve clients. The URL you use to access the repository should include only the server name as svnserve access is already rooted to only your repository by the configuration file. So for example if my server is called svn then the URL will be svn://svn.

This setup will still allow you to access the repository using the svn+ssh:// protocol as you would under a normal setup. It can be a bit confusing as access over SSH uses different paths then over the Subversion svnserve network service, because you have to use the full path to the repository on the local file system in the svn+ssh:// URL. To circumvent this, its possible to get the SSH access to also be rooted to your repository’s path and thus be symmetric with the above setup. To do this, create a new file at /usr/local/bin/svnserve and put the following code in it:
#!/bin/bash
exec /usr/bin/svnserve "$@" -r /var/svn

Give the file “execute permissions” by running
# chmod 755 /usr/local/bin/svnserve
, so it can be executed by the Subversion client instead of the system’s svnserve binary. Now both native Subversion and SSH access use basically the same URL, except for the schema part.

Related articles

• CentOS – Subversion Configuration (waterbiscuit.wordpress.com)
• Passwords and svn (stackoverflow.com)
• Importing a subversion repository (stackoverflow.com)
• Subversion – Merging Repositories (stackoverflow.com)

[מוצג כאן ללא אישור המחבר - אני מקווה שלא אכפת לו]