Re: stupid question

[Mark Allums]

On 5/13/2010 1:37 AM, steef wrote:


hi list,

how do i get rid of the message of a new (of course much valued)
maintainer Christian about MTA'S and cron when updating squeeze on the
commandline before using startx? apt-get upgrade hangs on this message
and i do not know the protocol to go on in this situation (if there is
any). so i cannot upgrade.

thank you in advance!



Is it a changelog message?  If it's a dialog, just dismiss it.  If X is 
running, use the mouse.  If not, the keyboard.


Tell us more.  When and where does the message appear?

MAA



--
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/4beba297.3090...@allums.com

Re: stupid question

[Jerome BENOIT]

Hello !

just enter `q' !

hth,
Jerome

On 13/05/10 14:37, steef wrote:


hi list,

how do i get rid of the message of a new (of course much valued)
maintainer Christian about MTA'S and cron when updating squeeze on the
commandline before using startx? apt-get upgrade hangs on this message
and i do not know the protocol to go on in this situation (if there is
any). so i cannot upgrade.

thank you in advance!

steef





--
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/4beba18a.1080...@rezozer.net

Re: libc6 upgrade lenny to squeeze failed, now dpkg is broken

[Sven Joachim]

On 2010-05-12 23:24 +0200, Chris Austin wrote:

>> On 2010-05-11 22:11 +0200, Chris Austin wrote:
>
>>> I was required to upgrade libc6 from lenny to squeeze in order to meet
>>> dependencies to install a package from unstable, but the libc6 upgrade
>>> failed because libc-bin was not installed.
>
>> How could this happen, given that libc6 depends on libc-bin?
>
> I was using KPackage, which I thought is a package manager like aptitude or
> synaptic.

You should probably learn some other tool, because kpackage is not
maintained anymore and has been removed from sid.

> I guess the answer to this is that for system-critical packages, one should
> first do a "dry run" in KPackage, by clicking the "Test (do not install)"
> checkbox.  But it would be really helpful if there was a list somewhere of
> the system-critical packages for which one needs to do this, to save having
> to do a dry run for every new package.

The right way to do this is to use apt pinning which is much less
error-prone than downloading and installing selected packages by hand.

> I have been referring to this old list while doing Lenny to Squeeze upgrades
> today.  It would be really helpful if there were lists like this for Lenny and
> Squeeze somewhere on debian.org.  Besides, it's nice to know what the 
> Essential
> and Required packages are!

You can get the list with aptitude:

aptitude search "~E ~Asqueeze"
aptitude search "~prequired ~Asqueeze"

lists all Essential and Required packages in squeeze.  Of course this
requires an entry for squeeze in your sources.list which brings us back
to apt pinning.

> I've learned today that when there are circular conflicts while upgrading, 
> e.g.
> libcairo2 has to be upgraded to install xulrunner-1.9.1, but upgrading
> libcairo2 breaks xulrunner-1.9, it helps to use the dpkg --auto-deconfigure
> option before the -i action-parameter, e.g.
>
> dpkg --auto-deconfigure -i libcairo2_1.8.10-4_i386.deb
>
> Then dpkg gives a nice message about considering deconfiguration of
> xulrunner-1.9, then decides to do it, and it works, or at least, it has done,
> the two or three times I have tried it today.

This is indeed a nice trick to know, but apt would do this for you
automatically.

Sven


-- 
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/878w7ob8gf@turtle.gmx.de

stupid question

[steef]

hi list,

how do i get rid of the message of a new (of course much valued) 
maintainer Christian about MTA'S and cron when updating squeeze on the 
commandline before using startx? apt-get upgrade hangs on this message 
and i do not know the protocol to go on in this situation (if there is 
any). so i cannot upgrade.


thank you in advance!

steef


--
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/4beb9e2b.9030...@home.nl

Re: emacs22-nox emacs23-nox how to run with X and without X on same machine?

[Phil Requirements]

On 2010-05-13 00:13:15 -0400, Mitchell Laks wrote:
> How can I get to use both emacs23-nox and emacs with gtk BOTH on the
> same machine, sometimes with X and sometimes without?

Hi Mitchell,

If you want to use Emacs with the GUI interface sometimes, you can
safely ignore the emacs23-nox package. You don't need to have both
emacs23 and emacs23-nox installed.

emacs23 - includes both the GUI version and the text-mode version.
emacs23-nox - has had all the GUI stuff stripped out.

Here's how I like to use Emacs, so it can be used in both GUI and
text-mode at the same time. First, I start Emacs in daemon mode:

emacs --daemon

Then I use emacsclient to open files from the command line or
from a file manager.

emacsclient myfile.txt -c
emacsclient myfile.txt -t

Using the -c option, the file will be opened in a GUI window.
Using the -t option, the file will be opened in text mode.

Hope this helps,

Phil


-- 
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/20100513063035.ga2...@kasploosh.net

Re: 64-bit netbooks with Debian linux

[Bill Wohler]

Peter Tenenbaum  writes:

> First, I intend to build a home computer which will run linux, and
> it will be 64-bit; since I'm quite new to maintaining my own linux
> computers, I'd rather limit the number of differences between the
> home machine and my portable.

Hi PT,

In regards to Debian, don't let this be a discriminator.

If you had a 64-bit and 32-bit system, it would only mean that you'd
have to burn two installation CDs. Once those CDs were installed, your
installations would be mostly indistinguishable. After the initial
install, Debian grabs the right bits for your system.

When I switched from 32-bit to 64-bit, the only difference I saw
besides a different installation image was a different kernel.

-- 
Bill Wohler  aka 
http://www.newt.com/wohler/
GnuPG ID:610BD9AD


-- 
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/871vdgqt4k@olgas.newt.com

Re: emacs22-nox emacs23-nox how to run with X and without X on same machine?

[Cláudio E. Elicker]

On Thursday 13 May 2010, Mitchell Laks wrote:
> hi
> I installed a new debian and I see that emacs23-nox conflicts with with
> emacs23. So what if I am trying to run emacs in a console in a machine
> withe emacs23 and not emacs23-nox installed? How can I get to use both
> emacs23-nox and emacs with gtk BOTH on the same machine, sometimes with X
> and sometimes without?
>
> thanks
> mitchell

emacs -nw

-- 
EMACS is my operating system; Linux is my device driver.


-- 
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/201005130147.59125.elic...@gmail.com

Re: libc6 upgrade lenny to squeeze failed, now dpkg is broken

[Mark Allums]

On 5/12/2010 4:24 PM, Chris Austin wrote:


I've learned today that when there are circular conflicts while upgrading, e.g.
libcairo2 has to be upgraded to install xulrunner-1.9.1, but upgrading
libcairo2 breaks xulrunner-1.9, it helps to use the dpkg --auto-deconfigure
option before the -i action-parameter, e.g.

dpkg --auto-deconfigure -i libcairo2_1.8.10-4_i386.deb

Then dpkg gives a nice message about considering deconfiguration of
xulrunner-1.9, then decides to do it, and it works, or at least, it has done,
the two or three times I have tried it today.



This may be a better way than I have been forced to do it.  Circular 
depencies crop up in Sid a lot.  The solution then is usually to be 
patient and wait for the Debians to straighten it out.


However, sometimes, one can't wait, and at such times, I have downloaded 
each package directly, using a web browser (or wget) and then used dpkg 
with options like --ignore-depends= or --force-overwrite.  Not 
recommended.  Not for newbies.  Not for the faint-of-heart.


But if we wanted to play it safe, we would stick to stable, and only 
upgrade to major releases.  And we would be content.  (And never learn 
anything.)


dpkg --auto-deconfigure is a gentler way, but you might want to see if 
aptitude can make some suggestions before jumping off the deep end.


And don't neglect the -s option of apt-get (and corresponding option of 
other package managers) to do dry runs.



MAA





--
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/4beb7e03.2080...@allums.com

emacs22-nox emacs23-nox how to run with X and without X on same machine?

[Mitchell Laks]

hi
I installed a new debian and I see that emacs23-nox conflicts with with 
emacs23. So what if I am 
trying to run emacs in a console in a machine withe emacs23 and not emacs23-nox 
installed? How can 
I get to use both emacs23-nox and emacs with gtk BOTH on the same machine, 
sometimes with X and sometimes 
without?

thanks
mitchell


-- 
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/20100513041314.ga10...@earthlink.net

Re: What to choose for Core i5 64 bits?

[Mark Allums]

If you have other i386 machines around, it may be convenient for you to
keep the same architecture so you can share the download bandwidth of
Debian updates, and things like that.


On the other hand, now might be a good time to begin the migration to 
the future.  32-bits will be around for a long time, but it will 
increasingly be relegated to older hardware and niche applications, such 
as embedded processors or cell phones and the like.  64-bits is going to 
be the "current" architecture for desktops, servers, and the like for a 
good while to come.


MAA





--
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/4beb78c1.9010...@allums.com

Re: Automounting problems.

[Dave Thayer]

On Wed, May 12, 2010 at 01:30:40PM -0700, Bob McGowan wrote:
> On 05/12/2010 02:55 AM, Chris Bannister wrote:
> > On Tue, May 11, 2010 at 10:54:47PM -0700, Marc Shapiro wrote:
> >> I am now slapping myself on the head for being so STUPID!  Automount is 
> >> working just fine, and has been all along.  Automount does its thing as 
> >> soon as a device is ACCESSED, not plugged in.  I was plugging the flash 
> >> drives in and looking in /mnt to see if they were showing up.  The 
> >> weren't.  The weren't supposed to, either.  As soon as I executed "ls 
> >> /mnt/lexar" lo and behold, there was the listing and everything was 
> >> working just fine.
> >>
> >> I think I'll slap myself on the head, again.
> > 
> > Not so fast! :) How are you supposed to access them if you don't know
> > what they will be labelled as?
> > 
> > What does "ls /mnt/" do?
> > 
> > Are you supposed to carry round a scrap of paper with the mount labels
> > written down?
> > 
> 
> No...
> 
> Generally, you set up an auto.xxx file to create a mount point in some
> specific directory that is not /media.  For example, with xxx being 'usb':
> 
>  auto.usb: zodiac -fstype=vfat,rw,user,noauto,gid=backup,umask=002 \
>:/dev/disk/by-id/usb-ROCKCHIP_USB_MP3_USBV1.00
> 
> And auto.master:
> 
>  /var/autofs/usb /etc/auto.usb --timeout=###
> 
> This setup associates the auto.usb file with /var/autofs/usb and the
> device identified by the id with the name zodiac.  The timeout should be
> set to some convenient value.
> 
> So, automount will mount that device on /var/autofs/usb/zodiac, when it
> is accessed.
> 

It should be noted that the  --ghost option of automount will create
an appropriate "ghost" directory for the device's mount point. For the
above auto.master stanza you could use:
  /var/autofs/usb /etc/auto.usb --timeout=### --ghost

This can lead to a cluttered /var/autofs/usb directory, however,
unless you do some udev-based scripting to manage things on the fly.

dt
  


-- 
Dave Thayer   | Whenever you read a good book, it's like the 
Denver, Colorado USA  | author is right there, in the room talking to 
d...@thayer-boyle.com | you, which is why I don't like to read 
  | good books. - Jack Handey "Deep Thoughts"


-- 
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/20100513033544.ga9...@thayer-boyle.com

Re: What to choose for Core i5 64 bits?

[Mark Allums]

On 5/12/2010 10:41 PM, Aaron Toponce wrote:
I for one want to get my money out of my hardware. If

you don't want a 64-bit system, then why did you pay for it?


+1





--
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/4beb7730.1010...@allums.com

Re: What to choose for Core i5 64 bits?

[Aaron Toponce]

On 05/12/2010 07:03 PM, Stefan Monnier wrote:
>> The 64-bit vs 32-bit argument is multi-faceted.  It gets much deeper than
>> just addressing more than 3GB of RAM:
>> * twice the transfer width on the bus
> 
> Nope, no difference on the bus.   Most accesses will be
> cache-line-sized anyway at that level.

You're kidding, right? You can push twice the data, which means faster
CPU to memory utilization for CPU intensive applications. Flash anyone?

>> * no memory split issues
> 
> For <=3GB systems, that makes no difference.  And as someone running
> a bigmem kernel on a 4GB system, I can say that even for other systems,
> it's not necessarily relevant.

It's very relevant. You must not have run into this issue much. 4:4
kernel splits are the best you can do on a 32-bit system, but it comes
at a performance cost. Splitting and performance are never an issue on
64-bit until you've reache 17 EB of RAM.

>> * increased virtual address space
> 
> Right.  Unlikely he'll ever notice it.

Whether he will or won't isn't the issue. I'm not discussing use cases,
I'm discussing the facts on why 64-bit is superior to 32-bit.

>> * more breathing room for mmap()'d files
> 
> Again, unlikely he'll ever notice it (otherwise he wouldn't have asked).

See above.

>> * deeper nested system calls with increased stability
> 
> I see no evidence of increased stability and have no idea what you want
> to say with "deeper nested system calls".

I'll give you an example. Use XFS on LVM, and export the mount over NFS.
The nested system calls in this scenario will cause a kernel oops on any
4K 32-bit kernel nearly every time (the default for Debian GNU/Linux,
Fedora, Ubuntu, openSUSE, etc). On a 64-bit kernel, because you have the
ability to make deeper nested system calls, you have stability in your
infrastructure. Something that couldn't be achieved with a 32-bit kernel.

>> * certain applications and operations will execute faster
> 
> Yup.  And others will be slower since you'll have to move around more
> data (up to twice as much if your data is made up mostly of pointers),
> which means that the apparent cache and RAM size will end up
> being reduced.

The same would be said for a 32-bit application implemented the same
way. Poor software development is hardly an argument against choosing a
CPU architecture.

>> If you have the hardware, you should definitely be running a 64-bit
>> operating system, even if you don't have 4GB+ of RAM.
> 
> If you have to ask, you probably won't notice any difference
> either way.

To each their own. I for one want to get my money out of my hardware. If
you don't want a 64-bit system, then why did you pay for it?

-- 
. O .   O . O   . . O   O . .   . O .
. . O   . O O   O . O   . O O   . . O
O O O   . O .   . O O   O O .   O O O



signature.asc
Description: OpenPGP digital signature

Re: aptitude update thinks there are no updates! (solved by deleting apt/lists)

[Chris Bannister]

On Wed, May 12, 2010 at 05:53:05PM +0530, Abhishek Dasgupta wrote:
> Hi all,
> 
> After about a fortnight, I tried to update my Debian squeeze desktop,
> 300 updates.
> 
> I issue a safe-upgrade, but the electricity goes out just as the
> updates begin downloading. After I turn the computer back on, issuing
> a safe-upgrade shows there are no updates! I try to aptitude update

The power going out during this process has caused this.

> but it thinks that the repositories are already updated, though
> apt-cache show nautilus gives the version 2.28.4. As I was in a hurry
> at the time, I just deleted /var/lib/apt/lists, so aptitude had no

OK, so "/var/lib/apt/lists" was probably corrupted.

>I am curious as to how this (bug?) could have occurred. 

Well, the power going out has obviously affected "/var/lib/apt/lists"
could be because the kernel didn't have a chance to flush its write
buffers?

>After all this I checked
> mirror.cse.iitk.ac.in  and it does have nautilus 2.30.1, so maybe the
> first no-updates scenario was also caused by this bug/problem.

The mirror could have synced meantime.

-- 
"Religion is excellent stuff for keeping common people quiet."
   -- Napoleon Bonaparte


-- 
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/20100513044430.gb18...@fischer

Re: Automounting problems.

[Chris Bannister]

On Wed, May 12, 2010 at 01:30:40PM -0700, Bob McGowan wrote:
> On 05/12/2010 02:55 AM, Chris Bannister wrote:
> > On Tue, May 11, 2010 at 10:54:47PM -0700, Marc Shapiro wrote:
> >> I am now slapping myself on the head for being so STUPID!  Automount is 
> >> working just fine, and has been all along.  Automount does its thing as 
> >> soon as a device is ACCESSED, not plugged in.  I was plugging the flash 
> >> drives in and looking in /mnt to see if they were showing up.  The 
> >> weren't.  The weren't supposed to, either.  As soon as I executed "ls 
> >> /mnt/lexar" lo and behold, there was the listing and everything was 
> >> working just fine.


So it seems you have not set a symbolic link, Marc?


> > Are you supposed to carry round a scrap of paper with the mount labels
> > written down?

> No...
> 
> Generally, you set up an auto.xxx file to create a mount point in some
> specific directory that is not /media.  For example, with xxx being 'usb':
> 
>  auto.usb: zodiac -fstype=vfat,rw,user,noauto,gid=backup,umask=002 \
>:/dev/disk/by-id/usb-ROCKCHIP_USB_MP3_USBV1.00
> 
> And auto.master:
> 
>  /var/autofs/usb /etc/auto.usb --timeout=###
> 
> This setup associates the auto.usb file with /var/autofs/usb and the
> device identified by the id with the name zodiac.  The timeout should be
> set to some convenient value.
> 
> So, automount will mount that device on /var/autofs/usb/zodiac, when it
> is accessed.
> 

as per ...

> You then create a symlink from /media to the above name:
> 
>   cd /media; ln -s /var/autofs/usb/zodiac zodiac
> 
> You will then do something to access that name, like 'ls /media/zodiac'
> to get it mounted.

-- 
"Religion is excellent stuff for keeping common people quiet."
   -- Napoleon Bonaparte


-- 
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/20100513042854.ga18...@fischer

Re: What to choose for Core i5 64 bits?

[Stefan Monnier]

> The 64-bit vs 32-bit argument is multi-faceted.  It gets much deeper than
> just addressing more than 3GB of RAM:
> * twice the transfer width on the bus

Nope, no difference on the bus.   Most accesses will be
cache-line-sized anyway at that level.

> * no memory split issues

For <=3GB systems, that makes no difference.  And as someone running
a bigmem kernel on a 4GB system, I can say that even for other systems,
it's not necessarily relevant.

> * increased virtual address space

Right.  Unlikely he'll ever notice it.

> * more breathing room for mmap()'d files

Again, unlikely he'll ever notice it (otherwise he wouldn't have asked).

> * deeper nested system calls with increased stability

I see no evidence of increased stability and have no idea what you want
to say with "deeper nested system calls".

> * certain applications and operations will execute faster

Yup.  And others will be slower since you'll have to move around more
data (up to twice as much if your data is made up mostly of pointers),
which means that the apparent cache and RAM size will end up
being reduced.

> If you have the hardware, you should definitely be running a 64-bit
> operating system, even if you don't have 4GB+ of RAM.

If you have to ask, you probably won't notice any difference
either way.


Stefan


-- 
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/jwvzl04sjo4.fsf-monnier+gmane.linux.debian.u...@gnu.org

Re: What to choose for Core i5 64 bits?

[deloptes]

Aaron Toponce wrote:

> 
> If you have the hardware, you should definitely be running a 64-bit
> operating system, even if you don't have 4GB+ of RAM.
> 

+1


-- 
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/hsfahg$nc...@dough.gmane.org

Re: What to choose for Core i5 64 bits?

[Aioanei Rares]

On 05/13/2010 12:31 AM, Aaron Toponce wrote:

On 5/12/2010 2:53 PM, Stefan Monnier wrote:
   

I'd go with an i386 install unless you have more than 3GB of RAM, in
which case I'd go with an amd64 install (or an i386 with a 686-bigmem
kernel).
 

The 64-bit vs 32-bit argument is multi-faceted. It gets much deeper than
just addressing more than 3GB of RAM:

* twice the transfer width on the bus
* no memory split issues
* increased virtual address space
* more breathing room for mmap()'d files
* deeper nested system calls with increased stability
* certain applications and operations will execute faster

If you have the hardware, you should definitely be running a 64-bit
operating system, even if you don't have 4GB+ of RAM.

   

+1


--
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/4beb2b0a.2070...@gmail.com

Re: Lenny to Squeeze upgrade problems

[Boyd Stephen Smith Jr.]

On Wednesday 12 May 2010 17:07:09 Nick Douma wrote:
> On Wed, May 12, 2010 at 04:44:12PM -0500, Boyd Stephen Smith Jr. wrote:
> > On Wednesday 12 May 2010 16:27:08 Nick Douma wrote:
> > > On Wed, May 12, 2010 at 04:24:05PM -0500, Ron Johnson wrote:
> > > > On 05/12/2010 04:16 PM, Boyd Stephen Smith Jr. wrote:
> > > >> Added Tag: needs-to-be-in-release-notes
> > > >
> > > > To heck with the Release Notes!  This needs to be front and center
> > > > when you when you do the "apt-get update".
> > >
> > > It does appear when you do the aptitude full-upgrade, but it doesn't
> > > block the output, it just shoots by.
> > >
> > > I do wonder how they will handle this when squeeze gets stable. The
> > > whole update your kernel, reboot, update the rest is a bit too easy to
> > > fuck up for my taste. I completely assumed that I could just change the
> > > apt sources.list and do the full-upgrade.
> >
> > You should *always* read the release notes first.  It is actually rather
> > rare that a release just needs an 'aptitude full-upgrade'.  Usually,
> > perl, apt, aptitude, or dpkg should be updated first.
> 
> Well, I did try to look for release notes, but I did not find any for
>  Squeeze.

Yeah, they usually don't get worked on until after the testing freeze.  They 
will be fairly complete by the time Squeeze is released.  Until then, you are 
on your own; upgrades from stable to testing are sometimes tested throughout 
the stable life cycle, but all the issues aren't addressed until it's better 
known what will actually be in the new stable.

If you want testing, best to install testing, really.  Stable and the upgrade 
is possible, but it's actually slower.  (It might be the best way is the 
testing d-i is broken, though.)
-- 
Boyd Stephen Smith Jr.   ,= ,-_-. =.
b...@iguanasuicide.net  ((_/)o o(\_))
ICQ: 514984 YM/AIM: DaTwinkDaddy `-'(. .)`-'
http://iguanasuicide.net/\_/


