ext3 mount failing due to bad superblock.

[darkestkhan]

I created ext3 on sda1 (using mke2fs -j) and it worked for last 20 days.
But after tiday reboot it stopped working - if it would be bad entry in fstab
I would still be able to mount it by hand, but I can't. I have some data
on it that I would rather not lose (I don't have enough space to make backups
of everything). Here is dmesg | tail output:

"
[  500.130158] EXT4-fs (sda1): VFS: Can't find ext4 filesystem
"

Note that I get the same error no matter if use mount -t ext{2,3,4}

Output of fsck:

"
fsck from util-linux 2.20.1
e2fsck 1.42.8 (20-Jun-2013)
ext2fs_open2: Bad magic number in super-block
fsck.ext3: Superblock invalid, trying backup blocks...
fsck.ext3: Bad magic number in super-block while trying to open /dev/sda1

The superblock could not be read or does not describe a correct ext2
filesystem.  If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193 
"

Is there some way to recover filesystem (or at least data contained in it)?

darkestkhan

--

"May the source be with you."


-- 
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/20131109082921.GA3838@localhost

Re: Why Debian

[xavi]

I use Debian because Debian is like an old good car. Easy to open and 
see how it's mounted. Without too much customization. Without too  much 
gurus and astronauts. And with a lot of support. I like it very much. 
Really.


But if you prefer more customization and a distro very user friendly 
(and the astronaut), maybe you could use Xubuntu or maybe Linux Mint.


Sorry for my english ;)

Il 2013-11-09 07:49 Gábor Hársfalvi ha scritto:

Because Debian uses the most stable packages - if you use the stable
version of Debian -  while Ubuntu uses the newest packages.

I like both Ubuntu and Debian - but Debian is closest to my heart.

2013/11/9 Beco 


On 8 Nov 2013 14:15, "Alberto Salvia Novella"
 wrote:

Summarizing:

Which are the very important reasons why do you prefer Debian

over Ubuntu?





Why to use a Debian based OS if you can use Debian?

My best,
Beco.


--

xavi   ||  lorajoler[at]paranoici.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/cc785228693bf3d387fd841fce3d3...@paranoici.org

Weird boot problem. How can this be?

[Ray Dillinger]

I have a strange problem where my computer does not recognize *ANY* boot device
or boot medium other than one single hard drive where a badly configured debian
linux is installed.  I don't think the particulars of that messed-up install
are relevant, but I've put a note about it at the bottom just in case.

I don't understand how it can possibly happen, because I have completely 
unplugged
that hard drive, flashed the BIOS of the machine with the most recent update, 
installed
a brand new blank hard drive, and it *STILL* doesn't recognize any boot medium 
or
boot device unless I plug the drive with that messed-up install back in.

The machine is an Asus Sabertooth X79 motherboard, IA64 "Sandy Bridge" 
architecture,
with an ASUS SATA DVD-ROM in the chassis and a generic DVD-ROM attached via 
USB2.  If
I don't have the single bootable hard drive (incidentally a 3 TB Seagate drive)
installed in the chassis, NO device will boot.  And if I do have it installed in
the chassis, no OTHER device will boot.

I want to fix my confused install by creating a clean "Jessie/Testing" system to
migrate data to.  But when I put a bootable 'Jessie' netinst disk into it (in 
either
drive) and a blank hard disk to format for a new system, and I get

"No Operating System Found" if I go straight into the BIOS boot menu and tell it
to boot off the drive that contains the netinst disk, or

"No bootable medium found; Please insert bootable disk into boot drive and 
press any
key" if I set the boot order so that the drive with the netinst is included.

I have also tried booting directly from a USB stick; it does exactly the same 
thing.

My main relevant current limitation in using the messed up install is that "su" 
and
"sudo" are both broken; to do anything as root, I have to be logged in as root.
There are some others, and lots of documentation that's just plain wrong about 
where
things are installed etc, but not being able to su or sudo is the most annoying.


My messed up install started as "Sarge" in a different IA64 machine a long time 
ago,
got upgraded to "Lenny" and then "Wheezy" when "Wheezy" was still experimental.
"Wheezy" was very definitely not ready for prime time, and I did some major 
config
hacking just to get a usable KDE desktop on it.  Used it that way for several
years, then I moved the drive to the current chassis and motherboard and "sorted
out" several new issues that that caused, by hand.  Next I wanted something from
the "Experimental" distro, so I downloaded it - and forgot to take 
"Experimental"
out of my debian sources list immediately afterward.  Over the next couple of
weeks, about half the software got "upgraded" to flaky versions not available in
"Wheezy".  I started trying to sort out issues and do configuration, and I wound
up with a bizarre mutant hybrid.

Then I realized I had "Experimental" in my sources, got rid of it, Added 
"Testing"
(which by this time was Jessie heading into the current freeze), and used dpkg 
to
get RID OF every version of everything that it couldn't still download.  That 
broke
a bunch of stuff, and I've managed fix some by hand and work around the rest of 
it
for several weeks now.   I don't see how it can be relevant when this drive 
isn't
even attached and I'm still having this problem, but if you can think of any 
reason
why it might be, do let me know.

Anyway, this is driving me bonkers.  If anybody has any clues as to what could 
be
wrong on such a basic level as to affect boot behavior on a blank hard drive 
and a
net install disk, and that immediately after flashing the BIOS, please do let 
me know.

Bear


--
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/527df1b0.4070...@sonic.net

Re: ext3 mount failing due to bad superblock.

[Jude DaShiell]

If you have your original debian net-inst dvd, it's probably time to 
put the dvd into the drive then reboot the computer into rescue mode.  
Then run fsck.ext4 -c /dev/sda1  and watch the fun.  This will 
use badblocks nondestructively and set off a repair operation which 
should end up with you having all of your data recovered.  Figure you 
have a bad hard drive on its last legs and backup what you can for a 
later and better install on a new hard drive would be what I would do in 
your situation.  Once the drive is alive again, you may want to install 
and run smartd-utils on it and check those log files since they'll 
provide warnings.  If you can get smartd-utils to e-mail you so much the 
better.

On Sat, 9 Nov 2013, darkestkhan wrote:

> I created ext3 on sda1 (using mke2fs -j) and it worked for last 20 days.
> But after tiday reboot it stopped working - if it would be bad entry in fstab
> I would still be able to mount it by hand, but I can't. I have some data
> on it that I would rather not lose (I don't have enough space to make backups
> of everything). Here is dmesg | tail output:
> 
> "
> [  500.130158] EXT4-fs (sda1): VFS: Can't find ext4 filesystem
> "
> 
> Note that I get the same error no matter if use mount -t ext{2,3,4}
> 
> Output of fsck:
> 
> "
> fsck from util-linux 2.20.1
> e2fsck 1.42.8 (20-Jun-2013)
> ext2fs_open2: Bad magic number in super-block
> fsck.ext3: Superblock invalid, trying backup blocks...
> fsck.ext3: Bad magic number in super-block while trying to open /dev/sda1
> 
> The superblock could not be read or does not describe a correct ext2
> filesystem.  If the device is valid and it really contains an ext2
> filesystem (and not swap or ufs or something else), then the superblock
> is corrupt, and you might try running e2fsck with an alternate superblock:
> e2fsck -b 8193 
> "
> 
> Is there some way to recover filesystem (or at least data contained in it)?
> 
> darkestkhan
> 
> --
> 
> "May the source be with you."
> 
> 
> 

---
jude 
Avoid the Gates Of Hell, use Linux!


-- 
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/alpine.bsf.2.01.1311090342530.51...@freire1.furyyjbeyq.arg

Re: Why Debian

[Alberto Salvia Novella]

So you feel more vanilla is better, is this?


El 09/11/13 08:48, Itay escribió:

On Sat, 9 Nov 2013, Beco wrote:

On 8 Nov 2013 14:15, "Alberto Salvia Novella"  
wrote:

Summarizing:

Which are the very important reasons why do you prefer Debian over 
Ubuntu?




Why to use a Debian based OS if you can use Debian?

My best,
Beco.


I second that.

Itay






--
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/527df33a.7010...@gmail.com

Re: Weird boot problem. How can this be?

[Jude DaShiell]

Okay, your bios settings are messed up on that computer.  You need to go 
into bios settings and give them some clues about what's actually on the 
computer in terms of hardware.  The bios settings on your machine have 
lost their mind somehow.

On Sat, 9 Nov 2013, Ray Dillinger wrote:

> 
> I have a strange problem where my computer does not recognize *ANY* boot
> device
> or boot medium other than one single hard drive where a badly configured
> debian
> linux is installed.  I don't think the particulars of that messed-up install
> are relevant, but I've put a note about it at the bottom just in case.
> 
> I don't understand how it can possibly happen, because I have completely
> unplugged
> that hard drive, flashed the BIOS of the machine with the most recent update,
> installed
> a brand new blank hard drive, and it *STILL* doesn't recognize any boot medium
> or
> boot device unless I plug the drive with that messed-up install back in.
> 
> The machine is an Asus Sabertooth X79 motherboard, IA64 "Sandy Bridge"
> architecture,
> with an ASUS SATA DVD-ROM in the chassis and a generic DVD-ROM attached via
> USB2.  If
> I don't have the single bootable hard drive (incidentally a 3 TB Seagate
> drive)
> installed in the chassis, NO device will boot.  And if I do have it installed
> in
> the chassis, no OTHER device will boot.
> 
> I want to fix my confused install by creating a clean "Jessie/Testing" system
> to
> migrate data to.  But when I put a bootable 'Jessie' netinst disk into it (in
> either
> drive) and a blank hard disk to format for a new system, and I get
> 
> "No Operating System Found" if I go straight into the BIOS boot menu and tell
> it
> to boot off the drive that contains the netinst disk, or
> 
> "No bootable medium found; Please insert bootable disk into boot drive and
> press any
> key" if I set the boot order so that the drive with the netinst is included.
> 
> I have also tried booting directly from a USB stick; it does exactly the same
> thing.
> 
> My main relevant current limitation in using the messed up install is that
> "su" and
> "sudo" are both broken; to do anything as root, I have to be logged in as
> root.
> There are some others, and lots of documentation that's just plain wrong about
> where
> things are installed etc, but not being able to su or sudo is the most
> annoying.
> 
> 
> My messed up install started as "Sarge" in a different IA64 machine a long
> time ago,
> got upgraded to "Lenny" and then "Wheezy" when "Wheezy" was still
> experimental.
> "Wheezy" was very definitely not ready for prime time, and I did some major
> config
> hacking just to get a usable KDE desktop on it.  Used it that way for several
> years, then I moved the drive to the current chassis and motherboard and
> "sorted
> out" several new issues that that caused, by hand.  Next I wanted something
> from
> the "Experimental" distro, so I downloaded it - and forgot to take
> "Experimental"
> out of my debian sources list immediately afterward.  Over the next couple of
> weeks, about half the software got "upgraded" to flaky versions not available
> in
> "Wheezy".  I started trying to sort out issues and do configuration, and I
> wound
> up with a bizarre mutant hybrid.
> 
> Then I realized I had "Experimental" in my sources, got rid of it, Added
> "Testing"
> (which by this time was Jessie heading into the current freeze), and used dpkg
> to
> get RID OF every version of everything that it couldn't still download.  That
> broke
> a bunch of stuff, and I've managed fix some by hand and work around the rest
> of it
> for several weeks now.   I don't see how it can be relevant when this drive
> isn't
> even attached and I'm still having this problem, but if you can think of any
> reason
> why it might be, do let me know.
> 
> Anyway, this is driving me bonkers.  If anybody has any clues as to what could
> be
> wrong on such a basic level as to affect boot behavior on a blank hard drive
> and a
> net install disk, and that immediately after flashing the BIOS, please do let
> me know.
> 
> Bear
> 
> 
> 

---
jude 
Avoid the Gates Of Hell, use Linux!


-- 
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/alpine.bsf.2.01.1311090352590.51...@freire1.furyyjbeyq.arg

Re: gschem for Debian 7?

[Jean-Marc]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

On 09/11/13 03:56, John Conover wrote:
> Where is the .deb for gschem for Debian 7?

Are you speaking about the electronics design software ?

http://packages.debian.org/search?keywords=gschem

> 
> Thanks,
> 
> John
> 

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.15 (GNU/Linux)
Comment: Using GnuPG with Icedove - http://www.enigmail.net/

iQIcBAEBCAAGBQJSffmlAAoJEECwQOvthjrRTRwP/2y0w4LdPZG0tvw7/qCsfOa6
HxS2ebgoSueTxTtKgNUJ3ikunZnqma3WevvTKawh5Yj4Yg8m3oQHjBObytsEj+vA
KOfxbZ31joBgQEN78xY/7+OOISp/SOGdlMvOFESiS9C30W420OoNZ8BC175poCon
vS+Nsqqe7+QGu5envut9Lr13+38F6uNzMqE6RTGIm+8X6YRqR/0l7y7WOLSLG22E
xxMphKFvN16H2v7rITehBzDW11tfC3Rp+GiDqWn2nblJzTU4mq+dQxST6vLrVx7K
CXQ/aX65aSmiflKuESP48cX+gpQN06EnkBVoNXEsQnD1O4px4XdIzgWzD+wfTj6w
iK+3yThkekQim8eT1Tb5DeBQHf1Ms9yGhlnIZMjkwkU0k93pnckn2EzRhCZm1ZJQ
ggPVBLnn/Fie5x3vfNO5PtX/bNZNDLjQ3j3Oa/L62sFMise4kouz0cGBZBNpC3Mr
rEz4OinUs/cOWunSpPv/10VQTjki3yAyh9vJ5LwBnJB9wIU3bEqRrUonFJNYnJOI
vD4YawE2TciJACO0qh3V8IuGeAGt3S+1u5yu/+Ma9lvH5sKMI93OKWdEbYMzX7NG
p7NkTFpmAC1kAycE8wmW1DzGbrJr1hq8Ba33N48JqAgSkzmXqKEJ6Qf0h14B2cAx
wz97rRFrDReirtrsRTAx
=JCq5
-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/527df9b0.4040...@6jf.be

Re: ext3 mount failing due to bad superblock.

[darkestkhan]

On Sat, Nov 9, 2013 at 8:49 AM, Jude DaShiell  wrote:
> If you have your original debian net-inst dvd, it's probably time to
> put the dvd into the drive then reboot the computer into rescue mode.

Funny thing (actually not so) - my optic drive is dead. But why do I
have to reboot
into recovery mode? System itself works correctly - /boot is on sda2
and everything
else is on LVM at sda3. (Windows 7 was on sda1 but it died due to...
lack of space;
srlsy - it started taking full 30GB of disk space after all updates).

> Then run fsck.ext4 -c /dev/sda1  and watch the fun.  This will
> use badblocks nondestructively and set off a repair operation which
> should end up with you having all of your data recovered.

Running this in recovery mode gets me the same message as running it normally
(as it should - after all sda1 is not mounted) which is the same as my
original mail.

I also tried all possible combinations of "e2fsck -b " -
result is the same.

-- 

darkestkhan
--
Feel free to CC me.
jid: darkestk...@gmail.com
May The Source be with You.


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

Re: Why Debian

[Itay]

On Sat, 9 Nov 2013, Alberto Salvia Novella wrote:

[propagated response to bottom]


El 09/11/13 08:48, Itay escribió:

On Sat, 9 Nov 2013, Beco wrote:


Which are the very important reasons why do you prefer Debian over 
Ubuntu?


Why to use a Debian based OS if you can use Debian?

My best,
Beco.


I second that.

Itay



So you feel more vanilla is better, is this?


I prefer chocolate... ;-)

Now seriously, I admit I did not try out ubuntu and my decision was 
based only on impression from reading ubuntu and debian publications, 
mailing lists, etc.
I had the impression that ubuntu's claim-to-fame was being closer to 
the cutting-edge, while debian's was stability.


I am a home user, with no formal education whatsoever in system 
administration and computers.
But after trying RedHat, Fedora, Centos, I got tired from trying to 
maintain a stable PC system for home use with these distributions.
Debian was the first to provide me with a good mixture of stability 
and concurrency with latest advances in computer technology.


Yes, I have to sweat on doing simple things, like configuring exim4 to 
send out email to my public address.
But the good thing in Debian for me is: I feel that once Ilearn to do 
something, the knowledge will stay with me, and will be relevant for 
quite some time in the future.


Hope this helps.
Itay

Re: ext3 mount failing due to bad superblock.

[Curt]

On 2013-11-09, darkestkhan  wrote:

> I created ext3 on sda1 (using mke2fs -j) and it worked for last 20 days.
> But after tiday reboot it stopped working - if it would be bad entry in fstab
> I would still be able to mount it by hand, but I can't. I have some data
> on it that I would rather not lose (I don't have enough space to make backups
> of everything). Here is dmesg | tail output:
>
> "
> [  500.130158] EXT4-fs (sda1): VFS: Can't find ext4 filesystem
> "

Is this of any help?

http://linuxexpresso.wordpress.com/2010/03/31/repair-a-broken-ext4-superblock-in-ubuntu/

Summary:

Says to do:

mke2fs -n /dev/sda1

to discover where the superblock backups are stored
then to replace the bad superblock

e2fsck -b block_number /dev/sda1

'block_number' being the first backup block number in the mke2fs -n
output.

Excuse me if this is all off the mark.







-- 
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/slrnl7s23f.22t.cu...@einstein.electron.org

Re: gschem for Debian 7?

[Joe]

On Fri, 8 Nov 2013 18:56:09 -0800
cono...@rahul.net (John Conover) wrote:

> Where is the .deb for gschem for Debian 7?
> 

Renamed:

http://packages.debian.org/wheezy/geda-gschem

-- 
Joe


-- 
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/20131109103930.5590b...@jretrading.com

Thank you - was [Re: Permission issue]

[Richard Owlett]

Richard Owlett wrote:

My dual boots Squeeze and Wheezy.
I've created a partition whose function in life is to be
essentially a scratch pad for all groups/users of both.
How do I force all files to be written to that partition to be
readable AND writable to everybody?




Thank you Siard and David.I think I now know what is happening 
and why.




--
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/527e243e.8080...@cloud85.net

Re: Why Debian

[D.E. Bil]

On Sat, Nov 09, 2013 at 05:40:06AM -0200, Beco wrote:
> On 8 Nov 2013 14:15, "Alberto Salvia Novella" 
> wrote:
> > Summarizing:
> >
> > Which are the very important reasons why do you prefer Debian over
> > Ubuntu?
> >
>
> Why to use a Debian based OS if you can use Debian?

Exactly. Ubuntu has changed a lot from being just Debian with a
brown theme, and not in a good way, IMO. It seems that being GNU/Linux
is not trendy enough for Canonical, and being free (as in beer) is
what people are after. Catering for possible MS immigrants? Anyway, it
surely drives away more seasoned users with different values and
mindset.

Linux Mint? It's pretty much a green Ubuntu with a different UI and
its own repositories enabled (with all kinds of non-free cruft
installed by default).

Debian GNU/Linux is community driven distribution that values "free
as in freedom" more than most big distros out there. Also, it's light,
customizable, supports more architectures than any other, doesn't hold
your hand too tight, has DFSG and social contract, stays out of the
way, does all that and more, and is still stable as a rock. (And I'm
running a mixed testing/unstable/experimental system.)

-- 
debil
:wq


-- 
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/20131109133447.GA1394@canavanofcanmake.Noise

Re: Why Debian

[legacy daily]

I use Debian because it has stayed true to its principles and because its
principles are sound. If innovation is what Ubuntu is after, let them
contribute their innovation to Debian or upstream projects like the kernel
or GNU or Gnome or XFCE or so many others. They want to be become RedHat
alternative? Let them contribute to Fedora. They want to make money? We
already have Apples and Microsofts and those have plenty of fans.

I haven't found a single advantage of using Ubuntu or Linux Mint over
Debian but plenty of issues instead. Their most visible recent "innovation"
Unity with its Amazon and other search results and privacy holes made me
realize even more just how valuable Debian is. Their shift in release
support makes something fairly useless even more useless. Fedora does a
decent job if one wants to reinstall their system periodically and stay on
the bleeding edge. Arch or Testing/Experimental do an even better job if
one wants to be on the bleeding edge.

Debian just works! Once configured this system delivers day after day after
day. I wish I had enough time to devote a good chunk to maintaining,
testing, and improving Debian. Unfortunately, for now I can just add to it
by using it and talking about it with friends and colleagues.

Xubuntu does a nice job with themes so does Linux Mint but why don't they
just try to add their themes to Debian instead? Debian has plenty of room
for anyone to contribute. If you have cycles and feel that you can improve
something, please consider contributing to Debian - Ubuntu will get it for
free and so will Linux Mint. You'll have improved many distributions and
not just the one that seems to switch principles every few months.

Regards,
Gevorg



- ld

http://legacydaily.com


On Fri, Nov 8, 2013 at 12:57 PM, Alberto Salvia Novella <
es204904...@gmail.com> wrote:

> Note: Since I'm not subscribed to this mailing list at the moment, please
> send also a copy to my email when replying.
> --
>
> Normally I write very short, like a Haiku  Haiku>; but I think this letter shall be the exception. So excuse me 😳
>
>
> ***
>  THE HISTORY
> ***
>
> My name is Alberto Salvia Novella .
> Till 2008 I investigated how to create a Windows based reliable desktop
> computer system, till I did it and I realized nearly no one else will be
> able to do it without expending great amounts of time and money.
>
> One night I dreamed I had a very old looking but robust operating system
> installed on my computer, and eventually realized that what I should do is
> to look for something that was like what I saw. Although at the time I
> didn't know a thing about any other operating systems different to Windows
> or even libre software, I downloaded and tried in deep about fifty
> different operating systems from the time intensively for three years.
>
> Without reading a line of other people opinion, it seemed to me at the
> time Ubuntu was by far the best option in overall. But latter it went very
> buggy, and I began to pose myself why was that. What seemed more probable
> to me is Canonical chose to make radical decisions and, rowing against
> tide, selected to do something very different from what other distributions
> had done to the moment; in order to discover how they could make libre
> software to grow in popularity.
>
> Being between jumping to other distribution (Debian or Mageia) and giving
> this mind scope of Canonical a try, I decided five months ago the best
> action I could do was to get more involved with the project and empower it
> from its roots; and see what will happen and what the real problems are.
>
> After five months; the latest project coordinator of the "One Hundred
> Papercuts " project, from
> Canonical, has asked me to take on the project. So; with the help of the
> team; I have redesigned branding and project goals, and have make a serious
> commitment to make it shine  20Hundred%20Papercuts/One%20Hundred%20Papercuts%20will%
> 20make%20Ubuntu%20shine>.
>
>
> 
>  THE POINT
> 
>
> The point is yet very simple: I suspect Debian has a mindset that makes it
> stand out, I can imagine what kind of values these are, and I want them to
> become widespread. And now I feel I have the opportunity to show and
> convince the Ubuntu community to adapt them, and probable with it many
> people around the world.
>
> So I wanted to ask you the following question so it can't be said it's
> only my imagination. Summarizing:
>
> Which are the very important reasons why do you prefer Debian over Ubuntu?
>
>
> --
> Thank you for your help.
>
>
> --
> 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/527d2618.30...@gmail.com
>
>

Re: Weird boot problem. How can this be?

[didier gaumet]

Le 09/11/2013 09:26, Ray Dillinger a écrit :
[...]
> I don't understand how it can possibly happen, because I have completely
> unplugged
> that hard drive, flashed the BIOS of the machine with the most recent
> update
[...]

Asus website says that Bios rev <= 1203 needs to be converted by an
utility program before being updated

> The machine is an Asus Sabertooth X79 motherboard, IA64 "Sandy Bridge"
> architecture,
[...]

On the Asus website, this is not an IA64 motherboard, but a X86-64
(amd64) one. Trying an amd64 version of Debian could help...


-- 
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/l5lflg$9kh$1...@ger.gmane.org

Re: Why Debian

[Mike McGinn]

I use debian because I used to use Kubuntu. I started with Mandrake, watched 
it become Mandriva, tried 'buntu with 7.04.

I loved it. It worked great, the community was great. I was an LTS guy, don't 
like the six month upgrade cycle. I have other things to do with my system 
rather than install software and upgrade it. My computer is a tool, not my 
life.

Than the quality of the releases kept getting worse - even the LTS releases. 
It was as if the Cannonical QA Department was partying all the time. Also 
there was the whole Kmail-Akanodi-Nepomuk fiasco going on with the Kmail 
developers (NOT 'buntu's fault). If I went beyond 10.04 on Kubuntu I would 
have to migrate over 10 years of email from kmail to something else. 

Don't want to do that.

