From pradhap at gmail.com  Tue Jul  1 01:35:36 2008
From: pradhap at gmail.com (Pradhap Devarajan)
Date: Tue, 1 Jul 2008 14:05:36 +0530
Subject: [belenix-dev] A testing ISO available
In-Reply-To: <46fe20470806302051x6cfec78esefd15950bd66fe37@mail.gmail.com>
References: <46fe20470806302051x6cfec78esefd15950bd66fe37@mail.gmail.com>
Message-ID: <b0db22430807010135x35b9e782n7228205b7c57ee67@mail.gmail.com>

Hi Moinak,

Some nits:-
*) Firefox 3 default page doesn't exist
*) /etc/release file needs to be updated
*) powertop doesn't work
*) You can add cpu-frequency scaling to /etc/power.conf check
http://blogs.sun.com/mhaywood/entry/powernow_for_solaris

~ Pradhap.D

On Tue, Jul 1, 2008 at 9:21 AM, Moinak Ghosh <moinakg at gmail.com> wrote:

> Hi Folks,
>
>   A testing ISO of the upcoming next release is available for
> download from here:
>
> http://www.belenix.net/binfiles/belenix.0.7.1_test1.iso
> http://www.belenix.net/binfiles/belenix.0.7.1_test1.iso.md5sum
>
> Note that this is a work in progress and obviously does not yet fix
> all the Bugs or RFEs. Some of the changes include:
>
>   - Based on ON Build 90
>   - Updated Fully Open X bits.
>   - KDE updated to 3.5.9 and some upstream patches removed
>   - Firefox3
>   - Sham's RAM based Boot integrated. In Grub screen select
>     more options to see that boot option.
>   - Caiman Installer updated to current version. Install not yet
>     tested.
>   - Added PowerTOP
>   - Added XVM PV drivers to support booting inside domU
>   - Qt 3.x is now built in both 32Bit and 64Bit versions.
>   - Gtk-Qt3 is fixed to build with proper Solaris build flags so the
>     nagging warning about /proc/.../cmdline does not appear.
>   - Updated man pages to new release.
>   - OpenMotif updated to fix some brokenness
>
> Regards,
> Moinak.
> _______________________________________________
> belenix-dev mailing list
> belenix-dev at opensolaris.org
> http://mail.opensolaris.org/mailman/listinfo/belenix-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.opensolaris.org/pipermail/belenix-dev/attachments/20080701/2e9d956d/attachment.html>

From moinakg at gmail.com  Tue Jul  1 06:15:22 2008
From: moinakg at gmail.com (Moinak Ghosh)
Date: Tue, 1 Jul 2008 18:45:22 +0530
Subject: [belenix-dev] A testing ISO available
In-Reply-To: <b0db22430807010135x35b9e782n7228205b7c57ee67@mail.gmail.com>
References: <46fe20470806302051x6cfec78esefd15950bd66fe37@mail.gmail.com>
	<b0db22430807010135x35b9e782n7228205b7c57ee67@mail.gmail.com>
Message-ID: <46fe20470807010615x4cd903e1oc46b2bffe0380f09@mail.gmail.com>

On Tue, Jul 1, 2008 at 2:05 PM, Pradhap Devarajan <pradhap at gmail.com> wrote:
> Hi Moinak,
>
> Some nits:-
> *) Firefox 3 default page doesn't exist
> *) /etc/release file needs to be updated
> *) powertop doesn't work
> *) You can add cpu-frequency scaling to /etc/power.conf check
> http://blogs.sun.com/mhaywood/entry/powernow_for_solaris

   Ok. What's the error from powertop ?

   BTW forgot to mention. Ksh93 is now the system shell. So /bin/sh
   and /sbin/sh are now Ksh93 shells.

Regards,
Moinak.

>
> ~ Pradhap.D
>
> On Tue, Jul 1, 2008 at 9:21 AM, Moinak Ghosh <moinakg at gmail.com> wrote:
>>
>> Hi Folks,
>>
>>   A testing ISO of the upcoming next release is available for
>> download from here:
>>
>> http://www.belenix.net/binfiles/belenix.0.7.1_test1.iso
>> http://www.belenix.net/binfiles/belenix.0.7.1_test1.iso.md5sum
>>
>> Note that this is a work in progress and obviously does not yet fix
>> all the Bugs or RFEs. Some of the changes include:
>>
>>   - Based on ON Build 90
>>   - Updated Fully Open X bits.
>>   - KDE updated to 3.5.9 and some upstream patches removed
>>   - Firefox3
>>   - Sham's RAM based Boot integrated. In Grub screen select
>>     more options to see that boot option.
>>   - Caiman Installer updated to current version. Install not yet
>>     tested.
>>   - Added PowerTOP
>>   - Added XVM PV drivers to support booting inside domU
>>   - Qt 3.x is now built in both 32Bit and 64Bit versions.
>>   - Gtk-Qt3 is fixed to build with proper Solaris build flags so the
>>     nagging warning about /proc/.../cmdline does not appear.
>>   - Updated man pages to new release.
>>   - OpenMotif updated to fix some brokenness
>>
>> Regards,
>> Moinak.
>> _______________________________________________
>> belenix-dev mailing list
>> belenix-dev at opensolaris.org
>> http://mail.opensolaris.org/mailman/listinfo/belenix-dev
>
>
> _______________________________________________
> belenix-dev mailing list
> belenix-dev at opensolaris.org
> http://mail.opensolaris.org/mailman/listinfo/belenix-dev
>
>


From maybird1776 at yahoo.com  Tue Jul  1 08:31:33 2008
From: maybird1776 at yahoo.com (ken mays)
Date: Tue, 1 Jul 2008 08:31:33 -0700 (PDT)
Subject: [belenix-dev] A testing ISO available
In-Reply-To: <46fe20470807010615x4cd903e1oc46b2bffe0380f09@mail.gmail.com>
Message-ID: <65296.71221.qm@web34201.mail.mud.yahoo.com>


There is one issue I noticed with this release that I am chasing down:

1. Allocation of resources during bootup - on my test laptop I get a '/ is full' error and on another test machine I see 'filesystem no dump/dump' issues.

I am doing a LiveCD boot to RAM. I see 'reallocateg' messages on one machine.

On my Intel 845G machine I see the Xserver trying to boot but it doesn't get there - goes back to prompt. On the Nvidia machine, I never see the Nvidia boot splash screen.

Conclusion:
Both test systems work fine with Belenix 0.7 and have 1GB+ RAM.

Using Belenix 0.7.1 (test) on both test systems, I can manage to get to the boot prompt if Xserver fails. Issue with memory/resource space allocation probing needs review.




--- On Tue, 7/1/08, Moinak Ghosh <moinakg at gmail.com> wrote:

> From: Moinak Ghosh <moinakg at gmail.com>
> Subject: Re: [belenix-dev] A testing ISO available
> To: "BeleniX Development" <belenix-dev at opensolaris.org>
> Cc: "Belenix Discuss" <belenix-discuss at opensolaris.org>
> Date: Tuesday, July 1, 2008, 9:15 AM
> On Tue, Jul 1, 2008 at 2:05 PM, Pradhap Devarajan
> <pradhap at gmail.com> wrote:
> > Hi Moinak,
> >
> > Some nits:-
> > *) Firefox 3 default page doesn't exist
> > *) /etc/release file needs to be updated
> > *) powertop doesn't work
> > *) You can add cpu-frequency scaling to
> /etc/power.conf check
> >
> http://blogs.sun.com/mhaywood/entry/powernow_for_solaris
> 
>    Ok. What's the error from powertop ?
> 
>    BTW forgot to mention. Ksh93 is now the system shell. So
> /bin/sh
>    and /sbin/sh are now Ksh93 shells.
> 
> Regards,
> Moinak.
> 
> >
> > ~ Pradhap.D
> >
> > On Tue, Jul 1, 2008 at 9:21 AM, Moinak Ghosh
> <moinakg at gmail.com> wrote:
> >>
> >> Hi Folks,
> >>
> >>   A testing ISO of the upcoming next release is
> available for
> >> download from here:
> >>
> >>
> http://www.belenix.net/binfiles/belenix.0.7.1_test1.iso
> >>
> http://www.belenix.net/binfiles/belenix.0.7.1_test1.iso.md5sum
> >>
> >> Note that this is a work in progress and obviously
> does not yet fix
> >> all the Bugs or RFEs. Some of the changes include:
> >>
> >>   - Based on ON Build 90
> >>   - Updated Fully Open X bits.
> >>   - KDE updated to 3.5.9 and some upstream patches
> removed
> >>   - Firefox3
> >>   - Sham's RAM based Boot integrated. In Grub
> screen select
> >>     more options to see that boot option.
> >>   - Caiman Installer updated to current version.
> Install not yet
> >>     tested.
> >>   - Added PowerTOP
> >>   - Added XVM PV drivers to support booting inside
> domU
> >>   - Qt 3.x is now built in both 32Bit and 64Bit
> versions.
> >>   - Gtk-Qt3 is fixed to build with proper Solaris
> build flags so the
> >>     nagging warning about /proc/.../cmdline does
> not appear.
> >>   - Updated man pages to new release.
> >>   - OpenMotif updated to fix some brokenness
> >>
> >> Regards,
> >> Moinak.
> >> _______________________________________________
> >> belenix-dev mailing list
> >> belenix-dev at opensolaris.org
> >>
> http://mail.opensolaris.org/mailman/listinfo/belenix-dev
> >
> >
> > _______________________________________________
> > belenix-dev mailing list
> > belenix-dev at opensolaris.org
> >
> http://mail.opensolaris.org/mailman/listinfo/belenix-dev
> >
> >
> _______________________________________________
> belenix-dev mailing list
> belenix-dev at opensolaris.org
> http://mail.opensolaris.org/mailman/listinfo/belenix-dev


      


From anil.verve at gmail.com  Tue Jul  1 20:34:14 2008
From: anil.verve at gmail.com (Anil Gulecha)
Date: Wed, 2 Jul 2008 09:04:14 +0530
Subject: [belenix-dev] A testing ISO available
In-Reply-To: <65296.71221.qm@web34201.mail.mud.yahoo.com>
References: <46fe20470807010615x4cd903e1oc46b2bffe0380f09@mail.gmail.com>
	<65296.71221.qm@web34201.mail.mud.yahoo.com>
Message-ID: <148d59250807012034h55473e0dj3e2ad906054ca71a@mail.gmail.com>

On 7/1/08, ken mays <maybird1776 at yahoo.com> wrote:
>
>  There is one issue I noticed with this release that I am chasing down:
>
>  1. Allocation of resources during bootup - on my test laptop I get a '/ is full' error and on another test machine I see 'filesystem no dump/dump' issues.
>

This is probably because of an application failing and dumping to the
ramdisk (which has only a few megs of ram free).

~Anil


From russiane39 at gmail.com  Tue Jul  1 18:11:44 2008
From: russiane39 at gmail.com (Michael Kosarev)
Date: Tue, 1 Jul 2008 18:11:44 -0700
Subject: [belenix-dev] Belenix 0.7.1 Bug/Notes list
Message-ID: <cf4355090807011811nf6d8497vabaf235207684c8@mail.gmail.com>

1. Boot from RAM is not working (some problem with livecd service)
2. Firefox lacks of flash9
3. OSS not works from LiveCD as usual :-)
jack at belenix:~# ossdetect
rem_drv osscore
rem_drv sblive
rem_drv ossusb
rem_drv vmix
rem_drv sadasupport
unloaded osscommon
add_drv -m '* 0666 root sys' osscore
add_drv -m '* 0666 root sys' -i '"pci1102,2"' sblive
add_drv -m '* 0666 root sys' -i '"usbif,class1"' ossusb
add_drv -m '* 0666 root sys' vmix
add_drv -m '* 0666 root sys' sadasupport
/dev/mixer: No such file or directory
4. Bumpup Xchat to 2.8.6 (grab SFEXchat.spec from SFE SVN)
5. Old bug (Probably kernel related) with turning off/ turning on hard
drives on boot up (At probing devices stage) still here
6. If you want Firefox from LiveCD - first you should run it from terminal.
7. As usual (don't know is it bug/feature), my nvidia 8800GT aren't
detected, and usual X.org nv driver used instead of Nvidia driver.

This is opinions from first 15minutes. But anyway, belenix becomes more
nicer, faster and better :-)

-- 
With best regards from Russia, Mike
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.opensolaris.org/pipermail/belenix-dev/attachments/20080701/d48fc40b/attachment.html>

From shampavman.cg at gmail.com  Wed Jul  2 08:27:30 2008
From: shampavman.cg at gmail.com (sham pavman)
Date: Wed, 2 Jul 2008 15:27:30 +0000
Subject: [belenix-dev] Belenix 0.7.1 Bug/Notes list
In-Reply-To: <cf4355090807011811nf6d8497vabaf235207684c8@mail.gmail.com>
References: <cf4355090807011811nf6d8497vabaf235207684c8@mail.gmail.com>
Message-ID: <9f9ad12d0807020827r373e1ecs10c0f70cca19610a@mail.gmail.com>

Hi ,
Can you be specific as to what aspect is not working?
I tried the boot from RAM ,its working flawlessly!!
Did you try it out on Vbox?
Apparently even i had problems while booting through Vbox, but haven't dug
into it as yet.

Regards
Shampavman
blogs.sun.com/sham

On Wed, Jul 2, 2008 at 1:11 AM, Michael Kosarev <russiane39 at gmail.com>
wrote:

> 1. Boot from RAM is not working (some problem with livecd service)
> 2. Firefox lacks of flash9
> 3. OSS not works from LiveCD as usual :-)
> jack at belenix:~# ossdetect
> rem_drv osscore
> rem_drv sblive
> rem_drv ossusb
> rem_drv vmix
> rem_drv sadasupport
> unloaded osscommon
> add_drv -m '* 0666 root sys' osscore
> add_drv -m '* 0666 root sys' -i '"pci1102,2"' sblive
> add_drv -m '* 0666 root sys' -i '"usbif,class1"' ossusb
> add_drv -m '* 0666 root sys' vmix
> add_drv -m '* 0666 root sys' sadasupport
> /dev/mixer: No such file or directory
> 4. Bumpup Xchat to 2.8.6 (grab SFEXchat.spec from SFE SVN)
> 5. Old bug (Probably kernel related) with turning off/ turning on hard
> drives on boot up (At probing devices stage) still here
> 6. If you want Firefox from LiveCD - first you should run it from terminal.
> 7. As usual (don't know is it bug/feature), my nvidia 8800GT aren't
> detected, and usual X.org nv driver used instead of Nvidia driver.
>
> This is opinions from first 15minutes. But anyway, belenix becomes more
> nicer, faster and better :-)
>
> --
> With best regards from Russia, Mike
>
> _______________________________________________
> belenix-dev mailing list
> belenix-dev at opensolaris.org
> http://mail.opensolaris.org/mailman/listinfo/belenix-dev
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.opensolaris.org/pipermail/belenix-dev/attachments/20080702/e0a170ef/attachment.html>

From moinakg at gmail.com  Wed Jul  9 20:10:05 2008
From: moinakg at gmail.com (Moinak Ghosh)
Date: Thu, 10 Jul 2008 08:40:05 +0530
Subject: [belenix-dev] BeleniX 0.7.1_test2 ISO available
Message-ID: <46fe20470807092010n3ef72440t1f0c8820b4f81ebf@mail.gmail.com>

Hi,

   I put up a second test ISO for the upcoming 0.7.1 release.
You can get it from here:

http://www.belenix.org/binfiles/belenix.0.7.1_test2.iso

The changes in this build include:

* Add module relocation support to reduce ramdisk space usage.
  Still not complete yet.
* Add ATI Graphics kernel module and zone support package.
* MDB Patch to fix 6174625 (::memstat should not show ridiculous
amounts of free memory)
* Fix Firefox home page
* Fix GRUB Menu Title.
* Add calculation of IMAGE_SIZE for updated Caiman installer.
* Bump Nvidia and OSS to newer versions. Nvidia driver is now 7.5MB UGH.
* Updates to Zone support.
* Gtk-Qt engine has been updated with proper build flags.
* Add patch to get fixe for bugs:
  http://bugs.opensolaris.org/view_bug.do?bug_id=6622965

No sse2 thing is not done yet. There will be an error from SMF at the start of
boot complaining about '/' being full. You can ignore it.

You can create Zones in BeleniX now using the the following procedure:

Edit: /etc/bzfscfg.conf and set ZONES_SNAP to the appropriate snapshot
of the root dataset that you want to clone. By default you need to set it to
the ... at install snapshot.
ZONES_DATASET should be set to the value of the root dataset.

Next you can use:

zonecfg -z myzone
myzone: No such zone configured
Use 'create' to begin configuring a new zone.
zonecfg:myzone> create -t SUNWbzfs
...
...

I am shooting for the final release early next week. The final release will
be based on ON Build93.

Regards,
Moinak.


From maybird1776 at yahoo.com  Thu Jul 10 07:24:53 2008
From: maybird1776 at yahoo.com (ken mays)
Date: Thu, 10 Jul 2008 07:24:53 -0700 (PDT)
Subject: [belenix-dev] BeleniX 0.7.1_test2 ISO available
In-Reply-To: <46fe20470807092010n3ef72440t1f0c8820b4f81ebf@mail.gmail.com>
Message-ID: <350045.37717.qm@web34206.mail.mud.yahoo.com>

1. I have Belenix 0.7.1_test1 working fine on my core test system. Had problems with my other test systems. KDE 3.5.9 loaded up and no MAJOR issues in basic desktop functionality. ATI Radeon 4870 card works fine.

2. Belenix 0.7.1_test2 works properly with my ATI Radeon HD 4870 graphics card and I tested the included ATI driver with my 1900x1200 2D display (the card handles the TV out [1080p] and DVI-I at 2560x1600). TV out works well.

Note: You may want to include the Nvidia 177.13 driver to properly detect the Nvidia GTX 280. I'll start testing this card after I finish up on the ATI 4870 card. Would be nice to have this working out of the box in Live CD mode.

My SoundBlaster X-Fi Platinum audio card still works too. This is great.

Besides updated networking drivers, I think everything else is there. I'll do more review later tonite.

~ Ken Mays

--- On Wed, 7/9/08, Moinak Ghosh <moinakg at gmail.com> wrote:

> From: Moinak Ghosh <moinakg at gmail.com>
> Subject: [belenix-dev] BeleniX 0.7.1_test2 ISO available
> To: "Belenix Discuss" <belenix-discuss at opensolaris.org>, "BeleniX Development" <belenix-dev at opensolaris.org>
> Date: Wednesday, July 9, 2008, 11:10 PM
> Hi,
> 
>    I put up a second test ISO for the upcoming 0.7.1
> release.
> You can get it from here:
> 
> http://www.belenix.org/binfiles/belenix.0.7.1_test2.iso
> 
> The changes in this build include:
> 
> * Add module relocation support to reduce ramdisk space
> usage.
>   Still not complete yet.
> * Add ATI Graphics kernel module and zone support package.
> * MDB Patch to fix 6174625 (::memstat should not show
> ridiculous
> amounts of free memory)
> * Fix Firefox home page
> * Fix GRUB Menu Title.
> * Add calculation of IMAGE_SIZE for updated Caiman
> installer.
> * Bump Nvidia and OSS to newer versions. Nvidia driver is
> now 7.5MB UGH.
> * Updates to Zone support.
> * Gtk-Qt engine has been updated with proper build flags.
> * Add patch to get fixe for bugs:
>   http://bugs.opensolaris.org/view_bug.do?bug_id=6622965
> 
> No sse2 thing is not done yet. There will be an error from
> SMF at the start of
> boot complaining about '/' being full. You can
> ignore it.
> 
> You can create Zones in BeleniX now using the the following
> procedure:
> 
> Edit: /etc/bzfscfg.conf and set ZONES_SNAP to the
> appropriate snapshot
> of the root dataset that you want to clone. By default you
> need to set it to
> the ... at install snapshot.
> ZONES_DATASET should be set to the value of the root
> dataset.
> 
> Next you can use:
> 
> zonecfg -z myzone
> myzone: No such zone configured
> Use 'create' to begin configuring a new zone.
> zonecfg:myzone> create -t SUNWbzfs
> ...
> ...
> 
> I am shooting for the final release early next week. The
> final release will
> be based on ON Build93.
> 
> Regards,
> Moinak.
> _______________________________________________
> belenix-dev mailing list
> belenix-dev at opensolaris.org
> http://mail.opensolaris.org/mailman/listinfo/belenix-dev


      


From moinakg at gmail.com  Thu Jul 10 08:13:22 2008
From: moinakg at gmail.com (Moinak Ghosh)
Date: Thu, 10 Jul 2008 20:43:22 +0530
Subject: [belenix-dev] BeleniX 0.7.1_test2 ISO available
In-Reply-To: <350045.37717.qm@web34206.mail.mud.yahoo.com>
References: <46fe20470807092010n3ef72440t1f0c8820b4f81ebf@mail.gmail.com>
	<350045.37717.qm@web34206.mail.mud.yahoo.com>
Message-ID: <46fe20470807100813j2c7a66a5kd3a51eac7d665b36@mail.gmail.com>

Thanks!

On Thu, Jul 10, 2008 at 7:54 PM, ken mays <maybird1776 at yahoo.com> wrote:
> 1. I have Belenix 0.7.1_test1 working fine on my core test system. Had problems with my other test systems. KDE 3.5.9 loaded up and no MAJOR issues in basic desktop functionality. ATI Radeon 4870 card works fine.
>
> 2. Belenix 0.7.1_test2 works properly with my ATI Radeon HD 4870 graphics card and I tested the included ATI driver with my 1900x1200 2D display (the card handles the TV out [1080p] and DVI-I at 2560x1600). TV out works well.

   It is still including the existing 6.8.0 ATI driver from the FOX
gate but the livecd
   now includes the Atigfx kernel driver.

>
> Note: You may want to include the Nvidia 177.13 driver to properly detect the Nvidia GTX 280. I'll start testing this card after I finish up on the ATI 4870 card. Would be nice to have this working out of the box in Live CD mode.

   Mistake. The livecd includes NVIDIA-Solaris-x86-173.14.05. I will
change it to
   177.13.

Regards,
Moinak.

>
> My SoundBlaster X-Fi Platinum audio card still works too. This is great.
>
> Besides updated networking drivers, I think everything else is there. I'll do more review later tonite.
>
> ~ Ken Mays
>
> --- On Wed, 7/9/08, Moinak Ghosh <moinakg at gmail.com> wrote:
>
>> From: Moinak Ghosh <moinakg at gmail.com>
>> Subject: [belenix-dev] BeleniX 0.7.1_test2 ISO available
>> To: "Belenix Discuss" <belenix-discuss at opensolaris.org>, "BeleniX Development" <belenix-dev at opensolaris.org>
>> Date: Wednesday, July 9, 2008, 11:10 PM
>> Hi,
>>
>>    I put up a second test ISO for the upcoming 0.7.1
>> release.
>> You can get it from here:
>>
>> http://www.belenix.org/binfiles/belenix.0.7.1_test2.iso
>>
>> The changes in this build include:
>>
>> * Add module relocation support to reduce ramdisk space
>> usage.
>>   Still not complete yet.
>> * Add ATI Graphics kernel module and zone support package.
>> * MDB Patch to fix 6174625 (::memstat should not show
>> ridiculous
>> amounts of free memory)
>> * Fix Firefox home page
>> * Fix GRUB Menu Title.
>> * Add calculation of IMAGE_SIZE for updated Caiman
>> installer.
>> * Bump Nvidia and OSS to newer versions. Nvidia driver is
>> now 7.5MB UGH.
>> * Updates to Zone support.
>> * Gtk-Qt engine has been updated with proper build flags.
>> * Add patch to get fixe for bugs:
>>   http://bugs.opensolaris.org/view_bug.do?bug_id=6622965
>>
>> No sse2 thing is not done yet. There will be an error from
>> SMF at the start of
>> boot complaining about '/' being full. You can
>> ignore it.
>>
>> You can create Zones in BeleniX now using the the following
>> procedure:
>>
>> Edit: /etc/bzfscfg.conf and set ZONES_SNAP to the
>> appropriate snapshot
>> of the root dataset that you want to clone. By default you
>> need to set it to
>> the ... at install snapshot.
>> ZONES_DATASET should be set to the value of the root
>> dataset.
>>
>> Next you can use:
>>
>> zonecfg -z myzone
>> myzone: No such zone configured
>> Use 'create' to begin configuring a new zone.
>> zonecfg:myzone> create -t SUNWbzfs
>> ...
>> ...
>>
>> I am shooting for the final release early next week. The
>> final release will
>> be based on ON Build93.
>>
>> Regards,
>> Moinak.
>> _______________________________________________
>> belenix-dev mailing list
>> belenix-dev at opensolaris.org
>> http://mail.opensolaris.org/mailman/listinfo/belenix-dev
>
>
>
> _______________________________________________
> belenix-dev mailing list
> belenix-dev at opensolaris.org
> http://mail.opensolaris.org/mailman/listinfo/belenix-dev
>


From moinakg at gmail.com  Thu Jul 10 08:15:46 2008
From: moinakg at gmail.com (Moinak Ghosh)
Date: Thu, 10 Jul 2008 20:45:46 +0530
Subject: [belenix-dev] BeleniX 0.7.1_test2 ISO available
In-Reply-To: <46fe20470807100813j2c7a66a5kd3a51eac7d665b36@mail.gmail.com>
References: <46fe20470807092010n3ef72440t1f0c8820b4f81ebf@mail.gmail.com>
	<350045.37717.qm@web34206.mail.mud.yahoo.com>
	<46fe20470807100813j2c7a66a5kd3a51eac7d665b36@mail.gmail.com>
Message-ID: <46fe20470807100815i3ca2a105mddb8e3824a71fa5d@mail.gmail.com>

Thanks!

On Thu, Jul 10, 2008 at 7:54 PM, ken mays <maybird1776 at yahoo.com> wrote:
> 1. I have Belenix 0.7.1_test1 working fine on my core test system. Had problems with my other test systems. KDE 3.5.9 loaded up and no MAJOR issues in basic desktop functionality. ATI Radeon 4870 card works fine.
>
> 2. Belenix 0.7.1_test2 works properly with my ATI Radeon HD 4870 graphics card and I tested the included ATI driver with my 1900x1200 2D display (the card handles the TV out [1080p] and DVI-I at 2560x1600). TV out works well.

   It is still including the existing 6.8.0 ATI driver from the FOX
gate but the livecd
   now includes the Atigfx kernel driver.

>
> Note: You may want to include the Nvidia 177.13 driver to properly detect the Nvidia GTX 280. I'll start testing this card after I finish up on the ATI 4870 card. Would be nice to have this working out of the box in Live CD mode.

   Mistake. The livecd includes NVIDIA-Solaris-x86-173.14.05. I will
change it to
   177.13.

Regards,
Moinak.

>
> My SoundBlaster X-Fi Platinum audio card still works too. This is great.
>
> Besides updated networking drivers, I think everything else is there. I'll do more review later tonite.
>
> ~ Ken Mays
>
> --- On Wed, 7/9/08, Moinak Ghosh <moinakg at gmail.com> wrote:
>
>> From: Moinak Ghosh <moinakg at gmail.com>
>> Subject: [belenix-dev] BeleniX 0.7.1_test2 ISO available
>> To: "Belenix Discuss" <belenix-discuss at opensolaris.org>, "BeleniX Development" <belenix-dev at opensolaris.org>
>> Date: Wednesday, July 9, 2008, 11:10 PM
>> Hi,
>>
>>    I put up a second test ISO for the upcoming 0.7.1
>> release.
>> You can get it from here:
>>
>> http://www.belenix.org/binfiles/belenix.0.7.1_test2.iso
>>
>> The changes in this build include:
>>
>> * Add module relocation support to reduce ramdisk space
>> usage.
>>   Still not complete yet.
>> * Add ATI Graphics kernel module and zone support package.
>> * MDB Patch to fix 6174625 (::memstat should not show
>> ridiculous
>> amounts of free memory)
>> * Fix Firefox home page
>> * Fix GRUB Menu Title.
>> * Add calculation of IMAGE_SIZE for updated Caiman
>> installer.
>> * Bump Nvidia and OSS to newer versions. Nvidia driver is
>> now 7.5MB UGH.
>> * Updates to Zone support.
>> * Gtk-Qt engine has been updated with proper build flags.
>> * Add patch to get fixe for bugs:
>>   http://bugs.opensolaris.org/view_bug.do?bug_id=6622965
>>
>> No sse2 thing is not done yet. There will be an error from
>> SMF at the start of
>> boot complaining about '/' being full. You can
>> ignore it.
>>
>> You can create Zones in BeleniX now using the the following
>> procedure:
>>
>> Edit: /etc/bzfscfg.conf and set ZONES_SNAP to the
>> appropriate snapshot
>> of the root dataset that you want to clone. By default you
>> need to set it to
>> the ... at install snapshot.
>> ZONES_DATASET should be set to the value of the root
>> dataset.
>>
>> Next you can use:
>>
>> zonecfg -z myzone
>> myzone: No such zone configured
>> Use 'create' to begin configuring a new zone.
>> zonecfg:myzone> create -t SUNWbzfs
>> ...
>> ...
>>
>> I am shooting for the final release early next week. The
>> final release will
>> be based on ON Build93.
>>
>> Regards,
>> Moinak.
>> _______________________________________________
>> belenix-dev mailing list
>> belenix-dev at opensolaris.org
>> http://mail.opensolaris.org/mailman/listinfo/belenix-dev
>
>
>
> _______________________________________________
> belenix-dev mailing list
> belenix-dev at opensolaris.org
> http://mail.opensolaris.org/mailman/listinfo/belenix-dev
>


From moinakg at gmail.com  Mon Jul 14 11:29:20 2008
From: moinakg at gmail.com (Moinak Ghosh)
Date: Mon, 14 Jul 2008 23:59:20 +0530
Subject: [belenix-dev] Thought's on package repository structuring
Message-ID: <46fe20470807141129u7788f925i4b72dad63367ef3c@mail.gmail.com>

Hi Folks,

   I have been giving some thoughts to the way the BeleniX package
repository should be structured and the way we should go about
using a proper packaging solution. I am listing some observations
below. Comments/suggestions are more than welcome :)

* Let consider the dependency list of SUNWfirefox:

   cat /var/sadm/pkg/SUNWfirefox/install/depend
   P SUNWcar Core Architecture, (Root)
   P SUNWkvm Core Architecture, (Kvm)
   P SUNWcsr Core Solaris, (Root)
   P SUNWcsu Core Solaris, (Usr)
   P SUNWcsl Core Solaris, (Shared Libs)
   ...
   ...

   Now my question is why do we need these dependencies on the
   core system ? It is not conceivable by any stretch if imagination
   that it will be possible to run Firefox without having SUNWcsr
   installed ... much less boot the system!

   So what purpose do these dependencies serve other than causing
   trouble ? Any auto-dependency resolution mechanism will try to
   pull down updated versions of these packages while trying to update
   Firefox from an recently updated repository thus screwing the running
   system.
   Can't we simply assume the base OpenSolaris system to be present
   without having to explicitly specify dependencies on it.

* Having the above enables us to have a clear separation between the
   base operating system and layered software on top. Thus I can choose
   to perform a software-update without having to upgrade my base system,
   or update an individual software package and dependencies without the
   packaging system trying to pull down an updated libc!

   I should still be able to do a dist-upgrade to perform a complete system
   upgrade in a new boot environment.
   This is additional flexibility to the user.

* However the above scenarios do not preclude brokenness. It is possible
   that a new layered software package needs a new version of a base
   system package, say for example hal. Updating to than new version
   without updating hal in the base system will cause breakage.

   This scenario can be tackled by extending the dependency mechanism
   with the ability to express version-specific dependencies like in RPM.
   Thus trying to update  pkgx where pkgx.depends: hal >= 10 for eg. will
   fail if installed hal version is 9. This is because hal is part of the base
   system and updating the base system requires a dist-upgrade.

* While doing a dist-upgrade it should be possible to specify a target
   release to upgrade to. This means that the BeleniX package repo
   should maintain separate or tagged repositories per release and
   micro-release. Of course disk usage can be controlled via effective
   usage of ZFS clones.

There are several approaches to going about getting these things done:

1) Stick to SVR4 and build wrapper utilities to get these features - moderate
  efforts but potential obsolescence since OpenSolaris is moving away from
  SVR4 and the packaging format is kinda creaky.

2) Migrate to IPS and extend it - quite a bit of effort needed. In
addition to above
   we need to add in more stuff like on-disk package file format support, full
   mirroring (including manifests), ability to remove packages from a repo,
   do not use timestamp-based versioning, web-based repository browsing
   and package searching etc., and several more things.

3) Use Dpkg and Apt from Nexenta's port. This gives a wealth of features and
   readymade solutions with maybe small effort needed to put in some tweaks.
   This is not aligned with what the OpenSolaris community is converging on -
   IPS. A lot of new OpenSolaris features will be implemented in the longer run
   centering on IPS. So in the longer run Dpkg might need more effort and
   will be a completely diverged but well-known solution.

>From my opinion I see merit in approach #2 even though it needs quite a lot
of effort. I do also see merit in #3 but then we get diverged.

