[SOLVED] Problem adding 11.04 to 40_custom

[Snowhog]

Just installed Natty Narwhal 11.04 Alpha 3 as my third Kubuntu OS this afternoon. I want to add to the /etc/grub.d/40_custom files in Lucid and Maverick so that each has the required entry for Natty. This is what the Lucid file looks like:

menuentry "Ubuntu, Maverick Meerkat"{
set root='(hd0,7)'
configfile /boot/grub/grub.cfg
}
menuentry "Ubuntu, Natty Narwhal"{
set root='(hd0,9)'
configfile /boot/grub/grub.cfg
}

And this is what the Marverick file looks like:

menuentry "Ubuntu, Lucid Lynx"{
set root='(hd0,1)'
configfile /boot/grub/grub.cfg
}
menuentry "Ubuntu, Natty Narwhal"{
set root='(hd0,9)'
configfile /boot/grub/grub.cfg
}

I ran sudo update-grub after booting into Lucid and then again in Maverick, Natty appears in the Grub Menu of each. However, selecting Natty from either Lucid or Maverick results in the following errors:

error: file not found
error: file not found
error: unknown command 'background_color'.
error: unknown command 'lua'.
syntax error
Incorrect command

Press any key to continue...

Pressing any key returns me to the Grub menu.

I activated 30_os-prober in Lucid and Maverick and reran sudo update-grub, adding Natty to the ### BEGIN /etc/grub.d/30_os-prober ### section of grub.cfg in Lucid and Maverick. Selecting Natty from there, Natty boots correctly. This is the Natty stanza in ### BEGIN /etc/grub.d/30_os-prober ### of Lucid's and Maverick's grub.cfg:

menuentry "Ubuntu, with Linux 2.6.38-5-generic (on /dev/sda9)" {
insmod ext2
set root='(hd0,9)'
search --no-floppy --fs-uuid --set 67532fdd-10e6-47bf-9ac3-26a52581799a
linux /boot/vmlinuz-2.6.38-5-generic root=UUID=67532fdd-10e6-47bf-9ac3-26a52581799a ro quiet splash vt.handoff=7
initrd /boot/initrd.img-2.6.38-5-generic
}
menuentry "Ubuntu, with Linux 2.6.38-5-generic (recovery mode) (on /dev/sda9)" {
insmod ext2
set root='(hd0,9)'
search --no-floppy --fs-uuid --set 67532fdd-10e6-47bf-9ac3-26a52581799a
linux /boot/vmlinuz-2.6.38-5-generic root=UUID=67532fdd-10e6-47bf-9ac3-26a52581799a ro single
initrd /boot/initrd.img-2.6.38-5-generic
}

What is wrong with the Natty stanza in my 30_os-prober files? The Lucid and Maverick stanzas work just fine.

[claydoh]

Re: Problem adding 11.04 to 40_custom

One thing to check is the drive/partitioning numbering:

• Drives start out at 0
• Partitions start at 1

Yes, nice and logical, that one :/ so the first partition on your first drive is (hd0,1)

Me, I am lazy. I just let Maverick's grub automagically add natty to the menu, and just remember to update grub as each new natty kernel arrives

of course I don't have a user-friendly menu entry.

hmpf. My Maverick/Natty laptop is having severe hardware failure somewhere and I am having trouble booting it even to grub. So I can't see what the auto-generated grub.cfg looks like in Maverick.

the os_prober script doesn't seem to be the right place to add extra entries, as it is an actual script. I wouldn't add anything there. 40_custom should be the correct place iirc

Here is the relevent Natty (as my main grub and OS) with Maverick added afterwards in my boot/grub/grub.cfg:

menuentry 'Ubuntu, with Linux 2.6.38-5-generic' --class ubuntu --class gnu-linux --class gnu --class os {
	recordfail
	set gfxpayload=$linux_gfx_mode
	insmod part_msdos
	insmod ext2
	set root='(/dev/sda,msdos1)'
	search --no-floppy --fs-uuid --set=root ebc0afc1-e5d1-41d3-8083-f776f27811d9
	linux	/boot/vmlinuz-2.6.38-5-generic root=UUID=ebc0afc1-e5d1-41d3-8083-f776f27811d9 ro  quiet splash vt.handoff=7
	initrd	/boot/initrd.img-2.6.38-5-generic
}
menuentry 'Ubuntu, with Linux 2.6.38-5-generic (recovery mode)' --class ubuntu --class gnu-linux --class gnu --class os {
	recordfail
	set gfxpayload=$linux_gfx_mode
	insmod part_msdos
	insmod ext2
	set root='(/dev/sda,msdos1)'
	search --no-floppy --fs-uuid --set=root ebc0afc1-e5d1-41d3-8083-f776f27811d9
	echo	'Loading Linux 2.6.38-5-generic ...'
	linux	/boot/vmlinuz-2.6.38-5-generic root=UUID=ebc0afc1-e5d1-41d3-8083-f776f27811d9 ro single 
	echo	'Loading initial ramdisk ...'
	initrd	/boot/initrd.img-2.6.38-5-generic
}
### END /etc/grub.d/10_linux ###

### BEGIN /etc/grub.d/20_linux_xen ###
### END /etc/grub.d/20_linux_xen ###

### BEGIN /etc/grub.d/20_memtest86+ ###
menuentry "Memory test (memtest86+)" {
	insmod part_msdos
	insmod ext2
	set root='(/dev/sda,msdos1)'
	search --no-floppy --fs-uuid --set=root ebc0afc1-e5d1-41d3-8083-f776f27811d9
	linux16	/boot/memtest86+.bin
}
menuentry "Memory test (memtest86+, serial console 115200)" {
	insmod part_msdos
	insmod ext2
	set root='(/dev/sda,msdos1)'
	search --no-floppy --fs-uuid --set=root ebc0afc1-e5d1-41d3-8083-f776f27811d9
	linux16	/boot/memtest86+.bin console=ttyS0,115200n8
}
### END /etc/grub.d/20_memtest86+ ###

### BEGIN /etc/grub.d/30_os-prober ###
menuentry "Ubuntu, with Linux 2.6.35-22-generic (on /dev/sda5)" --class gnu-linux --class gnu --class os {
	insmod part_msdos
	insmod ext2
	set root='(/dev/sda,msdos5)'
	search --no-floppy --fs-uuid --set=root d607d121-930d-4098-bca8-6cfa9463b134
	linux /boot/vmlinuz-2.6.35-22-generic root=UUID=d607d121-930d-4098-bca8-6cfa9463b134 ro quiet splash
	initrd /boot/initrd.img-2.6.35-22-generic
}
menuentry "Ubuntu, with Linux 2.6.35-22-generic (recovery mode) (on /dev/sda5)" --class gnu-linux --class gnu --class os {
	insmod part_msdos
	insmod ext2
	set root='(/dev/sda,msdos5)'
	search --no-floppy --fs-uuid --set=root d607d121-930d-4098-bca8-6cfa9463b134
	linux /boot/vmlinuz-2.6.35-22-generic root=UUID=d607d121-930d-4098-bca8-6cfa9463b134 ro single
	initrd /boot/initrd.img-2.6.35-22-generic
}
### END /etc/grub.d/30_os-prober ###

### BEGIN /etc/grub.d/40_custom ###
# This file provides an easy way to add custom menu entries. Simply type the
# menu entries you want to add after this comment. Be careful not to change
# the 'exec tail' line above.
menuentry "haiku" {
set root=(hd0,8)
chainloader +1
}
### END /etc/grub.d/40_custom ###

I would guess that Natty's grub wouldn't be too much different than in Maverick, but I will try and get something from that Maverick box if I can, and see if there are any differences. uuid may be a key here

[Snowhog]

Re: Problem adding 11.04 to 40_custom

Single HD in the laptop, and yes, fully aware of the enumeration 'differences' between BIOS and Grub.

The issue seems to be with grub.cfg itself. In my setup, Lucid's Grub2 is installed to the MBR, so when I boot the laptop, Lucid's Grub Menu is presented. In Lucid, I have a 40_custom that contains the stanza for adding Maverick to the end of the Lucid Grub Menu. It works fine.

What I have noticed, from the outset, is that Lucid's grub.cfg isn't replaced with Maverick's when I opt to boot into Maverick from Lucid. I know this is happening, because my custom Grub theme that is used in Lucid doesn't change when I opt to boot using Maverick's entry. It doesn't appear to matter (except cosmetically), as Maverick's grub.cfg is fully compatible with Lucid's Grub2 intermediate-stage loader.

