Want to read Slashdot from your mobile device? Point it at m.slashdot.org and keep reading!

 



Forgot your password?
typodupeerror
For the out-of-band Slashdot experience (mostly headlines), follow us on Twitter, or Facebook. ×

Comment: Re:It's the end of the world as we know it! (Score 1) 290 290

Furthermore, even if they would manage to return the blocks to the pool in a couple of years, it would both be too late and too little and the demand for address space far outpaces the supply that ipv4 can offer.

This. We got 7 billion people - probably closer to 10 before it peaks, and as a minimum I should have one IP address at home, at work and for my cell phone. So 3*10 billion is 30 billion, IPv4 can offer 4 billion. And that's not counting every other odd thing I might want, like remote-controlled alarm/heating/whatever at my cabin or my car, servers of various kind and maybe IoT will become good for something.

Of course they probably could have just done it much, much simpler by making a dotted quad a dotted quint:

1.2.3.4.5

For compatibility each host under 1.2.3.4.x is granted 256 ports IPv4 ports mapped from x*256 to (x+1)*256-1 to a designated "IPv4 compatibility ports" like say the last ports from 65279 to 65535. So 1.2.3.4.1 can either be fully addressed by quint-capable equipment or 1.2.3.4:256-511 that'll be mapped to 1.2.3.4.1:65279-65535. And 1.2.3.4.2 will have 1.2.3.4:512-767 mapped to 1.2.3.4.2:65279-65535 and so on. You could use the same technique to provide a virtual IPv4 interface for legacy software, it thinks it is listening to 1.2.3.4:256 but it's really listening at 1.2.3.4.1:65279 - and any application it tells to connect to 1.2.3.4:256 would work.

That would have led to a gradual 256-times expansion of the address space without any hard switch-offs. But instead they decided to solve everything and now 19 years after the IPv6 standard we're still only barely in motion.

Comment: Re:Modularity (Score 4, Informative) 79 79

The very page you link to says:

Some might argue that there might arise a small problem with shipping 27M ICU libraries. If you don't need ICU (http://site.icu-project.org/) you have to recompile Qt with ./configure -without-icu.

What's ICU?

Here are a few highlights of the services provided by ICU:

Code Page Conversion: Convert text data to or from Unicode and nearly any other character set or encoding. ICU's conversion tables are based on charset data collected by IBM over the course of many decades, and is the most complete available anywhere.

Collation: Compare strings according to the conventions and standards of a particular language, region or country. ICU's collation is based on the Unicode Collation Algorithm plus locale-specific comparison rules from the Common Locale Data Repository, a comprehensive source for this type of data.

Formatting: Format numbers, dates, times and currency amounts according the conventions of a chosen locale. This includes translating month and day names into the selected language, choosing appropriate abbreviations, ordering fields correctly, etc. This data also comes from the Common Locale Data Repository.

Time Calculations: Multiple types of calendars are provided beyond the traditional Gregorian calendar. A thorough set of timezone calculation APIs are provided.

Unicode Support: ICU closely tracks the Unicode standard, providing easy access to all of the many Unicode character properties, Unicode Normalization, Case Folding and other fundamental operations as specified by the Unicode Standard.

Regular Expression: ICU's regular expressions fully support Unicode while providing very competitive performance.

Bidi: support for handling text containing a mixture of left to right (English) and right to left (Arabic or Hebrew) data.

Text Boundaries: Locate the positions of words, sentences, paragraphs within a range of text, or identify locations that would be suitable for line wrapping when displaying the text.

And much more. Refer to the ICU User Guide for details.

Not sure exactly how much Qt functionality you'd lose, but it's an optional dependency.

Comment: Re:No, they just need reliable Linux distros. (Score 4, Insightful) 168 168

Maybe it's okay if systemd and PulseAudio fuck up your single Ubuntu workstation. That's not a luxury that these admins have. They need their Linux systems to work reliably all of the time.

Or maybe it's okay if systemd fucks up all the servers running RHEL 7. After all, nothing important runs on that. So let's check, is Red Hat Inc. tanking and considering backtracking? Hell no, they're growing strong both in revenue and profits in the year that's passed since. So if a $14 billion dollar company can make systemd work for them, it probably can't be that bad. Or if it's bad, well then rip out the bad parts like write a non-binary log because how hard could it be to take the binary messages, printf and log the text in addition to/instead of a blob? Sometimes it sounds like the only two options is to drink the kool-aid or nuke it from orbit.

Comment: Re:linux hard to install and use for desktop users (Score 4, Informative) 168 168

