Pantek Library
Hosting Provided By
CybrHost
High Speed Hosting
Mailing Lists: lists.debian.org > debian-user-digest > 07 > 120973.html (Request Expert lists.debian.org Support)

debian-user-digest Digest V2007 #2993

From: <debian-user-digest-request(at)lists.debian.org>
Date: Wed Dec 12 2007 - 00:09:17 EST


Content-Type: text/plain

debian-user-digest Digest Volume 2007 : Issue 2993

Today's Topics: 

  Re: vim syntax line                   [ Jerome BENOIT  ]
  Re: How to start KDE from a console   [ "John Fleming"  ]
  Re: How to start KDE from a console   [ Michael Pobega  ]
  Re: How to start KDE from a console   [ Ron Johnson  ]
  Re: How to start KDE from a console   [ Ron Johnson  ]
  Re: reporting aptitude errors         [ Daniel Burrows  ]
  Re: no email                          [ Daniel Burrows  ]
  Re: How to start KDE from a console [ Kent West <westk@acu.edu> ]

Date: Wed, 12 Dec 2007 07:00:51 +0800
From: Jerome BENOIT <jgmbenoit@mailsnare.net> To: debian-user@lists.debian.org
Subject: Re: vim syntax line 

Message-ID: <475F16A3.5020603@mailsnare.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

You get the point.

Thanks,
Jerome

Magnus Therning wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
 > Hash: SHA1
>
> On Dec 10, 2007 6:16 PM, Jerome BENOIT <jgmbenoit@mailsnare.net> wrote:

>> Hello List,
>>
>> I have just noticed on my Lenny box that the vim syntax line command in files
>> does not work anymore whereas the syntax feature is on.
>> May I set something in vimrc to make it works ? or is it a bug ?

>
> Are you talking about `modeline'?
>
> The relevant variables are `modeline' and `modelines'.
>
> /M
> -----BEGIN PGP SIGNATURE-----
 > Version: GnuPG v1.4.6 (GNU/Linux)
>
> iD8DBQFHXmF6iMWTaatN+6QRAq4PAKCU4nFeDaZmZ+QmXIf7wsNaYm+HcwCfRb6m
> LKmDnl1aK4DS1dEhsFxUgII=
> =hE3K
> -----END PGP SIGNATURE-----
 > 
-- 
Jerome BENOIT
jgmbenoit_at_mailsnare_dot_net

Do you need more help?X

