summaryrefslogtreecommitdiff
AgeCommit message (Collapse)Author
2013-02-26kernel-install: replace URLs with man pages in the error messagesHarald Hoyer
2013-02-26kernel-install: fixed paths in boot loader entryHarald Hoyer
For the loader entry a relative path has to be used.
2013-02-25tests: add a few more tests to test-util.cThomas Hindoe Paaboel Andersen
Add asserts on the resutls in FOREACH_WORD_QUOTED Added tests for: FOREACH_WORD strstrip delete_chars in_charset
2013-02-25kernel-install: remove LANG=Kay Sievers
2013-02-25nspawn: add --bind= and --bind-ro= to bind mount host paths into the containerLennart Poettering
2013-02-25kernel-install(8): add documentation about the configuration files usedHarald Hoyer
2013-02-25kernel-install: add kernel-install toolHarald Hoyer
2013-02-25Revert "nspawn: catch config mistake of specifying -b and args"Michal Schmidt
This reverts commit cb96a2c69a312fb089fef4501650f4fc40a1420b. It is not a mistake to pass args when -b is specified. They will simply be passed on to the container's init. The manpage needs fixing, that's true.
2013-02-25debug-shell: don't be picky, use /bin/sh rather than /bin/bashTom Gundersen
In a minimal initramfs, one might not always have the full bash available. Typically if using busybox.
2013-02-24build: remove explicit -shared in LDFLAGSDave Reisner
This doesn't need to be passed, as it's handled by libtool. Since the default for autoconf is --disable-static, this change is effectively a noop. It only matters if you pass --enable-static, in which case the static libs for systemd libraries will actually be built. Nitpicky, but this only affects systemd libs. The override for the other libs remains since these libs are always loaded dynamically and never compiled staticly.
2013-02-24journal: fix --untilPaul W. Frields
https://bugs.freedesktop.org/show_bug.cgi?id=58946
2013-02-24nspawn: catch config mistake of specifying -b and argsZbigniew Jędrzejewski-Szmek
2013-02-23test: test irreversible jobsMichal Schmidt
2013-02-22build-sys: move systemd-analyze to /usr/binKay Sievers
2013-02-22TODO: drop two itemsZbigniew Jędrzejewski-Szmek
2013-02-22systemctl: generalize action table to be usable in more action<->verb mappingsMichal Schmidt
Should be no functional change.
2013-02-22systemctl: make shutdown operations use irreversible jobsMichal Schmidt
Occasionally people report problem with reboot/poweroff operations hanging in the middle. One known cause is when a new transaction to start a unit is enqueued while the shutdown is going on. The start of the unit conflicts with the shutdown jobs, so they get cancelled. The failure case can be quite unpleasant, becase getty and sshd may already be stopped. Fix it by using irreversible jobs for shutdown (reboot/poweroff/...) actions. This applies to commands like "reboot", "telinit 6", "systemctl reboot". Should someone desire to use reversible jobs, they can say "systemctl start reboot.target".`
2013-02-22core, systemctl: add support for irreversible jobsMichal Schmidt
Add a new job mode: replace-irreversibly. Jobs enqueued using this mode cannot be implicitly canceled by later enqueued conflicting jobs. They can however still be canceled with an explicit "systemctl cancel" call.
2013-02-22systemctl: make "systemctl default" use "isolate" job modeMichal Schmidt
"systemctl default" should behave identically to "telinit N" (where N is the corresponding runlevel target number), therefore it should use isolate job mode too.
2013-02-22journal: sd_journal_get_cursor should return 0 on successZbigniew Jędrzejewski-Szmek
Documentation states that 0 is correct, and all other similar functions return 0 on success. Pointed-out-by: Steven Hiscocks <steven-systemd@hiscocks.me.uk>
2013-02-21TODO: removed ratelimitHarald Hoyer
2013-02-21fstab-generator: change kernel command line mount path for rootHarald Hoyer
Use /sysroot instead of /new_root to mount the real root in the initramfs.
2013-02-20man: be even more clear about ExecStart's first argument.Max F. Albrecht
2013-02-20tests: more tests for util.cThomas Hindoe Paaboel Andersen
tests for: test_parse_pid test_parse_uid test_safe_atolli test_safe_atod
2013-02-20man: document %%Zbigniew Jędrzejewski-Szmek
2013-02-18test-strv.c: ported test_specifier_printf() to _cleanup_free_ + assert_se + ↵Daniel Buch
cleanup
2013-02-18test-strv.c: added OOM check for current testsDaniel Buch
New OOM check patch: I do assert_se() before variable is used to do correct check.
2013-02-18test-strv.c: added strv_split_nulstr() testDaniel Buch
2013-02-18tests: add test of memdup_multiplyThomas Hindoe Paaboel Andersen
2013-02-17man: Add reason for disk model info not workingWilliam Giokas
In systemd-bootchart, the disk model information will not be found unless the root device is specified using `root=/dev/sdxY` on the kernel line. Just add a note as to why this doesn't happen.
2013-02-17bootctl: show "n/a" for empty boot option labelsKay Sievers
2013-02-17udev: usb_id: parse only 'size' bytes of the 'descriptors' bufferKay Sievers
2013-02-17udev: usb_id - ignore non-ASCII serial numbersKay Sievers
On Thu, Feb 7, 2013 at 3:52 PM, Robert Milasan <rmilasan@suse.com> wrote: > Hi, seems that using some strange usb devices with really bogus serial > numbers usb_id creates links with junk strings in it: > > /dev/disk/by-id/usb-TSSTcorp_BDDVDW_SE-506AB_㡒䍌䜶䉗ぁㄴ㌴†ँ-0:0 > > Initially was believed that usb_id is to blame, then the kernel, but it > turns out that really the usb cd/dvd drive has this bogus serial number: > > output from dmesg: > [ 538.200160] usb 1-2: new high-speed USB device number 5 using > ehci_hcd [ 538.335067] usb 1-2: New USB device found, idVendor=0e8d, > idProduct=1956 [ 538.335080] usb 1-2: New USB device strings: Mfr=1, > Product=2, SerialNumber=3 [ 538.335089] usb 1-2: Product: MT1956 > [ 538.335097] usb 1-2: Manufacturer: MediaTek Inc > [ 538.335105] usb 1-2: SerialNumber: > \xffffffe3\xffffffa1\xffffff92\xffffffe4\xffffff8d\xffffff8c ... > [ 538.337540] scsi6 : usb-storage 1-2:1.0 [ 539.341385] scsi 6:0:0:0: > CD-ROM TSSTcorp BDDVDW SE-506AB TS00 PQ: 0 ANSI: 0 > [ 539.354240] sr0: scsi3-mmc drive: 0x/24x writer dvd-ram cd/rw > xa/form2 cdda tray [ 539.354777] sr 6:0:0:0: Attached scsi CD-ROM sr0 > [ 539.355122] sr 6:0:0:0: Attached scsi generic sg2 type 5
2013-02-17efi: compare by substractionKay Sievers
2013-02-17udev: expose new ISO9660 properties from libblkidZeeshan Ali (Khattak)
2013-02-16TODOAuke Kok
2013-02-16systemctl: allow comma sepearted property listsZbigniew Jędrzejewski-Szmek
2013-02-16man: prettify systemctl(1)Zbigniew Jędrzejewski-Szmek
- reindent with two spaces, otherwise everything is squeezed near the right margin, - mark only optional arguments as optional, - some typos, etc.
2013-02-16bootchart: rename --filter to --no-filterZbigniew Jędrzejewski-Szmek
Turning off filtering with --filter is just too confusing. Config option "Filter" doesn't have to be changed, here "Filter=yes" already meant to filter.
2013-02-16bootchart: provide better error messagesZbigniew Jędrzejewski-Szmek
2013-02-16man: move bootchart README to manpage, docbooksifyZbigniew Jędrzejewski-Szmek
2013-02-16systemctl: Don't give re-activation warning if unit is maskedJan Janssen
2013-02-16systemctl: allow status with no unitsZbigniew Jędrzejewski-Szmek
This makes 'status' behave like 'list-units': systemctl status -> status of all units systemctl -t error status -> status of error units systemctl -t mount status -> etc.
2013-02-16unit: don't Require systemd-journald.socket from unitsMichal Schmidt
It is not really necessary to have a hard requirement dependency on systemd-journald.socket in almost every unit. The socket gets pulled into boot via at least two ways: sockets.target -> systemd-journald.socket sysinit.target -> systemd-journald.service -> systemd-journald.socket So just assume something pulled the socket in and drop the automatic requirement dependencies on it. "systemctl stop systemd-journald.socket" will now not take the whole system down with it.
2013-02-16execute: increase severity of journal connect failure messageMichal Schmidt
journald is supposed to work. Failure to connect to its socket implies losing messages. It should be a very unusual event. Log the failure with LOG_CRIT. Just because this unit's stdout/stderr failed to connect to the journal does not necessarily mean that we shouldn't try to log the failure using a structured entry, so let's use log_struct_unit.
2013-02-16execute: unify setup_{output,error}Michal Schmidt
The functions are quite similar. Unify them into one. The source gets shorter, the binary gets slightly smaller.
2013-02-16execute: robustness against journald failuresMichal Schmidt
Almost every unit logs to the journal. If journald gets a permanent failure, units would not be able to start (exit code 209/STDOUT). Add a fallback to /dev/null to avoid making the system entirely unusable in such a case.
2013-02-16log: fix fallbacks to kmsgMichal Schmidt
write_to_journal() returns 0 if journal_fd is closed and nothing is written. We need to make sure we'll try log_open_kmsg() then to make the fallback work for "journal-or-kmsg".
2013-02-14man: Update bootchart.conf(5)William Giokas
Recent changes in config options makes almost eveny variable in the man page obsolete.
2013-02-14bootchart: if "root=/dev" is not matched, don't try to read /sysHarald Hoyer
generated by cgit v1.2.3-54-g00ecf (git 2.45.2) at 2024-11-14 10:49:09 +0000