FreeBSD or Linux from Windows

FreeBSD is also very good for emulation, especially game consoles like Sonys PS3, or Nintendos Switch.
Due to the efficient kernel scheduler, I think.
If hardly, the rpcs3 team clearly states that FreeBSD gives the most performance compared to linux, although it wasn't the case before.
I tried yuzu on FreeBSD, and the performance in demanding games clearly improved compared to minimal linux distros or Windows.
I agree with this 100%. I have been using ps3/ps2/n64/gamecube emulators and the performance seems to be far better than it ever was on Linux. PCSX2 has the mouse mapping which is great. I can play titles using keyboard and mouse. I wasn't able to find that feature on RPCS3. :/
 
cmd LOL. VBScript will get you further than command line unless u running batch scripts. I once made a script to release and renew my ip to stay online while a hotel admin kept trying to kick me off the router. LOL. I used it in conjunction with a spoofed mac address. But VBScripts are pretty powerful in the Windows World. Even basic scipts like the following are quite useful at times:
Until its deprecated by MS

 
I agree with this 100%. I have been using ps3/ps2/n64/gamecube emulators and the performance seems to be far better than it ever was on Linux. PCSX2 has the mouse mapping which is great. I can play titles using keyboard and mouse. I wasn't able to find that feature on RPCS3. :/
Maybe that feature could be patched in into rpcs3.
 
LibreQuest SDK Chan are you running programs directly or using Linuxulator? I have yet to try emulators but it is very satisfying to know both of you have them working :) I like to play old games from time-to-time. Also a big Thank You to SDKChan for the poudriere information. SDKChan = Awesome :)

Espionage724 Thank you for the Wacom information. I am happy to know that some of you are using tablets with FreeBSD. I need to be able to use my tablet from time-to-time.

I have a usb camera with my microscope. I must be able to use this camera. I will test it out sometime soon, then see what happens. I taught myself how to dissect and identify flies and spiders, so dipterology and arachnology is a favorite hobby of mine. I also like to photograph nature with my macro lens. My microscope and camera are very important to me.

I'm currently reading books about Unix and FreeBSD. I have the following books to help me grasp this system a bit quicker:
Absolute BSD - The Ultimate Guide To FreeBSD (2002)
Absolute OpenBSD - Unix For The Practical Paranoid (2003)
Beginning Unix (2005)
BSD Hacks - 100 Industrial-Strength Tips & Tools (2004)
Embedded FreeBSD Cookbook (2002)
Mastering UNIX Shell Scripting
O'Reilly - BSD Hacks
O'Reilly - The Complete FreeBSD 4th Edition
OReilly - Unix Power Tools
Prentice Hall - The Art Of Unix Programming 2003
Teach Yourself FreeBSD In 24 Hours (2003)
The Complete FreeBSD, 4th Edition (2003)
Unix System Administration - A Beginner's Guide (2002)

anyone have other recommendations? I feel stupid sometimes whenever i am reading because i lack knowledge of certain things coming from my Windows world (like awk and sed). I have alot of catching up to do. On the other hand, even command prompt uses cd, dir, mkdir etc, so i am used to that stuff. I think that FreeBSD is written in C language, is this correct?
 
LibreQuest SDK Chan are you running programs directly or using Linuxulator? I have yet to try emulators but it is very satisfying to know both of you have them working :) I like to play old games from time-to-time. Also a big Thank You to SDKChan for the poudriere information. SDKChan = Awesome :)

Espionage724 Thank you for the Wacom information. I am happy to know that some of you are using tablets with FreeBSD. I need to be able to use my tablet from time-to-time.

I have a usb camera with my microscope. I must be able to use this camera. I will test it out sometime soon, then see what happens. I taught myself how to dissect and identify flies and spiders, so dipterology and arachnology is a favorite hobby of mine. I also like to photograph nature with my macro lens. My microscope and camera are very important to me.

I'm currently reading books about Unix and FreeBSD. I have the following books to help me grasp this system a bit quicker:
Absolute BSD - The Ultimate Guide To FreeBSD (2002)
Absolute OpenBSD - Unix For The Practical Paranoid (2003)
Beginning Unix (2005)
BSD Hacks - 100 Industrial-Strength Tips & Tools (2004)
Embedded FreeBSD Cookbook (2002)
Mastering UNIX Shell Scripting
O'Reilly - BSD Hacks
O'Reilly - The Complete FreeBSD 4th Edition
OReilly - Unix Power Tools
Prentice Hall - The Art Of Unix Programming 2003
Teach Yourself FreeBSD In 24 Hours (2003)
The Complete FreeBSD, 4th Edition (2003)
Unix System Administration - A Beginner's Guide (2002)

