JAVA & FreeBSD
16 отговора
909 прегледа
JAVA & FreeBSD
Някой може ли да ми предложи стабилна версия на JVM за FreeBSD. 1.5 изгърмя след 5 часа компилиране. Вобще има ли лесен начин да се работи с JAVA под тази операционна система. Ако някой JAVA developer работи под някакъв unix, моля да сподели опита си. Не искам да чета мнения за и против!
Нямам никакъв опит с JAVA. До момента не съм писал на JAVA, само на C++, PHP и др.
I wanna read interesting postingz
Нямам никакъв опит с JAVA. До момента не съм писал на JAVA, само на C++, PHP и др.
I wanna read interesting postingz
Re: JAVA & FreeBSD
New version of Kaffe has been released. Kaffe is a clean room implementation of the Java virtual machine, plus the associated class libraries needed to provide a Java runtime environment. 1.1.5 release sports improved AWT implementation, new garbage collector, internationalization support, new ports to FreeBSD on x86-64, Darwin on x86 and HP-UX on ia64 and much more.
в отговор на ilko_partizan
#7
Re: JAVA & FreeBSD
Благодаря, ще го погледна.
I wanna read interesting postingz
I wanna read interesting postingz
Re: JAVA & FreeBSD
В абсолютна заблуда си - ядрото на MacOS X е базирано на Mach, а не на FreeBSD. Двете ядра нямат почти нищо общо. Колекцията от базови програмки, които заедно с ядрото правят ОС-а (без Водата и Графита, дето са си техни разработки и правят OSX-а толкоз пари) е взета от FreeBSD, а не ядрото!
Re: JAVA & FreeBSD
Имаш няколко варианта:
1) Сваляш си Жаба Хикс.Игрек.Зет за Пингвиникс от сайта на Слънцето и я пускаш под емулацията на Пингивникс. Работи перфектно и това е препоръчителният (поне според мен) начин да се пускат Жаби под СвободноБСД. Дори и Затъмнение 3.0.2 тръгва.
2) Сваляш си сорса на Жабата + пачовете от проекта, дето се цели да направи сорсовете пригодни за компилиране под СвободноБСД и компилираш. Трябват ти към 1.3 ГБ свободно място и много свободно време, особено ако си от хората като мен, които изпадат в транс докато гледат как се мяткат редовете от компилацията по екрана... Този метод е приложим само за Жаба2 и по-ранните версии. Пачовете за Жаба5 са силно експериментални, както си го пише на сайта на проекта.
3) Опитваш с някоя друга Жаба - тази на Изключително Бавните Машини (ИБМ), на някакви си БлекНеЗнамСиКвоСи (звучи много хакерско, и никога не съм и посмявал да се опитвам да я сложа). Изобщо не е като да няма алтернативни реализации на Жаба, освен тази на Слънцето.
1) Сваляш си Жаба Хикс.Игрек.Зет за Пингвиникс от сайта на Слънцето и я пускаш под емулацията на Пингивникс. Работи перфектно и това е препоръчителният (поне според мен) начин да се пускат Жаби под СвободноБСД. Дори и Затъмнение 3.0.2 тръгва.
2) Сваляш си сорса на Жабата + пачовете от проекта, дето се цели да направи сорсовете пригодни за компилиране под СвободноБСД и компилираш. Трябват ти към 1.3 ГБ свободно място и много свободно време, особено ако си от хората като мен, които изпадат в транс докато гледат как се мяткат редовете от компилацията по екрана... Този метод е приложим само за Жаба2 и по-ранните версии. Пачовете за Жаба5 са силно експериментални, както си го пише на сайта на проекта.
3) Опитваш с някоя друга Жаба - тази на Изключително Бавните Машини (ИБМ), на някакви си БлекНеЗнамСиКвоСи (звучи много хакерско, и никога не съм и посмявал да се опитвам да я сложа). Изобщо не е като да няма алтернативни реализации на Жаба, освен тази на Слънцето.
Re: JAVA & FreeBSD
Бе май и ти си малко заблуден ама аре...
Предлагам ти малко енциклопедични данни.
(малко е дълго за четене, но пък може да ти е интересно...)
ОС-а: Apple MacOS X
Ядрото на Mac OS X: Apple Darwin
"Darwin is the core operating system of Apple Computer's Mac OS X and runs on an open source kernel called XNU.
Darwin integrates a number of techonlogies, most importantly the Mach 3.0 kernel, operating system services based on 4.4 BSD (Berkeley Software Distribution, particularly FreeBSD), high-performance networking facilities, and support for multiple integrated file systems.
..."
Ядрото върху което се изгражда Darwin: XNU
"XNU is the name of the kernel used in the open source Darwin operating system, that Apple uses as the foundation of its Mac OS X operating system. It is a hybrid kernel based on a mixed Mach kernel and FreeBSD kernel. XNU is a recursive acronym for 'XNU is Not Unix'
The primitives and fundamental services of the XNU kernel are based on Mach 3.0. Apple modified and extended Mach to meet the functional and performance goals of Mac OS X. Mach 3.0 was originally conceived as a simple, extensible microkernel. As such, it is able to run the core of an operating system as a separated process, which allows a great flexibility (one could run several operating systems in parallel above the Mach core), but this reduces performance because of the translations between Mach and the different codebases. With Mac OS X, since the behavior of the system is known in advance, BSD functionalities were built in to the core with Mach. The result is a combination of the assets of Mach and BSD. The Mach side of the kernel is responsible for the memory management, inter-process communication and the imput-output system, it also allows protective memory, pre-emptive multitasking and avanced virtual memory. The BSD side of the kernel manages users and the permissions, contains the network stack, offers virtual filing system and maintains POSIX compatibility."
За Mach ядрото: Mach kernel
"Mach is an operating system kernel developed at Carnegie-Mellon University to support operating system research, primarily distributed and parallel computation. The project at CMU ran from 1985 to 1994.
Mach developed from the realization that all modern operating systems shared a number of features in common, or wanted to if they didn't already. These included:
- support for multiple applications using multitasking
- threads, which can be thought of as parts of an application, or mini-applications which then multitask
- multi-processor support, in a single machine or over a network
- interprocess communications, sending messages directly between applications
- memory protection and safety
At the time, in the early to mid-1980s, any number of projects were attempting to address one of these problems. This typically meant taking an existing OS - often BSD - and modifying parts of it. After each modification the OS was compiled, the machine restarted, and the new change was tested. There were a number of problems with this approach, not the least of which was that even minor problems would cause the entire machine to crash.
Mach explored the concept that we now refer to as a microkernel. Instead of having all of the code for the operating system in a single large program (called the kernel), the majority of the code would instead be located in smaller programs known as servers which would run like any other program. The kernel's job was reduced from essentially "being" the OS, to maintaining the servers and scheduling their access to hardware.
In theory this meant that changes to the OS required nothing more than a re-loading of that single server program, as opposed to re-building OS and restarting the machine. Only work on the Mach kernel itself would require a restart, and in theory this should be a rare occurrence.
Mach is not an operating system on its own, and is largely unusable without a set of servers - and those servers did not exist. In order to get some sort of usable system up and running, the Mach authors ported BSD onto the Mach kernel in a quick-and-dirty fashion: instead of breaking down BSD into parts and building each of them as a server, they simply compiled the entire kernel into one server and ran it. The result was known as POE (which is distinct from the Perl Object Environment).
With POE running (effectively) beside the other applications, performance was abysmal. Every call from a user application, say to get the time, required the message to be sent to the kernel (an expensive operation known as a context switch), which would then send the request to the Unix library with another context switch - and then repeat it all again for the response! Thus Mach, through no real fault of its own, was generally considered to be very powerful, but incredibly slow.
Work over the next decade managed to improve the performance of these messages many times, to the point where the performance of late Mach-like operating systems was in fact often better than the BSDs they were based on. However by this point in time the academic world had largely lost interest in OS research, and Mach's promise remains unfulfilled.
At one time it was thought that Mach would slowly take over the entire operating system universe, but this has not happened. Perhaps the biggest reason for the general failure of Mach can be blamed on "laziness": everyone seemed to think it was someone else's job to deliver the library-based OS, and no one ever did. The largest effort to date is GNU Hurd, but GNU Hurd is now about a decade overdue. Several proprietary operating systems have been more successful, including QNX which seems to deliver on all of Mach's promises.
Work on Mach took place for a number of years at CMU, but eventually became dormant when many of the players involved left school to work in industry. Mach was briefly revived at the University of Utah in the mid-1990s and produced Mach 4 with significant improvements, before once again becoming dormant.
Meanwhile several vendors took practical approaches to using Mach. The BSD (or other) layer was run directly inside the kernel (thus avoiding lots of context switches) which resulted in reasonable performance while still retaining the advantages of multi-processing and an easy-to-use threading model. However even these advantages have been eroded as the various Unix vendors worked to provide them in their own products.
Versions of Mach-based operating systems of this ilk were found in OSF/1, NeXTSTEP and IBM's OS/2 for the RS6000-based machines - all of which are no longer widely used. Other operating systems looked to migrate to this sort of system as well, including Apple's Pink, IBM's Workplace OS, and any number of others.
Apple selected OPENSTEP to be the basis for the successor of the classic Mac OS. It became the Cocoa API of Mac OS X. OPENSTEP is in fact an upgraded version of NeXTSTEP, which used Mach 2.5. As such, OPENSTEP's Mach/BSD amalgam is the basis for Apple's Mac OS X operating system.
The lead developer on the Mach project, Richard F. Rashid, has been working at Microsoft since 1991 in various top-level positions revolving around the Microsoft Research division. Microsoft's Windows NT, forerunner of the current Windows XP, began with a microkernel-based model similar to the Mach's one.
Another of the original Mach developers, Avie Tevanian, was formerly head of software at NeXT and today is Chief Software Technology Officer at Apple."
Предлагам ти малко енциклопедични данни.
(малко е дълго за четене, но пък може да ти е интересно...)
ОС-а: Apple MacOS X
Ядрото на Mac OS X: Apple Darwin
"Darwin is the core operating system of Apple Computer's Mac OS X and runs on an open source kernel called XNU.
Darwin integrates a number of techonlogies, most importantly the Mach 3.0 kernel, operating system services based on 4.4 BSD (Berkeley Software Distribution, particularly FreeBSD), high-performance networking facilities, and support for multiple integrated file systems.
..."
Ядрото върху което се изгражда Darwin: XNU
"XNU is the name of the kernel used in the open source Darwin operating system, that Apple uses as the foundation of its Mac OS X operating system. It is a hybrid kernel based on a mixed Mach kernel and FreeBSD kernel. XNU is a recursive acronym for 'XNU is Not Unix'
The primitives and fundamental services of the XNU kernel are based on Mach 3.0. Apple modified and extended Mach to meet the functional and performance goals of Mac OS X. Mach 3.0 was originally conceived as a simple, extensible microkernel. As such, it is able to run the core of an operating system as a separated process, which allows a great flexibility (one could run several operating systems in parallel above the Mach core), but this reduces performance because of the translations between Mach and the different codebases. With Mac OS X, since the behavior of the system is known in advance, BSD functionalities were built in to the core with Mach. The result is a combination of the assets of Mach and BSD. The Mach side of the kernel is responsible for the memory management, inter-process communication and the imput-output system, it also allows protective memory, pre-emptive multitasking and avanced virtual memory. The BSD side of the kernel manages users and the permissions, contains the network stack, offers virtual filing system and maintains POSIX compatibility."
За Mach ядрото: Mach kernel
"Mach is an operating system kernel developed at Carnegie-Mellon University to support operating system research, primarily distributed and parallel computation. The project at CMU ran from 1985 to 1994.
Mach developed from the realization that all modern operating systems shared a number of features in common, or wanted to if they didn't already. These included:
- support for multiple applications using multitasking
- threads, which can be thought of as parts of an application, or mini-applications which then multitask
- multi-processor support, in a single machine or over a network
- interprocess communications, sending messages directly between applications
- memory protection and safety
At the time, in the early to mid-1980s, any number of projects were attempting to address one of these problems. This typically meant taking an existing OS - often BSD - and modifying parts of it. After each modification the OS was compiled, the machine restarted, and the new change was tested. There were a number of problems with this approach, not the least of which was that even minor problems would cause the entire machine to crash.
Mach explored the concept that we now refer to as a microkernel. Instead of having all of the code for the operating system in a single large program (called the kernel), the majority of the code would instead be located in smaller programs known as servers which would run like any other program. The kernel's job was reduced from essentially "being" the OS, to maintaining the servers and scheduling their access to hardware.
In theory this meant that changes to the OS required nothing more than a re-loading of that single server program, as opposed to re-building OS and restarting the machine. Only work on the Mach kernel itself would require a restart, and in theory this should be a rare occurrence.
Mach is not an operating system on its own, and is largely unusable without a set of servers - and those servers did not exist. In order to get some sort of usable system up and running, the Mach authors ported BSD onto the Mach kernel in a quick-and-dirty fashion: instead of breaking down BSD into parts and building each of them as a server, they simply compiled the entire kernel into one server and ran it. The result was known as POE (which is distinct from the Perl Object Environment).
With POE running (effectively) beside the other applications, performance was abysmal. Every call from a user application, say to get the time, required the message to be sent to the kernel (an expensive operation known as a context switch), which would then send the request to the Unix library with another context switch - and then repeat it all again for the response! Thus Mach, through no real fault of its own, was generally considered to be very powerful, but incredibly slow.
Work over the next decade managed to improve the performance of these messages many times, to the point where the performance of late Mach-like operating systems was in fact often better than the BSDs they were based on. However by this point in time the academic world had largely lost interest in OS research, and Mach's promise remains unfulfilled.
At one time it was thought that Mach would slowly take over the entire operating system universe, but this has not happened. Perhaps the biggest reason for the general failure of Mach can be blamed on "laziness": everyone seemed to think it was someone else's job to deliver the library-based OS, and no one ever did. The largest effort to date is GNU Hurd, but GNU Hurd is now about a decade overdue. Several proprietary operating systems have been more successful, including QNX which seems to deliver on all of Mach's promises.
Work on Mach took place for a number of years at CMU, but eventually became dormant when many of the players involved left school to work in industry. Mach was briefly revived at the University of Utah in the mid-1990s and produced Mach 4 with significant improvements, before once again becoming dormant.
Meanwhile several vendors took practical approaches to using Mach. The BSD (or other) layer was run directly inside the kernel (thus avoiding lots of context switches) which resulted in reasonable performance while still retaining the advantages of multi-processing and an easy-to-use threading model. However even these advantages have been eroded as the various Unix vendors worked to provide them in their own products.
Versions of Mach-based operating systems of this ilk were found in OSF/1, NeXTSTEP and IBM's OS/2 for the RS6000-based machines - all of which are no longer widely used. Other operating systems looked to migrate to this sort of system as well, including Apple's Pink, IBM's Workplace OS, and any number of others.
Apple selected OPENSTEP to be the basis for the successor of the classic Mac OS. It became the Cocoa API of Mac OS X. OPENSTEP is in fact an upgraded version of NeXTSTEP, which used Mach 2.5. As such, OPENSTEP's Mach/BSD amalgam is the basis for Apple's Mac OS X operating system.
The lead developer on the Mach project, Richard F. Rashid, has been working at Microsoft since 1991 in various top-level positions revolving around the Microsoft Research division. Microsoft's Windows NT, forerunner of the current Windows XP, began with a microkernel-based model similar to the Mach's one.
Another of the original Mach developers, Avie Tevanian, was formerly head of software at NeXT and today is Chief Software Technology Officer at Apple."
Re: JAVA & FreeBSD
Сваляш си Жаба Хикс.Игрек.Зет за Пингвиникс от сайта на Слънцето
това е препоръчителният (поне според мен) начин да се пускат Жаби под СвободноБСД. Дори и Затъмнение 3.0.2 тръгва.
Най-добри шансове имаш с каффе, но те не поддържат до 1.3 сънско
Леле, Боже, какви затъмнения, какви кафета, какви луди жаби...
Eeeeeeeeeeeeeeeaaaaaaasy rider
това е препоръчителният (поне според мен) начин да се пускат Жаби под СвободноБСД. Дори и Затъмнение 3.0.2 тръгва.
Най-добри шансове имаш с каффе, но те не поддържат до 1.3 сънско
Леле, Боже, какви затъмнения, какви кафета, какви луди жаби...
Eeeeeeeeeeeeeeeaaaaaaasy rider
