Re: [Sisuite-devel] systemimager-debian, systemimager 3.7.5 and debian sarge

2006-12-21 Thread dann frazier 
On Wed, Dec 20, 2006 at 07:59:15PM -0500, geoffroy vallee wrote:
> Hi Dann,
> 
> I will take into account all your remarks and actually, i will send soon new
> patches based new versions of the packages. I am currently testing these
> packages using OSCAR on Debian (project i am in charge of). These new
> packages includes the creation of the missing packages, i.e.,
> systemimager-bittorrent, systemimager-$(ARCH)initrd-template, and
> systemimager-imagemanip.

Sounds good, just please make sure to use a version string that will not 
conflict
with a real version string I may use in Debian. For example, if you
were doing 3.8.0 releases, please use 3.8.0-0geoff1, 3.8.0-0geoff222, etc.

> I will try to build packages for SID too since it will be usefull
> for you.

Thanks - keep in mind though that this is all just preparation for
sid, since 3.7 is still technical a devel stream. 3.8.0 would be the
first one I can upload to sid.

> Anyway, i will send small patches to the mailing list  when i will have done
> more testing with OSCAR (maybe in few days, i have to focus on other
> projects).

Thanks!

-- 
dann frazier


-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
___
sisuite-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/sisuite-devel

Re: [Sisuite-devel] systemimager-debian, systemimager 3.7.5 and debian sarge

2006-12-20 Thread geoffroy vallee 

Hi Dann,

I will take into account all your remarks and actually, i will send soon new
patches based new versions of the packages. I am currently testing these
packages using OSCAR on Debian (project i am in charge of). These new
packages includes the creation of the missing packages, i.e.,
systemimager-bittorrent, systemimager-$(ARCH)initrd-template, and
systemimager-imagemanip.

I will try to build packages for SID too since it will be usefull for you.
But you also have to know that i focus on debian stable since it is be the
version supported by OSCAR on Debian (i do not plan yet to try to push OSCAR
on Debian into the "official Debian release").

Anyway, i will send small patches to the mailing list  when i will have done
more testing with OSCAR (maybe in few days, i have to focus on other
projects).

2006/12/20, dann frazier <[EMAIL PROTECTED]>:


On Sun, Dec 10, 2006 at 01:46:23PM -0500, geoffroy vallee wrote:
> Hi all,
>
> I started to port systemimager 3.7.5 on Debian sarge based on the
> systemimager-debian repository. Please, find in attachment my first
> patches/files.
> The modifications allow one to create all standard packages modulo the
> following limitations:
> - the systemimager-bittorrent package is not complete, few files are
still
> missing, e.g., /etc/init.d/systemimager-server-bittorrent and
> /usr/bin/si_installbtimage,
> - the systemimager-i386initrd-template.package is still missing.
>
> Any idea how to fix these two issues? I did not have the time to big it
up
> because of a lack of time, the solution may be simple. I just wanted to
send
> out these modifications before to continue, just in case someone else is
> working on that. :-)
> I am not sure the patch 03 is the good way to patch the linux config
file.
> Let me know if you prefer to use another way.

Thanks a lot Geoffroy! I apologize for not responding sooner, I had
been filtering sisuite-devel to another folder and ignoring it as it
filled with mailman-admin stuff. I've updated my procmailrc so that I
should see messages to sisuite-devel in a timely fashion. (Thanks to
Joshua Cope for poking me about this thread).

Anyway, on with the comments.

The Bittorrent stuff looks good. Can you send me a single patch that
adds only the systemimager-bittorrent stuff in control.in and the
bittorrent part of the rules patch, as well as an entry in
debian/changelog that says something like "add systemimager-bittorrent
package"?

dch -a and svn diff are your friends here.

The other changes to control.in and rules look good too, and all seem
to be of the category of "updating version strings for 3.7.5". So,
similar to the above, can you send me a diff with just those other
changes (dependency changes, version string)? I don't think we need an
explicit changelog entry for this one, since it falls under updating
to the new upstream.

As for the kernel updates, 2.6.18 is now in sid, so please use that
version. And, can you combine the config changes and the kernel.rul
changes in a single patch (w/ a debian/changelog entry).

