Displaying 20 results from an estimated 7000 matches similar to: "syslinux synonym for the "restricted" option of lilo?"
2016 Aug 13
1
syslinux synonym for the "restricted" option of lilo?
On Tue, Aug 9, 2016 at 12:36 PM, Gene Cumm <gene.cumm at gmail.com> wrote:
>
> Look at "MENU MASTER PASSWD". It'll block [Esc] (to exit menu) and
> [Tab] (to edit an entry). It has a different design but might work
> for your goals.
>
Good idea! Menu master passwd with/without menu passwd in syslinux work
just like the mandatory/restricted passwd in lilo.
2016 Aug 09
0
syslinux synonym for the "restricted" option of lilo?
On Thu, Aug 4, 2016 at 5:32 AM, Guan Xin via Syslinux
<syslinux at zytor.com> wrote:
> Hello,
>
> Does syslinux have an option to ask for a password before booting a menu
> item only when the command line has been modified, like with the
> "restricted" option of lilo?
Look at "MENU MASTER PASSWD". It'll block [Esc] (to exit menu) and
[Tab] (to edit an
2005 Apr 29
2
Booting CentOS with LILO?
Hello all!
I would like to know if is possible to use LILO as the boot loader
instead of the default GRUB. My question comes because I tried to run
lilo command but the message "command not found" appear. It sounds
like my only boot loader option in CentOS is GRUB ??.
I found lilo.conf.anaconda, but not the lilo command. From already
thanks. Regards,
Juan P. Espino
2009 Feb 08
2
keytab-lilo included with SYSLINUX is not up to date
Hi,
I just noticed that the keytab-lilo utility included with SYSLINUX isn't
up to date. It *is* a problem since the old version isn't compatible
with current distributions like Debian ou Ubuntu (for example).
Two options are offered to those who would like to use keytab-lilo in
order to generate a file compatible with the KBDMAP directive :
- use an up to date version of keytab-lilo
2016 Mar 07
2
keytab-lilo: update to support kbd 2.0.3 format
On 29.12.2015 22:51, poma wrote:
> On 29.12.2015 22:20, Ady via Syslinux wrote:
>>
>>> On 27.12.2015 23:57, Jernej Simon?i? via Syslinux wrote:
>>>> On Sunday, December 27, 2015, 23:34:11, Ady via Syslinux wrote:
>>>>
>>>>> How this change would affect users with older versions of kbd /
>>>>> loadkeys / or in older OSes? I
2016 Mar 07
2
keytab-lilo: update to support kbd 2.0.3 format
On 07.03.2016 19:24, Ady via Syslinux wrote:
>> doc: keytab-lilo example on Fedora
>>
>> ---
>> doc/keytab-lilo.txt | 4 ++++
>> 1 file changed, 4 insertions(+)
>>
>> diff --git a/doc/keytab-lilo.txt b/doc/keytab-lilo.txt
>> index cdbea0f..f35b3e8 100644
>> --- a/doc/keytab-lilo.txt
>> +++ b/doc/keytab-lilo.txt
>> @@ -83,3 +83,7 @@
2005 Oct 25
2
lilo for centos 4.2
Where can I get lilo for centos 4.2?
I did "up2date lilo*" and nothing was retrieved.
2010 Jan 08
3
Lilo for CentOS 5?
Does there exist a version of Lilo built for x86_64 CentOS 5? It does not
seem to be on the DVD. *I* really, really, prefer Lilo over Grub.
--
Robert Heller -- 978-544-6933
Deepwoods Software -- Download the Model Railroad System
http://www.deepsoft.com/ -- Binaries for Linux and MS-Windows
heller at deepsoft.com -- http://www.deepsoft.com/ModelRailroadSystem/
2015 Dec 29
2
keytab-lilo: update to support kbd 2.0.3 format
> On 27.12.2015 23:57, Jernej Simon?i? via Syslinux wrote:
> > On Sunday, December 27, 2015, 23:34:11, Ady via Syslinux wrote:
> >
> >> How this change would affect users with older versions of kbd /
> >> loadkeys / or in older OSes? I mean, let's assume a user using a newer
> >> version of Syslinux (containing this proposed change in its keytab-lilo
2004 Oct 05
3
Translating Lilo to syslinux and (isolinux)
I have a Lilo.conf file, which I have tried for many hours to convert to
Syslinux. I looked around on the web for references on translating some
of the components. I want to convert it to Syslinux/Isolinux.
Any suggestions would be greatly appreciated. When I tried to convert it
I made sure that the kernel and initrd had proper DOS names and such.
-Michael
=:LILO.CONF:=
prompt
timeout=10
2005 Nov 30
8
why was LILO removed from centOS 4.2?
I can't choose LILO as boot loader anymore in the install process? And what is the
advantages in GRUP vs. LILO that are so great that LILO has been deleted all
together?
One big disadvantages when forced to use GRUB is that it is a hassle to make the
disks in a RAID1 bootable.
https://www.redhat.com/archives/fedora-list/2005-March/msg05935.html
and RAID1 seems pretty useless when it is the
2015 Dec 27
2
[PATCH] keytab-lilo: update to support kbd 2.0.3 format
Since kbd 2.0.3 (commit 6ff47cf2) the format generated by 'loadkeys -m' has
changed slightly, using "unsigned short" instead of "u_short"
Signed-off-by: Olivier Brunel <jjk at jjacky.com>
---
utils/keytab-lilo | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/utils/keytab-lilo b/utils/keytab-lilo
index 9e34160..337a869 100755
---
2004 Jul 16
1
Problem with SysLinux but not with LILO
Hi,
I am trying to use two products that use SysLinux and finally realised the
SysLinux is the cause of my woes. I'm trying to use Freesco and IPCop. IPCop
version 1.3 used a different boot loader to 1.4 which uses SysLinux. I have
been through numerous trials and tribulations in trying to get Freesco to
work but eventually gave up and went with IPCop. I kept getting the "Boot
2002 Jul 19
1
lilo causes a "Unexpected dirty buffer encountered at do_get_write_access:597 (03:02 blocknr 0)"
On my Debian box:
Package: lilo
Version: 1:22.2-5
Severity: normal
lilo seems to cause a kernel warning (see subject) when / is a ext3 partition.
Maybe a kernel problem? Who knows. I'm running 2.4.19-rc1-ac7
-- System Information:
Debian Release: testing/unstable
Architecture: i386
Kernel: Linux hummus 2.4.19-rc1-ac7 #1 Wed Jul 17 22:14:20 CEST 2002 i686
Locale: LANG=C, LC_CTYPE=C
Versions
2006 Oct 09
2
3.x box - lilo - hosed bootloader
Hi
Updated the firmware on a PERC RAID card as it was out of date and
causing a monitoring error - Everything went fine but on the reboot the
box now tells me it cant find a valid boot device - I am thinking maybe
somehow the boot block on the logical disk is shot.
Can anyone advise me on how to rebuild the bootloader on lilo using a
rescue CD?
thanks
2015 Dec 27
2
keytab-lilo: update to support kbd 2.0.3 format
On Sunday, December 27, 2015, 23:34:11, Ady via Syslinux wrote:
> How this change would affect users with older versions of kbd /
> loadkeys / or in older OSes? I mean, let's assume a user using a newer
> version of Syslinux (containing this proposed change in its keytab-lilo
> perl script) but with an older OS / older version of kbd / loadkeys /
> map files.
The changed
2007 Apr 22
1
Centos5: RAID1 on root/boot? [+lilo mkinitrd issues]
Hi,
I did a command-line upgrade of a RHL73 server to Centos 5. It was a
bit rocky road, but in the end it was successful.
There's one thing that bugged me. I'm using software RAID1 consisting
of /dev/hd{a,c}. No LVM or anything fancy, a number of /dev/mdX
partitions, including the root (+/boot).
I'd have preferred to continue using lilo as it works more easily with
RAID1
2006 Jan 24
1
[PATCH][XM-TEST] Add Lilo dependency check to configure.ac
Patch adds a dependency check for lilo, which is needed for full virt
testing, to the configure.ac script. Dependency checks should be there
rather than building and waiting to see the create script fail.
Thanks,
Dan
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
2016 Mar 07
0
keytab-lilo: update to support kbd 2.0.3 format
> doc: keytab-lilo example on Fedora
>
> ---
> doc/keytab-lilo.txt | 4 ++++
> 1 file changed, 4 insertions(+)
>
> diff --git a/doc/keytab-lilo.txt b/doc/keytab-lilo.txt
> index cdbea0f..f35b3e8 100644
> --- a/doc/keytab-lilo.txt
> +++ b/doc/keytab-lilo.txt
> @@ -83,3 +83,7 @@ where <kbd> is the name of the keyboard layout.
> Example:
>
>
2006 Sep 02
0
CentOS 4.4 LILO Raid (also e2fsprogs in general)
i noticed that the 4.4 upgrade broke LILO on Raid...
it gave errors on partitions not on the primary disk
along the lines of "/dev/dis: no such device"...
even explicitly installing the boot sector on each
device in the array, while it allowed the system
to boot, gave errors at boot time and did not
display the CentOS boot screen anymore...
i solved the problem by creating a