Re: sad but true, Linux sucks, a bit

[Jarth Berilcosm]

On Wed, 15 Jan 2014 11:08:22 -0600, yaro wrote:

Yeah, well, all this bitching proves i should look harder for the off-
topic list.

> On Wednesday, January 15, 2014 04:53:15 PM Jarth Berilcosm wrote:
>> On Wed, 15 Jan 2014 17:29:01 +0100, Ralf Mardorf wrote:
>> 
>> I'm using a news-reader and could not find the off-topic mailinglist.
>> 
>> Sorry to say so but your reply sounds more like rambling than anything.
>> I'll reply to the part i was able to comprehend.
>> 
>> Expectations ? Man, get a good night sleep.
>> 
>> Computers are cheap crap because they can be made to be cheap crap. The
>> production proces permits this.
>> 
>> >> Most importantly this list is not an opinion. Almost every listed
>> >> point has links to appropriate articles, threads and discussions
>> >> centered on it, proving that I haven't pulled it out of my <
>> >> expletive
>> >> 
>> >> >. And please always check your "facts".
>> >> 
>> >> If you get an impression that Linux sucks - you are largely wrong.
>> >> If I had to create a list of Windows problems, it would be almost as
>> >> long as this one.
>> > 
>> > -
>> > http://linuxfonts.narod.ru/
>> 
>> why.linux.is.not.ready.for.the.desktop.current.html
>> 
>> > Unworldly!
>> > 
>> > A lot of people think like you, not understanding that digital
>> > technology can't compare to analog technology. Sure, using a computer
>> > humans can do some things that can't be done manually or by analog
>> > technology, but most things are from much higher quality, when done
>> > with analog technology or manually. Multimedia, toolmaking, ... an
>> > endless list.
>> > 
>> > We use computers, because analog technology and handcrafted things
>> > are to expensive, the complete philosophy of human kind did go a step
>> > in the wrong direction.
>> > 
>> > I'm pro computers, already using Linux for more than 10 years, but
>> > started much earlier with computers in the late 80s.
>> > 
>> > It's a misunderstanding to guess that computer technology is that
>> > progressed. Computers are cheap crap. If you are aware that they are
>> > nothing but cheap crap, you can use them from an relatively objective
>> > point of view.
>> > 
>> > Less expectations = less disappointment
>> > 
>> > High expectations = high disappointment
>> > 
>> > IOW your opinion is subjective from an unworldly point of view.
>> > 
>> > Regards,
>> > Ralf
>> > 
>> > PS: You sent to the wrong list. I only Cc'ed to Debian user and sent
>> > to the off-topic list. I suspect replies should go to this list only.
> 
> 
> These "reasons why Linux is not ready for the desktop" lists are so
> stupid. Sure they're "objective." But you know how easy it is to take
> Windows or OS X,
> grab a list of THEIR flaws, and call them reasons *they* aren't ready
> for the desktop? This is practically trolling. Nothing to see here
> people, move along.
> 
> Conrad





-- 
jabadaba doooh ooh h


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/pan.2014.01.15.21.42...@yahoo.com

Re: sad but true, Linux sucks, a bit

[Jarth Berilcosm]

On Wed, 15 Jan 2014 18:22:27 +0100, Ralf Mardorf wrote:

Honestly ?  Get a break, go live in a tent or something.



> On Wed, 2014-01-15 at 16:53 +0000, Jarth Berilcosm wrote:
>> I'm using a news-reader and could not find the off-topic mailinglist.
> 
> That is a good example how the cheap crap called computer nowadays is
> misused, for laziness, carelessness, abyss of ignorance, to produce
> other cheap crap.
> 
>> Most importantly this list is not an opinion. Almost every listed point
>> has links to appropriate articles, threads and discussions
> 
> So it's nothing more than an opinion underpinned with some links,
> instead of objectivity and hard research. It takes seconds to underpin
> that all US presidents are shapeshifters, that there never was a
> Holocaust (no not Godwin). I try to point out that you can underpin
> every unreflected opinion by links.
> 
> There are only a few exceptions a computer is good for. The computer is
> the most overvalued tool humans invented.
> 
> And again, I like computers, but I don't overvalue computers = more
> satisfaction for me, than for you Jarth. Your disappointment is based on
> wrong points of departures.
> 
> Regards,
> Ralf
> 
> PS: d-community-offto...@lists.alioth.debian.org





-- 
jabadaba doooh ooh h


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/pan.2014.01.15.21.39...@yahoo.com

Re: sad but true, Linux sucks, a bit

[Jarth Berilcosm]

On Wed, 15 Jan 2014 17:29:01 +0100, Ralf Mardorf wrote:

I'm using a news-reader and could not find the off-topic mailinglist.

Sorry to say so but your reply sounds more like rambling than anything. 
I'll reply to the part i was able to comprehend.

Expectations ? Man, get a good night sleep.

Computers are cheap crap because they can be made to be cheap crap. The 
production proces permits this.