Date: Tue, 11 Dec 2007 19:02:56 -0600 From: "Bob Goldberg" <bobg.hahc@gmail.com> To: debian-user@lists.debian.org Subject: back to basics: what's wrong with this exim condition statement? Message-ID: <4e312cc10712111702l214d9463rf3277995b5fd8974@mail.gmail.com> Content-Type: multipart/alternative; boundary="----=_Part_9226_17321460.1197421376586" ------=_Part_9226_17321460.1197421376586 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline running debian etch (which is exim4); I'm having problems with an ACL; so i've gone to absolute basics, and I still have a problem :) So here's what I have in my ACL: accept message = condition is false condition = ${if eq{23}{123}{1}{0}} next, I telnet in, and transact an email up to the rcpt to: command. IF my condition uses 123 & 123 (IOW: it's true), my rcpt to: command is accepted - just what I expected. however, with the above condition, I would expect to get the message "condition is false", and instead I get "unexpected failure". I tried appending an "endpass", but that did nothing. what's wrong with my accept / condition statements? TIA - Bob ------=_Part_9226_17321460.1197421376586 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline running debian etch (which is exim4);<br><br>I&#39;m having problems with an ACL; so i&#39;ve gone to absolute basics, and I still have a problem :)<br><br>So here&#39;s what I have in my ACL:<br><br>&nbsp; accept message = condition is false <br>&nbsp;&nbsp;&nbsp; condition = ${if eq{23}{123}{1}{0}} <br><br><br>next, I telnet in, and transact an email up to the rcpt to: command.<br>IF my condition uses 123 &amp; 123 (IOW: it&#39;s true), my rcpt to: command is accepted - just what I expected. <br>however, with the above condition, I would expect to get the message &quot;condition is false&quot;, and instead I get &quot;unexpected failure&quot;.<br><br>I tried appending an &quot;endpass&quot;, but that did nothing. <br><br>what&#39;s wrong with my accept / condition statements?<br><br>TIA - Bob<br><br> ------=_Part_9226_17321460.1197421376586--

Date: Tue, 11 Dec 2007 19:36:02 -0600 From: Ron Johnson <ron.l.johnson@cox.net> To: ML Debian-User <debian-user@lists.debian.org> Subject: How to start KDE from a console prompt? Message-ID: <475F3B02.9000507@cox.net> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, To enter GNOME, I type "startx". I tried entering KDE by typing "startkde" which I what I remember doing a couple of years ago when I last tried it. But it can't start X. Anyone have any clues? $ startkde xsetroot: unable to open display '' xset: unable to open display "" xsetroot: unable to open display '' startkde: Starting up... startkde: Running kpersonalizer... kpersonalizer: cannot connect to X server kwin: cannot connect to X server kpersonalizer: cannot connect to X server kpersonalizer: cannot connect to X server kpersonalizer: cannot connect to X server kpersonalizer: cannot connect to X server kpersonalizer: cannot connect to X server kpersonalizer: cannot connect to X server kpersonalizer: cannot connect to X server kpersonalizer: cannot connect to X server [etc etc ad nauseum] - -- Ron Johnson, Jr. Jefferson LA USA "Your mistletoe is no match for my TOW missile." Santa-bot -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFHXzsCS9HxQb37XmcRAuMMAKClyQPT4JI+tacbXC017N6riYNPNACeJANr SkyAvIGWGSGN2JYEswwei3A= =AwsJ -----END PGP SIGNATURE-----

Date: Tue, 11 Dec 2007 20:52:01 -0500 From: "John Fleming" <john@wa9als.com> To: "Ron Johnson" <ron.l.johnson@cox.net>, "ML Debian-User" <debian-user@lists.debian.org> Subject: Re: How to start KDE from a console prompt? Message-ID: <001401c83c61$99631180$42d8a8c0@wa9als> Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=original Content-Transfer-Encoding: 7bit ----- Original Message ----- From: "Ron Johnson" <ron.l.johnson@cox.net> To: "ML Debian-User" <debian-user@lists.debian.org> Sent: Tuesday, December 11, 2007 8:36 PM Subject: How to start KDE from a console prompt?
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Hi,
>
> To enter GNOME, I type "startx". I tried entering KDE by typing
> "startkde" which I what I remember doing a couple of years ago when
> I last tried it. But it can't start X.
>
> Anyone have any clues?
>
> $ startkde
> xsetroot: unable to open display ''
> xset: unable to open display ""
> xsetroot: unable to open display ''
> startkde: Starting up...
> startkde: Running kpersonalizer...
> kpersonalizer: cannot connect to X server
> kwin: cannot connect to X server
> kpersonalizer: cannot connect to X server
> kpersonalizer: cannot connect to X server
> kpersonalizer: cannot connect to X server
> kpersonalizer: cannot connect to X server
> kpersonalizer: cannot connect to X server
> kpersonalizer: cannot connect to X server
> kpersonalizer: cannot connect to X server
> kpersonalizer: cannot connect to X server
> [etc etc ad nauseum]
>
> - --
> Ron Johnson, Jr.
> Jefferson LA USA
>
> "Your mistletoe is no match for my TOW missile." Santa-bot
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.6 (GNU/Linux)
>
> iD8DBQFHXzsCS9HxQb37XmcRAuMMAKClyQPT4JI+tacbXC017N6riYNPNACeJANr
> SkyAvIGWGSGN2JYEswwei3A=
> =AwsJ
> -----END PGP SIGNATURE-----
> >
> --
> To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact
> listmaster@lists.debian.org
> >
> --
> No virus found in this incoming message.
> Checked by AVG Free Edition.
> Version: 7.5.503 / Virus Database: 269.17.0/1180 - Release Date:
> 12/10/2007 2:51 PM
> > Try /etc/init.d/kdm start (assuming you have kdm) and let us know. startkde gives me similar messages, but starting kdm works fine. - John

Date: Tue, 11 Dec 2007 21:20:38 -0500 From: Michael Pobega <pobega@gmail.com> To: debian-user@lists.debian.org Subject: Re: How to start KDE from a console prompt? Message-ID: <20071212022038.GC4134@digital-haze.net> Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="oJ71EGRlYNjSvfq7" Content-Disposition: inline --oJ71EGRlYNjSvfq7 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Dec 11, 2007 at 07:36:02PM -0600, Ron Johnson wrote:
> Hi,
>=20
> To enter GNOME, I type "startx". I tried entering KDE by typing
> "startkde" which I what I remember doing a couple of years ago when
> I last tried it. But it can't start X.
>=20
> Anyone have any clues?
>=20
> $ startkde
> [snip x errors]
>=20 startx /usr/bin/startkde --=20 If programmers deserve to be rewarded for creating innovative programs, by the same token they deserve to be punished if they restrict the use of these programs.=20 - Richard Stallman --oJ71EGRlYNjSvfq7 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Digital signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFHX0V2g6qL2BGnx4QRAmNFAJ4uTk7+qV4qc2i8rMbn0zn23BuRmQCfc3Le cYjCm1b5W/WhzthaDO9H1CE= =S3jy -----END PGP SIGNATURE----- --oJ71EGRlYNjSvfq7--

Date: Tue, 11 Dec 2007 20:21:32 -0600 From: Ron Johnson <ron.l.johnson@cox.net> To: ML Debian-User <debian-user@lists.debian.org> Subject: Re: How to start KDE from a console prompt? Message-ID: <475F45AC.5060505@cox.net> Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 7bit -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 12/11/07 19:52, John Fleming wrote: >> >> ----- Original Message ----- From: "Ron Johnson" <ron.l.johnson@cox.net> >> To: "ML Debian-User" <debian-user@lists.debian.org> >> Sent: Tuesday, December 11, 2007 8:36 PM >> Subject: How to start KDE from a console prompt? >> >> >> Hi, >> >> To enter GNOME, I type "startx". I tried entering KDE by typing >> "startkde" which I what I remember doing a couple of years ago when >> I last tried it. But it can't start X. >> >> Anyone have any clues? >> >> $ startkde >> xsetroot: unable to open display '' >> xset: unable to open display "" >> xsetroot: unable to open display '' >> startkde: Starting up... >> startkde: Running kpersonalizer... >> kpersonalizer: cannot connect to X server >> kwin: cannot connect to X server >> kpersonalizer: cannot connect to X server >> kpersonalizer: cannot connect to X server >> kpersonalizer: cannot connect to X server >> kpersonalizer: cannot connect to X server >> kpersonalizer: cannot connect to X server >> kpersonalizer: cannot connect to X server >> kpersonalizer: cannot connect to X server >> kpersonalizer: cannot connect to X server >> [etc etc ad nauseum] >> >
> Try /etc/init.d/kdm start (assuming you have kdm) and let us know.
> startkde gives me similar messages, but starting kdm works fine. - John
Thanks for the suggestion, but I strongly dislike DMs. - -- Ron Johnson, Jr. Jefferson LA USA "Your mistletoe is no match for my TOW missile." Santa-bot -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFHX0WsS9HxQb37XmcRAvnpAJ9YTg/I8bvto4anx004Vl3SlUTkyQCfWyf9 0kBZMQZjb9ChHi+uAVU2kOI= =zQNQ -----END PGP SIGNATURE-----

Date: Tue, 11 Dec 2007 20:29:02 -0600 From: Ron Johnson <ron.l.johnson@cox.net> To: debian-user@lists.debian.org Subject: Re: How to start KDE from a console prompt? Message-ID: <475F476E.9000403@cox.net> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 12/11/07 20:20, Michael Pobega wrote:
> On Tue, Dec 11, 2007 at 07:36:02PM -0600, Ron Johnson wrote:
>> Hi, >> >> To enter GNOME, I type "startx". I tried entering KDE by typing >> "startkde" which I what I remember doing a couple of years ago when >> I last tried it. But it can't start X. >> >> Anyone have any clues? >> >> $ startkde >> [snip x errors] >>
>
> startx /usr/bin/startkde
Remembering that, I tried "startx startkde", but that bombed. Now I know why... If in 30 minutes you see my User Agent be KMail, it worked. :) - -- Ron Johnson, Jr. Jefferson LA USA "Your mistletoe is no match for my TOW missile." Santa-bot -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFHX0duS9HxQb37XmcRAobdAJ9dCQGc/OrUZsmzy5E8gUOO0PjEYgCgkuI1 xkgYH6lW2WdUTfhV5mH1w2c= =NQ4j -----END PGP SIGNATURE-----