So I got acquainted with Squeeze and later Wheezy. I am happy. I can do my 
work and other things. I don't get a kernel update every two weeks. Hibernate 
works on my laptop (another 'buntu hit or miss). I have 46 days of uptime on 
the laptop I lug everywhere. 

I will stay with Debian because once I get it set up the way I want it, it 
stays out of my way.

Mike

On Saturday, November 09, 2013 09:00:36 legacy daily wrote:
> I use Debian because it has stayed true to its principles and because its
> 
> 
> 
> - ld
> 
> http://legacydaily.com
> 
> 
> On Fri, Nov 8, 2013 at 12:57 PM, Alberto Salvia Novella <
> 
> es204904...@gmail.com> wrote:
> > Note: Since I'm not subscribed to this mailing list at the moment, please
> > send also a copy to my email when replying.
> > --
> > 
> > Normally I write very short, like a Haiku  > Haiku>; but I think this letter shall be the exception. So excuse me 😳
> > 
> > 
> > ***
> > 
> >  THE HISTORY
> > 
> > ***
> > 
> > My name is Alberto Salvia Novella .
> > Till 2008 I investigated how to create a Windows based reliable desktop
> > computer system, till I did it and I realized nearly no one else will be
> > able to do it without expending great amounts of time and money.
> > 
> > One night I dreamed I had a very old looking but robust operating system
> > installed on my computer, and eventually realized that what I should do
> > is to look for something that was like what I saw. Although at the time
> > I didn't know a thing about any other operating systems different to
> > Windows or even libre software, I downloaded and tried in deep about
> > fifty different operating systems from the time intensively for three
> > years.
> > 
> > Without reading a line of other people opinion, it seemed to me at the
> > time Ubuntu was by far the best option in overall. But latter it went
> > very buggy, and I began to pose myself why was that. What seemed more
> > probable to me is Canonical chose to make radical decisions and, rowing
> > against tide, selected to do something very different from what other
> > distributions had done to the moment; in order to discover how they
> > could make libre software to grow in popularity.
> > 
> > Being between jumping to other distribution (Debian or Mageia) and giving
> > this mind scope of Canonical a try, I decided five months ago the best
> > action I could do was to get more involved with the project and empower
> > it from its roots; and see what will happen and what the real problems
> > are.
> > 
> > After five months; the latest project coordinator of the "One Hundred
> > Papercuts " project, from
> > Canonical, has asked me to take on the project. So; with the help of the
> > team; I have redesigned branding and project goals, and have make a
> > serious commitment to make it shine  > 20Hundred%20Papercuts/One%20Hundred%20Papercuts%20will%
> > 20make%20Ubuntu%20shine>.
> > 
> > 
> > 
> > 
> >  THE POINT
> > 
> > 
> > 
> > The point is yet very simple: I suspect Debian has a mindset that makes
> > it stand out, I can imagine what kind of values these are, and I want
> > them to become widespread. And now I feel I have the opportunity to show
> > and convince the Ubuntu community to adapt them, and probable with it
> > many people around the world.
> > 
> > So I wanted to ask you the following question so it can't be said it's
> > only my imagination. Summarizing:
> > 
> > Which are the very important reasons why do you prefer Debian over
> > Ubuntu?
> > 
> > 
> > --
> > Thank you for your help.
> > 
> > 
> > --
> > 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/527d2618.30...@gmail.com
-- 
Mike McGinn KD2CNU
Ex Uno Plurima
No electrons were harmed in sending this message, some were inconvenienced.
** Registered Linux User 377849


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Co

Re: ext3 mount failing due to bad superblock.

[David F]

On 11/09/2013 04:09 AM, darkestkhan wrote:
> Funny thing (actually not so) - my optic drive is dead. But why do I
> have to reboot
> into recovery mode? System itself works correctly - /boot is on sda2
> and everything
> else is on LVM at sda3

If I understand you correctly that you can boot and use your system without
using the affected drive, then you don't need to boot from alternate media
to troubleshoot the filesystem; but I would still recommend it (can you boot
from a USB flash drive?).  If you must boot from the installed distro, it
might be better to boot in single-user ("recovery") mode.  The reason for
this is that most distributions are configured to automatically access
drives and filesystems, if only to probe them to determine what filesystems
are available.  In general, when troubleshooting filesystems and hard
drives, it's best only to access them in a very controlled way.  But please
consider using a live boot distribution that is specifically tailored for
this kind of work, such as parted magic, system rescue cd, etc.

You haven't given enough information, so it's hard to say for sure what is
the problem, forcing us to speculate heavily.  You should definitely check
the SMART data on the drive (use smartmontools package) to determine the
status of the drive hardware.  The output of dumpe2fs will be helpful.  Also
check your _entire_ kernel log, looking for any ATA or other errors that
would indicate drive/controller failures, as well as filesystem messages.
Nonetheless, there are 3 main possibilities:

A. hardware failure: your drive is hosed; there are a number of
sub-possibilities here: controller, cable, drive's controller card, drive
platter surface, drive head, etc.

B. software failure: the drive is working fine but somehow the data on it
became corrupted, either due to a bug in the filesystem software, through a
user-induced error such as writing to /dev/sdX, system crash, or some other
possibilities.

C. The filesystem is fine but you aren't mounting it correctly.  Are you
sure that you created an ext* filesystem and not some other kind?  Try using
mount without -t.  Are you sure that you're mounting the right device file?
 The right partition?

You will treat the A and B cases differently: if it's (A), I recommend
*against* trying to recover any data in-place as has been suggested in some
other posts here.  Running fsck on a dying drive can make the situation
worse (if you do it anyhow, try using the -c option as suggested elsewhere).
 You should rather make an image of the drive; you need some spare space on
which to make the image.  You can use something as simple as dd, but if you
encounter hardware errors while reading, try something like ddrescue.  If
you still have no luck, you can move the drive to a different machine or
even replace its on-drive controller card with one from an _identical_ model
-- I have successfully done this but it is difficult and not recommended
unless you have some _very_ valuable data on that drive.

>From then on, you can treat (A) and (B) more or less the same: you might use
fsck, debugfs, etc. on the filesystem, but before modifying it, you might
want to make a copy image [in case (A) a copy of the copy] before modifying
it -- or you might just run the tools in-place.  Hard to say with the
information you've provided, but from the sounds of it you may not have much
luck -- your filesystem sounds pretty sick.

If that's the case, you'll want to recover the contents rather than the
filesystem; tools like PhotoRec, foremost, scalpel [fork of foremost], etc.
will usually recover some of your files.  Lots of options here:
http://www.forensicswiki.org/wiki/Tools:Data_Recovery

I should mention that in case (B) [no hardware failure], if you just want to
jump to recovering the contents rather than the filesystem, it's not
critical to make a copy image; you can just recover straight from the hard
drive.

Good luck,
-- David


-- 
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/527e4ce8.4020...@meta-dynamic.com

Re: Why Debian

[Conrad Nelson]

I left Ubuntu clear back in 2008 when I saw very clearly that their 
developers (Especially in Canonical.) were starting to care less and 
less and less about what their community actually wanted. I saw the 
disastrous integration of Pulseaudio and how the developers and various 
"authorities" on their forum seemed to shout down or even go out of 
their way to discredit or silence critics of that move.


They totally ignored the fact that Pulseaudio, especially back in 2008, 
caused more problems than it solved and was a blatant case of a solution 
looking for a problem (To this day I have no issues at all whatsoever 
with straight up ALSA and still see very little tangible advantage to PA.).


But I didn't hop to Debian, I switched to Arch. At the time it seemed 
like a lot of users, if they were leaving Ubuntu, they were jumping ship 
to Arch. And it was for good reason, it offered way more choice than 
Ubuntu, and the developers generally didn't go out of their way deciding 
for you what you want, unlike Canonical in Ubuntu. For a very long time 
I used Arch, then Gentoo, and am still a big fan of both, since as far 
as choices and flexibility go they are leagues ahead of anything Debian 
could pull off without overhauling APT.


I largely left Arch because instead of the typical "developers force 
their favorite software on me" situation it was a combination of "too 
much RTFM in the community/oodles of arrogance on the part of the 
developers." One thing they did I do like, ironically since my criticism 
of PA, is the switch to systemd. The reason I drifted away from Gentoo 
was a seeming lack of direction and that it was getting to be a lot of 
work keeping conflicts down with USE flags. Not to mention for a rolling 
release, Gentoo seemed to move at a glacial pace in updating software 
(This in contrast to Arch which is pretty quick to getting up to date 
with upstream and VERY good at keeping the result from being broken.)


The reason I use Debian now is that I do like APT, and because I got a 
lot less time to tinker and play with Arch and Gentoo. My current 
circumstances don't allow me the time to do pre/post-upgrade maintenance 
the way Arch and Gentoo demand.


I like Debian. My only real beef with it is the DFSG. Debian developers 
(And a lot of users.) operate a little too much under the assumption 
end-users actually care about things such as source code being available 
and I do think this is why Debian is kept from being as popular as it 
could be. Great for forking distributions off of, however. While 
certainly, as a programmer, I can appreciate having source code for the 
software I use, I am way more a follower of the Torvalds philosophy 
("Use what works best for you and your hardware." over the Stallman 
philosophy (The false notion that software being open source is some 
sort of moral issue.). You'll often see me on this mailing list ranting 
at someone who invokes "it's closed source, so it's automatically bad." 
Debian tends to go out of its way to appease the Free Software 
Foundation for zero benefit (Or respect from RMS.) whatsoever.


Perhaps my biggest technical gripe is a side effect of the Debian 
philosophy: Good luck ever actually installing Debian over a wireless 
network on their official media, as they shortsightedly decided that 
"philosophy" is more important than "install Debian on a laptop." 
Another gripe is how much they hold back mainstream Debian for their pet 
projects that stand very little chance of significant adoption (Debian 
kfreebsd: BSD is in a decline, and (Debian Hurd) I see very little point 
in Hurd, as the project is virtually dead.). This keeps Debian from 
switching to better stuff like systemd (Yes, I know systemd is in the 
repos.) that could make better use of the Linux kernel.


Conrad

On 11/08/2013 11:57 AM, Alberto Salvia Novella wrote:
Note: Since I'm not subscribed to this mailing list at the moment, 
please send also a copy to my email when replying.

--

Normally I write very short, like a Haiku 
; but I think this letter shall be 
the exception. So excuse me 😳



***
 THE HISTORY
***

My name is Alberto Salvia Novella 
. Till 2008 I investigated how 
to create a Windows based reliable desktop computer system, till I did 
it and I realized nearly no one else will be able to do it without 
expending great amounts of time and money.


One night I dreamed I had a very old looking but robust operating 
system installed on my computer, and eventually realized that what I 
should do is to look for something that was like what I saw. Although 
at the time I didn't know a thing about any other operating systems 
different to Windows or even libre software, I downloaded and tried in 
deep about fifty different operating systems from the time intensively 
for three years.


Without reading a line of other people opinion, it seemed to m

libpam-cap not working

[Lukas Erlacher]

Hello,

my first post to the debian user list for a quite vexing issue. I'm running 
debian squeeze.

I'm trying to get capabilities working along the lines of 
blog.fpmurphy.com/2009/05/linux-security-capabilities.html.

I installed libcap2 (1:2.22-1.2), libcap2-bin (1:2.22-1.2), and 
libpam-cap(1:2.22-1.2), and edited /etc/security/capbilities.conf in order to 
give the user luke the cap_net_raw capability.

Everything seems set up correctly according to this check:

luke@leda:~$ /sbin/capsh --decode=$(grep CapInh /proc/$$/status|awk '{print 
$2}')
0x2000=cap_net_raw

However, actually using the capability with a copy of the ping binary is 
impossible:

luke@leda:~$ ls -al ./ping 
-rwxr-xr-x 1 luke luke 36136 Nov  9 17:18 ./ping
luke@leda:~$ /sbin/getcap ./ping
./ping = cap_net_raw+ip
luke@leda:~$ ./ping localhost
ping: icmp open socket: Operation not permitted

As one can see, cap_net_raw is the capability required, since directly putting 
it into the effective capabilities works:

root@leda:~# setcap cap_net_raw=pie /home/luke/ping
luke@leda:~$ ./ping localhost
PING localhost (127.0.0.1) 56(84) bytes of data.
64 bytes from localhost (127.0.0.1): icmp_req=1 ttl=64 time=0.019 ms

My google-fu has failed to turn up anything other than an old bug report that 
didn't go anywhere: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=633991

Any help or pointers muchly appreciated.

Best regards,
Luke.


-- 
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/527e6d12.9020...@lerlacher.de

Re: Weird boot problem. How can this be?

[Ray Dillinger]

On 11/09/2013 06:08 AM, didier gaumet wrote:


The machine is an Asus Sabertooth X79 motherboard, IA64 "Sandy Bridge"
architecture,

[...]

On the Asus website, this is not an IA64 motherboard, but a X86-64
(amd64) one. Trying an amd64 version of Debian could help...


On the ASUS website the board has an Intel Chipset with LGA 2011 CPU socket:
https://www.asus.com/Motherboards/SABERTOOTH_X79/#overview

LGA 2011 is compatible with Intel 64-bit processors including "Sandy Bridge:"
https://en.wikipedia.org/wiki/LGA_2011

And that seemed to clinch it, except that the damn thing wasn't working, so I
went to a third source and discovered why I was wrong:
https://en.wikipedia.org/wiki/amd64

The news to me is that INTEL ever deigned to release something whose instruction
set is commonly known as AMD-anything.  I've been assuming that "Intel 64" would
be "IA64" instruction set and "AMD 64" would be "AMD64" instruction set.  So...

You're right.  I shouldn't have said "IA64" in the first place, to describe
either of the machines this is from.  I should have said "Intel 64-bit 
processor"
which I had been assuming was the same thing.  More to the point I should not 
have
downloaded the IA64 images.

Thank  you.

Ray


--
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/527e75c5.2010...@sonic.net

IPTables question

[Bill.M]

Hi folks,

In IPTables one can specify multiple addresses, and multiple ports, but 
is there anyway to specify multiple interfaces.


For example,  -m multiport --destination-port 22,25,80

Or-s 1.2.3.4,1.2.3.5,1.2.3.7 or -s 1.2.3.4:1.2.3.10

But is there anyway to specify both eth0 and wlan0 as equally valid 
interfaces on my laptop depending on whether it's in my dock or on the 
road?


For example, -i wlan0,eth0 or -o wlan0,eth0
Is something like these possible?

It would save quite a bit of work in having to write duplicate rules and 
probably impact efficiency as well. I've googled around quite a bit but 
can find no references to multiple interfaces.


b.


--
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/527e7517.9070...@uniserve.com

Re: Why Debian

[Nate Bargmann]

* On 2013 09 Nov 10:49 -0600, Conrad Nelson wrote:
> I like Debian. My only real beef with it is the DFSG. Debian
> developers (And a lot of users.) operate a little too much under the
> assumption end-users actually care about things such as source code
> being available and I do think this is why Debian is kept from being
> as popular as it could be. Great for forking distributions off of,
> however. While certainly, as a programmer, I can appreciate having
> source code for the software I use, I am way more a follower of the
> Torvalds philosophy ("Use what works best for you and your
> hardware." over the Stallman philosophy (The false notion that
> software being open source is some sort of moral issue.). You'll
> often see me on this mailing list ranting at someone who invokes
> "it's closed source, so it's automatically bad." Debian tends to go
> out of its way to appease the Free Software Foundation for zero
> benefit (Or respect from RMS.) whatsoever.

IMO, Debian does a good job providing, or at least staying out of one's
way, support for using non-DFSG software.  It may be a bit unfair to say
that "Debian goes out of its way to appease the Free Software Foundation
for zero benefit (Or respect from RMS.) whatsoever." as if that were
true, then various GNU documentation would not be placed in non-free
when it has opted to use certain aspects of the GNU Free Document
License.  DFSG is actually closer to the pragmatic Open Source
philosophy than the dogmatic Free Software philosophy, IMO.


> Perhaps my biggest technical gripe is a side effect of the Debian
> philosophy: Good luck ever actually installing Debian over a
> wireless network on their official media, as they shortsightedly
> decided that "philosophy" is more important than "install Debian on
> a laptop." Another gripe is how much they hold back mainstream
> Debian for their pet projects that stand very little chance of
> significant adoption (Debian kfreebsd: BSD is in a decline, and
> (Debian Hurd) I see very little point in Hurd, as the project is
> virtually dead.). This keeps Debian from switching to better stuff
> like systemd (Yes, I know systemd is in the repos.) that could make
> better use of the Linux kernel.

I'll agree that the installer could use some tweaking between the
technical and philosophical regarding wireless drivers.  I'm not a
Debian Developer so I don't have any idea what discussions/bug reports
have taken place in this area.  I do know that I've had to do the
initial install using the wired connection and then install the proper
kernel package to get the needed firmware.  Even with this
inconvenience, Debian doesn't just remove those parts and say, "Good
luck!"

As for the other architectures, so long as someone is willing to work on
keeping them current, I think the upside to having them is that it does
make for a more solid distribution and it helps upstream projects be
more portable and, as with several years ago with the SCO lawsuits,
should the unthinkable occur and the Linux kernel have some legal action
against it, the other kernels represent a fall-back position for Debian
and its community.  While that seems like a long shot these days, it may
be important in the future.

- Nate

-- 

"The optimist proclaims that we live in the best of all
possible worlds.  The pessimist fears this is true."

Ham radio, Linux, bikes, and more: http://www.n0nb.us


-- 
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/20131109180136.gh4...@n0nb.us

Re: Why Debian

[legacy daily]

DFSG rocks! FOSS is the right way. I use Debian strictly because of its 
adherence to these principles. There is plenty of dogma and bending of rules 
elsewhere. If it changes its principles it will be something else maybe Ubuntu 
or something else but not Debian any longer.

- ld

On Nov 9, 2013, at 1:01 PM, Nate Bargmann  wrote:

* On 2013 09 Nov 10:49 -0600, Conrad Nelson wrote:
> I like Debian. My only real beef with it is the DFSG. Debian
> developers (And a lot of users.) operate a little too much under the
> assumption end-users actually care about things such as source code
> being available and I do think this is why Debian is kept from being
> as popular as it could be. Great for forking distributions off of,
> however. While certainly, as a programmer, I can appreciate having
> source code for the software I use, I am way more a follower of the
> Torvalds philosophy ("Use what works best for you and your
> hardware." over the Stallman philosophy (The false notion that
> software being open source is some sort of moral issue.). You'll
> often see me on this mailing list ranting at someone who invokes
> "it's closed source, so it's automatically bad." Debian tends to go
> out of its way to appease the Free Software Foundation for zero
> benefit (Or respect from RMS.) whatsoever.

IMO, Debian does a good job providing, or at least staying out of one's
way, support for using non-DFSG software.  It may be a bit unfair to say
that "Debian goes out of its way to appease the Free Software Foundation
for zero benefit (Or respect from RMS.) whatsoever." as if that were
true, then various GNU documentation would not be placed in non-free
when it has opted to use certain aspects of the GNU Free Document
License.  DFSG is actually closer to the pragmatic Open Source
philosophy than the dogmatic Free Software philosophy, IMO.


> Perhaps my biggest technical gripe is a side effect of the Debian
> philosophy: Good luck ever actually installing Debian over a
> wireless network on their official media, as they shortsightedly
> decided that "philosophy" is more important than "install Debian on
> a laptop." Another gripe is how much they hold back mainstream
> Debian for their pet projects that stand very little chance of
> significant adoption (Debian kfreebsd: BSD is in a decline, and
> (Debian Hurd) I see very little point in Hurd, as the project is
> virtually dead.). This keeps Debian from switching to better stuff
> like systemd (Yes, I know systemd is in the repos.) that could make
> better use of the Linux kernel.

I'll agree that the installer could use some tweaking between the
technical and philosophical regarding wireless drivers.  I'm not a
Debian Developer so I don't have any idea what discussions/bug reports
have taken place in this area.  I do know that I've had to do the
initial install using the wired connection and then install the proper
kernel package to get the needed firmware.  Even with this
inconvenience, Debian doesn't just remove those parts and say, "Good
luck!"

As for the other architectures, so long as someone is willing to work on
keeping them current, I think the upside to having them is that it does
make for a more solid distribution and it helps upstream projects be
more portable and, as with several years ago with the SCO lawsuits,
should the unthinkable occur and the Linux kernel have some legal action
against it, the other kernels represent a fall-back position for Debian
and its community.  While that seems like a long shot these days, it may
be important in the future.

- Nate

-- 

"The optimist proclaims that we live in the best of all
possible worlds.  The pessimist fears this is true."

Ham radio, Linux, bikes, and more: http://www.n0nb.us


-- 
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/20131109180136.gh4...@n0nb.us


--
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/82195cc7-eea4-4fcc-9e22-962b8e193...@gmail.com

Audio anomaly in Wheezy

[L V Gandhi]

I have Asus Vivobbok S400CA multibooting win8.1, debian KDE wheezy and
mavericks.
In Debian I have peculiar problem regarding Mic.
Speaker works ok. But Mic does not work in skype even in full volume
increase effected normal KDE mixer in task bar or pavucontrol.
However after starting audacity, Mic starts working.
This I have tested a few times.
Why it happens? Why initially Mic does not work
-- 
L V Gandhi

Re: IPTables question

[David F]

On 11/09/2013 12:47 PM, Bill.M wrote:
> But is there anyway to specify both eth0 and wlan0 as equally valid
> interfaces on my laptop depending on whether it's in my dock or on the road?
>
> For example, -i wlan0,eth0 or -o wlan0,eth0
> Is something like these possible?

* You can avoid specifying any interface at all, so long as you don't mind
the rule being applied to the loopback interface as well.  Chances are very
good that this will work for you and is the best solution, but you need to
evaluate the rules in question.

* You can use a '+' at the end of the interface name which acts as a
wildcard.  This won't help since your interfaces names differ in the first
character, not the last, but you can easily customize their names to differ
in their suffix rather than prefix by editing:
/etc/udev/rules.d/70-persistent-net.rules

* You can create a new chain, have packets from either interface jump to it
via two rules, then put the rest of your rules in that chain, without
specifying an interface name.

e.g. (untested):
iptables -t filter -N foo
iptables -t filter -A INPUT -i eth0  -j foo
iptables -t filter -A INPUT -i wlan0 -j foo
iptables -t filter -A foo --src 1.2.3.4 -j DROP
iptables -t filter -A foo -p tcp --dport 80 -j DROP
...

-- David


-- 
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/527e99f5.8070...@meta-dynamic.com

Re: Why Debian

[Beco]

On 9 November 2013 06:40, Itay  wrote:
> On Sat, 9 Nov 2013, Alberto Salvia Novella wrote:
>> So you feel more vanilla is better, is this?
>
>
> I prefer chocolate... ;-)

I second that.

> But the good thing in Debian for me is: I feel that once Ilearn to do
> something, the knowledge will stay with me, and will be relevant for quite
> some time in the future.

And specially that.

>
> Hope this helps.
> Itay

My best,
Beco.



-- 
Dr Beco
A.I. researcher

"For the things we have to learn before we can do them, we learn by
doing them" (Aristotle)


-- 
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/CALuYw2z1PkZVyOPQFVb2ASCqxkSByRLPx5EQEaN6k=jj4+m...@mail.gmail.com

Re: Why Debian

[Chris Bannister]

On Sat, Nov 09, 2013 at 11:40:04AM +0200, Itay wrote:
> Yes, I have to sweat on doing simple things, like configuring exim4
> to send out email to my public address.

You'll have that problem no matter what distribution you choose.

> But the good thing in Debian for me is: I feel that once Ilearn to
> do something, the knowledge will stay with me, and will be relevant
> for quite some time in the future.

Again, I don't think that is distribution specific.

-- 
"If you're not careful, the newspapers will have you hating the people
who are being oppressed, and loving the people who are doing the 
oppressing." --- Malcolm X


-- 
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/20131109210344.GB12850@tal

Grub, Raid, LVM

[PaulNM]

Hi Folks,

I've been dealing with a frustratingly vexing issue for a while, and am
at a loss on where to go next.

Basically, We have a 8x 3TB drive system that I'm trying to install
Wheezy on.  During the install each drive is partitioned with a 1MB BIOS
Boot partition, followed by a RAID partition taking up the rest of the
space.  The 8 RAID partitions are made into a RAID6 array (8 active, 0
spare), which is used for a volume group. Two logical volumes (for now)
are in there, for / and swap. (/ is ext4)

When ever I try to boot the system, I'm stuck at the grub rescue prompt
after Grub spits out "error: no such disk.". Doing ls shows all eight
drives (hd0) as well as their associated partitions (hd3,gpt2).  Unlike
the multiple VMs of this setup that I've created on my laptop, there are
no (md) or (Logical-Volume-Name) entries.  Prefix and Root are set to
(LV-OS), and attempts to set them to other values fail.

I've also attempted an identical install, but with a 200MB Raid
partition as the second partition, RAID1'd with ext2 /boot.  No
difference. (Actually, the installer fails to use it.  I've manually
copied the files and edited fstab. Updating/reinstalling grub afterwards
gets the same result.)

Every VM I've created works with no problems, but it always fails on
the actual hardware. Every theory I can come up with should also fail on
the VMs. Is there a way to make sure the bios boot partition is being
used? Would the fact that the physical install puts the usb drive as sda
be an issue?  I've tried editing device.map and updating/reinstalling
grub, but no dice.

It seems to me that for some reason Grub can't get to it's raid related
modules.  I've checked /boot/grub/grub.cfg. The auto-generated file does
contain all the insmod lines for raid, raid6rec,mdraid1x, lvm, a bunch
of part_gpt, and ext2.

Love to hear any ideas, no matter how far-fetched.

-PaulNM


-- 
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/527ea37d.7050...@paulscrap.com

Re: IPTables question

[Shawn Wilson]

Redhat has something called firewalld which generates rules based on zones. I 
don't use it because using dbus to help manage rules scares me. But it's there 
and could be what you want. 

David F  wrote:
>On 11/09/2013 12:47 PM, Bill.M wrote:
>> But is there anyway to specify both eth0 and wlan0 as equally valid
>> interfaces on my laptop depending on whether it's in my dock or on
>the road?
>>
>> For example, -i wlan0,eth0 or -o wlan0,eth0
>> Is something like these possible?
>
>* You can avoid specifying any interface at all, so long as you don't
>mind
>the rule being applied to the loopback interface as well.  Chances are
>very
>good that this will work for you and is the best solution, but you need
>to
>evaluate the rules in question.
>
>* You can use a '+' at the end of the interface name which acts as a
>wildcard.  This won't help since your interfaces names differ in the
>first
>character, not the last, but you can easily customize their names to
>differ
>in their suffix rather than prefix by editing:
>/etc/udev/rules.d/70-persistent-net.rules
>
>* You can create a new chain, have packets from either interface jump
>to it
>via two rules, then put the rest of your rules in that chain, without
>specifying an interface name.
>
>e.g. (untested):
>iptables -t filter -N foo
>iptables -t filter -A INPUT -i eth0  -j foo
>iptables -t filter -A INPUT -i wlan0 -j foo
>iptables -t filter -A foo --src 1.2.3.4 -j DROP
>iptables -t filter -A foo -p tcp --dport 80 -j DROP
>...
>
>-- David


-- 
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/b20675f7-67d9-4942-9dca-de4102336...@email.android.com

Re: IPTables question

[Pascal Hambourg]

Hello,

Bill.M a écrit :
> 
> In IPTables one can specify multiple addresses, and multiple ports, but 
> is there anyway to specify multiple interfaces.
> 
> For example,  -m multiport --destination-port 22,25,80
> 
> Or  -s 1.2.3.4,1.2.3.5,1.2.3.7 or -s 1.2.3.4:1.2.3.10

In addition to David's answer :
Unless recent change I am not aware of, you cannot specify an address
range in -s or -d. You must use the "iprange" match instead (or ipset if
your kernel supports it). Also, note that specifying multiple
comma-separated addresses or prefixes in -s or -d will result in
multiple rules being actually created, which can have undesirable
side-effects and impact efficiency.


-- 
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/527eb0fa.8080...@plouf.fr.eu.org

Re: Installing same packages in a Squeeze installation in a new Wheezy installation

[Dmitrii Kashin]

Bob Proulx  writes:

> Ken Heard wrote:
>
>> # dpkg --get-selections '*' > selection.dpkg
>
> That is definitely the old venerable way of doing this on Debian from
> a decade of years ago.  When working on the same version of Debian it
> even worked relatively well.  Then.  But now we have extended_states
> in APT supporting 'apt-get autoremove'.  With regards to that the
> above no longer works well.  For one problem it completely breaks the
> extended_states paradigm.
>
> The extended_states paradigm is to track for each package whether it
> was installed manually or installed as a dependency of another
> package.  If you install foo and foo depends upon libfoo then foo is
> marked as manual and libfoo is marked as automatic.

Yes. I have been skimming the whole thread for 10 minutes trying to know
if somebody remember about autoremove. So I am very glad to see your
letter. But I would like to append your answer.

I did a migration from Squeeze to Wheezy a while ago, getting the list
of manually installed packages by command:

% aptitude search '?installed ?not(?automatic)' | awk '{print $2}'

It is a very convenient way. And the only case I agree that aptitude is
useful.


pgpjxKYjwGTX8.pgp
Description: PGP signature

Re: Grub, Raid, LVM

[PaulNM]

On 11/09/2013 04:48 PM, Gary Dale wrote:
> On 09/11/13 04:05 PM, PaulNM wrote:
>> Hi Folks,
>>
>> I've been dealing with a frustratingly vexing issue for a while,
>> and am
>> at a loss on where to go next.
>>
>> Basically, We have a 8x 3TB drive system that I'm trying to install
>> Wheezy on.  During the install each drive is partitioned with a 1MB BIOS
>> Boot partition, followed by a RAID partition taking up the rest of the
>> space.  The 8 RAID partitions are made into a RAID6 array (8 active, 0
>> spare), which is used for a volume group. Two logical volumes (for now)
>> are in there, for / and swap. (/ is ext4)
>>
>> When ever I try to boot the system, I'm stuck at the grub rescue
>> prompt
>> after Grub spits out "error: no such disk.". Doing ls shows all eight
>> drives (hd0) as well as their associated partitions (hd3,gpt2).  Unlike
>> the multiple VMs of this setup that I've created on my laptop, there are
>> no (md) or (Logical-Volume-Name) entries.  Prefix and Root are set to
>> (LV-OS), and attempts to set them to other values fail.
>>
>> I've also attempted an identical install, but with a 200MB Raid
>> partition as the second partition, RAID1'd with ext2 /boot.  No
>> difference. (Actually, the installer fails to use it.  I've manually
>> copied the files and edited fstab. Updating/reinstalling grub afterwards
>> gets the same result.)
>>
>> Every VM I've created works with no problems, but it always fails on
>> the actual hardware. Every theory I can come up with should also fail on
>> the VMs. Is there a way to make sure the bios boot partition is being
>> used? Would the fact that the physical install puts the usb drive as sda
>> be an issue?  I've tried editing device.map and updating/reinstalling
>> grub, but no dice.
>>
>> It seems to me that for some reason Grub can't get to it's raid
>> related
>> modules.  I've checked /boot/grub/grub.cfg. The auto-generated file does
>> contain all the insmod lines for raid, raid6rec,mdraid1x, lvm, a bunch
>> of part_gpt, and ext2.
>>
>> Love to hear any ideas, no matter how far-fetched.
>>
>> -PaulNM
> 
> I know that Wheezy has no trouble booting from a RAID5 array occupying
> the entire disk partition (i.e. the partitions start after the GPT and
> occupy the entire rest of the disks).

Thanks Gary, that worked for me as well in earlier test VMs prior to
trying to install on the physical server. (Using RAID6) Everything I've
read says Wheezy is perfectly capable of doing what I've set up, others
have apparently done so, and it works perfectly fine in virtual machines.

> 
> My md0 device is partitioned without using LVM. In fact I've never
> really needed LVM so I can't comment on it. The partitions I have are
> named like md0p1, md0p2, etc.. This of course requires that device md0
> has a partition table.
> 
> 
> I'm confused by your comment that the installer fails to use the /boot
> partition you created. If you tell the installer to use a partition as
> /boot, it will do that.

Yeah, it's weird.  I've only tried a separate /boot twice. Once on the
physical server, where I only noticed during troubleshooting that the
/boot raid was empty, and the kernel/other files were in /boot on the
rootfs.

In the test VM afterwards, the installer did give a warning that it was
unable to mount /boot.  Maybe I missed it earlier?  Anyway, I shouldn't
need to use a separate boot, it works fine without it in VMs and other
reports online.  I only tried it for troubleshooting.


> 
> RAID does of course require that /etc/mdadm/mdadm.conf be populated with
> the correct RAID information and that the initramfs has the necessary
> modules. Grub also needs to be updated to include the correct boot
> information.
> 
> The lack of grub md names suggests that it doesn't know about your RAID
> setup. update-initramfs -u && update-grub may fix that. Also, make sure
> that grub is actually installed on the RAID array.

Hmm, my first thought was initramfs only has to do with the kernel, and
not grub.  That said, maybe grub does look at the initramfs config for
hints. Certainly worth a look the next time I have my hands on the
hardware.  I've installed grub to the harddrives, sdb to sdi, not just
during install, but again via chroot after booting rescue mode from the
installer.

Still curious as to why it works fine in VMs, though. I'm even using
SATA and not Virtio (KVM/Qemu), as well as identically sized "disks".

Also still open to other ideas and suggestions to try.  If nothing works
the next time I'm on the hardware (likely Tuesday), we're going to just
plug a usb flash drive in an internal usb port and use that for the OS.
 (*Really* hoping to avoid that, though.)

-PaulNM


-- 
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/527eb693.8080...@paulscrap.com

Re: IPTables question

[Shawn Wilson]

Pascal Hambourg  wrote:
>Hello,
>
>Bill.M a écrit :
>> 
>> In IPTables one can specify multiple addresses, and multiple ports,
>but 
>> is there anyway to specify multiple interfaces.
>> 
>> For example,  -m multiport --destination-port 22,25,80
>> 
>> Or -s 1.2.3.4,1.2.3.5,1.2.3.7 or -s 1.2.3.4:1.2.3.10
>
>In addition to David's answer :
>Unless recent change I am not aware of, you cannot specify an address
>range in -s or -d. You must use the "iprange" match instead (or ipset
>if
>your kernel supports it). Also, note that specifying multiple
>comma-separated addresses or prefixes in -s or -d will result in
>multiple rules being actually created, which can have undesirable
>side-effects and impact efficiency.

The speed impact of a small rule set is negligible. One ipset vs 20 rules, yes 
please - it's easier to look at. Also, idk any way to match interface with 
ipset - ip and port (even src and dst in one line) but not interface. 


-- 
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/4d539f94-5809-483f-bfa8-fc50e6e73...@email.android.com

Re: Why Debian

[Lisi Reisz]

On Friday 08 November 2013 17:57:44 Alberto Salvia Novella wrote:
> Which are the very important reasons why do you prefer Debian over
> Ubuntu?


I know it will sound silly, but one of the reasons that I don't use 
Ubuntu is that I simply don't like it.  This is much more at a gut 
level and instinctive than a thought out reaction.


I have tried to come to terms with it: there are those who love it, so 
there must be something to it.  My initial reaction was, I am sure, 
initiated by my reaction to the ghastly colour.  This is not a good 
reason for disliking a distro, but it certainly affected my initial 
reaction.

Then it never worked for me.  Debian, I could just install and it Just 
Worked®.  Ubuntu and the other *buntus were a pain to install.  They 
started out by refusing to work on my video set-up and moved on from 
there.  I was told that of course it worked; all I had to do was 
tweak this, adjust the other and tinker with this.  Erm Why?  Why 
should I lay up problems for myself by using a distro that I do not 
even like?

I said to one afficionado that Ubuntu didn't like me.  He said that 
Ubuntu would never love me until I first loved it.

Well, I don't love it and I am happy without it.

I approved of it enormously when Mark Shuttleworth first set it up.  
But I didn't and don't like the result.  I don't like the ethos.  I 
don't like the constant instability.  It releases buggy software, and 
by the time some of the bugs have been ironed out it is time for the 
next release.  I acknowledge that they have recently done something 
about this.  But I dislike the ethos more not less.

Debian, I love.  It can be all things to all men (or women!).  It is 
stable, or unstable and bang up to date, as I choose.  I like the 
ethos.  I like the community.  I like the quality of the help 
available and freely given.  This is evidenced by the fact that we 
often get Ubuntu users coming onto the Debian list to ask for help.

And I like the quality of the distro and all the other available 
software in the repositories.  I was sad when they took all non-free 
software out of the installer, because it is necessary to install 
network drivers before doing a net install:  that applies to newer 
Ethernet cards as well as to wireless ones.  I rapidly realised, 
however, that there is a very simple solution.  I open the box, 
insert an old ethernet card, do my network installation, load the 
drivers for the card(s) belonging to the box, remove the old card.

So far I have never had a serious problem with Debian and hardware, 
even though my husband and I have new computers, and his was bang up 
to date when I bought it.  He also wanted Old Stable, and I could 
still get his box to work.  All the problems that Google and the FM 
couldn't solve, this list has helped with.

A distro is a lot of things.  It is an operating system, a community, 
an attitude to life.  I like all of those in Debian.  Moreover, the 
commercial winds cannot blow cold and blow Debian away.


Lisi


--
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/201311092315.52649.lisi.re...@gmail.com

Re: IPTables question

[Pascal Hambourg]

Shawn Wilson a écrit :
> 
> Pascal Hambourg  wrote:
>>
>> Unless recent change I am not aware of, you cannot specify an address
>> range in -s or -d. You must use the "iprange" match instead (or ipset if
>> your kernel supports it).
> 
> Also, idk any way to match interface with ipset

I did not suggest ipset for such purpose.


-- 
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/527ebf36.5010...@plouf.fr.eu.org

Re: Grub, Raid, LVM

[Tom H]

On Sat, Nov 9, 2013 at 9:05 PM, PaulNM  wrote:
>
> I've been dealing with a frustratingly vexing issue for a while, and 
> am
> at a loss on where to go next.
>
> Basically, We have a 8x 3TB drive system that I'm trying to install
> Wheezy on.  During the install each drive is partitioned with a 1MB BIOS
> Boot partition, followed by a RAID partition taking up the rest of the
> space.  The 8 RAID partitions are made into a RAID6 array (8 active, 0
> spare), which is used for a volume group. Two logical volumes (for now)
> are in there, for / and swap. (/ is ext4)
>
> When ever I try to boot the system, I'm stuck at the grub rescue 
> prompt
> after Grub spits out "error: no such disk.". Doing ls shows all eight
> drives (hd0) as well as their associated partitions (hd3,gpt2).  Unlike
> the multiple VMs of this setup that I've created on my laptop, there are
> no (md) or (Logical-Volume-Name) entries.  Prefix and Root are set to
> (LV-OS), and attempts to set them to other values fail.
>
> I've also attempted an identical install, but with a 200MB Raid
> partition as the second partition, RAID1'd with ext2 /boot.  No
> difference. (Actually, the installer fails to use it.  I've manually
> copied the files and edited fstab. Updating/reinstalling grub afterwards
> gets the same result.)
>
> Every VM I've created works with no problems, but it always fails on
> the actual hardware. Every theory I can come up with should also fail on
> the VMs. Is there a way to make sure the bios boot partition is being
> used? Would the fact that the physical install puts the usb drive as sda
> be an issue?  I've tried editing device.map and updating/reinstalling
> grub, but no dice.
>
> It seems to me that for some reason Grub can't get to it's raid 
> related
> modules.  I've checked /boot/grub/grub.cfg. The auto-generated file does
> contain all the insmod lines for raid, raid6rec,mdraid1x, lvm, a bunch
> of part_gpt, and ext2.

1) Did you install grub on all the drives?