anyone have other recommendations? I feel stupid sometimes whenever i am reading because i lack knowledge of certain things coming from my Windows world (like awk and sed). I have alot of catching up to do. On the other hand, even command prompt uses cd, dir, mkdir etc, so i am used to that stuff. I think that FreeBSD is written in C language, is this correct?
I am running them from latest packages. For the USB microscope you'll need to install and enable webcamd. The instructions are in the handbook for usb webcams.
 
UNIX command line doesn't use dir. There's a few ways to create a command alias, though ;), like via .shrc, .login, or even via a symlink. Or you can write a Perl/Python/ruby script that lets you use Windows commands in a UNIX shell - I do remember seeing such an exercise in one of my Computer Science classes in college, BTW. The point was to type a Windows command into a UNIX shell, and have the shell actually react with a similar listing. One simple example was equating dir with ls.

The nice thing about BSD is that unlike Linux, even books over 20 years old are still useful in getting a solid handle on the basics. They might refer to really old versions of shells, interpreters and compilers, though. Even FreeBSD has gone through some changes - in the past, it used .txz and .tgz extensions for packages that get installed. And ZFS is something that only became available in 2017 on FreeBSD.
 
Dear forum,

I am a Windows-only user since 1999 and i am not moving forward with Windows 11...
Hello,
i read some comments, not all, and kindly disagree with those, so I thought I could give my opinion.
I tried windows a few years ago and did not like it because It was slow and was refusing to let me do things without obvious reasons.Plus, I could not understand why I had to pay to use my computer (I was young and naive :)). I then tried linux and was impressed. It provided equivalent applications for free, out of the box. The installation was straight forward, did not force me to lose time installing drivers and installing a software was just a command line away, while windows expected users to search, download and install binaries. Windows felt like something useless on its own.
Because I wanted bleeeding edge applications, I was compiling a lot of stuff in the end and switched to gentoo, that I still use nowadays for desktop.
I do pretty everything using command line because I find it fast and more powerful than a GUI. To be honest, there is one thing (and only one) that I consider better in microsoft ecosystem: office
That is my experience.

My (not at the time) wife bought a laptop but was complaining about slowness and crashes. I installed linux for her to try; she was happy with it and never switched back to Windows.
She NEVER uses command line and does everything through the GUI.
That is her experience.

To summarize, It is adaptable to different profiles.

Years later, I felt in love with FreeBSD, the core system is small but still provides natively a lot of functionalities that are, surprinsingly, not that easy with linux. Examples are sr-iov, fibre channel/iscsi...
But, I only once successfully installed it for desktop. It was hard to get a desktop interface(plus, it broke from time to time) and setting the language was even harder.
For this reason I use it for my servers, routers, etc... and use linux on desktop.

So, from my experience, I would advise you to try linux, even mint linux if you want.That would be a good start.You are not stuck with it and can decide later to keep it or switch to another distribution. Even FreeBSD ;-)
 
FreeBSD is also very good for emulation, especially game consoles like Sonys PS3, or Nintendos Switch.
Due to the efficient kernel scheduler, I think.
If hardly, the rpcs3 team clearly states that FreeBSD gives the most performance compared to linux, although it wasn't the case before.
I tried yuzu on FreeBSD, and the performance in demanding games clearly improved compared to minimal linux distros or Windows.
The point of all these posts here is: FreeBSD is a well rounded O/S that can be used for anything. The fact that there is no ONE graphical user interface is because there is no central authority in the project telling we developers make this or some other GUI our default. We all do our own thing. The downside is that there is so much choice and the many GUI options aren't cohesively bundled into one ISO or a single package that magically builds a desktop.

Ideally someone should publish an ISO with a default GUI. People should volunteer to pitch in and help out. We're short of people to do things like this.
 
LibreQuest SDK Chan are you running programs directly or using Linuxulator?
I never tried Linuxulator, but I read that it tends to add a small overhead compared to a ported application.
Whether it is big enough to notice, I don't know, but I don't want to test it with demanding games which already struggle to maintain double the framerate they should run with (60FPS instead of 30FPS) for example.