>> Most importantly this list is not an opinion. Almost every listed point
>> has links to appropriate articles, threads and discussions centered on
>> it, proving that I haven't pulled it out of my < expletive
>> >. And please always check your "facts".
> 
>> If you get an impression that Linux sucks - you are largely wrong. If I
>> had to create a list of Windows problems, it would be almost as long as
>> this one.
> 
> -
> http://linuxfonts.narod.ru/
why.linux.is.not.ready.for.the.desktop.current.html
> 
> Unworldly!
> 
> A lot of people think like you, not understanding that digital
> technology can't compare to analog technology. Sure, using a computer
> humans can do some things that can't be done manually or by analog
> technology, but most things are from much higher quality, when done with
> analog technology or manually. Multimedia, toolmaking, ... an endless
> list.
> 
> We use computers, because analog technology and handcrafted things are
> to expensive, the complete philosophy of human kind did go a step in the
> wrong direction.
> 
> I'm pro computers, already using Linux for more than 10 years, but
> started much earlier with computers in the late 80s.
> 
> It's a misunderstanding to guess that computer technology is that
> progressed. Computers are cheap crap. If you are aware that they are
> nothing but cheap crap, you can use them from an relatively objective
> point of view.
> 
> Less expectations = less disappointment
> 
> High expectations = high disappointment
> 
> IOW your opinion is subjective from an unworldly point of view.
> 
> Regards,
> Ralf
> 
> PS: You sent to the wrong list. I only Cc'ed to Debian user and sent to
> the off-topic list. I suspect replies should go to this list only.





-- 
jabadaba doooh ooh h


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/pan.2014.01.15.16.53...@yahoo.com

update flash

[Jarth Berilcosm]

If you have flash-player non-free installed make sure to run

 update-flashplugin-nonfree --install

 update-flashplugin-nonfree --status 

Flash Player version installed on this system  : 11.2.202.335
Flash Player version available on upstream site: 11.2.202.335


http://www.securityfocus.com/bid/58396 documents what's up with an old 
exploit used in new scenario's.




-- 
jabadaba doooh ooh h


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/pan.2014.01.15.15.56...@yahoo.com

Re: Disk is not visible with Debian 7.2 Live

[Jarth Berilcosm]

Does it still not happen when you boot form the 7.1 LiveCD ?

Maybe the 7.2 LiveCD does not load specific modules required for your set-
up. Validate with the package maintainers if required.

On Tue, 14 Jan 2014 17:28:48 -0500, Koji Tanaka wrote:

> Hi,
> 
> I'm having a issue that I cannot see disk with Debian 7.2 LiveCD boot.
> fdisk -l doesn't show anything, and I cannot partition the disk. It
> happens our old IBM dataplex servers. Did any one have the same/similar
> issue? It didn't happen till 7.1.
> 
> Thank you and best regards,
> Koji





-- 
jabadaba doooh ooh h


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/pan.2014.01.15.15.58...@yahoo.com

hpet increased min_delta_ns to

[Jarth Berilcosm]

May i ask for some feedback on the below.

This bug seems to pop back up again and again, i've found traces dating 
back to 2004 ... this seems to trigger or correlate with a plethora of 
issues. Is this a regression of some sort ?

On my system this bug >almost< exclusively occurs when i play a flash 
movie from any browser ( Iceweasel and Chromium tested ) 

Depending on boot-parameters there are gnome-shell slugdowns which 
require Xorg to be restarted or there is temporary slow-down which 
recovers after some time. Could be a few minutes.

I'm doing some tests on my system so don't panic when looking at the 
current cmdline, the mtrr settings seem to influence the frequence of 
occurence for this type of event. 

BOOT_IMAGE=/boot/vmlinuz-3.2.0-4-amd64 root=/dev/mapper/m4300-root ro 
quiet nomodeset enable_mtrr_cleanup mtrr_spare_regnr=4 elevator=deadline 
mtrr_gran_size=1M mtrr_chunk_size=16M video.allow_duplicates=1

I'm somewhat concerned this message might be an indication for a kernel-
level vulnerability but have little other indication but the flash-
playback trigger, and a surge of iritation-triggered paranoia.

It is also noticeable these messages are not-unique across systems and 
even distributions. When running from a vanilla self-compiled kernel 
these messages do not show but the same flash playback slugdown happens.

https://bugzilla.redhat.com/show_bug.cgi?id=989025

[  141.537195] CE: hpet increased min_delta_ns to 20113 nsec
[  141.538292] CE: hpet increased min_delta_ns to 30169 nsec
[  195.909019] CE: hpet increased min_delta_ns to 45253 nsec
[  195.909019] CE: hpet increased min_delta_ns to 67879 nsec

My Debian Wheezy system shows

Jan 12 13:30:26 localhost kernel: [ 2020.462393] CE: hpet increased 
min_delta_ns to 20113 nsec
Jan 12 14:18:19 localhost kernel: [ 2705.462317] CE: hpet increased 
min_delta_ns to 20113 nsec
Jan 12 14:18:24 localhost kernel: [ 2710.868851] CE: hpet increased 
min_delta_ns to 30169 nsec
Jan 12 21:19:52 localhost kernel: [ 1393.767958] CE: hpet increased 
min_delta_ns to 20113 nsec
Jan 12 23:10:09 localhost kernel: [ 2557.498114] CE: hpet increased 
min_delta_ns to 30169 nsec
Jan 12 23:10:53 localhost kernel: [ 2602.091457] CE: hpet increased 
min_delta_ns to 45253 nsec
Jan 13 00:58:04 localhost kernel: [ 5106.948096] CE: hpet increased 
min_delta_ns to 20113 nsec
Jan 13 15:42:46 localhost kernel: [  621.448579] CE: hpet increased 
min_delta_ns to 20113 nsec
Jan 13 15:44:57 localhost kernel: [  752.385203] CE: hpet increased 
min_delta_ns to 30169 nsec
Jan 13 15:44:57 localhost kernel: [  752.385441] CE: hpet increased 
min_delta_ns to 45253 nsec
Jan 13 19:11:49 localhost kernel: [  852.778250] CE: hpet increased 
min_delta_ns to 20113 nsec
Jan 14 12:40:05 localhost kernel: [  731.183563] CE: hpet increased 
min_delta_ns to 20113 nsec
Jan 14 18:51:30 localhost kernel: [21951.280044] CE: hpet increased 
min_delta_ns to 20113 nsec

