newbody wrote:I failed to find the code for frugal install on usb but maybe it is same as above then. or it is in the file.

Before doing a frugal install, it would be great if you could boot antiX with a LiveCD or LiveUSB on the target machine that has the ntfs partition. I will assume you can do this.

You need four things in order to boot:

1. Boot loader, usually grub or isolinux
2. A kernel, usually /antiX/vmlinuz
3. An initrd usually /antiX/initrd.gz
4. a linuxfs file that contains the entire Linux system usually /antiX/linuxfs

If you can boot from a LiveCD or a LiveUSB then you already have the first 3 things. For now, I suggest you continue to use those 3 things from either the LiveCD or LiveUSB and just put the linuxfs file on your ntfs partition.

So all you need to do is copy the linuxfs file to a place on your ntfs partition and then tell us where to find it with boot parameters. Assuming you are in the LiveCD or LiveUSB environment, you need to:

1. mount the ntfs partition (if it is not mounted already),
2. create an antiX/ directory on the top level of the ntfs partition,
3. copy /live/boot-dev/antiX/linuxfs to the antiX/ directory on the ntfs partition

Finally, you need to tell us which partition the linuxfs file is on and where to find it on that partition using boot parameters. The default directory is /antiX and the default filename is linuxfs so you just have to tell us the partition. If you have only one partition, or if you don't mind us scanning all of your partitions then you just need the from=hd boot code. You could also tell us the label, uuid, or device name of the partition. I gave examples of this above. You don't need the from=hd if you tell us the device name, label, or uuid, but it is still a very good idea to include it in case, for example, you insert a cd or a usb stick that has the same label you are using for your internal drive.

The other boot options are optional. I like to use the quiet options and also set the resolution of the text consoles to either 1024x768 with vga=791 or to 1280x1024 with vga=794. You could also use vga=ask to get prompted for what display resolution to use.

The new antiX option is used to abbreviate four common antiX options:

• L = lean
• X =Xtralean
• M = mean
• D = nodbus

So antiX=LXMD enables all four of these options.

BitJam, thanks for the detailed instruction.
Anti is answering me over at the thread he made here
post23814.html#p23814

My poor English fails to make my situation clear.
I do my best but not being native user of English
I get into confusing grammar errors and Anti interpret
my words so we misunderstand each other.

His take seems to be that it should work and
my take on it is that I am a pessimist. Maybe
it works for him, why else would he suggest it?

But something about me being a total absolute noob
makes me fail to read even the easiest instruction
and fail to follow it. More by pure luck would things work here.

So maybe we could continue in that thread? The questions
are very related so we keep this thread here for those specific
for the new test iso and the special problem that I have is
better to concentrate on that other thread I link to. Hope that is okay

Much appreciated you care.

Posting from antiX-full 04 March 2012

Now I get the wicd icon in antixcc __{{emoticon}}__
As usual, I have to set in Preferences the name of of the wireless interface (wlan0 for me)
I think that in earlier versions of antiX (of wicd ?), the interface was automatically detected

Minor bug:
In live session from CD (antiX-full, with icons), I get a small empty window in the top left corner. I can move, enlarge the window. It is not a terminal (no input). I can iconify it, maximize it, but cannot kill it from the window decoration. I cannot neither xkill it. I noticed this ghost window alraedy with test1. Cannot see which process it comes from.

Going to install to HD

On the P4, mountbox does mount/unmount USB flashdrives and calls up rox-filer as root. But now need to use MC, spacefm, sunflower or a 2nd instance of rox-filer as root to copy to HDD. Permission to do this, copy or open the file or directory, as user is not there; same with a save as from eg a wordprocessor as user. The copied file stays with root permissions, whether on HDD or copied back to USB flashdrive.
Anybody else find this so?

As to my P200MMX, it is being grumpy with the CD Rom handling the install CD. It did boot the CD & cli-installer started working, but hung up. Hardware issue, not software I’m sure.
As lagopus mentioned, also get a ‘ghost window’. Minor mystery.

Same problem as in test-1 with /boot/grub/menu.lst (using minstall):
I got entries for Windows (buggy) and for my fresh install of test-2 on /dev/sda7
But my current install of test1 in /dev/sda5 does not show up