The problem with trying to boot Natty from the Grub Menu of Lucid, where Natty was added using a 40_custom entry, is that Natty's grub.cfg is significantly different than Lucid's - I compared them - that, or the intermediate-stage loader in Lucid isn't fully compatible with Natty. Only grasping at straws on that.

So, for the benefit of anyone else looking at this, and who might have the answer I'm looking for, this is the content of my 40_custom file in Lucid for Natty which results in the errors when selected from Lucid's Grub Menu:

menuentry "Ubuntu, Natty Narwhal"{
set root='(hd0,9)'
configfile /boot/grub/grub.cfg
}

And this is the Natty section added to Lucid's Grub Menu (grub.cfg) utilizing 30_os-prober, that boots Natty when selected:

menuentry "Ubuntu, with Linux 2.6.38-5-generic (on /dev/sda9)" {
insmod ext2
set root='(hd0,9)'
search --no-floppy --fs-uuid --set 67532fdd-10e6-47bf-9ac3-26a52581799a
linux /boot/vmlinuz-2.6.38-5-generic root=UUID=67532fdd-10e6-47bf-9ac3-26a52581799a ro quiet splash vt.handoff=7
initrd /boot/initrd.img-2.6.38-5-generic
}

What I believe is the proximate cause of the problem, is that Lucid's /boot/grub/grub.cfg file, which has been read, and is in memory, is incompatible with Natty's /boot/grub/grub.cfg. I know that the two are significantly different, as I've done a side-by-side comparison of the two.

[claydoh]

Re: Problem adding 11.04 to 40_custom

What I have noticed, from the outset, is that Lucid's grub.cfg isn't replaced with Maverick's when I opt to boot into Maverick from Lucid. I know this is happening, because my custom Grub theme that is used in Lucid doesn't change when I opt to boot using Maverick's entry. It doesn't appear to matter (except cosmetically), as Maverick's grub.cfg is fully compatible with Lucid's Grub2 intermediate-stage loader.

as Lucid is your boot-os and boot-grub, you are not utilizing anything grub-wise from the other OS's installed (unless you are using chainloader) so forget about Maverick's grub as it is not being used - Lucid's is. techically, you could not install grub at all for, say, natty, and os-prober in lucid would still detect natty's kernel files and point grub to load those. It has for me in the past with other distros I have added to Kubuntu.

I still don't understand why you don't run update-grub from inside lucid and have os-prober add natty's entry. Then you can see what Lucid's grub needs for your custom entry, or use what it adds.

[Snowhog]

Re: Problem adding 11.04 to 40_custom

I still don't understand why you don't run update-grub from inside lucid and have os-prober add natty's entry. Then you can see what Lucid's grub needs for your custom entry, or use what it adds.

I have. That's how I got Natty added to Lucids' grub.cfg. Again, what follows, is the entry for Natty, in Lucid's grub.cfg, created from 30_os-prober:

menuentry "Ubuntu, with Linux 2.6.38-5-generic (on /dev/sda9)" {
insmod ext2
set root='(hd0,9)'
search --no-floppy --fs-uuid --set 67532fdd-10e6-47bf-9ac3-26a52581799a
linux /boot/vmlinuz-2.6.38-5-generic root=UUID=67532fdd-10e6-47bf-9ac3-26a52581799a ro quiet splash vt.handoff=7
initrd /boot/initrd.img-2.6.38-5-generic
}

