No, I'm not confused, and as said, I understand how what you want is desirable if all you've ever used is Linux, which seems to be the case, and hence it's probably futile to try and explain why what you're proposing is/not/ generally desirable.
If I need to configure something, I don't need to think through "ok, where did this package install its config?/usr/config?/opt/conf?/svr//conf?"
I see how what you say seems desirable from a Linux POV, where the install prefix even for 3rd party packages is just "/".
Other OS approach the matter more carefully, providing a split between the base system (pfx/), a prefix where installed packages go (e.g./usr/pkg) and a prefix for the user to use for their own purposes (trypically/usr/local). A good thing, IMO.
There was no "Split" between Linux and BSD. BSD (Berkeley Software Distribution) was around first. It was UNIX without much of the Bell Labs stuff. So Free UNIX. Linux is NOT UNIX but UNIX like.
If I may delve into the past, this comes close to the GUI-Command line wars in that the command liners knew they hated a Desktop display and mouse, but couldn't quite articulate why.
Well you seem to simply haven't paid attention, then. The obvious and still valid argument in favor of a command line is the ability to automate stuff, which you don't get in a GUI, unless baked into the programs thenselves (and even then it's nowhere near as flexible).
If you install software and it does not store the system wide/global configs in $PREFIX/etc then that software was written by no talent idiots that need to be beaten with a sack of doorknobs.
FTFY. People who assume or hardcode the install prefix to be/, should line up right with the "no talent idiots" to collect their beating.
You seem to be misunderstanding what a social life is. Hint: it has nothing to do with being able to mount camera storage. Ironically, since you're using Linux, you likely don't have a social life anyway so how exactly is it a trade-off for you?
Have you installed Windows recently? OK, I haven't since Windows 7, myself, but that install just asked me for timezone, language, and maybe which keyboard I was using (but the default was right), and the rest was just "next, next, next" and that was it, it ran for a while and rebooted 2x and was done with no further input.
So it's basically like the Debian installer, except for the part where you need two reboots (wth, seriously?). Not for nothing they say that a chicken could install Debian, provided there's sufficient grain on the enter key...
Do you by any chance have a more detailed write-up of how you configured your system anywhere?
No, I haven't. I can however help you out with specifics, or bits of configuration to get that going, if you care to drop into #fstd on Freenode, say.
read and send from multiple devices while keeping everything centrally for admin/back-up/security purposes. However, that would be a side project that needs to be done in my spare time
Mhm, making the mail accessible to multiple devices would probably involve additionally running an IMAP server (e.g. dovecot). My setup doesn't currently implement that, for remote mail checking I ssh/putty home
[...] or so comprehensive and detailed that I find them overwhelming.
Fortunately those often come with a reasonably default configuration.
I can't stand web-based mail readers, so, yes, I do use a PC email client, and I think many others do for the same reason. Furthermore, I couldn't stand to have to actively check for new email, so for me it's:
1. postfix with sender-dependent relay hosts and -authentication
2. fetchmail to periodically poll all email addresses i have for new mail, handing it the local postfix for delivery, which then "delivers" it to
3. procmail in order to sort the incoming mail into various maildirs, triggering
4. a script that watches ~/.maildir/new for new files, and if positive, puts a 'new mail' label into my WM's status bar, which causes me to fire up
5. mutt to read the mail. it doesn't even need to be compiled with IMAP/POP3 support this way, which is neat.
Oh little mentally challenged AC, please use your little peabrain to realize that it wasn't me who held that "not standing behind their words" speech. I was just pointing out the irony of AC saying that. That being said, it's pretty easy to depseudonymize me, anyway. Yawn.
Sorry to break it to you, but perl has use <version>; for a long time now.
That the Python people went about the version bump in about the most ham-fisted way imaginable does not mean that this would somehow be the case for all languages now.
Slashdot Mirror
Oh noes. So we're all gonna die, like, twice!
Yes, because people who care about that generally release their source code.
If it works all the time, what does he need upgrades and replacements for?
If I need to configure something, I don't need to think through "ok, where did this package install its config? /usr/config? /opt/conf? /svr//conf?"
Please use better straw-men.
An ocean of new opportunities for rooted machines...
[...] packages is just "/usr".
FTFM
I see how what you say seems desirable from a Linux POV, where the install prefix even for 3rd party packages is just "/". /), a prefix where installed packages go (e.g. /usr/pkg) and a prefix for the user to use for their own purposes (trypically /usr/local). A good thing, IMO.
Other OS approach the matter more carefully, providing a split between the base system (pfx
a lot of people are exposing their ignorance of how networking works.
The OSI model puts TCP at layer 4 (session), not layer 3 (addressing, AKA IP).
Oh the irony.
In any case you're making the massive leap to assume that TCP would be used for low latency audio;
I'm not AC, but, no. It's you who're making the massive leap to assuming this branch of the discussion still had anything to do with audio.
There was no "Split" between Linux and BSD. BSD (Berkeley Software Distribution) was around first. It was UNIX without much of the Bell Labs stuff. So Free UNIX. Linux is NOT UNIX but UNIX like.
FTFY...
If I may delve into the past, this comes close to the GUI-Command line wars in that the command liners knew they hated a Desktop display and mouse, but couldn't quite articulate why.
Well you seem to simply haven't paid attention, then. The obvious and still valid argument in favor of a command line is the ability to automate stuff, which you don't get in a GUI, unless baked into the programs thenselves (and even then it's nowhere near as flexible).
If you install software and it does not store the system wide/global configs in $PREFIX/etc then that software was written by no talent idiots that need to be beaten with a sack of doorknobs.
FTFY. People who assume or hardcode the install prefix to be /, should line up right with the "no talent idiots" to collect their beating.
You seem to be misunderstanding what a social life is.
Hint: it has nothing to do with being able to mount camera storage. Ironically, since you're using Linux, you likely don't have a social life anyway so how exactly is it a trade-off for you?
That's totally something the end user should be doing in a mature product!
In a mature product? Have you ever looked at the icon VLC uses?
Where's the problem? It's not strictly the switch's job to do that error checking, in fact, that would be a fairly odd thing to have.
Have you installed Windows recently? OK, I haven't since Windows 7, myself, but that install just asked me for timezone, language, and maybe which keyboard I was using (but the default was right), and the rest was just "next, next, next" and that was it, it ran for a while and rebooted 2x and was done with no further input.
So it's basically like the Debian installer, except for the part where you need two reboots (wth, seriously?).
Not for nothing they say that a chicken could install Debian, provided there's sufficient grain on the enter key...
Do you by any chance have a more detailed write-up of how you configured your system anywhere?
No, I haven't. I can however help you out with specifics, or bits of configuration to get that going, if you care to drop into #fstd on Freenode, say.
read and send from multiple devices while keeping everything centrally for admin/back-up/security purposes. However, that would be a side project that needs to be done in my spare time
Mhm, making the mail accessible to multiple devices would probably involve additionally running an IMAP server (e.g. dovecot). My setup doesn't currently implement that, for remote mail checking I ssh/putty home
[...] or so comprehensive and detailed that I find them overwhelming.
Fortunately those often come with a reasonably default configuration.
I will be removing the antenna from it
You're not allowed to damage foreign property.
I can't stand web-based mail readers, so, yes, I do use a PC email client, and I think many others do for the same reason.
Furthermore, I couldn't stand to have to actively check for new email, so for me it's:
1. postfix with sender-dependent relay hosts and -authentication
2. fetchmail to periodically poll all email addresses i have for new mail, handing it the local postfix for delivery, which then "delivers" it to
3. procmail in order to sort the incoming mail into various maildirs, triggering
4. a script that watches ~/.maildir/new for new files, and if positive, puts a 'new mail' label into my WM's status bar, which causes me to fire up
5. mutt to read the mail. it doesn't even need to be compiled with IMAP/POP3 support this way, which is neat.
Oh little mentally challenged AC, please use your little peabrain to realize that it wasn't me who held that "not standing behind their words" speech. I was just pointing out the irony of AC saying that.
That being said, it's pretty easy to depseudonymize me, anyway. Yawn.
...says AC.
increased radiation resistance
Keep on dreaming.
0% similar DNA between any two humans is difficult to achieve. Heck, even 99% is.
Many features
In the bloat
Off to FreeBSD
In a safety boat
burma shave
Because he got the virus baked into his OS right from day one, and still seems to be unaware of drive-by attacks?
Made me laugh, at least
Sorry to break it to you, but perl has use <version>; for a long time now.
That the Python people went about the version bump in about the most ham-fisted way imaginable does not mean that this would somehow be the case for all languages now.