Comments, Opinions ?

Regards,
Moinak.


From sriramnrn at gmail.com  Mon Jul 14 13:21:14 2008
From: sriramnrn at gmail.com (Sriram Narayanan)
Date: Tue, 15 Jul 2008 01:51:14 +0530
Subject: [belenix-dev] [belenix-discuss] Thought's on package repository
	structuring
In-Reply-To: <46fe20470807141129u7788f925i4b72dad63367ef3c@mail.gmail.com>
References: <46fe20470807141129u7788f925i4b72dad63367ef3c@mail.gmail.com>
Message-ID: <49977f270807141321m53e98e00y10f102403ea5216e@mail.gmail.com>

On Mon, Jul 14, 2008 at 11:59 PM, Moinak Ghosh <moinakg at gmail.com> wrote:
>
> 2) Migrate to IPS and extend it - quite a bit of effort needed. In
> addition to above
>   we need to add in more stuff like on-disk package file format support, full
>   mirroring (including manifests), ability to remove packages from a repo,
>   do not use timestamp-based versioning, web-based repository browsing
>   and package searching etc., and several more things.
>
> 3) Use Dpkg and Apt from Nexenta's port. This gives a wealth of features and
>   readymade solutions with maybe small effort needed to put in some tweaks.
>   This is not aligned with what the OpenSolaris community is converging on -
>   IPS. A lot of new OpenSolaris features will be implemented in the longer run
>   centering on IPS. So in the longer run Dpkg might need more effort and
>   will be a completely diverged but well-known solution.
>
> >From my opinion I see merit in approach #2 even though it needs quite a lot
> of effort. I do also see merit in #3 but then we get diverged.

I concur that approach #2 - IPS and modifications as needed is the
best way out. While I do apreciate the innovation at Nexenta, I also
do feel (like all of us in the Belenix team) that we should try and
stay as close to opensolaris as possible as far as core infrastructure
is concerned.

We ought to list our concerns and talk to the IPS team about these and
seek their perspective as well.

We could then work with the IPS team at first to provide solutions for
these concerns. In case the IPS team has different priorities at the
moment, then we could try to create a mergable and approvable set of
extensions/fixes that could go back into the IPS tree.

-- Sriram


From shivakumar.gn at gmail.com  Mon Jul 14 17:46:37 2008
From: shivakumar.gn at gmail.com (S h i v)
Date: Tue, 15 Jul 2008 06:16:37 +0530
Subject: [belenix-dev] [belenix-discuss] Thought's on package repository
	structuring
In-Reply-To: <46fe20470807141129u7788f925i4b72dad63367ef3c@mail.gmail.com>
References: <46fe20470807141129u7788f925i4b72dad63367ef3c@mail.gmail.com>
Message-ID: <319ee2b10807141746u3ea7c3reba7ecdcee27d984@mail.gmail.com>

On Mon, Jul 14, 2008 at 11:59 PM, Moinak Ghosh <moinakg at gmail.com> wrote:

>
> * <snip>
>   Can't we simply assume the base OpenSolaris system to be present
>   without having to explicitly specify dependencies on it.
>
> * However the above scenarios do not preclude brokenness. It is possible
>   that a new layered software package needs a new version of a base
>   system package, say for example hal. Updating to than new version
>   without updating hal in the base system will cause breakage.
>
>   This scenario can be tackled by extending the dependency mechanism
>   with the ability to express version-specific dependencies like in RPM.
>   Thus trying to update  pkgx where pkgx.depends: hal >= 10 for eg. will
>   fail if installed hal version is 9. This is because hal is part of the
> base
>   system and updating the base system requires a dist-upgrade.
>

If we consider both the points together, from most top layers we do not
include core package dependency.
For some where it might be necessary, we use a ">=ver" approach.
We need to have the versioning numbering scheme aligned with that of
upstream softwares and a mechanism to have >, <, == kind of logical
operations possible. I believe IPS currently solves this by have its own
numbering scheme (in divergence with the upstream package versions ?)



> 2) Migrate to IPS and extend it - quite a bit of effort needed. In
> addition to above
>   we need to add in more stuff like on-disk package file format support,
> full
>   mirroring (including manifests), ability to remove packages from a repo,
>   do not use timestamp-based versioning, web-based repository browsing
>   and package searching etc., and several more things.
>

Going with IPS is what I would vote for, but I am not sure if we need to
migrate to IPS for V0.8 itself since some of these are missing.
We can starting working on some of these items while staying with SVR4 for 1
more release.



> 3) Use Dpkg and Apt from Nexenta's port. This gives a wealth of features
> and
>   readymade solutions with maybe small effort needed to put in some tweaks.
>   This is not aligned with what the OpenSolaris community is converging on
> -
>   IPS. A lot of new OpenSolaris features will be implemented in the longer
> run
>   centering on IPS. So in the longer run Dpkg might need more effort and
>   will be a completely diverged but well-known solution.
>

Nexenta's support is seamless and awesome, but our initial idea of providing
a distro that showcases technologies at opensolaris.org and be aligned as
much as possible to work done here will not be true any longer. Too many
things get affected starting from building/packaging/integrating. I vote
against the option.

regards
Shiv
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.opensolaris.org/pipermail/belenix-dev/attachments/20080715/1ec95b9a/attachment.html>

From victoredwardocallaghan at gmail.com  Mon Jul 14 22:42:53 2008
From: victoredwardocallaghan at gmail.com (Edward O'Callaghan)
Date: Tue, 15 Jul 2008 15:42:53 +1000
Subject: [belenix-dev] [belenix-discuss] Thought's on package repository
	structuring
In-Reply-To: <319ee2b10807141746u3ea7c3reba7ecdcee27d984@mail.gmail.com>
References: <46fe20470807141129u7788f925i4b72dad63367ef3c@mail.gmail.com>
	<319ee2b10807141746u3ea7c3reba7ecdcee27d984@mail.gmail.com>
Message-ID: <cbc95d950807142242i381b90f4g9665541573f29c28@mail.gmail.com>

Hi,

We should try to fix IPS as much as we can and run with that.
Pooling more development time into a single project would be better for the
greater good, else we will be still right where we are now in a few years
time.

Let unify people, no more Unix wars :p .

Our approach should be along these lines:
a) Find the most critical issues at hand with IPS - most are already filed
such as :
http://defect.opensolaris.org/bz/show_bug.cgi?id=1829
b) Fix these problems first *before* adding more features, even though some
are much needed.
c) File all RFE for these features on http://defect.opensolaris.org/bz/

We should then create a poll on the BeleniX site for the top 10 that should
be worked on first and let the votes count for the top 5 that should be done
first, for example.

If we prioritize as above in this way, we can cover more ground in a more
logical manner!

Best Regards,
Edward O'Callaghan.

2008/7/15 S h i v <shivakumar.gn at gmail.com>:

> On Mon, Jul 14, 2008 at 11:59 PM, Moinak Ghosh <moinakg at gmail.com> wrote:
>
>>
>> * <snip>
>>   Can't we simply assume the base OpenSolaris system to be present
>>   without having to explicitly specify dependencies on it.
>>
>> * However the above scenarios do not preclude brokenness. It is possible
>>   that a new layered software package needs a new version of a base
>>   system package, say for example hal. Updating to than new version
>>   without updating hal in the base system will cause breakage.
>>
>>   This scenario can be tackled by extending the dependency mechanism
>>   with the ability to express version-specific dependencies like in RPM.
>>   Thus trying to update  pkgx where pkgx.depends: hal >= 10 for eg. will
>>   fail if installed hal version is 9. This is because hal is part of the
>> base
>>   system and updating the base system requires a dist-upgrade.
>>
>
> If we consider both the points together, from most top layers we do not
> include core package dependency.
> For some where it might be necessary, we use a ">=ver" approach.
> We need to have the versioning numbering scheme aligned with that of
> upstream softwares and a mechanism to have >, <, == kind of logical
> operations possible. I believe IPS currently solves this by have its own
> numbering scheme (in divergence with the upstream package versions ?)
>
>
>
>> 2) Migrate to IPS and extend it - quite a bit of effort needed. In
>> addition to above
>>   we need to add in more stuff like on-disk package file format support,
>> full
>>   mirroring (including manifests), ability to remove packages from a repo,
>>   do not use timestamp-based versioning, web-based repository browsing
>>   and package searching etc., and several more things.
>>
>
> Going with IPS is what I would vote for, but I am not sure if we need to
> migrate to IPS for V0.8 itself since some of these are missing.
> We can starting working on some of these items while staying with SVR4 for
> 1 more release.
>
>
>
>> 3) Use Dpkg and Apt from Nexenta's port. This gives a wealth of features
>> and
>>   readymade solutions with maybe small effort needed to put in some
>> tweaks.
>>   This is not aligned with what the OpenSolaris community is converging on
>> -
>>   IPS. A lot of new OpenSolaris features will be implemented in the longer
>> run
>>   centering on IPS. So in the longer run Dpkg might need more effort and
>>   will be a completely diverged but well-known solution.
>>
>
> Nexenta's support is seamless and awesome, but our initial idea of
> providing a distro that showcases technologies at opensolaris.org and be
> aligned as much as possible to work done here will not be true any longer.
> Too many things get affected starting from building/packaging/integrating. I
> vote against the option.
>
> regards
> Shiv
>
>
> _______________________________________________
> belenix-dev mailing list
> belenix-dev at opensolaris.org
> http://mail.opensolaris.org/mailman/listinfo/belenix-dev
>
>


-- 
All Documents adhered to the ISO/IEC 26300 standard file format for
electronic office documents, such as spreadsheets, charts, presentations and
word processing documents from this email address. The author does not take
responsibility of the recipients inability to read international standards
and who use proprietary products such as MS Office.
See: http://www.openoffice.org/
Edward O'Callaghan.
--
http://fedoraproject.org/wiki/EdwardOcallaghan
http://moonshine.opn4.org/
http://www.pcbsd.org/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.opensolaris.org/pipermail/belenix-dev/attachments/20080715/24621dab/attachment.html>

From maybird1776 at yahoo.com  Tue Jul 15 03:57:48 2008
From: maybird1776 at yahoo.com (ken mays)
Date: Tue, 15 Jul 2008 03:57:48 -0700 (PDT)
Subject: [belenix-dev] [belenix-discuss] Thought's on package repository
	structuring
In-Reply-To: <cbc95d950807142242i381b90f4g9665541573f29c28@mail.gmail.com>
Message-ID: <987005.97049.qm@web34207.mail.mud.yahoo.com>

Agree. Don't break any SVR4 packaging or installation, but extend Belenix to support and utilize IPS.

The Nexenta packaging model is a 'value-add' for Belenix. But IPS has priority to unify ISV development efforts - in which Nexenta will have to eventually support through an IPS version of apt.nexenta.org to keep in line with Sun updates and support as well - as well as Blastwave, Sunfreeware, and other ISVs.

Remember, OpenSolaris 2008.11 is THE reference standard - so you'd have to consider what options it provides or doesn't provide to extend from before you add 'features' from the other distros (aka Nexenta...)

~ Ken Mays



--- On Tue, 7/15/08, Edward O'Callaghan <victoredwardocallaghan at gmail.com> wrote:

> From: Edward O'Callaghan <victoredwardocallaghan at gmail.com>
> Subject: Re: [belenix-dev] [belenix-discuss] Thought's on package repository structuring
> To: "BeleniX Development" <belenix-dev at opensolaris.org>
> Date: Tuesday, July 15, 2008, 1:42 AM
> Hi,
> 
> We should try to fix IPS as much as we can and run with
> that.
> Pooling more development time into a single project would
> be better for the
> greater good, else we will be still right where we are now
> in a few years
> time.
> 
> Let unify people, no more Unix wars :p .
> 
> Our approach should be along these lines:
> a) Find the most critical issues at hand with IPS - most
> are already filed
> such as :
> http://defect.opensolaris.org/bz/show_bug.cgi?id=1829
> b) Fix these problems first *before* adding more features,
> even though some
> are much needed.
> c) File all RFE for these features on
> http://defect.opensolaris.org/bz/
> 
> We should then create a poll on the BeleniX site for the
> top 10 that should
> be worked on first and let the votes count for the top 5
> that should be done
> first, for example.
> 
> If we prioritize as above in this way, we can cover more
> ground in a more
> logical manner!
> 
> Best Regards,
> Edward O'Callaghan.
> 
> 2008/7/15 S h i v <shivakumar.gn at gmail.com>:
> 
> > On Mon, Jul 14, 2008 at 11:59 PM, Moinak Ghosh
> <moinakg at gmail.com> wrote:
> >
> >>
> >> * <snip>
> >>   Can't we simply assume the base OpenSolaris
> system to be present
> >>   without having to explicitly specify
> dependencies on it.
> >>
> >> * However the above scenarios do not preclude
> brokenness. It is possible
> >>   that a new layered software package needs a new
> version of a base
> >>   system package, say for example hal. Updating to
> than new version
> >>   without updating hal in the base system will
> cause breakage.
> >>
> >>   This scenario can be tackled by extending the
> dependency mechanism
> >>   with the ability to express version-specific
> dependencies like in RPM.
> >>   Thus trying to update  pkgx where pkgx.depends:
> hal >= 10 for eg. will
> >>   fail if installed hal version is 9. This is
> because hal is part of the
> >> base
> >>   system and updating the base system requires a
> dist-upgrade.
> >>
> >
> > If we consider both the points together, from most top
> layers we do not
> > include core package dependency.
> > For some where it might be necessary, we use a
> ">=ver" approach.
> > We need to have the versioning numbering scheme
> aligned with that of
> > upstream softwares and a mechanism to have >, <,
> == kind of logical
> > operations possible. I believe IPS currently solves
> this by have its own
> > numbering scheme (in divergence with the upstream
> package versions ?)
> >
> >
> >
> >> 2) Migrate to IPS and extend it - quite a bit of
> effort needed. In
> >> addition to above
> >>   we need to add in more stuff like on-disk
> package file format support,
> >> full
> >>   mirroring (including manifests), ability to
> remove packages from a repo,
> >>   do not use timestamp-based versioning, web-based
> repository browsing
> >>   and package searching etc., and several more
> things.
> >>
> >
> > Going with IPS is what I would vote for, but I am not
> sure if we need to
> > migrate to IPS for V0.8 itself since some of these are
> missing.
> > We can starting working on some of these items while
> staying with SVR4 for
> > 1 more release.
> >
> >
> >
> >> 3) Use Dpkg and Apt from Nexenta's port. This
> gives a wealth of features
> >> and
> >>   readymade solutions with maybe small effort
> needed to put in some
> >> tweaks.
> >>   This is not aligned with what the OpenSolaris
> community is converging on
> >> -
> >>   IPS. A lot of new OpenSolaris features will be
> implemented in the longer
> >> run
> >>   centering on IPS. So in the longer run Dpkg
> might need more effort and
> >>   will be a completely diverged but well-known
> solution.
> >>
> >
> > Nexenta's support is seamless and awesome, but our
> initial idea of
> > providing a distro that showcases technologies at
> opensolaris.org and be
> > aligned as much as possible to work done here will not
> be true any longer.
> > Too many things get affected starting from
> building/packaging/integrating. I
> > vote against the option.
> >
> > regards
> > Shiv
> >
> >
> > _______________________________________________
> > belenix-dev mailing list
> > belenix-dev at opensolaris.org
> >
> http://mail.opensolaris.org/mailman/listinfo/belenix-dev
> >
> >
> 
> 
> -- 
> All Documents adhered to the ISO/IEC 26300 standard file
> format for
> electronic office documents, such as spreadsheets, charts,
> presentations and
> word processing documents from this email address. The
> author does not take
> responsibility of the recipients inability to read
> international standards
> and who use proprietary products such as MS Office.
> See: http://www.openoffice.org/
> Edward O'Callaghan.
> --
> http://fedoraproject.org/wiki/EdwardOcallaghan
> http://moonshine.opn4.org/
> http://www.pcbsd.org/_______________________________________________
> belenix-dev mailing list
> belenix-dev at opensolaris.org
> http://mail.opensolaris.org/mailman/listinfo/belenix-dev


      


From manishchaks at gmail.com  Tue Jul 15 06:59:58 2008
From: manishchaks at gmail.com (Manish Chakravarty)
Date: Tue, 15 Jul 2008 19:29:58 +0530
Subject: [belenix-dev] [belenix-discuss] Thought's on package repository
	structuring
In-Reply-To: <987005.97049.qm@web34207.mail.mud.yahoo.com>
References: <987005.97049.qm@web34207.mail.mud.yahoo.com>
Message-ID: <0D76DB56-3B15-4D37-AA2A-1AEE78BEB408@gmail.com>


