Re: GSoC: PKGNG GUI Proposal Available for Review

2013-05-04 Thread Justin Muniz
 I wish you the best of luck. 
 

Thank you very much, Fernando!
 I'm also happy to see you will use packagekit as a frontend. No need to 
 reinvent the wheel.
 

It is a great utility. I have learned a lot while studying it. 

As a side note, I have made much progress porting PackageKit-0.8.8. It fixes a 
lot of issues that exist in the most recent version (0.6.11) from the ports 
collection. I started yesterday, but I've already made progress. 

Justin Muniz
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org


GSoC proposal review

2013-05-03 Thread Rushil Paul
Hi,
Can somebody review my proposal here and see if it can be further improved?
http://www.google-melange.com/gsoc/proposal/review/google/gsoc2013/rushilpaul/12001

-- 
Regards,
Rushil
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org


GSoC: PKGNG GUI Proposal Available for Review

2013-05-03 Thread Justin Edward Muniz
Thank you everyone for helping me create a suitable project to propose. I
have submitted a draft of my proposal, though I am still in the process of
enhancing it. If anyone has the time, please check it out and I'll gladly
accept any feedback.

I am new to Google Summer of Code, and just discovered I could update my
proposal after submitting it. Initially I uploaded most of the proposal but
I am still finishing the last parts. Any advice could help me (or others)
develop future proposals, so I hope to hear from people even after the
deadline.

My proposal can be read at the following address:
https://www.google-melange.com/gsoc/proposal/review/google/gsoc2013/justin_muniz/1

I appreciate you taking the time to read this email. Happy coding everyone.

Justin Muniz
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org


Re: My GSOC proposal for review

2013-05-03 Thread Wojciech Puchar
point c. is what i would like the most and is really the most important 
for NON embedded system.

others for embedded ones.

d. won't really cut much
f. may not save much but slow things down

i wish you a success.

On Thu, 2 May 2013, Amit Rawat wrote:


Hi,

I am attaching my gsoc proposal with this mail for review. If any body want
any extra thing in it they can mail.

Thanks,
Amit Rawat


___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org


GSoC project proposal for review (Port GlusterFS to FreeBSD)

2013-05-03 Thread Mike Ma
Hi all,

I'm planning to port GlusterFS as a GSoC project this year.
And you can find the more information of the proposal here:
http://www.google-melange.com/gsoc/proposal/review/google/gsoc2013/mikemandarine/26018

Any suggestions or comments are more than welcome.
I'm looking forward to connect with anyone who's interested in this.

Thanks a lot for your time .
-- 
Cheers,
Mike
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org


Re: GSoC: PKGNG GUI Proposal Available for Review

2013-05-03 Thread Wojciech Puchar

good for today and future ladmins that cannot type a command.

Any USEFUL proposals that add some real functionality?

On Fri, 3 May 2013, Justin Edward Muniz wrote:


Thank you everyone for helping me create a suitable project to propose. I
have submitted a draft of my proposal, though I am still in the process of
enhancing it. If anyone has the time, please check it out and I'll gladly
accept any feedback.

I am new to Google Summer of Code, and just discovered I could update my
proposal after submitting it. Initially I uploaded most of the proposal but
I am still finishing the last parts. Any advice could help me (or others)
develop future proposals, so I hope to hear from people even after the
deadline.

My proposal can be read at the following address:
https://www.google-melange.com/gsoc/proposal/review/google/gsoc2013/justin_muniz/1

I appreciate you taking the time to read this email. Happy coding everyone.

Justin Muniz
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org



___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org


Re: GSoC: PKGNG GUI Proposal Available for Review

2013-05-03 Thread Teske, Devin

On May 3, 2013, at 1:33 AM, Wojciech Puchar wrote:

good for today and future ladmins that cannot type a command.

Any USEFUL proposals that add some real functionality?


WIth great respect, I disagree with the dismissal that a GUI itself cannot 
bring value that a command-line tool couldn't otherwise bring to the table.

For example, in a stateful modal dialog, I believe that part of the value-add 
is seeing realtime calculations being performed based on user input. For a 
concrete example, imagine as you are checking/unchecking boxes of what to 
install, if the GUI continually keeps up-to-date a display of selected 
dependencies (packages and leaves), then that is something that on the 
command-line tool is more difficult.

What is the value-add in that you may say? Exploring, of course! Imagine that 
you have a need to fill, you go into a particular package category, and are 
faced with 5 things that all fill the same basic need -- but perhaps all but 
one has a massive runtime dependency list, so you choose that one. In this 
example, the GUI is far superior to command-line tools.

I'm actually taking the same approach in the design of bsdconfig packages 
(visible here: http://twitpic.com/ci2rid ) in that the TUI based management 
will aim to give you all that extra value-added information that would 
otherwise take multiple command-line queries and extra effort to correlate.

I argue that the goal should not be to develop tools that are useful for (as 
you call them) ladmins … but develop tools that the developers themselves 
find useful.

I personally feel that I myself have failed as a developer if I ever develop a 
tool that I don't use myself (or at least find useful in replacing an old way 
of doing something that is much more difficult).
--
Devin

P.S. I'm sorry… but that callous remark sparked a fire in me. Had to set the 
record straight… we need to give this student a running chance -- don't dare 
say this won't be useful (I've read the project proposal… it's good and it has 
bapt's +1 iirc, so that makes it good as gold basically)



On Fri, 3 May 2013, Justin Edward Muniz wrote:

Thank you everyone for helping me create a suitable project to propose. I
have submitted a draft of my proposal, though I am still in the process of
enhancing it. If anyone has the time, please check it out and I'll gladly
accept any feedback.

I am new to Google Summer of Code, and just discovered I could update my
proposal after submitting it. Initially I uploaded most of the proposal but
I am still finishing the last parts. Any advice could help me (or others)
develop future proposals, so I hope to hear from people even after the
deadline.

My proposal can be read at the following address:
https://www.google-melange.com/gsoc/proposal/review/google/gsoc2013/justin_muniz/1

I appreciate you taking the time to read this email. Happy coding everyone.

Justin Muniz
___
freebsd-hackers@freebsd.orgmailto:freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to 
freebsd-hackers-unsubscr...@freebsd.orgmailto:freebsd-hackers-unsubscr...@freebsd.org


___
freebsd-hackers@freebsd.orgmailto:freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org

_
The information contained in this message is proprietary and/or confidential. 
If you are not the intended recipient, please: (i) delete the message and all 
copies; (ii) do not disclose, distribute or use the message in any manner; and 
(iii) notify the sender immediately. In addition, please be aware that any 
message addressed to our domain is subject to archiving and review by persons 
other than the intended recipient. Thank you.
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org


Re: GSoC: PKGNG GUI Proposal Available for Review

2013-05-03 Thread Kris Moore
On 05/03/2013 04:33, Wojciech Puchar wrote:
 good for today and future ladmins that cannot type a command.

 Any USEFUL proposals that add some real functionality?


Since this will enable more people to run FreeBSD that otherwise
wouldn't give it a second glance, I would say it is VERY useful. Not
everybody is born with innate knowledge of the command-line, sometimes
you have to give users tools which are intuitive before they can get
into the nitty gritty. (I.E. most people learn to drive a car and don't
have the time or desire to rebuild an engine)

 On Fri, 3 May 2013, Justin Edward Muniz wrote:

 Thank you everyone for helping me create a suitable project to
 propose. I
 have submitted a draft of my proposal, though I am still in the
 process of
 enhancing it. If anyone has the time, please check it out and I'll
 gladly
 accept any feedback.

 I am new to Google Summer of Code, and just discovered I could update my
 proposal after submitting it. Initially I uploaded most of the
 proposal but
 I am still finishing the last parts. Any advice could help me (or
 others)
 develop future proposals, so I hope to hear from people even after the
 deadline.

 My proposal can be read at the following address:
 https://www.google-melange.com/gsoc/proposal/review/google/gsoc2013/justin_muniz/1


 I appreciate you taking the time to read this email. Happy coding
 everyone.

 Justin Muniz
 ___
 freebsd-hackers@freebsd.org mailing list
 http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
 To unsubscribe, send any mail to
 freebsd-hackers-unsubscr...@freebsd.org




-- 
Kris Moore
PC-BSD Software
iXsystems

___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org


Re: GSoC: PKGNG GUI Proposal Available for Review

2013-05-03 Thread Matt Olander
On Fri, May 3, 2013 at 6:57 AM, Kris Moore k...@pcbsd.org wrote:
 On 05/03/2013 04:33, Wojciech Puchar wrote:
 good for today and future ladmins that cannot type a command.

 Any USEFUL proposals that add some real functionality?


 Since this will enable more people to run FreeBSD that otherwise
 wouldn't give it a second glance, I would say it is VERY useful. Not
 everybody is born with innate knowledge of the command-line, sometimes
 you have to give users tools which are intuitive before they can get
 into the nitty gritty. (I.E. most people learn to drive a car and don't
 have the time or desire to rebuild an engine)

 On Fri, 3 May 2013, Justin Edward Muniz wrote:

 Thank you everyone for helping me create a suitable project to
 propose. I
 have submitted a draft of my proposal, though I am still in the
 process of
 enhancing it. If anyone has the time, please check it out and I'll
 gladly
 accept any feedback.

 I am new to Google Summer of Code, and just discovered I could update my
 proposal after submitting it. Initially I uploaded most of the
 proposal but
 I am still finishing the last parts. Any advice could help me (or
 others)
 develop future proposals, so I hope to hear from people even after the
 deadline.

 My proposal can be read at the following address:
 https://www.google-melange.com/gsoc/proposal/review/google/gsoc2013/justin_muniz/1


 I appreciate you taking the time to read this email. Happy coding
 everyone.

Great proposal, Justin! I look forward to seeing your work ;)

Cheers,
-matt
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org


Re: GSoC: PKGNG GUI Proposal Available for Review

2013-05-03 Thread Justin Edward Muniz
On Fri, May 3, 2013 at 1:51 PM, Matt Olander m...@ixsystems.com wrote:


 Great proposal, Justin! I look forward to seeing your work ;)

 Cheers,
 -matt


Thank you very much for your support, Matt!

As soon as I start committing code, I will share a link to my repository on
this mailing-list.

Justin Muniz
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org


Re: GSoC: PKGNG GUI Proposal Available for Review

2013-05-03 Thread Fernando Apesteguía
El 03/05/2013 20:00, Justin Edward Muniz justin.mu...@maine.edu
escribió:

 On Fri, May 3, 2013 at 1:51 PM, Matt Olander m...@ixsystems.com wrote:

 
  Great proposal, Justin! I look forward to seeing your work ;)
 
  Cheers,
  -matt
 

 Thank you very much for your support, Matt!

 As soon as I start committing code, I will share a link to my repository
on
 this mailing-list.

I wish you the best of luck. I'm also happy to see you will use packagekit
as a frontend. No need to reinvent the wheel.


 Justin Muniz
 ___
 freebsd-hackers@freebsd.org mailing list
 http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
 To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org


Re: My GSOC proposal for review

2013-05-02 Thread Amit Rawat
Hi,


Here is some data I collected
https://www.dropbox.com/sh/3ff3x34iq4cm2lu/RDFmXuO2xj.

Thanks,
Amit Rawat


On Thu, May 2, 2013 at 12:58 PM, Amit Rawat aami...@gmail.com wrote:

 Hi,

 I am attaching my gsoc proposal with this mail for review. If any body
 want any extra thing in it they can mail.

 Thanks,
 Amit Rawat

___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org


[Looking for GSoC mentor] Port NiLFS to FreeBSD

2013-05-01 Thread Takuya ASADA
Hi,

My friend has interest to apply GSoC'13 with Port NiLFS to FreeBSD, witch
is on IdeasPage(not tagged as GSoC though).
https://wiki.freebsd.org/IdeasPage#Port_NiLFS_to_FreeBSD
There's no technical contact on the page, who can be a mentor of the
project?
Or, it's not goot project for GSoC?
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org


Re: Port GlusterFS as a GSoC project

2013-04-27 Thread Marco Steinbach

On Fri, 26 Apr 2013, Mike Ma wrote:


Hi there,

I'm now a student and trying to get involved in GSoC this year.
I found the proposal of about GlusterFS in the idea list wiki page very
interesting to me, possibly it will be porting from NetBSD implementation.
As I'm quite distant from idea owner, he also suggested me to try to find
some folks that are physically closer to me to help mentoring.
So I'm writing to ask if there's any folk in Europe is interested helping
me with the project in any way, it could be easier for communication and
discussion.

Thanks a lot.


[...]

I am very interested in this effort and could help with testing and the
occassional odd line of code.  I wouldn't be of much help for mentoring,
though.

MfG CoCo
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org


Port GlusterFS as a GSoC 2013 project

2013-04-26 Thread Mike Ma
Hi there,

I'm now a student and trying to get involved in GSoC this year.
I found the proposal of about GlusterFS in the idea list wiki page very
interesting to me, possibly it will be porting from NetBSD implementation.
As I'm quite distant from idea owner so there's a big time difference, he
also suggested me to try to find some folks that are physically closer to
me to help mentoring.
So I'm writing to ask if there's any folk in Europe is interested helping
me with the project in any way, it could be easier for communication and
discussion.

Thanks a lot.

Regards,
Mike
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org


Port GlusterFS as a GSoC project

2013-04-26 Thread Mike Ma
Hi there,

I'm now a student and trying to get involved in GSoC this year.
I found the proposal of about GlusterFS in the idea list wiki page very
interesting to me, possibly it will be porting from NetBSD implementation.
As I'm quite distant from idea owner, he also suggested me to try to find
some folks that are physically closer to me to help mentoring.
So I'm writing to ask if there's any folk in Europe is interested helping
me with the project in any way, it could be easier for communication and
discussion.

Thanks a lot.

Regards,
Mike
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org


Re: GSOC: Qt front-ends

