rarely seeing any usa tv news os shows, i am always surprised how sensationalist they are. as if audience has no emotions or logical thinking of itself and needs to be spoonfed all of it.
lately, we are also getting some tv shows that are similar in presentation, but, fortunately, those are considered crap by most locals.
i fear that soon all of the things on the tv will be like the one seen here - and i'm not talking about the content, but about a way it is presented. imagine that he is talking in such an exaggarated way when at home or on street... eww.
oooh. that file open dialog is not thunderbirds dialog. it is the famous gtk file dialog, the sucky one that gives bad name to all gtk apps. i am cursing whenever i use them in thunderbird or gimp (or very rarely - firefox).
all the radios, tvs and other appliances i have had or seen lose some settings when left too long without electrical supply. for some, that's clock, for some programmed stations.
batteries can be installed in some devices, but i'd guess those are even worse than a constant electricity draw.
what i would really want from dovecot - great shared folders support (last i tried it was quite messy). another thing - mail filters (that 'sieve' or something) - but ones i can edit from withing the gui of my mailclient (be that thunderbird, kmail or whatever). i haven't heard of something like that being possible yet.
i am using pop3, but i could easily use imap. mail accessibility is not the main problem when considering switching, applications themselves are.
for example, i check out kmail now and then, and consider switching from thunderbird. even though it has several better features, there are things that are very nice to have and i am used to - that quick filter at the top, smaller header area (especially with headercollapse plugin) etc.
email being my primary communications medium, being able to use it efficiently is very important to me. i really hope kmail will become good enough for me - last i heard, they improved ways to view basic headers. also, i hope that kde4 push will bring more developers to it - i was reading that lack of developers is one of the biggest problems kdepim suite is facing.
And somewhere in the middle is the guy who wants performance, hates binaries, and has to choose between his technology-based morality and his desire to make use of his fancy new hardware.
hey. sounds like me;) but to be more precise, i don't hate binaries, i hate problems that come with closed source software - which is mostly drivers these days.
i am using nvidia driver on my box, but a complete opensource driver would be very nice. actually, i wouldn't have any problems moving to ati (that i dislike and avoid a lot with now) if they released an opensource driver.
problems with proprietary drivers include separate upgrades of kernel/driver (can lead to unusable xorg), no support for older cards (nvidia recently dropped support for one of my oldest cards, but the last working version has buggy headers...), worse quality in some cases (check out supending problems)...
first, according to that article, no release has happened yet - and the exact terms are not specified.
second, a ms spokeperson confirms the basic argument again : "Today's move was not required by the European Commission, but it seeks to address concerns expressed by the EC"
The same article noted that often the documentation for such things often is basically opening up your code.
i can't agree with that. i read that as microsoft is attempting to keep that information secret, but implementing it in opensource apps allows others to find it out from the source code of these opensource apps. and i can't find in the article such a claim, anyway.
actual implementation (that is, the code) can - and will - differ.
In order to network using the CIFS protocol for interoperability, Microsoft ended up having to release the full code for CIFS.
i haven't followed this closely enough, could you point out the actual release ? i'm curious whether that really is "full code" and what are the conditions. now, if microsoft is not capable of documenting the protocol, that tells something about their documentation skills or the protocol itself... release of source code has never been a requirement by european union.
A ruling of the Commission from March 2004, which was confirmed by the Court of First instance in December 2004, obliges Microsoft to disclose "complete and accurate interface documentation which would allow non-Microsoft work group servers to achieve full interoperability with Windows PCs and servers".
reading further, it just confirms the information i had before - microsoft is just trying to avoid documenting their interfaces/protocols:
Microsoft could provide these competitors with protocol information under terms that require the protocols themselves to be treated as confidential.
again, no mentioning of a request to open source for microsoft products, only the requirement to properly document things for the sake of interoperability. ps. both emphasis mine:)
i remember reading that once xorg was split up (in the modular stuff at version 7), they will be working on threading things out more. like, mouse control separated and being given higher priority to avoid those cases when you click on something accidentally because mouse stuttered a bit... i hope i can say 'we all hate that':)
i would guess this could expand in other things getting separated, thus allowing finer control over priorities. it's a good thing it got forked:)
thanks for the link. i believe two last capitalized letters (ine the url) are the most informative;)
it's a pr statement to spin it all even further. again, eu definitely _did not_ request releasing of source code. to quote that article, "The Windows source code is the ultimate documentation of Windows Server technologies."
this is like "we can't document shit, and we see a chance to do a pr spin as if this was requested".
also, notice article heading : "Microsoft Goes Beyond EU Decision"
how the hell do they imagine to measure _time spent on a page_ in a meaningful way ?
i constantly open several pages, leaving one to load in the background or just as reminders. some pages stay open for days (or even months !).
sometimes i click, read, close - sometimes (often) i click, read, go to make a tea (like now...), come back, click/read some more, go to the toilet, return to continue browsing...
i have myself attempted to measure time spent on pages, but i have always said that my results are far from definitive, with the possible mistake being at least twice. how could anybody imagine using something that unreliable for a serious task ?
could we please stop this ? unless it happened, like, today, _nobody_ (in europe) is forcing microsoft to release source code. this is being repeated for years, and debunked every time - so by now i don't understand how could anybody actually say that without trolling.
what is requested, is documentation about protocols for interoperability. documenting something is far from releasing the source for it.
good point. given that this project is still in development, they probably have a good chance to improve this. on the other hand, most consumers seem to grasp the concept of ibm/lenovo/dell/hp hardware and microsoft/? software - so having a short and clear explanation in a couple of sentences as the second information snippet on the page might help.
you seem to be confused. openmoko is the software stack, the platform. neo is the actual physical device, of which there can (and hopefully will) be many, many more.
OpenMoko is an Open Source project to create the world's first free mobile phone operating system.... The long term goal is that phone software won't be tied to a phone. You can install any OpenMoko software over the whole range of phones, and if you upgrade your phone, you don't lose the software. Bugs fixed on one phone are fixed on all.
Currently it is not suitable for users. The state of the software at the moment is pre-alpha. If you order a Neo1973, DO NOT expect to be able to use it as an everyday phone for several months.
The Neo1973 from FIC is the first of many phones that OpenMoko will run on.
(i did not cut out the part about "Currently it is not suitable for users", as i believe that's important;) )
BTW you can't restrict the format of the original. Consider an email from a corporate bidding for a govt contract, with attachments.
as an archive, probably not. but as the government, that should be a requirement for any information exchange to be only in completely documented, patent unencumbered and whatnot document formats - well, the correct definition of open document formats would help here.
of course, it's not a thing you do on a single day, but it should have been started a long time ago, to allow transitioning to these formats.
currenlty kde conference, akademy is in progress. of course, trolltech is present there, and from the reports, they are interested in being more open and collaborative with opensource developers:
The Trolls realize they need to cooperate more, and thus are trying to pursue the common interests. By introducing developer blogs, releasing early snapshots and having a community manager, they hope to increase communication with the community and encourage contributions. Until now, KDE developers often worked around limitations in Qt, but in the future they could send patches.
Linux's GUI development environment favors free at the one end, and deep-pocket folk at the other, while locking out the small guys. Seems... I dunno, sort of un-linuxy.
first, this is only one toolkit. yeah, probably the best, but not the only one.
second, what's so un-linuxy ? would gpl-only be better for you, like linux (the kernel) itself is ?
weird. are you sure you tried a recent version of slackware (like 11.0) ? if so, did you try any other kernels from the bootdisk besides "bare.i" ?
scsi, raid and other controllers like that are supported by kernels scsi, scsi2, scsi3 and raid.
second, what about 2gb ? i'm handling backups on a server with single file sometimes exceeding several hundreds of gb. i would notice if files could go only up to 2 gb.
compiling your own packages also got a little bit harder with removal of checkinstall for slack 12. it didn't work quite well with recent coreutils.
hopefully, checkinstall will get updated and included back, but in case somebody just wants it to get working fast, replacing 'chmod' from slack 11 made it so much happier.
i agree that gui might be important in some cases, but i am holding back until xen will not require patches to vanilla kernel.
what additionally seems weird, the development isn't as open as one would hope for such a popular project. getting some development snapshot ? any links from the main page ? nooo. in the end i managed to grab a copy from versioning system they used, but it was several versions behind vanilla kernels (that had some nfs patches that i needed), and i didn't feel like dissecting the patches or using older kernels only to play around with xen.
getting in the mainstream kernel would mean closer development cycle to the kernel itself. which is usually a good idea for anything dealing with the kernel.
Slashdot Mirror
rarely seeing any usa tv news os shows, i am always surprised how sensationalist they are. as if audience has no emotions or logical thinking of itself and needs to be spoonfed all of it.
lately, we are also getting some tv shows that are similar in presentation, but, fortunately, those are considered crap by most locals.
i fear that soon all of the things on the tv will be like the one seen here - and i'm not talking about the content, but about a way it is presented. imagine that he is talking in such an exaggarated way when at home or on street... eww.
oooh. that file open dialog is not thunderbirds dialog. it is the famous gtk file dialog, the sucky one that gives bad name to all gtk apps.
i am cursing whenever i use them in thunderbird or gimp (or very rarely - firefox).
when i was researching which firmware to use, i found this : http://xwrt.blogspot.com/2007/02/dd-wrt-continues- to-exploit-free-open.html
that's some weird math
all the radios, tvs and other appliances i have had or seen lose some settings when left too long without electrical supply.
for some, that's clock, for some programmed stations.
batteries can be installed in some devices, but i'd guess those are even worse than a constant electricity draw.
what i would really want from dovecot - great shared folders support (last i tried it was quite messy).
another thing - mail filters (that 'sieve' or something) - but ones i can edit from withing the gui of my mailclient (be that thunderbird, kmail or whatever). i haven't heard of something like that being possible yet.
i am using pop3, but i could easily use imap. mail accessibility is not the main problem when considering switching, applications themselves are.
for example, i check out kmail now and then, and consider switching from thunderbird.
even though it has several better features, there are things that are very nice to have and i am used to - that quick filter at the top, smaller header area (especially with headercollapse plugin) etc.
email being my primary communications medium, being able to use it efficiently is very important to me.
i really hope kmail will become good enough for me - last i heard, they improved ways to view basic headers.
also, i hope that kde4 push will bring more developers to it - i was reading that lack of developers is one of the biggest problems kdepim suite is facing.
hey. sounds like me
but to be more precise, i don't hate binaries, i hate problems that come with closed source software - which is mostly drivers these days.
i am using nvidia driver on my box, but a complete opensource driver would be very nice. actually, i wouldn't have any problems moving to ati (that i dislike and avoid a lot with now) if they released an opensource driver.
problems with proprietary drivers include separate upgrades of kernel/driver (can lead to unusable xorg), no support for older cards (nvidia recently dropped support for one of my oldest cards, but the last working version has buggy headers...), worse quality in some cases (check out supending problems)...
thanks for the link, again :)
a few things, though...
first, according to that article, no release has happened yet - and the exact terms are not specified.
second, a ms spokeperson confirms the basic argument again : "Today's move was not required by the European Commission, but it seeks to address concerns expressed by the EC"
i can't agree with that. i read that as microsoft is attempting to keep that information secret, but implementing it in opensource apps allows others to find it out from the source code of these opensource apps. and i can't find in the article such a claim, anyway.
actual implementation (that is, the code) can - and will - differ.
i haven't followed this closely enough, could you point out the actual release ? i'm curious whether that really is "full code" and what are the conditions.
now, if microsoft is not capable of documenting the protocol, that tells something about their documentation skills or the protocol itself...
release of source code has never been a requirement by european union.
reading further, it just confirms the information i had before - microsoft is just trying to avoid documenting their interfaces/protocols
again, no mentioning of a request to open source for microsoft products, only the requirement to properly document things for the sake of interoperability.
ps. both emphasis mine
could you provide a link to such requests ?
i haven't seen a request by eu to release "portions", "all" or any source coude so far.
i remember reading that once xorg was split up (in the modular stuff at version 7), they will be working on threading things out more. like, mouse control separated and being given higher priority to avoid those cases when you click on something accidentally because mouse stuttered a bit... :)
:)
i hope i can say 'we all hate that'
i would guess this could expand in other things getting separated, thus allowing finer control over priorities. it's a good thing it got forked
thanks for the link. i believe two last capitalized letters (ine the url) are the most informative ;)
it's a pr statement to spin it all even further. again, eu definitely _did not_ request releasing of source code. to quote that article, "The Windows source code is the ultimate documentation of Windows Server technologies."
this is like "we can't document shit, and we see a chance to do a pr spin as if this was requested".
also, notice article heading : "Microsoft Goes Beyond EU Decision"
disclaimer : i'm lazy.
how the hell do they imagine to measure _time spent on a page_ in a meaningful way ?
i constantly open several pages, leaving one to load in the background or just as reminders. some pages stay open for days (or even months !).
sometimes i click, read, close - sometimes (often) i click, read, go to make a tea (like now...), come back, click/read some more, go to the toilet, return to continue browsing...
i have myself attempted to measure time spent on pages, but i have always said that my results are far from definitive, with the possible mistake being at least twice. how could anybody imagine using something that unreliable for a serious task ?
could we please stop this ? unless it happened, like, today, _nobody_ (in europe) is forcing microsoft to release source code. this is being repeated for years, and debunked every time - so by now i don't understand how could anybody actually say that without trolling.
what is requested, is documentation about protocols for interoperability. documenting something is far from releasing the source for it.
good point. given that this project is still in development, they probably have a good chance to improve this.
on the other hand, most consumers seem to grasp the concept of ibm/lenovo/dell/hp hardware and microsoft/? software - so having a short and clear explanation in a couple of sentences as the second information snippet on the page might help.
you seem to be confused. openmoko is the software stack, the platform.
neo is the actual physical device, of which there can (and hopefully will) be many, many more.
http://wiki.openmoko.org/wiki/Main_Page
(i did not cut out the part about "Currently it is not suitable for users", as i believe that's important
as an archive, probably not. but as the government, that should be a requirement for any information exchange to be only in completely documented, patent unencumbered and whatnot document formats - well, the correct definition of open document formats would help here.
of course, it's not a thing you do on a single day, but it should have been started a long time ago, to allow transitioning to these formats.
of course, trolltech is present there, and from the reports, they are interested in being more open and collaborative with opensource developers
http://dot.kde.org/1183385741/
i guess they might be interested in hearing what problems/regressions you are facing.
first, this is only one toolkit. yeah, probably the best, but not the only one.
second, what's so un-linuxy ? would gpl-only be better for you, like linux (the kernel) itself is ?
weird.
are you sure you tried a recent version of slackware (like 11.0) ?
if so, did you try any other kernels from the bootdisk besides "bare.i" ?
scsi, raid and other controllers like that are supported by kernels scsi, scsi2, scsi3 and raid.
second, what about 2gb ? i'm handling backups on a server with single file sometimes exceeding several hundreds of gb. i would notice if files could go only up to 2 gb.
compiling your own packages also got a little bit harder with removal of checkinstall for slack 12.
:)
it didn't work quite well with recent coreutils.
hopefully, checkinstall will get updated and included back, but in case somebody just wants it to get working fast, replacing 'chmod' from slack 11 made it so much happier.
changelog recommended monitoring http://asic-linux.com.mx/~izto/checkinstall/, so that's probably something i'll do for some time
i agree that gui might be important in some cases, but i am holding back until xen will not require patches to vanilla kernel.
what additionally seems weird, the development isn't as open as one would hope for such a popular project.
getting some development snapshot ? any links from the main page ? nooo.
in the end i managed to grab a copy from versioning system they used, but it was several versions behind vanilla kernels (that had some nfs patches that i needed), and i didn't feel like dissecting the patches or using older kernels only to play around with xen.
getting in the mainstream kernel would mean closer development cycle to the kernel itself. which is usually a good idea for anything dealing with the kernel.