Daniel Stritt | 26 Mar 03:18 2014

Vector graphics program

Hello, after perusing haikuware, bebits, and osdrawer seems to be down, but I can't find what I am looking
for. Does anyone know of a vector based graphics app for Haiku? Similar to the icon tool, but for full sized images.



Louis Feuvrier | 21 Mar 15:59 2014

Re: [GSOC2014] Introduction (Louis 'manny' Feuvrier)

Hello guys,

I post these two patches in here because I can't seem to find the registration
mails I have been sent by Haiku's TRAC. I have contacted umccullough on advice
from PulkoMandy and in the meantime I am posting here. I will link to this
e-mail in my application.

The patch 1/2 might be a bad change, but it is testifying of my ability to
patch something! The 2/2 patch however seems very legit to me.

I am sorry to post stupid patches like this but I am short on time this week,
as I am working on both a CTF and an advanced presentation on the linux UEFI
stub in my laboratory. I also wanted to patch in the UEFI subtree, to get
accustomed to the build system in the meantime.

Thank you for reading

Luposian | 18 Mar 19:08 2014

Re: Capitalisation of Haiku? [was Re: GSOC-2014: "IPv6 Polish"]

From: Matt Madia
Sent: Tuesday, March 18, 2014 2:52 AM
Subject: [haiku] Re: Capitalisation of Haiku? [was Re: GSOC-2014: "IPv6 Polish"]
On Mar 18, 2014 4:47 AM, "Simon Taylor" <simontaylor1-XZoyATsUNX5Wk0Htik3J/w@public.gmane.org> wrote:
> On 18 Mar 2014, at 00:15, Matt Madia <mattmadia-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:
> > On Mon, Mar 17, 2014 at 8:59 AM, Sriharsha Karamchati
> > <leo.harsha93-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:
> > Hello there!  Thanks for your interest in HAIKU for Google Summer of Code!
> Looks so much better to my eyes. My other personal bug-bear is those who call it haiku-os, but then we have the domain to blame for that misunderstanding :)

I totally agree... the logo is “HAIKU”.  The written version should be “Haiku”.  “Haiku” (the company), when being specifically referenced, should be called “Haiku, Inc.”  “Haiku” (the OS), when being specifically referenced, should be called “Haiku OS”.  The fact that the company and the OS have the exact same name does lend credence to the issue of referenced confusion.

There was Be, Inc. and BeOS.  You never had Be and Be, so there was never any confusion as to which of the two you were talking about.  The only confusion I ever ran into was when I’d say “BeOS” and people would think I was talking about BIOS!

I usually say “Haiku” when I’m talking about the OS, because the company, itself, is not often the center of conversation.  But if someone were actually knowledgeable enough about Haiku to actually GET confused, I would simply say, “Haiku OS”.

Unless familiarity with the current domain name were intractable, I’d suggest changing it to “Haiku.com” or “Haiku-Inc.” or “HaikuInc.” (based on the fact, the “company” produces the software, so you find Haiku OS at the Haiku Inc site).  Alternatively, using “Haikuos” (without the hyphen) would be preferable, to my eye.

Yeah, but... whatever... what is, is and what will be will be... as long as it isn’t Be, because it’s Haiku!


Louis Feuvrier | 17 Mar 16:14 2014

Re: [GSOC2014] Haiku as a stand-alone UEFI app

> 2. Being severely limited due to size restrictions (< 900 bytes), the 
> stage 1 boot loader is just clever enough to locate and load Haiku's 
> stage 2 boot loader (haiku_loader) from the same partition.

This is the platform-dependent part, and it is located in system/boot/platform,
I believe?

> 3. The stage 2 boot loader loads the kernel and required kernel modules 
> and starts the kernel.

And this is in the system/boot/loader folder, if I am not mistaken?

> So I see two reasonable approaches for UEFI:
> 1. Let the firmware directly load the stage 2 boot loader.
> 2. Let the firmware load a stage 1 boot loader that loads the stage 2 
> boot loader.

You are making a very interesting point. I now understand that shaping the
Haiku kernel directly into an UEFI application might be too big of an
enterprise. However, it seems to me that your first solution is a perfect
middle ground, in-between the original re-write of the BIOS part and the
correct use of the UEFI firmware.

Where do you think such changes should take place in the source tree? I am
having a hard time visualizing how to have both the legacy BIOS booted
platforms and the new UEFI booted machines cohexist, both regarding
installation or upgrade and the source tree itself.

> CU, Ingo

Thank you for your quick answer, I now understand way better how the Haiku OS
actually boots! My proposal is evolving slowly but surely, and the work ahead
seems more clear now.


Louis 'manny' Feuvrier
LSE - EPITA 2016