Note the occurence for this bug does indicate but does not seem to 
trigger system slow-downs which seemed typical. A supposed work-around 
seems to be the boot parameter pci=nomsi , had it noted but not yet 
tested so far.

-- 
jabadaba doooh ooh h


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/pan.2014.01.15.15.53...@yahoo.com

sad but true, Linux sucks, a bit

[Jarth Berilcosm]

Looking back on using Linux as a desktop OS for almost 15 years we've 
seen tons of features added but not much in terms of 'bite'. 

Hardware support is a lot better but still sucks when it comes to 
consumer multi-media, gaming performance etc. 

Someone wrote down a well documented list on all this and more

http://linuxfonts.narod.ru/
why.linux.is.not.ready.for.the.desktop.current.html


What bothers me most on this list is the mention of uncountable 
regressions. Subjectively i came to the same conclusion as observed on 
various occasion even with commercial products. The word uncountable 
seems a bit harsh though not unimaginable. If so, this is bad, verry bad 
as it indicates a possible lack of oversight and follow-up or peer 
review. 

Let's just hope there's nothing lurking beneath the surface shall we. 
( Linux would not be generated by an AI would it not ? :D )

Fortunately there are some great projects ahead to improve the desktop, 
let's keep them fingers crossed one more time :-)

I'm honestly a bit amazed the desktop is not a priority for developers 
which often seem to be keen on serious gaming, at last the few I've met 
seemed to be. Maybe they have a secret Microsoft box in the house for 
that, or a console of sorts. Or an Apple.

Also, how many projects can one need for a specific purpose built on the 
libraries of a parent project providing 80% of the functionality. How 
much of these improvements go upstream, if at all ? I suspect the open-
and-free-model lacks the incentive to go forth with fusing projects to 
making delivery of targets more timely. 

Good developers are rare and should not be spread across so many 
projects. Good developers resolve bugs rather than building an economy 
upon them. A bug is a great marketing instrument for creating leverage, 
but it's also something stuck in the back of one's head in the long run.

Please consider the above with a grain of salt, i am not always known for 
a delicate choice of words.

Cheerio,

J.

-- 
jabadaba doooh ooh h


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/pan.2014.01.15.14.08...@yahoo.com

100% Fix for 64bit Flash with an Nvidia card

[Jarth Berilcosm]

People still suffering from flash playback issues such as sluggisch 
performance, hang-up's and others, i might have a fix for you.

Below you find the changes i made to my system to have Flash working 
flawlessly ( except for full-screen on this particular machine ) 
Please let me know if this works for you.

http://helpdesk.oxitech.info/doku.php?id=playing_flash_on_linux

Before these change came into effect flash played for 5 minutes then 
became sluggish and slowed down the whole GUI until the Display Manager 
was restarted. After i've played various +5 minutes movies and am now 
playing a move ( now at 1 hour 17 minutes ) … hence i consider the issue 
fixed. 

Right now, the speed of my Gnome3 session is faster than ever before.


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/l9so8b$b6p$1...@ger.gmane.org

Re: Debian gateway problem

[Jarth Berilcosm]

The only time i've seen this it was bad subnet / netmask configuration(s)

But it's working, so hey, good job ;-)

On Fri, 27 Dec 2013 01:26:12 +0900, mett wrote:

