Sponsored Content
The Lounge What is on Your Mind? Networks alternative to Internet Post 302403637 by Action on Saturday 13th of March 2010 01:29:33 PM
Old 03-13-2010
Quote:
Originally Posted by Neo
IMHO, there was nothing "good old things" about gopher, uucp, etc. I used gopher, wais, uucp ,etc and am glad they are relics of the past, personally speaking.

For me, there is nothing nostalgic about those old applications. The "Modern Junk" as you call it, is much, much better, in my opinion.


Yow, cool! What's about WAIS? Are there still any WAIS servers on the Net today? When speaking of what is junk and what's not, it is of course a personal position of each, for me better are old-style real things like ed, for example, email, uucp, you know, such things, and all of that in command line. If i had a real COM terminal, it would be great! The problem is that seems not to be any of them today any more. By the way, what do you think of z39.50? Is a pretty thing, huh?
 

7 More Discussions You Might Find Interesting

1. AIX

AIX versus Networks

HI folks, Actually i have a network engineer having 2 and 1/2 years of experience in cisco having CCNA certification also. Now my company offering me to move to AIX field. I am new to AIX and do not know more about that field. So i want a suggestion from you peoples, that I have to join AIX or... (5 Replies)
Discussion started by: rawatmohinder
5 Replies

2. Linux

SFTP an internet address from a system behind an internet proxy

I was wondering if it is possible to setup SFTP to go through the internet proxy while connecting to an internet location. Problem: Client system is behind internet proxy. SFTP to any internet location fails as there is no documented way to configure SFTP to connect to internet locations through... (4 Replies)
Discussion started by: toobrown1
4 Replies

3. Solaris

Multiple networks on same server

If I have 2 interfaces in a server on the same subnet/network does Solaris automatically choose to route packets destined for this network out the first interface. I.e if ce0 and ce1 were on same network ce0 would be chosen as it's first interface? (5 Replies)
Discussion started by: Actuator
5 Replies

4. IP Networking

solaris routing between two networks

ce0: flags=1100843<UP,BROADCAST,RUNNING,MULTICAST,ROUTER,IPv4> mtu 1500 index 2 inet 10.162.212.132 netmask ffffff00 broadcast 10.162.212.255 ether 0:14:4f:55:82:9 ce1: flags=1100843<UP,BROADCAST,RUNNING,MULTICAST,ROUTER,IPv4> mtu 1500 index 3 inet 10.231.11.232 netmask... (1 Reply)
Discussion started by: busyboy
1 Replies

5. Solaris

solaris routing between two networks

ce0: flags=1100843<UP,BROADCAST,RUNNING,MULTICAST,ROUTER,IPv4> mtu 1500 index 2 inet 10.162.212.132 netmask ffffff00 broadcast 10.162.212.255 ether 0:14:4f:55:82:9 ce1: flags=1100843<UP,BROADCAST,RUNNING,MULTICAST,ROUTER,IPv4> mtu 1500 index 3 inet 10.231.11.232 netmask... (3 Replies)
Discussion started by: busyboy
3 Replies

6. What is on Your Mind?

What Social Networks Do You Use Regularly?

What Online Social Networks Do You Use Regularly? I use Facebook and LinkedIn nearly everyday.... You? If your online social network is not listed, please do a "write in" vote.. Thanks! (39 Replies)
Discussion started by: Neo
39 Replies

7. AIX

Setting up NIM for different networks

Hi, I am struggling setting up a NIM master to serve hosts on a network that is not directly accessible through the "master"-s default interface. I now that I need to set up network definitions and maybe NIM routes, but got confused. The master has 2 interfaces: * en0 holding the address... (8 Replies)
Discussion started by: trifo75
8 Replies
SYSTEMD-NETWORKD.SERVICE(8)				     systemd-networkd.service				       SYSTEMD-NETWORKD.SERVICE(8)

NAME
systemd-networkd.service, systemd-networkd - Network manager SYNOPSIS
systemd-networkd.service /lib/systemd/systemd-networkd DESCRIPTION
systemd-networkd is a system service that manages networks. It detects and configures network devices as they appear, as well as creating virtual network devices. To configure low-level link settings independently of networks, see systemd.link(5). systemd-networkd will create network devices based on the configuration in systemd.netdev(5) files, respecting the [Match] sections in those files. systemd-networkd will manage network addresses and routes for any link for which it finds a .network file with an appropriate [Match] section, see systemd.network(5). For those links, it will flush existing network addresses and routes when bringing up the device. Any links not matched by one of the .network files will be ignored. It is also possible to explicitly tell systemd-networkd to ignore a link by using Unmanaged=yes option, see systemd.network(5). When systemd-networkd exits, it generally leaves existing network devices and configuration intact. This makes it possible to transition from the initrams and to restart the service without breaking connectivity. This also means that when configuration is updated and systemd-networkd is restarted, netdev interfaces for which configuration was removed will not be dropped, and may need to be cleaned up manually. CONFIGURATION FILES
The configuration files are read from the files located in the system network directory /lib/systemd/network, the volatile runtime network directory /run/systemd/network and the local administration network directory /etc/systemd/network. Networks are configured in .network files, see systemd.network(5), and virtual network devices are configured in .netdev files, see systemd.netdev(5). SEE ALSO
systemd(1), systemd.link(5), systemd.network(5), systemd.netdev(5), systemd-networkd-wait-online.service(8) systemd 237 SYSTEMD-NETWORKD.SERVICE(8)
All times are GMT -4. The time now is 07:18 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy