God knows. Apparently not, since its stated aim is to free up/mnt so things can be mounted directly there. An FHS-compliant/mnt has to be completely empty. But that means the/media name makes no sense, since you're mounting NFS etc. there too, and it wasn't that clear anyway. (multimedia?) Furthermore it messes up the way you could get to any directory in / with a single letter and a tab. (I know/boot also messes this up, but most bootloaders don't need/boot to be at/boot, you can make it/kernel or wherever if you want to). It's a name that's two letters longer and less meaningful for the same thing/mnt already did, and it mandates that you cannot use/mnt, you *have* to use/media instead. Which is dumb.
Freedesktop.org isn't the solution either, but LSB doesn't work, because, as the OP said, it's only a base. It doesn't even include a widget library - but it can't, because for any one they could standardise on there's a fairly major distro that doesn't support it. It needs to be more modular, and have a standard way for interfacing libraries, so the commercial vendors can say "requires lsb-qt-3 and lsb-libmad-15". At the moment it requires far too much static compilation, but you can't make all those libraries requirements of the base system, makers of lighter distros would revolt.
It does, it just doesn't handle it properly. What do you do when you distribute a Gtk or cups or libmad-dependent program via autopackage? You either set up a dependency and host your own Gtk autopackage package, which depends on X and glib so you need to host packages for these, etc, or, more likely, you just hope the user has it installed. Wheras with LSB you can rely on certain libraries to be installed (because they're in the specification), and you are forced to compile any which aren't statically. Although this is sub-optimal in many ways, it does ensure your program works.
Yep. But that's where dll hell comes from - applications including their own libraries. The linux way is having separate shared libs, and it's an important part of linux's stability.
Because any random program will work on your LSB system, even with all those other apps and stuff. Which is the point of LSB. It's a way to stop programs needing to distribute a redhat rpm and a suse rpm and a mandrake rpm and a debian deb and so on, instead you just make a lsb rpm which works on any lsb distro.
All I want is 3d for arranging my windows. The windows should stay flat and look the way they do, but I want to be able to rotate myself around them. Go around the back so the window on the right is now on the left. Tilt up a bit to see my media player. Desktop switching with my mousewheel is something, but I want to be able to continuously scroll.
Not for hacking. Hackers largely still use command lines. Movies don't like having plain text going (although there was real hexediting of that half-copied disk, which I was glad to see), so they'll use the 3d toys (jurassic park anyone?) but the fact is that's often where an experienced user is most productive. Hackers won't care much about looking good, they'll just use the text mode.
Not all of them, obviously. But there are some horrible things in the LSB standards. IIRC it mandates FHS compliance, which requires the utterly horrible/media. Also, on the apps front, LSB apps have to be mostly static, where good dynamic binaries and libraries is linux's greatest strength, and necessary since every app including qt or gtk would be nightmarish - your ram goes poof. And yet you can't make these part of the LSB standard, because important distributions don't have them installed, and don't want to. LSB needs a way to have apps depend on libraries, and it needs to take a serious look at where distributions aren't meeting it and why, because often it's because the standard is wrong and should be changed. The suggestion of multiple levels of LSB compliance could improve things a bit, if they can specify dynamic qt and gtk in one for a start.
Yeah, hotplug. It's somewhat less than stable on weirder systems and doesn't always get things right, plus when you come to make your own kernel you have to look through lsmod and pretty much guess which is which. Better than nothing, but I feel the kernel could include a list of which cards work with which drivers, prefferably searchable.
Do you not think it's kinda wrong for them to be patenting and making money off an improved 911 system? I suppose the people who make fire engines etc. are also making money off the emergency services, but still, it feels like it shouldn't be subject to ruthless profiteering like everything else.
They're numbered in a spiral out from London. The A1 goes north to edinburgh along the east coast, A2 into kent, A3 south to portsmouth, A4 to wales and A5 to Birmingham, with the A6 going north to Edinburgh (historically) by the west coast. Then the A7 goes south from Edinburgh to meet the A6, the A8 goes west to Glasgow, and the A9 north to Inverness. Then coming back to London we have the A10 up to Cambridge, the A11 out towards Norwich, A12 to Ipswich, A13 out to Chelmsford, A14 confusingly elsewhere, but then A15 going more southerly and so on until we get to A69, all of these starting gradually further from the dome of St Paul's which is taken as the centre of London. After this the A70-A99 are numbered in a spiral from Edinburgh, A100-699 from London and so on. The green ones are primary routes, in rare cases B roads can also be green roads, and link up a set of "primary destinations". Generally these are straighter and faster roads than the red ones, with more service stations, etc. B roads (which are normally yellow rather than orange) are numbered similarly, but motorways are different, instead taking the number of the nearby A road. Thus there are plenty of gaps in the motorway numbering, for example there is an M20 but no M19, and the M5 starts nowhere near London, it's just long and vaguely near the A5. Also, when an A road is upgraded to a motorway it keeps its name, just with a (M) afterwards, so we have the A1(M) for large sections of the A1 route.
Have you ever tried to compile-in the driver for your network card and no other without looking at the physical chipset or what module knoppix etc. use for it? It's pretty confusing, because the driver name often bears very little relation to the brand of card. Ah, my D-link DP864 (number made up because I can't remember it) must obviously need the Via-Rhine driver, how could I not see that?
Rebuilding external modules can be a pain - with svgalib I end up installing the whole thing again because there's no easy way to do the kernel module alone under 2.6. I wand reiser4 support as soon as possible. Most importantly though, can someone get Linus to stop breaking the perfectly good ide-scsi driver because he doesn't like it? Please.
Slackware comes with a big choice of kernels. One for most hardware, one for one lot of scsi controllers, one with another lot of scsi controllers, one with sata support, one with acpi, one that can boot from usb, one for using XFS as the root filesystem etc. I just found it goofy - often I'd need two of those options, so I pretty much always ended up compiling my own. There are so many choices for different types of hardware you have to just make everything modular (and have initrds for usb boot, XFS root etc.) or get people to compile their own.
No, the sculpture doesn't have much story, but then it sucks. And actually it was part of a pretty big story borrowed from Dante. Wasn't it? He's pondering before his final torment, or something like that.
Nero, iirc 5, at a small educational institution that couldn't afford to upgrade. I don't know if that version works with extra software from ahead and didn't have time to find out about it and getting it set up - policy was just to have an admin account with the login details known by everyone. That's the only time I've seen win2k, everyone else seems to have stuck with 98 or moved on to xp.
Once they have control of a process with your uid, none of this does any good. If all else fails, I think it should be possible to read and write bytes to arbitrary offsets in any process with the same uid with ptrace(2).
Very likely true. But I've yet to see an "off the shelf" program to let you do that. It's not impossible, but it's tricky. And what about people who don't use su, logging in on a separate console when they need to be root?
I'd expect all of this to be simpler than the original stack smasher they used as the local exploit....
Yes it is. But script kiddies outnumber exploit writers at least a hundred to one. Most exploits I've seen in use there has been a program/image/movie/etc. available to give you a shell from it. The guy attacking you is probably just pushing a button or running a script he got from a friend. And I haven't seen a simple script or similar to get local root, except where a bug exists (like the recent kernel local root exploit).
Slashdot Mirror
God knows. Apparently not, since its stated aim is to free up /mnt so things can be mounted directly there. An FHS-compliant /mnt has to be completely empty. But that means the /media name makes no sense, since you're mounting NFS etc. there too, and it wasn't that clear anyway. (multimedia?) Furthermore it messes up the way you could get to any directory in / with a single letter and a tab. (I know /boot also messes this up, but most bootloaders don't need /boot to be at /boot, you can make it /kernel or wherever if you want to). It's a name that's two letters longer and less meaningful for the same thing /mnt already did, and it mandates that you cannot use /mnt, you *have* to use /media instead. Which is dumb.
Nope, that relies on people having a compiler and make and so on installed. Many more newbie-oriented distros don't install them by default.
Freedesktop.org isn't the solution either, but LSB doesn't work, because, as the OP said, it's only a base. It doesn't even include a widget library - but it can't, because for any one they could standardise on there's a fairly major distro that doesn't support it. It needs to be more modular, and have a standard way for interfacing libraries, so the commercial vendors can say "requires lsb-qt-3 and lsb-libmad-15". At the moment it requires far too much static compilation, but you can't make all those libraries requirements of the base system, makers of lighter distros would revolt.
It does, it just doesn't handle it properly. What do you do when you distribute a Gtk or cups or libmad-dependent program via autopackage? You either set up a dependency and host your own Gtk autopackage package, which depends on X and glib so you need to host packages for these, etc, or, more likely, you just hope the user has it installed. Wheras with LSB you can rely on certain libraries to be installed (because they're in the specification), and you are forced to compile any which aren't statically. Although this is sub-optimal in many ways, it does ensure your program works.
Yep. But that's where dll hell comes from - applications including their own libraries. The linux way is having separate shared libs, and it's an important part of linux's stability.
Watch them on a computer with DeCSS, if you can.
Because any random program will work on your LSB system, even with all those other apps and stuff. Which is the point of LSB. It's a way to stop programs needing to distribute a redhat rpm and a suse rpm and a mandrake rpm and a debian deb and so on, instead you just make a lsb rpm which works on any lsb distro.
All I want is 3d for arranging my windows. The windows should stay flat and look the way they do, but I want to be able to rotate myself around them. Go around the back so the window on the right is now on the left. Tilt up a bit to see my media player. Desktop switching with my mousewheel is something, but I want to be able to continuously scroll.
Not for hacking. Hackers largely still use command lines. Movies don't like having plain text going (although there was real hexediting of that half-copied disk, which I was glad to see), so they'll use the 3d toys (jurassic park anyone?) but the fact is that's often where an experienced user is most productive. Hackers won't care much about looking good, they'll just use the text mode.
Not all of them, obviously. But there are some horrible things in the LSB standards. IIRC it mandates FHS compliance, which requires the utterly horrible /media. Also, on the apps front, LSB apps have to be mostly static, where good dynamic binaries and libraries is linux's greatest strength, and necessary since every app including qt or gtk would be nightmarish - your ram goes poof. And yet you can't make these part of the LSB standard, because important distributions don't have them installed, and don't want to. LSB needs a way to have apps depend on libraries, and it needs to take a serious look at where distributions aren't meeting it and why, because often it's because the standard is wrong and should be changed. The suggestion of multiple levels of LSB compliance could improve things a bit, if they can specify dynamic qt and gtk in one for a start.
Yeah, hotplug. It's somewhat less than stable on weirder systems and doesn't always get things right, plus when you come to make your own kernel you have to look through lsmod and pretty much guess which is which. Better than nothing, but I feel the kernel could include a list of which cards work with which drivers, prefferably searchable.
It can be hard to search google without a working network card. It's ok for people with another OS or computer, but that isn't everyone.
The drm however isn't, or at least wasn't, published, it was necessary to reverse-engineer that, but normal pdfs are fine.
Do you not think it's kinda wrong for them to be patenting and making money off an improved 911 system? I suppose the people who make fire engines etc. are also making money off the emergency services, but still, it feels like it shouldn't be subject to ruthless profiteering like everything else.
Someone offered RSS feeds of Google news, and they takedown'd him. That was the point they became evil in my book.
However, no kudos for whoever taught you to spell :)
They're numbered in a spiral out from London. The A1 goes north to edinburgh along the east coast, A2 into kent, A3 south to portsmouth, A4 to wales and A5 to Birmingham, with the A6 going north to Edinburgh (historically) by the west coast. Then the A7 goes south from Edinburgh to meet the A6, the A8 goes west to Glasgow, and the A9 north to Inverness. Then coming back to London we have the A10 up to Cambridge, the A11 out towards Norwich, A12 to Ipswich, A13 out to Chelmsford, A14 confusingly elsewhere, but then A15 going more southerly and so on until we get to A69, all of these starting gradually further from the dome of St Paul's which is taken as the centre of London. After this the A70-A99 are numbered in a spiral from Edinburgh, A100-699 from London and so on. The green ones are primary routes, in rare cases B roads can also be green roads, and link up a set of "primary destinations". Generally these are straighter and faster roads than the red ones, with more service stations, etc. B roads (which are normally yellow rather than orange) are numbered similarly, but motorways are different, instead taking the number of the nearby A road. Thus there are plenty of gaps in the motorway numbering, for example there is an M20 but no M19, and the M5 starts nowhere near London, it's just long and vaguely near the A5. Also, when an A road is upgraded to a motorway it keeps its name, just with a (M) afterwards, so we have the A1(M) for large sections of the A1 route.
Have you ever tried to compile-in the driver for your network card and no other without looking at the physical chipset or what module knoppix etc. use for it? It's pretty confusing, because the driver name often bears very little relation to the brand of card. Ah, my D-link DP864 (number made up because I can't remember it) must obviously need the Via-Rhine driver, how could I not see that?
Because that's what we do to any normal company that does this. Apple's just different, because there's a zillion blind apple fanboys here.
Rebuilding external modules can be a pain - with svgalib I end up installing the whole thing again because there's no easy way to do the kernel module alone under 2.6. I wand reiser4 support as soon as possible. Most importantly though, can someone get Linus to stop breaking the perfectly good ide-scsi driver because he doesn't like it? Please.
Slackware comes with a big choice of kernels. One for most hardware, one for one lot of scsi controllers, one with another lot of scsi controllers, one with sata support, one with acpi, one that can boot from usb, one for using XFS as the root filesystem etc. I just found it goofy - often I'd need two of those options, so I pretty much always ended up compiling my own. There are so many choices for different types of hardware you have to just make everything modular (and have initrds for usb boot, XFS root etc.) or get people to compile their own.
Because, and I'll get modded to hell for this, google is now evil. Really.
No, the sculpture doesn't have much story, but then it sucks. And actually it was part of a pretty big story borrowed from Dante. Wasn't it? He's pondering before his final torment, or something like that.
Nero, iirc 5, at a small educational institution that couldn't afford to upgrade. I don't know if that version works with extra software from ahead and didn't have time to find out about it and getting it set up - policy was just to have an admin account with the login details known by everyone. That's the only time I've seen win2k, everyone else seems to have stuck with 98 or moved on to xp.
Very likely true. But I've yet to see an "off the shelf" program to let you do that. It's not impossible, but it's tricky. And what about people who don't use su, logging in on a separate console when they need to be root?
I'd expect all of this to be simpler than the original stack smasher they used as the local exploit....
Yes it is. But script kiddies outnumber exploit writers at least a hundred to one. Most exploits I've seen in use there has been a program/image/movie/etc. available to give you a shell from it. The guy attacking you is probably just pushing a button or running a script he got from a friend. And I haven't seen a simple script or similar to get local root, except where a bug exists (like the recent kernel local root exploit).