> On Thu, 26 Dec 2013 20:41:24 +1300 Richard Hector
>  wrote:
> 
>> On 26/12/13 18:27, mett wrote:
>> > Hi,
>> > 
>> > I'm using a debian box as a router and multiserver between my LAN and
>> > the internet.
>> > 
>> > Everything was working fine till yesterday when I put the box down
>> > for upgrading memory, for a few hours.
>> > 
>> > Right now, the external interface of the gateway is fully accessible
>> > from the net, and I do not have any problem with the different
>> > services I am providing to the outside(mail, webserver. and dns for
>> > the web servers).
>> > 
>> > The problem is on the LAN side, I can access some sites but not all
>> > the sites as I used to do.
>> > 
>> > For example, I can access the "Start page" search engine but not
>> > "Duckduckgo".
>> 
>> That's really strange.
>> 
>> 
>> > iptables -A FORWARD -i ppp0 -o eth0 -m state --state
>> > ESTABLISHED,RELATED -j ACCEPT
>> 
>> I assume that's really on one line?
> Yes
>> 
>> 
>> > # Don't forward from the outside to the inside.
>> > iptables -A FORWARD -i ppp0 -o ppp0 -j REJECT
>> 
>> That looks like outside to outside - you probably want "-i ppp0 -o
>> eth0"
>> 
>> Beyond that, I have no idea, sorry.
>> 
>> I'd be testing with tcpdump, as you have been. Possibly confirm that
>> the IP addresses you're getting from DNS inside and on the gateway are
>> the same?
>> 
>> Also perhaps try removing everything unrelated to the masquerading bit
>> from your script and see if that works, then add bits back in?
>> 
>> I also generally use a policy DROP rule (iptables -P INPUT DROP), which
>> I specify at the top of the file, rather than dropping through to a
>> DROP/REJECT rule at the end. That shouldn't make any difference,
>> though.
>> 
>> Richard
>> 
>> 
>> 
> Hi,
> 
> It seems I had many problems in fact...
> I couldn't check everything yet but now it's working
> 
> I did few dirty things like deleting all the rules one by one because
> even when moving the script somewhere else, it still acted when I
> restarted interfaces.
> 
> Finally I cleaned the original script,
> going one rule at a time.
> 
> #!/bin/sh
> 
> PATH=/usr/sbin:/sbin:/bin:/usr/bin
> 
> #
> # delete all existing rules.
> #
> iptables -F
> 
> # Always accept loopback traffic iptables -A INPUT -i lo -j ACCEPT
> 
> #log udp port 5060 iptables -A INPUT -i ppp0 -p udp --dport 5060 -j LOG
> --log-level debug
> 
> #asterisk iptables -A INPUT -i ppp0 -p udp --dport 5060 -j ACCEPT
> 
> #tor iptables -A INPUT -i ppp0 -p tcp --dport 9001 -j ACCEPT
> 
> #postfix iptables -A INPUT -i ppp0 -p tcp --dport 25 -j ACCEPT iptables
> -A INPUT -i ppp0 -p tcp --dport 587 -j ACCEPT
> 
> #dovecot iptables -A INPUT -i ppp0 -p tcp --dport 110 -j ACCEPT iptables
> -A INPUT -i ppp0 -p tcp --dport 995 -j ACCEPT iptables -A INPUT -i ppp0
> -p tcp --dport 143 -j ACCEPT iptables -A INPUT -i ppp0 -p tcp --dport
> 993 -j ACCEPT
> 
> #apache iptables -A INPUT -i ppp0 -p tcp --dport 80 -j ACCEPT iptables
> -A INPUT -i ppp0 -p tcp --dport 443 -j ACCEPT
> 
> #maradns iptables -A INPUT -i ppp0 -p udp --dport 53 -j ACCEPT
> 
> 
> # Allow established connections, and those not coming from the outside
> iptables -A INPUT -m state --state ESTABLISHED,RELATED -j ACCEPT
> iptables -A FORWARD -i ppp0 -o eth0 -m state --state ESTABLISHED,RELATED
> -j ACCEPT
> 
> # Allow outgoing connections from the LAN side.
> iptables -A FORWARD -i eth0 -o ppp0 -j ACCEPT
> 
> # Masquerade.
> iptables -t nat -A POSTROUTING -o ppp0 -j MASQUERADE
> 
> # Don't forward from the outside to the inside.
> iptables -A FORWARD -i ppp0 -o eth0 -j REJECT
> 
> # Enable routing.
> echo 1 > /proc/sys/net/ipv4/ip_forward
> 
> 
> I realized that if I use the following rules at the beginning,
> even wih the POSTROUTING at the end, then it doesn't work.
> 
> [iptables -t nat -F]
> 
> Also, this one doesn't get accepted by iptables
> 
> iptables -A INPUT -m state --state NEW -i ! ppp0 -j ACCEPT it's
> deprecated and you have to put it before the option,
> which I tried but the result scared me with words like nontracked, raw
> and similar.
> 
> I thought the ! was for "Not this one".
> 
> Anyway, I deleted this rule and changed the one with ppp0 to ppp0 for
> ppp0 to eth0.
> I thought it made sense ppp0 to ppp0 like "don't forward via this
> interface". Only INPUT to OUTPUT.
> 
> I'll have to check the whole more seriously cause I was planning to
> drop,as you advised, all the non accepted ones in the INPUT chain,
> before the masquerade problem happened.
>  
> Thanks for your comment.



-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: htt

Re: Adding an SSD

[Jarth Berilcosm]

Hi,

Take note, i have the same type of disk but a 256GB variant. If you plan 
on compiling software keep the 750GB disk in your system and do the 
compiling from/on that disk. 

If migrating a linux system i mostly copy /etc to a backup medium and 
that's it. Moving /home can be done at any time. 

One warning, take care with copying /etc/passwd /etc/passwd- /etc/group /
etc/group- /etc/shadow /etc/shadow- /etc/gshadow /etc/gshadow- on your 
freshly installed system. This can cause annoyances and at times trouble.

For all purposes, the most important part is partitioning the disk. Make 
sure the parition are aligned. This has a noticeable or even drastic 
impact on performance for the better, at least it had for me. This is no 
longer a worry if you plan on running and installing from Wheezy.

For sure, check out this page, yes Debian does have documentation ;-)

https://wiki.debian.org/SSDOptimization?
action=show&redirect=SSDoptimization

or check this page http://www.oxitech.info/helpdesk/tweaks.html

I attempt at dumbing down this kind of information into copy-past like 
information, this page has just been started and is far from complete but 
i assume it's enough to get you started.

I hope this answers some or most of your questions.



On Thu, 26 Dec 2013 12:32:58 -0500, Brad Alexander wrote:

