Re: Extending fluxbox menu with a script.

[Scott Ferguson]

On 23/11/13 06:14, Sharon Kimble wrote:
> On Fri, 22 Nov 2013 12:15:21 +
> Sharon Kimble  wrote:
> 
>> On Fri, 22 Nov 2013 09:09:23 +1100
>> Scott Ferguson  wrote:
>>
>>> On 22/11/13 08:50, Scott Ferguson wrote:
 On 22/11/13 06:39, Scott Ferguson wrote:
>>> 

 Try #2 :/
>>>
>>> Try #3 (no sleep last night - trees and power lines down across the
>>> property in last nights storms)  Sorry.
>>> This time I remembered to escape those brackets. Please test this -
>>> I can only check the script works, can't check if mmaker likes it.
>>>

 Ignore the above - that echo won't reliably create multiple lines,
 printf will.

 Try this which will:-
>>>
>>> echo "
>>> #!/bin/bash
>>> # .fmenu
>>> mv ~/.fluxbox/menu{,-$(date +%Y%m%d-%R)}
>>> mmaker fluxbox -f
>>> printf "\t[submenu] \(My
>>> Menu\)\n\t[include]\(~/.fluxbox/usermenu\)\n\t[end]\n\t[separator]"
> ~/.fluxbox/menu" > ~/.fmenu
>>>


 The above will:-
 create a script ~./.fmenu

 Running ~/.fmenu will:-
 mv your existing ~/.fluxbox/menu to ~/.fluxbox/menu-mmdd-hh:mm
 create a new ~/.fluxbox/menu
 append your submenu to it


 If you want to remove the last [end] tag from the main menu (as
 suggested by Linux Fan try this:-
>>>
>>> echo "
>>> #!/bin/bash
>>> # .fmenu
>>> mv ~/.fluxbox/menu{,-$(date +%Y%m%d-%R)}
>>> mmaker fluxbox -f
>>> sed -i 's/\[end]//g' ~/.fluxbox/menu;sed -i '/^\s*$/d'
>>> ~/.fluxbox/menu printf "\t[submenu] \(My
>>> Menu\)\n\t[include]\(~/.fluxbox/usermenu\)\n\t[end]\n\t[separator]"
> ~/.fluxbox/menu" > ~/.fmenu
>>>
>>>
>>>
>>> Someone more awake than I can probably make that double invocation
>>> of sed into a single call.
>>>
>> Morning Scott.
>> Thanks for this, I hope you slept better? This is what I currently
>> have -
>>
>> #!/bin/bash
>> # .fmenu
>> mv ~/.fluxbox/menu{,-$(date +%Y%m%d-%R)}
>>
>> mmaker fluxbox -f
>>
>> sed -i 's/\[end]//g' ~/.fluxbox/menu;sed -i '/^\s*$/d' ~/.fluxbox/menu
>>
>> printf '\t[submenu] \(My
>> Menu\)\n\t[include]\(~/.fluxbox/usermenu\)\n\t[end]\n\t[separator]'
 ~/.fluxbox/menu" >~/.fmenu
>>
>> and the double sed line works okay, but its failing at the 'printf'
>> line saying -
>> 'tryitout
>> /home/boudiccas/bin/tryitout: line 21: /home/boudiccas/.fluxbox/menu 
>>
>>> ~/.fmenu'
>>
>> NB - my working script is always called 'tryitout', just whilst I'm
>> developing something. 
>>
>> The new menu is created without the two [end] at its end, but there is
>> nothing from 'printf' at all.
>>
>> Sorry
>> Sharon.
>>
> I've got it working with this line -
> mv ~/.fluxbox/menu{,-$(date +%Y%m%d-%R)}; mmaker fluxbox -f;perl -0777
> -pi -e 's/(.*)\[end]/$1/s;s/(.*)\[end]/$1/s;s/^\s*\n//gm'
> ~/.fluxbox/menu


There should be only one [end] tag to strip out at this point - other
than that the perl is fine. It's the next line that adds the second
[end] tag (the one you don't want to remove).

*Tip:* append "-x" to the first line of your script followed by "trap
read debug" to debug the script line-by-line. You'll need to press Enter
to process each line. Use cat and another terminal window and watch the
changes to the relevant files.

e.g.:-
#/bin/bash -x
# ~/bin/tryitout
trap read debug
[script goes here]



>;printf '\t[end]\n\t[separator]\n\t[submenu] (My
> Menu)\n\t[include] (~/.fluxbox/usermenu)\n\t[end]\n\t[end]'
>>> ~/.fluxbox/menu
> 
> Thanks for all those who offered solutions.
> 
> Sharon.
> 


-- 
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/529036db.6040...@gmail.com

Re: CIFS mount hangs

[Scott Ferguson]

This is why some (me) people dislike top posters and prefer to ignore
them over posters who make the effort to interleave their replies. Not
only does it require extra work to read the post and put it into context
- it 'seems' to also encourages posters to *not* read what they are
replying to. I could be wrong about that - but it coincides with
occasions when I ask for information that is not supplied after asking.
That mouse thing moves the cursor ;)


On 23/11/13 01:45, assm...@skygate.de wrote:
> Hi,
> 
> so I did some testing with a clone of the machine restored to the
> state before the upgrade to wheezy.
> 
> Squeeze:
> - Mount the share
> - Disable the share on windows host
> - Try to access the share with 'ls' results in 'no such device'
> - Enable the share on windows host
> - Try to access the share with 'ls' is successful
> 
> Wheezy:
> - Mount the share
> - Disable the share on windows host
> - Try to access the share with 'ls' results in 'Server ... has not
> responded in 300 seconds' .. and an error from ls after well 300
> seconds i would say. 

There's your most likely problem (read on).

> Until this the shell hangs and the access can not be interupted with
> CTRL-C.
> - Enable the share on windows host
> - Try to access the share with 'ls' is successful but shows an empty
> dir.
> - Remount brings the content back
> - Connection is lost after some time of inactivity (share is still
> available under squeeze)
> 
> This is the behavoiur when I manually disable the share. But in 'real
> life' the share is not diabled by anyone. It is still visible in the
> windows network environment.

Do you mean cifs (e.g. smbclient)? Or Windows(C) environment?  There's a
major difference.

> 
> I have now tried this:
> http://www.mail-archive.com/linux-cifs@vger.kernel.org/msg06161.html

http://www.mail-archive.com/linux-cifs@vger.kernel.org/msg06173.html is
also interesting - though I'd still check the timeout settings on the
samba server/s first (instead of cifs mount).

