06-11-2013
Yes, I was trying to preserve windows. I found the problem, turns out I was putting Lilo on the wrong disk and not fully enabling legacy bios support.
9 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Does anyone know what LILO stands for and what it exactly does during the boot process? (1 Reply)
Discussion started by: jensam
1 Replies
2. UNIX for Dummies Questions & Answers
Guys,
Any idea how to Install Lilo after Instal linux 7.2 ( 2.4.7 ). At first when i was installing Linux 7.2 i didnt install LILO because i have alllready installed Boot Magic from Power Quest (Having dual boot Windows2000 Server and Linux Red Hat7.2 ). I didnt install LILO because i was... (20 Replies)
Discussion started by: killerserv
20 Replies
3. UNIX for Dummies Questions & Answers
I have installed linux.. but it wont boot.. it says: "LI"
and then my computer freezes..
it has worked before..
A couple of days ago, I tried to install OpenBSD.. I used the whole disk for it..
I think it's something with the MBR-settings I made in the OpenBSD installation..
How can... (1 Reply)
Discussion started by: Hamcha
1 Replies
4. Filesystems, Disks and Memory
:confused: I've been trying to figure out what happen to Windows 2000 since I upgrade my partition of Red Hat 7.1 to 7.2. Before I even upgraded my system would dual boot both OS's now it only sees Linux in lilo. Can some one help me I'm in need of help. Can you tell me what I'm missing in my... (3 Replies)
Discussion started by: aojmoj
3 Replies
5. UNIX for Dummies Questions & Answers
I have a machine that dual boots win2k and linux, and we are handing it off so it no longer needs linux. Linux is a separate partition so I can delete the partition, but I need to remove lilo- how do I do that ? (7 Replies)
Discussion started by: dangral
7 Replies
6. Red Hat
I use redhat7.0, and I want to update kernel to 2.4.0,I make following steps:
#gzip -cd linux-2.4.0.tar.gz | tar xvf -
#cd linux
#make mrproper
#make config
#make dep
#make bzdisk
#make modules
#make modules_install
#cp linux/arch/i386/boot/bzImage /boot
then I modify lilo.conf,like... (0 Replies)
Discussion started by: konvalo
0 Replies
7. UNIX for Dummies Questions & Answers
I want to gain read/write access to a Windows 8 partition from a linux live cd. Prior to Windows 8, I used ntfs-3g to mount the partition from the command line.
The "Fdisk -l" command does not seem to be able to read efi partitions. There must be some new strategy for linux users. This is... (6 Replies)
Discussion started by: jamarsh
6 Replies
8. Red Hat
Hello
This is happening on: 3.13.7-200.fc20.x86_64
This happened already some weeks ago, until now i didn install linunx onto this machine, as i had to turn in the laptop to the service center so they could fix the UEFI flash storage.
Either way, its happening again. as i installed Fedora 20... (1 Reply)
Discussion started by: sea
1 Replies
9. Solaris
I can't get dual boot to work. I have first installed Windows10 on a new SSD, and then I installed Solaris 11.3 on the same disk. When I boot the disk, the GRUB shows Solaris, but no Windows. I can boot into Solaris fine. When I try to boot from a Windows10 partition, it does not work. Windows says... (7 Replies)
Discussion started by: kebabbert
7 Replies
LEARN ABOUT CENTOS
bio_alloc_bioset
BIO_ALLOC_BIOSET(9) The Linux VFS BIO_ALLOC_BIOSET(9)
NAME
bio_alloc_bioset - allocate a bio for I/O
SYNOPSIS
struct bio * bio_alloc_bioset(gfp_t gfp_mask, int nr_iovecs, struct bio_set * bs);
ARGUMENTS
gfp_mask
the GFP_ mask given to the slab allocator
nr_iovecs
number of iovecs to pre-allocate
bs
the bio_set to allocate from.
DESCRIPTION
If bs is NULL, uses kmalloc to allocate the bio; else the allocation is backed by the bs's mempool.
When bs is not NULL, if __GFP_WAIT is set then bio_alloc will always be able to allocate a bio. This is due to the mempool guarantees. To
make this work, callers must never allocate more than 1 bio at a time from this pool. Callers that need to allocate more than 1 bio must
always submit the previously allocated bio for IO before attempting to allocate a new one. Failure to do so can cause deadlocks under
memory pressure.
Note that when running under generic_make_request (i.e. any block driver), bios are not submitted until after you return - see the code in
generic_make_request that converts recursion into iteration, to prevent stack overflows.
This would normally mean allocating multiple bios under generic_make_request would be susceptible to deadlocks, but we have deadlock
avoidance code that resubmits any blocked bios from a rescuer thread.
However, we do not guarantee forward progress for allocations from other mempools. Doing multiple allocations from the same mempool under
generic_make_request should be avoided - instead, use bio_set's front_pad for per bio allocations.
RETURNS
Pointer to new bio on success, NULL on failure.
COPYRIGHT
Kernel Hackers Manual 3.10 June 2014 BIO_ALLOC_BIOSET(9)