2013-04-25 Thread Ollivier Robert
According to Freddie Cash on Wed, Apr 24, 2013 at 10:32:11AM -0700:
 Mostly off-topic for this thread, but improving the boot process to
 auto-detect hardware and auto-load kernel modules would be really nice.
 That way, GENERIC would be very small, with just the basic frameworks
 required (CAM, USB, PCI, TCP/IP, etc), and all the actual drivers would be
 loaded from modules.  That would remove almost all requirements to compile
 a custom kernel in the first place.  :)
 
 Granted, changing options in the kernel would require recompilation, but
 general use and hardware changes wouldn't.

That's what Solaris has been doing for years and yes, it does make a lot of 
sense.

-- 
Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- robe...@keltia.net
In memoriam to Ondine, our 2nd child: http://ondine.keltia.net/

___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org


Re: GSOC: Qt front-ends

2013-04-25 Thread Adrian Chadd
.. or we could just bite the bullet and split GENERIC into GENERIC
(which would have modules for everything) and GENERIC_NOMODULES.

Then just populate a default module list that goes into /boot/loader.conf.

If you're even more evil, you could populate a module list that goes
into /boot/kernel/module.conf.default, and then allow that to be
overridden.

Point is - a modular kernel works, right now. What we're missing is a
way to load them at boot time by the bootloader. Well, enough of them
to bring up the system so the rest can be autoloaded as needed.

_That_ whole mess would be a great GSoC project.



Adrian
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org


Re: GSOC: Qt front-ends

2013-04-25 Thread Lars Engels
On Thu, Apr 25, 2013 at 01:25:46AM -0700, Adrian Chadd wrote:
 .. or we could just bite the bullet and split GENERIC into GENERIC
 (which would have modules for everything) and GENERIC_NOMODULES.
 
 Then just populate a default module list that goes into /boot/loader.conf.

No, the list must be in kld_list= in rc.conf.
If you add all the modules to loader.conf you can drink a coffee while
the system boots.

 
 If you're even more evil, you could populate a module list that goes
 into /boot/kernel/module.conf.default, and then allow that to be
 overridden.
 
 Point is - a modular kernel works, right now. What we're missing is a
 way to load them at boot time by the bootloader. Well, enough of them
 to bring up the system so the rest can be autoloaded as needed.
 
 _That_ whole mess would be a great GSoC project.

+1


pgpuBzlZI_kIu.pgp
Description: PGP signature


Re: GSOC: Qt front-ends

2013-04-25 Thread Adrian Chadd
On 25 April 2013 01:38, Lars Engels l...@freebsd.org wrote:
 On Thu, Apr 25, 2013 at 01:25:46AM -0700, Adrian Chadd wrote:
 .. or we could just bite the bullet and split GENERIC into GENERIC
 (which would have modules for everything) and GENERIC_NOMODULES.

 Then just populate a default module list that goes into /boot/loader.conf.

 No, the list must be in kld_list= in rc.conf.
 If you add all the modules to loader.conf you can drink a coffee while
 the system boots.

.. so improve loader so that doesn't suck so hard.



Adrian
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org


Re: GSOC: Qt front-ends

2013-04-25 Thread Ollivier Robert
According to Adrian Chadd on Thu, Apr 25, 2013 at 01:25:46AM -0700:
 If you're even more evil, you could populate a module list that goes
 into /boot/kernel/module.conf.default, and then allow that to be
 overridden.
 
 Point is - a modular kernel works, right now. What we're missing is a
 way to load them at boot time by the bootloader. Well, enough of them
 to bring up the system so the rest can be autoloaded as needed.
 
 _That_ whole mess would be a great GSoC project.

I completely agree.

-- 
Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- robe...@keltia.net
In memoriam to Ondine, our 2nd child: http://ondine.keltia.net/

___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org


Re: GSOC: Qt front-ends

2013-04-25 Thread Lars Engels
On Thu, Apr 25, 2013 at 01:57:50AM -0700, Adrian Chadd wrote:
 On 25 April 2013 01:38, Lars Engels l...@freebsd.org wrote:
  On Thu, Apr 25, 2013 at 01:25:46AM -0700, Adrian Chadd wrote:
  .. or we could just bite the bullet and split GENERIC into GENERIC
  (which would have modules for everything) and GENERIC_NOMODULES.
 
  Then just populate a default module list that goes into /boot/loader.conf.
 
  No, the list must be in kld_list= in rc.conf.
  If you add all the modules to loader.conf you can drink a coffee while
  the system boots.
 
 .. so improve loader so that doesn't suck so hard.

Sure, but the rc.conf solution is the lower hanging fruit. :)


pgpIszgWmzYJo.pgp
Description: PGP signature


Re: GSOC: Qt front-ends

2013-04-25 Thread Adrian Chadd
On 25 April 2013 02:24, Lars Engels l...@freebsd.org wrote:

 Sure, but the rc.conf solution is the lower hanging fruit. :)

No it's not; think about it. You need to have a few modules loaded in
order to boot.

* usb
* maybe atkbd
* da/scsi
* ata / scsi block device drivers
* perhaps network
* perhaps vga/vesa
* perhaps acpi_* for your laptop device

.. those can't be in rc.conf .




Adrian
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org


Re: Fwd: GSOC: Qt front-ends

2013-04-24 Thread Chris Rees
On 24 Apr 2013 05:36, Justin Edward Muniz justin.mu...@maine.edu wrote:

 
  Justin I say stick to  FreeBSD-update . My reason is, as Pkgng becomes
  more popular , a front end for ports will be less useful as binary
packages
  become more popular . Kports is a monster program , you should set a
  reasonable goal ,and target dates; which may be hard with a cleanup
project
  .   Also a update notifier for kde that handles FreeBSD update would be
  very useful .
 
  My 2cents .
  ---
  Mark saad | mark.s...@longcount.org
 


 Thank you very much Mark,

  I was definitely hoping to get community feedback on this, and I
value
 you voicing your opinion. I agree that kports is a mammoth, and also that
a
 system updater GUI should have a way to notify the user of new updates.

  Any other perspectives are welcome, as well as support for a
 freebsd-update approach. I am working to refine my proposal, which as
 you've pointed out is very important. Eventually I would like to help in
 all three mentioned areas, but for now I must focus on one application.
 Does anyone think that a custom kernel configuration and management GUI
 utility would be desirable?

  I will shape my goals to meet the needs of the community.

Our kernel is actually very easy to configure, so I'm not convinced that
it's needed; you may be thinking of Linux's menuconfig, but I think that is
because of the complexity.

Chris
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org


Re: Fwd: GSOC: Qt front-ends

2013-04-24 Thread Fernando Apesteguía
El 24/04/2013 13:45, Chris Rees utis...@gmail.com escribió:

 On 24 Apr 2013 05:36, Justin Edward Muniz justin.mu...@maine.edu
wrote:
 
  
   Justin I say stick to  FreeBSD-update . My reason is, as Pkgng becomes
   more popular , a front end for ports will be less useful as binary
 packages
   become more popular . Kports is a monster program , you should set a
   reasonable goal ,and target dates; which may be hard with a cleanup
 project
   .   Also a update notifier for kde that handles FreeBSD update would
be
   very useful .
  
   My 2cents .
   ---
   Mark saad | mark.s...@longcount.org
  
 
 
  Thank you very much Mark,
 
   I was definitely hoping to get community feedback on this, and I
 value
  you voicing your opinion. I agree that kports is a mammoth, and also
that
 a
  system updater GUI should have a way to notify the user of new updates.
 
   Any other perspectives are welcome, as well as support for a
  freebsd-update approach. I am working to refine my proposal, which as
  you've pointed out is very important. Eventually I would like to help in
  all three mentioned areas, but for now I must focus on one application.
  Does anyone think that a custom kernel configuration and management GUI
  utility would be desirable?
 
   I will shape my goals to meet the needs of the community.

 Our kernel is actually very easy to configure, so I'm not convinced that
 it's needed; you may be thinking of Linux's menuconfig, but I think that
is
 because of the complexity.

I agree. Also, the kind of people who compile their kernels probably feel
more comfortable in console mode :)

The frontend for pkgng and freebsd-update might have a bigger user base.


 Chris
 ___
 freebsd-hackers@freebsd.org mailing list
 http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
 To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org


Re: Fwd: GSOC: Qt front-ends

2013-04-24 Thread Lars Engels

Am 24.04.2013 13:44, schrieb Chris Rees:
On 24 Apr 2013 05:36, Justin Edward Muniz justin.mu...@maine.edu 
wrote:




Justin I say stick to  FreeBSD-update . My reason is, as Pkgng 
becomes

more popular , a front end for ports will be less useful as binary

packages

become more popular . Kports is a monster program , you should set a
reasonable goal ,and target dates; which may be hard with a cleanup

project
.   Also a update notifier for kde that handles FreeBSD update would 
be

very useful .

My 2cents .
---
Mark saad | mark.s...@longcount.org




Thank you very much Mark,

 I was definitely hoping to get community feedback on this, and I

value
you voicing your opinion. I agree that kports is a mammoth, and also 
that

a
system updater GUI should have a way to notify the user of new 
updates.


 Any other perspectives are welcome, as well as support for a
freebsd-update approach. I am working to refine my proposal, which as
you've pointed out is very important. Eventually I would like to help 
in
all three mentioned areas, but for now I must focus on one 
application.
Does anyone think that a custom kernel configuration and management 
GUI

utility would be desirable?

 I will shape my goals to meet the needs of the community.


Our kernel is actually very easy to configure, so I'm not convinced 
that
it's needed; you may be thinking of Linux's menuconfig, but I think 
that is

because of the complexity.



It _is_ easy. But having a nice graphical tool which draws a pretty 
table of
GENERIC and NOTES together with useful information about the possible 
options

and devices would be a handy thing to have IMHO.
Let's make FreeBSD userfriendly :-)
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org


Re: Fwd: GSOC: Qt front-ends

2013-04-24 Thread Alexander Yerenkow
During some tests with cut down kernels one can easily make unbuildable
kernel, for example include option A, while omit hiddenly required B.
If there could be framework at least with deps tracking/checking, what
could be good for begin.
Both for configuring, and code clean up.
If this will come up in GUI - that would be awesome.

-- 
Regards,
Alexander Yerenkow
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org


Re: GSOC: Qt front-ends

2013-04-24 Thread Tony Li

On Apr 24, 2013, at 5:43 AM, Lars Engels lars.eng...@0x20.net wrote:

 It _is_ easy. But having a nice graphical tool which draws a pretty table of
 GENERIC and NOTES together with useful information about the possible options
 and devices would be a handy thing to have IMHO.
 Let's make FreeBSD userfriendly :-)


Side note: I agree that we would really, really like FreeBSD more user 
friendly.  

However, is kernel configuration where we really want to start?  Just how much 
of the user base reconfigures their kernels, anyway?  Wouldn't effort be better 
spent on making normal installation, maintenance and deployment clean and easy?

Regards,
Tony

___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org


Re: Fwd: GSOC: Qt front-ends

2013-04-24 Thread Freddie Cash
On Wed, Apr 24, 2013 at 5:43 AM, Lars Engels lars.eng...@0x20.net wrote:

 Am 24.04.2013 13:44, schrieb Chris Rees:

 Our kernel is actually very easy to configure, so I'm not convinced that
 it's needed; you may be thinking of Linux's menuconfig, but I think that
 is
 because of the complexity.



 It _is_ easy. But having a nice graphical tool which draws a pretty table
 of
 GENERIC and NOTES together with useful information about the possible
 options
 and devices would be a handy thing to have IMHO.
 Let's make FreeBSD userfriendly :-)


Especially if it handles dependencies!  For example, check USB Disk
Support, and have scbus, da, etc enabled automatically.  Or having the
LIBICONV stuff enabled if you add MSDOSFS support.  And so on.

That part of kernel configuration (keeping track of what devices require
which options and other devices) is currently the hardest part for newbies
(and even for some seasoned kernel compilers!).

Yes, the output of config KERNELNAME or buildkernel KERNCONF=KERNELNAME
will tell you about missing dependencies, but it breaks automated
compile/install processes.  Having the create kernel config file step
take care of dependencies would be nice.

-- 
Freddie Cash
fjwc...@gmail.com
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org


Re: Fwd: GSOC: Qt front-ends

2013-04-24 Thread Justin Edward Muniz

 Our kernel is actually very easy to configure, so I'm not convinced that
 it's needed; you may be thinking of Linux's menuconfig, but I think that is
 because of the complexity.

 Chris



While configuring the kernel may be trivial to someone who understands the
process and their systems needs, I am thinking of a software tool that goes
beyond the scope of the occasional generating of a kernel configuration
file.

Imagine that you have a number of systems and you want to run kernels that
are lighter weight than the generic kernel but each system has its own
individual needs. A GUI could help manage a large number of custom kernels,
and provide access to convenient access to features such as specifying a
kernel to load on the next boot only for testing. You could even configure
the custom kernel profiles to be built from separate source directories.

That is not to say of course that everyone else using x11 couldn't benefit
from it as well. The application could help avoid compatibility issues
during kernel installation by comparing the kernel's version to the version
of world. Some helpful aids would be visual categorization of options as
well as option descriptions, caveats, and hyperlinks to more in depth
information.

As for its place in Google Summer of Code, you could be right, it may not
be enough to dedicate such resources. I know however that I would use it,
maybe others would as well? Thank you for your advice once again Chris!
What do you think about the other utilities?

Justin Muniz
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org


Re: GSOC: Qt front-ends

2013-04-24 Thread Freddie Cash
On Wed, Apr 24, 2013 at 9:18 AM, Tony Li tony...@tony.li wrote:


 On Apr 24, 2013, at 5:43 AM, Lars Engels lars.eng...@0x20.net wrote:

  It _is_ easy. But having a nice graphical tool which draws a pretty
 table of
  GENERIC and NOTES together with useful information about the possible
 options
  and devices would be a handy thing to have IMHO.
  Let's make FreeBSD userfriendly :-)


 Side note: I agree that we would really, really like FreeBSD more user
 friendly.

 However, is kernel configuration where we really want to start?  Just how
 much of the user base reconfigures their kernels, anyway?  Wouldn't effort
 be better spent on making normal installation, maintenance and deployment
 clean and easy?


