Hi folks Working on a few minor issues related to the kernel packages, in particular, the need to have to mess around with the kernel-source tree before compiling any modules - An upgrade on the main build system has resulted in a shiny new set of key packages. The rtai-dev and kernel-headers packages are the only prerequisites for compiling kernel modules now. The change in the way kernel packages are produced has introduced a name change (kernel-image-2.6.12.6-magma is now linux-image-2.6.12.6-rtai) along with an increase in size for linux-headers-2.6.12.6-rtai (up by 1.4M). This is offset by dropping kernel-kbuild (355K). Mumblings from other quarters would suggest the addition of subversion to be useful, however, this adds another 1.4M to the final ISO. Along with the increase in size of the kernel packages, I'm at 630M for the ISO.. Question: Is subversion worth the additional space, should something be dropped in it's favour, or should I forget about reserving space for emc2 ? Regards, Paul. -- From the Klingon book of C: Klingon function calls do not have 'parameters' - they have 'arguments' - and they ALWAYS WIN THEM.
On Tuesday 27 December 2005 08:45, Paul wrote:
Hi folks
Working on a few minor issues related to the kernel packages, in particular, the need to have to mess around with the kernel-source tree before compiling any modules - An upgrade on the main build system has resulted in a shiny new set of key packages. The rtai-dev and kernel-headers packages are the only prerequisites for compiling kernel modules now. The change in the way kernel packages are produced has introduced a name change (kernel-image-2.6.12.6-magma is now linux-image-2.6.12.6-rtai) along with an increase in size for linux-headers-2.6.12.6-rtai (up by 1.4M). This is offset by dropping kernel-kbuild (355K).
Mumblings from other quarters would suggest the addition of subversion to be useful, however, this adds another 1.4M to the final ISO. Along with the increase in size of the kernel packages, I'm at 630M for the ISO..
Question: Is subversion worth the additional space, should something be dropped in it's favour, or should I forget about reserving space for emc2 ?
Well, if the new emc2 version is to be transfered from a cvs repo to an svn repo, then I'm in favor of enough of a svn kit to be able to keep it up2date. As to what to drop, I'm not familiar enough to have any really good, this could go, ideas. As long as apt-get is there, though, much of the rest of my concerns are only an ethernet cable away. I was disappointed that vim wasn't included in 4.30, but thats fixable so its just me mewling about it at the end of the day. I just wasn't aware that svn was being considered for the repo tool. My experience with it has been positive though. I hope you all had a merry Christmas, and will have a happy and prosperous new year.
Regards, Paul.
-- Cheers, Gene People having trouble with vz bouncing email to me should add the word 'online' between the 'verizon', and the dot which bypasses vz's stupid bounce rules. I do use spamassassin too. :-) Yahoo.com and AOL/TW attorneys please note, additions to the above message by Gene Heskett are: Copyright 2005 by Maurice Eugene Heskett, all rights reserved.
Hi Gene On Tuesday 27 December 2005 14:40, Gene Heskett wrote:
Well, if the new emc2 version is to be transfered from a cvs repo to an svn repo, then I'm in favor of enough of a svn kit to be able to keep it up2date. As to what to drop, I'm not familiar enough to have any really good, this could go, ideas. As long as apt-get is there, though, much of the rest of my concerns are only an ethernet cable away. I was disappointed that vim wasn't included in 4.30, but thats fixable so its just me mewling about it at the end of the day.
vim weighs in at an additional 4M (not as bad as emacs at 13.1), and rather than stiring up an editors war, I'd prefer to leave both of them out. For a lightweight CLI editor, you have nano, and kate serves as the heavyweight GUI editor. Personally, I use cedit (part of midnight commander). Debian's apt tools are part of the base system, so there is no chance of apt-get being thrown out. As for emc2 migrating to svn - It isn't going to happen any time soon. Sourceforge have recently started to trial subversion and do not plan on rolling it out across the system until March at the earliest. The inclusion of subversion in the BDI-4 builds is primarily for the people that use BDI-4 for non-EMC development.. Regards, Paul. -- From the Klingon book of C: Klingon function calls do not have 'parameters' - they have 'arguments' - and they ALWAYS WIN THEM.
On Tuesday 27 December 2005 10:22, Paul wrote:
Hi Gene
On Tuesday 27 December 2005 14:40, Gene Heskett wrote:
Well, if the new emc2 version is to be transfered from a cvs repo to an svn repo, then I'm in favor of enough of a svn kit to be able to keep it up2date. As to what to drop, I'm not familiar enough to have any really good, this could go, ideas. As long as apt-get is there, though, much of the rest of my concerns are only an ethernet cable away. I was disappointed that vim wasn't included in 4.30, but thats fixable so its just me mewling about it at the end of the day.
vim weighs in at an additional 4M (not as bad as emacs at 13.1), and rather than stiring up an editors war, I'd prefer to leave both of them out.
For a lightweight CLI editor, you have nano, and kate serves as the heavyweight GUI editor.
Kate may in some eyes be a heavyweight gui editor, but it has some warts I haven't found the right place to apply the acid to excise them. Its used here only under duress.
Personally, I use cedit (part of midnight commander).
That too, if only the blue screen blues could be reset. It works fine, but its control syntax doesn't seem 'right' to a vim user, which makes it slower because once I remember that I'm not using vim, I have to re-read everything to make sure an automatic vim response didn't mung the file. As for nano, I'm not fam with it at all, but may I presume there is a manpage for it also? I've used pico a couple of times, once after a box got rootkitted (old bind vulnerability) about 6 years ago, so the memory is hazy at best. The rootkitter left a copy of pico behind. Personally, as an old amiga user, I still miss the updated ced 4.20 thats on that old box in the basement. But thats history now.
Debian's apt tools are part of the base system, so there is no chance of apt-get being thrown out.
As for emc2 migrating to svn - It isn't going to happen any time soon. Sourceforge have recently started to trial subversion and do not plan on rolling it out across the system until March at the earliest. The inclusion of subversion in the BDI-4 builds is primarily for the people that use BDI-4 for non-EMC development..
Then that doesn't seem to be so important right now. And when that time comes, just sub svn for cvs in the iso & update the docs to reflect the change.
Regards, Paul.
-- Cheers, Gene People having trouble with vz bouncing email to me should add the word 'online' between the 'verizon', and the dot which bypasses vz's stupid bounce rules. I do use spamassassin too. :-) Yahoo.com and AOL/TW attorneys please note, additions to the above message by Gene Heskett are: Copyright 2005 by Maurice Eugene Heskett, all rights reserved.
participants (2)
-
Gene Heskett -
Paul