signature.asc
Description: This is a digitally signed message part.

Re: Lenny to Squeeze upgrade problems

[Nick Douma]

On Wed, May 12, 2010 at 04:44:12PM -0500, Boyd Stephen Smith Jr. wrote:
> On Wednesday 12 May 2010 16:27:08 Nick Douma wrote:
> > On Wed, May 12, 2010 at 04:24:05PM -0500, Ron Johnson wrote:
> > > On 05/12/2010 04:16 PM, Boyd Stephen Smith Jr. wrote:
> > >> On Wednesday 12 May 2010 16:04:07 Jordan Metzmeier wrote:
> > >>> This issue is because the new udev requires a>  .31 kernel with
> > >>> sysrq_deprecated=n (I am going off memory here so don't quote me). This
> > >>> means you need to first upgrade to the squeeze kernel, reboot, then
> > >>> upgrade udev and proceed with the "updgrade".
> > >>
> > >> Added Tag: needs-to-be-in-release-notes
> > >
> > > To heck with the Release Notes!  This needs to be front and center when
> > > you when you do the "apt-get update".
> > 
> > It does appear when you do the aptitude full-upgrade, but it doesn't block
> >  the output, it just shoots by.
> > 
> > I do wonder how they will handle this when squeeze gets stable. The whole
> >  update your kernel, reboot, update the rest is a bit too easy to fuck up
> >  for my taste. I completely assumed that I could just change the apt
> >  sources.list and do the full-upgrade.
> 
> You should *always* read the release notes first.  It is actually rather rare 
> that a release just needs an 'aptitude full-upgrade'.  Usually, perl, apt, 
> aptitude, or dpkg should be updated first.

Well, I did try to look for release notes, but I did not find any for Squeeze.


signature.asc
Description: Digital signature

Re: Lenny to Squeeze upgrade problems

[Boyd Stephen Smith Jr.]

On Wednesday 12 May 2010 16:27:08 Nick Douma wrote:
> On Wed, May 12, 2010 at 04:24:05PM -0500, Ron Johnson wrote:
> > On 05/12/2010 04:16 PM, Boyd Stephen Smith Jr. wrote:
> >> On Wednesday 12 May 2010 16:04:07 Jordan Metzmeier wrote:
> >>> This issue is because the new udev requires a>  .31 kernel with
> >>> sysrq_deprecated=n (I am going off memory here so don't quote me). This
> >>> means you need to first upgrade to the squeeze kernel, reboot, then
> >>> upgrade udev and proceed with the "updgrade".
> >>
> >> Added Tag: needs-to-be-in-release-notes
> >
> > To heck with the Release Notes!  This needs to be front and center when
> > you when you do the "apt-get update".
> 
> It does appear when you do the aptitude full-upgrade, but it doesn't block
>  the output, it just shoots by.
> 
> I do wonder how they will handle this when squeeze gets stable. The whole
>  update your kernel, reboot, update the rest is a bit too easy to fuck up
>  for my taste. I completely assumed that I could just change the apt
>  sources.list and do the full-upgrade.

You should *always* read the release notes first.  It is actually rather rare 
that a release just needs an 'aptitude full-upgrade'.  Usually, perl, apt, 
aptitude, or dpkg should be updated first.

In this case, we need a kernel upgrade followed by a reboot.  It's not nice, 
especially since I think that will make this upgrade a two-reboot process 
instead of the "normal" one-reboot process.

Hopefully, this will get addressed in the udev packaging -- *most* of the time 
programs are required to support running on the previous release's kernel for 
specifically this reason.
-- 
Boyd Stephen Smith Jr.   ,= ,-_-. =.
b...@iguanasuicide.net  ((_/)o o(\_))
ICQ: 514984 YM/AIM: DaTwinkDaddy `-'(. .)`-'
http://iguanasuicide.net/\_/


signature.asc
Description: This is a digitally signed message part.

Re: What to choose for Core i5 64 bits?

[Aaron Toponce]

On 5/12/2010 2:53 PM, Stefan Monnier wrote:
> I'd go with an i386 install unless you have more than 3GB of RAM, in
> which case I'd go with an amd64 install (or an i386 with a 686-bigmem
> kernel).

The 64-bit vs 32-bit argument is multi-faceted. It gets much deeper than
just addressing more than 3GB of RAM:

* twice the transfer width on the bus
* no memory split issues
* increased virtual address space
* more breathing room for mmap()'d files
* deeper nested system calls with increased stability
* certain applications and operations will execute faster

If you have the hardware, you should definitely be running a 64-bit
operating system, even if you don't have 4GB+ of RAM.

-- 
. O .   O . O   . . O   O . .   . O .
. . O   . O O   O . O   . O O   . . O
O O O   . O .   . O O   O O .   O O O



signature.asc
Description: OpenPGP digital signature

Re: Re: libc6 upgrade lenny to squeeze failed, now dpkg is broken

[Chris Austin]

Hi,

> On 2010-05-11 22:11 +0200, Chris Austin wrote:

>> I was required to upgrade libc6 from lenny to squeeze in order to meet
>> dependencies to install a package from unstable, but the libc6 upgrade
>> failed because libc-bin was not installed.

> How could this happen, given that libc6 depends on libc-bin?

I was using KPackage, which I thought is a package manager like aptitude or
synaptic.  I need to try to keep up with the latest release of Cadabra, which
is now on the Debian website in Sid.  I tried to install the latest release
straight from Sid, using Konqueror.  Konqueror gives an option to open with
KPackage, which I always select.  Then attempting the install gives a list of
dependency problems, so I tried upgrading to Squeeze versions where
necessary, always using Konqueror and KPackage.  This worked fine until I got
to libc6, and apparently the lenny libc6 was uninstalled, then the squeeze
upgrade was going to be installed, but the installation failed because libc-bin
was not installed.  Normally one would then just install libc-bin, but in this
case, with Lenny libc6 uninstalled, and Squeeze libc6 installation failed, the
result was that dpkg was broken.  However I've now fixed the problem, as
reported in another message.

I guess the answer to this is that for system-critical packages, one should
first do a "dry run" in KPackage, by clicking the "Test (do not install)"
checkbox.  But it would be really helpful if there was a list somewhere of
the system-critical packages for which one needs to do this, to save having
to do a dry run for every new package.

I once made such a list for Etch, by searching for all the Essential and
Required packages in the Etch Packages.gz.  The list of the 61 Required
packages for Etch, which I believe includes the 24 Essential packages at its
start, is:

tzdata libc6 bsdutils diff findutils grep hostname mktemp perl-base sed tar
base-passwd mawk base-files libsepol1 libselinux1 sysvinit-utils libattr1
libacl1 coreutils debianutils dpkg gzip libncurses5 ncurses-base ncurses-bin
bash libdevmapper1.02 libblkid1 libuuid1 mount e2fslibs libcomerr2 libss2
e2fsprogs sysv-rc lsb-base initscripts sysvinit libslang2 zlib1g util-linux
libpam-runtime libpam0g libcap1 libdb4.3 libpam-modules login makedev passwd
procps gcc-4.1-base libgcc1 libstdc++6 dselect liblocale-gettext-perl
libtext-charwidth-perl libtext-iconv-perl libtext-wrapi18n-perl debconf-i18n
debconf

I have been referring to this old list while doing Lenny to Squeeze upgrades
today.  It would be really helpful if there were lists like this for Lenny and
Squeeze somewhere on debian.org.  Besides, it's nice to know what the Essential
and Required packages are!

I've learned today that when there are circular conflicts while upgrading, e.g.
libcairo2 has to be upgraded to install xulrunner-1.9.1, but upgrading
libcairo2 breaks xulrunner-1.9, it helps to use the dpkg --auto-deconfigure
option before the -i action-parameter, e.g.

dpkg --auto-deconfigure -i libcairo2_1.8.10-4_i386.deb

Then dpkg gives a nice message about considering deconfiguration of
xulrunner-1.9, then decides to do it, and it works, or at least, it has done,
the two or three times I have tried it today.

Best regards,
Chris Austin.


-- 
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/20100514.39841.chrisaus...@ukonline.co.uk

Re: Lenny to Squeeze upgrade problems

[Nick Douma]

On Wed, May 12, 2010 at 04:24:05PM -0500, Ron Johnson wrote:
> On 05/12/2010 04:16 PM, Boyd Stephen Smith Jr. wrote:
>> On Wednesday 12 May 2010 16:04:07 Jordan Metzmeier wrote:
>>> This issue is because the new udev requires a>  .31 kernel with
>>> sysrq_deprecated=n (I am going off memory here so don't quote me). This
>>> means you need to first upgrade to the squeeze kernel, reboot, then upgrade
>>> udev and proceed with the "updgrade".
>>
>> Added Tag: needs-to-be-in-release-notes
>
> To heck with the Release Notes!  This needs to be front and center when 
> you when you do the "apt-get update".

It does appear when you do the aptitude full-upgrade, but it doesn't block the 
output, it just shoots by.

I do wonder how they will handle this when squeeze gets stable. The whole 
update your kernel, reboot, update the rest is a bit too easy to fuck up for my 
taste. I completely assumed that I could just change the apt sources.list and 
do the full-upgrade.


signature.asc
Description: Digital signature

Re: Lenny to Squeeze upgrade problems

[Ron Johnson]

On 05/12/2010 04:16 PM, Boyd Stephen Smith Jr. wrote:

On Wednesday 12 May 2010 16:04:07 Jordan Metzmeier wrote:

This issue is because the new udev requires a>  .31 kernel with
sysrq_deprecated=n (I am going off memory here so don't quote me). This
means you need to first upgrade to the squeeze kernel, reboot, then upgrade
udev and proceed with the "updgrade".


Added Tag: needs-to-be-in-release-notes


To heck with the Release Notes!  This needs to be front and center 
when you when you do the "apt-get update".


--
Dissent is patriotic, remember?


--
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/4beb1c75.6080...@cox.net

Re: What to choose for Core i5 64 bits?

[Ron Johnson]

On 05/12/2010 03:53 PM, Stefan Monnier wrote:

What would it be the recommended architecture/versioin to choose for
download an install?


I'd go with an i386 install unless you have more than 3GB of RAM, in
which case I'd go with an amd64 install (or an i386 with a 686-bigmem
kernel).


Or i386 with an amd64 kernel.


If you have other i386 machines around, it may be convenient for you to
keep the same architecture so you can share the download bandwidth of
Debian updates, and things like that.



--
Dissent is patriotic, remember?


--
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/4beb1ab7.3030...@cox.net

Re: Lenny to Squeeze upgrade problems

[Boyd Stephen Smith Jr.]

On Wednesday 12 May 2010 16:04:07 Jordan Metzmeier wrote:
> This issue is because the new udev requires a > .31 kernel with
> sysrq_deprecated=n (I am going off memory here so don't quote me). This
> means you need to first upgrade to the squeeze kernel, reboot, then upgrade
> udev and proceed with the "updgrade".

Added Tag: needs-to-be-in-release-notes
-- 
Boyd Stephen Smith Jr.   ,= ,-_-. =.
b...@iguanasuicide.net  ((_/)o o(\_))
ICQ: 514984 YM/AIM: DaTwinkDaddy `-'(. .)`-'
http://iguanasuicide.net/\_/


signature.asc
Description: This is a digitally signed message part.

Re: Lenny to Squeeze upgrade problems

[Nick Douma]

On Wed, May 12, 2010 at 05:04:07PM -0400, Jordan Metzmeier wrote:
> This issue is because the new udev requires a > .31 kernel with
> sysrq_deprecated=n (I am going off memory here so don't quote me). This
> means you need to first upgrade to the squeeze kernel, reboot, then upgrade
> udev and proceed with the "updgrade".

I do remember seeing something shoot by with that message, but I didnt think 
anything of it at the time. I will try this, and see what happens.


signature.asc
Description: Digital signature

Re: Lenny to Squeeze upgrade problems

[Jordan Metzmeier]

This issue is because the new udev requires a > .31 kernel with
sysrq_deprecated=n (I am going off memory here so don't quote me). This
means you need to first upgrade to the squeeze kernel, reboot, then upgrade
udev and proceed with the "updgrade".

-- 
Jordan Metzmeier

Re: What to choose for Core i5 64 bits?

[Stefan Monnier]

> What would it be the recommended architecture/versioin to choose for
> download an install?

I'd go with an i386 install unless you have more than 3GB of RAM, in
which case I'd go with an amd64 install (or an i386 with a 686-bigmem
kernel).
If you have other i386 machines around, it may be convenient for you to
keep the same architecture so you can share the download bandwidth of
Debian updates, and things like that.


Stefan


-- 
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/jwvtyqc268v.fsf-monnier+gmane.linux.debian.u...@gnu.org

Re: Automounting problems.

[Bob McGowan]

On 05/12/2010 02:55 AM, Chris Bannister wrote:
> On Tue, May 11, 2010 at 10:54:47PM -0700, Marc Shapiro wrote:
>> I am now slapping myself on the head for being so STUPID!  Automount is 
>> working just fine, and has been all along.  Automount does its thing as 
>> soon as a device is ACCESSED, not plugged in.  I was plugging the flash 
>> drives in and looking in /mnt to see if they were showing up.  The 
>> weren't.  The weren't supposed to, either.  As soon as I executed "ls 
>> /mnt/lexar" lo and behold, there was the listing and everything was 
>> working just fine.
>>
>> I think I'll slap myself on the head, again.
> 
> Not so fast! :) How are you supposed to access them if you don't know
> what they will be labelled as?
> 
> What does "ls /mnt/" do?
> 
> Are you supposed to carry round a scrap of paper with the mount labels
> written down?
> 

No...

Generally, you set up an auto.xxx file to create a mount point in some
specific directory that is not /media.  For example, with xxx being 'usb':

 auto.usb: zodiac -fstype=vfat,rw,user,noauto,gid=backup,umask=002 \
   :/dev/disk/by-id/usb-ROCKCHIP_USB_MP3_USBV1.00

And auto.master:

 /var/autofs/usb /etc/auto.usb --timeout=###

This setup associates the auto.usb file with /var/autofs/usb and the
device identified by the id with the name zodiac.  The timeout should be
set to some convenient value.

So, automount will mount that device on /var/autofs/usb/zodiac, when it
is accessed.

You then create a symlink from /media to the above name:

  cd /media; ln -s /var/autofs/usb/zodiac zodiac

You will then do something to access that name, like 'ls /media/zodiac'
to get it mounted.

A simple 'ls /media' gives you the list of names that you've set up this
way.

To determine the name you need to use for the device path in the
auto.usb file, first do an 'ls' of /dev/disk/by-id before plugging the
device, and one after.  The new device name is what you use.

-- 
Bob McGowan


-- 
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/4beb0ff0.5060...@symantec.com

Lenny to Squeeze upgrade problems

[Nick Douma]

I just tried to upgrade my Lenny installation to Squeeze using the following 
method:

I changed my sources.list from

deb http://ftp.nl.debian.org/debian/ lenny main contrib non-free
deb-src http://ftp.nl.debian.org/debian/ lenny main contrib non-free

deb http://security.debian.org/ lenny/updates main contrib non-free
deb-src http://security.debian.org/ lenny/updates main contrib non-free

deb http://volatile.debian.org/debian-volatile lenny/volatile main contrib 
non-free
deb-src http://volatile.debian.org/debian-volatile lenny/volatile main contrib 
non-free

deb http://download.tuxfamily.org/shames/debian-lenny/desktopfx/unstable/ ./

deb http://ansani.it/debian/ stable contrib

deb http://ftp.uni-kl.de/debian-multimedia/ stable main
deb-src http://ftp.uni-kl.de/debian-multimedia/ stable main

deb http://www.backports.org/debian lenny-backports main contrib non-free

to

deb http://ftp.nl.debian.org/debian/ squeeze main contrib non-free
deb-src http://ftp.nl.debian.org/debian/ squeeze main contrib non-free

deb http://security.debian.org/ squeeze/updates main contrib non-free
deb-src http://security.debian.org/ squeeze/updates main contrib non-free

deb http://download.tuxfamily.org/shames/debian-lenny/desktopfx/unstable/ ./

deb http://ansani.it/debian/ testing contrib

deb http://ftp.uni-kl.de/debian-multimedia/ testing main
deb-src http://ftp.uni-kl.de/debian-multimedia/ stable main

I then proceeded to execute

`aptitude update`
`aptitude full-upgrade`

Then it did the usual stuff of resolving the conflicts and the resulting 
solution seemed fine to me. I accepted it and it started installing. All was 
going fine, until I started to notice that a lot of xserver-xorg packages were 
being left unconfigured. All seemed to fail because xserver-xorg-core was not 
configured yet, which in turn failed because a udev related package was not 
configured yet. Aptitude then died with the message that there were too many 
errors to proceed.

It looks to me as if aptitude is executing the configuration step in the wrong 
order. Clearly, it should configure udev first, then xorg-core and then the 
xorg driver packages. Am I missing something here, might it have something to 
do with my particular makeup of the sources.list file? I'm a bit lost, and I 
would like to upgrade to Squeeze without resorting to a full clean install.

In the end I managed to restore a backup image I made moments before, so I 
didn't lose anything.


signature.asc
Description: Digital signature

Re: Re: East Asian fonts in Lenny

[Nima Azarbayjany]

Thanks for your support.  Installing unifonts did it well for me. ;)

Nima


--
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/4beb0b28.3060...@gmail.com

Lenny - GNOME FTP Connect To Server

[Tomas Kral]

Dear All,

I mounted an FTP site using GNOME Connect To Server.
But I cannot PUT any files over FTP to host.
It says: Error "Bad File Handle" while copying.
However I can GET files over FTP from host alright.

On Etch it works both ways, GET and PUT, only on Lenny I have got these
errors.

Would anyone see why?
Many thanks.

-- 
Tomas Kral 

Re: Fwd: Re: Kde 3.5 ...

[deloptes]

Sjoerd Hardeman wrote:

>> - ALL kde apps like kplayer/organizer and probably others start very
>> slowly about 20-30secs to pop up
> I really think you need to create a new profile. I am not seeing any of
> this, having a kweather applet constantly on my desk, tried kmoon and
> booting kde apps usually <2 sec.

I've installed with debootstrap and tested with a fresh created profile.

however I'll try removing the .kde4 directory and start over. It's possible
that some things were not completely installed and configured when I logged
in for the first time.

regards


-- 
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/hsev7b$dv...@dough.gmane.org

Re: Fwd: Re: Kde 3.5 ...

[Mike Bird]

On Wed May 12 2010 11:47:27 Dotan Cohen wrote:
> On 12 May 2010 13:21, deloptes  wrote:
> > - ALL kde apps like kplayer/organizer and probably others start very
> > slowly about 20-30secs to pop up
>
> I think that you have something borked in your install.

Are you testing in Squeeze or Sid or something else?

--Mike Bird


-- 
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/201005121212.33363.mgb-deb...@yosemite.net

Re: Fwd: Re: Kde 3.5 ...

[Dotan Cohen]

On 12 May 2010 13:21, deloptes  wrote:
> What I am missing now is also the old behavior from CTRL+ALT+DEL to get
> prompt for reboot or shutdown - or whatever. Now this combination is
> locking the screen. Was it adopted from newer windows?
>

No, that still works on my 4.4 system.


>> Thanks. It will stay unusable for you until you tell us what you need
>> to use it! That's what I'm here for.
>>
>
> Well,
> - kplayer was not working for DVB input.

That I can't test, sorry. No hardware.


> - korganizer does not start
> - kweather and kmoon are not visible (can not choose to activate), though it
> states it's installed.
>

Did you add them to the panel, as widgets?


> - ALL kde apps like kplayer/organizer and probably others start very slowly
> about 20-30secs to pop up
>

I think that you have something borked in your install.


> I'm sorry but I can not test anything that fast. it will take few weeks.
>

I'll be here. At that time you might want to start a new thread and
please CC me.



-- 
Dotan Cohen

http://bido.com
http://what-is-what.com


-- 
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/aanlktiljza6og_ixzbj4me4i_0txcigqbvvmsx7to...@mail.gmail.com

Re: Different ways of creating a USB-install stick

[VR]

Does anyone know where debian keeps the boot.img.gz files
necessary for creating the stick?






By going to www.debian.org, clicking getting debian, scrolling down to 
"Tiny CDs, floppy disks, USB sticks, etc" then selecting your 
architecture, then clicking hd-media.


E.g. 
http://ftp.nl.debian.org/debian/dists/lenny/main/installer-i386/current/images/hd-media/



--
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/4beae92b.2070...@iotk.net

Lenny - GNOME FTP Connect To Server

[Tomas Kral]

Dear List,

I mounted an FTP site using GNOME Connect To Server.
But I cannot PUT any files over FTP to host.
It says: Error "Bad File Handle" while copying.
However I can GET files over FTP from host alright.

On Etch it works both ways, GET and PUT, only on Lenny I have got these
errors.

Would anyone see why?
Many thanks.

-- 
Tomas Kral 

[SOLVED]Re: DVD-Ram

[Curt Howland]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On Wednesday 12 May 2010, Curt Howland was heard to say:
> Anyway, I believe the DVD drive handles DVD-RAM, and this is the
> message I get in the kern.log:
>
> [10357.909024] UDF-fs: No anchor found
> [10357.909032] UDF-fs: No partition found (1)
> [10359.847262] ISOFS: Unable to identify CD-ROM format.

Ok, to continue the saga and change the question, I found the 
following:

http://www.linuxquestions.org/questions/linux-hardware-18/how-can-i-format-a-dvd-ram-501752/

where it is suggested to simply format (and partition, I have assumed) 
the disk in ext2 using the standard tools.

So I did. fdisk for one partition of type 83, then

mke2fs -b 2048 /dev/hdc

which seemed to work just fine.

However, when I put the disk in, the following again came up:

[14455.902724] UDF-fs: No VRS found
[14455.902732] UDF-fs: No partition found (1)
[14455.997756] ISOFS: Unable to identify CD-ROM format.
[14456.246923] UDF-fs: No VRS found
[14456.246930] UDF-fs: No partition found (1)
[14456.341842] ISOFS: Unable to identify CD-ROM format.

Looking in /etc/fstab, I see:

/dev/hdc/media/cdrom0   udf,iso9660 user,noauto 0   0

which may very well be why there are UDF errors and why ext2 won't 
mount. Let's try putting "auto" in there...

/dev/hdc/media/cdrom0   autouser,noauto 0   0

And it worked.

# df
Filesystem   1K-blocks  Used Available Use% Mounted on
...
/dev/hdc   4402628 11284   4167674   1% /media/cdrom0

Adding a file, deleting, both worked just fine treating it as a 
regular disk.

My apologies for bothering the list with something already pretty well 
answered, but my searches had not turned up the information I needed 
when I did the searches the first two times.

I'll also try UDF to see if it's readable on Winders, since who knows 
wtf I'll be needing to mount backups on in several years. I've lost 
too many pictures that were stored on floppies already.

Thank you for your time,

Curt-

- -- 
Those who torment us for our own good will torment us without end,
for they do so with the approval of their consciences.
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (GNU/Linux)

iQEVAwUBS+riHi9Y35yItIgBAQJ3Hgf/ax53utQ7b4Wpe7BS2oQ9g5E/lg2+27F+
ltnpBNQdBg+28a/QZe8lcfLXFexu9ueQ/S6kAS61MgykezdbmYuwcri5guUD0tBL
JKl1o9irpbQUbNGfjRzSQcw3QOgkF634bxUZPW40aRHgr9KF63o44GyF+By+FrNG
b4omGFZUlo6OLJFXl1FLKW054mJqts5nDsKrgkWO7dRih4fVp9n6Tg5G5jm1SY6r
Z9Vi5vgCXk/3CeGpZ6G20+FmdMS85yQFO2o3r1Jegl9eI/CvsI6We6mk3ZtxAkgC
MVQybRfMt9kPJUu7ZCkuyEbDZXR3drfntlILF//UR8R3knxRTlgTcw==
=/QFG
-END PGP SIGNATURE-


-- 
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/201005121315.10654.howl...@priss.com

Re: only output the nth line

[Hugo Vanwoerkom]

Jozsi Vadkan wrote:

I have a file:






And i want to only output the first, second, and fourth line to another
file.

The:

sed -n '1,2p;4p' file.txt



h...@debian:~$ sed -n '1,2p;4p' file.txt
daemon
1):
0

ii  sed4.1.5-8The GNU sed stream editor

Hugo


--
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/hseoac$iq...@dough.gmane.org

Re: only output the nth line

[Tzafrir Cohen]

On Wed, May 12, 2010 at 06:58:57PM +0200, Jozsi Vadkan wrote:
> I have a file:

[snip]

> And i want to only output the first, second, and fourth line to another
> file.
> 
> The:
> 
> sed -n '1,2p;4p' file.txt
> 
> doesn't work.
> 
> What magic do i need for it? :D
> 
> Thanks..:\

Works just fine here:

$ nl /etc/fstab | sed -n '1,2p;4p'
 1  # /etc/fstab: static file system information.
 2  #
 4  proc/proc   procdefaults0
0
$ nl /etc/fstab | busybox sed -n '1,2p;4p'
 1  # /etc/fstab: static file system information.
 2  #
 4  proc/proc   procdefaults0
0


So please give some more details about your system (version of Debian,
version of sed, etc.). Also please tell us what actually happens when
you try to run it.

-- 
Tzafrir Cohen | tzaf...@jabber.org | VIM is
http://tzafrir.org.il || a Mutt's
tzaf...@cohens.org.il ||  best
tzaf...@debian.org|| friend


-- 
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/20100512171549.gu16...@pear.tzafrir.org.il

Re: only output the nth line

[Mike Bird]

On Wed May 12 2010 09:58:57 Jozsi Vadkan wrote:
> sed -n '1,2p;4p' file.txt
>
> doesn't work.

Works for me in Lenny.  What output do you see?  What version
of sed do you have?

--Mike Bird


-- 
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/201005121011.44506.mgb-deb...@yosemite.net

Re: only output the nth line

[Aioanei Rares]

Cross-posting ain't nice, Jozsi...


--
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/4beae142.7050...@gmail.com

only output the nth line

[Jozsi Vadkan]

I have a file:

cat file.txt
daemon
1):
596
0
0
1
0
0
bin
2):
12
0
0
1
0
0
sys
3):
0
0
0
0
0
0



