Re: -cpu option of qemu

2014-12-04 Thread peter
From: Reco 
Date: Thu, 4 Dec 2014 23:15:56 +0300
> Do you have the file such as /etc/qemu/target-x86_64.conf?

No.  Not even /etc/qemu/.  Now I've removed qemu and qemu-system 
and installed qemu-system-x86.  That left an empty target-x86_64.conf.

> What does change if you add to /etc/qemu/target-x86_64.conf strings
> from https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=652281#17 ?

After adding the cited lines to define Nehalem, this.

peter@armada:~$ qemu-system-x86_64 -cdrom /home/peter/MY/*.iso -boot d
qemu-system-x86_64:/etc/qemu/target-x86_64.conf:4: There is no option group 
'cpudef'

More than those lines must be needed in the file.  Too late to investigate 
further.

Thanks for the help,  ... Peter E.

-- 
123456789 123456789 123456789 123456789 123456789 123456789 123456789 12
Tel +1 360 639 0202  http://carnot.yi.org/  Bcc: peter at easthope. ca


-- 
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/E1Xwm4w-0002Ep-7U@armada.invalid



Re: Installing Linux on a Mac Mini without OSX

2014-12-04 Thread Brian Sammon
On Thu, 04 Dec 2014 21:39:08 -0800
Jimmy Johnson  wrote:

> As mentioned earlier, your machine is currently not using EFI.

I missed that -- and how do I know that for sure?

Is it possible that it's trying to use EFI, but my debian install is trying to 
do something not-EFI-compatible, and that's why it won't boot?


-- 
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/20141205013223.163341bf21dd31af3554f...@brisammon.fastmail.fm



Re: Random X crash

2014-12-04 Thread Jimmy Johnson

On 12/04/2014 02:56 PM, Joris Bolsens wrote:

I am getting seemingly random crashes of X.

I have 3 monitors (2 external, 1 laptop), and occasionally they will
flash black, and orientation gets reset to default. I have not been able
to find any action that specifically triggers this, although when i look
at dmesg, it seems to somehow be relate to my wifi. I have pasted (what
I think) are the relevant bits of dmesg below, please let me know if I
should provide more info.

dmesg first instance:

[14198.890344] bridge-wlan2: device is wireless, enabling SMAC
[14198.890348] bridge-wlan2: up
[14198.890353] bridge-wlan2: attached
[14198.930206] wlan2: Limiting TX power to 30 (30 - 0) dBm as advertised
by 80:ea:96:ee:dd:0a
[14199.090477] userif-3: sent link down event.
[14199.090481] userif-3: sent link up event.
[16815.766004] [drm:cpt_set_fifo_underrun_reporting] *ERROR* uncleared
pch fifo underrun on pch transcoder A
[16815.766009] [drm:cpt_serr_int_handler] *ERROR* PCH transcoder A FIFO
underrun
[16815.767229] [drm:ivybridge_set_fifo_underrun_reporting] *ERROR*
uncleared fifo underrun on pipe A
[16815.767234] [drm:ivb_err_int_handler] *ERROR* Pipe A FIFO underrun
[17129.902962] [drm:cpt_set_fifo_underrun_reporting] *ERROR* uncleared
pch fifo underrun on pch transcoder A
[17129.902966] [drm:cpt_serr_int_handler] *ERROR* PCH transcoder A FIFO
underrun
[17129.917635] [drm:ivybridge_set_fifo_underrun_reporting] *ERROR*
uncleared fifo underrun on pipe A
[17129.917639] [drm:ivb_err_int_handler] *ERROR* Pipe A FIFO underrun
[17197.888252] [drm:cpt_set_fifo_underrun_reporting] *ERROR* uncleared
pch fifo underrun on pch transcoder A
[17197.888256] [drm:cpt_serr_int_handler] *ERROR* PCH transcoder A FIFO
underrun
[17197.898583] [drm:ivybridge_set_fifo_underrun_reporting] *ERROR*
uncleared fifo underrun on pipe A
[17197.898588] [drm:ivb_err_int_handler] *ERROR* Pipe A FIFO underrun
[17553.192289] [drm:cpt_set_fifo_underrun_reporting] *ERROR* uncleared
pch fifo underrun on pch transcoder A
[17553.192294] [drm:cpt_serr_int_handler] *ERROR* PCH transcoder A FIFO
underrun
[17553.196104] [drm:ivybridge_set_fifo_underrun_reporting] *ERROR*
uncleared fifo underrun on pipe A
[17553.196108] [drm:ivb_err_int_handler] *ERROR* Pipe A FIFO underrun



Installing firmware-intel* and intel-microcode from non-free repos 
should fix your problem, I would also install firmware-linux* too, if 
not already installed.

--
Jimmy Johnson

Debian - Wheezy - KDE 4.8.4 - AMD64 - EXT4 at sda1
Registered Linux User #380263


--
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/54814fe6.8030...@gmail.com



Re: Debian fork: 'Devuan', Debian without Systemd

2014-12-04 Thread Buntunub
Laurent Bigonville-5 wrote
> Le Wed, 03 Dec 2014 10:18:36 +0100,
> Martin Steigerwald <

> Martin@

> > a écrit :
> 
>> Am Mittwoch, 3. Dezember 2014, 08:35:00 schrieb Erwan David:
>> > Le 02/12/2014 23:15, Martin Steigerwald a écrit :
>> > > Am Dienstag, 2. Dezember 2014, 18:47:38 schrieb Renaud OLGIATI:
>> > >> On Tue, 2 Dec 2014 14:22:13 -0700
>> > >> 
>> > >> Aaron Toponce <

> aaron.toponce@

> > wrote:
>> >  It's a waste. They shouldn't have left. I'm pretty neutral
>> >  about systemd as I'm only an end user but I disklike having it
>> >  forced upon me this way.
>> > >>> 
>> > >>> # apt-get install upstart
>> > >>> # apt-get install sysvinit-core
>> > >>> # apt-get install openrc
>> > >>> No one is forcing you to stick with systemd. The "fork" is just
>> > >>> silly.
>> > >> 
>> > >> Another way to look at it is "forward planning for the release
>> > >> after Jessie, when systemd may well become compulsory..."
>> > > 
>> > > Or going beyond what is offered in Debian… like making GNOME
>> > > installable without having any systemd related package installed.
>> > 
>> > The systemd package is just a small part of systemd. I'd like to
>> > remove systemd-logind and lbpam-systemd, sinc I have no clue at all
>> > that logind is better deisgned and programmed than resolved, which
>> > showed it was designed without any care for well known attacks.
>> 
>> I explicetely wrote "any systemd related package".
>> [...]
>> 
>> So you can still choose to what init system to use, but running
>> completely without any systemd related packages gives you a really
>> crippled system.
> 
> As explained several times on this ML, depending against libsystemd0
> package doesn't mean anything about requiring systemd to be used as
> PID1 or not. Even Ian's GR was not taking the "I don't want any systemd
> package on my machine" use case into account you know.
> 
> But if you have that special concern, you'll have to start recompiling
> the packages I'm afraid. Start with policykit and network-manager (and
> other package defining a dependency against libpam-systemd) to make
> them use ConsoleKit again, you would at least be able to remove the
> systemd package completely.

And so it comes full circle. This is why there is a need for a Debian fork.
/I/ don't have to do any of those things. You don't either. The good folks
at Devuan will take care of all that for you.




--
View this message in context: 
http://debian.2.n7.nabble.com/Debian-fork-Devuan-Debian-without-Systemd-tp338p3447295.html
Sent from the Debian User mailing list archive at Nabble.com.


--
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/1417757630187-3447295.p...@n7.nabble.com



Re: Installing Linux on a Mac Mini without OSX

2014-12-04 Thread Jimmy Johnson

On 12/04/2014 09:25 PM, Brian Sammon wrote:

On Thu, 04 Dec 2014 20:34:22 -0800
Jimmy Johnson  wrote:


Installing to the MBR should fix your booting problems.


This brings to mind another question/issue:  I need to
educate myself on how MBRs work on EFI machines.
Questions such as:
When it says it's installing Grub to the MBR, is it
really installing it to an MBR, or is it installing it
to EFI's alternative to an MBR?

Any suggested reading?



As mentioned earlier, your machine is currently not using EFI.

In your case grub will be installed to the MBR of sda/sda1
--
Jimmy Johnson

Debian - Wheezy - KDE 4.8.4 - AMD64 - EXT4 at sda1
Registered Linux User #380263


--
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/548144fc.4010...@gmail.com



Re: Installing Linux on a Mac Mini without OSX

2014-12-04 Thread Brian Sammon
On Thu, 04 Dec 2014 20:34:22 -0800
Jimmy Johnson  wrote:

> Installing to the MBR should fix your booting problems.

This brings to mind another question/issue:  I need to educate myself on how 
MBRs work on EFI machines.
Questions such as:
When it says it's installing Grub to the MBR, is it really installing it to an 
MBR, or is it installing it to EFI's alternative to an MBR?

Any suggested reading?


-- 
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/20141205002551.c643b8224d141d944790c...@brisammon.fastmail.fm



Re: LVM RAID5 with missing disk?

2014-12-04 Thread Gary Dale

On 04/12/14 12:51 PM, Dan Ritter wrote:

On Thu, Dec 04, 2014 at 02:13:59PM +0100, mad wrote:

Hi!

I wanted to create a RAID5 with lvm. The basic setup is something like

lvcreate --type raid5 -i 2 -L 1G -n my_lv my_vg

which would mean 3 physical drives would be used in this RAID5. But can
I specify that one drive is missing as it is possible with mdadm?

I don't think so, no. You can create your RAID with mdadm and
put LVM on top of that.

In general I strongly recommend against using RAID5. RAID1, 10,
or 6 are all better options if your data's availability is
important to you.

-dsr-

Sorry, but there are good reasons to use RAID 5 and better reasons to 
NOT use RAID 10. RAID 1 and RAID 5 are both immune to single disk 
failures in their most common configurations (1 or more data disks with 
1 parity disk). RAID 10 is also immune to single disk failure but uses 
half the disks for parity.


If you are concerned about availability, with 4 disks (the simplest RAID 
10 configuration) RAID 6 gives you the same data capacity with immunity 
to two disk failures and can increase capacity by 50% simply by adding 
another disk. You need 6 disks to get the same capacity with RAID 10 
while with 6 disks, RAID 6 will give you double the capacity of 4 disks 
or get you immunity to 3 disks failing.


Moreover, while a RAID 10 array can sometimes survive 2 disk failures, 
if it's the wrong 2, you are screwed. For example if A+B are mirrored by 
C+D, RAID 10 won't survive an A & C fail or a B & D fail, but will 
survive A & D or B & C failing.


RAID 0 and RAID 10 are used only when write performance is important. 
Read performance is generally better with any type of RAID. Since in 
most cases you are doing a lot more reads than writes, you are unlikely 
to notice much difference between RAID varieties. If you need RAID 10, 
you probably also need some high-performance hardware RAID controllers.


Of course, I don't know your situation, but for me, data integrity is 
important but so is capacity, so I use with RAID 5. I have the luxury of 
being take the server offline or shut down the GUI on my workstation, 
both of which use RAID 5, so that an array rebuild can proceed rapidly.


Just don't ignore smartctl errors. When you get a failing disk, replace 
it immediately.




--
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/54813cce.30...@torfree.net



Re: Installing Linux on a Mac Mini without OSX

2014-12-04 Thread Jimmy Johnson
On 12/04/2014 01:29 PM, Brian Sammon wrote:> On Thu, 04 Dec 2014 
14:46:09 -0500

> Stefan Monnier  wrote:
>
>>> I was recently given a Mac Mini (Intel Mid 2007) that had been wiped.
>>> I tried to install Debian (Wheezy) on it, and the installer reported
>>> success, but  when it came time to eject and reboot, Debian didn't
>>> boot from the hard drive.
>> [...]
>>> Is there a way to install Debian/Linux on this machine that doesn't 
involve

>>> buying or borrowing (or "borrowing") a copy of OSX?
>>
>> If you managed to boot a plain-normal Debian CDROM installer, then your
>> machine's firmware has full BIOS support and you can boot a plain-normal
>> Debian install on the harddisk as well, as if the machine were
>> a normal PC.
>
> Hmm... I was able to boot a plain-normal (I assume it is) Debian 
CDROM installer,
> but now I can't boot the plain-normal (I assume) Debian install that 
the installer

> said it installed.
>
> The two questions I have:
> Can I still assume that I have the firmware version that I want?
> What do I do next to troubleshoot/fix this?
>
> Another random question:
> The installer gave me the choice of installing Grub on the partition 
or on the

> Master Boot Record.  Which of these should I choose?


Installing to the MBR should fix your booting problems.
--
Jimmy Johnson

Debian - Wheezy - KDE 4.8.4 - AMD64 - EXT4 at sda1
Registered Linux User #380263


--
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/548135ce.4000...@gmail.com



Re: Debian fork: 'Devuan', Debian without Systemd

2014-12-04 Thread Martinx - ジェームズ
>> Jessie isn't Debian.
>
> So you say. Others have a different opinion.

Absolutely, it is just an opinion, I know.

Also, it seems to be Joey's opinion too: "It's become abundantly clear
that this is no longer the project I
originally joined in 1996."

https://lists.debian.org/debian-devel/2014/11/msg00174.html

And, Joey's opinion is very, very strong. He can talk about this, more
than anyone.

So, Jessie isn't Debian anymore... Soon or later, everybody will realize that.

Right now, I'm very concerned about Debian's stability, I'm using it
(since Potato) because it is _stable_, release after release, but,
when with systemd, it will not be that stable anymore, it is
impossible to be, mostly because systemd itself it too new and poorly
designed, not ready for production. Maybe in ~2020, who knows...

What is happening with Debian is just crazy.

Best!
Thiago


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



Re: Installing Linux on a Mac Mini without OSX

2014-12-04 Thread Brian Sammon
On Fri, 5 Dec 2014 08:01:48 +0900
Joel Rees  wrote:
> Can we conclude that you have read this page
> 
> https://wiki.debian.org/MacMiniIntel

I have read this page, and I'm hoping to add a "If you don't have OSX" section 
to it, once I figure out what to add.

> and followed appropriate links, such as the elilo link? (Even the PPC

I'm not sure which links are appropriate, so it's quite possible that I missed 
one.  I got the impression from the MacMiniIntel page that the elilo approach 
was a suboptimal one, so I've not looked into it much, as I'm hoping there's a 
approach that works better (than the MacMiniIntel page suggests the elilo 
approach would)

> link may be useful for background.)
> 
> You will probably have to interpret some things, and not expect an exact 
> recipe.
> 
> You may also want to ask on the debian boot list.

Thanks, I'll look into it.

> And, Jerome's kidding around notwithstanding, questions over at
> puredarwin are likely to yield useful information, if it takes going
> that far.

Yeah, that's on the todo list.


-- 
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/20141204184119.5ca9c34edfc8071363251...@brisammon.fastmail.fm



Re: Installing Linux on a Mac Mini without OSX

2014-12-04 Thread Joel Rees
On Fri, Dec 5, 2014 at 3:25 AM, Brian Sammon
 wrote:
> I was recently given a Mac Mini (Intel Mid 2007) that had been wiped.
>
> I tried to install Debian (Wheezy) on it, and the installer reported success, 
> but
> when it came time to eject and reboot, Debian didn't boot from the hard drive.
>
> Googling finds me various pages about installing Linux where one of the steps 
> is something like "Boot into OSX"
>
> Is there a way to install Debian/Linux on this machine that doesn't involve 
> buying or borrowing (or "borrowing") a copy of OSX?  Is it easier to install 
> linux on a USB disk and run it off of that?
>
> Two particular subtasks that I may need to do that seem to require OSX:
> 1) "Blessing" a partition
> 2) Checking what version of firmware it has (some versions have BIOS
>compatibility)
>
> Any pointers/suggestions?
>
> I'm also looking into PureDarwin as a possible solution.

Can we conclude that you have read this page

https://wiki.debian.org/MacMiniIntel

and followed appropriate links, such as the elilo link? (Even the PPC
link may be useful for background.)

You will probably have to interpret some things, and not expect an exact recipe.

You may also want to ask on the debian boot list.

And, Jerome's kidding around notwithstanding, questions over at
puredarwin are likely to yield useful information, if it takes going
that far.

-- 
Joel Rees

Be careful when you look at conspiracy.
Look first in your own heart,
and ask yourself if you are not your own worst enemy.
Arm yourself with knowledge of yourself, as well.


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



Random X crash

2014-12-04 Thread Joris Bolsens
I am getting seemingly random crashes of X.

I have 3 monitors (2 external, 1 laptop), and occasionally they will
flash black, and orientation gets reset to default. I have not been able
to find any action that specifically triggers this, although when i look
at dmesg, it seems to somehow be relate to my wifi. I have pasted (what
I think) are the relevant bits of dmesg below, please let me know if I
should provide more info.

dmesg first instance:

[14198.890344] bridge-wlan2: device is wireless, enabling SMAC
[14198.890348] bridge-wlan2: up
[14198.890353] bridge-wlan2: attached
[14198.930206] wlan2: Limiting TX power to 30 (30 - 0) dBm as advertised
by 80:ea:96:ee:dd:0a
[14199.090477] userif-3: sent link down event.
[14199.090481] userif-3: sent link up event.
[16815.766004] [drm:cpt_set_fifo_underrun_reporting] *ERROR* uncleared
pch fifo underrun on pch transcoder A
[16815.766009] [drm:cpt_serr_int_handler] *ERROR* PCH transcoder A FIFO
underrun
[16815.767229] [drm:ivybridge_set_fifo_underrun_reporting] *ERROR*
uncleared fifo underrun on pipe A
[16815.767234] [drm:ivb_err_int_handler] *ERROR* Pipe A FIFO underrun
[17129.902962] [drm:cpt_set_fifo_underrun_reporting] *ERROR* uncleared
pch fifo underrun on pch transcoder A
[17129.902966] [drm:cpt_serr_int_handler] *ERROR* PCH transcoder A FIFO
underrun
[17129.917635] [drm:ivybridge_set_fifo_underrun_reporting] *ERROR*
uncleared fifo underrun on pipe A
[17129.917639] [drm:ivb_err_int_handler] *ERROR* Pipe A FIFO underrun
[17197.888252] [drm:cpt_set_fifo_underrun_reporting] *ERROR* uncleared
pch fifo underrun on pch transcoder A
[17197.888256] [drm:cpt_serr_int_handler] *ERROR* PCH transcoder A FIFO
underrun
[17197.898583] [drm:ivybridge_set_fifo_underrun_reporting] *ERROR*
uncleared fifo underrun on pipe A
[17197.898588] [drm:ivb_err_int_handler] *ERROR* Pipe A FIFO underrun
[17553.192289] [drm:cpt_set_fifo_underrun_reporting] *ERROR* uncleared
pch fifo underrun on pch transcoder A
[17553.192294] [drm:cpt_serr_int_handler] *ERROR* PCH transcoder A FIFO
underrun
[17553.196104] [drm:ivybridge_set_fifo_underrun_reporting] *ERROR*
uncleared fifo underrun on pipe A
[17553.196108] [drm:ivb_err_int_handler] *ERROR* Pipe A FIFO underrun

dmesg second instance:
-
[20155.260197] /dev/vmnet: port on hub 0 successfully opened
[20155.260206] bridge-wlan2: device is wireless, enabling SMAC
[20155.261377] bridge-wlan2: up
[20155.261422] bridge-wlan2: attached
[20155.341711] wlan2: Limiting TX power to 30 (30 - 0) dBm as advertised
by 80:ea:96:ee:dd:0a
[20155.411171] userif-3: sent link down event.
[20155.412149] userif-3: sent link up event.
[20416.556616] [drm:cpt_set_fifo_underrun_reporting] *ERROR* uncleared
pch fifo underrun on pch transcoder A
[20416.556621] [drm:cpt_serr_int_handler] *ERROR* PCH transcoder A FIFO
underrun
[20416.556772] [drm:ivybridge_set_fifo_underrun_reporting] *ERROR*
uncleared fifo underrun on pipe A
[20416.556775] [drm:ivb_err_int_handler] *ERROR* Pipe A FIFO underrun
[21122.359725] [drm:cpt_set_fifo_underrun_reporting] *ERROR* uncleared
pch fifo underrun on pch transcoder A
[21122.359729] [drm:cpt_serr_int_handler] *ERROR* PCH transcoder A FIFO
underrun
[21122.369766] [drm:ivybridge_set_fifo_underrun_reporting] *ERROR*
uncleared fifo underrun on pipe A
[21122.369771] [drm:ivb_err_int_handler] *ERROR* Pipe A FIFO underrun
[22666.750046] [drm:cpt_set_fifo_underrun_reporting] *ERROR* uncleared
pch fifo underrun on pch transcoder A
[22666.750050] [drm:cpt_serr_int_handler] *ERROR* PCH transcoder A FIFO
underrun
[22666.751890] [drm:ivybridge_set_fifo_underrun_reporting] *ERROR*
uncleared fifo underrun on pipe A
[22666.751893] [drm:ivb_err_int_handler] *ERROR* Pipe A FIFO underrun
[22988.645046] [drm:cpt_set_fifo_underrun_reporting] *ERROR* uncleared
pch fifo underrun on pch transcoder A
[22988.645050] [drm:cpt_serr_int_handler] *ERROR* PCH transcoder A FIFO
underrun
[22988.645987] [drm:ivybridge_set_fifo_underrun_reporting] *ERROR*
uncleared fifo underrun on pipe A
[22988.645989] [drm:ivb_err_int_handler] *ERROR* Pipe A FIFO underrun




signature.asc
Description: OpenPGP digital signature


Re: Installing Linux on a Mac Mini without OSX

2014-12-04 Thread Ric Moore

On 12/04/2014 04:29 PM, Brian Sammon wrote:

On Thu, 04 Dec 2014 14:46:09 -0500
Stefan Monnier  wrote:


I was recently given a Mac Mini (Intel Mid 2007) that had been wiped.
I tried to install Debian (Wheezy) on it, and the installer reported
success, but  when it came time to eject and reboot, Debian didn't
boot from the hard drive.

[...]

Is there a way to install Debian/Linux on this machine that doesn't involve
buying or borrowing (or "borrowing") a copy of OSX?


If you managed to boot a plain-normal Debian CDROM installer, then your
machine's firmware has full BIOS support and you can boot a plain-normal
Debian install on the harddisk as well, as if the machine were
a normal PC.


Hmm... I was able to boot a plain-normal (I assume it is) Debian CDROM 
installer, but now I can't boot the plain-normal (I assume) Debian install that 
the installer said it installed.

The two questions I have:
Can I still assume that I have the firmware version that I want?
What do I do next to troubleshoot/fix this?

Another random question:
The installer gave me the choice of installing Grub on the partition or on the 
Master Boot Record.  Which of these should I choose?


If possible the normal route would be to the MBR. If you can boot from 
the CD install disk to a live session as root in a terminal window:

grub-install /dev/sda
update-grub
... I ~think~ will do the trick. I'd check this link out first though:
http://ubuntuforums.org/archive/index.php/t-24113.html
One of the above methods should get grub set correctly. Good Luck! Ric


--
My father, Victor Moore (Vic) used to say:
"There are two Great Sins in the world...
..the Sin of Ignorance, and the Sin of Stupidity.
Only the former may be overcome." R.I.P. Dad.
Linux user# 44256


--
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/5480dc32.9030...@gmail.com



Re: Replacing systemd in Jessie

2014-12-04 Thread Ric Moore

On 12/04/2014 03:16 PM, Lisi Reisz wrote:

On Thursday 04 December 2014 19:41:44 Brad Rogers wrote:

On Thu, 4 Dec 2014 18:48:31 +
Brian  wrote:

Hello Brian,


It probably also makes my behaviour stupid. But stupidity is in short
supply as you two have a monopoly on it and it doesn't look like you
you are going to do any sharing.


We were talking about a subset of developers, not *all* of them.
Re-read the thread, and that should become clear.


No, this is what had started that part of the thread:


User's do contrain.  They even dictate.  Always have.  Developers
should, if they are samrt, be developing what customers want or need.
Not the other way around. That's the formula for going out of business.
Listening to your customers as well as your potential customers is just
good business.


A generalised comment.


"Glittering Generality" perhaps? :) Ric




--
My father, Victor Moore (Vic) used to say:
"There are two Great Sins in the world...
..the Sin of Ignorance, and the Sin of Stupidity.
Only the former may be overcome." R.I.P. Dad.
Linux user# 44256


--
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/5480d806.1010...@gmail.com



Re: Replacing systemd in Jessie

2014-12-04 Thread Ric Moore

On 12/04/2014 12:33 PM, Patrick Bartek wrote:

On Wed, 03 Dec 2014, Brad Rogers wrote:


On Wed, 3 Dec 2014 09:24:03 -0800
Patrick Bartek  wrote:

Hello Patrick,


use and no one else's, why distribute it at all?


Simple:  Ego.



Perhaps.  Or insecurity, and the need for validation.  Or arrogance.
Or all the above.


Or perhaps to move Linux along where the likes of Google and Amazon has 
moved forwards to? That could be a reason, especially for servers. 
Unifying packaging could be another. If Linux is to have a paradigm 
shift, it could actually be what we need. I remain hopeful that the 
"Next Big Thing" happens within the Linux camp and not Apple's or 
Microsoft's. Could happen ya know. :) Ric




--
My father, Victor Moore (Vic) used to say:
"There are two Great Sins in the world...
..the Sin of Ignorance, and the Sin of Stupidity.
Only the former may be overcome." R.I.P. Dad.
Linux user# 44256


--
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/5480d77d.3070...@gmail.com



Re: Installing Linux on a Mac Mini without OSX

2014-12-04 Thread Brian Sammon
On Thu, 04 Dec 2014 14:46:09 -0500
Stefan Monnier  wrote:

> > I was recently given a Mac Mini (Intel Mid 2007) that had been wiped.
> > I tried to install Debian (Wheezy) on it, and the installer reported
> > success, but  when it came time to eject and reboot, Debian didn't
> > boot from the hard drive.
> [...]
> > Is there a way to install Debian/Linux on this machine that doesn't involve
> > buying or borrowing (or "borrowing") a copy of OSX?
> 
> If you managed to boot a plain-normal Debian CDROM installer, then your
> machine's firmware has full BIOS support and you can boot a plain-normal
> Debian install on the harddisk as well, as if the machine were
> a normal PC.

Hmm... I was able to boot a plain-normal (I assume it is) Debian CDROM 
installer, but now I can't boot the plain-normal (I assume) Debian install that 
the installer said it installed.

The two questions I have:
Can I still assume that I have the firmware version that I want?
What do I do next to troubleshoot/fix this?

Another random question:
The installer gave me the choice of installing Grub on the partition or on the 
Master Boot Record.  Which of these should I choose?


-- 
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/20141204162907.0de983753677069650c9d...@brisammon.fastmail.fm



Re: Replacing systemd in Jessie

2014-12-04 Thread Brad Rogers
On Thu, 4 Dec 2014 20:16:16 +
Lisi Reisz  wrote:

Hello Lisi,

>No, this is what had started that part of the thread:

I meant from where I chipped in.  Sorry I didn't make it clear.

-- 
 Regards  _
 / )   "The blindingly obvious is
/ _)radnever immediately apparent"
Well well well, you just can't tell
My Michelle - Guns 'N' Roses


pgp8imolZyza8.pgp
Description: OpenPGP digital signature


Re: Installing Linux on a Mac Mini without OSX

2014-12-04 Thread Brian Sammon
On Thu, 04 Dec 2014 19:46:22 +0100
Jerome BENOIT  wrote:

> > Two particular subtasks that I may need to do that seem to require
> > OSX: 1) "Blessing" a partition 2) Checking what version of firmware
> > it has (some versions have BIOS compatibility)
> > 
> > Any pointers/suggestions?
> 
> I will look towards a grub issue, specially if your partition is a gpt 
> partition table.
> For a gpt partition table, you must have a `bios grub' partition. 
> 
> > I'm also looking into PureDarwin as a possible solution.
> > 
> Debian is definitely better, do not trust the folks on the PureDarwin forums.

Ouch.

I have not seen any extravagant claims on behalf of PureDarwin.  Mostly just 
apologetic caveats that it's not quite yet ready for primetime.

In any case my interest in PureDarwin was primarily that it might have a 
"bless" command and/or a way to query the firmware version.

However, other messages in this thread suggest that neither of those two things 
are completely necessary.


-- 
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/20141204152621.6c99683101a49b2c142ea...@fastmail.fm



Re: Installing Linux on a Mac Mini without OSX

2014-12-04 Thread Jerome BENOIT


On 04/12/14 21:30, Brian Sammon wrote:
> On Thu, 04 Dec 2014 19:46:22 +0100
> Jerome BENOIT  wrote:
> 
>>> Two particular subtasks that I may need to do that seem to require
>>> OSX: 1) "Blessing" a partition 2) Checking what version of firmware
>>> it has (some versions have BIOS compatibility)
>>>
>>> Any pointers/suggestions?
>>
>> I will look towards a grub issue, specially if your partition is a gpt 
>> partition table.
>> For a gpt partition table, you must have a `bios grub' partition. 
>>
>>> I'm also looking into PureDarwin as a possible solution.
>>>
>> Debian is definitely better, do not trust the folks on the PureDarwin forums.
I was just kidding.
> 
> Ouch.
> 
> I have not seen any extravagant claims on behalf of PureDarwin.  Mostly just 
> apologetic caveats that it's not quite yet ready for primetime.
> 
> In any case, my interest in PureDarwin was primarily that it might have a 
> "bless" command and/or a way to query the firmware version.
> Other messages in this thread suggest that neither of these two things may be 
> fully necessary.

True.


Jerome
> 
> 


-- 
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/5480c65a.7070...@rezozer.net



Re: Replacing systemd in Jessie

2014-12-04 Thread Lisi Reisz
On Thursday 04 December 2014 19:41:44 Brad Rogers wrote:
> On Thu, 4 Dec 2014 18:48:31 +
> Brian  wrote:
>
> Hello Brian,
>
> >It probably also makes my behaviour stupid. But stupidity is in short
> >supply as you two have a monopoly on it and it doesn't look like you
> >you are going to do any sharing.
>
> We were talking about a subset of developers, not *all* of them.
> Re-read the thread, and that should become clear.

No, this is what had started that part of the thread:


User's do contrain.  They even dictate.  Always have.  Developers
should, if they are samrt, be developing what customers want or need.
Not the other way around. That's the formula for going out of business.
Listening to your customers as well as your potential customers is just
good business.


A generalised comment.

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



Re: Installing Linux on a Mac Mini without OSX

2014-12-04 Thread Brian Sammon
On Thu, 04 Dec 2014 19:46:22 +0100
Jerome BENOIT  wrote:

> > Two particular subtasks that I may need to do that seem to require
> > OSX: 1) "Blessing" a partition 2) Checking what version of firmware
> > it has (some versions have BIOS compatibility)
> > 
> > Any pointers/suggestions?
> 
> I will look towards a grub issue, specially if your partition is a gpt 
> partition table.
> For a gpt partition table, you must have a `bios grub' partition. 
> 
> > I'm also looking into PureDarwin as a possible solution.
> > 
> Debian is definitely better, do not trust the folks on the PureDarwin forums.

Ouch.

I have not seen any extravagant claims on behalf of PureDarwin.  Mostly just 
apologetic caveats that it's not quite yet ready for primetime.

In any case, my interest in PureDarwin was primarily that it might have a 
"bless" command and/or a way to query the firmware version.
Other messages in this thread suggest that neither of these two things may be 
fully necessary.


-- 
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/20141204153052.1875257a804ff0c298980...@brisammon.fastmail.fm



Re: -cpu option of qemu

2014-12-04 Thread Reco
 Hi.

On Thu, 04 Dec 2014 10:14:21 -0800
pe...@easthope.ca wrote:

> man qenu has, 
> "-cpu ? for list and additional feature selection".
> 
> Here,
> peter@armada:~$ qemu-system-x86_64 -cpu ?
> Unable to find x86 CPU definition
> 
> How should CPU definitions be provided? 
> Is there a package to install?

Seems to me that #652281 has returned.

Do you have the file such as /etc/qemu/target-x86_64.conf?

What does change if you add to /etc/qemu/target-x86_64.conf strings
from https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=652281#17 ?

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/20141204231556.30d07399082a0b426abe7...@gmail.com



Re: Replacing systemd in Jessie

2014-12-04 Thread Brad Rogers
On Thu, 4 Dec 2014 18:48:31 +
Brian  wrote:

Hello Brian,

>It probably also makes my behaviour stupid. But stupidity is in short
>supply as you two have a monopoly on it and it doesn't look like you
>you are going to do any sharing.

We were talking about a subset of developers, not *all* of them.
Re-read the thread, and that should become clear.

-- 
 Regards  _
 / )   "The blindingly obvious is
/ _)radnever immediately apparent"
You suck my blood like a leech
Death On Two Legs - Queen


pgpsnC6yH28f2.pgp
Description: OpenPGP digital signature


Re: Installing Linux on a Mac Mini without OSX

2014-12-04 Thread Stefan Monnier
> I was recently given a Mac Mini (Intel Mid 2007) that had been wiped.
> I tried to install Debian (Wheezy) on it, and the installer reported
> success, but  when it came time to eject and reboot, Debian didn't
> boot from the hard drive.
[...]
> Is there a way to install Debian/Linux on this machine that doesn't involve
> buying or borrowing (or "borrowing") a copy of OSX?

If you managed to boot a plain-normal Debian CDROM installer, then your
machine's firmware has full BIOS support and you can boot a plain-normal
Debian install on the harddisk as well, as if the machine were
a normal PC.

> Is it easier to install linux on a USB disk and run it off of that?

Nope.  Most of the Apple machines of that time are simply unable to boot
from USB unless you're using an EFI boot.

> Two particular subtasks that I may need to do that seem to require OSX:
> 1) "Blessing" a partition

AFAIK the only tool for that is `hfspbless' which is not widely
distributed, but if you look hard enough you should be able to find it.

See also https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=427492.

Note that this is only need if you want to boot via EFI rather than via
the BIOS.

> 2) Checking what version of firmware it has (some versions have BIOS
>compatibility)

Indeed, the BIOS compatibility was not available in earlier machines's
firmware (tho available as a firmware upgrade).  But since you seem to
have booted Debian's installer, it seems your firmware is already able
to handle BIOS.

One more detail: IIUC when booted via EFI your machine's video hardware
might not be initialized the way Linux and Xorg expect it to be, so Xorg
may fail to start (at least that's the case for my Mac Mini of around
2006).  You can fix that by adding some commands in the grub.cfg
(assuming you use grub-efi) which preload some vesa-bios to your video
hardware (something like "loadbios /boot/vbios.bin /boot/int10.bin" tho
you also need to put those corresponding files in your boot partition).


Stefan




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



Re: Installing Linux on a Mac Mini without OSX

2014-12-04 Thread Jon Leonard
On Thu, Dec 04, 2014 at 01:25:37PM -0500, Brian Sammon wrote:
> I was recently given a Mac Mini (Intel Mid 2007) that had been wiped.
> 
> I tried to install Debian (Wheezy) on it, and the installer reported success, 
> but 
> when it came time to eject and reboot, Debian didn't boot from the hard drive.
> 
> Googling finds me various pages about installing Linux where one of the steps 
> is something like "Boot into OSX"
> 
> Is there a way to install Debian/Linux on this machine that doesn't involve 
> buying or borrowing (or "borrowing") a copy of OSX?  Is it easier to install 
> linux on a USB disk and run it off of that?
> 
> Two particular subtasks that I may need to do that seem to require OSX:
> 1) "Blessing" a partition
> 2) Checking what version of firmware it has (some versions have BIOS
>compatibility)
> 
> Any pointers/suggestions?

I saw similar behavior installing on more recent Mac Minis.  There, the issue
was that the Mac firmware's idea of the boot sequence didn't match Debian's.

I wound up solving this by installing rEFInd (from
http://www.rodsbooks.com/refind/
) , though not always the same way.  You'd presumably need to install it
to the EFI partition if you don't have a Mac partition.  I think it's also
possible to get Grub or even the Linux Kernel set up to boot as the EFI
loader, but I stopped trying that after I got booting to work reliably.

It should be possible to boot the Debian installer in rescue mode, get a
shell, and do the install from there.

Jon Leonard

> I'm also looking into PureDarwin as a possible solution.
> 
> 
> -- 
> 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/20141204132537.c44457fee702caa9b3bac...@brisammon.fastmail.fm


-- 
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/20141204192110.gh22...@slimy.com



Re: Replacing systemd in Jessie

2014-12-04 Thread Brian
On Thu 04 Dec 2014 at 09:33:30 -0800, Patrick Bartek wrote:

> On Wed, 03 Dec 2014, Brad Rogers wrote:
> 
> > On Wed, 3 Dec 2014 09:24:03 -0800
> > Patrick Bartek  wrote:
> > 
> > Hello Patrick,
> > 
> > >use and no one else's, why distribute it at all?
> > 
> > Simple:  Ego.
> > 
> 
> Perhaps.  Or insecurity, and the need for validation.  Or arrogance.
> Or all the above.

Mmm. I write some programs which perform useful jobs for me. Maybe they
include a browser or a mailer or an init system, I do it to scratch my
itch and because it is fun.

Then I ask myself: maybe they might benefit someone? So I distribute
them, allowing anyone to do the same even after altering them. It could
be some of the changes could benefit my way of working but it doesn't
really matter as I'm happy with what I produced.

So that makes me

  * Egotistcal
  * Insecure
  * Requiring validation
  * Arrogant

It probably also makes my behaviour stupid. But stupidity is in short
supply as you two have a monopoly on it and it doesn't look like you
you are going to do any sharing.


-- 
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/04122014182643.502af8473...@desktop.copernicus.demon.co.uk



-cpu option of qemu

2014-12-04 Thread peter
man qenu has, 
"-cpu ? for list and additional feature selection".

Here,
peter@armada:~$ qemu-system-x86_64 -cpu ?
Unable to find x86 CPU definition

How should CPU definitions be provided? 
Is there a package to install?

Thanks,Peter E.
 
-- 
123456789 123456789 123456789 123456789 123456789 123456789 123456789 12
Tel +1 360 639 0202  http://carnot.yi.org/  Bcc: peter at easthope. ca


-- 
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/E1Xwauz-zZ-2Z@armada.invalid



Re: Installing Linux on a Mac Mini without OSX

2014-12-04 Thread Jerome BENOIT
Hello,

On 04/12/14 19:25, Brian Sammon wrote:
> I was recently given a Mac Mini (Intel Mid 2007) that had been
> wiped.
> 
> I tried to install Debian (Wheezy) on it, and the installer reported
> success, but when it came time to eject and reboot, Debian didn't
> boot from the hard drive.

I would consider eject as a comfort at this stage.
The reboot issue is the real issue here.

> 
> Googling finds me various pages about installing Linux where one of
> the steps is something like "Boot into OSX"

If you do not want a dual boot computer, forget this part and consider your box 
as
a regular box.

> 
> Is there a way to install Debian/Linux on this machine that doesn't
> involve buying or borrowing (or "borrowing") a copy of OSX? 

Take care as this model may be not be supported by last OS X.
You do not need it.

 Is it
> easier to install linux on a USB disk and run it off of that?
> 
> Two particular subtasks that I may need to do that seem to require
> OSX: 1) "Blessing" a partition 2) Checking what version of firmware
> it has (some versions have BIOS compatibility)
> 
> Any pointers/suggestions?

I will look towards a grub issue, specially if your partition is a gpt 
partition table.
For a gpt partition table, you must have a `bios grub' partition. 


> 
> I'm also looking into PureDarwin as a possible solution.
> 
Debian is definitely better, do not trust the folks on the PureDarwin forums.

Best wishes,
Jerome

> 

-- 
Jerome BENOIT, Ph.D. | jgmbenoit-at+rezozer*dot_net


-- 
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/5480abfe.1010...@rezozer.net



Installing Linux on a Mac Mini without OSX

2014-12-04 Thread Brian Sammon
I was recently given a Mac Mini (Intel Mid 2007) that had been wiped.

I tried to install Debian (Wheezy) on it, and the installer reported success, 
but 
when it came time to eject and reboot, Debian didn't boot from the hard drive.

Googling finds me various pages about installing Linux where one of the steps 
is something like "Boot into OSX"

Is there a way to install Debian/Linux on this machine that doesn't involve 
buying or borrowing (or "borrowing") a copy of OSX?  Is it easier to install 
linux on a USB disk and run it off of that?

Two particular subtasks that I may need to do that seem to require OSX:
1) "Blessing" a partition
2) Checking what version of firmware it has (some versions have BIOS
   compatibility)

Any pointers/suggestions?

I'm also looking into PureDarwin as a possible solution.


-- 
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/20141204132537.c44457fee702caa9b3bac...@brisammon.fastmail.fm



Re: LVM RAID5 with missing disk?

2014-12-04 Thread Dan Ritter
On Thu, Dec 04, 2014 at 02:13:59PM +0100, mad wrote:
> Hi!
> 
> I wanted to create a RAID5 with lvm. The basic setup is something like
> 
> lvcreate --type raid5 -i 2 -L 1G -n my_lv my_vg
> 
> which would mean 3 physical drives would be used in this RAID5. But can
> I specify that one drive is missing as it is possible with mdadm?

I don't think so, no. You can create your RAID with mdadm and
put LVM on top of that.

In general I strongly recommend against using RAID5. RAID1, 10,
or 6 are all better options if your data's availability is
important to you.

-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/20141204175144.gf30...@randomstring.org



Re: Replacing systemd in Jessie

2014-12-04 Thread Patrick Bartek
On Wed, 03 Dec 2014, Brad Rogers wrote:

> On Wed, 3 Dec 2014 09:24:03 -0800
> Patrick Bartek  wrote:
> 
> Hello Patrick,
> 
> >use and no one else's, why distribute it at all?
> 
> Simple:  Ego.
> 

Perhaps.  Or insecurity, and the need for validation.  Or arrogance.
Or all the above.

B


-- 
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/20141204093330.28501...@debian7.boseck208.net



Re: Debian fork: 'Devuan', Debian without Systemd

2014-12-04 Thread Jimmy Johnson

On 12/03/2014 07:13 AM, Erwan David wrote:


As explained several times on this ML, depending against libsystemd0
package doesn't mean anything about requiring systemd to be used as
PID1 or not. Even Ian's GR was not taking the "I don't want any systemd
package on my machine" use case into account you know.


Why focus on PID1 ? As I said, systemd-resolved proved to be
vulnerable to a well known attack.  What makes us think that more
quality was put in systemd-logind ? Not wanting systemd means not
wanting it *at all*. I personnally do not trust it for critical system
tasks.



First Squeeze has to get upgraded to Wheezy without any systemd 
components and then upgrade Wheezy to Jessie without systemd.

--
Jimmy Johnson

Debian - Wheezy - KDE 4.8.4 - AMD64 - EXT4 at sda1
Registered Linux User #380263


--
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/54806cdf.6000...@gmail.com



LVM RAID5 with missing disk?

2014-12-04 Thread mad
Hi!

I wanted to create a RAID5 with lvm. The basic setup is something like

lvcreate --type raid5 -i 2 -L 1G -n my_lv my_vg

which would mean 3 physical drives would be used in this RAID5. But can
I specify that one drive is missing as it is possible with mdadm?

TIA
mad


-- 
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/54805e17.7040...@sharktooth.de



Test only

2014-12-04 Thread Danny
Hi guys,

Please ignore this ... Just testing a few tweaks I made in postfix ... :)

Thank You

Danny


-- 
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/20141204122252.GF11639@fever.havannah.local



Re: Haven't seen this ssh output before

2014-12-04 Thread Jochen Spieker
berenger.mo...@neutralite.org:
>
> debsecan.
> 
> This is a tool which lists CVE (Common Vulnerabilities and
> Exposures) that the packages you installed contains.
> I think you might get some hints if you make a diff between the old
> (you said you have un-upgraded systems) and the new (the system
> which gaves you problems) systems.

Debsecan is a great tool, but to find out whether a specific upgrade
contains remedy for a specific CVE the easiest way is usually to just
look at the changelog. I would be very surprised if OpenSSH people close
security holes without mentioning that explicitly.


J.
-- 
If I was Mark Chapman I would have shot John Lennon with a water pistol.
[Agree]   [Disagree]
 


signature.asc
Description: Digital signature


Re: boot fails on jessie on Acer Travelmate

2014-12-04 Thread Pascal Hambourg
Pierre Couderc a écrit :
> One big difference is that after jessie installation boot flag has 
> disappeared : gpt :
> 
> wheezy :
> 
> Model: ATA Crucial_CT480M50 (scsi)
> Disk /dev/sda: 480GB
> Sector size (logical/physical): 512B/4096B
> Partition Table: gpt
> 
> Number  Start   EndSizeFile system Name  Flags
>   1  1049kB  512MB  511MB   fat32 boot
>   2  512MB   467GB  467GB   ext4
>   3  467GB   480GB  12.8GB  linux-swap(v1)
> 
> jessie :
> 
> Model: ATA Crucial_CT480M50 (scsi)
> Disk /dev/sda: 480GB
> Sector size (logical/physical): 512B/4096B
> Partition Table: gpt
> 
> Number  Start   EndSizeFile system Name  Flags
>   1  1049kB  538MB  537MB   fat32
>   2  538MB   467GB  467GB   ext4
>   3  467GB   480GB  12.8GB  linux-swap(v1)

In parted on a GPT disk, the "boot" flag identifies an EFI system
partition. An alias is "esp". As Simon suggested, you can toggle the
flag (with parted, not fdisk) and check whether the system can boot again.

parted /dev/sda set 1 boot on


-- 
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/54801b95.4060...@plouf.fr.eu.org