First Last Prev Next    No search results available      Search page      Enter new bug
Bug#: 52276
Alias:
Product:
Component:
Status: RESOLVED
Resolution: FIXED
Assigned To: Gentoo Games <games@gentoo.org>
Hardware:
OS:
Version:
Priority:
Severity:
Reporter: Tyler Montbriand <tsm@accesscomm.ca>
Add CC:
CC:
Remove selected CCs
URL:
Summary:
Status Whiteboard:
Keywords:

Filename Description Type Creator Created Size Actions
Create a New Attachment (proposed patch, testcase, etc.) View All

Bug 52276 depends on: Show dependency tree
Bug 52276 blocks:
Votes: 0    Show votes for this bug    Vote for this bug

Additional Comments: (this is where you put emerge --info)


Not eligible to see or edit group visibility for this bug.






View Bug Activity   |   Format For Printing   |   XML   |   Clone This Bug


Description:   Opened: 2004-05-28 09:53 0000
dosbox-0.58, 0.60, and 0.61 all failed to mount directories as they should.  In
the dosbox window, "mount c /home/monttyle/Documents/dosbox" is responded to with
stony silence.  "mount -cd" is also responded to with stony silence.  In fact,
even "mount eatflamingdeath" is responded to with stony silence - the command
doesn't appear to do a thing.

I tried emerging dosbox-cvs - which works yet is masked under amd64 - and works.

  mount c /home/monttyle/Documents/dosbox
gives
  Drive C is mounted as local directory /home/monttyle/Documents/dosbox

  mount -cd
gives
  CDROMS found:  1
   0. /dev/cdrom"

  mount eatflamingdeath
gives
  Usage MOUNT Drive-Letter Local-Directory
  So a MOUNT c c:\windows mounts windows directory as the C: drive in dosbox

Reproducible: Always
Steps to Reproduce:
1. emerge dosbox-0.60
2. run
3. mount c /etc

Actual Results:  
mount responds to any and all commands with stony silence

Expected Results:  
It should have mounted a directory, or at least printed an error message

------- Comment #1 From Mr. Bones. 2004-05-28 15:10:03 0000 -------
amd64 guys, please take a look.  works fine for x86.

------- Comment #2 From Mr. Bones. 2004-06-21 22:06:00 0000 -------
It seems that dosbox isn't stable enough for amd64 quite yet so I've moved it
back to ~amd64.  Check the ChangeLog for details.  I'll mark these fixed for now.

First Last Prev Next    No search results available      Search page      Enter new bug