Date: Tue, 11 Dec 2007 06:49:57 -0800 From: Daniel Burrows <dburrows@debian.org> To: debian-user@lists.debian.org Subject: Re: reporting aptitude errors Message-id: <20071211144957.GB9621@alpaca> Content-type: text/plain; charset=us-ascii Content-disposition: inline On Tue, Dec 11, 2007 at 10:04:19AM +0100, roberto <roberto03@gmail.com> was heard to say:
> hello
> i am receiving a long list of errors from aptitude but i do not know
> how to copy and post them here ...
If you are running at the command-line, you can click and drag to select text, and then middle-click in your email program to copy it. If you are running in visual mode, you can shift-click and drag to select text, and then middle-click in your email program to copy it. It would also be helpful if you include a brief description of what you were trying to do when the error occurred. Daniel

Date: Tue, 11 Dec 2007 18:36:19 -0800 From: Andrew Sackville-West <andrew@farwestbilliards.com> To: debian-user@lists.debian.org Subject: Re: How to start KDE from a console prompt? Message-ID: <20071212023619.GK7681@localhost.localdomain> Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="6UEPj0d4ZbbWkD8I" Content-Disposition: inline --6UEPj0d4ZbbWkD8I Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Dec 11, 2007 at 07:36:02PM -0600, Ron Johnson wrote:
> Hi,
>=20
> To enter GNOME, I type "startx". I tried entering KDE by typing
> "startkde" which I what I remember doing a couple of years ago when
> I last tried it. But it can't start X.
startx uses ~/.xinitrc to start up the X session. In case it doesn't exist, then debian has some default stuff that starts whatever the default window manager is. Look at `update-alternatives --config x-window-manager` to set a different window manager as the default.=20 Or, write your own .xinitrc (this is what I do) to start up a session the way you want the simplest is to use a one line .xinitrc with exec /usr/bin/startkde startx will then fire up X, and hand over control to .xinitrc and then when .xinitrc exits (it's essentially a regular bash script) X will die. >=20
> Anyone have any clues?
>=20
> $ startkde
> xsetroot: unable to open display ''
> xset: unable to open display ""
> xsetroot: unable to open display ''
> startkde: Starting up...
> startkde: Running kpersonalizer...
> kpersonalizer: cannot connect to X server
> kwin: cannot connect to X server
> kpersonalizer: cannot connect to X server
> kpersonalizer: cannot connect to X server
> kpersonalizer: cannot connect to X server
> kpersonalizer: cannot connect to X server
> kpersonalizer: cannot connect to X server
> kpersonalizer: cannot connect to X server
> kpersonalizer: cannot connect to X server
> kpersonalizer: cannot connect to X server
> [etc etc ad nauseum]
startkde command starts a kde session, but it assumes an X session is already running hence the need for calling startx with your own =2Exinitrc, or changing the default window manager. Other solutions exist as well like 'startx /usr/bin/startkde' I think. A --6UEPj0d4ZbbWkD8I Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Digital signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFHX0kjaIeIEqwil4YRAmKPAJ0apzhQtaGA0zpSgC3hPyaGvfQqZgCgx+GA lKQVxKJdYZZHOSTUDcRGIK4= =3DF8 -----END PGP SIGNATURE----- --6UEPj0d4ZbbWkD8I--