And i want to only output the first, second, and fourth line to another
file.

The:

sed -n '1,2p;4p' file.txt

doesn't work.

What magic do i need for it? :D

Thanks..:\


-- 
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/1273683537.12667.32.ca...@localhost

Re: Replace hardware without reinstall debian lenny

[Stefan Monnier]

> You could use UUID's instead of device names (/dev/sdX) to get around
> this issue.

Oh right, there's this as well.  If you use LVM (can't think of any
reason not to), then it's a non-issue since your volumes are
all labelled.


Stefan


-- 
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/jwvmxw52hev.fsf-monnier+gmane.linux.debian.u...@gnu.org

Re: Switching from NV to Nouveau in Squeeze

[Anand Sivaram]

On Wed, May 12, 2010 at 19:40, Snood  wrote:

> On 05/12/2010 08:08 AM, Mark Allums wrote:
>
>> On 5/12/2010 6:49 AM, Snood wrote:
>>
>>  I'm looking forward to seeing if nouveau will be an improvement,
>>> performance-wise, without causing reliability issues.
>>>
>>> I am, however, going to wait and install nouveau the easy way, once the
>>> upgrade to xserver-xorg-core becomes available in the repository. If
>>> this weren't my main system I might be tempted to experiment, but I just
>>> need this thing to keep working.
>>>
>>
>>
>> People running non-stable (even squeeze) are going to run into problems
>> now and then. It's an unavoidable certainty. nouveau is, well, new.
>> There are going to be problems with it.
>>
>
> Of course. But the problems I had with Gnome and Xfce on this system
> occurred not only in Squeeze, but also when running an Ubuntu LTS version
> and Debian Stable. I only saw those problems when using the restricted / glx
> drivers. Never with nv or vesa. I think this is, perhaps, more a measure of
> the card itself than the drivers. But I know a number of people with "high
> end" graphics cards from nvidia who have reported the same sorts of issues
> that I saw. It doesn't really matter much as these particular systems are no
> longer used as graphics workstations. As they've aged we stuck Linux on them
> and use them as admin workhorses, a job for which they are admirably suited
> because of all of the screen real estate.
>
>
>  Regarding reliability of video drivers: Running many different things,
>> hardware- and driver-wise, over time, I have learned that
>> dpkg-reconfigure is your friend, especially
>>
>> dpkg-reconfigure linux-image-2.6.32-5
>>
>> which regenerates the initrd.img. (I needed this recently. Substitute
>> the package name of your kernel.) Occasionally very helpful, that, when
>> troubleshooting drivers.
>>
>
> Yes. In my earlier experiences I would just wipe the drive and start over
> when I suspected that hangovers from previous experiments with drivers were
> getting in the way of new configurations. But after I became comfortable
> with a few different methods of installation and initial configuration I
> started paying attention to things like dpkg-reconfigure and debconf-show.
>
>
>
> --
> 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/4beab6c8.2070...@comcast.net
>
>

