User:User3412: Difference between revisions

import>User3412
No edit summary
m 197 revisions imported
 
(86 intermediate revisions by 9 users not shown)
Line 1: Line 1:
{{Template}}
__NOTOC__
{{Rofag}}
<!-- https://crustywin.miraheze.org/w/index.php?title=Mod:Windows_XP_75MB_Edition&diff=prev&oldid=46 because don cheadle wants me to be Vortrag for some reason -->
{{Mediawiki}}
<!-- Super Monkey Ball time -->
{{QEMU}}
Hello! I'm user3412, and this is my userpage! <br>
{{VSCode}}
I removed the content that's useless for me <br>
{{Electron}}
==Some vandalism i found on BetaWiki==
{{Git}}
=== Five robux a day keeps the wegjobip rh09ieor43gtb0gt ===
{{KernelHackerParam}}
Note: i dont support ukraine and europe, but i do support russia and american countries (Like the USA and Brazil i guess)


Note 2: please dont put the Userpage template on my userpage, i dont want and/or need that, thanks
get your free tvs


hes a CollabVM Wiki oldfag, hes a CollabVM midfag too and he made a bunch of spam pages,thank god he coped and seethed and stopped making spam pages [[File:Cool.png]]
free tvs
 
he also hates ukraine,likes the ukraine war and wants ukraine to be deleted because alot of people complained with russia for the war
 
he also changes images uploaded by forkies,vandalizers and/or jawfuls to 3d chocolateman to stop forkingness


get your free televisions
==Fandom account==
[https://microsoft.fandom.com/wiki/User:User3412gottheirballsucked proudly vandalizing fandom] ([https://microsoft.fandom.com/wiki/Special:Log/block?page=User%3AUser3412gottheirballsucked not anymore]) <br>
I also vandalized the Unikitty fandom in 11 July 2021 (along with others in CollabVM), but i didn't create a account in fandom, and the computernewb wiki article is gone (though the url was https://computernewb.com/wiki/Unikitty_Wiki_Raid_of_2021, so the article name was "Unikitty Wiki Raid of 2021"), and the accounts created were [https://unikitty.fandom.com/wiki/Special:Contributions/Iceppfro Iceppfro], [https://unikitty.fandom.com/wiki/Special:Contributions/Collabvm43344343 Collabvm43344343] (that account wasn't blocked, though) and [https://unikitty.fandom.com/wiki/Special:Contributions/Collabvmusergang Collabvmusergang] (globally locked by fandom)
==Facts==
==Facts==


andrej thought that i (user3412) am User123 because of similiar names, but i dont shill into CSS and "user3412" was the best name i could make
Andrej thought that I (user3412) am User123 because of similar names, but I don't shill into CSS and "user3412" was the best name I could make


I hate emojis because they are new things which i do also hate except for some
I hate (unicode) emojis because they are new things which I do also hate except for some


i love old things
I like old things


==The (shitty) rest==
<strike>I know how to hack linux by simply editing the boot parameters to use /bin/sh as the init</strike> That just makes linux enter on single-mode


Auuuugh dell did not make open-source drivers for bsd and/or linux for my laptop
I know how to install MediaWiki


i also got my ip leaked on uservm multiple times starting with DESKTOPGOOSE's what the fuck I VM in 2021
I know how to use Git


page vandals: 8
I use VSCodium as the main editor


He does not like sloths but he does hate emoji and replaces emoji with their meaning
I know how to use both QEMU CLI and virt-manager


I also use VS Code
I am an Brazilian since I was born in Brazil, and I always live in Brazil


And jacks off VS Code too
I also got my IP leaked on UserVM multiple times starting with DESKTOPGOOSE's (HNA's username at the time) what the fuck 1 VM in 2021 <!-- Comment by AIDSFighter: ????? !-->


Specs are [[User:{{PAGENAME}}/Specs|here]]
I don't like HP