Check out my initial experiences and general comments regarding antiX, and the Test 2 release in particular. I added some links in my article to some Debian-based resources in case anyone runs into issues with wireless firmware (something that rarely happens for me with antiX), but something I periodically encounter elsewhere (particularly with Ubuntu derivatives. The links are good resources to have handy.

I did have to reinstall my wireless firmware for the Broadcom 4311 to get it working right; not sure if that is because I had it there from a previous installation, or if the firmware wasn't included in the Test 2 build, but I didn't see it, so I installed it and got everything up and running quite easily. The article I wrote is on my blog at
========= SCRAPER REMOVED AN EMBEDDED LINK HERE ===========
url was:"http://brianmasinick.blogspot.com/2012/03/initial-experiences-with-antix-120-test.html"
linktext was:"Brian's Blog"
====================================

I also have the blank window. It was there on the live cd and is also present on the full install. I have tried to kill it several ways but it will not die. So I moved it to an unused desktop for now.

I did a full install on my old sony viao laptop and is running great. All my hardware was detected and is working very well.

Success with P200MMX, cli-installer. No ‘ghost window’, login after install goes to slim, works OK. Same issues with using USB thumbdrives as with the P4 (am I missing something considering this?)

Working very well from my thumb drive. No wireless issues (Atheros AR9285). Nice work anti!

I don't quite understand how to use the wallpaper changer. Seems easy enough, but I'm not sure how to choose the wallpaper I want. Random setting on it works good though.

Really looking forward to the final release and especially antiX snapshot.

Dave

EDIT: I think I have the wallpaper changer down. LOL

Very typical of Newbody. I fail to read texts

The other boot options are optional. I like to use the quiet options and also set the resolution of the text consoles to either 1024x768 with vga=791 or to 1280x1024 with vga=794. You could also use vga=ask to get prompted for what display resolution to use.

That sets the resolution for the boot process not for the slim which one have to set
using grandr or some other set up prog.

But the sad thing for me is that it does not remember the resolution that I give it.
Can I edit some xorg.conf or something so it does remember 1024 x 768 instead
of the 800 x 600 that it gives it now by default?

System now installed, but not updated. Had the same problem as afab, with gparted. Edited gparted.desktop as per instructions. Gparted opens but no partitions are shown."No devices detected" message is visible. When gparted is summoned via terminal all is well.

When using the sux command in terminal obtained:

bash: cannot set terminal process group (-1): Inappropriate ioctl for device
bash: no job control in this shell

Edit: Seems like a known bug:
========= SCRAPER REMOVED AN EMBEDDED LINK HERE ===========
url was:"http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=659878"
linktext was:"http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=659878"
====================================


I will update system.

System updated. I needed to reedit gparted.desktop. Changes were overidden after update. Still no partitons shown when gparted is opened via menu.

the ghost window is a result of a taskbar item that starts at boot, my guess in wicd. a suggestion is to set a delay on the start of wicd taskbar icon.

dark-D it is the volume icon in the task bar. A right-click on the ghost window and I think minimise. (Don;t have icewm to test and on my box I don't get the ghost)

anticapitalista, I'm trying out antiX-test2 in VirtualBox, and I like the improvements. The biggest improvement I've seen so far is the fact that the menu is automatically updated. For my new yet-to-be-released Mint-based Swift Linux, I will be using your successful menu-icewm-antix package to provide this feature, as I've been struggling to figure out how to do it on my own.

I like the fact that you have put many features into *.deb packages, including the automatic menu updates and the control center. This makes it easier to figure out how things work, as well as make it easier to copy these features.

I applaud your support for JWM, the default window manager of Puppy Linux. The Ubuntu/Unity and GNOME 3 controversies illustrate the value of having a Plan B. I don't think the people at IceWM would make any such controversial changes, but in the unlikely event that they do, you'll have the option of switching to JWM.

I'm curious about your decisions to include LibreOffice and remove Asian fonts. Are you copying Swift Linux? If so, I'm very flattered, just as you should be flattered that I'd copy features from antiX Linux.