You would have to be logged in as the administrator.
ANSWER
It depends on your operating system. A kernel is basicaly a line of code, different kernels control different operations for different systems within the computers program.
The closest thing to obtainging a true "kernel mode" is to run an open source Operating system like linux.
With something like windows you can obtain through administrative tools access to operating system programms, you can't truly rewrite (easily) the programs within your system.
A process transitions from user mode to kernel mode usually with some form of software interrupt. On x86 CPU's, the "INT 0x80" instruction is commonly used for running system calls. The kernel traps this software interrupt, processes the request, and returns to user mode by returning from the interrupt. This describes how real operating systems like Linux and FreeBSD work. Windows may work similarly to this, but it's not a real operating system anyway.
A modern symmetrically multi-processing operating system typically, today, consists of millions of lines of code. Most of these, eg Windows, Linux, FreeBSD, NetBSD, OpenBSD among many others, are written in the 'C/C++' programming language.
The above mentions INT 0x80 as being used on x86 CPUs, the author above is absolutely correct, though the answer could be further refined to say that INT 0x80 is specific to the Linux operating system kernel as being the maskable software interrupt used to invoke a system call (whether that be on ring -1, ring 0 or another ring if other rings are available on a given architecture - eg, VMware probably supports ring -1 on architectures supporting ring -1 so that guest operating systems may have free access to ring 0). That may well be the longest sentence I've ever written. :)
As INT 0x80 is a Linux maskable interrupt, it would also be used on other architectures as well such as Sun Microsystems SPARC or Digital Equipment Corporation VAX machines.
System calls (or SysCall/SysEnter) are used for many other purposes, particularly to access various hardware devices such as locally attached disk drives, USB devices, SCSI devices, Network (eg Ethernet [including Arcnet or Token Ring, assuming such things still exist]) cards or other bus attached devices etc.
I must agree with the above author's last sentence as well, though a Rockwell International engineer I once knew classified Windows as a 'virus' as opposed to a 'real' operating system like Linux (probably because Windows tends to proliferate as well as wreak havoc upon it's users).
Code running in kernel mode has unlimited access to hardware and CPU. Code in user mode can't address memory that kernel mode does not allow it to.
User mode and Kernel mode
bt.o is the kernel mode driver. When you insmod bt.o you are inserting it into the kernel, where it can cause bad things to happen if it screws up. btduser is the user mode driver. It runs as an application in user space, where usually the worse thing that can happen is a segfault. You don't have to insmod anything for user mode. You just run the application.
user mode and kernel mode
Kernel ModeIn Kernel mode, the executing code has complete and unrestricted access to the underlying hardware. It can execute any CPU instruction and reference any memory address. Kernel mode is generally reserved for the lowest-level, most trusted functions of the operating system. Crashes in kernel mode are catastrophic; they will halt the entire PC.User ModeIn User mode, the executing code has no ability to directly access hardware or reference memory. Code running in user mode must delegate to system APIs to access hardware or memory. Due to the protection afforded by this sort of isolation, crashes in user mode are always recoverable. Most of the code running on your computer will execute in user mode.
Kernel mode is considered a 'privileged' mode, meaning that code executing in that mode can have access to any part of the system, memory, devices, etc. There are no limitations on what it can do. User mode only allows certain operations. Anything requiring any amount of privileged must request the kernel to do things on their behalf. User mode is not a privileged mode and is therefore restrictive in terms of accessing memory, devices, etc.
The Windows XP Architecture uses both Kernel Mode and User Mode. The kernel mode is the layer of the operating system's code that is responsible for handling such fundamental operating system items as virtual memory and scheduling which applications will run at any given time. User mode is where your actual program runs and is controlled by components of the kernel. For example, the kernel is responsible for allocating the memory that an application uses.
Supervising mode is what system kernel runs in. It has unrestricted access to hardware, processor, memory and everything else. User mode is managed by supervisor mode, so programs can't crash other programs deliberately by writing over their memory. User mode programs communicate with hardware and kernel itself by system calls.
The user mode is :a mode that prvides an interface between the application and the OS and only has access to the hardware resources through rhe code running in kernel mode .Type your answer here...
because they love colonel burger
No. Regardless of what user you are running as, all your tasks are run in user mode. Supervisor mode is reserved for kernel-level processes.
In Windows NT a mutant provides kernel mode or user mode mutual exclusion with the notion of ownership.