Re: [OT] Hard Drive Energy Not Worth Conserving drives?

[Andrew McGlashan]

Hi,

Stefan Monnier wrote:

Read the ATA and SCSI specifications.  Or ask on either mailing list.
In short, the drive presents its LBA addressing based on 512B sectors.
The kernel can't choose to ignore that--it's stuck with it.  Since the
drive is presenting LBA based on 512B sectors, there is no way the
kernel can address LBA based on 4K sectors.



http://www.h-online.com/open/features/Kernel-Log-Coming-in-2-6-37-Part-3-Network-and-storage-hardware-1153025.html


Storage - The H Open Source: News and Features

Numerous changes to the network and storage code are to increase 
processing speed and improve the system's hardware support. Among the 
new additions are a PPTP stack, various drivers for Wi-Fi hardware by 
Atheros, Broadcom and Realtek, and code for hard disks with a logical 
sector size of 4 Kbytes




Now, when will stable release have a 2.6.37 kernel?  And are all those 
changes "non-free" -- so to be included in "supported" versions of Debian?


--
Kind Regards
AndrewM

Andrew McGlashan
Broadband Solutions now including VoIP


--
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/4d32a2c1.8000...@affinityvision.com.au

Re: OT: Output from date command - my little backup script

[Bob Proulx]

Adrian Levi wrote:
> Is the output from the date command a string or integer wrt date +%w?

The date command only produces string output.  %w produces one of the
characters 0, 1, 2, 3, 4, 5, 6.

> I'm trying to test a condition in my backup script where i want to
> match on day of week = 0
> 
> The program flow I am trying to achieve is" If the file exists and the
> day of the week is 0 then remove the file and set the day of the week
> to 0, otherwise set the day of the week to 0(perform Level 0 backup)".
>
> From man test i have 2 possibilities that i'm aware of, $backuplevel
> -eq 0 and $backuplevel = 0

In the shell -eq is a numeric comparison and = is a string
comparison.  Sometimes that makes no difference.  Sometimes that is a
critically important difference.  Although current shells will
complain if it isn't a number.

  00 -eq 0
  00 != 0
  02 -eq 2
  02 != 2

> if [ -f "$incrementalfile" ]
>   then
> backuplevel=`date +%w`
> if [ $backuplevel -eq 0]

You are missing a space after the 0 and before the ] and I am hoping
that is simply an email glitch.  But you must have a space there.

if [ $backuplevel -eq 0 ]

>   then
> rm "$incrementalfile" > /dev/null 2>&1

Redirecting the errors to /dev/null is bad.  Because you have
redirected the errors to /dev/null this may be unable to delete the
file, throwing an error, and you won't get the error.  Since you know
the file was there because of the -f test above it I think you should
just try to remove it, and not use rm -f either.

rm "$incrementalfile"

> fi
>   else
> backuplevel=0
> fi

Is there a question in there?

> I have also tried if [ $backuplevel = 0 ]

Sure.  String comparison should work okay there.

> But neither seems to match, that is to say that the incremental file
> does not get deleted so it continues to do an 'other than 0 level
> backup.

Run the script with sh -x and see what commands are traced.

  sh -x ./myscript

Use echo to print out lines in question.

  echo "DEBUG: if [ $backuplevel -eq 0 ]"
  if [ $backuplevel -eq 0 ]

  echo "DEBUG: Removing with: rm -f $backuplevel"
  rm -f $backuplevel

You can use the command line to try things.

  $ test 0 -eq 0 && echo yes || echo no
  yes
  $ test 0 = 0 && echo yes || echo no
  yes

  $ test 00 -eq 0 && echo yes || echo no
  yes
  $ test 00 = 0 && echo yes || echo no
  no

> The command echo $backuplevel returns 0 but I don't know if it is an
> integer or a string, or is it both?

The shell is only working with strings.  It doesn't become a number
until it is forced into an integer comparison such as [ 0 -eq 0 ].

> According to [1] Bash variables are untyped

They are untyped because they are all strings.

> but I don't know why neither of them match and delete my file.