I installed xserver-xorg-core-nouveau (1:0.0.15+git20100329+7858345-3) of
squeze.  My video card is an inbuilt one.
00:0d.0 VGA compatible controller: nVidia Corporation C61 [GeForce 7025 /
nForce 630a] (rev a2)
But after switching xorg.conf to use "nouveau", there was error saying that
no video device found.
Finally I followed.
http://nouveau.freedesktop.org/wiki/InstallNouveau
Compiled both drm and xf86-video-nouveau and replaced both libdrm and
/usr/lib/xorg/modules/drivers/nouveau_drv.so
Now it is working fine.

Re: DVD-Ram

[Boyd Stephen Smith Jr.]

On Wednesday 12 May 2010 10:53:27 Boyd Stephen Smith Jr. wrote:
> On Wednesday 12 May 2010 10:21:53 Curt Howland wrote:
> > Anyway, I believe the DVD drive handles DVD-RAM, and this is the
> > message I get in the kern.log:
> >
> > [10357.909024] UDF-fs: No anchor found
> > [10357.909032] UDF-fs: No partition found (1)
> > [10359.847262] ISOFS: Unable to identify CD-ROM format.
> 
> Sounds like you need to create a filesystem on it.  I think normally,
>  you'll want to use UDF for a DVD-RAM.  Package udftools, binary mkudffs
>  should do something like that.  The pktsetup binary might also be useful,
>  but I'm not sure.

