Re: aufs backport to kernel < 2.6.15

2007-04-01 Thread sfjro
Guten morgen Wilhelm und Pete, Wilhelm Meier: > if you (Junjiro) stays some additional days in germany, I would like to inv= > ite=20 > you too: that's for the nfs-export feature, for the SMP-support you are not= ::: Danke shon. Someday when I go to Germany, I will surely contact to both

Re: aufs backport to kernel < 2.6.15

2007-04-01 Thread sfjro
Guten morgen Pete, Hans-Peter Jansen: > Could you briefly elaborate, which problems you have in mind (other than=20 ::: Mainly locks. For example, VFS holds the inode lock, and then calls aufs. The different version VFS may not hold it. Usually, IMustLock() macro in aufs will detect this

Re: aufs backport to kernel < 2.6.15

2007-03-30 Thread Wilhelm Meier
Konichiwa Junjiro, hi Pete, Am Freitag, 30. März 2007 schrieb Hans-Peter Jansen: > > > > Haha, I decided now. Today I shall have a dinner with sausages, potatos, > > sour cabbage, Butter AUFS Brot, beer, mit singing Ein Prosit. :-) > > I thought about a _good_ restaurant, not a german kneipe, or e

Re: aufs backport to kernel < 2.6.15

2007-03-30 Thread Hans-Peter Jansen
Hi Junjiro, Am Freitag, 30. März 2007 04:29 schrieb [EMAIL PROTECTED]: > Hi Hans, I prefer being called Pete or Hans-Peter, if you don't mind. > Hans-Peter Jansen: > > before switching my users to openSUSE 10.2 diskless, I tackled the job > > of backporting aufs to (at least) 2.6.11 for SuSE 9.3

Re: aufs backport to kernel < 2.6.15

2007-03-29 Thread sfjro
Hi Hans, Hans-Peter Jansen: > before switching my users to openSUSE 10.2 diskless, I tackled the job of > backporting aufs to (at least) 2.6.11 for SuSE 9.3 (diff attached). ::: > All kudos to you! Thank you very much. I believe you have not only good skill

aufs backport to kernel < 2.6.15

2007-03-29 Thread Hans-Peter Jansen
Hi Junjiro, before switching my users to openSUSE 10.2 diskless, I tackled the job of backporting aufs to (at least) 2.6.11 for SuSE 9.3 (diff attached). Note, that I did it "the dirty way" yesterday afternoon, e.g. without checking the exact kernel API change revision, and by deactivating some