I don't see a problem (other than the missing space) but by using such
techniques as above you should be able to find it.  If it is the
missing space then you should have seen this error:

  $ [ 0 -eq 0]
  [: 1: missing `]'

So I assume it is a typo in your cut-n-paste.

Bob


signature.asc
Description: Digital signature

OT: Output from date command - my little backup script

[Adrian Levi]

Is the output from the date command a string or integer wrt date +%w?

I'm trying to test a condition in my backup script where i want to
match on day of week = 0

The program flow I am trying to achieve is" If the file exists and the
day of the week is 0 then remove the file and set the day of the week
to 0, otherwise set the day of the week to 0(perform Level 0 backup)".

>From man test i have 2 possibilities that i'm aware of, $backuplevel
-eq 0 and $backuplevel = 0

if [ -f "$incrementalfile" ]
  then
backuplevel=`date +%w`
if [ $backuplevel -eq 0]
  then
rm "$incrementalfile" > /dev/null 2>&1
fi
  else
backuplevel=0
fi

I have also tried if [ $backuplevel = 0 ]

But neither seems to match, that is to say that the incremental file
does not get deleted so it continues to do an 'other than 0 level
backup.
The command echo $backuplevel returns 0 but I don't know if it is an
integer or a string, or is it both?
According to [1] Bash variables are untyped but I don't know why
neither of them match and delete my file.
Severely confused,

Adrian

[1] http://tldp.org/LDP/abs/html/untyped.html
-- 
24x7x365 != 24x7x52 Stupid or bad maths?
 hm. I've lost a machine.. literally _lost_. it responds to
ping, it works completely, I just can't figure out where in my
apartment it is.


-- 
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/AANLkTikwd_ZVKn3-LjjM=nu31RCHgz9yk9hs60v=q...@mail.gmail.com

Re: [OT] Hard Drive Energy Not Worth Conserving drives?

[Stefan Monnier]

> Read the ATA and SCSI specifications.  Or ask on either mailing list.
> In short, the drive presents its LBA addressing based on 512B sectors.
> The kernel can't choose to ignore that--it's stuck with it.  Since the
> drive is presenting LBA based on 512B sectors, there is no way the
> kernel can address LBA based on 4K sectors.

I don't follow: what prevents the kernel from telling the higher-up
tools that the drive uses 4KB sectors (or 72KB sectors for that matter)?

>> In any case, the issue is probably not really in the kernel but in the
>> filesystems and partitioning tools: all that's really needed to use the

> The current "problem" with the hybrid drives is that the partitioning
> utilities don't automatically align partitions on the underlying 4k
> sector boundaries.

I'm glad we agree.

>> Indeed, and for that reason 4KB physical blocks wouldn't cause
>> additional disk space usage.
> The space savings with 4KB sectors has nothing to do with file systems
> or user data.

I was talking about the space usage increase incurred from the use of
≥4KB blocks in the FS, if we assume that the FS uses the underlying HD
block size as a lower-limit of its own block size.

> This is the ONLY reason these 4KB sector drives were developed:  more
> actual end user space on the drive.

That's a different topic, but an interesting one as well: the gain seems
small (e.g. WD has/had two Green 2TB drives, one using 4KB sectors and
the other using good'ol 512B sectors, and this using apparently the
same underlying head/drive technology, so it seems the gain, if any, was
too small to make it to the end user).
So why does WD do 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/jwvr5cds7ch.fsf-monnier+gmane.linux.debian.u...@gnu.org

HD manufacturers and Free Software (was: [SOLVED] Is squeeze compatible with WD20EARS and other 2TB drives?)

[Stefan Monnier]

> "MUST READ: Western Digital is unable to provide support for the
> Unix/Linux operating systems outside of jumper configurations (for
> EIDE hard drives) and physical installation support."

While I never expect any OS-specific support from hard-drive suppliers,
I find it offensive for a manufacturer to explicitly single out the OS
I use, indeed.
So, to get back to Debian, I wonder which manufacturers are more friendly
to Free Software (e.g. provides tools to update their drives's firmware
from systems like Debian).


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

Re: [SOLVED] Is squeeze compatible with WD20EARS and other 2TB drives?

[Stefan Monnier]

>> > I'm down on these drives due to the maniacal 8 second head park
>> > interval, which likely does more mechanical damage than it saves power
>> > in dollar terms.
>> There is simply no concrete evidence to back this urban legend.
> In the WD20EARS I purchased this was in no way just a legend -- be it  
> urban or rural or otherwise.

I'd be really surprised if you had evidence that your drive failed
because of mechanical damage due to aggressive head-park.

And if your drive failed while still young, well that happens to the
best of the drives, and is no evidence that those drives fail more often
than others and even less that if they do it's due to the aggressive
head-park.


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

Re: [really solved] Re: aptitude: set all packages auto-installed except given list?

[Andrei Popescu]

On Du, 16 ian 11, 01:00:50, Javier Barroso wrote:
> When you invoke aptitude unmarkauto ... aptitude has all your packages
> with auto mark, so aptitude will want to delete these unused packages
> *before* it start with your operation (unmarkauto in this case). I
> think it make sense

Well, '(un)mark' seems to be doing more than just (un)marking packages 
which is a bit counter-intuitive to me...

Regards,
Andrei
-- 
Offtopic discussions among Debian users and developers:
http://lists.alioth.debian.org/mailman/listinfo/d-community-offtopic


signature.asc
Description: Digital signature

Re: changing grub boot order

[briand]

On Sun, 16 Jan 2011 01:36:07 +0200
Andrei Popescu  wrote:

> On Sb, 15 ian 11, 14:55:08, bri...@aracnet.com wrote:
> > as per the wiki
> > 
> > I change the default in /etc/default/grub from 0 to 4.
> > 
> > I ran update-grub.
> > 
> > The same entry boots by default, i.e. it didn't work.
> > 
> > Anyone know why ?
> 
> Please post the outputs of 'grep default= /boot/grub/grub.cfg' and
> 'grep GRUB_DEFAULT /etc/default/grub'.
> 

GRUB_DEFAULT=4
set default="4"


Brian


-- 
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/20110115162417.747e0...@bamboo.deldotd.com

Re: [really solved] Re: aptitude: set all packages auto-installed except given list?

[Javier Barroso]

On Sat, Jan 15, 2011 at 9:41 PM, Andrei Popescu
 wrote:
> On Sb, 15 ian 11, 19:42:26, Andrei Popescu wrote:
>>
>> Actually this only helps cleaning the system of unneeded packages, but
>> still leaves me with a lot of packages not marked auto, so I had to
>> apply Javier's hack after all.
>
> Ok, this looks like the best version so far:
>
> Backup:
> aptitude --disable-columns -F %p search '~i!~M' > $PKG_LIST
> (in case you're wondering, my list currently has 177 packages)
>
> Restore (as root):
> aptitude -o Aptitude::Delete-Unused=false markauto ~i
> aptitude -o Aptitude::Delete-Unused=false unmarkauto $(cat $PKG_LIST | tr 
> "\n" " ")
> aptitude keep-all
>
> I still don't understand why 'Delete-Unused=false' is necessary with
> 'unmarkauto' and an additional 'keep-all' is needed, but at least it
> works.
When you invoke aptitude unmarkauto ... aptitude has all your packages
with auto mark, so aptitude will want to delete these unused packages
*before* it start with your operation (unmarkauto in this case). I
think it make sense

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

Re: Grub2 reinstall on raid1 system.

[Henrique de Moraes Holschuh]

On Sat, 15 Jan 2011, Tom H wrote:
> On Sat, Jan 15, 2011 at 9:06 AM, Henrique de Moraes Holschuh
>  wrote:
> > On Sat, 15 Jan 2011, Jack Schneider wrote:
> >> > >> You might want to try configuring grub and fstab to use UUID's
> >> > >> instead of /dev/mdX.  That removes the possibility that the kernel
> >> > >> will change the mdX designations.
> >> > >>
> >> > >> Use blkid to find out the UUID's of your partitions.
> >
> > Whatever you do, NEVER use the UUIDs of partitions, use the UUID of the
> > md devices.  The worst failure scenario involving MD and idiotic tools
> > is for a tool to cause a component device to be mounted instead of the
> > MD array.
> >
> > This is one of the reasons why the new MD formats that offset the data
> > inside the component devices exists.
> 
> If you want to use an md device's UUID in grub.cfg, you're going to
> have to edit it by hand or edit the grub2 scripts. AFAIK, they'll only
> use the md device names because they're unique (through their UUIDs).

You must either use /dev/md* or the MD device UUID.  Anything else is going
to bite you back, hard.

There really isn't a reason to use UUIDs with MD.  The md devices will _not_
move around, especially not when kernel autostart is non-operational (and it
is not operational in any Debian kernel).  But some initrd scripts will keep
pestering you until you do switch to UUIDs everywhere.  Annoying, that.

OTOH, you will learn very fast to never ever forget to update
/etc/mdadm/mdadm.conf AND the initrds when you touch the md arrays...

-- 
  "One disk to rule them all, One disk to find them. One disk to bring
  them all and in the darkness grind them. In the Land of Redmond
  where the shadows lie." -- The Silicon Valley Tarot
  Henrique Holschuh


-- 
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/20110116000103.ga20...@khazad-dum.debian.net

Re: Grub2 reinstall on raid1 system.

[Bob Proulx]

Jack Schneider wrote:
> Bob Proulx wrote:
> > Jack Schneider wrote:
> > > I have a raid1 based W/S running Debian Squeeze uptodate. (was
> > > until ~7 days ago) There are 4 drives, 2 of which had never been
> > > used or formatted. I configured a new array using Disk Utility from
> > > a live Ubuntu CD. That's where I screwed up... The end result was
> > > the names of the arrays were changed on the working 2 drives.
> > > IE: /dev/md0 to /dev/126 and /dev/md1 became md127.
> > 
> > Something else must have happened too.  Because normally just adding
> > arrays will not rename the existing arrays.  I am not familiar with
> > the "Disk Utility" that you mention.
>
> Hi, Bob 
> Thanks for your encouraging advice...

I believe you should be able to completely recover from the current
problems.  But it may be tedious and not completely trivial.  You will
just have to work through it.

Now that there is more information available, and knowing that you are
using software raid and lvm, let me guess.  You added another physical
extent (a new /dev/md2 partition) to the root volume group?  If so
that is a common problem.  I have hit it myself on a number of
occasions.  You need to update the mdadm.conf file and rebuild the
initrd.  I will say more details about it as I go here in this message.

> As I mentioned in a prior post,Grub was leaving me at a Grub rescue>prompt.  
> 
> I followed this procedure:
> http://www.gnu.org/software/grub/manual/html_node/GRUB-only-offers-a-rescue-shell.html#GRUB-only-offers-a-rescue-shell

That seems reasonable.  It talks about how to drive the grub boot
prompt to manually set up the boot.

But you were talking about using a disk utility from a live cd to
configure a new array with two new drives and that is where I was
thinking that you had been modifying the arrays.  It sounded like it
anyway.

Gosh it would be a lot easier if we could just pop in for a quick peek
at the system in person.  But we will just have to make do with the
correspondence course.  :-)

> Booting now leaves me at a busy box: However the Grub menu is correct.
> With the correct kernels. So it appears that grub is now finding the
> root/boot partitions and files. 

That sounds good.  Hopefully not too bad off then.

> > Next time instead you might just use mdadm directly.  It really is
> > quite easy to create new arrays using it.  Here is an example that
> > will create a new device /dev/md9 mirrored from two other devices
> > /dev/sdy5 and /dev/sdz5.
> > 
> >   mdadm --create /dev/md9 --level=mirror
> > --raid-devices=2 /dev/sdy5 /dev/sdz5
> > 
> > > Strangely the md2 array which I setup on the added drives remains as
> > > /dev/md2. My root partition is/was on /dev/md0. The result is that
> > > Grub2 fails to boot the / array.

> This is how I created /dev/md2.

Then that explains why it didn't change.  Probably the HOMEHOST
parameter is involved on the ones that changed.  Using mdadm from the
command line doesn't set that parameter.

There was just a long discussion about this topic just recently.
You might want to jump into it in the middle here and read our
learnings with HOMEHOST.

  http://lists.debian.org/debian-user/2010/12/msg01105.html

> mdadm --examine /dev/sda1 & /dev/sda2  gives I think a clean result 
> I have posted the output at : http://pastebin.com/pHpKjgK3

That looks good to me.  And healthy and normal.  Looks good to me for
that part.

But that is only the first partition.  That is just /dev/md0.  Do you
have any information on the other partitions?

You can look at /proc/partitions to get a list of all of the
partitions that the kernel knows about.

  cat /proc/partitions

Then you can poke at the other ones too.  But it looks like the
filesystems are there okay.

> mdadm --detail /dev/md0 --> gives  mdadm: md device /dev/md0 does not
> appear to be active. 
> 
> There is no /proc/mdstat  data output.  

So it looks like the raid data is there on the disks but that the
multidevice (md) module is not starting up in the kernel.  Because it
isn't starting then there aren't any /dev/md* devices and no status
output in /proc/mdstat.

> > I would boot a rescue image and then inspect the current configuration
> > using the above commands.  Hopefully that will show something wrong
> > that can be fixed after you know what it is.

I still think this is the best course of action for you.  Boot a
rescue disk into the system and then go from there.  Do you have a
Debian install disk #1 or Debian netinst or other installation disk?
Any of those will have a rescue system that should boot your system
okay.  The Debian rescue disk will automatically search for raid
partitions and automatically start the md modules.

> So it appears that I must rebuild my arrays.

I think your arrays might be fine.  More information is needed.

You said your boot partition was /dev/md0.  I assume that your root
partition was /dev/md1?  Then you added two new disks as /dev/md2?

  /dev/md0   /dev/sda1  /dev/sdc1

Let 

Re: Grub2 reinstall on raid1 system.

[Tom H]

On Sat, Jan 15, 2011 at 5:29 PM, Jack Schneider  wrote:
> On Fri, 14 Jan 2011 05:25:45 -0700
> Bob Proulx  wrote:
>> Jack Schneider wrote:
>> >
>> > I have a raid1 based W/S running Debian Squeeze uptodate. (was
>> > until ~7 days ago) There are 4 drives, 2 of which had never been
>> > used or formatted. I configured a new array using Disk Utility from
>> > a live Ubuntu CD. That's where I screwed up... The end result was
>> > the names of the arrays were changed on the working 2 drives.
>> > IE: /dev/md0 to /dev/126 and /dev/md1 became md127.
>>
>> Something else must have happened too.  Because normally just adding
>> arrays will not rename the existing arrays.  I am not familiar with
>> the "Disk Utility" that you mention.
>
> As I mentioned in a prior post,Grub was leaving me at a Grub rescue>prompt.
>
> I followed this procedure:
> http://www.gnu.org/software/grub/manual/html_node/GRUB-only-offers-a-rescue-shell.html#GRUB-only-offers-a-rescue-shell
> Booting now leaves me at a busy box: However the Grub menu is correct.
> With the correct kernels. So it appears that grub is now finding the
> root/boot partitions and files.

Assemble the arrays at the busybox/initramfs prompt with
"--update=super-minor" in order to update the minor.


>> You can inspect the raid partitions with --detail and --examine.
>>
>>   mdadm --examine /dev/sda1
>>   mdadm --detail /dev/md0
>
> mdadm --examine /dev/sda1 & /dev/sda2  gives I think a clean result
> I have posted the output at : http://pastebin.com/pHpKjgK3
> mdadm --detail /dev/md0 --> gives  mdadm: md device /dev/md0 does not
> appear to be active.
>
> There is no /proc/mdstat data output.

How about "mdadm --detail /dev/md125" given that
http://pastebin.com/pHpKjgK3 shows that sda1 and sdc1 have 125 as
their minor.


--
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/AANLkTi=et-gpncsaxuxqegkss7sprl8zj8zuhcwnl...@mail.gmail.com

Re: Grub2 reinstall on raid1 system.

[Tom H]

On Sat, Jan 15, 2011 at 9:06 AM, Henrique de Moraes Holschuh
 wrote:
> On Sat, 15 Jan 2011, Jack Schneider wrote:
>> > >> You might want to try configuring grub and fstab to use UUID's
>> > >> instead of /dev/mdX.  That removes the possibility that the kernel
>> > >> will change the mdX designations.
>> > >>
>> > >> Use blkid to find out the UUID's of your partitions.
>
> Whatever you do, NEVER use the UUIDs of partitions, use the UUID of the
> md devices.  The worst failure scenario involving MD and idiotic tools
> is for a tool to cause a component device to be mounted instead of the
> MD array.
>
> This is one of the reasons why the new MD formats that offset the data
> inside the component devices exists.

If you want to use an md device's UUID in grub.cfg, you're going to
have to edit it by hand or edit the grub2 scripts. AFAIK, they'll only
use the md device names because they're unique (through their UUIDs).


--
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/aanlktinblbrvvh-2avsog49zejzepunc7nmnvvubs...@mail.gmail.com

Re: Grub2 reinstall on raid1 system.

[Tom H]

On Sat, Jan 15, 2011 at 8:24 AM, Jack Schneider  wrote:
> On Fri, 14 Jan 2011 12:16:37 -0500
> Tom H  wrote:
>> >> >
> [BIG SNIP]
>
>> >> You might want to try configuring grub and fstab to use UUID's
>> >> instead of /dev/mdX.  That removes the possibility that the kernel
>> >> will change the mdX designations.
>> >>
>> >> Use blkid to find out the UUID's of your partitions.
>> >
>> > Thanks for the reply, Rob. What grub file do I change?
>> > grub.cfg?  grub *.map? I seem to have UUIDs for both disks and
>> > LVM partitions, change both?
>>
>> So you have LVM over RAID, not just RAID.
>
> Well, not really, not all of the disks are LVM2. The first two
> disks raid1 /dev/sda & /dev/sdc are partitioned with 1 small
> /(root) partition, /dev/md0 -> 10 gigs. The balance of the disk
> is /dev/md1 under LVM2 with seven logical volumes. /home,/var,/swap
> etc  The next two disks sdb and sdd are raid1 as /dev/md2 which I
> need to use as an extension of the LVM.

So you don't need to have any lvm reference in grub.cfg.


> More info, when I boot the machine, I see the "GRUB loading. WELCOME to
> GRUB!" info.  Then it enters the rescue mode with a "grub rescue>"
> prompt.  So the kernel is found/finding the / partition. Right?

For "grub rescue", check out
http://www.gnu.org/software/grub/manual/grub.html#GRUB-only-offers-a-rescue-shell


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

Re: changing grub boot order

[Andrei Popescu]

On Sb, 15 ian 11, 14:55:08, bri...@aracnet.com wrote:
> as per the wiki
> 
> I change the default in /etc/default/grub from 0 to 4.
> 
> I ran update-grub.
> 
> The same entry boots by default, i.e. it didn't work.
> 
> Anyone know why ?

Please post the outputs of 'grep default= /boot/grub/grub.cfg' and
'grep GRUB_DEFAULT /etc/default/grub'.

Regards,
Andrei
-- 
Offtopic discussions among Debian users and developers:
http://lists.alioth.debian.org/mailman/listinfo/d-community-offtopic


signature.asc
Description: Digital signature

changing grub boot order

[briand]

as per the wiki

I change the default in /etc/default/grub from 0 to 4.

I ran update-grub.

The same entry boots by default, i.e. it didn't work.

Anyone know why ?

Brian

For reference:

Configuring grub v2

The configuration file is /boot/grub/grub.cfg, but you shouldn't edit
it directly. This file is generated by grub v2's update-grub(8), based
on:

   1.

  The script snippets in /etc/grub.d/
   2.

  The configuration file /etc/default/grub 

To configure grub "v2", you should edit /etc/default/grub, then run
update-grub. Advanced configuration are achieved by modifying the
snippets in /etc/grub.d/. 


-- 
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/20110115145508.28f11...@bamboo.deldotd.com

Re: Grub2 reinstall on raid1 system.

[Jack Schneider]

On Fri, 14 Jan 2011 05:25:45 -0700
Bob Proulx  wrote:

> Jack Schneider wrote:
> > I have a raid1 based W/S running Debian Squeeze uptodate. (was
> > until ~7 days ago) There are 4 drives, 2 of which had never been
> > used or formatted. I configured a new array using Disk Utility from
> > a live Ubuntu CD. That's where I screwed up... The end result was
> > the names of the arrays were changed on the working 2 drives.
> > IE: /dev/md0 to /dev/126 and /dev/md1 became md127.
> 
> Something else must have happened too.  Because normally just adding
> arrays will not rename the existing arrays.  I am not familiar with
> the "Disk Utility" that you mention.
> 
Hi, Bob 
Thanks for your encouraging advice...

As I mentioned in a prior post,Grub was leaving me at a Grub rescue>prompt.  

I followed this procedure:
http://www.gnu.org/software/grub/manual/html_node/GRUB-only-offers-a-rescue-shell.html#GRUB-only-offers-a-rescue-shell
Booting now leaves me at a busy box: However the Grub menu is correct.
With the correct kernels. So it appears that grub is now finding the
root/boot partitions and files. 
> Next time instead you might just use mdadm directly.  It really is
> quite easy to create new arrays using it.  Here is an example that
> will create a new device /dev/md9 mirrored from two other devices
> /dev/sdy5 and /dev/sdz5.
> 
>   mdadm --create /dev/md9 --level=mirror
> --raid-devices=2 /dev/sdy5 /dev/sdz5
> 
> > Strangely the md2 array which I setup on the added drives remains as
> > /dev/md2. My root partition is/was on /dev/md0. The result is that
> > Grub2 fails to boot the / array.
> 
> You may have to boot a rescue cd.  I recommend booting the Debian
> install disk in rescue mode.  Then you can inspect and fix the
> problem.  But as of yet you haven't said enough to let us know what
> the problem might be yet.
> 
> > I have tried three REINSTALLING GRUB procedures from Sysresccd
> > online docs and many others GNU.org, Ubuntu etc.
> 
> This isn't encouraging.  I can tell that you are grasping at straws.
> You have my sympathy.  But unfortunately that doesn't help diagnose
> the problem.  Remain calm.  And repeat exactly the problem that you
> are seeing and the steps you have taken to correct it.
> 
> > The errors occur when I try to mount the partition with the /boot
> > directory. 'Complains about file system type 'linux_raid_member'
> 
> I haven't seen that error before.  Maybe someone else will recognize
> it.
> 
> I don't understand why you would get an error mounting /boot that
> would prevent the system from coming online.  Because by the time the
> system has booted enough to mount /boot it has already practically
> booted completely.  The system doesn't actually need /boot mounted to
> boot.  Grub reads the files from /boot and sets things in motion and
> then /etc/fstab instructs the system to mount /boot.
> 
> Usually when the root device cannot be assembled the error I see is
> that the system is "Waiting for root filesystem" and can eventually
> get to a recovery shell prompt.
> 
> > This machine has worked for 3 years flawlessly.. Can anyone help
> > with this? Or point me to a place or link to get this fixed. Google
> > doesn't help... I can't find a article/posting where it ended
> > successfully.  I have considered a full reinstall after Squeeze goes
> > stable, since this O/S is a crufty upgrade from sarge over time. But
> > useless now..
> 
> The partitions for raid volumes should be 'autodetect' 0xFD.  This
> will enable mdadm to assemble then into raid at boot time.
> 
> You can inspect the raid partitions with --detail and --examine.
> 
>   mdadm --examine /dev/sda1
>   mdadm --detail /dev/md0
> 

mdadm --examine /dev/sda1 & /dev/sda2  gives I think a clean result 
I have posted the output at : http://pastebin.com/pHpKjgK3
mdadm --detail /dev/md0 --> gives  mdadm: md device /dev/md0 does not
appear to be active. 

There is no /proc/mdstat  data output.  

> That will list information about the devices.  Replace with your own
> series of devices.
> 
> I would boot a rescue image and then inspect the current configuration
> using the above commands.  Hopefully that will show something wrong
> that can be fixed after you know what it is.
> 
> A couple of other hints: If you are not booting a rescue system but
> using something like a live boot then you may need to load the kernel
> modules manually.  You may need to load the dm_mod and md_mod modules.
> 
>   modprobe md_mod
> 
> You might get useful information from looking at the /proc/mdstat
> status.


> 
>   cat /proc/mdstat
> 
> There is a configuration file /etc/mdadm/mdadm.conf that holds the
> UUIDs of the configured devices.  If those have become corrupted then
> mdadm won't be able to assemble the /dev/md* devices.  Check that file
> and compare against what you see with the --detail output.
> 
> The initrd contains a copy of the mdadm.conf file with the components
> needed to assemble the root filesystem.  If the UUIDs ch

Re: blancing conections

[Bob Proulx]

Jesus arteche wrote:
> I have a web application that I want to scale in a cluster like Amazon EC2.
> I have a load balancer and behind several web server (Apache2). My question
> is:
> 
> How can I make for the session that is iniciated in webserver 1...will be
> available in webserver 2 cause the load balancer maybe can send the
> conection some times from 1 to 2 or viceversa.

One idea.  Store the session in a cookie (like Rails default cookie
store) so that it is provided by the client with every http request.
There are good things and bad things about using cookie based sessions
however.

One idea.  Store the session in a database that is shared between all
of the web application servers.  There are good things and bad things
about using database based sessions however.

Bob


signature.asc
Description: Digital signature

Re: stardict dictionary packages.

[Freeman]

On Sat, Jan 15, 2011 at 01:15:11PM -0800, evenso wrote:
> On Sat, Jan 15, 2011 at 07:52:01PM +, Camaleón wrote:
> > On Sun, 16 Jan 2011 01:50:39 +0700, Sthu Deus wrote:
> > 
> > > Good day.
> > 
> > It's late afternoon here :-P
> >  
> > > Are in Debian the packages holding dictionaries capable to work w/
> > > stardict?
> > > 
> > > I see plenty of dictionaries for dict use, for example, but not for
> > > stardict. Or it is almost unusable program in Debian repo - as the
> > > interface program w/o the dictionaries seems to me as VCR w/o the tapes.
> > > :)
> > 
> > Aren't "dict-freedict-*-*" packages working with Stardict? (just asking 
> > because I have not tested) :-?
> > 
> > Greetings,
> > 
> 
> I haven't tried it either but that appears to be the stardict recommendation
> as they offer dictd tarballs for installation to /usr/share/stardict/dic
> along with others.
> 
> http://yeelou.com/huzheng/stardict-dic/
> 

The dictd dictionaries on my system don't work but the tarballs of the same
dictionaries from yeelou.com do. I kind of like stardict. Once it is
running, it is as fast as dictd at the command line.

-- 
Regards,
Freeman

"Microsoft is not the answer. Microsoft is the question. NO (or Linux) is the
answer." --Somebody


-- 
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/20110115213651.GA18169@Europa.office

Re: stardict dictionary packages.

[Freeman]

On Sat, Jan 15, 2011 at 07:52:01PM +, Camaleón wrote:
> On Sun, 16 Jan 2011 01:50:39 +0700, Sthu Deus wrote:
> 
> > Good day.
> 
> It's late afternoon here :-P
>  
> > Are in Debian the packages holding dictionaries capable to work w/
> > stardict?
> > 
> > I see plenty of dictionaries for dict use, for example, but not for
> > stardict. Or it is almost unusable program in Debian repo - as the
> > interface program w/o the dictionaries seems to me as VCR w/o the tapes.
> > :)
> 
> Aren't "dict-freedict-*-*" packages working with Stardict? (just asking 
> because I have not tested) :-?
> 
> Greetings,
> 

I haven't tried it either but that appears to be the stardict recommendation
as they offer dictd tarballs for installation to /usr/share/stardict/dic
along with others.

http://yeelou.com/huzheng/stardict-dic/

-- 
Regards,
Freeman

"Microsoft is not the answer. Microsoft is the question. NO (or Linux) is the
answer." --Somebody


-- 
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/20110115211511.GA12565@Europa.office

Re: aptitude: set all packages auto-installed except given list?

[Andrei Popescu]

On Sb, 15 ian 11, 14:31:13, Boyd Stephen Smith Jr. wrote:
 
> (aptitude unmarkauto $(cat pkg.list)) should do what you want, and extra 
> newlines and spaces wouldn't matter even if the file contained them.  

Thanks for the tip, that saves a 'tr' invocation in my solution.

Regards,
Andrei
-- 
Offtopic discussions among Debian users and developers:
http://lists.alioth.debian.org/mailman/listinfo/d-community-offtopic


signature.asc
Description: Digital signature

Re: [really solved] Re: aptitude: set all packages auto-installed except given list?

[Andrei Popescu]

On Sb, 15 ian 11, 19:42:26, Andrei Popescu wrote:
> 
> Actually this only helps cleaning the system of unneeded packages, but 
> still leaves me with a lot of packages not marked auto, so I had to 
> apply Javier's hack after all.

Ok, this looks like the best version so far:

Backup:
aptitude --disable-columns -F %p search '~i!~M' > $PKG_LIST
(in case you're wondering, my list currently has 177 packages)

Restore (as root):
aptitude -o Aptitude::Delete-Unused=false markauto ~i
aptitude -o Aptitude::Delete-Unused=false unmarkauto $(cat $PKG_LIST | tr "\n" 
" ")
aptitude keep-all

I still don't understand why 'Delete-Unused=false' is necessary with 
'unmarkauto' and an additional 'keep-all' is needed, but at least it 
works.

Regards,
Andrei
-- 
Offtopic discussions among Debian users and developers:
http://lists.alioth.debian.org/mailman/listinfo/d-community-offtopic


signature.asc
Description: Digital signature

Re: aptitude: set all packages auto-installed except given list?

[Boyd Stephen Smith Jr.]

In <20110115133957.gi4...@wasteland.homelinux.net>, Jochen Schulz wrote:
>Florian Kulzer:
>> […] Backticks should also work if you want to avoid the $(...)
>> bashism.
>
>That's not a bashism, it's perfectly legal POSIX/SUS.

It's also preferred over backticks since you can't nest backticks AND some 
older shells have "convenient" behavior on input like
"Is it now `date"
that really messes with you if you try and use quotes inside backticks.  Like 
making the following ambiguous:
"Is it now`date +" %F "`, but I wish it was 100 years in the future."
-- 
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: Keyboard freezing/repeating endlessly

[Joe Riel]

On Sat, 15 Jan 2011 20:16:16 + (UTC)
Camaleón  wrote:

> On Sat, 15 Jan 2011 09:55:54 -0800, Joe Riel wrote:
> 
> > On Fri, 14 Jan 2011 07:47:59 -0800 Joe Riel wrote:
> > 
> >> On Fri, 14 Jan 2011 11:38:43 + (UTC) Camaleón wrote:
> >> 
> >> > You can:
> >> > 
> >> > 1/ Start the system with no xorg (console) and leave it so for
> >> > sometine to check if the problem is still present (even with no x
> >> > server).
> >> 
> >> I'll attempt to try this.  Might be painful working in a virtual
> >> terminal all the time.  Kind of limits what I can do.  This is my
> >> work machine...
> > 
> > Got lucky, sort of.  I was just working in a virtual terminal when
> > the lockup occurred.  That doesn't rule out X in that X was running
> > (I had just opened the terminal and was reading a man page),
> > however, it suggests the problem might not be with X.  That is
> > consistent with the observation that restarting gdm3 does not clear
> > the fault.
> 
> Hum... yes, then it can be something related to the kernel.
>  
> >> > 2/ Review you kernel log, just in case ("cat /var/log/kern.log |
> >> > grep input").
> > 
> > Found the following lines (more of same) in kern.log at the time of
> > the lockup.  However, I don't see them for other lockups (a lockup
> > occurred while I was typing this email), so it could be a
> > red-herring:
> > 
> > Jan 15 09:20:58 gauss kernel: [164858.674186] [drm] nouveau
> > :01:00.0: nouveau_channel_free: freeing fifo 2 Jan 15 09:20:59
> > gauss kernel: [164859.749505] [drm] nouveau :01:00.0:
> > nouveau_channel_free: freeing fifo 1 Jan 15 09:20:59 gauss kernel:
> > [164859.750491] [drm] nouveau :01:00.0: PFIFO_CACHE_ERROR - Ch
> > 1/5 Mthd 0x Data 0x8013 Jan 15 09:20:59 gauss kernel:
> > [164859.750507] [drm] nouveau :01:00.0: PGRAPH_ERROR - nSource:
> > DATA_ERROR, nStatus: BAD_ARGUMENT Jan 15 09:20:59 gauss kernel:
> > [164859.750511] [drm] nouveau :01:00.0: PGRAPH_ERROR - Ch 1/5
> > Class 0x008a Mthd 0x0300 Data 0x:0x Jan 15 09:20:59
> > gauss kernel: [164859.750566] [drm] nouveau :01:00.0:
> > PFIFO_CACHE_ERROR - Ch 1/4 Mthd 0x Data 0x801a Jan 15
> > 09:20:59 gauss kernel: [164859.750580] [drm] nouveau :01:00.0:
> > PGRAPH_ERROR - nSource: ILLEGAL_MTHD, nStatus: BAD_ARGUMENT
> > PROTECTION_FAULT
> 
> If X server is not running, where are these logs entries coming from? 
> (nouveau is the X driver for nvidia cards) >;-)