Can we help you?X

Date: Tue, 11 Dec 2007 18:39:36 -0800 From: Andrew Sackville-West <andrew@farwestbilliards.com> To: debian-user@lists.debian.org Subject: Re: Anyone using Debian on notebook? Message-ID: <20071212023936.GL7681@localhost.localdomain> Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="PETIzWh8d1Msfd+P" Content-Disposition: inline --PETIzWh8d1Msfd+P Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable I"m running sid on my LinuxCertified lappy. It came with ubuntu installed, which I wiped and replaced with debian on top of enxrypted lvm. Works great. Everything works but suspend2ram. I could probably make it work, but it's not worth it. I just shut it down.=20 A --PETIzWh8d1Msfd+P Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Digital signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFHX0noaIeIEqwil4YRAug+AJ48Fb6wF/6dfngV2KDs0opbmIClNwCgp69b 3LaLVWcbkUnElfQXLjRlTjM= =iBnJ -----END PGP SIGNATURE----- --PETIzWh8d1Msfd+P--

Date: Tue, 11 Dec 2007 18:42:45 -0800 From: Andrew Sackville-West <andrew@farwestbilliards.com> To: debian-user@lists.debian.org Subject: Re: System Lockup Message-ID: <20071212024245.GM7681@localhost.localdomain> Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="w1d+AIiKduYp7JzL" Content-Disposition: inline --w1d+AIiKduYp7JzL Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Dec 11, 2007 at 06:50:26PM +0100, strawks wrote:
> > I just experienced my first ever system lockup. No mouse, no keyboard=
=20
> > with an Iceape screen open.
>=20
> > I had saved a posting regarding SYSRQ and I tried Alt-Sysrq k then=20
> > Alt-Sysrq i and the Alt-Sysrq b with no response.=20
>=20
> Did you really press those 3 keys at the same time? To see if it works
> switch to a console and try it there (Alt-Sysrq-s should print
> something).
should print something about syncing the disks. >=20
> > In desperation I crashed and rebooted the system. I am using=20
> > linux-image 2.6.21-2-686. When the system came up I entered grep SYSRQ=
=20
> > /boot/config-$(uname -r) and got the response CONFIG_MAGIC-SYSRQ=3Dy
> >=20
> >=20
> > So its there. Either I did something wrong or it doesn't work with the=
=20
> > problem I encountered.
>=20
> Correct me if I'm wrong, but I thought sysrq should work in any case but
> hardware problem as it's done directly in the IRQ handler.
>=20 I think it's a kernel thing, and while it works in many lockup conditions, obviously it doesn't work in all cases.=20 A =20 --w1d+AIiKduYp7JzL Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Digital signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFHX0qlaIeIEqwil4YRAnJjAJ9BMiImoOgWA+DFkkymy8OKCjNEPgCfT95E 54jaAApLGX4c5+9rYHvYC/0= =C6do -----END PGP SIGNATURE----- --w1d+AIiKduYp7JzL--

