> > > Yo. I'm with you man! > What I meant was the way some confs etc are done in /etc. I've been using > freebsd (just learning) and the /etc/ssh/sshd_config was done slightly > differently and looked like it was taken from the project/openbsd with some > modifications (I don't know for sure but it sort of says it at the top and > spells out the rationale for the whole conf file). At the time I was > setting the system up I remember thinking that I preferred it. > But this extra layer of debian-ness is also a good thing as it creates > standardisation. Noone inheriting a box from me has to work out the crazy > way I structured apache if I adhere to the debian way etc etc
I'm a serious apt fan, and debian has always been my favourite, but over the last couple of years I've found I've dealt with too many different unix(ish) platforms and they tend to merge into a rough kind of way to guess where something is on different systems instead of knowing one particular platform really well.. so when you ultimately just want to change something slightly obscure but easy and you've found you haven't used flavour x in a while for some reason then I naturally think it's useful to just figure it out when you need it instead of remembering everything.. so when this happens on a debian or ubuntu system, I find doing `dpkg -L packname` quite often tells me where I should look, and if I don't know the package name then I might use a search with `dpkg -S /path/to/exe` to tell me.. you can do the same kind of thing with rpm if you're on a redhat like system and indeed on most platforms you can figure out how to do this quickly enough, but if not, from there there's the unix rosetta stone, which you seriously need to check out if you don't know of it (http://www.bhami.com/rosetta.html) and then always google and slug of course ;) -- SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/ Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html