I'm currently reading books about Unix and FreeBSD. I have the following books to help me grasp this system a bit quicker:
Absolute BSD - The Ultimate Guide To FreeBSD (2002)
Absolute OpenBSD - Unix For The Practical Paranoid (2003)
Beginning Unix (2005)
BSD Hacks - 100 Industrial-Strength Tips & Tools (2004)
Embedded FreeBSD Cookbook (2002)
Mastering UNIX Shell Scripting
O'Reilly - BSD Hacks
O'Reilly - The Complete FreeBSD 4th Edition
OReilly - Unix Power Tools
Prentice Hall - The Art Of Unix Programming 2003
Teach Yourself FreeBSD In 24 Hours (2003)
The Complete FreeBSD, 4th Edition (2003)
Unix System Administration - A Beginner's Guide (2002)

anyone have other recommendations? I feel stupid sometimes whenever i am reading because i lack knowledge of certain things coming from my Windows world (like awk and sed).
It depends how deep you want to dive into FreeBSD.
For grasping FreeBSD as it is and be able to use it on day to day basis as a regular user/system administrator I would recommend Absolute FreeBSD from Michael W. Lucas, it is written with the typical black humor, but still very detailed.
After reading that book I would recommend to skim some of the FreeBSD Handbooks online.
FreeBSD provides some very great online resources for free, too.

If you want to dive even deeper and learn how FreeBSD works internally this is my preferred choice: Design and Implementation of the FreeBSD OS.

I also don't know sed or awk that much, but each time I need something I read the manual pages or search for examples.
To be honest I am rarely needing both of them so, I don't worry to much about them, or regular expressions.

On the other hand, even command prompt uses cd, dir, mkdir etc,
The power shell and UNIX terminals have indeed some common commands they share.
cd, ls, clear, mkdir, mv, rm, rmdir is probably the same.
If you know one CLI you will get used fast to the other, too. :D

I think that FreeBSD is written in C language, is this correct?
To a large extend FreeBSD is indeed written in C, but you have small parts of Assembly in it, too.
 
Except we'll here from hundreds of people who will now post how much they don't like MATE or GhostBSD.
Exactly. When people think of an "out of the box" version of FreeBSD, they implicitly think of it as having their GUI stack of choice. They don't realize that it will very likely be running CDE as the primary desktop (or something else they don't use). Suddenly they become less interested in using and testing it.
 
Exactly. When people think of an "out of the box" version of FreeBSD, they implicitly think of it as having their GUI stack of choice. They don't realize that it will very likely be running CDE as the primary desktop (or something else they don't use). Suddenly they become less interested in using and testing it.
There was a thread where someone asked "Who is ideal for FreeBSD?". I guess one way to put it would be, "Who is the intended audience?". And in here, I could say that the intended audience is "People who don't mind discovering that FreeBSD is a largely DIY, and would not react negatively to discovering that the DIY part applies to stuff like GUI desktops, graphics stack, and servers.".

Well, with the support for wifi being what it is, I'd say that FreeBSD is also largely a DIY when it comes to wpa_supplicant.conf and roaming. The DIY part also applies to troubleshooting and researching error messages.
 
Well, with the support for wifi being what it is, I'd say that FreeBSD is also largely a DIY when it comes to wpa_supplicant.conf and roaming. The DIY part also applies to troubleshooting and researching error messages.
Very true. Because if they were then looking at using FreeBSD as a tool for setting up as WiFi access point rather than a client, suddenly they would really appreciate the DIY nature of FreeBSD. There would be less clutter to have to disable.

I do notice that people get very hungup on GUI and graphics. In some ways it has caused much of the open-source world to stagnate a little.
 
Snail I have Mint and i like it very much. I want to keep it and run a dualboot with FreeBSD. Mint is fantastic for a Linux machine. I really like the cinnamon DE but some will say that it is because i am a windows user :) Your post was a very nice read. I enjoyed your contribution to the thread. Thank You!

astyle I know that the dir command is ls. I made an error. I actually use ls -l as i prefer to see more info (also ls -l -d)
I also know about alias. see my attached screen captures but i have no desire to use dir, much less add it to my shrc file for longterm memory.