The problem with the above, while it does allow me to boot into Natty from Lucid, is that it boots the specified kernel directly. That is not what I want. I want to be taken to Natty's Grub Menu. This is what happens from Lucid's Grub Menu for Maverick (and thence, from Maverick's Grub Menu, I can go back to Lucid again). This is the expected and normal behavior of an entry created from a 40_custom file. But for Natty, it does not work.

Just including all the above into the 40_custom (I did try that) only results in a direct boot to the specified kernel when selected from Lucid's Grub Menu - it does not take me to Natty's Grub Menu.

[Snowhog]

Re: Problem adding 11.04 to 40_custom

Natty Narwhal grub.cfg
#
# DO NOT EDIT THIS FILE
#
# It is automatically generated by grub-mkconfig using templates
# from /etc/grub.d and settings from /etc/default/grub
#

### BEGIN /etc/grub.d/00_header ###
if [ -s $prefix/grubenv ]; then
set have_grubenv=true
load_env
fi
set default="0"
if [ "${prev_saved_entry}" ]; then
set saved_entry="${prev_saved_entry}"
save_env saved_entry
set prev_saved_entry=
save_env prev_saved_entry
set boot_once=true
fi

function savedefault {
if [ -z "${boot_once}" ]; then
saved_entry="${chosen}"
save_env saved_entry
fi
}

function recordfail {
set recordfail=1
if [ -n "${have_grubenv}" ]; then if [ -z "${boot_once}" ]; then save_env recordfail; fi; fi
}

function load_video {
insmod vbe
insmod vga
insmod video_bochs
insmod video_cirrus
}

insmod part_msdos
insmod ext2
set root='(/dev/sda,msdos9)'
search --no-floppy --fs-uuid --set=root 67532fdd-10e6-47bf-9ac3-26a52581799a
if loadfont /usr/share/grub/unicode.pf2 ; then
set gfxmode=auto
load_video
insmod gfxterm
fi
terminal_output gfxterm
insmod part_msdos
insmod ext2
set root='(/dev/sda,msdos9)'
search --no-floppy --fs-uuid --set=root 67532fdd-10e6-47bf-9ac3-26a52581799a
set locale_dir=($root)/boot/grub/locale
set lang=en_US
insmod gettext
if [ "${recordfail}" = 1 ]; then
set timeout=-1
else
set timeout=-1
fi
### END /etc/grub.d/00_header ###

### BEGIN /etc/grub.d/05_debian_theme ###
set menu_color_normal=white/black
set menu_color_highlight=black/light-gray
if background_color 44,0,30; then
clear
fi
### END /etc/grub.d/05_debian_theme ###

### BEGIN /etc/grub.d/10_linux ###
if [ ${recordfail} != 1 ]; then
set matches_file=${prefix}/gfxblacklist.txt
set class_match=3
if lua ${prefix}/hwmatch.lua; then
if [ ${match} = 0 ]; then
set linux_gfx_mode=keep
else
set linux_gfx_mode=text
fi
else
set linux_gfx_mode=text
fi
else
set linux_gfx_mode=text
fi
export linux_gfx_mode
if [ "$linux_gfx_mode" != "text" ]; then load_video; fi
menuentry 'Ubuntu, with Linux 2.6.38-5-generic' --class ubuntu --class gnu-linux --class gnu --class os {
recordfail
set gfxpayload=$linux_gfx_mode
insmod part_msdos
insmod ext2
set root='(/dev/sda,msdos9)'
search --no-floppy --fs-uuid --set=root 67532fdd-10e6-47bf-9ac3-26a52581799a
linux /boot/vmlinuz-2.6.38-5-generic root=UUID=67532fdd-10e6-47bf-9ac3-26a52581799a ro quiet splash vt.handoff=7
initrd /boot/initrd.img-2.6.38-5-generic
}
menuentry 'Ubuntu, with Linux 2.6.38-5-generic (recovery mode)' --class ubuntu --class gnu-linux --class gnu --class os {
recordfail
set gfxpayload=$linux_gfx_mode
insmod part_msdos
insmod ext2
set root='(/dev/sda,msdos9)'
search --no-floppy --fs-uuid --set=root 67532fdd-10e6-47bf-9ac3-26a52581799a
echo 'Loading Linux 2.6.38-5-generic ...'
linux /boot/vmlinuz-2.6.38-5-generic root=UUID=67532fdd-10e6-47bf-9ac3-26a52581799a ro single
echo 'Loading initial ramdisk ...'
initrd /boot/initrd.img-2.6.38-5-generic
}
### END /etc/grub.d/10_linux ###

### BEGIN /etc/grub.d/20_linux_xen ###
### END /etc/grub.d/20_linux_xen ###

### BEGIN /etc/grub.d/40_custom ###
# This file provides an easy way to add custom menu entries. Simply type the
# menu entries you want to add after this comment. Be careful not to change
# the 'exec tail' line above.
menuentry "Ubuntu, Lucid Lynx"{
set root='(hd0,1)'
configfile /boot/grub/grub.cfg
}
menuentry "Ubuntu, Maverick Meerkat"{
set root='(hd0,7)'
configfile /boot/grub/grub.cfg
}
### END /etc/grub.d/40_custom ###

### BEGIN /etc/grub.d/41_custom ###
if [ -f $prefix/custom.cfg ]; then
source $prefix/custom.cfg;
fi
### END /etc/grub.d/41_custom ###

Lucid Lynx grub.cfg
#
# DO NOT EDIT THIS FILE
#
# It is automatically generated by /usr/sbin/grub-mkconfig using templates
# from /etc/grub.d and settings from /etc/default/grub
#

### BEGIN /etc/grub.d/00_header ###
if [ -s $prefix/grubenv ]; then
load_env
fi
set default="0"
if [ ${prev_saved_entry} ]; then
set saved_entry=${prev_saved_entry}
save_env saved_entry
set prev_saved_entry=
save_env prev_saved_entry
set boot_once=true
fi

function savedefault {
if [ -z ${boot_once} ]; then
saved_entry=${chosen}
save_env saved_entry
fi
}

function recordfail {
set recordfail=1
if [ -n ${have_grubenv} ]; then if [ -z ${boot_once} ]; then save_env recordfail; fi; fi
}
insmod ext2
set root='(hd0,1)'
search --no-floppy --fs-uuid --set 264d960d-73d4-4929-8d5e-bfdf75e63379
if loadfont /usr/share/grub/unicode.pf2 ; then
set gfxmode=1024x768
insmod gfxterm
insmod vbe
if terminal_output gfxterm ; then true ; else
# For backward compatibility with versions of terminal.mod that don't
# understand terminal_output
terminal gfxterm
fi
fi
insmod ext2
set root='(hd0,1)'
search --no-floppy --fs-uuid --set 264d960d-73d4-4929-8d5e-bfdf75e63379
set locale_dir=($root)/boot/grub/locale
set lang=en
insmod gettext
if [ ${recordfail} = 1 ]; then
set timeout=-1
else
set timeout=-1
fi
### END /etc/grub.d/00_header ###

### BEGIN /etc/grub.d/05_debian_theme ###
insmod ext2
set root='(hd0,1)'
search --no-floppy --fs-uuid --set 264d960d-73d4-4929-8d5e-bfdf75e63379
insmod png
if background_image /usr/share/images/angelic-moon_grub.png ; then
set color_normal=yellow/black
set color_highlight=magenta/black
else
set menu_color_normal=white/black
set menu_color_highlight=black/light-gray
fi
### END /etc/grub.d/05_debian_theme ###

### BEGIN /etc/grub.d/10_linux ###
menuentry 'Ubuntu, with Linux 2.6.32-27-generic' --class ubuntu --class gnu-linux --class gnu --class os {
recordfail
insmod ext2
set root='(hd0,1)'
search --no-floppy --fs-uuid --set 264d960d-73d4-4929-8d5e-bfdf75e63379
linux /boot/vmlinuz-2.6.32-27-generic root=UUID=264d960d-73d4-4929-8d5e-bfdf75e63379 ro splash
initrd /boot/initrd.img-2.6.32-27-generic
}
menuentry 'Ubuntu, with Linux 2.6.32-27-generic (recovery mode)' --class ubuntu --class gnu-linux --class gnu --class os {
recordfail
insmod ext2
set root='(hd0,1)'
search --no-floppy --fs-uuid --set 264d960d-73d4-4929-8d5e-bfdf75e63379
echo 'Loading Linux 2.6.32-27-generic ...'
linux /boot/vmlinuz-2.6.32-27-generic root=UUID=264d960d-73d4-4929-8d5e-bfdf75e63379 ro single
echo 'Loading initial ramdisk ...'
initrd /boot/initrd.img-2.6.32-27-generic
}
### END /etc/grub.d/10_linux ###

### BEGIN /etc/grub.d/30_os-prober ###
menuentry "Ubuntu, with Linux 2.6.38-5-generic (on /dev/sda9)" {
insmod ext2
set root='(hd0,9)'
search --no-floppy --fs-uuid --set 67532fdd-10e6-47bf-9ac3-26a52581799a
linux /boot/vmlinuz-2.6.38-5-generic root=UUID=67532fdd-10e6-47bf-9ac3-26a52581799a ro quiet splash vt.handoff=7
initrd /boot/initrd.img-2.6.38-5-generic
}
menuentry "Ubuntu, with Linux 2.6.38-5-generic (recovery mode) (on /dev/sda9)" {
insmod ext2
set root='(hd0,9)'
search --no-floppy --fs-uuid --set 67532fdd-10e6-47bf-9ac3-26a52581799a
linux /boot/vmlinuz-2.6.38-5-generic root=UUID=67532fdd-10e6-47bf-9ac3-26a52581799a ro single
initrd /boot/initrd.img-2.6.38-5-generic
}
### END /etc/grub.d/30_os-prober ###

### BEGIN /etc/grub.d/40_custom ###
# This file provides an easy way to add custom menu entries. Simply type the
# menu entries you want to add after this comment. Be careful not to change
# the 'exec tail' line above.
# 10-10-12 customization
menuentry "Ubuntu, Maverick Meerkat"{
set root='(hd0,7)'
configfile /boot/grub/grub.cfg
}
### END /etc/grub.d/40_custom ###

[claydoh]

Re: Problem adding 11.04 to 40_custom

I get it now, you need to chainload each grub, ie you can navigate from grub to grub to grub and back again if needed before choosing which OS to boot to.

I don't see how it is chainloading other bootloaders in lucid's grub.cfg from looking at it. but this should be how it is supposed to be done, according to grub's documentation:

menuentry "Natty's Grub Bootloader" {
set root=(hd0,9)
chainloader +1
}

As far as I know, 40_custom simply adds whatever custom entry you create to grub.cfg, it doesn't do any magic, simply copies whatever is put there. I Think. Maybe.

[Snowhog]

Re: Problem adding 11.04 to 40_custom

I'll give that a try and report back.

[Snowhog]

Re: Problem adding 11.04 to 40_custom

"chainloader +1" does not work, either for Maverick or Natty. I should have known that. That 'feature' worked in Grub Legacy, but even there, later, was depricated in favor of "configfile".

There is something about how the grub files are written in Natty that make it's grub.cfg file incompatible with the initial control established by Lucid's Grub2 loaders. Wish I knew what it was.

I've posted a question about this issue on Launchpad. Maybe someone there has the answer.

[claydoh]

Re: Problem adding 11.04 to 40_custom

odd, as all the info i find on grub2 mentions chainloader. I have to use that to load my haiku bootloader.

one thing to try is to make temporary edits to the grub entry before it loads, selecting the entry, and hitting "e". You might try editing the drive number just to see (saves a lot of testing time). The "file not found' errors make me believe it isn't getting the correct location to find the kernel files.

Or you could make life easier by only having one grub booting all the OS's (no fun in that, I know )

[Snowhog]

Re: Problem adding 11.04 to 40_custom

Got it figured out (with help from Google!).

You need to use 'multiboot' in the 40_custom entries. Here is what my fixed 40_custom files look like:

Lucid -

#!/bin/sh
exec tail -n +3 $0
# This file provides an easy way to add custom menu entries. Simply type the
# menu entries you want to add after this comment. Be careful not to change
# the 'exec tail' line above.
# 10-10-12 customization
menuentry "Ubuntu, Maverick Meerkat"{
insmod ext2
set root='(hd0,7)'
multiboot /boot/grub/core.img
}
menuentry "Ubuntu, Natty Narwhal"{
insmod ext2
set root='(hd0,9)'
multiboot /boot/grub/core.img
}

Maverick -

#!/bin/sh
exec tail -n +3 $0
# This file provides an easy way to add custom menu entries. Simply type the
# menu entries you want to add after this comment. Be careful not to change
# the 'exec tail' line above.
# 10-10-12 customization
menuentry "Ubuntu, Lucid Lynx"{
insmod ext2
set root='(hd0,1)'
multiboot /boot/grub/core.img
}
menuentry "Ubuntu, Natty Narwhal"{
insmod ext2
set root='(hd0,9)'
multiboot /boot/grub/core.img
}

I don't know if the insmod ext2 entry is necessary, but the example given in the answer I found at [SOLVED] Chainload GRUB2 -> GRUB2? included it, so I put it in.

Works! As I only have Lucid's 05_debian_theme 'customized', the grub menu for Maverick and Natty are using their default 05_debian_theme, meaning I have no nice grub menu's displayed when I go to them from Lucid. But that is easily fixable, and I'll get to that soon enough.

Issue solved.