> IMHO at least all lightly or what's the point?
The prezzy should on be about 90 Mins, shouldn't it be? Some things will need to be dropped. Lets say I wanted to demo Printing from a Windows desktop through a Linux server. We take a preconfigured Windows box. We take a Linux box, add CUPS, configure CUPS, create a printer, perhaps install foo-matic drivers and/or ghostscript, then go to smb.conf, and set it up to print with CUPS (it probably is, but we'd want to discuss what is needed, and why). go back to the Windows box, and map to the printer. Add in any sort of "uniqueness" (new Cups printers don't show up unless Samba re-reads smb.conf) that should be discussed. Print a test page. Time's up. More or less. Cups is one method of printing. There are several. If I'm the only one using cups, I've wasted everyone's time. Samba is a big topic, because it ties to/depends on so many things. If I was going to do a discussion, I'd rather go a bit deeper on topics that people need help with than spend them on things that nobody cares about. Do people care about using smbclient and/or smbstatus? mount -t smbfs? Should I talk about the difference between SMB and NMB? The line dividing where samba ends, and something else (Microsoft networking, Linux security, Samba security, Printing, Domain Controller, etc.) And that's intentionally ignoring winbind & PAM. It's intentionally ignoring maintaining Samba across VPNs or other routed networks. (WINS servers). Given my own guess, most people want to be able to connect a single Linux desktop to a (spouses) Windows desktop and share files & printers in either direction. Mostly I'm looking for confirmation that that is an accurate guess. I believe it was Jarrod that was trying to set up a situation like that most reciently on the list. I suspect he isn't alone. Kev.
