Re: firefox-37, where to put

[Petter Adsen]

On Wed, 1 Apr 2015 22:54:02 -0400
Gene Heskett  wrote:

> Greetings all;
> 
> Iceweasel commited suicide when I was asked by my bank to delete its 
> history, so now all I get is a blank terminal screen that is using
> 100% of a cpu core until I kill it as root.  A total purge and
> reinstall didn't fix it.
> 
> Chromium seems incapable of performing an online credit card
> transaction. And crashes anytime I go to abcnews.go.com
> 
> So I just dl'd firefox-37 tarball for 64 bit linux and unpacked it
> into my home dirs bin subdir.  But thats likely not going to be great
> as it probably looks someplace else for its libraries & such.
> 
> So where is the std place it would normally live?  If it can still
> find the old iceweasel password cache, that would be a huge plus.

Just unpack it wherever you want it - /opt/firefox for example, and put
a symlink to the binary somewhere in your $PATH. It uses the
configuration and everything it can find in your home dir, so that
shouldn't be a problem.

Petter

-- 
"I'm ionized"
"Are you sure?"
"I'm positive."


pgpo2uAVhGaJm.pgp
Description: OpenPGP digital signature

Xorg -configure fails with "created screens does not match number of detected devices"

[venkat]

For last one week i am struggling to make my dual display work.
Earlier it was with 2.632 kernel and my previous mail thread "Upgrading 
guidance for Cedarview driver in Debian 6 - 2.6.32 Kernel" and various 
forums confirmed me that possibility of achieving with 2.6.32 is ZERO. .


Now the board has been updated with 3.4.106 kernel with wheezy.But, when 
i try to run Xorg -configure , it exits with an error message.

"created screens does not match number of detected devices"

Xorg -configure http://pastebin.com/G7sFuRYN

xorg.0.log : http://pastebin.com/68WQ8Zfv

My requirement does not even worry about screen resolution all i wanted 
is to control my X display like on/off


lspci info : http://pastebin.com/zBVesvmS

Board type : ATOM N2600

request some guidance and troubleshooting ideas,

Regards
Venkat.S


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

Archive: https://lists.debian.org/551cdcf0.2020...@vortexindia.co.in

Re: Dovecot .deb install broken...

[Bob Proulx]

Merlin at Dangerous Minds wrote:
> I just tried to install Dovecot for the first time.  It was on a virgin
> Ubuntu/Debian server (Version: 1:2.2.9-1ubuntu5) and the install failed.

Please note that Debian is not Ubuntu and Ubuntu is not Debian.

> After a bit of struggling I worked out that the install fails BY DESIGN.
> Spoke about this with a few people and we decided it was best to report this
> issue and request that you redesign the packing so it does not fail.  The
> reason it fails is as follows...

That's great.  Please do report the bug.  Buf please for the sake of
the kittens please report it to the Ubuntu bug tracker.  Or have the
decency to at least install Debian and try it there first.  Otherwise
why report it here?

Bob


signature.asc
Description: Digital signature

Re: [solved securely now??] What is the correct way to set encrypted swap with systemd?

[David Wright]

Quoting ~Stack~ (i.am.st...@gmail.com):
> On 04/01/2015 03:27 PM, David Wright wrote:
> > I don't recall seeing you post what you actually put into
> > /etc/crypttab to test PARTUUID, only the erroneous earlier versions
> > where you were still using swap's UUID.
> 
> Fair enough. Completely plausible I did something wrong as I haven't
> used PARTUUID's in my /etc/crypttab before.
> 
> 
> # blkid | grep sda3
> /dev/sda3: PARTUUID="0003efe2-03"
> 
> # grep swap /etc/crypttab
> # swap works.
> #sda3_crypt /dev/disk/by-id/ata-TOSHIBA_MK3259GSXP_42K5CE0TT-part3
> /dev/urandom cipher=aes-xts-plain64,size=256,swap
> # swap doesn't work.
> sda3_crypt PARTUUID=0003efe2-03 /dev/urandom
> cipher=aes-xts-plain64,size=256,swap

How about trying

sda3_crypt /dev/disk/by-partuuid/0003efe2-03 /dev/urandom 
cipher=aes-xts-plain64,size=256,swap

Cheers,
David.


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/20150402044544.gd24...@alum.home

Dovecot .deb install broken...

[Merlin at Dangerous Minds]

Greetings,

I just tried to install Dovecot for the first time.  It was on a virgin 
Ubuntu/Debian server (Version: 1:2.2.9-1ubuntu5) and the install 
failed.   After a bit of struggling I worked out that the install fails 
BY DESIGN.  Spoke about this with a few people and we decided it was 
best to report this issue and request that you redesign the packing so 
it does not fail.  The reason it fails is as follows...


When you install it asks you if you want to use self signed 
certificates.  I have certificates so I said, "No".  At the end of the 
install the script tries to start dovecot.  It cannot because the 
service does not have certificates so it fails.  This causes the script 
to abort and the other packages not to install and breaks the install 
process.  I had to purge dovecot, then install it with the self signed 
certificates.


So we have 2 issues here.  1.  Why allow people to not install 
certificates if it is just going to break the install and confuse them.  
2.  Why are you starting the service right after install when dovecot 
clearly requires manual configuration as part of the setup.


I recommend you resolve this by NOT starting the service as part of the 
install unless it is an upgrade and the service was already running.


~ Merlin


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

Archive: https://lists.debian.org/551cb147.8020...@dangerous-minds.com

Re: [solved securely now??] What is the correct way to set encrypted swap with systemd?

[Paul E Condon]

I read the prior discussion as taking for granted the idea that one
must have only one method of identifying individual partitions, and
that that method must be the latest to have arrived on the scene. For
example, if everyone else in the world accepts your idea that
LABEL=sda1 on the partition that was /dev/sda1 when Debian was
installed is something that should *not*be*done*, *then* I can be very
confident that my disk will not cause problems *because*of*an*identity*
*clash*. The whole scenario is false anyway. Who would let a disk
arrives at his facility in the hands of a stranger be *mount*ed
without first putting it in a USB disk carrier and using some system
tools to take a look at what is recorded on it?  And why would I offer
my disk to anyone without *telling* them how it is labeled?

I see the argument here, mine as well as yours, as a clash of wildly
imaginative false scenarios. 

Peace.

On 20150401_1619-0500, David Wright wrote:
> Quoting Paul E Condon (pecon...@mesanetworks.net):
> 
> > You can also use disk LABEL=. As implemented, the LABEL is actually
> > applied to individual partition. As long as every partition has a
> > different LABEL values there is no ambiguity. You only need to have
> > unique values for partitions that you feel you will be mounting and
> > umounting. Partitions with no LABEL value set never get compared by
> > LABEL value.
> 
> That may be a problem for anyone using wheezy as it only appears to
> have UUIDs and LABELs, and not PARTUUIDs and PARTLABELs available.
> As discussed, only PARTXXXs are persistent. (If ever I let the Debian
> installer loose on my labelled swap partition, I have to relabel it
> afterwards.)
> 
> > The system has always insisted on setting a unique UUID
> > value on every partition. Its done that way because of a design
> > decision of Debian developers.
> 
> The world has decided that, not just DDs.
> 
> > But it has a tiny flaw that you can
> > avoid by using LABEL values, which YOU can be sure are unique because
> > you didn't do repeats, whereas UUIDs are randomly generated and there
> > is a tiny, but non-zero chance of repeats for UUIDs.
> 
> Oh, please. "Assuming uniform probability for simplicity, the
> probability of one duplicate would be about 50% if every person on
> earth as of 2014 owned 600 million GUIDs." (Wikipedia)
> 
> What if you're running a disk farm of several thousand drives?
> No, LABELs don't scale well.
> 
> > If I read your message above, you are having trouble understanding how
> > to use the UUID/PARTUUID system for identifying partitions on disks.
> > I suggest that you don't need to use it, and if you don't use it you
> > don't need to understand it.
> 
> That's ok until Debian does something behind your back that catches
> you out. For example, GRUB uses UUIDs, whereas I prefer LABELs. But I
> have to understand what GRUB/Debian Installer/Upgrade is doing so I
> can mitigate the effects.
> 
> > I was once troubled by a similar situation when Debian first started to
> > use UUID, until I realized that for some disks, I had no intention
> > of ever changing the partion structure that was put there initially.
> 
> Hm. Never say never.

Yes.

> 
> > For disks that I did have some special use and some ideas about how
> > that special use might change in the future, I put LABEL=... on their
> > partitions and used LABEL= paradigm to identify the partitions. This
> > is what I do with all my external drives. And I put sticker on the
> > outside of the drive enclosure with the LABEL= value written with a
> > ball point pen on it. It is my personal responsibility to myself that
> > I never put the same LABEL= value on two different disks.
> 
> I agree. All my disks, internal and external are named and labelled
> just so. But I have so few, and all in different rôles. If I had lots,
> I wouldn't bother.
>
> > You can even
> > put a LABEL= value on the root system disk that is always /dev/sda1
> > during installation. I suggest that you use LABEL=sda1.
> 
> Bad idea. The names should not be loaded with extra meaning. My
> partition labelling *is* overloaded: mama01, 02 ... but I'm prepared
> to live with the necessary constraints: creating them in the correct
> order, and not resizing/creating new partitions afterwards unless I
> make a clean sweep of it.
> 
> What if you/(s)he were to take a disk labelled sda1 and put it in
> another computer to clone/recover/whatever it. Now it sits in a box
> where there's a /dev/sda1 and a /dev/sdb1 but the latter is called
> sda1. A recipe for disaster.
> 
> > As I see it, the only benefit that you the user get from using the
> > UUID/PARTUUID system is that if some Linux user is browsing through
> > the internals of what is written on your disk, he may wonder where
> > you got the software to do that and treat you with a little more
> > respect. Let me assure you, you are not Rodney Dangerfield
> 
> Eh?
A very wild scenario, not to be taken seriously

> 
> Cheers,
> David.
> 
> 

firefox-37, where to put

[Gene Heskett]

Greetings all;

Iceweasel commited suicide when I was asked by my bank to delete its 
history, so now all I get is a blank terminal screen that is using 100% 
of a cpu core until I kill it as root.  A total purge and reinstall 
didn't fix it.

Chromium seems incapable of performing an online credit card transaction. 
And crashes anytime I go to abcnews.go.com

So I just dl'd firefox-37 tarball for 64 bit linux and unpacked it into 
my home dirs bin subdir.  But thats likely not going to be great as it 
probably looks someplace else for its libraries & such.

So where is the std place it would normally live?  If it can still find 
the old iceweasel password cache, that would be a huge plus.

Thanks all.

Cheers, Gene Heskett
-- 
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Genes Web page 


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/201504012254.02774.ghesk...@wdtv.com

Re: [solved securely now??] What is the correct way to set encrypted swap with systemd?

[~Stack~]

On 04/01/2015 03:27 PM, David Wright wrote:
> I don't recall seeing you post what you actually put into
> /etc/crypttab to test PARTUUID, only the erroneous earlier versions
> where you were still using swap's UUID.

Fair enough. Completely plausible I did something wrong as I haven't
used PARTUUID's in my /etc/crypttab before.


# blkid | grep sda3
/dev/sda3: PARTUUID="0003efe2-03"

# grep swap /etc/crypttab
# swap works.
#sda3_crypt /dev/disk/by-id/ata-TOSHIBA_MK3259GSXP_42K5CE0TT-part3
/dev/urandom cipher=aes-xts-plain64,size=256,swap
# swap doesn't work.
sda3_crypt PARTUUID=0003efe2-03 /dev/urandom
cipher=aes-xts-plain64,size=256,swap





signature.asc
Description: OpenPGP digital signature

Re: [solved securely now??] What is the correct way to set encrypted swap with systemd?

[David Wright]

Quoting Paul E Condon (pecon...@mesanetworks.net):

> You can also use disk LABEL=. As implemented, the LABEL is actually
> applied to individual partition. As long as every partition has a
> different LABEL values there is no ambiguity. You only need to have
> unique values for partitions that you feel you will be mounting and
> umounting. Partitions with no LABEL value set never get compared by
> LABEL value.

That may be a problem for anyone using wheezy as it only appears to
have UUIDs and LABELs, and not PARTUUIDs and PARTLABELs available.
As discussed, only PARTXXXs are persistent. (If ever I let the Debian
installer loose on my labelled swap partition, I have to relabel it
afterwards.)

> The system has always insisted on setting a unique UUID
> value on every partition. Its done that way because of a design
> decision of Debian developers.

The world has decided that, not just DDs.

> But it has a tiny flaw that you can
> avoid by using LABEL values, which YOU can be sure are unique because
> you didn't do repeats, whereas UUIDs are randomly generated and there
> is a tiny, but non-zero chance of repeats for UUIDs.

Oh, please. "Assuming uniform probability for simplicity, the
probability of one duplicate would be about 50% if every person on
earth as of 2014 owned 600 million GUIDs." (Wikipedia)

What if you're running a disk farm of several thousand drives?
No, LABELs don't scale well.

> If I read your message above, you are having trouble understanding how
> to use the UUID/PARTUUID system for identifying partitions on disks.
> I suggest that you don't need to use it, and if you don't use it you
> don't need to understand it.

That's ok until Debian does something behind your back that catches
you out. For example, GRUB uses UUIDs, whereas I prefer LABELs. But I
have to understand what GRUB/Debian Installer/Upgrade is doing so I
can mitigate the effects.

> I was once troubled by a similar situation when Debian first started to
> use UUID, until I realized that for some disks, I had no intention
> of ever changing the partion structure that was put there initially.

Hm. Never say never.

> For disks that I did have some special use and some ideas about how
> that special use might change in the future, I put LABEL=... on their
> partitions and used LABEL= paradigm to identify the partitions. This
> is what I do with all my external drives. And I put sticker on the
> outside of the drive enclosure with the LABEL= value written with a
> ball point pen on it. It is my personal responsibility to myself that
> I never put the same LABEL= value on two different disks.

I agree. All my disks, internal and external are named and labelled
just so. But I have so few, and all in different rôles. If I had lots,
I wouldn't bother.