{{#babel: pt-br | ar-0 | ru-0 | en-2 | es-1 | fr-1 | br-0 | uk-0 | af-0 | ca-0 | pl-1}}
My favorite computer brand is DELL


XMPP contact: user3412@blah.im
I may leave the CollabVM Community in the distant future if i forget about CollabVM in the distant future


even though i play roblox all day, i play retrostudio most of the time
==History of the user3412 username/nickname==


you are not getting my roblox username
It actually started when user3412 was choosing an username for betacraft launcher


I love the red robin tune
he was trying to decide the username, and user3412 was the choice for him so he used the user3412 username


[[User:User3412/old|here]] is the old autistic version of the page
this happened before april, 4 2022


[[File:420edits.png|thumb|none|world record: 420 edits]]
==CfA: Trash edition response==


i joined CollabVM in october 2020 when i saw siam alam's new video showing collabvm
When user3412 saw Cfa: Trash Edition, user3412 decided to make candidates for deletion on over 13 pages. It isn't that much enough


[[File:Featured-made-with-crayons.svg|thumb|none|Made with crayons]]
==Babel==


<strike>strike test</strike>
{{#babel: pt-br | ar-0 | ru-0 | en-2 | es-1 | fr-1 | br-0 | uk-0 | af-0 | ca-0 | pl-1}}
 
 
 
 
    Partners
    Support
    Community
    Ubuntu.com
 
    Página Imutável
    Informações
    Anexos
 
    Ubuntu Wiki
    Entrar
    Help
 
OVMF
 
OVMF is a port of Intel's tianocore firmware to the qemu virtual machine. This allows easy debugging and experimentation with UEFI firmware; either for testing Ubuntu or using the (included) EFI shell.
 
Quick Start using virt-manager
 
    sudo apt-get install virt-manager libvirt-daemon ovmf
    Start creating a new VM in virt-manager, but before finishing, click "Customize configuration before install"
    Change the Firmware Option from BIOS to EUFI. (If it's not available do a systemctl restart libvirtd)
 
    Do whatever normal VM things you want to do. Initial screen when booting should now show TianoCore.
 
Builds
 
This is less necessary as the ovmf is now a package you can just apt get.
 
If you'd like to build your own image, follow the instructions at UEFI/EDK2. This will create the file Build/OvmfX64/DEBUG_GCC46/FV/OVMF.fd, which is the actual firmware image that qemu will use. Simple copy this to a file called bios.bin in the current directory.
 
Basic Qemu usage
 
For the simplest use-case, you can boot the machine like this (with bios.bin in the current directory):
 
qemu-system-x86_64 -L .
 
The -L . option tells qemu to look in the current directory for the bios.bin firmware image.
 
This will allow you to play with the firmware setup screens, and the EFI shell. However, there are no virtual disks available, so you won't be able to boot anything.
 
UEFI shell running on QEMU
 
Running an Ubuntu ISO
 
We can use the -cdrom argument to qemu to specify the Ubuntu installer ISO as a virtual CDROM. In this case, we also need to tell qemu that we want a little more memory (1024MB) than the default (128MB):
 
qemu-system-x86_64 -L . -cdrom ubuntu-12.04-desktop-amd64.iso -m 1024
 
Performing an install
 
If you'd like to run the Ubuntu installer and perform an actual install within the virtual machine, you'll need some virtual disk to install to. In this case, we'll create a 10GB file to act as the virtual disk:
 
truncate -s 10G ovmf.disk2
 
Then we can tell qemu to use this file as a virtual disk:
 
qemu-system-x86_64 -L . -cdrom ubuntu-12.04-desktop-amd64.iso -hda ovmf.disk -m 1024
 
If you prefer, you can use a block device as the qemu disk; just specify the device path instead of the file name (eg, -hda /dev/sdd). You'll probably need to run qemu with sudo for this to work.
 
Other usage
 
Some other options that may be helpful:
 
    -enable-kvm: Use the KVM virtualisation support for better virtual machine performance. Requires root.
 
    -serial pty: Allocate a PTY, and create a virtual serial device attached to the PTY. On startup, qemu will print the name of the PTY that is has allocated, and you can interact with it using screen /dev/pts/XX
 
    -monitor stdio: Start the qemu monitor from the qemu prompt. This allows you to control the virtual machine from the terminal.
 
    -nographic: Don't create a video device for the VM.
 
    -S: Don't start the VM immediately
 
    -hda fat:<directory>: Make <directory> available to the VM as a virtual FAT-formatted disk
 
This is how I generally use qemu for debugging:
 
sudo qemu-system-x86_64 -L . -serial pty -serial pty -monitor stdio \
        -drive file=/dev/local/virt-ovmf,if=ide,id=drive-ide0-0-0 \
        -nographic -S
 
This command:
 
    Creates two serial ports: one for the OVMF debug output, and one for a usable serial console
 
    Uses a LVM block device, /dev/local/virt-ovmf as the local storage
    Disables graphic output
    Starts the qemu monitor prompt on stdio
    Tells qemu not to start the machine right away.
 
I then:
 
    start two screen sessions on the PTYs that qemu prints
 
    start it by typing c at the monitor prompt
 
During boot, I get the OVMF debug output on the first screen session, and once the machine is booted, I get a login prompt on the second screen session. For this to work, you'll need to configure init to create a getty session on the serial ports. To do this from within your virtual machine:
 
cd /etc/init/
sed s/tty1/ttyS0 < tty1.conf | sudo dd of=ttyS0.conf
sed s/tty1/ttyS1 < tty1.conf | sudo dd of=ttyS1.conf
 
UEFI/OVMF (editada pela última vez em 2020-06-13 18:58:31 por jwilk)
 
The material on this wiki is available under a free license, see Copyright / License for details.