 |
|
| gcc? |
|
|
By shatty - Posted on August 3, 2002 - 20:14:37 (#2523)
Current version when comment was posted: 2.53 |
|
|
Hi, it seems like you've compiled these yourself. I was wondering if you had actually done that. If so, why not just post the binaries from geekgadgets? (are these more recent versions?) Along with that, I would recommend you to post the gcc from geekgadgets, or if you are porting, to try to port the latest gcc that maintains binary compatibility with beos. Yeah I know, that could take two months alone! But it would be very appreciated. :-)
|
|
| J00 4®3 0WN3|) B¥ N3†_$3®V3® |
|
|
By Jess - Posted on July 30, 2002 - 12:47:59 (#2452)
Current version when comment was posted: 2.53 |
|
|
J00 4®3 0WN3|) B¥ N3†_$3®V3® !¡!¡
|
|
| Re: hmmm |
|
|
By mmu_man - Posted on July 30, 2002 - 12:26:25 (#2451)
Current version when comment was posted: 2.53 |
|
|
Again, as part of OBOS, I can tell you that there *won't* be any net_server, not the way you intend at least. there surely will be inetd or a replacement, like BONE had anyway, as it's a standard UNIX daemon for connections. And anyway you have to distinguish between *implementations* and *API*. Even if the OBOS stack won't be BONE, it *will* have the BONE *API*, as the BONE API really _is_ the BSD API, and we all agreed that this was what we needed.
What that means is:
* sockets _will_ be like normal files,
* we will have a working select(),
* ...
All meaning many UNIX apps will compile *exactly the same* as they are already compiling on BONE. That is why I mean BONE's future is the OBOS stack.
As for the 2 lines you mention, again what's important here is not 'net_server', as it is used to designate the network stack, not an actual process, but 'kernel mode', and *for internal testing*.
That means that the stack *does* compile as a userland program, but it *doesn't* work with applications when compiled in userland. This is *only* to be able to test it more easily. Just like we are currently doing VM prototypes in userland as well, ONLY for testing, we surely won't have the VM in userland btw (that's a total non-sense =)).
|
|
| hmm |
|
|
By Jess - Posted on July 30, 2002 - 11:09:23 (#2449)
Current version when comment was posted: 2.53 |
|
|
Well it's a given if you where one of the testers it's not illegal for you then but how many people running BONE where REAL testers... I would wager then BONE utils & application would benifit what... all 4 you you guys... heh & from below a paste from the OBOS networking site... hmm seems net_server esque to me... I see no BSD like or Bone referance...if I'm wrong I'm wrong but from what I have heard it will be as I have said in all my other posts net_server esque -still seems that way to me... time will tell either way
- Jess
kernel mode net_server
userland net_server (for internal testing)
|
|
| corrections |
|
|
By mmu_man - Posted on July 30, 2002 - 10:56:07 (#2447)
Current version when comment was posted: 2.53 |
|
|
* BONE == ILLEGAL
Depends. for beta testers, it's certainly not, since they were requested to beta test it :) So that's what they do actually. For developpers, well that helps them waiting for a better one, so that they can focus on other things than net_server oddities, and then when the time comes to switch to another netstack we will get all the apps at once.
That doesn't mean I encourage ppl to use BONE, just that it has a role to play in BeOS.
Moreover, some parts of BONE are totally legal, as they have been made public on Be's site :
http://planetmirror.com/pub/beos/samples/bone/bone.zip
* YellowTab will have a net_server esque Net
True, as they use BeOS R5. Although I suspect they would be allowed by their agreement to use BONE (not sure, didn't read it), and also they plan on switching to OBOS or another OSBOS, so this isn't fixed.
* BONE has no future
* OBOS will have a net_server esque
False, and false as well, the OBOS stack will be BSD-like, in-kernel, and have nearly all the features BONE has (I mean userland-wise ! We won't be able to load bone kernel modules for example... well why not in fact :)). So YES BONE has a future, and it's the OBOS netstack. For me it's a logical upgrade.
* libpthreads
Someone was working on this, but I dunno what state it's in now, I heard it needed something from the kernel or something...
* I knew they where hard to begin with so maybe a Be Networking guru would want to start "bmap"
Sure it's harder do fix an unixish prog to use net_server, and it's not worth it in some cases, like say, netcat. And it would be even harder to begin coding a specific net_server version as it is deprecated (as far as I'm concerned), and it will be useless in some time.
* Something I said, that the OBOS net stack would be available for R5.
Well, it seems that the R5 kernel has a broken select() implementation that would give funky results anyway :-( Except that the OBOS netstack already runs in R5, and this select() issue is the only thing that prevents it from being really useful (net_server had issues with select() too btw, so maybe it would be better anyway, dunno, will haev to test). I bet it would run without a glitch on a bonified kernel, as it has a fixed select() :^)
<rant>Btw, if you really want networking in userland, consider switching to GNU Hurd :)))</rant>
|
|
| This is touchy |
|
|
By Jess - Posted on July 30, 2002 - 10:12:05 (#2446)
Current version when comment was posted: 2.53 |
|
|
Ok guys lets recap a few things... BONE = ILLEGAL so I'm not going to encourage BONE use... I know I don't want my workd ripped off or ill released b4 it was done or ready & I wouldnt want that for the guys at Be Inc. Also as I said YellowTab & AFAIK OBOS will have a net_server esque Net so again the net_server ports will be harder but better in the long run imo. I knew they where hard to begin with so maybe a Be Networking guru would want to start "bmap" heh multi threaded BeOS native "nmap" like tool along with some of the others. This may be a larger task then it's worth but I'm just tossing ideas out. BONE has no future so untill I can do these things myself & I am at the mercy of the porter's disgression
- Jess
|
|
| libpthread |
|
|
By Luton Hatter - Posted on July 30, 2002 - 09:07:42 (#2445)
Current version when comment was posted: 2.53 |
|
|
is anyone working on a libpthread atm.?
"anything that requires libpcap really isnt worth doing on net_server and until we get a working libpthreads things like MySQL (client or server) will not be available any time soon."
|
|
| RE: BONE |
|
|
By ahwayakchih - Posted on July 30, 2002 - 05:53:43 (#2443)
Current version when comment was posted: 2.53 |
|
|
mmu_man, ok ok. i just didn't want anyone to think "screw net_server ppl, we will have new net anyway and there is BONE"... i mean, yeah sure, if there will be new net in a month or so, than ok. but i doubt it will be. and BONE is not the answer for me.
|
|
| i have to agree with mmu_man |
|
|
By moooooooo - Posted on July 30, 2002 - 05:49:04 (#2442)
Current version when comment was posted: 2.53 |
|
|
most of the packages i port wont work on net_server and to get them to work would take a huge amount of effort and workarounds. so much so that the patches would be too big in most cases to be accepted back into the source trees.
anything that requires libpcap really isnt worth doing on net_server and until we get a working libpthreads things like MySQL (client or server) will not be available any time soon.
OBOS will change this and i look forward to it.
OBOS net_stack is already working (congrats to the team) and soon it will have kernel hooks too.
and Francois has just got his mmap() underway. things are looking good.
some of the apps here in the gnu packages have been checked into the OBOS source tree. The ones that Justin cant get working maybe he should talk to the OBOS people and make a joint effort.
The BeOS community is a friendly one and it never hurts to ask.
These comments pages on here arent really the place to try and get projects up and running.
You should get on to BeShare and as around, also get onto the forums like BeGroovy, The Synapse Loune, BeOSJournal.org forums or TheGreenboard.com.
and remember - we like feedback. Any feedback. Bugs, requests, praise. whatever.
just my 0.02c
peter
|
|
| Re: BONE |
|
|
By mmu_man - Posted on July 30, 2002 - 04:55:37 (#2441)
Current version when comment was posted: 2.53 |
|
|
You missunderstood me.
What I mean is:
* net_server is bloated, and deprecated, as it lacks some features needed for most of the apps I port anyway.
* when I tell BONE, I mean _BSD_ API, that is:
- sockets as files,
- BSD syscalls,
- select(), ...
all of which _will_ be provided by the OBOS net stack too. I'm not into BONE specific things like kernel modules, or undocumented ioctls.
* OBOS net stack *will* run on R5 AFAIK, (it already does), and it will have a BSD API.
So AFAIAC, it's 1) BONE, 2) net_server when doable without much hastle, and 3) then recompile OTB for the OBOS stack when it comes out. And most (all) of the soft I port is opensource anyway, so nothing stops anyone from adding the bits it misses for net_server.
|
|
| mmu_man |
|
|
By ahwayakchih - Posted on July 30, 2002 - 04:15:59 (#2440)
Current version when comment was posted: 2.53 |
|
|
hmm.. no, BONE IS NOT default API and SHOULD NOT be. new users get net_server. i still use net_server - it's default.
last i've read maillist archives of OBOS net team their leader said they are not oing to replace net_server :( so we will have new net only with OBOS release - which means a year or more of waiting :(
|
|
| Re: ever thought about asking the author/porter? |
|
|
By mmu_man - Posted on July 30, 2002 - 03:12:02 (#2436)
Current version when comment was posted: 2.53 |
|
|
And also the original author. I mean do a diff and send it to the package maintainer. So that next time you won't have to redo it all again, but just ./configure && make && make install !
Whenever porting such foreign things, try to avoid hacking directly, but leave the original code, and #if(n)def it to __BEOS__, so the package still compiles on the target it was intended to. This way the maintainer will have less reason to refuse your patch.
Also try to make changes only to sources, not derivatives. That is if there is a Makefile, but also a Makefile.in, and even if you hack the Makefile first, report your changes in the Makefile.in so you can just erase the Makefile (or make distclean) and revuild the whole thing directly. That goes for ./configure too and others. This way the patch can be directly applied without any more work from the maintainer, so he will thank you a lot.
Doing a patch is quite easy (do not add / to folder names, this will do weird things):
~/foobar$ cd ..
~$ mv foobar foobar.new
~$ tar zxf foobar.tgz
~$ mv foobar foobar.org
~$ mv foobar.new foobar
~$ diff -urN foobar.org foobar >foobar-beos-1.patch.txt
And voila :^)
(you may want to clean it up before submiting... (but be careful))
|
|
| Re: hmmm |
|
|
By mmu_man - Posted on July 30, 2002 - 02:59:08 (#2435)
Current version when comment was posted: 2.53 |
|
|
Better wait for OBOS network stack, won't be long IMO.
As far as I'm concerned, net_server is deprecated, and BONE is the default API until the OBOS stack comes out (I speak userland-wise, BONE is a no-no for kernel things as add-ons), even if I must write myself what it lacks =)
|
|
| hmmm |
|
|
By moooooooo - Posted on July 30, 2002 - 02:11:04 (#2434)
Current version when comment was posted: 2.53 |
|
|
well last time i looked (about a month ago) nmap was at 2.54beta.
nmap for net_server - i was working on it anyway
the others that require libpcap will not be able to be done on net_server though.
unless some guru out there can do a net_server port of libpcap (see http://www.tcpdump.org/ )
peter
|
|
| I did silly... |
|
|
By Jess - Posted on July 29, 2002 - 22:26:46 (#2433)
Current version when comment was posted: 2.53 |
|
|
heh you so silly man. I had asked you, but I'm not sure if you ever got the email. I have emailed you a few times but only got one response. That was about the nmap oddity. nmap is up to v2.99 now so think you can pull off a net_server version of these utils? Now you have been publically asked heh. ;)
|
|
| ever thought about asking the author/porter? |
|
|
By moooooooo - Posted on July 29, 2002 - 21:37:46 (#2432)
Current version when comment was posted: 2.53 |
|
|
Jess, given that i ported these over for BONE )nmap, PHoss, Snort, Portsentry (Portsentry has a bug at the moment)) have you ever thought about emailing me?
I mean that's what the "Email Publisher" link on BeBits is for. That and for bug reports.
Saves on duplicate effort and you may not even know that i am working on it anyway!
Communication is what it's all about ;-)
peter
|
|
| Don't kill yourself! |
|
|
By Jess - Posted on July 29, 2002 - 18:20:48 (#2430)
Current version when comment was posted: 2.53 |
|
|
Don't kill yourself due to lack of sleep or somthing man. Thanks very much for this stuff. I'm sure every one would be pleased with one new tool per week if that would be how it went. The point is thanks just don't make your brain go pop since as far as I know your not going to die if you dont port 300 *nix tools in 2 weeks heh. But as I said I don't know maybe your trying to thwart a contract with the devil heh. - TH4NKZ
- Jess
|
|
| net utils |
|
|
By triplez - Posted on July 29, 2002 - 17:03:26 (#2429)
Current version when comment was posted: 2.53 |
|
|
I will try my best to port what you request Jess. But I'm not too familiar with net_server. I'm more familiar with linux networking, but like I said, I'll try my best when I have the time. =)
As everyone might notice, the output is slowing down to 1-2 packages per day and it will slow down to 1 package per 2 days, but I'm trying hard as I come across more and more packages that doesn't port easily with just a "make".
Thanks for your encouragement Jess. Appreciate it! =)
Regards
Justin Lee
|
|
| Wicked! ~but with a twist... |
|
|
By Jess - Posted on July 29, 2002 - 16:35:06 (#2428)
Current version when comment was posted: 2.53 |
|
|
Well dude I must say Thanks Alot for porting these tools. These wil be soo usefull to the comunity but I have a request... (place dramatic music here) ~DUM DUM DUM~ Think you could toss in nmap, PHoss, Snort, or Portsentry? for net_server that is... it will be a longer lasting port imo then the Bone ones as the OBOS & YellowTab net stacks will be net_server esque. I hope you read this & at least consitter it.
|
|
| Thanks alot!! |
|
|
By triplez - Posted on July 28, 2002 - 12:10:41 (#2411)
Current version when comment was posted: 2.53 |
|
|
First thing first. Brian, thanks alot for that post. I really appreciate it. I've done alot of testing for most of the packages released here (well, those that HAS a testing package) and most of them pass with 98% passes. I will redo alot of the packages again to reduce dependancies between the packages especially the lib files (wonder why I would do that, but it helps alot anyway). And I'll try to find the time to post the tests out to the maintainers and maybe here too, and the compile options and the changes I made. Yes, the source files didn't come with the updated code. (Well sorry! I'm only human)
Secondly, about the post of binutils. Yes, I have been VERY VERY hesitant to release this because firstly, I need to put it under gnupro directory to avoid any conflict. Secondly, it hasn't undergone as much testing as I want it to. Yes, it works. I've run the test system and it passed with "FEW" errors. But I just have this nudging feeling it doesn't work SOMEWHERE SOMEHOW. Anyway, it doesn't really harm your system that badly. Just do what my small fine print note suggest if anything screws up.
Hehe! Nobody reads the fine print.
Regards,
Justin
PS
Thanks alot guys, I'll try my best to work on some of the harder-to-compile packages, so there will be lesser updates each day. I need sleep too. I haven't slept for days.
|
|
| cool. |
|
|
By brian68 - Posted on July 28, 2002 - 06:51:38 (#2407)
Current version when comment was posted: 2.53 |
|
|
IMHO, Justin did the right thing by posting a warning. I just wanted to clarify the issue in case anyone was hesitant to install because of it. Enjoy! :-)
|
|
| Brian |
|
|
By ahwayakchih - Posted on July 28, 2002 - 06:40:36 (#2406)
Current version when comment was posted: 2.53 |
|
|
yeah, but all packages except binutils (which i haven't installed) are installed to /home so all is ok.
|
|
| shard... |
|
|
By brian68 - Posted on July 28, 2002 - 06:01:26 (#2404)
Current version when comment was posted: 2.53 |
|
|
I'm referring to the warning on the GNU Packages page about possibly damaging your system, which is true if you install in /boot/beos/bin.
|
|
| hmm? |
|
|
By ahwayakchih - Posted on July 28, 2002 - 04:59:28 (#2399)
Current version when comment was posted: 2.53 |
|
|
Brian what are You talking about? Packages ARE installed in /boot/home/config/bin not in /boot/beos... all is ok here.
Triplez THX for Your work! :)
|
|
| Agreed -- in most cases |
|
|
By brian68 - Posted on July 28, 2002 - 04:54:26 (#2398)
Current version when comment was posted: 2.53 |
|
|
I prefer to install everything into ~/config/bin if I can. With the GeekGadgets, I prefer to remove the originals if I am installing a newer version. Just a personal preference to make testing easier. I never have to wonder if the wrong something-or-other joined the party. :-)
If any of the other installed GeekGadgets have hardcoded paths (I think some do), they will find the new app in the same place and (hopefully) not notice that anything has changed.
|
|
| Install locations.... |
|
|
By verranm - Posted on July 28, 2002 - 04:29:17 (#2397)
Current version when comment was posted: 2.53 |
|
|
I'd rather these go to /boot/home/config than geekgadgets. Doing it this way prevents version conflicts
|
|
| recommendations |
|
|
By brian68 - Posted on July 28, 2002 - 03:26:48 (#2396)
Current version when comment was posted: 2.53 |
|
|
I highly recommend configuring these packages, especially binutils, to install in /boot/apps/GeekGadgets, or at the very least, /boot/home/config/bin. You should never install anything into /boot/beos/bin.
Also, since a number of these packages depend on other packages installed on your system, I think each user should seriously consider grabbing the source and at least running 'make check'. Any errors you encounter in the test script can be sent to the official GNU bug lists where the maintainers can help you debug them.
Ultimately, I would like to see these port updates make it back into the GeekGadgets project set. There are some real gems in there and they're getting pretty rusty. See http://www.geekgadgets.org for details.
|
|
| 15 Packages and counting! |
|
|
By triplez - Posted on July 27, 2002 - 21:18:44 (#2392)
Current version when comment was posted: 2.53 |
|
|
Phew! Sorry that releases are getting slower and slower as I come across more and more errors compiling. Sigh. Nobody said this was easy! =)
Need help trying to get fileutils, textutils, sh-utils compiled!!
|
|
| All in one a NO NO. |
|
|
By triplez - Posted on July 27, 2002 - 11:20:29 (#2382)
Current version when comment was posted: 2.53 |
|
|
I'll be adding new packages everyday (trying my best) and zipping up into 1 big file everytime I update it isn't something I really want to be doing.
So bear with it. Sorry bout it.
|
|
| Support |
|
|
By verranm - Posted on July 27, 2002 - 05:29:14 (#2380)
Current version when comment was posted: 2.53 |
|
|
Great idea to collect these together, especially as .pkg's.
If I come across any others I need I'll build and post to you.
|
|
| All in one? |
|
|
By benno - Posted on July 27, 2002 - 02:22:47 (#2379)
Current version when comment was posted: 2.53 |
|
|
Hi,
can you put all packages you have compiled so far in one? This would make downloading a lot easier.
|
|
| support this effort |
|
|
By moooooooo - Posted on July 26, 2002 - 22:49:56 (#2377)
Current version when comment was posted: 2.53 |
|
|
i've "spoken" to Jason and there will be more than just these apps appearing here.
Please ensure you send him bug reports if there are any.
cheers
peter
|
|
| ncurses |
|
|
By moooooooo - Posted on July 25, 2002 - 03:43:39 (#2353)
Current version when comment was posted: 2.53 |
|
|
if there was a problem with my ncurses port then why not email me about it? it works fine on my 2 BeOS PCs and other peoples PCs....a bug report would have been nice ;-)
cheers
peter
|
|
|
|
|