On 15-Jul-08, at 4:27 PM, ken mays wrote:

> Agree. Don't break any SVR4 packaging or installation, but extend  
> Belenix to support and utilize IPS.
>
> The Nexenta packaging model is a 'value-add' for Belenix. But IPS  
> has priority to unify ISV development efforts - in which Nexenta  
> will have to eventually support through an IPS version of  
> apt.nexenta.org to keep in line with Sun updates and support as well  
> - as well as Blastwave, Sunfreeware, and other ISVs.
My vote is for keeping and using SVR4 till the time IPS becomes stable  
enough to be considered incorporating into BeleniX


>
>
> Remember, OpenSolaris 2008.11 is THE reference standard - so you'd  
> have to consider what options it provides or doesn't provide to  
> extend from before you add 'features' from the other distros (aka  
> Nexenta...)
>
> ~ Ken Mays
>
>
>
> --- On Tue, 7/15/08, Edward O'Callaghan <victoredwardocallaghan at gmail.com 
> > wrote:
>
>> From: Edward O'Callaghan <victoredwardocallaghan at gmail.com>
>> Subject: Re: [belenix-dev] [belenix-discuss] Thought's on package  
>> repository structuring
>> To: "BeleniX Development" <belenix-dev at opensolaris.org>
>> Date: Tuesday, July 15, 2008, 1:42 AM
>> Hi,
>>
>> We should try to fix IPS as much as we can and run with
>> that.
>> Pooling more development time into a single project would
>> be better for the
>> greater good, else we will be still right where we are now
>> in a few years
>> time.
>>
>> Let unify people, no more Unix wars :p .
>>
>> Our approach should be along these lines:
>> a) Find the most critical issues at hand with IPS - most
>> are already filed
>> such as :
>> http://defect.opensolaris.org/bz/show_bug.cgi?id=1829
>> b) Fix these problems first *before* adding more features,
>> even though some
>> are much needed.
>> c) File all RFE for these features on
>> http://defect.opensolaris.org/bz/
>>
>> We should then create a poll on the BeleniX site for the
>> top 10 that should
>> be worked on first and let the votes count for the top 5
>> that should be done
>> first, for example.
>>
>> If we prioritize as above in this way, we can cover more
>> ground in a more
>> logical manner!
>>
>> Best Regards,
>> Edward O'Callaghan.
>>
>> 2008/7/15 S h i v <shivakumar.gn at gmail.com>:
>>
>>> On Mon, Jul 14, 2008 at 11:59 PM, Moinak Ghosh
>> <moinakg at gmail.com> wrote:
>>>
>>>>
>>>> * <snip>
>>>>  Can't we simply assume the base OpenSolaris
>> system to be present
>>>>  without having to explicitly specify
>> dependencies on it.
>>>>
>>>> * However the above scenarios do not preclude
>> brokenness. It is possible
>>>>  that a new layered software package needs a new
>> version of a base
>>>>  system package, say for example hal. Updating to
>> than new version
>>>>  without updating hal in the base system will
>> cause breakage.
>>>>
>>>>  This scenario can be tackled by extending the
>> dependency mechanism
>>>>  with the ability to express version-specific
>> dependencies like in RPM.
>>>>  Thus trying to update  pkgx where pkgx.depends:
>> hal >= 10 for eg. will
>>>>  fail if installed hal version is 9. This is
>> because hal is part of the
>>>> base
>>>>  system and updating the base system requires a
>> dist-upgrade.
>>>>
>>>
>>> If we consider both the points together, from most top
>> layers we do not
>>> include core package dependency.
>>> For some where it might be necessary, we use a
>> ">=ver" approach.
>>> We need to have the versioning numbering scheme
>> aligned with that of
>>> upstream softwares and a mechanism to have >, <,
>> == kind of logical
>>> operations possible. I believe IPS currently solves
>> this by have its own
>>> numbering scheme (in divergence with the upstream
>> package versions ?)
>>>
>>>
>>>
>>>> 2) Migrate to IPS and extend it - quite a bit of
>> effort needed. In
>>>> addition to above
>>>>  we need to add in more stuff like on-disk
>> package file format support,
>>>> full
>>>>  mirroring (including manifests), ability to
>> remove packages from a repo,
>>>>  do not use timestamp-based versioning, web-based
>> repository browsing
>>>>  and package searching etc., and several more
>> things.
>>>>
>>>
>>> Going with IPS is what I would vote for, but I am not
>> sure if we need to
>>> migrate to IPS for V0.8 itself since some of these are
>> missing.
>>> We can starting working on some of these items while
>> staying with SVR4 for
>>> 1 more release.
>>>
>>>
>>>
>>>> 3) Use Dpkg and Apt from Nexenta's port. This
>> gives a wealth of features
>>>> and
>>>>  readymade solutions with maybe small effort
>> needed to put in some
>>>> tweaks.
>>>>  This is not aligned with what the OpenSolaris
>> community is converging on
>>>> -
>>>>  IPS. A lot of new OpenSolaris features will be
>> implemented in the longer
>>>> run
>>>>  centering on IPS. So in the longer run Dpkg
>> might need more effort and
>>>>  will be a completely diverged but well-known
>> solution.
>>>>
>>>
>>> Nexenta's support is seamless and awesome, but our
>> initial idea of
>>> providing a distro that showcases technologies at
>> opensolaris.org and be
>>> aligned as much as possible to work done here will not
>> be true any longer.
>>> Too many things get affected starting from
>> building/packaging/integrating. I
>>> vote against the option.
>>>
>>> regards
>>> Shiv
>>>
>>>
>>> _______________________________________________
>>> belenix-dev mailing list
>>> belenix-dev at opensolaris.org
>>>
>> http://mail.opensolaris.org/mailman/listinfo/belenix-dev
>>>
>>>
>>
>>
>> -- 
>> All Documents adhered to the ISO/IEC 26300 standard file
>> format for
>> electronic office documents, such as spreadsheets, charts,
>> presentations and
>> word processing documents from this email address. The
>> author does not take
>> responsibility of the recipients inability to read
>> international standards
>> and who use proprietary products such as MS Office.
>> See: http://www.openoffice.org/
>> Edward O'Callaghan.
>> --
>> http://fedoraproject.org/wiki/EdwardOcallaghan
>> http://moonshine.opn4.org/
>> http://www.pcbsd.org/_______________________________________________
>> belenix-dev mailing list
>> belenix-dev at opensolaris.org
>> http://mail.opensolaris.org/mailman/listinfo/belenix-dev
>
>
>
> _______________________________________________
> belenix-dev mailing list
> belenix-dev at opensolaris.org
> http://mail.opensolaris.org/mailman/listinfo/belenix-dev



From sriramnrn at gmail.com  Tue Jul 15 08:25:34 2008
From: sriramnrn at gmail.com (Sriram Narayanan)
Date: Tue, 15 Jul 2008 20:55:34 +0530
Subject: [belenix-dev] [belenix-discuss] Thought's on package repository
	structuring
In-Reply-To: <0D76DB56-3B15-4D37-AA2A-1AEE78BEB408@gmail.com>
References: <987005.97049.qm@web34207.mail.mud.yahoo.com>
	<0D76DB56-3B15-4D37-AA2A-1AEE78BEB408@gmail.com>
Message-ID: <49977f270807150825o7acf3c2bl64b2a94a99ca055e@mail.gmail.com>

On Tue, Jul 15, 2008 at 7:29 PM, Manish Chakravarty
<manishchaks at gmail.com> wrote:
>
> On 15-Jul-08, at 4:27 PM, ken mays wrote:
>
>> Agree. Don't break any SVR4 packaging or installation, but extend
>> Belenix to support and utilize IPS.
>>
>> The Nexenta packaging model is a 'value-add' for Belenix. But IPS
>> has priority to unify ISV development efforts - in which Nexenta
>> will have to eventually support through an IPS version of
>> apt.nexenta.org to keep in line with Sun updates and support as well
>> - as well as Blastwave, Sunfreeware, and other ISVs.
> My vote is for keeping and using SVR4 till the time IPS becomes stable
> enough to be considered incorporating into BeleniX
>

We could indeed continue to use SVR4.

I have one suggestion, though:

Rather than waiting for IPS to become stable, it'd be better to
explore IPS early on, understand it's strengths, learn about future
directions, and help everyone understand IPS limitations (if any), and
discuss how one might address these.

In a lot of ways, IPS is the future for packaging, and it's better
that we start to understand it now than later.

-- Sriram


From moinakg at gmail.com  Tue Jul 15 10:34:45 2008
From: moinakg at gmail.com (Moinak Ghosh)
Date: Tue, 15 Jul 2008 23:04:45 +0530
Subject: [belenix-dev] [belenix-discuss] Thought's on package repository
	structuring
In-Reply-To: <49977f270807150825o7acf3c2bl64b2a94a99ca055e@mail.gmail.com>
References: <987005.97049.qm@web34207.mail.mud.yahoo.com>
	<0D76DB56-3B15-4D37-AA2A-1AEE78BEB408@gmail.com>
	<49977f270807150825o7acf3c2bl64b2a94a99ca055e@mail.gmail.com>
Message-ID: <46fe20470807151034k21dd766an4d8b27b0182b4b47@mail.gmail.com>

On Tue, Jul 15, 2008 at 8:55 PM, Sriram Narayanan <sriramnrn at gmail.com> wrote:
> On Tue, Jul 15, 2008 at 7:29 PM, Manish Chakravarty
> <manishchaks at gmail.com> wrote:
>>
>> On 15-Jul-08, at 4:27 PM, ken mays wrote:
>>
>>> Agree. Don't break any SVR4 packaging or installation, but extend
>>> Belenix to support and utilize IPS.
>>>
>>> The Nexenta packaging model is a 'value-add' for Belenix. But IPS
>>> has priority to unify ISV development efforts - in which Nexenta
>>> will have to eventually support through an IPS version of
>>> apt.nexenta.org to keep in line with Sun updates and support as well
>>> - as well as Blastwave, Sunfreeware, and other ISVs.
>> My vote is for keeping and using SVR4 till the time IPS becomes stable
>> enough to be considered incorporating into BeleniX
>>
>
> We could indeed continue to use SVR4.
>
> I have one suggestion, though:
>
> Rather than waiting for IPS to become stable, it'd be better to
> explore IPS early on, understand it's strengths, learn about future
> directions, and help everyone understand IPS limitations (if any), and
> discuss how one might address these.
>
> In a lot of ways, IPS is the future for packaging, and it's better
> that we start to understand it now than later.

   Ok since the consensus is towards IPS, I will list a few of the top
priorities
   that we should consider:

   * On-disk format. This is very impt. Tying package installation to
a repository
   seems to be a heavy-handed approach.

   * Good mirroring support ... possibly via the well-established and
mature rsync.
   We do not need to re-invent the wheel here.

   * Postrun support. Dpkg avoids integrated packaging scripts and in Dpkg
   package installation is a matter of laying down bits on disk. This
is the same
   thing that IPS does. However Dpkg also allows an explicit Configure stage
   where postinstall scripts can be run to setup the software if needed.The
   package state indicates whether it is configured or not. A failure during
   Configure is logged and one can fix the cause and rerun the Configure stage.
   Configured is a first-class package state. So other packages can indicate a
   dependency on a certain package to be in Configured state.
   We need this functionality in IPS. Currently lack of this is
resulting in ugly
   workarounds like the way the JDS folks are introducing a bunch of
SMF services
   to tackle updating various caches. I really get butterflies in my
stomach when I
   think of the approach.

   * IPS creates snapshots during package installation and if the download phase
   is cancelled by pressing CTRL+C or fails it asks to reboot to a
snapshot. This is
   crazy! An inappropriate use of the power of ZFS. I have been told
that the reboot
   message  during package download failure has been fixed and the download does
   not directly stream files into the live filesystem ... this needs
to be checked.

   * IPS using a custom port for HTTP traffic is a problem esp. if
accessing over a
   firewall or hosting by third-parties. Why not simply use Apache and
run the depotd
   at the back.

   * We need a GUI package manager ... "Imagine" possibly.

   * I do not understand why IPS has to be multi-platform ? We are
trying to solve
   "OpenSolaris" packaging Not a Grand Unified Packaging Solution for Humanity
   IMHO. I do however understand the possibility of running the depotd on other
   platforms.

   * A published package cannot be removed from the repository.

   * IPS used to store indexes in a sparse DB file, I think this has
been fixed now.

   * IPS is sloooww. I recently did an image-update inside a VMWare
ESX Server on a
   very high-end dedicated metal running only a single VM in the US.
It took 5 mins to
   compute the plan and another 30mins to update. This is while in the
US. Imagine
   how long it takes from other parts of the world!

   * Using timestamps for versioning confuses me and makes for messy
long version
   strings.

   * Of course add to these the original topics I mentioned including
more flexible
   dependency control.

One last point not directly related to IPS but related to packaging in
general. I believe
we should completely drop the idea of sparse-root zones in BeleniX.
Simplifies life
and duplication can be reduced by using ZFS clones for Zones.

Regards,
Moinak.

>
> -- Sriram
> _______________________________________________
> belenix-dev mailing list
> belenix-dev at opensolaris.org
> http://mail.opensolaris.org/mailman/listinfo/belenix-dev
>