> 
> Will see how this will work out.
> 
> Thanks so far!
> 
> Tobias
> 
>> On 21/11/13 22:39, assm...@skygate.de wrote:
>>> Hi,
>>>



> 
>> How does "$ testparm -v" on the new box compare with the same from the
>> box that did work?

??   Did you read that?

> 
>>>
>>> Any ideas to debug and understand are welcome.
> 
>> The output of:
>> $ testparm -v

?? Did you read that?

I'd suggest you look at the timeout values. Just a thought. :)

> 
>> Plus the settings used on the boxes that host the samba resources might
>> be informative.

Might be informative?
I meant "extremely useful"
Sorry.

>> Do you have any logs from the other boxes?

??

> 
>>>


Kind regards


-- 
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/529033f0.7070...@gmail.com

Re: Extending fluxbox menu with a script.

[Scott Ferguson]

On 23/11/13 01:13, Sharon Kimble wrote:
> On Fri, 22 Nov 2013 12:15:21 +
> Sharon Kimble  wrote:
> 
>> On Fri, 22 Nov 2013 09:09:23 +1100
>> Scott Ferguson  wrote:
>>
>>> On 22/11/13 08:50, Scott Ferguson wrote:
 On 22/11/13 06:39, Scott Ferguson wrote:
>>> 

 Try #2 :/
>>>
>>> Try #3 (no sleep last night - trees and power lines down across the


>>>
>> Morning Scott.
>> Thanks for this, I hope you slept better? This is what I currently
>> have -
>>
>> #!/bin/bash
>> # .fmenu
>> mv ~/.fluxbox/menu{,-$(date +%Y%m%d-%R)}
>>
>> mmaker fluxbox -f
>>
>> sed -i 's/\[end]//g' ~/.fluxbox/menu;sed -i '/^\s*$/d' ~/.fluxbox/menu
>>
>> printf '\t[submenu] \(My
>> Menu\)\n\t[include]\(~/.fluxbox/usermenu\)\n\t[end]\n\t[separator]'
 ~/.fluxbox/menu" >~/.fmenu
>>
>> and the double sed line works okay, but its failing at the 'printf'
>> line saying -
>> 'tryitout
>> /home/boudiccas/bin/tryitout: line 21: /home/boudiccas/.fluxbox/menu 
>>
>>> ~/.fmenu'
>>
>> NB - my working script is always called 'tryitout', just whilst I'm
>> developing something. 
>>
>> The new menu is created without the two [end] at its end, but there is
>> nothing from 'printf' at all.
>>
>> Sorry
>> Sharon.
>>
> I've been doing some more testing and now got the 'submenu' being
> generated at the end, which is good. But, the sed lines are also
> stripping out *all* of the [end] lines which separate the sections of
> the menu, which are needed for it to function properly. So how can we
> get it to just strip out the two [end] at the end of the main menu, and
> leave all of the other [end] in the script intact please?

Here's what *should* happen when the created script ~/.fmenu is run:-

1. archive the existing menu
$ mv ~/.fluxbox/menu{,-$(date +%Y%m%d-%R)}

2. Create new menu
$ mmaker fluxbox -f

3. Strip the first, and at this stage *only*, [end] tag from the new menu
$ sed -i 's/\[end]//g' ~/.fluxbox/menu

4. Remove the empty line (and tab) from the new menu (left from where
the end tag was stripped out)

$ sed -i '/^\s*$/d' ~/.fluxbox/menu

5. Create the submenu (this step creates the '2nd' end tag)
$ printf '\t[submenu] \(My
Menu\)\n\t[include]\(~/.fluxbox/usermenu\)\n\t[end]\n\t[separator]'
~/.fluxbox/menu" >~/.fmenu


If the script strips out both [end] tags it's because steps 3 and 4 are
being run after step 5 (or their wouldn't be two [end] tags to strip out.


> 
> Thanks
> Sharon.
> 

Kind regards


-- 
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/52903005.8040...@gmail.com

Re: Extending fluxbox menu with a script.

[Scott Ferguson]

On 22/11/13 23:15, Sharon Kimble wrote:
> On Fri, 22 Nov 2013 09:09:23 +1100
> Scott Ferguson  wrote:
> 
>> On 22/11/13 08:50, Scott Ferguson wrote:
>>> On 22/11/13 06:39, Scott Ferguson wrote:
>> 
>>>
>>> Try #2 :/
>>
>> Try #3 (no sleep last night - trees and power lines down across the
>> property in last nights storms)  Sorry.
>> This time I remembered to escape those brackets. Please test this - I
>> can only check the script works, can't check if mmaker likes it.
>>




> Thanks for this, I hope you slept better? This is what I currently
> have -
> 
> #!/bin/bash
> # .fmenu
> mv ~/.fluxbox/menu{,-$(date +%Y%m%d-%R)}
> 
> mmaker fluxbox -f
> 
> sed -i 's/\[end]//g' ~/.fluxbox/menu;sed -i '/^\s*$/d' ~/.fluxbox/menu
> 
> printf '\t[submenu] \(My
> Menu\)\n\t[include]\(~/.fluxbox/usermenu\)\n\t[end]\n\t[separator]'
>>> ~/.fluxbox/menu" >~/.fmenu
> 
> and the double sed line works okay, but its failing at the 'printf'
> line saying -
> 'tryitout
> /home/boudiccas/bin/tryitout: line 21: /home/boudiccas/.fluxbox/menu 
> 
>> ~/.fmenu'
> 
> NB - my working script is always called 'tryitout', just whilst I'm
> developing something. 


I know nothing of 'tryitout', neither does the script (~/.fmenu) :)
That is why fprint fails.

Edit ~/bin/tryitout so it contains:-
#!/bin/bash
# ~/bin/tryitout
mv ~/.fluxbox/menu{,-$(date +%Y%m%d-%R)}
mmaker fluxbox -f
printf "\t[submenu] \(My
Menu\)\n\t[include]\(~/.fluxbox/usermenu\)\n\t[end]\n\t[separator]




Kind regards


-- 
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/52902e04.8080...@gmail.com

Re: MIT discovered issue with gcc

[Andrew McGlashan]

Hi,

The following link shows the issue in a nutshell:

http://www.securitycurrent.com/en/research/ac_research/mot-researchers-uncover-security-flaws-in-c

[it refers to the PDF that I mentioned]

-- 
Kind Regards
AndrewM


-- 
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/52900637.1080...@affinityvision.com.au

MIT discovered issue with gcc

[Andrew McGlashan]

Hi,

I understand that Debian has a bunch of vulnerabilities as described in
the following PDF.

http://pdos.csail.mit.edu/~xi/papers/stack-sosp13.pdf

Just a small quote:

"This paper presents the first systematic approach for
reasoning about and detecting unstable code. We implement
this approach in a static checker called Stack, and
use it to show that unstable code is present in a wide
range of systems software, including the Linux kernel and
the Postgres database. We estimate that unstable code
exists in 40% of the 8,575 Debian Wheezy packages that
contain C/C++ code. We also show that compilers are
increasingly taking advantage of undefined behavior for
optimizations, leading to more vulnerabilities related to
unstable code."

This looks very serious indeed, but a quick search of Debian mailing
lists didn't show anything being acknowledged for this issue should
Debian users be concerned?

-- 
Kind Regards
AndrewM


-- 
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/52900522.9040...@affinityvision.com.au

Re: NAS hdd's in Debian desktop computer?

[Jon N]

On Nov 22, 2013 7:42 PM, "Kelly Clowers"  wrote:
>
> On Fri, Nov 22, 2013 at 5:13 AM, Jon N  wrote:
> 
>
> >
> > Which leads to my questions.  If the NAS drive is installed in a
> > desktop computer running Debian Linux what is the result of this?
> > Will this command just be ignored?  Will the shorter time the drive
> > spends trying to perform whatever operation it's having a problem with
> > cause a problem if the OS does not have a way of dealing with this?
> > How else will will this affect my system?
> >
> > In my online searches I have seen many results dealing with using
> > desktop drives in NAS's, but nothing (so far) that addresses the issue
> > the other way around.  So any light you can shed on this will be
> > gratefully appreciated.
> >
>
> Both mdadm and a real HW RAID controller will kick
> a drive out of the array if it takes too long to
> respond. Mdadm is by default set higher than HW
> RAID, though. Either way, it just means less chance
> of a false positive drive failure.

It won't be in a RAID, I was just thinking of using it as a regular hdd.
Since there won't be RAID controller, and as far as I know Mdadm won't be
running (does it run if I don't set up a RAID?) I was wondering how it, or
if, it would affect the system.

Thanks,
Jon

Re: NAS hdd's in Debian desktop computer?

[Kelly Clowers]

On Fri, Nov 22, 2013 at 5:13 AM, Jon N  wrote:
​​

>
> Which leads to my questions.  If the NAS drive is installed in a
> desktop computer running Debian Linux what is the result of this?
> Will this command just be ignored?  Will the shorter time the drive
> spends trying to perform whatever operation it's having a problem with
> cause a problem if the OS does not have a way of dealing with this?
> How else will will this affect my system?
>
> In my online searches I have seen many results dealing with using
> desktop drives in NAS's, but nothing (so far) that addresses the issue
> the other way around.  So any light you can shed on this will be
> gratefully appreciated.
>

​Both mdadm and a real HW RAID controller will kick
a drive​ out of the array if it takes too long to
respond. Mdadm is by default set higher than HW
RAID, though. Either way, it just means less chance
of a false positive drive failure.

​Cheers,
Kelly​

Re: Script to tell if Qpopper is running.

[Pol Hallen]

Has anyone written a script that will run under a cron job that checks
to make sure that the pop3 server is running and if not will restart it?


apt-get install mon

Pol


--
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/528fe336.1050...@fuckaround.org

Re: Script to tell if Qpopper is running.

[Sharon Kimble]

On Fri, 22 Nov 2013 13:13:54 -0800 (PST)
Account for Debian group mail  wrote:

> 
> 
> On Fri, 22 Nov 2013, Jerry Stuckle wrote:
> 
> > On 11/22/2013 3:54 PM, Account for Debian group mail wrote:
> >> >> >> Hello all,
> >> >> Once in a while the Qpopper on our mail server will just die. I
> >> >> have to
> >> go in and issue a "/etc/init.d/openbsd-inetd restart" and it will
> >> be backup and running.
> >> >> Has anyone written a script that will run under a cron job that
> >> >> checks
> >> to make sure that the pop3 server is running and if not will
> >> restart it?
> >> >> >> Thanks,
> >> >> Ken
> >> >> >
> > The bigger question would be - why is it dying?  I think I'd try to
> > figure > that out instead.
> >
> > I've been running qpopper for > 10 years, and never had it "just
> > die". It's > been 100% solid.
> >
> > Jerry
> 
> Jerry,
> 
> Trying to figure out why it dies once a year (or so) on a machine
> that is processing a lot of mail is not a question of why but rather
> get the pop3 server back up now.
> 
> I've tried to write a little script using expect, but my programing
> skill, at last are not that good anymore.
> 
> I have such scripts running for many programs on my computers that
> check to make sure everything is running as it should and if there is
> a problem restart that program.
> 
> So once again I ask, does anyone have such a script for their pop3
> server?
> 
Ken.
If you've already got working scripts for checking various things
then you could try adapting one to fulfil your new purpose. That
shouldn't be too hard, and would be better because you would know
*exactly* what everything in it was doing,

Sharon. 



signature.asc
Description: PGP signature

Re: Script to tell if Qpopper is running.

[Account for Debian group mail]

On Fri, 22 Nov 2013, Jerry Stuckle wrote:


On 11/22/2013 3:54 PM, Account for Debian group mail wrote:



Hello all,

Once in a while the Qpopper on our mail server will just die. I have to
go in and issue a "/etc/init.d/openbsd-inetd restart" and it will be
backup and running.

Has anyone written a script that will run under a cron job that checks
to make sure that the pop3 server is running and if not will restart it?


Thanks,

Ken




The bigger question would be - why is it dying?  I think I'd try to figure 
that out instead.


I've been running qpopper for > 10 years, and never had it "just die". It's 
been 100% solid.


Jerry


Jerry,

Trying to figure out why it dies once a year (or so) on a machine that is 
processing a lot of mail is not a question of why but rather get the pop3 
server back up now.


I've tried to write a little script using expect, but my programing skill,
at last are not that good anymore.

I have such scripts running for many programs on my computers that check 
to make sure everything is running as it should and if there is a problem 
restart that program.


So once again I ask, does anyone have such a script for their pop3 server?

Thanks,

Ken


--
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/pine.lnx.4.64.1311221303070.14...@mail.pcez.com

Re: Script to tell if Qpopper is running.

[Jerry Stuckle]

On 11/22/2013 3:54 PM, Account for Debian group mail wrote:



Hello all,

Once in a while the Qpopper on our mail server will just die. I have to
go in and issue a "/etc/init.d/openbsd-inetd restart" and it will be
backup and running.

Has anyone written a script that will run under a cron job that checks
to make sure that the pop3 server is running and if not will restart it?


Thanks,

Ken




The bigger question would be - why is it dying?  I think I'd try to 
figure that out instead.


I've been running qpopper for > 10 years, and never had it "just die". 
It's been 100% solid.


Jerry


--
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/528fc56a.5050...@attglobal.net

Script to tell if Qpopper is running.

[Account for Debian group mail]

Hello all,

Once in a while the Qpopper on our mail server will just die. I have to go 
in and issue a "/etc/init.d/openbsd-inetd restart" and it will be backup 
and running.


Has anyone written a script that will run under a cron job that checks to 
make sure that the pop3 server is running and if not will restart it?



Thanks,

Ken


--
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/pine.lnx.4.64.1311221249430.14...@mail.pcez.com

Read clipboard?

[Antispammbox-debian]

Hi all


On my Squeeze using parcellite clipboard manager.
Do know if it is possible, through a bash program, 
or compiled with gcc/mingw-linux, read the contents 
of the clipboard?


Thanks

Regards


--
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/334AAB30881E4BA99C63BD4849A5DEC6@CentrinoDuo

Re: QT through ssh tunnel

[Georgi Naplatanov]

On 11/22/2013 03:11 PM, Dan wrote:

Hi,

I have gnome and I use a QT application  (virtualbox) with a ssh
tunnel in the same computer. I use a different user than the user that
I use with Gnome.

The problem is that I get the old QT theme (Windows 95/motif style)
when I run virtualbox with a ssh tunnel. In the other hand, if I run a
GTK application (ex gedit) with a ssh tunnel I do not have that
problem. It is not a big deal, but i would nice to have the fancy QT
theme.

If I do the same thing in my laptop I get the right QT theme in
virtualbox using a ssh tunnel. I have wheezy and gnome in both
computers. I do not know why I have a different behaviour.

Thanks,
Dan



Hi Dan,

try to delete all (old) configuration files in user's home directory like

rm -Rf ~/.kde*

I had an issue with Skype on Wheezy (amd64) and the problem was due an 
old configuration file/directory, I can not remember exact name, but I 
guess it was something like .kde4*


HTH

Best regards
Georgi


--
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/528fbef3.3080...@oles.biz

Re: NAS hdd's in Debian desktop computer?

[Jon N]

On Fri, Nov 22, 2013 at 9:14 AM, Dan Ritter  wrote:

> For MythTV storage, you either value the video data enough to
> have multiple copies, or you don't.
>
> (I assume you value the database enough to run the standard
> backup job daily, and store it on a disk that is not running
> your database.)

Although I would definitely not like to loose the recordings (which
would be about all that would be on this disk) I have never considered
hdd's inexpensive enough to back up that much data.  The database is
though, and much smaller of course.  There is a script that makes
backups that are on a different drive than the database.  It just
occurred to me that this backup is small enough that I could put a
copy in the cloud also, a little redundancy wouldn't hurt.
>
> If you keep multiple copies of the video data on different disks, then
> it will be safe against a disk failure. If you don't, it won't.

True enough.  Just to be clear, I was not asking about backup media
when I referred to hdd's described as a NAS drives, but for use as my
main storage.  I assume at this point you were talking about backup
because of my concern over hdd failure.  Since I do a lousy job of
backing up much of anything I will have to rethink my storage plans
all over again.  If I don't backup all the video's I would certainly
need much less space to do it.

> Either way, there's no reason not to use NAS rated disks.

Good.  That was the main question.  Do you know if Linux (Debian or
not) would do something different based on the "(...) Error Recovery
Control" message than it would do otherwise?

Thanks,
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/cancvmg2osdo7mreqyhaxyyaps0unou2ckmg8d2mifjwzvda...@mail.gmail.com

Re: Extending fluxbox menu with a script.

[Sharon Kimble]

On Fri, 22 Nov 2013 12:15:21 +
Sharon Kimble  wrote:

> On Fri, 22 Nov 2013 09:09:23 +1100
> Scott Ferguson  wrote:
> 
> > On 22/11/13 08:50, Scott Ferguson wrote:
> > > On 22/11/13 06:39, Scott Ferguson wrote:
> > 
> > > 
> > > Try #2 :/
> > 
> > Try #3 (no sleep last night - trees and power lines down across the
> > property in last nights storms)  Sorry.
> > This time I remembered to escape those brackets. Please test this -
> > I can only check the script works, can't check if mmaker likes it.
> > 
> > > 
> > > Ignore the above - that echo won't reliably create multiple lines,
> > > printf will.
> > > 
> > > Try this which will:-
> > 
> > echo "
> > #!/bin/bash
> > # .fmenu
> > mv ~/.fluxbox/menu{,-$(date +%Y%m%d-%R)}
> > mmaker fluxbox -f
> > printf "\t[submenu] \(My
> > Menu\)\n\t[include]\(~/.fluxbox/usermenu\)\n\t[end]\n\t[separator]"
> > >> ~/.fluxbox/menu" > ~/.fmenu
> > 
> > > 
> > > 
> > > The above will:-
> > > create a script ~./.fmenu
> > > 
> > > Running ~/.fmenu will:-
> > > mv your existing ~/.fluxbox/menu to ~/.fluxbox/menu-mmdd-hh:mm
> > > create a new ~/.fluxbox/menu
> > > append your submenu to it
> > > 
> > > 
> > > If you want to remove the last [end] tag from the main menu (as
> > > suggested by Linux Fan try this:-
> > 
> > echo "
> > #!/bin/bash
> > # .fmenu
> > mv ~/.fluxbox/menu{,-$(date +%Y%m%d-%R)}
> > mmaker fluxbox -f
> > sed -i 's/\[end]//g' ~/.fluxbox/menu;sed -i '/^\s*$/d'
> > ~/.fluxbox/menu printf "\t[submenu] \(My
> > Menu\)\n\t[include]\(~/.fluxbox/usermenu\)\n\t[end]\n\t[separator]"
> > >> ~/.fluxbox/menu" > ~/.fmenu
> > 
> > 
> > 
> > Someone more awake than I can probably make that double invocation
> > of sed into a single call.
> > 
> Morning Scott.
> Thanks for this, I hope you slept better? This is what I currently
> have -
> 
> #!/bin/bash
> # .fmenu
> mv ~/.fluxbox/menu{,-$(date +%Y%m%d-%R)}
> 
> mmaker fluxbox -f
> 
> sed -i 's/\[end]//g' ~/.fluxbox/menu;sed -i '/^\s*$/d' ~/.fluxbox/menu
> 
> printf '\t[submenu] \(My
> Menu\)\n\t[include]\(~/.fluxbox/usermenu\)\n\t[end]\n\t[separator]'
> >>~/.fluxbox/menu" >~/.fmenu
> 
> and the double sed line works okay, but its failing at the 'printf'
> line saying -
> 'tryitout
> /home/boudiccas/bin/tryitout: line 21: /home/boudiccas/.fluxbox/menu 
> 
> >~/.fmenu'
> 
> NB - my working script is always called 'tryitout', just whilst I'm
> developing something. 
> 
> The new menu is created without the two [end] at its end, but there is
> nothing from 'printf' at all.
> 
> Sorry
> Sharon.
> 
I've got it working with this line -
mv ~/.fluxbox/menu{,-$(date +%Y%m%d-%R)}; mmaker fluxbox -f;perl -0777
-pi -e 's/(.*)\[end]/$1/s;s/(.*)\[end]/$1/s;s/^\s*\n//gm'
~/.fluxbox/menu;printf '\t[end]\n\t[separator]\n\t[submenu] (My
Menu)\n\t[include] (~/.fluxbox/usermenu)\n\t[end]\n\t[end]'
>>~/.fluxbox/menu

Thanks for all those who offered solutions.

Sharon.


signature.asc
Description: PGP signature

Re: message formatting [was Wheezy/XFCE/VNC}

[Andre Majorel]

On 2013-11-20 17:45 +1300, Chris Bannister wrote:
> On Tue, Nov 19, 2013 at 02:26:21PM +0100, Andre Majorel wrote:
>
> > An attribution wouldn't have hurt but it's plain to see that Jon
> > was replying to Emilio's message, not Ron's. Or don't mailers
> > show threads any more ?
> 
> Mutt, the one I use, does; but I don't keep *all* the messages
> in a thread. I must have deleted the message that Jonathan
> referred to at some stage. I think this adds more credence to
> the point that providing context and attribution would
> certainly help avoid conversations like this one.

Agreed with your conclusion but I'll add one of my own :
deleting mail has a cost. :->

A possible alternative is flagging. "F" to mark the important
posts, "/~F" and "n" to find them, "l~F" to hide the others.

-- 
André Majorel 
bugs.debian.org, food for your spambots.


-- 
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/20131122152849.ga14...@aym.net2.nerim.net

Re: Extending fluxbox menu with a script.

[Linux-Fan]

On 11/22/2013 03:13 PM, Sharon Kimble wrote:
> I've been doing some more testing and now got the 'submenu' being
> generated at the end, which is good. But, the sed lines are also
> stripping out *all* of the [end] lines which separate the sections of
> the menu, which are needed for it to function properly. So how can we
> get it to just strip out the two [end] at the end of the main menu, and
> leave all of the other [end] in the script intact please?
> 
> Thanks
> Sharon.

Use head -n -1 instead of removing all "[end]" lines with the sed command.

http://lists.debian.org/debian-user/2013/11/msg01187.html

-- 
http://masysma.ohost.de/



signature.asc
Description: OpenPGP digital signature

Re: CIFS mount hangs

[assmann]

Hi,

so I did some testing with a clone of the machine restored to the
state before the upgrade to wheezy.

Squeeze:
- Mount the share
- Disable the share on windows host
- Try to access the share with 'ls' results in 'no such device'
- Enable the share on windows host
- Try to access the share with 'ls' is successful

Wheezy:
- Mount the share
- Disable the share on windows host
- Try to access the share with 'ls' results in 'Server ... has not
responded in 300 seconds' .. and an error from ls after well 300
seconds i would say. Until this the shell hangs and the access can not be 
interupted with
CTRL-C.
- Enable the share on windows host
- Try to access the share with 'ls' is successful but shows an empty
dir.
- Remount brings the content back
- Connection is lost after some time of inactivity (share is still
available under squeeze)

This is the behavoiur when I manually disable the share. But in 'real
life' the share is not diabled by anyone. It is still visible in the
windows network environment.

I have now tried this:
http://www.mail-archive.com/linux-cifs@vger.kernel.org/msg06161.html

Will see how this will work out.

Thanks so far!

Tobias

> On 21/11/13 22:39, assm...@skygate.de wrote:
>> Hi,
>> 
>> I tried your tricks, removing auto, adding _netdev but the problem
>> still exists. I seems to happen when I am not working on the share for
>> a certain amount of time. The share seems to be lost thenthis did
>> not happen under wheezy. So I am thinking about, what kind of code to
>> blame? mount.cifs? Maybe try some kind of APT-Pinning to find out?
>> (Never tried this till before).

> I'd try 1x1 (isolation testing) first. Starting with "# mount -a" when
> the network resource is unavailable and looking at any error messages.
> Or try a manual mount (when the network resource is unavailable).

> How does "$ testparm -v" on the new box compare with the same from the
> box that did work?

>> 
>> Any ideas to debug and understand are welcome.

> The output of:
> $ testparm -v

> Plus the settings used on the boxes that host the samba resources might
> be informative.
> Do you have any logs from the other boxes?

>> 
>> TIA!
>> 
>>> On 19/11/13 23:33, assm...@skygate.de wrote:
 Dear list,

 since my upgrade to wheezy I have a problem with a cifs mount. It is a
 share of my windows host. The setup worked fine in debian squeeze.

> 

> the _netdev will create an error message, but it still works (allows a
> normal boot if a cifs resource is unavailable).

> None of the wheezy boxes I build have problems with cifs dropping out
> that isn't the fault of the Windoof part of the network, nor do I know
> of any problems similar to yours - so my best guess would be that Debian
> is the wrong end of the problem. I didn't see any relevant bug
> reports perhaps if you tell us more about the rest of the network?

> With Squeeze I did have some problems with a mostly Windoof WAN (some
> Apples) due to routing problems but that was solved by using autofs. If
> you can't solve the cause of the problem by looking at the logs on the
> other boxes in your network I'd suggest autofs.

> You could also try the samba mailing list?  sa...@lists.samba.org


> Kind regards.




Mit freundlichen Grüßen

Tobias Assmann
___

 SkyGate internetworking GmbH
 Pfuelstrasse 5, Aufgang VI
 D - 10997 Berlin
 Handelsreg. Berlin Charlottenburg, HRB 87258
 Geschaeftsfuehrer: Stephan Jensen

 T: +49- (0)30 - 611038-0
 F: +49- (0)30 - 61280465
 W: http://www.skygate.de
___



-- 
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/1379580994.20131122154...@skygate.de

Re: NAS hdd's in Debian desktop computer?

[Dan Ritter]

