01-22-2003
i figured out how to gain rw access to my files, but even after replacing my RC.CONF file i am still having problems. Once I go into multiuser mode, it tells me:
=1: not found
does not existface lo0
anyone know why it would have problems finding my loopback interface? Thanks again.
8 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
ok well last night "something" caused by computer to "flip out"...i noticed that it seemed to be in dos but there was allot of info displaying on the screen real fast and after turning it off i was told there was no hard disk detected...
so after talking to tech support i got windows up and... (4 Replies)
Discussion started by: justchillin
4 Replies
2. UNIX for Dummies Questions & Answers
First of all, I'd like to preface this post by relaying that I have considerable experience with FreeBSD but I'm a Linux newb. I've been attempting to compile linux-2.6.29.3 from source and I'm having some problems and have a few newb questions...
a) First of all, my kernel won't boot, it fails... (0 Replies)
Discussion started by: urbanriot
0 Replies
3. Solaris
Help needed please! I see the following scsi errors during boot up. The server eventually boots up successfully. Please let me now how to fix these errors:
Executing last command: boot
Boot device: disk File and args:
SunOS Release 5.8 Version Generic_117350-62 64-bit
Copyright 1983-2003 Sun... (4 Replies)
Discussion started by: pingmeback
4 Replies
4. AIX
IBM P Series #7026
Error Codes
#E47E212E - init
#1BA70F4E - SRC
#BA431EB7 - SRC
#C69F5C9B- SYSPROC
#369DO49B - SYSPFS
This happens on reboot the core dump fills up the root file system so I don't think it completes the dump. I can't read the core file with dbx.
Thanks (6 Replies)
Discussion started by: tholmes
6 Replies
5. Solaris
Hi all.
I am seeing in one of our less-used servers that it crashed and now won't restart. I get the message 'continue with normal startup or boot into maintenance mode'.
I go into maintenance and run fsck on /usr0 (mentioned in error at restart) it then reboots but goes right back to... (3 Replies)
Discussion started by: jamie_collins
3 Replies
6. Shell Programming and Scripting
Hello...
I am trying to loop through my hosts file that contains 100+ servers to check or update the nameservers on them...
My while loop is breaking after the first server responds...
#!/bin/bash
while read line; do
a=( $(echo $line | tr " " "\n") )
if }" != "" ] && }" != "#" ] &&... (1 Reply)
Discussion started by: CompSCI
1 Replies
7. UNIX for Dummies Questions & Answers
I have the following chunk of code...
while
when I try to execute this script, it outputs an error "test: ] missing"
Is there a syntax error here? (9 Replies)
Discussion started by: itech4814
9 Replies
8. Red Hat
I am trying to understand what are the differences of boot messages verbosity levels for the kernel field in grub.conf
From my research, there appear to be three levels:
quiet
verbose
debug
I have also found documents that specify removing quiet from the kernel field. If this is done, is... (1 Reply)
Discussion started by: thaebich
1 Replies
LO(4) BSD Kernel Interfaces Manual LO(4)
NAME
lo -- software loopback network interface
SYNOPSIS
device loop
DESCRIPTION
The loop interface is a software loopback mechanism which may be used for performance analysis, software testing, and/or local communication.
As with other network interfaces, the loopback interface must have network addresses assigned for each address family with which it is to be
used. These addresses may be set or changed with the SIOCSIFADDR ioctl(2). The loopback interface should be the last interface configured,
as protocols may use the order of configuration as an indication of priority. The loopback should never be configured first unless no hard-
ware interfaces exist.
If the transmit checksum offload capability flag is enabled on a loopback interface, checksums will not be generated by IP, UDP, or TCP for
packets sent on the interface.
If the receive checksum offload capability flag is enabled on a loopback interface, checksums will not be validated by IP, UDP, or TCP for
packets received on the interface.
By default, both receive and transmit checksum flags will be enabled, in order to avoid the overhead of checksumming for local communication
where data corruption is unlikely. If transmit checksum generation is disabled, then validation should also be disabled in order to avoid
packets being dropped due to invalid checksums.
DIAGNOSTICS
lo%d: can't handle af%d. The interface was handed a message with addresses formatted in an unsuitable address family; the packet was
dropped.
SEE ALSO
inet(4), intro(4)
HISTORY
The lo device appeared in 4.2BSD. The current checksum generation and validation avoidance policy appeared in FreeBSD 8.0.
BSD March 15, 2009 BSD