From victoredwardocallaghan at gmail.com  Tue Jul 15 16:15:32 2008
From: victoredwardocallaghan at gmail.com (Edward O'Callaghan)
Date: Tue, 15 Jul 2008 16:15:32 -0700
Subject: [belenix-dev] [belenix-discuss] Thought's on package repository
	structuring
In-Reply-To: <46fe20470807151034k21dd766an4d8b27b0182b4b47@mail.gmail.com>
References: <987005.97049.qm@web34207.mail.mud.yahoo.com>
	<0D76DB56-3B15-4D37-AA2A-1AEE78BEB408@gmail.com>
	<49977f270807150825o7acf3c2bl64b2a94a99ca055e@mail.gmail.com>
	<46fe20470807151034k21dd766an4d8b27b0182b4b47@mail.gmail.com>
Message-ID: <cbc95d950807151615s54e40d0bs4a62ea4b34c169c7@mail.gmail.com>

In regards to :

"  * IPS creates snapshots during package installation and if the download
phase
  is cancelled by pressing CTRL+C or fails it asks to reboot to a
snapshot. This is
  crazy! An inappropriate use of the power of ZFS. I have been told
that the reboot
  message  during package download failure has been fixed and the download
does
  not directly stream files into the live filesystem ... this needs
to be checked."

http://defect.opensolaris.org/bz/show_bug.cgi?id=1249
FIXINSOURCE.

Regards,
Edward.

2008/7/15 Moinak Ghosh <moinakg at gmail.com>:

> On Tue, Jul 15, 2008 at 8:55 PM, Sriram Narayanan <sriramnrn at gmail.com>
> wrote:
> > On Tue, Jul 15, 2008 at 7:29 PM, Manish Chakravarty
> > <manishchaks at gmail.com> wrote:
> >>
> >> On 15-Jul-08, at 4:27 PM, ken mays wrote:
> >>
> >>> Agree. Don't break any SVR4 packaging or installation, but extend
> >>> Belenix to support and utilize IPS.
> >>>
> >>> The Nexenta packaging model is a 'value-add' for Belenix. But IPS
> >>> has priority to unify ISV development efforts - in which Nexenta
> >>> will have to eventually support through an IPS version of
> >>> apt.nexenta.org to keep in line with Sun updates and support as well
> >>> - as well as Blastwave, Sunfreeware, and other ISVs.
> >> My vote is for keeping and using SVR4 till the time IPS becomes stable
> >> enough to be considered incorporating into BeleniX
> >>
> >
> > We could indeed continue to use SVR4.
> >
> > I have one suggestion, though:
> >
> > Rather than waiting for IPS to become stable, it'd be better to
> > explore IPS early on, understand it's strengths, learn about future
> > directions, and help everyone understand IPS limitations (if any), and
> > discuss how one might address these.
> >
> > In a lot of ways, IPS is the future for packaging, and it's better
> > that we start to understand it now than later.
>
>    Ok since the consensus is towards IPS, I will list a few of the top
> priorities
>   that we should consider:
>
>   * On-disk format. This is very impt. Tying package installation to
> a repository
>   seems to be a heavy-handed approach.
>
>   * Good mirroring support ... possibly via the well-established and
> mature rsync.
>   We do not need to re-invent the wheel here.
>
>   * Postrun support. Dpkg avoids integrated packaging scripts and in Dpkg
>   package installation is a matter of laying down bits on disk. This
> is the same
>   thing that IPS does. However Dpkg also allows an explicit Configure stage
>   where postinstall scripts can be run to setup the software if needed.The
>   package state indicates whether it is configured or not. A failure during
>   Configure is logged and one can fix the cause and rerun the Configure
> stage.
>   Configured is a first-class package state. So other packages can indicate
> a
>   dependency on a certain package to be in Configured state.
>   We need this functionality in IPS. Currently lack of this is
> resulting in ugly
>   workarounds like the way the JDS folks are introducing a bunch of
> SMF services
>   to tackle updating various caches. I really get butterflies in my
> stomach when I
>   think of the approach.
>
>   * IPS creates snapshots during package installation and if the download
> phase
>   is cancelled by pressing CTRL+C or fails it asks to reboot to a
> snapshot. This is
>   crazy! An inappropriate use of the power of ZFS. I have been told
> that the reboot
>   message  during package download failure has been fixed and the download
> does
>   not directly stream files into the live filesystem ... this needs
> to be checked.
>
>   * IPS using a custom port for HTTP traffic is a problem esp. if
> accessing over a
>   firewall or hosting by third-parties. Why not simply use Apache and
> run the depotd
>   at the back.
>
>   * We need a GUI package manager ... "Imagine" possibly.
>
>   * I do not understand why IPS has to be multi-platform ? We are
> trying to solve
>   "OpenSolaris" packaging Not a Grand Unified Packaging Solution for
> Humanity
>   IMHO. I do however understand the possibility of running the depotd on
> other
>   platforms.
>
>   * A published package cannot be removed from the repository.
>
>   * IPS used to store indexes in a sparse DB file, I think this has
> been fixed now.
>
>   * IPS is sloooww. I recently did an image-update inside a VMWare
> ESX Server on a
>   very high-end dedicated metal running only a single VM in the US.
> It took 5 mins to
>   compute the plan and another 30mins to update. This is while in the
> US. Imagine
>   how long it takes from other parts of the world!
>
>   * Using timestamps for versioning confuses me and makes for messy
> long version
>   strings.
>
>   * Of course add to these the original topics I mentioned including
> more flexible
>   dependency control.
>
> One last point not directly related to IPS but related to packaging in
> general. I believe
> we should completely drop the idea of sparse-root zones in BeleniX.
> Simplifies life
> and duplication can be reduced by using ZFS clones for Zones.
>
> Regards,
> Moinak.
>
> >
> > -- Sriram
> > _______________________________________________
> > belenix-dev mailing list
> > belenix-dev at opensolaris.org
> > http://mail.opensolaris.org/mailman/listinfo/belenix-dev
> >
> _______________________________________________
> belenix-dev mailing list
> belenix-dev at opensolaris.org
> http://mail.opensolaris.org/mailman/listinfo/belenix-dev
>



-- 
All Documents adhered to the ISO/IEC 26300 standard file format for
electronic office documents, such as spreadsheets, charts, presentations and
word processing documents from this email address. The author does not take
responsibility of the recipients inability to read international standards
and who use proprietary products such as MS Office.
See: http://www.openoffice.org/
Edward O'Callaghan.
--
http://fedoraproject.org/wiki/EdwardOcallaghan
http://moonshine.opn4.org/
http://www.pcbsd.org/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.opensolaris.org/pipermail/belenix-dev/attachments/20080715/ad7c53b1/attachment.html>

From moinakg at gmail.com  Tue Jul 15 20:31:21 2008
From: moinakg at gmail.com (Moinak Ghosh)
Date: Wed, 16 Jul 2008 09:01:21 +0530
Subject: [belenix-dev] [belenix-discuss] Thought's on package repository
	structuring
In-Reply-To: <cbc95d950807151615s54e40d0bs4a62ea4b34c169c7@mail.gmail.com>
References: <987005.97049.qm@web34207.mail.mud.yahoo.com>
	<0D76DB56-3B15-4D37-AA2A-1AEE78BEB408@gmail.com>
	<49977f270807150825o7acf3c2bl64b2a94a99ca055e@mail.gmail.com>
	<46fe20470807151034k21dd766an4d8b27b0182b4b47@mail.gmail.com>
	<cbc95d950807151615s54e40d0bs4a62ea4b34c169c7@mail.gmail.com>
Message-ID: <46fe20470807152031i742503a1qa106d61cca490224@mail.gmail.com>

On Wed, Jul 16, 2008 at 4:45 AM, Edward O'Callaghan
<victoredwardocallaghan at gmail.com> wrote:
> In regards to :
>
> "  * IPS creates snapshots during package installation and if the download
> phase
>   is cancelled by pressing CTRL+C or fails it asks to reboot to a
> snapshot. This is
>   crazy! An inappropriate use of the power of ZFS. I have been told
> that the reboot
>   message  during package download failure has been fixed and the download
> does
>   not directly stream files into the live filesystem ... this needs
> to be checked."
>
> http://defect.opensolaris.org/bz/show_bug.cgi?id=1249
> FIXINSOURCE.

   Thanks. That ticks off one item in the list. However there is one more point
   that needs mention:

   I am seeing people reporting problems with image-update and their ZFS
   list output is cluttered with snapshots. We need some way of managing
   all these snapshots such that they do not grow endlessly.

   In addition by default we need to only have 2 boot environments at any time.
   One being the previous working version and the other being the current
   active version. It should of course be possible for the user to configure
   keeping more boot environments around.

Regards,
Moinak.

>
> Regards,
> Edward.
>


From victoredwardocallaghan at gmail.com  Wed Jul 16 00:56:31 2008
From: victoredwardocallaghan at gmail.com (Edward O'Callaghan)
Date: Wed, 16 Jul 2008 17:56:31 +1000
Subject: [belenix-dev] [belenix-discuss] Thought's on package repository
	structuring
In-Reply-To: <46fe20470807152031i742503a1qa106d61cca490224@mail.gmail.com>
References: <987005.97049.qm@web34207.mail.mud.yahoo.com>
	<0D76DB56-3B15-4D37-AA2A-1AEE78BEB408@gmail.com>
	<49977f270807150825o7acf3c2bl64b2a94a99ca055e@mail.gmail.com>
	<46fe20470807151034k21dd766an4d8b27b0182b4b47@mail.gmail.com>
	<cbc95d950807151615s54e40d0bs4a62ea4b34c169c7@mail.gmail.com>
	<46fe20470807152031i742503a1qa106d61cca490224@mail.gmail.com>
Message-ID: <cbc95d950807160056x564cb0e1ma376a03fe6d28a41@mail.gmail.com>

Moinak,

See: http://defect.opensolaris.org/bz/show_bug.cgi?id=2548

Regards,

Edward.

2008/7/16 Moinak Ghosh <moinakg at gmail.com>:

> On Wed, Jul 16, 2008 at 4:45 AM, Edward O'Callaghan
> <victoredwardocallaghan at gmail.com> wrote:
> > In regards to :
> >
> > "  * IPS creates snapshots during package installation and if the
> download
> > phase
> >   is cancelled by pressing CTRL+C or fails it asks to reboot to a
> > snapshot. This is
> >   crazy! An inappropriate use of the power of ZFS. I have been told
> > that the reboot
> >   message  during package download failure has been fixed and the
> download
> > does
> >   not directly stream files into the live filesystem ... this needs
> > to be checked."
> >
> > http://defect.opensolaris.org/bz/show_bug.cgi?id=1249
> > FIXINSOURCE.
>
>    Thanks. That ticks off one item in the list. However there is one more
> point
>   that needs mention:
>
>   I am seeing people reporting problems with image-update and their ZFS
>   list output is cluttered with snapshots. We need some way of managing
>   all these snapshots such that they do not grow endlessly.
>
>   In addition by default we need to only have 2 boot environments at any
> time.
>   One being the previous working version and the other being the current
>   active version. It should of course be possible for the user to configure
>   keeping more boot environments around.
>
> Regards,
> Moinak.
>
> >
> > Regards,
> > Edward.
> >
> _______________________________________________
> belenix-dev mailing list
> belenix-dev at opensolaris.org
> http://mail.opensolaris.org/mailman/listinfo/belenix-dev
>



-- 
All Documents adhered to the ISO/IEC 26300 standard file format for
electronic office documents, such as spreadsheets, charts, presentations and
word processing documents from this email address. The author does not take
responsibility of the recipients inability to read international standards
and who use proprietary products such as MS Office.
See: http://www.openoffice.org/
Edward O'Callaghan.
--
http://fedoraproject.org/wiki/EdwardOcallaghan
http://moonshine.opn4.org/
http://www.pcbsd.org/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.opensolaris.org/pipermail/belenix-dev/attachments/20080716/fa2e7e34/attachment.html>

From manishchaks at gmail.com  Wed Jul 16 04:53:31 2008
From: manishchaks at gmail.com (Manish Chakravarty)
Date: Wed, 16 Jul 2008 17:23:31 +0530
Subject: [belenix-dev] [belenix-discuss] Thought's on package repository
	structuring
In-Reply-To: <49977f270807150825o7acf3c2bl64b2a94a99ca055e@mail.gmail.com>
References: <987005.97049.qm@web34207.mail.mud.yahoo.com>
	<0D76DB56-3B15-4D37-AA2A-1AEE78BEB408@gmail.com>
	<49977f270807150825o7acf3c2bl64b2a94a99ca055e@mail.gmail.com>
Message-ID: <b4dbee910807160453r7a29699hfc8fef191345cdc3@mail.gmail.com>

[...snip...]
>
> Rather than waiting for IPS to become stable, it'd be better to
> explore IPS early on, understand it's strengths, learn about future
> directions, and help everyone understand IPS limitations (if any), and
> discuss how one might address these.
>
> In a lot of ways, IPS is the future for packaging, and it's better
> that we start to understand it now than later.

It's the future of packaging for us only if we decide we will keep IPS
in belenix :)

I am not a traditionalist ( and am _nowhere_ near an old-timer )

This is more of me saying "no IPS till it fits us " as opposed to
"No, I will use SVR4 since I've been using it since 1984" [1]

Regards,
Manish

[1] = I was born in 1984


From moinakg at gmail.com  Wed Jul 16 07:21:29 2008
From: moinakg at gmail.com (Moinak Ghosh)
Date: Wed, 16 Jul 2008 19:51:29 +0530
Subject: [belenix-dev] [belenix-discuss] Thought's on package repository
	structuring
In-Reply-To: <cbc95d950807160056x564cb0e1ma376a03fe6d28a41@mail.gmail.com>
References: <987005.97049.qm@web34207.mail.mud.yahoo.com>
	<0D76DB56-3B15-4D37-AA2A-1AEE78BEB408@gmail.com>
	<49977f270807150825o7acf3c2bl64b2a94a99ca055e@mail.gmail.com>
	<46fe20470807151034k21dd766an4d8b27b0182b4b47@mail.gmail.com>
	<cbc95d950807151615s54e40d0bs4a62ea4b34c169c7@mail.gmail.com>
	<46fe20470807152031i742503a1qa106d61cca490224@mail.gmail.com>
	<cbc95d950807160056x564cb0e1ma376a03fe6d28a41@mail.gmail.com>
Message-ID: <46fe20470807160721u4640dbfew2212954655d84848@mail.gmail.com>

On Wed, Jul 16, 2008 at 1:26 PM, Edward O'Callaghan
<victoredwardocallaghan at gmail.com> wrote:
> Moinak,
>
> See: http://defect.opensolaris.org/bz/show_bug.cgi?id=2548

   Good idea. But my point was having too many BEs lingering around and eating
   disk space is not a good idea either. There should be a policy mechanism that
   allows deletion of old or unneeded BEs automatically.

Regards,
Moinak.

>
> Regards,
>
> Edward.
>
> 2008/7/16 Moinak Ghosh <moinakg at gmail.com>:
>>
>> On Wed, Jul 16, 2008 at 4:45 AM, Edward O'Callaghan
>> <victoredwardocallaghan at gmail.com> wrote:
>> > In regards to :
>> >
>> > "  * IPS creates snapshots during package installation and if the
>> > download
>> > phase
>> >   is cancelled by pressing CTRL+C or fails it asks to reboot to a
>> > snapshot. This is
>> >   crazy! An inappropriate use of the power of ZFS. I have been told
>> > that the reboot
>> >   message  during package download failure has been fixed and the
>> > download
>> > does
>> >   not directly stream files into the live filesystem ... this needs
>> > to be checked."
>> >
>> > http://defect.opensolaris.org/bz/show_bug.cgi?id=1249
>> > FIXINSOURCE.
>>
>>   Thanks. That ticks off one item in the list. However there is one more
>> point
>>   that needs mention:
>>
>>   I am seeing people reporting problems with image-update and their ZFS
>>   list output is cluttered with snapshots. We need some way of managing
>>   all these snapshots such that they do not grow endlessly.
>>
>>   In addition by default we need to only have 2 boot environments at any
>> time.
>>   One being the previous working version and the other being the current
>>   active version. It should of course be possible for the user to
>> configure
>>   keeping more boot environments around.
>>
>> Regards,
>> Moinak.
>>
>> >
>> > Regards,
>> > Edward.
>> >
>> _______________________________________________
>> belenix-dev mailing list
>> belenix-dev at opensolaris.org
>> http://mail.opensolaris.org/mailman/listinfo/belenix-dev
>
>
>
> --
> All Documents adhered to the ISO/IEC 26300 standard file format for
> electronic office documents, such as spreadsheets, charts, presentations and
> word processing documents from this email address. The author does not take
> responsibility of the recipients inability to read international standards
> and who use proprietary products such as MS Office.
> See: http://www.openoffice.org/
> Edward O'Callaghan.
> --
> http://fedoraproject.org/wiki/EdwardOcallaghan
> http://moonshine.opn4.org/
> http://www.pcbsd.org/
> _______________________________________________
> belenix-dev mailing list
> belenix-dev at opensolaris.org
> http://mail.opensolaris.org/mailman/listinfo/belenix-dev
>
>


From moinakg at gmail.com  Wed Jul 16 20:48:16 2008
From: moinakg at gmail.com (Moinak Ghosh)
Date: Thu, 17 Jul 2008 09:18:16 +0530
Subject: [belenix-dev] [belenix-discuss] Thought's on package repository
	structuring
In-Reply-To: <b4dbee910807160453r7a29699hfc8fef191345cdc3@mail.gmail.com>
References: <987005.97049.qm@web34207.mail.mud.yahoo.com>
	<0D76DB56-3B15-4D37-AA2A-1AEE78BEB408@gmail.com>
	<49977f270807150825o7acf3c2bl64b2a94a99ca055e@mail.gmail.com>
	<b4dbee910807160453r7a29699hfc8fef191345cdc3@mail.gmail.com>
Message-ID: <46fe20470807162048vdd97d0nea5f57ac6c4265f8@mail.gmail.com>

On Wed, Jul 16, 2008 at 5:23 PM, Manish Chakravarty
<manishchaks at gmail.com> wrote:
> [...snip...]
>>
>> Rather than waiting for IPS to become stable, it'd be better to
>> explore IPS early on, understand it's strengths, learn about future
>> directions, and help everyone understand IPS limitations (if any), and
>> discuss how one might address these.
>>
>> In a lot of ways, IPS is the future for packaging, and it's better
>> that we start to understand it now than later.
>
> It's the future of packaging for us only if we decide we will keep IPS
> in belenix :)
>
> I am not a traditionalist ( and am _nowhere_ near an old-timer )
>
> This is more of me saying "no IPS till it fits us " as opposed to
> "No, I will use SVR4 since I've been using it since 1984" [1]

   Yes agreed. That is why for now we have to adapt pkg-get from
   Blastwave for our own purposes.

Regards,
Moinak.

>
> Regards,
> Manish
>
> [1] = I was born in 1984
> _______________________________________________
> belenix-dev mailing list
> belenix-dev at opensolaris.org
> http://mail.opensolaris.org/mailman/listinfo/belenix-dev
>


