similar to: memdisk - grub2

Hello, I'm having a problem booting a compressed ISO image using memdisk via grub2 (version 2.02). The entry in my grub.cfg looks like: menuentry 'boot ISO image' { linux16 /memdisk iso initrd16 /my-image.iso.gz } When selected, this starts to boot and then fails with: Ramdisk at 0x37979000, length 0x0033b298 gzip image: decompressed addr 0x7f7f7000, len

Hello CentOS users, in the recent time I keep getting the logwatch warnings from my 2 dedicated servers running CentOS 7.4.1708. I guess because of the numerous kernel updates (because of Spectre+Meltdown) in the near past? Could someone please suggest me, which files in my /boot partition would be safe to delete? I would like to avoid the situation of having to boot the rescue partiton etc.

> Hello, > > I'm having a problem booting a compressed ISO image using memdisk via grub2 (version 2.02). The entry in my grub.cfg looks like: > > menuentry 'boot ISO image' { > linux16 /memdisk iso > initrd16 /my-image.iso.gz > } > > When selected, this starts to boot and then fails with: > > Ramdisk at 0x37979000, length 0x0033b298

I have a need to have a live Linux (Debian or sysrescued ) to boot off a hard-drive so that the hard-drive ends up umounted after boot. (for running partimage ). I've gone down the memdisk iso route and read about the issues there - I've seen a way to do this by mounting over nfs (messy) - but I want to do this without the network. I'm thinking that there should be a way to loop

The correct way has to be one or the other: http://wiki.dovecot.org/LDA/Exim are mutually exclusive with http://wiki.dovecot.org/HowTo/DebianStable It appears that exim can either call dovecot's LDA or make the delivery itself. There may be good reasons to do it one way or the other. ---------------------------------------------------------------- Karl Schmidt

Hi Daniel, Thanks for replying; I was hoping to get in touch with you on this issue. I had a look at how SelectionIDAG does it when generating the matcher table, and it does consider the implicit defs as additional output. Here is the match table generated for the pattern: /* 0*/ OPC_CheckOpcode, TARGET_VAL(ISD::SIGN_EXTEND), /* 3*/ OPC_MoveChild0, /* 4*/ OPC_CheckOpcode,

Someone might want to add this to the docs - cable list and compatibility list - took me way to long to find. I was trying to find information on my UPS and came up with the following names for the same UPS series. Powerware 5119 Exide name was NetUPS SE Deltec name was PowerRite Pro II (1000VA-3000VA) What I have: The Exide NETUPS SE model PRC2400a p/n 05144038-3904 OUTPUT 2400VA 1600 WATTS

I just moved to dovecot with Maildir. I think this is probably a stupid question, but I couldn't find an answer after an hour of googling and searching the wiki. What would happen if I ran a script that did this: mv ~/Maildir/.folder_one/cur/* ~/Maildir/.folder_two/cur/ My hunch is it might break things. What if dovecot was stopped? ,.,.,. Where can I find a list of files in

Something came up that Confounded problems in my move from UW-imap to dovecot. I found a problem with the new icedove update in Debian lenny when moving from 1.5.0.13+1.5.0.14b.dfsg1-0etch1 to 2.0.0.9-3 that could look like a dovecot issue. Icedove runs for a while but eventually quits updating the displayed email, yet appears to be working and busy trying to get messages from the server. I

First things first -- I've alluded to this before, but let me be clear -- there is no global database that contains monitor-specific information which is used by any linux drivers. Please forget any notions you had of such a thing existing or being used. The information comes from the EDID blob supplied by the monitor. Presumably hwinfo has a primitive EDID parser, which is where that

Dear Syslinux folks, For a firmware update I am following the Gentoo Wiki [1] to create a floppy image of 20 MB, so that the vendor update utility fits. Unfortunately, FreeDOS does not load, and it seems to hang loading the FreeDOS kernel. The original FreeDOS image boots. Do you know if that issue is memdisk related? It?s started from GRUB with the commands below. linux16 /boot/memdisk

This is set up with Win2K boxes sharing a QB file on a SAMBA share. It may be quite different than with 95-98x-ME(Miserable Edition). There are two or more problems - one thing I identified is that it is possible for two computers to connect to the QB(QuickBooks) share using the same quick books logon - something that will cause data corruption. (Something that could have been easily

Hello, I'm trying to boot a dos floppy stored on a disk image which is initially loaded over pxe using memdisk. I've created the disk image as follows: dd if=/dev/zero of=$IMGLOCATION/$IMGNAME bs=$(( 1024 * 1024 )) count=20 LOOPDEV=$(losetup --show -f $IMGLOCATION/$IMGNAME) MAJOR_MINOR=$(ls -l $LOOPDEV|awk '{print $5$6}'|sed 's/,/:/') DMSIZE=$(( $(ls -l

This is probably the problem May 3 16:44:45 kernel: [ 7.068336] nouveau E[ DEVICE][0000:08:00.0] unknown chipset, 0x137000a1 May 3 16:44:45 kernel: [ 7.068401] nouveau E[ DRM] failed to create 0x80000080, -22 May 3 16:44:45 kernel: [ 7.068723] nouveau: probe of 0000:08:00.0 failed with error -22 I can make this card available - if you can tell me an older card that can do the

Hi all, My computer is booted with UEFI and Grub2. I tried to load VHD files with memdisk and boot from there. memdisk is extracted from 'bios/memdisk' in syslinux 6.03 zip file. In Grub2, I executed: linux16 /memdisk harddisk initrd16 /Win10.vhd Then the system frozen at 'initrd16' line. The VHD file is 8192MB, fixed image. I also tried to boot a small floppy disk (FreeDOS), and

This is sort of working -- but I can't get it to do a 4k output. Not sure how the monitor resolution is detected - This monitor is supposed to do 3480x1200 60hz 4:4:4 But the info I get from hwinfo is different. How does nouveau get this information? If it is from an ID - with a list - the list is probably is wrong. # hwinfo --monitor 95: None 00.1: 10002 LCD Monitor [Created at

On 05/06/2017 12:38 PM, Ilia Mirkin wrote: > The information comes from the EDID blob supplied by the monitor. > Presumably hwinfo has a primitive EDID parser, which is where that > information comes from. A more complete EDID parser is available at > > https://cgit.freedesktop.org/xorg/app/edid-decode/ > > For example, > > $ ./src/edid-decode/edid-decode

Hi, I'm using libguestfs 1.42, When I run the following python3 commands on a rhel7.8: print(g.ls('/sys')) print(g.sh('ls /sys')) I get: [] block bus class dev devices firmware fs hypervisor kernel module power It seems that g.ls('/sys') is chrooted correctly. But g.sh('ls /sys') isn't. I came across this behavior when I used

Hello, Acceleration for Pascal cards is coming in Linux 4.12, support for Pascal cards in xorg-video-nouveau is in 1.0.15, and if I remember correctly, on the Mesa-side, you will need >=17.0. Pierre On 02:04 am - May 04 2017, Karl Schmidt wrote: > This is probably the problem > May 3 16:44:45 kernel: [ 7.068336] nouveau E[ DEVICE][0000:08:00.0] unknown chipset, 0x137000a1 > May

https://bugzilla.mindrot.org/show_bug.cgi?id=2461 Bug ID: 2461 Summary: Source IP missing in log when no suitable key exchange method found Product: Portable OpenSSH Version: 6.0p1 Hardware: Other OS: Linux Status: NEW Severity: normal Priority: P5 Component: sshd