>
>H.J. Thomassen scripsit:
>
>> In August 2008 a thread was started by 'zmkm' where he asked (among
>> other things) for a "unix assembler manual" by DMR. I could post a
>> scan on line if somebody is still interested. It's a 12 page text and
>> the CPU involved is -of course- DEC PDP-11.
>
>Go for it, I'd say. Many will be interested, and no one is likely to sue.
At http://wwwlehre.ba-stuttgart.de/~helbig/os/v6/doc/index.html
you'll find the V6 assembler manual.
Enjoy,
Wolfgang
Hi all,
I just discovered this list & decided to join.
In August 2008 a thread was started by 'zmkm' where
he asked (among other things) for a "unix assembler
manual" by DMR. I could post a scan on line if
somebody is still interested. It's a 12 page text
and the CPU involved is -of course- DEC PDP-11.
Plse let me know.
Regards
--
Hendrik-Jan Thomassen <hjt(a)ATComputing.nl>
Wow I'm surprised a few hours googleing about and I got it running....
I found this 'idle' emulator ("Incomplete Draft of a Lisa Emulator"
http://sourceforge.net/projects/idle-lisa-emu ), which can infact run
Xenix! It also says it can run the uniplus SYSV (so says the
readme)..
Searching around I found the following site:
http://unixsadm.blogspot.com/2007/12/xenix-blast-from-past-looking-back-at.…
which has Xenix 3.0 disk images in the DART format... which as luck
would have it idle cannot mount. However I found another lisa
emulator, lisaem ( http://www.sunder.net/ ) which has a tool to
convert the disks from DART to DC42 (disk copy 4.2).
So it was a simple matter of converting the disks
lisafsh-tool.exe "Xenix OS Boot Floppy"
quit
... etc etc...
Then firing up idle, setting the CPU to max speed, and booting up...
whenver I was going to answer a question I toggled it back to 5Mhz..
otherwise it would take FOREVER to boot... lol like the 'good old
days'.
Once the boot floppy had formatted the 5mb hard disk image, and
transfered on reboot I had to tell the bootloader to boot from the
profile disk..
pf(0,0)xenix
And away it went. After installing the OS & the C compiler I'm left
with 23 blocks free!.. which I guess for a 5mb disk, is pretty cool..
Anyways there are assorted Xenix PDF's which can be found here
http://www.tenox.tc/docs/
Namely these two for Apple Lisa Xenix..
http://www.tenox.tc/docs/apple_lisa_xenix_programmers_guide.pdfhttp://www.tenox.tc/docs/apple_lisa_xenix_programmers_reference.pdf
It's amazing that lisa emulators were sort of capable of running Lisa
Office System, now they can run the old unix stuff... it's still
impressive.
Hello from Italy!
I'm interested in Xenix copyright. Do someone of you know who exactly
owns Xenix? According to Wikipedia, Microsoft gave everything to SCO,
but did they gave also the copyright for the non-x86 versions?
I'm asking this because I'm interested in "saving" Xenix from fading
into the digital night. If everything belongs to SCO, then maybe an
"binary only, non-commercial hobbyst license" could *eventually* be
released, at least for older or non-x86 products
Best regards,
Lorenzo
PS: First mailing list post ever. I'm definitely a newbie, here :)
Yeah that's the extent of it. trust me I was shocked when I tried to
dd a Xenix install, and Qemu booted it right up. But without a C
compiler it's useless. I should add that the TCP/IP supported like 3
NIC's... so even *if* you could find it..... it'd be limited. You can
get the disk to work though.... But not under Qemu, Virtual PC and
VMWare can use it.
The 'issue' is that simply Xenix's method of detecting disk density
doesn't work under any emulator because while it's trying the wrong
thing it will 'work' when it shouldnt...
if you are trying to load a 3 1/5" high density disk, the device is
2/60
Low density is
2/36
so change the device for fd0 to be either.... or even symlink it.
For what it's worth, running it under Virtual PC is fast, however the
console is kind of screwed up.. Xenix uses a nonstandard screen mode
(well for virtual pc's bios that is).
I used to have Microsoft Word for Xenix... in the box and everything.
I'll be dammed if I know where it is. I wish I had managed to keep the
license cards.... :|
And no, outside of a picture from an ad talking about the PDP-11
version of Xenix, and one anicdote in USENET saying that any issues
they had were traced back to Microsoft additions to the system...
there is no trace of it.
But then who knows, maybe someone will post back with something.
On Tue, Feb 10, 2009 at 1:08 PM, Lorenzo Gatti <gattilorenz(a)gmail.com> wrote:
> I know they won't release anything, but asking is never a bad thing.
> I saw the lisa and tandy versions, thank you. What I'm searching is
> the PDP-11 one,
> and I doubt I will find it easily. Do any of you have it?
> BTW, even the x86 version is not working well in emulators.
> Well, at least you cannot install it, but if you have a dd image of a
> working xenix system, this will boot fine in bochs/qemu.
> But you won't be able to use disks (at least images, never tried the
> real disks) to install new software, lol.
> So it's basically a closed system, if you don't connect it to another
> xenix (virtual?) machine via virtual serial port.
>
> 2009/2/10 Jason Stevens <neozeed(a)gmail.com>:
>> I doubt SCO/Microsoft will release anything.. but then you never know.
>> Do you have Xenix for the PDP-11? I've seen the lisa & Tandy 68000
>> floating around, but both used some custom MMU so that cut out
>> emulators... lol I haven't even bothered asking for source, as I
>> figured these v6/v7 things are basically lost in the mists of time...
>> but then there is v6/v7 for the Pdp-11/Interdata 32b & the recent port
>> of v7 to the i386 http://nordier.com/v7x86/index.html
>
Trying to understand some users and groups that continue to exist on BSD
systems.
Can someone please point me to references or share examples of historical
and/or recent uses of the following users and groups?
Also any clarifications of my understandings below would be appreciated.
(My context is BSD. I know some of these may have different old and
existing uses on other systems.)
daemon user
I see /var/msgs on NetBSD is owned by daemon. msgs will abort if doing -c
(cleanup) if not root or daemon user. I guess that is historic. I don't
see any daemon user usage.
operator user
I understand that historically, the operator user had logins
for those doing disk backups (via its login group privileges).
I understand the operator group, just wondering if any recent uses of
operator user.
bin user
Don't know what uses it.
daemon group
I understand that historically, these are for processes needing less
privileges than the wheel group. Also historically, programs using
/var/spool directories were setgid daemon. Anything common other than
LPD/LPR still use the daemon group?
sys group
I understand that historically, the sys group was used for access to the
kernel (/sys?) sources. (I don't know if that was just read or was for
writing too.) Anyone still use "sys" group? (I guess this is like wsrc
which sometimes I manually setup and use for writing to src directories.)
bin group
I understand that historically, used as the group for system binaries, but
commonly the wheel group is used instead. Some third-party software, like
OpenOffice.org, install files owned by the bin group.
staff group
How would this differ from wheel or operators?
Any recent systems actually have default use of this?
guest group
Any recent systems actually have default use of this?
nobody group versus nogroup group
What is the significance of having both of these groups?
Thanks!
My knowledge comes from my early days at Sun in 84-85 as a rock-n-roll roadie
turned into a UNIX sysadmin. It was passed to me as I was learning how to
take care of trade show Sun Workstations. So take it with a grain of salt.
> daemon user
daemon was for daemon processes that ran in the background but did not want to
run as root. I believe it was used by inetd when it spawned a process but an
not sure. It was also used by sendmail when it gave up its SUID root privileges.
> operator user
operator was a normal user that had privilege to read the raw file systems
through group membership. Sysadmins who did backups would also be a member of
this group. The group I recall in the early days was "kmem" although now
there is a separate group "disk".
> bin user
A user to go with group bin. Typically would be the "proper" owner of all the
binaries and libraries on a system. It has lingered on for far to long
because, IMHO, the vendors had no clue as to why everything was owned by bin
and just kept it that way since "thats the way it's always been".
> bin group
I was told that group bin came from UCB to allow semi-trusted staff to replace
binaries in the file system without giving them the root password.
> staff group
My recollection is that staff was for group read/write permissions for home
directories, separate from group wheel which granted extra privileges
> nobody group versus nogroup group
The nobody group was a group to go with the nobody user introduced with NFS.
nogroup may have been someone's attempt to make the name more obvious, or it
may have been for non-privileged account. But the second case weakens the
protection of a non-privileged account
I was poking around an HP UX system at work today, and noticed a
command I've never noticed before ... /usr/bin/bs.
I'm sure it's been there for a long time, even though I've been an
HPUX admin for more than a decade, sometimes I'm just blind ... but
anyway ....
I tried to search on google ... it looks like only HPUX, AIX, and
Maybe AU/X has it. Seems to be some kind of pseudo BASIC like
interpreter.
Anyone ever use it for anything? Has anyone even noticed it before?
I'll have to boot my Crimson to see if IRIX has it.
- Derrik
Derrik Walker v2.0, RHCE
lorddoomicus(a)mac.com
http://www.doomd.net
"There's nothing nice about Steve Jobs and there's nothing evil about
Bill Gates."
-- Chuck Peddle, MOS 6502 Chip Designer
A note to all 2.11bsd users:
Over the past 2 years several bug fixes for 2.11BSD accumulated, and over
xmas break I finally found the time to communicate them to Steven Schultz.
Steven was so kind to package them into two new patch files
446 issued December 27, 2008
447 issued December 31, 2008
Together, the patches address the following points
- ulrem.s: the unsigned long modulo operator (%) was broken in libkern
- umount: returned inverted exit codes (1 for success, 0 for failure)
- tar: core dumped when a whole /usr tree was archived
- tcsh: the time buildin function printed some erroneous or zero statistics
- ps: core dumped when '-t' option was used with no further argument
- apropos: core dumped when 2 or more arguments were given
- vmstat: wrong normalization for some fields
- several issues around the rk disk driver
- no rk root attach function
- no rk BOOTDEV support
- incorrect UCB_METER code (vmstat/iostat never showed any rk activity)
- autoconfig left the RK11 controller in an error state
- pstat: added additional options to access more kernel data structures
- new -c option, dumping the coremap
- new -m option, dumping the ub_map (UNIBUS map)
- new -b option, dumping the buffer pool table
- change -s output, gives now full table dump
- adapt the info's displayed by -T
- some documentation corrections (vmstat, pstat, tcsh)
Note: In case you wonder, as I did, why 211BSD survived 20 years with a
broken unsigned long % operator:
- only the non-FPP libkern implementation was affected
- the kernel simply doesn't have any unsigned long modulo's :)
- apparently only standalone mkfs after patch 434 was compromised
For the full story of all the above consult the header of the patch files.
The patch files are available from moe.2bsd.com and ftp.wx.gd-ais.com.
Note, that Steven changed the packaging some time ago, the patches are
now packed in bzip'ed tarballs in groups of ten patches. So you'll have
to look into
ftp://moe.2bsd.com/pub/2.11BSD/440-447.tar.bz2ftp://ftp.wx.gd-ais.com/pub/2.11BSD/440-447.tar.bz2
With best regards,
Walter Mueller