2) At the grub prompt, does "lsmod" list lvm, mdraid*, and raid*? If
the output goes off-screen, you'll need to run "set pager=1" first.

3) Boot from a Debian installation cd into rescue mode or from a live
cd (and install mdadm and lvm2), download bootinfoscript, and run it.
RESULTS.txt should give you a better idea of where grub is installed,
etc. Run grub-probe while chrooted; it should also tell you whether
grub is detecting your disks, partitions, raid volumes, and LVM
volumes.

3) Re-install grub with 'grub-install --modules "space-separated list
of lvm and raid modules" /dev/sdX', although it shouldn't be necessary
to ask grub-install to preload a module because AIUI grub-install
determines automatically what modules to include in core.img. Too bad
there isn't a grub utility to determine which modules are included in
this image. There's also a GRUB_PRELOAD_MODULES variable that you can
set in "/etc/default/grub" and the included modules will be loaded as
early as possible; you might want to try that first. (I've never used
this variable.)


-- 
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/CAOdo=syjq4_cvwhrya1aruekmunndy9nnhq8m115xpvtsdk...@mail.gmail.com

Re: Grub, Raid, LVM

[Tom H]

> On 11/09/2013 04:48 PM, Gary Dale wrote:
>> On 09/11/13 04:05 PM, PaulNM wrote:
>>
>> The lack of grub md names suggests that it doesn't know about your RAID
>> setup. update-initramfs -u && update-grub may fix that. Also, make sure
>> that grub is actually installed on the RAID array.
>
> Hmm, my first thought was initramfs only has to do with the kernel, and
> not grub. That said, maybe grub does look at the initramfs config for
> hints. Certainly worth a look the next time I have my hands on the
> hardware. I've installed grub to the harddrives, sdb to sdi, not just
> during install, but again via chroot after booting rescue mode from the
> installer.