Well, the X server was running.  I was originally in X and switched to
a virtual terminal.  The lockup occurred while I was working in the
virtual terminal.  I searched google for that error message and found
a few related bug reports in other forums.  At least one user was
experiencing very similar behavior (keyboard goes away).  

> > Anyway, the behaviour you are experiencing with the ps/2 keyboard
> > is weird enough to fill a bug in Debian BTS, I would go for it.

I'll do so.


-- 
Joe Riel


--
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/20110115123346.46efebe8@gauss

Re: aptitude: set all packages auto-installed except given list?

[Boyd Stephen Smith Jr.]

In <20110115110130.GC15639@think.homelan>, Andrei Popescu wrote:
>My usual method of 'cleaning' the system was to set all installed
>packages to auto-installed and then mark one by one the ones I need to
>keep.
>
>aptitude --schedule-only markauto ~i
>
>Seems to be doing the first part, but I can't convince aptitude to
>unmark my list (which I processed to not contain unneeded space and
>newlines):
>
>aptitude unmarkauto < pkg.list
>
>has no effect

The redirection operator you've used ('<') opens the named file, and replaces 
file descriptor 0 (stdin), with the descriptor of the just opened file, just 
before running the command.  Aptitude doesn't read packages to operate on from 
stdin, so it's not surprising this didn't have the effect you wanted.