that was always a problem of Linux being reliant on X Windows, and you don't know if the X windows is going to run properly until it's installed. therefore the installer has to be text-based, or so they claim. but it's all BS. the people who are doing the video drivers have a vested interest in discouraging direct use of those video drivers -- they are typically employed in jobs that have to do with either X Windows or something related. they want you to use X, even though X is terribly insecure and generally crappy software.

Not sure if you're stoned or trolling or dropped out of a time vortex from the 90s, but

1) GUI installers have been the norm for desktop oriented distros for years, mostly through live CDs.
2) For most of Linux history there's been zero credible competitors to X
3) Wayland is mainly driven by ex-X developers
4) Wayland will still need drivers to have accelerated graphics

5) Neither application developers nor users usually see X, you write against for example Qt and the toolkit takes care of talking to X. They might hate X, but they hide its quirks pretty well.

Comment: Re:He answered the most boring questions! (Score 2) 168 168

It's the typical FOSS mindset. Since you did something other than what I wanted, all of your work was a waste of time.

I think those wanna-be generals aren't really the community, but those who want to exploit the community to achieve their pet goals. To steal an expression from 4chan: The FOSS community is not your personal army. The opposite is less intuitive, but it also means the community isn't going to stand still just because your pet needs have been met while many others feel theirs haven't. For example I haven't heard much shit about PulseAudio in recent years, though initially it was rather crappy but it did add features that didn't exist before. Maybe in ten years time we'll feel the same about systemd.

Comment: Re:It's the non-engineers. (Score 1) 125 125

If you can't manage pointers and complex sets of data safely, you're unlikely to be able to manage projects and manpopwer and deadlines any better.

Careful, the same would imply that someone who can manage projects, manpower and deadlines can manage pointers and complex sets of data safely. The most fundamental difference is that working with people is that your subordinates have a brain and will let you know when something is obviously wrong, non-nonsensical or impossible. I don't mean they're geniuses but the computer isn't even toilet trained and will poop all over the floor if it can't find the bathroom. It'll go in an infinite loop or write full the disk or flood the network or trash the database with total obliviousness.

Half my job is figuring out every conceivable way the system can crap out, take bad input, return junk or be exploited because the system won't deal with any situation on its own. Project management is a lot more about resolving the daily issues your team is struggling with right now, not chasing corner cases that might one day happen. And the software solution is often just throwing some kind of error, if you're aware you've almost trivially dealt with it.

Management problems are typically "soft issues" that doesn't have definitive causes or solutions. Like today we talked about a new reporting solution that is behind schedule and how the estimates were set and causes they're off, consequences, remaining uncertainty, mitigation strategies, if it's possible to free up existing resources or add resources without running into the mythical man-month and how we plan to deal with our needs just not today but going forward. You're not chasing a bug in code that you can patch and declare fixed. It's a constant re-balancing of competing priorities.

Comment: Re:If you're using GPL code, you have no choice (Score 1) 161 161

Sure, as long as you use some GPL code the requirements apply to the work as a whole. But if you write part A using the GPL license, I can write part B using the BSD license. The GPL license is okay with A+B and if someone wants to use part B in a non-GPL project or replace part A with differently licensed code they can. The point was he doesn't have to use the GPL unless he wants to. He can use a far more permissive "I don't care, use it wherever you want" license for his bits.

Comment: Re:FSF was very non-specific, and probably wrong (Score 2) 161 161

The FSF post didn't say either what terms of the license they thought Apple was violating, nor why they think distributing via the app store is any different than distributing via the post office.

The way copyright law defines distribution it essentially means transmit, like over radio and TV or down a wire. There's a very limited exception carved out for passing along transitory copies unaltered so each node on the Internet isn't liable for everything passing through just the source and potentially the sink. Moving a copy physically around never invokes copyright, which is why Apple is on the hook and the post office not. And Apple's software storing it on the user device leads to vicarious and contributory liability if they violate the reproduction right, since they're both materially contributing and profiting from it.

This is pretty much straight up copyright law, not the FSFs opinion. I haven't read up on exactly what beef they have with the app store's terms, but Apple's activity very clearly falls under copyright law.

Comment: Re:If you're using GPL code, you have no choice (Score 1) 161 161

Oh, how /. has fallen when this is modded up. It must be GPL-compatible, it must not be GPL. The FSF keeps a list of compatible licenses though the general theme is "like GPL or freer", like it doesn't have to be a copyleft license. If he doesn't want to introduce any new license headaches he could just use the modified BSD license which is pretty much as minimal as it gets. Whether it resolves his license problems are another matter, the GPL demands the whole project must be compatible and I'd guess that Apple's code is not. So the lawyer is right it doesn't matter, it's probably a violation either way.

If a 6600 used paper tape instead of core memory, it would use up tape at about 30 miles/second. -- Grishman, Assembly Language Programming

Working...