[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Axiom-developer] 20081202.02.tpd.patch (website download.html add D

From: William Sit
Subject: Re: [Axiom-developer] 20081202.02.tpd.patch (website download.html add Doyen Thumbdrive)
Date: Fri, 05 Dec 2008 01:45:08 -0500

Hi Alfredo:

Thanks for the quick suggestion. I'll try that this weekend when I have more time.

The following report probably is unrelated to Doyen (or Axiom), but more to BIOS and drivers?

One minor "complaint" or rather "bug report": Doyen is not supposed to alter the machine or original OS. However I have found that, on my laptop (Acer Travelmate 7520G running Windows Vista Home Premium, SP1), the time of day (or perhaps the time zone, I'm not sure which) is always altered after I shut down Doyen and reboot to Windows Vista. This happens even when I simply do a restart right after booting up. I suspect this is due to Doyen modifying the time or time zone setting, say to manual instead of from internet time, since manual is the setting I got after rebooting to Windows even though I reset it back to internet time. If this is correct, then Doyen might have modified some BIOS setting. Alternative theory: internet is not connected early enough in the boot process and the time zone is not set/reset correctlly (although the choice presented always has, in my case, Eastern US, as the default). I am not certain whether the time during Doyen is correct or not. I think it is.

Also, while Doyen recognizes the wireless hardware (Broadcom BCM 43 family), the driver does not seem to recognize the on/off switch that controls the wireless (kind of like *the switch*, not the hardware itself, is disabled). This is probably again a BIOS and driver problem.

Thanks again for all your hard work on the Doyen project.


On Thu, 4 Dec 2008 10:19:34 -0500
 "Alfredo Portes" <address@hidden> wrote:
Hi William,

I will address your email in more detail later, but I will like to
make a quick remark.

Doyen is created using Linux Live Scripts:

In the documentation we have this:

"1) persistent changes
Use 'changes=...' boot parameter to specify persistent changes directory or file. If a directory is used, eg. changes=/some_dir/ and the /some_dir/ is found on some partition on your disk, then all the changes made to the root filesystem will be saved to that directory. This works even if /some_dir/ is on NTFS or VFAT, thanks to posixovl overlay (an userspace filesystem, already included). Important note: if you plan to save changes on VFAT, make sure to modify your distribution's shutdown scripts. It must not execute killall, else posixovl is killed and everything is wrong. Instead, call the cleanup script from /mnt/live/cleanup. If a file is specified for the changes boot parameter, eg. changes=/path/file.dat, and the file has a valid filesystem inside, then the file will be loop-mounted and changes written to it. You may also use changes=/dev/sda1/path/ and changes=/dev/sda1/path/file.dat ... to specify particular device where to look for. Other devices will be skipped (will not be even

You make want to give it a try. I will try to document all this later
on (once I get to test it

Thank you for the feedback.


William Sit, Professor Emeritus
Mathematics, City College of New York Office: R6/202C Tel: 212-650-5179
Home Page:

reply via email to

[Prev in Thread] Current Thread [Next in Thread]