Alright, someone who's working on Arch needs to add a cache clearing script to pacman or something. I didn't realize that it would keep fucking packages forever and ever, and have filled my disk up with old junk I don't need now. One clearing and crontab job later, it shouldn't happen again. Now to go back and reinstall X, from where it was broken before all this mess.
Pacman/yaourt -Sc?
Yea, I threw that in my cron after this mess. It's still kinda stupid that it'll happily fill up my 7GB partition with junk old packages
Alright, someone who's working on Arch needs to add a cache clearing script to pacman or something. I didn't realize that it would keep fucking packages forever and ever, and have filled my disk up with old junk I don't need now. One clearing and crontab job later, it shouldn't happen again. Now to go back and reinstall X, from where it was broken before all this mess.
Pacman/yaourt -Sc?
Yea, I threw that in my cron after this mess. It's still kinda stupid that it'll happily fill up my 7GB partition with junk old packages
If pacman is anything like apt, the cached packages are used for repair and reinstallation. They do serve a purpose, but not everyone needs the cache.
It's like the hotfix uninstallers that litter XP installs.
Alright, someone who's working on Arch needs to add a cache clearing script to pacman or something. I didn't realize that it would keep fucking packages forever and ever, and have filled my disk up with old junk I don't need now. One clearing and crontab job later, it shouldn't happen again. Now to go back and reinstall X, from where it was broken before all this mess.
Pacman/yaourt -Sc?
Yea, I threw that in my cron after this mess. It's still kinda stupid that it'll happily fill up my 7GB partition with junk old packages
If pacman is anything like apt, the cached packages are used for repair and reinstallation. They do serve a purpose, but not everyone needs the cache.
It's like the hotfix uninstallers that litter XP installs.
Except that it's easy to get rid of the cached files.
BTW, pacman -Sc will only remove previous versions of the package files; the package files that match the currently installed revisions are kept. pacman -Scc will remove all of them.
Barrakketh on
Rollers are red, chargers are blue....omae wa mou shindeiru
Magic trick for installing and running Google Earth on Ubuntu 10.10 (pieced together from various things on the tubes):
./GoogleEarthLinux.bin --target /tmp/ge
cd /tmp/ge/setup.data/bin/Linux/x86/
mv setup.gtk setup.gtk2
gedit/whatever ~/.config/Google/GoogleEarthPlus.conf
Make sure enableTips=false is located under [General]
MKR on
0
proyebatGARY WAS HEREASH IS A LOSERRegistered Userregular
edited October 2010
Man, I'm so happy 10.10 installs catalyst 10.10, because it was a bitch to install everyone after 10.7 manually (somehow the run file's automated script wouldn't install correctly). See, my computer has an nforce4 chipset which is incompatible with catalyst 9.something-10.7 and seriously reinstalled Ubuntu and Arch Linux multiple times until I figured out the problem. Then I had to wait, and wait, and wait.
Ugh.
proyebat on
0
TincheNo dog food for Victor tonight.Registered Userregular
edited October 2010
My Ubuntu box just locked up on me upon exiting Chrome. Apparently it's a known issue, and fixed in Maverick's kernel (I'm still on Lucid).
This is the first time since switching to Ubuntu I've had a lock-up. Actually, I think this is the first time since I've switched that I've had to reboot, barring kernel updates. I usually leave the computer on, it goes to sleep after an hour, when I get back I wake it up and continue where I left off, repeating this process for weeks.
I just lost my Linux lock-up virginity
Tinche on
We're marooned on a small island, in an endless sea,
Confined to a tiny spit of sand, unable to escape,
But tonight, it's heavy stuff.
0
proyebatGARY WAS HEREASH IS A LOSERRegistered Userregular
edited October 2010
Heyo, I ran myself into a little snag earlier today.
I was trying to embed a filesystem into a loopback file, but accidentally made a dir without mounting the file as a loopback.
Is there anyway to copy the contents of a dir (preserving all links) into a loopback mounted file? I know squashfs does the job great, but was looking for help with ext2/3/4.
Is it hard links or soft links you're worried about saving?
End on
I wish that someway, somehow, that I could save every one of us
0
proyebatGARY WAS HEREASH IS A LOSERRegistered Userregular
edited October 2010
Assuming both, I'm not sure if compiling the kernel produces one type or both.
I realized I caught this mistake early enough that I can copy what I've compiled already, it would only take a few minutes, but I'd like to know how to fix this provided I caught the mistake later in my build.
I've heard of cpio being used to preserve hard links (basically using a pipe where one end "archives" the source and the other end "unarchives" to the destination).
rsync has an -H flag that preserves hard links as well, and it's fairly straight forward to do a directory to directory copy.
In either case, you'd want to make sure you specify all the right flags to get user, group, timestamp, etc information all copied too.
End on
I wish that someway, somehow, that I could save every one of us
0
proyebatGARY WAS HEREASH IS A LOSERRegistered Userregular
Hello all, I have a live-CD question for those that would be willing to help out a (clueless) forumer. I am looking for a distro/live-CD for security testing purposes. Is BackTrack (http://www.backtrack-linux.org/) my best option for this? It is mentioned in a lot of places through my googling but being new to this I am unsure. I am not doing anything all that extensive, for example my first target is just breaking a small WEP secure network I created in my living room (starting out very small).
This is all pretty much just for giggles as I try and learn a few things from it. Any other suggestions?
Backtrack is the security/penetration testing distro. But a lot of the tools are available elsewhere, so you could probably create your own if you know what tools you need.
Backtrack is the security/penetration testing distro. But a lot of the tools are available elsewhere, so you could probably create your own if you know what tools you need.
That's pretty much what I have seen in several places, I just wasn't really sure if I am going to be jumping into a pool with weights on around my ankles and trying to tread water by trying to starting there.
I got a SunBlade workstation of unknown vintage that sits on the super secure part of our network. Right now it is running Solaris 9. It wouldn't surprise me if it was SUNs R&D box for Solaris 9 I'm assuming it's that old. Pretty much right now it is just a waste of electricity, but we'd like to make it useful.
I think my first move is to scrounge a Solaris 10 disk or something, and ideally I'd love to be able to remotely log in to it, mostly because it is cool and why the hell not.
Feasible? Even if its not, I'm gonna do it, but it'd be nice to know I'm not wasting my time.
I dunno how many of y'all have been following the Ubuntu developments recently? But stuff hath happened.
Banshee will be replacing Rhythmbox in 11.04
11.04 will use a modified version of the "Unity" netbook interface. Canonical is apparently positioning the environment as a challenger to Gnome 3, and there is talk of merging or having collaboration between the two parties.
Patches from Nautilus-Elementary are going to be included. The Elementary team has done a lot in their efforts to make Nautilus more usable. Yay.
As a person using Ubuntu full time on my main machine, my thoughts on these are:
Banshee will be replacing Rhythmbox in 11.04
I'm ok with switching to Banshee (yes, I know I don't have to, blah blah) as long as the following Rhythmbox functionality is there: a Do plugin, sound menu integration, and bidirectional sync with my iPhone. I already have Mono on my system for Do and Docky, so no problems there.
11.04 will use a modified version of the "Unity" netbook interface. Canonical is apparently positioning the environment as a challenger to Gnome 3, and there is talk of merging or having collaboration between the two parties.
I'm actually kinda happy with my current 2.3 setup, but I realize that might not be a viable choice since Gnome is switching to Gnome Shell anyway. In any case, I *really* like Ubuntu's Gnome modifications, like the messaging menu and application indicators in general, so I'm giving Unity a chance when Natty comes out. I'm also liking they switched to Compiz for Unity. Incidentally, I already use a vertical dock on the left edge, set to auto-hide (Docky).
Patches from Nautilus-Elementary are going to be included. The Elementary team has done a lot in their efforts to make Nautilus more usable. Yay.
I use Nautilus Elementary myself, from ammonkey's repo. Apparently, Nautilus Elementary was considered to be the default file manager in Natty but some Ubuntu devs considered it "too hacky", which caused ammonkey (main NE developer) to throw a fit on his blog. I don't know just how hacky NE is, but I have had it bug out on me a number of times, so maybe there's something there. I like the general direction though, and acknowledging something needs to be done about Nautilus' default interface.
New icon theme again. Probably in 11.10.
Don't really have an opinion on this. I think they said something about a whole new sound theme for Natty too.
Tinche on
We're marooned on a small island, in an endless sea,
Confined to a tiny spit of sand, unable to escape,
But tonight, it's heavy stuff.
This has been bugging me. For some crazy reason, the Arch Linux folk have decided that PYTHON 3 IS NEW PYTHON EVERYONE MUST USE and made the default python symlink point to python3. Yes, they are the only distribution that does this. Yes, this breaks compatibility with a ton of Python 2 scripts they don't package, as well as a pretty big chunk of Python-related AUR pkgbuilds. Yes, upstream told them not to do it. Yes, it breaks their "no modifications from upsteam" rule, as well as their "simplicity is good and complicated should be avoided" rule of thumb.
Several people (myself included) have posted about it in the forum thread at Arch, but the maintainers don't seem to care. Meanwhile, Arch users have come to freenode #python with issues relating to this change so frequently that the channel topic now contains "NO ARCH".
...and I don't even run Arch anymore! I was considering slapping Arch PPC on my new old Mac, but since a lot of my hobby development is in Python, I might have to use something else...
I guess I can kinda see their point of view, but if there's anything the linux world doesn't need it's more shit being broken for no good reason.
For most cases things aren't being broken. Most Python packages are distributed via PyPI and easy_install/pip will install those packages and things will work properly. Ditto for Python packages distributed through Arch's official repositories.
The only place this is even an issue are scripts that end-users wrote and for AUR packages where the package maintainers were too dumb to actually follow the mailing lists. I've known that this was coming for months, and you can fix the packages you're distributing through AUR with one line of code ("find ${pkgdir} -type f -iname '*.py" -exec sed -i -e 's|python$|python2' {} \;") added to your PKGBUILD.
Frem is also wrong on several points, some of which is caused by a misunderstanding of Arch's policies. For starters, the "no modifications from upstream" rule. Not only are modifications allowed so packages will build/run correctly on Arch, if you install Python with "make altinstall" there would be no "/usr/bin/python" symlink or binary. Applications relying on its presence are, to some degree, wrong. The only modification to Python 2.7 is that they fixed the shebangs on some files distributed with Python that do not work properly with "make altinstall" and there is a ticket on the Python bug tracker working towards fixing it. Patches can also be applied to fix an application that is broken and there is no upstream release that fixes the issue (since Arch is a bleeding-edge distro basically everything from the official repos are the latest versions).
In any event, as things stand now Python 2.7 is the last release of the Python 2 series and won't be getting any new features, though it will be supported for several more years. Most of the work done on 2.7 was some things backported from Python 3 to ease porting to Python 3. If you're a new Python developer or starting a new project where you can choose to use Python 3 you should be using Python 3.
Barrakketh on
Rollers are red, chargers are blue....omae wa mou shindeiru
Pytharch Linon
Meh, I guess I just fall into the "why break things and make them annoying to fix?" category. ("Because it's bleeding edge! Tweak it or use something else.") I'd have preferred that they just omit the symlink altogether so that (a) a more obvious error message resulted for incompatible scripts, and (b) it'd be easier to symlink it to whatever version you wanted and not have to relink every time there was a Python 3 update. Because future-proofing is great, but if you're developing or using a Python desktop app now, 2.7 is generally the version you'll be using just because Python 3 versions of the three of the most popular toolkits that aren't TkInter aren't there yet. Django developers are in a similar boat.
But as I said, I no longer use the distribution. And I guess it's not a huge issue in the grand lisp-derivative of things. I'm mostly just hating because Arch is now a slightly lesser shade of perfect.
---
X.org is dead!
On the other end of the perfection spectrum, Mark Shuttleworth has announced that Ubuntu has decided to also break everything. X.org is gone, now we'll get Wayland.
I've personally hated X since shortly after I started using Linux, for reasons relating to just getting it running at all (2001), how much memory it liked to eat (2002), how much of a pain graphics drivers were (2005), and how it does a shoddy job of handling multiple monitors (2007-present). So I think this is pretty great. I will likely retract the preceding statement in two years or so when it will probably go into the main Ubuntu distribution and inevitably break on my machine.
The Wayland architecture is a bit more streamlined, and it supports Mac OS X-style backwards compatibility with X.org. One major goal is to make it easier to do pretty compositing things. (I'm also hoping that it'll allow you to launch an app on one workspace and then switch to another workspace before the app loads without the app popping up in your face when it loads. Another thing which has annoyed me about X since forever.)
It does look like we loose the ability to run gui apps remotely. But since realistically, the vast majority of users never actually did that, it might be worth the loss of having that built into the core in exchange for a simplified pipeline, especially with how badly we're dependent on closed source drivers for gaming. Or does this hurt closed source drivers? I try to ignore those matters until things go horribly wrong.
It does look like we loose the ability to run gui apps remotely. But since realistically, the vast majority of users never actually did that, it might be worth the loss of having that built into the core in exchange for a simplified pipeline, especially with how badly we're dependent on closed source drivers for gaming. Or does this hurt closed source drivers? I try to ignore those matters until things go horribly wrong.
The word is 'lose' (antonym of 'gain'), not 'loose' (antonym of 'tight').
I hate X but do use the ability to run gui apps remotely, but am also not really an Ubuntu user. I don't know how I feel about this.
Oh great, I get to have fun recompiling things to work on X now. Ubuntu is the most popular distro, and for some stupid reason almost every other distro follows it's lead. This means that most packages are going to start requiring Wayland or something
Here's some stuff from an offsite FAQ about what Wayland does, and why it doesn't provide network transparency.
Is wayland replacing the X server?
It could replace X as the native Linux graphics server, but I'm sure X will always be there on the side. I imagine that Wayland and X will coexist in two ways on a Linux desktop:
Wayland is a graphics multiplexer for a number of X servers. Linux today typically only uses one X server for GDM and the user session, but we'll probably see that move to a dedicated GDM X server, an X server for user sessions (spawning more on the fly as more users log in) and maybe a dedicated screensaver/unlock X server. Right now we rely on VT switching to move between X servers, and it's horrible. We have no control over what the transitions look like and the VT ioctls are pretty bad. Wayland provides a solution here, in that it can host several X servers as they push their root window to Wayland as surfaces. The compositor in this case will be a dedicated session switcher that will cross-fade between X servers or spin them on a cube.
Further down the road we run a user session natively under Wayland with clients written for Wayland. There will still (always) be X applications to run, but we now run these under a root-less X server that is itself a client of the Wayland server. This will inject the X windows into the Wayland session as native looking clients. The session Wayland server can run as a nested Wayland server under the system Wayland server described above, maybe even side by side with X sessions.
There's a number of intermediate steps, suchs as running the GNOME screen saver as a native wayland client, for example, or running a composited X desktop, where the compositor is a Wayland client, pushing the composited desktop to Wayland.
Why not extend the X server?
Because we for the first time we have a realistic chance of not having to do that. It's entirely possible to incorporate the buffer exchange and update models the Wayland is built on into X. However, we have an option here of pushing X out of the hotpath between clients and the hardware and making it a compatibility option. I'm not deluding myself that any general purpose desktop Linux distribution will stop shipping X as we know it or as a Wayland client anytime soon. Nor should they, there will still be X applications to run and people expect that from a Linux desktop. What's different now is that a lot of infrastructure has moved from the X server into the kernel (memory management, command scheduling, mode setting) or libraries (cairo, pixman, freetype, fontconfig, pango etc) and there is very little left that has to happen in a central server process.
Is Wayland network transparent / does it support remote rendering?
No, that is outside the scope of Wayland. To support remote rendering you need to define a rendering API, which is something I've been very careful to avoid doing. The reason Wayland is so simple and feasible at all is that I'm sidestepping this big task and pushing it to the clients. It's an interesting challenge, a very big task and it's hard to get right, but essentially orthogonal to what Wayland tries to acheive. This doesn't mean that remote rendering won't be possible with Wayland, it just means that you will have to put a remote rendering server on top of Wayland. One such server could be the X.org server, but other options include an RDP server, a VNC server or somebody could even invent their own new remote rendering model. Which is a feature when you think about it; layering X.org on top of Wayland has very little overhead, but the other types of remote rendering servers no longer requires X.org, and experimenting with new protocols is easier.
It seems to indicate that we'll initially just see Wayland as a way to run a lot of dedicated X servers. Which is neat, but what's the point? Are GDM or Xscreensaver more secure just because they've got their own instance of X.org? Or is this an eye candy thing?
It also indicates that someone could write a Wayland layer for network transparency, but that they'd have to write a software rendering layer along with it. I'll be kinda surprised if such a layer that behaves very similar to X.org doesn't surface before X.org fades from the scene forever. (Which is precisely how long X.org will take to fade from the scene! But.)
From what all I've read of what Wayland is going to do, it seems like it'll allow you to have your eyecandy (like 3D compositing) and still run OpenGL programs on hardware. If you have an Nvidia card, Nvidia's already worked this into their drivers, making this shift completely useless.
From what all I've read of what Wayland is going to do, it seems like it'll allow you to have your eyecandy (like 3D compositing) and still run OpenGL programs on hardware. If you have an Nvidia card, Nvidia's already worked this into their drivers, making this shift completely useless.
Nvidia accomplished this by bypassing large chunks of X.org, and their drivers are closed source. It sort of excludes like 50% (more?) of the market.
I think that's just the Ubuntu crowd being idiots. I switched to Linux for freedom to modify my system and ability to fix anything myself, but I'd also like tools and games to be Linux native.
I don't know if we've discussed this in here before, but is there a Linux media server that can take data on a network drive and stream it to consoles (360 and PS3)?
Additionally, I want to be able to download something to the Linux box, scan it for threats to other machines on my network, then put it on the network drive. Is there an anti-virus program I can use to scan this network drive for mac or windows-targeted threats?
I don't know if we've discussed this in here before, but is there a Linux media server that can take data on a network drive and stream it to consoles (360 and PS3)?
Additionally, I want to be able to download something to the Linux box, scan it for threats to other machines on my network, then put it on the network drive. Is there an anti-virus program I can use to scan this network drive for mac or windows-targeted threats?
KlamAV is an open source virus scanner, or you can get Avast or AVG's linux versions.
For streaming to the Xbox, I'm not quite sure.
elliotw2 on
XBL:Elliotw3|PSN:elliotw2
0
proyebatGARY WAS HEREASH IS A LOSERRegistered Userregular
edited November 2010
for xbox steaming, try "ushare". I once got it working. It was kind of a hassle.
Ugh, the replies in MRK's link just makes my head explode. What a bunch of idiots arguing over personal opinions.
Posts
Yea, I threw that in my cron after this mess. It's still kinda stupid that it'll happily fill up my 7GB partition with junk old packages
If pacman is anything like apt, the cached packages are used for repair and reinstallation. They do serve a purpose, but not everyone needs the cache.
It's like the hotfix uninstallers that litter XP installs.
BTW, pacman -Sc will only remove previous versions of the package files; the package files that match the currently installed revisions are kept. pacman -Scc will remove all of them.
Ugh.
This is the first time since switching to Ubuntu I've had a lock-up. Actually, I think this is the first time since I've switched that I've had to reboot, barring kernel updates. I usually leave the computer on, it goes to sleep after an hour, when I get back I wake it up and continue where I left off, repeating this process for weeks.
I just lost my Linux lock-up virginity
Confined to a tiny spit of sand, unable to escape,
But tonight, it's heavy stuff.
I was trying to embed a filesystem into a loopback file, but accidentally made a dir without mounting the file as a loopback.
Is there anyway to copy the contents of a dir (preserving all links) into a loopback mounted file? I know squashfs does the job great, but was looking for help with ext2/3/4.
I realized I caught this mistake early enough that I can copy what I've compiled already, it would only take a few minutes, but I'd like to know how to fix this provided I caught the mistake later in my build.
rsync has an -H flag that preserves hard links as well, and it's fairly straight forward to do a directory to directory copy.
In either case, you'd want to make sure you specify all the right flags to get user, group, timestamp, etc information all copied too.
Well, I found one program, but I forget what the name of it was, and it sucked.
This is all pretty much just for giggles as I try and learn a few things from it. Any other suggestions?
WoWtcg and general gaming podcast
WoWtcg and gaming website
That's pretty much what I have seen in several places, I just wasn't really sure if I am going to be jumping into a pool with weights on around my ankles and trying to tread water by trying to starting there.
WoWtcg and general gaming podcast
WoWtcg and gaming website
I think my first move is to scrounge a Solaris 10 disk or something, and ideally I'd love to be able to remotely log in to it, mostly because it is cool and why the hell not.
Feasible? Even if its not, I'm gonna do it, but it'd be nice to know I'm not wasting my time.
Lightweight, support for tons of formats and of course gapless playback.
Here's the OMG Ubuntu! summary.
As a person using Ubuntu full time on my main machine, my thoughts on these are:
I'm ok with switching to Banshee (yes, I know I don't have to, blah blah) as long as the following Rhythmbox functionality is there: a Do plugin, sound menu integration, and bidirectional sync with my iPhone. I already have Mono on my system for Do and Docky, so no problems there.
I'm actually kinda happy with my current 2.3 setup, but I realize that might not be a viable choice since Gnome is switching to Gnome Shell anyway. In any case, I *really* like Ubuntu's Gnome modifications, like the messaging menu and application indicators in general, so I'm giving Unity a chance when Natty comes out. I'm also liking they switched to Compiz for Unity. Incidentally, I already use a vertical dock on the left edge, set to auto-hide (Docky).
I use Nautilus Elementary myself, from ammonkey's repo. Apparently, Nautilus Elementary was considered to be the default file manager in Natty but some Ubuntu devs considered it "too hacky", which caused ammonkey (main NE developer) to throw a fit on his blog. I don't know just how hacky NE is, but I have had it bug out on me a number of times, so maybe there's something there. I like the general direction though, and acknowledging something needs to be done about Nautilus' default interface.
Don't really have an opinion on this. I think they said something about a whole new sound theme for Natty too.
Confined to a tiny spit of sand, unable to escape,
But tonight, it's heavy stuff.
Thank you. This thing's tricky to get installed, but... it works. Which is more than I can say for any other gapless media player I've tried.
Several people (myself included) have posted about it in the forum thread at Arch, but the maintainers don't seem to care. Meanwhile, Arch users have come to freenode #python with issues relating to this change so frequently that the channel topic now contains "NO ARCH".
...and I don't even run Arch anymore! I was considering slapping Arch PPC on my new old Mac, but since a lot of my hobby development is in Python, I might have to use something else...
I guess I can kinda see their point of view, but if there's anything the linux world doesn't need it's more shit being broken for no good reason.
The only place this is even an issue are scripts that end-users wrote and for AUR packages where the package maintainers were too dumb to actually follow the mailing lists. I've known that this was coming for months, and you can fix the packages you're distributing through AUR with one line of code ("find ${pkgdir} -type f -iname '*.py" -exec sed -i -e 's|python$|python2' {} \;") added to your PKGBUILD.
Frem is also wrong on several points, some of which is caused by a misunderstanding of Arch's policies. For starters, the "no modifications from upstream" rule. Not only are modifications allowed so packages will build/run correctly on Arch, if you install Python with "make altinstall" there would be no "/usr/bin/python" symlink or binary. Applications relying on its presence are, to some degree, wrong. The only modification to Python 2.7 is that they fixed the shebangs on some files distributed with Python that do not work properly with "make altinstall" and there is a ticket on the Python bug tracker working towards fixing it. Patches can also be applied to fix an application that is broken and there is no upstream release that fixes the issue (since Arch is a bleeding-edge distro basically everything from the official repos are the latest versions).
In any event, as things stand now Python 2.7 is the last release of the Python 2 series and won't be getting any new features, though it will be supported for several more years. Most of the work done on 2.7 was some things backported from Python 3 to ease porting to Python 3. If you're a new Python developer or starting a new project where you can choose to use Python 3 you should be using Python 3.
Pytharch Linon
Meh, I guess I just fall into the "why break things and make them annoying to fix?" category. ("Because it's bleeding edge! Tweak it or use something else.") I'd have preferred that they just omit the symlink altogether so that (a) a more obvious error message resulted for incompatible scripts, and (b) it'd be easier to symlink it to whatever version you wanted and not have to relink every time there was a Python 3 update. Because future-proofing is great, but if you're developing or using a Python desktop app now, 2.7 is generally the version you'll be using just because Python 3 versions of the three of the most popular toolkits that aren't TkInter aren't there yet. Django developers are in a similar boat.
But as I said, I no longer use the distribution. And I guess it's not a huge issue in the grand lisp-derivative of things. I'm mostly just hating because Arch is now a slightly lesser shade of perfect.
---
X.org is dead!
On the other end of the perfection spectrum, Mark Shuttleworth has announced that Ubuntu has decided to also break everything. X.org is gone, now we'll get Wayland.
I've personally hated X since shortly after I started using Linux, for reasons relating to just getting it running at all (2001), how much memory it liked to eat (2002), how much of a pain graphics drivers were (2005), and how it does a shoddy job of handling multiple monitors (2007-present). So I think this is pretty great. I will likely retract the preceding statement in two years or so when it will probably go into the main Ubuntu distribution and inevitably break on my machine.
The Wayland architecture is a bit more streamlined, and it supports Mac OS X-style backwards compatibility with X.org. One major goal is to make it easier to do pretty compositing things. (I'm also hoping that it'll allow you to launch an app on one workspace and then switch to another workspace before the app loads without the app popping up in your face when it loads. Another thing which has annoyed me about X since forever.)
It does look like we loose the ability to run gui apps remotely. But since realistically, the vast majority of users never actually did that, it might be worth the loss of having that built into the core in exchange for a simplified pipeline, especially with how badly we're dependent on closed source drivers for gaming. Or does this hurt closed source drivers? I try to ignore those matters until things go horribly wrong.
The word is 'lose' (antonym of 'gain'), not 'loose' (antonym of 'tight').
I hate X but do use the ability to run gui apps remotely, but am also not really an Ubuntu user. I don't know how I feel about this.
The full thing is here, and worth a skim.
It seems to indicate that we'll initially just see Wayland as a way to run a lot of dedicated X servers. Which is neat, but what's the point? Are GDM or Xscreensaver more secure just because they've got their own instance of X.org? Or is this an eye candy thing?
It also indicates that someone could write a Wayland layer for network transparency, but that they'd have to write a software rendering layer along with it. I'll be kinda surprised if such a layer that behaves very similar to X.org doesn't surface before X.org fades from the scene forever. (Which is precisely how long X.org will take to fade from the scene! But.)
Cardapio? (Screenshots)
Confined to a tiny spit of sand, unable to escape,
But tonight, it's heavy stuff.
Nvidia accomplished this by bypassing large chunks of X.org, and their drivers are closed source. It sort of excludes like 50% (more?) of the market.
You could always run Kicker or Plasma?
http://www.omgubuntu.co.uk/2010/11/hey-adobe-bring-creative-suite-for-ubuntu/
The thing bugging me there is all the people saying "why would you want Adobe software on Linux when you switch to it for freedom?"
As though everyone uses Linux for one group's ideal of freedom. :?
Additionally, I want to be able to download something to the Linux box, scan it for threats to other machines on my network, then put it on the network drive. Is there an anti-virus program I can use to scan this network drive for mac or windows-targeted threats?
KlamAV is an open source virus scanner, or you can get Avast or AVG's linux versions.
For streaming to the Xbox, I'm not quite sure.
Ugh, the replies in MRK's link just makes my head explode. What a bunch of idiots arguing over personal opinions.