On Sat, Apr 28, 2001 at 02:47:20PM -0700, Tovar wrote:
> this isn't foolproof since MacOS does allow the user to move or rename
> the System\ Folder to whatever/wherever the hell they feel like it,
> though i have known very few who actually do that.
>
> Yes, indeed, beware of that.
this isn't foolproof since MacOS does allow the user to move or rename
the System\ Folder to whatever/wherever the hell they feel like it,
though i have known very few who actually do that.
Yes, indeed, beware of that. I've been naming my System Folder's with
its version number bac
Am Freitag, 27. April 2001 15:33 schrieb Samuel Rydh:
> >> Now I have it and I'm very impressed. Mol seems to be really fast and
> >> stable but what is bothering me is, that I have to start it as root. In
> >> an earlier version I could load the kernel modules in an init scrips and
> >> was then a
On Fri, Apr 27, 2001 at 03:33:03PM +0200, Samuel Rydh wrote:
>
> The startmol script has a --loadonly option which does the trick
> for you. Just add
>
> startmol --loadonly
>
> to the rc.local file.
we don't wear red hats here, there is no such file on a debian
system. please read /etc/
>> Now I have it and I'm very impressed. Mol seems to be really fast and stable
>> but what is bothering me is, that I have to start it as root. In an earlier
>> version I could load the kernel modules in an init scrips and was then able
> to start mol as regular user.
>
>I found that loading 'mols
On Fri, 27 Apr 2001, Fabian Jakobs wrote:
> Now I have it and I'm very impressed. Mol seems to be really fast and stable
> but what is bothering me is, that I have to start it as root. In an earlier
> version I could load the kernel modules in an init scrips and was then able
> to start mol as reg
Am Donnerstag, 26. April 2001 18:30 schrieb Philippe Lelédy:
> On Thu, 26 Apr 2001, Fabian Jakobs wrote:
> > Am Donnerstag, 26. April 2001 11:17 schrieb Jens Schmalzing:
> > > Hi,
> >
> > "Ihr Computer kann mit der Systemsoftware auf diesem Startvolume nicht
> > starten. Installieren Sie bitte die
> I had the same problem with trying to run Classic under MacOSX. I
> looked in http://discussions.info.apple.com and found a link to the
> following TechNote:
>
> http://til.info.apple.com/techinfo.nsf/artnum/n106277
>
> It's a problem if you have MacOSX installed on UFS. Maybe the same fix
> w
Hi,
Ethan Benson writes:
> in this case presuming you ask the user via debconf where thier
> macos partition is and you manage to copy the ROM over yourself, and
> be sure to remove it on package removal (--purge?) then /usr/lib/mol
> would be fine.
That's what I had in mind. As for the details
On Fri, Apr 27, 2001 at 11:27:43AM +0200, Geert Uytterhoeven wrote:
>
> Or make a Debian package of MacOS and put it in non-free? :-)
as funny as that sounds its actually possible (not legally), though
not very practical since it would be at least a 100MB package.
mol works quite fine running
On Fri, Apr 27, 2001 at 10:55:29AM +0200, Geert Uytterhoeven wrote:
>
> My first guess was /var, but since it is some sort of configuration setting, I
> think it belongs in /etc. The idea is that you can backup your configuration
> by
> backing up /etc. Hmmm... this stil doesn't backup yout list
On Fri, 27 Apr 2001, Ethan Benson wrote:
> there is also the issue of MacOS upgrades, if MacOS is upgraded and
> its ROM replaced it will crash the next time mol is run since it deals
> with mismatched ROMs very poory.
>
> ultimatly the user just has to know about this and how to deal with it
>
On Fri, Apr 27, 2001 at 10:54:07AM +0200, Jens Schmalzing wrote:
> Hi,
>
> Geert Uytterhoeven writes:
>
> > > IMO the default molrc should look for the rom in
> > > /usr/local/lib/mol/something
>
> > Is that Debian compliant? I'd expect the rom to be in /etc/mol/.
>
> If I understand the FHS Se
On Fri, 27 Apr 2001, Ethan Benson wrote:
> On Fri, Apr 27, 2001 at 10:32:24AM +0200, Geert Uytterhoeven wrote:
> > On Thu, 26 Apr 2001, Ethan Benson wrote:
> > > IMO the default molrc should look for the rom in
> > > /usr/local/lib/mol/something
> >
> > Is that Debian compliant? I'd expect the ro
Hi,
Geert Uytterhoeven writes:
> > IMO the default molrc should look for the rom in
> > /usr/local/lib/mol/something
> Is that Debian compliant? I'd expect the rom to be in /etc/mol/.
If I understand the FHS Section 4.4 correctly, putting the MacOS ROM
image under /usr/lib/mol is fine. After a
On Fri, Apr 27, 2001 at 10:32:24AM +0200, Geert Uytterhoeven wrote:
> On Thu, 26 Apr 2001, Ethan Benson wrote:
> > IMO the default molrc should look for the rom in
> > /usr/local/lib/mol/something
>
> Is that Debian compliant? I'd expect the rom to be in /etc/mol/.
i don't know what policy reall
On Thu, 26 Apr 2001, Ethan Benson wrote:
> IMO the default molrc should look for the rom in /usr/local/lib/mol/something
Is that Debian compliant? I'd expect the rom to be in /etc/mol/.
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lot
Fabian> Am Donnerstag, 26. April 2001 11:17 schrieb Jens Schmalzing:
>> Hi,
>>
>> I've just finished some very preliminary version of the promised
>> Mac-on-Linux packages and put them into incoming. They should
>> appear
Fabian> Installation and configuration went fine for me but MacOS
Fabian>
Hi,
Ethan Benson writes:
> the mol packages didn't come with a MacOS ROM did they?
Of course not.
Regards, Jens.
--
J'qbpbe, le m'en fquz pe j'qbpbe!
Le veux aimeb et mqubib panz je pézqbpbe le djuz tqtaj!
On Thu, Apr 26, 2001 at 06:30:08PM +0200, Philippe Lelédy wrote:
> I had the same problem, and solved it easily:
>
> your ROM is not comptatible with your MacOS
>
> Remind that for MOL the ROM is read from Linux filesystems and for
> native MacOS it is read from MacOS filesystem.
>
> So copy-st
On Thu, 26 Apr 2001, Fabian Jakobs wrote:
> Am Donnerstag, 26. April 2001 11:17 schrieb Jens Schmalzing:
> > Hi,
>
> "Ihr Computer kann mit der Systemsoftware auf diesem Startvolume nicht
> starten. Installieren Sie bitte die für diesen Computer notwendige
> Systemsoftware"
> neustart
>
> My t
Hi,
Fabian Jakobs writes:
> Installation and configuration went fine for me but MacOS won't
> boot.
Unfortunately, it is still highly unlikely that your system will boot
MacOS via Mac-on-Linux right after installation. You have to do a
fair amount of configuration by hand, most of which involve
On Thu, 26 Apr 2001, Fabian Jakobs wrote:
> Am Donnerstag, 26. April 2001 11:17 schrieb Jens Schmalzing:
> > Hi,
> >
> > I've just finished some very preliminary version of the promised
> > Mac-on-Linux packages and put them into incoming. They should appear
>
> Installation and configuration we
Hi,
Jonas Smedegaard writes:
> You don't allow access to the .dsc file - is that on purpose?
No, out of stupidity. Should be fixed.
Regards, Jens.
--
J'qbpbe, le m'en fquz pe j'qbpbe!
Le veux aimeb et mqubib panz je pézqbpbe le djuz tqtaj!
On 26 Apr 2001, Jens Schmalzing wrote:
> I've just finished some very preliminary version of the promised
> Mac-on-Linux packages and put them into incoming. They should appear
> in sid within hours, and in woody after the usual quarantine period.
> In the meantime, you can get the packages and s
Am Donnerstag, 26. April 2001 11:17 schrieb Jens Schmalzing:
> Hi,
>
> I've just finished some very preliminary version of the promised
> Mac-on-Linux packages and put them into incoming. They should appear
Installation and configuration went fine for me but MacOS won't boot. MacOS
refuses to st
On 26 Apr 2001, Jens Schmalzing wrote:
> I've just finished some very preliminary version of the promised
> Mac-on-Linux packages and put them into incoming. They should appear
Coool - I will go grab them immediately :-)
> Following suggestions on this list, I have split Mac-on-Linux into
> thr
Hi,
I've just finished some very preliminary version of the promised
Mac-on-Linux packages and put them into incoming. They should appear
in sid within hours, and in woody after the usual quarantine period.
In the meantime, you can get the packages and source from
deb http://samiel.theorie.phys
28 matches
Mail list logo