> You can even
> put a LABEL= value on the root system disk that is always /dev/sda1
> during installation. I suggest that you use LABEL=sda1.

Bad idea. The names should not be loaded with extra meaning. My
partition labelling *is* overloaded: mama01, 02 ... but I'm prepared
to live with the necessary constraints: creating them in the correct
order, and not resizing/creating new partitions afterwards unless I
make a clean sweep of it.

What if you/(s)he were to take a disk labelled sda1 and put it in
another computer to clone/recover/whatever it. Now it sits in a box
where there's a /dev/sda1 and a /dev/sdb1 but the latter is called
sda1. A recipe for disaster.

> As I see it, the only benefit that you the user get from using the
> UUID/PARTUUID system is that if some Linux user is browsing through
> the internals of what is written on your disk, he may wonder where
> you got the software to do that and treat you with a little more
> respect. Let me assure you, you are not Rodney Dangerfield

Eh?

Cheers,
David.


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/20150401211903.gb21...@alum.home

Re: Jessie: NIS breaks network ??

[Bob Proulx]

Joao Roscoe wrote:
> I'm preparing a new jessie box (test system, preparing for deploying as
> soon as it gets into stable).

Jessie implies that you are using default that I cannot name for fear
of starting a flamewar.  But it hasn't been heavily tested in
conjuction with NIS/yp.

> Installed the base system, with kde and gnome, and included a small script
> in /etc/NetworkManager/dispatcher.d to set hostname and hosts files with
> info from DHCP. Worked nicely.

I have worked in an environment that dynamically set the hostname
based upon dhcp name.  That was quite the nightmare in many ways
because machine dhcp239 would report a failing component.  Where is
it?  What does it do?  Who's system is it?  Things were much better
after the dynamic naming was abandoned and static naming was resumed.
I avoid dynamically named systems except in special circumstances.
Although that is not your current problem.  Obviously you like it that
way or you wouldn't have done it that way.

The problems with NetworkManager are legion.  I always remove
NetworkManager from my systems.  That improves the reliability of the
networking on my systems.  That by itself will likely fix your system
so that networking starts reliably.  But on your systems it would
likely not be easily possible.  Therefore for you I recommend simply
configuring it off and avoid it that way.

> So, I installed NIS, and except for a small delay everything was still ok.
> ypwhich returned one of NIS servers (it took about two seconds, but
> succeeded). Restarted autofs, and all filesystems came up nicely. System
> was fast and responsive.

I am a long time user and admin for sites using NIS/yp, autofs, nis
groups, and other things in that space.  The way I configure those
systems is with /etc/network/interfaces for networking.  Depending
upon the system it is either dhcp or static and either works fine.
The interfaces are required to be up for the system and are therefore
marked with "auto" which is synchronous boot time configuration
instead of "allow-hotplug" which is hotplugged event driven.  The
"auto" instead of "allow-hotplug" is important for nis/yp as the
networking must be up and online all of the time for it to operate.
Hotplugged networking and nis/yp is not a good combination.  I am also
not using that other default which shall not be named.

> Then, I rebooted the box, and now It won't bring eth0 up anymore. Tried
> removing NIS, and networking got back to normal.
> 
> Could not understand the situation, so far.
> Any hints?

I would reconfigure /etc/network/interfaces for "auto" and restart.
Once an interface is configured in /e/n/interfaces then NetworkManager
should ignore that interface from then on.  I am hoping that will be
enough to solve your issue.

Since you are using NetworkManager I presume you want it and therefore
hopefully someone else using NIS/yp with NetworkManager will have
specific recommendations for that combination.  I fear that
combination is not very popularly used in the field.

Bob


signature.asc
Description: Digital signature

Re: [solved securely now??] What is the correct way to set encrypted swap with systemd?

[David Wright]

Quoting ~Stack~ (i.am.st...@gmail.com):
> On 03/29/2015 07:06 AM, Sven Hartge wrote:
> > ~Stack~  wrote:
> > 
> >> One more question if you don't mind: I understand why the encrypted
> >> partition UUID is going to change every time, but the physical
> >> partition UUID for my /dev/sda3 shouldn't change though. If they are
> >> the same systemd.fsck shouldn't have a problem with the physical
> >> partition UUID of /dev/sda3, but yet it does (at least for me). So
> >> what is the difference between the UUID pointing to /dev/sda3 and the
> >> /dev/disk/by-id pointing to /dev/sda3?
> > 
> > Please provide an example of such an UUID and the way you obtained it. 
> 
> Greetings Sven,
> 
> So something odd has happened...
> 
> # blkid |grep sda3
> /dev/sda3: PARTUUID="0003efe2-03"
> /dev/mapper/sda3_crypt: UUID="f4aad427-3462-4dcf-a40d-617e90a7b1cb"
> TYPE="swap"
> 
> # grep sda3 /etc/crypttab
> sda3_crypt /dev/disk/by-id/ata-TOSHIBA_MK3259GSXP_42K5CE0TT-part3
> /dev/urandom cipher=aes-xts-plain64,size=256,swap
> 
> That "PARTUUID" is odd because it used to be a UUID...huh...really not
> sure what happened...but I have a guess (below)...

I can't work out why your blkid | grep produces so little
output. Here's some of mine:

wheezy:
/dev/sda1: LABEL="gina01" UUID="a854f3b7-4ba1-4fa3-8d43-c150169c91a6" 
TYPE="ext4" 
/dev/sda4: LABEL="gina04" UUID="32e87272-a109-46ba-8914-c0b5374cb32e" 
TYPE="swap" 
/dev/sdb2: LABEL="mama02" UUID="2013-1105" TYPE="vfat" 
/dev/sdb4: LABEL="mama04" UUID="8561eb12-3ee8-42e1-a5c7-6d36fea217d3" 
SEC_TYPE="ext2" TYPE="ext3" 

jessie:
/dev/sda1: LABEL="john01" UUID="53515dcb-96fb-4c28-b456-1efbd1fdac38" 
TYPE="ext3" PARTUUID="c889c889-01"
/dev/sda4: LABEL="john04" UUID="876c1170-c64f-4fdf-aae2-a20e9c4a26f6" 
TYPE="swap" PARTUUID="c889c889-04"
/dev/sdb1: PARTLABEL="EFI" PARTUUID="d01dcc00-c77d-4e35-81d9-6ffc12536839"
/dev/sdb2: LABEL="mama02" UUID="2013-1105" TYPE="vfat" PARTLABEL="FAT32" 
PARTUUID="4123d2d5-b471-405e-90ed-76afea329c13"
/dev/sdb4: LABEL="mama04" UUID="8561eb12-3ee8-42e1-a5c7-6d36fea217d3" 
TYPE="ext3" PARTLABEL="m04" PARTUUID="5fabaa67-6f04-4d59-b797-e6fee7f4d454"

I don't suppose it's relevant in your case that wheezy is blind to
PARTxxx unlike jessie, so sdb1 doesn't even appear.

I prefer the output from /run/udev/data because, though much more
voluminous, the labelling is better:

S:disk/by-id/ata-ST3000DM001-1E6166_Z1F3FX1E-part4
S:disk/by-id/wwn-0x5000c500642bbfd3-part4
S:disk/by-label/mama04
S:disk/by-partlabel/m04
S:disk/by-partuuid/5fabaa67-6f04-4d59-b797-e6fee7f4d454
S:disk/by-path/pci-:00:1d.7-usb-0:5:1.0-scsi-0:0:0:0-part4
S:disk/by-uuid/8561eb12-3ee8-42e1-a5c7-6d36fea217d3
E:ID_FS_LABEL=mama04
E:ID_FS_TYPE=ext3
E:ID_FS_USAGE=filesystem
E:ID_FS_UUID=8561eb12-3ee8-42e1-a5c7-6d36fea217d3
E:ID_PART_ENTRY_TYPE=0fc63daf-8483-4772-8e79-3d69d8477de4
E:ID_PART_ENTRY_UUID=5fabaa67-6f04-4d59-b797-e6fee7f4d454
E:ID_PART_TABLE_TYPE=gpt
E:ID_PART_TABLE_UUID=35365a04-6978-4588-9fbe-75c8f3263aba

Unlike, say, sba4 and mama04 where the difference is obvious, UUIDs
all look alike with a quick glance.

> Thus, I would want to point to the partition PARTUUID because (as you
> pointed out to me earlier) the swap filesystem is going to change every
> time due to urandom and thus the UUID should be changing on every
> boot...blkid is probably seeing that this is a ever changing swap
> partition and just returning the PARTUUID for me.

I don't think it's blkid's prerogative to interpret the information,
but just to present it.

> But putting that PARTUUID in my /etc/crypttab didn't work and I ended up
> with the systemd.fsck timing out and not mounting swap. Hrm.

I don't recall seeing you post what you actually put into
/etc/crypttab to test PARTUUID, only the erroneous earlier versions
where you were still using swap's UUID.

Cheers,
David.


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/20150401202758.ga21...@alum.home

Re: Installing Debian Wheezy using the latest Kernel from Jessie

[Ivanov, Konstantin]

I've used debootstrap before to install  Debian in a chroot, and made a
bootable ISO from it. How does that help me with installing the OS though?

On Wed, Apr 1, 2015 at 3:28 PM, Lisi Reisz  wrote:

> On Wednesday 01 April 2015 20:34:02 Ivanov, Konstantin wrote:
> > On Wed, Apr 1, 2015 at 11:23 AM, Sven Hartge  wrote:
> > > Ivanov, Konstantin  wrote:
> > > > I need to install Debian Wheezy on an HP ProLiant DL380 Gen9 server
> > > > with a HP Smart Array P840 Controller.
> > >
> > > I had the same problem some months ago.
> > >
> > > I uses a GRML USB key and uses grml-bootstrap (a nice wrapper around
> > > cdebootstrap) to install Wheezy with the kernel 3.16 from the
> backports.
> > > Worked like a charm.
> >
> > Can you provide more details please ? How can I use a live distribution
> to
> > install Wheezy ?
>
>
> https://www.google.co.uk/search?q=grml-bootstrap&oq=grml-bootstrap&aqs=chrome..69i57.1256j0j7&sourceid=chrome&es_sm=93&ie=UTF-8
>
> And could you possibly bottom post?  I have reordered this for now.
>
> Thanks.
>
> Lisi
>
> > > --
> > > Sigmentation fault. Core dumped.
> > >
> > >
> > > --
> > > To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
> > > with a subject of "unsubscribe". Trouble? Contact
> > > listmas...@lists.debian.org
> > > Archive: https://lists.debian.org/abgjqt1jj...@mids.svenhartge.de
>
>
> --
> To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact
> listmas...@lists.debian.org
> Archive: https://lists.debian.org/201504012128.10383.lisi.re...@gmail.com
>
>

Re: Installing Debian Wheezy using the latest Kernel from Jessie

[Lisi Reisz]

On Wednesday 01 April 2015 20:34:02 Ivanov, Konstantin wrote:
> On Wed, Apr 1, 2015 at 11:23 AM, Sven Hartge  wrote:
> > Ivanov, Konstantin  wrote:
> > > I need to install Debian Wheezy on an HP ProLiant DL380 Gen9 server
> > > with a HP Smart Array P840 Controller.
> >
> > I had the same problem some months ago.
> >
> > I uses a GRML USB key and uses grml-bootstrap (a nice wrapper around
> > cdebootstrap) to install Wheezy with the kernel 3.16 from the backports.
> > Worked like a charm.
>
> Can you provide more details please ? How can I use a live distribution to
> install Wheezy ?

https://www.google.co.uk/search?q=grml-bootstrap&oq=grml-bootstrap&aqs=chrome..69i57.1256j0j7&sourceid=chrome&es_sm=93&ie=UTF-8

And could you possibly bottom post?  I have reordered this for now.

Thanks.

Lisi

> > --
> > Sigmentation fault. Core dumped.
> >
> >
> > --
> > To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
> > with a subject of "unsubscribe". Trouble? Contact
> > listmas...@lists.debian.org
> > Archive: https://lists.debian.org/abgjqt1jj...@mids.svenhartge.de


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/201504012128.10383.lisi.re...@gmail.com

Re: Installing Debian Wheezy using the latest Kernel from Jessie

[Ivanov, Konstantin]

Can you provide more details please ? How can I use a live distribution to
install Wheezy ?

On Wed, Apr 1, 2015 at 11:23 AM, Sven Hartge  wrote:

> Ivanov, Konstantin  wrote:
>
> > I need to install Debian Wheezy on an HP ProLiant DL380 Gen9 server with
> > a HP Smart Array P840 Controller.
>
> I had the same problem some months ago.
>
> I uses a GRML USB key and uses grml-bootstrap (a nice wrapper around
> cdebootstrap) to install Wheezy with the kernel 3.16 from the backports.
> Worked like a charm.
>
> Grüße,
> Sven.
>
> --
> Sigmentation fault. Core dumped.
>
>
> --
> To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact
> listmas...@lists.debian.org
> Archive: https://lists.debian.org/abgjqt1jj...@mids.svenhartge.de
>
>

bind9 (or alsa) hangs at shutdown

[Racla Grillyz]

Hello. I am running Wheezy and during the shutdown, when
all the services are getting stopped, the service 'bind9' takes around
one minute to stop (showing the message "waiting for pid XYIJ to die...").

I tried to issue a 'kill -9' in its rc-script and, although bind9
seems to heal, it happens that alsa takes up to a minute to stop.

Summarizing:

if kill -9 to bind9, alsa take one minute to stop
else bind9 takes one minute to stop.

At least, that is what appear on the screen.

Any suggestions? Bye.


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/20150401175425.GA3148@debian

Re: Is this an April Fool joke running early ? (Systemd to fork the kernel)

[Eike Lantzsch]

On Wednesday 01 April 2015 23:04:49 Andrew McGlashan wrote:
> On 1/04/2015 2:07 AM, bjf...@gmail.com wrote:
> > Reading Wikipedia- it says systemd was chosen as default on Jessie aft
> > er discussion over these mailing lists...
> 
> > Is this wrong?
> 
> It is wrong to a great extent.
> 
> Most negative discussion of system was quashed
[snip]
> 
> And although this time, the kernel fork is an April Fool's joke, it
> really might not be far from the truth down the track.
> 
> Again, I must say, I want Linus Linux and most definitely not Lennart
> Linux myself.
> 
> A.
Wouldn't that be Lennax?

