I can avoid Dell/Windows problems like this.

http://www.telegraph.co.uk/technology/de...aptop.html

I hope this will inspire people to learn scripting. Simple scripts like these can speed up things and make life easier. Last one is a winner

https://www.jitbit.com/alexblog/249-now-thats-what-i-call-a-hacker/

Over the course of the next few weeks I'll be slowly adding some Google ads to various parts of the website, including the Forums. In terms of growth, I'd describe our current status as 'plateaued'

To get the hardware I need to test things like UEFI, to get us a dedicated web server, to add more services for people in the community, this is a natural addition to the project, no revenue - no growth. We've survived this long without it, but to get to the next level, we need to consider all possibilities.

Linux Lite will always be free.

I installed latest version of whisker menu and I can not succeed to make it transparent.
Can some one help?

Hi guys;

My Linux Lite 2.4 system has been hanging at boot.  So when I pressed F4 to see what the problem was it read " Starting Bridge socket events into upstart.

I searched for a possible solution and found a post by Stéphane Graber (stgraber) in the launchpad.net site that said that in order to resolve the issue I have to edit /var/lib/lxc/<container>/config and make it look like something like [this]:
"""
# Template used to create this container: /usr/share/lxc/templates/lxc-download
# Parameters passed to the template: -d ubuntu -r trusty -a amd64
# For additional config options, please look at lxc.conf(5)

# Distribution configuration
lxc.include = /usr/share/lxc/config/ubuntu.common.conf
lxc.arch = x86_64

# Container specific configuration
lxc.rootfs = /var/lib/lxc/YOUR-CONTAINER-NAME/rootfs
lxc.utsname = YOUR-CONTAINER-NAME

# Network configuration
lxc.network.type = veth
lxc.network.flags = up
lxc.network.link = lxcbr0
lxc.network.hwaddr = YOUR-CONTAINER-MAC-ADDRESS

But how can I do that when I can't even boot into the damn system !

How does one restore a single file or directory in Linux Lite?  I was going through the restore process using the Backups utility (aka Deja Dup), and it appeared it was going to restore everything I backed up, when I only need to retrieve one file.

Hi I have another boot issue this and it's this when I boot my modified chromebox with Linux Lite as standalone os it boots slower than usual then when I pressed f4 the system hangs at "starting enable remaining boot-time encrypted block devices".  I googled that phrase and discovered a forum post in the Linux Mint bugs.launchpad.net site that said that in order to resolve this issue, I had to drop into recovery mode on boot, remount the root partition as read/write if necessary, edit fstab to fix or comment out the offending entry, save it and reboot. 

So rebooted my modified chrome-box and went into the grub menu and booted this distro's kernel in recovery mode and tried to edit fstab by remounting the root partition as read write and couldn't do it.  Along the way, I also discovered that terminal no longer works when pressing ctrl-alt-F1 nor does ctrl-alt-F2 nor with F3.  After trying to run fstab in recovery mode several times and discovering that it just sits there I googled this problem I found a workaround at this forum post http://unix.stackexchange.com/questions/...rect-fstab whereby I see the contents of the fstab file add init=/bin/bash to the end of the kernel command line.  So I did what is on that post and got into the fstab file and saw the phrase which is the title of this post. 

Therefore, I googled "Kernel Panic- not syncing VFS: unable to mount root fs on unknown block (0,0)" to find a likely solution for this error and found this post in the Ubuntu forum dating back to 2012 a user by the name of lemon squeeze states that If you cannot get a root prompt at all, then get a LiveCD (the cd / usb key you used to install ubuntu should work) and boot from it. Then you have a useable system from which you can access the broken one.  http://askubuntu.com/questions/116635/ke...oo-swapper.  So my question to you guys is this should I follow Oli's instructions to Boot to a LiveCD, select Try Ubuntu and then open a a terminal. Run the following:
sudo fdisk -l etc, etc in other words try to fix this my installed distro with an ubuntu live usb as shown in the you tube video : https://www.youtube.com/watch?v=L7jIAvs5bFU

[size=1em]Hi,[/size]

[size=1em]I started new thread instead of using the other thread.[/size]
[size=1em]I think this is possibly disk related..??[/size]
[size=1em]I booted a live gparted, and prepared partitions in advance. (see below)[/size]

[size=1em]"IMPORTANT" the NUC contains a "Samsung nvme pcie ssd"[/size]
[size=1em]So gparted detected drive O.K, and allowed me to create partitions.[/size]
[size=1em]Linux kernel gives an odd, but normal: /dev/nvme0n1p1[/size]
[size=1em]I decide to install LL2.6 1st and make sure everything works.[/size]
[size=1em]I ran LL2.6 Live boot USB, installed it, and it all ran O.K, no errors.[/size]
[size=1em]On re-boot I get the "grub screen"[/size]

[size=1em][img height=600 width=800]http://i.imgur.com/J4ZR8pT.jpg[/img][/size]

[size=1em]I checked Win7 still booted O.K, and it booted fine.[/size]
[size=1em]Then I re-booted and selected "Linux Lite",[/size]
[size=1em]momentary disk access, then the following: (sorry only have camera phone)[/size]

[size=1em][img height=600 width=800]http://i.imgur.com/SqFUzpz.jpg[/img][/size]

[size=1em]More Info when I re-booted a LL Live USB:[/size]

[size=1em]Couple of observations/notes:[/size]
[size=1em]1. The NUC Bios is set to Legacy & Safeboot "disabled", and the nvme pcie drive is recognised in BIOS[/size]
[size=1em]2. For the Win7 install I needed to install it initially to 2nd drive, add 2 NS hofixes, then "clone" to nvme drive.[/size]
[size=1em]    This is because Win7 does not recognise nvme pcie drives.[/size]
[size=1em]3. I think the disk order is due to the nvme pcie card being plugged direct on Mobo, and 2nd disk is on SATA port[/size]
[size=1em]4. The nvme pcie disk "Model Unknown."..?? and it's sector size 512B/512B vs other disk is 512B/4096B ??[/size]

[size=1em]Googling shows nvme pcie drives appear to be problematic in terms of setting up for Linux Boot[/size]
[size=1em]I got confused, when discussions centred around UEFI & GPT started to be discussed, no mention of "Legacy scenario"..!![/size]
[size=1em]So more research needed, but any comments welcome [/size]

[size=1em]Below we have some code that I expected would evaluate the variable %t before loading the relevant web page. It doesn't work it simply uses %t as a literal string.[/size]

[size=1em]I know the variable itself works fine so I'm wondering if the code is just badly formatted or the problem needs to be approached differently.[/size]

[size=1em]Thought this would be easy but now it's driving me mad. A green glow for the first one with a solution.[/size]