du = you (singular) dere = you (plural) deg = yourself
How about just saying "yous" for plural and "you" for singular? "How are yous?" (How are you all?)
Norwegian has no "the", just a postfix on nouns:
"mann" = man "mannen" = the man "menn" = men "mennene" = the men
There are also genders; masc., neut. and fem, as well as weak and strong nouns. The above is a weak masculine noun.
Neuter:
"hus" = house "huset" = the house "hus" = houses "husene" = the houses
Feminine:
"katt" = cat "katta" = the cat "katter" = cats "kattene" = the cats
The is also no difference between 'is' and 'are'. Technically, in English, if things were logical, you'd say "How is you?" in singular and "How are you?" in plural. Because that isn't consistant, I don't see the point of keeping that difference. In Norwegian it's always "er".
And why do always voice synthesizers sound weird with some wovels? Is it because the guys who make speech synthesizers doesn't know that although there isn't supposed to be a difference between single and double consonants in English, there actually is?
The word "shit" sounds very different from "sheet". In Norwegian, a repeated consonant means a short vowel. It would be "shitt" and "shit".
English spelling is very twisted indeed. If I were to write the paragraph about speech synthesizers in a language that resembles actual pronounciation, I think it would look like this:
"End oai du olveis vois synntesaisers saond oirrd oitt summ oaoells? Iss itt bikkos th gais hu meik spitsh sinntesaisers dossent nao that altthao ther issnt suppaost tu bi a diffrens bittoin sinngl and dubbel connsonnants inn Innglissh, therr ectshully iss?"
I enjoy playing around with what-ifs like these.;)
In general, I can agree about annoying internal mechanisms overwriting your configuration files... In Debian's case, well, the tools it provides for configuration are rather good. In some cases, they just respectfully modify what you did, or add to it. In the places where they locked a file in to a configuration tool, they've also made sure you can either disable it gracefully, or made sure that it isn't nessecary to.
Of course. But the availability differs between distributions. And Slackware doesn't care much for dependencies.
I've heard much negative talk of.rpm. I've hardly heard anything about bad about.deb. Everyone seems to recommend it wherever I look. dpkg/apt seems to receive a lot of praise.
Though RedHat seems to be one of few distributions for which packages are widely available, Debian feels less commercial to me, and it allows me to customize it without bypassing much of any built-in system mechanisms.
With Debian, I don't have to compile at all. No matter how trivial compilation is, it's still a process that lasts for a while. If you look at my initial parent post, I've talked about the different issues.
Although I see lots of little warning messages when I run my precompiled MPlayer binary, it still seems to work just as my customized MPlayer compiles used to do, down to having compiled-in support for fonts, win32 codecs, skins,..., etc.
When you need to enable things with compile switches, that is IMO not better than having something hard-coded. Letting macros (#define, #ifdef,...) save your day doesn't make a truely modular design. It's just a bad monolithic emulation.
Unless you keep tedious notes of all significant and insignificant libraries you hurriedly installed to get a source compiled, then you don't know exactly what's installed on your system. Wether you think this is amateurish or foolish is besides the point. The way in which Linux shares a small set of directories for files of various purposes (bin, lib, man, etc) makes it impossible to see exactly what file belongs to what application. Package managers are a blessing in this context. They keep those 'tedious notes' for you, and I think it's only reasonable that a modern computer OS does so.
If by 'packages installed as root' you mean daemons running as root: I avoid that as best as I can.
Some of you may like to compile from source. I think it's tedious, especially when some pieces of software I've attempted to compile want me to spend hours compiling 10 other libraries first. It takes longer to download the source. It might not compile, whereas Debian packages work reliably. Compiling programs is about the most boring task I know of. You just sit there and wait. And I personally don't reap advantages from compiling from source. Binaries are perfectly dandy.
Okay. Fine. But that sounds much more time consuming than just using apt, where the vast majority of prepacked software packages are are kept up to date, in Debian's repositories or someone else's.
That's all nice... *if* you're using Slackware packages all the way. The fundamental problem doesn't really lie in Slackware's package management. It even has an 'apt' now, named 'slackpkg'. The problem for me lies in the poor availability of packages for Slackware compared to other distributions like RedHat and Debian.
I've been a Slackware user since the mid-to-late 90's and I would not trade it for anything else. I tried Debian once, maybe twice. Didn't like it. dselect and tasksel were horrible... Then someone on Undernet #Linux said "Don't use dselect, then.:)" and a lightbulb switched on... I hadn't realized that the base system is all you need to get going. You can completely customize the thing after doing that. I was amazed, it was the distribution I had been dreaming about. It's similar enough to Slackware to satisfy my geek heart but it makes cleanups so much simpler... Actually, they make them possible at all. It's damn impossible to clean up anything in Slackware unless you use it's package system, for which almost no 3rd party packages are available.
When I switched to Debian recently, I decided on a nazi regime for software installation. I said to myself "NEVER install anything from source" and hoped I would be able to survive on.deb's and apt alone... and it worked.
My Slackware server just got cracked. I caught the cracker red-handed and threw him out. It's too much work to keep packages updated on a Slackware box where things are compiled from source and you hardly know what you have installed. I'm going to install Debian on it as soon as I can.
On that point: The server is several thousand miles away and I don't want to bother the dude at the colocation facility with the re-install. Can I somehow install Debian on that box via SSH?
This is a bit of a stupid question, and it doesn't really belong in this discussion, but is there any way to send a private message to a Slashdot user?
In Norway, we use mil.no. For communes (administrative regions of Norway), we have the kommune.no tree. For high schools we have vgs.no (Videregående Skole). There are also regional domains for each province/county, and priv.no for individuals, but I never see anyone use those.
Agh! Moderators: It was a joke! I was refering to the window environments and not software for them! It was a joke about how they are both horrendously bloated.
My Winamp suffers from the same thing. 2.9 was nice. 5 is back to normal visually, but they need to get that damned thing to start immediately instead of taking umpteen seconds to do the job.
I must've been mistaken, then. I'm 99% positive I read otherwise from a different source. My point still applies, though. I'd be hard pressed to say eBay is an unserious company.
Slashdot Mirror
That sounds self-contradictive.
"Intel are a big corporation."
How can it be "are" if it is "a corporation"?
The criminals you see in crime shows on TV are the sucky ones. The smart criminals don't get caught, or illude the authorities for 20-30 years.
UNDER the wall? Nobody would be able to read it! :O
In Norwegian, we have:
;)
du = you (singular)
dere = you (plural)
deg = yourself
How about just saying "yous" for plural and "you" for singular? "How are yous?" (How are you all?)
Norwegian has no "the", just a postfix on nouns:
"mann" = man
"mannen" = the man
"menn" = men
"mennene" = the men
There are also genders; masc., neut. and fem, as well as weak and strong nouns. The above is a weak masculine noun.
Neuter:
"hus" = house
"huset" = the house
"hus" = houses
"husene" = the houses
Feminine:
"katt" = cat
"katta" = the cat
"katter" = cats
"kattene" = the cats
The is also no difference between 'is' and 'are'. Technically, in English, if things were logical, you'd say "How is you?" in singular and "How are you?" in plural. Because that isn't consistant, I don't see the point of keeping that difference. In Norwegian it's always "er".
And why do always voice synthesizers sound weird with some wovels? Is it because the guys who make speech synthesizers doesn't know that although there isn't supposed to be a difference between single and double consonants in English, there actually is?
The word "shit" sounds very different from "sheet". In Norwegian, a repeated consonant means a short vowel. It would be "shitt" and "shit".
English spelling is very twisted indeed. If I were to write the paragraph about speech synthesizers in a language that resembles actual pronounciation, I think it would look like this:
"End oai du olveis vois synntesaisers saond oirrd oitt summ oaoells? Iss itt bikkos th gais hu meik spitsh sinntesaisers dossent nao that altthao ther issnt suppaost tu bi a diffrens bittoin sinngl and dubbel connsonnants inn Innglissh, therr ectshully iss?"
I enjoy playing around with what-ifs like these.
In general, I can agree about annoying internal mechanisms overwriting your configuration files... In Debian's case, well, the tools it provides for configuration are rather good. In some cases, they just respectfully modify what you did, or add to it. In the places where they locked a file in to a configuration tool, they've also made sure you can either disable it gracefully, or made sure that it isn't nessecary to.
Of course. But the availability differs between distributions. And Slackware doesn't care much for dependencies. I've heard much negative talk of .rpm. I've hardly heard anything about bad about .deb. Everyone seems to recommend it wherever I look. dpkg/apt seems to receive a lot of praise.
Though RedHat seems to be one of few distributions for which packages are widely available, Debian feels less commercial to me, and it allows me to customize it without bypassing much of any built-in system mechanisms.
With Debian, I don't have to compile at all. No matter how trivial compilation is, it's still a process that lasts for a while. If you look at my initial parent post, I've talked about the different issues.
Although I see lots of little warning messages when I run my precompiled MPlayer binary, it still seems to work just as my customized MPlayer compiles used to do, down to having compiled-in support for fonts, win32 codecs, skins, ..., etc.
When you need to enable things with compile switches, that is IMO not better than having something hard-coded. Letting macros (#define, #ifdef, ...) save your day doesn't make a truely modular design. It's just a bad monolithic emulation.
Okei. Skulle du ha lyst å ta en prat, kan du jeg jo kontaktes på Gmail-kontoen min (vises headeren min).
Unless you keep tedious notes of all significant and insignificant libraries you hurriedly installed to get a source compiled, then you don't know exactly what's installed on your system. Wether you think this is amateurish or foolish is besides the point. The way in which Linux shares a small set of directories for files of various purposes (bin, lib, man, etc) makes it impossible to see exactly what file belongs to what application. Package managers are a blessing in this context. They keep those 'tedious notes' for you, and I think it's only reasonable that a modern computer OS does so. If by 'packages installed as root' you mean daemons running as root: I avoid that as best as I can.
Some of you may like to compile from source. I think it's tedious, especially when some pieces of software I've attempted to compile want me to spend hours compiling 10 other libraries first. It takes longer to download the source. It might not compile, whereas Debian packages work reliably. Compiling programs is about the most boring task I know of. You just sit there and wait. And I personally don't reap advantages from compiling from source. Binaries are perfectly dandy.
Okay. Fine. But that sounds much more time consuming than just using apt, where the vast majority of prepacked software packages are are kept up to date, in Debian's repositories or someone else's.
That's all nice... *if* you're using Slackware packages all the way. The fundamental problem doesn't really lie in Slackware's package management. It even has an 'apt' now, named 'slackpkg'. The problem for me lies in the poor availability of packages for Slackware compared to other distributions like RedHat and Debian.
I've been a Slackware user since the mid-to-late 90's and I would not trade it for anything else. I tried Debian once, maybe twice. Didn't like it. dselect and tasksel were horrible... Then someone on Undernet #Linux said "Don't use dselect, then. :)" and a lightbulb switched on... I hadn't realized that the base system is all you need to get going. You can completely customize the thing after doing that. I was amazed, it was the distribution I had been dreaming about. It's similar enough to Slackware to satisfy my geek heart but it makes cleanups so much simpler... Actually, they make them possible at all. It's damn impossible to clean up anything in Slackware unless you use it's package system, for which almost no 3rd party packages are available.
When I switched to Debian recently, I decided on a nazi regime for software installation. I said to myself "NEVER install anything from source" and hoped I would be able to survive on .deb's and apt alone... and it worked.
My Slackware server just got cracked. I caught the cracker red-handed and threw him out. It's too much work to keep packages updated on a Slackware box where things are compiled from source and you hardly know what you have installed. I'm going to install Debian on it as soon as I can.
On that point: The server is several thousand miles away and I don't want to bother the dude at the colocation facility with the re-install. Can I somehow install Debian on that box via SSH?
This is a bit of a stupid question, and it doesn't really belong in this discussion, but is there any way to send a private message to a Slashdot user?
I've never seen an ad where they claim they are the internet?
At this very moment, I love Norway. If someone started doing ads like that over here, I'm going to arrange a stake burning.
In Norway, we use mil.no. For communes (administrative regions of Norway), we have the kommune.no tree. For high schools we have vgs.no (Videregående Skole). There are also regional domains for each province/county, and priv.no for individuals, but I never see anyone use those.
Agh! Moderators: It was a joke! I was refering to the window environments and not software for them! It was a joke about how they are both horrendously bloated.
At no point did I disagree. I was merely trying to clarify and be informative.
I tend to use this system: k = kilo M = mega G = giga b = bit B = byte I.e. kb = kilobit, kB = kilobyte, etc.
Sounds like one scary goldfish... Are you sure you didn't mean blowfish?
You mean like those pesky "KDE" and "GNOME" programs?
My Winamp suffers from the same thing. 2.9 was nice. 5 is back to normal visually, but they need to get that damned thing to start immediately instead of taking umpteen seconds to do the job.
I must've been mistaken, then. I'm 99% positive I read otherwise from a different source. My point still applies, though. I'd be hard pressed to say eBay is an unserious company.