Techwarelabs Community - small size os

Techwarelabs Community (https://www.techwarelabs.com/community/index.php)

- Operating Systems (https://www.techwarelabs.com/community/forumdisplay.php?f=17)

- - small size os (https://www.techwarelabs.com/community/showthread.php?t=2266)

no kidding

too time consuming

not my way of working....

yes, im a lazyboy

this guy I know told me about this firewall OS. He said it didn't require a hard drive. you could fit it on a floppy and it was configurable via web interface. Now to remember where it was

do you guys read the entire thing? yeesh
this is what i like:

http://people.freebsd.org/~picobsd/picobsd.html

but heres floppyfw:

http://www.zelow.no/floppyfw/

also if you would read what it actually SAYS:

Quote:

To display the configuration for the network interfaces on your system, enter the folowing command:

% ifconfig

ifconfig being the command, and the display for the config is all the crap below.... :shake:

Quote:

dc0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
inet 192.168.1.3 netmask 0xffffff00 broadcast 192.168.1.255
ether 00:a0:cc:da:da:da
media: Ethernet autoselect (100baseTX <full-duplex>)
status: active
dc1: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
inet 10.0.0.1 netmask 0xffffff00 broadcast 10.0.0.255
ether 00:a0:cc:da:da:db
media: Ethernet 10baseT/UTP
status: no carrier
lp0: flags=8810<POINTOPOINT,SIMPLEX,MULTICAST> mtu 1500
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 16384
inet 127.0.0.1 netmask 0xff000000
tun0: flags=8010<POINTOPOINT,MULTICAST> mtu 1500

stupid handbook...

it just says to type in that whole thing
located in "6.6.2 Configuring the Network Card"
on this page
http://www.freebsd.org/doc/en_US.ISO...ook/x6696.html

here is an exact cut and paste quote

Quote:

Once the right driver is loaded for the network card, the card needs to be configured. As with many other things, the network card may have been configured at installation time by sysinstall.

To display the configuration for the network interfaces on your system, enter the folowing command:

% ifconfig
dc0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
inet 192.168.1.3 netmask 0xffffff00 broadcast 192.168.1.255
ether 00:a0:cc:da:da:da
media: Ethernet autoselect (100baseTX <full-duplex>)
status: active
dc1: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
inet 10.0.0.1 netmask 0xffffff00 broadcast 10.0.0.255
ether 00:a0:cc:da:da:db
media: Ethernet 10baseT/UTP
status: no carrier
lp0: flags=8810<POINTOPOINT,SIMPLEX,MULTICAST> mtu 1500
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 16384
inet 127.0.0.1 netmask 0xff000000
tun0: flags=8010<POINTOPOINT,MULTICAST> mtu 1500

Note: Old versions of FreeBSD may require the -a option following ifconfig(8), for more details about the correct syntax of ifconfig(8), please refer to the manual page. Note also that entries concerning IPv6 (inet6 etc.) were omitted in this example.

and if you read about 15 lines down...

Quote:

To configure your card, you need root privileges. The network card configuration can be done from the command line with ifconfig(8) but you would have to do it after each reboot of the system. The file /etc/rc.conf is where to add the network card's configuration.

Open /etc/rc.conf in your favorite editor. You need to add a line for each network card present on the system, for example in our case, we added these lines:

ifconfig_dc0="inet 192.168.1.3 netmask 255.255.255.0"
ifconfig_dc1="inet 10.0.0.1 netmask 255.255.255.0 media 10baseT/UTP"

see?

% is the shell prompt... all that other stuff is not the command..when you just type "ifconfig" that status is what it displays... if you notice the part of the command being typed is bolded..

let me show you an example... ( on that same link you gave me about a page down )

Quote:

% ping -c5 192.168.1.3
PING 192.168.1.3 (192.168.1.3): 56 data bytes
64 bytes from 192.168.1.3: icmp_seq=0 ttl=64 time=0.082 ms
64 bytes from 192.168.1.3: icmp_seq=1 ttl=64 time=0.074 ms
64 bytes from 192.168.1.3: icmp_seq=2 ttl=64 time=0.076 ms
64 bytes from 192.168.1.3: icmp_seq=3 ttl=64 time=0.108 ms
64 bytes from 192.168.1.3: icmp_seq=4 ttl=64 time=0.076 ms

you don't type out all that...... only those on the line of the shell prompt (i.e. "%")

i see i see

i have a whole lot to learn...

hey, what does -c5 mean after ping command
does it mean ping using 5 packets?

tru, and also to find out what all the switches (i.e. -c5) you can just read the man files:

"man ping"

it tells you more then u every wanna know for the command

most every program has a man file to teach ya what u need to know.

once you know the syntax tho its pretty simple ( i have a lot to learn too i'm a novice to normal user..i can get around and install a couple things )

Getting a little OT, but I think if I had a *third* computer, I'd consider making it a Linux/BSD box, and configuring like, *one* thing per day, until it was up and running in like, a month, heh. I'm not sure what I'd do with it though...but the experience would be very useful, IMO.

I would go with floppyfw

all I had to do was
-building the machine with two nics and floppy
-make the floppy disc
-put username and pass on the floppy disc (in config)
-start using it.