Sriharsha Karamchati | 17 Mar 13:59 2014

GSOC-2014: "IPv6 Polish" [New Project Idea + Patch of code]

     I have attached a patch of code which was written using scapy (python). This code modifies the DSCP code values for specific packet in order to provide privileged services for them. I think this can be effectively used while probing, as when we send the packets across the network to scan the Operating Systems for ports, I think we can mark these packets separately by modifying the DSCP values so that they get higher preference in the network traffic and do net get lost, thereby ensuring higher probability of the specific packet reaching out to all the systems.
    Any suggestions/Ideas will be appreciated.

P.S: Will someone please mentor this project idea and guide further. I would also like to work towards the completion of IPv6 framework by solving the ticket related to configuration mentioned in IPv6 polish-http://www.haiku-os.org/community/gsoc/2014/ideas


Sriharsha Karamchati

Attachment (code.zip): application/zip, 3987 bytes
Louis Feuvrier | 16 Mar 20:55 2014

[GSOC2014] Haiku as a stand-alone UEFI app

Hey guys,

I am Louis Feuvrier and I am interested in working on the UEFI bootloader for
Haiku-os in the context of GSOC. I already introduced myself here[1] if you are
interested. I discussed a bit with tqh regarding this matter, and the consensus
currently seems to be a simple stand-alone UEFI app replicating the work done
by the ia32 bios module.

As most you must know, the linux kernel is bootable without the help of any
bootloader on the UEFI platform. This archlinux forum post[2] casts light on
the fact that you can invoke the linux kernel with a correct command-line
directly with UEFI. I am wondering if this would not be a great way of
implementing UEFI support in Haiku, thus avoiding a re-write of a lesser
grub-clone, or the shipment of grub itself with a BFS-aware UEFI application.

This solution would need only a few tweaks on the existing kernel, as most of
the UEFI implementations around still have bios compatibility. Making the haiku
kernel compatible with pure UEFI hardware could be a next step in the process.
As far as I know, the TianoCore module for QEMU is also bios compatible, and
most PC around still keep a bios compatibility.

As stated by tqh, problems arise when upgrading the kernel. In fact,
considering the kernel would be stored in the UEFI partition (a simple
fat-formated partition,) a solution could be to mount this partition on the
/boot/efi folder or any other (as linux does currently.)

The only real problem I can see is the need to modify the command-line after
install, when upgrading the kernel or modifying the root partition for
example. There would be a need for a modification in the package-management
system, and a stand-alone program allowing the user to modify the NvRAM.
Another solution might be to just dump the command-line in a file on the UEFI
partition and just read it before loading the kernel.

I understand that this may imply fixes in many parts of the haiku source tree,
but the workload seems to be diminished by this solution, and attention can be
focused on making the best of the UEFI firmware itself.

I would greatly appreciate feedbacks from all of you on this idea, both
regarding the feasability itself, and the potential drawbacks.

Thanks for reading,

[1] http://www.freelists.org/post/haiku/GSOC2014-Introduction-Louis-manny-Feuvrier
[2] https://bbs.archlinux.org/viewtopic.php?pid=1090040#p1090040


Louis 'manny' Feuvrier
LSE - EPITA 2016

Fredrik Holmqvist | 16 Mar 19:26 2014

New and updated EFI branch

This is mostly for devs and potential GSoC students.

I've done some minor cleanup to the EFI code and updated to a new
Haiku revision to leave it in a better state than it has been siting
in for a few months. As I didn't want to change history in the efi_pm
branch I've created a new efi branch[1]. Consider the efi_pm branch

It builds and runs, if you disable 'treat errors as warnings' for
src/system/boot. This can be done in build/jam/ArchitectureRules by

  EnableWerror src system boot ;

You will need to configure for x86_64 to build the EFI application with

jam -q -sHAIKU_BOOT_PLATFORM=efi haiku_loader.efi

[1] https://github.com/tqh/haiku

Have fun...

Fredrik Holmqvist, TQH

Humdinger | 16 Mar 10:01 2014

