Re: More on UIDs/Permissions
Bruce Dubbs wrote: Jeremy Utley wrote: Bruce Dubbs wrote: That is true, however it it technically possible to run multiple servers on different ports. I've never heard of anyone actually doing it though. I'm willing to put all the ftp servers on the same uids/gids but I'd like more opinions. I've thought about a standard of systemaccounts some time ago, and I'm happy to see it's an issue. I have the problem when switching from one server to the other, I want to have as many things the same as possible. Standardized. UID's are one of them. Is it a good idea to group systemaccounts together? For example I've a mailserver running postfix, with virusscanning done by the combination of clamav/clamsmtp and spamchekking done by spamassassin. So I need at least 4 different accounts: postfix: the uids/gids postfix/postfix and nobody/nogroup and the gid postdrop clamav and clamsmtp: the uid/gid clamav/clamav spamassassin: the uid/gid spamassassin/spamassassin What about reserving a range in the numbers for uids and gids for all mail and related software: for example from 100 to 150. And within these you're free to choose. Any relation between port and uidnr/gidnr is not possible with this concept. Stef -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: r3771 - trunk/edguide
Bruce Dubbs wrote these words on 04/22/05 13:27 CST: The zone IDREFS 'fam' and 'libfam' define the area that the index entry refers to. Since all the index entries on the page have 'fam' as the first IDREF in the zone, all the index entries have links to the top of the page. I do not see what the 2nd entry does for us. I am wondering if we should just reference the specific point ('libfam') and have the index link point to that section of the book. Thanks for the explanation. It is done this way so the Index can show what package the entry comes from and then a pointer straight to that section of the package instructions. If we don't want to identify what package it is from in the Index, then yes, we could drop it, but to me, it is valuable information, at very little cost. -- Randy rmlscsi: [GNU ld version 2.15.94.0.2 20041220] [gcc (GCC) 3.4.3] [GNU C Library stable release version 2.3.4] [Linux 2.6.10 i686] 13:41:00 up 20 days, 13:14, 2 users, load average: 0.06, 0.04, 0.04 -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: r3771 - trunk/edguide
M.Canales.es wrote: A link to the actual program/libary description or to the configuration steps for configuring files without the need to scroll-down the full package page. Got it. My misunderstanding. There is no need to change. I'll add the explaination to the edguide. -- Bruce -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page