Tushar Teredesai wrote:
> On 9/14/05, Richard A Downing <[EMAIL PROTECTED]> wrote:
>
>>Sorry to go against everything my BLFS editorial colleagues have said,
>>but I rather like this proposal.
>>
>>I think it adds to the educational nature of both books.
>>
>>If a device exists and has no rule in the lfs set, then a node is
>>created with the default permissions. This is good, since the user will
>>learn, indeed be taught, how to write a rule to achieve their real
>>objectives. This is far better than giving a rote answer, that may only
>>be satisfactory in the context of writing BLFS.
>>
>>In the cases where the device node must be 'forced' because there is no
>>/sys entry, then I say we should teach why, not just baldly tel the answer.
>>
>>I think the effort to put this into BLFS will be worth it in the long run.
>>
>
>
> +1.
>
> But perhaps the change should be made after a new release of LFS +
> BLFS so that BLFS has more time to incorporate the changes.
Well I had intended to reply yesterday, however I've lost my modem.
Notice this coming from SWBell again and I with net access from my cell
phone. I did not like the proposal at first either (July IIRC when I
read it first), however I have since changed my mind. For Randy, I
believe Richard's post above is _the_ answer to your question. (What is
the benefit?) Edumacation! ;-)
Another thing, and this does border on the minimalist thinking, but why
should I have an audio group and alsa rules on my mail server strait
from a base LFS that can't (won't) take advantage of them? The same for
tty{S*,CAU*} etc....and owned by yet another group (dialout) that I do
not want on my server. Of course, that particular vantage point can
easily be reversed and make just as much sense if only LFS is involved.
However, we have BLFS where all the add on software is displayed. It
just seems to me that BLFS is the logical place to configure these
devices with proper permissions and ownership. Untill that point, the
devices are created with safe root-only owner/group/permissions.
Just to throw it out there for the BLFS crew, well anyone interested
actually. I had envisioned one page in BLFS for the other sections to
link back to. This page would contain various rules files and any pages
can link back to it when a new rule is needed say in udf-tools (nobody
has mentioned the pktcdvd device yet). I'd even like to go so far as to
mention cdsymlinks{,.sh} and cdromid..but this may be a bit much so
early on. Anyway, it's one simple way to go for BLFS, which I don't
_think_ will be all that invasive.
-- DJ Lucas
--
http://linuxfromscratch.org/mailman/listinfo/lfs-dev
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page