Some meta comments...
I'd prefer it if you sent each patch in a separate e-mail, and include
the patch inline (as opposed to an attachment). Essentially, same
rules as lkml. The reason is that it makes it easier for me to reply
to specific code changes inline (you'll see a cut & pasted the ones
above), and that it makes it easier to discuss patches because a
mail-per-patch means that discussions of those patches are in
separate, easier-to-follow threads. Also, as I've implied above,
patches that do one logical thing and touch multiple files are
preferred over patches that do multiple things to a single file. That
way if we decide to, say drop bittorrent support, we can easily just
revert that changeset w/o affecting other functionality.

Thanks a lot Geoffroy, this work is very appreciated. Let me know if
you have any questions about the above.

--
dann frazier


-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV___
sisuite-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/sisuite-devel

Re: [Sisuite-devel] systemimager-debian, systemimager 3.7.5 and debian sarge

2006-12-20 Thread dann frazier 
On Sun, Dec 10, 2006 at 01:46:23PM -0500, geoffroy vallee wrote:
> Hi all,
> 
> I started to port systemimager 3.7.5 on Debian sarge based on the
> systemimager-debian repository. Please, find in attachment my first
> patches/files.
> The modifications allow one to create all standard packages modulo the
> following limitations:
> - the systemimager-bittorrent package is not complete, few files are still
> missing, e.g., /etc/init.d/systemimager-server-bittorrent and
> /usr/bin/si_installbtimage,
> - the systemimager-i386initrd-template.package is still missing.
> 
> Any idea how to fix these two issues? I did not have the time to big it up
> because of a lack of time, the solution may be simple. I just wanted to send
> out these modifications before to continue, just in case someone else is
> working on that. :-)
> I am not sure the patch 03 is the good way to patch the linux config file.
> Let me know if you prefer to use another way.

Thanks a lot Geoffroy! I apologize for not responding sooner, I had
been filtering sisuite-devel to another folder and ignoring it as it
filled with mailman-admin stuff. I've updated my procmailrc so that I
should see messages to sisuite-devel in a timely fashion. (Thanks to
Joshua Cope for poking me about this thread).

Anyway, on with the comments.

The Bittorrent stuff looks good. Can you send me a single patch that
adds only the systemimager-bittorrent stuff in control.in and the
bittorrent part of the rules patch, as well as an entry in
debian/changelog that says something like "add systemimager-bittorrent
package"?

dch -a and svn diff are your friends here.

The other changes to control.in and rules look good too, and all seem
to be of the category of "updating version strings for 3.7.5". So,
similar to the above, can you send me a diff with just those other
changes (dependency changes, version string)? I don't think we need an
explicit changelog entry for this one, since it falls under updating
to the new upstream.

As for the kernel updates, 2.6.18 is now in sid, so please use that
version. And, can you combine the config changes and the kernel.rul
changes in a single patch (w/ a debian/changelog entry).

Some meta comments...
I'd prefer it if you sent each patch in a separate e-mail, and include
the patch inline (as opposed to an attachment). Essentially, same
rules as lkml. The reason is that it makes it easier for me to reply
to specific code changes inline (you'll see a cut & pasted the ones
above), and that it makes it easier to discuss patches because a
mail-per-patch means that discussions of those patches are in
separate, easier-to-follow threads. Also, as I've implied above,
patches that do one logical thing and touch multiple files are
preferred over patches that do multiple things to a single file. That
way if we decide to, say drop bittorrent support, we can easily just
revert that changeset w/o affecting other functionality.

Thanks a lot Geoffroy, this work is very appreciated. Let me know if
you have any questions about the above.

-- 
dann frazier


-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
___
sisuite-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/sisuite-devel

Re: [Sisuite-devel] systemimager-debian, systemimager 3.7.5 and debian sarge

2006-12-20 Thread dann frazier 
On Sun, Dec 17, 2006 at 10:15:52PM -0500, geoffroy vallee wrote:
> Hi all,
> 
> The package creation is based on the kernel version shipped with Debian. I
> do not want to change the kernel by default. It is the approach selected by
> Dann and i think it is the best one. Debian developers spend a lot of time
> to ship a kernel coherent for the distribution, i think it is a bad idea to
> want to change that.

The reason for this is that we try to keep all kernels built within
Debian on the same kernel version. This means we can all share the
same linux-source- package, which is the only place that needs to be
patched for legal issues/security fixes, etc.