Date: Tue, 11 Dec 2007 18:45:29 -0800 From: Andrew Sackville-West <andrew@farwestbilliards.com> To: debian-user@lists.debian.org Subject: Re: Wating for root file system. Kernel bug? Message-ID: <20071212024529.GN7681@localhost.localdomain> Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="jrLL7VzBua603j+s" Content-Disposition: inline --jrLL7VzBua603j+s Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Dec 11, 2007 at 07:13:49PM +0200, wanderlust wrote:
> Hello.
>=20
> I'm trying to install Debian/etch on Acer Aspire 5520G, but the problem
> is, that kernel 2.6.18 doesn't support Marvell netcard 436b. I found it
> is supportable in 2.6.23.9, so I decided to compile it. I used default
> configuration, taken from /proc/config.gz and after compiling and
> installing (using modules on initrd) I had to reboot to new kernel.
>=20
> But I got a failure. Everything seems ok during loading from initrd, but
> kernel couldn't find root filesystem (module is available). I looked
> through /dev and found none sd devices (there is SATA disk on the
> laptop). Any ideas how to solve a problem? It works fine with 2.6.18
> kernel.
you're missing a module probably. rebuild the initrd with 'modules=3Dmost' in the confuration. A --jrLL7VzBua603j+s Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Digital signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFHX0tJaIeIEqwil4YRArL+AKCfuIkjp/pgq4Q8UAT5X1h3N4ZaSACgo52/ sX/FgPDVNfhx/y4K308NFQE= =v4lq -----END PGP SIGNATURE----- --jrLL7VzBua603j+s--

