Date: Sat, 29 Dec 2018 15:05:56 +0100 From: Polytropon <freebsd@edvax.de> To: Jonathan Engwall <engwalljonathanthereal@gmail.com> Cc: freebsd-questions@freebsd.org Subject: Re: Hello(trouble with magic number) Message-ID: <20181229150556.dcddc29a.freebsd@edvax.de> In-Reply-To: <CAP=T6ZOPOc-efMHFNFXseDtjmU=DeQWKcOHsvqRtJKwH_YHjTw@mail.gmail.com> References: <CAP=T6ZPz7JEKb9P1ReiZ%2B1GbwDQKkjAjQa=j=cvyBztF8s=Ohw@mail.gmail.com> <CAP=T6ZMxHUmCeb428D3Kh-MUVwU%2BHtVPFVCPh9y2=C=Ok2%2BtDg@mail.gmail.com> <CAP=T6ZNJzaJjxbxDpqzZ8d7CGJt1Wda3tRKQ_4YfGhwsk3dYVQ@mail.gmail.com> <CAP=T6ZO-%2B_VKH3VZccBUF1C21hg2f6foK5WKo-4J=o_0yrOqzA@mail.gmail.com> <CAP=T6ZN0GBb=Va4OFd4gGDrULsfxXEQZpFA6Lwbxz2Jw=TVXzg@mail.gmail.com> <CAP=T6ZNT7epbYGF1xo4QrzEJ1WFfXLP1K4wbqO%2BxR3eeSVpp6A@mail.gmail.com> <CAP=T6ZNNuVE4%2BM2DiBC_Uid9Mj64ZCVz=svEEQ_N1H16rHm91Q@mail.gmail.com> <CAP=T6ZO3ZC8X2gzDUrad4rraaf7m62yVHw48ydp5AVDj2twmWQ@mail.gmail.com> <CAP=T6ZM8uRcTnzAi9an_Gr0NhAN=xZL%2BShPQvcfbsEYyd51Kqg@mail.gmail.com> <CAP=T6ZMX3qpQyiPQtRvgKZk-FO_K0Luarnk6t2u8EhoeTBFVow@mail.gmail.com> <CAP=T6ZNxEwyP8cwXuecxzC=w%2BJfKSk7HLQPPuWk_UOC1uhTM1g@mail.gmail.com> <20181228152218.596c04c1.freebsd@edvax.de> <CAP=T6ZMq-ry7V3z84AgAoG8QMSj9vPdodb8RS067SrtkG6shKQ@mail.gmail.com> <CAP=T6ZOPOc-efMHFNFXseDtjmU=DeQWKcOHsvqRtJKwH_YHjTw@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, 28 Dec 2018 18:07:52 -0800, Jonathan Engwall wrote: > I am trying to network centos, ubuntu, and dragonfly. But that's not exactly a FreeBSD-related question. ;-) > I have freebsd installed in a VM on virtualbox which is running on centOS. > Ubuntu also runs in virtualbox on my centos. Ah okay, not it makes more sense! If that's the case, you've probably been successfully using FreeBSD's VM-ready images. https://www.freebsd.org/where.html One of those: https://download.freebsd.org/ftp/releases/VM-IMAGES/12.0-RELEASE/amd64/Latest/ Which implies you already have FreeBSD up and running, is that correct? > The issue is really connectivity. I am having problems with telnet and ssh. > At present all my VMs are receiving the same ip address. How do you configure your addresses for the VMs? Are they set up static, or do you use a DHCP server that provides addresses for the VM instances? Check that in the VirtualBox configuration tool. If you do not have such a "local DHCP" service running, manually enter each instance and set its IP manually, for example 10.0.0.1 for CentOS ("upper level"), 10.0.0.2 for Ubuntu, 10.0.0.3 for DragonflyBSD, and finally 10.0.0.4 for FreeBSD. There is nothing wrong with such static configuration for virtual interfaces. At least that's a good point to start. Then you can add routing / NAT as needed, so the VM instances can access the Internet. Check the corresponding items in the VirtualBox configuration carefully. How does your host system (CentOS) connect to the Internet? That is probably the most important thing to fix. > Writing data to a usb to read with freebsd is only an exercise. FreeBSD can read lots of filesystem types, no matter if they are on USB, on CD or DVD, on SD cards, or on hard disks or SSDs. For data exchange among different systems, I usually suggest using tar (which is not a filesystem, but every OS has a tar program, and it will work with any medium). So, for example, if you'd want to create a "data exchange medium" to be used by Linux and FreeBSD, you could use Ext-2 as a filesystem, because both systems understand it well enough in a R/W manner. If you just want to transfer data into "one directions" (write here, read there), you can use tar. Yes, even with USB sticks. As you're running the systems as VM instances, make sure VirtualBox has USB support configured properly. > The problem > is mostly that I only have internet with my telephone right now. That's terrible, I can understand. > And about rufus: a very good utility for windows that writes bootable media. Interesting, you didn't mention "Windows" before. Sure, yes, "Windows" doesn't have a native tool to write image files to media. But as I said: You'll have to write the image 1:1, not "open" it and deal with its content. Please see my previous suggestion for using dd, because if you're running CentOS already, which is a Linux-type operating system, just use its dd program as mentioned in the handbook. Of course, you probably _could_ write the FreeBSD VM image to a USB stick and then create a VM instance from that, but surely that's _not_ what you're trying to do... ;-) -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ...
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20181229150556.dcddc29a.freebsd>