Mostly off-topic for this thread, but improving the boot process to
auto-detect hardware and auto-load kernel modules would be really nice.
That way, GENERIC would be very small, with just the basic frameworks
required (CAM, USB, PCI, TCP/IP, etc), and all the actual drivers would be
loaded from modules.  That would remove almost all requirements to compile
a custom kernel in the first place.  :)

Granted, changing options in the kernel would require recompilation, but
general use and hardware changes wouldn't.

Most likely not a GSoC project.  But it's still a nice dream.  :)
-- 
Freddie Cash
fjwc...@gmail.com
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org


Re: Fwd: GSOC: Qt front-ends

2013-04-24 Thread Chris Rees
On 24 April 2013 18:30, Justin Edward Muniz justin.mu...@maine.edu wrote:
 Our kernel is actually very easy to configure, so I'm not convinced that
 it's needed; you may be thinking of Linux's menuconfig, but I think that is
 because of the complexity.

 Chris



 While configuring the kernel may be trivial to someone who understands the
 process and their systems needs, I am thinking of a software tool that goes
 beyond the scope of the occasional generating of a kernel configuration
 file.

 Imagine that you have a number of systems and you want to run kernels that
 are lighter weight than the generic kernel but each system has its own
 individual needs. A GUI could help manage a large number of custom kernels,
 and provide access to convenient access to features such as specifying a
 kernel to load on the next boot only for testing. You could even configure
 the custom kernel profiles to be built from separate source directories.

 That is not to say of course that everyone else using x11 couldn't benefit
 from it as well. The application could help avoid compatibility issues
 during kernel installation by comparing the kernel's version to the version
 of world. Some helpful aids would be visual categorization of options as
 well as option descriptions, caveats, and hyperlinks to more in depth
 information.

 As for its place in Google Summer of Code, you could be right, it may not be
 enough to dedicate such resources. I know however that I would use it, maybe
 others would as well? Thank you for your advice once again Chris! What do
 you think about the other utilities?

I think the interface to pkgng and freebsd-update are still
interesting; at least more worthwhile than the kernel configuration
one.

I think the pkgng one has the edge, since packages are updated far
more often than base, and it's easier to track base.

Now you are at a stage where you should make your own decision; which
one looks the most interesting to you?  Once you decide on an area of
interest, you can just start hacking :)

Chris
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org


Fwd: GSOC: Qt front-ends

2013-04-24 Thread Justin Edward Muniz

  I agree. Also, the kind of people who compile their kernels probably
 feel more comfortable in console mode :)

 The frontend for pkgng and freebsd-update might have a bigger user base.



Hello Fernando, thank you for pointing me towards kports earlier. I
appreciate your help.

It is starting to seem that there is more interest in the GUI pkgng and
freebsd-update utilities at present. I do intend to pursue two out of three
of them on my time eventually; I'd like to use them all, and see others
benefit from them as well. GUI is my forté.

Justin Muniz
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org


Re: GSOC: Qt front-ends

2013-04-24 Thread Justin Edward Muniz

 Mostly off-topic for this thread, but improving the boot process to
 auto-detect hardware and auto-load kernel modules would be really nice.
 That way, GENERIC would be very small, with just the basic frameworks
 required (CAM, USB, PCI, TCP/IP, etc), and all the actual drivers would be
 loaded from modules.  That would remove almost all requirements to compile
 a custom kernel in the first place.  :)

 Granted, changing options in the kernel would require recompilation, but
 general use and hardware changes wouldn't.

 Most likely not a GSoC project.  But it's still a nice dream.  :)
 --
 Freddie Cash
 fjwc...@gmail.com



I really like that idea. If I remember correctly some folks over at PC-BSD
have started creating scripts to load sound and graphics drivers. Your idea
may be closer to reality than you think!

Justin Muniz
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org


Fwd: GSOC: Qt front-ends

2013-04-24 Thread Justin Edward Muniz

 I think the interface to pkgng and freebsd-update are still
 interesting; at least more worthwhile than the kernel configuration
 one.

 I think the pkgng one has the edge, since packages are updated far
 more often than base, and it's easier to track base.

 Now you are at a stage where you should make your own decision; which
 one looks the most interesting to you?  Once you decide on an area of
 interest, you can just start hacking :)

 Chris



That's good to hear.

I am sure that you are right, a pkgng GUI would probably see more use in
general. I am definitely close to making my decision, but this thread has
been so much help, I am glad for the insight.

The coding is what I look forward to the most :D

Justin Muniz
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org


Re: GSOC: Qt front-ends

2013-04-24 Thread Freddie Cash
On Wed, Apr 24, 2013 at 11:03 AM, Justin Edward Muniz 
justin.mu...@maine.edu wrote:

 
  I think the interface to pkgng and freebsd-update are still
  interesting; at least more worthwhile than the kernel configuration
  one.
 
  I think the pkgng one has the edge, since packages are updated far
  more often than base, and it's easier to track base.
 
  Now you are at a stage where you should make your own decision; which
  one looks the most interesting to you?  Once you decide on an area of
  interest, you can just start hacking :)
 
  Chris
 


 That's good to hear.

 I am sure that you are right, a pkgng GUI would probably see more use in
 general. I am definitely close to making my decision, but this thread has
 been so much help, I am glad for the insight.

 The coding is what I look forward to the most :D


You'll probably want to get in touch with the PC-BSD folks.  As they are
moving to pkgng for everything, they are updating their Python-based GUIs
to work with it.  Might be a possibility to work together, or to build off
what they have, or to get ideas/inspiration for a more general tool.

For example, (going from memory of my home PC-BSD install) the System
Update or System Manager tool uses pkgng behind the scenes, and provides a
tree-based view of PC-BSD-specific packages that can be installed via
simply ticking checkboxes and hitting Install button.

And, they have a ports-based GUI tool as well, although I have not used it
as yet so couldn't tell you what it supports.  I do my ports-based installs
via a terminal.  :)

-- 
Freddie Cash
fjwc...@gmail.com
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org


Re: Fwd: GSOC: Qt front-ends

2013-04-24 Thread Justin Edward Muniz

  It _is_ easy. But having a nice graphical tool which draws a pretty table
 of
 GENERIC and NOTES together with useful information about the possible
 options
 and devices would be a handy thing to have IMHO.
 Let's make FreeBSD userfriendly :-)



I agree completely, hopefully we can make that happen. I imagine that the
people using a kernel management utility would probably have configured it
by hand before, but could benefit from a GUI in some way. Quick access to
information is a good benefit to any GUI.

Justin Muniz
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org


Re: Fwd: GSOC: Qt front-ends

2013-04-24 Thread Justin Edward Muniz

 During some tests with cut down kernels one can easily make unbuildable
 kernel, for example include option A, while omit hiddenly required B.
 If there could be framework at least with deps tracking/checking, what
 could be good for begin.
 Both for configuring, and code clean up.
 If this will come up in GUI - that would be awesome.


 Especially if it handles dependencies!  For example, check USB Disk
 Support, and have scbus, da, etc enabled automatically.  Or having the
 LIBICONV stuff enabled if you add MSDOSFS support.  And so on.

Dependency checking and resolution is a really great idea. Thank you both
for voicing your thoughts!
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org


Re: GSOC: Qt front-ends

2013-04-24 Thread Justin Edward Muniz

 Side note: I agree that we would really, really like FreeBSD more user
 friendly.

 However, is kernel configuration where we really want to start?  Just how
 much of the user base reconfigures their kernels, anyway?  Wouldn't effort
 be better spent on making normal installation, maintenance and deployment
 clean and easy?

 Regards,
 Tony



What you say makes a lot of sense. I am feeling confident that the kernel
GUI should be a lower priority, and not used for the GSoC proposal.

Thank you for your time.

Justin Muniz
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org


Re: GSOC: Qt front-ends

2013-04-24 Thread Teske, Devin

On Apr 24, 2013, at 11:10 AM, Freddie Cash wrote:

On Wed, Apr 24, 2013 at 11:03 AM, Justin Edward Muniz 
justin.mu...@maine.edumailto:justin.mu...@maine.edu wrote:


I think the interface to pkgng and freebsd-update are still
interesting; at least more worthwhile than the kernel configuration
one.

I think the pkgng one has the edge, since packages are updated far
more often than base, and it's easier to track base.

Now you are at a stage where you should make your own decision; which
one looks the most interesting to you?  Once you decide on an area of
interest, you can just start hacking :)

Chris



That's good to hear.

I am sure that you are right, a pkgng GUI would probably see more use in
general. I am definitely close to making my decision, but this thread has
been so much help, I am glad for the insight.

The coding is what I look forward to the most :D


You'll probably want to get in touch with the PC-BSD folks.  As they are
moving to pkgng for everything, they are updating their Python-based GUIs
to work with it.  Might be a possibility to work together, or to build off
what they have, or to get ideas/inspiration for a more general tool.

For example, (going from memory of my home PC-BSD install) the System
Update or System Manager tool uses pkgng behind the scenes, and provides a
tree-based view of PC-BSD-specific packages that can be installed via
simply ticking checkboxes and hitting Install button.

And, they have a ports-based GUI tool as well, although I have not used it
as yet so couldn't tell you what it supports.  I do my ports-based installs
via a terminal.  :)


I've been planning a pkgng management tool in base for a while now (and am 
closing in on that goal).

The tool is bsdconfig

It's relevant to this discussion because it supports running both in GUI and in 
TUI.

This is accomplished by using dialog(1) for TUI and Xdialog(1) (from ports) for 
GUI. One code base, two modes.

The package management is being implemented as a bsdconfig(8) module in HEAD 
(see usr.sbin/bsdconfig).

Executing bsdconfig packages produces something inspired by sysinstall but 
greatly improved (faster, cleaner, more efficient, and provides more data).

Here's a screenshot:
http://twitpic.com/ci2rid

Sorry, no screenshot of the X11 side yet.

Executing bsdconfig -X packages or bsdconfig packages -X gives you the X11 
GUI.

Is it the flashiest GUI you've ever seen? Far from it. But when I've demo'd the 
code, people have been generally positive about the approach.

Just wanted to let you know what my plans are.

Feel free to go full-boar with a Qt-based front-end, just wanted to let you 
know what I'm cooking in HEAD.
--
Devin

_
The information contained in this message is proprietary and/or confidential. 
If you are not the intended recipient, please: (i) delete the message and all 
copies; (ii) do not disclose, distribute or use the message in any manner; and 
(iii) notify the sender immediately. In addition, please be aware that any 
message addressed to our domain is subject to archiving and review by persons 
other than the intended recipient. Thank you.
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org


Re: Fwd: GSOC: Qt front-ends

2013-04-24 Thread Baptiste Daroussin
On Wed, Apr 24, 2013 at 02:03:56PM -0400, Justin Edward Muniz wrote:
 
  I think the interface to pkgng and freebsd-update are still
  interesting; at least more worthwhile than the kernel configuration
  one.
 
  I think the pkgng one has the edge, since packages are updated far
  more often than base, and it's easier to track base.
 
  Now you are at a stage where you should make your own decision; which
  one looks the most interesting to you?  Once you decide on an area of
  interest, you can just start hacking :)
 
  Chris
 
 
 
 That's good to hear.
 
 I am sure that you are right, a pkgng GUI would probably see more use in
 general. I am definitely close to making my decision, but this thread has
 been so much help, I am glad for the insight.
 
 The coding is what I look forward to the most :D

imho a pkgng frontend should be done via packagekit, just write a pkgng backend
for packagekit and you will gain for FreeBSD a KDE frontend and a GTK frontend.

That said any frontend at convenience to contributor will be anyway good :)

regards,
Bapt


pgpNCIZpQMvf5.pgp
Description: PGP signature


Re: GSOC: Qt front-ends

2013-04-24 Thread Teske, Devin
On Apr 24, 2013, at 11:51 AM, Teske, Devin wrote:


On Apr 24, 2013, at 11:10 AM, Freddie Cash wrote:

On Wed, Apr 24, 2013 at 11:03 AM, Justin Edward Muniz 
justin.mu...@maine.edumailto:justin.mu...@maine.edu wrote:


I think the interface to pkgng and freebsd-update are still
interesting; at least more worthwhile than the kernel configuration
one.

I think the pkgng one has the edge, since packages are updated far
more often than base, and it's easier to track base.

Now you are at a stage where you should make your own decision; which
one looks the most interesting to you?  Once you decide on an area of
interest, you can just start hacking :)

Chris



That's good to hear.

I am sure that you are right, a pkgng GUI would probably see more use in
general. I am definitely close to making my decision, but this thread has
been so much help, I am glad for the insight.

The coding is what I look forward to the most :D


You'll probably want to get in touch with the PC-BSD folks.  As they are
moving to pkgng for everything, they are updating their Python-based GUIs
to work with it.  Might be a possibility to work together, or to build off
what they have, or to get ideas/inspiration for a more general tool.

For example, (going from memory of my home PC-BSD install) the System
Update or System Manager tool uses pkgng behind the scenes, and provides a
tree-based view of PC-BSD-specific packages that can be installed via
simply ticking checkboxes and hitting Install button.

And, they have a ports-based GUI tool as well, although I have not used it
as yet so couldn't tell you what it supports.  I do my ports-based installs
via a terminal.  :)


I've been planning a pkgng management tool in base for a while now (and am 
closing in on that goal).

The tool is bsdconfig

It's relevant to this discussion because it supports running both in GUI and in 
TUI.

This is accomplished by using dialog(1) for TUI and Xdialog(1) (from ports) for 
GUI. One code base, two modes.

The package management is being implemented as a bsdconfig(8) module in HEAD 
(see usr.sbin/bsdconfig).


Clarification:

The module is being *implemented* in HEAD, but is being *developed* on 
SF.nethttp://SF.net (URL Below):

http://druidbsd.sf.net/download/bsdconfig/

Right now, if you download the latest tarball from that directory 
(bsdconfig.YYMMDD-#.tgz) and replace usr.sbin/bsdconfig in your checked-out 
tree, you'll have ~1500 lines more than HEAD (at the time of this writing).

My plan is to (before the next BAFUG) commit the packages module in one swift 
action (hence why I'm developing it outside of the main tree).
--
Devin



Executing bsdconfig packages produces something inspired by sysinstall but 
greatly improved (faster, cleaner, more efficient, and provides more data).

Here's a screenshot:
http://twitpic.com/ci2rid

Sorry, no screenshot of the X11 side yet.

Executing bsdconfig -X packages or bsdconfig packages -X gives you the X11 
GUI.

Is it the flashiest GUI you've ever seen? Far from it. But when I've demo'd the 
code, people have been generally positive about the approach.

Just wanted to let you know what my plans are.

Feel free to go full-boar with a Qt-based front-end, just wanted to let you 
know what I'm cooking in HEAD.
--
Devin

_
The information contained in this message is proprietary and/or confidential. 
If you are not the intended recipient, please: (i) delete the message and all 
copies; (ii) do not disclose, distribute or use the message in any manner; and 
(iii) notify the sender immediately. In addition, please be aware that any 
message addressed to our domain is subject to archiving and review by persons 
other than the intended recipient. Thank you.
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org


Re: GSOC: Qt front-ends

2013-04-24 Thread Teske, Devin

On Apr 24, 2013, at 11:54 AM, Baptiste Daroussin wrote:

 On Wed, Apr 24, 2013 at 02:03:56PM -0400, Justin Edward Muniz wrote:
 
 I think the interface to pkgng and freebsd-update are still
 interesting; at least more worthwhile than the kernel configuration
 one.
 
 I think the pkgng one has the edge, since packages are updated far
 more often than base, and it's easier to track base.
 
 Now you are at a stage where you should make your own decision; which
 one looks the most interesting to you?  Once you decide on an area of
 interest, you can just start hacking :)
 
 Chris
 
 
 
 That's good to hear.
 
 I am sure that you are right, a pkgng GUI would probably see more use in
 general. I am definitely close to making my decision, but this thread has
 been so much help, I am glad for the insight.
 
 The coding is what I look forward to the most :D
 
 imho a pkgng frontend should be done via packagekit, just write a pkgng 
 backend
 for packagekit and you will gain for FreeBSD a KDE frontend and a GTK 
 frontend.
 
 That said any frontend at convenience to contributor will be anyway good :)
 

If you could pardon my ignorance… but what is packagekit again (for the benefit 
of others)?
-- 
Devin

_
The information contained in this message is proprietary and/or confidential. 
If you are not the intended recipient, please: (i) delete the message and all 
copies; (ii) do not disclose, distribute or use the message in any manner; and 
(iii) notify the sender immediately. In addition, please be aware that any 
message addressed to our domain is subject to archiving and review by persons 
other than the intended recipient. Thank you.
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org


Re: GSOC: Qt front-ends

2013-04-24 Thread Justin Edward Muniz
 You'll probably want to get in touch with the PC-BSD folks.  As they are
 moving to pkgng for everything, they are updating their Python-based GUIs
 to work with it.  Might be a possibility to work together, or to build
off what
 they have, or to get ideas/inspiration for a more general tool.

I will definitely contact them with any questions I have. I have just been
reading through the script called pc-updatemanager and it is a nice aid for
developing a pkgng back-end with.

 If you could pardon my ignorance… but what is packagekit again (for the
 benefit of others)?

I've just looked into this myself, it is an api and daemon that together
allow you to create a package manager while not worrying about the abstract
inner workings. The benefit is that one back-end (for pkgng in this case)
could be programmed, but it would work with both the gtk and qt packagekit
clients. On top of everything it offers some really cool advanced features.
(http://www.packagekit.org/)

 imho a pkgng frontend should be done via packagekit, just write a pkgng
 backend for packagekit and you will gain for FreeBSD a KDE frontend and
 a GTK frontend.

I really like this suggestion, I am looking in to this now and it is very,
very cool. I still need to learn more about it but I appreciate the
recommendation. I had never heard about packagekit before today.

 The tool is bsdconfig

I checked out your Web site, and I want to say congratulations on your
progress. It is quite an accomplishment. I think that a modern GUI could
however appeal to a different crowd. If FreeBSD comes with bsdconfig,
perhaps a qt GUI could be an alternative.

I like qt compared to xdialog because you can have a more persistent
interface with more options available to you at any one time. There is less
navigating through menus.

Thank you for letting me know about your work, I will take it in
consideration when trying to develop the strongest proposal I can.

Justin Muniz
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org


Re: GSOC: Qt front-ends

2013-04-24 Thread Fernando Apesteguía
El 24/04/2013 21:18, Teske, Devin devin.te...@fisglobal.com escribió:


 On Apr 24, 2013, at 11:54 AM, Baptiste Daroussin wrote:

  On Wed, Apr 24, 2013 at 02:03:56PM -0400, Justin Edward Muniz wrote:
 
  I think the interface to pkgng and freebsd-update are still
  interesting; at least more worthwhile than the kernel configuration
  one.
 
  I think the pkgng one has the edge, since packages are updated far
  more often than base, and it's easier to track base.
 
  Now you are at a stage where you should make your own decision; which
  one looks the most interesting to you?  Once you decide on an area of
  interest, you can just start hacking :)
 
  Chris
 
 
 
  That's good to hear.
 
  I am sure that you are right, a pkgng GUI would probably see more use
in
  general. I am definitely close to making my decision, but this thread
has
  been so much help, I am glad for the insight.
 
  The coding is what I look forward to the most :D
 
  imho a pkgng frontend should be done via packagekit, just write a pkgng
backend
  for packagekit and you will gain for FreeBSD a KDE frontend and a GTK
frontend.
 
  That said any frontend at convenience to contributor will be anyway
good :)
 

 If you could pardon my ignorance… but what is packagekit again (for the
benefit of others)?

It's an application to manage packages. It is developed in a way that it's
easy to add new backends keeping the same interface. See[1] for the general
information and this[2] page for the currently supported back ends.

[1] http://www.packagekit.org

[2] http://www.packagekit.org/pk-matrix.html

 --
 Devin

 _
 The information contained in this message is proprietary and/or
confidential. If you are not the intended recipient, please: (i) delete the
message and all copies; (ii) do not disclose, distribute or use the message
in any manner; and (iii) notify the sender immediately. In addition, please
be aware that any message addressed to our domain is subject to archiving
and review by persons other than the intended recipient. Thank you.
 ___
 freebsd-hackers@freebsd.org mailing list
 http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
 To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org


Re: GSOC: Qt front-ends

2013-04-24 Thread Teske, Devin

On Apr 24, 2013, at 2:33 PM, Fernando Apesteguía wrote:


El 24/04/2013 21:18, Teske, Devin 
devin.te...@fisglobal.commailto:devin.te...@fisglobal.com escribió:


 On Apr 24, 2013, at 11:54 AM, Baptiste Daroussin wrote:

  On Wed, Apr 24, 2013 at 02:03:56PM -0400, Justin Edward Muniz wrote:
 
  I think the interface to pkgng and freebsd-update are still
  interesting; at least more worthwhile than the kernel configuration
  one.
 
  I think the pkgng one has the edge, since packages are updated far
  more often than base, and it's easier to track base.
 
  Now you are at a stage where you should make your own decision; which
  one looks the most interesting to you?  Once you decide on an area of
  interest, you can just start hacking :)
 
  Chris
 
 
 
  That's good to hear.
 
  I am sure that you are right, a pkgng GUI would probably see more use in
  general. I am definitely close to making my decision, but this thread has
  been so much help, I am glad for the insight.
 
  The coding is what I look forward to the most :D
 
  imho a pkgng frontend should be done via packagekit, just write a pkgng 
  backend
  for packagekit and you will gain for FreeBSD a KDE frontend and a GTK 
  frontend.
 
  That said any frontend at convenience to contributor will be anyway good :)
 

 If you could pardon my ignorance… but what is packagekit again (for the 
 benefit of others)?

It's an application to manage packages. It is developed in a way that it's easy 
to add new backends keeping the same interface. See[1] for the general 
information and this[2] page for the currently supported back ends.

[1] 
http://www.packagekit.orghttps://urldefense.proofpoint.com/v1/url?u=http://www.packagekit.orgk=%2FbkpAUdJWZuiTILCq%2FFnQg%3D%3D%0Ar=LTzUWWrRnz2iN3PtHDubWRSAh9itVJ%2BMUcNBCQ4tyeo%3D%0Am=8MiGlyOMD3O%2FR2YU9sNxl1vMPdajxy%2FqKps59tnvAWw%3D%0As=29faa229ba8cb89cdb69d00087e23dde5669cdb61308c5b6d44156beb6d8766e

[2] 
http://www.packagekit.org/pk-matrix.htmlhttps://urldefense.proofpoint.com/v1/url?u=http://www.packagekit.org/pk-matrix.htmlk=%2FbkpAUdJWZuiTILCq%2FFnQg%3D%3D%0Ar=LTzUWWrRnz2iN3PtHDubWRSAh9itVJ%2BMUcNBCQ4tyeo%3D%0Am=8MiGlyOMD3O%2FR2YU9sNxl1vMPdajxy%2FqKps59tnvAWw%3D%0As=a802599114b383f22d717ee7fc4e7fc54e911e80958ed8f20c9a31228a3dbea5


Cool. Kinda reminds me of SANE for interfacing with scanners.
--
Devin

_
The information contained in this message is proprietary and/or confidential. 
If you are not the intended recipient, please: (i) delete the message and all 
copies; (ii) do not disclose, distribute or use the message in any manner; and 
(iii) notify the sender immediately. In addition, please be aware that any 
message addressed to our domain is subject to archiving and review by persons 
other than the intended recipient. Thank you.
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org


Re: GSOC: Qt front-ends

2013-04-23 Thread Mark Saad

On Apr 21, 2013, at 4:11 PM, Justin Edward Muniz justin.mu...@maine.edu wrote:

 Hello everyone once again,
 
 I decided to split this from my previous thread because the nature of
 my questions has changed. I benefited from the last thread, and I am
 grateful to those who responded to it.
 
 For me Google Summer of Code is a big opportunity, and my interest in
 contributing to the open source community is fairly limited to FreeBSD for
 many reasons. I know that my application may have a better chance of being
 approved if I have a mentor to help me with my endeavors.
 
 I currently have three project ideas in mind; however I need to
 understand which one would be the most beneficial, and try to find a
 mentor, before I create my proposal. Eventually I would like to develop
 each application and release them along with a meta-package that comprises
 of them all. For now, I need to focus on just one of the three.
 
 Originally I was interested in developing a Qt front-end for
 freebsd-update; indeed most of my research has been for that project.
 However, I am also interested in furthering kports -- which seems to be
 notoriously buggy, has broken package functionality, and is a mammoth of an
 application; the last development for kports was in 2009. I also am
 interested in developing a graphical application to customize the FreeBSD
 kernel.
 
 I have compiled a list of features that I would like to concentrate on
 for each project. Some of the features are far less important than others,
 so my actual application may omit some of them, or consider them optional.
 If it would be appropriate I will certainly share my lists, but since the
 lists are long I don't want to spam the mailing-list. I am new to this
 community after all!
 
 If anyone is interested in discussing these possibilities or just one
 of them in particular, I will greatly appreciate any advice, insight,
 concerns, criticism, or ideas. Ideally I am also looking to talk with
 anyone who might be interested in mentoring my Google Summer of Code
 project.
 
 Justin Muniz
 __


Justin I say stick to  FreeBSD-update . My reason is, as Pkgng becomes more 
popular , a front end for ports will be less useful as binary packages become 
more popular . Kports is a monster program , you should set a reasonable goal 
,and target dates; which may be hard with a cleanup project .   Also a update 
notifier for kde that handles FreeBSD update would be very useful . 

My 2cents .
---
Mark saad | mark.s...@longcount.org

___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org


Fwd: GSOC: Qt front-ends

2013-04-23 Thread Justin Edward Muniz

 Justin I say stick to  FreeBSD-update . My reason is, as Pkgng becomes
 more popular , a front end for ports will be less useful as binary packages
 become more popular . Kports is a monster program , you should set a
 reasonable goal ,and target dates; which may be hard with a cleanup project
 .   Also a update notifier for kde that handles FreeBSD update would be
 very useful .

 My 2cents .
 ---
 Mark saad | mark.s...@longcount.org



Thank you very much Mark,

 I was definitely hoping to get community feedback on this, and I value
you voicing your opinion. I agree that kports is a mammoth, and also that a
system updater GUI should have a way to notify the user of new updates.

 Any other perspectives are welcome, as well as support for a
freebsd-update approach. I am working to refine my proposal, which as
you've pointed out is very important. Eventually I would like to help in
all three mentioned areas, but for now I must focus on one application.
Does anyone think that a custom kernel configuration and management GUI
utility would be desirable?

 I will shape my goals to meet the needs of the community.

Justin Muniz
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org


GSOC: Qt front-ends

2013-04-21 Thread Justin Edward Muniz
Hello everyone once again,

 I decided to split this from my previous thread because the nature of
my questions has changed. I benefited from the last thread, and I am
grateful to those who responded to it.

 For me Google Summer of Code is a big opportunity, and my interest in
contributing to the open source community is fairly limited to FreeBSD for
many reasons. I know that my application may have a better chance of being
approved if I have a mentor to help me with my endeavors.

 I currently have three project ideas in mind; however I need to
understand which one would be the most beneficial, and try to find a
mentor, before I create my proposal. Eventually I would like to develop
each application and release them along with a meta-package that comprises
of them all. For now, I need to focus on just one of the three.

 Originally I was interested in developing a Qt front-end for
freebsd-update; indeed most of my research has been for that project.
However, I am also interested in furthering kports -- which seems to be
notoriously buggy, has broken package functionality, and is a mammoth of an
application; the last development for kports was in 2009. I also am
interested in developing a graphical application to customize the FreeBSD
kernel.

 I have compiled a list of features that I would like to concentrate on
for each project. Some of the features are far less important than others,
so my actual application may omit some of them, or consider them optional.
If it would be appropriate I will certainly share my lists, but since the
lists are long I don't want to spam the mailing-list. I am new to this
community after all!

 If anyone is interested in discussing these possibilities or just one
of them in particular, I will greatly appreciate any advice, insight,
concerns, criticism, or ideas. Ideally I am also looking to talk with
anyone who might be interested in mentoring my Google Summer of Code
project.

Justin Muniz
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org


GSOC: Qt front-end for freebsd-update

2013-04-14 Thread Justin Edward Muniz
 I am excited for this year's Google Summer of Code, and I have a
project in mind that I am working to propose.

 I am a CS major and have experience with Qt, C++ and shell scripting.
I have been developing on FreeBSD for several years, and I am looking to
tackle developing a new Qt front-end for the freebsd-update command.

 I am thinking a rather straight-forward user interface with more
advanced options available (such as selecting a specific server). I am
looking for constructive feedback, and also a developer interested in
mentoring me this Summer.

 Thanks everyone for your time, and for your hard work.

Justin Muniz
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org


Re: GSOC: Qt front-end for freebsd-update

2013-04-14 Thread Chris Rees
On 14 April 2013 07:11, Justin Edward Muniz justin.mu...@maine.edu wrote:
  I am excited for this year's Google Summer of Code, and I have a
 project in mind that I am working to propose.

  I am a CS major and have experience with Qt, C++ and shell scripting.
 I have been developing on FreeBSD for several years, and I am looking to
 tackle developing a new Qt front-end for the freebsd-update command.

  I am thinking a rather straight-forward user interface with more
 advanced options available (such as selecting a specific server). I am
 looking for constructive feedback, and also a developer interested in
 mentoring me this Summer.

  Thanks everyone for your time, and for your hard work.

Are you referring to the suggestion below?

https://wiki.freebsd.org/IdeasPage#KDE_front-ends_to_the_freebsd-update.288.29utility

Colin Percival (CCd) mentions he would be the technical contact for
this project, though that was five years ago-- perhaps he'd like to
comment.

Chris
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org


Re: GSOC: Qt front-end for freebsd-update

2013-04-14 Thread Jilles Tjoelker
On Sun, Apr 14, 2013 at 02:11:44AM -0400, Justin Edward Muniz wrote:
  I am excited for this year's Google Summer of Code, and I have a
 project in mind that I am working to propose.

  I am a CS major and have experience with Qt, C++ and shell scripting.
 I have been developing on FreeBSD for several years, and I am looking to
 tackle developing a new Qt front-end for the freebsd-update command.

  I am thinking a rather straight-forward user interface with more
 advanced options available (such as selecting a specific server). I am
 looking for constructive feedback, and also a developer interested in
 mentoring me this Summer.

If you want to work on freebsd-update, I think it will be more useful to
improve freebsd-update itself. Some issues are:

* It is not particularly robust in the face of errors (such as a full
  disk). From reading the documentation, you might get the impression
  that it is better than it actually is. The state for the rollback
  command is only set up after installation of the update so that
  command is not useful for backing out a partially installed update.

* The upgrade feature takes large amounts of time and network bandwidth.

* Less required user interaction would be nice. Think of upgrading many
  machines.

* freebsd-update and pkgng are two upgrade systems. Perhaps
  freebsd-upgrade should be scrapped altogether in favour of a
  pkgng-based solution.

If you want to write GUIs, perhaps a pkgng GUI is more interesting.

-- 
Jilles Tjoelker
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org


Re: GSOC: Qt front-end for freebsd-update

2013-04-14 Thread Wojciech Puchar

I am a CS major and have experience with Qt, C++ and shell scripting.
I have been developing on FreeBSD for several years, and I am looking to
tackle developing a new Qt front-end for the freebsd-update command.


spend your time for something more useful :)
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org


Re: GSOC: Qt front-end for freebsd-update

2013-04-14 Thread Justin Edward Muniz
Thank you for your advice! I have already sent an email to Colin, and I did
indeed take the idea from that page.

Justin Muniz

On Sun, Apr 14, 2013 at 7:04 AM, Chris Rees cr...@freebsd.org wrote:

 On 14 April 2013 07:11, Justin Edward Muniz justin.mu...@maine.edu
 wrote:
   I am excited for this year's Google Summer of Code, and I have a
  project in mind that I am working to propose.
 
   I am a CS major and have experience with Qt, C++ and shell
 scripting.
  I have been developing on FreeBSD for several years, and I am looking to
  tackle developing a new Qt front-end for the freebsd-update command.
 
   I am thinking a rather straight-forward user interface with more
  advanced options available (such as selecting a specific server). I am
  looking for constructive feedback, and also a developer interested in
  mentoring me this Summer.
 
   Thanks everyone for your time, and for your hard work.

 Are you referring to the suggestion below?


 https://wiki.freebsd.org/IdeasPage#KDE_front-ends_to_the_freebsd-update.288.29utility

 Colin Percival (CCd) mentions he would be the technical contact for
 this project, though that was five years ago-- perhaps he'd like to
 comment.

 Chris

___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org


Re: GSOC: Qt front-end for freebsd-update

2013-04-14 Thread Eitan Adler
On 14 April 2013 11:42, Justin Edward Muniz justin.mu...@maine.edu wrote:
 Thank you for your advice! I have already sent an email to Colin, and I did
 indeed take the idea from that page.

I think GUI front ends to freebsd-update, portsnap, or pkgng would all
be useful.

One thing I would look into though, is what PC-BSD offers. They may
already have similar things.


-- 
Eitan Adler
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org


Re: GSOC: Qt front-end for freebsd-update

2013-04-14 Thread Justin Edward Muniz

 I think GUI front ends to freebsd-update, portsnap, or pkgng would all be
 useful.

 One thing I would look into though, is what PC-BSD offers. They may
 already have similar things.

 Very interesting, I am checking out the source for PC-BSD's updater to
study it.
Portsnap and pkgng seem like interesting projects, would it be bizarre to
combine
functionality into one GUI? I need to do more research on pkgng, I am more
familiar
with the other commands.
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org


Re: GSOC: Qt front-end for freebsd-update

2013-04-14 Thread Kimmo Paasiala
On Sun, Apr 14, 2013 at 7:02 PM, Justin Edward Muniz
justin.mu...@maine.edu wrote:

 I think GUI front ends to freebsd-update, portsnap, or pkgng would all be
 useful.

 One thing I would look into though, is what PC-BSD offers. They may
 already have similar things.

 Very interesting, I am checking out the source for PC-BSD's updater to
 study it.
 Portsnap and pkgng seem like interesting projects, would it be bizarre to
 combine
 functionality into one GUI? I need to do more research on pkgng, I am more
 familiar
 with the other commands.

Please don't mix the two, they are related but their usages do not
really overlap.

portsnap(8) only deals with keeping the ports(7) tree and the
/usr/ports/INDEX file up to date.

PKGNG (like the old pkg_* tools) is mostly concerned with registering
built ports as packages or installing pre-built packages in the
system. Some functionality of it does use the ports tree but it does
not depend on it.


I have to also ask, what would a GUI offer that the command line tools
do not offer at the moment?


-Kimmo
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org


Re: GSOC: Qt front-end for freebsd-update

2013-04-14 Thread Eitan Adler
On 14 April 2013 12:15, Kimmo Paasiala kpaas...@gmail.com wrote:
 I have to also ask, what would a GUI offer that the command line tools
 do not offer at the moment?

A GUI.


-- 
Eitan Adler
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org


Re: GSOC: Qt front-end for freebsd-update

2013-04-14 Thread Kimmo Paasiala
On Sun, Apr 14, 2013 at 7:17 PM, Eitan Adler li...@eitanadler.com wrote:
 On 14 April 2013 12:15, Kimmo Paasiala kpaas...@gmail.com wrote:
 I have to also ask, what would a GUI offer that the command line tools
 do not offer at the moment?

 A GUI.



That's kind of given :D

But does FreeBSD lack a GUI for ports/packages management? I don't see
many requests for such things on the FreeBSD forums or on the mailing
lists.

-Kimmo
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org


Re: GSOC: Qt front-end for freebsd-update

2013-04-14 Thread Fernando Apesteguía
On Sun, Apr 14, 2013 at 6:22 PM, Kimmo Paasiala kpaas...@gmail.com wrote:

 On Sun, Apr 14, 2013 at 7:17 PM, Eitan Adler li...@eitanadler.com wrote:
  On 14 April 2013 12:15, Kimmo Paasiala kpaas...@gmail.com wrote:
  I have to also ask, what would a GUI offer that the command line tools
  do not offer at the moment?
 
  A GUI.
 
 

 That's kind of given :D

 But does FreeBSD lack a GUI for ports/packages management? I don't see
 many requests for such things on the FreeBSD forums or on the mailing
 lists.


It seems we already have something similar in the ports[1] collection.
There is also a newer version[2] using Qt4 but it seems more limited. It
might be worth a look at those first.

[1] ports-mgmt/kports
[2] ports-mgmt/kports-qt4



 -Kimmo
 ___
 freebsd-hackers@freebsd.org mailing list
 http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
 To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org

___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org


Re: GSOC: Qt front-end for freebsd-update

2013-04-14 Thread Justin Edward Muniz

 Please don't mix the two, they are related but their usages do not really
 overlap.

 portsnap(8) only deals with keeping the ports(7) tree and the
 /usr/ports/INDEX file up to date.

 PKGNG (like the old pkg_* tools) is mostly concerned with registering
 built ports as packages or installing pre-built packages in the
 system. Some functionality of it does use the ports tree but it does
 not depend on it.


 Yes, that does make sense; thank you for your input. A set of GUIs
seems like the
way to go, the reason why I considered combining them is for convenience. I
am still learning
about pkgng, but I do understand that it does not replace ports package
management
tools.

 A front-end could certainly add or combine functionality for
convenience, but
some admins run multiple operating systems and may have to reference notes
before updates.
And some newer users might prefer a GUI for some of these common commands.

Justin Muniz
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org


Re: GSOC: Qt front-end for freebsd-update

2013-04-14 Thread Justin Edward Muniz

 It seems we already have something similar in the ports[1] collection.
 There is also a newer version[2] using Qt4 but it seems more limited. It
 might be worth a look at those first.

 [1] ports-mgmt/kports
 [2] ports-mgmt/kports-qt4

  Yes, I just found those GUI programs myself. No sense reinventing the
wheel;
I will check out the functionality and make sure I don't overlap. I am most
interested
in a GUI front-end for updating binary updates to the base system. Thank
you for taking
your time to help! I will keep researching current GUI projects and make
sure this is
worthwhile.

 Everyone has given me much to work with, I appreciate it all.

Justin Muniz
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org


Re: GSOC: Qt front-end for freebsd-update

2013-04-14 Thread Kimmo Paasiala
On Sun, Apr 14, 2013 at 7:50 PM, Justin Edward Muniz
justin.mu...@maine.edu wrote:

 It seems we already have something similar in the ports[1] collection.
 There is also a newer version[2] using Qt4 but it seems more limited. It
 might be worth a look at those first.

 [1] ports-mgmt/kports
 [2] ports-mgmt/kports-qt4

  Yes, I just found those GUI programs myself. No sense reinventing the
 wheel;
 I will check out the functionality and make sure I don't overlap. I am most
 interested
 in a GUI front-end for updating binary updates to the base system. Thank
 you for taking
 your time to help! I will keep researching current GUI projects and make
 sure this is
 worthwhile.

  Everyone has given me much to work with, I appreciate it all.

 Justin Muniz


Could you also take a look at how security/pinentry-* ports offer
multiple ways to implement a GUI for a simple service, it offers a
curses, QT and GTK frontends to pinentry.

-Kimmo
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org


GSOC and Contribution to open source.

2013-04-14 Thread santosh hosamani
Hi ,

I am interested in participating for GSOC -2013 . I am interested in
following ideas

CPU online/offline project
BHyVe BIOS emulation to boot legacy systems I have two years of work exp in
linux kernel  device driver,C

now I have selected master thesis as  virtualization so I would be
interested in contributing to this field .
and I have no prior experience in open source so I would be really thankful
if anyone could guide me how to start contributing
to the world of open source.

Regards,
santosh.
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org


Re: GSOC 2013 project Kernel Size Reduction for Embedded System

2013-04-12 Thread Lars Engels

Am 10.04.2013 15:27, schrieb Matthew Jacob:

On 4/9/2013 11:53 PM, Daniel Braniss wrote:
this host can run x11 apps! so 'Huge' is a relative matter, my first 
PDP11/45 has 64K :-) danny

Bah. Real old farts ran munix on a 32k PDP 11/03- shell and apps in
the low 16k and the kernel in the upper. Or was it the other way
around? At Tektronix, a PDP 11/70 supported 64 users runing vi and
compiling simultaneously, although starting a link job meant going out
for coffee.

As a point of comparison with huge and speed: in 1987 my Sun 3/50
with a 15MHz 68020 and 4MB of memory could open the mailtool and I
could be reading email within a second.

My current desktop with 8GB of memory and running 8 cores @ 2.2GHz
and Thunderbird running almost entirely memory before being
un-iconified still takes a couple of seconds to be usable.



That's why I use mutt. :-)
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org


Re: GSOC 2013 project Kernel Size Reduction for Embedded System

2013-04-11 Thread Peter Jeremy
On 2013-Apr-09 11:05:56 -0700, Freddie Cash fjwc...@gmail.com wrote:
You have to look at the in-memory sizes, not the on-disk sizes.

Or, even better, look at the difference between installed physical RAM
and how much RAM is available to userland processes.

-- 
Peter Jeremy


pgpOHqKqYTU0M.pgp
Description: PGP signature


Re: GSOC 2013 project Kernel Size Reduction for Embedded System

2013-04-10 Thread Daniel Braniss
  happy that FreeBSD is among the selected organization.
 
  I am a third year student interested to work in the field of embedded
  system. I applied last year and the title of my project was  Kernel Size
 why only in embedded system. smaller programs are always good :)
 
 And yes FreeBSD kernel is huge. doesn't really matter with 1GB or more 
 RAM but yes - it is huge even relative to linux.
 
hum,
Copyright (c) 1992-2012 The FreeBSD Project.
Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
The Regents of the University of California. All rights reserved.
FreeBSD is a registered trademark of The FreeBSD Foundation.
FreeBSD 9.1-PRERELEASE #2: Wed Dec 12 13:15:53 IST 2012
danny@rnd:/home/obj/rnd/alix/i386.i386/r+d/stable/9/sys/ALIX i386
CPU: Geode(TM) Integrated Processor by AMD PCS (498.06-MHz 586-class CPU)
  Origin = AuthenticAMD  Id = 0x5a2  Family = 0x5  Model = 0xa  Stepping = 2
  Features=0x88a93dFPU,DE,PSE,TSC,MSR,CX8,SEP,PGE,CMOV,CLFLUSH,MMX
  AMD Features=0xc040MMX+,3DNow!+,3DNow!
real memory  = 268435456 (256 MB)
avail memory = 253120512 (241 MB)
pnpbios: Bad PnP BIOS data checksum
K6-family MTRR support enabled (2 registers)
cryptosoft0: software crypto on motherboard
pcib0 pcibus 0 on motherboard
pci0: PCI bus on pcib0
Geode LX: PC Engines ALIX.3 v0.99h tinyBIOS V1.4a (C)1997-2007

and top:
last pid: 31829;  load averages:  0.00,  0.00,  0.00   up 60+17:07:18  09:52:20
24 processes:  1 running, 23 sleeping
CPU:  0.0% user,  0.0% nice,  0.4% system,  0.0% interrupt, 99.6% idle
Mem: 17M Active, 56M Inact, 33M Wired, 34M Buf, 136M Free
Swap: 512M Total, 512M Free

  PID USERNAME  THR PRI NICE   SIZERES STATETIME   WCPU COMMAND
31829 danny   1  210  9784K  2004K RUN  0:00  1.86% top
 4288 danny   1  210 13160K  5128K select   0:01  1.37% xterm
21604 root1  200 21940K 12796K select  16:51  0.00% python
  687 root1  200 11160K  2660K select   5:55  0.00% ntpd
 3967 danny   1  200 13024K  4364K select   1:55  0.00% elockd
  537 root1  200  9592K  9612K select   1:54  0.00% amd-6.2a3
...

this host can run x11 apps!
so 'Huge' is a relative matter, my first PDP11/45 has 64K :-)

danny


___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org


Re: GSOC 2013 project Kernel Size Reduction for Embedded System

2013-04-10 Thread Matthew Jacob

On 4/9/2013 11:53 PM, Daniel Braniss wrote:
this host can run x11 apps! so 'Huge' is a relative matter, my first 
PDP11/45 has 64K :-) danny
Bah. Real old farts ran munix on a 32k PDP 11/03- shell and apps in the 
low 16k and the kernel in the upper. Or was it the other way around? At 
Tektronix, a PDP 11/70 supported 64 users runing vi and compiling 
simultaneously, although starting a link job meant going out for coffee.


As a point of comparison with huge and speed: in 1987 my Sun 3/50 with a 
15MHz 68020 and 4MB of memory could open the mailtool and I could be 
reading email within a second.


My current desktop with 8GB of memory and running 8 cores @ 2.2GHz and 
Thunderbird running almost entirely memory before being un-iconified 
still takes a couple of seconds to be usable.


Progress!
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org


Re: GSOC 2013 project Kernel Size Reduction for Embedded System

2013-04-10 Thread Jonathan Anderson
On Tuesday, 9 April 2013 at 22:18, Joshua Isom wrote:
 Would clang's LTO help for size? I know work's starting on the bsd
 elftools ld, but I doubt it has any LTO support yet. Running -Os on the
 kernel as a whole instead of object files could probably help a lot
 also. I might try to set it up and see a size comparision.


The last I heard, LTO on the kernel required something like 16 GB of RAM and 
produced a not-quite-working image.


Jon
-- 
Jonathan Anderson

Research Associate
Computer Laboratory
University of Cambridge

jonathan.ander...@cl.cam.ac.uk
+44 1223 763 747






___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org


Re: GSOC 2013 project Kernel Size Reduction for Embedded System

2013-04-10 Thread Joshua Isom

On 4/10/2013 9:43 AM, Jonathan Anderson wrote:


The last I heard, LTO on the kernel required something like 16 GB of RAM and 
produced a not-quite-working image.


Jon



I upgraded my system with 32Gb for a reason.
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org


Re: GSOC 2013 project Kernel Size Reduction for Embedded System

2013-04-10 Thread Adrian Chadd
On 10 April 2013 13:06, Joshua Isom jri...@gmail.com wrote:

 I upgraded my system with 32Gb for a reason.

Yes, yes you did.

TO force me to fix ath(4) and busdma. ;-)



Adrian
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org


Re: GSOC 2013 project Kernel Size Reduction for Embedded System

2013-04-09 Thread Alfred Perlstein

On 4/8/13 6:42 PM, Adrian Chadd wrote:

Well, it's relatively easy to experience what it's like.


No it's not.  We all have jobs that demand different things from us.  
Taking the time to guess at the problem, only to be told you're doing 
it wrong by someone actually in the position to build the list of 
requirements is not only a big honking waste of time but not fun nor 
interesting.


Either gather some acceptable feature/performance regressions together 
that small can live with or stop evangelizing.  Looking at .o files 
and guessing what to trim isn't going to work.


It sounds like what you want is some magic where you get all the 
features and your small image while not having to compromise on 
features/speed.  Cool, maybe someone will invent something amazing that 
gives you less from more, but until then it makes sense to actually be 
pragmatic and put together a list of things to trim based on sacrifice, 
not just because they are big.


-Alfred



Reboot your machine with 32mb. Try to do things like bring up network
interfaces. Snark when stupid stuff occurs, like you can't allocate
enough mbufs for the driver RX path _and_ run the ifconfig command to
completion to bring said interface up.

There's just a lot of code. You can start by cross-building one of the
MIPS kernels targeting a small system (eg AP121) and look at the
text/data sections of the resulting .o's. Group them together into
subsystems and take a look.

Now, as for what we can get away with - I'm still going through
another round of review. Yes, there's likely a bunch of syscalls or
syscall behaviours that we just don't need in the embedded world.
Things like all the POSIX compatible fine grained locking? Likely
don't need. But there's some reasonably big areas of bloat that we
could easy hit right now. I've chopped out some of the more silly
abuses in the past (posix acl code that only gets used by ZFS, always
being compiled in? Sigh.)

Eg:

textdata bss dec hex filename
   59772 160   49184  109116   1aa3c kern_umtx.o

That's a lot of both code and bss just for mutex handling, don't you
think? Do we really need 59KiB of code and 48KiB of BSS just for mutex
handling?

textdata bss dec hex filename
 184   0   12160   123443038 sc_machdep.o

.. 8 consoles? 12k of BSS? again, not much, but ..

adrian@lucy:~/work/freebsd/svn/src/sys/cam] cat
/tmp/AP121-nodebug.txt | egrep 'ata'
textdata bss dec hex filename
   11536   0   0   115362d10 ata_all.o
   176241504  16   191444ac8 ata_da.o
6388 448  1668521ac4 ata_pmp.o
   18960 304   0   192644b40 ata_xpt.o

.. 52 odd KiB tied up in CAM ATA transport, which we don't use unless
the ATA code is compiled in. It's just sitting there, waiting for an
ATA device to come along.

lucy# cat /tmp/AP121-nodebug.txt | grep vfs_ | grep -v devfs | sort -k3
4160  48   042081070 vfs_acl.o
4752  48   0480012c0 vfs_export.o
5464   0   054641558 vfs_extattr.o
8128 288   0841620e0 vfs_default.o
   11020 160   0   111802bac vfs_cluster.o
7916  96  1680281f5c vfs_lookup.o
   19908 144  16   200684e64 vfs_vnops.o
   34504 208  16   3472887a8 vfs_syscalls.o
3068  64  323164 c5c vfs_hash.o
   22700 208  32   22940599c vfs_mount.o
1760 144 1602064 810 vfs_init.o
   14520  16 160   146963968 vfs_mountroot.o
   139961568 176   157403d7c vfs_cache.o
   648521680 256   66788   104e4 vfs_subr.o
   521882000 304   54492d4dc vfs_bio.o

.. 260KiB just for VFS handling.

etc, etc.

I'd love to fix this, but I have to make a choice right now between
porting to more of the Atheros wifi/soc platforms, or tackling this
particular issue. I'd love for others to help out here. I'm sure that
reducing code size in general is going be beneficial on the lower end
platforms, even just in cache savings.

Thanks,


Adrian
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org



___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org


Re: GSOC 2013 project Kernel Size Reduction for Embedded System

2013-04-09 Thread Wojciech Puchar

happy that FreeBSD is among the selected organization.

I am a third year student interested to work in the field of embedded
system. I applied last year and the title of my project was  Kernel Size

why only in embedded system. smaller programs are always good :)

And yes FreeBSD kernel is huge. doesn't really matter with 1GB or more 
RAM but yes - it is huge even relative to linux.



___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org


Re: GSOC 2013 project Kernel Size Reduction for Embedded System

2013-04-09 Thread Alfred Perlstein

On 4/9/13 10:36 AM, Wojciech Puchar wrote:

happy that FreeBSD is among the selected organization.

I am a third year student interested to work in the field of embedded
system. I applied last year and the title of my project was  Kernel 
Size

why only in embedded system. smaller programs are always good :)

And yes FreeBSD kernel is huge. doesn't really matter with 1GB or more 
RAM but yes - it is huge even relative to linux.


Ah, any insight as to why?

-Alfred

___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org


Re: GSOC 2013 project Kernel Size Reduction for Embedded System

2013-04-09 Thread Wojciech Puchar
And yes FreeBSD kernel is huge. doesn't really matter with 1GB or more RAM 
but yes - it is huge even relative to linux.


Ah, any insight as to why?

my custom compiled kernel:

-r-xr-xr-x  1 root  wheel  8791402  6 kwi 22:08 /boot//kernel/kernel

only with features i need. linux is AFAIK like 3-4MB uncompressed.
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org


Re: GSOC 2013 project Kernel Size Reduction for Embedded System

2013-04-09 Thread Kimmo Paasiala
On Tue, Apr 9, 2013 at 8:53 PM, Wojciech Puchar
woj...@wojtek.tensor.gdynia.pl wrote:
 And yes FreeBSD kernel is huge. doesn't really matter with 1GB or more
 RAM but yes - it is huge even relative to linux.


 Ah, any insight as to why?

 my custom compiled kernel:

 -r-xr-xr-x  1 root  wheel  8791402  6 kwi 22:08 /boot//kernel/kernel

 only with features i need. linux is AFAIK like 3-4MB uncompressed.


Your comparison is far from accurate, include the memory taken by
loaded kernel modules on both systems and then you might get some
proper numbers.

-Kimmo
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org


Re: GSOC 2013 project Kernel Size Reduction for Embedded System

2013-04-09 Thread Freddie Cash
You have to look at the in-memory sizes, not the on-disk sizes.

Linux kernels are very barebones when it comes to what is compiled directly
into the kernel image on disk.  Everything else is loaded from modules at
boot time.  Especially if using distro-provided kernels.  They even use ram
disks / initrds to get around the can't boot without drivers for Y, but Y
is a module and not loaded at boot, adding extra memory pressure that's
not shown in the on-disk size of the kernel image file.

FreeBSD kernels tend to be the opposite, with everything compiled directly
into the
kernel image on-disk, and very little actually being loaded via modules.
At least GENERIC, anyway.

You would need to manually compile kernels with the same sets of drivers on
each system, in order to do a proper comparison of on-disk sizes.  Or, look
at in-memory stats for the two, once the systems are booted, all modules
are loaded, and the system is ready for use.

Just comparing ls output of default FreeBSD/Linux installs isn't useful in
any way.
-- 
Freddie Cash
fjwc...@gmail.com
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org


Re: GSOC 2013 project Kernel Size Reduction for Embedded System

2013-04-09 Thread Lev Serebryakov
Hello, Kimmo.
You wrote 9 апреля 2013 г., 21:59:37:

KP Your comparison is far from accurate, include the memory taken by
KP loaded kernel modules on both systems and then you might get some
KP proper numbers.
  Linux is known to _work_ on SOHO MIPS boxes, with 4MiB of flash and
 16MiB of RAM. You could say about ``loaded kernel modules,'' but when
 whole firmware, with all needed utils, like PPPoE client, Web-based
 UI, DHCP server, etc, is only 3.5MiB (Ok, it is compressed, but
 anyway it should work on 16MiB of RAM), it looks like functional
 Linux kernel could be about 1MiB without any modules.

-- 
// Black Lion AKA Lev Serebryakov l...@freebsd.org

___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org

Re: GSOC 2013 project Kernel Size Reduction for Embedded System

2013-04-09 Thread Edward Tomasz Napierała
In order to optimize - in this case for size - we need a way to measure
what should we focus on, and it looks like we don't have it yet.

Would it be possible to write a tool - e.g. by instrumenting LLVM - that
would make it possible to calculate, for every function in the call graph,
the amount of code in that function and everything it pulls in, i.e. all
the code paths that it might call.  When we have that, clustering the graph
should give us some idea what to focus on.

Or perhaps such a tool already exists?

-- 
If you cut off my head, what would I say?  Me and my head, or me and my body?

___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org


Re: GSOC 2013 project Kernel Size Reduction for Embedded System

2013-04-09 Thread Adrian Chadd
On 9 April 2013 11:47, Edward Tomasz Napierała tr...@freebsd.org wrote:
 In order to optimize - in this case for size - we need a way to measure
 what should we focus on, and it looks like we don't have it yet.

We have a good starting point. We can look at the code/data/bss from
each .o file that's included in the build.