On Fri, Nov 22, 2013 at 08:13:56AM -0500, Jon N wrote:
> desktop system.  So far, about the only potential issue I can see is
> something called "(...) Error Recovery Control".
> 
> If I have this correct, if a desktop drive is having problems reading
> something it just keeps trying for a long time (I haven't found any
> reference as to how long, but it's longer than a NAS drive).  This
> would cause a NAS to think the drive was broken and ignore it.  A NAS
> drive on the other hand will try for a shorter period of time and (if
> it still fails) report the problem to the NAS so the NAS OS can take
> steps in correcting it.
> 
> Which leads to my questions.  If the NAS drive is installed in a
> desktop computer running Debian Linux what is the result of this?
> Will this command just be ignored?  Will the shorter time the drive
> spends trying to perform whatever operation it's having a problem with
> cause a problem if the OS does not have a way of dealing with this?
> How else will will this affect my system?
> 
> In my online searches I have seen many results dealing with using
> desktop drives in NAS's, but nothing (so far) that addresses the issue
> the other way around.  So any light you can shed on this will be
> gratefully appreciated.

For MythTV storage, you either value the video data enough to
have multiple copies, or you don't.

(I assume you value the database enough to run the standard
backup job daily, and store it on a disk that is not running
your database.)

If you keep multiple copies of the video data on different disks, then
it will be safe against a disk failure. If you don't, it won't.

Either way, there's no reason not to use NAS rated disks.

-dsr-


-- 
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/20131122141427.gt4...@randomstring.org

Re: Extending fluxbox menu with a script.

[Sharon Kimble]

On Fri, 22 Nov 2013 12:15:21 +
Sharon Kimble  wrote:

> On Fri, 22 Nov 2013 09:09:23 +1100
> Scott Ferguson  wrote:
> 
> > On 22/11/13 08:50, Scott Ferguson wrote:
> > > On 22/11/13 06:39, Scott Ferguson wrote:
> > 
> > > 
> > > Try #2 :/
> > 
> > Try #3 (no sleep last night - trees and power lines down across the
> > property in last nights storms)  Sorry.
> > This time I remembered to escape those brackets. Please test this -
> > I can only check the script works, can't check if mmaker likes it.
> > 
> > > 
> > > Ignore the above - that echo won't reliably create multiple lines,
> > > printf will.
> > > 
> > > Try this which will:-
> > 
> > echo "
> > #!/bin/bash
> > # .fmenu
> > mv ~/.fluxbox/menu{,-$(date +%Y%m%d-%R)}
> > mmaker fluxbox -f
> > printf "\t[submenu] \(My
> > Menu\)\n\t[include]\(~/.fluxbox/usermenu\)\n\t[end]\n\t[separator]"
> > >> ~/.fluxbox/menu" > ~/.fmenu
> > 
> > > 
> > > 
> > > The above will:-
> > > create a script ~./.fmenu
> > > 
> > > Running ~/.fmenu will:-
> > > mv your existing ~/.fluxbox/menu to ~/.fluxbox/menu-mmdd-hh:mm
> > > create a new ~/.fluxbox/menu
> > > append your submenu to it
> > > 
> > > 
> > > If you want to remove the last [end] tag from the main menu (as
> > > suggested by Linux Fan try this:-
> > 
> > echo "
> > #!/bin/bash
> > # .fmenu
> > mv ~/.fluxbox/menu{,-$(date +%Y%m%d-%R)}
> > mmaker fluxbox -f
> > sed -i 's/\[end]//g' ~/.fluxbox/menu;sed -i '/^\s*$/d'
> > ~/.fluxbox/menu printf "\t[submenu] \(My
> > Menu\)\n\t[include]\(~/.fluxbox/usermenu\)\n\t[end]\n\t[separator]"
> > >> ~/.fluxbox/menu" > ~/.fmenu
> > 
> > 
> > 
> > Someone more awake than I can probably make that double invocation
> > of sed into a single call.
> > 
> Morning Scott.
> Thanks for this, I hope you slept better? This is what I currently
> have -
> 
> #!/bin/bash
> # .fmenu
> mv ~/.fluxbox/menu{,-$(date +%Y%m%d-%R)}
> 
> mmaker fluxbox -f
> 
> sed -i 's/\[end]//g' ~/.fluxbox/menu;sed -i '/^\s*$/d' ~/.fluxbox/menu
> 
> printf '\t[submenu] \(My
> Menu\)\n\t[include]\(~/.fluxbox/usermenu\)\n\t[end]\n\t[separator]'
> >>~/.fluxbox/menu" >~/.fmenu
> 
> and the double sed line works okay, but its failing at the 'printf'
> line saying -
> 'tryitout
> /home/boudiccas/bin/tryitout: line 21: /home/boudiccas/.fluxbox/menu 
> 
> >~/.fmenu'
> 
> NB - my working script is always called 'tryitout', just whilst I'm
> developing something. 
> 
> The new menu is created without the two [end] at its end, but there is
> nothing from 'printf' at all.
> 
> Sorry
> Sharon.
> 
I've been doing some more testing and now got the 'submenu' being
generated at the end, which is good. But, the sed lines are also
stripping out *all* of the [end] lines which separate the sections of
the menu, which are needed for it to function properly. So how can we
get it to just strip out the two [end] at the end of the main menu, and
leave all of the other [end] in the script intact please?

Thanks
Sharon.


signature.asc
Description: PGP signature

NAS hdd's in Debian desktop computer?

[Jon N]

Hi,