(aptitude unmarkauto $(cat pkg.list)) should do what you want, and extra 
newlines and spaces wouldn't matter even if the file contained them.  
-- 
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.

Squeeze and Logitech, Inc. QuickCam Pro 4000

[Slobodan Aleksić]

Hello List,

I own a Logitech QuickCamPro and it doesn't work with Squeeze, any other 
people who have the same problem or no problem with it ?!


Only thing I found relevant was a closed bug :
http://lists.debian.org/debian-kernel/2010/06/msg00310.html

Greetings!


--
Slobodan


--
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/4d3202b3.7010...@aleksic.de

blancing conections

[Jesus arteche]

hi guys,

I have a web application that I want to scale in a cluster like Amazon EC2.
I have a load balancer and behind several web server (Apache2). My question
is:

How can I make for the session that is iniciated in webserver 1...will be
available in webserver 2 cause the load balancer maybe can send the
conection some times from 1 to 2 or viceversa.


Thanks

Re: Keyboard freezing/repeating endlessly

[Camaleón]

On Sat, 15 Jan 2011 09:55:54 -0800, Joe Riel wrote:

> On Fri, 14 Jan 2011 07:47:59 -0800 Joe Riel wrote:
> 
>> On Fri, 14 Jan 2011 11:38:43 + (UTC) Camaleón wrote:
>> 
>> > You can:
>> > 
>> > 1/ Start the system with no xorg (console) and leave it so for
>> > sometine to check if the problem is still present (even with no x
>> > server).
>> 
>> I'll attempt to try this.  Might be painful working in a virtual
>> terminal all the time.  Kind of limits what I can do.  This is my work
>> machine...
> 
> Got lucky, sort of.  I was just working in a virtual terminal when the
> lockup occurred.  That doesn't rule out X in that X was running (I had
> just opened the terminal and was reading a man page), however, it
> suggests the problem might not be with X.  That is consistent with the
> observation that restarting gdm3 does not clear the fault.