> What is the best approach for adding an SSD to an existing system? This
> is on my desktop, with a 750GB spinning HD, and I am adding a 120GB
> Kingston ssdNow 300. Is the backup/nuke'n'pave the best or most reliable
> approach from a Debian perspective, or is there a way to partition the
> SSD and transfer the existing contents of the filesystems on the
> spinning HD to the SSD without overwriting things like the UUIDs of the
> partitions on the SSD?
> What are best practices now that SSDs (and the kernel's handling of
> SSDs)
> have theoretically gotten "better" over the last couple of years?
> 
> I have paid peripheral attention to the whole SSD discussion, but not
> enough to be an expert. Then, a coworker made me a deal I couldn't pass
> up,
> so I bought it. I've been looking through articles for about the last
> bit,
> but a lot of them are from 2012 or before, and I'm wondering if they are
> out of date, and if so, how far.
> 
> Finally, I plan to run encrypted partitions, with lvm containers within.
>>From what I have seen in my reading, this is not a problem for SSDs. The
> encryption layer sits above the filesystem writes, it doesn't actually
> write to the drive any more than regular writes. So the plan is, due to
> practical necessity, to have two encrypted volumes, and separate LVM
> containers within them. On the SSD, the system partitions, like /, /usr,
> /var, /tmp, /usr/local, etc. On the 750GB drive, /data, ~/.PlayOnLinux,
> /opt. I'm not sure which way to go with /home. There is plenty of room
> on the SSD for it, but I am trying to walk the line between the speed of
> the SSD and "beating it up." So any practical experience or advice from
> those who have done this would be appreciated.
> 
> Thanks,
> --b What is the best approach for
> adding an SSD to an existing system? This is on my desktop, with a 750GB
> spinning HD, and I am adding a 120GB Kingston ssdNow 300. Is the
> backup/nuke'n'pave the best or most reliable approach from a
> Debian perspective, or is there a way to partition the SSD and transfer
> the existing contents of the filesystems on the spinning HD to the SSD
> without overwriting things like the UUIDs of the partitions on the SSD?
> What are best practices now that SSDs (and the kernel's handling of
> SSDs) have theoretically gotten "better" over the last couple
> of years?
> 
> I have paid peripheral attention to the whole SSD discussion,
> but not enough to be an expert. Then, a coworker made me a deal I
> couldn't pass up, so I bought it. I've been looking through
> articles for about the last bit, but a lot of them are from 2012 or
> before, and I'm wondering if they are out of date, and if so, how
> far.
> 
> Finally, I plan to run encrypted partitions, with lvm
> containers within. From what I have seen in my reading, this is not a
> problem for SSDs. The encryption layer sits above the filesystem writes,
> it doesn't actually write to the drive any more than regular writes.
> So the plan is, due to practical necessity, to have two encrypted
> volumes, and separate LVM containers within them. On the SSD, the system
> partitions, like /, /usr, /var, /tmp, /usr/local, etc. On the 750GB
> drive, /data, ~/.PlayOnLinux, /opt. I'm not sure which way to go
> with /home. There is plenty of room on the SSD for it, but I am trying
> to walk the line between the speed of the SSD and "beating it
> up." So any practical experience or advice from those who have done
> this would be appreciated.
> Thanks,--b



-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://li

Re: FYI NVidia guide to improve performance and stability on Debian

[Jarth Berilcosm]

On Wed, 25 Dec 2013 03:57:19 +, Jarth Berilcosm wrote:

> Hi,
> 
> Because i've had my share of 'blues' with NVidia on Debian i've compiled
> a guide which documents what i believe to be a permanent fix for many
> issues.
> 
> http://www.oxitech.info/helpdesk/nvidia.html
> 
> Basically, the below resolves most if not all troubles.
> 
>   1. set nomodeset as a boot parameter in /etc/default/grub 2. do 
not
>   initialise your screen into a graphical mode ( no vga=
> option ) at boot
> 
> There is a somewhat detailed and hopefully correct explanation on the
> page.
> 
> I have the impression the latest driver from NVidia is more performant
> and stable as well. So i've installed that one. I'm not motivated to
> stick with the current version as right now my machine works like a
> dream since the past few hours.
> 
> 
> Let me know if the guide works for you.
> 
> 
> Best Regards,
> 
> J.

This is apparently not a win-all situation as, apparently, for more 
modern graphics cards these issue do not come into play.


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/l9hbdo$rrs$1...@ger.gmane.org

Re: Nvidia 210 with HDMI

[Jarth]

Op 25-12-13 19:02, Gábor Hársfalvi schreef:

Thanks for this - but sound still don't work with HDMI from the TV :S

What should I do now?


2013/12/25 Jarth Berilcosm mailto:ja...@yahoo.com>>

On Fri, 01 Nov 2013 10:59:10 +0100, Gábor Hársfalvi wrote:

> Hi,
>
> Could someone help about using audio with Nvidia 210 videocard
with Asus
> Motherboard with Nvidia onboard Soundcard?
>
> How to configure Alsa?
>
> Thanks Hi,Could someone
help
> about using audio with Nvidia 210 videocard with Asus
Motherboard with
> Nvidia onboard Soundcard?How to
> configure Alsa?
> Thanks

aptitude install alsa alsa-firmware-loaders alsa-tools alsa-tools-gui
alsa-utils alsamixergui

Should do all the work for you


--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
<mailto:debian-user-requ...@lists.debian.org>
with a subject of "unsubscribe". Trouble? Contact
listmas...@lists.debian.org <mailto:listmas...@lists.debian.org>
Archive: http://lists.debian.org/l9dc58$mar$4...@ger.gmane.org



Hi,

I'm not sure if i get your question correctly. Alsa is working correctly 
now ?


J.

--

- - -
ja...@yahoo.com

Jarth Berilcosm, because everything is as nearby as it is far away

Re: Grub2 menu editing

[Jarth Berilcosm]

On Wed, 25 Dec 2013 12:14:20 -0800, Gary Roach wrote:

> Would someone tell me how to edit the grub2 menu. I have over 10 items
> showing including versions of the OS that I don't even use anymore.
> Further, the items are out of order and I have to be careful when
> rebooting or the wrong OS gets loaded. I'm using Debian Wheezy and AMD
> 64 OS with an Intel i5750 processor.
> 
> Gary R.

Grub2 is a verry different beast, a custom boot menu can be generated 
with /etc/grub.d/40_custom

As a root user, to change the default boot item change

Be carefull to count from the top starting with 0 for the first line, if 
there is a recovery mode this counts as one more item too.