From victoredwardocallaghan at gmail.com  Wed Jul 16 21:33:46 2008
From: victoredwardocallaghan at gmail.com (Edward O'Callaghan)
Date: Thu, 17 Jul 2008 14:33:46 +1000
Subject: [belenix-dev] [belenix-discuss] Thought's on package repository
	structuring
In-Reply-To: <46fe20470807160721u4640dbfew2212954655d84848@mail.gmail.com>
References: <987005.97049.qm@web34207.mail.mud.yahoo.com>
	<0D76DB56-3B15-4D37-AA2A-1AEE78BEB408@gmail.com>
	<49977f270807150825o7acf3c2bl64b2a94a99ca055e@mail.gmail.com>
	<46fe20470807151034k21dd766an4d8b27b0182b4b47@mail.gmail.com>
	<cbc95d950807151615s54e40d0bs4a62ea4b34c169c7@mail.gmail.com>
	<46fe20470807152031i742503a1qa106d61cca490224@mail.gmail.com>
	<cbc95d950807160056x564cb0e1ma376a03fe6d28a41@mail.gmail.com>
	<46fe20470807160721u4640dbfew2212954655d84848@mail.gmail.com>
Message-ID: <cbc95d950807162133m692e8a83h3296a579aea944a5@mail.gmail.com>

..and that's what I *have* reported Moinak..
However, I got my hands full with ext3 support and GRUB menu generator ..
Thus, someone needs to assign them self to this and commit a patch. I would
not use the SMF idea that other guy had :p !
It should be part of the libbe API upgrade chain..

if(beadm list >= 3){
return (find oldest snv);
}
print "would you like to remove this old snv %i ? :", snv_version
...
else{ continue; }


Thanks,
Edward.

2008/7/17 Moinak Ghosh <moinakg at gmail.com>:

> On Wed, Jul 16, 2008 at 1:26 PM, Edward O'Callaghan
> <victoredwardocallaghan at gmail.com> wrote:
> > Moinak,
> >
> > See: http://defect.opensolaris.org/bz/show_bug.cgi?id=2548
>
>    Good idea. But my point was having too many BEs lingering around and
> eating
>   disk space is not a good idea either. There should be a policy mechanism
> that
>   allows deletion of old or unneeded BEs automatically.
>
> Regards,
> Moinak.
>
> >
> > Regards,
> >
> > Edward.
> >
> > 2008/7/16 Moinak Ghosh <moinakg at gmail.com>:
> >>
> >> On Wed, Jul 16, 2008 at 4:45 AM, Edward O'Callaghan
> >> <victoredwardocallaghan at gmail.com> wrote:
> >> > In regards to :
> >> >
> >> > "  * IPS creates snapshots during package installation and if the
> >> > download
> >> > phase
> >> >   is cancelled by pressing CTRL+C or fails it asks to reboot to a
> >> > snapshot. This is
> >> >   crazy! An inappropriate use of the power of ZFS. I have been told
> >> > that the reboot
> >> >   message  during package download failure has been fixed and the
> >> > download
> >> > does
> >> >   not directly stream files into the live filesystem ... this needs
> >> > to be checked."
> >> >
> >> > http://defect.opensolaris.org/bz/show_bug.cgi?id=1249
> >> > FIXINSOURCE.
> >>
> >>   Thanks. That ticks off one item in the list. However there is one more
> >> point
> >>   that needs mention:
> >>
> >>   I am seeing people reporting problems with image-update and their ZFS
> >>   list output is cluttered with snapshots. We need some way of managing
> >>   all these snapshots such that they do not grow endlessly.
> >>
> >>   In addition by default we need to only have 2 boot environments at any
> >> time.
> >>   One being the previous working version and the other being the current
> >>   active version. It should of course be possible for the user to
> >> configure
> >>   keeping more boot environments around.
> >>
> >> Regards,
> >> Moinak.
> >>
> >> >
> >> > Regards,
> >> > Edward.
> >> >
> >> _______________________________________________
> >> belenix-dev mailing list
> >> belenix-dev at opensolaris.org
> >> http://mail.opensolaris.org/mailman/listinfo/belenix-dev
> >
> >
> >
> > --
> > All Documents adhered to the ISO/IEC 26300 standard file format for
> > electronic office documents, such as spreadsheets, charts, presentations
> and
> > word processing documents from this email address. The author does not
> take
> > responsibility of the recipients inability to read international
> standards
> > and who use proprietary products such as MS Office.
> > See: http://www.openoffice.org/
> > Edward O'Callaghan.
> > --
> > http://fedoraproject.org/wiki/EdwardOcallaghan
> > http://moonshine.opn4.org/
> > http://www.pcbsd.org/
> > _______________________________________________
> > belenix-dev mailing list
> > belenix-dev at opensolaris.org
> > http://mail.opensolaris.org/mailman/listinfo/belenix-dev
> >
> >
> _______________________________________________
> belenix-dev mailing list
> belenix-dev at opensolaris.org
> http://mail.opensolaris.org/mailman/listinfo/belenix-dev
>



-- 
All Documents adhered to the ISO/IEC 26300 standard file format for
electronic office documents, such as spreadsheets, charts, presentations and
word processing documents from this email address. The author does not take
responsibility of the recipients inability to read international standards
and who use proprietary products such as MS Office.
See: http://www.openoffice.org/
Edward O'Callaghan.
--
http://fedoraproject.org/wiki/EdwardOcallaghan
http://moonshine.opn4.org/
http://www.pcbsd.org/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.opensolaris.org/pipermail/belenix-dev/attachments/20080717/e4b79ad4/attachment.html>

From russiane39 at gmail.com  Wed Jul 16 22:58:55 2008
From: russiane39 at gmail.com (Michael Kosarev)
Date: Thu, 17 Jul 2008 09:58:55 +0400
Subject: [belenix-dev] belenix-dev Digest, Vol 5, Issue 5
In-Reply-To: <mailman.9047.1216269301.622.belenix-dev@opensolaris.org>
References: <mailman.9047.1216269301.622.belenix-dev@opensolaris.org>
Message-ID: <cf4355090807162258p4829da26k926562fcd15d552b@mail.gmail.com>

Well, as for me - I hate IPS, I think it's evil's creation and nothing
else. There is so much alternatives around, I vote for Pacman and
Archlinux Build System (http://wiki.archlinux.org/index.php/Pacman),
there is only benefits:
1) Written in C, not that phyton stuff like IPS - so it works fast
2) Already available Package Build System, so we don't need to invent wheel
3) Ability not only to install pre-built packages, but to compile them yourself
4) Many GUI frontends already available

--
With best regards from Russia, Mike


From maybird1776 at yahoo.com  Thu Jul 17 06:28:24 2008
From: maybird1776 at yahoo.com (ken mays)
Date: Thu, 17 Jul 2008 06:28:24 -0700 (PDT)
Subject: [belenix-dev] Firefox 3.0.1 released
Message-ID: <259875.71313.qm@web34202.mail.mud.yahoo.com>

Wonder if this could be in Belenix 0.7.1....

http://www.mozilla.com/en-US/firefox/3.0.1/releasenotes/
What?s New in Firefox 3.0.1

Firefox 3.0.1 fixed several issues found in Firefox 3.

Fixed several security issues. 
Fixed several stability issues. 
Fixed an issue where the phishing and malware database did not update on first launch. 
Under certain circumstances, Firefox 3.0 did not properly save the SSL certificate exceptions list. 


      


From moinakg at gmail.com  Thu Jul 17 08:23:45 2008
From: moinakg at gmail.com (Moinak Ghosh)
Date: Thu, 17 Jul 2008 20:53:45 +0530
Subject: [belenix-dev] Firefox 3.0.1 released
In-Reply-To: <259875.71313.qm@web34202.mail.mud.yahoo.com>
References: <259875.71313.qm@web34202.mail.mud.yahoo.com>
Message-ID: <46fe20470807170823h3315ed3cje0125309c80079f2@mail.gmail.com>

Thanks for the notice ... will try considering we are shooting for freezing
on the ISO by tomorrow.

Regards,
Moinak.

On Thu, Jul 17, 2008 at 6:58 PM, ken mays <maybird1776 at yahoo.com> wrote:
> Wonder if this could be in Belenix 0.7.1....
>
> http://www.mozilla.com/en-US/firefox/3.0.1/releasenotes/
> What's New in Firefox 3.0.1
>
> Firefox 3.0.1 fixed several issues found in Firefox 3.
>
> Fixed several security issues.
> Fixed several stability issues.
> Fixed an issue where the phishing and malware database did not update on first launch.
> Under certain circumstances, Firefox 3.0 did not properly save the SSL certificate exceptions list.
>
>
>
> _______________________________________________
> belenix-dev mailing list
> belenix-dev at opensolaris.org
> http://mail.opensolaris.org/mailman/listinfo/belenix-dev
>


From shivakumar.gn at gmail.com  Fri Jul 18 19:31:07 2008
From: shivakumar.gn at gmail.com (S h i v)
Date: Sat, 19 Jul 2008 08:01:07 +0530
Subject: [belenix-dev] BeleniX 0.7.1 update release available
Message-ID: <319ee2b10807181931g1e14b96ev62166f9ceb677c8@mail.gmail.com>

Hello All,

The first update to the 0.7 release is now available. Give it a try
and provide us the feedback.

Download location : http://www.belenix.org/download
(torrent is not yet available. will be available soon)

Bugs/Feature Requests may be logged at
http://sourceforge.net/tracker/?group_id=216118

This update brings in the latest development OpenSolaris build 93,
updates to KDE 3.5.9, firefox 3.0.1, ability to create zones among
other changes, bugfixes. This release includes the latest Caiman
installer due to which upgrades from this release will become possible
going forward.

Complete list of changes:

    * Based on ON Build 93 that has new drivers (like ATIgfx) among other stuff.
    * Included the rum driver.
    * Nvidia driver updated to 173.14.05.
    * OSS updated to 4.0-1016.
    * Updated Fully Open X bits.
    * KDE updated to 3.5.9 and some upstream patches removed
    * Firefox 3.0.1
    * /sbin/sh is now ksh93.
    * Sham's RAM based Boot integrated. In Grub screen select more
options to see that boot option.
      Install from RAM is possible and is *fast*. See Sham's Blog for
details (http://blogs.sun.com/sham/entry/belenix_0_7_can_boot).
    * Caiman Installer updated to current version. Grub boot entries
for Windows partitions are now automatically added. Detecting Linux
partitions is a work in progress.
    * Added PowerTOP.
    * Added XVM PV drivers to support booting inside domU.
    * Qt 3.x is now built in both 32Bit and 64Bit versions.
    * Gtk-Qt3 is fixed to build with proper Solaris build flags so the
nagging warning about /proc/.../cmdline does not appear.
    * Updated man pages to new release.
    * OpenMotif updated to fix some brokenness.
    * Ability to create zones via ZFS snapshots. See
http://www.belenix.org/content/How-do-I-create-Zones-BeleniX ?.
    * Added Single-User Console boot option when booting from harddisk.
    * Many bugfixes. Fixed Usbdump in livecd mode.
    * More packages available via get-pkgs utility including various
multimedia stuff. New pkg.belenix.org repository now online. This is
Not yet an IPS repository however.
    * OpenSolaris G11N packages now available in the repository.
    * Setting is applied during install to trim ZFS ARC to 50% of RAM
if there is 1GB RAM or less.

Pending Issues

    * Sendmail cribs while booting off harddisk.
    * BeleniX still does not boot on non-SSE CPUs (to be handled in 0.7.2)


Website: www.belenix.org
Discussion List : belenix-discuss at opensolaris.org
IRC : #belenix @ freenode.net

best regards
Shiv


From shivakumar.gn at gmail.com  Fri Jul 18 20:29:38 2008
From: shivakumar.gn at gmail.com (S h i v)
Date: Sat, 19 Jul 2008 08:59:38 +0530
Subject: [belenix-dev] BeleniX 0.7.1 update release available
In-Reply-To: <319ee2b10807181931g1e14b96ev62166f9ceb677c8@mail.gmail.com>
References: <319ee2b10807181931g1e14b96ev62166f9ceb677c8@mail.gmail.com>
Message-ID: <319ee2b10807182029s7688b04ag4137fe81ec94a561@mail.gmail.com>

The belenix.org website has undergone a sea of changes and provides
nice options to collaborate with each other and communicate
information.
Feel free to register on the belenix.org website, mark your locations
on the map, make use of the forums, use scoopzone, submit
opensolaris/belenix related stories... :)

-Shiv


