you may try with
__fpurge()
On Wed, Jan 9, 2013 at 1:23 AM, Tobias Boege wrote:
> On Tue, 08 Jan 2013, Niroj Pokhrel wrote:
> > Hi all,
> > I tried to use fflush(stdin) in gcc as I used to in other compilers. But
> It
> > didn't clear my buffer so I am wondering how can I clear the stdin buffe
PM, beyond.hack
> wrote:
> > hello experts,,
> > I am on Fedora 16 and My current kernel is as per the uname -r output
> > is 3.1.0-7.fc16.i686.PAE
> >
> > I am compiling a kernel 3.4.1 and after the compilation the bzimage and
> > initramfs are successfully gene
hello experts,,
I am on Fedora 16 and My current kernel is as per the uname -r output
is 3.1.0-7.fc16.i686.PAE
I am compiling a kernel 3.4.1 and after the compilation the bzimage and
initramfs are successfully generated..
then doing a
#make install
is giving error like this::
sh-4.2# make install
@Vladimir Murzin--thnx. for the link..really interesting it is..
@Santosh sir,
Quoting from:
http://www.ibm.com/developerworks/linux/library/l-initrd/index.html
*The initial RAM disk (initrd) is an initial root file system that is
mounted prior to when the real root file system is available. The
So can i say that after the initiallisation that the bios do, the bios
code can access all the peripherals completely???
1..I mean that from the bios code only,, can i acess the harddisk
completely..specifically the kernel bcz. If i have accessed the MBR in
harddisk, so can i access the remaining
***when bootloader in bios executes its code, it do POST and other
things...then as I read from somewhere kernel does initrd to load some
basic modules so as to mount the root file system and then removes the
initrd fs.
(srry my mistake)
___
hello experts,,
I am starting out and heavily *confused* for the part of linux kernel boot::
*(plz. do rectify me at all the wrong places)*
when bootloader in bios executes its code, it do POST and other
things...then as I read from somewhere kernel does initrd to load some
basic modules
Experts..
> As we know that in virtual memory, virtual pages are allocated for a
> process..and when that memory is used page fault occurs and then handler
> allocates a page frame i.e. Real physical memory..hence our small physical
> memory are able to handle bigger processes...
>
so a information