GRUB_DEFAULT=0 to the correct value in /etc/default/grub

then run 

update-grub2


All you need is here http://www.gnu.org/software/grub/grub.html


UPDATE-GRUB
(8) 
   
UPDATE-GRUB(8)

NAME
   update-grub, update-grub2 - stub for grub-mkconfig

SYNOPSIS
   update-grub

DESCRIPTION
   update-grub is a stub for running grub-mkconfig -o /boot/grub/
grub.cfg to generate a grub2 config file.

SEE ALSO
   grub-mkconfig(8)





-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/l9fj4r$cpp$2...@ger.gmane.org

Re: Nvidia package installation problems

[Jarth Berilcosm]

On Wed, 25 Dec 2013 08:46:21 +, Brad Rogers wrote:

> On Wed, 25 Dec 2013 00:17:17 + (UTC)
> Jarth Berilcosm  wrote:
> 
> Hello Jarth,
> 
>>Honestly, i don't know what's going with Debian lately. Wheezy looked
>>promising and has been quite a dissapointment when it comes to package
>>quality.
> 
> It's strange, isn't it;  I've not had any problems at all.  Admittedly,
> I'm not using Wheezy (I am always on 'testing'), but even so maybe you'd
> expect an issue or two.
> 
>>Golden hint include nomodeset in /etc/default/grub on the line
>>GRUB_CMD_LINE_DEFAULT="quiet splash nomodeset"
> 
> No "nomodeset" here, and everything seems fine.  Of course, I could set
> it and see what changes/improvements it makes.
> 
>>Make sure in /etc/modprobe.conf.d/nvidia.. there is a line stating
>>blacklist nouveau
> 
> Surely you mean '/etc/modprobe.d/' not '/etc/modprobe.conf.d/'?  The
> latter doesn't exist here.

Hi Brad,

Yeah, i lost focus due to frustrations and wrote down an incorrect 
pathname. Should have had some tea much sooner ;-)

What i've figured so far is nomodeset is mostly required by older 
hardware, this is an "NVIDIA Corporation G86M [Quadro FX 360M]" graphics 
card which is quite old. Almost unsupported.

My system logs were littered with segfault errors on gnome-shell and quite 
a few other programs. Since late last night there are no segfault errors 
anymore, it means I've done something right ;-) My system was left 
running for hours today with a few segfault sensitive applications 
running, no errors whatsoever, hurray.

I wrote a guide on my experience.

 http://www.oxitech.info/helpdesk/nvidia.html 

Right now, i hope I have not been deluding myself but at least it's a 
stable delusion so far :-)



-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/l9fhif$cpp$1...@ger.gmane.org

FYI NVidia guide to improve performance and stability on Debian

[Jarth Berilcosm]

Hi,

Because i've had my share of 'blues' with NVidia on Debian i've compiled 
a guide which documents what i believe to be a permanent fix for many 
issues.

http://www.oxitech.info/helpdesk/nvidia.html

Basically, the below resolves most if not all troubles.

1. set nomodeset as a boot parameter in /etc/default/grub
2. do not initialise your screen into a graphical mode ( no vga= 
option ) at boot

There is a somewhat detailed and hopefully correct explanation on the 
page.

I have the impression the latest driver from NVidia is more performant 
and stable as well. So i've installed that one. I'm not motivated to 
stick with the current version as right now my machine works like a dream 
since the past few hours.


Let me know if the guide works for you.


Best Regards,

J.


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/l9dl2v$6bl$1...@ger.gmane.org

Re: testiing and sid

[Jarth Berilcosm]

On Mon, 23 Dec 2013 23:16:51 -0500, erosenberg wrote:

> 1]  My apologies to those who noted that I was sending HTML emails.
>  Thunderbird is on the computer with no X windows. When I fix that
> computer the HTML emails will be a thing of the past.
> 2] In reference to fixing the the computer with the broken X windows,
> would it be reasonable to load testing on another hard drive, and then
> copy the appropriate directories from the broken distribution?  If it
> OK, which  directories should I copy?  Any precautions?
> TIA Ethan
> 
> 
> 1]  My apologies to those who noted that I was sending HTML
> emails.  Thunderbird is on the computer with no X windows. When I fix
> that computer the HTML emails will be a thing of the past. />2] In reference to fixing the the computer with the broken
> X windows, would it be reasonable to load testing on another hard drive,
> and then copy the appropriate directories from the broken distribution?
>  If it OK, which  directories should I copy?  Any
> precautions?TIA />Ethan

hmm, i'd advice against. 

aptitude reinstall packagename

dpkg-reconfigure -plow packagename

can work wonders


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/l9dq8e$lqe$1...@ger.gmane.org

Re: NVIDIA Problem?

[Jarth Berilcosm]

On Thu, 07 Nov 2013 00:26:12 -0500, erosenberg wrote:

> If you don't have an NVIDIA graphics card, then remove the nvidia
>  packages:
>  * glx-alternative-nvidia * nvidia-driver * libgl1-nvidia-glx and
>  instead, install libgl1-mesa-glx. This should allow your INTEL
> card
>  to do the 3D acceleration.
> 
> Darac -
> 
> Thanks.
> 
> I checked, no Nvidia device.
> 
> Did as above. Computer is now in infinite loop. Ask for a reboot,
> reboots and returns to the terminal login prompt.
> 
> TIA
> 
> Ethan
> 
>  
>   If you don't have an NVIDIA graphics card, then remove 
the nvidia   />
> packages:
>   * glx-alternative-nvidia
>   * nvidia-driver
>   * libgl1-nvidia-glx
> and instead, install libgl1-mesa-glx. This should allow your INTEL
> card
> to do the 3D acceleration.Darac - />Thanks.I checked, no Nvidia device.Did as
> above. Computer is now in infinite loop. Ask for a reboot, reboots and
> returns to the terminal login prompt.TIAEthan />