Hum... yes, then it can be something related to the kernel.
 
>> > 2/ Review you kernel log, just in case ("cat /var/log/kern.log | grep
>> > input").
> 
> Found the following lines (more of same) in kern.log at the time of the
> lockup.  However, I don't see them for other lockups (a lockup occurred
> while I was typing this email), so it could be a red-herring:
> 
> Jan 15 09:20:58 gauss kernel: [164858.674186] [drm] nouveau :01:00.0: 
> nouveau_channel_free: freeing fifo 2 
> Jan 15 09:20:59 gauss kernel: [164859.749505] [drm] nouveau :01:00.0: 
> nouveau_channel_free: freeing fifo 1 
> Jan 15 09:20:59 gauss kernel: [164859.750491] [drm] nouveau :01:00.0: 
> PFIFO_CACHE_ERROR - Ch 1/5 Mthd 0x Data 0x8013 
> Jan 15 09:20:59 gauss kernel: [164859.750507] [drm] nouveau :01:00.0: 
> PGRAPH_ERROR - nSource: DATA_ERROR, nStatus: BAD_ARGUMENT 
> Jan 15 09:20:59 gauss kernel: [164859.750511] [drm] nouveau :01:00.0: 
> PGRAPH_ERROR - Ch 1/5 Class 0x008a Mthd 0x0300 Data 0x:0x 
> Jan 15 09:20:59 gauss kernel: [164859.750566] [drm] nouveau :01:00.0: 
> PFIFO_CACHE_ERROR - Ch 1/4 Mthd 0x Data 0x801a 
> Jan 15 09:20:59 gauss kernel: [164859.750580] [drm] nouveau :01:00.0: 
> PGRAPH_ERROR - nSource: ILLEGAL_MTHD, nStatus: BAD_ARGUMENT PROTECTION_FAULT

If X server is not running, where are these logs entries coming from? 
(nouveau is the X driver for nvidia cards) >;-)

Anyway, the behaviour you are experiencing with the ps/2 keyboard is weird 
enough to fill a bug in Debian BTS, I would go for it.

Greetings,

-- 
Camaleón


-- 
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/pan.2011.01.15.20.16...@gmail.com

Re: stardict dictionary packages.

[Camaleón]

On Sun, 16 Jan 2011 01:50:39 +0700, Sthu Deus wrote:

> Good day.

It's late afternoon here :-P
 
> Are in Debian the packages holding dictionaries capable to work w/
> stardict?
> 
> I see plenty of dictionaries for dict use, for example, but not for
> stardict. Or it is almost unusable program in Debian repo - as the
> interface program w/o the dictionaries seems to me as VCR w/o the tapes.
> :)

Aren't "dict-freedict-*-*" packages working with Stardict? (just asking 
because I have not tested) :-?

Greetings,

-- 
Camaleón


-- 
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/pan.2011.01.15.19.52...@gmail.com

stardict dictionary packages.

[Sthu Deus]

Good day.

Are in Debian the packages holding dictionaries capable to work w/
stardict?

I see plenty of dictionaries for dict use, for example, but not for
stardict. Or it is almost unusable program in Debian repo - as the
interface program w/o the dictionaries seems to me as VCR w/o the
tapes. :)

Thank You for Your time.


-- 
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/4d31ec84.ca7a0e0a.0341.9...@mx.google.com

Re: need help making shell script use two CPUs/cores

[Carl Johnson]

Stan Hoeppner  writes:

> Carl Johnson put forth on 1/13/2011 11:34 AM:
>
>> Processors  Time (seconds)
>> P1  66
>> P2  36
>> P3  25
>> P4  20
>> P5  20
>> P6  20
>> P7  20
>> P8  20
>
> Your numbers bear out exactly what I predicted.  Look at the decrease in run
> time from 1 to 2, 2 to 3, and from 3 to 4 processes:
>
> #CPUs Decremental run timeFractional gain per CPU
> 2 30s 1/2
> 3 11s 1/6th
> 4  5s 1/13th
>
> You can clearly see the effects of serious memory contention when 3 cores are
> pegged.  Bringing the 4th core into the mix yields almost nothing compared to
> three cores, cutting only 5 seconds from a 66 second run time.

