Ron Johnson wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 12/31/07 15:48, charlie derr wrote:
[snip]
Of course, I would do all this from the (real) console, not a GNOME
terminal window.
you're just chicken :-]
Real Men use the console. I'm not sure what Real Women use.
Yeah, I
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 01/02/08 11:23, charlie derr wrote:
Ron Johnson wrote:
On 12/31/07 15:48, charlie derr wrote:
[snip]
Of course, I would do all this from the (real) console, not a GNOME
terminal window.
you're just chicken :-]
Real Men use the console.
Ron Johnson wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 12/31/07 15:48, charlie derr wrote:
[snip]
Of course, I would do all this from the (real) console, not a GNOME
terminal window.
you're just chicken :-]
Real Men use the console. I'm not sure what Real Women use.
(i'm
http://www.assembla.com/wiki/show/door/SidGnomeRefusingToDie
It seemed like there was too much output there to want to burden the list with it all (but I thought someone clueful might still
possibly catch something I haven't)
my working assumption at this point is that last night either
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 12/31/07 09:15, charlie derr wrote:
http://www.assembla.com/wiki/show/door/SidGnomeRefusingToDie
It seemed like there was too much output there to want to burden the
list with it all (but I thought someone clueful might still possibly
catch
Charlie,
In this kind of situation, I would # apt-get --purge remove the
problematic package(s), then # apt-get update and try again.
as Daniel and Florian have pointed out elsewhere in this thread, my problem is with libxml2 being completely borken at the moment
(I think) and aptitude is
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 12/31/07 15:48, charlie derr wrote:
[snip]
Of course, I would do all this from the (real) console, not a GNOME
terminal window.
you're just chicken :-]
Real Men use the console. I'm not sure what Real Women use.
(i'm still in the same
Hello Roberto.
Roberto C. Sanchez, 26.02.2007 04:20:
On Sun, Feb 25, 2007 at 07:46:40PM -0500, Steve Kleene wrote:
Here are the only errors I got with the deb files I made:
dpkg -i alsa-lib_1.0.14rc2-1_i386.deb -
dpkg: error processing alsa-lib_1.0.14rc2-1_i386.deb (--install): trying to
References: [EMAIL PROTECTED]
On Sun Feb 25 22:15:59 2007, Roberto C. Sanchez wrote:
I forget what branch you are running, but if you are on Etch and need
something from Sid or experimental, then you can follow my HOWTO:
http://people.connexer.com/~roberto/howtos/debcustomize
Thanks,
In another thread (sound problems on debian), I explained that my new etch
installation didn't drive my Intel onboard sound card. It was suggested that
I try upgrading from source from alsa-1.0.13 to alsa-1.0.14. I've done this
and have sound now but wonder what kind of pain will be ahead with
On Sun, Feb 25, 2007 at 04:14:48PM -0500, Steve Kleene wrote:
What I did was to put in alsa-base 1.0.14-rc1 from Debian experimental and
alsa-lib and alsa-driver 1.0.14rc2 from source. I made deb files of these
two but couldn't install them that way because of conflicts. I tried
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 02/25/07 15:14, Steve Kleene wrote:
In another thread (sound problems on debian), I explained that my new etch
installation didn't drive my Intel onboard sound card. It was suggested that
I try upgrading from source from alsa-1.0.13 to
References: [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED]
On Sun Feb 25 16:15:46 2007, I wrote:
What I did was to put in alsa-base 1.0.14-rc1 from Debian experimental and
alsa-lib and alsa-driver 1.0.14rc2 from source. I made deb files of these
two but couldn't install them that way
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 02/25/07 18:46, Steve Kleene wrote:
References: [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED]
On Sun Feb 25 16:15:46 2007, I wrote:
What I did was to put in alsa-base 1.0.14-rc1 from Debian experimental and
alsa-lib and alsa-driver
BTW, why wouldn't alsa-source 1.0.14~rc1-1 from experimental solve
your problem?
Maybe it would. I hadn't noticed that it was available. If all I needed was
a driver, that would have been the way to go. I installed alsa-lib first but
am not sure if that was necessary.
--
To UNSUBSCRIBE,
On Sun, Feb 25, 2007 at 07:46:40PM -0500, Steve Kleene wrote:
Here are the only errors I got with the deb files I made:
dpkg -i alsa-lib_1.0.14rc2-1_i386.deb -
dpkg: error processing alsa-lib_1.0.14rc2-1_i386.deb (--install): trying to
overwrite `/usr/bin/nm', which is also in
References: [EMAIL PROTECTED]
On Sun Feb 25 21:46:34 2007, Roberto C. Sanchez wrote:
On Sun, Feb 25, 2007 at 07:46:40PM -0500, Steve Kleene wrote:
Here are the only errors I got with the deb files I made:
dpkg -i alsa-lib_1.0.14rc2-1_i386.deb -
dpkg: error processing
On Sun, Feb 25, 2007 at 10:05:54PM -0500, Steve Kleene wrote:
References: [EMAIL PROTECTED]
On Sun Feb 25 21:46:34 2007, Roberto C. Sanchez wrote:
On Sun, Feb 25, 2007 at 07:46:40PM -0500, Steve Kleene wrote:
Here are the only errors I got with the deb files I made:
dpkg -i
In article [EMAIL PROTECTED],
Bryan Donlan [EMAIL PROTECTED] wrote:
On 8/30/05, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
Can anyone suggest a tutorial on writing what I think are called init
scripts?
Take a look at the files in /etc/init.d, just use one of them as a
template, and symlink
On 8/29/05, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
Can anyone recommend a good disk recovery company?
Thanks in advance,
Dave Williams
You don't need one for this. Which bootloader are you using, LILO or
GRUB? You can pass init=/bin/sh using it.
For grub, select the boot menu option,
This did it!!! I had misunderstood the last lines of this post. (I stupidly
missed the in either case.
Im back in business.
Thank you Bryan! Thank you all!
A VERY grateful Dave Williams.
Bryan Donlan [EMAIL PROTECTED] wrote:
On 8/29/05, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
On 8/30/05, David W. Williams [EMAIL PROTECTED] wrote:
I should have mentioned, I'm the:
Re: I messed up bootmisc.sh - now can't log in! guy
from debian-user
I just tried this with vi, and when I went to save, got this message:
E45: 'readonly' option is set (add ! to override
Bryan Donlan [EMAIL PROTECTED] wrote:
On 8/30/05, David W. Williams [EMAIL PROTECTED] wrote:
I should have mentioned, I'm the:
Re: I messed up bootmisc.sh - now can't log in! guy
from debian-user
I just tried this with vi, and when I went to save, got this message:
E45: 'readonly
On 8/30/05, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
Bryan Donlan [EMAIL PROTECTED] wrote:
On 8/30/05, David W. Williams [EMAIL PROTECTED] wrote:
I should have mentioned, I'm the:
Re: I messed up bootmisc.sh - now can't log in! guy
from debian-user
I just tried this with vi
[EMAIL PROTECTED] wrote:
Michael Spang [EMAIL PROTECTED] wrote:
[EMAIL PROTECTED] wrote:
Michael Spang [EMAIL PROTECTED] wrote:
Alan Ianson wrote:
On Sat August 27 2005 06:38 pm, [EMAIL PROTECTED] wrote:
Alan Ianson [EMAIL PROTECTED] wrote:
On Sat August 27 2005 05:28 pm, [EMAIL
Alan Ianson wrote:
On Sat August 27 2005 06:38 pm, [EMAIL PROTECTED] wrote:
Alan Ianson [EMAIL PROTECTED] wrote:
On Sat August 27 2005 05:28 pm, [EMAIL PROTECTED] wrote:
I've tried booting off a cd-rom and mounting the disk, but I can't get
the disk to mount for some reason.
Michael Spang [EMAIL PROTECTED] wrote:
Alan Ianson wrote:
On Sat August 27 2005 06:38 pm, [EMAIL PROTECTED] wrote:
Alan Ianson [EMAIL PROTECTED] wrote:
On Sat August 27 2005 05:28 pm, [EMAIL PROTECTED] wrote:
I've tried booting off a cd-rom and mounting the disk, but I can't
[EMAIL PROTECTED] wrote:
Michael Spang [EMAIL PROTECTED] wrote:
Alan Ianson wrote:
On Sat August 27 2005 06:38 pm, [EMAIL PROTECTED] wrote:
Alan Ianson [EMAIL PROTECTED] wrote:
On Sat August 27 2005 05:28 pm, [EMAIL PROTECTED] wrote:
I've
Michael Spang [EMAIL PROTECTED] wrote:
[EMAIL PROTECTED] wrote:
Michael Spang [EMAIL PROTECTED] wrote:
Alan Ianson wrote:
On Sat August 27 2005 06:38 pm, [EMAIL PROTECTED] wrote:
Alan Ianson [EMAIL PROTECTED] wrote:
On Sat August 27 2005 05:28 pm, [EMAIL
I added a command to run mysqld to bootmisc.sh. Now everything boots
fine, but the command that I added to bootmisc.sh runs but doesn't exit,
leaving me with a system running mysql but at runlevel 2 (single user mode) .
It does not return a prompt so I can't log in and fix the problem. With it
On Sat August 27 2005 05:28 pm, [EMAIL PROTECTED] wrote:
I've tried booting off a cd-rom and mounting the disk, but I can't get the
disk to mount for some reason. I'm willing to try pretty much anything at
this point.
My default grub menu list has a recovery option. If that option isn't
Alan Ianson [EMAIL PROTECTED] wrote:
On Sat August 27 2005 05:28 pm, [EMAIL PROTECTED] wrote:
I've tried booting off a cd-rom and mounting the disk, but I can't get the
disk to mount for some reason. I'm willing to try pretty much anything at
this point.
My default grub menu list has a
On Sat August 27 2005 06:38 pm, [EMAIL PROTECTED] wrote:
Alan Ianson [EMAIL PROTECTED] wrote:
On Sat August 27 2005 05:28 pm, [EMAIL PROTECTED] wrote:
I've tried booting off a cd-rom and mounting the disk, but I can't get
the disk to mount for some reason. I'm willing to try pretty much
On Thu, 04 Mar 2004 06:20:04 +0100, [EMAIL PROTECTED] wrote:
Trouble is, I can't now install the regular woody version of KDE.
[snip]
I'm not really sure how I got into this rut, but I'd welcome with open arms any
suggestions on how to get out.
After setting sources.list right, I'd suggest
Hmm. I tried apt-get install kdebase, which gives me:
Sorry, but the following packages have unmet dependencies:
kdebase: Depends: kdelibs3 (= 4:2.2.2-1) but it is not going to be installed
Depends: libkonq3 (= 4:2.2.2-14.7) but it is not going to be installed
Depends:
Hello all,
I've managed to badly screw up apt-get by going from KDE 2.2 in woody to a KDE 3.2
woody backport.
Shame on me, but now I've uninstalled the 3.2 backport and reset my sources.list
to have the following (uncommented) lines:
deb http://ftp.us.debian.org/debian/ stable main
deb-src
This is propably due to a large amount of unresolved dependencies. I've
tried similar when trying to install and old package in a new
system. The old package want'ed to downgrade a lot of other packages and
all of h*ll broke loose... I've solved the dependencies problem by calling
apt-get -f
Stan Brown wrote:
I just really messed up!
I have a stable machine, and i had installed all the PostgreSQL related pa
ckages
from the stable archive, and all was well.
Then I downloaded all the PostgreSQL 7.1 RC1 packages from
http://people.debian.org/~elphick/postgresql/,
On Sat Apr 14 02:18:40 2001 Oliver Elphick wrote...
Stan Brown wrote:
I just really messed up!
I have a stable machine, and i had installed all the PostgreSQL related pa
ckages
from the stable archive, and all was well.
Then I downloaded all the PostgreSQL 7.1 RC1 packages
* Stan Brown [EMAIL PROTECTED], 2001-04-14 17:29 +0200:
On Sat Apr 14 02:18:40 2001 Oliver Elphick wrote...
You got the packages built for unstable; if you look more closely in that
URL you will also find packages for potato.
So I dselect _all_ postgress related packages (hey I can
Hi Again Stan,
Sorry your having so much trouble. I'm not certain how to cure the
dselect
wanting to uninstall 208 packages. Maybe dpkg --clear-avail command?
May I suggest using a script I made to save your currently installed
package
state/list to a floppy. Then if
I just really messed up!
I have a stable machine, and i had installed all the PostgreSQL related
packages
from the stable archive, and all was well.
Then I downloaded all the PostgreSQL 7.1 RC1 packages from
http://people.debian.org/~elphick/postgresql/, put them in a directory all to
Hi Stan,
Get the postgresql package that you had installed before, and then...
dpkg --force-downgrade postgresql-original version
If neccessary
dpkg --force-downgrade --force-overwrite postgresql-original version
E-mail back if that doesn't work of course.
Hope that helps you,
Jimmy
CTRL - ALT KP
+ or KP - to zoom in or out.
Unfortunately thats all the V5 appears good for at the moment ,the 3d
drivers appear to suck, but im sure they will improve, this is linux
after all , and debian to top it off - cant lose :).
Original Message
Subject: Re: I messed up
Corey,
Where shall I send the case of beers and the strippers? I finally have my
Xfree86 4.0.1 up and running, at 1280x1024x16bpp. Thank You !
Now, I understand that Xfree86 4.0.1 has built-in True Type support. So
that means I can do away with the xfstt? What lines do I need to add to my
Claudette if I get either the beers or the strippers, you will have made a
friend for life. In fact just the suggestion of them makes you a friend
automatically :)
I must thank whoever mentioned the XFree86 -configure command, that
starting point was the catalyst to getting X working - the rest
On Fri, Nov 03, 2000 at 11:13:41PM -0500, Joel Dinel wrote:
OK, I found out that you don't use XF86Setup anymore.
XFree86 -configure seems to detect my stuff OK. When I run XFree86
-xf86config /root/whatever.file I get a nice empty gray screen, and
the mouse won't mouse. That's as far as it
Actually, It's Joel. I'm using the wife's Pc right now.
Yes well I believe there is a sample of a XF86Config fore buried in my
filesystem somewhere. I'll try to figure out the syntax for the fonts from
there.
When I exit X, I noticed a message about not being able to load the Speedo
fonts and
Claudette Woodgate [EMAIL PROTECTED] writes:
Corey,
Where shall I send the case of beers and the strippers? I finally have my
Xfree86 4.0.1 up and running, at 1280x1024x16bpp. Thank You !
OK I've never understood what's so great about high resolutions. The
higher the resolution, the
%% Krzys Majewski [EMAIL PROTECTED] writes:
km OK I've never understood what's so great about high resolutions. The
km higher the resolution, the smaller the stuff on your screen, the
km closer to the screen you sit, the more you squint to see stuff, the
km sooner you go
Chris writes:
OK I've never understood what's so great about high resolutions.
Lots and lots of really small pixels.
The higher the resolution, the smaller the stuff on your screen,...
The higher the resolution the more stuff I can get on the screen while
including enough pixels in each bit
A simple apt-get upgrade today left me with Xfree86 4.0.1 and this little
problem :
[EMAIL PROTECTED]:~$ sudo XF86Setup
Warning SERVER specification missing in Card database entry Trident TGUI9420
(generic) (line 2178).
Warning SERVER specification missing in Card database entry Trident
Hi,
I'm in the same boat. A routine apt-get dist-upgrade on my woody
box upgraded X and now GDM doesn't work. Before I reinstall the old
version of X, does anyone know how to fix it? I'm using the most
recent version of GDM. Thanks.
Casey
On Fri, Nov 03, 2000 at 10:39:46PM -0500, Joel Dinel wrote:
A simple apt-get upgrade today left me with Xfree86 4.0.1 and this little
problem :
OK, I found out that you don't use XF86Setup anymore.
XFree86 -configure seems to detect my stuff OK. When I run XFree86 -xf86config
Ok, next step I can suggest is this:
In the XF86Config.new file thats been created, under the InputDevice
section change the Option protocol auto line to Option
protocol IMPS/2.
This has got my PS/2 mouse working.
More news as the hacking of config files happens :)
Cheers,
Corey J. Popelier
Oh, and after doing that, copying the XF86Config.new file to /etc/X11
directory meant I could now run startx again, and resume to having X
running with WindowMaker. Allbeit in a god awful resolution, so thats the
next step.
BTW, I *think* the ZAxisMapping for intelli-mice is now:
Option
My next trick for those who are interested was to copy the
DefaultColorDepth line from the Screen section of the X3.3.6 config file
to the X4.0.1 config file. This now gives me the appropriate colour
depths, but its still in 640x480 at this stage.
For those who don't really want a running
Cheers,
Corey J. Popelier
http://members.dingoblue.net.au/~pancreas
-- Forwarded message --
Date: Sat, 4 Nov 2000 13:08:46 +0800 (WST)
From: Corey Popelier [EMAIL PROTECTED]
To: Casey Henderson [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Subject: Re: I messed up Xfree86
Well
Hey,
I was installing Debian 2.1 Slink, and I was trying to get through the
installation process as quickly aspossible. I accidently made VGA16 as the
default x server instead of SVGA. How do I make SVGA the default X server?
Thanks,
Cameron Matheson
On Sun, Jan 16, 2000 at 08:41:40PM -0700, Cameron Matheson wrote:
Hey,
I was installing Debian 2.1 Slink, and I was trying to get through the
installation process as quickly aspossible. I accidently made VGA16 as the
default x server instead of SVGA. How do I make SVGA the default X
Thanks man, that worked perfectly.
Cameron Matheson
On Sun, Jan 16, 2000 at 08:41:40PM -0700, Cameron Matheson wrote:
Hey,
I was installing Debian 2.1 Slink, and I was trying to get through the
installation process as quickly aspossible. I accidently made VGA16 as
the
default x server
Boot from your rescue flop, edit your /etc/inittab file and
change the line:
id:5:initdefault:
to:
id:3:initdefault:
I don't believe this will work on a Debian system by default, since Debian
by default doesn't make any differences between runlevels 2-5. Are you by
any chance a RedHat
On 22/10/99 Brad wrote:
Boot from your rescue flop, edit your /etc/inittab file and
change the line:
id:5:initdefault:
to:
id:3:initdefault:
I don't believe this will work on a Debian system by default, since Debian
by default doesn't make any differences between runlevels 2-5. Are you
-BEGIN PGP SIGNED MESSAGE-
On Fri, 22 Oct 1999, Ethan Benson wrote:
On 22/10/99 Brad wrote:
Boot from your rescue flop, edit your /etc/inittab file and
change the line:
id:5:initdefault:
to:
id:3:initdefault:
I don't believe this will work on a Debian system by
On 22/10/99 Brad wrote:
RedHat doesn't start xdm through init either, but uses a script in
/etc/rc.d/init.d. RedHat is set up so that xdm will only start in runlevel
5 (although you could always run it by hand in any runlevel if you felt
like it). The change Onno posted would set the default
Is there a way to keep debian from trying to start x at start up? I messed
up the resolution and can't read anything. I think MS products sometimes
use F8. How about debian? Is there any other way to get to the command line
and re-run xf86config? I tried using my boot disk, but this too tried
After you have booted up, press Alt-Ctrl-F1 which will get you to a text
login prompt. Login, type 'killall xdm' and then run xf86config, and
have your monitor settings handy.
Matthew
jh wrote:
Is there a way to keep debian from trying to start x at start up? I messed
up the resolution
On 21/10/99 jh wrote:
Is there a way to keep debian from trying to start x at start up? I messed
up the resolution and can't read anything. I think MS products sometimes
use F8. How about debian? Is there any other way to get to the command line
and re-run xf86config? I tried using my boot disk
Matthew Dalton posts:
type 'killall xdm' and then run xf86config
Why do U want to do a 'kill' when U can stop the daemon 'xdm' ?
Typing '/etc/init.d/xdm stop' at the CLI is a better go. Do an
'xf86config' after that. Restart the daemon 'xdm' after testing out
with the X -probeonly test, by
Boot from your rescue flop, edit your /etc/inittab file and
change the line:
id:5:initdefault:
to:
id:3:initdefault:
Your should be fine ;-)
Good luck,
Onno
At 06:56 PM 10/21/99 -0600, jh wrote:
Is there a way to keep debian from trying to start x at start up? I messed
up the resolution
? I messed
up the resolution and can't read anything. I think MS products sometimes
use F8. How about debian? Is there any other way to get to the command line
and re-run xf86config? I tried using my boot disk, but this too tried to
start x. I got into this trouble because I do not know my systems
At 11:20 AM 10/22/99 +1000, Matthew Dalton wrote:
After you have booted up, press Alt-Ctrl-F1 which will get you to a text
login prompt. Login, type 'killall xdm' and then run xf86config, and
have your monitor settings handy.
Matthew
Or this hmm with Linux there are plenty of options, some
Well a lot anyways. I wanted to tryout xdm, so I dselected it, ran it
manually, and it worked. I purged it, installed gdm to check that out,
it didn't work (somthing about no display configured, I didn't feel like
messing with it). I purged gdm to try wdm, that ran but obviously
wasn't
Oops. I messed up my permissions on the /etc directory and the
/var/spool/lpd. Would someone be kind enough to ls -l those directories
and send me the results. I know it won't be a perfect match, but it
oughtta be close enough. Thanks.
Kent West
[EMAIL PROTECTED]
On Sun, 6 Apr 1997, Jim Smith wrote:
[... much deleted ...]
Ya can't be too paranoid!!
[ ... ]
Even paranoids have real enemies
- Attributed to Dr. Henry Kissinger
Michael J. McCann wrote:
On Sun, 6 Apr 1997, Jim Smith wrote:
[... much deleted ...]
Ya can't be too paranoid!!
[ ... ]
Even paranoids have real enemies
- Attributed to Dr. Henry Kissinger
Just because you're paranoid doesn't mean somebody isn't out to
Kurt Cockrum wrote:
In-Reply-To: [EMAIL PROTECTED]
Sounds like, right offhand, if you could recover an old /etc/lilo.conf, maybe
from an old backup (hope your rescue disk has the stuff on it necessary to
restore from a backup), or by just typing it in, you could run lilo on that
and
Glen Journeay wrote:
Jim,
Your scsi driver module should be located in
/lib/modules/2.x.x/scsi. If you can boot up from a recover floppy then
try and mount your normal root under /mnt and get at your modules (or
recover your old kernel). Hope this helps. I know how this feels
78 matches
Mail list logo