The fact that this is currently 2.6.18 is a temporary thing, and no
release of Debian will actually ship with that. Since 3.6 is the
latest stable release of systemimager, that is the version that will
ship in etch (unfortunately). Since 3.6 requires devfs support, I had
to deviate from the single-kernel-source thing to use an older kernel
that supports devfs, 2.6.12 (also, unfortunately).

So, once 3.8 releases we can actually upload it to sid, and it should
track whatever the latest source is. Debian sid usually gets an upload
of the newest upstream kernel source within 24 hours of its
release. The exception is when we are frozen for a release, like right
now. In other words, by the time we can upload systemimager 3.8, we
will be able to use a newer kernel.

-- 
dann frazier


-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
___
sisuite-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/sisuite-devel

Re: [Sisuite-devel] systemimager-debian, systemimager 3.7.5 and debian sarge

2006-12-18 Thread geoffroy vallee 

Hi all,

I perfectly understand your position but as i said before, it seems to me
that this is the procedure selected by Dann (but maybe i missed something).
I do not disagree with that approach (keeping the same kernel for
everything) and Dann did a great job in creating scripts to ease the
creation of new Debian packages.
To change that, more work has to be done, i do not feel confortable doing
that without a strong collaboration with Dann (i am only a contributor, i am
not here to brake everything in sis-debian) and actually i do not really
have the time for that right now.

To summarize, i have to admit that currently i only want something that
works on Debian and that can be used in OSCARonDebian. If you want to modify
the way stuff are done on Debian, please also contact Dann, he is still _the
guy_ for sis on Debian (but i will be happy to participate to any
discussions/modifications). Currently I focus on creating usable packages,
nothing more.

Sorry to not be able to give a more constructive answer but as i said, i am
still a new contributor in the project, i do not think i can really reply to
this kind of questions.

Regards,

2006/12/18, Erich Focht <[EMAIL PROTECTED]>:


On Monday 18 December 2006 18:34, Joshua Cope wrote:
> Oops.. perhaps I was unclear; I think Erich and I are in violent
agreement.

Oh, sorry then...

> For a given SystemImager version, I would like the default, non-UYOK
> kernel to be the same on all Linux distributions. I'd like to create
> loadable modules for, say, SystemImager 3.7.4-1, without worrying about
> which distribution the imageserver is running.

This actually shows one weakness of our approach: if you want to produce a
special kernel module for a particular systemimager version, you'll need
to
somehow produce the patched kernel source tree and build your module
against
it. Having something like a systemimager-kernel-devel package would be
helpful
in such cases. Not sure whether a patched and configured kernel tree is
just
made with some simple "make" target...

Regards,
Erich

>
>- Josh
>
>
> Erich Focht wrote:
> > On Monday 18 December 2006 17:57, Joshua Cope wrote:
> >
> >> Let me add another vote for keeping the kernel version consistent.
> >>
> >
> > Not sure what you mean here: do you want to install with the same
kernel as on
> > the target OS? You can do it with UYOK.
> >
> > If you just join in and request systemimager to use the debian kernel,
than
> > please have in mind that debian is just one rather unimportant
distribution
> > (** me running and hiding ** ;-) . Adopting this strategy means that
you need
> > a kernel per distribution. No, you just need every kernel which was
ever used
> > in any distribution.
> >
> >
> >> During installation, I load custom device drivers onto my clients
after
> >> booting. It's nice to know that Systemimager version X.Y.Z always
> >> creates boot images with kernel version V. I'd rather not have to
check
> >> both the SystemImager version and the imageserver distribution to
figure
> >> out which kernel I'm going to get.
> >>
> >
> > If your custom module is in the right place inside the image (the
correct
> > /lib/modules/... path), all will be fine. systemconfigurator will
create
> > initrd images for every kernel it detects in /boot.
> >
> > Erich
> >
> >
> >>- Josh
> >>
> >
> >
> >
> >
>
>
>


-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share
your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
___
sisuite-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/sisuite-devel

-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV___
sisuite-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/sisuite-devel

Re: [Sisuite-devel] systemimager-debian, systemimager 3.7.5 and debian sarge

2006-12-18 Thread Erich Focht 
On Monday 18 December 2006 18:34, Joshua Cope wrote:
> Oops.. perhaps I was unclear; I think Erich and I are in violent agreement.

Oh, sorry then...

