is my newly installed release 14.2 functioning?

S

sehrguey-the-2nd

Freebsd 14.2 successfully installed in virtualbox. hooray! now what?
commands recommended by Handbook like "pkg" are answered with "Unknown command"
a try to add a user following online tutorials ended in errors.
what would advise kind and not overly busy people?
 
sehrguey-the-2nd said:
a try to add a user following online tutorials ended in errors.
Click to expand...
Try running bsdconfig in that VM, and poke around. It should offer a way to add a regular user.

That reminds me - that really should have been done during the installation.

Don't skip steps, and follow official documentation like the User Handbook ... instead of incomplete thrid-party tutorials that have been put together by someone who actually read the Handbook and knows FreeBSD better than you.

Sometimes, you will discover that you need to start the installation over and over again, because you skipped an important step early on, and the only way to correct that mistake is to re-start the installation from the very beginning, come to the same early point, and make some different choices - like NOT skipping that step. That's OK, that's part of learning FreeBSD.
 
As Maturin said here, it is better to study the OS on real hardware. Moreover, we see that you are only at the very beginning of the journey. It makes sense, as it seems to me, to buy old hardware and assemble a test rig. You will have to study the entire handbook for a long time. Believe me, there is a lot of useful stuff there and even a year may not be enough to study everything. This is if you don’t mind spending money. And if your budget is tight, then my recommendation is to buy a second storage device (SSD, HDD, etc.) and install FreeBSD there. It’s a good thing - there is cheap old and used hardware in all countries. That’s how I live. It’s not hard for me to buy such things for pennies.
It’s just that now you are stuck on the primary configuration, tomorrow you will start studying ZFS, then jails, then virtualization, WM (Wayland, sway...). It would be very inconvenient for me to drag all this into a virtual machine under Windows.
Study! The forum is full of useful recommendations.
 
wow! thank you for your readiness to help!
here is my report:
-- done another installation of Freebsd VM (this time from dvd1.iso not disk1.iso);
-- pinging failed. Name does not resolve (machine network settings: attached to NAT, the host 's internet comes from wifi thru Android USB teathering);
which leaves fetching/installing pkg out of question
a try to login a user created at the installation time brings about "login incorrect"
 
USerID said:
As Maturin said here, it is better to study the OS on real hardware. Moreover, we see that you are only at the very beginning of the journey. It makes sense, as it seems to me, to buy old hardware and assemble a test rig. You will have to study the entire handbook for a long time. Believe me, there is a lot of useful stuff there and even a year may not be enough to study everything. This is if you don’t mind spending money. And if your budget is tight, then my recommendation is to buy a second storage device (SSD, HDD, etc.) and install FreeBSD there. It’s a good thing - there is cheap old and used hardware in all countries. That’s how I live. It’s not hard for me to buy such things for pennies.
It’s just that now you are stuck on the primary configuration, tomorrow you will start studying ZFS, then jails, then virtualization, WM (Wayland, sway...). It would be very inconvenient for me to drag all this into a virtual machine under Windows.
Study! The forum is full of useful recommendations.
Click to expand...
I'm ready to study it's only the question where from. and btw, dude, I never was under Microsoft since end of 1900's, Linux is my love
 
sehrguey-the-2nd said:
-- done another installation of Freebsd VM (this time from dvd1.iso not disk1.iso);
-- pinging failed. Name does not resolve (machine network settings: attached to NAT, the host 's internet comes from wifi thru Android USB teathering);
which leaves fetching/installing pkg out of question
Click to expand...
This sounds like a VirtualBox VM. ping is unsupported in NAT configuration. up/download traffic shouldn't be a problem in NAT. Check VMs /etc/resolv.conf if it is populated.

If it isn't, change the network adapter from NAT to "Attached to: Bridged Adapter", I believe the listed name is "ue0" (but I could be wrong, haven't worked with USB tethering a while). ping can send packages in bridged adapter configuration.

Or, leave to NAT, set the VM's name resolver manually:

/etc/resolvconf.conf
Code: 
resolvconf=NO

/etc/resolv.conf
Code: 
nameserver 1.1.1.1
nameserver 8.8.8.8
# up to 3 name server may be listed
 
sehrguey-the-2nd T-Daemon I use BridgedAdapter and i have no problems with internet. As a side not, i use ethernet and check cable connected but wireless shouldn't be a problem. FreeBSD will ask if you want to fetch pkg when you have internet working or you can install it from the dvd (but that doesn't fix your network problem).
 