E. L.


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/4895082.dsCLp5oxgM@lxcl01

Re: links won't open using icedove/wheezy

[Michael Munger]

I am having the same problem as stated here 
(https://lists.debian.org/debian-user/2012/07/msg02095.html). I have 
read the thread, but didn't seem to get a resolution.


To recap: when I click on a link in Icedove, Firefox opens, but it 
doesn't go to the URL. It stays on the homepage (as if the link was not 
passed).


Steps take so far:
1. Removed everything from update-alternatives for x-www-browser, and 
then added in firefox (only).
2. Running "x-www-browser www.google.com" works. Firefox opens, and it 
goes to google. (My home page is not google, FYI).
3. I have confirmed mailto links work. (Clicking a mailto: link opens a 
new email in icedove, and it is properly addressed).
4. I have confirmed that the network protocol handler is set to 
x-www-browser (default) in the preferences. (Preferences > Advanced > 
General > Config Editor).


*OS Information:*
Linux d7 3.2.0-4-amd64 #1 SMP Debian 3.2.65-1+deb7u1 x86_64 GNU/Linux
Distributor ID:Debian
Description:Debian GNU/Linux 7.8 (wheezy)
Release:7.8
Codename:wheezy

*Desktop: XFCE*

Everything installed from repos except Firefox (obviously). Firefox is 
installed in /opt/firefox/. Executable is /opt/firefox/firefox, and the 
symlink in the path is /usr/local/bin/firefox. This all works with 
update-alternatives as noted before.


--
Michael Munger, dCAP, MCPS, MCNPS, MBSS
High Powered Help, Inc.
Microsoft Certified Professional
Microsoft Certified Small Business Specialist
Digium Certified Asterisk Professional
mich...@highpoweredhelp.com

Re: encfs quit wrking after full upgrade (jessie)

[David Wright]

Quoting Harry Putnam (rea...@newsguy.com):

> Somehting happened to the kernel during that upgrade but I'm not sure
> what.
> 
> uname -a:
>   Linux dv 3.16.0-4-586 #1 Debian 3.16.7-ckt2-1 (2014-12-08) i686
>   GNU/Linux
> 
> Shouldn't the `chk' part match the kernel version?
> 
> Is that likely to be the problem?

No, there are a number of independent "counters" there.

But your kernel looks rather old. Here are the last two in my
apt-cacher-ng cache:

32554074 Feb  5 13:20 linux-image-3.16.0-4-586_3.16.7-ckt4-3_i386.deb
32716516 Mar 17 11:00 linux-image-3.16.0-4-586_3.16.7-ckt7-1_i386.deb

and for 686:

33125736 Feb 11 00:02 linux-image-3.16.0-4-686-pae_3.16.7-ckt4-3_i386.deb
33306690 Mar  5 09:50 linux-image-3.16.0-4-686-pae_3.16.7-ckt7-1_i386.deb

Cheers,
David.


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/20150401163839.gb18...@alum.home

Re: Installing Debian Wheezy using the latest Kernel from Jessie

[Sven Hartge]

Ivanov, Konstantin  wrote:

> I need to install Debian Wheezy on an HP ProLiant DL380 Gen9 server with
> a HP Smart Array P840 Controller.

I had the same problem some months ago.

I uses a GRML USB key and uses grml-bootstrap (a nice wrapper around
cdebootstrap) to install Wheezy with the kernel 3.16 from the backports.
Worked like a charm.

Grüße,
Sven.

-- 
Sigmentation fault. Core dumped.


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/abgjqt1jj...@mids.svenhartge.de

Scanning bug in Jessie

[Andrew Wood]

Ive used my old Hp ScanJet 5300 with Simple Scan without problems for 
years and it was working fine on Jessie but a recent update seems to 
have broken something and several updates later its still not working.


It switches the lamp on and waits for it to warm up but then at the 
point where scanning would normally start it says Unable to start scan.


I can still run it using Wheezy so theres nothing wrong with the 
scanner.  Is anyone else having similair issues or should I file a bug 
report?


Andrew



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

Archive: https://lists.debian.org/551c1acc.6000...@perpetualmotion.co.uk

Re: Upgrade for wheezy to jessie hangs

[Darac Marjal]

On Wed, Apr 01, 2015 at 05:23:46PM +0200, Laurens Blankers wrote:
> Hello fellow Debian users,
> 
> I have been testing upgrading to Jessie given that release is coming
> closer. I ran into a problem while upgrading which actually causes the
> upgrade to hang and the system to get into a non-bootable state. I
> actually managed to track down the problem to an interaction between
> memtest86+, grub, and LVM snapshots, and I filed a bug about it:
> 
> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=777528
> 
> Unfortunately it has been almost 2 months now without hearing anything
> from the maintainer. Naturally I am a bit disappointed and a bit worried
> because memtest86+ is installed by default so potentially a lot of
> people could run into this problem.
> 
> My question: can I do something to make the issue more noticeable?
> Should I improve the description of the issue? Do you think it actually
> is release critical? If so, is there a way to make it more noticeable to
> the maintainer or release team?

I think narrowing down the cause of the bug might help the maintainer.