I seem to be looking at it in a different way, because the numbers don't
seem that much different that what I would expect.

#CPUs  time  theoretical   time-theoreticalgain/CPU(theoretical)
1  66
2  3666/2 = 33 36-33   = 3   (+9%) 1  -1/2 = 1/2
3  2566/3 = 22 25-22   = 3   (+14%)1/2-1/3 = 1/6
4  2066/4 = 16.5   20-16.5 = 3.5 (+21%)1/3-1/4 = 1/12

-- 
Carl Johnsonca...@peak.org


-- 
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/87ei8e2foa.fsf@oak.localnet

Re: Keyboard freezing/repeating endlessly

[Joe Riel]

On Fri, 14 Jan 2011 07:47:59 -0800
Joe Riel  wrote:

> On Fri, 14 Jan 2011 11:38:43 + (UTC)
> Camaleón  wrote:
> 
> > You can:
> > 
> > 1/ Start the system with no xorg (console) and leave it so for
> > sometine to check if the problem is still present (even with no x
> > server).
> 
> I'll attempt to try this.  Might be painful working in a 
> virtual terminal all the time.  Kind of limits what I can
> do.  This is my work machine...

Got lucky, sort of.  I was just working in a virtual terminal
when the lockup occurred.  That doesn't rule out X in that
X was running (I had just opened the terminal and was reading
a man page), however, it suggests the problem might not be
with X.  That is consistent with the observation that restarting
gdm3 does not clear the fault.

> 
> > 2/ Review you kernel log, just in case ("cat /var/log/kern.log |
> > grep input").

Found the following lines (more of same) in kern.log at the time
of the lockup.  However, I don't see them for other lockups
(a lockup occurred while I was typing this email), so it could
be a red-herring:

Jan 15 09:20:58 gauss kernel: [164858.674186] [drm] nouveau :01:00.0: 
nouveau_channel_free: freeing fifo 2
Jan 15 09:20:59 gauss kernel: [164859.749505] [drm] nouveau :01:00.0: 
nouveau_channel_free: freeing fifo 1
Jan 15 09:20:59 gauss kernel: [164859.750491] [drm] nouveau :01:00.0: 
PFIFO_CACHE_ERROR - Ch 1/5 Mthd 0x Data 0x8013
Jan 15 09:20:59 gauss kernel: [164859.750507] [drm] nouveau :01:00.0: 
PGRAPH_ERROR - nSource: DATA_ERROR, nStatus: BAD_ARGUMENT
Jan 15 09:20:59 gauss kernel: [164859.750511] [drm] nouveau :01:00.0: 
PGRAPH_ERROR - Ch 1/5 Class 0x008a Mthd 0x0300 Data 0x:0x
Jan 15 09:20:59 gauss kernel: [164859.750566] [drm] nouveau :01:00.0: 
PFIFO_CACHE_ERROR - Ch 1/4 Mthd 0x Data 0x801a
Jan 15 09:20:59 gauss kernel: [164859.750580] [drm] nouveau :01:00.0: 
PGRAPH_ERROR - nSource: ILLEGAL_MTHD, nStatus: BAD_ARGUMENT PROTECTION_FAULT


-- 
Joe Riel


--
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/20110115095554.5c9cbb44@gauss

Re: [kinda solved] Re: aptitude: set all packages auto-installed except given list?

[Andrei Popescu]

On Sb, 15 ian 11, 14:14:11, Andrei Popescu wrote:
> On Sb, 15 ian 11, 12:23:07, Florian Kulzer wrote:
> > > 
> > > Any other suggestions?
> > 
> >   aptitude --schedule-only unmarkauto $(cat pkg.list)
> 
> Do you mean after a '--schedule-only markauto ~i'? Hmm, let's try... 
> Nope, not what I needed. But the solution seems to be:
> 
> aptitude --schedule-only markauto ~i
> aptitude --schedule-only install $(cat pkg.list)

Actually this only helps cleaning the system of unneeded packages, but 
still leaves me with a lot of packages not marked auto, so I had to 
apply Javier's hack after all.

Regards,
Andrei
-- 
Offtopic discussions among Debian users and developers:
http://lists.alioth.debian.org/mailman/listinfo/d-community-offtopic


signature.asc
Description: Digital signature

Re: Grub2 reinstall on raid1 system.

[Jack Schneider]

On Sat, 15 Jan 2011 12:06:11 -0200
Henrique de Moraes Holschuh  wrote:

> On Sat, 15 Jan 2011, Jack Schneider wrote:
> > > >> You might want to try configuring grub and fstab to use UUID's
> > > >> instead of /dev/mdX.  That removes the possibility that the
> > > >> kernel will change the mdX designations.
> > > >>
> > > >> Use blkid to find out the UUID's of your partitions.
> 
> Whatever you do, NEVER use the UUIDs of partitions, use the UUID of
> the md devices.  The worst failure scenario involving MD and idiotic
> tools is for a tool to cause a component device to be mounted instead
> of the MD array.
> 
> This is one of the reasons why the new MD formats that offset the data
> inside the component devices exists.
> 
Thanks, Henrique!!!  That gives me a new place to start this AM...

Jack


--
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/20110115082823.28019...@torrid.volunteerwireless.net

Re: aptitude: set all packages auto-installed except given list?

[Gilles Mocellin]

Le samedi 15 janvier, Florian Kulzer écrivit :
> On Sat, Jan 15, 2011 at 13:01:30 +0200, Andrei Popescu wrote:
>  [...]
> 
>   aptitude --schedule-only unmarkauto $(cat pkg.list)
> 
> is somewhat clumsy, but it seems to work here. I only tried a simple
> test case with a list of two packages, and I did not test if
> --schedule-only is really necessary. If your list of packages exceeds
> the maximum number of command line arguments then you have to split the
> file. Backticks should also work if you want to avoid the $(...)
> bashism.

Another simpler form, but perhaps again a bashism is :
# aptitude unmarkauto $(< pkg.list)

No process fork for "cat".


signature.asc
Description: Digital signature

Re: Grub2 reinstall on raid1 system.

[Henrique de Moraes Holschuh]

On Sat, 15 Jan 2011, Jack Schneider wrote:
> > >> You might want to try configuring grub and fstab to use UUID's
> > >> instead of /dev/mdX.  That removes the possibility that the kernel
> > >> will change the mdX designations.
> > >>
> > >> Use blkid to find out the UUID's of your partitions.

Whatever you do, NEVER use the UUIDs of partitions, use the UUID of the
md devices.  The worst failure scenario involving MD and idiotic tools
is for a tool to cause a component device to be mounted instead of the
MD array.

This is one of the reasons why the new MD formats that offset the data
inside the component devices exists.

-- 
  "One disk to rule them all, One disk to find them. One disk to bring
  them all and in the darkness grind them. In the Land of Redmond
  where the shadows lie." -- The Silicon Valley Tarot
  Henrique Holschuh


-- 
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/20110115140611.ga26...@khazad-dum.debian.net

Re: Grub2 reinstall on raid1 system.

[Jack Schneider]

On Fri, 14 Jan 2011 05:25:45 -0700
Bob Proulx  wrote:

> Jack Schneider wrote:
> > I have a raid1 based W/S running Debian Squeeze uptodate. (was
> > until ~7 days ago) There are 4 drives, 2 of which had never been
> > used or formatted. I configured a new array using Disk Utility from
> > a live Ubuntu CD. That's where I screwed up... The end result was
> > the names of the arrays were changed on the working 2 drives.
> > IE: /dev/md0 to /dev/126 and /dev/md1 became md127.
> 
> Something else must have happened too.  Because normally just adding
> arrays will not rename the existing arrays.  I am not familiar with
> the "Disk Utility" that you mention.
> 
> Next time instead you might just use mdadm directly.  It really is
> quite easy to create new arrays using it.  Here is an example that
> will create a new device /dev/md9 mirrored from two other devices
> /dev/sdy5 and /dev/sdz5.
> 
>   mdadm --create /dev/md9 --level=mirror
> --raid-devices=2 /dev/sdy5 /dev/sdz5

This is how I created /dev/md2.

> 
> > Strangely the md2 array which I setup on the added drives remains as
> > /dev/md2. My root partition is/was on /dev/md0. The result is that
> > Grub2 fails to boot the / array.
> 
> You may have to boot a rescue cd.  I recommend booting the Debian
> install disk in rescue mode.  Then you can inspect and fix the
> problem.  But as of yet you haven't said enough to let us know what
> the problem might be yet.
> 
> > I have tried three REINSTALLING GRUB procedures from Sysresccd
> > online docs and many others GNU.org, Ubuntu etc.
> 
> This isn't encouraging.  I can tell that you are grasping at straws.
> You have my sympathy.  But unfortunately that doesn't help diagnose
> the problem.  Remain calm.  And repeat exactly the problem that you
> are seeing and the steps you have taken to correct it.
> 
I have not made any changes to any files on the root partition. I have
only used the procedures from SystemRescueCD and then backed out. All
seem to fail with the same "linux_raid_member" error.
> > The errors occur when I try to mount the partition with the /boot
> > directory. 'Complains about file system type 'linux_raid_member'
> 


> I haven't seen that error before.  Maybe someone else will recognize
> it.
> 
> I don't understand why you would get an error mounting /boot that
> would prevent the system from coming online.  Because by the time the
> system has booted enough to mount /boot it has already practically
> booted completely.  The system doesn't actually need /boot mounted to
> boot.  Grub reads the files from /boot and sets things in motion and
> then /etc/fstab instructs the system to mount /boot.
I get that when using the live rescue disk.
> 
> Usually when the root device cannot be assembled the error I see is
> that the system is "Waiting for root filesystem" and can eventually
> get to a recovery shell prompt.
> 
> > This machine has worked for 3 years flawlessly.. Can anyone help
> > with this? Or point me to a place or link to get this fixed. Google
> > doesn't help... I can't find a article/posting where it ended
> > successfully.  I have considered a full reinstall after Squeeze goes
> > stable, since this O/S is a crufty upgrade from sarge over time. But
> > useless now..
> 
> The partitions for raid volumes should be 'autodetect' 0xFD.  This
> will enable mdadm to assemble then into raid at boot time.
> 
> You can inspect the raid partitions with --detail and --examine.
> 
>   mdadm --examine /dev/sda1
>   mdadm --detail /dev/md0
> 
> That will list information about the devices.  Replace with your own
> series of devices.
> 
> I would boot a rescue image and then inspect the current configuration
> using the above commands.  Hopefully that will show something wrong
> that can be fixed after you know what it is.
> 
> A couple of other hints: If you are not booting a rescue system but
> using something like a live boot then you may need to load the kernel
> modules manually.  You may need to load the dm_mod and md_mod modules.
> 
>   modprobe md_mod
> 
> You might get useful information from looking at the /proc/mdstat
> status.
> 
>   cat /proc/mdstat
> 
> There is a configuration file /etc/mdadm/mdadm.conf that holds the
> UUIDs of the configured devices.  If those have become corrupted then
> mdadm won't be able to assemble the /dev/md* devices.  Check that file
> and compare against what you see with the --detail output.
> 
> The initrd contains a copy of the mdadm.conf file with the components
> needed to assemble the root filesystem.  If the UUIDs change over what
> is recorded in the initrd then the initrd will need to be rebuilt.  To
> do that make sure that the /etc/mdadm/mdadm.conf file is correct and
> then reconfigure the kernel with dpkg-reconfigure.
> 
>   dpkg-reconfigure linux-image-2.6.32-5-i686
> 
> Good luck!
> 
> Bob
Thanks, Bob
I will do as you suggest shortly.. BTW,  A little more info in my reply
to Tom..

TIA, Jack


-- 
To UNSUBSCRIBE, email to debian-user-req

Re: Grub2 reinstall on raid1 system.

[Jack Schneider]

On Fri, 14 Jan 2011 12:16:37 -0500
Tom H  wrote:
> >> >
[BIG SNIP]

> >> You might want to try configuring grub and fstab to use UUID's
> >> instead of /dev/mdX.  That removes the possibility that the kernel
> >> will change the mdX designations.
> >>
> >> Use blkid to find out the UUID's of your partitions.
> >
> > Thanks for the reply, Rob. What grub file do I change?
> > grub.cfg?  grub *.map? I seem to have UUIDs for both disks and
> > LVM partitions, change both?
> 
> So you have LVM over RAID, not just RAID.
Hi, Tom.
Well, not really, not all of the disks are LVM2. The first two
disks raid1 /dev/sda & /dev/sdc are partitioned with 1 small
/(root) partition, /dev/md0 -> 10 gigs. The balance of the disk
is /dev/md1 under LVM2 with seven logical volumes. /home,/var,/swap
etc  The next two disks sdb and sdd are raid1 as /dev/md2 which I
need to use as an extension of the LVM. 

More info, when I boot the machine, I see the "GRUB loading. WELCOME to
GRUB!" info.  Then it enters the rescue mode with a "grub rescue>"
prompt.  So the kernel is found/finding the / partition. Right?
 


> 
> For grub2, you're only supposed to edit "/etc/default/grub".
> 
> 

I started interpreting that as simply needing a update-grub type of
fix.. I was/am  wrong...   So I resorted  to systemrescuecd-2.0.0..
to fix up Grub..


Thanks, Jack


--
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/20110115072451.00d25...@torrid.volunteerwireless.net

Re: aptitude: set all packages auto-installed except given list?

[Jochen Schulz]

Florian Kulzer:
> 
> […] Backticks should also work if you want to avoid the $(...)
> bashism.

That's not a bashism, it's perfectly legal POSIX/SUS.

http://pubs.opengroup.org/onlinepubs/009695399/utilities/xcu_chap02.html#tag_02_06_03

J.
-- 
In this bunker there are women and children. There are no weapons.
[Agree]   [Disagree]
 


signature.asc
Description: Digital signature

Re: Lenny - xvinfo: No Adaptors present.. No XVideo

[Sven Joachim]

On 2011-01-15 12:58 +0100, Camaleón wrote:

> On Fri, 14 Jan 2011 21:03:19 -0500, Chris Jones wrote:
>
>> On Fri, Jan 14, 2011 at 12:37:11PM EST, Camaleón wrote:
>> 
>> [..]
>> 
>>> Maybe it's time for you attach/upload the whole "/var/log/Xorg.0.log"
>>> file :-)
>> 
>> Hey.. why not..
>> 
>>   http://pastebin.com/38DZcW7D
>
> Thanks :-)
>
> Some comments on the log...
>
> ***
> (II) Loading /usr/lib/xorg/modules/extensions//libglx.so
> (II) Module glx: vendor="NVIDIA Corporation"
> compiled for 4.0.2, module version = 1.0.0
> Module class: X.Org Server Extension
> (II) NVIDIA GLX Module  173.14.09  Thu Jun  5 00:07:40 PDT 2008
> (II) Loading extension GLX
> **
>
> It seems loading the GLX module using some part of the nvidia closed 
> drivers... how is that possible? :-?