You can use UDF, if you want, but you can also use any file system you want 
based on OS compatibility and speed, as long as it can handle the 2k sectors 
size.

"pktsetup" is for when you want to use a normal CD-R/DVD-R as a read/write UDF 
file system.
-- 
Boyd Stephen Smith Jr.   ,= ,-_-. =.
b...@iguanasuicide.net  ((_/)o o(\_))
ICQ: 514984 YM/AIM: DaTwinkDaddy `-'(. .)`-'
http://iguanasuicide.net/\_/


signature.asc
Description: This is a digitally signed message part.

Re: DVD-Ram

[Boyd Stephen Smith Jr.]

On Wednesday 12 May 2010 10:21:53 Curt Howland wrote:
> Anyway, I believe the DVD drive handles DVD-RAM, and this is the
> message I get in the kern.log:
> 
> [10357.909024] UDF-fs: No anchor found
> [10357.909032] UDF-fs: No partition found (1)
> [10359.847262] ISOFS: Unable to identify CD-ROM format.

Sounds like you need to create a filesystem on it.  I think normally, you'll 
want to use UDF for a DVD-RAM.  Package udftools, binary mkudffs should do 
something like that.  The pktsetup binary might also be useful, but I'm not 
sure.
-- 
Boyd Stephen Smith Jr.   ,= ,-_-. =.
b...@iguanasuicide.net  ((_/)o o(\_))
ICQ: 514984 YM/AIM: DaTwinkDaddy `-'(. .)`-'
http://iguanasuicide.net/\_/


