unsubscribe

[Dan Winkler]

-Original Message-From: [EMAIL PROTECTED]To: [EMAIL PROTECTED]Sent: Thu, 27 Mar 2003 17:10:54 -0600 (CST)Subject: debian-user-digest Digest V2003 #1041To UNSUBSCRIBE, send email to [EMAIL PROTECTED] with
a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]


debian-user-digest DigestVolume 2003 : Issue 1041

Today's Topics:
  Difference between "woody" and "stab  [ Uwe Storbeck <[EMAIL PROTECTED]> ]
  creating boot cds [ adit y <[EMAIL PROTECTED]> ]
  Re: Official Exim 4 package   [ Steve Lamb <[EMAIL PROTECTED]> ]
  Re: Official Exim 4 package   [ Steve Lamb <[EMAIL PROTECTED]> ]
  apt-get dist-upgrade bails[ Patrick Wiseman <[EMAIL PROTECTED] ]
  apt-get dist-upgrade bails[ Patrick Wiseman <[EMAIL PROTECTED] ]
  Re: Problems with horde/imp   [ UnKnown <[EMAIL PROTECTED]> ]
  Re: sylpheed-doc package broken?  [ [EMAIL PROTECTED] ]
  Re: name conflict: ud / ud-ldap   [ Colin Watson <[EMAIL PROTECTED]> ]
  Re: Newbee-ish X and root question[ Vineet Kumar <[EMAIL PROTECTED] ]
  Re: [OT, FLAME] Linux Sucks   [ Hal Vaughan <[EMAIL PROTECTED] ]
  Re: apt-get dist-upgrade bails[ Jonathan Matthews  ]
  Re: sylpheed-doc package broken?  [ Colin Watson <[EMAIL PROTECTED]> ]
  Re: "Your Sexual Partner Will Not Kn  [ "linux stuff" <[EMAIL PROTECTED] ]
  Re: [OT, FLAME] Linux Sucks   [ Colin Watson <[EMAIL PROTECTED]> ]
Date: Thu, 27 Mar 2003 22:03:39 +0100
From: Uwe Storbeck <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Subject: Difference between "woody" and "stable" in apt Default-Release?
Message-ID: <[EMAIL PROTECTED]>
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline

Hi,

I've just seen a somewhat irritating behaviour of apt-get
update/upgrade. Formerly I thought "woody" and "stable" are synonyms
for now because Woody is the current stable distribution.

I've set Default-Release to "stable" in apt.conf:

APT {
  Get {
Fix-Broken "true";
Show-Upgraded "true";
Purge "true";
  };
  Default-Release "stable";
};

If I add woody-proposed-updates to my sources.list and do an upgrade
with apt-get update/upgrade the packages from proposed-updates won't
get installed:

deb http://http.us.debian.org/debian woody-proposed-updates main contrib non-free

# apt-get upgrade
Reading Package Lists... Done
Building Dependency Tree... Done
0 packages upgraded, 0 newly installed, 0 to remove and 0  not upgraded.

# apt-show-versions -a -p logcheck
logcheck1.1.1-13.1  install ok installed
logcheck1.1.1-13.1  stable
logcheck1.1.1-13.5.woody.0  proposed-updates
logcheck/stable uptodate 1.1.1-13.1

If I change Default-Release to "woody" proposed-updates get installed
as expected.

So if I want proposed-updates I have to set Default-Release to "woody"
instead of "stable". Not just understandable, but as far as good.

If I additionally want to mix stable and testing releases and use apt
pinning things will be somewhat more complicated and don't work as
expected anymore.

My preferences:

Package: *
Pin: release a=woody-proposed-updates,o=Debian,l=Debian
Pin-Priority: 999
Package: *
Pin: release a=stable,o=Debian,l=Debian
Pin-Priority: 900
Package: *
Pin: release a=sarge-proposed-updates,o=Debian,l=Debian
Pin-Priority: 777
Package: *
Pin: release a=testing,o=Debian,l=Debian
Pin-Priority: 700

If I set Default-Release to "stable" pinning works as expected, packages
will be installed from Woody by default. But as already written packages
from proposed-updates will not be installed on upgrades.
If I change Default-Release to "woody" to get the proposed-updates apt
tries to upgrade all my packages to testing on an apt-get upgrade run.
I've tried some variations in the preferences file with "woody" and
"sarge" instead of "stable" and "testing" but nothing works.