The lack of mdraid and lvm names at the grub prompt is before the
initramfs comes into play. It's "just" a question of the relevant grub
modules not being present and active.

Maybe the preload variable that I referred to earlier is all that's needed.


-- 
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/CAOdo=Szk=ey_kpgjjo9_bkbqekpcsw8uyyw2q94-l-gb4nw...@mail.gmail.com

Re: Installing same packages in a Squeeze installation in a new Wheezy installation

[Bob Proulx]

Dmitrii Kashin wrote:
> Bob Proulx writes:
> > Ken Heard wrote:
> > in APT supporting 'apt-get autoremove'.  With regards to that the
> > above no longer works well.  For one problem it completely breaks the
> > extended_states paradigm.
> >
> > The extended_states paradigm is to track for each package whether it
> > was installed manually or installed as a dependency of another
> > package.  If you install foo and foo depends upon libfoo then foo is
> > marked as manual and libfoo is marked as automatic.
> 
> Yes. I have been skimming the whole thread for 10 minutes trying to know
> if somebody remember about autoremove. So I am very glad to see your
> letter. But I would like to append your answer.
> 
> I did a migration from Squeeze to Wheezy a while ago, getting the list
> of manually installed packages by command:
> 
> % aptitude search '?installed ?not(?automatic)' | awk '{print $2}'

