Re: [blfs-dev] BLFS Systemd Additions
On 02/21/14 13:20, Bruce Dubbs wrote: Armin K. wrote: I know what you meant. I have no problems with shipping package specific notes for now. Maintaining seperate BLFS is something I can't do alone and maintaining same instructions in one branch, then generating two different books is something I don't know a) to do b) if it's possible. a. Can be cured. b. Yes, it's possible. Though I've never messed with it, it really doesn't look too difficult. Lookup use of xsl:when. Since this direction interests me, I'll take a look maybe next week. --DJ -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-dev] BLFS Systemd Additions
Le 22/02/2014 09:59, DJ Lucas a écrit : On 02/21/14 13:20, Bruce Dubbs wrote: Armin K. wrote: I know what you meant. I have no problems with shipping package specific notes for now. Maintaining seperate BLFS is something I can't do alone and maintaining same instructions in one branch, then generating two different books is something I don't know a) to do b) if it's possible. a. Can be cured. b. Yes, it's possible. Though I've never messed with it, it really doesn't look too difficult. Lookup use of xsl:when. Since this direction interests me, I'll take a look maybe next week. --DJ I can help with the xsl, and there is already some knowledge about variable books in the CLFS community, but I am somewhat worried that if we take this direction, all the BLFS editors will have to cope with both sets (systemd and sysvinit) of instructions. Pierre -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-dev] BLFS Systemd Additions
On 02/22/2014 01:57 PM, Pierre Labastie wrote: Le 22/02/2014 09:59, DJ Lucas a écrit : On 02/21/14 13:20, Bruce Dubbs wrote: Armin K. wrote: I know what you meant. I have no problems with shipping package specific notes for now. Maintaining seperate BLFS is something I can't do alone and maintaining same instructions in one branch, then generating two different books is something I don't know a) to do b) if it's possible. a. Can be cured. b. Yes, it's possible. Though I've never messed with it, it really doesn't look too difficult. Lookup use of xsl:when. Since this direction interests me, I'll take a look maybe next week. --DJ I can help with the xsl, and there is already some knowledge about variable books in the CLFS community, but I am somewhat worried that if we take this direction, all the BLFS editors will have to cope with both sets (systemd and sysvinit) of instructions. Pierre There are different ways than with playing with xsl (shell subsitutions and such, generating .xml files from .xml.in files using templates) but given that some already say that they wouldn't like systemd and sysv instructions in the same repository, I didn't speak up. As for maintenance, it would be still the same. systemd specific instructions are mostly related to bootscript part in more than 70% of the packages anyways so that wouldn't need to be touched for the time being. -- Note: My last name is not Krejzi. -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-dev] BLFS Systemd Additions
Date: Sat, 22 Feb 2014 14:20:08 +0100 From: Armin K. kre...@email.com To: BLFS Development List blfs-dev@linuxfromscratch.org Subject: Re: [blfs-dev] BLFS Systemd Additions . . There are different ways than with playing with xsl (shell subsitutions and such, generating .xml files from .xml.in files using templates) but ((We here completely bypass xml; much saner with just a lean BNF spec (incl e.g. don't-type-anything-twice), use lex/yacc on it to e.g. wrap all the (repetitive) build structure around it. (Also, really, do folks still e.g. edit dates manually in b/lfs xml ... ; that's nuts.) )) given that some already say that they wouldn't like systemd and sysv instructions in the same repository, I didn't speak up. As for I'd say that that - i.e. not mixing the repos yet - is probably prudent _overall_, for the time being at least - separate repos like for lfs, but kept substantially in-sync; and seeing a bit further down the line, if merging is feasible; and meantime you _do_ have a functioning ongoing sysd-blfs book. maintenance, it would be still the same. systemd specific instructions are mostly related to bootscript part in more than 70% of the packages anyways so that wouldn't need to be touched for the time being. That's partly why the original suggestion, that _instead_ - not additional to, but instead - of the time/resource spend that you did for the 'free-form' text/wiki notes, why not use that _same_ chunk of time/resource *instead* -- not additional to, but instead -- and keep your notes as changes to the blfs-7.4 xml, and publish those changes as sets of patches. You don't need to undertake any more burden than that. Those patch-sets would, I'm sure, be by far an even more helpful resource to folks than the text/wiki notes already are. rgds, akh -- Note: My last name is not Krejzi. -- -- -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-dev] BLFS Systemd Additions
Pierre Labastie wrote: Le 22/02/2014 09:59, DJ Lucas a écrit : On 02/21/14 13:20, Bruce Dubbs wrote: Armin K. wrote: I know what you meant. I have no problems with shipping package specific notes for now. Maintaining seperate BLFS is something I can't do alone and maintaining same instructions in one branch, then generating two different books is something I don't know a) to do b) if it's possible. a. Can be cured. b. Yes, it's possible. Though I've never messed with it, it really doesn't look too difficult. Lookup use of xsl:when. Since this direction interests me, I'll take a look maybe next week. --DJ I can help with the xsl, and there is already some knowledge about variable books in the CLFS community, but I am somewhat worried that if we take this direction, all the BLFS editors will have to cope with both sets (systemd and sysvinit) of instructions. I don't think so. If there are two roles added, systemd and sysv, then the sections so marked would be only rendered in the specific book. Sections without either marking would be rendered in both books. I would envision this to be done at the sectx level, but it could be done at a child tag too. I'm not sure if it could be done at the xi:include / level or not, but that would give some interesting alternatives. In this scenario, an editor would not alter the instructions for the book that he is not concerned with. We could try this out in a branch and see how it works before making a commitment. -- Bruce -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-dev] BLFS Systemd Additions
Armin K. wrote: There are different ways than with playing with xsl (shell subsitutions and such, generating .xml files from .xml.in files using templates) but given that some already say that they wouldn't like systemd and sysv instructions in the same repository, I didn't speak up. As for maintenance, it would be still the same. systemd specific instructions are mostly related to bootscript part in more than 70% of the packages anyways so that wouldn't need to be touched for the time being. And I suspect that 75% of the packages in the proposed alternate book would be identical. -- Bruce -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-dev] BLFS Systemd Additions
On 02/22/14 11:29, DJ Lucas wrote: Profiling is really what we are looking for, and we already have the functionality for two pass profiling in our Makefile for BLFS. See the attached patch. Oh, I forgot to mention, I didn't check to see if bind includes a unit file, it was just used as an example. --DJ -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-dev] BLFS Systemd Additions
Date: Fri, 21 Feb 2014 00:27:53 +0100 From: Armin K. kre...@email.com To: BLFS Development List blfs-dev@linuxfromscratch.org Subject: Re: [blfs-dev] BLFS Systemd Additions On 02/19/2014 11:00 PM, Armin K. wrote: Hello, I've taken some time to write modifications that are necessarry for the current BLFS book to get some packages to work with native systemd units or to utilize features that they can use from systemd components itself. The notes are available here if anyone wants to play with it. http://www.linuxfromscratch.org/~krejzi/notes.txt This is incredibly ugly to read, but I'm not very friendly with wikis and such to put them there. Note that instructions only up to IV. Networking for now. I hope to continue tomorrow since it's getting late now. Cheers Notes have been updated for remaining server packages. Only Iptables, CUPS and Cups Filters modifications remain to be added. The following packages need to be modified and/or (not) installed when using LFS systemd as a base. Chapter 3: The Bash Shell Startup Files . # + 58 pkgs. . Chapter 39: alsa-utils-1.0.27.2 If anyone cares enough to add the instructions to the wiki, let me know. Otherwise, I'll keep them at the same address. Might it be better all-round if you retained these as sets of patches against your own working copy of blfs book xml, and then apply/rebase them with mainline blfs book xml? That way, you kind-of get a de-facto blfs-systemd book? Yeah, I know it'd be likely not quite as straightforward as that. But, you're putting a non-trivial amount of resource expenditure into the above work: and then it's being stored/presented in a very un-structured way; thus, I'd suggest, wasting/undoing a non-trivial part of your effort. I'm aware of the issues last year whereby - if I may presume to word it - it seems you felt inter alia that your work was being wasted on mainstream blfs book; and so perhaps want to avoid getting back into that scenario. But, it doesn't have to be either _that_ or the present (wiki/notes) approach: I think that the suggest patches or similar structured (parseable/programmable) route be considered as a good intermediate option. From here, it looks like you've more-or-less got a blfs-systemd book there. Why not publish it just like for lfs-systemd? rgds, akh p.s. For the avoidance of doubt: I still think sysd has, to say the least, serious issues. However, I really think it's not good for such work as what you've done above, to be shovelled into largely-unstructured notes/wiki that makes it awkward to work with in an automated fashion. -- Note: My last name is not Krejzi. -- -- -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-dev] BLFS Systemd Additions
On 02/21/2014 11:40 AM, akhiezer wrote: Date: Fri, 21 Feb 2014 00:27:53 +0100 From: Armin K. kre...@email.com To: BLFS Development List blfs-dev@linuxfromscratch.org Subject: Re: [blfs-dev] BLFS Systemd Additions On 02/19/2014 11:00 PM, Armin K. wrote: Hello, I've taken some time to write modifications that are necessarry for the current BLFS book to get some packages to work with native systemd units or to utilize features that they can use from systemd components itself. The notes are available here if anyone wants to play with it. http://www.linuxfromscratch.org/~krejzi/notes.txt This is incredibly ugly to read, but I'm not very friendly with wikis and such to put them there. Note that instructions only up to IV. Networking for now. I hope to continue tomorrow since it's getting late now. Cheers Notes have been updated for remaining server packages. Only Iptables, CUPS and Cups Filters modifications remain to be added. The following packages need to be modified and/or (not) installed when using LFS systemd as a base. Chapter 3: The Bash Shell Startup Files . # + 58 pkgs. . Chapter 39: alsa-utils-1.0.27.2 If anyone cares enough to add the instructions to the wiki, let me know. Otherwise, I'll keep them at the same address. Might it be better all-round if you retained these as sets of patches against your own working copy of blfs book xml, and then apply/rebase them with mainline blfs book xml? That way, you kind-of get a de-facto blfs-systemd book? I've tried that approach (sort of) and failed because I couldn't keep up with all the changes and such. Note that using a systemd branch of blfs would also bring GNOME back and that would add a lot more packages and I'll be left by myself for those. Yeah, I know it'd be likely not quite as straightforward as that. But, you're putting a non-trivial amount of resource expenditure into the above work: and then it's being stored/presented in a very un-structured way; thus, I'd suggest, wasting/undoing a non-trivial part of your effort. I'm aware of the issues last year whereby - if I may presume to word it - it seems you felt inter alia that your work was being wasted on mainstream blfs book; and so perhaps want to avoid getting back into that scenario. But, it doesn't have to be either _that_ or the present (wiki/notes) approach: I think that the suggest patches or similar structured (parseable/programmable) route be considered as a good intermediate option. From here, it looks like you've more-or-less got a blfs-systemd book there. Why not publish it just like for lfs-systemd? rgds, akh p.s. For the avoidance of doubt: I still think sysd has, to say the least, serious issues. However, I really think it's not good for such work as what you've done above, to be shovelled into largely-unstructured notes/wiki that makes it awkward to work with in an automated fashion. I'm only one person and keeping up with LFS which is at least 10 times smaller and making sure it's perfect is hard enough. BLFS requires modifications to more packages than the entire LFS has. Easiest approach would be for both instructions to co-exist, with some kinds of role=systemd xml tags to indicate it's required for systemd and role=sysvinit to indicate it's required for sysv (mostly configuration parts). but I believe it has been said once that BLFS should not mix instructions for those two books, so I'm not going to try. -- Note: My last name is not Krejzi. -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-dev] BLFS Systemd Additions
Armin K. wrote: I'm only one person and keeping up with LFS which is at least 10 times smaller and making sure it's perfect is hard enough. That's an understatement. BLFS requires modifications to more packages than the entire LFS has. Easiest approach would be for both instructions to co-exist, with some kinds of role=systemd xml tags to indicate it's required for systemd and role=sysvinit to indicate it's required for sysv (mostly configuration parts). but I believe it has been said once that BLFS should not mix instructions for those two books, so I'm not going to try. I don't have a problem with using role to generate two versions of the book from the same source. It will take a lot of up front work though. -- Bruce -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-dev] BLFS Systemd Additions
On 02/21/2014 06:01 PM, Bruce Dubbs wrote: Armin K. wrote: I'm only one person and keeping up with LFS which is at least 10 times smaller and making sure it's perfect is hard enough. That's an understatement. BLFS requires modifications to more packages than the entire LFS has. Easiest approach would be for both instructions to co-exist, with some kinds of role=systemd xml tags to indicate it's required for systemd and role=sysvinit to indicate it's required for sysv (mostly configuration parts). but I believe it has been said once that BLFS should not mix instructions for those two books, so I'm not going to try. I don't have a problem with using role to generate two versions of the book from the same source. It will take a lot of up front work though. -- Bruce No, it's not two versions of the book, but one version with Do this if you are using sysvinit and do this if you are using systemd. I believe it was you who said that we shouldn't mix those when Ragnar suggested it back ... ugh long time ago anyways. -- Note: My last name is not Krejzi. -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-dev] BLFS Systemd Additions
Em 21-02-2014 14:16, Armin K. escreveu: On 02/21/2014 06:01 PM, Bruce Dubbs wrote: Armin K. wrote: I'm only one person and keeping up with LFS which is at least 10 times smaller and making sure it's perfect is hard enough. That's an understatement. BLFS requires modifications to more packages than the entire LFS has. Easiest approach would be for both instructions to co-exist, with some kinds of role=systemd xml tags to indicate it's required for systemd and role=sysvinit to indicate it's required for sysv (mostly configuration parts). but I believe it has been said once that BLFS should not mix instructions for those two books, so I'm not going to try. I don't have a problem with using role to generate two versions of the book from the same source. It will take a lot of up front work though. -- Bruce No, it's not two versions of the book, but one version with Do this if you are using sysvinit and do this if you are using systemd. I believe it was you who said that we shouldn't mix those when Ragnar suggested it back ... ugh long time ago anyways. The difference between BLFS and BLFS systemd should be along the same lines as LFS and LFS systemd. Each one do what is necessary for itself, unless asked by the other and agreed. And each one is most respectfull to the decisions of the other. Without that, life will be hell. -- []s, Fernando -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-dev] BLFS Systemd Additions
Armin K. wrote: On 02/21/2014 06:01 PM, Bruce Dubbs wrote: Armin K. wrote: I'm only one person and keeping up with LFS which is at least 10 times smaller and making sure it's perfect is hard enough. That's an understatement. BLFS requires modifications to more packages than the entire LFS has. Easiest approach would be for both instructions to co-exist, with some kinds of role=systemd xml tags to indicate it's required for systemd and role=sysvinit to indicate it's required for sysv (mostly configuration parts). but I believe it has been said once that BLFS should not mix instructions for those two books, so I'm not going to try. I don't have a problem with using role to generate two versions of the book from the same source. It will take a lot of up front work though. No, it's not two versions of the book, but one version with Do this if you are using sysvinit and do this if you are using systemd. I believe it was you who said that we shouldn't mix those when Ragnar suggested it back ... ugh long time ago anyways. What I said, or at least intended to say, was that users shouldn't be constantly reminded that if you have x, do y, otherwise z. I don't have an objection to doing that in the source by developers and creating the xsl to generate a 'standard' blfs version and a 'systemd' blfs version. -- Bruce -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-dev] BLFS Systemd Additions
On 02/21/2014 07:57 PM, Bruce Dubbs wrote: Armin K. wrote: On 02/21/2014 06:01 PM, Bruce Dubbs wrote: Armin K. wrote: I'm only one person and keeping up with LFS which is at least 10 times smaller and making sure it's perfect is hard enough. That's an understatement. BLFS requires modifications to more packages than the entire LFS has. Easiest approach would be for both instructions to co-exist, with some kinds of role=systemd xml tags to indicate it's required for systemd and role=sysvinit to indicate it's required for sysv (mostly configuration parts). but I believe it has been said once that BLFS should not mix instructions for those two books, so I'm not going to try. I don't have a problem with using role to generate two versions of the book from the same source. It will take a lot of up front work though. No, it's not two versions of the book, but one version with Do this if you are using sysvinit and do this if you are using systemd. I believe it was you who said that we shouldn't mix those when Ragnar suggested it back ... ugh long time ago anyways. What I said, or at least intended to say, was that users shouldn't be constantly reminded that if you have x, do y, otherwise z. I don't have an objection to doing that in the source by developers and creating the xsl to generate a 'standard' blfs version and a 'systemd' blfs version. -- Bruce I know what you meant. I have no problems with shipping package specific notes for now. Maintaining seperate BLFS is something I can't do alone and maintaining same instructions in one branch, then generating two different books is something I don't know a) to do b) if it's possible. -- Note: My last name is not Krejzi. -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-dev] BLFS Systemd Additions
On 02/21/2014 08:20 PM, Bruce Dubbs wrote: Armin K. wrote: I know what you meant. I have no problems with shipping package specific notes for now. Maintaining seperate BLFS is something I can't do alone and maintaining same instructions in one branch, then generating two different books is something I don't know a) to do b) if it's possible. a. Can be cured. b. Yes, it's possible. If you can give me few hints on how to do it, or even point me to the right places (I can't think of right term to search online) to look at, I might look at fixing that for 7.6 release. -- Bruce -- Note: My last name is not Krejzi. -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-dev] BLFS Systemd Additions
Date: Fri, 21 Feb 2014 20:04:15 +0100 From: Armin K. kre...@email.com To: BLFS Development List blfs-dev@linuxfromscratch.org Subject: Re: [blfs-dev] BLFS Systemd Additions . . I know what you meant. I have no problems with shipping package specific notes for now. Yes, but could they be shipped as, say, diffs/patches against e.g. blfs-7.4 release (just an example - but in any case a known baseline); so that folks can apply them as wanted ( against a known baseline - hence the 'blfs-7.4 rel' example). Current-format shipping is not making best use, results-wise, of the work that you have obviously done in obtaining that info: the info is not as readily re-usable as it really could be - and I'd expect could quite readily be, as the blfs-sysd changes that you've made look generally fairly 'clean'. Do you maintain your internal changes as changes to xml tree, or what; is it amenable to generating diffs/patches that folks could apply to main blfs xml? This is realy the crux of what I was meaning: can you generate such diffs 'at no(t much) extra cost', from the internal-format info that you're creating anyhow? Would that be better expenditure of your resources than writing up the large-ish text/wiki documents? Maintaining seperate BLFS is something I can't do alone If the blfs-sysd changes are avail as patches, then I'd expect folks'd come on-board more readily. and maintaining same instructions in one branch, then generating two different books is something I don't know a) to do b) if it's possible. Had expected here that there _would_ be two separate xml trees, at least for foreseeable, like for lfs. And then in time see how 'clean' the diffs between the two can be; and from there if want to merge. Didn't mean to be distracting folks away from blfs testing. akh -- Note: My last name is not Krejzi. -- -- -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-dev] BLFS Systemd Additions
On 02/21/2014 08:34 PM, akhiezer wrote: Date: Fri, 21 Feb 2014 20:04:15 +0100 From: Armin K. kre...@email.com To: BLFS Development List blfs-dev@linuxfromscratch.org Subject: Re: [blfs-dev] BLFS Systemd Additions . . I know what you meant. I have no problems with shipping package specific notes for now. Yes, but could they be shipped as, say, diffs/patches against e.g. blfs-7.4 release (just an example - but in any case a known baseline); so that folks can apply them as wanted ( against a known baseline - hence the 'blfs-7.4 rel' example). Current-format shipping is not making best use, results-wise, of the work that you have obviously done in obtaining that info: the info is not as readily re-usable as it really could be - and I'd expect could quite readily be, as the blfs-sysd changes that you've made look generally fairly 'clean'. Do you maintain your internal changes as changes to xml tree, or what; is it amenable to generating diffs/patches that folks could apply to main blfs xml? This is realy the crux of what I was meaning: can you generate such diffs 'at no(t much) extra cost', from the internal-format info that you're creating anyhow? Would that be better expenditure of your resources than writing up the large-ish text/wiki documents? Maintaining seperate BLFS is something I can't do alone If the blfs-sysd changes are avail as patches, then I'd expect folks'd come on-board more readily. and maintaining same instructions in one branch, then generating two different books is something I don't know a) to do b) if it's possible. Had expected here that there _would_ be two separate xml trees, at least for foreseeable, like for lfs. And then in time see how 'clean' the diffs between the two can be; and from there if want to merge. Didn't mean to be distracting folks away from blfs testing. akh Even patches require maintenance and given how fast the book changes, the notes I wrote might become obsolete sooner or later. Note: My last name is not Krejzi. -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-dev] BLFS Systemd Additions
Armin K. wrote: On 02/21/2014 08:20 PM, Bruce Dubbs wrote: Armin K. wrote: I know what you meant. I have no problems with shipping package specific notes for now. Maintaining seperate BLFS is something I can't do alone and maintaining same instructions in one branch, then generating two different books is something I don't know a) to do b) if it's possible. a. Can be cured. b. Yes, it's possible. If you can give me few hints on how to do it, or even point me to the right places (I can't think of right term to search online) to look at, I might look at fixing that for 7.6 release. It really is a matter of .xsl programming. That's not an easy language. You might want to start with http://www.w3schools.com/XSL/ and look at the LFS/BLS stylesheets. What we would end up doing is running xsltproc with either a defined variable or a completely different .xsl file. I can't say I'm an expert with xsl, but we can get it done with time. -- Bruce -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-dev] BLFS Systemd Additions
Em 21-02-2014 16:34, akhiezer escreveu: Had expected here that there _would_ be two separate xml trees, at least for foreseeable, like for lfs. And then in time see how 'clean' the diffs between the two can be; and from there if want to merge. Thanks, akhiezer. Tha is exactly what i think. What I wrote before is differences between LFS and LFS systemd should be also in LFS and BLFS systemd: one of the differences is two separate trees. I am *completely* against BLFS systemd inside BLFS tree. -- []s, Fernando -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-dev] BLFS Systemd Additions
Em 21-02-2014 18:04, Fernando de Oliveira escreveu: Em 21-02-2014 16:34, akhiezer escreveu: Had expected here that there _would_ be two separate xml trees, at least for foreseeable, like for lfs. And then in time see how 'clean' the diffs between the two can be; and from there if want to merge. Thanks, akhiezer. Tha is exactly what i think. What I wrote before is differences between LFS and LFS systemd should be also in LFS and BLFS systemd: one of the differences is two separate trees. I am *completely* against BLFS systemd inside BLFS tree. If mixing sysvint and systemd in the same tree works for LFS, then a _discussion_ to do the same with BLFS is acceptable. A discussion to decide if BLFS will be based only in systemd is acceptable. The status quo is acceptable. -- []s, Fernando -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-dev] BLFS Systemd Additions
On 02/19/2014 11:00 PM, Armin K. wrote: Hello, I've taken some time to write modifications that are necessarry for the current BLFS book to get some packages to work with native systemd units or to utilize features that they can use from systemd components itself. The notes are available here if anyone wants to play with it. http://www.linuxfromscratch.org/~krejzi/notes.txt This is incredibly ugly to read, but I'm not very friendly with wikis and such to put them there. Note that instructions only up to IV. Networking for now. I hope to continue tomorrow since it's getting late now. Cheers Notes have been updated for remaining server packages. Only Iptables, CUPS and Cups Filters modifications remain to be added. The following packages need to be modified and/or (not) installed when using LFS systemd as a base. Chapter 3: The Bash Shell Startup Files Chapter 4: acl-2.2.52 Chapter 4: attr-2.4.47 Chapter 4: ConsoleKit-0.4.6 Chapter 4: Cyrus SASL-2.1.26 Chapter 4: Iptables-1.4.21 Chapter 4: libcap-2.24 Chapter 4: MIT Kerberos V5-1.12.1 Chapter 4: OpenSSH-6.5p1 Chapter 4: Polkit-0.112 Chapter 4: Stunnel-4.56 Chapter 9: Expat-2.1.0 Chapter 11: Gperf-3.0.4 Chapter 11: Intltool-0.50.2 Chapter 12: acpid-2.0.21 Chapter 12: at-3.1.14 Chapter 12: autofs-5.0.8 Chapter 12: BlueZ-4.101 Chapter 12: Colord-1.0.6 Chapter 12: D-Bus-1.8.0 Chapter 12: Fcron-3.1.2 Chapter 12: GPM-1.20.7 Chapter 12: Sysstat-10.2.1 Chapter 12: Udev Extras (from systemd) Chapter 12: UDisks-2.1.2 Chapter 12: UPower-0.9.23 Chapter 13: Git-1.9.0 Chapter 13: Perl Modules: XML::Parser-2.41 Chapter 13: Running a Subversion Server Chapter 14: DHCP-4.3.0 Chapter 15: NFS-Utils-1.2.9 Chapter 15: ntp-4.2.6p5 Chapter 15: rpcbind-0.2.1 Chapter 15: rsync-3.1.0 Chapter 15: Samba-4.1.4 Chapter 15: wpa_supplicant-2.1 Chapter 16: Avahi-0.6.31 Chapter 16: NetworkManager-0.9.8.8 Chapter 16: Wicd-1.7.2.4 Chapter 20: Apache-2.4.7 Chapter 20: BIND-9.9.5 Chapter 20: ProFTPD-1.3.4d Chapter 20: vsftpd-3.0.2 Chapter 21: Dovecot-2.2.12 Chapter 21: Exim-4.82 Chapter 21: Postfix-2.11.0 Chapter 21: sendmail-8.14.8 Chapter 22: MariaDB-10.0.8 Chapter 22: MySQL-5.6.16 Chapter 22: PostgreSQL-9.3.2 Chapter 23: OpenLDAP-2.4.39 Chapter 23: Soprano-2.9.4 Chapter 23: Unbound-1.4.21 Chapter 23: Virtuoso-6.1.8 Chapter 23: xinetd-2.3.15 Chapter 28: Kde-workspace-4.11.6 Chapter 28: Starting KDE Chapter 32: xfce4-session-4.10.1 Chapter 34: LXSession-0.4.9.2 Chapter 39: alsa-utils-1.0.27.2 If anyone cares enough to add the instructions to the wiki, let me know. Otherwise, I'll keep them at the same address. -- Note: My last name is not Krejzi. -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