> For a given SystemImager version, I would like the default, non-UYOK 
> kernel to be the same on all Linux distributions. I'd like to create 
> loadable modules for, say, SystemImager 3.7.4-1, without worrying about 
> which distribution the imageserver is running.

This actually shows one weakness of our approach: if you want to produce a
special kernel module for a particular systemimager version, you'll need to
somehow produce the patched kernel source tree and build your module against
it. Having something like a systemimager-kernel-devel package would be helpful
in such cases. Not sure whether a patched and configured kernel tree is just
made with some simple "make" target...

Regards,
Erich

> 
>- Josh
> 
> 
> Erich Focht wrote:
> > On Monday 18 December 2006 17:57, Joshua Cope wrote:
> >   
> >> Let me add another vote for keeping the kernel version consistent. 
> >> 
> >
> > Not sure what you mean here: do you want to install with the same kernel as 
> > on
> > the target OS? You can do it with UYOK.
> >
> > If you just join in and request systemimager to use the debian kernel, than
> > please have in mind that debian is just one rather unimportant distribution
> > (** me running and hiding ** ;-) . Adopting this strategy means that you 
> > need
> > a kernel per distribution. No, you just need every kernel which was ever 
> > used
> > in any distribution. 
> >
> >   
> >> During installation, I load custom device drivers onto my clients after 
> >> booting. It's nice to know that Systemimager version X.Y.Z always 
> >> creates boot images with kernel version V. I'd rather not have to check 
> >> both the SystemImager version and the imageserver distribution to figure 
> >> out which kernel I'm going to get.
> >> 
> >
> > If your custom module is in the right place inside the image (the correct
> > /lib/modules/... path), all will be fine. systemconfigurator will create
> > initrd images for every kernel it detects in /boot.
> >
> > Erich
> >
> >   
> >>- Josh
> >> 
> >
> >
> >
> >   
> 
> 
> 


-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
___
sisuite-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/sisuite-devel

Re: [Sisuite-devel] systemimager-debian, systemimager 3.7.5 and debian sarge

2006-12-18 Thread Joshua Cope 
Oops.. perhaps I was unclear; I think Erich and I are in violent agreement.

For a given SystemImager version, I would like the default, non-UYOK 
kernel to be the same on all Linux distributions. I'd like to create 
loadable modules for, say, SystemImager 3.7.4-1, without worrying about 
which distribution the imageserver is running.

   - Josh


Erich Focht wrote:
> On Monday 18 December 2006 17:57, Joshua Cope wrote:
>   
>> Let me add another vote for keeping the kernel version consistent. 
>> 
>
> Not sure what you mean here: do you want to install with the same kernel as on
> the target OS? You can do it with UYOK.
>
> If you just join in and request systemimager to use the debian kernel, than
> please have in mind that debian is just one rather unimportant distribution
> (** me running and hiding ** ;-) . Adopting this strategy means that you need
> a kernel per distribution. No, you just need every kernel which was ever used
> in any distribution. 
>
>   
>> During installation, I load custom device drivers onto my clients after 
>> booting. It's nice to know that Systemimager version X.Y.Z always 
>> creates boot images with kernel version V. I'd rather not have to check 
>> both the SystemImager version and the imageserver distribution to figure 
>> out which kernel I'm going to get.
>> 
>
> If your custom module is in the right place inside the image (the correct
> /lib/modules/... path), all will be fine. systemconfigurator will create
> initrd images for every kernel it detects in /boot.
>
> Erich
>
>   
>>- Josh
>> 
>
>
>
>   



-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
___
sisuite-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/sisuite-devel

Re: [Sisuite-devel] systemimager-debian, systemimager 3.7.5 and debian sarge

2006-12-18 Thread Erich Focht 
On Monday 18 December 2006 17:57, Joshua Cope wrote:
> Let me add another vote for keeping the kernel version consistent. 

Not sure what you mean here: do you want to install with the same kernel as on
the target OS? You can do it with UYOK.

If you just join in and request systemimager to use the debian kernel, than
please have in mind that debian is just one rather unimportant distribution
(** me running and hiding ** ;-) . Adopting this strategy means that you need
a kernel per distribution. No, you just need every kernel which was ever used
in any distribution. 

> During installation, I load custom device drivers onto my clients after 
> booting. It's nice to know that Systemimager version X.Y.Z always 
> creates boot images with kernel version V. I'd rather not have to check 
> both the SystemImager version and the imageserver distribution to figure 
> out which kernel I'm going to get.