Ah, very good.

> It is a very convenient way. And the only case I agree that aptitude is
> useful.

In Wheezy 7 and later there is now the apt-mark command with the
showmanual action.  (Squeeze 6 has apt-mark but not showmanual.)

  apt-mark showmanual

Much less typing now and perhaps quite a bit faster too. :-)

Bob


signature.asc
Description: Digital signature

Re: Why Debian

[green]

Alberto Salvia Novella wrote at 2013-11-08 11:57 -0600:
> Which are the very important reasons why do you prefer Debian over Ubuntu?

If other responses to this query are an indication, Debian is
attractive to people who are interested in productivity and therefore
want stable "set and forget" software.

Debian is able to provide this because the Debian community (1) has a
strong commitment to "free and open source software" via the DFSG and
(2) is without commercial affiliation.  Both result in software
written and/or maintained *by the user* which will naturally be more
useful *to the user*.  *This is a major reason why software freeness
is important.*  Software written by a company will include features
that are useful to the company but forced onto the user without
consent and perhaps without knowledge.  This is what we see in Ubuntu
with the Amazon and privacy issues and probably lots of other issues
(eg. LTS instability and the frenzied release cycle).


signature.asc
Description: Digital signature

Re: libpam-cap not working

[Lukas Erlacher]

Correction...