I've been shopping around for new hardware to build a new desktop
computer for myself.  This would be both a MythTV frontend/backend, as
well as for general purpose computing (which for me means mostly
internet browsing and email, but occasionally I use LibreOffice, view
PDF's and similar non-exciting things).

I realized that with the hardware I have picked out so far I have the
opportunity to have a fairly low power, as in it will not use a lot of
electricity, computer.  And I like that idea very much.

I thought picking a hard drive would be mostly a no-brainer.  I had a
particular manufacturer and model line in mind.  I have one of these
already and it works without problem.  But, the reviews show a _lotS
of complaints recently of either DOA's or failures after only a few
months.  Even though I know reviews are not perfect, I do rely heavily
on them for product comparison.

I did notice though that the model line of hard drives listed as for
use in NAS's had a much better user review rating, and also had
similar power usage ratings as the energy savings models.  But I can't
figure out if there are any reasons not to use one of these drives in
desktop system.  So far, about the only potential issue I can see is
something called "(...) Error Recovery Control".

If I have this correct, if a desktop drive is having problems reading
something it just keeps trying for a long time (I haven't found any
reference as to how long, but it's longer than a NAS drive).  This
would cause a NAS to think the drive was broken and ignore it.  A NAS
drive on the other hand will try for a shorter period of time and (if
it still fails) report the problem to the NAS so the NAS OS can take
steps in correcting it.

Which leads to my questions.  If the NAS drive is installed in a
desktop computer running Debian Linux what is the result of this?
Will this command just be ignored?  Will the shorter time the drive
spends trying to perform whatever operation it's having a problem with
cause a problem if the OS does not have a way of dealing with this?
How else will will this affect my system?

In my online searches I have seen many results dealing with using
desktop drives in NAS's, but nothing (so far) that addresses the issue
the other way around.  So any light you can shed on this will be
gratefully appreciated.

Thanks,
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/CANcvmg3qOX8T=+MuCqa8VoEUW=+dbuhqjo_w0pvtxqxgsdu...@mail.gmail.com

QT through ssh tunnel

[Dan]

Hi,

I have gnome and I use a QT application  (virtualbox) with a ssh
tunnel in the same computer. I use a different user than the user that
I use with Gnome.

The problem is that I get the old QT theme (Windows 95/motif style)
when I run virtualbox with a ssh tunnel. In the other hand, if I run a
GTK application (ex gedit) with a ssh tunnel I do not have that
problem. It is not a big deal, but i would nice to have the fancy QT
theme.

If I do the same thing in my laptop I get the right QT theme in
virtualbox using a ssh tunnel. I have wheezy and gnome in both
computers. I do not know why I have a different behaviour.

Thanks,
Dan


-- 
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/cak00fol3xpj7+njjsb878fc0wrghg5s5exx7cucko7y5ysp...@mail.gmail.com

Re: Extending fluxbox menu with a script.

[Sharon Kimble]

On Fri, 22 Nov 2013 09:09:23 +1100
Scott Ferguson  wrote:

> On 22/11/13 08:50, Scott Ferguson wrote:
> > On 22/11/13 06:39, Scott Ferguson wrote:
> 
> > 
> > Try #2 :/
> 
> Try #3 (no sleep last night - trees and power lines down across the
> property in last nights storms)  Sorry.
> This time I remembered to escape those brackets. Please test this - I
> can only check the script works, can't check if mmaker likes it.
> 
> > 
> > Ignore the above - that echo won't reliably create multiple lines,
> > printf will.
> > 
> > Try this which will:-
> 
> echo "
> #!/bin/bash
> # .fmenu
> mv ~/.fluxbox/menu{,-$(date +%Y%m%d-%R)}
> mmaker fluxbox -f
> printf "\t[submenu] \(My
> Menu\)\n\t[include]\(~/.fluxbox/usermenu\)\n\t[end]\n\t[separator]" >>
> ~/.fluxbox/menu" > ~/.fmenu
> 
> > 
> > 
> > The above will:-
> > create a script ~./.fmenu
> > 
> > Running ~/.fmenu will:-
> > mv your existing ~/.fluxbox/menu to ~/.fluxbox/menu-mmdd-hh:mm
> > create a new ~/.fluxbox/menu
> > append your submenu to it
> > 
> > 
> > If you want to remove the last [end] tag from the main menu (as
> > suggested by Linux Fan try this:-
> 
> echo "
> #!/bin/bash
> # .fmenu
> mv ~/.fluxbox/menu{,-$(date +%Y%m%d-%R)}
> mmaker fluxbox -f
> sed -i 's/\[end]//g' ~/.fluxbox/menu;sed -i '/^\s*$/d' ~/.fluxbox/menu
> printf "\t[submenu] \(My
> Menu\)\n\t[include]\(~/.fluxbox/usermenu\)\n\t[end]\n\t[separator]" >>
> ~/.fluxbox/menu" > ~/.fmenu
> 
> 
> 
> Someone more awake than I can probably make that double invocation of
> sed into a single call.
> 
Morning Scott.
Thanks for this, I hope you slept better? This is what I currently
have -

#!/bin/bash
# .fmenu
mv ~/.fluxbox/menu{,-$(date +%Y%m%d-%R)}

mmaker fluxbox -f

sed -i 's/\[end]//g' ~/.fluxbox/menu;sed -i '/^\s*$/d' ~/.fluxbox/menu

printf '\t[submenu] \(My
Menu\)\n\t[include]\(~/.fluxbox/usermenu\)\n\t[end]\n\t[separator]'
>>~/.fluxbox/menu" >~/.fmenu

and the double sed line works okay, but its failing at the 'printf'
line saying -
'tryitout
/home/boudiccas/bin/tryitout: line 21: /home/boudiccas/.fluxbox/menu 

>~/.fmenu'

NB - my working script is always called 'tryitout', just whilst I'm
developing something. 

The new menu is created without the two [end] at its end, but there is
nothing from 'printf' at all.

Sorry
Sharon.


signature.asc
Description: PGP signature

Re: CPU frequency and custom kernel

[Sean Alexandre]

On Fri, Nov 22, 2013 at 03:03:33AM -0500, ken wrote:
> I've found cpuspeed to be buggy... the speed at which the cpu runs
> seems to have little to do with the conditions specified in the
> config file. Recent kernel upgrades have improved cpuspeed somewhat
> (without any changes to the config file), but it's still nonsensical
> at times.

I think that was it. I upgraded to most recent stable kernel (3.12.1) [1] and
no longer see the problem.

I took a look at the 3.2 changelog [2] to see if I could tell what particular
change Debian developers made to get this working. There are quite a few
cpufreq related changes, but it wasn't clear to me which fixes the problem
I was seeing.

[1] https://www.kernel.org/
[2] 
http://ftp-master.metadata.debian.org/changelogs//main/l/linux/linux_3.2.51-1_changelog


-- 
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/20131122115430.GA7395@tuzo

Re: CPU frequency and custom kernel

[Sean Alexandre]

On Fri, Nov 22, 2013 at 11:06:14AM +0100, Jochen Spieker wrote:
> Check the files in this directory:
> 
> /sys/devices/system/cpu/cpu0/cpufreq
> 
> Especially scaling_available_frequencies, scaling_max_freq and
> scaling_min_freq.

I've been using the cpufreq-info, which I think reports what's in those files.
For the Debian kernel I get:

cpufrequtils 008: cpufreq-info (C) Dominik Brodowski 2004-2009
Report errors and bugs to cpuf...@vger.kernel.org, please.
analyzing CPU 0:
  driver: acpi-cpufreq
  CPUs which run at the same hardware frequency: 0 1 2 3
  CPUs which need to have their frequency coordinated by software: 0
  maximum transition latency: 10.0 us.
  hardware limits: 800 MHz - 2.30 GHz
  available frequency steps: 2.30 GHz, 2.00 GHz, 1.80 GHz, 1.60 GHz, 1.40 GHz, 