Date: Tue, 11 Dec 2007 18:48:11 -0800 From: Andrew Sackville-West <andrew@farwestbilliards.com> To: debian-user@lists.debian.org Subject: Re: backup script partly fails when in cron.weekly Message-ID: <20071212024811.GO7681@localhost.localdomain> Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="PLomxqHhGwMWzngE" Content-Disposition: inline --PLomxqHhGwMWzngE Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Dec 11, 2007 at 08:24:07AM -0500, Haines Brown wrote:
> Benjamin Schmidt <b.schmidt@t-p.com> writes:
>=20
> > But maybe you should not use this (in my opinion) unusual command "find
> > / -print ...". Instead use tar, like:
> >=20
> > tar -zcvf /media/mirror/`date +%F`.tar.gz -C / --exclude=3D/media/*
> > --exclude=3D/proc/* --exclude=3D/sys/* --exclude=3D/mnt/*
>=20
> Benjamin, thanks for the suggestion, but I had a problem with the
> script:
>=20
> Cowardly refusing to create an empty archive
>=20
> I don't understand this error.=20
It means that when tar followed all the instructions you gave it, there was nothing left to put in the archive, so it sanely refuses to create the archive. I looks like you're missing the final path on that line. man tar A --PLomxqHhGwMWzngE Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Digital signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFHX0vraIeIEqwil4YRAvTlAKCGbjvzVIYexq70RIMtDn/45lrN0QCg2vz3 WktIavFFx2rYljpF/B/Ctjk= =ctLx -----END PGP SIGNATURE----- --PLomxqHhGwMWzngE--

Date: Tue, 11 Dec 2007 22:27:40 -0500 From: Kamaraju S Kusumanchi <kamaraju@bluebottle.com> To: debian-user@lists.debian.org Subject: Re: How to start KDE from a console prompt? Message-ID: <fjnjqr$h91$1@ger.gmane.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7Bit Ron Johnson wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Hi,
>
> To enter GNOME, I type "startx". I tried entering KDE by typing
> "startkde" which I what I remember doing a couple of years ago when
> I last tried it. But it can't start X.
>
> Anyone have any clues?
>
> $ startkde
> xsetroot: unable to open display ''
> xset: unable to open display ""
> xsetroot: unable to open display ''
Others have given you good suggestions. Another approach is to just do xinit and once X starts, there will be an xterm in which you can type startkde. hth raju -- Kamaraju S Kusumanchi http://www.people.cornell.edu/pages/kk288/ http://malayamaarutham.blogspot.com/

Date: Tue, 11 Dec 2007 21:21:11 -0600 From: Ron Johnson <ron.l.johnson@cox.net> To: debian-user@lists.debian.org Subject: Re: How to start KDE from a console prompt? Message-Id: <200712112121.30960.ron.l.johnson@cox.net> Content-Type: multipart/signed; boundary="nextPart1383219.kfZm3WalNQ"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit --nextPart1383219.kfZm3WalNQ Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline On Tuesday 11 December 2007 08:29:02 pm Ron Johnson wrote:
> On 12/11/07 20:20, Michael Pobega wrote:
> > On Tue, Dec 11, 2007 at 07:36:02PM -0600, Ron Johnson wrote:
> >> Hi,
> >>
> >> To enter GNOME, I type "startx". I tried entering KDE by typing
> >> "startkde" which I what I remember doing a couple of years ago when
> >> I last tried it. But it can't start X.
> >>
> >> Anyone have any clues?
> >>
> >> $ startkde
> >> [snip x errors]
> >
> > startx /usr/bin/startkde
>
> Remembering that, I tried "startx startkde", but that bombed. Now I
> know why...
>
> If in 30 minutes you see my User Agent be KMail, it worked. :)
Well, it seems to have worked. Thanks. --nextPart1383219.kfZm3WalNQ Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQBHX1O6S9HxQb37XmcRAlcjAJ9OaIeOHOXMtdYHxRk2ZriTsCFlbQCg1/aU Ne9QOktUUgamDt5F1a6rrqQ= =SjrV -----END PGP SIGNATURE----- --nextPart1383219.kfZm3WalNQ--

Date: Tue, 11 Dec 2007 18:40:12 -0800 From: Daniel Burrows <dburrows@debian.org> To: Mark Grieveson <dg135@torfree.net> Cc: debian-user@lists.debian.org Subject: Re: no email Message-id: <20071212024012.GA16771@alpaca> Content-type: text/plain; charset=us-ascii Content-disposition: inline On Tue, Dec 11, 2007 at 01:04:21PM -0500, Mark Grieveson <dg135@torfree.net> was heard to say:
> On Tue, 11 Dec 2007 21:58:19 +0530
> Kumar Appaiah <akumar@iitm.ac.in> wrote:
>
> > On Tue, Dec 11, 2007 at 10:56:12AM -0500, Mark Grieveson wrote:
> > > Hello. I'm subscribed to the digest of this list, and used to
> > > regularly receive email. Suddenly, it stopped. I resubscribed, but
> > > still am receiving nothing. I now follow the list via the web.
> >
> > Have you eliminated common problems, like a spamfilter at your end?
> > Sometimes, people don't realise that all their mails are silently
> > eaten up by the spam filters.
> >
> > Kumar
>
> I use sylpheed-claws-gtk, with bogofilter. I check my spam file, and
> it's not going in there.
What's upstream from you? Could your ISP be "helpfully" dropping the mails? Daniel

Date: Tue, 11 Dec 2007 22:02:30 -0500 From: Roan Horning <roan@horning.us> To: debian-user@lists.debian.org Subject: Re: volume mgmt w/o gnome Message-ID: <475F4F46.9050005@horning.us> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Hi, ivman (http://ivman.sourceforge.net/) is for automounting: Ivman is a generic handler for HAL <http://freedesktop.org/wiki/Software_2fhal> events. Originally for automounting, it can now be used to run arbitrary commands when events or conditions occur or properties are modified on your hardware (e.g., run a command when you close your laptop's lid, run a command when a particular device is attached or a particular CD is inserted, etc) It's available in debian (using your favorite apt frontend). I'm using it with XFCE to replace the functionality of gnome-volume-manager. --Roan

Can't find what you're looking for?X

Date: Tue, 11 Dec 2007 22:31:40 -0600 From: Kent West <westk@acu.edu> To: debian-user@lists.debian.org Subject: Re: How to start KDE from a console prompt? Message-ID: <475F642C.8070603@acu.edu> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Andrew Sackville-West wrote:
> startx uses ~/.xinitrc to start up the X session. In case it doesn't
> exist, then debian has some default stuff that starts whatever the
> default window manager is. Look at `update-alternatives --config
> x-window-manager` to set a different window manager as the default.
>
> Or, write your own .xinitrc (this is what I do) to start up a session
> the way you want the simplest is to use a one line .xinitrc with
>
> exec /usr/bin/startkde
> >
>
I just put the bare "startkde" in my ~/.xinitrc. Of course, the method I use assumes I'm not doing other things in that file (which I'm not, other than switching between WMs via commented-out lines, as below). My ~.xinitrc file looks something like this: westk[@westk03]:/home/westk> cat .xinitrc #icewm #xterm #wmaker startkde #xfce #gnome-session -- Kent End of debian-user-digest Digest V2007 Issue #2993 ************************************************** Received on Wed Dec 12 00:09:37 2007

Do you need help?X

This archive was generated by hypermail 2.1.8 : Wed Mar 19 2008 - 02:57:51 EDT

Contact Us  Legal Notices  Order Services Online 
Pantek Home  Privacy Policy  IT news  Site Map  Pantek Library