You can build a bare-bones kernel and modules, and use that to see how
big things are.

You can group those by subsystem to get an idea of how big each
subsystem is. Whether or not it's loaded is (mostly) irrelevant - if
we compile out USB but then include it as a module, the underlying
size is almost the same anyway.

Thanks,



Adrian
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org

Re: GSOC 2013 project Kernel Size Reduction for Embedded System

2013-04-09 Thread Joshua Isom

On 4/9/2013 1:47 PM, Edward Tomasz Napierała wrote:

In order to optimize - in this case for size - we need a way to measure
what should we focus on, and it looks like we don't have it yet.

Would it be possible to write a tool - e.g. by instrumenting LLVM - that
would make it possible to calculate, for every function in the call graph,
the amount of code in that function and everything it pulls in, i.e. all
the code paths that it might call.  When we have that, clustering the graph
should give us some idea what to focus on.

Or perhaps such a tool already exists?



Would clang's LTO help for size?  I know work's starting on the bsd 
elftools ld, but I doubt it has any LTO support yet.  Running -Os on the 
kernel as a whole instead of object files could probably help a lot 
also.  I might try to set it up and see a size comparision.


Also, what about the userland?  Linux got popular for embedded partly 
for busybox and uclibc.  If Linux didn't exist, someone would have 
ported minix instead.

___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org

GSOC 2013 project Kernel Size Reduction for Embedded System

2013-04-08 Thread Amit Rawat
GSOC posted the list of selected organization for GSOC 2013 and I am highly
happy that FreeBSD is among the selected organization.

I am a third year student interested to work in the field of embedded
system. I applied last year and the title of my project was  Kernel Size
Reduction for Embedded System. The link to my last year proposal is

https://www.google-melange.com/gsoc/proposal/review/google/gsoc2012/amitrawat10/1#c8001;
But due to some flaws it doesn't get selected. I am looking to improve my
proposal for this year and apply again. I explain some portion of my
project pictorially on my blog


https://amit10rawat.wordpress.com/2013/02/26/kernel-size-reduction-for-embedded-system/


I am looking for suggestion and new ideas by which I can reduce the size of
kernel.

Amit Rawat(amraw)
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org


Re: GSOC 2013 project Kernel Size Reduction for Embedded System

2013-04-08 Thread Jilles Tjoelker
On Mon, Apr 08, 2013 at 08:28:04PM +, Amit Rawat wrote:
 GSOC posted the list of selected organization for GSOC 2013 and I am
 highly happy that FreeBSD is among the selected organization.

 I am a third year student interested to work in the field of embedded
 system. I applied last year and the title of my project was  Kernel
 Size Reduction for Embedded System. The link to my last year proposal
 is
 https://www.google-melange.com/gsoc/proposal/review/google/gsoc2012/amitrawat10/1#c8001

 But due to some flaws it doesn't get selected. I am looking to improve my
 proposal for this year and apply again. I explain some portion of my
 project pictorially on my blog

 https://amit10rawat.wordpress.com/2013/02/26/kernel-size-reduction-for-embedded-system/

 I am looking for suggestion and new ideas by which I can reduce the
 size of kernel.

It looks like the overlay idea could be implemented more simply by
taking advantage of the VM system: make part of the kernel code
pageable. Memory formerly occupied by rarely used kernel code can then
be used by userland applications. You will need some sort of backing
store where the kernel code can be read after booting; this is not
normally available.

However, almost no kernel code is safe in a situation where an
instruction fetch may fault. Reading or writing the secondary storage
can easily cause a deadlock. It causes the thread to sleep, which is not
allowed while holding a mutex. It would help if you could wire down
pieces which will need to be used in the near future from a place where
a fault is safe, but this may also be very slow even if the code is
already in memory.

Some other ideas for kernel size reduction:

* Find pieces of code that are required but seem big for what they do
  for you, and try to make them smaller. The proposal should list
  concrete parts.

* Find variables and functions that are required only during kernel
  initialization, place them in a special section and add this section
  to the free memory pool after kernel initialization.

-- 
Jilles Tjoelker
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org


Re: GSOC 2013 project Kernel Size Reduction for Embedded System

2013-04-08 Thread Adrian Chadd
Hi,

Your idea is interesting, but it doesn't fix the underlying problem -
there's just too much code. :(



Adrian
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org


Re: GSOC 2013 project Kernel Size Reduction for Embedded System

2013-04-08 Thread Erich Dollansky
Hi,

On Mon, 8 Apr 2013 20:28:04 +
Amit Rawat aami...@gmail.com wrote:

 GSOC posted the list of selected organization for GSOC 2013 and I am
 highly happy that FreeBSD is among the selected organization.
 
 I am a third year student interested to work in the field of embedded
 system. I applied last year and the title of my project was  Kernel
 Size Reduction for Embedded System. The link to my last year
 proposal is 
 https://www.google-melange.com/gsoc/proposal/review/google/gsoc2012/amitrawat10/1#c8001;
 But due to some flaws it doesn't get selected. I am looking to
 improve my proposal for this year and apply again. I explain some
 portion of my project pictorially on my blog
 
 
 https://amit10rawat.wordpress.com/2013/02/26/kernel-size-reduction-for-embedded-system/
 
 
 I am looking for suggestion and new ideas by which I can reduce the
 size of kernel.
 
did you look at historic operating systems and how they did it?

When I was a student, we simply loaded a module into memory and then
wrote it to an external memory when not needed. It was a very basic
swapping algorithm with fixed size. It did not differentiate between
code and data etc. All calls where done through a wrapper which was
always in memory. So, the module was loaded by the OS. The OS did not
notice that we removed the code from memory. Only the wrapper knew of
what we did.

We selected functions/modules which have to be in memory and which
could be on disk. There was a fixed number of memory segments we could
use for loading external modules. The trick was to select the modules
so that the system did not lock up.

We did not use  a tree structure what you might could.

The advantage of this was that the actual code was not
modified.

Yes, I know that this is hard core.

My problem would be that I do not know how much effort it would be to
implement this in a modern operating system.

Erich


 Amit Rawat(amraw)
 ___
 freebsd-hackers@freebsd.org mailing list
 http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
 To unsubscribe, send any mail to
 freebsd-hackers-unsubscr...@freebsd.org

___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org


Re: GSOC 2013 project Kernel Size Reduction for Embedded System

2013-04-08 Thread Alfred Perlstein

On 4/8/13 4:10 PM, Adrian Chadd wrote:

Hi,

Your idea is interesting, but it doesn't fix the underlying problem -
there's just too much code. :(

If you were to API'ify some of the more basic things such as fget, 
fdrop, filedesc stuff you could potentially swap out the systems for 
simpler (albeit less efficient) algorithms, the cost there may be slow 
smp performance, or maybe not allowing threads?


What we really need is someone to pin down those parts of code that 
smaller systems may not need and provide compromise when we remove them.


Other ideas are simple like for instance removing certain syscalls (for 
example, more recent ones such as openat) and features such as unix 
descriptor passing.


However, until a bunch of embedded folks come forward and state what 
they are really willing to sacrifice, then we won't really have anything 
to go on, and it will be guessing at what will work for a space that not 
all of us are familiar with.


So I'm hoping some people can make the tough call to give direction 
here, otherwise nothing good will come of it.


Has anyone actually done this?  Or maybe compared against another 
embedded OS?


-Alfred
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org


Re: GSOC 2013 project Kernel Size Reduction for Embedded System

2013-04-08 Thread Adrian Chadd
Well, it's relatively easy to experience what it's like.

Reboot your machine with 32mb. Try to do things like bring up network
interfaces. Snark when stupid stuff occurs, like you can't allocate
enough mbufs for the driver RX path _and_ run the ifconfig command to
completion to bring said interface up.

There's just a lot of code. You can start by cross-building one of the
MIPS kernels targeting a small system (eg AP121) and look at the
text/data sections of the resulting .o's. Group them together into
subsystems and take a look.

Now, as for what we can get away with - I'm still going through
another round of review. Yes, there's likely a bunch of syscalls or
syscall behaviours that we just don't need in the embedded world.
Things like all the POSIX compatible fine grained locking? Likely
don't need. But there's some reasonably big areas of bloat that we
could easy hit right now. I've chopped out some of the more silly
abuses in the past (posix acl code that only gets used by ZFS, always
being compiled in? Sigh.)

Eg:

   textdata bss dec hex filename
  59772 160   49184  109116   1aa3c kern_umtx.o

That's a lot of both code and bss just for mutex handling, don't you
think? Do we really need 59KiB of code and 48KiB of BSS just for mutex
handling?

   textdata bss dec hex filename
184   0   12160   123443038 sc_machdep.o

.. 8 consoles? 12k of BSS? again, not much, but ..

adrian@lucy:~/work/freebsd/svn/src/sys/cam] cat
/tmp/AP121-nodebug.txt | egrep 'ata'
   textdata bss dec hex filename
  11536   0   0   115362d10 ata_all.o
  176241504  16   191444ac8 ata_da.o
   6388 448  1668521ac4 ata_pmp.o
  18960 304   0   192644b40 ata_xpt.o

.. 52 odd KiB tied up in CAM ATA transport, which we don't use unless
the ATA code is compiled in. It's just sitting there, waiting for an
ATA device to come along.

lucy# cat /tmp/AP121-nodebug.txt | grep vfs_ | grep -v devfs | sort -k3
   4160  48   042081070 vfs_acl.o
   4752  48   0480012c0 vfs_export.o
   5464   0   054641558 vfs_extattr.o
   8128 288   0841620e0 vfs_default.o
  11020 160   0   111802bac vfs_cluster.o
   7916  96  1680281f5c vfs_lookup.o
  19908 144  16   200684e64 vfs_vnops.o
  34504 208  16   3472887a8 vfs_syscalls.o
   3068  64  323164 c5c vfs_hash.o
  22700 208  32   22940599c vfs_mount.o
   1760 144 1602064 810 vfs_init.o
  14520  16 160   146963968 vfs_mountroot.o
  139961568 176   157403d7c vfs_cache.o
  648521680 256   66788   104e4 vfs_subr.o
  521882000 304   54492d4dc vfs_bio.o

.. 260KiB just for VFS handling.

etc, etc.

I'd love to fix this, but I have to make a choice right now between
porting to more of the Atheros wifi/soc platforms, or tackling this
particular issue. I'd love for others to help out here. I'm sure that
reducing code size in general is going be beneficial on the lower end
platforms, even just in cache savings.

Thanks,


Adrian
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org


Re: GSOC 2013 project Kernel Size Reduction for Embedded System

2013-04-08 Thread Kevin Day

On Apr 8, 2013, at 7:34 PM, Alfred Perlstein bri...@mu.org wrote:
 However, until a bunch of embedded folks come forward and state what they are 
 really willing to sacrifice, then we won't really have anything to go on, and 
 it will be guessing at what will work for a space that not all of us are 
 familiar with.
 
 So I'm hoping some people can make the tough call to give direction here, 
 otherwise nothing good will come of it.
 
 Has anyone actually done this?  Or maybe compared against another embedded OS?


Ages ago we had to make things work in 16 or 32MB of total system memory on 
i386. 

For the most part, disabling every compiled-in option/driver we didn't need was 
90% of the effort. Which options/drivers is going to be totally application 
dependent, so that really can't be done for you.

As for the rest, there isn't any large low hanging fruit that can get culled 
from the kernel easily. The base kernel isn't modular enough to trim out 
individual syscalls or anything, and doing so wouldn't have made a huge dent.

There are a lot of ways FreeBSD could be more embedded friendly (being able 
turn on/off parts of userland depending on licenses is a huge one), but 
producing a trimmed kernel isn't something I'd rank very highly. If building a 
kernel with everything modularized as possible isn't small enough, FreeBSD 
probably isn't going to work for you for other reasons.


___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org


Re: GSOC 2013 project Kernel Size Reduction for Embedded System

2013-04-08 Thread Adrian Chadd
On 8 April 2013 19:28, Kevin Day toa...@dragondata.com wrote:

 Ages ago we had to make things work in 16 or 32MB of total system memory on 
 i386.

 For the most part, disabling every compiled-in option/driver we didn't need 
 was 90% of the effort. Which options/drivers is going to be totally 
 application dependent, so that really can't be done for you.

 As for the rest, there isn't any large low hanging fruit that can get culled 
 from the kernel easily. The base kernel isn't modular enough to trim out 
 individual syscalls or anything, and doing so wouldn't have made a huge dent.

 There are a lot of ways FreeBSD could be more embedded friendly (being able 
 turn on/off parts of userland depending on licenses is a huge one), but 
 producing a trimmed kernel isn't something I'd rank very highly. If building 
 a kernel with everything modularized as possible isn't small enough, FreeBSD 
 probably isn't going to work for you for other reasons.

The MIPS kernels I'm producing are pretty bare. There's not a lot of
options to disable at this point.. :(



Adrian
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org


Re: GSoC Project: Automated Kernel Crash Reporting System - Discussion

2012-05-25 Thread Dieter BSD
1) tar up files
2) encrypt tarball
3) copy encrypted tarball with rcp, ftp, uucp, ...
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org


[ GSOC ] Project: Parallelization in the ports collection

2012-05-22 Thread Alexander Pronin
Hello Community.

My name is Alexander Pronin. I am a GSOC student at The FreeBSD Project.
My project is Parallelization in the ports collection and pkgng utility
I have created wiki page where I described problems that I have to solve and 
approaches to solving this problems.
( 
http://wiki.freebsd.org/SummerOfCode2012/Parallelization_in_the_ports_collection
 )
But some problems still seem to be unsolved.

I would be grateful to discuss my project ideas. So any feedback is more that 
appreciated.

---
Best regards,
Alexander Pronin___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org


Re: GSoC Project: Automated Kernel Crash Reporting System - Discussion