The line "Found Debian GNU/Linux (7.8) on /dev/mapper/vg-root_snapshot"
is generated by the "os-prober" package which, when grub2 regenerates
its config, searches all block devices for additional installed
operating systems. This includes block devices which aren't mounted
(because you probably want to be able to boot to Windows even if you
don't access its files from Linux, for example).

memtest86+ is running update-grub as part of its postinst in order to
add an entry for itself into the grub menu (I can't remember if you can
run memtest86+ from within Linux, but if so, it certainly won't have
access to all the memory. The normal way is to boot into it).

Now, interestingly, the last of your error messages is "done", which
suggests to me that os-prober is finished.

If you run the install to the point at which it hangs, kill the postinst
and then run "update-grub" yourself, does THAT complete?

It's possible that the "grub-probe: error: unknown filesystem" is the
cause of the hang. Perhaps update-grub is failing and the postinst of
memtest86+ isn't handling that error properly.

> 
> Thanks,
> 
> Laurens
> 
> 
> --
> To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
> Archive: https://lists.debian.org/551c0d82.1080...@blankersfamily.com
> 


signature.asc
Description: Digital signature

encfs quit wrking after full upgrade (jessie)

[Harry Putnam]

Following a fairly recent `full-upgrade', I'm no longer able to mount
and enfs directory I've had for a good while.

I installed it on jessie using wheezy on my sources.list.

That worked for some months... but my most recent `full-upgrade' has
done something that causes it to fail now.

Error from attempted encfs mount:
   EncFS Password: 
   fuse: device not found, try 'modprobe fuse' first
   fuse failed.  Common problems:
- fuse kernel module not installed (modprobe fuse)
- invalid options -- see usage message

Error when attempting to modprobe fuse.
  modprobe fuse
  modprobe: ERROR: could not insert 'fuse': Invalid argument


Somehting happened to the kernel during that upgrade but I'm not sure
what.

uname -a:
  Linux dv 3.16.0-4-586 #1 Debian 3.16.7-ckt2-1 (2014-12-08) i686
  GNU/Linux

Shouldn't the `chk' part match the kernel version?

Is that likely to be the problem?


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/87d23n3kov@reader.local.lan

Upgrade for wheezy to jessie hangs

[Laurens Blankers]

Hello fellow Debian users,

I have been testing upgrading to Jessie given that release is coming
closer. I ran into a problem while upgrading which actually causes the
upgrade to hang and the system to get into a non-bootable state. I
actually managed to track down the problem to an interaction between
memtest86+, grub, and LVM snapshots, and I filed a bug about it:

http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=777528

Unfortunately it has been almost 2 months now without hearing anything
from the maintainer. Naturally I am a bit disappointed and a bit worried
because memtest86+ is installed by default so potentially a lot of
people could run into this problem.

My question: can I do something to make the issue more noticeable?
Should I improve the description of the issue? Do you think it actually
is release critical? If so, is there a way to make it more noticeable to
the maintainer or release team?

Thanks,

Laurens


--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/551c0d82.1080...@blankersfamily.com

Re: Monitor is flickering when changes on the screen (i.e. cursor)

[Lisi Reisz]

On Wednesday 01 April 2015 16:16:58 Flo wrote:
> On 04/01/15 15:50, Floris wrote:
> > Op Wed, 01 Apr 2015 12:50:18 +0200 schreef Flo :
> >> Dear all,
> >>
> >> I installed jessie with LXDE, 3.16.0-4-amd64.
> >>
> >> The problem I am facing is that when I move the cursor or when there are
> >> other changes on the screen like moving lines the Monitor starts to
> >> flicker.
> >>
> >> The monitor&computer isn't new, there was Debian installed a few years
> >> ago and there it worked.
> >>
> >> The difficulty for me is that I don't know where to start from to find a
> >> solution.
> >>
> >> Can anyone give me a hint?
> >>
> >> Thany you very much in advance.
> >>
> >> Regards,
> >> Flo
> >
> > Does the problem also occurs when you use an other OS? For example
> > with a live Linux pendrive.
>
> There was an old Debian installed which I removed yesterday and there it
> worked without that problem.
>
> > Are there warning (WW) or error (EE) messages in
> > journalctl -u gdm.service
> > when the screen is flickering?
>
> Ok, I will check that and get back to you as soon as I have the
> information (it's my mother's pc, I am not there very often).
>
> Thank you.
>
> Regards,
> Flo.
>
> PS: I also tried different resolutions. No effect!

Different refresh rate?  Is that set the same now as before?  

Lisi


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/201504011628.47117.lisi.re...@gmail.com

Re: Monitor is flickering when changes on the screen (i.e. cursor)

[Flo]

On 04/01/15 15:50, Floris wrote:
> Op Wed, 01 Apr 2015 12:50:18 +0200 schreef Flo :
> 
>> Dear all,
>>
>> I installed jessie with LXDE, 3.16.0-4-amd64.
>>
>> The problem I am facing is that when I move the cursor or when there are
>> other changes on the screen like moving lines the Monitor starts to
>> flicker.
>>
>> The monitor&computer isn't new, there was Debian installed a few years
>> ago and there it worked.
>>
>> The difficulty for me is that I don't know where to start from to find a
>> solution.
>>
>> Can anyone give me a hint?
>>
>> Thany you very much in advance.
>>
>> Regards,
>> Flo
>>
>>
> 
> Does the problem also occurs when you use an other OS? For example
> with a live Linux pendrive.
> 

There was an old Debian installed which I removed yesterday and there it
worked without that problem.

> Are there warning (WW) or error (EE) messages in
> journalctl -u gdm.service
> when the screen is flickering?
> 

Ok, I will check that and get back to you as soon as I have the
information (it's my mother's pc, I am not there very often).

Thank you.

Regards,
Flo.

PS: I also tried different resolutions. No effect!


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/551c0bea.6090...@gmx.at

Re: zfs, autofs dependencies

[Reco]

 Hi.

On Wed, 1 Apr 2015 10:33:29 -0400
Dan Ritter  wrote:

> On Wed, Apr 01, 2015 at 02:15:32PM +0300, Mimiko wrote:
> > The question is, is there are method better to overcome this
> > problem? How to specify mount order? How to enable zfs import early?
 
> I suspect you will need to talk to the zfsonlinux mailing list.
> 
> http://list.zfsonlinux.org/mailman/listinfo/zfs-discuss

No, the problem is related to the Debian indeed. As ZFS is used as an
LVM here, so you might as well replace those fancy /dev/zvol/* with
something conventional, and the problem will still remain.

Consider the following /etc/fstab.

/dev/sda1 /backup  ext4 noauto,nofail,user_xattr 0 2
/dev/sda2 /backup/network  ext4 noauto,nofail,user_xattr 0 2
/dev/sda3 /backup/op   ext4 noauto,nofail,user_xattr 0 2

How do you can use /etc/fstab to specify a mount order? Without 
resorting to the shell scripts, of course.

Reco


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
https://lists.debian.org/20150401175539.343f9e126e5fcfbc773e2...@gmail.com

Installing Debian Wheezy using the latest Kernel from Jessie

[Ivanov, Konstantin]

Hello all!

I have a chicken and the egg type of a problem here.

I need to install Debian Wheezy on an HP ProLiant DL380 Gen9 server with
a HP Smart Array P840 Controller.

The controller uses the hpsa.ko kernel module, but the version of this
module on the Wheezy kernel does not work (it does not recognized the disks
during installation). However the module from the backported
kernel 3.16.0-0.bpo.4-amd64 works.

I cannot change the initrd.gz file either because compiling the module on
the 3.2.0-4-amd64 kernel that ships with Wheezy fails.

Is there a way to install Wheezy but use the latest kernel during the
installation instead? I can either use a virtual media or a Cobbler PXE
server.

I tried to build a custom installer following the instructions at [1] but
that failed.

Any help at this point will be greatly appreciated!




[1] https://wiki.debian.org/DebianInstaller/Modify/CustomKernel

Re: zfs, autofs dependencies

[Dan Ritter]

On Wed, Apr 01, 2015 at 02:15:32PM +0300, Mimiko wrote:
> Hello.
> 
> I've setup a file server on Debian Wheezy x86_64. I've used 2 ssd
> for system folders which are partitioned and used in software raid
> with mdadm. It's working ok. Also there are a bunch of disks which
> are combined in a big disk raid-z2 with zfs:
> zpool create -f -m none -o ashift=12 zfspool raidz2 disk1 
> 
> On this poll I've created three volumes:
> zfs create -V 4T zfspool/backup
> zfs create -V 1T zfspool/network
> zfs create -V 1T zfspool/op
> 
> mount /dev/zvol/zfspool/backup /backup
> mount /dev/zvol/zfspool/network /backup/network
> mount /dev/zvol/zfspool/op /backup/op
> 
> As you can see, network and op a mount into /backup folder.
> 
> No, the problem is where to describe mount parameters so it will
> follow the order? I've used in /etc/fstab:
> 
> /dev/zvol/zfspool/backup  /backup  ext4
> defaults,noauto,nofail,user_xattr,acl,barrier=1   0   2
> /dev/zvol/zfspool/network  /backup/network  ext4
> defaults,noauto,nofail,user_xattr,acl,barrier=1   0   2
> /dev/zvol/zfspool/op  /backup/op  ext4
> defaults,noauto,nofail,user_xattr,acl,barrier=1   0   2
> 
> I've put noauto and nofail parameters so on boot system will not
> stop with error, because at boot zfs volumes are not ready and
> imported yet.
> 
> Although, that I've used this in fstab, /backup/network and
> /backup/op are not mounted because they are mounted by zfs-mount in
> incorrect order, before /backup is mounted. So in
> /etc/init.d/zfs-mount script I've found do_mount() command and
> duplicated it. First time do_mount() mounts only /backup, second
> time do_mount() can mount other disks.
> 
> The question is, is there are method better to overcome this
> problem? How to specify mount order? How to enable zfs import early?
> 
> Second problem arises for autofs. I've setup it, so in /backup are
> some iso files. But when autofs starts it does not find /backup,
> because it is not mounted yet. So the mounted by autofs folders are
> empty. I need to restart autofs for files to appear.
> 
> How to specify that autofs should start after zfs mounted those partition?

I suspect you will need to talk to the zfsonlinux mailing list.

http://list.zfsonlinux.org/mailman/listinfo/zfs-discuss

-dsr-


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/20150401143329.gk26...@randomstring.org

Re: Monitor is flickering when changes on the screen (i.e. cursor)

[Floris]

Op Wed, 01 Apr 2015 12:50:18 +0200 schreef Flo :


Dear all,

I installed jessie with LXDE, 3.16.0-4-amd64.

The problem I am facing is that when I move the cursor or when there are
other changes on the screen like moving lines the Monitor starts to  
flicker.


The monitor&computer isn't new, there was Debian installed a few years
ago and there it worked.

The difficulty for me is that I don't know where to start from to find a
solution.

Can anyone give me a hint?

Thany you very much in advance.

Regards,
Flo




Does the problem also occurs when you use an other OS? For example
with a live Linux pendrive.

Are there warning (WW) or error (EE) messages in
journalctl -u gdm.service
when the screen is flickering?

Success,

Floris


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

Archive: https://lists.debian.org/op.xwe123tn5k9...@jessica.jkfloris.demon.nl

Re: Is this an April Fool joke running early ? (Systemd to fork the kernel)

[Andrew McGlashan]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

On 1/04/2015 2:07 AM, bjf...@gmail.com wrote:
> Reading Wikipedia- it says systemd was chosen as default on Jessie aft
er discussion over these mailing lists...
> 
> Is this wrong?

It is wrong to a great extent.

Most negative discussion of system was quashed

The DDs and committee members discussed things to a certain extent,
enough for them to decide it was the way to go ... much to the dismay of
a huge number of users and system administrators whom have basically
been silenced.

Attempts were made to "remedy" the situation, by way of a vote that only
DD's were able to vote in, the users and system administrators were
largely ridiculed and ignored with the very strong pro side people on
systemd getting their way with a bunch of DDs resigning as the last
straw over this matter.  There is absolutely no doubt that systemd has
been extremely divisive and for many, myself included, the damage is too
great.  I've greatly loved Debian over the years for all sorts of
reasons, but this will have me parting ways as soon as I'm able to do so
unless there is a miraculous miracle before then.


And although this time, the kernel fork is an April Fool's joke, it
really might not be far from the truth down the track.

Again, I must say, I want Linus Linux and most definitely not Lennart
Linux myself.

A.

-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iF4EAREIAAYFAlUb3t8ACgkQqBZry7fv4vvmVgD+I6UuKVqrFXxlf0+b3Ndi0rxC
rFl4hHWNJki+InAnWqAA/A3DoXPE41ZPNaBSJam2gl0veXh55rie0tAhZjn+6see
=XLIl
-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: https://lists.debian.org/551bdee1.9000...@affinityvision.com.au

Re: Making initramfs agree with rootfs about time zone

[Richard Hector]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Err, whoops.

That wasn't supposed to be encrypted. Not sure how that happened ...

Here we go:

On 02/04/15 00:21, Richard Hector wrote:
> On 01/04/15 11:56, Martin Read wrote:
>> I have a dual-boot Win7/Debian jessie system. Because Windows
>> doesn't deal gracefully with handling the hardware time-of-day
>> clock the proper way (hwclock set to GMT, all TZ handling in
>> software), this means that the hwclock changes for daylight
>> savings time.
> 
> I believe it's possible to fix that in Windows these days, eg:
> 
> http://kb.norsetech.net/set-windows-clock-to-utc-time/
> 
> Richard
> 
> 
> 

-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.19 (GNU/Linux)

iQEcBAEBAgAGBQJVG9xqAAoJELSi8I/scBaNDIAH+gJOZZaXoOcV5bXnm339gedY
Tm3tG6GaAXZKlD3V3VulLjVJjfOwmminGuRVD/hGYPB4qOk+Gl+NESgPqqu2kp8Z
GWaqBXinkv6gCKE2BU7NzLn+95WV7cehrKC3yKdsckFnkJipV229x5XXQRAB4dmi
cE6xKEBFUDpop8u5v7hac3q7/Z1VWr/fMgsDNoCrXfs1LuSRSYhT5Lg/lLugAQDJ
9CAH3vAy21LFRBtPBzHSjGBY9bWfpZOZFtXBcHmXJVdMneP+MYExdwfLIXQBHkvI
VARFf8zlU1BtCnj6foL4wyGSzKcNcojUdzd16bTmyd/Ghw3i0GTGis22LlUktyg=
=ubqT
-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: https://lists.debian.org/551bdc6a.5030...@walnut.gen.nz

Re: Making initramfs agree with rootfs about time zone

[Richard Hector]

-BEGIN PGP MESSAGE-
Charset: utf-8
Version: GnuPG v2.0.19 (GNU/Linux)

hQEMA07UmgrFcS2hAQf/dwmi7WfCdgUxzk0BIhdGs9qKWgbRiiVyqxLm2Min3wqF
Xw6mgqsMBh3vQ24CCVmPTF4q2eiy2ZMsGjsFwXm2SJK8WrgsSOKSFtyt77rZHpHx
SExwcy/nXHoSaynm9x3dNwfy2qcrANSmG9dWBiX3HUc1GSw08DVa50D+iqZBmyWH
csubGvcXMxbvYBAKwFZniS2NrtM6I+5si0UajzbKJ99ACjlAvj4TdOsuzuMscL+q
ke/pCpXamBtG3IxZQbCQJIufPxmT7CrC71D3RrNudHLoeaeSYMq6Fqv1RVj5P9pm
LFd8P9q7eyBgSLoUXnNIFErSF684XevIdG3jElhQi9LpAaT7r7EOUXqvvhO7TbLT
4n/n4YPb4NUN9fY+aFX4Z8TnxJK1RC6ZEXJn/6HMP0GJk5FHn2Pg7abUnNEcIQvi
sr7Bn6JQ9mB3gCwgR5vH2/DC5tCmMKO+lhW3pHmCAWohBlAkWLfjHFEo+ZJlterp
cpH9A3MBy6qjWo6rv7cLshqK42krjcDVQdduVgNMrvBDE1f5PsqOZ4QHaosP4+pT
S/xKMhyaCdpzJTVTwTOZwP2gHhhHYCRlg+jyreet8EF73tBJkiTJ5T8WLxf4PQwp
+Y6Xhvjsbz/1qH1QPak1AC+B0FGiCdWIhIK2hHPlbxOPZ28wP6nxkERVad4IqY8a
f/oF0LKRO8/lTfhYw8c8jlfRFZ4z55ic9ymSavIJnWCxPLskwuniPYic79xj81BK
LNyQ8J7AWrSIfvOCjzapFPEyCgwudqD0ImdZAQYO6AcfqGSWLwUL/1/vxqlTyQHW
tiZwCYAAInvKpqkFC/5YEM/SGLgm6vKnD8cPgeO6v1N61cZXTRbkOdaInPmRsCBw
ZPK0UfgpyDVMhetOWcNNBGdAtGLPsmIgVeWjQpTDb7N/DdzZbVpntQEjnOk3SAgn
OPhAyVAORkXdesX1YB9MuXZkY11IgJFTnGBzedarPkbzK/O35GNgfipK12U2HGEQ
N/N94uLzrgDxv34RowDKYxLAII5tOMvYVI/sc8m5ucfC/i+d++HF+sJs6WqJ/3s8
8YUp5IJ1h3ju6cwr/Zls7r6/YLPVGn3H/TRk8DgCKxIdPaGUuz0JOZegV8pIF6wX
01RG5EwdikNVIYnOCHQN2vm+FtOtO/zRWXSMEOxAySIlME8M3xyBhNrOnyP2hKet
XSTRCXhcxYIXDcJn9+xa5hf3uxl7smV2e31AxDprCywKCiWLVukeQF8+garbIGkl
RuvdYn/6bbtAi5otMetpuH1TcdYAQdq16rcPvEeKUqC6gUVl4w06Oh6XWEg4+jp5
KXUY
=GIzP
-END PGP MESSAGE-


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/551bd4cd.6010...@walnut.gen.nz

zfs, autofs dependencies

[Mimiko]

Hello.

I've setup a file server on Debian Wheezy x86_64. I've used 2 ssd for 
system folders which are partitioned and used in software raid with 
mdadm. It's working ok. Also there are a bunch of disks which are 
combined in a big disk raid-z2 with zfs:

zpool create -f -m none -o ashift=12 zfspool raidz2 disk1 

On this poll I've created three volumes:
zfs create -V 4T zfspool/backup
zfs create -V 1T zfspool/network
zfs create -V 1T zfspool/op

mount /dev/zvol/zfspool/backup /backup
mount /dev/zvol/zfspool/network /backup/network
mount /dev/zvol/zfspool/op /backup/op

As you can see, network and op a mount into /backup folder.

No, the problem is where to describe mount parameters so it will follow 
the order? I've used in /etc/fstab:


/dev/zvol/zfspool/backup  /backup  ext4 
defaults,noauto,nofail,user_xattr,acl,barrier=1   0   2
/dev/zvol/zfspool/network  /backup/network  ext4 
defaults,noauto,nofail,user_xattr,acl,barrier=1   0   2
/dev/zvol/zfspool/op  /backup/op  ext4 
defaults,noauto,nofail,user_xattr,acl,barrier=1   0   2


I've put noauto and nofail parameters so on boot system will not stop 
with error, because at boot zfs volumes are not ready and imported yet.


Although, that I've used this in fstab, /backup/network and /backup/op 
are not mounted because they are mounted by zfs-mount in incorrect 
order, before /backup is mounted. So in /etc/init.d/zfs-mount script 
I've found do_mount() command and duplicated it. First time do_mount() 
mounts only /backup, second time do_mount() can mount other disks.


The question is, is there are method better to overcome this problem? 
How to specify mount order? How to enable zfs import early?


Second problem arises for autofs. I've setup it, so in /backup are some 
iso files. But when autofs starts it does not find /backup, because it 
is not mounted yet. So the mounted by autofs folders are empty. I need 
to restart autofs for files to appear.


How to specify that autofs should start after zfs mounted those partition?

Thank you.


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

Archive: https://lists.debian.org/551bd354.3050...@gmail.com

Monitor is flickering when changes on the screen (i.e. cursor)

[Flo]

Dear all,

I installed jessie with LXDE, 3.16.0-4-amd64.

The problem I am facing is that when I move the cursor or when there are
other changes on the screen like moving lines the Monitor starts to flicker.

The monitor&computer isn't new, there was Debian installed a few years
ago and there it worked.

The difficulty for me is that I don't know where to start from to find a
solution.

Can anyone give me a hint?

Thany you very much in advance.

Regards,
Flo


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/551bcd6a.8060...@gmx.at

Mailing List

[Pericos Investment Network EA LTD Andrew]

Hi,
I want to inquire about the Kenyan email database. Are the emails verified?
I have a mail server, i just need the mails. can i get a sample?
Thank You
Pericos

Re: Upgrading guidance for Cedarview driver in Debian 6 - 2.6.32 Kernel

[venkat]

On 01-04-2015 04:11, David Wright wrote:

Quoting venkat (venka...@vortexindia.co.in):


Primary intent : To control connected HDMI and CRT monitors individually.

We use VESA as display driver for connected display(Single display).
Now, we are trying to extend and use dual display as said (HDMI and
CRT).
We configured it using BIOS and see the display output in connected
screen (HDMI and CRT).

Interestingly, we notice that XRANDR does not reflect any info on
connected devices. Is updating kernel the only way to solve this??
or is there some configuration error on my side.

Have you tried running
Xorg -configure
as root, which will write xorg.conf.new into the current directory.
That should at least tell you what's being seen by the X server.

If what you posted is exactly that, then it doesn't look very hopeful.

Cheers,
David.


Yes the the info posted is exactly same and this info belongs to 2.6.32 
kernel.
The situation almost concludes that with 2.6.32 kernel is does not 
support HDMI and CRT configurations

 LSPCI info : http://pastebin.com/KKWXkXHH
 XORG info : http://pastebin.com/VyU4CDst

However,  to understand how multiple monitor works installed a fresh 
copy of debian 7 (7.8) which uses 3.2.0-4-486 kernel version.
After installing, we noticed that the behavior is still same as debian 6 
(2.6.32) . We see that connected display works.

But, Still we notice that XRANDR dost not show info about HDMI ot CRT

Screen 0: minimum 1024 x 768, current 1024 x 768, maximum 1024 x 768
default connected 1024x768+0+0 0mm x 0mm
   1024x7680.0*

Although, Xorg.conf has some information on Screen 0 : Card 0 and Screen 
1 : card 1


Section "Screen"
Identifier "Screen0"
Device "Card0"
Section "Screen"
Identifier "Screen1"
Device "Card1"

  Xorg information : http://pastebin.com/EHVpaV3M
  lspci info:   http://pastebin.com/zBVesvmS

With this XORG is there some possibility that i can individually control 
my connected interface. Am i missing some more configurations??


--
Regards
Venkat.S