On Sat 24 Sep 2022 at 18:48:13 (-0700), Ray Andrews wrote:
> On 2022-09-24 13:52, Dan Ritter wrote:
> > Ray Andrews wrote:
> > > To whom might read this. I can't boil this down to a formal bug report
> > > but
> > > for what it's worth:
> > >
> > > BULLSEYE INSTALL, 2022-09-23:
> > >
> > > Deci
On Sun, 25 Sept 2022 at 04:03, Ray Andrews wrote:
> ... I get as far as partitioning and although the disk (sdb) is
> already partitioned and formatted and working fine, it seemed to be
> impossible to just leave things as they were and install to the existing
> partitions, it kept complaining t
On Sat 24 Sep 2022 at 10:45:56 (-0700), Ray Andrews wrote:
> To whom might read this. I can't boil this down to a formal bug
> report but for what it's worth:
>
> BULLSEYE INSTALL, 2022-09-23:
>
> Decided to do a virgin install of bullseye to my /dev/sdb while
> keeping /dev/sda devoted to Stret
On 2022-09-24 13:52, Dan Ritter wrote:
Ray Andrews wrote:
To whom might read this. I can't boil this down to a formal bug report but
for what it's worth:
BULLSEYE INSTALL, 2022-09-23:
Decided to do a virgin install of bullseye to my /dev/sdb while keeping
/dev/sda devoted to Stretch. Got t
Ray Andrews wrote:
> To whom might read this. I can't boil this down to a formal bug report but
> for what it's worth:
>
>
> BULLSEYE INSTALL, 2022-09-23:
>
> Decided to do a virgin install of bullseye to my /dev/sdb while keeping
> /dev/sda devoted to Stretch. Got the installer onto a USB sti
> From: anonym...@hoi-polloi.org
> To: debian-user@lists.debian.org
> Hello!
> Today I downloaded the latest release of Debian, the 9.1 i386 XFCE Live. I
> downloaded as a torrent by the earlier Debian 9.0.1 x64 XFCE. I experienced
> (sorry my poor english!) that the LibreOffice Writer couldn"t s
Hi.
On Wed, Sep 09, 2015 at 08:51:30PM +0200, Javier Barroso wrote:
> > 8) This part's 'grep .' meaning currently escapes me:
> >
> > open my $grep_status, "grep-status -n -FPackage '' ".
> > " -s Package -s Architecture".
> > " -s Version -s Status -n |".
> > "grep . |
Hello,
On Wed, Sep 9, 2015 at 7:43 PM, Reco wrote:
> Hi.
>
> On Wed, Sep 09, 2015 at 07:23:42PM +0200, Javier Barroso wrote:
>> Hello,
>>
>> I would like to recieve feed back about a script which I have just
>> upload to github.
>>
>> https://github.com/i5513/apt-history-gui
>>
>> It is working
Hi.
On Wed, Sep 09, 2015 at 07:23:42PM +0200, Javier Barroso wrote:
> Hello,
>
> I would like to recieve feed back about a script which I have just
> upload to github.
>
> https://github.com/i5513/apt-history-gui
>
> It is working on my computer, but I cannot be sure it will work on
> other de
On 03/15/2013 10:35 AM, Darac Marjal wrote:
Talk to the good people on the debian-mentors list.
Thank you very much Darac Marjal!
Have a nice time,
Benjamin
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists
On Thu, Mar 14, 2013 at 06:59:20PM +0100, benjamin kent wrote:
> Hello everybody.
>
> Lately I encountered trouble with a MP3 player using the FAT file-system.
> As others had this problem, too , I wrote a little tool.
>
> http://sourceforge.net/projects/plgen/?source=navbar
>
> https://freecode
On Sun, 13 May 2012 15:06:35 +0200, Mirko Parthey wrote:
> On Tue, May 08, 2012 at 05:56:49PM +, Camaleón wrote:
>> I am considering in adding a couple of PCI based Eicon Diva 2.02
>> "passive" cards on a system running hylafax server. The fax server is
>> now using a couple of external RS-232
On Tue, May 08, 2012 at 05:56:49PM +, Camaleón wrote:
> I am considering in adding a couple of PCI based Eicon Diva 2.02
> "passive" cards on a system running hylafax server. The fax server is now
> using a couple of external RS-232 modems that work like a charm but as I
> have a pair of unu
> > I stop using huge tmpfs for tmp since it gains nothing for me.
>
> Okay, so no more worries about this. I will keep the old-good default for
> "/tmp" then.
>
> Greetings,
I also got in problems, when k3b asked me for a temporary place for a
temporary ISO. I choose /tmp (good choice for no
On Sun, 04 Mar 2012 18:12:09 +0900, Osamu Aoki wrote:
> Hi,
>
> I join too late but ... (I do not use tmpfs for /tmp)
Time does not matter when good feedback comes to place :-)
> On Tue, Nov 29, 2011 at 04:13:05PM +, Camaleón wrote:
>> On Mon, 28 Nov 2011 18:07:43 +, Camaleón wrote:
>>
Hi,
I join too late but ... (I do not use tmpfs for /tmp)
On Tue, Nov 29, 2011 at 04:13:05PM +, Camaleón wrote:
> On Mon, 28 Nov 2011 18:07:43 +, Camaleón wrote:
>
> > I'm running an updated wheezy and today faced with this little
> > problematic.
>
> (...)
>
> > Okay, so /tmp is full
On Thu, Mar 01, 2012 at 02:54:30AM +1300, Chris Bannister wrote:
> On Wed, Feb 22, 2012 at 08:59:38AM +, Dom wrote:
> > I think it would have been nice to have a warning of this change of
> > behaviour. I have apt-listchanges installed and I'm sure it didn't
> > notify me of any changes.
>
> T
On Wed, Feb 22, 2012 at 08:59:38AM +, Dom wrote:
> I think it would have been nice to have a warning of this change of
> behaviour. I have apt-listchanges installed and I'm sure it didn't
> notify me of any changes.
True, but there was a "discussion" on debian-devel titled:
"/tmp as tmpfs a
Dom wrote:
> I think it would have been nice to have a warning of this change of
> behaviour. I have apt-listchanges installed and I'm sure it didn't
> notify me of any changes.
These types of changes are discussed in debian-devel. In a released
system they would be in the release notes. But sin
On 22/02/12 01:10, Seb wrote:
I just discovered to my horror /tmp is handled by a tmpfs system that
allocates by default a percentage of RAM that happens to be too small
for my use of /tmp. What is the Debianish way to avoid using this
system for /tmp so that it uses whatever is available on /?
John Hasler wrote:
> Bob writes:
> > Did you mean TMPDIR?
>
> Yes. Note that you may want to provide for cleanup. Consider tmpreaper.
I like tmpreaper quite a bit. It is great for /tmp and /var/tmp. For
$HOME/tmp I don't think it is needed. For $HOME/tmp just running find
$HOME/tmp with some
On Tue, 21 Feb 2012 19:55:36 -0700,
Bob Proulx wrote:
> John Hasler wrote:
>> Seb writes: > I just discovered to my horror /tmp is handled by a
>> tmpfs system that > allocates by default a percentage of RAM that
>> happens to be too small > for my use of /tmp. What is the Debianish
>> way to av
Bob writes:
> Did you mean TMPDIR?
Yes. Note that you may want to provide for cleanup. Consider tmpreaper.
> Although not every program is coded to honor TMPDIR...
File bug reports.
--
John Hasler
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscr
Seb wrote:
> Bob Proulx wrote:
> > Set RAMTMP=no in the /etc/default/rcS file.
> > # sed --in-place 's/RAMTMP=.*/RAMTMP=no/' /etc/default/rcS
>
> Thank you! With this modification, does /tmp still get cleared after
> each reboot?
Yes. That is controlled by TMPTIME=0 in the same /etc/default/r
John Hasler wrote:
> Seb writes:
> > I just discovered to my horror /tmp is handled by a tmpfs system that
> > allocates by default a percentage of RAM that happens to be too small
> > for my use of /tmp. What is the Debianish way to avoid using this
> > system for /tmp so that it uses whatever is
Seb writes:
> I just discovered to my horror /tmp is handled by a tmpfs system that
> allocates by default a percentage of RAM that happens to be too small
> for my use of /tmp. What is the Debianish way to avoid using this
> system for /tmp so that it uses whatever is available on /?
Set TEMPDIR
On Tue, 21 Feb 2012 18:17:15 -0700,
Bob Proulx wrote:
> Seb wrote:
>> I just discovered to my horror /tmp is handled by a tmpfs system that
>> allocates by default a percentage of RAM that happens to be too small
>> for my use of /tmp. What is the Debianish way to avoid using this
>> system for
Seb wrote:
> I just discovered to my horror /tmp is handled by a tmpfs system that
> allocates by default a percentage of RAM that happens to be too small
> for my use of /tmp. What is the Debianish way to avoid using this
> system for /tmp so that it uses whatever is available on /?
Set RAMTMP=n
On Mon, 28 Nov 2011 19:44:46 +,
Dom wrote:
> On 28/11/11 18:07, Camaleón wrote:
>> Hello,
>> I'm running an updated wheezy and today faced with this little
>> problematic.
>> While running Midnight Commander to open (on-the-fly decompression
>> for browsing the archive) the kernel source pa
On Mon, 28 Nov 2011 18:07:43 +, Camaleón wrote:
> I'm running an updated wheezy and today faced with this little
> problematic.
(...)
> Okay, so /tmp is full. Fine. I know how to solve it but I can foresee
> more situations like this in the future so some questions arise. As the
> current tm
On 28/11/11 18:07, Camaleón wrote:
Hello,
I'm running an updated wheezy and today faced with this little
problematic.
While running Midnight Commander to open (on-the-fly decompression for
browsing the archive) the kernel source package (a ~75 MiB .tar.bz2 file)
I got this error:
http://picpas
Camaleón wrote:
> /dev/sda2247G 7,7G 239G 4% /
> tmpfs423M 423M 0 100% /tmp <--- here!
>
> Okay, so /tmp is full. Fine. ...
Especially when you have 250G of space it seems egregious to clamp it
down to only 423M.
> 1/ How many room should be set for a "/tmp"
On 28/11/11 19:07, Camaleón wrote:
Hello,
I'm running an updated wheezy and today faced with this little
problematic.
While running Midnight Commander to open (on-the-fly decompression for
browsing the archive) the kernel source package (a ~75 MiB .tar.bz2 file)
I got this error:
http://picp
On Mon, 01 Aug 2011 11:23:23 +, Camaleón wrote:
> On Mon, 01 Aug 2011 10:07:33 +0300, Volkan YAZICI wrote:
(...)
>> BTW, there appears to be a significant problem with your wifi channel
>> selection. That is,
>>
>> 1. There are actually 3 useable channels in the wifi spectrum: 1, 6,
>> 11.
On Mon, 01 Aug 2011 10:07:33 +0300, Volkan YAZICI wrote:
> On Sun, 31 Jul 2011 14:53:03 + (UTC), Camaleón writes:
(...)
>> Okay, let's make a brute-force test. I've removed the power cord of the
>> netbook and walked next to the AP, et voilà, now it associates fine...
>> go figure :-o
>
> I
On Sun, 31 Jul 2011 14:53:03 + (UTC), Camaleón writes:
> Tried with both ("-D nl80211" and reduced conf file) but I get the same ;-
> (
>
> ***
> Trying to associate with 00:26:44:df:60:91 (SSID='WLAN_6D' freq=2452 MHz)
> Authentication with 00:26:44:df:60:91 timed out.
> ***
>
> It cannot even
On Sun, 31 Jul 2011 15:07:28 +0100, Brian wrote:
> On Sun 31 Jul 2011 at 13:22:45 +, Camaleón wrote:
>
>> On Sun, 31 Jul 2011 15:24:11 +0300, Volkan YAZICI wrote:
>>
>> > Oh, and I forgot to say in the previous mail: Turn everything
>> > fiddling with the wifi interfaces off, that is, nm, ho
On Sun 31 Jul 2011 at 13:22:45 +, Camaleón wrote:
> On Sun, 31 Jul 2011 15:24:11 +0300, Volkan YAZICI wrote:
>
> > Oh, and I forgot to say in the previous mail: Turn everything fiddling
> > with the wifi interfaces off, that is, nm, hostapd, etc., before trying
> > any manual method.
>
> Hey
On Sun, 31 Jul 2011 15:24:11 +0300, Volkan YAZICI wrote:
> On Sun, 31 Jul 2011 12:02:02 + (UTC), Camaleón writes:
(...)
>> But when I try to connect, both of my wifi cards fail:
>>
>> wlan0 → broadcom 4313+brcmsmac
(...)
>> Authentication with 00:26:44:df:60:91 timed out.
>> wlan2 → ral
On Sun, 31 Jul 2011 12:02:02 + (UTC), Camaleón writes:
> In testing I have "2.6.39-2686-pae"
> [...]
>
> Good idea. Done...
>
> /etc/wpa_supplicant/wpa_supplicant.conf
>
> # WPA-PSK/TKIP
>
> ctrl_interface=/var/run/wpa_supplicant
>
> network={
> ssid="WLAN_6D"
> key_mgmt=WPA-PSK
> p
On Sat, 30 Jul 2011 21:52:49 +0300, Volkan YAZICI wrote:
> On Mon, 25 Jul 2011 16:46:56 + (UTC), Camaleón writes:
(...)
>> I wonder if someone is currently using this driver and what are his/her
>> experiences.
>
> I'm using brcmsmac since 1 year without a problem.
(...)
Thanks for repliy
On Mon, 25 Jul 2011 16:46:56 + (UTC), Camaleón writes:
> Our cell phone provider has given us a netbook that embeds a broadcom
> 4313 wifi chipset¹.
>
> This card seems to be supported by the new -and open source- brcmsmac
> driver² (still in a staging development) but I am having problems to
On Mon, 25 Jul 2011 16:46:56 +, Camaleón wrote:
(...)
> I wonder if someone is currently using this driver and what are his/her
> experiences.
>
> ¹http://wiki.debian.org/brcm80211
Ping...
No one is using a broadcom 4313 wifi chipset with the new "brcmsmac"
driver? :-?
Greetings,
--
C
On Thu, Dec 9, 2010 at 10:26 PM, Sven Joachim wrote:
> On 2010-12-09 18:55 +0100, Camaleón wrote:
>
>> I basically see two issues here:
>>
>> 1/ We lack? for a "recommended way/Debian way" for disabling scripts
>> (this thread is plenty of alternatives and tips for doing it but
>> documentation is
On 2010-12-09 18:55 +0100, Camaleón wrote:
> I basically see two issues here:
>
> 1/ We lack? for a "recommended way/Debian way" for disabling scripts
> (this thread is plenty of alternatives and tips for doing it but
> documentation is not very clear on the matter). I think it is important
> f
On Thu, Dec 09, 2010 at 04:50:52AM -0500, Tom H wrote:
> On Thu, Dec 9, 2010 at 2:56 AM, Joel Roth wrote:
> > On Wed, Dec 08, 2010 at 08:24:51PM +0100, Sven Joachim wrote:
> >> On 2010-12-07 17:21 +0100, Camaleón wrote:
>
>
> >> > A month ago, I disabled Network Manager service in my Squeeze sys
On Fri, 10 Dec 2010 01:33:20 +0900, Osamu Aoki wrote:
> On Thu, Dec 09, 2010 at 08:15:08AM +, Camaleón wrote:
>> On Thu, 09 Dec 2010 07:37:19 +0100, Sven Joachim wrote:
>>
>> > On 2010-12-08 23:41 +0100, Javier Barroso wrote:
>> >
>> >> On Wed, Dec 8, 2010 at 8:24 PM, Sven Joachim wrote:
>>
Hi,
On Thu, Dec 09, 2010 at 08:15:08AM +, Camaleón wrote:
> On Thu, 09 Dec 2010 07:37:19 +0100, Sven Joachim wrote:
>
> > On 2010-12-08 23:41 +0100, Javier Barroso wrote:
> >
> >> On Wed, Dec 8, 2010 at 8:24 PM, Sven Joachim wrote:
> >>>
> >>> You should use "update-rc.d network-manager disa
Sven Joachim wrote:
On 2010-12-09 09:15 +0100, Camaleón wrote:
On Thu, 09 Dec 2010 07:37:19 +0100, Sven Joachim wrote:
On 2010-12-08 23:41 +0100, Javier Barroso wrote:
On Wed, Dec 8, 2010 at 8:24 PM, Sven Joachim wrote:
You should use "update-rc.d network-manager disable" instead. See
upd
On Thu, 09 Dec 2010 07:07:11 -0500, Tom H wrote:
> On Thu, Dec 9, 2010 at 6:11 AM, Camaleón wrote:
(...)
>> The warning can be ignored but the service levels are not touched and
>> it does not work as expected (meaning, the service is not disabled at
>> all).
>
> It was silly of me to say that
On Thu, Dec 9, 2010 at 6:11 AM, Camaleón wrote:
> On Thu, 09 Dec 2010 03:54:11 -0500, Tom H wrote:
>> On Wed, Dec 8, 2010 at 10:38 AM, Camaleón wrote:
>>
>> Whenever I use update-rc.d on a sid box to stop/remove/disable, I get a
>> "using concurrency based boot sequencing" message with a warning a
On Thu, 09 Dec 2010 03:54:11 -0500, Tom H wrote:
> On Wed, Dec 8, 2010 at 10:38 AM, Camaleón wrote:
(...)
>> Mmm... man page says by using "defaults" the service should be put in
>> sequence number 20 (unless there are any conflicts):
>>
>> t...@debian:~$ ls -l /etc/rc* | grep network-manager
>
On Thu, Dec 9, 2010 at 2:56 AM, Joel Roth wrote:
> On Wed, Dec 08, 2010 at 08:24:51PM +0100, Sven Joachim wrote:
>> On 2010-12-07 17:21 +0100, Camaleón wrote:
>> > A month ago, I disabled Network Manager service in my Squeeze system so
>> > it doesn't run on start up. I wanted to keep NM install
On Wed, Dec 8, 2010 at 5:41 PM, Javier Barroso wrote:
> On Wed, Dec 8, 2010 at 8:24 PM, Sven Joachim wrote:
>> On 2010-12-07 17:21 +0100, Camaleón wrote:
>>
>>
>>> A month ago, I disabled Network Manager service in my Squeeze system so
>>> it doesn't run on start up. I wanted to keep NM installed
On 2010-12-09 09:15 +0100, Camaleón wrote:
> On Thu, 09 Dec 2010 07:37:19 +0100, Sven Joachim wrote:
>
>> On 2010-12-08 23:41 +0100, Javier Barroso wrote:
>>
>>> On Wed, Dec 8, 2010 at 8:24 PM, Sven Joachim wrote:
You should use "update-rc.d network-manager disable" instead. See
u
On Wed, Dec 8, 2010 at 10:38 AM, Camaleón wrote:
> On Wed, 08 Dec 2010 08:37:52 -0500, Tom H wrote:
>> On Wed, Dec 8, 2010 at 8:23 AM, Camaleón wrote:
>>> On Tue, 07 Dec 2010 23:46:53 +0100, Jochem Kossen wrote:
>
You didn't disable network-manager. You removed the startup scripts
which
On 2010-12-08 01:21 +0100, Arthur Machlas wrote:
> Problem is, or at least, what I think the problem with that is, is
> that insserv is installed by default, and concurrent is now the
> default as well. So whenever a system service is added removed,
> changed or when insserv is called by some othe
On Thu, 09 Dec 2010 07:37:19 +0100, Sven Joachim wrote:
> On 2010-12-08 23:41 +0100, Javier Barroso wrote:
>
>> On Wed, Dec 8, 2010 at 8:24 PM, Sven Joachim wrote:
>>>
>>> You should use "update-rc.d network-manager disable" instead. See
>>> update-rc.d(8).
>> I think update-rc.d manpage should
On Wed, Dec 08, 2010 at 08:24:51PM +0100, Sven Joachim wrote:
> On 2010-12-07 17:21 +0100, Camaleón wrote:
>
>
> > A month ago, I disabled Network Manager service in my Squeeze system so
> > it doesn't run on start up. I wanted to keep NM installed (just in case)
> > but preferred to use the ol
On 2010-12-08 23:41 +0100, Javier Barroso wrote:
> On Wed, Dec 8, 2010 at 8:24 PM, Sven Joachim wrote:
>>
>> You should use "update-rc.d network-manager disable" instead. See
>> update-rc.d(8).
> I think update-rc.d manpage should then change example which Camaleon
> referenced in her solved pos
On Wed, Dec 8, 2010 at 8:24 PM, Sven Joachim wrote:
> On 2010-12-07 17:21 +0100, Camaleón wrote:
>
>
>> A month ago, I disabled Network Manager service in my Squeeze system so
>> it doesn't run on start up. I wanted to keep NM installed (just in case)
>> but preferred to use the old "ifup" network
On 2010-12-07 17:21 +0100, Camaleón wrote:
> A month ago, I disabled Network Manager service in my Squeeze system so
> it doesn't run on start up. I wanted to keep NM installed (just in case)
> but preferred to use the old "ifup" network setup method.
>
> So I issued "update-rc.d network-manage
On Tue, 07 Dec 2010 14:05:20 -0700, green wrote:
> Camaleón wrote at 2010-12-07 09:21 -0700:
>> So I issued "update-rc.d network-manager remove" and also disabled
>> gnome NM applet from being started. So far so good, no more NM running
>> at booting.
>
> You probably want to use "disable" instea
No one else has mentioned it:
chmod a-x /etc/init.d/script-name
Works for me :-)
Cheers
--
Joel Roth
--
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/2010120816115
On Tue, 07 Dec 2010 15:46:50 -0700, Bob Proulx wrote:
> Arthur Machlas wrote:
>> Camaleón wrote:
>> > Are you suggesting to manually edit the "/etc/init.d/network-manager"
>> > script header to fit my needs? Correct me if I'm wrong, but I expect
>> > this file (as any file located here) can be upd
On Wed, 08 Dec 2010 08:37:52 -0500, Tom H wrote:
> On Wed, Dec 8, 2010 at 8:23 AM, Camaleón wrote:
>> On Tue, 07 Dec 2010 23:46:53 +0100, Jochem Kossen wrote:
(...)
>>> You didn't disable network-manager. You removed the startup scripts
>>> which were correctly put back by the update.
>>>
>>> O
On Wed, Dec 8, 2010 at 8:23 AM, Camaleón wrote:
> On Tue, 07 Dec 2010 23:46:53 +0100, Jochem Kossen wrote:
> On Tue, 07 Dec 2010 23:46:53 +0100, Jochem Kossen wrote:
>> On Tue, Dec 07, 2010 at 04:21:38PM +, Camale?n wrote:
>>>
>>> A month ago, I disabled Network Manager service in my Squeeze s
On Tue, 07 Dec 2010 23:46:53 +0100, Jochem Kossen wrote:
On Tue, 07 Dec 2010 23:46:53 +0100, Jochem Kossen wrote:
> On Tue, Dec 07, 2010 at 04:21:38PM +, Camale?n wrote:
>> Hello,
>>
>> A month ago, I disabled Network Manager service in my Squeeze system so
>> it doesn't run on start up. I w
On Tue, Dec 7, 2010 at 2:35 PM, Camaleón wrote:
> On Tue, 07 Dec 2010 10:51:11 -0600, Arthur Machlas wrote:
>>
>> I'd definitely hold off on the bug report. I think you should look at
>> the lsb headers of the network-manager script in /etc/init.d and change
>> them to stop on all levels, start on
On Tue, Dec 7, 2010 at 6:16 PM, Paul Lane wrote:
> On Tue, Dec 7, 2010 at 10:21 AM, Camaleón wrote:
>> Hello,
>>
>> A month ago, I disabled Network Manager service in my Squeeze system so
>> it doesn't run on start up. I wanted to keep NM installed (just in case)
>> but preferred to use the old "
On Tue, Dec 7, 2010 at 10:21 AM, Camaleón wrote:
> Hello,
>
> A month ago, I disabled Network Manager service in my Squeeze system so
> it doesn't run on start up. I wanted to keep NM installed (just in case)
> but preferred to use the old "ifup" network setup method.
>
> So I issued "update-rc.d
On Tue, Dec 07, 2010 at 04:21:38PM +, Camale?n wrote:
> Hello,
>
> A month ago, I disabled Network Manager service in my Squeeze system so
> it doesn't run on start up. I wanted to keep NM installed (just in case)
> but preferred to use the old "ifup" network setup method.
>
> So I issued
Arthur Machlas wrote:
> Camaleón wrote:
> > Are you suggesting to manually edit the "/etc/init.d/network-manager"
> > script header to fit my needs? Correct me if I'm wrong, but I expect this
> > file (as any file located here) can be updated at any time and so
> > replacing any of the customized v
Camaleón wrote at 2010-12-07 09:21 -0700:
> So I issued "update-rc.d network-manager remove" and also disabled gnome
> NM applet from being started. So far so good, no more NM running at
> booting.
You probably want to use "disable" instead of "remove". See update-rc.d(8).
signature.asc
Descr
On Tue, Dec 7, 2010 at 1:35 PM, Camaleón wrote:
> On Tue, 07 Dec 2010 10:51:11 -0600, Arthur Machlas wrote:
>
>> On Tue, Dec 7, 2010 at 10:21 AM, Camaleón wrote:
>
> (...)
>
>>> Before I fill a bug report (I think a service that has been manually
>>> disabled should keep its state regardless any f
On Tue, 07 Dec 2010 10:51:11 -0600, Arthur Machlas wrote:
> On Tue, Dec 7, 2010 at 10:21 AM, Camaleón wrote:
(...)
>> Before I fill a bug report (I think a service that has been manually
>> disabled should keep its state regardless any further update it can be
>> applied afterwards), I would lik
On Tue, Dec 7, 2010 at 10:21 AM, Camaleón wrote:
> Hello,
Hi
> A month ago, I disabled Network Manager service in my Squeeze system so
> it doesn't run on start up. I wanted to keep NM installed (just in case)
> but preferred to use the old "ifup" network setup method.
>
> So I issued "update-rc
On Wed, Aug 20, 2003 at 05:16:19PM +0300, Sourian wrote:
| Who's spamming us???
Poor quality bots. (see how an autoresponder generated that message)
I suspect that some instance of SoBig.F used the address of this
list when sending itself to that autoresponder. The autoresponder
then decides to
Who's spamming us???
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]
Sent: Wednesday, August 20, 2003 2:48 PM
To: [EMAIL PROTECTED]
Subject: feedback
Thank you for your feed back.
Your feed back is important to us to maintain a high quality website. If
you have m
79 matches
Mail list logo
