09-05-2019
Can you show us the output of any good df command ( df -m, df -k etc...)?
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Hi...
question is this:
How do I mount an LVD hotswap scsi drive in bay #2 on a netra using the mount command? volmgt doesn't seem to mount it and/or I don't know how to view the drives data if it's formatted which it may not be. This drive is not new out of the box so I'm not sure.
... (4 Replies)
Discussion started by: soulshaker
4 Replies
2. UNIX for Dummies Questions & Answers
I have Pentium 4 CPU with 3 GHZ
500MB of RAM w/ 120 GB of HDD space. I am trying to install Sun Solaris 9 (x86).
I saw somewhere to on-line to get Device Configuration Assistant, but I am not sure where or if you guys have any documentations on this issue.
This is the error I am getting:
... (1 Reply)
Discussion started by: vtsao
1 Replies
3. UNIX for Advanced & Expert Users
I umount one filesystem like this:
# umount -F /export/home1
Then I tried to mount it back as:
# mount /dev/dsk/c1t0d0s6 /export/home1
mount: I/O error
mount: cannot mount /dev/dsk/c1t0d0s6
partition /dev/dsk/c1t0d0s6 and directory /export/home1 all exist in the system. Why can I not... (5 Replies)
Discussion started by: duke0001
5 Replies
4. Linux
Hello,
I am trying to mount an external USB drive connected to a SnapServer 410 ( a network file server running a linux OS called Guardian OS).
THanks to some articles on the the web, I found that I needed to use the following command:
> mount -t vfat /dev/sde /mnt/usbext
... (7 Replies)
Discussion started by: drmoque
7 Replies
5. AIX
hi when i am trying to mount this newly created LV i get following error
/#mount /bancs_cards
Replaying log for /dev/lvbancscards.
mount: 0506-324 Cannot mount /dev/lvbancscards on /bancs_cards: The media is not formatted or the format is not correct.
/#lslv lvbancscards
LOGICAL VOLUME: ... (3 Replies)
Discussion started by: zedex
3 Replies
6. SuSE
hi all,
I been trying to use mount command to unzip iso file. here is the command im using
mount -t iso9660 -o loop file.iso /mnt/cdrom
then i get below error..
mount: wrong fs type, bad option, bad superblock on /dev/loop1,
missing codepage or other error
In some cases... (1 Reply)
Discussion started by: s_linux
1 Replies
7. UNIX for Advanced & Expert Users
I am having trouble mounting with cifs, but mounting the exact same command with smbfs works fine. The share is on another samba server and is set to full public guest access. # mount -t cifs //servername/sharename /mnt/temp -o password=""
mount error 13 = Permission denied Refer to the... (3 Replies)
Discussion started by: humbletech99
3 Replies
8. Red Hat
I dualboot Ubuntu and Fedora in one hard drive. Below are the scenario.
First, installed Ubuntu 10.4 on the entire disk (40GiB of size).
Then, shrink the Ubuntu installation to equal size to free up space for fedora.
Second, installed Fedora 13 using the option "Use free space on selected... (2 Replies)
Discussion started by: etcpasswd
2 Replies
9. Windows & DOS: Issues & Discussions
I am trying to set a share between windows and an AIX server. I was able to do this to a windows 2008 server. I am now trying to get this to worked on a windows 7 enterprise pc. below is what i get. I have turned off the firewall wall in windows the user is an admin in the pc. same account works... (6 Replies)
Discussion started by: fierfek
6 Replies
10. UNIX for Beginners Questions & Answers
hi
i have an android phone which i think is bricked, so wanted to see what the actual issue is, I flashed it with TWRP recovery image and launched terminal i, was able understand that mount is not happening, it says invalid argument and no such file or directory. Below is what i get while... (32 Replies)
Discussion started by: nanz143
32 Replies
LEARN ABOUT DEBIAN
git-merge-base
GIT-MERGE-BASE(1) Git Manual GIT-MERGE-BASE(1)
NAME
git-merge-base - Find as good common ancestors as possible for a merge
SYNOPSIS
git merge-base [-a|--all] <commit> <commit>...
git merge-base [-a|--all] --octopus <commit>...
git merge-base --independent <commit>...
DESCRIPTION
git merge-base finds best common ancestor(s) between two commits to use in a three-way merge. One common ancestor is better than another
common ancestor if the latter is an ancestor of the former. A common ancestor that does not have any better common ancestor is a best
common ancestor, i.e. a merge base. Note that there can be more than one merge base for a pair of commits.
OPERATION MODE
As the most common special case, specifying only two commits on the command line means computing the merge base between the given two
commits.
More generally, among the two commits to compute the merge base from, one is specified by the first commit argument on the command line;
the other commit is a (possibly hypothetical) commit that is a merge across all the remaining commits on the command line.
As a consequence, the merge base is not necessarily contained in each of the commit arguments if more than two commits are specified. This
is different from git-show-branch(1) when used with the --merge-base option.
--octopus
Compute the best common ancestors of all supplied commits, in preparation for an n-way merge. This mimics the behavior of git
show-branch --merge-base.
--independent
Instead of printing merge bases, print a minimal subset of the supplied commits with the same ancestors. In other words, among the
commits given, list those which cannot be reached from any other. This mimics the behavior of git show-branch --independent.
OPTIONS
-a, --all
Output all merge bases for the commits, instead of just one.
DISCUSSION
Given two commits A and B, git merge-base A B will output a commit which is reachable from both A and B through the parent relationship.
For example, with this topology:
o---o---o---B
/
---o---1---o---o---o---A
the merge base between A and B is 1.
Given three commits A, B and C, git merge-base A B C will compute the merge base between A and a hypothetical commit M, which is a merge
between B and C. For example, with this topology:
o---o---o---o---C
/
/ o---o---o---B
/ /
---2---1---o---o---o---A
the result of git merge-base A B C is 1. This is because the equivalent topology with a merge commit M between B and C is:
o---o---o---o---o
/
/ o---o---o---o---M
/ /
---2---1---o---o---o---A
and the result of git merge-base A M is 1. Commit 2 is also a common ancestor between A and M, but 1 is a better common ancestor, because 2
is an ancestor of 1. Hence, 2 is not a merge base.
The result of git merge-base --octopus A B C is 2, because 2 is the best common ancestor of all commits.
When the history involves criss-cross merges, there can be more than one best common ancestor for two commits. For example, with this
topology:
---1---o---A
/
X
/
---2---o---o---B
both 1 and 2 are merge-bases of A and B. Neither one is better than the other (both are best merge bases). When the --all option is not
given, it is unspecified which best one is output.
SEE ALSO
git-rev-list(1), git-show-branch(1), git-merge(1)
GIT
Part of the git(1) suite
Git 1.7.10.4 11/24/2012 GIT-MERGE-BASE(1)