2012-05-20 Thread Ilya Bakulin
On 19.05.12 22:02, Mel Flynn wrote:
 As I read the original intent is to post crashdumps at a specified
 remote location through rc(8) using an sh(1) script on the next
 reboot. tar seemed appropriate. I'm only mentioning extending
 libfetch(3), because it will be easy for fetch(1) to pick it up, it
 benefits more than just this project and once integrated into fetch(1)
 can be used in said script above. Other than openssh we don't really
 have a good tool in the base system to put local files elsewhere
 securely. Also, if the BUGS section of fetch(3) is out of date, I'm
 happy to be corrected :) 
I'm not going to make you happy...

From lib/libfetch/http.c:
/*
 * Store a file by HTTP
 */
FILE *
fetchPutHTTP(struct url *URL __unused, const char *flags __unused)
{
warnx(fetchPutHTTP(): not implemented);
return (NULL);
}

Adding HTTP PUT support to libfetch would be cool, but I doubt that it's
worth wasting GSoC time for that. Most people use curl for that just
because Google tells them to. On the other hand, SSH is available in
FreeBSD system in 99% of use cases, and it would be quite easy to setup
secure file transfer.

The final decision should however be made by TS.

-- 
Regards,
Ilya Bakulin
http://kibab.com
xmpp://kibab...@jabber.ru




signature.asc
Description: OpenPGP digital signature


Re: GSoC Project: Automated Kernel Crash Reporting System - Discussion

2012-05-19 Thread Mel Flynn
On 19-5-2012 5:54, Tim Kientzle wrote:
 
 On May 18, 2012, at 7:51 AM, Mel Flynn wrote:
 
 On 17-5-2012 14:53, Mateusz Guzik wrote:
 On Wed, May 16, 2012 at 11:37:44PM +0300, tza...@it.teithe.gr wrote:

 Nice. What about curl over the HTTPS protocol?


 curl would be ok, except it's not in the base system.

 For this reason, it's probably best to use tar(1) to package up multiple
 files and implement http put support in libfetch(3). You may also need
 to implement 305 Use Proxy support.
 
 Depends on where the files are coming from.  If you
 have files on disk, then tar(1) might be a good choice.
 If you're going to have to construct the files, then you
 can maybe avoid writing them to disk by using libarchive(3)
 directly instead of going through the tar command-line
 interface.

As I read the original intent is to post crashdumps at a specified
remote location through rc(8) using an sh(1) script on the next reboot.
tar seemed appropriate.

I'm only mentioning extending libfetch(3), because it will be easy for
fetch(1) to pick it up, it benefits more than just this project and once
integrated into fetch(1) can be used in said script above.

Other than openssh we don't really have a good tool in the base system
to put local files elsewhere securely. Also, if the BUGS section of
fetch(3) is out of date, I'm happy to be corrected :)
-- 
Mel
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org


Re: GSoC Project: EFI on amd64/i386

2012-05-18 Thread Andrey V. Elsukov
On 17.05.2012 17:28, Eric McCorkle wrote:
 As i see we already have sys/boot/efi/libefi/efipart.c that uses
 EFI BLOCK_IO_PROTOCOL to make part devsw. EFI BLOCK_IO_PROTOCOL
 provides access to each disk and partition. AFAIK it supports only
 GPT and MBR+EBR, so there might be some problems with ZFS support,
 because we can use ZFS atop of BSD partition.
 
 
 I'd need to take a look, but if the efi loaders are not directly
 calling the EFI_BLOCK_IO_PROTOCOL functions, then it should be easy to
 implement a layer that understands BSDlabels.  IA64 might have a solution.
 
 Then again, is a BSDlabel really necessary on a GPT disk?

It might be necessary for the ZFS case. ZFS can use several devices/partitions
and they should be accessible while booting.

-- 
WBR, Andrey V. Elsukov
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org


Re: GSoC Project: Automated Kernel Crash Reporting System - Discussion

2012-05-18 Thread Mel Flynn
On 17-5-2012 14:53, Mateusz Guzik wrote:
 On Wed, May 16, 2012 at 11:37:44PM +0300, tza...@it.teithe.gr wrote:

 Nice. What about curl over the HTTPS protocol?

 
 curl would be ok, except it's not in the base system.

For this reason, it's probably best to use tar(1) to package up multiple
files and implement http put support in libfetch(3). You may also need
to implement 305 Use Proxy support.
-- 
Mel
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org


Re: GSoC Project: Automated Kernel Crash Reporting System - Discussion

2012-05-18 Thread Aaron Zauner
hi,

first of; grats on getting the project. very interesting.

 * Can you recommend a secure way of sending a report from a FreeBSD system
 to the Central Collector machine?
i don't know if the use of a gnu tool would conflict with FreeBSD
politics but you could use tar(1) or an equivalent and GPG.
this would also be protocol independent. e.g.: you can use a public
key for the central server to encrypt traffic destined for the server.

 * Do you propose a different Web Server than the Apache HTTP Server? For
 example, on my initial planning I had included MySQL as the selected DBMS
 and after some discussions I changed to PostgreSQL.

lighttpd works very well and fast with PHP in my experience.
varnish-cache is also pretty cool for heavy loads or distributed
setups. postgres is a good choice.
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org


Re: GSoC Project: Automated Kernel Crash Reporting System - Discussion

2012-05-18 Thread Tim Kientzle

On May 18, 2012, at 7:51 AM, Mel Flynn wrote:

 On 17-5-2012 14:53, Mateusz Guzik wrote:
 On Wed, May 16, 2012 at 11:37:44PM +0300, tza...@it.teithe.gr wrote:
 
 Nice. What about curl over the HTTPS protocol?
 
 
 curl would be ok, except it's not in the base system.
 
 For this reason, it's probably best to use tar(1) to package up multiple
 files and implement http put support in libfetch(3). You may also need
 to implement 305 Use Proxy support.

Depends on where the files are coming from.  If you
have files on disk, then tar(1) might be a good choice.
If you're going to have to construct the files, then you
can maybe avoid writing them to disk by using libarchive(3)
directly instead of going through the tar command-line
interface.

Tim

___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org


Re: GSoC Project: Automated Kernel Crash Reporting System - Discussion

2012-05-17 Thread Jeremie Le Hen
On Wed, May 16, 2012 at 02:45:24PM +0300, tza...@it.teithe.gr wrote:
  In this case Apache is a good choice. I would however recommend using
  www/nginx and PHP in FastCGI mode (FPM option in lang/php5 port). This
  is a preffered setup for almost all Russian highloaded websites.
  At the beginning using Apache is a reasonable choice.
 
 I have never used nginx before. I have considered also the lighttpd.  
 Both with BSD licenses (nginx with a 2-clause BSD like license) and  
 FastCGI support. As I read from Wikipedia, PHP performance has  
 received special attention in lighttpd. I will test both Web servers  
 and then I will make up my mind.

I think the HTTP server is not a big deal unless there is a really
useful feature in one that the other doesn't provide.  Most of the work
will be done by the PHP backend anyway.

From an architectural point of view, best practices nowadays are leaning
toward external PHP processes with FastCGI, as described by Ilya.  There
are alternatives to FPM, such as sysutils/py-supervisor.

I don't know who will be administrating this server in the end, but I
think it would be good to ask the FreeBSD webmaster team opinion though.

-- 
Jeremie Le Hen

Men are born free and equal.  Later on, they're on their own.
Jean Yanne
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org


Re: GSoC Project: Automated Kernel Crash Reporting System - Discussion

2012-05-17 Thread Mateusz Guzik
On Wed, May 16, 2012 at 11:37:44PM +0300, tza...@it.teithe.gr wrote:
 Quoting Mateusz Guzik mjgu...@gmail.com:
 
 On Wed, May 16, 2012 at 12:30:20AM +0300, tza...@it.teithe.gr wrote:
 Hello Community,
 
 I have the project Automated Kernel Crash Reporting System for
 this GSoC and I would like to discuss my plans about it before
 starting the coding on May 21.
 
 
 Cogratulations. :)
 
 I have created a page in the FreeBSD Wiki 
 (http://wiki.freebsd.org/SummerOfCode2012/AutomatedKernelCrashReportingSystem)
 where I describe in details the architecture of the system.
 
 Here are some points that I would like to be discussed:
 
 * The implementation of the kcrashreporter is planned to be done in
 two shell scripts. The first shell script is a rc.d script and the
 second is the actual program. I choose to code it in shell because
 kcrashreporter invokes the kgdb to collect the necessary debugging
 information. I think that using the shell instead of traditional
 programming language for this kind of job is more straightforward
 and natural. Do you have a different opinion?
 
 
 Are you going to support textdumps?
 
 I would like to note that some machines have swap space only for
 textdumps, so I think you should support these.
 
 Support for textdumps is already on the list.
 
 ddb is equiped with a lot of cool commands that show various important
 debugging information(e.g. show alllocks). AFAIK kgdb doesn't have such
 facilities so you will have to implement those first if you decide to
 use it (btw I think these would be useful even without this project).
 Take a look at tools/debugscripts.
 That being said, I would give a priority to support for textdumps (and
 in case kgdb support cannot be finished in time, I would make sure that
 the project is expendable enough to support information obtained from
 kgdb and possibly other sources).
 
 Indeed, DDB is equipped with features that kgdb does not provide but
 only kgdb has access to the full debug information whenever we want
 because of its operation on the core dump. As far as I understand,
 if we want to use DDB to collect the debugging information, we have
 to do it *immediately* after the kernel panic and before the first
 reboot. Also consider that DDB is not included in the generic
 FreeBSD kernel of -STABLE and -RELEASE. You have to compile a custom
 kernel with the options KDB and DDB. I think that the nature of DDB
 as an on-line debugger is a restriction mainly for the manual
 behavior of kcrashreporter.

Maybe this is a gross misunderstanting on my side, but I'm pretty sure
that:

DDB supports simple form of scripting that allows series of commands to
be run on certain events, e.g. kernel panic. Output can be captured
(capture on).

textdump is a part of DDB that saves aforementioned output.

In other words, there are no textdumps without DDB and there is no
problem with running DDB commands automatically after panic. Also it
looks like you will have to actually add DDB to GENERIC in order to obtain
textdumps in default installations.

 I do not think that I could update the kgdb with the features that
 DDB provides, but if it is mandatory to collect these information
 and kgdb cannot, I will do my best.
 
 I don't know if these are good ideas (no clue about cryptography), but I
 would either:
 - HTTP POST data over SSL
 or
 - HTTP POST data encrypted with some public key
 
 Nice. What about curl over the HTTPS protocol?
 

curl would be ok, except it's not in the base system.

Actually I just now checked for tools in base that support HTTP POST and
couldn't find any. Should've checked before proposing such solution,
sorry.

 hardware information, dmesg, locks, locked vnodes, mount points, ps,
 backtraces of all threads
 
 Basically if ddb can show something easly enough (or you will be able to
 make it do so), the report should contain it.
 
 First I will try to search if and how we can obtain these
 information using kgdb.
 
 
 I guess this site won't be very busy, so whatever popular httpd you will
 choose it should be fine (although I would stick with either apache or
 nginx). No clue about databases.
 
 One more vote for nginx.
 
 Also it would be nice to have a way to contact the owner of machine that
 submitted the report. One way I can think of is the ability to specify
 e-mail address (say in rc.conf?) that will be included in the report.
 
 This is a feature that is included from the initial planning and
 with the way that you proposed :)
 
 
 
 This message was sent using IMP, the Internet Messaging Program.
 
 

-- 
Mateusz Guzik mjguzik gmail.com
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org


Re: GSoC Project: EFI on amd64/i386

2012-05-17 Thread Eric McCorkle
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 05/16/12 01:32, Andrey V. Elsukov wrote:

 As i see we already have sys/boot/efi/libefi/efipart.c that uses
 EFI BLOCK_IO_PROTOCOL to make part devsw. EFI BLOCK_IO_PROTOCOL
 provides access to each disk and partition. AFAIK it supports only
 GPT and MBR+EBR, so there might be some problems with ZFS support,
 because we can use ZFS atop of BSD partition.
 

I'd need to take a look, but if the efi loaders are not directly
calling the EFI_BLOCK_IO_PROTOCOL functions, then it should be easy to
implement a layer that understands BSDlabels.  IA64 might have a solution.

Then again, is a BSDlabel really necessary on a GPT disk?
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.19 (FreeBSD)

iQIcBAEBAgAGBQJPtPziAAoJENSCzbQ+koZ7WZwQAKPN80f/I3obnwSNgSeJ9RyJ
q14FYshFuOyaiPPm+HsRdJsv82rdOx9AWi5uuBLTjGADHQ7FdVZTk7fIvhSakUHN
d6s/FTcxpLopnibNApXXPNla2fHi25qz8c4axd/4XyxoJ1EGIWnXJ3pQ8R/GCNhK
olXDocZ+vylO6IW0ta2C4yq2rYFLNCKoR5+Kdoo4B/S+NEguqBCUW/DXTvWqeJw5
GJGzCTDmCKGaOp9LrSQ5jws4XmnqsoBFeL7Zd1Yu40KvS3QyhHpeh1GCZklq3ncG
xdGcK4P7/rwrfR3zSf0tHFCbt1o7BJ0XNHL4MrZflbGuQFGvIbdReXNmLi4QDvKS
7QzqsbbtgnL6NrWfJ/Z4UqEZt0dKAj9wZNX5AVP+p2KJomSoV2NPnuuFKAtoiGfe
282daJ4q3D60fxfdo/rExdpA6k2usnxZDCyFM15hhg4jJQDnl32Yj9ym5bbTeDDU
Uqoh1Ka/Oj/RtRXHLFdAdL34Jm4RyFgeaRUtVD7o7f5ASCHx0EuFFAh1eZTqFCEi
yN1V1+z8FE7va0fQDO7a5S+2O8Hph9K+W8Dxcuq1g/Rg8mBZ8Klny6etWghP6vvR
ISiqdMvLkfqqF3eVcB/EY9rLahHr14kabMtSWLRVurVjEPxZ/ju0+9342z3vcY75
xIQe8JfKjuOjkclmpioa
=flEs
-END PGP SIGNATURE-
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org

  1   2   3   4   5   >