I want to add my notes for installing FreeBSD in VirtualBox in Windows 10 for any users interested in also installing FreeBSD. I notice that i have found alot of misinformation in threads and it is probably because 14.2 has changed certain things and those threads contain info for older versions of FreeBSD. For example, one does not have to add mouse to xinitrc because the mouse is enabled by default. The documentation mentions this as well. I suppose it is because of virtualbox-ose-additions. Little things like that have made my journey complicated. I have finally completed notes that i think could be helpful to other newbies. Please let me know if anything need adjusted. The following notes have worked for me in virtualbox 6.1.30 r148432 (Qt5.6.2)

1. setup Virtualbox

Quick outlook of Virtual box settings
I like to alot 40GB dynamic sizing but it is your call here.
However, you should atleast use 20 GB to enjoy installing packages

system
set Base memory to end of green area (half or slightly less-than half of total mem)
unchecked floppy (unless you want it)
checked Optical
checked Hard Disk
unchecked Network
checked Enable I/O APIC

display
Video Memory 128 MB
Graphics Controller: VBoxSVGA
unchecked Enable 3D Acceleration

Storage:
FreeBSD virtual drive (obviously)
I like to add two IDE devices for cds and leave empty

Audio
checked Enable Audio Output
default settings work:
Host Audio Driver: Windows DirectSound
Audio Controller: ICH AC97

Network
checked Enable Network Adapter
Attached to: Bridged Adapter
Name: your adapter should appear here
Advanced: checked Cable connected (wired is better and easier)
default Adapter type works: Intel PRO/1000 MT Desktop (8254OEM)

----------------------------------------------------------------

2. install FreeBSD using the FreeBSD-14.2-RELEASE-amd64-dvd1.iso
attached to one of your cdrom devices

a. be sure to add a non-root user during installation
b. at the end of installation you will notice a prompt:
use a shell to make further modifications?
select yes. you will be at a shell and see #
now is a good time to update FreeBSD.

issue the following commands (internet required and internet
should be attached when installing):
# freebsd-update fetch
wait for the update information to be fetched
when less reaches END, press Q key to quit less

# freebsd-update install
wait for the updates to be installed

exit the shell with a shutdown command:
# shutdown -h now

close virtualbox window (power off machine) whenever
you see the press any key to reboot text (do not reboot)

reboot seems to have issues when the iso is still attached
after shutdown.
vm settings: detach/remove installation iso from cdrom

start the FreeBSD virtualmachine again.

3. setup and configuration of FreeBSD