Re: Goodsearch (was: Re: haiku Digest V14 #31)

Hi Alessandro!

On 15 March 2014 15:41, alessandro <almir159@...> wrote:
> I'm supporting Haiku (also) through goodsearch, and I don't understand how
> is it possible that the total (by all members) raised for haiku through
> goodsearch increase of only 1,5 ~ 2 dollars every day.
> But on the main page of goodsearch there is written " 1914 supporters".
> So, only 14 of 1914 really use this search engine?

My guess is that the majority of the 1914 supporters have only tried
Goodsearch a few times and weren't satisfied with the search results.
The Haiku community coming from all over the world, I suspect that the
lack of localization (i.e. filter results for sites from a specific
country) may be the main reason that Goodsearch doesn't work well for

I try to do a few searches a day with Goodsearch anyway. Let's hope
more people recognize this as a very easy way to support Haiku. A few
cents are donated in a minute. Multiplied by a thousand people, it's a
force to be reckoned with.


     Deutsche Haiku News  -  Haiku Gazette

Sriharsha Karamchati | 15 Mar 19:46 2014

[GSOC-2014] Introduction - [IPv6 Project]

Hi ,

I am Sriharsha Karamchati, Computer Science undergraduate student at "International Institute
of Information Technology. Hyderabad - INDIA". Currently doing my
research in Center for Security Theory And Algorithmic Research (CSTAR).

My Research stream being in IPv6 and Network Forensics. I am an IPv6
enthusiast  and have been working with it since 2 years and had quite a lot of Hands-on.


The projects I have done which are specifically related to IPv6, Operating System , Kernels, and Network were

1)Implemented Packet classification in IIIT Network.

2) I have written a white paper on Quality Of Services in IPv6.

3) Modifying DSCP code values in order to provide privileged services for the selected packets using scapy.

4)Made an Application Level file sharing protocol with support for upload/download/ Indexed searching and File Hashing.


5) Experience in Configuring Cisco Routers and Switches and Summer Project on Encapsulation of IPv6 Packets  .Also wrote new probes for OS scanning and IPv6 fingerprinting.


6) Made an OS Shell which supported almost all commands (Background processes, Redirection, I/O etc) of the Linux terminal and also some additional user defined commands.


7) Made 2 Hacks at Banglore Hackathon 2013: One on Packet Sniffing in an open Wifi Network and Displaying the statistics as feed for the users and displaying the Embed-code for popular sires and other on Distributed Computing ,which distributes the computation among the devices to optimize the memory and computation capacity using node.js


My present research project is “Setting up an IPv6 workbench for my Institute” which includes configuring various Operating Systems and Wireless devices..

I have been going through the Ideas page


“IPv6 Polish” was the one which fascinated me, I would love working with the unfinished task implementing them to perfection. And can also come up with some creative Ideas which would be highly appreciated once implemented in the OS. I was looking into the Haiku OS since few days,I might be late getting to you,I apologise for that , but I think  my high interest and experience with IPv6 should help me working with Haiku with great effort and effectiveness .

Any guidance/suggestions on how I shall proceed further would be of great help.

I will send my reports on the study I have done so far on IPv6 if required which might be helpful in developing the framework for IPv6 support.


Sriharsha Karamchati



alessandro | 15 Mar 15:41 2014

Re: haiku Digest V14 #31

Hi, excuse me if I write in this mailing list, perhaps it's not the best place...
I'm supporting Haiku (also) through goodsearch, and I don't understand how is it possible that the total (by all members) raised for haiku through goodsearch increase of only 1,5 ~ 2 dollars every day:
I raise 1 dollar every week doing my usually searchs.
It mean that 14 of us could raise together 2 dollars every day.
But on the main page of goodsearch there is written " 1914 supporters".
So, only 14 of 1914 really use this search engine?
Louis Feuvrier | 15 Mar 12:12 2014

Re: [GSOC2014] Introduction (Louis 'manny' Feuvrier)

> We use a subset of GNU-EFI. GNU-EFI caters to different OS'es,
> compilers, architectures
> and has its own library for support functions. It is an excellent
> library and much easier to
> work with than Tianocore.

I am familiar with your work on EFI-Example, it is a very informative
repository that helped me a lot getting on track quickly. I have it
working on my TianoCore-enhanced QEMU and will be trying to get it to
work on my hardware soon.

> > - What is the exact purpose of M. Holmqvist's github repository[5]?
> >   This is the sole place where I could find an EFI-related branch.
> It is the development branch for EFI related work. We usually use
> GitHub for bigger features.

Does this mean I am to do my pull-requests on this repository,
deliberately ignoring the warning[1] on the front page?

> I recommend checking out this tree, configure it for x86_64 and build
> the EFI app with
>   jam -sHAIKU_BOOT_PLATFORM=efi haiku_loader.efi

I am currently trying to get this to work, but I have to confess this is
my first time with boost Jamfiles, so this might take me some time.

I would like to patch stuff in the efi subtree, is there anything
non-trivial I can work on yet? I was thinking of editing the
serial_{init,puts} functions, as a humble start.

> And don't hesitate to ask if there is anything.

Will do!

[1] "Please do not perform Pull Requests here. They will be ignored.
Patches can be sent to http://dev.haiku-os.org/" on the github repo.

Thank you for reading,


Louis 'manny' Feuvrier
LSE - EPITA 2016