According to the Top 7, we need to select a 404 image - an image that will be displayed when users try to bring up a page that does not exist.
Please quote the source so the team can negotiate rights if necessary.
According to the Top 7, we need to select a 404 image - an image that will be displayed when users try to bring up a page that does not exist.
Please quote the source so the team can negotiate rights if necessary.
we could create a black image showing the error message in kernelpanic-flavor.
like http://orionida.files.wordpress.com/2008/02/kernel-panic.jpg but with some other data and errors (404 should be shown somewhere)
It's not complete(as in, 25 rows of text) but maybe this is a start?
[<c0292932>] __get_page+0xe2/0x1d2
[<c0120423>] search_disk+0xe9/0x19d
[<c09283d2>] search_backup_disk+0xf1/0x21
[<c0e29fa1>] search_frantically+0x12/0xe12
[<c0021df0>] __wait_on_server_magic+0x48/0x9
Warning: server_magic timeout reached!
[<c0f2359d>] get_error_page+0x2/0xd34
[<c0d34a9d>] __alert_code_monkeys+0x03/0xe9d
Warning: code_monkeys not responding to messages
[<c0a92d92>] __render_error_page+0x0/0x404
[<c02a94da>] render_404_error_page+0x0/0x0
Server panic - Aiee, your file was not found!
I made it community wiki, so edit this to be more complete, then just put it on your favorite terminal and screen shot it (or if you want to be really awesome, recompile linux and put in these functions and make the linux kernel actually say this, and then screen shot it)
Looks like Tux tried the rm -rf / command again. We really need to take that computer away from him.
Source: linux.org.uk.
Xeno found an image that I think could be a decent 404 picture, although we probably need to add text somewhere:
cat: /foo/bar: No such file or directory
Maybe not cat, but how about GET:
HTTP GET: http://unix.stackexchange.com/foo/bar: No such file or directory
(Does it really have to be an image?)
How about this as a U&L 404 "image" ? I tried to simulate loading (mounting) a URL, then a have a generalized fsck
error message related to failing to find a URL.
# mount /http/URL /dev/console
mount: special device /http/URL does not exist
# fsck /http/url
fsck 1.43.1 (29-Jun-2016)
fsck: No such file or directory while trying to open /http/url
The superblock could not be read or does not describe a correct
URL. If the device is valid and it really contains a URL (and
not swap or ufs or something else), then the superblock is
corrupt, and you might try running fsck with an alternate superblock.
You are now being dropped into an emergency shell.
#