Well, what's stopping people using NexentaStor (non-free) or NexentaOS (free as in beer/speech)? Better yet, Nexenta is OpenSolaris w/ ZFS, etc, but is an Ubuntu LTS 8.04-based distribution. Its always been the best of both worlds. If you have something using ZFS today, you can export the pool, install Nexenta, and reimport, being back up in minutes.
CalDav is the wave of the future, with most calendaring clients supporting it (but not MS), and many servers commercial and otherwise also supporting it (Zimbra). The real coming out party was the commercial release of both OSX Server 10.5 and the client, which have both ends. But guess what, the server is open source: calendar server can be gotten and put on any platform. If you want something today, Zimbra or OSX Server are there for the taking. RedHat has a Messenging product coming out based on Zimbra for this exact purpose.
NexentaOS (proper) is almost a complete Ubuntu userland on top of OpenSolaris. Install and hack all you want. NexentaStor is trying to have NAS functionality, focused on multi-tier storage.
I would of course recommend Nexenta (Debianised OpenSolaris) or the storage focused product NexentaStor. Check out Nexenta.com. I have 50TB on it, but you likely just want to throw something less than one:)
Regarding running applications within the scope of a VE (DomU equivalent), yes he is. I extensively use both Virtuozzo and Xen. Each has their strengths. VZ allows efficient use of memory (shared memory across all VMs) as well as disk space, as binaries _can_ be shared with a copy on write file system. You can do a lot of this in Xen, but you can't mount a Xen domU filesystem in Dom0 when a DomU is using it. In OpenVZ, the filesystem is only mounted in the hardware node and exposed through an FS layer (copy-on-write) to the child VZs. Regardless of the state of the VM, you can enter into its state w/ a shell similar to a chroot. But you can fully execute commands from the hardware nodes context into the VZ context. The line separating the two is a process in OpenVZ. In Xen, its a full OS instance with private memory spaces. Its a double edged sword, but it has saved my ass in a few cases with OpenVZ.
Its hard to sit idly by as some statements like this are made. As an individual who has helped out with these systems and further helps maintain processes to keep systems up to date (almost all linux boxen involved use apt-get updates to state up to date pretty religiously), it has generally been the case the successfully attacked systems have come by unique approaches to each machine. Most have been indirect attacks via local root exploits using compromised user names from other institutions. Passwords are generally cracked and not sniffed, with almost all exploits using recently announced local root exploits on systems otherwise protected from direct access to the internet. In a nutshell, these are focused, diligent attempts using a wide arsenal of previously known and unknown attacks (yes, some locally compromised systems were truly patched!) to gain as much resources as possible. It pains me that the people here are apt to paint with such a wide paint brush, when in fact these types of attacks are generally successful whenever there is a keen focus to gain resources and its not your run-of-the-mill script kiddie.
I'll also answer that our redhat-based distros used to use libsafe, but newer 9-based versions have incompabilities with that library (matlab and other standard tools don't work with it, and it hasn't been updated for the new nptl stuff). Also, libsafe doesn't help against the kernel exploits (it didn't help). grsecurity is hard to deploy uniformly, especially when you rely on stock vendor kernels because of other vendor requirements.
I've seen it throughout this thread. I would love OSX, but if it could use my already existing and likely faster x86 hardware. A lot of what is desired, configd, netinfo-like system, directory layout, packaging, etc, is standard between OSX and Darwin, which is native on both PPC and x86. So, the real answer is for those who wish to jump on this bandwagon to adopt darwin-x86 and finish off the product as a x86 desktop OS. You have have OSX (to a certain degree) and x86.. but there is a lot of work left to do! (And GNUStep would aid in filling out the higher level application stuff, or the usual KDE/Gnome argument could ensue)
Speaking of RIAA/MPAA, I was listening to a song today that makes for the best anti-MPAA theme. You may or may not have heard of the song "Open Up" by Leftfield. Its a energetic, beaty song with great lyrics by John Lydon.. "Burn hollywood burn.. Take down tinseltown.. burn down to the ground.." You'll all love it. Its actually one of the better songs I've heard regardless of the lyrics:)
Directory Administrator is a user/group management tool for data stored in LDAP servers. Systems use nss_ldap and pam_ldap to access and authenticate against this information. Open-IT also provides packages for OpenLDAP and PADL software (nss/pam_ldap) to do this securely. You can even enable ACLs in OpenLDAP to limit exposure. Most people in this discussion are interested in user management tools, and don't want to be exposed fully to LDAP and its nomenclature.
As the host of open-it.org, are entire focus is solving this problem. Many people are actively working on integration with ActiveDirectory, and other tie ins, and people loosely associated with Open-IT are working in various projects that help resolve this (Samba-TNG supports ldap backends).
As for management, we now host Directory Administrator,a great GTK front end to user management, I have also created a simply useradd program for creating users in ldap (its called addluser).
We are currently working on a new release of Directory Administrator with a new backend which will allow CLI, GUI, and Web clients to be built on it. Further, if you love WebObjects, Apple just released 5.1, which has a JNDI adaptor, allowing quick Web Apps to be built against LDAP directory servers using Java.
Is the documentation not up to snuff at Open-IT, then help out! We have some basic howtos, and I package pam_ldap, nss_ldap, openldap, and other great things to get you going.
Actually, I think that this is something that could be started for all non-profits. I'd love to start up an effort where non-profits can post their needs for IT help and the greater OpenSource community can help locally (or nationally) different organizations. Sort of a donate your IT expertise. Would be great if one could claim it on your taxes!
It shouldn't just be H4H, it should be everyone, and it will help prove the validity of OpenSource in the business desktop space.
As a former employee of one of these companies, I would just like to concur that this does not reflect on the viability of Linux even as a profitable business. There are many companies based on Linux that are failing, but from my experience, it has more to do with poor management and the money/business focus trumping any technology push within these companies. Linux companies are best served not by large investments (which push the business agenda) but by sound technology, small, nurtured growth, and a focus on the end goal of maturation instead of immediate revenue generation.
Profit is one thing (necessary), but growth for the sake of generating revenues, and making revenues king generally results in turning business stragedies into "Lets charge a premium for this free community-thing" or "Lets do some of the infrastructure in a proprietary tie-in way." You end up killing the true technology that may win in the end and let the business mind-set gravitate back to the standard proprietary ways of doing business. This I feel is why so many Linux co's, who have had "new management" take over, tend to sound hipocritical today and sound oh so old fashioned and counter-revolutionary.
The end result: Don't trust Linux co's to be the flag bearer or to succeed in maturing Linux. It will take further maturation by the OS community, non-greedy/sound business plans, and people focused on the end goal. Its not anti-business! Its just that sound business-building/technology-building tactics are not employed!
Review is correct, but potential of device is good
on
Agenda VR3 Review
·
· Score: 3
I actually signed up as a developer and bought one of the devices. The original boot that came on it sucked hard, but the kernel/root image that I've since flashed to it has made it a passable device.
Would I suggest it to a normal PDA user? Definitely not yet. It needs to have its task switching system fixed, its X optimized or stream-lined, and its startup procedure tailored to end users. However, if you hook up the serial port to your linux box, start up ppp, and then telnet into the device, its amazingly passable as a unix machine. Of course that is not what it's designed for. Most people don't want a 2x speed DEC 3100 workstation:) (thats the processor, memory, and speed specs)
As to the limit on the number of apps: First I noticed that swap wasn't used, nor should it, but a 2.4.x kernel running out of memory without any swap-styled VM pages seems to "fit the bill" for what happens to these devices when you run too many apps. My guess is that some kernel hacking needs to be done to better handle low-memory management. But consider this. I got python on it, and it works, a few threads and all.
End result: It needs a lot of help, but it has enough ooph (66mhz, 16mb flashram, 8mb rom) to be a very reasonable PDA.. it just needs to have its resources re-oriented and one needs to not attempt "quick ports", which are easy, but do not take into account that its such an under-powered linux device that tweaks are a must!
LKCL is also involved in open-it.org's project goals, which hopes to address the ActiveDirectory, Kerberos, and possibly the DDNS components of the equation. However, we'd like to design a better AD, not just be another AD that nips at the heels of MS.
I just scanned some comments and didn't see this yet, but how about a.gnu TLD? This way, most open source projects can get their own domain easily, and companies are less likely to squat on it.
I know.. I know...gnu may be limiting to GPL, etc...oss? Just a few thoughts that sprang to mind
Slashdot Mirror
Well, what's stopping people using NexentaStor (non-free) or NexentaOS (free as in beer/speech)? Better yet, Nexenta is OpenSolaris w/ ZFS, etc, but is an Ubuntu LTS 8.04-based distribution. Its always been the best of both worlds. If you have something using ZFS today, you can export the pool, install Nexenta, and reimport, being back up in minutes.
CalDav is the wave of the future, with most calendaring clients supporting it (but not MS), and many servers commercial and otherwise also supporting it (Zimbra). The real coming out party was the commercial release of both OSX Server 10.5 and the client, which have both ends. But guess what, the server is open source: calendar server can be gotten and put on any platform. If you want something today, Zimbra or OSX Server are there for the taking. RedHat has a Messenging product coming out based on Zimbra for this exact purpose.
NexentaOS (proper) is almost a complete Ubuntu userland on top of OpenSolaris. Install and hack all you want. NexentaStor is trying to have NAS functionality, focused on multi-tier storage.
I would of course recommend Nexenta (Debianised OpenSolaris) or the storage focused product NexentaStor. Check out Nexenta.com. I have 50TB on it, but you likely just want to throw something less than one :)
Regarding running applications within the scope of a VE (DomU equivalent), yes he is. I extensively use both Virtuozzo and Xen. Each has their strengths. VZ allows efficient use of memory (shared memory across all VMs) as well as disk space, as binaries _can_ be shared with a copy on write file system. You can do a lot of this in Xen, but you can't mount a Xen domU filesystem in Dom0 when a DomU is using it. In OpenVZ, the filesystem is only mounted in the hardware node and exposed through an FS layer (copy-on-write) to the child VZs. Regardless of the state of the VM, you can enter into its state w/ a shell similar to a chroot. But you can fully execute commands from the hardware nodes context into the VZ context. The line separating the two is a process in OpenVZ. In Xen, its a full OS instance with private memory spaces. Its a double edged sword, but it has saved my ass in a few cases with OpenVZ.
Its hard to sit idly by as some statements like this are made. As an individual who has helped out with these systems and further helps maintain processes to keep systems up to date (almost all linux boxen involved use apt-get updates to state up to date pretty religiously), it has generally been the case the successfully attacked systems have come by unique approaches to each machine. Most have been indirect attacks via local root exploits using compromised user names from other institutions. Passwords are generally cracked and not sniffed, with almost all exploits using recently announced local root exploits on systems otherwise protected from direct access to the internet. In a nutshell, these are focused, diligent attempts using a wide arsenal of previously known and unknown attacks (yes, some locally compromised systems were truly patched!) to gain as much resources as possible. It pains me that the people here are apt to paint with such a wide paint brush, when in fact these types of attacks are generally successful whenever there is a keen focus to gain resources and its not your run-of-the-mill script kiddie.
I'll also answer that our redhat-based distros used to use libsafe, but newer 9-based versions have incompabilities with that library (matlab and other standard tools don't work with it, and it hasn't been updated for the new nptl stuff). Also, libsafe doesn't help against the kernel exploits (it didn't help). grsecurity is hard to deploy uniformly, especially when you rely on stock vendor kernels because of other vendor requirements.
I've seen it throughout this thread. I would love OSX, but if it could use my already existing and likely faster x86 hardware. A lot of what is desired, configd, netinfo-like system, directory layout, packaging, etc, is standard between OSX and Darwin, which is native on both PPC and x86. So, the real answer is for those who wish to jump on this bandwagon to adopt darwin-x86 and finish off the product as a x86 desktop OS. You have have OSX (to a certain degree) and x86.. but there is a lot of work left to do! (And GNUStep would aid in filling out the higher level application stuff, or the usual KDE/Gnome argument could ensue)
loan word.. loan word..
sheesh!
keiretsu = corportation/firm in japanese
packetto = loan worn (usually in katakana) meaning packet.
ie.. Packet Company in Japanese
Speaking of RIAA/MPAA, I was listening to a song today that makes for the best anti-MPAA theme. You may or may not have heard of the song "Open Up" by Leftfield. Its a energetic, beaty song with great lyrics by John Lydon.. "Burn hollywood burn.. Take down tinseltown.. burn down to the ground.." You'll all love it. Its actually one of the better songs I've heard regardless of the lyrics :)
I better explain this.
Directory Administrator is a user/group management tool for data stored in LDAP servers. Systems use nss_ldap and pam_ldap to access and authenticate against this information. Open-IT also provides packages for OpenLDAP and PADL software (nss/pam_ldap) to do this securely. You can even enable ACLs in OpenLDAP to limit exposure. Most people in this discussion are interested in user management tools, and don't want to be exposed fully to LDAP and its nomenclature.
As the host of open-it.org, are entire focus is solving this problem. Many people are actively working on integration with ActiveDirectory, and other tie ins, and people loosely associated with Open-IT are working in various projects that help resolve this (Samba-TNG supports ldap backends).
As for management, we now host Directory Administrator,a great GTK front end to user management, I have also created a simply useradd program for creating users in ldap (its called addluser).
We are currently working on a new release of Directory Administrator with a new backend which will allow CLI, GUI, and Web clients to be built on it. Further, if you love WebObjects, Apple just released 5.1, which has a JNDI adaptor, allowing quick Web Apps to be built against LDAP directory servers using Java.
Is the documentation not up to snuff at Open-IT, then help out! We have some basic howtos, and I package pam_ldap, nss_ldap, openldap, and other great things to get you going.
Back to work...
Actually, I think that this is something that could be started for all non-profits. I'd love to start up an effort where non-profits can post their needs for IT help and the greater OpenSource community can help locally (or nationally) different organizations. Sort of a donate your IT expertise. Would be great if one could claim it on your taxes!
It shouldn't just be H4H, it should be everyone, and it will help prove the validity of OpenSource in the business desktop space.
As a former employee of one of these companies, I would just like to concur that this does not reflect on the viability of Linux even as a profitable business. There are many companies based on Linux that are failing, but from my experience, it has more to do with poor management and the money/business focus trumping any technology push within these companies. Linux companies are best served not by large investments (which push the business agenda) but by sound technology, small, nurtured growth, and a focus on the end goal of maturation instead of immediate revenue generation.
Profit is one thing (necessary), but growth for the sake of generating revenues, and making revenues king generally results in turning business stragedies into "Lets charge a premium for this free community-thing" or "Lets do some of the infrastructure in a proprietary tie-in way." You end up killing the true technology that may win in the end and let the business mind-set gravitate back to the standard proprietary ways of doing business. This I feel is why so many Linux co's, who have had "new management" take over, tend to sound hipocritical today and sound oh so old fashioned and counter-revolutionary.
The end result: Don't trust Linux co's to be the flag bearer or to succeed in maturing Linux. It will take further maturation by the OS community, non-greedy/sound business plans, and people focused on the end goal. Its not anti-business! Its just that sound business-building/technology-building tactics are not employed!
I actually signed up as a developer and bought one of the devices. The original boot that came on it sucked hard, but the kernel/root image that I've since flashed to it has made it a passable device.
:) (thats the processor, memory, and speed specs)
Would I suggest it to a normal PDA user? Definitely not yet. It needs to have its task switching system fixed, its X optimized or stream-lined, and its startup procedure tailored to end users. However, if you hook up the serial port to your linux box, start up ppp, and then telnet into the device, its amazingly passable as a unix machine. Of course that is not what it's designed for. Most people don't want a 2x speed DEC 3100 workstation
As to the limit on the number of apps: First I noticed that swap wasn't used, nor should it, but a 2.4.x kernel running out of memory without any swap-styled VM pages seems to "fit the bill" for what happens to these devices when you run too many apps. My guess is that some kernel hacking needs to be done to better handle low-memory management. But consider this. I got python on it, and it works, a few threads and all.
End result: It needs a lot of help, but it has enough ooph (66mhz, 16mb flashram, 8mb rom) to be a very reasonable PDA.. it just needs to have its resources re-oriented and one needs to not attempt "quick ports", which are easy, but do not take into account that its such an under-powered linux device that tweaks are a must!
The source code is now available under a commercially restrictive license. Check out the beta.turbolinux.com site.
LKCL is also involved in open-it.org's project goals, which hopes to address the ActiveDirectory, Kerberos, and possibly the DDNS components of the equation. However, we'd like to design a better AD, not just be another AD that nips at the heels of MS.
I just scanned some comments and didn't see this yet, but how about a .gnu TLD? This way, most open source projects can get their own domain easily, and companies are less likely to squat on it.
.gnu may be limiting to GPL, etc.. .oss? Just a few thoughts that sprang to mind
I know.. I know..
I did however get it to finally work with XF4.0.1 and their last set of drivers. OpenSource aside, it does work and kicked ass against my Voodoo3.
TurboLinux already did an Itanium port.. and they are doing an S390..