Configuring NIC device in Solaris 9 SPARC OS [QEMU]
I have Xubuntu 18.04 installed on my PC. I have created a 10G .img image file created by QEMU-IMG. I have installed inside of it Solaris 9 SPARC edition [GUI interface]. If I try and mount the image file as a loop device (using sudo losetup /dev/loop0 /path-to-img-file) I can only mount it as read only.
When I type in dmesg into terminal I am informed that the UFS kernel has been compiled in read-only support.
I investigated into this and found that the Linux UFS kernel is compiled to be as such (read only for UFS) as there has been data loss issues when mounting UFS file systems as read,write in the past. Therefore I need to setup an internet connection within Solaris 9 through the QEMU VM I know about editing the following configuration files ...
But what I am struggling to do is locate and/or install the driver for my NIC card on my mounted Solaris 9 OS and activate it (ifconfig XXPUT-NIC-DEV-HEREXXX up ) If I can do that then I can get down to business on the conf files above.
Can anyone help? I shall gladly await your response
regards
Hi.
I have HP-9000 Server running HP-UX 10.20. rECENTLY OUR network upgraded to 100mb/sec and I want to do same on the server. So, I add the second Network card (100MB). But the problem is, I can't find a way of configuring this card. How am i going to tell the server to use this 100mb card... (1 Reply)
Hi ......
I'm trying to configure my Solaris servers with only one NIC card to have 2 IP addresses as well as 2 different default gateways.
( NOT to be confused with multi-pathing - with 2 physical IPs & 1 virtual ip)
Thanks,
Remi (1 Reply)
Old DG box Aviion PentiumPro running R4.20Mu06 being used to try to recreate Ingres db from backup tapes so machine has not been operational before and some of original files in /etc may have ben overwritten
Unable to get NIC working
Any pointers on how to go about configuring NIC :rolleyes: (0 Replies)
I couldn't install my nic in solaris 10. I compiled and added
the driver but failed to attach the driver and ifconfig output
shows only loopback dev. Please see the following output and tell
me whether my nic has been detected and why the driver failed to
attach?
My nic is detected in linux... (0 Replies)
Dear All
I want tune my NIC's rps, rfs and xps value.
In my system I have two NIC (eth0, eth1) and I have a bond0 ( eth0, eth1).
Here is the question? Which device should I modify ?
eth0 and eth1? or just modify bond0 or modify all device (eth0, eth1, bond0)
Any advice is welcome.... (0 Replies)
I have a Oracle SPARC server with Solaris SPARC 10 OS installed
I have a domestic router/modem box from my ISP in my house. I have a wifi extender in my room which has a RJ45 female socket for ethernet connection. The Wifi extender is configured properly to act as a bridge for machines to... (5 Replies)
Discussion started by: alphatron150
5 Replies
LEARN ABOUT CENTOS
losetup
LOSETUP(8) System Administration LOSETUP(8)NAME
losetup - set up and control loop devices
SYNOPSIS
Get info:
losetup loopdev
losetup -l [-a]
losetup -j file [-o offset]
Delete loop:
losetup -d loopdev...
Delete all used loop devices:
losetup -D
Print name of first unused loop device:
losetup -f
Setup loop device:
losetup [-o offset] [--sizelimit size]
[-p pfd] [-rP] {-f[--show]|loopdev} file
Resize loop device:
losetup -c loopdev
DESCRIPTION
losetup is used to associate loop devices with regular files or block devices, to detach loop devices and to query the status of a loop
device. If only the loopdev argument is given, the status of the corresponding loop device is shown.
Note that the old output format (e.g. losetup -a) with comma delimited strings is deprecated in favour of the --list output format (e.g.
losetup -a -l).
OPTIONS
+The size and offset arguments may be followed by the multiplicative +suffixes KiB=1024, MiB=1024*1024, and so on for GiB, TiB, PiB, EiB,
ZiB and YiB +(the "iB" is optional, e.g. "K" has the same meaning as "KiB") or the suffixes +KB=1000, MB=1000*1000, and so on for GB, TB,
PB, EB, ZB and YB.
-a, --all
show status of all loop devices. Note that not all information are accessible for non-root users. See also --list. The old output
format (as printed without --list) is deprecated.
-c, --set-capacity loopdev
force loop driver to reread size of the file associated with the specified loop device
-d, --detach loopdev...
detach the file or device associated with the specified loop device(s)
-D, --detach-all
detach all associated loop devices
-f, --find
find the first unused loop device. If a file argument is present, use this device. Otherwise, print its name
-h, --help
print help
-j, --associated file
show status of all loop devices associated with given file
-l, --list
if a loop device or the -a option is specified, print default columns for either the specified loop device or all loop devices,
default is to print info about all devices.
-o, --offset offset
the data start is moved offset bytes into the specified file or device
-O, --output columns
specify which columns are to be printed for the --list output
--sizelimit size
the data end is set to no more than size bytes after the data start
-P, --partscan
force kernel to scan partition table on newly created loop device
-r, --read-only
setup read-only loop device
--show print device name if the -f option and a file argument are present.
-v, --verbose
verbose mode
ENCRYPTION
Cryptoloop is no longer supported in favor of dm-crypt. For more details see cryptsetup(8).
RETURN VALUE
losetup returns 0 on success, nonzero on failure. When losetup displays the status of a loop device, it returns 1 if the device is not con-
figured and 2 if an error occurred which prevented from determining the status of the device.
FILES
/dev/loop[0..N]
loop block devices
/dev/loop-cotrol
loop control device
EXAMPLE
The following commands can be used as an example of using the loop device.
# dd if=/dev/zero of=~/file.img bs=1MiB count=10
# losetup --find --show ~/file.img
/dev/loop0
# mkfs -t ext2 /dev/loop0
# mount /dev/loop0 /mnt
...
# umount /dev/loop0
# losetup --detach /dev/loop0
AUTHORS
Karel Zak <kzak@redhat.com>, based on original version from Theodore Ts'o <tytso@athena.mit.edu>
AVAILABILITY
The losetup command is part of the util-linux package and is available from ftp://ftp.kernel.org/pub/linux/utils/util-linux/.
util-linux July 2003 LOSETUP(8)