sehrguey-the-2nd said:
Freebsd 14.2 successfully installed in virtualbox. hooray! now what?
Click to expand...
Congrats, now it's time to have some fun. Maybe install some software to help you get things done?

For example, I can't live without the Midnight Commander, easily installed by running this command: # pkg install mc. Note: don't type the # character, the only reason that's there is to indicate that this command should be run as the root user.

sehrguey-the-2nd said:
commands recommended by Handbook like "pkg" are answered with "Unknown command"
a try to add a user following online tutorials ended in errors.
Click to expand...
I can't help wonder how you installed this thing? You mentioned the ISO images, which is a good way to go, but then I don't quite understand the result. For example: the installer already provides options to add user accounts and the likes, did you use those options?

Did you go with default options or did you maybe customize the whole lot? Also... what exactly was the error, maybe try copy/paste it? Because this almost makes me think of a PATH gone wrong:

Code: 
peter@bsd:/home/peter $ which pkg
/usr/local/sbin/pkg
peter@bsd:/home/peter $ unset PATH
peter@bsd:/home/peter $ which pkg
peter@bsd:/home/peter $ pkg
/usr/local/bin/ksh: pkg: not found
peter@bsd:/home/peter $
See what I mean? First it could find pkg, then I removed the path and b00m, it was gone. Ignore the somewhat uncommon location btw, that's merely because my environment is highly customized and somewhat experimental.

USerID said:
As Maturin said here, it is better to study the OS on real hardware.
Click to expand...
Not sure I agree with that. There really isn't all that much different between 'real' hardware or a vm, fact of the matter is that real hardware also comes with plenty of real headaches. Especially if you want to use the OS along side your normal one.

A VM provides just too many advantages. For example... when things go wrong with the network then it's easy to get locked out of a box; back to the console. On hardware that would require physical access, but with a vm you can simply call up the console (or... you're already working on it).

I've seen too many people trying to make a picture of their console with an error message or "problem" on it, while they could be copy/pasting all that if they had used a vm.
 
astyle said:
Try running bsdconfig in that VM, and poke around. It should offer a way to add a regular user.

That reminds me - that really should have been done during the installation.

Don't skip steps, and follow official documentation like the User Handbook ... instead of incomplete thrid-party tutorials that have been put together by someone who actually read the Handbook and knows FreeBSD better than you.

Sometimes, you will discover that you need to start the installation over and over again, because you skipped an important step early on, and the only way to correct that mistake is to re-start the installation from the very beginning, come to the same early point, and make some different choices - like NOT skipping that step. That's OK, that's part of learning FreeBSD.
Click to expand...
thank you I tried to find and install oracle cli and utils but in vain, their links to the mentioned downloads bring to extension packs and and new releases only. which left me without a tool to poke around
 
johnjohn said:
sehrguey-the-2nd T-Daemon I use BridgedAdapter and i have no problems with internet. As a side not, i use ethernet and check cable connected but wireless shouldn't be a problem. FreeBSD will ask if you want to fetch pkg when you have internet working or you can install it from the dvd (but that doesn't fix your network problem).
Click to expand...
you are right the networking problem is of the urgent priority
 
