Le 20.04.2013 19:58, Richard Owlett a écrit :
Wayne Topa wrote:
I KNOW. I KNOW ;)
But you need to know the right key words.
As a matter of fact Mr. Powell had just responded to my post
suggesting I read one of his pagers.
He beat you by minutes.
Thanks.
HTH
--
Wayne
So, may we conclu
On 04/20/2013 02:07 PM, Lisi Reisz wrote:
On Saturday 20 April 2013 17:51:54 Stephen Powell wrote:
On Sat, 20 Apr 2013 10:12:51 -0400 (EDT), Richard Owlett wrote:
I need complete documentation on LILO with emphasis on lilo.conf.
I don't know about complete documentation, but the best lilo tut
On Saturday 20 April 2013 17:51:54 Stephen Powell wrote:
> On Sat, 20 Apr 2013 10:12:51 -0400 (EDT), Richard Owlett wrote:
> > I need complete documentation on LILO with emphasis on lilo.conf.
>
> I don't know about complete documentation, but the best lilo tutorial
> that I know of is
>
>http:
Wayne Topa wrote:
On 04/20/2013 12:11 PM, Richard Owlett wrote:
Tony van der Hoff wrote:
On 20/04/13 16:19, Richard Owlett wrote:
Tony van der Hoff wrote:
On 20/04/13 15:50, Richard Owlett wrote:
Tony van der Hoff wrote:
On 20/04/13 15:12, Richard Owlett wrote:
I need complete documentatio
Stephen Powell wrote:
On Sat, 20 Apr 2013 10:12:51 -0400 (EDT), Richard Owlett wrote:
I need complete documentation on LILO with emphasis on lilo.conf.
I don't know about complete documentation, but the best lilo tutorial
that I know of is
http://users.wowway.com/~zlinuxman/lilo.htm
I w
On 04/20/2013 12:11 PM, Richard Owlett wrote:
Tony van der Hoff wrote:
On 20/04/13 16:19, Richard Owlett wrote:
Tony van der Hoff wrote:
On 20/04/13 15:50, Richard Owlett wrote:
Tony van der Hoff wrote:
On 20/04/13 15:12, Richard Owlett wrote:
I need complete documentation on LILO with emph
On Sat, 20 Apr 2013 10:12:51 -0400 (EDT), Richard Owlett wrote:
>
> I need complete documentation on LILO with emphasis on lilo.conf.
I don't know about complete documentation, but the best lilo tutorial
that I know of is
http://users.wowway.com/~zlinuxman/lilo.htm
I wrote the above-mentione
Tony van der Hoff wrote:
On 20/04/13 16:19, Richard Owlett wrote:
Tony van der Hoff wrote:
On 20/04/13 15:50, Richard Owlett wrote:
Tony van der Hoff wrote:
On 20/04/13 15:12, Richard Owlett wrote:
I need complete documentation on LILO with emphasis on lilo.conf .
Assume I'm stranded on a de
On 20/04/13 16:19, Richard Owlett wrote:
> Tony van der Hoff wrote:
>> On 20/04/13 15:50, Richard Owlett wrote:
>>> Tony van der Hoff wrote:
On 20/04/13 15:12, Richard Owlett wrote:
> I need complete documentation on LILO with emphasis on lilo.conf .
> Assume I'm stranded on a desert i
Tony van der Hoff wrote:
On 20/04/13 15:50, Richard Owlett wrote:
Tony van der Hoff wrote:
On 20/04/13 15:12, Richard Owlett wrote:
I need complete documentation on LILO with emphasis on lilo.conf .
Assume I'm stranded on a desert isle (SW Missouri is a fair
approximation) with a computer and
On 20/04/13 15:50, Richard Owlett wrote:
> Tony van der Hoff wrote:
>> On 20/04/13 15:12, Richard Owlett wrote:
>>> I need complete documentation on LILO with emphasis on lilo.conf .
>>> Assume I'm stranded on a desert isle (SW Missouri is a fair
>>> approximation) with a computer and a set of inst
Tony van der Hoff wrote:
On 20/04/13 15:12, Richard Owlett wrote:
I need complete documentation on LILO with emphasis on lilo.conf .
Assume I'm stranded on a desert isle (SW Missouri is a fair
approximation) with a computer and a set of install disks.
What *ONE* document will answer ALL my LILO
berenger.mo...@neutralite.org wrote:
Le 20.04.2013 16:12, Richard Owlett a écrit :
I need complete documentation on LILO with emphasis on
lilo.conf .
Assume I'm stranded on a desert isle (SW Missouri is a fair
approximation) with a computer and a set of install disks.
What *ONE* document will an
On 20/04/13 15:12, Richard Owlett wrote:
> I need complete documentation on LILO with emphasis on lilo.conf .
> Assume I'm stranded on a desert isle (SW Missouri is a fair
> approximation) with a computer and a set of install disks.
> What *ONE* document will answer ALL my LILO questions.
> Hint: m
Le 20.04.2013 16:12, Richard Owlett a écrit :
I need complete documentation on LILO with emphasis on lilo.conf .
Assume I'm stranded on a desert isle (SW Missouri is a fair
approximation) with a computer and a set of install disks.
What *ONE* document will answer ALL my LILO questions.
Hint: man
On Thu, 29 Mar 2012 22:31:05 -0400 (EDT), Marc Shapiro wrote:
>
> I apologize for not posting this sooner, but this was the first chance
> that I had to reboot and go into the BIOS Setup.
>
> To answer your questions...
>
> AMI BIOS v02.54 4/22/2005
>
> Features Setup
>
On Thu, 29 Mar 2012 19:39:54 -0700, Marc wrote in message
<4f751cfa.1050...@gmail.com>:
> On 03/27/12 03:59, Arnt Karlsen wrote:
> > On Mon, 26 Mar 2012 05:43:45 -0500, Stan wrote in message
> > ..one thing lilo will do, is hop back to the old disk if you make
> > that a menu option. Found that
On 03/27/12 03:59, Arnt Karlsen wrote:
On Mon, 26 Mar 2012 05:43:45 -0500, Stan wrote in message
..one thing lilo will do, is hop back to the old disk if you make
that a menu option. Found that out trying to boot /dev/md0 rather
than dance between /dev/hd{a,b}0. ;o)
Absolutely! I left the men
Stephen,
I apologize for not posting this sooner, but this was the first chance
that I had to reboot and go into the BIOS Setup.
To answer your questions...
AMI BIOS v02.54 4/22/2005
Features Setup
USB Function For DOSEnabled (Default was Disabled)
Marc
On Mon, 26 Mar 2012 05:43:45 -0500, Stan wrote in message
<4f704861.1040...@hardwarefreak.com>:
> On 3/25/2012 10:58 PM, Marc Shapiro wrote:
>
> > I should have googled before posting. Aparently lilo is not
> > capable of recognizing USB keyboards, but the BIOS can. All I
> > needed to do was
On Sun, 25 Mar 2012 23:58:15 -0400 (EDT), Marc Shapiro wrote:
>
> I should have googled before posting. Aparently lilo is not capable of
> recognizing USB keyboards, but the BIOS can. All I needed to do was
> find the right BIOS option. The only tricky part was that this option
> (in my BIOS
On 3/25/2012 10:58 PM, Marc Shapiro wrote:
> I should have googled before posting. Aparently lilo is not capable of
> recognizing USB keyboards, but the BIOS can. All I needed to do was
> find the right BIOS option. The only tricky part was that this option
> (in my BIOS) says nothing about key
On 03/25/12 20:31, Marc Shapiro wrote:
I just migrated my / partition to a larger partition on a new disk. I
used find piped to cpio which took care of everything except
modifications to fstab and lilo.conf and then running lilo. I made those
changes, leaving tho old setup in lilo.conf as the def
On Sun, 26 Sep 2010 20:01:36 -0400 (EDT)
Stephen Powell wrote:
> >> I also don't see any zz-lilo hook scripts, which the latest version
> >> of lilo would have installed. Reinstall the latest version of
> >> lilo. This should also install a file
> >> in /etc/initramfs/post-update.d called lilo o
On Sun, 26 Sep 2010 19:51:12 -0400 (EDT)
Stephen Powell wrote:
> > # Kernel image management overrides
> > # See kernel-img.conf(5) for details
> > do_symlinks = no
> > relative_links = yes
> > do_bootloader = no
> > do_bootfloppy = no
> > do_initrd = yes
> > link_in_boot = yes
> > postinst_hook
On Sun, 26 Sep 2010 22:29:34 -0400 (EDT), bri...@aracnet.com wrote:
> On Sat, 25 Sep 2010 12:28:00 -0400 (EDT), Stephen Powell wrote:
>>
>> Several problems here. S30initramfs, S50symlink_hook,
>> K30initramfs, and K50symlink_hook, though they will still
>> work, I now consider obsolete. S30initr
On Sun, 26 Sep 2010 22:14:29 -0400 (EDT), bri...@aracnet.com wrote:
> On Sat, 25 Sep 2010 12:28:00 -0400 (EDT), Stephen Powell wrote:
>> I'm also going to need
>> to see the output of the following commands:
>>
>>ls -Al /dev/disk/by-id/
>
> lrwxrwxrwx 1 root root 9 Sep 26 18:12
> ata-WDC_WD
On Sat, 25 Sep 2010 12:28:00 -0400 (EDT)
Stephen Powell wrote:
>
> Several problems here. S30initramfs, S50symlink_hook,
> K30initramfs, and K50symlink_hook, though they will still
> work, I now consider obsolete. S30initramfs and K30initramfs
> were made obsolete by newer versions of the init
On Sat, 25 Sep 2010 12:28:00 -0400 (EDT)
Stephen Powell wrote:
> On Sat, 25 Sep 2010 03:40:04 -0400 (EDT), bri...@aracnet.com wrote:
> I'm also going to need
> to see the output of the following commands:
>
>ls -Al /dev/disk/by-id/
lrwxrwxrwx 1 root root 9 Sep 26 18:12 ata-WDC_WD2500YS-01
On Sat, 25 Sep 2010 03:40:04 -0400 (EDT), bri...@aracnet.com wrote:
>
> Before I post all that stuff, let me show you exactly what's happening
> on boot. I think there is something very strange going on and it may
> not be lilo.
>
> Lin_img0 is : /boot/vmlinuz
>
> When I boot using that entry
On Sat, 25 Sep 2010 00:54:12 -0400 (EDT), Stan Hoeppner wrote:
> Stephen Powell put forth on 9/24/2010 4:06 PM:
>> Current stock Debian kernels for the
>> amd64 architecture are right on the ragged edge of being too
>> large for lilo to load below the 16M line
>
> And the bulk of these ~16MB stock
On Sat, 25 Sep 2010 00:17:30 -0500
Stan Hoeppner wrote:
> bri...@aracnet.com put forth on 9/24/2010 7:42 PM:
>
> > right now I'm thinking I've got something misconfigured, but what ??
> > Running lilo manually should fix whatever's going on and it most
> > certainly isn't.
>
> Did you possibly
On Fri, 24 Sep 2010 21:18:25 -0400 (EDT)
Stephen Powell wrote:
Before I post all that stuff, let me show you exactly what's happening
on boot. I think there is something very strange going on and it may
not be lilo.
Lin_img0 is : /boot/vmlinuz
When I boot using that entry I get the following
bri...@aracnet.com put forth on 9/24/2010 7:42 PM:
> right now I'm thinking I've got something misconfigured, but what ??
> Running lilo manually should fix whatever's going on and it most
> certainly isn't.
Did you possibly lose your BIOS LBA configuration before the
dist-upgrade, and didn't kno
Stephen Powell put forth on 9/24/2010 4:06 PM:
> Current stock Debian kernels for the
> amd64 architecture are right on the ragged edge of being too
> large for lilo to load below the 16M line
And the bulk of these ~16MB stock kernels is the initrd, correct? Wow
those are huge. I'm so glad I rol
On Fri, 24 Sep 2010 20:42:56 -0400 (EDT), bri...@aracnet.com wrote:
>
> I've run lilo and rebooted multiple times and always get the same
> result.
Interesting. What happens if you specify
root=802
as an argument to the boot prompt?
> right now I'm thinking I've got something misconfigured
On Fri, 24 Sep 2010 17:06:43 -0400 (EDT)
Stephen Powell wrote:
> On Fri, 24 Sep 2010 10:10:53 -0400 (EDT), bri...@aracnet.com wrote:
> >
> > I deleted one of the older images and when it finished I got this
> > mess:
> >
> > Could not find postrm hook script [lilo-update].
> > Looked in: '/bin'
On Fri, 24 Sep 2010 10:10:53 -0400 (EDT), bri...@aracnet.com wrote:
>
> I deleted one of the older images and when it finished I got this mess:
>
> Could not find postrm hook script [lilo-update].
> Looked in: '/bin', '/sbin', '/usr/bin', '/usr/sbin'
> Examining /etc/kernel/postrm.d .
> Purging c
On Fri, 24 Sep 2010 11:57:25 +0200
David Baron wrote:
> Try reinstalling your kernel, or if you compiled your own, install a
> recent linux-image-2.6.32.5 from Sid. The postinstall script will
> point /etc/fstab and lilo.conf to the newer UUID references and then
> it should play.
>
> The postin
On Fri, 24 Sep 2010 11:57:25 +0200
David Baron wrote:
> Try reinstalling your kernel, or if you compiled your own, install a
> recent linux-image-2.6.32.5 from Sid. The postinstall script will
> point /etc/fstab and lilo.conf to the newer UUID references and then
> it should play.
I'll give it a
Try reinstalling your kernel, or if you compiled your own, install a recent
linux-image-2.6.32.5 from Sid. The postinstall script will point /etc/fstab
and lilo.conf to the newer UUID references and then it should play.
The postinstall for home-brew kernels does not do this for you, I'm afraid a
In <4c9c2ca9.3020...@hardwarefreak.com>, Stan Hoeppner wrote:
>bri...@aracnet.com put forth on 9/23/2010 11:25 PM:
>>> No, that's normal. What had you changed on the system immediately
>>> prior to this boot problem occurring?
>>
>> apt-get dist-upgrade, natch.
>
>WTF is "natch"?
Shortening of "
bri...@aracnet.com put forth on 9/23/2010 11:25 PM:
>> No, that's normal. What had you changed on the system immediately
>> prior to this boot problem occurring?
>
> apt-get dist-upgrade, natch.
WTF is "natch"?
--
Stan
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with
On Thu, 23 Sep 2010 21:25:56 -0700
wrote:
> aaargh. I've never had so much trouble in my entire
> linux/debian/life. I have had a smooth boot or bootloader upgrade on
> this computer since I fired it up. other one works good, though. but
> really, 1/2 _is_ bad.
I have NOT had a smooth, etc..
On Thu, 23 Sep 2010 23:20:45 -0500
Stan Hoeppner wrote:
> bri...@aracnet.com put forth on 9/23/2010 10:50 PM:
>
> > Boot image: /boot/vmlinuz-2.6.32-5-amd64
> > Device 0x0802: BIOS drive 0x80, 255 heads, 30515 cylinders,
> >63 sectors. Partition offset: 120583890 sectors.
> > Usi
bri...@aracnet.com put forth on 9/23/2010 10:50 PM:
> Boot image: /boot/vmlinuz-2.6.32-5-amd64
> Device 0x0802: BIOS drive 0x80, 255 heads, 30515 cylinders,
>63 sectors. Partition offset: 120583890 sectors.
> Using Volume ID 5879D4A8 on bios 80
> Setup length is 27 sectors.
> Mappe
On Fri, Sep 03, 2010 at 03:49:10PM -0400, Stephen Powell wrote:
> On Fri, 03 Sep 2010 14:15:23 -0400 (EDT), Thomas H. George wrote:
> > On Fri, Sep 03, 2010 at 12:24:08PM -0400, Stephen Powell wrote:
> >> On Fri, 03 Sep 2010 12:06:29 -0400 (EDT), Thomas H. George wrote:
> >>>
> >>> After latest up
On Fri, 03 Sep 2010 14:15:23 -0400 (EDT), Thomas H. George wrote:
> On Fri, Sep 03, 2010 at 12:24:08PM -0400, Stephen Powell wrote:
>> On Fri, 03 Sep 2010 12:06:29 -0400 (EDT), Thomas H. George wrote:
>>>
>>> After latest upgrade installation of lilo fails.
>>>
>>> I am not using raid and have th
On Fri, Sep 03, 2010 at 12:24:08PM -0400, Stephen Powell wrote:
> On Fri, 03 Sep 2010 12:06:29 -0400 (EDT), Thomas H. George wrote:
> >
> > After latest upgrade installation of lilo fails.
> >
> > I am not using raid and have the entry boot=/dev/hda in lilo.conf as
> > specified in the man page.
On Fri, 03 Sep 2010 12:06:29 -0400 (EDT), Thomas H. George wrote:
>
> After latest upgrade installation of lilo fails.
>
> I am not using raid and have the entry boot=/dev/hda in lilo.conf as
> specified in the man page. The installation fails with error code 01
> which according to the lilo man
On Mon, 21 Jun 2010 15:56:01 -0400 (EDT), Joachim Wiedorn wrote:
>
> At fist: I don't read list 'debian-user'. I am the new developer of lilo.
> See: http://alioth.debian.org/projects/lilo/
> and: http://lilo.alioth.debian.org/
>
> Marc Shapiro wrote:
>> There has been a lot of talk about lilo and
Hello,
At fist: I don't read list 'debian-user'. I am the new developer of lilo.
See: http://alioth.debian.org/projects/lilo/
and: http://lilo.alioth.debian.org/
> There has been a lot of talk about lilo and squeeze on the list lately,
> but I don't really want to get into that argument. I have
On Thu, 17 Jun 2010 21:07:53 -0400 (EDT), Stephen Powell wrote:
> In particular, there is a section under "Customizing the Lenny Environment"
> that specifically explains how to convert from grub-pc to lilo.
Oops! That should read "convert from grub (version 1) to lilo". You'll
have to adapt the
On Thu, 17 Jun 2010 19:04:51 -0400 (EDT), Marc Shapiro wrote:
> My lilo.conf is as follows:
>
> # /etc/lilo.conf
>
> boot="UUID=5019cd9d-5d2e-4d7c-a6f4-0eccb5144c77"
> ...
>
> Can anyone tell me what is causing this?
> I have never had problems with lilo, before. It always 'just works'.
Marc,
On Fri, 04 Jun 2010 20:50:46 -0400 (EDT), thib wrote:
> Stephen Powell wrote:
>> Report? What report?
>
> That was actually meant to be a quick off-list note about your post in
> 505609 which I thought deserved at least two nice words. ;-)
Oh, thanks. And sorry. I figured you must have accid
Stephen Powell wrote:
Report? What report?
That was actually meant to be a quick off-list note about your post in
505609 which I thought deserved at least two nice words. ;-)
-t
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Co
On Tue, 01 Jun 2010 11:12:06 -0400 (EDT), thib wrote:
> Stephen Powell wrote:
>> I am still hopeful that lilo will not be dropped from the distribution.
>> I think it would be a mistake, and I believe lilo has many more years
>> of useful life than most people think it does (or should have) at this
On Wed, 02 Jun 2010 10:23:54 -0400 (EDT), John Hasler wrote:
> Tom H writes:
>> I meant to say the Lenny repos (although I am curious to see whether
>> [Lilo] will really disappear from the Squeeze repos once Squeeze is
>> released).
>
> If it has an RC bug at the time of the release it will be re
On Wed, 02 Jun 2010 12:02:15 -0400 (EDT), Jon Dowland wrote:
>
> Just how often is a total restore-from-backup required, I wonder?
A total restore from backup could be for one of two purposes:
(1) To restore a machine in case of a hard drive failure. Replace
the bad drive with a good drive and
On Tue, 01 Jun 2010 12:14:42 -0400 (EDT), John Hasler wrote:
> Stephen Powell writes:
>> Actually, I've been tempted to volunteer to become the upstream
>> maintainer for lilo myself.
>
> Please do so.
>>
>> However, although the SAPL is written in assembly language, it is
>> written in s390 assem
On Wed, Jun 2, 2010 at 10:05 AM, Stephen Powell wrote:
> On Wed, 02 Jun 2010 09:55:58 -0400 (EDT), Tom H wrote:
>> On Wed, Jun 2, 2010 at 9:30 AM, Stephen Powell wrote:
>>> On Wed, 02 Jun 2010 09:06:56 -0400 (EDT), Tom H wrote:
Don't you think that lilo will be left in the repos but not
On 28/05/2010 17:39, Roger Leigh wrote:
> One obvious solution not already mentioned is to back up the bootloader
> *in Linux* as a normal file, so the backup software can then just back
> it up like any other file. It's a simple enough workaround to the
> deficiencies in your backup software.
>
>
On 24/05/2010 23:44, Stan Hoeppner wrote:
> So it would appear boot loaders in general have a lack of interested/committed
> developers? Both LILO and GRUB.
>
> So instead of just LILO, why didn't the Debian team just throw both
> bootloaders out the window and start over with committed devs?
>
On 01/06/2010 10:32, Stan Hoeppner wrote:
> The reason grub2 is being forced upon us all is the need of the "desktop"
> users who want a 20MB kitchen sink kernel and initrd that will support any
> piece of hardware on any machine they throw at it. Many sysadmins don't want
> or need that, and we'r
On 30/05/2010 14:04, thib wrote:
> Like any dist upgrade, squeeze will have release notes with upgrade
> instructions and I'm quite confident everything concerning lilo will
> be covered. There are probably many upgrade test patterns they'll
> have to try, that's true, but I would hope the transit
Tom H writes:
> I meant to say the Lenny repos (although I am curious to see whether
> [Lilo] will really disappear from the Squeeze repos once Squeeze is
> released).
If it has an RC bug at the time of the release it will be removed.
--
John Hasler
--
To UNSUBSCRIBE, email to debian-user-requ
On Wed, 02 Jun 2010 09:55:58 -0400 (EDT), Tom H wrote:
> On Wed, Jun 2, 2010 at 9:30 AM, Stephen Powell wrote:
>> On Wed, 02 Jun 2010 09:06:56 -0400 (EDT), Tom H wrote:
>>>
>>> Don't you think that lilo will be left in the repos but not available
>>> at install time? You could then install lilo po
On Wed, Jun 2, 2010 at 9:30 AM, Stephen Powell wrote:
> On Wed, 02 Jun 2010 09:06:56 -0400 (EDT), Tom H wrote:
>>
>> Don't you think that lilo will be left in the repos but not available
>> at install time? You could then install lilo post-OS-install or
>> through pre-seeding.
>
> Not without an a
On Wed, 02 Jun 2010 09:06:56 -0400 (EDT), Tom H wrote:
>
> Don't you think that lilo will be left in the repos but not available
> at install time? You could then install lilo post-OS-install or
> through pre-seeding.
Not without an active upstream maintainer. That's the critical need now.
--
On Tue, Jun 1, 2010 at 3:44 PM, Stephan Seitz
wrote:
> On Mon, May 31, 2010 at 01:29:15AM +0300, Andrei Popescu wrote:
>>
>> Having /boot on a separate partition for robustness, security or
>> advanced features (encrypted LVM and stuff) is one thing, but having it
>> because the default bootloader
On Tue, Jun 1, 2010 at 5:32 AM, Stan Hoeppner wrote:
> Tom H put forth on 5/31/2010 1:04 AM:
>
>> I have gone through various big changes in OSs, WinNT to Win2k, OS9 to
>> OSX (although I was a Sol-Lin admin too so it wasn't as great a shock
>> as for Mac-only admins [1. see OT anecdote below]), S
Stephen Powell wrote:
Actually, that is largely a myth. Lilo's only release-critical bug turned
out not to be a bug at all. It was this "bug" that gave rise to the belief
that stock kernels were getting too big for lilo to load. But the problem
was that a new kernel was installed without lilo
On Mon, May 31, 2010 at 01:29:15AM +0300, Andrei Popescu wrote:
Having /boot on a separate partition for robustness, security or
advanced features (encrypted LVM and stuff) is one thing, but having it
because the default bootloader doesn't support current (ext4) and future
(btrfs) filesystems see
On Ma, 01 iun 10, 10:25:42, Stephen Powell wrote:
>
> Actually, I've been tempted to volunteer to become the upstream maintainer
> for lilo myself. I have worked on boot loaders before, on other platforms.
[...]
> I agree. But I also sympathize with the poor package maintainer who is
> essent
Stephen Powell writes:
> Actually, I've been tempted to volunteer to become the upstream
> maintainer for lilo myself.
Please do so.
> However, although the SAPL is written in assembly language, it is
> written in s390 assembly language, which is totally different from x86
> assembly language. I
Stan Hoeppner wrote:
The
problem, in and of itself, is booting. Period. There is [no] way to test it
but to replace LILO with Grub2 and see if the system boots afterward. I
cannot do this on production servers, obviously. Cloning drives to play with
on a lab machine would be a good idea, but
On Tue, 01 Jun 2010 10:20:09 -0400 (EDT), thib wrote:
>
> In the worst case, people will maintain unofficial packages in unofficial
> repositories. In fact, I'm not even sure there's still much to maintain
> with the package.. just keep it around.
>
> It's very true, official support is best,
On Tue, 01 Jun 2010 05:32:37 -0400 (EDT), Stan Hoeppner wrote:
> From a seasoned sysadmin perspective, a "vendor" forced change away from
> something as critical as a bootloader, causes immediate push back. In LILO's
> current state, and given the way I run kernels, I could likely used LILO 22.8
>
Stan Hoeppner wrote:
LILO isn't broken and it works well enough for may folks such as myself. We
should have the option of keeping it, as an installable package, until _we_
feel we need to change to something else. It's as much a philosophical issue
as it is a practical one. There is no legiti
Stephen Powell put forth on 5/31/2010 8:57 PM:
> On Sun, 30 May 2010 03:48:50 -0400 (EDT), Andrei Popescu wrote:
>> On Sat,29.May.10, 22:35:56, Stan Hoeppner wrote:
>>>
>>> My gut instinct is that due to the above reasons and possibly others, the
>>> next
>>> dist upgrade is going to hose all my p
Tom H put forth on 5/31/2010 1:04 AM:
> On Sat, May 29, 2010 at 11:46 PM, Stan Hoeppner
> wrote:
>> Tom H put forth on 5/28/2010 10:55 PM:
>>> On Fri, May 28, 2010 at 9:50 PM, Stan Hoeppner
>>> wrote:
Roger Leigh put forth on 5/28/2010 11:39 AM:
>>>
> For the most part, grub is a vast
On Sun, 30 May 2010 03:48:50 -0400 (EDT), Andrei Popescu wrote:
> On Sat,29.May.10, 22:35:56, Stan Hoeppner wrote:
>>
>> My gut instinct is that due to the above reasons and possibly others, the
>> next
>> dist upgrade is going to hose all my production servers whilst trying to
>> forcibly conver
>> Maybe, but ext4 support is not really crucial. Simply make /boot ext2.
Actually ext3 works fine.
> Having /boot on a separate partition for robustness, security or
> advanced features (encrypted LVM and stuff) is one thing, but having it
> because the default bootloader doesn't support curre
On Sat, May 29, 2010 at 11:46 PM, Stan Hoeppner wrote:
> Tom H put forth on 5/28/2010 10:55 PM:
>> On Fri, May 28, 2010 at 9:50 PM, Stan Hoeppner
>> wrote:
>>> Roger Leigh put forth on 5/28/2010 11:39 AM:
>>
For the most part, grub is a vast
improvement over LILO, and except for the od
On Sun,30.May.10, 22:50:44, Stephan Seitz wrote:
> On Sun, May 30, 2010 at 07:11:19PM +0200, Sven Joachim wrote:
> >The main problem with grub1 is the same as with lilo: there is no
> >upstream maintainer, and crucial parts of the code are undocumented
> >and not understandable¹.
>
> But at least
On Sun, May 30, 2010 at 3:12 PM, Brian Marshall wrote:
> On Sun, May 30, 2010 at 03:02:23PM -0700, Mark wrote:
> > I just booted to Lenny, changed the "default=0" value to
> > "default=3" in /boot/grub/menu.lst so it now boots to XP by default. My
> > limited experience with grub2 in Sq
On Sun, May 30, 2010 at 03:02:23PM -0700, Mark wrote:
> I just booted to Lenny, changed the "default=0" value to
> "default=3" in /boot/grub/menu.lst so it now boots to XP by default. My
> limited experience with grub2 in Squeeze didn't appear to have this ability,
> so what would I have
On Sun, May 30, 2010 at 1:50 PM, Stephan Seitz <
stse+deb...@fsing.rootsland.net > wrote:
>
> I would say, the default bootloader should be grub1, expert installation
> can offer grub2 as well. Lilo should be in the distribution as well, so
> people can switch after installation. At least for the
On Sun, May 30, 2010 at 07:11:19PM +0200, Sven Joachim wrote:
The main problem with grub1 is the same as with lilo: there is no
upstream maintainer, and crucial parts of the code are undocumented
and not understandable¹.
But at least grub1 is working in a wider field than grub2. And lilo is
st
Paul E Condon put forth on 5/30/2010 10:37 AM:
> On 20100529_223556, Stan Hoeppner wrote:
>> I'm far more concerned at this point with distribution upgrades than new
>> installs.
>>
>> My gut instinct is that due to the above reasons and possibly others, the
>> next
>> dist upgrade is going to h
On 2010-05-30 18:29 +0200, Stephan Seitz wrote:
> On Fri, May 28, 2010 at 11:55:58PM -0400, Tom H wrote:
>>The reverse argument can be made too. Both grub1 and grub2 just work.
>
> I accept this argument for grub1. Yes, I never had problems with
> grub1, but grub2 is simply not ready for prime tim
On Fri, May 28, 2010 at 11:55:58PM -0400, Tom H wrote:
The reverse argument can be made too. Both grub1 and grub2 just work.
I accept this argument for grub1. Yes, I never had problems with grub1,
but grub2 is simply not ready for prime time.
While grub2 works for simple workstations, it can
On 20100529_223556, Stan Hoeppner wrote:
> thib put forth on 5/28/2010 9:44 PM:
>
> > * If yes, should it still be presented as an "expert" option in d-i?
> > Why not, I guess. If not, should extlinux be extensively tested to be
> > provided as an alternative choice in d-i? I really don't kno
Stan Hoeppner wrote:
My gut instinct is that due to the above reasons and possibly others, the next
dist upgrade is going to hose all my production servers whilst trying to
forcibly convert them to Grub2. Is my instinct correct?
Like any dist upgrade, squeeze will have release notes with upgra
On Sat,29.May.10, 22:35:56, Stan Hoeppner wrote:
>
> My gut instinct is that due to the above reasons and possibly others, the next
> dist upgrade is going to hose all my production servers whilst trying to
> forcibly convert them to Grub2. Is my instinct correct?
Worst case you'll have to pin l
Stephen Powell put forth on 5/29/2010 9:48 AM:
> As time goes on, these restrictions are getting more restrictive.
> And we are looking at alternatives to our existing backup software.
> But for now, I have to live within these restrictions.
Implement VMware ESX and VMware Consolidate Backup (o
On Sunday 30 May 2010 05:40:21 Mark Allums wrote:
> For yet another view on this, Grub2 is pants. I see no good reason to
> eliminate both lilo and GRUB at the same time. Eliminate lilo or GRUB
> but not both, and let the user choose to use Grub2 or the older method.
> When Grub2 matures some m
For yet another view on this, Grub2 is pants. I see no good reason to
eliminate both lilo and GRUB at the same time. Eliminate lilo or GRUB
but not both, and let the user choose to use Grub2 or the older method.
When Grub2 matures some more, move to it, but it's not ready yet to
take on the
Tom H put forth on 5/28/2010 10:55 PM:
> On Fri, May 28, 2010 at 9:50 PM, Stan Hoeppner wrote:
>> Roger Leigh put forth on 5/28/2010 11:39 AM:
>
>>> For the most part, grub is a vast
>>> improvement over LILO, and except for the odd corner cases which
>>> grub doesn't cover,
>>
>> In what way is
thib put forth on 5/28/2010 9:44 PM:
> * If yes, should it still be presented as an "expert" option in d-i?
> Why not, I guess. If not, should extlinux be extensively tested to be
> provided as an alternative choice in d-i? I really don't know how much
> work would be needed for this.
I'm fa
1 - 100 of 1202 matches
Mail list logo
