Blog

MySQL Administration: Backup and Security Strategies on Linux

16.04.2006 at 19:51

I found the following slides from the OpenSource Database Conference 05 which cover security and backup strategies for mysql quite intresting. Learned a few intersting things while reading it.

MySQL Administration: Backup and Security Strategies on Linux

read more comments

PHP Development with Eclipse

15.04.2006 at 22:43

With PHPEclipse there is a decent plugin for PHP within Eclipse available, although it isn't yet as feature rich as Eclipse for Java development it is quite useable. In combination with the Subversion plugin development becomes even easier.

For both PHPeclipse and Subclipse are well documented install instructions available.

Note that there is also an official PHP-IDE from Eclipse which is developed together with Zend. This is however in a early development state and i haven't had time to take a closer look at it. In the longterm this is probably the solution to go with.

All in all i am quite happy with the development environment.

Marc

read more comments

Subversion backend selection and authentication configuration

25.03.2006 at 23:31

After a few db corruption and jurnal recovering with the Berkley DB backend i strongly advise you to use the filesystem based backend instead. I think it is by now the default but to be sure set it on the command line. By the way here is a comparison of the thow different backends. Personally i like the fact that if needed the repository data can be manipulated by standard tools.

svndadmin create --fs-type fsfs repo

Once the repository is created you can add your files.

svn import . file:///home/svn/repo -m "Initial commit."

Authentication with svnserve (from the docs)

The default svnserve setup provides anonymous read-only access. This means that you can use an svn:// Url to checkout and update, or use the repo-browser in TortoiseSVN to view the repository, but you won't be able to commit any changes.

To enable write access to a repository, you need to edit the conf/svnserve.conf file in your repository directory. This file controls the configuration of the svnserve daemon, and also contains useful documentation.

You can enable anonymous write access by simply setting:

[general]
anon-access = write

However, you will not know who has made changes to a repository, as the svn:author property will be empty. You will also be unable to control who makes changes to a repository. This is a somewhat risky setup!

One way to overcome this is to create a password database:

[general]
anon-access = none
auth-access = write
password-db = userfile

Where userfile is a file which exists in the same directory as svnserve.conf. This file can live elsewhere in your filesytem (useful for when you have multiple repositories which require the same access rights) and may be referenced using an absolute path, or a path relative to the conf directory. The userfile should have a structure of:

[users]
username = password
...

This example would deny all access for unauthenticated (anonymous) users, and give read-write access to users listed in userfile.

Just in case you do not already know, there is an ebook online which covers Subversion in depth.

Marc

read more comments

Resizing loop back fileystems

11.03.2006 at 21:40

I recently needed to resize an existing loop back fileystem which was created with dd after some research i came up with the following which worked fine for me.

First you need to get the current image size preferably in megabytes this can be done with

# du -m loop-back-image.img
300 loop-back-image.img

It says the size is 300mb, so here is how we can add another 100mb to it.

# dd if=/dev/zero of=loop-back-image.img bs=1M seek=300 count=100

seek=300 means that dd will start at this point which is the end, and count=100 tells dd to add 100mb to that point, so we end up with a total size of 400mb. Run resize2fs on the enlarged 400mb image, it will resize the ext2 filesystem on it to fill the image.

# resize2fs loop-back-image.img

If you want to reduce the loop back image size you first have to resize the filesystem on it.

# resize2fs loop-back-image.img 200M

Afterwards you can run 'dd' on the 300mb image to reduce it to 200mb.

# dd if=/dev/zero of=loop-back-image.img bs=1M seek=200 count=0

Again seek=200 says dd to start at 200mb and count=0 means that it should add nothing to that point so we end up with a total image size of 200mb.

read more comments

Debian update and NO_PUBKEY found

18.01.2006 at 17:14

To add the requested key do the following go to http://ftp-master.debian.org/ and download the archive signing key. Then add it to the system as shown below and go on normally.

apt-key add [file-of-key]

Marc

read more comments

<< 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 >>