If your custom module is in the right place inside the image (the correct
/lib/modules/... path), all will be fine. systemconfigurator will create
initrd images for every kernel it detects in /boot.

Erich

> 
>- Josh



-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
___
sisuite-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/sisuite-devel

Re: [Sisuite-devel] systemimager-debian, systemimager 3.7.5 and debian sarge

2006-12-18 Thread Joshua Cope 
Let me add another vote for keeping the kernel version consistent. 
During installation, I load custom device drivers onto my clients after 
booting. It's nice to know that Systemimager version X.Y.Z always 
creates boot images with kernel version V. I'd rather not have to check 
both the SystemImager version and the imageserver distribution to figure 
out which kernel I'm going to get.

   - Josh



-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
___
sisuite-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/sisuite-devel

Re: [Sisuite-devel] systemimager-debian, systemimager 3.7.5 and debian sarge

2006-12-18 Thread Erich Focht 
Hi,

I think this is just a small confusion on Geoffroy's side. The systemimager
kernel has nothing to do with the Debian kernel, it's just used for deployment
and is common to any distro. If one wants to install with the OS kernel of the
master node, he can still use UYOK.

Regards,
Erich

On Monday 18 December 2006 10:06, Andrea Righi wrote:
> I disagree. Even if you choose to use a Debian for the image server you
> can install RH, SuSE, Mandriva, etc images. The kernel shipped with
> systemimager is (should be) a general purpose kernel tested with a lot
> of distro and not a kernel focused on Debian only. Moreover remember
> that that kernel is totally independent from the kernel that runs on the
> image server, it's a kind of distro embedded in systemimager and for
> this reason the kernel must be coherent with all the internal
> systemimager components, not with the external environment.
> 
> Anyway, this is my point of view, and I want to say that I really
> appreciate your work for the debian porting. We really need this
> support! ;-)
> 
> Regards,
> -Andrea
> 
> geoffroy vallee wrote:
> > Hi all,
> > 
> > The package creation is based on the kernel version shipped with Debian.
> > I do not want to change the kernel by default. It is the approach
> > selected by Dann and i think it is the best one. Debian developers spend
> > a lot of time to ship a kernel coherent for the distribution, i think it
> > is a bad idea to want to change that.
> > 
> > If someone wants to change that, i think the person has to take contact
> > with the Debian team in charge of the kernel packaging or, other
> > solution, create a new package and port all driver packages available in
> > Debian. But clearly, i do not want to do that. :-)
> > 
> > Moreover, remember, if you want to include a package within the official
> > Debian distribution and if you package is based on the kernel, you must
> > use the kernel by default.
> > 
> > Regards,
> > 
> > 2006/12/17, Erich Focht <[EMAIL PROTECTED] >:
> > 
> > On Sunday 17 December 2006 11:40, Andrea Righi wrote:
> > > Instead, I've another question... regarding patch 02 I've not
> > understood
> > > why you changed the default kernel version. The 2.6.18.1
> >  has been
> > > strongly tested and it seems to work well with all the other
> > > systemimager components...
> > 
> > Indeed, we should rather move forward in the kernel versions, not
> > backwards. In average this brings us more and better device drivers
> > support.
> > 
> > Regards,
> > Erich


-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
___
sisuite-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/sisuite-devel

Re: [Sisuite-devel] systemimager-debian, systemimager 3.7.5 and debian sarge

2006-12-18 Thread Andrea Righi 
I disagree. Even if you choose to use a Debian for the image server you
can install RH, SuSE, Mandriva, etc images. The kernel shipped with
systemimager is (should be) a general purpose kernel tested with a lot
of distro and not a kernel focused on Debian only. Moreover remember
that that kernel is totally independent from the kernel that runs on the
image server, it's a kind of distro embedded in systemimager and for
this reason the kernel must be coherent with all the internal
systemimager components, not with the external environment.

Anyway, this is my point of view, and I want to say that I really
appreciate your work for the debian porting. We really need this
support! ;-)

Regards,
-Andrea