login as root (su doesn't make sense here):
$ pkg
- pkg is not installed so type yes to fetch it
$ pkg update
$ pkg install doas
- or: $ pkg install sudo
- i prefer doas. your choice.
$ pkg install nano
- i like nano editor over vi. your choice.
- vi is already installed, so continue.

change user permissions for your added user
my added user name is john
use your added user name instead of john:

$ pw groupmod wheel -m john
$ pw groupmod video -m john
$ pw groupmod operator -m john

if you chose to install doas:
$ nano /usr/local/etc/doas.conf

type the following in nano but change john:
permit :wheel
permit keepenv john as root

press Control key plus letter o to write
press enter to save/write the file
press Control key plus letter x to exit nano

if you chose to install sudo (and using vi):
$ visudo

find the following line:
# %wheel ALL=(ALL) ALL

remove the comment (#):
%wheel ALL=(ALL) ALL

to remove the comment, type i in vi to enter insert mode
just move the cursor to the # and press enter to move
the text to a newline.

press ESC key to exit insert mode.
type :wq
to write and quit vi.

now we need to make some changes to rc.conf
if you want to run a display manager at boot
$ sysrc sddm_enable="YES"
or whatever dm you have installed light-dm etc
i prefer to maintain a login shell and exit xorg to the shell
so at the prompt type:

$ sysrc moused_enable="YES"
- this enables mouse daemon
$ sysrc pf_enable="YES"
- this enables the built-in p(acket) f(ilter)
- you could also enable firewalls like ipfw instead of pf
$ sysrc sshd_enable="NO"
- if you have no need to run ssh, then disable it
$ sysrc dbus_enable="YES"
- if you want to run DEs, then enable it
$ sysrc hald_enable="YES"
- some say that it runs by default but i do not yet know
$ sysrc vboxguest_enable="YES"
$ sysrc vboxservice_enable="YES"
$ sysrc vboxnet_enable="YES"
- i do not know if the vbox entries are necessary in 14.2 or not

in order to mount cdrom, we need to enable the user to do so:
$ sysctl vfs.usermount=1

note: some say that the following UFS disk setting adds speed:
- sysctl vfs.read_max="128"
- i do not know if this is true or not
- do not use if ZFS is your installation selection

now we need to make a /boot loader.conf file:
$nano /boot/loader.conf

type the following into nano, then write, enter save, then exit:
autoboot_delay="5"
coretemp_load="YES"
ahci_load="YES"
aio_load="YES"
tmpfs_load="YES"
vboxdrv_load="YES"
pf_load="YES"
pflog_load="YES"
fusefs_load="YES"
snd_ich_load="YES"
snd_driver_load="YES"

the sound loaders are necessary to hear audio.
if ich is not your virtualbox controller, then you
probably selected hda. snd_hda_load="YES"

now we have to add pseudo file system support

$ nano /etc/fstab

add the following data to the file:
proc /proc procfs rw 0 0

then write, enter save, x to exit nano.

you can type clear at the prompt and return/enter to clear the screen:
$ clear

now we are done as root:
$ exit

login as regular user
login: $ john
password: $ ********

$ doas pkg install virtualbox-ose-additions
- or $ sudo pkg install virtualbox-ose-additions

FreeBSD is not windows but i like to reboot (-r) here:
$ doas shutdown -r now
- or $ sudo shutdown -r now

you can now install xorg for a graphical environment:
$ doas pkg install xorg
- or $ sudo pkg install xorg

you are now up and running with FreeBSD in VirtualBox.

when you want to shutdown/halt (-h):
$ doas shutdown -h now
- or $ sudo shutdown -h now

I hope that my notes are helpful to you :)
 

Attachments

  • tempaliasdir.jpg
    tempaliasdir.jpg
    34.4 KB · Views: 10
  • shrcaliasdir.jpg
    shrcaliasdir.jpg
    49.7 KB · Views: 8
I do notice that people get very hungup on GUI and graphics. In some ways it has caused much of the open-source world to stagnate a little.
I personally find that to be rather understandable - I was hung up on that, too, and was quite grateful for Xorg's auto-configuration, which FreeBSD got right rather early on. Yeah, it does take making sure the GPU drivers work.

As much as I tout ZFS and ports as the good things about FreeBSD, I believe I do have to say that Xorg working was just as important for me. If Xorg was not working, and was just as messy and unreliable to configure as Wayland is these days, then unfortunately, not even ZFS and the Ports would have been enough to win me over. And I'm afraid that in addition to Xorg, wifi is like that for a lot of people. As in, if wifi is not working quite right, and requires a huge constellation of details to get right and be stable, then a lot of the other perks don't really matter.

Kind of like the importance of having a modem that your ISP lists as compatible. Yeah, there's the whole Internet out there to explore, but none of it matters if your modem doesn't work right.

Or, even in terms of setting up a DE in FreeBSD - yeah, the desktops are nice to have, but their features don't matter if the GPU doesn't work right.
 
Or, even in terms of setting up a DE in FreeBSD - yeah, the desktops are nice to have, but their features don't matter if the GPU doesn't work right.
Agreed, in some ways a less noisy approach to developing an enterprise UNIX server operating system would be to completely refuse to support graphics and GPUs entirely. Be best of breed and focus just on what matters for the use-case.

I suppose with that idea, people would suddenly be grateful that FreeBSD is a DIY operating system. Community written (incomplete) WiFi drivers and all.
 
As in, if wifi is not working quite right, and requires a huge constellation of details to get right and be stable, then a lot of the other perks don't really matter.
I had FreeBSD set-up about 2 weeks ago on my laptop, was about to go outside and chill with it, but remembered I didn't figure out wifi and didn't feel like messing with it right then. I wiped to Windows and was outside in about 2 hours :p

About a week before that I went out-of-town and thought I had wifi figured out; I could connect to my phone's hotspot over wifi, but DNS didn't work until randomly a few minutes later. I switched to USB tethering that used to work easy and it too had no DNS (I'm pretty sure it's something with local_unbound just being enabled default conf and the network stack not all linking up correctly when a network interface drops connection in some way; seems perfect on home Ethernet, but inconsistent anything wireless).
 
From a fresh install, updates, fetching drivers, stripping the malware, locking down the machine takes quite a bit more time than 2 hours to do properly ;)
I have to get real times (probably in a few days :p) but Firefox sync usually shows 1-2 hour times from my last OS sign-on, and Firefox is usually the last core thing I install