ShelLuser said:
Also... what exactly was the error, maybe try copy/paste it? Because this almost makes me think of a PATH gone wrong:
Click to expand...
Code: 
Username    :  me
Password    : <blank>
Full Name   : me really
Uid         : 1001
Class       :
Groups      : me 
Home        ; /home/me
Shell       : /bin/sh
OK? (yes/no) [yes] : yes
pw: gr_tmp(): Read-only file system
adduser     : ERROR There was an error adding user (me)
root@:/ # ls /home
ls: /home: No such file or directory
cracauer@ said:
You should copy and paste what you did and the exact reply.
Click to expand...
cracauer@ said:
You should copy and paste what you did and the exact reply.
Click to expand...
firstly, I "must install VMware Tools in a virtual machine to use the copy and paste feature." which is impossible having no network
 
sehrguey-the-2nd said:
firstly, I "must install VMware Tools in a virtual machine to use the copy and paste feature." which is impossible having no network
Click to expand...

so are you running vmware or virtualbox?

what is the host system? I have virtualbox running FreeBSD on Windows 10. First, you need to configure the network in virtualbox (if you haven't already done so). If you were disconnected from the internet while installing FreeBSD, then you will need to configure the network in FreeBSD. I simply choose automatic configuration in /etc/rc.conf:

Code: 
 ifconfig_em0="DHCP"

I use ethernet / cable connected instead of wifi, so my interface is em0. I do not use VMWare, so i cannot advise you how to proceed using VMWare.
 
sehrguey-the-2nd said:
Code: 
Username    :  me
Password    : <blank>
Full Name   : me really
Uid         : 1001
Class       :
Groups      : me
Home        ; /home/me
Shell       : /bin/sh
OK? (yes/no) [yes] : yes
pw: gr_tmp(): Read-only file system
adduser     : ERROR There was an error adding user (me)
root@:/ # ls /home
ls: /home: No such file or directory


firstly, I "must install VMware Tools in a virtual machine to use the copy and paste feature." which is impossible having no network
Click to expand...
Just read your own output here!

Yes, you have to specify a password when running adduser! even if you're the only user on the system! Of course you're gonna have errors if you skip that... :rolleyes:😲

Oh, and since you have VirtualBox, keep things consistent, don't try to install irrelevant stuff like VMWare Tools unless you see official VirtualBox documentation thatf it even works... :rolleyes:😲
 
sehrguey-the-2nd said:
it is virtualbox 7 on Ubuntu 20. and I found /etc/rc.conf but don't know which editor to use, "nano" is not present
Click to expand...
Thank you for clarifying. Virtualbox does not make use of VMWare tools, so you will need to install the virualbox-ose-additions package, after you solve the networking problem of course.

I am not a fan of vi but it is worth learning if you plan to use FreeBSD daily. I prefer nano but it is GNU software and it is not included on the dvd. You can use vi or ee (SirDice told me about ee, which is similar to nano in certain aspects).

If you use vi, then place the cursor where you can begin typing a new line (one of the tildes ~). press i key on your keyboard to enter insert mode (i'm not a vi guy, but i believe that it means insert mode). Insert mode is edit mode, so you can now type. However, i have made a typing error before and i somehow managed to erase the line and kick myself out of insert mode whenever i tried to correct it (maybe one must use a delete character key instead of backspace). I recommend typing the line correctly so as not to create any problems using vi. After you type the text correctly, then press the colon character key on your keyboard : then type wq and press enter/return key to write the file, then quit vi.

So type i where you want to insert text , type line of text, then type :wq then press enter/return.

try not to get discouraged. FreeBSD is a fantastic system but it is not Windows or Linux. The forum has lots of helpful and knowledgeable members :)

One time i wanted to make a screen capture within Windows 10 but the FreeBSD vm still had the focus. I pressed the Print Screen on the keyboard and the shell switched to ttyv1. I didn't know that this key is a shortcut for alt+F1-9 keys. LOL. Sometimes mistakes lead to new discoveries. Noone is immune to mistakes but we can always learn from them.
 
You must log in or register to reply here.
Back
Top