Samba and Apache on the Empeg

Greetings People

I finally "fixed" my Empeg: the reason was a faulty drive cable (as suspected). In fact, the middle connector was the dodgy one (as speculated).

Anyway, in order to run Samba (I believe somebody needed to do this so that they could use Windows software to do stuff on files on the Empeg) and Apache, the only support from the kernel needed is System V IPC. This increases memory consumption by about 27K. Moreover, this cannot be had as a loadable module (not that loadable module support is enabled to begin with). Note that both Samba and Apache will run out of the box if IPC is present in the kernel.

Typical RSS of Apache (1.3.9 from Debian) is about 1.3 MB. Typical RSS of Samba (smbd + nmbd, 2.0.7 from Debian) is about 1.1 MB. Of course, these need not be run at the same time, and Apache can be configured to run minimally.

Regards
Amit

Hm, so they could run quite comfortably on MkIIa... Maybe we should suggest to Mark to include SysV IPC support into his kernels. 27kB is not that much...

Kim Salo got samba running a while back, the thread about this is here.

Hmmm ... Kim mentions about tweaking Samba source and the stuff being nowhere near plug and play, etc. At least the current Samba from the Debian distribution works out of the box, given System V IPC.

Regards
Amit

27KB would be about equal to the size difference between a "stock" v200b7 zImage and the Hijack v200b7 zImage.. of course, those are the compressed sizes.

Say, this interests me a bit.

I checked out Kim's post as well, but it doesn't have the start-to-finish HOWTO.

What I wound up doing was going through my Solaris Samba install, using ldd and a few other things on the Empeg (I grabbed a library distribution from - arrrgh, can't remember who posted a link to it now, it was about 9MB compressed), and tried my darndest to recreate the file arrangement.

I know I'm CLOSE, but still no cigar.

If you want, write me privately and we can work through it, then we can post the actual steps (or we can discuss it publicly too - just thinking "I am the Lorax! I speak for the trees!")

Heh-heh.

Actually, it helps (IMHO) a lot (and avoids kludges) to have at least a minimal Debian "installation" (either on the Empeg directly, or on an NFS server). I say Debian because pre-compiled ARM packages for it are readily available. Then it's not necessary to keep coming up with missing libraries, files and devices, etc.

I didn't have to do anything special other than the steps mentioned below (nothing at all to the Samba source/package) to get it up and running. To do it this way:

[1] Get a minimal Debian file-system up and chroot into it.
[2] Recompile (or download) a kernel that has stuff that you want, plus System V IPC.
[3] Install the Samba package.

That should be it.

Regards
Amit

Actually, my bad. I was ambiguous in what I mentioned. I just said "increases memory consumption by 27 KB". That's not quite what I meant. 27 KB is the size of the object file (ipc.o) which is added to the kernel before it is compressed.

Then again, this size is only a rough indicator. The resident set size of the code will be a tad larger.

Regards
Amit