On 09.11.2013 18:12, Lukas Erlacher wrote:
> Hello,
> 
> my first post to the debian user list for a quite vexing issue. I'm running 
> debian squeeze.
> 

I'm running wheezy, of course.

root@leda:~# lsb_release -a
No LSB modules are available.
Distributor ID: Debian
Description:Debian GNU/Linux 7.2 (wheezy)
Release:7.2
Codename:   wheezy

> I'm trying to get capabilities working along the lines of 
> blog.fpmurphy.com/2009/05/linux-security-capabilities.html.
> 
> I installed libcap2 (1:2.22-1.2), libcap2-bin (1:2.22-1.2), and 
> libpam-cap(1:2.22-1.2), and edited /etc/security/capbilities.conf in order to 
> give the user luke the cap_net_raw capability.
> 
> Everything seems set up correctly according to this check:
> 
> luke@leda:~$ /sbin/capsh --decode=$(grep CapInh /proc/$$/status|awk '{print 
> $2}')
> 0x2000=cap_net_raw
> 
> However, actually using the capability with a copy of the ping binary is 
> impossible:
> 
> luke@leda:~$ ls -al ./ping 
> -rwxr-xr-x 1 luke luke 36136 Nov  9 17:18 ./ping
> luke@leda:~$ /sbin/getcap ./ping
> ./ping = cap_net_raw+ip
> luke@leda:~$ ./ping localhost
> ping: icmp open socket: Operation not permitted
> 
> As one can see, cap_net_raw is the capability required, since directly 
> putting it into the effective capabilities works:
> 
> root@leda:~# setcap cap_net_raw=pie /home/luke/ping
> luke@leda:~$ ./ping localhost
> PING localhost (127.0.0.1) 56(84) bytes of data.
> 64 bytes from localhost (127.0.0.1): icmp_req=1 ttl=64 time=0.019 ms
> 
> My google-fu has failed to turn up anything other than an old bug report that 
> didn't go anywhere: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=633991
> 
> Any help or pointers muchly appreciated.
> 
> Best regards,
> Luke.
> 
> 


-- 
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/527eee41.5050...@lerlacher.de