Because the nvidia-glx package is installed, even though Chris does not
use it.  This is bad because no program that uses OpenGL will be able to
run, but not directly related to the problem.

> And there is something more in your log it caught my attention:
>
> ***
> (II) Primary Device is: PCI 01:00:0
> (--) Assigning device section with no busID to primary device
> (--) Chipset Unknown NVIDIA chip found

Yeah, the nv driver is too old and does not really know the card.
Should not be much of a problem, though.

> I still don't see why are you so reluctant to "test" the closed source 
> driver. Just to test, for seeing how it goes and if it solves nothing 
> then at least you can decide the next step with confidence :-)

I wonder why Chris bought a laptop with such a powerful card in the
first place if he has no use for it.  Intel graphics would have been
cheaper and also cause much less headaches.

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

[Solved] Re: aptitude: set all packages auto-installed except given list?

[Andrei Popescu]

On Sb, 15 ian 11, 12:23:07, Florian Kulzer wrote:
> > 
> > Any other suggestions?
> 
>   aptitude --schedule-only unmarkauto $(cat pkg.list)

Do you mean after a '--schedule-only markauto ~i'? Hmm, let's try... 
Nope, not what I needed. But the solution seems to be:

aptitude --schedule-only markauto ~i
aptitude --schedule-only install $(cat pkg.list)

Didn't think of trying with --schedule-only

Regards,
Andrei
-- 
Offtopic discussions among Debian users and developers:
http://lists.alioth.debian.org/mailman/listinfo/d-community-offtopic


signature.asc
Description: Digital signature

Re: Lenny - xvinfo: No Adaptors present.. No XVideo

[Camaleón]

On Fri, 14 Jan 2011 21:03:19 -0500, Chris Jones wrote:

> On Fri, Jan 14, 2011 at 12:37:11PM EST, Camaleón wrote:
> 
> [..]
> 
>> Maybe it's time for you attach/upload the whole "/var/log/Xorg.0.log"
>> file :-)
> 
> Hey.. why not..
> 
>   http://pastebin.com/38DZcW7D

Thanks :-)

Some comments on the log...

***
(II) Loading /usr/lib/xorg/modules/extensions//libglx.so
(II) Module glx: vendor="NVIDIA Corporation"
compiled for 4.0.2, module version = 1.0.0
Module class: X.Org Server Extension
(II) NVIDIA GLX Module  173.14.09  Thu Jun  5 00:07:40 PDT 2008
(II) Loading extension GLX
**

It seems loading the GLX module using some part of the nvidia closed 
drivers... how is that possible? :-?

Now look mine:

***
(II) LoadModule: "glx"
(II) Loading /usr/lib/xorg/modules/extensions//libglx.so
(II) Module glx: vendor="X.Org Foundation"
compiled for 1.4.2, module version = 1.0.0
ABI class: X.Org Server Extension, version 0.3
(==) AIGLX enabled
(II) Loading extension GLX
***

Here is loading the Xorg stock GLX extension.

...

And there is something more in your log it caught my attention:

***
(II) Primary Device is: PCI 01:00:0
(--) Assigning device section with no busID to primary device
(--) Chipset Unknown NVIDIA chip found
***

And now compare to mine:

***
(II) Primary Device is: PCI 01:00:0
(--) Assigning device section with no busID to primary device
(--) Chipset Quadro FX 1500 found
***

I still don't see why are you so reluctant to "test" the closed source 
driver. Just to test, for seeing how it goes and if it solves nothing 
then at least you can decide the next step with confidence :-)

You said your card was "unsupported" and you maybe right.

- Lenny ships "nvidia-glx" 173.14.09 and your card is not listed:

http://us.download.nvidia.com/XFree86/Linux-x86/173.14.09/README/appendix-a.html

- But Squeeze ships "nvidia-glx" 195.36.31 and your card appears there:

http://us.download.nvidia.com/XFree86/Linux-x86/195.36.31/README/supportedchips.html

So you can test the closed driver in squeeze and see how it goes. If all 
is fine you can then install the latest driver available from nvidia site 
in lenny (it will require driver compilation).

Greetings,

-- 
Camaleón


-- 
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/pan.2011.01.15.11.58...@gmail.com

Re: aptitude: set all packages auto-installed except given list?

[Javier Barroso]

On Sat, Jan 15, 2011 at 12:38 PM, Andrei Popescu
 wrote:
> On Sb, 15 ian 11, 12:25:26, Javier Barroso wrote:
>>
>> If you have a packages.txt file with a package by line, do it with awk:
>>
>> aptitude markauto '~i'$(awk '{printf "!~n^"$1"$";}' packages.txt)
>>
>> And a similar trick marking these packages like manual installed.
>
> Thanks, at a first glance that was enough. I just hoped for a solution
> that wouldn't involve such hacks. Unless somebody comes up with a
> cleaner solution I'll file a whishlist bug.
Ok, I would like to hear Daniel (aptitude author) reply, aptitude
development seems to be in standby  :(, I hope squeeze freeze be the
reason ...


-- 
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/aanlktinmfseafsj2zvzy+7wyz2cnz3_ndyxb9cavz...@mail.gmail.com

Re: aptitude: set all packages auto-installed except given list?

[Florian Kulzer]

On Sat, Jan 15, 2011 at 13:01:30 +0200, Andrei Popescu wrote:

 [...]

> How can I:
> 
> - set everything to auto-installed
> - automatically mark as manually installed the ones in the list
> 
> ?
> 
> I already tried (as root):
> 
> aptitude markauto ~i
> 
> This will try to remove everything and I have to abort
> 
> aptitude --schedule-only markauto ~i
> 
> Seems to be doing the first part, but I can't convince aptitude to 
> unmark my list (which I processed to not contain unneeded space and 
> newlines):
> 
> aptitude unmarkauto < pkg.list
> 
> has no effect
> 
> aptitude install < pkg.list
> 
> first tries to remove everything and when I say 'n' it starts crunching 
> on my processor.
> 
> Any other suggestions?

  aptitude --schedule-only unmarkauto $(cat pkg.list)

is somewhat clumsy, but it seems to work here. I only tried a simple
test case with a list of two packages, and I did not test if
--schedule-only is really necessary. If your list of packages exceeds
the maximum number of command line arguments then you have to split the
file. Backticks should also work if you want to avoid the $(...)
bashism.

-- 
Regards,|
  Florian   | http://www.florian-kulzer.eu


-- 
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/20110115112307.GA3041@isar.localhost

Re: aptitude: set all packages auto-installed except given list?

[Andrei Popescu]

On Sb, 15 ian 11, 12:29:15, Javier Barroso wrote:
> >
> > And a similar trick marking these packages like manual installed.
> Maybe essential packages should be installed no auto (add !~E to expression)

Not needed since apt/aptitude will never auto-remove packages 
'Essential: yes'.

Regards,
Andrei
-- 
Offtopic discussions among Debian users and developers:
http://lists.alioth.debian.org/mailman/listinfo/d-community-offtopic


signature.asc
Description: Digital signature

Re: aptitude: set all packages auto-installed except given list?

[Andrei Popescu]

On Sb, 15 ian 11, 12:25:26, Javier Barroso wrote:
> 
> If you have a packages.txt file with a package by line, do it with awk:
> 
> aptitude markauto '~i'$(awk '{printf "!~n^"$1"$";}' packages.txt)
> 
> And a similar trick marking these packages like manual installed.

Thanks, at a first glance that was enough. I just hoped for a solution 
that wouldn't involve such hacks. Unless somebody comes up with a 
cleaner solution I'll file a whishlist bug.

Regards,
Andrei
-- 
Offtopic discussions among Debian users and developers:
http://lists.alioth.debian.org/mailman/listinfo/d-community-offtopic


signature.asc
Description: Digital signature

Re: aptitude: set all packages auto-installed except given list?

[Javier Barroso]

On Sat, Jan 15, 2011 at 12:25 PM, Javier Barroso  wrote:
> Hi,
>
> On Sat, Jan 15, 2011 at 12:01 PM, Andrei Popescu
>  wrote:
>> Hi,
>>
>> My usual method of 'cleaning' the system was to set all installed
>> packages to auto-installed and then mark one by one the ones I need to
>> keep. I even have a good list generated with:
>>
>> aptitude -F '%?p' search '~i!~M' > bak/pkg.list
>>
>> Now the problem I'm facing is that (probably due to some aptitude bug
>> than seems to have disappeared) most of my installed packages are set to
>> manually installed. How can I:
>>
>> - set everything to auto-installed
>> - automatically mark as manually installed the ones in the list
>>
>> ?
>>
>> I already tried (as root):
>>
>>    aptitude markauto ~i
> Maybe, I don't known if command line length limit imposed by bash will
> let to do it:
>
> Generate an string like:
>
> aptitude markauto  '~i!~n^package1$!~n^package2$'
>
> If you have a packages.txt file with a package by line, do it with awk:
>
> aptitude markauto '~i'$(awk '{printf "!~n^"$1"$";}' packages.txt)
>
> And a similar trick marking these packages like manual installed.
Maybe essential packages should be installed no auto (add !~E to expression)


--
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/AANLkTikbgSNb=u=dwth-xz9ahqdv3pbpm6ov7xv3z...@mail.gmail.com

Re: aptitude: set all packages auto-installed except given list?

[Javier Barroso]

Hi,

On Sat, Jan 15, 2011 at 12:01 PM, Andrei Popescu
 wrote:
> Hi,
>
> My usual method of 'cleaning' the system was to set all installed
> packages to auto-installed and then mark one by one the ones I need to
> keep. I even have a good list generated with:
>
> aptitude -F '%?p' search '~i!~M' > bak/pkg.list
>
> Now the problem I'm facing is that (probably due to some aptitude bug
> than seems to have disappeared) most of my installed packages are set to
> manually installed. How can I:
>
> - set everything to auto-installed
> - automatically mark as manually installed the ones in the list
>
> ?
>
> I already tried (as root):
>
>    aptitude markauto ~i
Maybe, I don't known if command line length limit imposed by bash will
let to do it:

Generate an string like:

aptitude markauto  '~i!~n^package1$!~n^package2$'

If you have a packages.txt file with a package by line, do it with awk:

aptitude markauto '~i'$(awk '{printf "!~n^"$1"$";}' packages.txt)

And a similar trick marking these packages like manual installed.

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/AANLkTi=6td7emokzzg-1c1mpodf9a_u1niwtwx0zl...@mail.gmail.com

aptitude: set all packages auto-installed except given list?

[Andrei Popescu]

Hi,

My usual method of 'cleaning' the system was to set all installed 
packages to auto-installed and then mark one by one the ones I need to 
keep. I even have a good list generated with:

aptitude -F '%?p' search '~i!~M' > bak/pkg.list

Now the problem I'm facing is that (probably due to some aptitude bug 
than seems to have disappeared) most of my installed packages are set to 
manually installed. How can I:

- set everything to auto-installed
- automatically mark as manually installed the ones in the list

?

I already tried (as root):

aptitude markauto ~i

This will try to remove everything and I have to abort

aptitude --schedule-only markauto ~i

Seems to be doing the first part, but I can't convince aptitude to 
unmark my list (which I processed to not contain unneeded space and 
newlines):

aptitude unmarkauto < pkg.list

has no effect

aptitude install < pkg.list

first tries to remove everything and when I say 'n' it starts crunching 
on my processor.

Any other suggestions?

Regards,
Andrei
-- 
Offtopic discussions among Debian users and developers:
http://lists.alioth.debian.org/mailman/listinfo/d-community-offtopic


signature.asc
Description: Digital signature