You're reffering to Debian Squeeze, not Wheezy. The latter one is the current
stable release and it would be quite decent if gnewsense was based on it.
However, you're right with the rest of your points.
Squeeze still gets support so using it is not a problem from a security point
of view -
Thankyou, where do I actually download the source code for Trisquel?
GnewSense 3 is definitely based on debian Squeeze (6), not Wheezy(7),
considering how perfectly it works with GTK+2 themes, and how perfectly it
doesn't with my Nvidia GeForce 6200 GPU.
where do I actually download the source code for Trisquel?
Here for the all of it, select the sources DVD at
https://trisquel.info/en/download
Or if you want the source for one package only, you can use the apt-get
source $PACKAGENAME command to get it.
I understand. I believe the use of add-ons like AdBlock Plus and Disconnect
could mitigate this; and there's a new add-on surfacing, Privacy Badger, by
EFF, that could possibly help in this task: https://www.eff.org/privacybadger
Pretty cool, huh? I would love to have an e-reader. I've been avoiding them
because I don't want to contribute to any potential kakotopia on the horizon.
A bookstore employee at a major retailer recently asked me if I wanted to buy
one of their readers, which were on sale. I told her that I
Are we going green?
OK. Cool, thanks!
So, because I'm still a rookie at this, I have another question; should I go
with the 944M triskel_7.0-20140629_i686.iso version? I'm assuming that the
i signifies Intel.
Also, I understand the Apple shame. I remember being mocked when having an
Apple in public. Boy
Jabjabs, OK. Cool, thanks!
So, because I'm still a rookie at this, I have another question; should I go
with the 944M triskel_7.0-20140629_i686.iso version? I'm assuming that the
i signifies Intel.
Also, I understand the Apple shame. I remember being mocked when having an
Apple in
i686 means 32 bit, amd64 means 64 bit (and can be used on Intel, AMD and
others)
I'm glad I asked! Thanks.
Here is my new question on askbuntu. My friend installed Ubuntu 14.04 LTS on
his Samsung NP 300 G5X laptop that had 4GB RAM and a 700GB HDD. He encrypted
the Ubuntu installation and used LVM. After reboot he was taken directly to
grub. He was successful in booting into Ubuntu a couple of
Try powering off and hitting F4 over and over during reboot.
I think F4 is the hard reset for Samsung.
He tried that too but failed.
The brick problem seems to happen after installing GNU/Linux then writing to
the NVRAM.
UEFI should garbage-collect after every reboot. Samsung's doesn't. The right
thing to do is acknowledge the bug, fix it, and push updates to customers.
The absolute wrong thing to do is blame the user
15 matches
Mail list logo
