Ian Shields <[EMAIL PROTECTED]> writes:
> > > I think that this is a reasonable forum for discussing exam 
> > objectives and the 
> > > concept of drivers, libata for example, is reasonable.  The 
> > question is, for 
> > > what exam?
> > 
> > Should libata be part of the LPI 101 exam, and therefore part of the
> > exam objectives?  If so, is it too late to get it inserted into the 
> > new exam objectives?
> 
> The IBM developerWorks tutorial (
> http://www.ibm.com/developerworks/linux/lpi/) for topic 101 needs 
> updating. It's on my list of things to do.

Ian, I know that you are coming to LW next week.  We could discuss this live.

There is a technical advisory committee meeting on the wednesday (I believe).
Can you make that?

Also, is anyone else on the list coming to LWSF?  You're all invited to the
TAC meeting :)


> libATA has been in Fedora since Fedora 7, so it's not just Ubuntu. I 
> believe ti is worth mentioning as the SCSI-like interface has at least one 
> ramification, namely that you are limited in the number of partitions that 
> are supported on a single disk. IIRC, you are really limited to a maximum 
> partition number, so if you only have extended partitions on a disk you 
> lose four partition numbers. So the partition that used to be /dev/hda16 
> becomes unusable with libATA. That sort of thing does belong in the LPI 
> exam IMHO. 

I guess my concern is that this looks a little like the '1024 cyclinder
limit' issue.  It's a big deal the first time (and maybe the 2nd and 3rd) but
it seems a little too specific for the exam.  It may become a 'gimme'
question if there are just too few things to ask around it.

Regards,
-- 
g. matthew rice <[EMAIL PROTECTED]>      starnix care, toronto, ontario, ca
phone: 647.722.5301 x242                                  gpg id: EF9AAD20
http://www.starnix.com              professional linux services & products
_______________________________________________
lpi-examdev mailing list
lpi-examdev@lpi.org
http://list.lpi.org/cgi-bin/mailman/listinfo/lpi-examdev

Reply via email to