For general announcements.
Sat Nov 15, 2014 3:31 pm
idunno whether line 37 is the line being parsed within the ob menu file or line number in the calling script but
"not well-formed (invalid token)" means a stray character exists withing the menu file.
Could be a misspelling <cate gory> or <categor;>
or <!-- a comment tag containing -- an inline dash character can choke the parser -->
If "line 37" isn't an accurate pointer, try diffing a backup copy of the menufile against the current file.
Sat Nov 15, 2014 9:40 pm
I get what looks like the same error. Didn't read every word. I edited the menu in geany and had no trouble - added the commands for halt, reboot, etc. What changes are you trying to make, and what is it doing?
Sat Nov 15, 2014 9:47 pm
I ran upgrade and dist-upgrade
and there were no troubles regarding systemd and libsystemd0, both are still not installed.
I have to run dpkg-reconfigure console-data after each boot and set it to German.
I recall it would be kept over reboots.
live-boot is installed, i realized after the new kernel was installed.
Does that make sense?
Sat Nov 22, 2014 11:45 pm
In case you missed it, a mention of Refracta on -user today:
https://lists.debian.org/debian-user/20 ... 01516.html
Sun Nov 23, 2014 2:46 am
@golinux: nice little review there. Too bad there's so much noise on that thread.
@nadir: when you run 'dpkg-reconfigure console-data' does it change the settings
in etc/default/keyboard?
Sun Nov 23, 2014 3:09 am
fsmithred wrote:@golinux: nice little review there. Too bad there's so much noise on that thread.
There's way too much noise on the LIST period! But that's a good thing for a number of reasons. I guess you won't know whether a systemd-free Jessie will truly be possible until stable is released . . .
Sun Nov 23, 2014 4:08 am
Yup. etc/default/keyboard didn't get changed. I replaced us with de and after reboot tty was with a german layout. Thanks.
I probably have used reconfigure console-data on liveCDs. I haven't used tty in a long time, i usually use a terminal from X.
But on this low-resources laptop it makes sense to not run X when not needed.
-
kFreeBSD still works without systemd too, btw (and with sysv, which might be surprising). I made a further installation, rather painless (well: like a Debian Linux installation. enter -enter- enter ... done).
Looks as if refracta and exgnulinux are the only projects who care for it. And, let's face it, that are mainly two persons.
I am impressed.
Sat Nov 29, 2014 5:30 am
dzz wrote:- Code:
:~$ cat package_list | grep systemd
:~$
When I run this command, I get:
- Code:
$ cat package_list | grep systemd
cat: package_list: No such file or directory
What am I missing?
Sat Nov 29, 2014 11:42 am
golinux wrote:dzz wrote:- Code:
:~$ cat package_list | grep systemd
:~$
When I run this command, I get:
- Code:
$ cat package_list | grep systemd
cat: package_list: No such file or directory
What am I missing?
1. You need to have a filed named package_list. You can make one with
'dpkg -l > package_list'
or you could replace "package_list" with the full path to the package list, which is /lib/live/mount/medium/pkglist.../package_list when you're running live.
2. Useless use of cat. Just 'grep something package_list'
Sat Nov 29, 2014 1:50 pm
I am pretty sure package_list was included on the iso's, in one of the folders of /home/user
I was wondering wyh dzz proposed to do that instead of simply running dpkg -l | grep systemd, so i checked. Else, if i wouldn't have wondered, i wouldn't remember.
If in doubt do "locate package_list" or "find /home/user -name '*package_list*" (assuming i remember right it was in home. Else you will have to use fine / -name '*package_list*". If both, find or locate, give no result, than i remember wrong. I prefer locate as it is easy.
Well: perhaps i did locate and remembering it was in home is wrong. fsmithred seems to say it is elsewhere ...
Powered by phpBB © phpBB Group.
phpBB Mobile / SEO by Artodia.