I don't understand the point of this email -- are you advocating for some
change, or to avoid some change?
(I looked at the bug report and skimmed some of the messages -- it seems like
by posting this to the debian-user list you are looking for comments or
support here, but the issue is not c
Thorsten Glaser:
> Just accept that this idea, originating from the systemd people at
Fedora/Freedesktop, is NOT welcome to classical Unix people.
Ahem! We classical Unix people experienced this idea in the late 1980s,
from where it *really* originated, Sun and AT&T.
* https://groups.googl
Thank you for the additional information you have supplied regarding
this Bug report.
This is an automatically generated reply to let you know your message
has been received.
Your message is being forwarded to the package maintainers and other
interested parties for their attention; they will rep
On 2018-10-28 16:58 +, Grzesiek Sójka wrote:
> On 10/28/18 2:10 PM, Sven Joachim wrote:
>> Wouldn't it be better to fix the init system that sets such a bad
>> default PATH? Whatever init system that may be - sysv-rc's
>> /etc/init.d/rc script sets PATH=/sbin:/
On 10/28/18 2:10 PM, Sven Joachim wrote:
Wouldn't it be better to fix the init system that sets such a bad
default PATH? Whatever init system that may be - sysv-rc's
/etc/init.d/rc script sets PATH=/sbin:/usr/sbin:/bin:/usr/bin, so this
should not happen with sysvinit + sysv-rc.
Pl
On 2018-10-28 14:47 +, Grzesiek Sójka wrote:
> On 10/28/18 11:27 AM, Grzesiek Sójka wrote:
>> Hi there,
>>
>> I just upgraded Sid and now I get the following during boot:
>>
>> [] Configuring network interfaces.../etc/init.d/rpcbind: 42:
>> /etc/
On 10/28/18 11:27 AM, Grzesiek Sójka wrote:
Hi there,
I just upgraded Sid and now I get the following during boot:
[] Configuring network interfaces.../etc/init.d/rpcbind: 42:
/etc/init.d/rpcbind: stat: not found
/run/rpcbind not owned by root failed!
Starting NFS common utilities: statd
On Friday 20 May 2016 18:08:37 Rodary Jacques wrote:
> I read quite a lot of the answers to your post, and I still think there is
> a problem, not linked to the kernel's interface name name. I have a wifi
> interface named *everywhere* wlan0. It isn't found by network-pre.target,
> network-target
I read quite a lot of the answers to your post, and I still think there is a
problem, not
linked to the kernel's interface name name. I have a wifi interface named
*everywhere*
wlan0. It isn't found by network-pre.target, network-target or
networking-service, I
don't know which one. What I k
On 2016-05-18, Gene Heskett wrote:
>> *exactly* those devices tagged as "auto" in /etc/network/interfaces.
>>
>> So that should be the database you're looking for? Try, for starters
>>
>> grep auto /etc/network/interfaces
>
> auto lo eth0 eth1
>
> Its there in the complete interfaces file I just
On Wed 18 May 2016 at 12:32:24 -0500, David Wright wrote:
> On Wed 18 May 2016 at 17:39:45 (+0100), Brian wrote:
> > On Wed 18 May 2016 at 10:44:40 -0500, David Wright wrote:
> >
> > > On Wed 18 May 2016 at 10:56:01 (-0400), Gene Heskett wrote:
> > > >
> > > > auto lo eth0 eth1
> > >
> > > Agre
On Wed 18 May 2016 at 17:39:45 (+0100), Brian wrote:
> On Wed 18 May 2016 at 10:44:40 -0500, David Wright wrote:
>
> > On Wed 18 May 2016 at 10:56:01 (-0400), Gene Heskett wrote:
> > >
> > > auto lo eth0 eth1
> >
> > Agree with Lisi, I've never seen this (though I'm not claiming it's
> > either
On Wed 18 May 2016 at 10:50:23 (+0200), to...@tuxteam.de wrote:
> On Tue, May 17, 2016 at 11:22:29AM -0500, David Wright wrote:
> > On Tue 17 May 2016 at 11:26:28 (-0400), Gene Heskett wrote:
>
> [...]
What was snipped is "I do not see that as a disadvantage, udev can do
that much unwanted damage
On Wed 18 May 2016 at 10:44:40 -0500, David Wright wrote:
> On Wed 18 May 2016 at 10:56:01 (-0400), Gene Heskett wrote:
> >
> > auto lo eth0 eth1
>
> Agree with Lisi, I've never seen this (though I'm not claiming it's
> either wrong or harmful).
It's an ok line. From interfaces(5):
Lines beg
On Wednesday 18 May 2016 16:54:49 Gene Heskett wrote:
> "auto lo eth0"
auto lo
and
auto eth0
now??
Lisi
It may not solve anything, but when rationality seems to fail one has to
resort to magic, and just get the incantation right
Lisi
On Wednesday 18 May 2016 11:37:59 Lisi Reisz wrote:
> On Wednesday 18 May 2016 16:14:36 Gene Heskett wrote:
> > auto lo eth0 eth1
> >
> > Its there in the complete interfaces file I just posted, and you
> > snipped.
>
> Gene - we have, I think, established that your set-up doesn't work the
> way p
tool to fully restart all networking even the
> > > > > interface thru which connection is made.
> > > > > Are the `ifdown eth & ifup eth` the only option now?
> > > >
> > > > Just to add these commands in that thread.
> > > >
> &
On Wednesday 18 May 2016 16:14:36 Gene Heskett wrote:
> auto lo eth0 eth1
>
> Its there in the complete interfaces file I just posted, and you snipped.
Gene - we have, I think, established that your set-up doesn't work the way
predicted.
The one thing that looks very different to me is the stick
s made.
> > > Are the `ifdown eth & ifup eth` the only option now?
> >
> > Just to add these commands in that thread.
> >
> > To restart all the interfaces as they are defined in
> > /etc/network/interfaces, I do :
> >
> > # ifdown -a; ifu
th & ifup eth` the only option now?
> > > > >
> > > > > Just to add these commands in that thread.
> > > > >
> > > > > To restart all the interfaces as they are defined in
> > > > > /etc/network/interfaces, I do :
> &
; > > Are the `ifdown eth & ifup eth` the only option now?
> > >
> > > Just to add these commands in that thread.
> > >
> > > To restart all the interfaces as they are defined in
> > > /etc/network/interfaces, I do :
> > >
> > > #
mmands in that thread.
> > > >
> > > > To restart all the interfaces as they are defined in
> > > > /etc/network/interfaces, I do :
> > > >
> > > > # ifdown -a; ifup -a
> > >
> > > /etc/init.d/networking stop does ifdown -a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wed, May 18, 2016 at 03:42:27PM +0200, Elimar Riesebieter wrote:
> * Lisi Reisz [2016-05-18 12:31 +0100]:
>
> > On Tuesday 17 May 2016 18:29:36 Elimar Riesebieter wrote:
> [...]
> > > /etc/init.d/networking stop does ifd
On Wednesday 18 May 2016 14:42:27 Elimar Riesebieter wrote:
> * Lisi Reisz [2016-05-18 12:31 +0100]:
> > On Tuesday 17 May 2016 18:29:36 Elimar Riesebieter wrote:
>
> [...]
>
> > > /etc/init.d/networking stop does ifdown -a
> > > /etc/init.d/networking start d
* Lisi Reisz [2016-05-18 12:31 +0100]:
> On Tuesday 17 May 2016 18:29:36 Elimar Riesebieter wrote:
[...]
> > /etc/init.d/networking stop does ifdown -a
> > /etc/init.d/networking start does ifup -a
>
> But
> # ifdown -a; ifup -a
> is much more elegant!!
I would u
ad.
> >
> > To restart all the interfaces as they are defined in
> > /etc/network/interfaces, I do :
> >
> > # ifdown -a; ifup -a
>
> /etc/init.d/networking stop does ifdown -a
> /etc/init.d/networking start does ifup -a
But
# ifdown -a; ifup -a
is much more elegant!!
Lisi
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tue, May 17, 2016 at 11:22:29AM -0500, David Wright wrote:
> On Tue 17 May 2016 at 11:26:28 (-0400), Gene Heskett wrote:
[...]
> You don't see any disadvantage to removing the "hotplug stuff".
> Hooray, let's go back to PCs as static boxes. Shut i
On Tuesday 17 May 2016 19:30:06 Lisi Reisz wrote:
> On Tuesday 17 May 2016 23:43:08 Gene Heskett wrote:
> [snip]
>
> If it ain't broke, hit it with a hammer? ;-)
>
> Lisi
Yup, have you got a bigger one my lady?
Cheers, Gene Heskett
--
"There are four boxes to be used in defense of liberty:
soa
On Tuesday 17 May 2016 23:43:08 Gene Heskett wrote:
[snip]
If it ain't broke, hit it with a hammer? ;-)
Lisi
On Tuesday 17 May 2016 15:25:47 Andy Smith wrote:
> Hi Gene,
>
> On Tue, May 17, 2016 at 03:12:45PM -0400, Gene Heskett wrote:
> > Configuring interface eth1=eth1 (inet)
> > run-parts --verbose /etc/network/if-pre-up.d
> > run-parts: executing /etc/network/if-pre-up.d/wireless-tools
> > run-parts:
On Tue 17 May 2016 at 14:51:57 (-0400), Gene Heskett wrote:
> Interesting is that in a man 5 interfaces, it says the gateway address is
> colon delimited. I don't recall ever seeing that since my first install
> in early 1998. Does anyone ever actually read these man pages but me?
Yes, but I h
Hi Gene,
On Tue, May 17, 2016 at 03:12:45PM -0400, Gene Heskett wrote:
> Configuring interface eth1=eth1 (inet)
> run-parts --verbose /etc/network/if-pre-up.d
> run-parts: executing /etc/network/if-pre-up.d/wireless-tools
> run-parts: executing /etc/network/if-pre-up.d/wpasupplicant
> ip addr add
On Tuesday 17 May 2016 13:26:35 Elimar Riesebieter wrote:
> * Gene Heskett [2016-05-17 11:26 -0400]:
>
> [...]
>
> > Because of some rare condition, you make
> > all the other users with a less rare condition suffer?
>
> I was just talking about facts, nothing e
On Tuesday 17 May 2016 13:09:33 Gilles Mocellin wrote:
> Le 17/05/2016 à 14:34, Mimiko a écrit :
> > On 17.05.2016 15:16, Elimar Riesebieter wrote:
> >> Ask your search engine: "init.d/networking restart is deprecated"
> >
> > This was the only tool to fully restart all networking even the
> > int
On Tue 17 May 2016 at 16:38:52 (+0200), Elimar Riesebieter wrote:
> * Gene Heskett [2016-05-17 09:56 -0400]:
> > On Tuesday 17 May 2016 09:08:55 to...@tuxteam.de wrote:
> [...]
> > > In my opinion, a warning is in order ("this might not be doing
> > > what you think it does"), but deprecated seems
On Tuesday 17 May 2016 12:22:29 David Wright wrote:
> On Tue 17 May 2016 at 11:26:28 (-0400), Gene Heskett wrote:
> > On Tuesday 17 May 2016 10:38:52 Elimar Riesebieter wrote:
> > > * Gene Heskett [2016-05-17 09:56 -0400]:
> > > > On Tuesday 17 May 2016 09:08:55 to...@tuxteam.de wrote:
> > >
> >
rt all networking even the
> > interface thru which connection is made.
> > Are the `ifdown eth & ifup eth` the only option now?
> >
>
> Just to add these commands in that thread.
>
> To restart all the interfaces as they are defined in
> /etc/network/interfac
* Gene Heskett [2016-05-17 11:26 -0400]:
[...]
> Because of some rare condition, you make
> all the other users with a less rare condition suffer?
I was just talking about facts, nothing else. If you open
/etc/init.d/networking (ifupdown_0.7.8) in an editor and scroll down
to
Le 17/05/2016 à 14:34, Mimiko a écrit :
On 17.05.2016 15:16, Elimar Riesebieter wrote:
Ask your search engine: "init.d/networking restart is deprecated"
This was the only tool to fully restart all networking even the
interface thru which connection is made.
Are the `ifdown eth & ifup eth` th
On Tue 17 May 2016 at 11:26:28 (-0400), Gene Heskett wrote:
> On Tuesday 17 May 2016 10:38:52 Elimar Riesebieter wrote:
> > * Gene Heskett [2016-05-17 09:56 -0400]:
> > > On Tuesday 17 May 2016 09:08:55 to...@tuxteam.de wrote:
> > [...]
> > > > In my opinion, a warning is in order ("this might not
On Tuesday 17 May 2016 10:38:52 Elimar Riesebieter wrote:
> * Gene Heskett [2016-05-17 09:56 -0400]:
> > On Tuesday 17 May 2016 09:08:55 to...@tuxteam.de wrote:
>
> [...]
>
> > > In my opinion, a warning is in order ("this might not be doing
> > > what you think it does"), but deprecated seems ex
On Tuesday 17 May 2016 15:38:52 Elimar Riesebieter wrote:
> * Gene Heskett [2016-05-17 09:56 -0400]:
> > On Tuesday 17 May 2016 09:08:55 to...@tuxteam.de wrote:
>
> [...]
>
> > > In my opinion, a warning is in order ("this might not be doing
> > > what you think it does"), but deprecated seems exa
Hi Elimar,
>> On Tuesday 17 May 2016 09:08:55 to...@tuxteam.de wrote:
>>
>[...]
>> > In my opinion, a warning is in order ("this might not be doing what
>> > you think it does"), but deprecated seems exaggerated to me.
>> >
>> > regards
>> >
>> > [1] Schocking Truth! Not everything seen on the I
* Gene Heskett [2016-05-17 09:56 -0400]:
> On Tuesday 17 May 2016 09:08:55 to...@tuxteam.de wrote:
>
[...]
> > In my opinion, a warning is in order ("this might not be doing
> > what you think it does"), but deprecated seems exaggerated to me.
> >
> > regards
> >
> > [1] Schocking Truth! Not eve
On Tuesday 17 May 2016 09:08:55 to...@tuxteam.de wrote:
> On Tue, May 17, 2016 at 02:16:32PM +0200, Elimar Riesebieter wrote:
>
> [...]
>
> > Ask your search engine: "init.d/networking restart is deprecated"
>
> I don't know about yours, but *my* /etc/i
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tue, May 17, 2016 at 03:36:58PM +0200, Elimar Riesebieter wrote:
[...]
> I don't understand why "init.d/networking restart is deprecated" is
> scaring off people? It is a matter of fact! Reading the results will
> give all answers a user want.
N
* to...@tuxteam.de [2016-05-17 15:08 +0200]:
> On Tue, May 17, 2016 at 02:16:32PM +0200, Elimar Riesebieter wrote:
>
> [...]
>
> > Ask your search engine: "init.d/networking restart is deprecated"
>
> I don't know about yours, but *my* /etc/init.d/net
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tue, May 17, 2016 at 02:16:32PM +0200, Elimar Riesebieter wrote:
[...]
> Ask your search engine: "init.d/networking restart is deprecated"
I don't know about yours, but *my* /etc/init.d/networking is alive
and healthy! More to
On Tuesday 17 May 2016 08:16:32 Elimar Riesebieter wrote:
> * Gene Heskett [2016-05-17 08:05 -0400]:
> > Greetings all;
> >
> > 32 bit Debian wheezy, updated at least daily.
> >
> > This fact was brought to my attention because I needed a path to a
> > router I needed to do a hard reset on, and r
On 17.05.2016 15:16, Elimar Riesebieter wrote:
Ask your search engine: "init.d/networking restart is deprecated"
This was the only tool to fully restart all networking even the
interface thru which connection is made.
Are the `ifdown eth & ifup eth` the only option now?
--
Mimiko desu.
On Tuesday 17 May 2016 08:11:50 Peter Ludikovsky wrote:
> In /etc/network/interfaces change
> allow-hotplug eth1
> to
> auto eth1
Blind as a bat, gonna have to get my cateracts fixed as I didn't see
that. I don't have the allow-hotplug line, but the auto line didn't have
eth1, added, wo
* Gene Heskett [2016-05-17 08:05 -0400]:
> Greetings all;
>
> 32 bit Debian wheezy, updated at least daily.
>
> This fact was brought to my attention because I needed a path to a router
> I needed to do a hard reset on, and reconfigure to do my stuff, but my
> normal home network isn't on the
In /etc/network/interfaces change
allow-hotplug eth1
to
auto eth1
Regards,
/peter
Am 17.05.2016 um 14:05 schrieb Gene Heskett:
> Greetings all;
>
> 32 bit Debian wheezy, updated at least daily.
>
> This fact was brought to my attention because I needed a path to a router
> I needed to
Greetings all;
32 bit Debian wheezy, updated at least daily.
This fact was brought to my attention because I needed a path to a router
I needed to do a hard reset on, and reconfigure to do my stuff, but my
normal home network isn't on the usual 192.168.1.1 class C, and a hard
reset puts the ro
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 05/05/2015 12:28 PM, Thomas H. George wrote:
> On Tue, May 05, 2015 at 05:54:53PM +0200, Michael Biebl wrote:
>> Am 05.05.2015 um 17:13 schrieb Thomas H. George:
>>> Entered /etc/init.d/gdm3 start from a root console. Respons
On Tue, May 05, 2015 at 05:54:53PM +0200, Michael Biebl wrote:
> Am 05.05.2015 um 17:13 schrieb Thomas H. George:
> > Entered /etc/init.d/gdm3 start from a root console. Response was to
> > check systemctl status gdm.service and journalctl -xn. A script of the
> > ou
Am 05.05.2015 um 17:13 schrieb Thomas H. George:
> Entered /etc/init.d/gdm3 start from a root console. Response was to
> check systemctl status gdm.service and journalctl -xn. A script of the
> output of these entries:
>
>
> Script started on Tue 05 May 2015 10:58:05 AM ED
On Tue, May 05, 2015 at 11:13:15AM -0400, Thomas H. George wrote:
> Entered /etc/init.d/gdm3 start from a root console. Response was to
> check systemctl status gdm.service and journalctl -xn. A script of the
> output of these entries:
>
>
> Script started on Tue 05 May 20
Entered /etc/init.d/gdm3 start from a root console. Response was to
check systemctl status gdm.service and journalctl -xn. A script of the
output of these entries:
Script started on Tue 05 May 2015 10:58:05 AM EDT
[01;35mZebra:~# [00msystemctl status gdm.service
[1;31m●[0m gdm.service
Lisi Reisz a écrit :
> On Sunday 01 September 2013 10:26:22 Erwan David wrote:
>> Et ces règles ne dépendent de rien d'autre ? Par exemple chez moi j'ai
>> une interface tun0 pour un VPN? qui n'existera que si le VPN est lancé...
>
> This is an English language list!
Looks like that post escaped
On Sunday 01 September 2013 10:26:22 Erwan David wrote:
> Le 01/09/2013 11:10, Dominique Asselineau a écrit :
> > François TOURDE wrote on Sun, Sep 01, 2013 at 10:00:55AM +0200
> >
> >> Le 15949ième jour après Epoch,
> >>
> >> Gaëtan PERRIER écrivait:
> >>> Bonsoir,
[snip]
> Et ces règles ne dépend
Le 01/09/2013 11:10, Dominique Asselineau a écrit :
> François TOURDE wrote on Sun, Sep 01, 2013 at 10:00:55AM +0200
>> Le 15949ième jour après Epoch,
>> Gaëtan PERRIER écrivait:
>>
>>> Bonsoir,
>>>
>>> C'est possible quand on est sur un réseau statique mais avec une réseau
>>> en dhcp ça ne me sem
On 2012-09-24 20:58 +0200, Regid Ichira wrote:
> $ grep Provides /etc/init.d/mountnfs-bootclean.sh
> # Provides: mountnfs-bootclean
>
> $ grep Description /etc/init.d/bootmisc.sh
> # Short-Description: Miscellaneous things to be done during bootup.
>
$ grep Provides /etc/init.d/mountnfs-bootclean.sh
# Provides: mountnfs-bootclean
$ grep Description /etc/init.d/bootmisc.sh
# Short-Description: Miscellaneous things to be done during bootup.
# Description: Some cleanup. Note, it need to run after
mountnfs
hemselves, making this script redundant.
> $
>
> $ ls -l /etc/init.d/bootlogs
> -rwxr-xr-x 1 root root 1276 Aug 11 20:30 /etc/init.d/bootlogs
> $ dpkg -S /etc/init.d/bootlogs
> initscripts: /etc/init.d/bootlogs
>
> Is it a bug that bootlogs was not remove
$ zgrep -A1 'bootlogs init script has been removed'
/usr/share/doc/initscripts/changelog.Debian.gz
- bootlogs init script has been removed; current logging daemons
handle this themselves, making this script redundant.
$
$ ls -l /etc/init.d/bootlogs
-r
Bob Proulx proulx.com> writes:
>
> Looking at http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=634215 I
> see that you have found a problem related to @reboot with cron
> starting earlier using the dependency based booting than it did before
> with the legacy based manually specified number boot
Regid Ichira wrote:
> Bob Proulx writes:
> > Regid Ichira wrote:
> > > I have installed the ntp package. I edited /etc/insserv.conf, and
> > > added +ntp to the $time line.
> > >
> > > $ grep time /etc/insserv.conf
> > > # The system time has been set correctly
> > > $time
Bob Proulx proulx.com> writes:
>
> Regid Ichira wrote:
> > I have installed the ntp package. I edited /etc/insserv.conf, and
> > added +ntp to the $time line.
> >
> > $ grep time /etc/insserv.conf
> > # The system time has been set correctly
> > $time +hwclock +ntp
>
>
between
rsyslog and ntp? rsyslog needs $time. ntp needs $syslog.
> I then issued
> dpkg-reconfigure sysv-rc
> , expecting to have ntp added to the cron line of
> .etc/init.d/.depend.start. Which is not the case:
>
> $ grep ^cron /etc/init.d/.depend.start
> cron
>
> I then issued
> dpkg-reconfigure sysv-rc
AFAIK this does not do anything if you have already migrated to a
dependency-based boot system.
> , expecting to have ntp added to the cron line of
> .etc/init.d/.depend.start. Which is not the case:
>
> $ grep ^cron /etc/in
cron line of
.etc/init.d/.depend.start. Which is not the case:
$ grep ^cron /etc/init.d/.depend.start
cron: sysklogd bind9
Where I am wrong?
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.
Did you know about the big kernel power regression?
My system (laptop) is always under 100% load no matter what the
frequency I'm on (BOINC).
Some stats (kernel 2.6.39.2)
2.17GHz -> >103°C (luckily BIOS is coming to rescue)
1.67GHz -> ~94°C
1.33GHz -> ~83°C
1.00GHz -> ~74°C
Are you still going t
On Mi, 15 iun 11, 23:47:31, Andrei POPESCU wrote:
> On Mi, 15 iun 11, 12:55:54, Ralf Mardorf wrote:
> > Anyway, major distros should care about the state of the art for Linux
> > multimedia, but they, including Debian, don't.
>
> "Debian" doesn't care about anything.
Sorry, rephrasing this: Debi
On Mi, 15 iun 11, 12:55:54, Ralf Mardorf wrote:
> Anyway, major distros should care about the state of the art for Linux
> multimedia, but they, including Debian, don't.
"Debian" doesn't care about anything. If there are people interested in
improving Debian regarding multimedia it will be, other
On Wed, 2011-06-15 at 20:56 +1000, Scott Ferguson wrote:
Hi Scott :)
> much of what you seem to desire from Debian corresponds with the
> Debian Multimedia Project tasks:-
> http://wiki.debian.org/DebianMultimedia
Yes.
> Much of the
> realtime-patches have been accepted in the mainline kernel,
On 15/06/11 00:16, Ralf Mardorf wrote:
> On Tue, 2011-06-14 at 13:53 +, Camaleón wrote:
>
Hi Ralf,
much of what you seem to desire from Debian corresponds with the
Debian Multimedia Project tasks:-
http://wiki.debian.org/DebianMultimedia
"The Debian Multimedia project aims to make
On Wed, 2011-06-15 at 11:49 +0300, Andrei POPESCU wrote:
> BTW, are you aware of 64studio?
> http://www.64studio.com/
The best multimedia distro I know. I suspect Planet CCRMA as being
equal, but it's a rpm based distro, so I suspect things to be a little
bit different to Debian. The bad with 64 S
On Ma, 14 iun 11, 15:23:16, Ralf Mardorf wrote:
> OT: Btw. 2.6.39.1 don't need a rt-patch anymore. I installed the
> outdated proprietary nvidia driver, since there's no package for the
> installer, for the current one, but I guess there's the current
> proprietary driver for the 'regular' Debian k
On 06/14/2011 09:59 PM, Ralf Mardorf wrote:
On Tue, 2011-06-14 at 16:10 +, Camaleón wrote:
[snip]
Ok, perhaps you don't have the tools to measure the load, so I won't ask
you to do it, but ...
Have you ever compared temperature and battery life when switching
between ondemand and performanc
On Tue, 14 Jun 2011 19:24:22 +0200, Ralf Mardorf wrote:
> On Tue, 2011-06-14 at 17:00 +, Camaleón wrote:
>> sm01@stt008:~$ grep -i "CONFIG_CPU_FREQ_DEFAULT_GOV"
>> /boot/config-2.6.26-2-amd64 CONFIG_CPU_FREQ_DEFAULT_GOV_PERFORMANCE=y #
>> CONFIG_CPU_FREQ_DEFAULT_GOV_POWERSAVE is not set #
>> C
On Tue, 2011-06-14 at 17:00 +, Camaleón wrote:
> sm01@stt008:~$ grep -i "CONFIG_CPU_FREQ_DEFAULT_GOV"
> /boot/config-2.6.26-2-amd64
> CONFIG_CPU_FREQ_DEFAULT_GOV_PERFORMANCE=y
> # CONFIG_CPU_FREQ_DEFAULT_GOV_POWERSAVE is not set
> # CONFIG_CPU_FREQ_DEFAULT_GOV_USERSPACE is not set
> # CONFIG_C
On Tue, 14 Jun 2011 18:29:36 +0200, Ralf Mardorf wrote:
> On Tue, 2011-06-14 at 16:10 +, Camaleón wrote: [snip]
>
> Ok, perhaps you don't have the tools to measure the load, so I won't ask
> you to do it, but ...
>
> Have you ever compared temperature and battery life when switching
> betwee
On Wed, 2011-06-15 at 00:34 +0800, Jimmy Wu wrote:
> > I assume that is so people who want something else will be able to
> > change it without needing to recompile the kernel.
Correct, but they have to know about a scrip ;). I don't think they do
know, excepted of the experts ;).
Since my kernel
On Tue, 2011-06-14 at 18:29 +0200, Ralf Mardorf wrote:
> On Tue, 2011-06-14 at 16:10 +, Camaleón wrote:
> [snip]
>
> Ok, perhaps you don't have the tools to measure the load, so I won't ask
> you to do it, but ...
>
> Have you ever compared temperature and battery life when switching
> betwee
Sorry, re-sending to list - gmail doesn't reply-to on debian-user properly.
On Wed, Jun 15, 2011 at 00:33, Jimmy Wu wrote:
> On Wed, Jun 15, 2011 at 00:29, Ralf Mardorf
> wrote:
>> On Tue, 2011-06-14 at 16:15 +, Camaleón wrote:
>>> On Tue, 14 Jun 2011 18:02:40 +0200, Ralf Mardorf wrote:
>>>
On Tue, 2011-06-14 at 16:10 +, Camaleón wrote:
[snip]
Ok, perhaps you don't have the tools to measure the load, so I won't ask
you to do it, but ...
Have you ever compared temperature and battery life when switching
between ondemand and performance?
How much is the difference on your machine
On Tue, 14 Jun 2011 18:02:40 +0200, Ralf Mardorf wrote:
> Why not using ondemand set by the kernel's default governor?
Because then you will force users to recompile the kernel in order they
can change it. And that's simply silly. Didn't you want a sytem without
hassle?
> My desktop kernels a
On Tue, 14 Jun 2011 17:51:51 +0200, Ralf Mardorf wrote:
> On Tue, 2011-06-14 at 14:54 +, Camaleón wrote:
>> > Is there any CPU where CPU frequency scaling really makes a
>> > difference for load?
>>
>> Define "load" in your context.
>
> 'Load' should be for 'ampere'
>
> Ampere = Volt / Resi
On Tue, 2011-06-14 at 16:29 +0100, Darac Marjal wrote:
> On Tue, Jun 14, 2011 at 04:16:38PM +0200, Ralf Mardorf wrote:
> > On Tue, 2011-06-14 at 13:53 +, Camaleón wrote:
> >
> >
> [cut]
> >
> > > It's not about "load" but "frequency speed" and my micro reduces its
> > > cycles from 2.8 Ghz.
On Tue, 2011-06-14 at 15:55 +0100, Lisi wrote:
> On Tuesday 14 June 2011 15:16:38 Ralf Mardorf wrote:
> > And there are billions of users who tried to switch from Windows to
> > Linux just regarding to ethical reasons or better software regarding to
> > their needs and they all need to use Windows,
On Tue, 2011-06-14 at 14:54 +, Camaleón wrote:
> > Is there any CPU where CPU frequency scaling really makes a difference
> > for load?
>
> Define "load" in your context.
'Load' should be for 'ampere'
Ampere = Volt / Resistance
Watt = Volt * Ampere
Caused heat and battery durability depend
On Tue, Jun 14, 2011 at 04:16:38PM +0200, Ralf Mardorf wrote:
> On Tue, 2011-06-14 at 13:53 +, Camaleón wrote:
>
>
[cut]
>
> > It's not about "load" but "frequency speed" and my micro reduces its
> > cycles from 2.8 Ghz. (normal run) to 2.0 Ghz (idle+ondemad) which I
> > prefer. Why wasting
On Tuesday 14 June 2011 15:16:38 Ralf Mardorf wrote:
> And there are billions of users who tried to switch from Windows to
> Linux just regarding to ethical reasons or better software regarding to
> their needs and they all need to use Windows, because the Linux
> community don't care about people
On Tue, 14 Jun 2011 16:16:38 +0200, Ralf Mardorf wrote:
> On Tue, 2011-06-14 at 13:53 +, Camaleón wrote:
>
>> But that's a known issue, right? Or at least is not different from
>> other problems that any user which requires a specific/fine grained
>> setup or tweaks may experience.
>
> Yes a
On Tue, 2011-06-14 at 13:53 +, Camaleón wrote:
> But that's a known issue, right? Or at least is not different from other
> problems that any user which requires a specific/fine grained setup or
> tweaks may experience.
Yes and yes.
> But then you are enforcing a cpu frequency policy that
On Tue, 14 Jun 2011 15:23:16 +0200, Ralf Mardorf wrote:
> On Mon, 2011-06-13 at 13:28 +, Camaleón wrote:
>> > - Inexperienced people get 'mysterious' xruns using jackd.
>>
>> I don't undertsand this. Can you expand this a bit for neophytes? :-)
>
> If you install jackd and try to make music
On Mon, 2011-06-13 at 13:28 +, Camaleón wrote:
> > - Inexperienced people get 'mysterious' xruns using jackd.
>
> I don't undertsand this. Can you expand this a bit for neophytes? :-)
If you install jackd and try to make music without a real-time capable
kernel or with CPU ferquency scaling
On Du, 12 iun 11, 17:35:02, Ralf Mardorf wrote:
>
> - This can be done without this script. What is the kernel config for?
For those who don't ever compile their kernel. I assume these are the
most.
Regards,
Andrei
--
Offtopic discussions among Debian users and developers:
http://lists.alioth.
On Sun, 12 Jun 2011 17:35:02 +0200, Ralf Mardorf wrote:
> On Sun, 2011-06-12 at 13:35 +, Camaleón wrote:
>> On Sun, 12 Jun 2011 12:23:16 +0200, Ralf Mardorf wrote:
>>
>> (not sure if this post was targeted to this mailing list...)
>>
>> (...)
>>
>> > anyway, this is idiocy, hence the defaul
1 - 100 of 422 matches
Mail list logo
