Re: [lpi-examdev] SQL in 101
+1 Met vriendelijke groeten, *Henk Snel* Storage Consultant Mobiel: +31 (0) 653493434 E-mail: henk.s...@tenict.nl http://www.linkedin.com/in/henksnel [image: Logo] Dodeweg 6c 3832 RC Leusden http://www.tenict.nl On Wed, Feb 11, 2015 at 6:45 PM, Hendrik Jan Thomassen h...@atcomputing.nl wrote: Matthew Rice wrote: My own personal reasons for not hating it in the objectives is that I've seen a few times where management want to get reports out of a DB and they turn to the techs to help them with that task. in particular, having Excel/*Office connecting to the DB and then trying to figure out some simple queries. This exactly illustrates my point that SQL as such has nothing to do with Linux system administration, but is just another application domain. In this case: use of computers for business applications. There are so many other uses for a computer, even with Linux :-) The Linux OS is the common denominator under a plethora of different application domains: business administration, telecom, science, numerical control, web serving, ... ... ... I.m.h.o. the LPI certification should restrict itself to this common denominator under all application domains. -- Hendrik-Jan Thomassen h...@atcomputing.nl AT Computing Linux/UNIXperts, opleiders oplossers Tel +31 24 352 72 82 Kerkenbos 1238Tel cursussecretariaat: +31 24 352 72 72 6546 BE Nijmegen Fax +31 24 352 72 92 i...@atcomputing.nl www.atcomputing.nl 'If you think education is expensive, try ignorance.' ___ lpi-examdev mailing list lpi-examdev@lpi.org http://list.lpi.org/cgi-bin/mailman/listinfo/lpi-examdev -- *Disclaimer:* Dit bericht (inclusief de eventuele bijlagen) is vertrouwelijk. Wanneer u dit bericht ten onrechte heeft ontvangen, dient u de afzender hiervan onmiddellijk per kerende e-mail op de hoogte te brengen en dit bericht te verwijderen uit uw systeem. Elk onbevoegd gebruik en/of onbevoegde verspreiding van dit bericht is niet toegestaan. U wordt erop gewezen dat e-mailberichten aan wijziging onderhevig kunnen zijn. Voor al onze aanbiedingen en of offerte(s) zijn onze algemene voorwaarden van toepassing. Deze voorwaarden zijn gedeponeerd bij de KvK te Utrecht. Onze voorwaarden kunnen op verzoek tevens toegezonden worden. TenICT is niet aansprakelijk voor de onjuiste en onvolledige overdracht van de informatie in dit bericht noch voor mogelijke vertraging in de ontvangst van dit bericht of schade aan uw systeem als gevolg van dit bericht. TenICT staat er niet voor in dat de integriteit van dit bericht behouden is gebleven noch dat dit bericht vrij is van virussen, niet is onderschept of vatbaar is geweest voor tussenkomst (door derden). ___ lpi-examdev mailing list lpi-examdev@lpi.org http://list.lpi.org/cgi-bin/mailman/listinfo/lpi-examdev
Re: [lpi-examdev] SQL in 101
Well, Linux is slowly becoming just one chunk of the infrastructure. I.e., MQ and SQL are almost becoming mandatory services for IaaS, and unavoidable. That said, I'd still argue it's LPIC-2, for now. - bjs On Wed, Feb 11, 2015 at 12:45 PM, Hendrik Jan Thomassen h...@atcomputing.nl wrote: Matthew Rice wrote: My own personal reasons for not hating it in the objectives is that I've seen a few times where management want to get reports out of a DB and they turn to the techs to help them with that task. in particular, having Excel/*Office connecting to the DB and then trying to figure out some simple queries. This exactly illustrates my point that SQL as such has nothing to do with Linux system administration, but is just another application domain. In this case: use of computers for business applications. There are so many other uses for a computer, even with Linux :-) The Linux OS is the common denominator under a plethora of different application domains: business administration, telecom, science, numerical control, web serving, ... ... ... I.m.h.o. the LPI certification should restrict itself to this common denominator under all application domains. -- Hendrik-Jan Thomassen h...@atcomputing.nl AT Computing Linux/UNIXperts, opleiders oplossers Tel +31 24 352 72 82 Kerkenbos 1238Tel cursussecretariaat: +31 24 352 72 72 6546 BE Nijmegen Fax +31 24 352 72 92 i...@atcomputing.nl www.atcomputing.nl 'If you think education is expensive, try ignorance.' ___ lpi-examdev mailing list lpi-examdev@lpi.org http://list.lpi.org/cgi-bin/mailman/listinfo/lpi-examdev -- -- Bryan J Smith - http://www.linkedin.com/in/bjsmith ___ lpi-examdev mailing list lpi-examdev@lpi.org http://list.lpi.org/cgi-bin/mailman/listinfo/lpi-examdev
Re: [lpi-examdev] SQL in LPIC 1
Am 11.02.2015 um 14:56 schrieb Fabian Thorns: As this is usually not the default I wouldn't expect many people really using it. Exactly! ;-) ___ lpi-examdev mailing list lpi-examdev@lpi.org http://list.lpi.org/cgi-bin/mailman/listinfo/lpi-examdev
Re: [lpi-examdev] SQL in LPIC 1
On Wed, Feb 11, 2015 at 8:16 AM, Anselm Lingnau anselm.lingnau+exam...@linupfront.de wrote: Anyway, that's what I was told at the time. Maybe Matt can shed more light on the actual rationale of adding SQL to LPIC-1. After all, he was there and I wasn't ;^). The way LPI figures out exam objectives does suggest that the issue must have come up during the JTA. As I recall, it was always a controversial choice to include it. The JTA showed that there was some interest but it wasn't universal. My own personal reasons for not hating it in the objectives is that I've seen a few times where management want to get reports out of a DB and they turn to the techs to help them with that task. in particular, having Excel/*Office connecting to the DB and then trying to figure out some simple queries. Regards, --matt -- G. Matthew Rice m...@starnix.com gpg id: EF9AAD20 ___ lpi-examdev mailing list lpi-examdev@lpi.org http://list.lpi.org/cgi-bin/mailman/listinfo/lpi-examdev
Re: [lpi-examdev] SQL in LPIC 1
Hi there, On 02/11/2015 02:16 PM, Anselm Lingnau wrote: Simone Piccardi picca...@truelite.it wrote: Could you provide some examples? In my (limited) experience almost all programs I'm using just log to text file (journald beeing the main exception). Apache can write its access log to an SQL database, for example. AFAIK, the modern syslog replacements (like rsyslogd or syslogd-ng) can also be configured to use an SQL database backend rather than the traditional text files. Reasons why one would want to do this include (a) speed and (b) ease of finding things, both of which aren't exactly among the strengths of the text-file based approach (as the journald developers, too, are fond of pointing out). Note that getting these tools to actually log to an SQL database is not part of the LPIC-1 exam (and rightly so, as far as I'm concerned). I presume the general idea is that a “junior” sysadmin might end up working in a place where senior staff have set things up that way, and a junior employee would need basic familiarity with SQL in order to look at logging data – much like LPIC-1 doesn't require a candidate to be able to install and configure an MTA from scratch, just to deal with it once it's there. As this is usually not the default I wouldn't expect many people really using it. If, on the other hand, someone touches these defaults, than it would be most likely to implement tools like logstash to centrally log, normalize, aggregate and analyze the log data. This, however, would be far beyond the LPIC-1 focus.In case someone would have set this up the junior administrator would find himself in front of an interface like kibana which requires some additional learning time anyway. Anyway, that's what I was told at the time. Maybe Matt can shed more light on the actual rationale of adding SQL to LPIC-1. After all, he was there and I wasn't ;^). The way LPI figures out exam objectives does suggest that the issue must have come up during the JTA. Would be interesting to know where this objective's roots are, yeah :-) This objective has already been marked in the Future consideration section of the LPIC-1 wiki page, so it will for sure pop up again during the next review of the objectives. Fabian (who would still vote for dropping SQL once we get the chance to) ___ lpi-examdev mailing list lpi-examdev@lpi.org http://list.lpi.org/cgi-bin/mailman/listinfo/lpi-examdev
Re: [lpi-examdev] SQL in 101
I think that SQL knowledge is important when dealing with web services. But since other services like Apache are treated in LPIC-2, maybe SQL (along with some specific service management of packages like MySQL or MariaDB), should also be include in LPIC-2 and not in LPIC-1. My $0.02 ___ lpi-examdev mailing list lpi-examdev@lpi.org http://list.lpi.org/cgi-bin/mailman/listinfo/lpi-examdev
Re: [lpi-examdev] Suggestion for 105.3 (Exam 101) mysqldump
This would be nice for you ! http://www.oss-db.jp/outline/eng_index.shtml On 2015/02/10 23:59, G. Matthew Rice wrote: On Tue, Feb 10, 2015 at 9:58 AM, Harald Maaßen har...@nwa-net.de wrote: There are only funny looking characters and pictures on that page. ;-) This doesn't get all of those thingies but it helps: https://translate.google.com/translate?sl=jatl=enjs=yprev=_thl=enie=UTF-8u=http%3A%2F%2Fwww.oss-db.jp%2Fedit-text= -- Toru Nakatani / LPI-Japan ___ lpi-examdev mailing list lpi-examdev@lpi.org http://list.lpi.org/cgi-bin/mailman/listinfo/lpi-examdev
Re: [lpi-examdev] lpi-examdev Digest, Vol 85, Issue 12
/listinfo/lpi-examdev -- *Disclaimer:* Dit bericht (inclusief de eventuele bijlagen) is vertrouwelijk. Wanneer u dit bericht ten onrechte heeft ontvangen, dient u de afzender hiervan onmiddellijk per kerende e-mail op de hoogte te brengen en dit bericht te verwijderen uit uw systeem. Elk onbevoegd gebruik en/of onbevoegde verspreiding van dit bericht is niet toegestaan. U wordt erop gewezen dat e-mailberichten aan wijziging onderhevig kunnen zijn. Voor al onze aanbiedingen en of offerte(s) zijn onze algemene voorwaarden van toepassing. Deze voorwaarden zijn gedeponeerd bij de KvK te Utrecht. Onze voorwaarden kunnen op verzoek tevens toegezonden worden. TenICT is niet aansprakelijk voor de onjuiste en onvolledige overdracht van de informatie in dit bericht noch voor mogelijke vertraging in de ontvangst van dit bericht of schade aan uw systeem als gevolg van dit bericht. TenICT staat er niet voor in dat de integriteit van dit bericht behouden is gebleven noch dat dit bericht vrij is van virussen, niet is onderschept of vatbaar is geweest voor tussenkomst (door derden). -- next part -- An HTML attachment was scrubbed... URL: http://list.lpi.org/cgi-bin/mailman/private/lpi-examdev/attachments/20150211 /bd6fa0ef/attachment-0001.htm -- Message: 3 Date: Wed, 11 Feb 2015 14:33:36 -0500 From: Bryan J Smith b.j.sm...@ieee.org Subject: Re: [lpi-examdev] SQL in 101 To: This is the lpi-examdev mailing list. lpi-examdev@lpi.org Message-ID: cad5acgjl+ejzmcjlyfgu3ifuerzro5ep_1erhyshrpljacc...@mail.gmail.com Content-Type: text/plain; charset=UTF-8 Well, Linux is slowly becoming just one chunk of the infrastructure. I.e., MQ and SQL are almost becoming mandatory services for IaaS, and unavoidable. That said, I'd still argue it's LPIC-2, for now. - bjs On Wed, Feb 11, 2015 at 12:45 PM, Hendrik Jan Thomassen h...@atcomputing.nl wrote: Matthew Rice wrote: My own personal reasons for not hating it in the objectives is that I've seen a few times where management want to get reports out of a DB and they turn to the techs to help them with that task. in particular, having Excel/*Office connecting to the DB and then trying to figure out some simple queries. This exactly illustrates my point that SQL as such has nothing to do with Linux system administration, but is just another application domain. In this case: use of computers for business applications. There are so many other uses for a computer, even with Linux :-) The Linux OS is the common denominator under a plethora of different application domains: business administration, telecom, science, numerical control, web serving, ... ... ... I.m.h.o. the LPI certification should restrict itself to this common denominator under all application domains. -- Hendrik-Jan Thomassen h...@atcomputing.nl AT Computing Linux/UNIXperts, opleiders oplossers Tel +31 24 352 72 82 Kerkenbos 1238Tel cursussecretariaat: +31 24 352 72 72 6546 BE Nijmegen Fax +31 24 352 72 92 i...@atcomputing.nl www.atcomputing.nl 'If you think education is expensive, try ignorance.' ___ lpi-examdev mailing list lpi-examdev@lpi.org http://list.lpi.org/cgi-bin/mailman/listinfo/lpi-examdev -- -- Bryan J Smith - http://www.linkedin.com/in/bjsmith -- Message: 4 Date: Wed, 11 Feb 2015 21:26:23 +0100 From: Alexandru Juncu al...@linux.com Subject: Re: [lpi-examdev] SQL in 101 To: This is the lpi-examdev mailing list. lpi-examdev@lpi.org Message-ID: CAPhGq=zc-vrffnhk5kqzwjww3tjjcdmb3e_5howivzo6kzt...@mail.gmail.com Content-Type: text/plain; charset=UTF-8 I think that SQL knowledge is important when dealing with web services. But since other services like Apache are treated in LPIC-2, maybe SQL (along with some specific service management of packages like MySQL or MariaDB), should also be include in LPIC-2 and not in LPIC-1. My $0.02 -- Message: 5 Date: Thu, 12 Feb 2015 12:49:59 +0900 From: Toru Nakatani nakat...@lpi.or.jp Subject: Re: [lpi-examdev] Suggestion for 105.3 (Exam 101) mysqldump To: lpi-examdev@lpi.org Message-ID: 54dc22e7@lpi.or.jp Content-Type: text/plain; charset=utf-8 This would be nice for you ! http://www.oss-db.jp/outline/eng_index.shtml On 2015/02/10 23:59, G. Matthew Rice wrote: On Tue, Feb 10, 2015 at 9:58 AM, Harald Maa?en har...@nwa-net.de wrote: There are only funny looking characters and pictures on that page. ;-) This doesn't get all of those thingies but it helps: https://translate.google.com/translate?sl=jatl=enjs=yprev=_thl=en; ie=UTF-8u=http%3A%2F%2Fwww.oss-db.jp%2Fedit-text= -- Toru Nakatani / LPI-Japan -- ___ lpi-examdev mailing list lpi-examdev@lpi.org http://list.lpi.org/cgi-bin/mailman/listinfo/lpi-examdev End of lpi-examdev
Re: [lpi-examdev] SQL in LPIC 1
Fabian Thorns fab...@thorns.it wrote: I'm not sure why we have SQL on the exams right not, ISTR that this was originally added because many programs these days offer logging into SQL databases, and system administrators should be able to formulate SQL queries in order to get at these logs. In addition, many programs these days use SQLite as a lightweight structured method for storing configuration and data files, and it is frequently useful for a system administrator to be able to access and manipulate that information. The SQL required in LPIC-1 isn't exactly rocket science, and it is fairly well-defined and limited as LPI exam topics go. (Note that the LPI objectives do not require knowledge of the DDL.) I don't have a problem with this being on the exam. Anselm -- Anselm Lingnau ... Linup Front GmbH ... Linux-, Open-Source- Netz-Schulungen anselm.ling...@linupfront.de, +49(0)6151-9067-103, Fax -299, www.linupfront.de Linup Front GmbH, Postfach 100121, 64201 Darmstadt, Germany Sitz: Weiterstadt (AG Darmstadt, HRB7705), Geschäftsführer: Oliver Michel ___ lpi-examdev mailing list lpi-examdev@lpi.org http://list.lpi.org/cgi-bin/mailman/listinfo/lpi-examdev
Re: [lpi-examdev] SQL in LPIC 1
Simone Piccardi picca...@truelite.it wrote: Could you provide some examples? In my (limited) experience almost all programs I'm using just log to text file (journald beeing the main exception). Apache can write its access log to an SQL database, for example. AFAIK, the modern syslog replacements (like rsyslogd or syslogd-ng) can also be configured to use an SQL database backend rather than the traditional text files. Reasons why one would want to do this include (a) speed and (b) ease of finding things, both of which aren't exactly among the strengths of the text-file based approach (as the journald developers, too, are fond of pointing out). Note that getting these tools to actually log to an SQL database is not part of the LPIC-1 exam (and rightly so, as far as I'm concerned). I presume the general idea is that a “junior” sysadmin might end up working in a place where senior staff have set things up that way, and a junior employee would need basic familiarity with SQL in order to look at logging data – much like LPIC-1 doesn't require a candidate to be able to install and configure an MTA from scratch, just to deal with it once it's there. Anyway, that's what I was told at the time. Maybe Matt can shed more light on the actual rationale of adding SQL to LPIC-1. After all, he was there and I wasn't ;^). The way LPI figures out exam objectives does suggest that the issue must have come up during the JTA. Anselm -- Anselm Lingnau ... Linup Front GmbH ... Linux-, Open-Source- Netz-Schulungen anselm.ling...@linupfront.de, +49(0)6151-9067-103, Fax -299, www.linupfront.de Linup Front GmbH, Postfach 100121, 64201 Darmstadt, Germany Sitz: Weiterstadt (AG Darmstadt, HRB7705), Geschäftsführer: Oliver Michel ___ lpi-examdev mailing list lpi-examdev@lpi.org http://list.lpi.org/cgi-bin/mailman/listinfo/lpi-examdev
