Date: Tue, 28 Aug 2007 16:51:11 -0400
From: "Mike" <mikewk147@oh.rr.com>
To: <debian-user@lists.debian.org>
Subject: Re: Shut down or leave on?
Message-ID: <000e01c7e9b5$2b099870$6201a8c0@mkuhar2>
Content-Type: text/plain;
format=flowed;
charset="iso-8859-1";
reply-type=original
Content-Transfer-Encoding: 7bit
> How much would all this apply to a laptop? I mean, are
> they considered more robust or less? w/ regard to powering off and on?
>
> Cavan
>
> On 8/28/07, Mike <mikewk147@oh.rr.com> wrote:
>>
>> ----- Original Message -----
>> From: "Raquel" <raquel@thericehouse.net>
>> To: <debian-user@lists.debian.org>
>> Sent: Tuesday, August 28, 2007 1:50 PM
>> Subject: Re: Shut down or leave on?
>>
>>
>> > On Tue, 28 Aug 2007 09:45:51 -0700
>> > Jeff <debian@waysoft.com> wrote:
>> >
>> >> Raquel wrote:
>> >> > On Tue, 28 Aug 2007 11:28:35 -0400
>> >> > "Richard Carter" <carter.r.a.l@gmail.com> wrote:
>> >> >
>> >> >> Hi Folks,
>> >> >>
>> >> >> Is it better to leave a system running all the time or is it
>> >> >> better to shut it down over night, on weekends, holidays etc?
>> >> >>
>> >
>> > <snip>
>> >
>> >> >>
>> >> >> I'd appreciate your advice.
>> >> >>
>> >> >> Robin Carter
>> >> >>
>> >> >
>> >> > I've always gone for leaving my machines on. I feel there is
>> >> > less wear and tear on components by leaving the machine on.
>> >> >
>> >> Specifically, as I understand it, thermal shock to minuscule
>> >> electronic components during power-on. In the past, I've lost a
>> >> number of motherboards and processors due (presumably) to this
>> >> effect. Since keeping my machines on 24/7 (for several years
>> >> now), I have not had any such problems.
>> >>
>> >> Jeff
>> >>
>> >
>> > I also understand that when the hard disks get power that the
>> > platters torque just a tad, if not causing heads to come into
>> > contact with the platter, at least causing wear on bearings.
>> >
>>
>> The stress created during the cool down and heat up cycle, between
>> powering
>> off and powering on, can cause microfractures in the solid state
>> components.
>> Further, on the lower quality powersupplies, the power on sequence can
>> cause
>> current surges that can also weaken electronic components, although the
>> filtering in the present day switching powersupplies is supposed to
>> eliminate this. The amount electricity usage from present day devices is
>> minimal compared to replacement costs for those devices. I say, leave it
>> on.
>>
>> -mike
A really good question. Pretty much all the components are the same, except
that they try to user lower microprocessors in laptops, meaning heat
generators. The also try to use other lower power components as well. But
here is where we come against a stumbling block as to what I and others have
already said. Unlike the desktop machines, there just isn't the realestate
available in a laptop. Less realestate, less room for thins like fans. The
fans present don't have near the air flow as their bigger cousins.
Plus,factor in the recent problems with batteries catching fire. I know
that there was a big recall on the batteries in question, but this answer
has to be tempered for all those who haven't taken advantage of that recall.
Despite the previous answer, the same things apply, I would say, turn it
off. As far as laptops are concerned, I would turn it off when not in use.
I have two desktops and one laptop. I keep the desktops on 24x7. The
laptop I turn off whenever not in use. Because of being battery powered,
there are less current surges on power on with laptop. IMHO.
-mike
>>
>> > --
>> > Raquel
>> > ============================================================
>> > Our particular principles of religion are a subject of
>> > accountability to our god alone. I enquire after no man's and
>> > trouble none with mine; nor is it given to us in this life to know
>> > whether yours or mine, our friend's or our foe's, are exactly the
>> > right.
>> > --Thomas Jefferson
>> >
>> >
>> > --
>> > To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
>> > with a subject of "unsubscribe". Trouble? Contact
>> > listmaster@lists.debian.org
>> >
>>
>>
>> --
>> To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
>> with a subject of "unsubscribe". Trouble? Contact
>> listmaster@lists.debian.org
>>
>>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
Date: Tue, 28 Aug 2007 16:53:27 -0400
From: Celejar <celejar@gmail.com>
To: debian-user@lists.debian.org
Subject: Re: WYSIWYG editor
Message-Id: <20070828165327.dfd92d3d.celejar@gmail.com>
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
On Tue, 28 Aug 2007 15:49:03 -0500
Sam Leon <leon.mailinglist.36@gmail.com> wrote:
> Loeghmon T. Nejad wrote:
> > What do you recommend as a good, practical WYSIWYG editor for creating
> > simple web pages, with mostly text, some graphics and pdf, for debian
> > Lenny please? Thanks.
> >
> > --
> > Regards,
>
> I would like to know too. I think us html noobs using linux are just
> out of luck :(
>
> Quanta plus has a very crappy one that I have been using though.
>
> Sam
This gets asked here periodically; I'm not sure if there's a really good
WYSIWYG solution. Try this thread:
http://lists.debian.org/debian-user/2007/01/msg02822.html
Celejar
--
mailmin.sourceforge.net - remote access via secure (OpenPGP) email
ssuds.sourceforge.net - A Simple Sudoku Solver and Generator
Date: Tue, 28 Aug 2007 22:05:08 +0100
From: Graham <doubleyou@loftmail.com>
To: debian-user@lists.debian.org
Subject: Re: fstab and removable usb drives
Message-ID: <20070828220508.30dcf8d0@pluto.lan>
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
On Tue, 28 Aug 2007 15:23:21 -0400
Celejar <celejar@gmail.com> wrote:
> Thanks. The problem was my non-zero last field, as per my other
> posts. BTW, mounting by label / UUID is often a better idea,
> especially for removable storage, since it ensures consistency of
> mount points even when the connection order varies. This may not be
> important to you, but it is to many.
Yes, you're right. I haven't really bothered with UUID, simply because
I've never been in a position where I've had to connect two removable
storage devices at the same time, so haven't really had the need for
it... plus I'm lazy and stuck in an old routine. ;)
Glad your issue is resolved.
Graham
Date: Tue, 28 Aug 2007 14:33:04 -0500
From: "Mumia W.." <paduille.4061.mumia.w+nospam@earthlink.net>
To: icelinux@icelinux.net
Cc: Debian User List <debian-user@lists.debian.org>
Subject: Re: question about kernel source packages
Message-ID: <46D47870.3000606@earthlink.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
On 08/28/2007 02:15 PM, icelinux@icelinux.net wrote:
> Quoting "Mumia W.." <paduille.4061.mumia.w+nospam@earthlink.net>:
>
>> On 08/28/2007 12:02 PM, icelinux@icelinux.net wrote:
>>> I notice there is a source package for the kernel and a package of
>>> debian patches. Has the kernel source already been patched or would
>>> one need to patch it with all of the included debian patches when
>>> building a custom kernel?
>>>
>>
>> It's already patched.
>
> Doublechecking, you are absolutely positive?
>
>
Read the files README.Debian and Debian.src.changelog in the kernel
source directory.
If those files exist, and if their contents suggest that the kernel has
been patched (they do here), then the kernel source has already been
patched.
Date: Tue, 28 Aug 2007 17:10:35 -0400
From: Celejar <celejar@gmail.com>
To: debian-user@lists.debian.org
Subject: Re: fstab and removable usb drives
Message-Id: <20070828171035.9ce0a157.celejar@gmail.com>
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
On Tue, 28 Aug 2007 22:05:08 +0100
Graham <doubleyou@loftmail.com> wrote:
> On Tue, 28 Aug 2007 15:23:21 -0400
> Celejar <celejar@gmail.com> wrote:
>
> > Thanks. The problem was my non-zero last field, as per my other
> > posts. BTW, mounting by label / UUID is often a better idea,
> > especially for removable storage, since it ensures consistency of
> > mount points even when the connection order varies. This may not be
> > important to you, but it is to many.
>
> Yes, you're right. I haven't really bothered with UUID, simply because
> I've never been in a position where I've had to connect two removable
> storage devices at the same time, so haven't really had the need for
> it... plus I'm lazy and stuck in an old routine. ;)
I have a USB HDD which I use for backup, and the backup script
(rsnapshot) uses paths listed in its config files, so I need to be sure
that the drive is always in the same place, since I also have flash
drives which I use for sneakernet purposes. I haven't yet had a
problem, but I like knowing that I'm doing things 'right' ...
> Glad your issue is resolved.
Thanks.
> Graham
Celejar
--
mailmin.sourceforge.net - remote access via secure (OpenPGP) email
ssuds.sourceforge.net - A Simple Sudoku Solver and Generator
Date: Tue, 28 Aug 2007 14:14:13 -0700
From: David Brodbeck <brodbd@u.washington.edu>
To: List Debian User <debian-user@lists.debian.org>
Subject: Re: Shut down or leave on?
Message-Id: <97F79625-D0E8-4387-9963-B6E00B51B708@u.washington.edu>
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Content-Transfer-Encoding: 7bit
On Aug 28, 2007, at 1:49 PM, Martin McCormick wrote:
> I think some drives exercise the head rack during
> lulls of activity to keep it from stiffening up.
Some older drives also periodically move the head around to do
thermal recalibration. As the drive warms up the platters expand and
the head positioning logic has to compensate. Modern drives do this
automatically by using embedded servo tracks, but older ones had to
recalibrate every few minutes. It was a big headache for some A/V
applications, because it interrupted the data stream.
Date: Tue, 28 Aug 2007 17:19:40 -0400
From: Celejar <celejar@gmail.com>
To: binary@freedom.prodigynetwork.co.uk
Cc: debian-user <debian-user@lists.debian.org>
Subject: Re: [Fwd: Re: i686 Port]
Message-Id: <20070828171940.093e191a.celejar@gmail.com>
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
On Tue, 28 Aug 2007 21:53:22 +0100 (BST)
"Richard Thompson" <binary@freedom.prodigynetwork.co.uk> wrote:
[snipped discussion about the benefit of 686 optimization of typical
applications]
> Userspace services daemons etc, like any program will
perform better on an
> i686 processor if they are i686 optimised :-)
But again, most of the low level code the daemons will be running will
be either in the kernel or libc, IIUC.
Celejar
--
mailmin.sourceforge.net - remote access via secure (OpenPGP) email
ssuds.sourceforge.net - A Simple Sudoku Solver and Generator
Date: Tue, 28 Aug 2007 17:22:43 -0400
From: icelinux@icelinux.net
To: debian-user@lists.debian.org
Subject: Re: Shut down or leave on?
Message-ID: <20070828172243.fk5t04h9cgcs0c88@icelinux.net>
Content-Type: text/plain;
charset=ISO-8859-1;
DelSp="Yes";
format="flowed"
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
> I've always gone for leaving my machines on. I feel there is less
> wear and tear on components by leaving the machine on.
>
> Specifically, as I understand it, thermal shock to minuscule electronic
> components during power-on. In the past, I've lost a number of
> motherboards and processors due (presumably) to this effect. Since
> keeping my machines on 24/7 (for several years now), I have not had any
> such problems.
I have been turning mine off at night for years and never had a =20
problem. Years ago it would cause a problem with the hard drives but =20
that has been corrected. I do not even bother powering then down all =20
of the time and I have never not been able to boot Linux.
It does save electricity and if you are concerned about system =20
maintenannce then all you need to do is ensure that anacron is =20
installed and running. anacron will run the maintenance task which =20
have been missed after bootup. Unless you have a very old machine you =20
will probably not even notice.
"Everything should be made as simple as possible, but not simpler."
Albert Einstein
Date: Tue, 28 Aug 2007 23:50:14 +0200
From: Nigel Henry <cave.dnb@tiscali.fr>
To: debian-user@lists.debian.org
Subject: Re: Strange 224.0.0.251 address being accessed on bootup
Message-Id: <200708282350.14880.cave.dnb@tiscali.fr>
Content-Disposition: inline
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
On Tuesday 28 August 2007 03:53, Douglas A. Tutty wrote:
> On Mon, Aug 27, 2007 at 04:28:48PM +0200, Nigel Henry wrote:
> > On Monday 27 August 2007 03:52, Douglas A. Tutty wrote:
> > > Since this is all happening in /etc/rcS.d, I'd suggest booting with
> > > init=/bin/sh and running the /etc/rcS.d scripts manually one at a time
> > > to try to track it down. If you can get a shell while these errors are
> > > happening, perhaps you can see what processes are running.
> >
> > I havn't tried that before. Is that going to be similar to the
> > interactive boot up that you can do on Fedora?
>
> I've never used Fedora. There's nothing interactive about it. When you
> init=/bin/sh, you get sh running instead of init. The only drive
> mounted is the / and its ro. So you cd to /etc/rcS.d, do an ls and
> write down all the file names so you can tick them off as you run them.
>
> #less README
>
> read it..
>
> Then, one at a time, type e.g.:
> #./S01glibc.sh start
> #./S02hostname.sh start
>
> You're sort-of single-stepping the init process to track down a problem.
> Once you have, try to fix it and then shutdown. Since init normally
> does this, I wouldn't want to try to bring the system all the way up in
> this manner.
>
> Doug.
Thanks for that Doug. I tried it out on my Etch install.
I've still got this avahi-daemon problem on the Etch install. it's a bit
puzzling. I booted Etch up, opened synaptic to verify the zeroconf package
was no longer installed, and that is so. Then opened sysv-rc-conf in a
terminal, and see that I'd already disabled the avahi-daemon in all
runlevels. tail -f /var/log/messages though is still showing IP 192.168.0.7
pointing to IP 224.0.0.251.
I then do an ifdown eth0, and an ifup eth0, and the messages are still there.
next I do an /etc/init.d.avahi-daemon stop, and it confirms a stop.
Do an ifdown eth0, and an ifup eth0 again, and no more messages apart from the
one line that confirms that eth0 is up.
It would appear that even though the daemon is disabled on all runlevels,
something somewhere is starting it before I login.
Interestingly I opened synaptic to see if I could remove the avahi-daemon, and
got a few dependencies that would also be removed, as below.
kde
kdenetwork
kdnssd
libnss-mdns
Now I don't want KDE to be removed, as that's my desktop.
Out of interest I shutdown Etch, bootup Lenny, and here, synaptic only want s
to remove libnss-mdns as a dependency.
It looks like KDE has something to do with this problem.
How do I find out what is responsible for launching the avahi-daemon
shellscript?
This is the last bit of dmesg on Etch, where for some reason I can't disable
the avahi daemon, apart from running /etc/init.d/avahi-daemon stop , when I'm
booted up.
ip_tables: (C) 2000-2006 Netfilter Core Team
Netfilter messages via NETLINK v0.30.
ip_conntrack version 2.4 (8127 buckets, 65016 max) - 224 bytes per conntrack
eth0: link up, 100Mbps, full-duplex, lpa 0x45E1
NET: Registered protocol family 10
lo: Disabled Privacy Extensions
IPv6 over IPv4 tunneling driver
lp0: using parport0 (interrupt-driven).
ppdev: user-space parallel port driver
eth0: no IPv6 routers present
DROPPED IN= OUT=eth0 SRC=192.168.0.7 DST=224.0.0.22 LEN=40 TOS=0x00 PREC=0xC0
TTL=1 ID=0 DF OPT (94040000) PROTO=2
DROPPED IN= OUT=eth0 SRC=192.168.0.7 DST=224.0.0.251 LEN=141 TOS=0x00
PREC=0x00 TTL=255 ID=0 DF PROTO=UDP SPT=5353 DPT=5353 LEN=121
DROPPED IN= OUT=eth0 SRC=192.168.0.7 DST=224.0.0.251 LEN=141 TOS=0x00
PREC=0x00 TTL=255 ID=0 DF PROTO=UDP SPT=5353 DPT=5353 LEN=121
DROPPED IN= OUT=eth0 SRC=192.168.0.7 DST=224.0.0.251 LEN=141 TOS=0x00
PREC=0x00 TTL=255 ID=0 DF PROTO=UDP SPT=5353 DPT=5353 LEN=121
DROPPED IN= OUT=eth0 SRC=192.168.0.7 DST=224.0.0.251 LEN=129 TOS=0x00
PREC=0x00 TTL=255 ID=0 DF PROTO=UDP SPT=5353 DPT=5353 LEN=109
DROPPED IN= OUT=eth0 SRC=192.168.0.7 DST=224.0.0.251 LEN=175 TOS=0x00
PREC=0x00 TTL=255 ID=0 DF PROTO=UDP SPT=5353 DPT=5353 LEN=155
DROPPED IN= OUT=eth0 SRC=192.168.0.7 DST=224.0.0.251 LEN=175 TOS=0x00
PREC=0x00 TTL=255 ID=0 DF PROTO=UDP SPT=5353 DPT=5353 LEN=155
DROPPED IN= OUT=eth0 SRC=192.168.0.7 DST=224.0.0.251 LEN=175 TOS=0x00
PREC=0x00 TTL=255 ID=0 DF PROTO=UDP SPT=5353 DPT=5353 LEN=155
DROPPED IN= OUT=eth0 SRC=192.168.0.7 DST=224.0.0.251 LEN=236 TOS=0x00
PREC=0x00 TTL=255 ID=0 DF PROTO=UDP SPT=5353 DPT=5353 LEN=216
DROPPED IN= OUT=eth0 SRC=192.168.0.7 DST=224.0.0.251 LEN=113 TOS=0x00
PREC=0x00 TTL=255 ID=0 DF PROTO=UDP SPT=5353 DPT=5353 LEN=93
DROPPED IN= OUT=eth0 SRC=192.168.0.7 DST=224.0.0.251 LEN=236 TOS=0x00
PREC=0x00 TTL=255 ID=0 DF PROTO=UDP SPT=5353 DPT=5353 LEN=216
DROPPED IN= OUT=eth0 SRC=192.168.0.7 DST=224.0.0.251 LEN=129 TOS=0x00
PREC=0x00 TTL=255 ID=0 DF PROTO=UDP SPT=5353 DPT=5353 LEN=109
DROPPED IN= OUT=eth0 SRC=192.168.0.7 DST=224.0.0.251 LEN=236 TOS=0x00
PREC=0x00 TTL=255 ID=0 DF PROTO=UDP SPT=5353 DPT=5353 LEN=216
DROPPED IN= OUT=eth0 SRC=192.168.0.7 DST=224.0.0.22 LEN=40 TOS=0x00 PREC=0xC0
TTL=1 ID=0 DF OPT (94040000) PROTO=2
NET: Registered protocol family 4
NET: Registered protocol family 3
NET: Registered protocol family 5
DROPPED IN= OUT=eth0 SRC=192.168.0.7 DST=224.0.0.251 LEN=72 TOS=0x00 PREC=0x00
TTL=255 ID=0 DF PROTO=UDP SPT=5353 DPT=5353 LEN=52
DROPPED IN= OUT=eth0 SRC=192.168.0.7 DST=224.0.0.251 LEN=72 TOS=0x00 PREC=0x00
TTL=255 ID=0 DF PROTO=UDP SPT=5353 DPT=5353 LEN=52
DROPPED IN= OUT=eth0 SRC=192.168.0.7 DST=224.0.0.251 LEN=72 TOS=0x00 PREC=0x00
TTL=255 ID=0 DF PROTO=UDP SPT=5353 DPT=5353 LEN=52
d
Any comments, suggestions, and including "go and get a life", welcome.
This is no big deal, but would be nice to resolve this problem.
Nigel.
Date: Tue, 28 Aug 2007 23:55:52 +0200 (CEST)
From: "Jose Sancho Alonso" <j.sancho@calltalk.es>
To: debian-user@lists.debian.org
Subject: Belkin F5d7051
Message-ID: <64689.195.8.80.1.1188338152.squirrel@webmail.calltalk.es>
Content-Type: text/plain;charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable
Hi Debian users. I've been reading threads here and there about this
topic, but I still haven't found a suitable answer for me to make my WiFi
Adapter Belkin F5D7051 work in Debian 4.0 rev1
I've read about that feature in Edgy that powers down the usb ports and
the possible workarounds to disable it, but none of the solutions are goo=
d
for my system. They're all different and none of them produces any
positive effect. So I guess my adapter remains without enough power to
work. I've already installed ndiswrapper and everything is ok. Driver is
installed and hardware present. Please, I'm starting to desperate.
Somebody help me in this. Does anybody know the right script and the righ=
t
rules file name to disable the usb power limit feature?? Thank you!
Date: Tue, 28 Aug 2007 14:58:00 -0700
From: Freddy Freeloader <fredddy@cableone.net>
To: Debian User <debian-user@lists.debian.org>
Subject: Re: replacement for formmail
Message-ID: <46D49A68.3010706@cableone.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Douglas A. Tutty wrote:
> On Tue, Aug 28, 2007 at 12:51:00PM -0700, Freddy Freeloader wrote:
>
>> Anyone have any good recommendations for replacing formmail?
>>
>> I just started working for someone who is using it and we are trying to
>> lock his sites down more than they have been in the past and are looking
>> for a replacement.
>>
>
> What is formmail?
>
> Doug.
>
>
>
A buggy, insecure perl script used for sending mail from a website.
It's been around for a long time and a lot of people use it, but we
would like to move away from it. You can still see one replacement for
it using apt-cache if your sources.list file is pointed to sarge. You
can find it by searching packages at debian.org and choosing "any" for
the release.
Date: Tue, 28 Aug 2007 23:53:30 +0200 (CEST)
From: pinniped <cirilo_bernardo@yahoo.com>
To: debian-user@lists.debian.org
Subject: Shut down or leave on?
Message-Id: <listhandler=2&site=www.debianhelp.org&nid=9888&pid=&cid=35088&uid=76&tid=79&ecce83513433b3c71997435c12797810@www.debianhelp.org>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: quoted-printable
**snip**
>I hoped to reduce the probability of it [tape player]
>failing at the same time as the internal HD by
>starting it less often
For HDs the R/W head always comes into contact with the disc once the rot=
ation drops enough. Crack open a dead HD and you'll see nice concentric =
rings which just don't exist on a new device. HD life depends an awful lo=
t on the bearing condition as well; I found older bearings (HDs 10 years =
ago) get a bit gummy and may stick on startup, especially in humid condit=
ions, in which case it was better to keep running. Environment is a huge =
factor - if you get a "condensible atmosphere" as you would frequently ge=
t in Hawaii, it's best to keep running because the elevated temperature d=
iscourages condensation.
For a tape device the usual problems are mechanical wear (which doesn't h=
appen if you're not running a tape), expired pinch rollers, spiders, geck=
os, ants, dust, and lint. The dust and lint is usually made worse by a fa=
n forcing dirty air from the room through the drive. The electronics them=
selves are not likely to fail unless you have a lightning strike. Some e=
lectronic components age poorly and there's no saving them regardless of =
whether you remove power or not.
I've found most HDs manufactured in the past 5 years are very tolerant of=
power cycling so I think the primary consideration for switching off you=
r equipment in this case would be environmental factors (does it get very=
humid where you are).
>But I notice that most backup utilities are designed to
>backup automatically at the same time every day or week.
>That seems to assume that the system is always running.
You can initiate a backup yourself; you don't have to have the system run=
ning all the time. Most backup software was originally intended for busin=
esses so it's convenient to do the backup when hardly anyone is using the=
machines; home computers simply aren't used (as much) in the same way.
Date: Wed, 29 Aug 2007 00:07:46 +0200 (CEST)
From: pinniped <cirilo_bernardo@yahoo.com>
To: debian-user@lists.debian.org
Subject: WYSIWYG editor
Message-Id: <listhandler=2&site=www.debianhelp.org&nid=9900&pid=&cid=35096&uid=76&tid=79&b1d362abfd15c82099c34c50ae7ee50d@www.debianhelp.org>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: quoted-printable
>What do you recommend as a good, practical WYSIWYG editor
>for creating simple web pages, with mostly text, some
>graphics and pdf, for debian Lenny please? Thanks.
This may be a bit [OT] since I don't have any WYSIWYG web page editor to =
recommend, but ...
Actually WYSIWYG is VERY BAD for web page creation. People can resize the=
ir windows etc - and then what? All your WYSIWYG has gone to waste. In a=
ddition your WYSIWYG is probably not even rendering the same as your favo=
rite browsers.
As annoying as it may be at the start, the best way is probably to edit w=
ith a text editor and have a browser (or several browsers) rendering the =
file. You will find that for the most part you don't waste time looking =
at the browser window - you just put in all the appropriate markup and in=
formation and then much later you look at the browser and go "I didn't me=
an for it to look quite like that" and make a few adjustments. Keep in m=
ind that unless you use "style sheets" (in which case you're trying to fo=
rce a certain look on your visitors), HTML was really only meant to provi=
de the content and it was really up to the end user to play around with t=
he browser to control the final look. Ultimately it is impossible to ensu=
re a document looks good in all circumstances but it takes some effort to=
make a good page look bad.
Date: Tue, 28 Aug 2007 23:58:14 +0200
From: "[L]ash" <lash@semailer.com>
To: debian-user@lists.debian.org
Subject: Re: Pcmcia express card
Message-ID: <20070828235814.75d9332f@localhost.localdomain>
Content-Type: multipart/signed; boundary=Sig_x.SShhqApfCDlfkNkpHlNgK;
protocol="application/pgp-signature"; micalg=PGP-SHA1
--Sig_x.SShhqApfCDlfkNkpHlNgK
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: quoted-printable
Il giorno Sun, 26 Aug 2007 09:58:15 -0400
Wayne Topa <linuxone@intergate.com> ha scritto:
> Good luck
>=20
> Wayne
>=20
thanks, i need it :)
--=20
Andrea Corradi | Debian User | www.debian.org
Fingerprint: A41E F6B0 DBDB F04C 4940 E411 30F3 CD62 57B1 8458
gpg --keyserver keyserver.linux.it --recv-key 57B18458
Please avoid sending me Word or PowerPoint attachments.
http://www.gnu.org/philosophy/no-word-attachments.html
--Sig_x.SShhqApfCDlfkNkpHlNgK
Content-Type: application/pgp-signature; name=signature.asc
Content-Disposition: attachment; filename=signature.asc
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
iD8DBQFG1Jp4MPPNYlexhFgRAisAAJ4zS0ZqCPAxzLPV7e2dF76q2sp27QCePpoE
aDM4/ywFxGrx7wKume7E3oE=
=bGMJ
-----END PGP SIGNATURE-----
--Sig_x.SShhqApfCDlfkNkpHlNgK--
Date: Tue, 28 Aug 2007 17:36:36 -0500
From: "Nelson Castillo" <nelsoneci@gmail.com>
To: "Nigel Henry" <cave.dnb@tiscali.fr>
Cc: debian-user@lists.debian.org
Subject: Re: Strange 224.0.0.251 address being accessed on bootup
Message-ID: <2accc2ff0708281536p28b501b8ya41be428bf0c4398@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
On 8/28/07, Nigel Henry <cave.dnb@tiscali.fr> wrote:
(cut)
> TTL=255 ID=0 DF PROTO=UDP SPT=5353 DPT=5353 LEN=52
> DROPPED IN= OUT=eth0 SRC=192.168.0.7 DST=224.0.0.251 LEN=72 TOS=0x00 PREC=0x00
> TTL=255 ID=0 DF PROTO=UDP SPT=5353 DPT=5353 LEN=52
> d
>
> Any comments, suggestions, and including "go and get a life", welcome.
Well, it seems like a multicast address. I've used that range to do
multicast in a LAN (with videolan).
Regards,
N.-
--
http://arhuaco.org
Date: Wed, 29 Aug 2007 00:23:15 +0200 (CEST)
From: pinniped <cirilo_bernardo@yahoo.com>
To: debian-user@lists.debian.org
Subject: [Fwd: i686 Port]
Message-Id: <listhandler=2&site=www.debianhelp.org&nid=9902&pid=35092&cid=35097&uid=76&tid=79&6df58e9328b9ba0fa5d94a6bfabc59c0@www.debianhelp.org>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: quoted-printable
> Userspace services daemons etc, like any program will
perform better on an
> i686 processor if they are i686 optimised :-)
It would certainly be interesting to see comparisons of this. The primar=
y advantage is that more registers are available so there are less games =
played with swapping values in memory for those routines which contain ma=
ny variables. Personally I have written very few routines which exhaust e=
ven the small(ish) number of registers on the i386.
If you believe you have a significant gain in compiling for the i686, you=
can always use the Debian tools to build the same packages from source.
End of debian-user-digest Digest V2007 Issue #2268
**************************************************
Received on Tue Aug 28 19:03:24 2007