What am I doing wrong?

I want my system mostly be pinned to stable with proposed-updates
installed. Additionally I want to use a few packages from testing.

Regards

Uwe
Date: Thu, 27 Mar 2003 12:54:50 -0800 (PST)
From: adit y <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Subject: creating boot cds
Message-ID: <[EMAIL PROTECTED]>
In-Reply-To: <[EMAIL PROTECTED]>
Content-Type: text/plain; charset=us-ascii

Hi,

Just trying to learn how to make bootable installation
cds. Boot cd's downloaded from the website work fine, 
when i raw write partboot.img, partroot.img to a a 2
floppy disks and boot using floppies it works fine. if
i burn them to cd the system boots and looks like it
is asking for a second floppy which has the
partroot.img , if i use the floppy disk it works fine.
but why do i need to insert the second floppy, i
already have the partroot.img in the root directory .
some how the cd i burnt is not  able to know that the
partroot.img image it is expecting is present in the
root directory.

it always stops at vfs: insert root floppy disk to
load ramdisk and present enter it's the same with
e

Re: Can't get my mouse to work

[Dan Winkler]

Ah okay, when I try using gpmconfig it tells me "gpm: /dev/psaux: No such
device".  So what does that mean?  There is a file /dev/psaux which looks
right, but I can't get "cat < /dev/psaux" to work either.  Any thoughts?

-Original Message-
From: Robert Wilderspin <[EMAIL PROTECTED]>
To: Dan Winkler <[EMAIL PROTECTED]>
Date: Tuesday, April 07, 1998 2:49 PM
Subject: Re: Can't get my mouse to work


>On 7 Apr 98 00:02:50 GMT, in linux.debian.user you wrote:
>
>>The mouse is a PS/2 mouse.  It works fine under Windows 95.  It does not
>>work at all under Linux.  When I run XF86Setup, I select PS/2 mouse and
set
>>the device to be /dev/psaux and "apply" the changes, but moving the mouse
>>does not move the cursor.  The /dev/psaux file exists and looks right.  I
>>believe the kernel has PS/2 support included because in /var/log/messages
>>there's a line that says "PS/2 Auxiliary pointing device detected --
driver
>>installed."  But in /proc/interrupts there's no mention of a PS/2 device
or
>>a mouse.  I've also tried disabling both serial ports and the parallel
port
>>in the BIOS to see if there was some IRQ conflict, but that made no
>>difference.
>>
>>So... what should I try next?
>
>If you haven't already, try to get it working with gpm.  Run
>"gpmconfig" (if I remember it correctly) and select the PS/2 device.
>The man-pages describe how to do this better.
>
>If that works okay, then you can follow the man-pages again to use gpm
>to handle it under X using the "-R" switch, changing the device in
>XF86Config to "/dev/gpmdata" with type "MouseSystems".  What this does
>is set up a fake device for X to use, controlled via gpm.  This is all
>from my rusty memory, but I know that it should work.
>
>
>It's a shame that simple things like this are so complicated to get
>working, as I'm sure it puts a lot of people off using Linux.  I hope
>that this is of some use to you.
>
>Rob Wilderspin.
>--
>The problem with people is that half of them are
>below average intelligence. And don't realise it.
>-= (send replies to rob@)
>


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Can't get my mouse to work

[Dan Winkler]

I've installed Debian 1.3.1 on my Gateway Pentium Pro and I can't get the
mouse to work.  I've received a lot of help from Rob Browning so I can
supply a lot of information but we have run out of ideas and could use some
help.  Here's what we know:

The mouse is a PS/2 mouse.  It works fine under Windows 95.  It does not
work at all under Linux.  When I run XF86Setup, I select PS/2 mouse and set
the device to be /dev/psaux and "apply" the changes, but moving the mouse
does not move the cursor.  The /dev/psaux file exists and looks right.  I
believe the kernel has PS/2 support included because in /var/log/messages
there's a line that says "PS/2 Auxiliary pointing device detected -- driver
installed."  But in /proc/interrupts there's no mention of a PS/2 device or
a mouse.  I've also tried disabling both serial ports and the parallel port
in the BIOS to see if there was some IRQ conflict, but that made no
difference.

So... what should I try next?


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]