Well, I never looked into virtual machines, although the term sounds familiar, so I Googled it, and it seems like a good solution!
P.S.: let me ask you something..I have 4GB of RAM, do you think this will be enough for Windows 7 x64?
This page says that any Windows x64 will need at least 2GB, plus #! is currently taking 800MB, with only a few tabs in IceWeasel.
So running it with only 4GB on the whole system, is stretching it? I think...maybe I should buy more RAM for it?
I am keeping a Windows 7 VM around and am running it with 2-4G of RAM (depending on how much I need for Linux applications). 2G run Acrobat and MS Office 2010 applications just fine. I can't make any comments on that HP software, but with Acrobat being the most bloated application I can imagine running, the testing framework would most likely work just fine, too. Passing through external ports to a qemu-kvm VM is no problem, too.
You have obviously tested the export thingy? (If it applies here anyway, I probably don't understand the question exactly)
http://stackoverflow.com/questions/7411 … rogramming
This, together with imbecile's suggestion yields:
#!/bin/bash export CATCH=/dev/shm/catch # POSIX shared memory is very useful for things like this… x-terminal-emulator -e bash -c 'sudo apt-get install package; echo $? > $CATCH' if [[ $(<$CATCH) -ne 0 ]]; then # error handling fi
It could work but doesn't have to; the script will warn you but you can continue.
Ubuntu does some things differently than Debian, however the script performs quite generic actions most of which have not many reasons to not succeed on Debian-like systems.
Note that none of the actual BL stuff has been tested on Ubuntu systems, so breakage of the packages themselves might still happen. Your mileage may vary. The packages should be installable on Ubuntu Trusty and later though because we avoid using versioned dependencies wherever we can.
Besides doing the full netinstall, you could also just configure our repositories on your Ubuntu system and, after installing some kind of desktop from the Ubuntu repos, just install the BL features you want (a list of all available packages is shown in our repository index).
I've been attempting to buy a new phone for myself these days and am hopelessly lost between the endless fragmentation which makes up the Android world and hopelessly overpriced Apple hardware…doesn't matter when your employer is footing the bill though :DD
You probably want a <=5 inch screen for pocketability, endless battery life and a robust build (just like me). I'll just paste my notes so far:
* Sony Xperia z3c http://www.gsmarena.com/sony_xperia_z5_compact-7535.php * Sony Xperia z5c http://www.gsmarena.com/sony_xperia_z5_compact-7535.php * Sony Xperia m5 http://www.gsmarena.com/sony_xperia_m5-7464.php * Motorola Moto G3 http://www.gsmarena.com/motorola_moto_g_%283rd_gen%29-7247.php * Apple Iphone 6 http://www.gsmarena.com/apple_iphone_6-6378.php
All Androids on this list have the advantage that the vendors (Sony, Motorola) a) do release the kernel sources for their phones so Cyanogenmod support is almost guaranteed and b) use a unbloated almost-stock Android (motorola) or a have a ASOP program (Sony) c) and tend to upgrade even their very old phones. In any case: long support span (<- this is poor me on a budget speaking again).
Perhaps you are referring to unattended upgrades. It's the horror of any sysadmin but if you use Debian stable, using it should be safe. I think we are not going to set up this by default in order to not configure the system to do things the user doesn't expect.
If you are referring to notifications about available updates by way of a systray icon, then it seems that gnome-packagekit is the successor of update-notifier in Debian and offering this exact functionality. Most likely KDE has something similar; from various threads I gather that XFCE doesn't.
^ All ok?
…It's good to see you, I must go // I know I look a fright…
Oh, man, I shot marvin in the face. I didn't mean it. It was an accident. We probably went over a bump or something.
We gotta be real fuckin' delicate with this Jimmie situation.
You got to appreciate what an explosive element this Bonnie situation is.
This is a real good movie ;DDDD
^ It's the old Intel card…
Then you need to find a working configuration manually. Run compton --help, it'll output a list of all supported options. Try different backends, and backend-specific options. GLX is usually the best performing option, though also the most featureful/option-rich/buggy one.
I'm out of comments here.
In any case, adding not used repos to the sources may cause some problems. Maybe a commented line could be added which the user could uncomment if they want to?
It shouldn't matter at all.
I can't guarantee that you were updating your system just during the time when I was messing around with the webserver configuration (or rebooted the server, happened 2 days ago, but only ONCE) though (sorry).
That's one old Intel graphics card.
Due to the insuffiencies of Linux graphics drivers it's impossible to find a non-tearing setting for all sorts of hardware/software.
You might want to have a look at the vsync option.
I am using a Intel HD4400 and have butter-soft scrolling in Firefox (not much scrolling going on anywhere else) with these settings:
backend = "glx"; vsync = "opengl-swc"; glx-no-stencil = true; glx-no-rebind-pixmap = true;
Do not forget to remove/comment out
dbe = false; paint-on-overlay = false; sw-opti = false;
I have low rendering speeds and tearing in OpenGL-painted video though (not in the browser, by mpv and its opengl output) and extremely low performance on OpenGL games though, so I always disable compositing for that.
the purpose of our jessie-backports is compensating for a lack of official backports; should a package in there appear in the official backports repo, we would remove ours anyway.
Could we perhaps organize pinning and/or version numbering so that the same package appearing in the official backports would result in that getting priority, and being automatically installed with the next upgrade?
We would need to deploy custom APT pinning preferences in one of our packages. This should be possible since we are still different from the original Debian backports by origin (o= pinning). This needs to be thought out carefully though as to not break anything…
The legacy APT respository which was the default until the now superseeded alpha2 release at pkg.2ion.eu, access to which had been preserved until now will be taken offline today. If you have an old install of BL or earlier, please switch to our new repository. Instructions are located at https://pkg.bunsenlabs.org.
APT will fail with a HTTP status of 410: Gone.
I'm not in graphics but we have dark-teal-theme in the repo and deb8 here https://github.com/BunsenLabs/deb8-theme and here http://crunchbang.org/forums/viewtopic.php?pid=419252 (which is cyanish-coloured). deb8 also hasn't been touched since March so there might be bugs (GTK3's CSD and such). I can build a package but have to ask hhh if he wants it included.
Of other things, I know nothing.
You seem to be missing APT source entries…make sure that /etc/apt/sources.list contains at something like (possibly different mirrors):
deb http://ftp.de.netcup.net/debian/ jessie main contrib non-free deb-src http://ftp.de.debian.org/debian/ jessie main contrib non-free deb http://security.debian.org/ jessie/updates main contrib non-free deb-src http://security.debian.org/ jessie/updates main contrib non-free
Your apt-get update command seems to be hitting only jessie/updates and not jessie. Check the file and post the output of `apt-cache policy libappindicator1`.
Using Lubuntu now
^ I have no chance to actually try it, but it should work because device files representing block devices can be accessed using regular read(), write(), lseek() etc syscalls which will do their job just fine. For the purpose of writing consecutive blocks to the device with no offset it'll be no different from dd, but as dd gives you much more control over the process (block size, number of blocks, offset, even character set conversions [which makes sense when writing to a character instead of a block device!]) it can be much faster depending on the physical properties of the block device (spinning disk, flash memory with controller in front of it, ...), or actually fit your purpose