On Sat, Jul 19, 2008 at 8:01 AM, S h i v <shivakumar.gn at gmail.com> wrote:
> Hello All,
>
> The first update to the 0.7 release is now available. Give it a try
> and provide us the feedback.
>
> Download location : http://www.belenix.org/download
> (torrent is not yet available. will be available soon)
>
> Bugs/Feature Requests may be logged at
> http://sourceforge.net/tracker/?group_id=216118
>
> This update brings in the latest development OpenSolaris build 93,
> updates to KDE 3.5.9, firefox 3.0.1, ability to create zones among
> other changes, bugfixes. This release includes the latest Caiman
> installer due to which upgrades from this release will become possible
> going forward.
>
> Complete list of changes:
>
>    * Based on ON Build 93 that has new drivers (like ATIgfx) among other stuff.
>    * Included the rum driver.
>    * Nvidia driver updated to 173.14.05.
>    * OSS updated to 4.0-1016.
>    * Updated Fully Open X bits.
>    * KDE updated to 3.5.9 and some upstream patches removed
>    * Firefox 3.0.1
>    * /sbin/sh is now ksh93.
>    * Sham's RAM based Boot integrated. In Grub screen select more
> options to see that boot option.
>      Install from RAM is possible and is *fast*. See Sham's Blog for
> details (http://blogs.sun.com/sham/entry/belenix_0_7_can_boot).
>    * Caiman Installer updated to current version. Grub boot entries
> for Windows partitions are now automatically added. Detecting Linux
> partitions is a work in progress.
>    * Added PowerTOP.
>    * Added XVM PV drivers to support booting inside domU.
>    * Qt 3.x is now built in both 32Bit and 64Bit versions.
>    * Gtk-Qt3 is fixed to build with proper Solaris build flags so the
> nagging warning about /proc/.../cmdline does not appear.
>    * Updated man pages to new release.
>    * OpenMotif updated to fix some brokenness.
>    * Ability to create zones via ZFS snapshots. See
> http://www.belenix.org/content/How-do-I-create-Zones-BeleniX ?.
>    * Added Single-User Console boot option when booting from harddisk.
>    * Many bugfixes. Fixed Usbdump in livecd mode.
>    * More packages available via get-pkgs utility including various
> multimedia stuff. New pkg.belenix.org repository now online. This is
> Not yet an IPS repository however.
>    * OpenSolaris G11N packages now available in the repository.
>    * Setting is applied during install to trim ZFS ARC to 50% of RAM
> if there is 1GB RAM or less.
>
> Pending Issues
>
>    * Sendmail cribs while booting off harddisk.
>    * BeleniX still does not boot on non-SSE CPUs (to be handled in 0.7.2)
>
>
> Website: www.belenix.org
> Discussion List : belenix-discuss at opensolaris.org
> IRC : #belenix @ freenode.net
>
> best regards
> Shiv
>


From maybird1776 at yahoo.com  Sat Jul 19 06:36:55 2008
From: maybird1776 at yahoo.com (ken mays)
Date: Sat, 19 Jul 2008 06:36:55 -0700 (PDT)
Subject: [belenix-dev] BeleniX 0.7.1 update release available
In-Reply-To: <319ee2b10807181931g1e14b96ev62166f9ceb677c8@mail.gmail.com>
Message-ID: <657550.6642.qm@web34201.mail.mud.yahoo.com>

About Belenix 0.7.1..

1. Was there a interim release as the official stable driver release from Nvidia is 173.14.09: http://www.nvidia.com/object/solaris_display_173.14.09.html

The latest driver is Nvidia 177.13 at: http://us.download.nvidia.com/solaris/177.13/NVIDIA-Solaris-x86-177.13.run

The reason I'd asked for a previous upgrade during the TEST phase was in reviewing the Nvidia GTX 280 card and reports of crashes with Flash animations through FireFox website browsing. The new drivers corrected a few problems we had in testing the Nvidia GTX 280 which is why it was suggested to the Belenix team to update the Nvidia drivers from 173.14.05.....

~ Ken Mays



--- On Fri, 7/18/08, S h i v <shivakumar.gn at gmail.com> wrote:

> From: S h i v <shivakumar.gn at gmail.com>
> Subject: [belenix-dev] BeleniX 0.7.1 update release available
> To: "Bangalore OpenSolaris User Group" <ug-bosug at opensolaris.org>, "Belenix Discuss" <belenix-discuss at opensolaris.org>, "BeleniX Development" <belenix-dev at opensolaris.org>, "Advocacy Mailing List" <advocacy-discuss at opensolaris.org>, distribution-discuss at opensolaris.org, opensolaris-announce at opensolaris.org
> Date: Friday, July 18, 2008, 10:31 PM
> Hello All,
> 
> The first update to the 0.7 release is now available. Give
> it a try
> and provide us the feedback.
> 
> Download location : http://www.belenix.org/download
> (torrent is not yet available. will be available soon)
> 
> Bugs/Feature Requests may be logged at
> http://sourceforge.net/tracker/?group_id=216118
> 
> This update brings in the latest development OpenSolaris
> build 93,
> updates to KDE 3.5.9, firefox 3.0.1, ability to create
> zones among
> other changes, bugfixes. This release includes the latest
> Caiman
> installer due to which upgrades from this release will
> become possible
> going forward.
> 
> Complete list of changes:
> 
>     * Based on ON Build 93 that has new drivers (like
> ATIgfx) among other stuff.
>     * Included the rum driver.
>     * Nvidia driver updated to 173.14.05.
>     * OSS updated to 4.0-1016.
>     * Updated Fully Open X bits.
>     * KDE updated to 3.5.9 and some upstream patches
> removed
>     * Firefox 3.0.1
>     * /sbin/sh is now ksh93.
>     * Sham's RAM based Boot integrated. In Grub screen
> select more
> options to see that boot option.
>       Install from RAM is possible and is *fast*. See
> Sham's Blog for
> details
> (http://blogs.sun.com/sham/entry/belenix_0_7_can_boot).
>     * Caiman Installer updated to current version. Grub
> boot entries
> for Windows partitions are now automatically added.
> Detecting Linux
> partitions is a work in progress.
>     * Added PowerTOP.
>     * Added XVM PV drivers to support booting inside domU.
>     * Qt 3.x is now built in both 32Bit and 64Bit versions.
>     * Gtk-Qt3 is fixed to build with proper Solaris build
> flags so the
> nagging warning about /proc/.../cmdline does not appear.
>     * Updated man pages to new release.
>     * OpenMotif updated to fix some brokenness.
>     * Ability to create zones via ZFS snapshots. See
> http://www.belenix.org/content/How-do-I-create-Zones-BeleniX
> ?.
>     * Added Single-User Console boot option when booting
> from harddisk.
>     * Many bugfixes. Fixed Usbdump in livecd mode.
>     * More packages available via get-pkgs utility
> including various
> multimedia stuff. New pkg.belenix.org repository now
> online. This is
> Not yet an IPS repository however.
>     * OpenSolaris G11N packages now available in the
> repository.
>     * Setting is applied during install to trim ZFS ARC to
> 50% of RAM
> if there is 1GB RAM or less.
> 
> Pending Issues
> 
>     * Sendmail cribs while booting off harddisk.
>     * BeleniX still does not boot on non-SSE CPUs (to be
> handled in 0.7.2)
> 
> 
> Website: www.belenix.org
> Discussion List : belenix-discuss at opensolaris.org
> IRC : #belenix @ freenode.net
> 
> best regards
> Shiv
> _______________________________________________
> belenix-dev mailing list
> belenix-dev at opensolaris.org
> http://mail.opensolaris.org/mailman/listinfo/belenix-dev


      


From moinakg at gmail.com  Sun Jul 20 06:46:07 2008
From: moinakg at gmail.com (Moinak Ghosh)
Date: Sun, 20 Jul 2008 19:16:07 +0530
Subject: [belenix-dev] BeleniX 0.7.1 update release available
In-Reply-To: <657550.6642.qm@web34201.mail.mud.yahoo.com>
References: <319ee2b10807181931g1e14b96ev62166f9ceb677c8@mail.gmail.com>
	<657550.6642.qm@web34201.mail.mud.yahoo.com>
Message-ID: <46fe20470807200646s2793380atc225201a10227683@mail.gmail.com>

On Sat, Jul 19, 2008 at 7:06 PM, ken mays <maybird1776 at yahoo.com> wrote:
> About Belenix 0.7.1..
>
> 1. Was there a interim release as the official stable driver release from Nvidia is 173.14.09: http://www.nvidia.com/object/solaris_display_173.14.09.html
>
> The latest driver is Nvidia 177.13 at: http://us.download.nvidia.com/solaris/177.13/NVIDIA-Solaris-x86-177.13.run
>
> The reason I'd asked for a previous upgrade during the TEST phase was in reviewing the Nvidia GTX 280 card and reports of crashes with Flash animations through FireFox website browsing. The new drivers corrected a few problems we had in testing the Nvidia GTX 280 which is why it was suggested to the Belenix team to update the Nvidia drivers from 173.14.05.....

   The driver 177.13 causes problems with some Nvidia cards. My GeForce 7300
   gives garbled display. I had a report from another person I can't remember of
   problems with this one.

Regards,
Moinak.

>
> ~ Ken Mays
>
>
>
> --- On Fri, 7/18/08, S h i v <shivakumar.gn at gmail.com> wrote:
>
>> From: S h i v <shivakumar.gn at gmail.com>
>> Subject: [belenix-dev] BeleniX 0.7.1 update release available
>> To: "Bangalore OpenSolaris User Group" <ug-bosug at opensolaris.org>, "Belenix Discuss" <belenix-discuss at opensolaris.org>, "BeleniX Development" <belenix-dev at opensolaris.org>, "Advocacy Mailing List" <advocacy-discuss at opensolaris.org>, distribution-discuss at opensolaris.org, opensolaris-announce at opensolaris.org
>> Date: Friday, July 18, 2008, 10:31 PM
>> Hello All,
>>
>> The first update to the 0.7 release is now available. Give
>> it a try
>> and provide us the feedback.
>>
>> Download location : http://www.belenix.org/download
>> (torrent is not yet available. will be available soon)
>>
>> Bugs/Feature Requests may be logged at
>> http://sourceforge.net/tracker/?group_id=216118
>>
>> This update brings in the latest development OpenSolaris
>> build 93,
>> updates to KDE 3.5.9, firefox 3.0.1, ability to create
>> zones among
>> other changes, bugfixes. This release includes the latest
>> Caiman
>> installer due to which upgrades from this release will
>> become possible
>> going forward.
>>
>> Complete list of changes:
>>
>>     * Based on ON Build 93 that has new drivers (like
>> ATIgfx) among other stuff.
>>     * Included the rum driver.
>>     * Nvidia driver updated to 173.14.05.
>>     * OSS updated to 4.0-1016.
>>     * Updated Fully Open X bits.
>>     * KDE updated to 3.5.9 and some upstream patches
>> removed
>>     * Firefox 3.0.1
>>     * /sbin/sh is now ksh93.
>>     * Sham's RAM based Boot integrated. In Grub screen
>> select more
>> options to see that boot option.
>>       Install from RAM is possible and is *fast*. See
>> Sham's Blog for
>> details
>> (http://blogs.sun.com/sham/entry/belenix_0_7_can_boot).
>>     * Caiman Installer updated to current version. Grub
>> boot entries
>> for Windows partitions are now automatically added.
>> Detecting Linux
>> partitions is a work in progress.
>>     * Added PowerTOP.
>>     * Added XVM PV drivers to support booting inside domU.
>>     * Qt 3.x is now built in both 32Bit and 64Bit versions.
>>     * Gtk-Qt3 is fixed to build with proper Solaris build
>> flags so the
>> nagging warning about /proc/.../cmdline does not appear.
>>     * Updated man pages to new release.
>>     * OpenMotif updated to fix some brokenness.
>>     * Ability to create zones via ZFS snapshots. See
>> http://www.belenix.org/content/How-do-I-create-Zones-BeleniX
>> ?.
>>     * Added Single-User Console boot option when booting
>> from harddisk.
>>     * Many bugfixes. Fixed Usbdump in livecd mode.
>>     * More packages available via get-pkgs utility
>> including various
>> multimedia stuff. New pkg.belenix.org repository now
>> online. This is
>> Not yet an IPS repository however.
>>     * OpenSolaris G11N packages now available in the
>> repository.
>>     * Setting is applied during install to trim ZFS ARC to
>> 50% of RAM
>> if there is 1GB RAM or less.
>>
>> Pending Issues
>>
>>     * Sendmail cribs while booting off harddisk.
>>     * BeleniX still does not boot on non-SSE CPUs (to be
>> handled in 0.7.2)
>>
>>
>> Website: www.belenix.org
>> Discussion List : belenix-discuss at opensolaris.org
>> IRC : #belenix @ freenode.net
>>
>> best regards
>> Shiv
>> _______________________________________________
>> belenix-dev mailing list
>> belenix-dev at opensolaris.org
>> http://mail.opensolaris.org/mailman/listinfo/belenix-dev
>
>
>
> _______________________________________________
> belenix-dev mailing list
> belenix-dev at opensolaris.org
> http://mail.opensolaris.org/mailman/listinfo/belenix-dev
>


From moinakg at gmail.com  Sun Jul 20 07:40:09 2008
From: moinakg at gmail.com (Moinak Ghosh)
Date: Sun, 20 Jul 2008 20:10:09 +0530
Subject: [belenix-dev] BeleniX 0.7.1 update release available
In-Reply-To: <46fe20470807200646s2793380atc225201a10227683@mail.gmail.com>
References: <319ee2b10807181931g1e14b96ev62166f9ceb677c8@mail.gmail.com>
	<657550.6642.qm@web34201.mail.mud.yahoo.com>
	<46fe20470807200646s2793380atc225201a10227683@mail.gmail.com>
Message-ID: <46fe20470807200740i752f642dy646115a12bbd12ca@mail.gmail.com>

On Sun, Jul 20, 2008 at 7:16 PM, Moinak Ghosh <moinakg at gmail.com> wrote:
> On Sat, Jul 19, 2008 at 7:06 PM, ken mays <maybird1776 at yahoo.com> wrote:
>> About Belenix 0.7.1..
>>
>> 1. Was there a interim release as the official stable driver release from Nvidia is 173.14.09: http://www.nvidia.com/object/solaris_display_173.14.09.html
>>
>> The latest driver is Nvidia 177.13 at: http://us.download.nvidia.com/solaris/177.13/NVIDIA-Solaris-x86-177.13.run
>>
>> The reason I'd asked for a previous upgrade during the TEST phase was in reviewing the Nvidia GTX 280 card and reports of crashes with Flash animations through FireFox website browsing. The new drivers corrected a few problems we had in testing the Nvidia GTX 280 which is why it was suggested to the Belenix team to update the Nvidia drivers from 173.14.05.....

   177.13 causes problems with 8800GT as well. Hangs with blank screen.
   Looks like not a good release to move to.

Regards,
Moinak.

>
>   The driver 177.13 causes problems with some Nvidia cards. My GeForce 7300
>   gives garbled display. I had a report from another person I can't remember of
>   problems with this one.
>
> Regards,
> Moinak.
>
>>
>> ~ Ken Mays
>>
>>
>>
>> --- On Fri, 7/18/08, S h i v <shivakumar.gn at gmail.com> wrote:
>>
>>> From: S h i v <shivakumar.gn at gmail.com>
>>> Subject: [belenix-dev] BeleniX 0.7.1 update release available
>>> To: "Bangalore OpenSolaris User Group" <ug-bosug at opensolaris.org>, "Belenix Discuss" <belenix-discuss at opensolaris.org>, "BeleniX Development" <belenix-dev at opensolaris.org>, "Advocacy Mailing List" <advocacy-discuss at opensolaris.org>, distribution-discuss at opensolaris.org, opensolaris-announce at opensolaris.org
>>> Date: Friday, July 18, 2008, 10:31 PM
>>> Hello All,
>>>
>>> The first update to the 0.7 release is now available. Give
>>> it a try
>>> and provide us the feedback.
>>>
>>> Download location : http://www.belenix.org/download
>>> (torrent is not yet available. will be available soon)
>>>
>>> Bugs/Feature Requests may be logged at
>>> http://sourceforge.net/tracker/?group_id=216118
>>>
>>> This update brings in the latest development OpenSolaris
>>> build 93,
>>> updates to KDE 3.5.9, firefox 3.0.1, ability to create
>>> zones among
>>> other changes, bugfixes. This release includes the latest
>>> Caiman
>>> installer due to which upgrades from this release will
>>> become possible
>>> going forward.
>>>
>>> Complete list of changes:
>>>
>>>     * Based on ON Build 93 that has new drivers (like
>>> ATIgfx) among other stuff.
>>>     * Included the rum driver.
>>>     * Nvidia driver updated to 173.14.05.
>>>     * OSS updated to 4.0-1016.
>>>     * Updated Fully Open X bits.
>>>     * KDE updated to 3.5.9 and some upstream patches
>>> removed
>>>     * Firefox 3.0.1
>>>     * /sbin/sh is now ksh93.
>>>     * Sham's RAM based Boot integrated. In Grub screen
>>> select more
>>> options to see that boot option.
>>>       Install from RAM is possible and is *fast*. See
>>> Sham's Blog for
>>> details
>>> (http://blogs.sun.com/sham/entry/belenix_0_7_can_boot).
>>>     * Caiman Installer updated to current version. Grub
>>> boot entries
>>> for Windows partitions are now automatically added.
>>> Detecting Linux
>>> partitions is a work in progress.
>>>     * Added PowerTOP.
>>>     * Added XVM PV drivers to support booting inside domU.
>>>     * Qt 3.x is now built in both 32Bit and 64Bit versions.
>>>     * Gtk-Qt3 is fixed to build with proper Solaris build
>>> flags so the
>>> nagging warning about /proc/.../cmdline does not appear.
>>>     * Updated man pages to new release.
>>>     * OpenMotif updated to fix some brokenness.
>>>     * Ability to create zones via ZFS snapshots. See
>>> http://www.belenix.org/content/How-do-I-create-Zones-BeleniX
>>> ?.
>>>     * Added Single-User Console boot option when booting
>>> from harddisk.
>>>     * Many bugfixes. Fixed Usbdump in livecd mode.
>>>     * More packages available via get-pkgs utility
>>> including various
>>> multimedia stuff. New pkg.belenix.org repository now
>>> online. This is
>>> Not yet an IPS repository however.
>>>     * OpenSolaris G11N packages now available in the
>>> repository.
>>>     * Setting is applied during install to trim ZFS ARC to
>>> 50% of RAM
>>> if there is 1GB RAM or less.
>>>
>>> Pending Issues
>>>
>>>     * Sendmail cribs while booting off harddisk.
>>>     * BeleniX still does not boot on non-SSE CPUs (to be
>>> handled in 0.7.2)
>>>
>>>
>>> Website: www.belenix.org
>>> Discussion List : belenix-discuss at opensolaris.org
>>> IRC : #belenix @ freenode.net
>>>
>>> best regards
>>> Shiv
>>> _______________________________________________
>>> belenix-dev mailing list
>>> belenix-dev at opensolaris.org
>>> http://mail.opensolaris.org/mailman/listinfo/belenix-dev
>>
>>
>>
>> _______________________________________________
>> belenix-dev mailing list
>> belenix-dev at opensolaris.org
>> http://mail.opensolaris.org/mailman/listinfo/belenix-dev
>>
>


From manishchaks at gmail.com  Mon Jul 28 03:51:43 2008
From: manishchaks at gmail.com (Manish Chakravarty)
Date: Mon, 28 Jul 2008 16:21:43 +0530
Subject: [belenix-dev] New binutils and Gcc4 packages are built
In-Reply-To: <46fe20470806300445s520f007dvf17afcd4eb296d78@mail.gmail.com>
References: <46fe20470806261203g2820d0ady103c60e831a3f442@mail.gmail.com>
	<D1C50A32-27CF-4C2D-8CC2-39F80FEAB286@gmail.com>
	<46fe20470806300445s520f007dvf17afcd4eb296d78@mail.gmail.com>
Message-ID: <b4dbee910807280351ia21442blc66522458f4ebb27@mail.gmail.com>

http://www.belenix.net/binfiles/extra_packages/
seems to be down.

Throws a
"Forbidden

You don't have permission to access /binfiles/extra_packages/ on this server.
"
error

On Mon, Jun 30, 2008 at 5:15 PM, Moinak Ghosh <moinakg at gmail.com> wrote:
> On Mon, Jun 30, 2008 at 5:09 PM, Manish Chakravarty
> <manishchaks at gmail.com> wrote:
>> This is good news.
>> I must then recompile stuff with gcc4 for me kde4 stuff.
>
>   That is the idea :)
>
> Regards,
> Moinak.
>
>>
>>
>> On 27-Jun-08, at 12:33 AM, Moinak Ghosh wrote:
>>
>>> Hiya Folks,
>>>
>>>   Thanks to Michael Kosarev there is a beefy BeleniX build machine
>>> available
>>> installed with 0.7 as of now. The plan for near future is to use that
>>> as a common
>>> build server for the core contributors and provision zones for
>>> developers to be
>>> able to experiment and share workspaces easily.  I will provide
>>> further updates
>>> as and when things get setup and a process is worked out.
>>>
>>> For testing I setup a new chroot environment on that box by zfs-
>>> cloning the root
>>> pool and pulled a copy of the BeleniX SVN repository. I then managed
>>> to get
>>> SFEbinutils and SFEgcc (Gcc4) built on 0.7. I had to install Studio
>>> 11 as well.
>>>
>>> These packages are available from:
>>> http://www.belenix.net/binfiles/extra_packages/
>>>
>>> SFEbinutils.tar.bz2, SFEbinutils-devel.tar.bz2, SFEgccruntime.tar.bz2,
>>> SFEgcc.tar.bz2
>>>
>>> You will have  to download and unzip and untar these files and
>>> pkgadd them. If
>>> you have untarred in the current directory then the following command
>>> will do the
>>> trick:
>>>
>>> pkgadd -d . SFEbinutils SFEbinutils-devel SFEgccruntime SFEgcc
>>>
>>> Gcc4 is impt in order to successfully build KDE4.
>>>
>>> Regards,
>>> Moinak.
>>> _______________________________________________
>>> belenix-dev mailing list
>>> belenix-dev at opensolaris.org
>>> http://mail.opensolaris.org/mailman/listinfo/belenix-dev
>>
>> _______________________________________________
>> belenix-dev mailing list
>> belenix-dev at opensolaris.org
>> http://mail.opensolaris.org/mailman/listinfo/belenix-dev
>>
> _______________________________________________
> belenix-dev mailing list
> belenix-dev at opensolaris.org
> http://mail.opensolaris.org/mailman/listinfo/belenix-dev
>



-- 
Manish Chakravarty
http://manish-chaks.livejournal.com/


From moinakg at belenix.org  Mon Jul 28 07:10:58 2008
From: moinakg at belenix.org (Moinak Ghosh)
Date: Mon, 28 Jul 2008 19:40:58 +0530
Subject: [belenix-dev] New binutils and Gcc4 packages are built
In-Reply-To: <b4dbee910807280351ia21442blc66522458f4ebb27@mail.gmail.com>
References: <46fe20470806261203g2820d0ady103c60e831a3f442@mail.gmail.com>
	<D1C50A32-27CF-4C2D-8CC2-39F80FEAB286@gmail.com>
	<46fe20470806300445s520f007dvf17afcd4eb296d78@mail.gmail.com>
	<b4dbee910807280351ia21442blc66522458f4ebb27@mail.gmail.com>
Message-ID: <46fe20470807280710n36fd09dq360690f2553cb004@mail.gmail.com>

On Mon, Jul 28, 2008 at 4:21 PM, Manish Chakravarty
<manishchaks at gmail.com> wrote:
> http://www.belenix.net/binfiles/extra_packages/
> seems to be down.
>
> Throws a
> "Forbidden
>
> You don't have permission to access /binfiles/extra_packages/ on this server.
> "
> error

   You are not supposed to access that directory directly. You need to
   use the get-pkgs utility.

Regards,
Moinak.

>
> On Mon, Jun 30, 2008 at 5:15 PM, Moinak Ghosh <moinakg at gmail.com> wrote:
>> On Mon, Jun 30, 2008 at 5:09 PM, Manish Chakravarty
>> <manishchaks at gmail.com> wrote:
>>> This is good news.
>>> I must then recompile stuff with gcc4 for me kde4 stuff.
>>
>>   That is the idea :)
>>
>> Regards,
>> Moinak.
>>
>>>
>>>
>>> On 27-Jun-08, at 12:33 AM, Moinak Ghosh wrote:
>>>
>>>> Hiya Folks,
>>>>
>>>>   Thanks to Michael Kosarev there is a beefy BeleniX build machine
>>>> available
>>>> installed with 0.7 as of now. The plan for near future is to use that
>>>> as a common
>>>> build server for the core contributors and provision zones for
>>>> developers to be
>>>> able to experiment and share workspaces easily.  I will provide
>>>> further updates
>>>> as and when things get setup and a process is worked out.
>>>>
>>>> For testing I setup a new chroot environment on that box by zfs-
>>>> cloning the root
>>>> pool and pulled a copy of the BeleniX SVN repository. I then managed
>>>> to get
>>>> SFEbinutils and SFEgcc (Gcc4) built on 0.7. I had to install Studio
>>>> 11 as well.
>>>>
>>>> These packages are available from:
>>>> http://www.belenix.net/binfiles/extra_packages/
>>>>
>>>> SFEbinutils.tar.bz2, SFEbinutils-devel.tar.bz2, SFEgccruntime.tar.bz2,
>>>> SFEgcc.tar.bz2
>>>>
>>>> You will have  to download and unzip and untar these files and
>>>> pkgadd them. If
>>>> you have untarred in the current directory then the following command
>>>> will do the
>>>> trick:
>>>>
>>>> pkgadd -d . SFEbinutils SFEbinutils-devel SFEgccruntime SFEgcc
>>>>
>>>> Gcc4 is impt in order to successfully build KDE4.
>>>>
>>>> Regards,
>>>> Moinak.
>>>> _______________________________________________
>>>> belenix-dev mailing list
>>>> belenix-dev at opensolaris.org
>>>> http://mail.opensolaris.org/mailman/listinfo/belenix-dev
>>>
>>> _______________________________________________
>>> belenix-dev mailing list
>>> belenix-dev at opensolaris.org
>>> http://mail.opensolaris.org/mailman/listinfo/belenix-dev
>>>
>> _______________________________________________
>> belenix-dev mailing list
>> belenix-dev at opensolaris.org
>> http://mail.opensolaris.org/mailman/listinfo/belenix-dev
>>
>
>
>
> --
> Manish Chakravarty
> http://manish-chaks.livejournal.com/
> _______________________________________________
> belenix-dev mailing list
> belenix-dev at opensolaris.org
> http://mail.opensolaris.org/mailman/listinfo/belenix-dev
>



-- 
================================
http://www.belenix.org/
http://moinakg.wordpress.com/


From manishchaks at gmail.com  Mon Jul 28 07:16:38 2008
From: manishchaks at gmail.com (Manish Chakravarty)
Date: Mon, 28 Jul 2008 19:46:38 +0530
Subject: [belenix-dev] New binutils and Gcc4 packages are built
In-Reply-To: <46fe20470807280710n36fd09dq360690f2553cb004@mail.gmail.com>
References: <46fe20470806261203g2820d0ady103c60e831a3f442@mail.gmail.com>
	<D1C50A32-27CF-4C2D-8CC2-39F80FEAB286@gmail.com>
	<46fe20470806300445s520f007dvf17afcd4eb296d78@mail.gmail.com>
	<b4dbee910807280351ia21442blc66522458f4ebb27@mail.gmail.com>
	<46fe20470807280710n36fd09dq360690f2553cb004@mail.gmail.com>
Message-ID: <b4dbee910807280716h567cda51had1307847f4a209c@mail.gmail.com>

On Mon, Jul 28, 2008 at 7:40 PM, Moinak Ghosh <moinakg at belenix.org> wrote:
> On Mon, Jul 28, 2008 at 4:21 PM, Manish Chakravarty
> <manishchaks at gmail.com> wrote:
>> http://www.belenix.net/binfiles/extra_packages/
>> seems to be down.
>>
>> Throws a
>> "Forbidden
>>
>> You don't have permission to access /binfiles/extra_packages/ on this server.
>> "
>> error
>
>   You are not supposed to access that directory directly. You need to
>   use the get-pkgs utility.
Moinak,

Will get-pkgs devel get me gcc4 ?


From moinakg at belenix.org  Mon Jul 28 07:26:20 2008
From: moinakg at belenix.org (Moinak Ghosh)
Date: Mon, 28 Jul 2008 19:56:20 +0530
Subject: [belenix-dev] New binutils and Gcc4 packages are built
In-Reply-To: <b4dbee910807280716h567cda51had1307847f4a209c@mail.gmail.com>
References: <46fe20470806261203g2820d0ady103c60e831a3f442@mail.gmail.com>
	<D1C50A32-27CF-4C2D-8CC2-39F80FEAB286@gmail.com>
	<46fe20470806300445s520f007dvf17afcd4eb296d78@mail.gmail.com>
	<b4dbee910807280351ia21442blc66522458f4ebb27@mail.gmail.com>
	<46fe20470807280710n36fd09dq360690f2553cb004@mail.gmail.com>
	<b4dbee910807280716h567cda51had1307847f4a209c@mail.gmail.com>
Message-ID: <46fe20470807280726p36ea3324g844fb465b8ee897f@mail.gmail.com>

On Mon, Jul 28, 2008 at 7:46 PM, Manish Chakravarty
<manishchaks at gmail.com> wrote:
> On Mon, Jul 28, 2008 at 7:40 PM, Moinak Ghosh <moinakg at belenix.org> wrote:
>> On Mon, Jul 28, 2008 at 4:21 PM, Manish Chakravarty
>> <manishchaks at gmail.com> wrote:
>>> http://www.belenix.net/binfiles/extra_packages/
>>> seems to be down.
>>>
>>> Throws a
>>> "Forbidden
>>>
>>> You don't have permission to access /binfiles/extra_packages/ on this server.
>>> "
>>> error
>>
>>   You are not supposed to access that directory directly. You need to
>>   use the get-pkgs utility.
> Moinak,
>
> Will get-pkgs devel get me gcc4 ?

   Just checked. Gcc4 is not present in the repo. You will have to build
   SFEgcc. However you will have to run  get-pkgs devel  to be able to
   compile anything in BeleniX.

Regards,
Moinak.

> _______________________________________________
> belenix-dev mailing list
> belenix-dev at opensolaris.org
> http://mail.opensolaris.org/mailman/listinfo/belenix-dev
>



-- 
================================
http://www.belenix.org/
http://moinakg.wordpress.com/


From manishchaks at gmail.com  Mon Jul 28 07:29:25 2008
From: manishchaks at gmail.com (Manish Chakravarty)
Date: Mon, 28 Jul 2008 19:59:25 +0530
Subject: [belenix-dev] New binutils and Gcc4 packages are built
In-Reply-To: <46fe20470807280726p36ea3324g844fb465b8ee897f@mail.gmail.com>
References: <46fe20470806261203g2820d0ady103c60e831a3f442@mail.gmail.com>
	<D1C50A32-27CF-4C2D-8CC2-39F80FEAB286@gmail.com>
	<46fe20470806300445s520f007dvf17afcd4eb296d78@mail.gmail.com>
	<b4dbee910807280351ia21442blc66522458f4ebb27@mail.gmail.com>
	<46fe20470807280710n36fd09dq360690f2553cb004@mail.gmail.com>
	<b4dbee910807280716h567cda51had1307847f4a209c@mail.gmail.com>
	<46fe20470807280726p36ea3324g844fb465b8ee897f@mail.gmail.com>
Message-ID: <b4dbee910807280729r730ce497v70553771df58f0ff@mail.gmail.com>

>> Will get-pkgs devel get me gcc4 ?
>
>   Just checked. Gcc4 is not present in the repo. You will have to build
>   SFEgcc. However you will have to run  get-pkgs devel  to be able to
>   compile anything in BeleniX.
I assume this would  mean
1) Checking out SFE via svn anonymously
2) running an pkgbuild --download build SFEgcc.spec