I can go from wiped disk to latest installed CU in under an hour easy though and do the initial conf/lockdown stuff while the CU installs
 
I have to get real times (probably in a few days :p) but Firefox sync usually shows 1-2 hour times from my last OS sign-on, and Firefox is usually the last core thing I install

I can go from wiped disk to latest installed CU in under an hour easy though and do the initial conf/lockdown stuff while the CU installs
Have you done a security audit? I don't feel your setup is as secure/private as you might think in that case.

Besides, it takes way less time to read a man-page and write ~5 lines into wpa_supplicant.conf.
 
I've never had a need to run Linux for any reason.
If I want to play with a distribution, I do so on a VM running under ESXi.

I did tinker with CentOS for server-oriented personal needs, but also gave that up.
I find great value in FBSD and ZFS as the underlying platform for my XigmaNAS.

I'm the odd man out here, as everything I write is expressly intended to run on Windows Win32 and Excel on Windows.
I only service Windows machines, which I connect to my service network via Windows Server which manages DNS and DHCP for these Windows clients.

That aside, I have a great love and skill with the command line, vbscript and powershell.
Microsoft is continually making these obsolete, and/or forcing one to Win11 for the latest Powershell versions.
The loss of vbscript is troublesome as it is very comprehensive and available on every version of Windows.

I find the concept of OPC (other peoples code) to be irritating, especially so when presented in DLL form without source.
 
Have you done a security audit? I don't feel your setup is as secure/private as you might think in that case.
It's not exactly secure, but my main set-up is mostly defaults and things manually disabled. If anything my set-up takes longer to make an insecure speedy Windows set-up vs more security with turning up defaults :p

Besides, it takes way less time to read a man-page and write ~5 lines into wpa_supplicant.conf.

I'm not too into having to go into that file each time I might want to connect to a different AP or manually clean it up. I took a trip recently and had:
  • Home
  • Bus
  • Airport
  • Plane
  • New Airport
  • Hotel
  • Trains (transfers and to/from)
I'd have to find the SSIDs for all those places, command-line connect to it, and hopefully be good to go. Then for good practice remember to clear them out later :p

wifimgr GUI looks like it would make that easy, but when I was trying that app that's when I ran into the DNS thing.
 
Besides, it takes way less time to read a man-page and write ~5 lines into wpa_supplicant.conf.
It would take me maybe an hour just to make sure it works correctly... Exactly what lines? are the values the correct ones for the hotspot? What if I guess incorrectly, even after readng the manual? Am I to be stuck without wifi and access to Internet for a few days, or even the duration of the trip if I guess incorrectly? That's just not acceptable.
 
Agreed, in some ways a less noisy approach to developing an enterprise UNIX server operating system would be to completely refuse to support graphics and GPUs entirely. Be best of breed and focus just on what matters for the use-case.

I suppose with that idea, people would suddenly be grateful that FreeBSD is a DIY operating system. Community written (incomplete) WiFi drivers and all.
That kind of approach doesn't really fly in the enterprise. If you don't have the basics right, the perks and nice features don't matter.

A car needs 4 wheels and tires. If it lacks that basic stuff, it doesn't matter if it's a Rolls Royce or a Ferrari, it's not rolling! And I don't care that tires got outsourced to Michelin or Goodyear. If I'm expected to be the one installing the tires, and to know how to do it, I would not take the car even if I were paid. If the manufacturer refuses to install tires, I simply go to another shop. It may not offer all the flexibility I want (Ferrari HQ does actually file lawsuits against people who modify Ferraris after purchasing them!), but at least I would have a car that rolls and can take me places if I just have the money for gas... 🤷‍♂️

If I don't like the brand of the tires the car came with, I can get them swapped out later. But I would not buy a car that came without any tires from get-go. It would take being an enthusiast who already has a lot of things in place (brains and facilities) to take full advantage of a barn find of a car that doesn't even have 4 wheels properly installed on it.
 
Back
Top