All my problem are mostly gone since i've uninstalled EVERY Debian Nvidia 
package. Have a look at the below.

If you want to know what card to use do something like

uname -m   
to know what architecture it is ( x86_64 = 64bit, x86 = 32bit)

lspci |grep -i vga
to know the model for sure

Get the latest driver from http://www.nvidia.co.uk/Download/index.aspx?
lang=en-uk , make sure to select the driver based on what you see from the 
output above. There is no specific driver for Debian or any other distro, 
just select Linux 32-bit or Linux 64-bit .. you only need ARM if it is a 
mobile device of some sort, or it's one of these chinese laptops.

You should now have file somewhat like NVIDIA-Linux-x86_64-331.20.run

chmod o+x NVIDIA-Linux-x86_64-331.20.run 
(or whatever your file is called)

stop the display manager if it is not stopped allready ( service gdm3 
stopor service lightdm stop )

If it doesn not complain about drivers allready installed just wait and 
mostly press ok or yes, you should have either the kernel-headers or 
linux-source installed ( make sure to do ln -s /usr/src/linux-source-3.2 
linux )

Now, it will take some time to finish. 

In the meantime you apply 'the magic' , in /etc/default/grub make sure 
nomodeset is present in the GRUB_CMD_LINUX="" or GRUB_CMD_LINUX_DEFAULT=""

It is possible there is already "quiet splash" present you can just 
append it like "quiet splash nomodeset"

If the installation finishes, you should do 

modinfo nvidia | grep version

version:331.20
vermagic:   3.2.0-4-amd64 SMP mod_unload modversions 

this should show the version like it does below the command, vermagic is 
the kernel version, there should also be a nvidia-uvm module

modinfo nvidia-uvm

filename:   /lib/modules/3.2.0-4-amd64/kernel/drivers/video/nvidia-
uvm.ko
supported:  external
license:MIT
depends:nvidia
vermagic:   3.2.0-4-amd64 SMP mod_unload modversions 

take note /etc/modprobe.conf.d/nvidia-kernel-common.conf
should look like the below

alias char-major-195* nvidia
options nvidia NVreg_DeviceFileUID=0 NVreg_DeviceFileGID=44 
NVreg_DeviceFileMode=0660
blacklist nouveau

If it is so, it should now be safe to reboot your computer. You won't 
believe the speed at which your machine will work on your desktop.


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/l9dc25$mar$3...@ger.gmane.org

Re: Nvidia 210 with HDMI

[Jarth Berilcosm]

On Fri, 01 Nov 2013 10:59:10 +0100, Gábor Hársfalvi wrote:

> Hi,
> 
> Could someone help about using audio with Nvidia 210 videocard with Asus
> Motherboard with Nvidia onboard Soundcard?
> 
> How to configure Alsa?
> 
> Thanks Hi,Could someone help
> about using audio with Nvidia 210 videocard with Asus Motherboard with
> Nvidia onboard Soundcard?How to
> configure Alsa?
> Thanks

aptitude install alsa alsa-firmware-loaders alsa-tools alsa-tools-gui 
alsa-utils alsamixergui

Should do all the work for you


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/l9dc58$mar$4...@ger.gmane.org

Re: Debian Wheezy Compromised - www-data user is sending 1000 emails an hour

[Jarth Berilcosm]

On Mon, 23 Dec 2013 18:42:24 +0100, Gilles Mocellin wrote:

> Le 23/12/2013 15:30, Raffaele Morelli a écrit :
>> 2013/12/14 Lukasz Szybalski > >
>>
>>
>> [...]
>>
>>
>> root should not own files served by apache for any reason, that's
>> really "dangerous"!
>> you should never do that...
> 
> Excuse-me, but I think you're wrong.
> The only reason I see where a file served by a web server must not be
> root is if it's suid and the web server has the rights to write to it
> (by the group membership).
> 
> As a security measure, I preach the opposite : all files are root (or
> another user, not used by the web server).
> For the directories and files that have to be modified by the
> application and so by the web server, I use a group membership
> (www-data) with write privileges for the group.
> 
> Like this, if someone find a hole in the web app, it can make it execute
> something with the user running the web server, and can not write to the
> files served by the web server (except those specified above, using the
> group www-data).
> And so, it can not modify application files (php scripts...) and make it
> do what they want (send spam, propagate...).
> 
> 
>   
> 
>   
>   
> Le 23/12/2013 15:30, Raffaele Morelli a
>   écrit :
> 
>  cite="mid:CAD4guxO2TOCk4a78SS9EyhJUz1v-
zcf2njcdoqx5eieerro...@mail.gmail.com"
>   type="cite"> 
> 
>   2013/12/14 Lukasz Szybalskidir="ltr">< href="mailto:szybal...@gmail.com";
> target="_blank">szybal...@gmail.com>
> 
>   
> 
>   
> 
>   
>  
> 
>   
> 
>   
> 
>   
> 
>   
> 
> [...]
> 
>   
> 
>   
> 
> 
>  cite="mid:CAD4guxO2TOCk4a78SS9EyhJUz1v-
zcf2njcdoqx5eieerro...@mail.gmail.com"
>   type="cite"> 
> 
>   
> root should not own files served by apache for any
>   reason, that's really "dangerous"!
> you should never do that...
>   
> 
>   
> 
> 
> Excuse-me, but I think you're wrong.
> The only reason I see where a file served by a web server must not
> be root is if it's suid and the web server has the rights to write
> to it (by the group membership).
> 
> As a security measure, I preach the opposite : all files are root
> (or another user, not used by the web server).
> For the directories and files that have to be modified by the
> application and so by the web server, I use a group membership
> (www-data) with write privileges for the group.
> 
> Like this, if someone find a hole in the web app, it can make it
> execute something with the user running the web server, and can not
> write to the files served by the web server (except those specified
> above, using the group www-data).
> And so, it can not modify application files (php scripts...) and
> make it do what they want (send spam, propagate...).
> 
>   
> 


