MX-14 beta 2

[BitJam]

Would this be correct?

Code: Select all

df -h $/media/backup-2013

Drop the dollar-sign:

Code: Select all

df -h /media/backup-2013

I was trying to copy files from a hard drive 130 gig sda1 formatted as ext3, and only holding data to a 1 Gig external hard drive " /media/backup-2013 formatted as ect4" not to a usb flash drive. Not a NTFS formatted hard drive.

If you are interested or curious, I suggest you Google(fuse hidden file). There are many complaints about not being able to delete these files. I got the impression they only showed up on fuse mediated filesystems but maybe I was wrong.

All the problems started when the .fuse file appeared. [...] Maybe this was another instance of the tumber bug.

I suggest you turn tumbler off. It was off by default in beta-1 and will likely be off by default in beta-3 and beyond. Something strange happened on your system. Hopefully you will not encounter it again which would mean we probably will never find out what actually happened.

[golinuxgo]

And, again, just a reminder that MX-14 is not designed for low-end machines--where antiX rules.

This is a "midweight" distro.

I previously had squeeze with gnome2 and xfce desktops installed on this machine so I thought MX-14 might work OK. Unfortunately I don't have free space on my other testing machine to install MX-14 right now.

Here's a followup on my attempt to install MX-14 posted here. This time I tried the command line install. I told the installer to put grub on /dev/sda1 (root) not the mbr (there isn't one). It reported completion but when I rebooted there was no grub, just a blank screen with a cursor. Couldn't bring up the console. No keyboard. No nothing. It was just dead. So I popped in the refracta live disk and tried to chroot into mx1 to reinstall grub. I had never tried this before but have read quite a bit. Anyway, this is the resulting message:

/boot/grub is not readable by GRUB on boot. Installation is impossible . . .

I have no idea where the install went sideways. But I do know that refracta (with xfce) installed and booted successfully shortly thereafter. Sure it lumbers along and the internet is not really usable. But it BOOTS and WORKS! I have retired that old 'toaster' for now but may try to install AntiX on it when I have some spare time maybe this summer.

Final comment . . . this has been the crankiest distro, I've ever played with. I really, REALLY wanted to like it but it seems it was not meant to be. Bummer. Maybe the final release will have the kinks worked out . . .

[lucky9]

This time I tried the command line install. I told the installer to put grub on /dev/sda1 (root) not the mbr (there isn't one). It reported completion but when I rebooted there was no grub, just a blank screen with a cursor. Couldn't bring up the console. No keyboard. No nothing. It was just dead. So I popped in the refracta live disk and tried to chroot into mx1 to reinstall grub. I had never tried this before but have read quite a bit. Anyway, this is the resulting message:

There isn't one? No MBR? What do you have?
If you don't install GRUB to the MBR you won't get to the /boot/grub/menu.list which is where the OS will boot from. You didn't use another distro to chainload either. How could you think you could boot the OS? There has to be a way for /boot/grub/menu.list to be called so it can boot the OS.

[golinuxgo]

This time I tried the command line install. I told the installer to put grub on /dev/sda1 (root) not the mbr (there isn't one). It reported completion but when I rebooted there was no grub, just a blank screen with a cursor. Couldn't bring up the console. No keyboard. No nothing. It was just dead. So I popped in the refracta live disk and tried to chroot into mx1 to reinstall grub. I had never tried this before but have read quite a bit. Anyway, this is the resulting message:

There isn't one? No MBR? What do you have?
If you don't install GRUB to the MBR you won't get to the /boot/grub/menu.list which is where the OS will boot from. You didn't use another distro to chainload either. How could you think you could boot the OS? There has to be a way for /boot/grub/menu.list to be called so it can boot the OS.

Good heavens! I've been using distros with grub2 for the last 3 years at least, probably longer. This distro doesn't??? I can barely remember /boot/grub/menu.list . . .

[richb]

[
Good heavens! I've been using distros with grub2 for the last 3 years at least, probably longer. This distro doesn't??? I can barely remember /boot/grub/menu.list . . .

It does use grub2 and there is no /boot/menu.list in grub2 as you said.

[ko]

This time I tried the command line install. I told the installer to put grub on /dev/sda1 (root) not the mbr (there isn't one). It reported completion but when I rebooted there was no grub, just a blank screen with a cursor. Couldn't bring up the console. No keyboard. No nothing. It was just dead. So I popped in the refracta live disk and tried to chroot into mx1 to reinstall grub. I had never tried this before but have read quite a bit. Anyway, this is the resulting message:

There isn't one? No MBR? What do you have?
If you don't install GRUB to the MBR you won't get to the /boot/grub/menu.list which is where the OS will boot from. You didn't use another distro to chainload either. How could you think you could boot the OS? There has to be a way for /boot/grub/menu.list to be called so it can boot the OS.

You're (nearly) absolutely right, but it's /boot/grub/grub.cfg, NOT /boot/grub/menu.list

[uncle mark]

Good heavens! I've been using distros with grub2 for the last 3 years at least, probably longer. This distro doesn't??? I can barely remember /boot/grub/menu.list . . .

It does use grub2 and there is no /boot/menu.list in grub2 as you said.

Yeah, lucky got his terms mixed up a bit, but...

The OP still needs to explain how he expects to boot MX-14. If he put grub on root, then he has to invoke it from some other method.

[GuiGuy]

........
Final comment . . . this has been the crankiest distro, I've ever played with. I really, REALLY wanted to like it but it seems it was not meant to be. Bummer. Maybe the final release will have the kinks worked out . . .

Your opinion appears to be based on trying MX on an unsuitable machine.
My opinion is very different: this is the most promising beta I have ever played with.

[whell]

........
Final comment . . . this has been the crankiest distro, I've ever played with. I really, REALLY wanted to like it but it seems it was not meant to be. Bummer. Maybe the final release will have the kinks worked out . . .

Your opinion appears to be based on trying MX on an unsuitable machine.
My opinion is very different: this is the most promising beta I have ever played with.

Ditto. My beta 2 has been running steady for a week, and nary a hick-up. I've streamed audio and video, served music and video files, traded files with my wife's Windows box, and all has worked great.

[kmathern]

I just pulled out an old HP Celeron computer that hadn't been booted in over 500 days. It had an old squeeze install that I was using to play with window managers etc. MX-14 live loaded but there were problems. QupZilla crashed every time it tried to pull up a web page. The page would appear for a few seconds and then . . . poof....

... Maybe you gurus will see something in there that could be a problem:

Code: Select all

$ inxi -F
System:    Host: mx1 Kernel: 3.12-0.bpo.1-686-pae i686 (32 bit) 
           Desktop: Xfce 4.10.2 Distro: MX-14_13.98_386-xfce beta2 30 January 2014

Machine:   No /sys/class/dmi, using dmidecode: you must be root to run dmidecode

CPU:       Single core Celeron (Coppermine) (-UP-) cache: 128 KB flags: (pae sse) clocked at 664.621 MHz 

You have the SSE2 problem noted in these two threads: http://forum.mepiscommunity.org/viewtop ... 91&t=35543 & http://forum.mepiscommunity.org/viewtop ... 91&t=35541. Your Celeron/Coppermine cpu lacks sse2 support, so any web page you go to with flash content will crash Qupzilla.