geoffroy vallee wrote:
> Hi all,
> 
> The package creation is based on the kernel version shipped with Debian.
> I do not want to change the kernel by default. It is the approach
> selected by Dann and i think it is the best one. Debian developers spend
> a lot of time to ship a kernel coherent for the distribution, i think it
> is a bad idea to want to change that.
> 
> If someone wants to change that, i think the person has to take contact
> with the Debian team in charge of the kernel packaging or, other
> solution, create a new package and port all driver packages available in
> Debian. But clearly, i do not want to do that. :-)
> 
> Moreover, remember, if you want to include a package within the official
> Debian distribution and if you package is based on the kernel, you must
> use the kernel by default.
> 
> Regards,
> 
> 2006/12/17, Erich Focht <[EMAIL PROTECTED] >:
> 
> On Sunday 17 December 2006 11:40, Andrea Righi wrote:
> > Instead, I've another question... regarding patch 02 I've not
> understood
> > why you changed the default kernel version. The 2.6.18.1
>  has been
> > strongly tested and it seems to work well with all the other
> > systemimager components...
> 
> Indeed, we should rather move forward in the kernel versions, not
> backwards. In average this brings us more and better device drivers
> support.
> 
> Regards,
> Erich
> 
> 

-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
___
sisuite-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/sisuite-devel

Re: [Sisuite-devel] systemimager-debian, systemimager 3.7.5 and debian sarge

2006-12-17 Thread geoffroy vallee 

Hi all,

The package creation is based on the kernel version shipped with Debian. I
do not want to change the kernel by default. It is the approach selected by
Dann and i think it is the best one. Debian developers spend a lot of time
to ship a kernel coherent for the distribution, i think it is a bad idea to
want to change that.

If someone wants to change that, i think the person has to take contact with
the Debian team in charge of the kernel packaging or, other solution, create
a new package and port all driver packages available in Debian. But clearly,
i do not want to do that. :-)

Moreover, remember, if you want to include a package within the official
Debian distribution and if you package is based on the kernel, you must use
the kernel by default.

Regards,

2006/12/17, Erich Focht <[EMAIL PROTECTED]>:


On Sunday 17 December 2006 11:40, Andrea Righi wrote:
> Instead, I've another question... regarding patch 02 I've not understood
> why you changed the default kernel version. The 2.6.18.1 has been
> strongly tested and it seems to work well with all the other
> systemimager components...

Indeed, we should rather move forward in the kernel versions, not
backwards. In average this brings us more and better device drivers
support.

Regards,
Erich


-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV___
sisuite-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/sisuite-devel

Re: [Sisuite-devel] systemimager-debian, systemimager 3.7.5 and debian sarge

2006-12-17 Thread Erich Focht 
On Sunday 17 December 2006 11:40, Andrea Righi wrote:
> Instead, I've another question... regarding patch 02 I've not understood
> why you changed the default kernel version. The 2.6.18.1 has been
> strongly tested and it seems to work well with all the other
> systemimager components...

Indeed, we should rather move forward in the kernel versions, not
backwards. In average this brings us more and better device drivers support.

Regards,
Erich


-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
___
sisuite-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/sisuite-devel

Re: [Sisuite-devel] systemimager-debian, systemimager 3.7.5 and debian sarge

2006-12-17 Thread Andrea Righi 
I've looked at your patches, unfortunately I've no experience to create
deb packages, so, sorry, I've not the answer for your questions...

Instead, I've another question... regarding patch 02 I've not understood
why you changed the default kernel version. The 2.6.18.1 has been
strongly tested and it seems to work well with all the other
systemimager components...

Thanks,
-Andrea

geoffroy vallee wrote:
> Hi all,
> 
> I started to port systemimager 3.7.5 on Debian sarge based on the
> systemimager-debian repository. Please, find in attachment my first
> patches/files.
> The modifications allow one to create all standard packages modulo the
> following limitations:
> - the systemimager-bittorrent package is not complete, few files are
> still missing, e.g., /etc/init.d/systemimager-server-bittorrent and
> /usr/bin/si_installbtimage,
> - the systemimager-i386initrd-template.package is still missing.
> 
> Any idea how to fix these two issues? I did not have the time to big it
> up because of a lack of time, the solution may be simple. I just wanted
> to send out these modifications before to continue, just in case someone
> else is working on that. :-)
> I am not sure the patch 03 is the good way to patch the linux config
> file. Let me know if you prefer to use another way.
> 
> Regards,
> 
> 

-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
___
sisuite-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/sisuite-devel