This is a long standing 'hot' topick, it is even a legendary page on the 
apache web site ...

Basically you're both right. On the one hand if a file is owned by root 
it cannot be easily overwritten if it is to be accessed from another 
proces, on the other hand if the process running as root get's 
compromised you're a looong way from home.

It is a best practice, by default, in Debian to not run a web-server as a 
privileged user. As such any compromise will execute code as this user, 
which might as well be privilege escalation code but it's a barrier of 
some kind to start with.

What you'd need is a wheel group and setfacl and getfacl for fine grained 
access control. Personally i allways set files to the least possible 
privilege and if i can block world from one or more of rwxs i will.




-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/l9dad7$mar$2...@ger.gmane.org

Re: Nvidia package installation problems

[Jarth Berilcosm]

Hi,

I've ran into the same issues on an old NVidia Quadro FX 360M.

Honestly, i don't know what's going with Debian lately. Wheezy looked 
promising and has been quite a dissapointment when it comes to package 
quality.

Golden hint include nomodeset in /etc/default/grub on the line 
GRUB_CMD_LINE_DEFAULT="quiet splash nomodeset"

This will greatly improve the speed and stability of your system.

Make sure in /etc/modprobe.conf.d/nvidia.. there is a line stating 
blacklist nouveau

What i've done is to download the latest nvidia driver ( long life version 
) and run the installer, make sure to remove ANY debian nvidia packages.

So far i had to ditch gdm as login manager as it crashed and crashed, 
using lightdm now.

J. 

On Tue, 24 Dec 2013 10:02:42 -0500, Jon N wrote:

> On Mon, Dec 23, 2013 at 11:37 AM, Brad Rogers  wrote:
> 
> <---snip--->
> 
>>>have any trouble doing that.  But I don't want to have a package from
>>>repository still installed at the same time as the nvidia download.
>>
>> There are problems with that as you can imagine.  Debian packages can
>> get confused by a previous nvidia installation.  I don't know whether
>> the same is true the other way round, but better safe than sorry.
>>
>> I include here a list of all nvidia specific packages I have installed,
>> for the sake of comparison with your own list:
>>
>> glx-alternative-nvidia_0.4.1 libgl1-nvidia-glx_319.76-1
>> libnvidia-ml1_319.76-1 libvdpau1_0.7-1 libxnvctrl0_319.72-1
>> libxnvctrl0_319.72-1 libxnvctrl0_319.72-1 nvidia-driver_319.76-1
>> nvidia-kernel-dkms_319.76-1 nvidia-settings_319.72-1
>> nvidia-alternative_319.76-1 nvidia-xconfig_319.72-1
>> nvidia-installer-cleanup_20131102+1 *
>> nvidia-kernel-common_20131102+1 nvidia-kernel-source_319.76-1
>> nvidia-support_20131102+1 xserver-xorg-video-nouveau_1.0.10-1
>> xserver-xorg-video-nvidia_319.76-1
>>
>> * handy for ensuring the nvidia downloaded module stuff doesn't
>>   conflict with the Debian packages.
> 
> Before I gave up I ran 'dpkg-reconfigure with each package name above
> hoping that fix something, or at least generate an error message that
> would give some clue.  But, no luck.  So I uninstalled it all and
> rebooted.  My desktop came up fine with (I think) the vesa driver.
> 
> But, I often watch HD shows through MythTV, which didn't work well at
> all with the vesa driver, nor with the nouveau driver.  So, back to the
> downloaded nvidia driver.  Which had the exact same problem as the
> nvidia package loaded through the repository, X would not load.  Ouch, I
> hadn't expected that.
> 
> Poking around again I noticed a line in Xorg.0.log:
> 
> "Kernel command line: BOOT_IMAGE+/vmlinux-3.11.-2-686-pae
> root=/dev/mapper/MyVG-root_LV ro nomodeset nouveau.modeset=0"
> 
> I did notice that earlier, but wasn't worried about nouveau being in
> there because it's blacklisted.  But with these continuing problems I
> guess it's worth looking into.  I edited it out in /etc/defaults/grub
> and ran 'update-grub'.  That was it!  I am really puzzled how it got
> there.  It seem strange to me that uninstalling the downloaded nvidia
> drivers (which is the first thing I did when this all started) would add
> that.  None of the 'grub.*' files in /etc/defaults was newer than 2012,
> but it was in there, suggesting it was always in the command line.  So
> why was it a problem now???  As usual, I figure I must have missed
> something, or done something dumb.  But, at least it works!
> 
> Oh, and one of my reasons for changing in the first place was to have
> the driver automatically configured for each new kernel update that was
> installed.  Apparently I did not have 'dkms' installed before, but it
> got left over.  The nvidia driver offered to register with it for
> automatic updates.  So I still get the main reason for changing.
> 
> Thanks for all your help,
> Jon



-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/l9d86d$mar$1...@ger.gmane.org