Am I correct?


From moinakg at belenix.org  Mon Jul 28 07:34:13 2008
From: moinakg at belenix.org (Moinak Ghosh)
Date: Mon, 28 Jul 2008 20:04:13 +0530
Subject: [belenix-dev] New binutils and Gcc4 packages are built
In-Reply-To: <b4dbee910807280729r730ce497v70553771df58f0ff@mail.gmail.com>
References: <46fe20470806261203g2820d0ady103c60e831a3f442@mail.gmail.com>
	<D1C50A32-27CF-4C2D-8CC2-39F80FEAB286@gmail.com>
	<46fe20470806300445s520f007dvf17afcd4eb296d78@mail.gmail.com>
	<b4dbee910807280351ia21442blc66522458f4ebb27@mail.gmail.com>
	<46fe20470807280710n36fd09dq360690f2553cb004@mail.gmail.com>
	<b4dbee910807280716h567cda51had1307847f4a209c@mail.gmail.com>
	<46fe20470807280726p36ea3324g844fb465b8ee897f@mail.gmail.com>
	<b4dbee910807280729r730ce497v70553771df58f0ff@mail.gmail.com>
Message-ID: <46fe20470807280734t2fcf08b6ke7dbfd8080e2ffe8@mail.gmail.com>

On Mon, Jul 28, 2008 at 7:59 PM, Manish Chakravarty
<manishchaks at gmail.com> wrote:
>>> Will get-pkgs devel get me gcc4 ?
>>
>>   Just checked. Gcc4 is not present in the repo. You will have to build
>>   SFEgcc. However you will have to run  get-pkgs devel  to be able to
>>   compile anything in BeleniX.
> I assume this would  mean
> 1) Checking out SFE via svn anonymously
> 2) running an pkgbuild --download build SFEgcc.spec
>
> Am I correct?

   Yes, but note Sriram's notes in an earlier email thread. There are a few
   things you need to do.

Regards,
Moinak.

> _______________________________________________
> belenix-dev mailing list
> belenix-dev at opensolaris.org
> http://mail.opensolaris.org/mailman/listinfo/belenix-dev
>



-- 
================================
http://www.belenix.org/
http://moinakg.wordpress.com/


From manishchaks at gmail.com  Mon Jul 28 07:46:24 2008
From: manishchaks at gmail.com (Manish Chakravarty)
Date: Mon, 28 Jul 2008 20:16:24 +0530
Subject: [belenix-dev] New binutils and Gcc4 packages are built
In-Reply-To: <46fe20470807280734t2fcf08b6ke7dbfd8080e2ffe8@mail.gmail.com>
References: <46fe20470806261203g2820d0ady103c60e831a3f442@mail.gmail.com>
	<D1C50A32-27CF-4C2D-8CC2-39F80FEAB286@gmail.com>
	<46fe20470806300445s520f007dvf17afcd4eb296d78@mail.gmail.com>
	<b4dbee910807280351ia21442blc66522458f4ebb27@mail.gmail.com>
	<46fe20470807280710n36fd09dq360690f2553cb004@mail.gmail.com>
	<b4dbee910807280716h567cda51had1307847f4a209c@mail.gmail.com>
	<46fe20470807280726p36ea3324g844fb465b8ee897f@mail.gmail.com>
	<b4dbee910807280729r730ce497v70553771df58f0ff@mail.gmail.com>
	<46fe20470807280734t2fcf08b6ke7dbfd8080e2ffe8@mail.gmail.com>
Message-ID: <b4dbee910807280746j68d2a90an7ad43f1b3e62bfa@mail.gmail.com>

>> I assume this would  mean
>> 1) Checking out SFE via svn anonymously
>> 2) running an pkgbuild --download build SFEgcc.spec
>>
>> Am I correct?
>
>   Yes, but note Sriram's notes in an earlier email thread. There are a few
>   things you need to do.
I am getting all confused.
I will probably wait for the next BOSUG meet to clarify my doubts

Thanks for the help!
Manish


From moinakg at belenix.org  Mon Jul 28 08:00:46 2008
From: moinakg at belenix.org (Moinak Ghosh)
Date: Mon, 28 Jul 2008 20:30:46 +0530
Subject: [belenix-dev] New binutils and Gcc4 packages are built
In-Reply-To: <b4dbee910807280746j68d2a90an7ad43f1b3e62bfa@mail.gmail.com>
References: <46fe20470806261203g2820d0ady103c60e831a3f442@mail.gmail.com>
	<D1C50A32-27CF-4C2D-8CC2-39F80FEAB286@gmail.com>
	<46fe20470806300445s520f007dvf17afcd4eb296d78@mail.gmail.com>
	<b4dbee910807280351ia21442blc66522458f4ebb27@mail.gmail.com>
	<46fe20470807280710n36fd09dq360690f2553cb004@mail.gmail.com>
	<b4dbee910807280716h567cda51had1307847f4a209c@mail.gmail.com>
	<46fe20470807280726p36ea3324g844fb465b8ee897f@mail.gmail.com>
	<b4dbee910807280729r730ce497v70553771df58f0ff@mail.gmail.com>
	<46fe20470807280734t2fcf08b6ke7dbfd8080e2ffe8@mail.gmail.com>
	<b4dbee910807280746j68d2a90an7ad43f1b3e62bfa@mail.gmail.com>
Message-ID: <46fe20470807280800vf49ceb1pd097c9229f288224@mail.gmail.com>

On Mon, Jul 28, 2008 at 8:16 PM, Manish Chakravarty
<manishchaks at gmail.com> wrote:
>>> I assume this would  mean
>>> 1) Checking out SFE via svn anonymously
>>> 2) running an pkgbuild --download build SFEgcc.spec
>>>
>>> Am I correct?
>>
>>   Yes, but note Sriram's notes in an earlier email thread. There are a few
>>   things you need to do.
> I am getting all confused.
> I will probably wait for the next BOSUG meet to clarify my doubts

   I was referring to this thread where you asked a similar question:
   http://mail.opensolaris.org/pipermail/ug-bosug/2008-July/006710.html

Regards,
Moinak.

>
> Thanks for the help!
> Manish
> _______________________________________________
> belenix-dev mailing list
> belenix-dev at opensolaris.org
> http://mail.opensolaris.org/mailman/listinfo/belenix-dev
>



-- 
================================
http://www.belenix.org/
http://moinakg.wordpress.com/