signature.asc
Description: This is a digitally signed message part.

DVD-Ram

[Curt Howland]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Hi. I have been interested in trying DVD-RAM due to its 30 year 
shelf-life and supposed "ease of use" of just being mounted like a 
regular disk without having to use CD or DVD writing software.

Anyway, I believe the DVD drive handles DVD-RAM, and this is the 
message I get in the kern.log:

[10357.909024] UDF-fs: No anchor found
[10357.909032] UDF-fs: No partition found (1)
[10359.847262] ISOFS: Unable to identify CD-ROM format.

When I look in K3b's media information, it correctly identifies a 
DVD-RAM 4.3GB with nothing written to it.

But it won't mount, and I am going to assume that it's because there 
is no file system. Do I need to partition/format like a HD, or use 
K3b and format like a DVD-RW?

Or, sad to say, is the above error indicative of a drive that can't 
handle DVD-RAM?
- -- 
Those who torment us for our own good will torment us without end,
for they do so with the approval of their consciences.
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (GNU/Linux)

iQEVAwUBS+rHkS9Y35yItIgBAQK35Af/QdG4AdTQFxGYpqciW9tL5gDcXTIAvj4r
3ZBb/kuG55TGSMlWC/93m3/OLIKl93DMPfdpdIpCwCBHDutz9gnDeyMbnHQCmV01
9rrCNETyMFfrxMecaLxQ8mFWxQGHuO0mzpVL6RQQDq7Njr1vYJnwz9FUSoTcaVE9
B3LKlKpfNkSymVrBBOwisSAtxvJ7hl7PH3NEZLBpNcwCdq376cF4jQKkq+0LR9qB
sa2Y88bkvv1526BFIoC9aacKyiwH9wEehtHeJlVPCMoN0GWAD5MX8k1kgmnuJfWa
z/DT5f0BOR/L3YF9t4ukZgx9KemYIQHBztRpeNLV0RiBa+BHqBuECw==
=zoxr
-END PGP SIGNATURE-


-- 
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/201005121121.58209.howl...@priss.com

Figured it out: Re: What happened to 'permissions.rules?' [Re: Why does /dev/rtc0 belong to group audio in Lenny but not in Sid?]

[Rick Thomas]

I figured it out myself...