1.20 GHz, 1000 MHz, 800 MHz
  available cpufreq governors: conservative, powersave, userspace, ondemand, 
performance
  current policy: frequency should be within 800 MHz and 2.30 GHz.
  The governor "ondemand" may decide which speed to use
  within this range.
  current CPU frequency is 800 MHz (asserted by call to hardware).
  cpufreq stats: 2.30 GHz:5.20%, 2.00 GHz:0.14%, 1.80 GHz:0.16%, 1.60 
GHz:0.20%, 1.40 GHz:0.28%, 1.20 GHz:0.44%, 1000 MHz:0.49%, 800 MHz:93.09%  
(39552)

And then for the custom kernel I get:

cpufrequtils 008: cpufreq-info (C) Dominik Brodowski 2004-2009
Report errors and bugs to cpuf...@vger.kernel.org, please.
analyzing CPU 0:
  driver: acpi-cpufreq
  CPUs which run at the same hardware frequency: 0 1 2 3
  CPUs which need to have their frequency coordinated by software: 0
  maximum transition latency: 10.0 us.
  hardware limits: 800 MHz - 2.30 GHz
  available frequency steps: 2.30 GHz, 2.00 GHz, 1.80 GHz, 1.60 GHz, 1.40 GHz, 
1.20 GHz, 1000 MHz, 800 MHz
  available cpufreq governors: conservative, powersave, userspace, ondemand, 
performance
  current policy: frequency should be within 800 MHz and 2.30 GHz.
  The governor "ondemand" may decide which speed to use
  within this range.
  current CPU frequency is 1.80 GHz (asserted by call to hardware).
  cpufreq stats: 2.30 GHz:11.32%, 2.00 GHz:1.27%, 1.80 GHz:0.94%, 1.60 
GHz:0.59%, 1.40 GHz:1.17%, 1.20 GHz:0.60%, 1000 MHz:1.12%, 800 MHz:82.99%  (713)

That last line for the custom kernel says the CPU runs at 800 MHz most of the 
time, 
but I think that's because the stats don't roll over on reboot. It shows I'm 
using 
the Debian kernel most of the time.


-- 
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/20131122111329.GA5843@tuzo

Re: does grub support wireless keyboard?

[Paul Cartwright]

On 11/22/2013 12:01 AM, Long Wind wrote:
> another question: how to find out if my PC support USB keyboard?
> does grub support USB keyboard?
> if it support USB KB, does that mean it support wireless keyboard?
> I am considering logitech wireless keyboard
> I am running wheezy
> Thanks!
>
>
I am running Mint and I have a bluetooth keyboard & mouse, they work
fine. It is a Logitech keyboard..

-- 
Paul Cartwright
Registered Linux User #367800 and new counter #561587


-- 
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/528f3e16.2040...@gmail.com

(solved) Re: does grub support wireless keyboard?

[Long Wind]

Thank all those who reply!

Info provided by Atle Solbakken confirm my guess.


On 11/22/13, Atle Solbakken  wrote:

> Hi
>
> My MB is about 1-2 years old, and has native support for USB keyboards
> which works with the wireless Logitech MK250. Most newer motherboards
> support USB-keyboards.
>
> The BIOS doesn't really care (or know) whether an USB-keyboard is
> wireless or not. If it works with cabled USB keyboards, it will work
> with wireless keyboards.
>
> And if the BIOS supports USB keyboards, they work in GRUB as well :) I
> have wheezy too btw., works like a charm.
>
>
> Atle.
>
>
>


-- 
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/CAB-gxZAwxZL4qp8q3PtaW99TdduREtPcEUhEpenNK6uw=35...@mail.gmail.com

Re: CPU frequency and custom kernel

[Jochen Spieker]

Sean Alexandre:
> 
> I can't figure out why it's faster. Everything I've checked is the same 
> between
> the two kernels. If I boot to the Debian provided kernel the CPU runs at 800
> MHz, but if I boot to my custom kernel it runs at 1.8 GHz. (These are baseline
> speeds, after boot without running anything else.)

Check the files in this directory:

/sys/devices/system/cpu/cpu0/cpufreq

Especially scaling_available_frequencies, scaling_max_freq and
scaling_min_freq.

J.
-- 
Nothing is as I planned it.
[Agree]   [Disagree]
 


signature.asc
Description: Digital signature

Re: does grub support wireless keyboard?

[Atle Solbakken]

Den 22. nov. 2013 06:01, skrev Long Wind:

another question: how to find out if my PC support USB keyboard?
does grub support USB keyboard?
if it support USB KB, does that mean it support wireless keyboard?
I am considering logitech wireless keyboard
I am running wheezy
Thanks!



Hi

My MB is about 1-2 years old, and has native support for USB keyboards 
which works with the wireless Logitech MK250. Most newer motherboards 
support USB-keyboards.


The BIOS doesn't really care (or know) whether an USB-keyboard is 
wireless or not. If it works with cabled USB keyboards, it will work 
with wireless keyboards.


And if the BIOS supports USB keyboards, they work in GRUB as well :) I 
have wheezy too btw., works like a charm.



Atle.




--
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/528f2601.5040...@goliathdns.no

Re: CPU frequency and custom kernel

[ken]

On 11/21/2013 07:42 PM Sean Alexandre wrote:

I've built my own kernel, but the CPU runs faster (hotter, more fan noise, etc.)

I can't figure out why it's faster. Everything I've checked is the same between
the two kernels. If I boot to the Debian provided kernel the CPU runs at 800
MHz, but if I boot to my custom kernel it runs at 1.8 GHz. (These are baseline
speeds, after boot without running anything else.)

Here's what I've checked so far:

* Kernel versions are the same. The Debian version is 3.2.0-4-amd64 and the
   version I got from kernel.org is 3.2.52.
* The boot command line has the same paremeters for both:
   linux /vmlinuz-3.2.0-4-amd64 root=/dev/mapper/tuzo-root ro quiet
* Both boot to the same root file system, and use the same configuration files.
* The .config file used to build the custom kernel is the same as the one used
   to build the Debian kernel. (I'm going to pare it down to just what I need
   once I figure out this problem.)
* Both use the ondemand cpufreq governor.


I've found cpuspeed to be buggy... the speed at which the cpu runs seems 
to have little to do with the conditions specified in the config file. 
Recent kernel upgrades have improved cpuspeed somewhat (without any 
changes to the config file), but it's still nonsensical at times.





Is there anything else I should check?

My next step would be to try and build the kernel source from the Debian
package instead of from kernel.org. Maybe this is a code difference?





--
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/528f0fd5.1020...@mousecar.com