On Sun, Jan 15, 2012 at 2:35 PM, Stephen Powell wrote:
> On Sun, 15 Jan 2012 08:24:40 -0500 (EST), Arno Schuring wrote:
>> John Hasler (jhas...@newsguy.com on 2012-01-14 12:25 -0600):
>>>
>>> IMHO putting critical
>>> boot software in an "unallocated" area that other software will (not
>>> unreaso
On Sun, 15 Jan 2012 08:24:40 -0500 (EST), Arno Schuring wrote:
> John Hasler (jhas...@newsguy.com on 2012-01-14 12:25 -0600):
>> IMHO putting critical
>> boot software in an "unallocated" area that other software will (not
>> unreasonably) assume contains nothing important is a loony idea.
>
> It'
I wrote:
> IMHO putting critical boot software in an "unallocated" area that
> other software will (not unreasonably) assume contains nothing
> important is a loony idea.
Arno Schuring writes:
> It's not any more loony than hardcoding the disk sectors in which the
> kernel file resides.
Like Gru
John Hasler (jhas...@newsguy.com on 2012-01-14 12:25 -0600):
> Panayiotis writes:
> > I have another computer running Wheezy with lvm and it's working
> > fine. Maybe it's the sum of the md driver + lvm driver that is too
> > big to fit in the gap?
>
> Use Lilo. It doesn't use the "gap" at all.
T
> Panayiotis writes:
>> I have another computer running Wheezy with lvm and it's working fine.
>> Maybe it's the sum of the md driver + lvm driver that is too big to
>> fit in the gap?
>
> Use Lilo. It doesn't use the "gap" at all. IMHO putting critical boot
> software in an "unallocated" area t
Panayiotis writes:
> I have another computer running Wheezy with lvm and it's working fine.
> Maybe it's the sum of the md driver + lvm driver that is too big to
> fit in the gap?
Use Lilo. It doesn't use the "gap" at all. IMHO putting critical boot
software in an "unallocated" area that other s
On Σαβ, 2012-01-14 at 16:23 +0100, tv.deb...@googlemail.com wrote:
> 14/01/2012 15:21, Panayiotis Karabassis wrote:
> > Thanks to all.
> >
> > On 01/14/2012 03:06 PM, tv.deb...@googlemail.com wrote:
> >> 14/01/2012 13:18, Tom H:
> >>> On Sat, Jan 14, 2012 at 5:06 AM, Panayiotis
> >>> Karabassis w
I did that once on an install and figured out what I did wrong too. This
wasn't with debian though but with slackware. What I did was to allocate
too little swap space in my swap partition. If you manually chose the
amount of swap space you'll need to increase that amount then the problem
go
14/01/2012 15:21, Panayiotis Karabassis wrote:
Thanks to all.
On 01/14/2012 03:06 PM, tv.deb...@googlemail.com wrote:
14/01/2012 13:18, Tom H:
On Sat, Jan 14, 2012 at 5:06 AM, Panayiotis
Karabassis wrote:
On my desktop, which is running Squeeze, I tried to upgrade some
packages to their Wh
On Sat, 14 Jan 2012 09:21:15 -0500 (EST), Panayiotis Karabassis wrote:
>
> Can Lilo boot from an LVM partition sitting on top of mdadm?
Ah! Well, that's a horse of a different color, as the old saying goes.
I honestly don't know. There is information in the man pages for lilo
and lilo.conf conc
On 01/14/2012 03:46 PM, Stephen Powell wrote:
> On Sat, 14 Jan 2012 05:06:33 -0500 (EST), Panayiotis Karabassis wrote:
>>
>> On my desktop, which is running Squeeze, I tried to upgrade some
>> packages to their Wheezy version. I have now reverted the upgrade, but I
>> am alarmed.
>>
>> One of the p
Thanks to all.
On 01/14/2012 03:06 PM, tv.deb...@googlemail.com wrote:
> 14/01/2012 13:18, Tom H:
>> On Sat, Jan 14, 2012 at 5:06 AM, Panayiotis
>> Karabassis wrote:
>>>
>>> On my desktop, which is running Squeeze, I tried to upgrade some
>>> packages to their Wheezy version. I have now reverted
On Sat, 14 Jan 2012 05:06:33 -0500 (EST), Panayiotis Karabassis wrote:
>
> On my desktop, which is running Squeeze, I tried to upgrade some
> packages to their Wheezy version. I have now reverted the upgrade, but I
> am alarmed.
>
> One of the packages was grub2 which was at version
> 1.98+201008
14/01/2012 13:18, Tom H:
On Sat, Jan 14, 2012 at 5:06 AM, Panayiotis Karabassis wrote:
On my desktop, which is running Squeeze, I tried to upgrade some
packages to their Wheezy version. I have now reverted the upgrade, but I
am alarmed.
One of the packages was grub2 which was at version
1.98+
On Sat, Jan 14, 2012 at 6:55 AM, Thierry Chatelet wrote:
> On Saturday 14 January 2012 11:06:33 Panayiotis Karabassis wrote:
>>
>> On my desktop, which is running Squeeze, I tried to upgrade some
>> packages to their Wheezy version. I have now reverted the upgrade, but I
>> am alarmed.
>>
>> One o
On Sat, Jan 14, 2012 at 6:18 AM, Panayiotis Karabassis wrote:
>
> /dev/sda1 63 1953520064 976760001 fd Linux raid
> autodetect
The post-MBR gap's OK.
How large is "core.img"?
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Tr
On Sat, Jan 14, 2012 at 5:06 AM, Panayiotis Karabassis wrote:
>
> On my desktop, which is running Squeeze, I tried to upgrade some
> packages to their Wheezy version. I have now reverted the upgrade, but I
> am alarmed.
>
> One of the packages was grub2 which was at version
> 1.98+20100804-14+sque
On Saturday 14 January 2012 11:06:33 Panayiotis Karabassis wrote:
> Hi,
>
> On my desktop, which is running Squeeze, I tried to upgrade some
> packages to their Wheezy version. I have now reverted the upgrade, but I
> am alarmed.
>
> One of the packages was grub2 which was at version
> 1.98+20100
On 01/14/2012 12:31 PM, tv.deb...@googlemail.com wrote:
> 14/01/2012 11:06, Panayiotis Karabassis wrote:
>> Hi,
>>
>> On my desktop, which is running Squeeze, I tried to upgrade some
>> packages to their Wheezy version. I have now reverted the upgrade, but I
>> am alarmed.
>>
>> One of the packages
14/01/2012 11:06, Panayiotis Karabassis wrote:
Hi,
On my desktop, which is running Squeeze, I tried to upgrade some
packages to their Wheezy version. I have now reverted the upgrade, but I
am alarmed.
One of the packages was grub2 which was at version
1.98+20100804-14+squeeze1 and was upgraded
20 matches
Mail list logo