Most of the /etc/udev/rules.d/*.rules files seem to have moved to /lib  
in Sid.


Sorry for the noise...

Rick


On May 12, 2010, at 10:43 AM, Rick Thomas wrote:



Thanks, that answers the immediate question.

Which rises the larger question...

Sid does not seem to have anything that corresponds to Lenny's /etc/ 
udev/rules.d/*permissions.rules


Any idea why?  Any idea what has replaced it.


Rick

On May 12, 2010, at 4:32 AM, Sven Joachim wrote:


On 2010-05-12 10:06 +0200, Rick Thomas wrote:


In Lenny, "ls -ld /dev/audio" gives


lenny:~$ ls -ld /dev/rtc0
crw-rw 1 root audio 254, 0 May  2 15:25 /dev/rtc0


Ugh.  This is not really desirable.


But in Sid, it gives


sid:~$ ls -ld /dev/rtc0
crw-rw 1 root root 254, 0 May 10 23:51 /dev/rtc0



Anybody know why?


,[ /usr/share/doc/udev/changelog.Debian.gz ]
| udev (0.140-1) unstable; urgency=low
| [...]
|   * permissions.rules: removed rtc group audio.
| [...]
|  -- Marco d'Itri   Mon, 23 Mar 2009 13:16:50 +0100
`

HTH,
  Sven





--
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/866694a4-d26d-452a-ac33-b94ac7644...@pobox.com

Re: What happened to 'permissions.rules?' [Re: Why does /dev/rtc0 belong to group audio in Lenny but not in Sid?]

[Sven Joachim]

On 2010-05-12 16:43 +0200, Rick Thomas wrote:

> Sid does not seem to have anything that corresponds to Lenny's /etc/
> udev/rules.d/*permissions.rules
>
> Any idea why?  Any idea what has replaced it.

Read /usr/share/doc/udev/NEWS.Debian.gz.

Sven


-- 
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/87hbmdw3rj@turtle.gmx.de

Re: Re (3): Re^n: Grub vs. linux-image-2.6.32 conundrum

[Stephen Powell]

On Tue, 11 May 2010 19:29:39 -0400 (EDT), Peter Easthope wrote:
> Stephen Powell wrote:
>>  ...
>> "if it ain't broke, don't fix it"
>>  ...
>> I don't understand what problem you are trying to solve.
> 
> But it is broke!
> In one sense, the primary problem is failure of X.
> 
> dalton:/home/peter# uname -rv
> 2.6.30-2-686 #1 SMP Sat Sep 26 01:16:22 UTC 2009
> dalton:/home/peter# startx 
>...
> (EE) open /dev/fb0: No such file or directory
> SELinux: Disabled on system, not enabling X server
> 
> waiting for X server to shut down ...
> 
> dalton:/home/peter#

This problem is totally unrelated to which boot loader you use.

> 
> A later kernel might fix the /dev/fb0 problem but 
> currently the kernel update fails when update-initramfs 
> invokes update-grub.  
> 
> So these options come to mind.
> * Wait for grub-pc to be fixed, put it back onto the 
>   NetVista, get the latest kernel and sooner or later 
>   get a working /dev/fb0.
> * Fix the update-initramfs script so that it works with lilo.
>   That will allow kernel updating.
> * Compile a custom kernel so that a ramfs is not required.
>   Again the kernel can be updated.
> * Reinstall Lenny and wait for grub-pc to be fixed 
>   before reinstalling Squeeze.
> 
> The first option is quickest, provided it works.
> 
> Thanks to anyone with a helpful idea, ... Peter E.

Your kernel installation environment is not configured correctly for
use with lilo.  That's why you are having trouble upgrading to
a newer kernel.  Assuming that you are using only stock kernel images,
here is what you should do:

(1) Login as root.

(2) Create a file called /usr/sbin/lilo-update.  It should look like
this:

   #!/bin/sh
   # 
   # This script is referenced by /etc/kernel-img.conf.
   #
   lilo >&2

(3) Mark the file executable

   chmod +x /usr/sbin/lilo-update

(4) Edit the file /etc/kernel-img.conf.  When you're done editing,
it should look like this:

   # Kernel image management overrides
   # See kernel-img.conf(5) for details
   do_symlinks = yes
   relative_links = yes
   do_bootloader = yes
   do_bootfloppy = no
   do_initrd = yes
   link_in_boot = yes
   postinst_hook = lilo-update
   postrm_hook = lilo-update

(5) Check the / directory for symlinks.  If they are found, remove them

   rm /vmlinuz
   rm /initrd.img
   rm /vmlinuz.old
   rm /initrd.img.old

(6) Check the /boot directory for symlinks.  If they are not there, add them.

   cd /boot
   ln -s vmlinuz-2.6.30-2-686 vmlinuz
   ln -s initrd.img-2.6.30-2-686 initrd.img

(I am assuming here that 2.6.30-2-686 is the only installed kernel.)

(7) Edit /etc/lilo.conf.  Make sure that the /boot directory appears in all
of the symlinks.  For example,

   # /etc/lilo.conf
   # 
   # global options
   #
   append="acpi=off notsc clocksource=pit"
   boot=/dev/hda
   compact
   default=Linux
   delay=40
   install=text
   large-memory
   lba32
   root=/dev/hda1
   read-only
   vga=normal
   #
   # per-image options
   #
   image=/boot/vmlinuz
label=Linux
initrd=/boot/initrd.img
   #
   image=/boot/vmlinuz.old
label=LinuxOld
initrd=/boot/initrd.img.old
optional

Note the "image" and "initrd" lines (total of four).  They specify a symlink
in the /boot directory.

Now install your new kernel.  It should install just fine.  I don't know if the
new kernel will fix the X problem you are having, but that has nothing to do
with which bootloader you use.  As long as you use only stock kernel images
and no custom-compiled kernel images, this should work just fine.

-- 
  .''`. Stephen Powell
 : :'  :
 `. `'`
   `-


-- 
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/1874972669.67550.1273676721208.javamail.r...@md01.wow.synacor.com

What happened to 'permissions.rules?' [Re: Why does /dev/rtc0 belong to group audio in Lenny but not in Sid?]

[Rick Thomas]

Thanks, that answers the immediate question.

Which rises the larger question...

Sid does not seem to have anything that corresponds to Lenny's /etc/ 
udev/rules.d/*permissions.rules


Any idea why?  Any idea what has replaced it.


Rick

On May 12, 2010, at 4:32 AM, Sven Joachim wrote:


On 2010-05-12 10:06 +0200, Rick Thomas wrote:


In Lenny, "ls -ld /dev/audio" gives


lenny:~$ ls -ld /dev/rtc0
crw-rw 1 root audio 254, 0 May  2 15:25 /dev/rtc0


Ugh.  This is not really desirable.


But in Sid, it gives


sid:~$ ls -ld /dev/rtc0
crw-rw 1 root root 254, 0 May 10 23:51 /dev/rtc0



Anybody know why?


,[ /usr/share/doc/udev/changelog.Debian.gz ]
| udev (0.140-1) unstable; urgency=low
| [...]
|   * permissions.rules: removed rtc group audio.
| [...]
|  -- Marco d'Itri   Mon, 23 Mar 2009 13:16:50 +0100
`

HTH,
   Sven



--
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/186e2964-480c-4281-9b22-472ecd103...@pobox.com

Re: Different ways of creating a USB-install stick

[James Stuckey]

2010/5/12 James Stuckey 

>
>
> 2010/4/26 Γιώργος Πάλλας 
>
> James Stuckey wrote:
>>
>>> Hello,
>>>
>>> I'm curious as to the different ways one can create a USB install stick,
>>> for the purpose of installing Debian.
>>>
>>> It is possible to do it by
>>> a) acquiring (where?) a boot.img.gz file, and then doing "zcat
>>> boot.img.gz > /dev/sdc". Then load a netboot iso to the disc.
>>> b) making a FAT/FAT32 partition on the stick, and then doing "syslinux
>>> /dev/sdXX", copying vmlinuz and initrd.gz to the stick
>>> c) using Unetbootin with an .iso file
>>>
>>> I like the way Unetbootin allows one to use a larger .iso (dvd, or full
>>> cd iso). The downside of a) and b) is that you can only use the smaller
>>> netboot .isos, and if I wanted to load a few more files onto the disc for
>>> use I wouldn't have the room to do so.
>>>
>>> Does anyone know another method? I'm particularly interested in knowing
>>> the way to do what Unetbootin does manually, so that I could load a cd/dvd
>>> iso onto the stick after making it boot-able.
>>>
>>> Regards,
>>> James
>>>
>>
>> About c), I know that ubuntu can work that way, but has failed in the past
>> with debian, because the debian installer believes it runs from a cd and
>> tries to find the packages to be installed from the host's cdrom. I dont
>> know if something has changed recently.
>>
>> Giorgos
>>
>


> Does anyone know where debian keeps the boot.img.gz files necessary for
>> creating the stick?
>>
>

NVIDIA drivers for cards that aren't supported in stable [was: Aptitude Error]

[James Stuckey]

This command seemed to work the best. The others just generated a list of
what seemed like all packages installed.

stuc...@debian:~$ apt-show-versions | grep sid
flightgear/sid uptodate 1.9.1-1.1
libnfsidmap2/squeeze uptodate 0.23-2
libresid-builder-dev/squeeze uptodate 2.1.1-8
libresid-builder0c2a/squeeze uptodate 2.1.1-8
libsidplay1/squeeze uptodate 1.36.59-5
libsidplay2/squeeze uptodate 2.1.1-8
libsidplay2-dev/squeeze uptodate 2.1.1-8
libsidutils-dev/squeeze uptodate 2.1.1-8
libsidutils0/squeeze uptodate 2.1.1-8
netbeans-ide/sid uptodate 6.0.1+dfsg-3
netbeans-platform/sid uptodate 6.0.1+dfsg-3
nvidia-glx/sid upgradeable from 190.53-4 to 195.36.24-1
nvidia-kernel-source/sid upgradeable from 190.53-4 to 195.36.24-1
nvidia-vdpau-driver/sid upgradeable from 190.53-4 to 195.36.24-1
simgear1.9.1/sid uptodate 1.9.1-2

So just for clarification, the *proper* way of running nvidia drivers for
any card that isn't supported in stable on debian as of right now is:

a) install squeeze, since it's easier than doing it from testing
b) echo 'APT::Default-Release "testing";' >> /etc/apt/apt.conf
c) edit sources.list to include sid lines
d) apt-get -t sid install [some nvidia package?]
e) m-a a-i nvidia

+ take notice of the instructions on the wiki [
http://wiki.debian.org/NvidiaGraphicsDrivers].

Thereafter the user should note that if he tries to install 'foo' and 'foo'
isn't in testing, he will get 'foo' from sid, if 'foo' is in sid, along with
the necessary dependencies of 'foo' from sid if he does "apt-get install
foo".

*There's information about this in 2.7.2 of the DR [
http://www.debian.org/doc/manuals/debian-reference/ch02.en.html#_packages_from_mixed_source_of_archives]
that I may not have understood fully.

Re: Switching from NV to Nouveau in Squeeze

[Snood]

On 05/12/2010 08:08 AM, Mark Allums wrote:

On 5/12/2010 6:49 AM, Snood wrote:


I'm looking forward to seeing if nouveau will be an improvement,
performance-wise, without causing reliability issues.

I am, however, going to wait and install nouveau the easy way, once the
upgrade to xserver-xorg-core becomes available in the repository. If
this weren't my main system I might be tempted to experiment, but I just
need this thing to keep working.



People running non-stable (even squeeze) are going to run into problems
now and then. It's an unavoidable certainty. nouveau is, well, new.
There are going to be problems with it.


Of course. But the problems I had with Gnome and Xfce on this system 
occurred not only in Squeeze, but also when running an Ubuntu LTS 
version and Debian Stable. I only saw those problems when using the 
restricted / glx drivers. Never with nv or vesa. I think this is, 
perhaps, more a measure of the card itself than the drivers. But I know 
a number of people with "high end" graphics cards from nvidia who have 
reported the same sorts of issues that I saw. It doesn't really matter 
much as these particular systems are no longer used as graphics 
workstations. As they've aged we stuck Linux on them and use them as 
admin workhorses, a job for which they are admirably suited because of 
all of the screen real estate.



Regarding reliability of video drivers: Running many different things,
hardware- and driver-wise, over time, I have learned that
dpkg-reconfigure is your friend, especially

dpkg-reconfigure linux-image-2.6.32-5

which regenerates the initrd.img. (I needed this recently. Substitute
the package name of your kernel.) Occasionally very helpful, that, when
troubleshooting drivers.


Yes. In my earlier experiences I would just wipe the drive and start 
over when I suspected that hangovers from previous experiments with 
drivers were getting in the way of new configurations. But after I 
became comfortable with a few different methods of installation and 
initial configuration I started paying attention to things like 
dpkg-reconfigure and debconf-show.



--
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/4beab6c8.2070...@comcast.net

aptitude update thinks there are no updates! (solved by deleting apt/lists)

[Abhishek Dasgupta]

Hi all,

After about a fortnight, I tried to update my Debian squeeze desktop,
and I was using the mirror.cse.iitk.ac.in mirror. After downloading
the repository lists, it tells me there are no updates -- I am
surprised as I know that Gnome 2.30 is already in testing. Thinking
that it could be a problem with the mirror, I switch to
ftp.ch.debian.org and update. This time, it does say there are about
300 updates.

I issue a safe-upgrade, but the electricity goes out just as the
updates begin downloading. After I turn the computer back on, issuing
a safe-upgrade shows there are no updates! I try to aptitude update
but it thinks that the repositories are already updated, though
apt-cache show nautilus gives the version 2.28.4. As I was in a hurry
at the time, I just deleted /var/lib/apt/lists, so aptitude had no
choice but to really download the lists. After this the safe-upgrade
proceeded as usual. I realised after deleting /var/lib/apt/lists that
I should have kept a copy, but too late.

Though the problem is (in a sense) solved, I am curious as to how this
(bug?) could have occurred. After all this I checked
mirror.cse.iitk.ac.in  and it does have nautilus 2.30.1, so maybe the
first no-updates scenario was also caused by this bug/problem.

Abhishek
--
Please cc me as I am not subscribed to debian-user.


-- 
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/aanlktinkeqchqnw2ja6zije7g9eslap37wjjb3yfu...@mail.gmail.com

Re: Switching from NV to Nouveau in Squeeze

[Mark Allums]

On 5/12/2010 6:49 AM, Snood wrote:


I'm looking forward to seeing if nouveau will be an improvement,
performance-wise, without causing reliability issues.

I am, however, going to wait and install nouveau the easy way, once the
upgrade to xserver-xorg-core becomes available in the repository. If
this weren't my main system I might be tempted to experiment, but I just
need this thing to keep working.



People running non-stable (even squeeze) are going to run into problems 
now and then.  It's an unavoidable certainty.  nouveau is, well, new. 
There are going to be problems with it.


Regarding reliability of video drivers:  Running many different things, 
hardware- and driver-wise, over time, I have learned that 
dpkg-reconfigure is your friend, especially


dpkg-reconfigure linux-image-2.6.32-5

which regenerates the initrd.img.  (I needed this recently.  Substitute 
the package name of your kernel.)  Occasionally very helpful, that, when 
troubleshooting drivers.


MAA



--
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/4bea9a3a.6090...@allums.com

Re: Switching from NV to Nouveau in Squeeze

[Snood]

On 05/11/2010 09:43 PM, Charles Kroeger wrote:

Saw that xserver-xorg-video-nouveau package is now in the main
repository.


It does not appear to be in Sid or Squeeze as of this afternoon. (EST USA)
yes. However, I notice that 'nv' is still in Squeeze-main contrib non-free:

xserver-xorg-video-nv  1:2.1.17-2


Sorry. I'm not thinking or communicating well. I'm using the vesa driver 
on the system, not nv. My brain was tracking back to an earlier 
experiment in which I was using other repositories. I use only main and 
security for Squeeze.


However, I have been showing xserver-xorg-video-nouveau in Squeeze main 
for a couple of days.



but nv appears to be 'broken' if used in the /etc/X11/xorg.conf file, on my
version of things. Perhaps this is the result of some Debian religious
fanatics, but I think it's time to bid adeau to nv, alas it served me well.

I installed nouveau:

xserver-xorg-video-nouveau  1:0.0.15+git20100329+7858345-3 X.Org X
server -- Nouveau display driver (experimental)

and placed it, instead, into the /etc/X11/xorg.conf file and lo it brought
forth an X session and looked just like nv. But, nv and nouveau are,
no pun intended, a bit two dimensional when one still has available the
nvidia-glx Xorg driver one should simply use it if one's hardware will comply.


Too rich for my blood. By that I mean that nvidia-glx with this Quadro 
card has caused all sorts of odd breakages and unreliability issues in 
the DE. I have done enough experimenting with identical configurations 
of Xfce and Gnome on this system, with the only difference being use of 
different video drivers (vesa, nv, glx/restricted) under both Ubuntu and 
Debian to know that it's not my imagination. I'd rather have a reliable 
system than 3D, so glx is a no go for me. The vesa driver has been 
absolutely flawless, but quite slow, of course. The slowness has been 
worth it because absolutely nothing in the user interface has ever been 
broken since I went to vesa. I don't game, and I've just learned to be 
patient when switching workspaces.


;)

I'm looking forward to seeing if nouveau will be an improvement, 
performance-wise, without causing reliability issues.


I am, however, going to wait and install nouveau the easy way, once the 
upgrade to xserver-xorg-core becomes available in the repository. If 
this weren't my main system I might be tempted to experiment, but I just 
need this thing to keep working.



--
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/4bea95b5.2080...@comcast.net

Re: Fwd: Re: Kde 3.5 ...

[Sjoerd Hardeman]

deloptes schreef:

I forgot to mention that the keyboard froze after pressing ALT+F2 and
switching language settings

Please, please comment on this bug:
https://bugs.kde.org/show_bug.cgi?id=205369

The problem is that it was not iresponsive for just 10secs but forever.


I see. Does that happen often, or only that once?


For now it has happened twice ... it could be that I have
installed/configured something after logging in the first time. 


What is happening permanently is that if I click the logout button the whole
desktop freezes. I have to press CTRL+ALT+F[1-6] to restart kdm
That's strange. Try to play with kdm options, and by creating a new 
profile (move your .kde). It might be that a program refuses to shut 
down and is causing the trouble

What I am missing now is also the old behavior from CTRL+ALT+DEL to get
prompt for reboot or shutdown - or whatever. Now this combination is
locking the screen. Was it adopted from newer windows?

This is a change in xorg. A google gives you lots of hits, eg:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=539762



Thanks. It will stay unusable for you until you tell us what you need
to use it! That's what I'm here for.



Well, 
- kplayer was not working for DVB input.

- korganizer does not start
- kweather and kmoon are not visible (can not choose to activate), though it
states it's installed.

- ALL kde apps like kplayer/organizer and probably others start very slowly
about 20-30secs to pop up
I really think you need to create a new profile. I am not seeing any of 
this, having a kweather applet constantly on my desk, tried kmoon and 
booting kde apps usually <2 sec.


Sjoerd



signature.asc
Description: OpenPGP digital signature

Re: Trying to get a kernel patch included in Squeeze

[deloptes]

Andrei Popescu wrote:

> 
> Unless I'm doing something terribly wrong, at this point I'm assuming
> that the patch will not apply to 2.6.32, but I have no ideea how
> difficult it would be to backport it. Comments?
> 

if you are not supporting multiple systems that need this patch you can
download and compile the kernel from kernel.org

The kernel patches are applied to the main line in this case to 2.6.33 by
the way (if you are using the patch from kernel.org.

regards


-- 
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/hsdvta$fb...@dough.gmane.org

Re: Fwd: Re: Kde 3.5 ...

[deloptes]

Dotan Cohen wrote:

> On 11 May 2010 23:02, deloptes  wrote:
 - weather
>>>
>>
http://kde-look.org/content/show.php/yaWP+%28Yet+Another+Weather+Plasmoid%29?content=94106
>>
>> This was not working in 4.3 and I couldn't start it in 4.4.
>>
> 
> Interesting, it works on the Ubuntu box I test KDE on.
> 
> 
 - korganizer
>>>
>>> Check!
>>
>> it took at least 10min to start
>>
> 
> Wow. Any console output?
> 
> 
 - infrared control
>>>
>>> How did you do this in KDE 3?
>>
>> with klirc and lircd and modifying the kernel key map for my cinergy xxs
>> dvbt card ;-)
>>
>> a big challenge was to setup the kde keys ... it's not very developed,
>> but the basic functionality works
>>
> 
> Please, your input is needed here:
> https://bugs.kde.org/show_bug.cgi?id=197885
> 
> 
>>> i   plasma-widget-kbstate                                          - A
>>> plasma widget that shows the state of the modifier keys
>>
>> In kde3 the "idiots" didn't think of us poor people not using latin and
>> associated per default ALT+K to switch the keymap. Now if you switch from
>> english to rushian/bulgarian or whatever ALT+K gives a completely
>> different keycode ... So I had to always change this.
>>
>> Now in kde4 it's even better. You have to click ... and no reasonable
>> language switching combination is working. In this point Windows wins, as
>> it's per default configured to switch languages when typing
>> (left)ALT+SHIFT
>>
> 
> I switch between languages with the Capslock key.
> עובד גם בעברית!‏
> Работает тоже по Русский!
> 
> 
 - screen management (xrandr interface)
>>>
>>> Yes, built into System Settings.
>>
>> yes but not working for me and everybody running i915 vga card. this is
>> also related to X-Server and the a**holes from intel. (don't judge me the
>> notebook was given to me from the company I'm working for :-( )
>>
> 
> I don't think that's a KDE issue, though.

no but it's definitely an issue if you can not arrange your displays.

> 
> 
>>> http://kde-apps.org/content/show.php/Krypt?content=80641
>>
>> the question is if it is compiling in kde4? and also if it is working
>> well
>>
> 
> It's not a core or even supported app, I think. It's a third-party
> app. I really can't help with that.

yes, I know. I'll check ... I have about  10 application to recompile.

> 
> 
 I forgot to mention that the keyboard froze after pressing ALT+F2 and
 switching language settings
>>>
>>> Please, please comment on this bug:
>>> https://bugs.kde.org/show_bug.cgi?id=205369
>>
>> The problem is that it was not iresponsive for just 10secs but forever.
>>
> 
> I see. Does that happen often, or only that once?

For now it has happened twice ... it could be that I have
installed/configured something after logging in the first time. 

What is happening permanently is that if I click the logout button the whole
desktop freezes. I have to press CTRL+ALT+F[1-6] to restart kdm

What I am missing now is also the old behavior from CTRL+ALT+DEL to get
prompt for reboot or shutdown - or whatever. Now this combination is
locking the screen. Was it adopted from newer windows?

>>
> 
> Thanks. It will stay unusable for you until you tell us what you need
> to use it! That's what I'm here for.
> 

Well, 
- kplayer was not working for DVB input.
- korganizer does not start
- kweather and kmoon are not visible (can not choose to activate), though it
states it's installed.

- ALL kde apps like kplayer/organizer and probably others start very slowly
about 20-30secs to pop up


I'm sorry but I can not test anything that fast. it will take few weeks.

I will probably test upgrading (As I said) from lenny to squeeze to sid. To
simulate an upgrade of my current system. I think this is more important.
This will take a while, so my plan for now is to see what basically works
and what not.

regards


-- 
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/hsdvg7$dp...@dough.gmane.org

Re: Automounting problems.

[Chris Bannister]

On Tue, May 11, 2010 at 10:54:47PM -0700, Marc Shapiro wrote:
> I am now slapping myself on the head for being so STUPID!  Automount is 
> working just fine, and has been all along.  Automount does its thing as 
> soon as a device is ACCESSED, not plugged in.  I was plugging the flash 
> drives in and looking in /mnt to see if they were showing up.  The 
> weren't.  The weren't supposed to, either.  As soon as I executed "ls 
> /mnt/lexar" lo and behold, there was the listing and everything was 
> working just fine.
> 
> I think I'll slap myself on the head, again.

Not so fast! :) How are you supposed to access them if you don't know
what they will be labelled as?

What does "ls /mnt/" do?

Are you supposed to carry round a scrap of paper with the mount labels
written down?

-- 
Chris.


-- 
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/20100512095518.gc18...@fischer

Trying to get a kernel patch included in Squeeze

[Andrei Popescu]

Hello Debian Users,

A regression introduced in kernel 2.6.30, where the beeps produced by 
the BIOS on power chord removal are disabled[1] was recently fixed for 
2.6.33 which AFAIK will *not* be in Squeeze.

I'm trying to get this issue fixed for Squeeze, but, since I'm aware 
that the Debian kernel team doesn't have a lot of time, it would be very 
nice to be able to just provide a bug report with the patch to apply.

Since my laptop is one of the affected models I tried to test the patch 
provided for 2.6.33[2], following the "rebuild official kernel" 
how-to[3], but the patch doesn't seem to apply:

- if I follow the guideline and just drop it under 
  debian/patches/bugfixes/all and add the relevant 5+beep.1 series file 
  the patch seems to be ignored (no mention in the output of
  'make -f debian/rules source-all')
- if I try to apply it manually it failes:

a...@think:linux-2.6-2.6.32$ patch -p0 < 
debian/patches/bugfix/all/thinkpad-beep.patch 
patching file b/sound/pci/hda/patch_analog.c
Hunk #1 FAILED at 71.
Hunk #2 FAILED at 165.
Hunk #3 FAILED at 203.
Hunk #4 FAILED at 3482.
Hunk #5 FAILED at 3523.
Hunk #6 FAILED at 3655.
6 out of 6 hunks FAILED -- saving rejects to file 
b/sound/pci/hda/patch_analog.c.rej

Unless I'm doing something terribly wrong, at this point I'm assuming 
that the patch will not apply to 2.6.32, but I have no ideea how 
difficult it would be to backport it. Comments?

This issue is not a showstopper for me as I can just use the 2.6.29 
kernel or wait for a fixed 2.6.33 in experimental (and unstable after 
the release), but it seems worthwhile to have it fixed for squeeze.

[1] 
https://sourceforge.net/mailarchive/forum.php?thread_name=4BAE0730.8020509%40gmail.com&forum_name=alsa-user
[2] 
https://sourceforge.net/mailarchive/message.php?msg_name=alpine.LNX.2.00.1003261047210.3925%40eeebox2.perex-int.cz
[3] http://wiki.debian.org/HowToRebuildAnOfficialDebianKernelPackage

Regards,
Andrei
-- 
http://nuvreauspam.ro/2010/05/4-neticheta-pe-mail/


signature.asc
Description: Digital signature

Re: Why does /dev/rtc0 belong to group audio in Lenny but not in Sid?

[Sven Joachim]

On 2010-05-12 10:06 +0200, Rick Thomas wrote:

> In Lenny, "ls -ld /dev/audio" gives
>
>> lenny:~$ ls -ld /dev/rtc0
>> crw-rw 1 root audio 254, 0 May  2 15:25 /dev/rtc0

Ugh.  This is not really desirable.

> But in Sid, it gives
>
>> sid:~$ ls -ld /dev/rtc0
>> crw-rw 1 root root 254, 0 May 10 23:51 /dev/rtc0
>>
>
> Anybody know why?

,[ /usr/share/doc/udev/changelog.Debian.gz ]
| udev (0.140-1) unstable; urgency=low
| [...] 
|   * permissions.rules: removed rtc group audio.
| [...]
|  -- Marco d'Itri   Mon, 23 Mar 2009 13:16:50 +0100
`

HTH,
Sven


-- 
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/87ljbp7c5y@turtle.gmx.de

Why does /dev/rtc0 belong to group audio in Lenny but not in Sid?

[Rick Thomas]

In Lenny, "ls -ld /dev/audio" gives


lenny:~$ ls -ld /dev/rtc0
crw-rw 1 root audio 254, 0 May  2 15:25 /dev/rtc0




But in Sid, it gives


sid:~$ ls -ld /dev/rtc0
crw-rw 1 root root 254, 0 May 10 23:51 /dev/rtc0



Anybody know why?

Thanks!

Rick


--
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/ac045fbc-f572-4d9e-967b-67660214a...@cs.rutgers.edu

Re: Laptop can't resume from suspend mode

[Matteo Riva]

2010/5/11 Johan Grönqvist :
> 2010-05-10 18:12, Matteo Riva skrev:
>>
>> Using Xorg 7.5 with radeonhd FOSS driver.
>>
>> Anybody had this problem and/or knows about a solution?
>>
>
> I have not had the problem (I use the radeon driver), and do not know of a
> solution, but wanted to point you to a recent changelog that might be of
> interest.
>
> (from
> )
>
> 
>  Debian Changelog xorg (1:7.5+6)
>
> xorg (1:7.5+6) unstable; urgency=medium
>
>   * Drop radeonhd from xserver-xorg-video-all.  We switched to kernel
>     modesetting for radeon, and that clashes with this driver.
>   [...]
>  -- Julien Cristau   Fri, 07 May 2010 13:34:32 +0200
>
> -

Hm that's not the problem as I have version 1:7.5+5 (testing)


--
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/aanlktimv2szrh-s6todhnsopmcggtjnuwyoec98jo...@mail.gmail.com